MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0

Search This thread
By:
Advanced…
P

pndwal

Senior Member
Jun 23, 2016
5,884
6,494
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
Lagartixo said:
Started problem today and made all procedures including v2.3.1-MOD_2.1 and no solution. CTS profile match fail. (Mi9 with EvoX 13)
Click to expand...
Click to collapse
Of course you also need Play Integrity deviceIntegrity pass since Safetyis deprecated...
JakeDHS07 said:
Yup looks like there's gonna need to be an update 🙄. It's a damn good thing I don't need or use NFC hardly ever and just do this for fun otherwise I'd be very annoyed.
Click to expand...
Click to collapse
This:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88103103

🙃 😬 PW
 
P

pndwal

Senior Member
Jun 23, 2016
5,884
6,494
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
jknaggs said:
CTS profile match fail here also on P7pro Feb security update. Running latest USNF 2.4.

Device still certified in play store and all banking apps working.
Click to expand...
Click to collapse
Bank app are usually fine since they don't monitor environment for security compliance / device integrity full time...

Google does that for Pay/Wallet, so even if PI API's deviceIntegrity fails at boot-time only or momentarily later while Pay/Wallet is not in use, security requirements will fail for contactless payments on next use. Nb. This applies to removing and replacing screen lock pattern/password also...

👀 PW
 
D

ddrum2000

Senior Member
Feb 17, 2009
184
9
Google Nexus 10
LG Nexus 5X
pndwal said:
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
Click to expand...
Click to collapse
I did all of that. Do you mind being a little more specific about the order? Also if CTS failing, this doesn't really matter at this point does it?
 
P

pndwal

Senior Member
Jun 23, 2016
5,884
6,494
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
ddrum2000 said:
I did all of that. Do you mind being a little more specific about the order? Also if CTS failing, this doesn't really matter at this point does it?
Click to expand...
Click to collapse
Can you be specific about why you are
ddrum2000 said:
... unable to add cards to gpay/wallet...
Click to expand...
Click to collapse
... Do you have
IMG_20230206_055816.jpg

screen that doesn't ever complete, or other?

👍 PW
 
D

ddrum2000

Senior Member
Feb 17, 2009
184
9
Google Nexus 10
LG Nexus 5X
benjaminrm said:
Hi, 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!
github.com

Releases · Jukmisael/safetynet-fix-jukmisael

Google SafetyNet attestation workarounds for Magisk - Jukmisael/safetynet-fix-jukmisael
github.com github.com
Click to expand...
Click to collapse
This did not work for me. Which apps do you have "enabled" on the denylist. I currently have: Google Play Store, Wallet, GPay, Play Protect Service, and some other non-relevent apps.
 
P

pndwal

Senior Member
Jun 23, 2016
5,884
6,494
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
ddrum2000 said:
I did all of that. Do you mind being a little more specific about the order? Also if CTS failing, this doesn't really matter at this point does it?
Click to expand...
Click to collapse
pndwal said:
Can you be specific about why you are

... Do you have
View attachment 5830511
screen that doesn't ever complete, or other?

👍 PW
Click to expand...
Click to collapse
ddrum2000 said:
No. I'm getting this Google pay error messageView attachment 5830525

And this fail from the security checker
View attachment 5830527
Click to expand...
Click to collapse
Ah... The issue most here have is old (deprecated) S/N ctsProfileMatch and new PI deviceIntegrity failing only sporadically; they generally have these passing...

Yes, you need to fix PI deviceIntegrity first, then clear data etc for G Pay/Wallet, G Play services etc to reset failed security checks... It may just reset itself after some days (even a week), but only if you have PI deviceIntegrity... 😜 PW
 
P

pndwal

Senior Member
Jun 23, 2016
5,884
6,494
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
  • Haha
Reactions: ipdev, osm0sis and Nergal di Cuthah
osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,317
34,672
Halifax
GT-i9250
Google Nexus 4
  • Like
Reactions: Garbonzo17, shoey63, ipdev and 2 others
P

pndwal

Senior Member
Jun 23, 2016
5,884
6,494
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
ddrum2000 said:
This did not work for me. Which apps do you have "enabled" on the denylist. I currently have: Google Play Store, Wallet, GPay, Play Protect Service, and some other non-relevent apps.
Click to expand...
Click to collapse
Did you have this passing previously?... Is ROM stock?...

You don't need Play Store in denylist... Keep Play Protect Service... Other than that, only bank and detection apps + GPay/Wallet are normally added...

Try passing PI deviceIntegrity with all modules disabled other than one of @Displax's USNF Mod builds, denylist enforced and Zygisk = Yes appearing on Magisk App home screen... PW
 
P

pndwal

Senior Member
Jun 23, 2016
5,884
6,494
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
osm0sis said:
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...

github.com

Commits · Jukmisael/safetynet-fix-jukmisael

Google SafetyNet attestation workarounds for Magisk - Commits · Jukmisael/safetynet-fix-jukmisael
github.com github.com
Click to expand...
Click to collapse
Better ping the member:
benjaminrm said:
Hi, 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!
github.com

Releases · Jukmisael/safetynet-fix-jukmisael

Google SafetyNet attestation workarounds for Magisk - Jukmisael/safetynet-fix-jukmisael
github.com github.com
Click to expand...
Click to collapse
😶

... Did you see any especially suspect commits?... Just tooo many since Dec... Seems to be trying to do all kinds of root hiding (Shamiko's job) too...

But security is the big issue for sure... PW
 
osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,317
34,672
Halifax
GT-i9250
Google Nexus 4
Last edited:
  • Like
Reactions: ipdev and pndwal
Bad Bimr

Bad Bimr

Senior Member
Dec 29, 2010
230
37
Been reading for about an hour and could not find a definitive answer.
Have Both Pixel 6A and 7
magisk stable 25.2 (25200)(33)
with modules:
Advanced Charging Controller (ACC) v2022.7.3.30
MagiskHide PropsConfig v6.1.2-v137
SystemlessHosts 1.0
Universal SafteyNet Fix v2.4.0

Lately I have been getting an error (Pixel 7) about root upon opening my wallet but it would still work. Today however it did not work. Running YASNAC - SafetyNet Checker it passes for the first few times but after a while CTS fails. Then later it may pass again. With the Pixel 6A it passes when you reboot but fails a few seconds after.
What is going on? Is there a fix?
Thanks in advance.
BB
 
P

pndwal

Senior Member
Jun 23, 2016
5,884
6,494
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
Bad Bimr said:
Been reading for about an hour and could not find a definitive answer.
Have Both Pixel 6A and 7
magisk stable 25.2 (25200)(33)
with modules:
Advanced Charging Controller (ACC) v2022.7.3.30
MagiskHide PropsConfig v6.1.2-v137
SystemlessHosts 1.0
Universal SafteyNet Fix v2.4.0

Lately I have been getting an error (Pixel 7) about root upon opening my wallet but it would still work. Today however it did not work. Running YASNAC - SafetyNet Checker it passes for the first few times but after a while CTS fails. Then later it may pass again. With the Pixel 6A it passes when you reboot but fails a few seconds after.
What is going on? Is there a fix?
Thanks in advance.
BB
Click to expand...
Click to collapse
There's plenty on it here if you read back...

Basically 2.4.0 failed to maintain deviceIntegrity from the getgo:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88052749

Now we have intermittent failures w/ @Displax modded USNF builds also:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88103103

And note what I posted just above:
pndwal said:
Of course you also need Play Integrity deviceIntegrity pass since Safetyis deprecated...

This:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88103103

🙃 😬 PW
Click to expand...
Click to collapse

👀 PW
 
  • Like
Reactions: Bad Bimr
D

ddrum2000

Senior Member
Feb 17, 2009
184
9
Google Nexus 10
LG Nexus 5X
pndwal said:
Did you have this passing previously?... Is ROM stock?...

You don't need Play Store in denylist... Keep Play Protect Service... Other than that, only bank and detection apps + GPay/Wallet are normally added...

Try passing PI deviceIntegrity with all modules disabled other than one of @Displax's USNF Mod builds, denylist enforced and Zygisk = Yes appearing on Magisk App home screen... PW
Click to expand...
Click to collapse
Ok so what am I missing here. I cleared the storage for gpay, wallet, and play services, then rebooted. Here's what I got...
Screenshot_20230207-233425.png

My enabled modules
Screenshot_20230207-233605.png


Then the denylist...
Screenshot_20230207-233511.png


Then I try to add a card in wallet
Screenshot_20230207-233638.png


What am I missing? Thanks for the help.
 
Fishawy

Fishawy

Senior Member
Mar 26, 2010
3,335
636
Melbourne
OnePlus 9 Pro
Google Pixel 7 Pro
ddrum2000 said:
Ok so what am I missing here. I cleared the storage for gpay, wallet, and play services, then rebooted. Here's what I got..

My enabled modules


Then the denylist...


Then I try to add a card in wallet


What am I missing? Thanks for the help.
Click to expand...
Click to collapse
Not sure about the USNF module you're using, as I'm using Displax's fork.

I can't see Google Play Services in your DenyList. I would say this needs to be added, then clear storage for all, reboot and test.
 
You must log in or register to reply here.

Similar threads

Chainfire
[Android 2.1+][03.10.2011][v3.2] Chainfire3D [ROOT][OpenGL ES 2.0+]
Replies
3K
Views
3M
rignfool
rignfool
apb_axel
[ZIP] Synapse + Script => Universal Kernel Manager v3.8.1
Replies
3K
Views
766K
D
Dildoman
repey6
[6.0-12.0][Magisk]Dolby Digital Plus[upd.20211005]
Replies
2K
Views
737K
B
b4minee
Chainfire
[2014.05.01][ROOT] Mobile ODIN v4.20
Replies
5K
Views
3M
Zagnutty
Zagnutty
DooMLoRD
[04/Jan][ROOTING/UNROOTING] DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit)
Replies
927
Views
3M
B
bishoy ashraf

Top Liked Posts

24 Hours 30 Days All time
  • 1
    simplepinoi177
    simplepinoi177
    anatoly1983 said:
    Device: Realme GT2 pro (RMX 3301)
    Android 13 (Realme UI 4.0 version - c13)
    Click to expand...
    Click to collapse
    From your screenshots, it doesn't look like all the selections in the sub-selection/drop-down are ticked...you need every single one of them to be ticked...
    But you really need to pass everything other than "STRONG_INTEGRITY" if you want any hope of getting Wallet or other (especially Google based) apps to work while rooted...
    Also, you should really recheck if Displax's USNF-MOD 1.2 is properly installed and working as, usually, the mod in itself is usually enough...
    Also you can do (or re-do, as it were) what I stated below; it seemed to work for sas46...
    simplepinoi177 said:
    you might want to check out Post #3223, for Pixel 6 & Pixel 7 particularly, that mod works out real well...
    And of course the obligatory clear cache & data of Google Play Protect, Google Framework, Google Play Services, Wallet, Gpay, all these apps' ticks in their respective sub-menu is ticked in MagiskHide, and be sure to restart (personal experience; I did all that and couldn't add card, but after restart I could). Also, I passed safetynet and successfully added card, but had to call the banks on two cards to get it working without error at a store...
    Click to expand...
    Click to collapse

    sas46 said:
    It works as you first described

    Magisk Hide+SafetyNetFix Mod, no zygisk or shamiko, no enforce deny list

    Denied wallet+play services+framework+protect, deleted all datas and reboot

    Wallet works and no root detected, thanks!!
    Click to expand...
    Click to collapse
    View
  • 4
    P
    pndwal
    For those using Canary builds

    Please be aware that in 25207+ major refactoring (of selinux rule patching) has broken many modules etc... This is likely the cause of issues with hiding using recent builds as Shamiko is affected... Please see discussion in Magisk Discussion thread...

    You could revert to 25206 or wait for fixes hopefully in 25211... 👀 PW
    View
    3
    jasonbiggs
    jasonbiggs
    zgfg said:
    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
    Click to expand...
    Click to collapse
    Yes! I was trying to find the link for that mod. This worked. Thanks!

    View
    3
    P
    pndwal
    nate911 said:
    Yes. Device and basic passes.

    I use the phone for 2 hrs

    I run the checker again and device and basic integrity fails.

    Reboot. It then starts passing again

    Edit: restarting gms fixes it too.

    Thanks @pndwal
    Click to expand...
    Click to collapse
    Ok, so NOT intermittently passing only basicIntegrity verdict...

    Sounds like the same issues w/ official 2.4.0... Are you sure you actually have v2.4.0-MOD_1.2 @Displax build?

    If so, please say device/ROM... Also, suggest reverting to v2.3.1-MOD_3.0... There may possibly still be issues with 2.4.0 builds... Please report your mileage with that if you do... PW
    View
    3
    zgfg
    zgfg
    jasonbiggs said:
    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?

    Thanks!
    Click to expand...
    Click to collapse
    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
    View
    3
    osm0sis
    osm0sis
    I was on 2.3.1_MOD_3.0 on Android 12 and now 2.4.0_MOD_1.2 on Android 13 and all was now well in both setups.
    View
  • 314
    kdrag0n
    kdrag0n
    Universal SafetyNet Fix
    Magisk module​

    Magisk module to work around Google's SafetyNet attestation.

    This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS profile attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.

    If you still have trouble passing SafetyNet with this module, use MagiskHide Props Config to spoof a certified device profile. This is a common issue on old devices, custom ROMs, and stock ROMs without GMS certification (e.g. Chinese ROMs).

    Android versions up to 13 Beta 3 are supported, including OEM skins such as Samsung One UI and MIUI.

    How does it work?
    The way this workaround works is relatively low-level. An in-depth explanation, as well as source code and ROM changes, can be found on GitHub.

    Ideally, this workaround should be incorporated in custom ROMs instead of injecting code with a Magisk module. See the ProtonAOSP website for more information.

    Downloads
    Downloads and changelogs can be found on GitHub. The topmost release is the latest.

    Latest release
    v2.4.0
    Highlights
    • Play Integrity bypass without breaking device checks or causing other issues
    • Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)
    Other changes
    • Updated instructions for newer Android and Magisk versions
    • Better debugging for future development
    This version only supports Zygisk (Magisk 24 and newer).

    It's taken a while to find a way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently, but I wanted to make sure this module doesn't cause any unnecessary breakage. Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary. Enjoy!

    If you found this helpful, please consider supporting development with a recurring donation for rewards such as early access to updates, exclusive behind-the-scenes development news, and priority support.
    Alternatively, you can also buy me a coffee. All support is appreciated ❤️

    Source code
    View
    213
    Displax
    Displax
    So, here is my modification of USNF with Play Integrity API bypass.

    It changes fingerprint to old 7.1.2 6.0 (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.

    Updated 3.0:
    No words needed, you understand everything yourself 😜

    Updated 2.1:
    Hide "Enable OEM Unlock" setting

    Updated 2.0:
    Bypassing DEVICE_INTEGRITY for devices that shipped with Android 13+ (Pixel`s 7 )

    Updated:
    Drop fingerprint to lowest possible (6.0) to ensure that no one use same Android version

    Usage:
    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
    View
    58
    Displax
    Displax
    So, here is my new modification of USNF with Play Integrity API bypass.

    It is now based on top of original v2.4.0 codebase instead of v2.3.1, with adding new hiding algorithm for current realities and some code refreshing.

    Changelog:

    Version 1.2
    * Fix crash and endless tests loop/failing on Android < 9.0 (bug from original version 2.4.0).
    * Do not unpatch (revert) changes. To prevent possible tests failing after a while on some ROMs (cross conflicts).

    Version 1.1
    * Fix KeyStore hook desynchronization (tests randomly failing problem).


    Usage:
    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.

    Source code: https://github.com/Displax/safetynet-fix/tree/dev
    View
    31
    P
    pndwal
    Folks, the SafetyNet API was depreciated last Month with 'full turndown' slated for June 2024 and the introduction of the new Play Integrity API. It has also become clear that Google apps are simply the first to adopt the long foretold Play Integrity API; all responsible banks are bound to follow suit in short order, and at least before the June 2023 migration deadline.

    This means (assuming fully deployed Hardware Key Attestation doesn't come first 😬) that the need for a 'Universal Play Integrity Fix' has become quite urgent.

    We currently have workarounds involving using older fingerprint props by means of MHPC module (similar to fix needed for uncertified ROMs), but success/mileage varies per device and users of regular bank apps / gamers etc on stock devices will all soon be forced to experiment with MHPC prints also... This is hardly ideal.

    So I've made an issue report/request on USNF GitHub as follows. This information may be insightful to users here also...

    Please let me know here if I have missed anything important, or add any technically relevant details there...

    PLEASE DON'T spam that issue with unimportant details or queries... (The previous issue is already burgeoning w/ OT.) That's what this thread is for... 😛 :

    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.
    https://developer.android.com/training/safetynet/deprecation-timeline

    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

    1. 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
    2. 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.
    I'm guessing that the 'passing' messages based on the old SafetyNet API are likely to realigned soon.

    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.
    Click to expand...
    Click to collapse

    Here's hoping... 🙃 PW
    View
    29
    Displax
    Displax
    So, created separate thread for my mod. Welcome)

    [MODULE] [MOD] Universal SafetyNet Fix

    Universal SafetyNet Fix [MOD] Magisk module...
    forum.xda-developers.com forum.xda-developers.com
    View

New posts