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.
Related
Hi
I flashed stock image on my device for some reasons and since then no matter which version of Supersu I flash the safetynet is failing.
any suggestions will be very helpful
SafetyNet will always fail if your device is rooted, even with systemless mode.
SuicideFlasher said:
SafetyNet will always fail if your device is rooted, even with systemless mode.
Click to expand...
Click to collapse
anyway to bypass this with another super user tool?
No way aside from unrooting.
[email protected] said:
Hi
I flashed stock image on my device for some reasons and since then no matter which version of Supersu I flash the safetynet is failing.
any suggestions will be very helpful
Click to expand...
Click to collapse
SuperSU will always trip it. Also on a stock image with stock kernel, an unlocked bootloader will also trip it since the latest update
ndarkside93 said:
SuperSU will always trip it. Also on a stock image with stock kernel, an unlocked bootloader will also trip it since the latest update
Click to expand...
Click to collapse
The unlocked bootloader check isn't present on all devices, and doesn't seem to be present on this one. Also, phh's root with Magisk and Magisk Hide currenly passes.
josephcsible said:
The unlocked bootloader check isn't present on all devices, and doesn't seem to be present on this one. Also, phh's root with Magisk and Magisk Hide currenly passes.
Click to expand...
Click to collapse
Yes magisk will pass, but SuperSU will always fail. It's not looking for the packages installed for magisk, but does look for the packages installed by SuperSU. And the latest security patches updated safetynet to do a bootloader check, which can be masked by a custom kernel.
ndarkside93 said:
And the latest security patches updated safetynet to do a bootloader check, which can be masked by a custom kernel.
Click to expand...
Click to collapse
I can pass SafetyNet without a custom kernel (running stock M4B30X).
josephcsible said:
I can pass SafetyNet without a custom kernel (running stock M4B30X).
Click to expand...
Click to collapse
Yes, and stock was last updated to October patch set. It became universal in the November patches
ndarkside93 said:
Yes, and stock was last updated to October patch set. It became universal in the November patches
Click to expand...
Click to collapse
But the Nexus 5 is no longer getting security patches (the October one was the last one), so wouldn't that mean that it will never get that check?
josephcsible said:
But the Nexus 5 is no longer getting security patches (the October one was the last one), so wouldn't that mean that it will never get that check?
Click to expand...
Click to collapse
I suppose that is true.
ndarkside93 said:
I suppose that is true.
Click to expand...
Click to collapse
I don't think so.
Isn't Safety Net part of Google Services?
That will still be updated.
Fif_ said:
I don't think so.
Isn't Safety Net part of Google Services?
That will still be updated.
Click to expand...
Click to collapse
SafetyNet itself will be, but to detect an unlocked bootloader, it relies on the bootloader to pass a kernel parameter that it looks at. The Nexus 5 bootloader doesn't pass any such parameter, and a bootloader update (of which there are no more) would be required for it to start.
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
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.
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 see that some custom roms pass Safety Net out of the box (no need to root, install magisk, etc). However, the same is not true for Xiaomi.EU rom. Is something wrong with this rom? Is there a way to fix this for Google to trust this rom? (I mean a way to fix it so that it passes Safety Net out of the box after flashing without having to root and install magisk, etc.).
Thanks.
aap7 said:
I see that some custom roms pass Safety Net out of the box (no need to root, install magisk, etc). However, the same is not true for Xiaomi.EU rom. Is something wrong with this rom? Is there a way to fix this for Google to trust this rom? (I mean a way to fix it so that it passes Safety Net out of the box after flashing without having to root and install magisk, etc.).
Thanks.
Click to expand...
Click to collapse
Can you pass safetynet after unlocking bootloader these days, don't think so
yerman said:
Can you pass safetynet after unlocking bootloader these days, don't think so
Click to expand...
Click to collapse
depends on the conditions, with the right custom rom and magisk hide - no probs at all
yerman said:
Can you pass safetynet after unlocking bootloader these days, don't think sany benefits of safety net pass?
Click to expand...
Click to collapse