*The below post covers up to 4.4.4 only. for 5.0, read this thread: http://forum.xda-developers.com/goo...asic-overview-root-options-lollipop-t2947144*
{
"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 see a lot of threads asking about updating to Lollipop and about returning to stock to receive OTA updates.. from rooted users.
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, noob 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"?
It all depends what you want to keep going forward.
I don't want root or custom recovery
If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:
- boot.img
- recovery.img
- bootloader.img
- system.img
- cache.img
- userdata.img
- radio.img
It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.
If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located
I want to keep root
You have a couple options here.
You could like above, fastboot flash individually the system.img and boot.img (not recovery.img) then reflash supersu from your custom recovery. Please note, with lollipop as of now, you need as special modified boot.img, not the stock one - so this still is not the quickest method.
Alternatively, you can flash a pre-rooted zip*. Within a couple of hours of the factory image becoming available, guys from XDA will release pre-rooted zips that you simply flash from a custom recovery. This will be a quick process. Put the zip on your /sdcard, boot into recovery and flash it.
With both these options, you very well may need to factory reset after flashing roms, especially if it's a version jump - just as you may need to do with an OTA update. The benefit of being rooted however, is that you can use titanium backup to backup your apps and take a Nandroid backup too, rooted users upgrading should keep these available on the sdcard before updating.
*Please note with Android 5.0 Lollipop, you need to flash a ROM.zip, Permissive kernel and SuperSU all at once. You have to download all 3 files and flash them one after the other in that order. You can flash some custom kernels, such as elementalx straight over permissive kernel. Also, you can ONLY flash elementalX as it allows root to run at boot (without permissive kernel) however, some apps NEED permissive to run anyway
OTA is designed for noobs. Granted, those root users asking how to return to stock or thinking OTA is the only update method available - are also noobs... 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.
adb and fastboot. What is it? How can it help you? - basic information about adb and fastboot (by @rootSU)
All you need to know about Android | Read this before you post/root ! - Understand the basics before you root (by @abaaaabbbb63 )
How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5 - Understand how to undo whatever you do before you root (by @abaaaabbbb63 )
OTA Help-Desk - Understand how OTA's work and what this means if you are rooted (by @Sandman-007)
Always informative Mr. RootSU
stankyou said:
Always informative Mr. RootSU
Click to expand...
Click to collapse
Thanks. I try
Thanks for this - I am rooted and have a basic knowledge of fastboot from unlocking and rooting the N5 last year and the N4 before that.. however, as I've not touched it for about that long it's probably about time I start the reading process again to get ready for some Lollipop action!
I had been planning on getting the factory images from Google and using fastboot to fresh flash it - looks like that's not really necessary tho?
Thanks
...sent from the Nexus 5000
I still remember rocking your dGB ROM during the Desire days. LOL
but my rooted and modified nexus 5 did receive an ota.. can i or should i apply it? or my rooted and unmodified nexus 5 did receive an ota.. can you decribe to me what would happen if i do apply it?
Thanks for this, really informative.
simms22 said:
but my rooted and modified nexus 5 did receive an ota.. can i or should i apply it? or my rooted and unmodified nexus 5 did receive an ota.. can you decribe to me what would happen if i do apply it?
Click to expand...
Click to collapse
Ooh good point. I'll mention that.
androidsnax said:
Thanks for this - I am rooted and have a basic knowledge of fastboot from unlocking and rooting the N5 last year and the N4 before that.. however, as I've not touched it for about that long it's probably about time I start the reading process again to get ready for some Lollipop action!
I had been planning on getting the factory images from Google and using fastboot to fresh flash it - looks like that's not really necessary tho?
Thanks
...sent from the Nexus 5000
Click to expand...
Click to collapse
If you want to keep root, The best thing to do would be to wait for a pre-rooted rom.zip - which should also contain the custom boot.img needed to give root permissions...
Just make sure you do all your backups first if you want to keep stuff.
Oh and if anyone has any suggestions for things I should include in the OP, please let me know.
rootSU said:
I see a lot of threads asking about updating to Lollipop and about returning to stock to receive OTA updates.. from rooted users.
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 background
OTA's are simple for unrooted, noob 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
Why shouldn't rooted users apply OTA's if they can?
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"?
So what are the actual options?
It all depends what you want to keep going forward.
I don't want root or custom recovery
If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:
- boot.img
- recovery.img
- bootloader.img
- system.img
- cache.img
- userdata.img
- radio.img
It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.
If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located
I want to keep root
You have a couple options here.
You could like above, fastboot flash individually the system.img and boot.img (not recovery.img) then reflash supersu from your custom recovery. Please note, with lollipop as of now, you need as special modified boot.img, not the stock one - so this still is not the quickest method.
Alternatively, you can flash a pre-rooted zip. Within a couple of hours of the factory image becoming available, guys from XDA will release pre-rooted zips that you simply flash from a custom recovery. This will be a quick process. Put the zip on your /sdcard, boot into recovery and flash it.
With both these options, you very well may need to factory reset after flashing roms, especially if it's a version jump - just as you may need to do with an OTA update. The benefit of being rooted however, is that you can use titanium backup to backup your apps and take a Nandroid backup too, rooted users upgrading should keep these available on the sdcard before updating.
Conclusion
OTA is designed for noobs. Granted, those root users asking how to return to stock or thinking OTA is the only update method available - are also noobs... 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.
useful links
adb and fastboot. What is it? How can it help you? - basic information about adb and fastboot (by @rootSU)
All you need to know about Android | Read this before you post/root ! - Understand the basics before you root (by @abaaaabbbb63 )
How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5 - Understand how to undo whatever you do before you root (by @abaaaabbbb63 )
OTA Help-Desk - Understand how OTA's work and what this means if you are rooted (by @Sandman-007)
Click to expand...
Click to collapse
Seems like we've gone with what I previously said about people who want OTAs while rooted
You should also add that if one STILL wants to take OTAs for some silly reason, even after reading this thread, he/she should stay away from root access completely and use their phone like any other unknowledgable/ignorant person would, like someone that OTAs were meant for. :angel:
Lethargy said:
Seems like we've gone with what I previously said about people who want OTAs while rooted
You should also add that if one STILL wants to take OTAs for some silly reason, even after reading this thread, he/she should stay away from root access completely and use their phone like any other unknowledgable/ignorant person would, like someone that OTAs were meant for. :angel:
Click to expand...
Click to collapse
Yep
Well said, sir. Nice work.
stankyou said:
I still remember rocking your dGB ROM during the Desire days. LOL
Click to expand...
Click to collapse
Ha. Oh wow.
Thank you so much.
Nice information thx
rootSU said:
Oh and if anyone has any suggestions for things I should include in the OP, please let me know.
Click to expand...
Click to collapse
Probably goes without saying but a link to a pre-rooted ROM where you mention this option would be great. When available of course.
Only because finding a stock pre-rooted ROM at times like these can be a task even for vets. Having it right there would be very useful for those peaking in on this already informative thread.
Thanks
tgrgrd00 said:
Probably goes without saying but a link to a pre-rooted ROM where you mention this option would be great. When available of course.
Only because finding a stock pre-rooted ROM at times like these can be a task even for vets. Having it right there would be very useful for those peaking in on this already informative thread.
Thanks
Click to expand...
Click to collapse
na, very easy. basic aosp/stock rooted roms(these are what you want) will be in the android development section of the nexus 5. always. in the original development section, there will be original roms only.
rootSU said:
If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:
- boot.img
- recovery.img
- bootloader.img
- system.img
- cache.img
- userdata.img
- radio.img
It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.
If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located @Sandman-007)
Click to expand...
Click to collapse
Also, you can edit flash-all.bat and find entry:
Code:
nulfastboot -w update image-hammerhead-ktu84p.zip
and remove "-w" and save it. Then just execute flash-all.bat and the script will flash all the images without wiping data. I always do that way and never had data wiped.
Nice advices once again and I totally agree with OTA subject.
I used Lollipop a few days then I went back to KK and I do not plan to update soon. Since I didn't follow recent discussions about Lollipop I have a question: flashing a rooted flashable zip won't be a mess? e.g unavailable /sdcard, a 32Gb storage that becomes 16Gb (actually that's what I had - clean flash of course)... Lollipop is really different compared to KK so would it not be more appropriate to flash the factory imgs (without restoring user data from KK) before enjoying Lollipop's stuff?
Related
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
I have been rooting, unlocking, and loading Roms on other devices for awhile now, but I'm not familiar with how to manage stock updates. I can't seem to find anything, (so maybe this info could be added to a sticky).
I'm rooted with TWRP and a zipped OTA has been posted in anothet thread for my device, XT1064. What can I do to load it? Do I need to flash back to stock first? Can I simply run a fastboot command? I feel like I should know this by now but I'm a bit confused by all the different sources of information.
Thanks, all, for your help.
I have the same question. If someone who has done this, is out there, please let us know.
you tried asked in that other thread???
If is the OTA update do not use it!!!
If you received the OTA on your phone do not update!!!
you will brick your phone.
To install OTA revert back to stock with the factory image. You will go back to Stock Kernel and recovery.
Or wait til someone builds a stock updated ROM and flash that.
If is a image of the ROM, not the OTA, a already updated ROM just follow the instructions on the thread...
Yes, I did ask in the other thread, but I thought it would be better to post a new Q&A thread to keep from cluttering up the other one. Thanks for your help. I'll just wait for a flashable ROM..
Try this method:
http://forum.xda-developers.com/moto-g-2014/help/guide-update-to-lollipop-losing-apps-t2979971
The main idea with OTA is the incremental nature of the update. To keep OTA filesize to a minimum, the system will be patched, not completely overwritten.
So, if you have altered your system in any way, OTA will fail, because it tries to patch files that differ from what it expects. The OTA will check which device it is executed on and will perform various checksum tests before actually installing itself.
If you are experienced with flashing and know how to modify the update-script inside the OTA.zip, then you can go from XT1068-4.4 to XT1064-5.0.1.
But it is quite a lengthy process and not easy nor recommended
You have to go from XT1068-4.4 to XT1064-4.4 to 5.0 to 5.0.1 and must restore the modem. Last but not least the build.prob has to be modified to reflect dual-sim capability.
By the way, the need to lock the bootloader for OTA is a myth. It is not necessary.
Here you can download OTA, fresh firmware or system image to update your device.
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
firmware.zip only [19.6 MB]
2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip [TWRP] [1.15 GB]
Downloads: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer. Don't know, what's that. Looks like a hash or a signature.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed). If you want just firmware, take it. Should be fastboot flashable.
*Additional notes*
Next lines describe my experience before I returned the device state to nearly stock.
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
city2026 said:
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
Download: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed).
*Additional notes*
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
Click to expand...
Click to collapse
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
TWRP system backup added
csoulr666 said:
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
Click to expand...
Click to collapse
I tried to update from recent backup (the one before I changed kernel and deleted system apps), but facebook.odex didn't let me.
Finally, the very first backup did it. I took only system and boot, switched twrp recovery to htc, skipped all setup and installed OTA over fresh system.
Here you go. Now you have TWRP image of this update.
BTW, kernel version is different. CL build number is the same.
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
ash0r said:
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
Click to expand...
Click to collapse
Unfortunately you cannot flash this with TWRP.
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
ash0r said:
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
Click to expand...
Click to collapse
You can try to restore the TWRP backup in the post. And yes, you will lose every mod since it is a backup of the stock, unrooted firmware.
The main problem of flashing the OTA zip would be that you will have to relock the bootloader before installing . So if you unlock it again, the internal storage will be wiped. The best way is to backup everything(Including the internal storage) and then proceed.
Actually, you can save your data while upgrading from non-worthy stock.
So, you may do this
Full backup, you never know what can go wrong.
Save or make a note of what you changed by yourself in system (from busybox to xposed & various modes.). You may use TB for sys-apps and simple file copying for modes. *
Restore updated system image from 1st post, so you have updated system.
See if it worked out and restore/reinstall your other system stuff.
* Remember, you still may access files of your twrp backup images through some archiver. Like I do using 7-Zip.
It's very important to save backup somewhere, cause it might be that my image can be not absolutely clean or can be not absolute right for your phone (like sell location difference). So it'll be easy to return back to working machine.
For this purposes I also setted up my TB for daily auto-backup of texts and settings and weekly backup of apps.
---
Don't sure about relock for upgrading. It seems to be launching, but it needs pure system and original boot & recovery. Some fastboot-magic helps here. That's how I did it after restoring to the very first backup.
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
The Watergod said:
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
Click to expand...
Click to collapse
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
keninzeg said:
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
Click to expand...
Click to collapse
Did you buy your phone from a carrier? Carrier phones get different software updates
csoulr666 said:
Did you buy your phone from a carrier? Carrier phones get different software updates
Click to expand...
Click to collapse
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
keninzeg said:
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
Click to expand...
Click to collapse
If it has EE applications then it is an EE branded phone. Your updates will arrive differently and will have a different software number. So using the Europe zip will not help.
city2026 said:
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
Click to expand...
Click to collapse
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
The Watergod said:
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
Click to expand...
Click to collapse
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
city2026 said:
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
Click to expand...
Click to collapse
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Simply flash custom kernel: like liberty sense or stock sense w/ dt2w.
It will unlock the opportunity to write on every partition. I mean system, cache, etc.
The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Hi
I will assume you have the virus I have been seeing lately that wouldn't allow you to reset the phone, where in reset option the automatic restore option remains checked and you can't uncheck it.
The only solution is through TWRP, you need to enter TWRP, erase Cache, Data, System then flash the Lollipop ROM again or stock from here: http://forum.xda-developers.com/one...one-mini-2-t3250020/post63859743#post63859743
So there is no Rom available that's pretty much stock without bloatware that I can install with twrp? If not is there some idiots guide to putting my stock recovery back on thank you all again
Nexus 6 Rooted and Unlocked and now new OTA – confused
Dear Friends,
I am currently having Nexus 6 with Build Number MRA58N which is rooted unlocked. Last time I had to format Nexus 6 just to update to this build. The nexus toolkit was somehow not working for me.
Now I see again that there is an OTA called android 6.0.1
image hosting
Now I tried using Wugfresh Toolkit first to take android backup but it fails and shows as shown in screenshot that currently there is no modified boot.img available for MRA58N.
free photo upload
I really don’t want to flash factory image bcz it will overwrite everything and erase all.
Kindly help.
Reformatting and again restoring is too much of pain.
Google is your friend, you should Google something like that before creating a post, but anyway you can't take an Ota on a rooted device, if you want the Ota, flash system.img of the current rom, and then take the Ota
I did try and read many posts but still could not conclude anything for sure. Yes I agree OTA cannot be taken on rooted device and thats why my question. you suggested flashing system.img of current rom. Now thats where confusion starts as many posts mention that one needs to be 100percent stock. Many people recommended complete wipe and yet many posed lot of questions because of marshmallow special kernel rom issues which is beyond my technical understanding.
Hence I summarized to pose my query to get considered opinion and guidance. Your response is helpful but am not able to fully comprehend.
Hence request for more guidance.
Really appreciate if some experts would kindly reply to my query and guide me. It will be very helpful as I really want to update but really scared of messing up. Kindly respond.
http://www.droidviews.com/how-to-install-ota-updates-on-rooted-nexus-6/
also watch a few youtube vid's - it is a road well traveled.
i.e.
- Flash the system image for build that you are currently running.
- sideload the update
be patient and don't even think of interrupting the process.
Read the stickies and learn something, toolkits and no skills spell disaster.
Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit.
Now i am stuck at this ADB step. Kindly help Pls.
upload an image
image hosting site over 5mb
Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit. Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit.
Now i am stuck at this ADB step. Kindly help Pls.
upload an image
image hosting site over 5mb
Now i am stuck at this ADB step. Kindly help Pls.
Something got messed up in the process. You can try to individually flash your corresponding boot.img from your version via fastboot. You can download and extract that boot.img from Google's stock images.
This is just me speaking my mind but why people go through the trouble to root just to keep the stock ROM is beyond me.
Given your situation you are better off wiping/formatting and reflashing a new ROM stock (hopefully not) or custom.
Offering this as a comment, not an answer. I agree with mikeprius - in your position I would bite the bullet, download the latest MMB29K image, and run flash-all to wipe and set your device to the newest version - or perhaps even wait for the one which may arrive within a few days. If you leave the device on stock, unrooted, you'll be able to apply OTAs without any problem at all.
For curiosity, why do you even need root? As you've discovered, it opens up cans of worms that can be more trouble than they're worth unless there's an *overwhelming* necessity for root.
looks like failed with verification of /boot
reflash these for build you are currently on - I've done this without losing data:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
fastboot reboot-bootloader
it''ll probably pop up with the dead android -- don't reboot. Press
power button+vol up
you may have have to do a bunch of times -- eventually it go to the menu to allow you sideload the update.
Why are people so fixated on installing an old ROM and then sideloading the update when the obvious answer is to simply install the components of the latest ROM? I get the desire to retain the existing data, but to my eyes it looks as if the phone is now in an unstable and unreliable state and a complete refresh is the best solution.
it's a choice and there is experience gained in the exercise - and the existing data thing is big deal to many.
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 ...