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

Root questions

I'm on a stock unlocked 10 in the USA. I'm trying to understand all the root options. I really only want root for a couple reasons which is primarily titanium backup and greenify.
I don't believe I need sunshine for this but believe I need to unlock the bootloader. Correct? My concern is what happens with otas? How will I get them? Will I have to unroot every time I want to apply one? Do I have to apply a new recovery for what I want to do?
I also read that there are potential radio issues when rooting. Will I encounter that?

I'm in the same boat and new to htc. You need to unlock the bootloader to root. You only need s-off if you want to flash firmware from other regions etc.
If you flash twrp/root, you can't get OTA updates. So you would have to flash custom rom which hopefully updates to include the latest OTA (will take some time)
Or... You restore back to stock system and recovery (I think?) then get OTA, then reflash twrp and re-root.
I can't find a clear guide anywhere, there are snippets of information hidden away in several post's. Once I understand, I will flash twrp/root and try Leedroid rom, knowing I can restore via nandroid, hopefully. Also think there are issues if you change system, hosts file, gps.conf etc, it's not clear....
So... waiting for clear guidance on, how to restore back to stock, meaning I can try twrp/root/custom rom.
Missing greenify, adblock, changing kernel params, TBackup to debloat and backup
Sent from my HTC 10 using XDA-Developers mobile app

http://forum.xda-developers.com/showthread.php?t=3373025
Sent from my Nexus 5 using XDA-Developers mobile app

Are there any clear instructions on this?
Sent from my HTC 10 using XDA-Developers mobile app

Also do we lose encryption? If we flash back to stock to take an ota, so we have to wipe every time?
Sent from my HTC 10 using XDA-Developers mobile app

Bump....

If you S-Off and S-On, you lose data because you lose/gain encryption keys. (Or.. well, somethin' like that.)

Thanks but I don't think I need s off. I just want to greenify and backup
Sent from my HTC 10 using XDA-Developers mobile app

km8j said:
I'm on a stock unlocked 10 in the USA. I'm trying to understand all the root options. I really only want root for a couple reasons which is primarily titanium backup and greenify.
I don't believe I need sunshine for this but believe I need to unlock the bootloader. Correct?
Click to expand...
Click to collapse
Correct.
km8j said:
My concern is what happens with otas? How will I get them? Will I have to unroot every time I want to apply one? Do I have to apply a new recovery for what I want to do?
Click to expand...
Click to collapse
In order to root, you will need to flash a custom recovery (TWRP) and the latest BETA SuperSU (either the modified version that leaves forced encryption enabled, or the standard version that requires you to specify that prior to flashing). Doing that alone will not break your ability to receive an OTA update. However, for an OTA to be completely installed, stock recovery is required (which replaces TWRP). After rooting, you can return to stock recovery if you desire, and then you should be able to install the OTA with no problem, provided you haven't modified system at all. However, you'll then have to re-install custom recovery and root again, as the new boot.img that's included in the OTA zip will remove root access. Then you can follow the same procedure to be prepared for future OTAs.
The question really becomes, will you be using either of those apps to modify system? I don't personally know how they work and why they need root access - I'm assuming it's to access information under /data. If they're not touching /system, you should be fine.
km8j said:
I also read that there are potential radio issues when rooting. Will I encounter that?
Click to expand...
Click to collapse
The radio issues aren't necessarily related to root - they're related to removing encryption. Using the modified SuperSU or applying the proper flag to the standard SuperSU prevent this from being an issue.

Flash stock over rooted to get OTA

I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.

Technically you'll be updating your device by flashing the newest stock anyway. No need for OTAs. You can then re-root.

GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
Yes, sounds doable

ABotelho23 said:
Technically you'll be updating your device by flashing the newest stock anyway. No need for OTAs. You can then re-root.
Click to expand...
Click to collapse
Not what i meant. Let's say I'm on rooted OB18. But i want to update it to OB19. all i have is OB18 stock firmware. So, can i flash OB18 over rooted OB18 and then update it to OB19 (ota). Then re-root.
The reason I'm asking this is i have a very limited data internet connection. So i can save GBs if this is doable.

XDRdaniel said:
Yes, sounds doable
Click to expand...
Click to collapse
Yeah. Well.. I'm gonna try this out myself. Thanks! :highfive:

GTRanushka said:
Not what i meant. Let's say I'm on rooted OB18. But i want to update it to OB19. all i have is OB18 stock firmware. So, can i flash OB18 over rooted OB18 and then update it to OB19 (ota). Then re-root.
The reason I'm asking this is i have a very limited data internet connection. So i can save GBs if this is doable.
Click to expand...
Click to collapse
Plan to keep a copy of OB18 around? If so, then yea absolutely it should work. Root will either modify your system or your kernel depending on the method, which both get overwritten if you flash stock.
Issue you'll probably end up having in the future though is that if you always use OB18, when it comes time to install OB20, you'll be downgrading without a wipe, which I don't think is a great idea.

GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
No you can't.
Because OTA will fail for "partition mismatching": the systemless root alters only but anyhow the /boot partition.
You must update with FOTA (Full OTAs), doesn't matter you're using stock or TWRP recovery.
The OxygenOS built-in updater should detects your system as modified and download only FOTAs.

Simone98RC said:
No you can't.
Because OTA will fail for "partition mismatching": the systemless root alters only but anyhow the /boot partition.
You must update with FOTA (Full OTAs), doesn't matter you're using stock or TWRP recovery.
The OxygenOS built-in updater should detects your system as modified and download only FOTAs.
Click to expand...
Click to collapse
Let's say he has open beta 18, rooted and twrp installed, if he flashes ob18 again over it, this will get rid both of the root and twrp, resulting in an untouched system, therefore, ota after this will be possible. He can then flash back twrp and root the device

XDRdaniel said:
Let's say he has open beta 18, rooted and twrp installed, if he flashes ob18 again over it, this will get rid both of the root and twrp, resulting in an untouched system, therefore, ota after this will be possible. He can then flash back twrp and root the device
Click to expand...
Click to collapse
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.

Simone98RC said:
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Click to expand...
Click to collapse
This would be weird because I always had to flash magisk after a ota update..

GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
In order to flash OTAS has to have stock rom but also recovery stock and bootloader blocked but not installed the OTAS otherwise it tells you that you have something modified and you have to download the complete rom. (That does not suit you)

ajnexus5 said:
In order to flash OTAS has to have stock rom but also recovery stock and bootloader blocked but not installed the OTAS otherwise it tells you that you have something modified and you have to download the complete rom. (That does not suit you)
Click to expand...
Click to collapse
You don't need a locked bootloader for OTA just have to flash stock full ROM zip and stock recovery then you're good to go

Simone98RC said:
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Click to expand...
Click to collapse
Why i try to unroot and do OTAs is the much less download size compared to FOTAs.

Renosh said:
You don't need a locked bootloader for OTA just have to flash stock full ROM zip and stock recovery then you're good to go
Click to expand...
Click to collapse
I tried it with the bootloader open and I did not think that something is not right that it has to download complete the rom.:

from B189 to Oreo .. root/bootloader unlocked/device decrypted! HOW?

Hello everyone
so finally also C432 has received Oreo update !
right now i'm on B189 with root , bootloader unlocked and device decrypted (and twrp)
now the question is....
how can i upgrade to Oreo and and keep device decrypted bootloader unlocked without losing everything and install all again?
is there any way to achieve it? thank you for your help/suggestions !:fingers-crossed:

none? is not possible? It'll just delete everything again?

Hi.. I've done rooting Oreo but it's not properly rooted though. If you're already rooted then search DUK_fullOTA_flasher.zip and follow instructions. You'll get Oreo installed without loosing anything and still unlocked bootloader but you'll loose TWRP and decryption. Copy update.zip file from phone to pc and then use HuaweiUpdateExtractor on pc and extract Ramdisk.img from UPDATE. APP from the 'update.zip' and put it back in phone. Then use Magisk manager to patch this img file and then move it back to pc after patching. Then use adb/fastboot method to flash it. Voila!! You're rooted but device is still encrypted. I've not done any factory reset/data wipe bcz don't wanna loose my data. Device encryption won't let you use any module and you can't change anything apart from using systemless hosts AdAway and also you can use Greenify or TB but can't use any feature that writes to system.

puneetbhagat said:
Hi.. I've done rooting Oreo but it's not properly rooted though. If you're already rooted then search DUK_fullOTA_flasher.zip and follow instructions. You'll get Oreo installed without loosing anything and still unlocked bootloader but you'll loose TWRP and decryption. Copy update.zip file from phone to pc and then use HuaweiUpdateExtractor on pc and extract Ramdisk.img from UPDATE. APP from the 'update.zip' and put it back in phone. Then use Magisk manager to patch this img file and then move it back to pc after patching. Then use adb/fastboot method to flash it. Voila!! You're rooted but device is still encrypted. I've not done any factory reset/data wipe bcz don't wanna loose my data. Device encryption won't let you use any module and you can't change anything apart from using systemless hosts AdAway and also you can use Greenify or TB but can't use any feature that writes to system.
Click to expand...
Click to collapse
thank you for your kind and full answer I appreciate it! seems like I'll have to wait cause having device decrypted is a must as is a must to have it rooted! I'll stick to b189 until a better way is found [emoji4]
Sent from my DUK-L09 using Tapatalk

simika said:
thank you for your kind and full answer I appreciate it! seems like I'll have to wait cause having device decrypted is a must as is a must to have it rooted! I'll stick to b189 until a better way is found [emoji4]
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
Any time mate :good:
I know there is a method to decrypt it but I really don't wanna lose my data. Here is the link:
https://forum.xda-developers.com/honor-8-pro/how-to/guide-magisk-root-honor-8-pro-oreo-t3743587

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.