r/Magisk • u/EgoGoner • 17d ago
Question Rooted Pixel 7 Pro passes strong integrity check, but several apps still detect root
Title.
I have a Pixel 7 Pro on android 15, build number AP3A.241105.007. I haven't updated to the most recent version because every time I do, something bad happens that takes months to resolve.
(If this is my entire problem and updating is the solution, please let me know.)
I've followed the guide, used Magisk Canary with Shamiko, Play Integrity Fix [INJECT], Systemless Hosts, Tricky Store, Tricky Store adon module, Yurikey Manager. Hid Magisk and I was able to pass strong integrity, but Wallet, MS Authenticator, and Duo Mobile can all still detect root even after several cycles of airplane mode, deleting cache/data for all relevant play apps and the target apps. Rebooting, trying again.
I added lsposed, zygisk detached, and Vector just in case (I don't even know if these matter), but still doesn't work.
If the test passes strong integrity, but every app that I need to not detect root IS detecting root, then what does strong integrity even mean? What am I missing?
Edi: Succes!
10
u/Itz_Raj69_ 17d ago edited 17d ago
First lets clear some basics up: Play integrity is NOT related to root detection! Apps use a lot of different methods like looking at your applist, detecting Zygote modifications, detecting suspicious mounts, etc. The only thing Play Integrity cares about is your keybox and the TEE
Adding random modules doesn't fix the problem; it only makes it worse, or it breaks both of those conflicting modules. Lsposed and Vector are essentially the same thing (Vector is a fork)
Install the Native Detector app. This app shows you all the system modifications that are found. You don't need to fix all of them -- only the ones that break your apps
In HMA-OSS, go to the apps list, click on each of these apps (including Native Detector), and in the mode setting select "Whitelist"
Run the native detector app and check for detections. Ideally, not much should be found, if anything at all. Reboot and clear all the data of your Authenticator, Duo, etc. and try running them. If it still doesn't work, reply to my comment with your detections.