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
Related
I'm returning my phone to stock and wish to flash the stock 4.4.4 recovery back over TWRP. As 4.4.4 firmware has not been officially posted anywhere, is there any way someone can provide a means of flashing it back? And if that isn't possible, is it safe to flash 4.4.2 stock recovery only?
Thanks for the help.
DJMaj07 said:
I'm returning my phone to stock and wish to flash the stock 4.4.4 recovery back over TWRP. As 4.4.4 firmware has not been officially posted anywhere, is there any way someone can provide a means of flashing it back? And if that isn't possible, is it safe to flash 4.4.2 stock recovery only?
Thanks for the help.
Click to expand...
Click to collapse
This makes no sense.
To get back to where you were you can,
1) restore your last twrp backup. That is what twrp is for. If you never made one, Someone could post one, system & boot only.
Recovery has nothing to do with it. The full fxz/XML 444 is what you need.
If you Rsd the 442 XML in order to "reOTA" you risk a brick.
aviwdoowks said:
This makes no sense.
To get back to where you were you can,
1) restore your last twrp backup. That is what twrp is for. If you never made one, Someone could post one, system & boot only.
Recovery has nothing to do with it. The full fxz/XML 444 is what you need.
If you Rsd the 442 XML in order to "reOTA" you risk a brick.
Click to expand...
Click to collapse
Let me explain. I unlocked my bootloader and flashed TWRP. I am currently running stock unrooted 4.4.4 with TWRP. I want to return to the stock recovery, and then relock the bootloader. Obviously a TWRP backup won't help here.
Philz has a built in custom ROM creation feature to do this very thing. You can flash Philz from twrp then reboot recovery. Be sure to wipe cache & dalvik but not data. Then flash the custom ROM that some kind reader may post. Or twrp restore the system & boot, same thing.
DJMaj07 said:
Let me explain. I unlocked my bootloader and flashed TWRP. I am currently running stock unrooted 4.4.4 with TWRP. I want to return to the stock recovery, and then relock the bootloader. Obviously a TWRP backup won't help here.
Click to expand...
Click to collapse
Why would you re-lock the bootloader? Ever?
You realize that you can NEVER get rid of the "Warning: Unlocked Bootloader" message, right? Re-locked BLs **STILL** display that message. There is no way to EVER get back to "Locked" status. No way to ever get rid of the Unlocked boot message (other than flashing a new logo.bin, but you can only do that if UNlocked).
We just don't understand why you would want to do that...? If you are selling it, why not just sell it as unlocked? Your buyer will still see the "warning" message regardless....
DJMaj07 said:
Let me explain. I unlocked my bootloader and flashed TWRP. I am currently running stock unrooted 4.4.4 with TWRP. I want to return to the stock recovery, and then relock the bootloader. Obviously a TWRP backup won't help here.
Click to expand...
Click to collapse
Sorry
The 442 stock recovery should work, pull it from the XML. Use Rashr tools to flash. Then superSU to hide root/unroot
Then you have as close to a locked phone as possible. The bootloader screen will still show your unlock status though.
samwathegreat said:
Why would you re-lock the bootloader? Ever?
You realize that you can NEVER get rid of the "Warning: Unlocked Bootloader" message, right? Re-locked BLs **STILL** display that message. There is no way to EVER get back to "Locked" status. No way to ever get rid of the Unlocked boot message (other than flashing a new logo.bin, but you can only do that if UNlocked).
We just don't understand why you would want to do that...? If you are selling it, why not just sell it as unlocked? Your buyer will still see the "warning" message regardless....
Click to expand...
Click to collapse
The relocking of the bootloader isn't really the priority, I mainly just want to get the stock recovery back to prevent issues with accepting OTAs in the future. This was never about making that message go away. That's why I focused on the "getting back to stock recovery" part in the OP
aviwdoowks said:
Sorry
The 442 stock recovery should work, pull it from the XML. Use Rashr tools to flash. Then superSU to hide root/unroot
Then you have as close to a locked phone as possible. The bootloader screen will still show your unlock status though.
Click to expand...
Click to collapse
That would be great if 4.4.2 recovery was safe. Could I just use fastboot to flash the recovery and relock the bootloader?
DJMaj07 said:
The relocking of the bootloader isn't really the priority, I mainly just want to get the stock recovery back to prevent issues with accepting OTAs in the future. This was never about making that message go away. That's why I focused on the "getting back to stock recovery" part in the OP
Click to expand...
Click to collapse
I see,
To make sure your system is ota ready you will need to pull the STK recovery from the 444 XML when it comes but the 442 one may have the same md5 anyway
---------- Post added at 08:05 PM ---------- Previous post was at 07:58 PM ----------
DJMaj07 said:
That would be great if 4.4.2 recovery was safe. Could I just use fastboot to flash the recovery and relock the bootloader?
Click to expand...
Click to collapse
When you do get ready to flash the 442 recovery post the md5 & also ask others to post there md5 for their 444 recovery. Maybe someone saved their recovery from 444.
DJMaj07 said:
The relocking of the bootloader isn't really the priority, I mainly just want to get the stock recovery back to prevent issues with accepting OTAs in the future. This was never about making that message go away. That's why I focused on the "getting back to stock recovery" part in the OP
Click to expand...
Click to collapse
Bootloader status has no effect on OTAs whatsoever. Why relock the bootloader at all?
So does anyone know where to find this stock recovery?
Updating from 5.0 to 5.0.1 I got a message that said "error" during the reboot and install phase. I had to manually shut down the phone and reboot. After the reboot, I noticed that there was no update available and my phone is still on 5.0. I've only unlocked the bootloader and does with CF. No custom recovery or rom.
Sent from my Nexus 6 using XDA Free mobile app
You used CF so if you rooted it wont work.
As stated in the other threads, you cannot update if you have root. You need to unroot. The update notification will eventually pop up again,
Hand76 said:
You used CF so if you rooted it wont work.
Click to expand...
Click to collapse
PaisanNYC said:
As stated in the other threads, you cannot update if you have root. You need to unroot. The update notification will eventually pop up again,
Click to expand...
Click to collapse
Ah okay I didn't realize that. Thanks for the info!
Sent from my Nexus 6 using XDA Free mobile app
I'm not rooted, I just have decrypted and I get the error.
Aston Martin said:
I'm not rooted, I just have decrypted and I get the error.
Click to expand...
Click to collapse
Same issue - any change to the kernel or system files is going to cause this issue. You need to be completely stock (having the bootloader unlocked is not an issue)
n00b question: I have mine unlocked and rooted; how should I go about getting this update?
TheLegendary87 said:
n00b question: I have mine unlocked and rooted; how should I go about getting this update?
Click to expand...
Click to collapse
Unroot relock boot loader which will while everything again and apply update
ryuken11221 said:
Unroot relock boot loader which will while everything again and apply update
Click to expand...
Click to collapse
Did you mean "...which will wipe everything again..." ? If so, that's really not what I wanted to hear, haha.
TheLegendary87 said:
Did you mean "...which will wipe everything again..." ? If so, that's really not what I wanted to hear, haha.
Click to expand...
Click to collapse
yeah lol i know its hard to hear
ryuken11221 said:
yeah lol i know its hard to hear
Click to expand...
Click to collapse
Found this thread which walks you through the update process without having to wipe your data. Worked perfectly.
TheLegendary87 said:
n00b question: I have mine unlocked and rooted; how should I go about getting this update?
Click to expand...
Click to collapse
You need to get stock before taking any OTA (bootloader being unlocked doesn't cause any issues with update). You can either download factory images for 5.0 and flash those (skip userdata.img if you don't want to lose data), and then take OTA, OR, do it the easier way - download factory images for 5.0.1 and flash those (skip userdata.img to avoid losing data)
ryuken11221 said:
Unroot relock boot loader which will while everything again and apply update
Click to expand...
Click to collapse
huh? why relock bootloader? And that's not going to fix the issue with the modified system files
jj14 said:
You need to get stock before taking any OTA (bootloader being unlocked doesn't cause any issues with update). You can either download factory images for 5.0 and flash those (skip userdata.img if you don't want to lose data), and then take OTA, OR, do it the easier way - download factory images for 5.0.1 and flash those (skip userdata.img to avoid losing data)
Click to expand...
Click to collapse
Exactly what I did following the guidence in this thread: http://forum.xda-developers.com/nexus-6/help/help-5-01-wipe-t2970924
I have unlocked bootloader, flashed Custom Recovery TWRP to my Moto G2 XT1068 and rooted on 4.4.4 stock, while waiting for the official lollipop updates.
So does this break the OTA, and if so how to enable it again?!
Yes you don't get official Lollipop OTA if you unlock your bootloader. For getting official OTA you have to unroot ur phone and relock the bootloader
sumit227 said:
Yes you don't get official Lollipop OTA if you unlock your bootloader. For getting official OTA you have to unroot ur phone and relock the bootloader
Click to expand...
Click to collapse
Okay, understood. thanks mate
And a few threads along the road you will read:Just do a full unroot and reflash stock recovery,unlocked bootloader is no problem for capturing OTA.
I don't know.....
Sent from my XT1068 using XDA Free mobile app
Rooting didnt affect OTA with my old moto g upgrading from 4.4.2 to 4.4.4 and probably wont affect the new moto g too
epivitor said:
Rooting didnt affect OTA with my old moto g upgrading from 4.4.2 to 4.4.4 and probably wont affect the new moto g too
Click to expand...
Click to collapse
No. You will receive ota but you can't install it. For root to work, /system has to be modified. The OTA-package will recognize this and refuses to install.
sumit227 said:
Yes you don't get official Lollipop OTA if you unlock your bootloader. For getting official OTA you have to unroot ur phone and relock the bootloader
Click to expand...
Click to collapse
Also not true. OTA does not require a relock. Only unroot and stock-recovery is required.
Wolfcity said:
And a few threads along the road you will read:Just do a full unroot and reflash stock recovery,unlocked bootloader is no problem for capturing OTA.
I don't know.....
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, because it is a fact.
doppelhelix said:
Also not true. OTA does not require a relock. Only unroot and stock-recovery is required.
Click to expand...
Click to collapse
Wolfcity said:
And a few threads along the road you will read:Just do a full unroot and reflash stock recovery,unlocked bootloader is no problem for capturing OTA.
I don't know.....
Click to expand...
Click to collapse
Oh my bad sorry, for OTA we don't need to relock I think relock is for regain the warranty correct me if I'm wrong.
Thanks for the answers guys.
Now why the heck i can't relock the bootloader whatever i do?! did anyone successfully relocked the bootloader before, and if so. how?!
i've followed all the guides around and it always give me errors and i can't flash rom!!
and in fact isnt really any useful to relock it?!
solly84 said:
it always give me errors and i can't flash rom!!
Click to expand...
Click to collapse
That's a bit vague. Please post exactly the output on your screen.
doppelhelix said:
That's a bit vague. Please post exactly the output on your screen.
Click to expand...
Click to collapse
sure!
seems like i cant relock my bootloader, whenever i do all the sequence of flashing the stock rom without the "oem lock begin" everything goes smoothly and i can restore to stock image.
as soon as i put "oem lock begin" i got a error in boot.img:
bootloader preflash validation failed
bootloader invalid signed image
and it doesn't continue...
solly84 said:
bootloader preflash validation failed
bootloader invalid signed image
Click to expand...
Click to collapse
Maybe the rom currently installed and the rom you try to flash and lock are not the same. Or, at one point you installed a rom that had a version above your current one. There are some partitions that can't be downgraded, like gpt and motoboot (which is the bootloader). Subsequently the lock will fail. Anyway, locking the bootloader is absolutely not necessary. There is no benefit in doing so.
doppelhelix said:
Maybe the rom currently installed and the rom you try to flash and lock are not the same. Or, at one point you installed a rom that had a version above your current one. There are some partitions that can't be downgraded, like gpt and motoboot (which is the bootloader). Subsequently the lock will fail. Anyway, locking the bootloader is absolutely not necessary. There is no benefit in doing so.
Click to expand...
Click to collapse
Yeah, i had tried a lot of Roms, so maybe that is why. And now i am on Custom Lollipop Rom (Titan)...
but eventually as you said, its not necessary, so i will just forget about it.
Thanks man.
Hello everyone, I'm new here, my nexus 6 is on stock 5.0.1 and waiting for update to 5.1, here are my concerns.
1. How can I root my phone without unlock boot loader or flash a twrp recovery( I Know if I got a twrp recovery, I can not get OTA).
2. If I need unlock boot loader in order to root, could this affect ota?
3. If I rooted my phone, can I get ota in the future?
Thanks.
Dennypalace said:
Hello everyone, I'm new here, my nexus 6 is on stock 5.0.1 and waiting for update to 5.1, here are my concerns.
1. How can I root my phone without unlock boot loader or flash a twrp recovery( I Know if I got a twrp recovery, I can not get OTA).
2. If I need unlock boot loader in order to root, could this affect ota?
3. If I rooted my phone, can I get ota in the future?
Thanks.
Click to expand...
Click to collapse
1. You can't 2. No can be unlocked and still do the ota 3. YES!
nms247 said:
1. You can't 2. No can be unlocked and still do the ota 3. YES!
Click to expand...
Click to collapse
Thanks. So this means if I want to root my phone, I will have to unlock boot loader. And is there anything I can do if I want to update through OTA after I rooted and unlocked my phone?
Dennypalace said:
Thanks. So this means if I want to root my phone, I will have to unlock boot loader. And is there anything I can do if I want to update through OTA after I rooted and unlocked my phone?
Click to expand...
Click to collapse
As long as you flash the stock recovery before an ota you'll be fine
Actually any system modification including root on Lollipop will prevent an OTA so in answer to question 3, no.
Basically need to flash stock system.img, recovery.img and stock boot (if you changed the kernel).
At least thats what I'm about to do.
y2whisper said:
Basically need to flash stock system.img, recovery.img and stock boot (if you changed the kernel).
At least thats what I'm about to do.
Click to expand...
Click to collapse
Correct. That's exactly what I did, and it worked.
rootSU said:
Actually any system modification including root on Lollipop will prevent an OTA so in answer to question 3, no.
Click to expand...
Click to collapse
Weird as I took the OTA while rooted.
Still working on it on my end. Drivers aren't installed for add sideboard trying to figure it out
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.