This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders or custom verified boot keys. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021.
Instructions:
1. Make sure Magisk hide is enabled.
2. Download the universal safety net fix from kdrag0n's github repository right here.
3. Install it from Magisk manager.
4. Test if it works, if not then download this version of the module instead.
5. If it works congratulations your device now passes safetynet responses.
Credits
@kdrag0n
Worked for me, thanks!
This version of the safetynet fix only works for Magisk v24+(Zygisk).
If you are on version 23.0 of Magisk this should work. But it requires Riru v24.0.0 or newer installed and Magisk hide enabled.
I've attached my results from a SM-A750FN variant.
Hello, I just can't get the cts profile working. What am I doing wrong? I already installed the fix (GitHub - kdrag0n / safetynet-fix: Universal fix for Google SafetyNet on Android devices with hardware attestation and unlocked bootloaders.) With Magisk
This module should help you. I'm using it. Safety net is passing.
How do I pass Safetynet check? Specifically the cts profile, which always fail for me... I do not have this problem before then just all of a sudden I have it now and because of this I can't use and/or download some of the apps in playstore ... I did not do anything to my phone except for the lcd replacement... I need help
if its unlock bootloader (first boot poco boot image has an icon with unlocked padlock ) then youll lose safety net
samsungics1200 said:
if its unlock bootloader (first boot poco boot image has an icon with unlocked padlock ) then youll lose safety net
Click to expand...
Click to collapse
But can I bypass it like I did before? Like using zygisk? Because zygisk for some reason doesn't work now
Only option is using magisk, with the following plugins
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
And then
GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
After doing both use zygisk to block in magisk and boom pass all checks.
viperinc said:
Only option is using magisk, with the following plugins
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
And then
GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
After doing both use zygisk to block in magisk and boom pass all checks.
Click to expand...
Click to collapse
I already did this... Still no luck unfortunately
Im on crdroid 7.16 btw... Dunno if it helps
Cloud9.xxiii said:
Im on crdroid 7.16 btw... Dunno if it helps
Click to expand...
Click to collapse
You run the script to select the signed props fingerprint?
viperinc said:
You run the script to select the signed props fingerprint?
Click to expand...
Click to collapse
I don't know that... Enlighten me pls?
Cloud9.xxiii said:
I don't know that... Enlighten me pls?
Click to expand...
Click to collapse
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Have a read so you know what's happening.
Select 1, f and then 22 and whatever version closest to the base rom your on. Save and reboot.
viperinc said:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Have a read so you know what's happening.
Select 1, f and then 22 and whatever version closest to the base rom your on. Save and reboot.
Click to expand...
Click to collapse
Ohhhh this... This is my solution before and it works, now it doesn't
CRdroid 7.16 has issue for pass the safetynet (cts profile mismatch), you need to downgrade it to 7.15.
Skyfly19 said:
CRdroid 7.16 has issue for pass the safetynet (cts profile mismatch), you need to downgrade it to 7.15.
Click to expand...
Click to collapse
Possible. A bit late tho I was so pissed yesterday and decided to go back in stock rom. Guess I'll just look for other ROMs to try. Thanks for the response guys
I haven't modded android devices for a while now so I am hoping someone can get me up to speed.
Does unlocking the bootloader trip safetynet? I want to install TWRP and even possibly get Magisk running but I want to pass safetynet and I'm not sure if this is possible.
Thanks.
Hello,
"Does unlocking the bootloader trip safetynet?"
no, only if you use magisk
and if you use magisk with this module:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
and in magisk settings hide all google apps from magisk
then you have safetynet OK
apps like google pay work
Fedon said:
Hello,
"Does unlocking the bootloader trip safetynet?"
no, only if you use magisk
and if you use magisk with this module:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
and in magisk settings hide all google apps from magisk
then you have safetynet OK
apps like google pay work
Click to expand...
Click to collapse
Thank you! But what about OTA updates? Are the steps to retain those while having Magisk installed the same as other phones (or similar)?
You can do OTA, but after OTA (before restart) you need to open magisk and click on root again (option "after OTA"), then restart and... you have still root
Thank you for the help!
A new version of Safety Net fix mod has been uploaded to GitHub today, and it finally works for me! I've tried everything before and gave up months ago.
Maybe not necessary, but I did the following:
- I turned off Zygisk and rebooted.
- Flashed the Safety Net fix in Magisk and rebooted.
- Turned on Zygisk and rebooted again. It did the trick!
Thanks to Displax for the Mod!
Release v2.4.0-MOD_1.3 · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Release v2.4.0-MOD_1.3 · Displax/safetynet-fix
github.com
Does this work with Gpay? I've been using Safetynet fix v2.3.1-MOD_3.0 for awhile now in order for GPay to work.. The earlier releases of v2.4.0 didn't seem to work with GPay.