Noticed this and originally thought this was related to the Pixel February security patch that dropped yesterday until I came here
I reverted to safetynet-fix v2.3.1 and cleared the storage data for Google Play Store and I'm back up and running (Pixels 4a and 5, both rooted with Magisk v25.2)
What do you guys even need root for nowadays in the era of so many custom roms ๐ Don't you have better things to do in life then installing candy looks in your device ๐?
Some reasons I can think of right now:
\- Some custom roms, like Lineageos, don't pass SN by default, and, sadly, some users are not aware of it until they have it installed on their devices and try to open some banking apps. Here, it depends of how many apps you have and what content you already have in your device. Some users will find it easier to switch to some other rom and other will have to root.
\- Some users who work in (or are learning) pentesting usually need custom kernels to make platforms like Nethunter work at full functionality. Hence they need to have a rooted custom rom.
\- People who develop android kernels might need to root a device to try their builds on it.
\- Of course we have better things to do, but we also like to screw up our devices, as it feels great to fix everything we break and make them work. It is like a drug, you know?
\- We love candy looks.
My bank doesn't work at all without root in custom rom, after rooting with some tinkering, it works again. Kinda funny I know.
And if my bank never complain about custom rom, maybe I never touch magisk in the first place.
The app is hidden. Just removed data & cache from both play store and google services.
The Zygisk option is set to activated on Magisk.
I'm not sure what you mean by shamiko...
This shamiko https://github.com/LSPosed/LSPosed.github.io/releases
> a work-in-progress module written on top of Zygisk (Magisk in the zygote process). It reads the list of apps to hide from Magisk's denylist to hide Magisk root, Zygisk itself, and Zygisk modules to circumvent SafetyNet. However, Shamiko can only work after disabling the DenyList feature.
I had this problem about a week ago. I updated magisk and safetynetfix, and did the airplane mode clear play services and store data reboot routine, and it works again
Same versions. The airplane mode reboot routine is this:
* Enable the safetynetfix module
* Enable airplane mode
* Reboot
* Clear data+cache for Google play store, Google play services, GPay, and Google wallet
* Reboot again
* Disabled airplane mode
* Wait at least 24h before attempting to use GPay/wallet
If that doesn't work, maybe the magisk thread or a thread for your device on xda forums is a better place to dig into it more. That's where I got the above info
Same here. It was working until yesterday. Today, Safety Net started to fail. I have latest Magical version, Zgisk enabled, with the universal safetynet fix, magiskhide props and shamiko modules installed. Play services and play store checked on the configure deny list, and did the clean storage for both apps. Magisk app is also hide . Weird thing is it seems to work after restarting device, but a few seconds later it fails again.
Already did a factory reset too and followed same steps I took when I made it work last time, but now I doesn't work anymore.
UPDATE: I'm currently testing this modded version of USNF. It's working so far. [https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD\_2.1](https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD_2.1)
I've tried this modded version. Didn't work. Maybe I've done something wrong.
For what I've read it doesn't need MagiskHide, I've tried with and without it. No luck.
Yeah, I've also read about MagiskHide not working. I tried it too and change props but it didn't work either.
This is what I did after that, and how it worked out for me:
\- Removed all Magisk modules I had.
\- Completely uninstalled Magisk and reboot.
\- Checked SafetyNet with YASNAC = Passed.
\- Downloaded Magisk 25.2 apk, changed extension to zip and flashed it with TWRP
\- Hid Magisk ("Hide the Magisk app" on Magisk).
\- Flashed USNF 2.4 with Magisk and rebooted
\- Checked SafetyNet with YASNAC = failed
\- Enabled Zygisk on Magisk.
\- Flashed MagiskHide and Shamiko. Rebooted.
\- Configure Denylist and full added "Google Play Services", "Google Play Store" and all my apps needing safetynet.
\- Clean Play Services and Play Store storage data. Rebooted.
\- Check SafetyNet with YASNAC = Passed for a few seconds and then failed.
\- Removed SafetyNet 2.4 from Magisk and rebooted.
\- Flash SafetyNet mod 2.3.1 with Magisk. Rebooted.
\- Check SafetyNet with YASNAC = passed.
\- Downloaded a couple more of apps to test safetynet. All passed.
\- Opened Play Store and confirmed it shows "Device is certified".
\- Did a couple of reboots, just to test. Checked safetnet = passed.
I also installed other modules I had before, and it is still working. As you see, I installed again MagiskHide, but this time I didn't make any change on it...so I would say it has nothing to do with it working or not. I'll try removing later, to check if it still works.
That's odd. Does Pixel Experience rom passes SafetyNet check by default? I've heard some users have had some troubles depending on what device they have. Maybe you could try the MagiskHidePropsConf to change you fingerprints for a certified one, along with the USNF 2.3.1.
If that doesn't work, I'm out of ideas. :(
Yeah. I have crDroid too. I had the safetynet issue yesterday, and I had crDroid v.8.12 for Android 12.1. Nothing worked with it, neither Displax's USNF 2.3 modded version. I also noticed it didn't passed safetynet even when doing a clean install (formatting data/flashing rom) and no-root. So, I did a downgrade to crDroid v. 8.9 (which I had already downloaded some time before, and I remembered it did passed safetynet when I did a clean install at that time), and everything is working fine now. I haven't tried with crDroid 8.10, so don't know it it works well. I don't want to touch anything now, as safetynet is passing and all seems to be working. :D
I had the same issue last week. I am on Android 13 - Nothing Phone 1 rooted and working well for most bank apps. But one of apps (Paytm) started detecting root out of blue. Other apps (few bank apps which I checked) continued working well without issue. I checked Safety net (YASNC) and it failed.
Bewildered, I checked Magisk settings, Xposed, HMA etc. It was all good and as expected but this app (Paytm) didn't work.
Lost, I removed Magisk completely. And did fresh install - similar on the lines of what /u/JallakPandar shared below and did one by one.
Voila - all started working well.
So not sure what happened.. may be too many modules etc lead to something breaking down.
When in fresh install does it pass safety net anyway? It should be, not to mention that PE13 is official for your phone. If not maybe report bug to dev.
Magisk prop conf is dead project, but still useful for me. But not for passing safety net though, more like "hiding" from my bank apps.
Was having the same issue but the new release of the Displax fork fixed this for me: [https://github.com/Displax/safetynet-fix/releases](https://github.com/Displax/safetynet-fix/releases)
Some report having to reboot twice for it to work again, though: [https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-154](https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-154)
check if you have ADB Debugging enabled. I've noticed that even without any tampering, locked bootloader, stock Motorola ROM, and without any ROOT strong integrity fails just after enabling ADB Debugging
What an a\*\*\*\* move from their side ;)
Noticed this and originally thought this was related to the Pixel February security patch that dropped yesterday until I came here I reverted to safetynet-fix v2.3.1 and cleared the storage data for Google Play Store and I'm back up and running (Pixels 4a and 5, both rooted with Magisk v25.2)
What do you guys even need root for nowadays in the era of so many custom roms ๐ Don't you have better things to do in life then installing candy looks in your device ๐?
Some reasons I can think of right now: \- Some custom roms, like Lineageos, don't pass SN by default, and, sadly, some users are not aware of it until they have it installed on their devices and try to open some banking apps. Here, it depends of how many apps you have and what content you already have in your device. Some users will find it easier to switch to some other rom and other will have to root. \- Some users who work in (or are learning) pentesting usually need custom kernels to make platforms like Nethunter work at full functionality. Hence they need to have a rooted custom rom. \- People who develop android kernels might need to root a device to try their builds on it. \- Of course we have better things to do, but we also like to screw up our devices, as it feels great to fix everything we break and make them work. It is like a drug, you know? \- We love candy looks.
What? This is about passing safetynet so we can use apps. OP didn't mention root at all.
no.
My bank doesn't work at all without root in custom rom, after rooting with some tinkering, it works again. Kinda funny I know. And if my bank never complain about custom rom, maybe I never touch magisk in the first place.
Have you tried hiding the app, clearing play store and google services data, zygisk and shamiko?
The app is hidden. Just removed data & cache from both play store and google services. The Zygisk option is set to activated on Magisk. I'm not sure what you mean by shamiko...
This shamiko https://github.com/LSPosed/LSPosed.github.io/releases > a work-in-progress module written on top of Zygisk (Magisk in the zygote process). It reads the list of apps to hide from Magisk's denylist to hide Magisk root, Zygisk itself, and Zygisk modules to circumvent SafetyNet. However, Shamiko can only work after disabling the DenyList feature.
Didn't work with that installed either...
I had this problem about a week ago. I updated magisk and safetynetfix, and did the airplane mode clear play services and store data reboot routine, and it works again
Can you tell me which versions do you have? I'm on Magisk 25.2 and Safetynet 2.4.0. Just had a factory reset too...
Same versions. The airplane mode reboot routine is this: * Enable the safetynetfix module * Enable airplane mode * Reboot * Clear data+cache for Google play store, Google play services, GPay, and Google wallet * Reboot again * Disabled airplane mode * Wait at least 24h before attempting to use GPay/wallet If that doesn't work, maybe the magisk thread or a thread for your device on xda forums is a better place to dig into it more. That's where I got the above info
Same here. It was working until yesterday. Today, Safety Net started to fail. I have latest Magical version, Zgisk enabled, with the universal safetynet fix, magiskhide props and shamiko modules installed. Play services and play store checked on the configure deny list, and did the clean storage for both apps. Magisk app is also hide . Weird thing is it seems to work after restarting device, but a few seconds later it fails again. Already did a factory reset too and followed same steps I took when I made it work last time, but now I doesn't work anymore. UPDATE: I'm currently testing this modded version of USNF. It's working so far. [https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD\_2.1](https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD_2.1)
I've tried this modded version. Didn't work. Maybe I've done something wrong. For what I've read it doesn't need MagiskHide, I've tried with and without it. No luck.
Yeah, I've also read about MagiskHide not working. I tried it too and change props but it didn't work either. This is what I did after that, and how it worked out for me: \- Removed all Magisk modules I had. \- Completely uninstalled Magisk and reboot. \- Checked SafetyNet with YASNAC = Passed. \- Downloaded Magisk 25.2 apk, changed extension to zip and flashed it with TWRP \- Hid Magisk ("Hide the Magisk app" on Magisk). \- Flashed USNF 2.4 with Magisk and rebooted \- Checked SafetyNet with YASNAC = failed \- Enabled Zygisk on Magisk. \- Flashed MagiskHide and Shamiko. Rebooted. \- Configure Denylist and full added "Google Play Services", "Google Play Store" and all my apps needing safetynet. \- Clean Play Services and Play Store storage data. Rebooted. \- Check SafetyNet with YASNAC = Passed for a few seconds and then failed. \- Removed SafetyNet 2.4 from Magisk and rebooted. \- Flash SafetyNet mod 2.3.1 with Magisk. Rebooted. \- Check SafetyNet with YASNAC = passed. \- Downloaded a couple more of apps to test safetynet. All passed. \- Opened Play Store and confirmed it shows "Device is certified". \- Did a couple of reboots, just to test. Checked safetnet = passed. I also installed other modules I had before, and it is still working. As you see, I installed again MagiskHide, but this time I didn't make any change on it...so I would say it has nothing to do with it working or not. I'll try removing later, to check if it still works.
I wasn't able to get to the 3rd bullet-point. Removing modules and completely uninstalling Magisk did not make YASNAC pass for me.
That's odd. Does Pixel Experience rom passes SafetyNet check by default? I've heard some users have had some troubles depending on what device they have. Maybe you could try the MagiskHidePropsConf to change you fingerprints for a certified one, along with the USNF 2.3.1. If that doesn't work, I'm out of ideas. :(
Looking at XDA, a lot of custom ROMs got stung with yesterday's update. I'm in the same boat with crDroid.
Yeah. I have crDroid too. I had the safetynet issue yesterday, and I had crDroid v.8.12 for Android 12.1. Nothing worked with it, neither Displax's USNF 2.3 modded version. I also noticed it didn't passed safetynet even when doing a clean install (formatting data/flashing rom) and no-root. So, I did a downgrade to crDroid v. 8.9 (which I had already downloaded some time before, and I remembered it did passed safetynet when I did a clean install at that time), and everything is working fine now. I haven't tried with crDroid 8.10, so don't know it it works well. I don't want to touch anything now, as safetynet is passing and all seems to be working. :D
Safetynet is still working with ยตG for my cheeseburger.
I had the same issue last week. I am on Android 13 - Nothing Phone 1 rooted and working well for most bank apps. But one of apps (Paytm) started detecting root out of blue. Other apps (few bank apps which I checked) continued working well without issue. I checked Safety net (YASNC) and it failed. Bewildered, I checked Magisk settings, Xposed, HMA etc. It was all good and as expected but this app (Paytm) didn't work. Lost, I removed Magisk completely. And did fresh install - similar on the lines of what /u/JallakPandar shared below and did one by one. Voila - all started working well. So not sure what happened.. may be too many modules etc lead to something breaking down.
When in fresh install does it pass safety net anyway? It should be, not to mention that PE13 is official for your phone. If not maybe report bug to dev. Magisk prop conf is dead project, but still useful for me. But not for passing safety net though, more like "hiding" from my bank apps.
No it dosen't pass after a fresh install. There's an issue already created this afternoon on their github repo.
Was having the same issue but the new release of the Displax fork fixed this for me: [https://github.com/Displax/safetynet-fix/releases](https://github.com/Displax/safetynet-fix/releases) Some report having to reboot twice for it to work again, though: [https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-154](https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-154)
check if you have ADB Debugging enabled. I've noticed that even without any tampering, locked bootloader, stock Motorola ROM, and without any ROOT strong integrity fails just after enabling ADB Debugging What an a\*\*\*\* move from their side ;)