How to setup.

Ensure that you already read #guide and #basic. Read this by sending the hashtag to the chat.

Here the step :

First, you need to know what changes to latest version. [1]

Second, you need to set the configuration. [2]

Third, run TSupport-Action. Select Fprint-updater, until you see a prompt hold your screen it will set all to default. Do the same for Bbox-updater.

Fourth :
1. reboot device.
2. check device certification. [3]
3. click fix device certification. [4]
4. check integrity. [5]

If you already follow all the instructions, and still can't pass any integrity, you can ask in chat. But make sure you ALREADY TRIED THE STEP.

Bad News For Me

My SDCard corrupted. SDCard is nto accessible. I tried the old method to fix but not working. I have lot of data in the SDCard. Should I format it ?

Data Loss

I was unable to recover the data and, in the process, inadvertently corrupted everything. As a result, I had to format the SD card to make it usable again.

Unfortunately, I have lost my noscripts, including the bbox checker, bbox obfuscator, and others.

I am now in the process of rewriting the noscripts from scratch. I was able to recover the TSupport files from multiple sources outside of the SD card. However, everything that was inside my SD card is corrupted.

RCS & GWallet/GPay

I found the way how you can pass meet system requirements. You will need LSPosed and HMA/L.

First, here the work directory you need to know to configure everything.

You need to create new file stop-tspa-auto-target then configure customize.txt :

com.android.vending!
com.google.android.gms!
com.google.android.gsf!
com.google.android.ims!
com.google.android.contactkeys!
com.google.android.safetycore!
com.google.android.apps.messaging!
com.google.android.apps.walletnfcrel!
com.whatsapp!
com.whatsapp.w4b!
io.github.vvb2060.keyattestation!
com.reveny.nativecheck!

Next configure hma.txt :

com.android.vending
com.google.android.gms
com.google.android.gsf
com.google.android.ims
com.google.android.contactkeys
com.google.android.safetycore
com.google.android.apps.messaging
com.google.android.apps.walletnfcrel
icu.nullptr.applistdetector
com.reveny.nativecheck

Third after this setup, click TSupport action then update fp, and configure all to false. Restart/Reopen HMA/L to make sure new configuration applied.

To use RCS, try to install Carrier Services from Play Store. If still not working maybe your provider is not supported.

Take note, you need to use R250817 or later. Make sure to set verified boot hash. Also, you need to wait till the next day [UTC+0] for your wallet to pass system requirements. [ CACHED ]

If your wallet still not meet the security requirements try to put

com.google.android.apps.walletnfcrel!

instead

com.google.android.apps.walletnfcrel

into the hma.txt, this config are recommended for A14+.

Additional Tips :
https://news.1rj.ru/str/CitraIntegrityTrick/566

Everything working fine.

Hey guys, I have a problem since a long time. This related to mobile internet connection, I have put my telco card to other phone to test if this cause by the telco connection problem.

What I found is that on another phone it give me a stable and fast connection. But when I put it back to my phone it has bad connection result. I cant even use the Internet to watch YouTube ( Laggy and Slow ).

So, anyone experiencing the same ? May I know how you solve this ? Or this cause by ROM ? I am currently on HyperOS and this is StockROM.

So, it fixed after return to MIUI.

Guys, send me HMA/HMAL download link. Will add it to notes

Hey guys, on MIUI. I have problem with Gpay then I notice that my HMAL is not working properly.
So I try to find what the problem, but nothing. I think its a bug because its not working. So I changed to HMA and it work.

Finally today, my Gpay pass security requirements. I have tried to fix this before, because the result is cached so I take like 4-5 day to find which one work to pass.

Tips Updated!

Key Revoked!
Use SpoofProvider.

Released ( R250917 ).

If you already familiar with old setup. Just use manual setup.

Denoscription for Force Strong :

- Used to spoof bootloader, and get device certified.

Issue:
- Play Integrity is not working properly.
- Some app that use full Play Integrity check might not working.

Have you wonder ... what kind of setup CIT use ?

My Setup :

KSU Next ( Magic Mount ~ LKM ) :
• Zygisk Next
• PIF Inject 4.3s ( KOWX712 )
• Tricky Store
• TSupport Advance ( Latest )
• LSPosed ( JingMatrix )

LSPosed Module :
• HMA
• CorePatch

Device Environment:
- Stock ROM ( MIUI 14 ~ A13 )
- TEE status NORMAL
- SeLinux status ENFORCING

Others Additional Setup :
https://news.1rj.ru/str/CitraIntegrityTrick/750

Remember to spoof security patch, mostly for custom ROM and old device.

Spoof your Boot Hash.

Play Store and GMS/F detection ensures device integrity through multiple checks. They verify SELinux status to confirm enforcement, validate the device fingerprint, and examine the keystore to ensure the bootloader is locked and not revoked. System properties are reviewed for bootloader and custom ROM traces, while suspicious apps like Magisk, KernelSU, or Apatch are flagged if present. Kernel versions are analyzed to detect custom builds, and boot hash verification confirms chain-of-trust integrity. Lastly, OS, vendor, and boot patch levels are inspected to maintain compatibility with the latest Play Store and GMS/F requirements.

I recommend rebooting your device using the physical power button instead of the reboot button inside the Root Manager. The Root Manager’s reboot option can potentially damage your MicroSD card, as it likely performs a direct reboot without following the standard system reboot procedure. This means the system fails to unmount the MicroSD properly during the reboot process, which can result in data corruption or filesystem errors on the card.

Based on my experience, I never get the corrupt issue anymore. After flashing a module I do reboot from the power button instead of clicking the reboot button directly from Root Manager.