Related
Hello, I've been trying to pass the safetynet check for way too many hours now and I've got no clue how to do it.
I've tried Magisk 16.0 with universal fix, with Props Config (with changed configs), tried on a completely new LineageOS ROM install. I've also tried Magisk 16.4, but to no luck.
Both CTS profile match and Basic integrity are false.
Any more tips?
Use magisk.It will work.If it is on tez app, you can pass safetynet by disabling telephone acess on permission of google paly services.
What is SafetyNet?
"SafetyNet provides a set of services and APIs that help protect your app against security threats, including device tampering, bad URLs, potentially harmful apps, and fake users." -Android Developers
Like stated above, SafetyNet is a set of APIs embedded in Google Play Services to see whether a device has been tampered with from its factory state (e.g. a custom ROM is installed). Developers can use this API to block smartphones in which SafetyNet fails to pass.
How will this affect me and my usage of the device?
Several apps use this API to block users with custom ROMs, such as Google Pay, Netflix, and others, especially banking apps. If you don't use any of these, then failing SafetyNet probably won't matter to you. But if you do use some of these apps, you'll find that they often refuse to run.
How to pass SafetyNet:
You will need Magisk and Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You will need this ZIP:
https://forum.xda-developers.com/apps/magisk/universal-safetynet-fix-magisk-17-t3840680
After you have downloaded both of these, go ahead and flash Magisk through TWRP. After installation is complete, Go to the Modules section in Magisk Manager and press the + button and select the SafetyNet spoofer ZIP. After it's done, reboot your phone. Then go to Settings in Magisk Manager and turn Magisk Hide off and then on again. Go to the Magisk Hide section and select the following apps to hide Magisk from:
Google
Google Services Framework
Google Play Store
(and other apps requiring SafetyNet to pass)
Then go to Play Store>Settings and see if it says your Device is certified. If not, clear Play Store data and try again.
Done! Now you will have passed SafetyNet!
JarlPenguin said:
What is SafetyNet?
"SafetyNet provides a set of services and APIs that help protect your app against security threats, including device tampering, bad URLs, potentially harmful apps, and fake users." -Android Developers
Like stated above, SafetyNet is a set of APIs embedded in Google Play Services to see whether a device has been tampered with from its factory state (e.g. a custom ROM is installed). Developers can use this API to block smartphones in which SafetyNet fails to pass.
How will this affect me and my usage of the device?
Several apps use this API to block users with custom ROMs, such as Google Pay, Netflix, and others, especially banking apps. If you don't use any of these, then failing SafetyNet probably won't matter to you. But if you do use some of these apps, you'll find that they often refuse to run.
How to pass SafetyNet:
You will need Magisk and Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You will need this ZIP:
https://forum.xda-developers.com/apps/magisk/universal-safetynet-fix-magisk-17-t3840680
After you have downloaded both of these, go ahead and flash Magisk through TWRP. After installation is complete, Go to the Modules section in Magisk Manager and press the + button and select the SafetyNet spoofer ZIP. After it's done, reboot your phone. Then go to Settings in Magisk Manager and turn Magisk Hide off and then on again. Go to the Magisk Hide section and select the following apps to hide Magisk from:
Google
Google Services Framework
Google Play Store
(and other apps requiring SafetyNet to pass)
Then go to Play Store>Settings and see if it says your Device is certified. If not, clear Play Store data and try again.
Done! Now you will have passed SafetyNet!
Click to expand...
Click to collapse
I am on Lineage 15.1 based on 8.1, I followed every step you have mentioned but it shows ctsProfile : False and basicintegrity : true
Hello. I have unlocked bootloader with TWRP installed with default Stock Kernel. Also I have Magisk 20.4 with Edxposed installed and I can't pass the Safety Net. Until before 2-3 months the problem was due to Edxposed. If I deactivate the Riru core from Magisk then I passed the Safety Net. Now something very strange happens and the Edxposed is not only the Suspicious. If I disable it then again I Failed the Safety Net. I tried in safe mode in which disables Magisk, Edxposed and all extra apps (it leaves only the Play Store and some default apps like Duo if I remember well) etc ... and I can't pass the Safety Net again. I tried to Reflash the rom via TWRP so that to have the default boot.img and default boot recovery but again can't pass the Safety Net. How can detect what is which makes the Safety Net to be failed ?
Note 1 : I know that if I make format so that to erase not only the system partition but and data with internal partition and flash the rom from beginning then I would pass the Safety Net as new user but all this process is NOT solution because I should install all the apps with settings and transfer all personal data from the beginning.
Also the sense is to understand for which reason something happens and NOT to make format to resolve all the problems because you will never become better and the unique solution would be the format which is some process, time consuming.
Note 2: The Valid Pass in Safety Net is NOT always from Magisk but from some other third party software like Root Checker which can do the same job. The reason is that the most usual to check Safety Net is from Magisk which make someone to make Magisk to Pass Safety Net but ONLY VISUAL. What I mean ? If you install the HiddenCore Module from Edxposed then the Magisk show that you Pass the Safety Net while any other similar software like Root Checker shows as result failed and if you go to search Netflix or Revolut in Google Play which is some quick way to check if you really pass or fail the Safety Net then you can't find them as result due to failing in Safety Net.
Johnn78 said:
Note 1: I know that if I make format so that to erase not only the system partition but and data with internal partition and flash the rom from beginning then I would pass the Safety Net as new user but all this process is NOT solution because I should install all the apps with settings and transfer all personal data from the beginning.
Click to expand...
Click to collapse
I don't have the solution for your issue specifically, but I have a tip for you in case you would need to reinstall the whole system in the end: you can use titanium backup, or oendbackup (this one you find at f-droid), or another root backup solution (either free, or paid like swift backup) to save your apps + data, so you can recover it later without having to go through the whole annoying process of doing/installing/configuring everything again. Making it a lot easier.
abacate123 said:
I don't have the solution for your issue specifically, but I have a tip for you in case you would need to reinstall the whole system in the end: you can use titanium backup, or oendbackup (this one you find at f-droid), or another root backup solution (either free, or paid like swift backup) to save your apps + data, so you can recover it later without having to go through the whole annoying process of doing/installing/configuring everything again. Making it a lot easier.
Click to expand...
Click to collapse
If I have the app which makes the perfect restore then I wouldn't have problem to make format so that to make restoring later. In past I had tried the twrp which has option for backup but the restore in system and data partition is not good. I couldn't restore the apps such it was when I had made the backup. C an the titanium or oandbackup restore the apps such it was when Imake the backup ?
If you boot into Android Safe Mode, Magisk and modules are still active (unless you use the current Canary, 20411+, in which case Magisk will disable all modules). It's just the Manager and other apps that are disabled.
First thing you should check is if MagiskHide is even enabled, and if it is you should toggle it off and on again.
Second thing is to see if it works. Add a root app or an app like Rootbeer to the Hide list and see if it detects root.
And more: https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Didgeridoohan said:
If you boot into Android Safe Mode, Magisk and modules are still active (unless you use the current Canary, 20411+, in which case Magisk will disable all modules). It's just the Manager and other apps that are disabled.
First thing you should check is if MagiskHide is even enabled, and if it is you should toggle it off and on again.
Second thing is to see if it works. Add a root app or an app like Rootbeer to the Hide list and see if it detects root.
And more: https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Click to expand...
Click to collapse
I don't know if finally happens something with hide of Magisk. I had until now the Root Checker to check about rooting and SafetyNet. If I run Root Checker then it tells me that I am rooted (and failed SafetyNet) and if I hide It then it refers that I am unrooted such the first image shows. But question is, is that correct or happens such with Magisk that may refers that you pass the Safety Net while is reality is NOT truth ? I say this, because I run the Root beer which you told me but if I hide it or not then in both situations, it refers that I am rooted (image 2 & 3). The hide isn't seem to not doing anything because If I don't hide Root beer then such you can see I have 6 "X" while if I hide it then I have only one in "Root Management Apps". Whats means this result ? I tried to turn off and on again from the settings of Magisk the hide but not any result.
That likely means that MagiskHide is working but that you haven't repackaged the Magisk Manager with a random package name. There's an option for that in the Manager settings.
That also means that the SafetyNet failure is because of your setup. Something is triggering it and you're going to have to figure out what. Use the information in the link I posted earlier to help you on your way.
Didgeridoohan said:
That likely means that MagiskHide is working but that you haven't repackaged the Magisk Manager with a random package name. There's an option for that in the Manager settings.
That also means that the SafetyNet failure is because of your setup. Something is triggering it and you're going to have to figure out what. Use the information in the link I posted earlier to help you on your way.
Click to expand...
Click to collapse
Now I saw this setting in settings about repacking with random name. Is this new setting in Magisk ? Because I don't remember to have seen it again in previous Magisk versions. If I go to repackage it, it has as default name "Manager". Should I leave this name or to change this to someother random name ?
Johnn78 said:
Now I saw this setting in settings about repacking with random name. Is this new setting in Magisk ? Because I don't remember to have seen it again in previous Magisk versions. If I go to repackage it, it has as default name "Manager". Should I leave this name or to change this to someother random name ?
Click to expand...
Click to collapse
It's not a new feature... I had to go back and check, but John showcased the first version of hiding the Manager in August 2017 and it was then included in the release of Magisk v14.0 in September 2017. The hiding mechanism has improved a lot since then, but the concept has been around for a while.
Some root detection methods actually do look for "Manager" in the app label (stupid way of detecting root, but hey), so renaming it to something else could be a good idea. It won't hurt, that's for sure.
Didgeridoohan said:
It's not a new feature... I had to go back and check, but John showcased the first version of hiding the Manager in August 2017 and it was then included in the release of Magisk v14.0 in September 2017. The hiding mechanism has improved a lot since then, but the concept has been around for a while.
Some root detection methods actually do look for "Manager" in the app label (stupid way of detecting root, but hey), so renaming it to something else could be a good idea. It won't hurt, that's for sure.
Click to expand...
Click to collapse
I repacked it with different name and the rootbeer appears as result not rooted but the safety net remained sa failed. After I unistalled completly the EdXposed with its modules, LuckyPatcher & Magisk. Also I run and the Magisk Unistaller via twrp and the Edxposed unistaller (this failed because it couldn't detect the edxposed as install due to unistallation of edxposed before) and safety Net remained as Failed. I tried and in safe Mode but the problem persists. Overmore I restore the original boot.img so that to unistall the twrp and go back to original recovery but the Failing in safety Net remains either I go from normal boot either from safe mode. The only which I haven't tried is to lock again the bootloader but I don't believe that this is the problem because in past I always have it unlocked and had passed the Safety Net. I have read that the snet is the process of play store service which decides if mobile will pass the safetynet or not. Can't we unistall this service ?
& something else if you know it, the result of safety Net is "decided" only one time in every boot ? Because If it is some process which make the safety net to be failed and I kill the process then will I get immediate the pass in safety Net or I should restart the mobile as result the process will come again because it will be located in boot list ?
SafetyNet doesn't check for the Manager. That was just for you to fully hide Magisk from other detection methods.
If you uninstall Magisk you can't pass SafetyNet with an unlocked bootloader (unless you are using a custom kernel that masks the bootloader state). MagiskHide helps hiding the unlocked bootloader, so uninstalling it will trigger SN.
If you want to figure things out you have to leave Magisk installed with MagiskHide active (or lock the bootloader, but that's likely not advisable since it can brick your device unless you first restore it to completely stock).
Edit: you can of course go without Google services, but if you are using the stock OEM ROM this could prove troublesome and not worth the effort. If you do, you can of course not use any apps or services that depend on SafetyNet. What is your reason for wanting to pass SafetyNet anyway? Do you actually need it?
Didgeridoohan said:
SafetyNet doesn't check for the Manager. That was just for you to fully hide Magisk from other detection methods.
If you uninstall Magisk you can't pass SafetyNet with an unlocked bootloader (unless you are using a custom kernel that masks the bootloader state). MagiskHide helps hiding the unlocked bootloader, so uninstalling it will trigger SN.
If you want to figure things out you have to leave Magisk installed with MagiskHide active (or lock the bootloader, but that's likely not advisable since it can brick your device unless you first restore it to completely stock).
Edit: you can of course go without Google services, but if you are using the stock OEM ROM this could prove troublesome and not worth the effort. If you do, you can of course not use any apps or services that depend on SafetyNet. What is your reason for wanting to pass SafetyNet anyway? Do you actually need it?
Click to expand...
Click to collapse
Now with default boot, I will go to install Magisk so that via hiding to hide the the unlcking of bootloader. Do you consider some Magisk version as best ? Stable or canary or something else ?
Lately I want to istall the Revolut & the Google Play store can't find it as result. After from many days I couldn't find etflix. Later I learnt that was due to failing in safety net. I found them as apk & installed them successfully but can't get updates from play store for these two apps because mark my device as failed in safety Net. Also if I go to update the os via fota (and with stock boot img) I got error & I suppose that is due to safety Net. In past I could update os only if I have boot stock img & passing the safety Net.
@Didgeridoohan hello bro. I resolved the problem. I cleared the data and cache of Google Play Store, Google Play Services and Google Framework Services and after from restarting I passed the Safety Net with Edxposed installed and activated. Thanks for your help !
This is a weird one.
To start, my phone has latest magisk, and passed safety net.
I once again am trying out edxposed (seeing if the game I'm playing still detects, and yes it does).
So, I managed to install edxposed (with hiddencore), magisk working and passing safetynet (check screenshot), however, as mentioned, game still detects something and refuses to start (another note is that the game starts without issues with just magisk and safetynet passed).
Because game doesn't work, I uninstalled hiddencore, edxposed, and riru core (in that order) and somehow magisk cannot pass safetynet anymore.
I've tried everything over again plus countless restarts to get a screenshot of my phone with edxposed and safetynet passed.
-edit-
clearing playstore data did the trick
Hi,
Did u fix your problem ?
Thanks!
Just to be clear, you have only Magisk and Edxposed WITHOUT HiddenCore module installed, and you're passing SN and your game runs fine without detecting root?
I'm a little confused about the order of events and the steps you took, because it reads like you installed edxposed and HiddenCore at the same time (HiddenCore will merely mask SN success test in magisk, it doesn't actually fix the issue as other tester apps more accurately fail to pass SN with edxposed installed. Then you describe you uninstalled all of riru/edxposed framework and hiddencore and then a screen shot of edxposed with Magisk SN test passing??? Okay so, did you reinstall hiddencore? Did you run the test after several reboots to confirm reliability? The game you mentioned, did that quit detecting edxposed? What did you do here exactly?
1. don't consider Magisk's SafetyNet as trustable. Test with other apps like org.freeandroidtools.safetynettest (SafetyNet Test 1.2.1). Or open google play and search for Netflix, and see in Setting at the bottom should say Device is/not certified. Before that clear the Google Play Store Cache и Data Storage because it will remember the previous state and will show an old state.
2. Dont need to uninstall the whole EdXposed and frameworks. Just go in Magisk and turn off the Riru Core framework. Restart. And the SafetyNet should work again. But then GravityBox (and other apps using edXposed) will stop working
3. Yes, recently it stop working for me too, coz Google did next dirty thing. Before I was passing SafetyNet. I had Riru Core 21.3 + EdXposed YAHFA v0.5.0.6 Canary + EdXposedManager v4.5.7 + GravityBox
4. I solve the problem, now I pass SafetyNet again, my GravityBox is working, Google Play show device is certified, all good, so I am happy again. What I did is:
5. Restored my old backup. If I have installed EdXposed-SandHook-v0.5.0.6 Canary I am not able to uninstall it preperly and restore the phone, so whatever I do after it always break SafetyNet. Somehow SandHook mess the phone in irreversible way so the only way out is to flash old backup. That's why I was using EdXposed YAHFA v0.5.0.6 Canary which dont mess the phone and after uninstall phone can pass SafetyNet. So maybe is was not necessary to restore the old backup...
I use LG V20 with LineageOS 17.1 Android 10
6. installed the taichi-v6.2.2.zip framework in Magisk.
https://magiskroot.net/download-xposed-for-android-10/
https://magiskroot.net/taichi-magisk-module/
https://github.com/taichi-framework/TaiChi/releases
https://virtualxposed.com/tai-chi/
https://taichi.cool/download.html
https://github.com/taichi-framework/TaiChi/issues/1153
installed TaiChi 6.4.0.apk
in Modules I enable GravityBox only. Do NOT enable HiddenCore Module because it is detected and if I enable it fail the SafetyNet
in /system/etc/hosts I put this to block connections:
127.0.0.1 techavenue.net
127.0.0.1 www.techavenue.net
127.0.0.1 chinatelecom.com.cn
127.0.0.1 www.chinatelecom.com.cn
127.0.0.1 alibaba.com
127.0.0.1 www.alibaba.com
Click to expand...
Click to collapse
I dont advice you using TaiChi blindly. I just share what I did to have GravityBox with SafetyNet working. You can Thanks me if you find my tips helpful.... But choosing TaiChi is your decision, you can take a look some controversial topic about TaiChi here https://forum.xda-developers.com/xposed/warning-taichi-t4012681
Hello,
I've rooted my p7, how am i supposed to pass safety net?
I've used pixelflasher to root, install magisk and update.
In magisk, I've tried many times to set the "Google Play service" in the exclusion list, it always get uncheck.
I've installed the safety net fix in magisk.
Be sure to check play service, wallet... And empty their cache, all that in airplane mode and reboot.
But still... Play service become uncheck on exclude list and Google Play direct certified my device... Bank apps didn't work ...
What is different with the p7 than the p5?
My p5 is easy to do all that, i can flash the modified boot from magisk easily, which can't be done in cmd with the p7, only pixelflasher have been able to
Hide Magisk, use Zygisk denylist and Displax's universal safetynet fix.
https://forum.xda-developers.com/t/...nlock-bootloader-pass-safetynet-more.4505353/
1. Install displax's safetynetfix
2. Hide Magisk
3. Enable Zygisk
4. Enforce DenyList
5. Configure DenyList and check all your required apps (clear storage for apps already installed)
6. Install AirFrozen
7. Freeze Magisk in AirFrozen and now your banking apps should work fine
dewri21 said:
1. Install displax's safetynetfix
2. Hide Magisk
3. Enable Zygisk
4. Enforce DenyList
5. Configure DenyList and check all your required apps (clear storage for apps already installed)
6. Install AirFrozen
7. Freeze Magisk in AirFrozen and now your banking apps should work fine
Click to expand...
Click to collapse
I did like this but didn't use AirFrozen. I hid Magisk from within Magisk and my banking apps work fine and I'm device certified. Also, when using DenyList I expanded all the Google Play apps and made sure all the subcomponents were selected rather than just the one's picked by default. Accepted my choices with the arrow at the top of the screen rather than the nav button which seemed sometimes to not save my choices. YMMV.
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
v2.3.1-mod_2.0 is required. Older version won't pass device integrity.
Hid magisk, enabled zygisk and denylist, but didn't need to deny any google apps. No shamiko either.
Use https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck to confirm you pass both device and basic integrity.
Still have L1 too
ktdt00 said:
I did like this but didn't use AirFrozen. I hid Magisk from within Magisk and my banking apps work fine and I'm device certified. Also, when using DenyList I expanded all the Google Play apps and made sure all the subcomponents were selected rather than just the one's picked by default. Accepted my choices with the arrow at the top of the screen rather than the nav button which seemed sometimes to not save my choices. YMMV.
Click to expand...
Click to collapse
I had to use AirFrozen for two of my banking apps. Rest were fine. So in case any banking app doesn't work, you know what to do.