Database Develop

[5.0] [info] Basic overview of root (and update) options for Lollipop

As things have changed with how root is obtained and how OTA's are limited to users since 5.0, I hope this thread to serve as a basic overview of the root options available to you. I see a lot of threads asking about updating to Lollipop and about returning to stock to receive OTA updates.. from rooted users.
*The below post covers updating to 5.0 only. For updating to 4.4.x, read this thread: [Info] Rooted user? Learn to update properly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have created this thread as I have strong feelings about rooted users and OTA's in general, so I wanted to collect my thoughts together in a single thread to hopefully persuade rooted users to avoid OTA updates. Of course, you're free to choose to ignore this.
OTA's are simple for unrooted users. They are minimal effort, quick and require no knowledge. However they have a propensity to go wrong - often resulting in a user having to factory reset to get things working.
OTA's are designed to be small to save on data usage. This is achieved by not supplying the entire ROM, kernel or app, but instead, including patches. These patch files (*.p) will unpack the recovery.img, bootloader.img, boot.img or *.apk and insert the new code into it. This means the OTA expects an exact version to install. You cannot skip an OTA and expect to apply a later one because the code in the patch might not "fit". Also, this is why modified users cannot apply an OTA. There are ways for rooted, stock kernel, no modification users to apply OTA updates but it is not recommended
Please note, rooted users will still receive the OTA notification. You do not need to apply it though. Some Custom ROMS even receive it.
Well if you are modified, you have to first return completely to stock to apply an OTA. This is a relatively long process compared to other options available to you. If you are simply rooted with stock kernel and no modifications, you can simply re-apply root after accepting the OTA, but it's a bit messy and still - it's an OTA that can go wrong. I think part of OTA's appeal is you can do it anywhere - but this is also it's biggest problem. rooted users need resources to be available to them so they can remedy whatever needs remedying after application.
In short, it's just not the best option, Why would anyone ever choose "not the best"?
Section 1, from Stock (unrooted)
Method 1 (You are fully stock 5.0)
1. Unlock bootloader if necessary (This wipes data)
2. Fastboot flash a custom recovery image (of your choice)
3. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
4. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
Method 2a (You are fully stock 4.4.x)
1. Unlock bootloader if necessary (This wipes data)
2. Fastboot flash a custom recovery image (of your choice)
3. Fastboot flash stock 5.0 system.img (this will not wipe data if yous till have data at this time, however, you MAY still need to wipe data later)
4. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
5. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
Method 2b (You are fully stock 4.4.x)
1. Unlock bootloader if necessary (This wipes data)
2. Accept OTA update
3. Fastboot flash a custom recovery image (of your choice)
4. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
5. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
Method 3a (You are fully stock 4.4.x)
1. Unlock bootloader if necessary (This wipes data)
2. Use the google Factory flash-all method to flash 5.0
3. Use the CF-Autoroot method to modify the kernel (boot.img) for root (Will not get permissive mode) and SuperSU
4. Fastboot flash a custom recovery
You can follow this guide here: [How-To][Windows] Download and Flash Android 5.0 and Reroot & Recovery (by @spc_hicks09)
Method 3b (You are fully stock 4.4.x)
1. Unlock bootloader if necessary (This wipes data)
2. Accept OTA update
3. Use the CF-Autoroot method to modify the kernel (boot.img) for root (Will not get permissive mode) and SuperSU
4. Fastboot flash a custom recovery
Method 3c (You are fully stock 5.0)
1. Unlock bootloader if necessary (This wipes data)
2. Use the CF-Autoroot method to modify the kernel (boot.img) for root (Will not get permissive mode) and SuperSU
3. Fastboot flash a custom recovery
Section 2, from rooted with custom recovery
Method 4 (You are rooted 4.4.x with custom recovery)
1. Fastboot flash stock 5.0 system.img (this will not wipe data if you still have data at this time, however, you MAY still need to wipe data later)
2. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
3. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
Method 5 (You are rooted 4.4.x with custom recovery)
1. Flash from recovery, an existing packages ROM.zip
2. Flash from recovery, a flashable custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
3. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
You can get a ROM.zip from here: [ROM] [STOCK] Android 5.0 LRX21O - Stock/Flashable (11/12/14) )by @bigxie
Please note, there is no OTA option mentioned here in section 2. This is becuse now, since 5.0 - you MUST be fully stock (recovery included) to accept an OTA update, so the process doesn't really exist
OTA is designed for everyday users. If you're going to be rooted, you should understand what you have and what it means to be rooted. Familiarise yourselves with fastboot. Familiarise yourself with your recovery. Learn how to take backups and you will get much more out of your phone that constantly wasting time returning to stock, applying OTA's then re-rooting. You're wasting time doing this - it's a fools errand. I hope this thread helps to open your eyes and your minds.
If you still want to (return to stock in order to) accept OTA updates, even after reading this thread (perhaps because doing things properly mean more work for you) then perhaps you shouldn't be rooted. Having, maintaining and understanding root takes effort and if you're not willing to put the time in, you will become a danger to your phone and possibly a drain on this forum too We write lots of guides and info threads for your benefit. If you have questions, please just ask.
Please let me know if I have missed anything
This is not a "help me update" thread so please don't post here asking for help with a particular process. Post in the thread for the method you are using. This thread is to discuss which option/method would be best for you.

Do we really need yet another thread on updating and rooting?
Also, permissive boot image is no longer needed on Lollipop.
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Guide on how to retain SuperSU Root permission after flashing Code Blue kernel
How To Retain SuperSU Root Permission with Code Blue Kernel on custom Lollipop ROMs
Not sure how many here have flashed Code Blue kernel on N5X ROM (ver.5.4), but recently I discovered that even though I had Superuser in my Settings menu, my Rooted apps (MyBackup Root, Root Explorer, Wakelock Detector) were not working after I flashed a custom kernel like Code Blue kernel.
After digging through various forum threads, I have managed to make my rooted apps work again on a custom kernel like Code Blue.
Hopefully some of you may find this how to guide helpful.
Pre-requisite
Download the following files to your Nexus 5:-
Permissive Kernel Zip
- https://www.androidfilehost.com/?fid=95747613655048458
Code Blue Kernel for Lollipop
- http://forum.xda-developers.com/google-nexus-5/orig-development/kernel-t2697951
Latest SuperSU by Chainfire (at the time of this post it is [BETA][2014.11.20] SuperSU v2.27)
- http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
- Direct download link: http://download.chainfire.eu/630/SuperSU/BETA-SuperSU-v2.27.zip
Step 1: Reboot to TWRP Custom Recovery
1. Shut off the phone
2. Press and hold Volume Down + Power Button
3. Use Volume down to toggle to Recovery Mode and confirm selection using the Power Button
Step 2: Flash the Permissive Kernel
1. Click on Install button in TWRP Custom Recovery
2. Select the Permissive Kernel Zip file which is N5_+LPX13D_PermissiveKernel.zip
3. Swipe to Confirm Flash
4. Click on the Home button only!
Important Note: Do Not click Reboot System yet!!!
Step 3: Flash the Code Blue Kernel
1. Click on Install button in TWRP Custom Recovery
2. Select the Code Blue Kernel Zip file (at the time of this post is Code_Blue_r620-L_hammerhead.zip)
3. Swipe to Confirm Flash
4. Click on the Home button only!
Important Note: Do Not click Reboot System yet!!!
Step 4: Flash the latest SuperSU
1. Click on Install button in TWRP Custom Recovery
2. Select the SuperSU Zip file (at the time of this post is BETA-SuperSU-v2.27.zip)
3. Swipe to Confirm Flash
4. Now click on Reboot System button and wait for the phone to reboot.
Once the phone boots up, you should have SuperSU appear under the Settings menu.
Try to reinstall your rooted apps again just to make sure they get fresh root permission from SuperSU.

upndwn4par said:
Do we really need yet another thread on updating and rooting?
Click to expand...
Click to collapse
Yes indeed. There is no single place that addresses all the options. Any guide we have just gives one or two methods. This thread serves as a place to direct the hundreds of people asking the same question that drives those of us who frequently assist these users a little bit batty.
upndwn4par said:
l
Also, permissive boot image is no longer needed on Lollipop.
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Then I shall verify the lack of requirement and update accordingly - should I be satisfied. Thanks for bringing it to my attention.

upndwn4par said:
Do we really need yet another thread on updating and rooting?
Also, permissive boot image is no longer needed on Lollipop.
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I was under the impression this wasn't ready for release to the masses just yet?
It's definitely the solution I'm waiting for and happy to enjoy the standard experience until it's approved for the less technical amongst us.

Updated OP to make it feel less like a roll-up thread as that is not what it is intended to be. It's an info thread to allow users to understand what update / root options are available to them in regards to Android 5.0.
This is not a "help me update" thread so please don't post here asking for help with a particular process. Post in the thread for the method you are using. This thread is to discuss which option/method would be best for you.

I appreciate the thread. There is an over abundance of random threads addressing methods. It is nice to have a centrally located one. I haven't jumped on LP just yet, as I am waiting a little while for more development. It is nice to know people are taking the time to collect the options. I am tired of reading over and over about how people failed.
As usual, good post rootSU

wangdaning said:
I appreciate the thread. There is an over abundance of random threads addressing methods. It is nice to have a centrally located one. I haven't jumped on LP just yet, as I am waiting a little while for more development. It is nice to know people are taking the time to collect the options. I am tired of reading over and over about how people failed.
As usual, good post rootSU
Click to expand...
Click to collapse
Thank you kindly.

upndwn4par said:
Do we really need yet another thread on updating and rooting?
Also, permissive boot image is no longer needed on Lollipop.
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
If this is how you have root could you please test something for me
1 - root (mount as rw) on es file explorer
2 - installing better battery stats through app to system
3 - use Terminal Emulator and type su (press enter) type am start (press enter) and does it return with error or lots of options
Sent from my Android 5.0 Nexus 5

Ben36 said:
If this is how you have root could you please test something for me
1 - root (mount as rw) on es file explorer
2 - installing better battery stats through app to system
3 - use Terminal Emulator and type su (press enter) type am start (press enter) and does it return with error or lots of options
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
1) Works
2) Works
3) Haven't found a terminal emulator that works on lollipop. In adb shell I get what looks like a man page in Linux.

This one works - https://play.google.com/store/apps/details?id=jackpal.androidterm
Sent from my Android 5.0 Nexus 5

upndwn4par said:
1) Works
2) Works
3) Haven't found a terminal emulator that works on lollipop. In adb shell I get what looks like a man page in Linux.
Click to expand...
Click to collapse
Ben36 said:
This one works - https://play.google.com/store/apps/details?id=jackpal.androidterm
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
+1 for jackpal.

Ben36 said:
This one works - https://play.google.com/store/apps/details?id=jackpal.androidterm
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
rootSU said:
+1 for jackpal.
Click to expand...
Click to collapse
Been using that one for years. Won't install from Google Play. Same error that a lot of people get on Lollipop.
The one in ROM Toolbox FCs.

upndwn4par said:
Been using that one for years. Won't install from Google Play. Same error that a lot of people get on Lollipop.
The one in ROM Toolbox FCs.
Click to expand...
Click to collapse
Weird... Works fine here. But your error can't be a root issue if it's on actual install of the app from the play store
Sent from my Android 5.0 Nexus 5

upndwn4par said:
Been using that one for years. Won't install from Google Play. Same error that a lot of people get on Lollipop.
The one in ROM Toolbox FCs.
Click to expand...
Click to collapse
Run a logcat. The smart money is on INSTALL_FAILED_DUPLICATE_PERMISSION. I had this when i tried to install quicksearchbox. Turned out
Code:
Package com.google.android.googlequicksearchbox attempting to redeclare permission com.android.launcher3.permission.RECEIVE_LAUNCH_BROADCASTS already owned by com.android.launcher3
Wonder if you find similar

OK I tested the SuperSU 2.27 BETA on stock kernel without permissive boot.img
Most things I tested worked OK. For example, am start displayed man, which I would expect. However, Viper4Android I didn't get working, which is one app we knew previously to require permissive kernel. Also I asked @sykopompos if we still need permissive and he said SELinux is buggy in L so this method is still a bit different (patraphrasing) So although, yes this is an alternative worth mentioning, it doesn't rule out the Permissive option completely.
I will adjust the OP appropriately.

I've always used permissive with pie patch and i have never had any problems like I see others post about
Sent from my Android 5.0 Nexus 5

Ben36 said:
I've always used permissive with pie patch and i have never had any problems like I see others post about
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
I've never needed PIE patch. I thought PIE patch was if you didn't have permissive, but I don't really know a lot about it. I just use permissive

rootSU said:
I've never needed PIE patch. I thought PIE patch was if you didn't have permissive, but I don't really know a lot about it. I just use permissive
Click to expand...
Click to collapse
Es file explorer root access wouldn't work without pie patch even with the permissive kernel
Sent from my Android 5.0 Nexus 5

Ben36 said:
Es file explorer root access wouldn't work without pie patch even with the permissive kernel
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Ah ok. But yeah, bad application

How to install ElementalX Kernel

I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.

The kernel is the boot.img. Just flash it via TWRP and it will automatically be present.

And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...

daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Better flash superSU2.65.zip (latest atm).

Not necessarily better. Versions after 2.62 have a number of comments across various threads saying that root doesn't work for them. 2.62 uses a different method from the later versions. 2.62 works fine for me and (from the silence in the forums) for most people, so upgrading to 2.64/2.65 is probably taking an unnecessary risk.
And again, why try to install a different kernel on a working rooted device? It makes no sense to me unless there's an amazing function that will make a discernable difference, and personally I don't believe that any kernel makes that much of a difference in real-life normal usage.

dahawthorne said:
personally I don't believe that any kernel makes that much of a difference in real-life normal usage.
Click to expand...
Click to collapse
Not something i'd agree with since CPU governors and I/O schedulers can make allot of difference to "real life normal usage", obviously this depends on what the developer impliments and user choice.

there are times that I'll run elementalx kernel, but I ALWAYS change the governor and scheduler. always. as I can't stand the way that its set up. personally, I always use ondemand with deadline :angel:

daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Wondering how you achieved root.I am unable using the stock kernel.TWRP installed just fine.Do you mind sharing your procedure?

Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.

To install elementalx, just flash in recovery.
dahawthorne said:
And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...
Click to expand...
Click to collapse
Silliness. Why are you even on xda with that attitude? He probably wants to install it so he can use some of the added features and enhancements.

"Why are you even on xda with that attitude?" Ditto. We're all entitled to our opinions, and my opinion is that a lot of noobs do stuff just to see what happens, and the result is that they're in forums asking after the event "How do I fix this?" rather than "How do I do this?", and in both cases without any particular need or reason or understanding of what they want. And this is a typical thread - an admitted noob wants to install a specific kernel, and still hasn't said why (though he/she has thanked me, which I appreciate ). I think that to warn noobs about unnecessary tinkering is doing them a service - isn't that why we all respond to questions?

dahawthorne said:
Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.
Click to expand...
Click to collapse
Thanks very much -so to be clear that was with the Stock kernel?
I am running 3.10.40-g557ba38
Trying to avoid a brick situation,sorry to be a bother..

Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.

Awesome thanks again.

dahawthorne said:
Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.
Click to expand...
Click to collapse
Thanks again-this worked out perfectly and I am running Cyanide which has made me very happy so far.REALLY fast and smooth.Everything working great so far.Loving my N6- who needs Samsung! I just had to edit the .xml file for the Music volume other than that the ROM seems about perfect.

Magisk and Bootloader

Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You

Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.

Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?

inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.

1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.

Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.

Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again

I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.

Ok.Thank you very much.I will learn more ...

Questions about TWRP used for current root method

I rooted the e5 plus using this method: https://forum.xda-developers.com/mo...o-e5-plus-rhannah-backup-magisk-root-t3822702
This was different from what I'm used to as normally TWRP replaces the stock recovery and then root is applied. Here, TWRP is only used in fastboot and not applied permanently.
A couple of questions:
Since recovery is not replaced, can this device receive OTA updates with no issues?
Can a normal factory reset be done without soft bricking the device?
If I want to install zip files for mods etc, can I use the fastboot temp TWRP to do this and it will still work?
Are there any actions/caveats that should be done or avoided with this TWRP method?
Excuse my ignorance but I'm sure someone else may have the same question and I'd rather not brick my device.
Thank you.

shezzy83 said:
I rooted the e5 plus using this method: https://forum.xda-developers.com/mo...o-e5-plus-rhannah-backup-magisk-root-t3822702
This was different from what I'm used to as normally TWRP replaces the stock recovery and then root is applied. Here, TWRP is only used in fastboot and not applied permanently.
A couple of questions:
Since recovery is not replaced, can this device receive OTA updates with no issues?
Can a normal factory reset be done without soft bricking the device?
If I want to install zip files for mods etc, can I use the fastboot temp TWRP to do this and it will still work?
Are there any actions/caveats that should be done or avoided with this TWRP method?
Excuse my ignorance but I'm sure someone else may have the same question and I'd rather not brick my device.
Thank you.
Click to expand...
Click to collapse
OTA won't work if rooted, you'll have to flash stock boot or flash full stock ROM.
Flashing twrp causes issues because of avb and dm-verity
TWRP won't have access to data because of encryption and won't be able to write to system.
Basically you're only booting twrp to make a backup and then use Magisk to patch your boot.img for root. From there you can install magisk modules and Xposed as well as any apps you use that need root.
You might use the TWRP installer within Android to install TWRP but it didn't boot for me on my E5 Plus.

reaper-death said:
Basically you're only booting twrp to make a backup and then using Magisk to patch your boot.img for root.
.
Click to expand...
Click to collapse
Ok so that's the answer I was looking for. TWRP is ONLY for backing up in our case since it doesn't have access. Therefore, none of what I asked about will work.

shezzy83 said:
Ok so that's the answer I was looking for. TWRP is ONLY for backing up in our case since it doesn't have access. Therefore, none of what I asked about will work.
Click to expand...
Click to collapse
These Moto e5 + posts have become pointless.
No method works and if root does work it will have issues. The original poster can't fix the issue because they don't know what they are talking about half the time.
We need better people on here who can make a video or explain how to do this without ****ing with our heads ?
Like a person who knows what they are doing with that exact phone model and are not just saying **** for a post ?
Contact me if you need real help fixing these people's mistakes [not root] "fix a bricked phone"!

Question Updating after root

I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.

scuzzo500 said:
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.
Click to expand...
Click to collapse
You can update any way you want. You might find sideloading the OTA to be easiest.
The only way you can "accidentally" brick your device is if you break the bootloader by flashing the wrong image...but if you're not sure what that means, you probably shouldn't be attempting this anyway.

.

I'm pretty familiar with rooting and updating. If you look at my post history you can verify I've been working with root since Droid x2. I'm currently typing this on a one plus 7 pro I converted to gm1925. However, each platform has its specific issues and every new version of Android can be different. I don't have twrp to backup and I want to make sure I don't brick what, to me, is a significant financial investment. I'm just asking to understand what other individuals feel is best practices.

scuzzo500 said:
I'm pretty familiar with rooting and updating. If you look at my post history you can verify I've been working with root since Droid x2. I'm currently typing this on a one plus 7 pro I converted to gm1925. However, each platform has its specific issues and every new version of Android can be different. I don't have twrp to backup and I want to make sure I don't brick what, to me, is a significant financial investment. I'm just asking to understand what other individuals feel is best practices.
Click to expand...
Click to collapse
I personally update using PixelFlasher and the factory image each month. Others prefer sideloading the OTA. Yet others restore the boot image and take automatic OTAs.
It's completely up to you. Again, the only way you'll brick your device is by doing something stupid such as flashing the wrong image to the bootloader partition. As long as the bootloader functions and you can interact with the device via ADB, it's not bricked and is recoverable

V0latyle said:
I personally update using PixelFlasher and the factory image each month. Others prefer sideloading the OTA. Yet others restore the boot image and take automatic OTAs.
It's completely up to you. Again, the only way you'll brick your device is by doing something stupid such as flashing the wrong image to the bootloader partition. As long as the bootloader functions and you can interact with the device via ADB, it's
Click to expand...
Click to collapse

I still haven't put the phone into regular use because I want to make sure I can keep root while updating. I just cannot stand ads. I'll start reading up on pixelflasher and get a good feel for it. Thank you for the help.

I definitely bet on Pixelflasher. It is idiotproof and very handy.

I like sideloading OTA's when I'm stock. A couple commands from any device with current platform tools and it's done. It's also arguably the documented "Google way". Different strokes for different folks I guess...

Thank you to everyone. I've muddled through pixel flasher and I have updated to TD1A.221105.001. Now I'll jump in the pixelflash thread and ask a few questions.

H
scuzzo500 said:
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.
Click to expand...
Click to collapse
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
There is no problem if you install the last update without having installed the previous updates?

alsansan said:
There is no problem if you install the last update without having installed the previous updates?
Click to expand...
Click to collapse
If It's an OTA, i supose there is no problem. If the system gives you the option. Otherwise you can avoid previous justo using flasher. If you keep your init_boot patched It's easy to root again once used the flasher.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
Just followed your instructions and it worked flawlessly. I totally forgot this and figured I would need to reflash each time.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
Followed your steps. It was easy and worked well.
Thank you

scuzzo500 said:
I still haven't put the phone into regular use because I want to make sure I can keep root while updating. I just cannot stand ads. I'll start reading up on pixelflasher and get a good feel for it. Thank you for the help.
Click to expand...
Click to collapse
I don't understand rooting the phone just to block ads.
Just use Adguard which surpasses any root adblocking abilities.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
I thought the problem here was that the patching from magisk doesn't back up the boot_init (Yet). If I recall correctly pixel flasher ensured the backup being there.
That would mean next time the attempt to restore images might fail again. Unless if this issue of magisk has already been addressed. I didn't check.

fivefour said:
I don't understand rooting the phone just to block ads.
Just use Adguard which surpasses any root adblocking abilities.
Click to expand...
Click to collapse
That's because you don't root just to block adds.

oscarcam said:
That's because you don't root just to block adds.
Click to expand...
Click to collapse
I know plenty of other uses of root, I have developed several root apps and maintained various kernels over the years.
Read what I quoted.

I read, but I didn't understand the same. Sorry.