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.
Related
Stock Nexus 5X Kernel + SafetyNet Patch
Current version: android-msm-bullhead-3.10-nougat-mr1.1
Suitable for build: N4F26T
I compiled the stock kernel for the Nexus 5X and applied the SafetyNet patch by sultanxda.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is for Android 7.1.1, build N4F26T!!!! This will not work on any prior build.
- All stock features that came with the N4F26T build will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the kernel included in the N4F26T build, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Extract <boot_image>.img from zip file
- Test it with: fastboot boot <boot_image>.img
- Once you know it works, flash with command: fastboot flash boot <boot_image>.img
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
And otherwise, I'm not a professional developer, just a hobbyist. Please don't ask me for a ton of help, I only created this kernel because I want to run completely stock, but still use Android Pay while having an unlocked bootloader in case I ever decide to root my device in the future. I will try to maintain this kernel with each new release until I lose interest
(shamelessly copied from Sakete's kernel for the Pixel/Pixel XL. Thanks for the inspiration, Sakete!)
It will work on Rooted Android 7.1.1 NMF26F ?
AFK269 said:
It will work on Rooted Android 7.1.1 NMF26F ?
Click to expand...
Click to collapse
You'll have to test it and let me know as I'm not using it on a rooted phone
If your root method trips SafetyNet then this kernel is useless to you, as it will only bypass the unlocked bootloader check and not the root check.
Well I tried to install your kernel and it is missing files and will not install. I wish there was a way to just flash the bypass of safety net with any kernel that you wanted to use.
weaselskhs said:
Well I tried to install your kernel and it is missing files and will not install. I wish there was a way to just flash the bypass of safety net with any kernel that you wanted to use.
Click to expand...
Click to collapse
Can you clarify? Did you flash with fastboot? What steps did you use?
Bootloop while installing unpacked .img file using TWRP. PixelROM 7.1.1, SuperSU v2.78 SR2
doggie13_ said:
Bootloop while installing unpacked .img file using TWRP. PixelROM 7.1.1, SuperSU v2.78 SR2
Click to expand...
Click to collapse
I wouldn't expect this kernel to work with custom ROMs.
Well that makes sense as I am also running Pixel Rom 7.1.1 and super su
It'd be super cool if this patch worked with PixelRom
Is there a specific reason this doesn't work with custom ROMs?
19lmyers said:
Is there a specific reason this doesn't work with custom ROMs?
Click to expand...
Click to collapse
Well for starters there is code missing from the stock kernel to work properly with the pixel rom. Which begs the question why you would want to flash the stock kernel on a pixel rom when you can use other custom kernels. I believe that Franco's kernel has the safetynet patch included.
Thanks to share
Hi,
Will this work for 6p?
Thanks
turbo81 said:
Hi,
Will this work for 6p?
Thanks
Click to expand...
Click to collapse
No. It's only for Nexus 5X (Bullhead).
Subbed. I'll be waiting for the N4F26I build. I miss using Android Pay.
Does anyone know if there is or will be a patch for the nexus 6p?
drew_t said:
Does anyone know if there is or will be a patch for the nexus 6p?
Click to expand...
Click to collapse
If you want use Franco.Kernel ... He has already did this. Find it at N6P thread, not here.
apatal said:
Subbed. I'll be waiting for the N4F26I build. I miss using Android Pay.
Click to expand...
Click to collapse
+1
I am waiting for N4F26I build.
Updated OP for N4F26I. Unfortunately, my 5X started bootlooping (hardware issue) so I don't have the device to test it with anymore
Updated for N4F26O.
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.
every time i flash the zip from the official post but it never passes cts or basicintegrety am i supposed to patch the boot image
You want to have root access or want to flash magisk?
Yes, you need to flash patched boot image as well
shashank1320 said:
You want to have root access or want to flash magisk?
Yes, you need to flash patched boot image as well
Click to expand...
Click to collapse
no mean i flash magisk using the zip and basicintegrety and cts always fails is this because the way i flashed magisk
Sammy4798 said:
no mean i flash magisk using the zip and basicintegrety and cts always fails is this because the way i flashed magisk
Click to expand...
Click to collapse
Let me check and give you correct method. Are you on Nougat or Oreo?
shashank1320 said:
Let me check and give you correct method. Are you on Nougat or Oreo?
Click to expand...
Click to collapse
nougat
shashank1320 said:
Let me check and give you correct method. Are you on Nougat or Oreo?
Click to expand...
Click to collapse
nougat
Sammy4798 said:
nougat
Click to expand...
Click to collapse
There's a post above of yours identical to this, no need to bump.
Anyway, to pass SafetyNet check there's a series of requirements that your device needs to satisfy, like untouched hosts file (you can modify them systemlessy thanks to Magisk own module), root detection must be hide to almost everything that contains "Google" in package name (usually hiding Play Services, Google Play Store and Google Services Framework should be enough) and your device must have a valid fingerprint (and so, certified as "valid" to Google's network) and finally, you must have a locked bootloader. The hardest step is the bootloader hiding, and for this you can give a try to SafetyPatch module - https://forum.xda-developers.com/apps/magisk/module-safetypatcher-t3809879 - for me it worked like a charm.