So as the title says safety net breaks just by unlocking the bootloader and doing nothing else, no twrp no magisk and even if i flash magisk it doesnt fix it even with magiskprops module.
I flashed stock rom 10.3.1 with msmtool and booted the phone and everything was fine until i unlocked the bootloader and rebooted. I lost all oneplus wallpapers and even then play store says device not verified and netflix shows as unsupported app.
Even with 10.3.4 the issue is same and cant be fixed with magisk. Previously i was using 10.3.2 with unlocked bootloder and magisk and safety net was fine so how it is now not working with factory rom i flashed with msmtool
https://forum.xda-developers.com/on...etynet-magisk-edxposed-tests-failing-t4077527
Manu11 said:
So as the title says safety net breaks just by unlocking the bootloader and doing nothing else, no twrp no magisk and even if i flash magisk it doesnt fix it even with magiskprops module.
I flashed stock rom 10.3.1 with msmtool and booted the phone and everything was fine until i unlocked the bootloader and rebooted. I lost all oneplus wallpapers and even then play store says device not verified and netflix shows as unsupported app.
Even with 10.3.4 the issue is same and cant be fixed with magisk. Previously i was using 10.3.2 with unlocked bootloder and magisk and safety net was fine so how it is now not working with factory rom i flashed with msmtool
Click to expand...
Click to collapse
Don't think so. I'm on a rooted 10.3.4 and I don't see such issues with playstore or safetynet.
hallo dare said:
https://forum.xda-developers.com/on...etynet-magisk-edxposed-tests-failing-t4077527
Click to expand...
Click to collapse
safetynet fails even without the magisk, so i dont think its a magisk problem
Manu11 said:
safetynet fails even without the magisk, so i dont think its a magisk problem
Click to expand...
Click to collapse
What'd u do ?
jaggillararla said:
What'd u do ?
Click to expand...
Click to collapse
There's nothing you can do about safetynet. The moment you unlock the bootloader, you have tripped the safetynet. Why do you need safetynet btw unless you are using bank apps or secure stuff, safetynet really doesn't help much
amirage said:
There's nothing you can do about safetynet. The moment you unlock the bootloader, you have tripped the safetynet. Why do you need safetynet btw unless you are using bank apps or secure stuff, safetynet really doesn't help much
Click to expand...
Click to collapse
Bro as i told already in my post i was yesterday using unlocked bootloader + magisk+ twrp with passing safety net. The problem started when i clean flashed stock rom with msmtool and unlocked bootloader.
ANYWAYS GUYS AFTER SO MANY USELESS ATTEMPS I SOLVED IT..
Older version of magisk worked and safety net passes, i dont know how new version failed me :/ Device is certified again
That's why I don't update anything if not have to
Config below
Sent from OnePlus 7 Pro, OxygenOS 10.0.3, TWRP 3.3.1-75, Magisk 20.4, TaiChi Xposed 6.1.8, Modded Play Store 16.5.15, android core.java patched and SafetyNet pass OK
Install magisk
Go to magisk settings
Enable magisk hide(if you're getting problems with banking apps or games that detect root just hide magisk manager too)
Enable it for google play services and enjoy!
Playstore uncertified status appeared to me when I flash stock rom through TWRP but it solves flashing new firmware via OTA
Sent from my OnePlus7Pro using XDA Labs
The reason an older version of Magisk worked is because newer versions of Magisk turn MagiskHide off by default, which is needed to pass SafetyNet.
Also, SafetyNet is not an e-fuse like Knox is. You don't "trip" it, you can only fail it when it checks your device.
Related
My device is failing and as a result I am unable to setup Android Pay. Is anyone else seeing this on their phone?
Same issue
I'm rooted with Magisk and I pass.... so that's very odd
Just got an OTA that fixed it.
tw1tch175 said:
Just got an OTA that fixed it.
Click to expand...
Click to collapse
Sprint or unlocked U11 ?
I guess unlocked to get an OTA this fast...
Howling Wolf said:
Sprint or unlocked U11 ?
I guess unlocked to get an OTA this fast...
Click to expand...
Click to collapse
Yeah, unlocked. It seemed like a day zero ota that rolled out a bit late, it didn't update my monthly security but after it I had an update to my headphone dac and Assistant app.
heslo.rb26 said:
I'm rooted with Magisk and I pass.... so that's very odd
Click to expand...
Click to collapse
How did you do it? I flashed TWRP and Magisk, and then flashed the stock recovery, and I am failing safety net...
HTCdev to unlock bootloader
Flash TWRP
Flash Magisk
Boom, pass SafetyNet no worries
EDIT: Just read Google has passed an update to SafetyNet and it no longer passes with Magisk V12. Apparently V13 fixes this, will flash soon and report back
heslo.rb26 said:
HTCdev to unlock bootloader
Flash TWRP
Flash Magisk
Boom, pass SafetyNet no worries
EDIT: Just read Google has passed an update to SafetyNet and it no longer passes with Magisk V12. Apparently V13 fixes this, will flash soon and report back
Click to expand...
Click to collapse
Let us know
ticklemepinks said:
Let us know
Click to expand...
Click to collapse
Currently not working for me but I didn't flash the stock boot.img before I flashed the new Magisk so that is probably my issue there. Don't really have the time to mess with it currently so it will have to wait. If anyone else manages to get it working, feel free to update us
EDIT: Got off my ass and uninstalled Magisk, flashed the original boot.img and removed the Magisk Manager. Then I restarted the handset and flashed the Magisk v13 beta.... Pass SafetyNet checks no worries!
heslo.rb26 said:
HTCdev to unlock bootloader
Flash TWRP
Flash Magisk
Boom, pass SafetyNet no worries
EDIT: Just read Google has passed an update to SafetyNet and it no longer passes with Magisk V12. Apparently V13 fixes this, will flash soon and report back
Click to expand...
Click to collapse
I figured that out last night too after spending an hour wondering what I did wrong. Enabling Core-only mode on v12 also works, but you get no modules which is kind of pointless. I will try flashing V13.
EDIT:
Just flashed V13, and it still doesn't work.
@heslo.rb26 How did you get it to work?
ryanyz10 said:
I figured that out last night too after spending an hour wondering what I did wrong. Enabling Core-only mode on v12 also works, but you get no modules which is kind of pointless. I will try flashing V13.
EDIT:
Just flashed V13, and it still doesn't work.
@heslo.rb26 How did you get it to work?
Click to expand...
Click to collapse
Uninstalled Magisk
Flashed the stock boot.img
Rebooted and uninstalled Magisk Manager
Back to Recovery and flashed the new Magisk
.....
Profit
heslo.rb26 said:
Uninstalled Magisk
Flashed the stock boot.img
Rebooted and uninstalled Magisk Manager
Back to Recovery and flashed the new Magisk
.....
Profit
Click to expand...
Click to collapse
I think it might have failed because I flashed a module. Don't think you can do that in the current beta and still pass the new safety net.
That could very well be the issue, currently only using Magisk for root, no modules
I had SafetyNet working with v12 but then on the next reboot it failed. I upgraded to Magisk v13 and again it worked for one reboot. Also looks like the OTA is for unlocked models only (not Sprint)... anyone got any others ideas?
I have tried everything to bypass safetynet I even tried flashing stock rom with untouched system image and I still get safetynet fails
does the new update adds verified boot meaning that if the device has an unlocked bootloader it won't bypass safetynet ?
AlMaghraby said:
I have tried everything to bypass safetynet I even tried flashing stock rom with untouched system image and I still get safetynet fails
does the new update adds verified boot meaning that if the device has an unlocked bootloader it won't bypass safetynet ?
Click to expand...
Click to collapse
You need magisk to pass safety net since you unlocked your bootloader
Just flash LeeDroid and be done with it. Easy.
I formated restored untouched system image installed magisk and universal safetynet fix v2beta5 and all good thanks for the info.
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
airdi1 said:
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
Click to expand...
Click to collapse
As I mentioned in the post, I do not have Xposed framework
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
tabletalker7 said:
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
Click to expand...
Click to collapse
I have magisk 16.7
virtyx said:
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
Click to expand...
Click to collapse
How do I do that? Do you have a link to this zip?
quantumcity said:
I have magisk 16.7
Click to expand...
Click to collapse
Google "Magisk uninstaller". Flash that file in TWRP. Then reboot to recovery. Then flash Magisk 16.4
quantumcity said:
How do I do that? Do you have a link to this zip?
Click to expand...
Click to collapse
its in the magisk official thread.
virtyx said:
its in the magisk official thread.
Click to expand...
Click to collapse
Yes
So for me, the safety net check passes in the Magisk app but I am not able to access Google tez which tells me that my device is rooted or custom ROM has been changed. Using Magisk v 16.0
16.4... notice the 4
Just fyi I'm on 5.19 and using Magisk 16.0 and safety net passes just fine. Use Google pay daily and play store shows certified.
I hide everything Google related in magisk hide just to be sure
Eric214 said:
16.4... notice the 4
Click to expand...
Click to collapse
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
I have attached the screenshots below. And I understand that I'm using Magisk 16.0
skr975 said:
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
Click to expand...
Click to collapse
Do you have it hidden in Magisk? Google Pay works here if you hide it.
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
quantumcity said:
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
Click to expand...
Click to collapse
In playstore / settings are you uncertified? After unlocking bootloader I was and couldn't use Google pay. I flashed magisk and it was still uncertified so I cleared playstore app data. Now the phone says certified and Google pay works for me.
I suggest you flash 16.4 magisk and clear app data in playstore to see if you can get them working. Also you will need a different app than magisk manager to check safety net ATM as it will come back with "invalid response"
Sent from my OnePlus6 using XDA Labs
Hey, does TWRP breaks the SafetyNet? Can I install TWRP without getting a SafetyNet error?
simon151102 said:
Hey, does TWRP breaks the SafetyNet? Can I install TWRP without getting a SafetyNet error?
Click to expand...
Click to collapse
TWRP doesn't, but unlocking your Bootloader to get TWRP on your phone does. To hide the unlocked Bootloader state, your Kernel needs to be patched. Most custom Kernels are patched for this reason and hide the Bootloader state.
There are other things that might cause safetynet to fail. Older Root methods like the LOS SU Addon, or selinux being in 'Permissive' mode.
Magisk Hide is usually the cure for most safetynet problems.
Dirk said:
TWRP doesn't, but unlocking your Bootloader to get TWRP on your phone does. To hide the unlocked Bootloader state, your Kernel needs to be patched. Most custom Kernels are patched for this reason and hide the Bootloader state.
There are other things that might cause safetynet to fail. Older Root methods like the LOS SU Addon, or selinux being in 'Permissive' mode.
Magisk Hide is usually the cure for most safetynet problems.
Click to expand...
Click to collapse
So does Unlocking bootloader on my A5 2017 breaks the safetynet?
simon151102 said:
So does Unlocking bootloader on my A5 2017 breaks the safetynet?
Click to expand...
Click to collapse
As @Dirk clearly stated it depends on your kernel.
I have installed a custom rom(los 17.1) on my s6. To pass safetynet I need the fingerprint build and I can't find it. Can someone help me? Also can I get widevine L1 on this phone?
ISmokeAir said:
I have installed a custom rom(los 17.1) on my s6. To pass safetynet I need the fingerprint build and I can't find it. Can someone help me? Also can I get widevine L1 on this phone?
Click to expand...
Click to collapse
Hi, you need Magisk to pass SafetyNet.
See my tutorial from step 5 : https://forum.xda-developers.com/galaxy-s6/general/guide-tutorial-howto-samsung-galaxy-s6-t4108425
In TWRP recovery, only flash Magisk*.zip and don't wipe cache.
Reboot phone.
Install Magisk Manager.
SafetyNet icon is green.
djibe89 said:
Hi, you need Magisk to pass SafetyNet.
See my tutorial from step 5 : https://forum.xda-developers.com/galaxy-s6/general/guide-tutorial-howto-samsung-galaxy-s6-t4108425
In TWRP recovery, only flash Magisk*.zip and don't wipe cache.
Reboot phone.
Install Magisk Manager.
SafetyNet icon is green.
Click to expand...
Click to collapse
But that means that I don't have Google play which is a problem for me.
Did you end up getting a fingerprint?
Look at the magisk module called MagiskHide Props Config to spoof your device fingerprint into the last official Samsung 7.0 one, it did wonders for me
screen said:
Look at the magisk module called MagiskHide Props Config to spoof your device fingerprint into the last official Samsung 7.0 one, it did wonders for me
Click to expand...
Click to collapse
Last time I did that my device was infinitely booting and had to remove the modules from twrp before it would boot again