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.
Related
Greetings,
i've android 6.0.1 (MMB29K) December security patch and i want to update to 6.0.1 (MMB29S) the January security patch. i'm rooted , xposed and using twrp with custom kernal . any ideas how i can update without losing any of those ?
??
Flash the factory image (but not userdata.img) then re-root. It's the only way
EddyOS said:
Flash the factory image (but not userdata.img) then re-root. It's the only way
Click to expand...
Click to collapse
what would i lose in this case ?
You should not lose anything as you are not touching the userdata partition.
even the configurations and settings of the system and apps ?
I asked the same question a few months ago. You lose nothing. As long as you don't touch data/userdata, your device will reboot looking exactly as it did before, just without root. I don't have Xposed, so I can't guarantee that, but everything else will be fine in my experience.
Can I use this trick to update to 6.0.1 ? I now have 6.0.0 with franco kernel + xposed framework and root
dont want to install everything from the begininng...
deepstate said:
Can I use this trick to update to 6.0.1 ? I now have 6.0.0 with franco kernel + xposed framework and root
dont want to install everything from the begininng...
Click to expand...
Click to collapse
+1
I have all that and flash a debloated stock, rooted rom that is updated every month, dirty flash, and I loose nothing. Just boots and all is good
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.
Hey everyone,
I have a Nexus 5 that I haven't updated in a long time that I'd like to get the latest possible OS for. The only modifications I've made which I think might be important are:
Unlocked bootloader
Rooted using SuperSU (v2.8.2 currently)
Installed XPosed (installer v2.6.1, not sure what version of the framework but it should be the latest supported by 4.4.4) with a few modules
Installed App Ops and removed permissions from some apps
Installed StickMount
I don't believe I have any custom recovery installed (I'd used a script to root and install XPosed originally and I don't know if it made any other changes). I'm comfortable using adb if needed but I'm cool with tools like FlashFire too.
My end goal is to have an updated OS with root and XPosed. I assume I'll need Magisk for XPosed, but not sure about root.
How should I go about doing this? I'm cool with losing all of my data (I'll be making backups with Titanium Backup) though knowing ahead of time if that'll be the case would be nice. If it's possible to update without losing data and without affecting anything that'd be nice, but maybe a clean start would be good? The OTA guide on this forum is only for 5, not 6, and most online guides start with 5. I don't want to mess up obviously. xD
Any advice/steps would be appreciated! Thanks!
Aecyl said:
Hey everyone,
Click to expand...
Click to collapse
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
pavik62 said:
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
Click to expand...
Click to collapse
The link you gave doesn't have the latest 6.0.1 build and it also says that it requires a minimum bootloader (HHZ12h) that I don't have (I have HHZ11k). Would it be possible to use the latest build from Google? What do I do about the bootloader? And would using TWRP as the recovery prevent me from passing SafetyNet?
Thanks for replying!
Could I follow this guide with the latest factory image and then install Magisk, root, and XPosed? https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Roxasmaker said:
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Click to expand...
Click to collapse
Would I have to do anything to XPosed or supersu first? I'd like to update to 6.0.1, too. I've seen online that there are OTA updates for it too.
Nope. But you may have to reinstall root, which is very easy once you're updated. Just let the updates do their thing, and you'll be on your merry way! Hope I helped
I think what I'll do is flash stock 4.4.4 keeping user data and then use the OTAs to update to 6. That way I have a clean system install to use Magisk with without losing any user data. (If that doesn't work I'll just flash 6.0.1 for a clean install.)
I'm staying in S244, Updating to S251 update is seriously required for upcoming custom Roms install ?
If s251 update required,
it requires to install my stock boot and stock recovery (almost stock rom)
Wonder Wicked Witch said:
I'm staying in S244, Updating to S251 update is seriously required for upcoming custom Roms install ?
If s251 update required,
it requires to install my stock boot and stock recovery (almost stock rom)
Click to expand...
Click to collapse
no it doesn't. at least not for LOS.
im still on S244 but I'm beta testing LineageOS 14.1 which is already based on blobs from S251.
celoxocis said:
no it doesn't. at least not for LOS.
im still on S244 but I'm beta testing LineageOS 14.1 which is already based on blobs from S251.
Click to expand...
Click to collapse
Thanks for the info, Thumbs up?
I'm on s251 and full stock, the 14 days are finished for the bootloader.
So can i root my P2 safely or I must go back to s244 ?
Mathurin239 said:
I'm on s251 and full stock, the 14 days are finished for the bootloader.
So can i root my P2 safely or I must go back to s244 ?
Click to expand...
Click to collapse
no you can stay on s251 of course and still be able to unlock and root your phone.
im on s251 too now and fully reset my phone to test los beta from scratch.
P2 with TWRP and root with magisk, it's all good !!
No plan for updating to s251. Cuz I'm using custom rom and s251 is not a major update, it contains only November security patch + android pay.
Wonder Wicked Witch said:
No plan for updating to s251. Cuz I'm using custom rom and s251 is not a major update, it contains only November security patch + android pay.
Click to expand...
Click to collapse
... which you want to have
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
I have updated to android 12.. will I need to revert in order to do any flashing?
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
systemshock869 said:
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
Click to expand...
Click to collapse
Well, kind of. It now exists as a Magisk module. You need to install Riru module and LSposed module to get an "Xposed like" feature.
BUT, latest Magisk versions (Beta and Canary who are more compatible with Android 12) now have a new feature called zygisk. That feature is not compatible with Riru and LSposed. So if you're going to LSposed, use latest stable Magisk, which still works.
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
systemshock869 said:
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Click to expand...
Click to collapse
I'm running stock with latest Magisk Canary and besides that, I only use my Addon features module (which adds some cool custom stuff into stock ROM).
systemshock869 said:
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
Click to expand...
Click to collapse
The only ROMs I know that exist for Pixel 4a are ABC and Proton AOSP ROMs. But, if I'm not mistaken, there aren't any ones built for Android 12.
Cheers!
Thanks so much! It's always frustrating, as a casual user, to come back to the mod scene and have to try to re-learn the current meta for both android modding and your particular device by wading through scattered forum posts.
Typhus_ said:
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
Click to expand...
Click to collapse
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
JohnC said:
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
Click to expand...
Click to collapse
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
systemshock869 said:
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
systemshock869 said:
Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
Just that some Xposed apps and modules only work with android 10, and I don't see any features of A11 or A12 that I would use.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
systemshock869 said:
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
Click to expand...
Click to collapse
SafetyNet will fail as soon as you unlock your bootloader.
There is a Magisk module provided by kdrag0n that fixes that but the free version, for the time being, needs Riru and Lsposed to work properly. That means you need to root your device using stable Magisk 23.0 if youwant to fixe SafetyNet right away.
The magisk patched boot.img version that I've shared on that post I've pointed out to you is Canary Magisk, where Magisk Hide feature no longer exists and it's incompatible with Riru and LSposed, as I've already said.
I'm running my device with SafetyNet failing and I couldn't care less since it's not problematic for my daily usage. Any app I cannot install through playstore can be installed using apkmirror. As for Magisk hide, it doesn't exit anymore but there's a "App deny list" that works as well to "hide" Magisk from banking apps (for instance).
I'm not using TWRP since there's really no need for it on Pixel 4a.
Everything can be done through fastboot and Magisk.
Anyway, if you really want to have SafteyNet passing, you need to manually patch stock boot.img (that you may find as well on that thread I've shared) with latest Magisk stable and flash that version. Afterwards install Riru, LSposed and SaftyNet fix by kdrag0n.
Cheers!
Typhus_ said:
I'm not using TWRP since there's really no need for it on Pixel 4a.
Click to expand...
Click to collapse
I use TWRP to do image Backups/Restores.
JohnC said:
I use TWRP to do image Backups/Restores.
Click to expand...
Click to collapse
I don't need to do that. Everything I have is backed up on my Google account.
Sure, /data and stuff like games or whatever needs to be downloaded again but, it's fine by me.
Furthermore, I don't use custom ROMs any more. Just stock Pixel ROM with my mods installed and I get by just fine, smooth and happy.
Cheers!
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
Depends on the ROM. LineageOS staff say to install the latest Android 11 image before flashing a LineageOS 18.1 rom. I'd assume that to be true for any other roms based on LineageOS.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Do u have to disable OTA updates to keep from a calamity? If so, are manual updates a pain? Can u retain ur data with manual OTAs?
Zaxx32 said:
Do u have to disable OTA updates to keep from a calamity?
Click to expand...
Click to collapse
Yes.
Zaxx32 said:
If so, are manual updates a pain?
Click to expand...
Click to collapse
No.
Zaxx32 said:
Can u retain ur data with manual OTAs?
Click to expand...
Click to collapse
Yes.
Everytime a new build comes up, download the factory image directly from Pixel Official firmware site, extract it, open flash_all.bat, on the update command you see a "-w" flag. Delete the "-w" and save flash_all.bat. Connect device to PC, reboot to fastboot and run edited flash_all.bat.
If you don't delete the -w, you'll lose your data.
Cheers!
Awesome....thanx!