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
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.
*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
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.
Last edited:
