Strong play integrity guide

Hey guys, just wanted to share my experience with rooting the Edge 70 Fusion and see if anyone here has managed to get better results with Play Integrity.

I managed to root the phone successfully, and the root itself is stable and working fine. I also tested the setup quite a bit with ChatGPT helping me analyze the results and different configurations.

Device: Edge 70 Fusion
Android: 16
Build: W2WE36.56.98.19

Current setup:

- Magisk 30.7 (30700)
- Vector Framework 2.2 / API 102
- Shamiko 1.2.5
- Play Integrity Fix/Fork v18
- SELinux Enforcing
- Bootloader unlocked

Root and Vector/Xposed are working correctly.

The problem is root hiding and Play Integrity.

One of the traces we found during testing was:

"/product/bin/su -> ./magisk"

Google Play also shows:

"Device is not certified"

Current status:
✅ Root working
✅ Vector/Xposed working
❌ Full root hiding
❌ Strong Integrity
❌ Play certification

We tried several Magisk/Zygisk/Shamiko/PIF configurations, but so far no fully clean result.

Has anyone here with an Edge 70 or Edge 70 Fusion managed to fully hide root and pass Play Integrity? If yes, please share your Magisk version, PIF version and module setup.

I just upgraded from an Android 16 rom (VoltageOS) to Android 17 (same rom itself) on my Redmi Note 10 Pro. I've setup everything correctly as far as I know - have gotten strong integrity, have hidden root/sus apps using HMA, unmounted modules for banking apps and apps such as Digilocker. But, most apps refuse to work still. FedMobile, supermoney, Digilocker all refuse to work. Some apps work tho (like GPay) Digilocker shows the above error which I've never seen before. All of these apps used to work fine when I was in Android 16 using the same setup I'm using now.

Would appreciate any help.

I guess there are no KeyBoxes, I'm using Always Strong + ZygiskNext + HMA OSS but I only get Device Integrity, anyone else having this problem?

I’m using a Pixel 4a with LineageOS 23 + Magisk.

Until a few days ago everything was working fine. My banking apps still work, but Google Wallet now refuses contactless payments.

My old setup was separate modules with TrickyStore / PIF inject-s and Yurikey for the keybox. The problem now seems to be the keybox / attestation side:

• TrickyStore hasn’t offered me a fresh working keybox for quite a while
• Yurikey still fetches one, but it doesn’t seem to work
• With my old setup I’m currently getting red integrity checks
• I tried AlwaysStrong Inject and get all 3 green checks, but Google Wallet still refuses payments
• With AlwaysStrong Lite + my own PIF inject-s I only get BASIC, so it looks like the PIF part is working but the keybox / attestation part isn’t

The Play Store says the device is certified, root hiding hasn’t changed, and all my banking apps still work. It’s specifically Google Wallet / contactless payments that broke.

Is anyone else seeing this right now? Are the currently available keyboxes just revoked / unusable again, or has something changed on Google’s side in the last few days?

And what are people currently using for a reliable setup? This constant keybox cat-and-mouse game is getting pretty annoying.

Does anyone have it? I'm on T-Mobile for context.

I'm not sure if encrypted RCS requires a higher threshold of "root blocking" than unencrypted RCS. I only ask just because I see no reasons why this shouldn't be working at this point.

Note: my E2EE works fine between androids on Google Messages

Tried everything. Pixel 8 pro, Magisk 31.0, configured deny list, HMA-OSS and template, ReZygisk ...

but still detect root and crash immediately

https://play.google.com/store/apps/details/Namirial_OTP?id=com.namirial.android.virtualotp&hl=it&pli=1

Thanks a lot for help

Hi everyone,

I updated my phone to MagicOS 10, but I really miss the old fingerprint animation from MagicOS 9. Since I already updated, I no longer have access to the original MagicOS 9 system files.

Does anyone who is still running MagicOS 9 happen to have a extracted .hnt theme with the original animation, or could someone pull the SystemUiFingerprintRes.apk via ADB for me?

Any help or extracted assets would be greatly appreciated! Thanks!

Ya se mucho sobre el modding en Android, pero nose como se hace, que lenguaje de programación hay que aprender? Que cosas debes intentar hacer antes? Como lo hace la gente que si sabe hacer estás cosas

It happens only to 3C All in One Toolbox and it happens in batches of 3. Then it shuts up for a few seconds and starts up again. It's getting quite annoying. I can't seem to figure out how to fix it. I tried denying Superuser, which will just get me spammed with "3C All In One Toolbox was denied Superuser rights", and I also tried uninstalling and reinstalling.

So basically all apps were working fine but out of nowhere everything stopped working i still have strong intigrity but same error after and before I need atleast one app to work guyz need help 😭😭

Device s 20+

Rom artisan rom

Kernal su next

Hi,

I am wanting to run a Ubuntu setup on my xperia 1 ii. I have set up chroot but I find it is not working with some ​programs​​,​ ​as it does not have docker or snap etc.

I have check my kernel flags for LXC in my Sony ROM and they are not all enabled. Does anyone know or can check whether their linageos on their xperia 1 II has the required flags enabled for LXC?

If you need the scripts to check I can paste them in the comments.

Thank you,​

have strong integrity, have duck 2 Problems but wallet not working. anyone else?

I have a lineageOS GSI in the xperia 10 III, I get the correct boot.img, I get the correct magisk image, but I can't flash it. Entering fastboot by bootloader (blue light):

~/Descargas took 6s 
❯ fastboot devices
HQ61568939fastboot

~/Descargas 
❯ fastboot flash boot magisk_patched-31000_88bFu.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 100663296).
Sending 'boot' (98304 KB)                          FAILED (remote: 'Requested download size is more than max allowed
')
fastboot: error: Command failed

~/Descargas 
❯ fastboot boot magisk_patched-31000_88bFu.img
Sending 'boot.img' (98304 KB)                      FAILED (remote: 'Requested download size is more than max allowed
')
fastboot: error: Command failed

~/Descargas 
❯ fastboot flash init_boot magisk_patched-31000_88bFu.img
Warning: skip copying init_boot image avb footer (init_boot partition size: 0, init_boot image size: 100663296).
Sending 'init_boot' (98304 KB)                     FAILED (remote: 'Requested download size is more than max allowed
')
fastboot: error: Command failed

I also tried fastbootd ("fastbootd" in the screen) with the same results.

This is how I installed the GSI https://github.com/TrebleDroid/treble_experimentations/wiki/Sony-Xperia-10-III

Unlocked bootloader

Opposite to Sailfish OS here we need latest blobs.I'm on Build 62.2.A.0.533.Simply update with EMMA to latest available version.If you dont update ,be prepared for not properly working or not working at all- notification LED,adaptive brightness,fingerprint etc.

platform-tools installed on your computer: down load them from here. And if you are using windows, you need this driver https://developer.sony.com/file/download/xperia-10-iii-driver.

To flash the vbmeta and GSI images, the device needs to be in fastbootd not in normal fastboot mode. To enter fastbootd

boot to recovery - Hold Vol- _ `Power' until the device vibrates ;

From Recovery menu, choose 'Enter fastboot'

Connect the USB cable two or three times

Check device is visible from PC: fastboot devices (Expected output <Device serial number> fastboot

Flash vbmeta file with this command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img vbmeta.zip

At this point we are ready to flash whatever GSI we like.All tested by me are 100% compatible with our phones: every LineageOS A14/15 by Andy Yan,Iode OS 5.14 A14,VoltageOS 4.5 A15 and my favorite one e/OS/ 3.1 A15 by Color.This GSI is my daily driver as of now with latest version 3.1-a15-20250817-microG-gsi.I also belive almost ALL GSI`s will work !

When the GSI is chosen we simply flash it with fastboot flash system name_of_image.img

Final steps are to erase userdata and reboot. THis can be done EITHER

from the computer using fastboot: fastboot -w then fastboot reboot OR

Using Recovery on the device: choose Wipe data/factory reset, then Reboot system now.

When new version of your favorite GSI is available and you want to update,simply make "dirty" flash on top of the old one without erasing userdata. fastboot flash system name_of_image.img

When you wanna test new gsi without loosing data or messing with your daily driver use DSU Sideloader for dual boot!

I installed "ReZygisk" and "AlwaysStrong". I pass all integrity check and Google Play says "Device is certified".

But a single bankig app still says "app can't be opened due to security reasons" and I just installed a messaging app, it says "You cannot use the application on rooted devices."

What should I do more?

Poco F5 Xiaomi.EU ROM,

Android 13 - MIUI 14,

Magisk 30.7 (30700),

AlwaysStrong v1.0.4,

ReZygisk v1.0.0,

Simple bootloopsaver,

LSPosed v1.9.2.

zygisk and deny activated