some of us recommend doing the airplane mode thing for Google Play Store/Google Play Services when trying to pass the Integrity test after installing Magisk
not necessary for the average app
Is this better than originalSo, here is my modification of USNF with Play Integrity API bypass.
It changes fingerprint to old
22.214.171.124 (LOL) and apply it only for GMS SafetyNet process (by Zygisk injection), so your original prints/security path level does not change. This avoids many side effects/problems with global props changing.
Bypassing DEVICE_INTEGRITY for devices that shipped with Android 13+ (Pixel`s 7 )
Drop fingerprint to lowest possible (6.0) to ensure that no one use same Android version
1. Delete/disable/reset MagiskHidePropsConfig (if installed).
2. Just install it over old Universal SafetyNet Fix and reboot device.
3. You may be needed to wipe GMS data (not cache) if there is no result immediately.
Many thanks to @1nikolas for integrity checker.
Source code: https://github.com/Displax/safetynet-fix/tree/integrity
Did you read what you quoted?
Wait this module will be updated ”within days”?He's possibly still asleep as its 5:30AM Sydney time, or starting his walk up his belltower on the way to work
USNF MOD v.2: Bypassing DEVICE_INTEGRITY for devices that shipped with Android 13+ (Pixel`s 7 )
It functionally makes no dfifference if youre
a) already passing with the non-modded one
b) whether you use v1.0 or v2.0 of the Modded version, if the non-modded one doesnt work, unless youre on a device launching with A13...
All the above will be moot wihin days when kdrag0n rolls out his updated official one
Will it rain next year on the same day?
You may be missing the point of this module.
Very low level firmware... Looks like broken droidguard implementation to me, but OEM is responsible to implement keymaster functions...
Brutal commit log... If it is real it looks fake/spam as hell. I wouldn't trust giving that thing zygote access on my device...
Interesting fork of a very experimental fork of @Displax's fork of official USNF!... PWHi, I was having problems passing CTS Profile Match today.
Device: Pixel 7 Feb Update
Tried v2.4.0 and v2.3.1-MOD_2.1 without success.
This last module have worked for me, hope for your devices too!
I've needed to wipe data for Play Store , Wallet/Pay and Play Services at least but twice even that wasn't enough; removing all updates for Play Store , Wallet/Pay and Play Services also, rebooting (very important) and starting fresh fixed it... PW
Nah just judging by the repetitious and nonsensical commit names. It's chaos. I mean look at this page of them: https://github.com/Jukmisael/safety...&branch=myfix&qualified_name=refs/heads/myfix
Maybe I am doing something wrong but I followed this process but I am unable to add cards to gpay/wallet. Any thoughts? I'm on a pixel 6a Feb 2023 update.Moving this here:
Nice interception of that ball!
Yup, the method I previously posted in G Pay Magisk Discussion thread didn't work for me either this time...
Not sure it will clear w/o intervention... Try what I wrote in this thread... May need to clear updates, caches and uninstall G Pay again before rebooting and reinstalling as mentioned in last paragraph re. my recent saga:
Be sure to do the reboot or you may need to go through hoops to get other issues fixed even if G Pay updates to wallet and works again, eg Activity list never populates issue...
Hope it works for you and please report your results...
Should we still use your mod from here https://forum.xda-developers.com/t/...tynet-fix-2-4-0.4217823/page-91#post-87198517
Or the new 2.4.0 update includes your fixes and should be the only option from now on?
That is correct if you you have the Magisk DenyList Enforcing.
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.