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.

I will push an update for TSupport. No valid key right now so use Force Mode.

If you already use Force Mode with latest TSupport and still didn't pass the integrity. You will need to set security_patch.txt :

Open this directory /data/adb/tricky_store create a file security_patch.txt then write this text :

system=prop
boot=prop
vendor=prop

then click TSupport action and select Force Mode. Check the Integrity.

If status persist try this :

system=202509
boot=prop
vendor=prop

then click TSupport action again with the same step.

Guys, I will be using A12 from now.

Sadly there is no custom recovery supported for A12 for my device.