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.
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?
Anyone know why I'm not passing SafetyNet?
Previously, it was on 7.1.2 stock with twrp flashed and rooted. Now on 8.0 stock, no root or twrp but not passing SafetyNet.
SafetyNet also dectects unlocked bootloader.
Have you tried this? https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
This requires root, though.
mngdew said:
SafetyNet also dectects unlocked bootloader.
Have you tried this? https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
This requires root, though.
Click to expand...
Click to collapse
i just tried this kernel (stock, with SafetyNet patch) but no luck, unfortunately. something is still tripping SN.
https://forum.xda-developers.com/pixel-xl/development/kernel-stock-kernel-safetynet-patch-t3588154
poolemit said:
i just tried this kernel (stock, with SafetyNet patch) but no luck, unfortunately. something is still tripping SN.
https://forum.xda-developers.com/pixel-xl/development/kernel-stock-kernel-safetynet-patch-t3588154
Click to expand...
Click to collapse
I tried the method in that thread. Everything works but suhide. Safety net is still being triggered some how.
gabes100 said:
I tried the method in that thread. Everything works but suhide. Safety net is still being triggered some how.
Click to expand...
Click to collapse
You shouldn't have to root to flash the kernel. You just need to have your bootloader unlocked. Then just boot to twrp and install the kernel.
robocuff said:
You shouldn't have to root to flash the kernel. You just need to have your bootloader unlocked. Then just boot to twrp and install the kernel.
Click to expand...
Click to collapse
I have an unlocked bootloader but have not put a custom recovery or rooted... I'm thinking i may try this method.. is there a walk through?
I know i read that modifying the pixel is more tricky than the old days of android and I do not want to mess it up.. Thanks!
poolemit said:
Anyone know why I'm not passing SafetyNet?
Previously, it was on 7.1.2 stock with twrp flashed and rooted. Now on 8.0 stock, no root or twrp but not passing SafetyNet.
Click to expand...
Click to collapse
Take a look at my couple of posts and links on this page. It is because of an old api that topjohnwu has not been able to fix yet due to his move. It is not actually failing, but not responding to the server correctly. There is also a link for a checker that has been updated and works fine. It is discussed a ton on the Magisk page threads.
https://forum.xda-developers.com/pixel/how-to/9-0-released-t3825746/page4
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.
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.
I have installed the magisk into my phone A51
I have patched the 'AP' file with magisk its not working !
I patched only the boot, it makes an error, and it required a data erease, after that start working !
I have clicked into magisk to uninstall the root, and i have locked the bootloader and the data ereased again !
Problem:
But the SECURE FOLDER still making errors! since 2016 i still have this problem with samsung, when flashing the original firmware it still reading the device as rooted before!
I want the phone to be back as it is, like original, whats the solution please!
you have been warned.
BK☑️ said:
ROOTYour KNOX status will be tripped if you follow this tutorial...What's knox ? : https://www.google.com/search?q=samsung+knox+explained
Click to expand...
Click to collapse