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...

[Q] Installing twrp

Hi all,
I just recently purchased a G5, with the 2gb ram. I assume this is Cedric?
Do I need to download the 64 bit Cedric release of twrp?
I have unlocked the bootloader, but a bit confused about twrp.
I have twrp image, and I know how to use fastboot commands. My query is during the install of twrp and some guides warn about "swipe to modify". I am worried I will flash trwp and then end up with the stock rom wiped too and obviously no operating system.
I have experience of flashing twrp on a nexus device also my htc m8. This appears to be a little bit different.
Thanks,.

maritimesbob said:
Hi all,
I just recently purchased a G5, with the 2gb ram. I assume this is Cedric?
Do I need to download the 64 bit Cedric release of twrp?
I have unlocked the bootloader, but a bit confused about twrp.
I have twrp image, and I know how to use fastboot commands. My query is during the install of twrp and some guides warn about "swipe to modify". I am worried I will flash trwp and then end up with the stock rom wiped too and obviously no operating system.
I have experience of flashing twrp on a nexus device also my htc m8. This appears to be a little bit different.
Thanks,.
Click to expand...
Click to collapse
firstly, i need to tell you that i am a dummy so dont trust me i guess
but while i am these days reading into my moto g5 i can tell that
if you need the 64bit cedric it depends on which ROM you want to install.
in this context once you found your ROM there might be hopefully a guide to it:fingers-crossed:
tho i wondered if my moto g5 is compatible with x64 at all but yea i installed twrp cedric-3.2.1-0 x64 and it works
(i have the XT1676 Moto G5 , 3GB RAM, Fine Gold 16GB)

Actually, I am happy to keep the stock Moto rom. I wanted to install a custom recovery so I can flash xposed and use Gravitybox.

maritimesbob said:
Hi all,
I just recently purchased a G5, with the 2gb ram. I assume this is Cedric?
Do I need to download the 64 bit Cedric release of twrp?
I have unlocked the bootloader, but a bit confused about twrp.
I have twrp image, and I know how to use fastboot commands. My query is during the install of twrp and some guides warn about "swipe to modify". I am worried I will flash trwp and then end up with the stock rom wiped too and obviously no operating system.
I have experience of flashing twrp on a nexus device also my htc m8. This appears to be a little bit different.
Thanks,.
Click to expand...
Click to collapse
If you are sticking with stock rom flash my 32 bit twrp as it supports encryption (official twrp)
If you are flashing a custom nougat rom use the 32 bit twrp (official twrp)
If you are flashing a 64bit Oreo rom use the 64 bit twrp (you will need to format data to remove encryption)
If you are using twrp on stock rom and you swipe to modify then the rom will no longer boot - To get around around this you can either root the rom or flash the disable dm-verity zip
All instructions are on my official twrp thread - however the 64bit twrp will be on the 64bit custom rom threads as I do not support this
Read the FAQ section on the twrp thread as all the most common questions have answers there

So to flash an Oreo rom, I need to flash the 64bit version of twrp? As I am currently using the offical version which is 32bit, do I simply go in fastboot mode and flash the 64bit twrp and it will replace the other version of twrp I have installed?

dummy alert,
but yes, thats what worked for me
for example here, since its going abour Orea, you get the link for the x64
it is same named like the x86 version whats a bit weird
and another thing is that you can choose the "twrp-3.2.1-0-cedric.img" unlike its said on the linked poste. its obviously the newer version which i used successfuly flashing Oreo Android 8.1.0

Update to EMUI 8 (Mate SE) after nuking Factory ROM w Twrp?

Pulled kind of a boner. Got a Mate SE yesterday. It came with EMUI 5.1 and Android 7.0. I had read that version was still fairly easy/cheap to unlock the bootloader so I just left it as is without updating anything. Unlocked the bootloader, installed Twrp (to both recoveries) and now am unsure how to proceed with installing custom ROMs because I ended up nuking the factory ROM to install an older AOSP buggy build I found on here.
Didn’t realize that every custom ROM now seems to want you to install via fastboot with EMUI 8 required to have been installed beforehand, but I'm now stuck on this old AOSP ROM with no backup of the original & with Twrp recovery.
Sorry for all the questions but I've flash a million ROMs the old school Twrp ways since forever but this seems like a different beast. Should’ve slowed my roll. Is there some files I can flash via Fastboot or Twrp in order to use these new treble ROMs while keeping my boot loader unlocked? Thanks.

peestandingup said:
Pulled kind of a boner. Got a Mate SE yesterday. It came with EMUI 5.1 and Android 7.0. I had read that version was still fairly easy/cheap to unlock the bootloader so I just left it as is without updating anything. Unlocked the bootloader, installed Twrp (to both recoveries) and now am unsure how to proceed with installing custom ROMs because I ended up nuking the factory ROM to install an older AOSP buggy build I found on here.
Didn’t realize that every custom ROM now seems to want you to install via fastboot with EMUI 8 required to have been installed beforehand, but I'm now stuck on this old AOSP ROM with no backup of the original & with Twrp recovery.
Sorry for all the questions but I've flash a million ROMs the old school Twrp ways since forever but this seems like a different beast. Should’ve slowed my roll. Is there some files I can flash via Fastboot or Twrp in order to use these new treble ROMs while keeping my boot loader unlocked? Thanks.
Click to expand...
Click to collapse
Yes, in order to use the new "gsi" rims you need to do stock firmware upgrade. It is easy to do. But completely different then you seem to be used to , with twrp.
Just search for hwota , and I have a guide thread for 7x (basicly same as mate)

mrmazak said:
Yes, in order to use the new "gsi" rims you need to do stock firmware upgrade. It is easy to do. But completely different then you seem to be used to , with twrp.
Just search for hwota , and I have a guide thread for 7x (basicly same as mate)
Click to expand...
Click to collapse
Thank you. Just getting the files together but a little confused on one part. At the beginning, you say to extract the HWOTA package then put all the downloaded system files into the appropriate folder (HWOTA7 in my case), but at the final step you say to "From in TWRP install sdcard HWOTA--hi6250-7-8.zip", however that is the package we extracted from zip already before?
Does that mean I need to zip it back up with the system files I added in it in order to flash via Twrp? As is its just folders. Thanks. Just want to make sure I get everything right.

peestandingup said:
Thank you. Just getting the files together but a little confused on one part. At the beginning, you say to extract the HWOTA package then put all the downloaded system files into the appropriate folder (HWOTA7 in my case), but at the final step you say to "From in TWRP install sdcard HWOTA--hi6250-7-8.zip", however that is the package we extracted from zip already before?
Does that mean I need to zip it back up with the system files I added in it in order to flash via Twrp? As is its just folders. Thanks. Just want to make sure I get everything right.
Click to expand...
Click to collapse
Should be two folders. One each for 7 and 8. Each with twrp, and no-check recovery . And a zip file.

mrmazak said:
Should be two folders. One each for 7 and 8. Each with twrp, and no-check recovery . And a zip file.
Click to expand...
Click to collapse
Got it all done & went fine. Running Lineage at the moment. You're a life saver man, thanks!

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

Question Can anyone make TWRP for this device?

I want to flash custom rom on this phone, but without twrp I can't flash zip file, so I'm stuck with older version of gsi, without twrp, I can't root my devices for other Rom, so if anyone had skill to do so, please take your time and build twrp for people in needs, thanks

Which custom ROM?
Surely the custom ROM developer will have instructions of how to flash their custom ROM.....

elmor0 said:
Which custom ROM?
Surely the custom ROM developer will have instructions of how to flash their custom ROM.....
Click to expand...
Click to collapse
GSI can be flashed over ADB & TWRP thats what he means

nadejo said:
GSI can be flashed over ADB & TWRP thats what he means
Click to expand...
Click to collapse
GSI is a system image. On a dynamic partition device, that should be flashed through fastbootd. TWRP isn't needed for that.
TWRP will come, everyone must be patient...

Do you believe there will be any custom rom (not GSI) for this device?
As I research on previous models it doesn't seems like is ever going to happen

Not many but ROG 3 had a few custom ROMS...

Yesterday I posted a Beta TWRP for this device on Telegram. If you want to try it, here's the link:
EDIT: Removed TG link. See two posts down.

You barely need custom ROMs for these devices. The stock firmware is already quite lean and you can pretty much tweak, change and optimize them as you please. Signature spoofing works too...

Official TWRP is now available: https://forum.xda-developers.com/t/official-twrp-for-asus-rog-phone-6-6-pro-qualcomm-only.4518029/