Related
I am ever impatient. So when I saw new factory images up on the Google page, I just had to try them out. I upgraded to LMY47E, then naturally the next day I saw the news about LMY47M. Being that I'm a T-Mobile customer, I want the M version (reported the T-Mobile version) of the new 5.1. Unfortunately, as part of the LMY47E upgrade, the bootloader was moved from 71.05 to 71.08.
Now, trying to flash factory images from LRX22C results in a bootloader mismatch error. I got around this by manually flashing radio, system, boot, etc. images on the phone, and I do in fact now have the 5.01 build showing. However, when I try to sideload the LMY47M build, I'm receiving an error from this line in the updater script:
Code:
#getprop("ro.build.fingerprint") == "google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys" ||
abort("Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
It's stating that I have 5.0.2 LRX22G signed with test keys. I don't know how I would have got an engineering build installed from flashing factory firmware from the Google page, but apparently something is confused somewhere along the way. The best I can guess is that perhaps that's some leftover remnants from when I had installed a CM12 nightly build (which I believe is based on 5.0.2).
I don't know what I need to flash with what to get that cleared so I can sideload the LMY47M OTA, and I'm concerned that I may be unable to properly upgrade to additional OTA upgrades if there's a missmatch along the way. There was a confirmed update coming to move from LMY47E to LMY47M per T-Mo support , also confirmed by @askdes) but again, if I have some funky mismatched stuff, unsure if I can upgrade to LMY47E again and still expect to receive the OTA.
I'd love to have someone with more knowledge of these wonderful things weigh in on this. Educated opinions are always welcome, but someone with actual first-hand knowledge would be incredibly helpful to my sanity as well.
Thanks!
Theres nothing you can do to receive the OTA now.
Maybe the M factory image will become available. If so, you'll be able to flash that. Well at least the system and boot image. If the bootloader is newer, that too.
I suppose the other options are that if someone could install TWRP with an unmodified, unrooted M on, they could take a backup of system and boot and give you them to do a Nandroid restore via TWRP... Or maybe someone can take a system dump for you. But you cannot downgrade the bootloader.
mikecole79 said:
I am ever impatient. So when I saw new factory images up on the Google page, I just had to try them out. I upgraded to LMY47E, then naturally the next day I saw the news about LMY47M. Being that I'm a T-Mobile customer, I want the M version (reported the T-Mobile version) of the new 5.1. Unfortunately, as part of the LMY47E upgrade, the bootloader was moved from 71.05 to 71.08.
Now, trying to flash factory images from LRX22C results in a bootloader mismatch error. I got around this by manually flashing radio, system, boot, etc. images on the phone, and I do in fact now have the 5.01 build showing. However, when I try to sideload the LMY47M build, I'm receiving an error from this line in the updater script:
Code:
#getprop("ro.build.fingerprint") == "google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys" ||
abort("Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
It's stating that I have 5.0.2 LRX22G signed with test keys. I don't know how I would have got an engineering build installed from flashing factory firmware from the Google page, but apparently something is confused somewhere along the way. The best I can guess is that perhaps that's some leftover remnants from when I had installed a CM12 nightly build (which I believe is based on 5.0.2).
I don't know what I need to flash with what to get that cleared so I can sideload the LMY47M OTA, and I'm concerned that I may be unable to properly upgrade to additional OTA upgrades if there's a missmatch along the way. There was a confirmed update coming to move from LMY47E to LMY47M per T-Mo support , also confirmed by @askdes) but again, if I have some funky mismatched stuff, unsure if I can upgrade to LMY47E again and still expect to receive the OTA.
I'd love to have someone with more knowledge of these wonderful things weigh in on this. Educated opinions are always welcome, but someone with actual first-hand knowledge would be incredibly helpful to my sanity as well.
Thanks!
Click to expand...
Click to collapse
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
clairez said:
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
Click to expand...
Click to collapse
Thank you both for the replies. My course at this point seems to be "wait until M is up on the factory images page", which is what I suspected.
I have done a full factory flash of the LRX22C image, manually (since the script fails because of the newer bootloader) and it has still left me with the engineering build stamp showing. Any idea where that information is coming from? The image I used to flash back was the LRX22C for Shamu from developers <dot> google <dot> com/android/nexus/images. I would think that would have wiped the world (exception of the bootloader that doesn't know how to travel back in time; should really introduce that thing to Doc....). I'm not sure if it's because of the bootloader itself, or because of some other thing that just didn't get wiped properly. I flashed the radio, boot, cache, recovery, userdata, and system images initially, then re-flashed recovery to TWRP 2.8 after. Where does ro.build.fingerprint get it's information from? Is that all from the bootloader?
clairez said:
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
Click to expand...
Click to collapse
But you can not flash an older bootloader So far for the developer phone At least HTC has S-Off.
gee2012 said:
But you can not flash an older bootloader So far for the developer phone At least HTC has S-Off.
Click to expand...
Click to collapse
I could be wrong (often am), but I thought several folks tried and succeeded with a factory image flash, by using the following methodology:
1. If your phone is showing OEM Unlock in the developer options and you can boot into recovery, then
2. Boot into android and remove all security
3. Set OEM Unlock and USB debugging
4. Perform several reboots to ensure OEM Unlock is persistent (if not, do not proceed)
5. Perform a factory reset/data wipe in recovery
6. Reflash the 5.01 factory image (or wait for 5.1 M version) using the manual method located here:
[TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader
http://forum.xda-developers.com/nexu...shamu-t2954008
* Use Method 2 from this tutorial, Method 1 does not work
7. You can relock the bootloader as outlined in the tutorial.
8. At this point if all went as expected, the N6 is factory fresh and eligible for the OTA.
But before you proceed check out some of the other posts to ensure that others have succeeded. So many reports of bricked phones it is hard to tell what caused the problem.
I have used the above method several times, but only reflashing to a newer version.
Hope this helps ....
PS: I missed the mention of CM12! There are so many variables in your situation, I am unsure now that there is a way back. So many of the hard bricked cases involved CM12. Good luck, I hope you come out of this right side up!
mikecole79 said:
Thank you both for the replies. My course at this point seems to be "wait until M is up on the factory images page", which is what I suspected.
I have done a full factory flash of the LRX22C image, manually (since the script fails because of the newer bootloader) and it has still left me with the engineering build stamp showing. Any idea where that information is coming from? The image I used to flash back was the LRX22C for Shamu from developers <dot> google <dot> com/android/nexus/images. I would think that would have wiped the world (exception of the bootloader that doesn't know how to travel back in time; should really introduce that thing to Doc....). I'm not sure if it's because of the bootloader itself, or because of some other thing that just didn't get wiped properly. I flashed the radio, boot, cache, recovery, userdata, and system images initially, then re-flashed recovery to TWRP 2.8 after. Where does ro.build.fingerprint get it's information from? Is that all from the bootloader?
Click to expand...
Click to collapse
I am in the same situation as you are, mine shows my build fingerprint as "google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy020120939:eng/test-keys" I have gone through the same steps as you have and tried to reflash LRX22C. I guess we wait until the factory image!
wadsface said:
I am in the same situation as you are, mine shows my build fingerprint as "google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy020120939:eng/test-keys" I have gone through the same steps as you have and tried to reflash LRX22C. I guess we wait until the factory image!
Click to expand...
Click to collapse
Have you flashed a custom kernel? Sounds like a non-google boot.IMG or something is on the device.
clairez said:
4. Perform several reboots to ensure OEM Unlock is persistent (if not, do not proceed)
Click to expand...
Click to collapse
That is absurd.
Unlocked is unlocked is unlocked.
The only thing that may not be persistent is the flag in the dev settings menu, ENABLE oem unlock.
Once you enable the unlock, you may *immediately* try to unlock it. If the enable setting isn't persistent, then it just won't unlock.
ONCE IT IS UNLOCKED, IT IS UNLOCKED. DON'T EVER LOCK IT AGAIN.
I also received that error when trying to sideload the OTA. The only modification I made was using a custom kernel, but I flashed the stock boot.img before attempting to sideload. So I'm not sure what could have caused the error?
I just read somewhere that we can get the sideload to work if a line in the updater script is deleted or modified. Has anyone else read this?
To sideload an OTA you need a stock recovery. I have been unable to sideload an OTA with a custom recovery installed since 5.0. The Dees Troy (guessing TWRP recovery) in the path is a dead giveaway that it is from the recovery. I don't think it is checking bootloader version when sideloading OTA.
android_mp99 said:
TI don't think it is checking bootloader version when sideloading OTA.
Click to expand...
Click to collapse
It is. OTA doesn't replace the bootloader. It patches the existing BL with the deltas - I.e. the code that have changed. Obviously the bootloader must be the exact expected version for a patch to work, so it is definitely being checked when you install an OTA, no matter what method you use..
If you patched the BL with an incorrect patch, you could very easily be facing a brick.
Then I'm guessing the people that were able to sideload the OTA with the new bootloader got lucky or are talking a bunch of BS (totally possible). I haven't tried it myself but I know for sure that the stock recovery is needed to sideload the OTA since 5.0 and the error reported earlier by some could be because of the recovery installed.
You definitely need stock recovery, yes
Since I have never updated my bootloader, I'm inclined to think it must be recovery. I was trying to sideload via TWRP.
doitright said:
[snip]
ONCE IT IS UNLOCKED, IT IS UNLOCKED. DON'T EVER LOCK IT AGAIN.
Click to expand...
Click to collapse
There are many reasons that people want to have a locked bootloader, such as, among many other reasons, your employer requires it, for example.
rootSU said:
It is. OTA doesn't replace the bootloader. It patches the existing BL with the deltas - I.e. the code that have changed. Obviously the bootloader must be the exact expected version for a patch to work, so it is definitely being checked when you install an OTA, no matter what method you use..
If you patched the BL with an incorrect patch, you could very easily be facing a brick.
Click to expand...
Click to collapse
No, OTA updates do not verify which bootloader your device is running, and they do NOT patch the bootloader -- they fully replace it.
android_mp99 said:
Then I'm guessing the people that were able to sideload the OTA with the new bootloader got lucky or are talking a bunch of BS (totally possible). I haven't tried it myself but I know for sure that the stock recovery is needed to sideload the OTA since 5.0 and the error reported earlier by some could be because of the recovery installed.
Click to expand...
Click to collapse
rootSU said:
You definitely need stock recovery, yes
Click to expand...
Click to collapse
You can use TWRP as well. It just requires an edit to one line in the updater-script file.
efrant said:
There are many reasons that people want to have a locked bootloader, such as, among many other reasons, your employer requires it, for example.
No, OTA updates do not verify which bootloader your device is running, and they do NOT patch the bootloader -- they fully replace it.
Click to expand...
Click to collapse
Yes you're right, my mistake.
efrant said:
You can use TWRP as well. It just requires an edit to one line in the updater-script file.
Click to expand...
Click to collapse
You need to have stock recovery to apply a stock ota. You could edit the updater-script for any amount of purposes, but that isn't really the point. The people who simply want to "check for updates" and use the standard mechanism to apply it, it will not work with twrp.
rootSU said:
You need to have stock recovery to apply a stock ota. You could edit the updater-script for any amount of purposes, but that isn't really the point. The people who simply want to "check for updates" and use the standard mechanism to apply it, it will not work with twrp.
Click to expand...
Click to collapse
Yeah, ok, but we were talking about sideloading the OTA, no? You can sideload an OTA update file (or even flash it directly from your device) using TWRP just by editing one line. But yes, as far as clicking on "check for updates" and having it install that way requires the stock recovery.
efrant said:
Yeah, ok, but we were talking about sideloading the OTA, no? You can sideload an OTA update file (or even flash it directly from your device) using TWRP just by editing one line. But yes, as far as clicking on "check for updates" and having it install that way requires the stock recovery.
Click to expand...
Click to collapse
You technically can. But then you edit the line, side load the ota via twrp, and immediately flash SuperSU to stop the updated system image from replacing the recovery.. It all seems a little pointless to me. If you're going to modify an ota (or download a modified ota) to side load from custom recovery rather than use a pre-rooted ROM.zip, it seems to add unnecessary steps.
Is it okay to flash the newest image (LMY74I) coming from LMY47O? I won't do any harm in skipping 5.0.1 will I?
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
mymusicathome said:
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
Click to expand...
Click to collapse
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Forerunner326 said:
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Click to expand...
Click to collapse
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
rootSU said:
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
Click to expand...
Click to collapse
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Forerunner326 said:
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Click to expand...
Click to collapse
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Is this because oem unlocking was unchecked for those people?
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Even if the device is rooted, all it will do is cause root to be lost correct?
Forerunner326 said:
Is this because oem unlocking was unchecked for those people?
Click to expand...
Click to collapse
See this post on relocking instructions:
http://forum.xda-developers.com/showthread.php?p=59699095
Forerunner326 said:
Even if the device is rooted, all it will do is cause root to be lost correct?
Click to expand...
Click to collapse
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
rootSU said:
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
Click to expand...
Click to collapse
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
theDXT said:
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
Click to expand...
Click to collapse
Flash everything from the factory image except the userdata.img
I recently unrooted my Moto X 1053 DevEd (GSM) in order to accept the Lollipop 5.1 OTA. I got the update and it's working great.
Now I want to re-root my phone, but first I want to be sure that I have a copy of stock recovery.img for Lollipop 5.1.
How can I back up recovery.img from my phone without my phone being rooted?
Thanks!
is temp booting custom recovery still possible... I haven't messed around with stuff in a while, but I think if you can temp boot twrp recovery (fastboot boot twrp) you might be able to use it to back up the stock recovery... you should google for more info on that, make sure it doesn't flash instead of boot.
otherwise you can't backup stock recovery without root. it's kind of a catch 22: you want to back up stock recovery before you root, but you can't do that on the device without root.
normally you can get the recovery from the stock firmware zip file. but I don't think Motorola is handing them out for 5.1 yet - if they are then it will be in that file. if not I suppose the next best thing is to rummage through the OTA file. I haven't unzipped it myself but it has to be in there right? some info that might help: the recovery size is 10mb. I can see it with the DiskInfo app, along with its block partition name mmcblk0p34, although it probably won't be named that in the zip file idk... anyway you can find the OTA here: https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
That is a really, really helpful post, dtg7. I had hoped Moto would have posted the firmware, but I guess I'm too impatient. As I didn't have a separate copy of the OTA, I'm doing as you suggested and grabbing the OTA from the site you linked to. I'll try to extract the recovery.img file from there. I'll post my results.
Yes, this is a classic catch 22, as you say.
dtg7 said:
I haven't messed around with stuff in a while,...
Click to expand...
Click to collapse
This is precisely my problem. I get semi-proficient with phone stuff every now and then when I'm changing things around, but then I forget almost everything I need to know to do the most basic geek maneuvers. When I had an HTC Sensation, which was a favorite for ROM-makers and modders, I was swapping out the ROM nearly every day between meals. With the Moto X I haven't done this much, maybe because I've gotten older, but mainly because there don't seem to be as many custom ROMs for the Moto X (nor is as much need for them, with Xposed and with a decent stock ROM.
dtg7 said:
anyway you can find the OTA here: https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
Click to expand...
Click to collapse
Isn't that a link to KitKat 4.4.4 (i.e., 213.44.1)?
I've got Lollipop 5.1 on my phone, and "About Phone" lists it as 222.21.15.
It's actually system.img from 222.21.15 that I'm trying to get ahold of.
varxx said:
Isn't that a link to KitKat 4.4.4 (i.e., 213.44.1)?
I've got Lollipop 5.1 on my phone, and "About Phone" lists it as 222.21.15.
It's actually system.img from 222.21.15 that I'm trying to get ahold of.
Click to expand...
Click to collapse
Or is this still the case (quoted from elsewhere on this site)?
file name ... references the build your phone must be on to accept the update, not the version of the update itself. That is how Moto has done it for some time now.
Click to expand...
Click to collapse
varxx said:
Or is this still the case (quoted from elsewhere on this site)?
Click to expand...
Click to collapse
yes that is still the case, moto otas refer to the android version you're updating From
that file is what I used to update from 4.4.4 to lollipop
dtg7 said:
yes that is still the case, moto otas refer to the android version you're updating From
that file is what I used to update from 4.4.4 to lollipop
Click to expand...
Click to collapse
Thanks for clarifying this.
varxx said:
Thanks for clarifying this.
Click to expand...
Click to collapse
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
AaronCompNetSys said:
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
Click to expand...
Click to collapse
I can't find recovery.img in the uncompressed file dtg7 kindly linked above:
https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
Maybe I didn't look hard enough.
I *did* find the 4.4.4 recovery.img in the uncompressed file I requested and received from Moto. It seems like Moto sometimes uses the same recovery.img from release to release, but I'd be skittish about using this with stock 5.1 until someone can give it the all-clear. As of right now (27 june 15, 9:00 GMT), Moto hasn't posted stock 5.1.
AaronCompNetSys said:
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
Click to expand...
Click to collapse
varxx said:
As of right now (27 june 15, 9:00 GMT), Moto hasn't posted stock 5.1.
Click to expand...
Click to collapse
Looks like the stock XT1053 5.1 firmware is available now. See the links here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
dtg7 said:
Looks like the stock XT1053 5.1 firmware is available now. See the links here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Click to expand...
Click to collapse
Thanks! I'm not sure if I want to try flashing just the recovery or not, I've been having lots lof radio active time so I migh full wipe/flash to try to clear that up.
Here is just the recovery from the "tmo_retail_xt1053_5.1_lpa23.12-15.222.21.15.ghost_row.retail.en.us.tgz" file:
https://mega.co.nz/#!WU5WjaqL!109FXTQovfywRxJM67YBH5KHrErNZYILPVyzk4HGK-c
varxx said:
I recently unrooted my Moto X 1053 DevEd (GSM) in order to accept the Lollipop 5.1 OTA. I got the update and it's working great.
Now I want to re-root my phone, but first I want to be sure that I have a copy of stock recovery.img for Lollipop 5.1.
How can I back up recovery.img from my phone without my phone being rooted?
Thanks!
Click to expand...
Click to collapse
I'm having difficulty figuring out how to approach the update. I'm on the XT1095 running 22.21.11.victara_tmo.tmo.en.US, TWRP, and root. The only guides I've seen are supposed to update from 23.11.14.
Is the file here the right file? How do I return to stock properly?
wiiareonfire said:
I'm having difficulty figuring out how to approach the update. I'm on the XT1095 running 22.21.11.victara_tmo.tmo.en.US, TWRP, and root. The only guides I've seen are supposed to update from 23.11.14.
Is the file here the right file? How do I return to stock properly?
Click to expand...
Click to collapse
Yes, on that page download the full 5.0 factory image. Then flash it to your phone. After that you will be on stock, unrooted, and factory recovery and can take the OTA. The OTA should appear when you look for updates on your phone after that, no need to sideload, well unless you want to, lol.
Sent from my XT1095 using Tapatalk
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted
cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.
evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.