- Jan 19, 2015
Pixel 7 Pro
Pixel 7 Pro
Original post updated, thanks.
Pixel 7 Pro
Pixel 7 Pro
That's what I thought but others have brought it up in recent pages of this thread so I wasn't sure if I was missing something.MHPC is deprecated. And the fingerprints for our device aren't even available through it so might as well not have it at all.
This version seems to be working great for me on my Pixel 7 Pro with Feb patch! CTS profile passes consistently now and I am meeting both basic and device integrity. I didn't clear data for anything, just installed this test version over the previous 3.0 mod and all seems good. Thanks a lot for your hard work!
This seems to work on Pixel 7.
You sir are a Chad. 7pro CTS passing again as well as MEETS_DEVICE_INTEGRITY.
Can confirm it's working on Pixel 7. This is only module installed.
@Displax Thank you for all your hard work. Working fine on P7P
Just an update on this, I've noticed that Google wallet occasionally says my device may be jailbroken or running uncertified software and tap to pay won't be available, however it still works and SafetyNet still passes (the pay contactless setup in wallet also says my phone meets security requirements). It didn't happen before on kdrag0n's USNF 2.4.0 (before the background GPS update too presumably) so I'm not sure why this is occurring. Always scares me to see that pop up haha but I suppose as long as tap to pay is still working and SafetyNet is still passing then it's fine.
I'm on a similar setup although just "2.4.0", I need to look around for "2.4.0_MOD_1.2" in particular to try that out.
Yes! I was trying to find the link for that mod. This worked. Thanks!With Integrity and CTS do you refer to the deprecated SafetyNet or the 'new' Play Integrity API?
Also, are you using USNF from this thread or the newer/better safetynet-fix-v2.4.0-MOD_1.2 from the other thread?
Look into the other USNF thread from Displax and find more info in the thread about GPay
Btw, banking apps do not rely only on PI API - they try many other detections od root, hence you might need (things vary from app to app) Shamiko, Hide My Applist or even the Magisk Delta fork
The best would be to search through the Magisk related threads here on XDA, how the other user(s) solved the root detection from your particular banking or similar app
With Integrity and CTS do you refer to the deprecated SafetyNet or the 'new' Play Integrity API?so I'm on android 13, pixel 6a. Got Integrity and CTS match and also Play Store as Certified. Although, still no google pay or banks access. Any hints to get this working or it this fix not fully functional on 13 as of yet?
Please make 'Universal Play Integrity Fix' ... #204
Fixes to expand 'Universal SafetyNet Fix' to become a 'Universal Play Integrity Fix' are needed.
The SafetyNet Attestation API is deprecated and has been replaced by the Play Integrity API.
New Play Integrity API is rolling out from June 2022, and evidently Google Play Store and Google Pay/Wallet are already using its verdict.
June 2023 is the Migration Deadline for app developers. This will also allow their older app versions to continue working with SafetyNet API for a limited time.
June 2024 is the End of life for SafetyNet API; its attestation will no longer work for any app version, and apps will receive an error.
The new Integrity API has more strict requirements for passing attestation, and this seems to be enforced in Android 11+ particularly.
Currently (evidently due to this), device security issues are detected by
I'm guessing that the 'passing' messages based on the old SafetyNet API are likely to realigned soon.
- Google Pay/Wallet, which may state "You can't pay contactless with this device...(Your phone doesn't meet software standards)" on updating or attempting to add a card despite in-app Contactless setup stating "You're ready to pay contactless with your phone (Your phone meets security requirements)", and
- Google Play Store, which may no longer show apps like Netflix w/ Android 11+ (developers can 'exclude devices from their app's distribution based on their device integrity . Device exclusion is based on the latest device integrity verdict that the Play Store app receives from the Play Integrity API') despite in-app settings showing Play Protect 'Device is certified' result.
A workaround that evidently allows Play Integrity API attestation to pass (and solve Wallet / Play Store issues also) has been discovered. It involves spoofing an earlier certified ROM, generally by using MagiskHide Props Config module to change fingerprint prop to one for Android 10 or earlier.
Undoubtedly other apps will begin to detect broken TEE etc / fail as they migrate or begin integrating the Play Integrity API.
A 'Universal Play Integrity Fix' will evidently require more understanding / research into how the fingerprint prop is used, and possibly other new behaviours.