Database Develop

How to downgrade back to 1.00 radio and .77 HBOOT for the OTA (S-OFF ONLY!!!)

Note: You *MUST* be s-OFF for this to work properly. If you're not, it won't work.
1. Download this zip file: http://www.mediafire.com/?mi4utrhbacdbbxt mirror: http://www.megaupload.com/?d=LSR7QG9W
2. Rename it to PB31IMG.zip (uppercase name and lowercase extension matters, make sure it's not .zip.zip also) and push it to the root of your sdcard, so it's /sdcard/PB31IMG.zip
2 1/2. MAKE A NANDROID BACKUP (in case you ever want to go back)
3. Reboot into HBOOT by holding vol down while booting up, or by typing "adb reboot oem-42"
4. Hit vol-up when it asks if you want to apply the zip.
5. Wait for it to finish, then reboot when it asks you to.
Congrats, now you're back to stock 2.1-update1 with the original 1.00 radio.
thanks to aiccucs for his work in compiling the stock zip!

Cheers, mate.

just curious but don't you also need to put back the stock recovery back on? and that zip is stock without root, right?

the337 said:
just curious but don't you also need to put back the stock recovery back on? and that zip is stock without root, right?
Click to expand...
Click to collapse
Completely stock without root. Includes stock system, kernel, recovery, radio, and HBOOT as well as a data wipe. The only thing not stock is the fact you're still going to be S-OFF, but that's nothing really to worry about. VZW techs don't really know how to check that .

Doing this will 100% allow you to receive the OTA when Verizon finally releases it right?

ZFriedenreich said:
Doing this will 100% allow you to receive the OTA when Verizon finally releases it right?
Click to expand...
Click to collapse
Yes.
/10char

good work A++++

I had originally pulled the stock Rom image from the RUU (ran the RUU and snagged the image from the temp folder). I was able to flash back to that but had to do some trickery first pushing some files over to the phone in and then running some commands in ADB. Is this just that same image extracted directly from the stock RUU? Or has this been modified in some way?
I'm assuming it's either been modified to allow flashing without pushing those other two files first, or s-off disables the check that would normally throw a "image you are attempting to flash is older" error.

I thought we could just flash stock recovery and apply the OTA... This route, we lose all our settings and apps, correct?
Sent from my Incredible via TapaTalk...

Awesome post! Thanks man
Sent from my ADR6300 using XDA App

And having S-Off, if VZW tries to remove our root ability, all we would have to do is install SU back on correct?

Can't you just apply the ruu's with the new clockworkmod?
Sent from my ADR6300 using XDA App

I got the following quote from http://unrevoked.com/rootwiki/doku.php/public/forever
"How can I use S-OFF to recover from an unrooted update?
S-OFF gives your device permanent NAND unlock in the booted system, and also disables HBOOT's signature checking on firmware zip files. So, even if you take a OTA that has not been rooted, you can simply flash a new recovery that allows you to install su, and use that to restore yourself to a fully rooted system. We have provided ClockworkMod and Amon-Ra recovery images for you to use for this purpose. "

Hatman41 said:
I got the following quote from http://unrevoked.com/rootwiki/doku.php/public/forever
"How can I use S-OFF to recover from an unrooted update?
S-OFF gives your device permanent NAND unlock in the booted system, and also disables HBOOT's signature checking on firmware zip files. So, even if you take a OTA that has not been rooted, you can simply flash a new recovery that allows you to install su, and use that to restore yourself to a fully rooted system. We have provided ClockworkMod and Amon-Ra recovery images for you to use for this purpose. "
Click to expand...
Click to collapse
Yeah, I don't think we need to revert to original hboot/radio/etc... I think we just need stock recovery and a stock rom to get the OTA

anyone besides the OP tried this yet?

kentoe said:
Yeah, I don't think we need to revert to original hboot/radio/etc... I think we just need stock recovery and a stock rom to get the OTA
Click to expand...
Click to collapse
I would hope this option is the case because I never updated my radio (still on 1.xx), so if I used the method in this thread wouldn't I risk bricking because I'd be flashing the radio on top of itself?
Sent from my Incredible using XDA App

What about reverting everything back if we have S-ON? Sorry if this is a n00b question.

Ruggerxpunk said:
I would hope this option is the case because I never updated my radio (still on 1.xx), so if I used the method in this thread wouldn't I risk bricking because I'd be flashing the radio on top of itself?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Yes, so therefore you wouldn't have to do anything besides going back to a stock rom.

Xxq TZ pxX said:
What about reverting everything back if we have S-ON? Sorry if this is a n00b question.
Click to expand...
Click to collapse
You can use this.
http://forum.xda-developers.com/showthread.php?t=727263

Ruggerxpunk said:
I would hope this option is the case because I never updated my radio (still on 1.xx), so if I used the method in this thread wouldn't I risk bricking because I'd be flashing the radio on top of itself?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Also know if your rooted with s-on you cannot flash proper otas because the signature check is there and it want allow you to flash a legit signed ota with clockwork. Also know if you accept the ota you will loose root. And won't be able to gain it back without s-off. I really don't understand why people are so apprehensive. Live a little man. It's just a phone. Not a ferrari. Even though it runs like one.

[Q] Verizon DE Software Upgrade Q

If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike

Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
You need stock /system partition and stock recovery. It doesn't matter whether the bootloader is locked or unlocked.

Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
To install? or to be notified and receive the update?
To receive the update you'll need to be running the "stock" Verizon firmware, rooted/unrooted and bootloader locked/unlocked doesn't matter.
For it to install successfully, to expand on what kbluhm posted...
Keep in mind that usually OTA updates will look for certain files to be present on your phone and verify their size and check sums (MD5 or the like) before the OTA update will install. If files are missing or changed, the ota update will fail. That is why "stock /system" is required.
And "stock recovery" is needed because when the phone reboots to install the update, it tries to boot to stock recovery and run the install script. The 3rd party recoveries don't seem to work, or have errors, when installing the OTA update zips.
If you've rooted with SlapMyMoto, RockMyMoto, or thel like, you may have other issues to deal with in order to take any OTA updates since those processes can touch other files/partitions on the phone which will cause problems with the OTA Updates.

So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?

Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!

You could grab the factory image from Motorola and flash only system and recovery using fastboot. That is my plan. You can find the zip file on Motorola's site or there is a topic here on XDA.
Sent from my XT1060 using Tapatalk

guitarbedlam said:
So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?
Click to expand...
Click to collapse
Mike7143 said:
Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!
Click to expand...
Click to collapse
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735

KidJoe said:
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...

guitarbedlam said:
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...
Click to expand...
Click to collapse
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.

KidJoe said:
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.
Click to expand...
Click to collapse
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.

tcrews said:
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.
Click to expand...
Click to collapse
Interesting. One of the issues reported with the Kit Kat update was the OTA failing due to apps frozen with Titanium Backup. I only "disable" via the stock app manager, so I haven't had a problem.

Most likely those with failures had modified/deleted/renamed something else that was causing the issues and blaming it on the frozen apps. I have updated every device I've had with frozen apps. Freezing, at least in Titanium Backup, tells the OS the app is not available. In recovery, the OS is not loaded and knows nothing about frozen apps. Titanium doesn't touch the actual files so they are still present to be patched by the OTA.
Sent from my Nexus 10

[Q] Where is the OTA update stored?

Hi All,
I have an ATT m7 that I'm running on GPE 4.4 (build KTR16S) with TWRP and the bulletproof kernel.
I'm getting notifications for the 4.4.2 update, and I'd like to install it, but obviously with TWRP installed, it can't automate the update process. So, a few questions:
1) Is it okay for me to manually install the update after locating it from my own recovery?
2) Where is the update stored, so that I can track it down within TWRP to flash?
Thanks guys!

karankshah said:
Hi All,
I have an ATT m7 that I'm running on GPE 4.4 (build KTR16S) with TWRP and the bulletproof kernel.
I'm getting notifications for the 4.4.2 update, and I'd like to install it, but obviously with TWRP installed, it can't automate the update process. So, a few questions:
1) Is it okay for me to manually install the update after locating it from my own recovery?
2) Where is the update stored, so that I can track it down within TWRP to flash?
Thanks guys!
Click to expand...
Click to collapse
Mines in the downloads folder

karankshah said:
Hi All,
I have an ATT m7 that I'm running on GPE 4.4 (build KTR16S) with TWRP and the bulletproof kernel.
I'm getting notifications for the 4.4.2 update, and I'd like to install it, but obviously with TWRP installed, it can't automate the update process. So, a few questions:
1) Is it okay for me to manually install the update after locating it from my own recovery?
2) Where is the update stored, so that I can track it down within TWRP to flash?
Thanks guys!
Click to expand...
Click to collapse
you can't flash ota updates with twrp. only stock recovery. like mb_guy said, the ota are stored in the ''downloads'' folder. When you apply the ota, the file is deleted automatically.
You can manually flash ota updates from stock recovery. Move the ota.zip to android/obb. boot phone in stock recovery, select ''apply from phone storage'' ---> /obb --> your ota.zip

For some reason the update is in the /cache/ directory instead of in the downloads directory.
How do I switch to the standard recovery? Do I need to reflash the entire ROM or is there another flashable file?

karankshah said:
For some reason the update is in the /cache/ directory instead of in the downloads directory.
How do I switch to the standard recovery? Do I need to reflash the entire ROM or is there another flashable file?
Click to expand...
Click to collapse
you can flash stock recovery the same way you flashed custom recovery:
Code:
fastboot flash recovery name_of_recovery.img
you must flash the stock recovery that match your firmware version which you can find with a:
Code:
fastboot getvar all

karankshah said:
For some reason the update is in the /cache/ directory instead of in the downloads directory.
How do I switch to the standard recovery? Do I need to reflash the entire ROM or is there another flashable file?
Click to expand...
Click to collapse
Stock recovery from here
http://forum.xda-developers.com/showthread.php?t=2545227

bored_stupid said:
Stock recovery from here
http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Thanks for the help guys. I spent way too long trying to figure out how to get my computer to recognize my phone while in fastboot so I could get the main version number.
I finally was able to figure that out, but I'm not seeing my version (1.26.502.10) on the page.
Are any of the other recoveries usable? Or does this mean that I would have to go back to stock ATT, take the OTA update ATT was pushing a loong time ago, and then re-root to then flash a GE rom?

karankshah said:
Thanks for the help guys. I spent way too long trying to figure out how to get my computer to recognize my phone while in fastboot so I could get the main version number.
I finally was able to figure that out, but I'm not seeing my version (1.26.502.10) on the page.
Are any of the other recoveries usable? Or does this mean that I would have to go back to stock ATT, take the OTA update ATT was pushing a loong time ago, and then re-root to then flash a GE rom?
Click to expand...
Click to collapse
There is a rom dump here. once downloaded, you should be able to extract the stock recovery from there.
http://forum.xda-developers.com/showthread.php?p=40764389&highlight=1+26+502+10#post40764389

bored_stupid said:
There is a rom dump here. once downloaded, you should be able to extract the stock recovery from there.
http://forum.xda-developers.com/showthread.php?p=40764389&highlight=1+26+502+10#post40764389
Click to expand...
Click to collapse
It looks like he's pulled the 1.26.502.10 rom - know of any other places it might be? Most of the 502.10 roms I'm seeing now are pre-rooted.

karankshah said:
It looks like he's pulled the 1.26.502.10 rom - know of any other places it might be? Most of the 502.10 roms I'm seeing now are pre-rooted.
Click to expand...
Click to collapse
I can only find pre-rooted roms two. however, if the rom has the SuperSU installed, you can do a full unroot from the SuperSU settings

bored_stupid said:
I can only find pre-rooted roms two. however, if the rom has the SuperSU installed, you can do a full unroot from the SuperSU settings
Click to expand...
Click to collapse
That might be a good idea. Do you know if that removes S-OFF?

bored_stupid said:
I can only find pre-rooted roms two. however, if the rom has the SuperSU installed, you can do a full unroot from the SuperSU settings
Click to expand...
Click to collapse
Ah - nevermind - just found out it won't reinstall the stock recovery, which means the OTA update won't stick anyway. Looks like the only way is the long way.

karankshah said:
Ah - nevermind - just found out it won't reinstall the stock recovery, which means the OTA update won't stick anyway. Looks like the only way is the long way.
Click to expand...
Click to collapse
If you unzip the OTA the stock recovery should be in there..
Sent from my GT-I9505 using XDA Premium 4 mobile app

karankshah said:
Thanks for the help guys. I spent way too long trying to figure out how to get my computer to recognize my phone while in fastboot so I could get the main version number.
I finally was able to figure that out, but I'm not seeing my version (1.26.502.10) on the page.
Are any of the other recoveries usable? Or does this mean that I would have to go back to stock ATT, take the OTA update ATT was pushing a loong time ago, and then re-root to then flash a GE rom?
Click to expand...
Click to collapse
Here is your stock recovery
http://www.androidfilehost.com/?fid=23501681358538645

[Q] Applying OTA Update on rooted phone with S-ON

HI there,
I have a rooted HTC One M7 Stock ROM hboot 1.57 S-ON and now I got the following update:
Software update: 6.14.111.2 (659.71 MB)
System improvements
-Android 4.4.3
-OpenSSL security improvement
Application updates
-Camera
-Gallery
-HTC Sync Manager
My question is, how can I apply the update? I already tried but since I have twrp as recovery it didn't go through. Is there a way of applying the update without losing root and my current configuration (contacts, apps, SMSs, etc)? Should I try to get S-OFF first? (I already tried to no avail like two months ago)
What is the best option to get it working with the latest software version? Sorry if my questions seem a bit too noob. I already tried looking for a similar thread.

braistorms said:
HI there,
I have a rooted HTC One M7 Stock ROM hboot 1.57 S-ON and now I got the following update:
Software update: 6.14.111.2 (659.71 MB)
System improvements
-Android 4.4.3
-OpenSSL security improvement
Application updates
-Camera
-Gallery
-HTC Sync Manager
My question is, how can I apply the update? I already tried but since I have twrp as recovery it didn't go through. Is there a way of applying the update without losing root and my current configuration (contacts, apps, SMSs, etc)? Should I try to get S-OFF first? (I already tried to no avail like two months ago)
What is the best option to get it working with the latest software version? Sorry if my questions seem a bit too noob. I already tried looking for a similar thread.
Click to expand...
Click to collapse
You must be 100% stock for ota updates, stock recovery and stock rom (untouched /system and /data/preload files). /data/preload is wiped when unlocking bootloader.

alray said:
You must be 100% stock for ota updates, stock recovery and stock rom (untouched /system and /data/preload files). /data/preload is wiped when unlocking bootloader.
Click to expand...
Click to collapse
Thanks alray for your answer. Does it mean no way I'm going to get the update working (Since I unlocked the bootloader, using htcdev method)? Or did I misunderstood you? If so, is there any other way I can get the same software?

braistorms said:
Thanks alray for your answer. Does it mean no way I'm going to get the update working (Since I unlocked the bootloader, using htcdev method)? Or did I misunderstood you? If so, is there any other way I can get the same software?
Click to expand...
Click to collapse
you first need to flash your stock recovery back and then the content of /data/preload if you can find it for your version. Otherwise you will need to restore your phone back to stock or to use custom roms.

alray said:
you first need to flash your stock recovery back and then the content of /data/preload if you can find it for your version. Otherwise you will need to restore your phone back to stock or to use custom roms.
Click to expand...
Click to collapse
Thanks again alray, very much. So you mean, if I manage to get the /data/preload and stock recovery working and run the OTA,
Will I lose root access?
Will I lose my actual configuration?
Will I be able to get everything as it is now if I have a nandroid backup?
Thanks again!

braistorms said:
Thanks again alray, very much. So you mean, if I manage to get the /data/preload and stock recovery working and run the OTA,
Click to expand...
Click to collapse
Yes you should be able to run the OTA updates if you have stock recovery for your version and the content of /data/preload for your version. Best way to know is to flash you stock recovery back and try the ota. If the ota fails, enter the stock recovery menu and you'll see why the ota installation aborted (which file is missing)
Will I lose root access?
Click to expand...
Click to collapse
Probably like for every ota updates, re-root after installation.
Will I lose my actual configuration?
Click to expand...
Click to collapse
You should not, but better to backup everything before proceeding.
Will I be able to get everything as it is now if I have a nandroid backup?
Click to expand...
Click to collapse
If you have a backup and restore it, it will restore your phone to the same state it was when you did that backup. (data, system and kernel)

[Q] rooted, unlocked, TWRP recovery, stock, Verizon OTA help

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.