Develop Bugs

[HELP!] Systemless Rooting on 6.0.1 Build MMB29P

Hi! So I'm looking to root my Nexus 5x following this guide. However, I can't find the modified boot.img for my build MMB29P. I have a brand new phone out of the box (my mic stopped working so this is a replacement) so I'd like to get this done in the next little while the phone has no data and I can wipe anything I need to without worry and use the restore afterwards. I also heard something about SuperSU being able to use stock boot.img or something of that nature, could someone clue me in? Thanks!

[GUIDE] Unlock/Root/Flash for Nexus 5X - Heisenberg's How-To Guide For Beginners
take a look at section 6
as an alternative there are some toolkits that may be more convenient to you (on-screen instructions and detailed faq/guides)

The latest version of SuperSU (v. 2.66 I believe) is automated for systems root. I actually used the SuperSU beta v. 2.62 to root. I just unlocked bootloader, flashed TWRP, and then flashed that version of SuperSU.
Sent from my Nexus 5X using Tapatalk

Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?

jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.

https://www.androidfilehost.com/?w=files&flid=43558

k.s.deviate said:
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
Click to expand...
Click to collapse
Even with systemless root?

When it comes to upgrading, there are a couple of routes you can take. Both involve downloading the official factory image ZIP first. Extract the contents, reboot into bootloader, and then you have option:
1. Edit the flash-all script (.bat for windows and .sh for Linux/Mac) by removing the -w option. Removing this option will prevent the upgrade from wiping user data. Once the option is removed, simply run the script to upgrade.
2. Flash the images individually. Sometimes certain things don't change like bootloader.img or radio.img. You should always flash boot.img, system.img, and vendor.img when updating. This is the route I take.
After flashing the images, you will need to reboot into Recovery mode and flash SuperSU. Then wipe cache and dalvik and reboot into system. If you use a custom kernel, you will need to reflash that as well after updating.
Sent from my Nexus 5X using Tapatalk

Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.

jkingaround said:
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
Click to expand...
Click to collapse
Google posts the official factory images on the developer site. Here is the link: https://developers.google.com/android/nexus/images
AFAIK the boot warning can't be removed, but I may be wrong. It's nothing to worry about though.
Having a custom kernel is not necessary, but there are benefits to using one. Custom kernels typically provide better battery life with same or improved performance. They can also make your device run cooler and use less memory. Custom kernels also allow for various tweaks such as change vibration intensty, screen DPI, headphone/speaker gain, etc. I personally use ElementalX with the Interactive Governor tweaks from the thread in the general forum, but I've read that Franco Kernel is very good as well and will probably try that out in the future.
Sent from my Nexus 5X using Tapatalk

jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
Just pick a custom rom to try and follow OP instructions. Cataclysm seems to be a hit...

Is it safe to mod locked device?

As the title says is it possible to root, install modifications to stock ROM and is there a fast way to revert everything is something go wrong? I'm asking because support for 5X has ended, and I can't permanently unlock bootloader. I don't want to hard brick this phone by mistake and also I don't want just look how this device is being wasted.
So here's some probably noob questions that I want to ask:
1. Can I install TWRP on NO RPMB bootloader and boot it without issues? If so, how?
2. What recovery version should I install 4-core or regular 6-core?
3. Can I root device and hide it with magisk?
4. If an security update appear how to install it since stock recovery is replaced with TWRP?
5. If something go wrong like 2nd death loop how to revert everything? Can I simply flash stock system image in TWRP to "fix" device?
Thanks in advance.

You might try the solution the user in this thread suggested, https://forum.xda-developers.com/nexus-5x/help/rpmb-bootloader-locked-t3481906/page2

So I have to unlock bootloader, then flash TWRP, Super SU, compatible Magisk in one attempt, then I'm ready to go? Will TWRP boot and work like nothing happened?
Sent from my Nexus 5X using XDA Labs

I haven't tried it but based on the steps I would think it should work. It won't hurt anything. It also won't stop the bootloader from locking upon a reboot. But as long as you can unlock it prior to flashing any of the partitions as the reddit thread suggests you could be ok.

Locked bootloader won't allow to boot custom kernels that's sure, but will it boot modded stock kernels from this thread https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169 since they're stock kernels

Banan PL said:
Locked bootloader won't allow to boot custom kernels that's sure, but will it boot modded stock kernels from this thread https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169 since they're stock kernels
Click to expand...
Click to collapse
I'm running custom kernels just fine with locked bootloader.

CazeW said:
I'm running custom kernels just fine with locked bootloader.
Click to expand...
Click to collapse
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs

Banan PL said:
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
As long as TWRP is installed and "stuck" (ie: boot directly into TWRP after flash), you can basically flash anything (custom ROMs/kernels etc.).
The worst thing that can happen is that you brick the ROM without TWRP installed and the ROM is bricked/the oem unlock flag is reset (not tripped). Even then there's a .tot file somewhere here on XDA that can recover the phone.
I'm assuming that an upgrade to O is also possible via stock images (unlock bl, flash stock images, boot into O, trip the OEM unlock flag, unlock BL and follow the steps described).

Banan PL said:
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Haven't tried Jolla's multiboot or drivedroid. As long as you can get into fastboot, you can just unlock it again and flash stock (though you will obviously lose everything that's on the device). Haven't tried flashing custom ROMs but as custom kernels are working, I don't see why custom ROMs wouldn't.

negusp said:
As long as TWRP is installed and "stuck" (ie: boot directly into TWRP after flash), you can basically flash anything (custom ROMs/kernels etc.).
The worst thing that can happen is that you brick the ROM without TWRP installed and the ROM is bricked/the oem unlock flag is reset (not tripped). Even then there's a .tot file somewhere here on XDA that can recover the phone.
I'm assuming that an upgrade to O is also possible via stock images (unlock bl, flash stock images, boot into O, trip the OEM unlock flag, unlock BL and follow the steps described).
Click to expand...
Click to collapse
In short unlocking bootloader JUST allows to flash system images in fastboot, nothing more nothing less? So if I flash TWRP then Lineage it will boot and work like nothing happened (like on 5X with unlocked bootloader), it's sounds so good that I can't even believe.
Sent from my Nexus 5X using XDA Labs

Banan PL said:
In short unlocking bootloader JUST allows to flash system images in fastboot, nothing more nothing less? So if I flash TWRP then Lineage it will boot and work like nothing happened (like on 5X with unlocked bootloader), it's sounds so good that I can't even believe.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I don't own a device without RPMB (I got a fairly new refurb), but I've used TWRP/flashed ROMs and kernels successfully with the bootloader locked and TWRP installed.

Alright I'll flash TWRP take nandroid and hopefully device will boot. Can someone give me link to 4-core TWRP, I can't find it?
Sent from my Nexus 5X using XDA Labs

Google 4 core twrp 5x xda. It's in that thread. https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199

Strange I can't flash recovery it's getting replaced by stock. TWRP shows a message, but I'm unable to read it. It appear for a while then device reboot into system.
It says something like "Renamed stock recovery file to /system to prevent the stock ROM from replacing TWRP" or something like that. Any help?

Banan PL said:
Strange I can't flash recovery it's getting replaced by stock. TWRP shows a message, but I'm unable to read it. It appear for a while then device reboot into system.
It says something like "Renamed stock recovery file to /system to prevent the stock ROM from replacing TWRP" or something like that. Any help?
Click to expand...
Click to collapse
Did you unlock and then without rebooting flash the TWRP?

CazeW said:
Did you unlock and then without rebooting flash the TWRP?
Click to expand...
Click to collapse
I've unlocked bootloader then flashed TWRP and rebooted into recovery

Banan PL said:
I've unlocked bootloader then flashed TWRP and rebooted into recovery
Click to expand...
Click to collapse
Did you then do a factory reset and flash root? That should make it stick. If not, you can always just use the TWRP app to get into TWRP when needed.
Edit: You also booted to recovery straight from fastboot after flashing, without rebooting the phone?

CazeW said:
Did you then do a factory reset and flash root? That should make it stick. If not, you can always just use the TWRP app to get into TWRP when needed.
Edit: You also booted to recovery straight from fastboot after flashing, without rebooting the phone?
Click to expand...
Click to collapse
This is what I've done: unlocked bootloader, format data in fastboot, flashed twrp, rebooted into twrp. Here device keep rebooting into system and replacing twrp with stock recovery.

Banan PL said:
This is what I've done: unlocked bootloader, format data in fastboot, flashed twrp, rebooted into twrp. Here device keep rebooting into system and replacing twrp with stock recovery.
Click to expand...
Click to collapse
So you are not actually getting into recovery at all. Try with different TWRP image.

CazeW said:
So you are not actually getting into recovery at all. Try with different TWRP image.
Click to expand...
Click to collapse
I tried with regular TWRP 4-core modded TWRP and with Multiboot TWRP. Same result.
Sent from my Nexus 5X using XDA Labs

Keep Magisk/Root and Take Updates?

On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?

wy1d said:
On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?
Click to expand...
Click to collapse
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.

mac796 said:
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.
Click to expand...
Click to collapse
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk

wy1d said:
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA

mac796 said:
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA
Click to expand...
Click to collapse
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk

wy1d said:
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.

mac796 said:
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.
Click to expand...
Click to collapse
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk

wy1d said:
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it

mac796 said:
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it
Click to expand...
Click to collapse
Such a bummer the Magisk method doesn't work anymore. It's definitely the safest and most graceful.
Sent from my Pixel 2 XL using Tapatalk

Ota update for pixel 2 xl with magisk and twrp already installed

I am sure this has been asked and answered 100 times but for the life of me I can't find a definite answer. I have a Pixel 2 XL and it is rooted and I have Magisk and TWRP installed on it. I want to be able to install the OTA for this month, but I do not want to lose anything on the phone. I also would rather not lose Magisk or TWRP. Normally on my android phones I use ROMs and can just update through TWRP, but I want to stay on stock because I don't want to lose Active Edge. So can someone please help me by giving me step by step instructions or point me to instructions that are simple to follow so I can take the OTA?
I really appreciate the help.

I was having the same problem and was helped by some of the members here.. Best way is to flash the firmware after removing the -w from the flash all file. Then flash twrp and magisk.
Ota

Thanks for your help. I will try that.

magicmaker said:
Thanks for your help. I will try that.
Click to expand...
Click to collapse
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:

Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.

rank78 said:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
Click to expand...
Click to collapse
Not that I'm aware of, but maybe some on the horizon...

Badger50 said:
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Click to expand...
Click to collapse
Hi, quick question
I am only able to do them steps above if I have done 'fastboot unlock_critical'? I have only done 'fastboot unlock'
Also I would need to boot into TWRP and flash a kernel + magisk to retain root?

You have to issue the "fastboot unlock_critical" command in order for the bootloader to update, since the bootloader is included in both factory images and full OTAs. Speaking of full OTA's, one of our recognized developers, @elliwigy, revealed (thread here) that it is possible to flash a full OTA image through TWRP, which eliminates the need to open the factory image and remove the -w flag from the last line. Flashing the OTA works because TWRP doesn't check signatures like the stock recovery. You will lose both root and TWRP upon reboot however, so you will still need to connect to a PC in order to reinstall TWRP so you can subsequently replace the stock Kernel with the Flash Kernel and then root.
I can verify this works, as I tried it with the May update.

Android 10 root/twrp

Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?

More details will be needed to help. Bootloader unlocked? Guessing yes since you say you had twrp. Check the guide section for root instructions.

Yes I have it unlocked. I looked at the guide and it looks like I will have to reflash the stock rom which I'd like to avoid.

Kreuger said:
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
Click to expand...
Click to collapse
Since, twrp is not available yet for Android 10 (Q), I suggest one of the three following options:
1. If you have to re-flash the Pixel 3 XL Android 10 (Q) Factory image, do #4 'keep data' in this Guide.
2. If your Pixel 3XL has the latest Android 10 (Q) Factory image installed, just do #9 A. in this Guide to root.
3. If you are on a Custom ROM follow the OP Instructions in the Custom ROM thread to root.

Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?

Kreuger said:
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Click to expand...
Click to collapse
Yes!
Why not do #1 update your Pixel 3 XL to the February Factory image (QQ1A.200205.002). You will not lose your data (need to reinstall anything). Then do #2 to root.

I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.

Kreuger said:
Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Some people are reporting that issue. You can set the custom channel to canary/canary debug manually. Check the magisk thread.

Thank you. I tried to find it on the github site and found nothing.

Kreuger said:
Thank you. I tried to find it on the github site and found nothing.
Click to expand...
Click to collapse
It is under the magisk files repo.

Kreuger said:
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Kernel/Kernel Managers are optional. #10 B ,in the guide, updated.

Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.

Kreuger said:
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Click to expand...
Click to collapse
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.

wangdaning said:
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
Click to expand...
Click to collapse
Ah I was unaware. Thanks