Database Develop

[Q] i have a moto x dev edition vzw

here my problem i've unlocked bootloader rooted and installed twrp but i cant update my phone to 4.4. everytime i take the ota update my phone just boots and shutdowns and repeats. any suggestions?

bk07 said:
here my problem i've unlocked bootloader rooted and installed twrp but i cant update my phone to 4.4. everytime i take the ota update my phone just boots and shutdowns and repeats. any suggestions?
Click to expand...
Click to collapse
you're rooted trying to do an OTA?
once you root, accepting an OTA can mess up your phone or make you lose root.

PremierGT said:
you're rooted trying to do an OTA?
once you root, accepting an OTA can mess up your phone or make you lose root.
Click to expand...
Click to collapse
idc about losing root b/c it has an unlockedbootloader getting root back is the easy part i do want the update to 4.4 though

bk07 said:
idc about losing root b/c it has an unlockedbootloader getting root back is the easy part i do want the update to 4.4 though
Click to expand...
Click to collapse
flash back to stock recovery. then do OTA. should work for you.

PremierGT said:
flash back to stock recovery. then do OTA. should work for you.
Click to expand...
Click to collapse
i've tryed that as well

bk07 said:
i've tryed that as well
Click to expand...
Click to collapse
don't flash back to it in twrp. use rsdlite or manually flash it with fastboot commands. if you actually flashed the full ota and didn't have root or twrp anymore then you would be able to take the OTA no problem.

jayboyyyy said:
don't flash back to it in twrp. use rsdlite or manually flash it with fastboot commands. if you actually flashed the full ota and didn't have root or twrp anymore then you would be able to take the OTA no problem.
Click to expand...
Click to collapse
Oddly I've done that even before I put twrp on my phone I used mfastboot with the stock IMG I got from moto. I did the update right when I got the phone and it did what I described so I thought I for find a something where I could flash stock to my phone by using twrp.

Download Motorola device manager. It should automatically restore the software to stock 4.4.
http://d1tsx1og7dz7v4.cloudfront.net/MotorolaDeviceManager_2.4.5.exe

thx for the help i had to mfastboot 4.4

This is your easiest option. All you need to do is run this utility. It will install drivers, download firmware, and flash back to stock. I used it earlier, and it's brilliant.
Even if you've already solved your problem, I highly recommend saving this for later use.
http://forum.xda-developers.com/showthread.php?t=2597625

[Q]Unlocked Bootloader,TWRP and 4.4.2 Update

Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!

msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.

dray_jr said:
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.
Click to expand...
Click to collapse
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy

msespindola said:
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.

dray_jr said:
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.
Click to expand...
Click to collapse
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?

msespindola said:
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?
Click to expand...
Click to collapse
idk i dont like to doing things half way there have been way to many bricks lately.

If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X

Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
this is why i dont read on my phone i miss crap anyway if you flash 4.4.2 yes you can flash the 4.4 TWRP and then SuperSU with a unlocked bootloader.. sorry for my miss read thanks for the catch

dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thx guys, I'll do this later, thx for the awesome responses
Sent from my XT1058 using xda app-developers app

dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.

NPOA556 said:
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.
Click to expand...
Click to collapse
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Sent from my Dev Edition Moto X

Schaweet said:
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Click to expand...
Click to collapse
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.

NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
What I've read is you need to go back to stock recovery and also make sure any /system files are unchanged. For example I renamed my old exchange apk's (in /system/app) when I put in the new ones from the nexus 5 on 4.4.2, so I would need to name those files back.

NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Sent from my Dev Edition Moto X

Schaweet said:
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Click to expand...
Click to collapse
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.

NPOA556 said:
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.
Click to expand...
Click to collapse
Good questions. I'm not sure. We certainly root differently than a non Dev edition. They might have some files modified that we don't have to modify. Also, I wonder is going to stock recovery will unroot us.
I guess we wait and stay patient.
Sent from my Dev Edition Moto X

Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.

Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
The only hope you have is if someone decides to take that factory image and runnit through kitchen to make it a flashable zip. You will also need the updated modem from either 4.4 or 4.4.2 to prevent system settings from fc ing
This goes for any moto, retail and or developer edition
You may also attempt to flash the sbf firmware and remove the delete userdata from the XML but no guarantee that you will not have issues
Hope that helps
Sent on my Gummy running Lenoto X

To take an ota you must be stock. Meaning everything. As long as you haven't flashed an updated bootloader you can just flash system.IMG and recovery.IMG from the sbf your phone is currently on you can take an ota. A successful ota does NOT require a data wipe.
---------- Post added at 04:08 PM ---------- Previous post was at 04:04 PM ----------
finalarcadia said:
Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.
Click to expand...
Click to collapse
You cannot flash any of those through twrp! If you want to flash 4.4.2 you need to fastboot the system.IMG and boot.IMG and you will need to wipe your data. If you choose this route you will not be able to take the ota when its available you'd have to wait for the sbf file to be released and update through house of moto, rsd, or fastboot.

flashallthetime said:
Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
...
Click to expand...
Click to collapse
some questions.. and comments...
I agree with #1. You must have STOCK recovery for an OTA to install properly. And #3, because the OTA generally has a file list with check sums to compare against what is on your device to make sure all required files are there and the correct version/size/etc before it will start to install.
#2 I have a question on as I've not had an issue with this unless the root process makes changes to system files (thus causing a problem for #3). I've lost root taking an OTA, but that is it.
Then again, I have a Dev X with unlocked bootloader, and I don't know enough about RockMyMoto, SlapMyMoto, etc was of rooting the X, except that initially they replaced the recovery partition with an image that when selected/booted allowed write to system, etc. This would cause issue with #1 (no longer have stock recovery on the recovery partition), but not sure what, if any system files get touched or altered from stock.
Finally, you mention clearing data being required... This would wipe you back to factory defaults and remove your apps/data. I don't believe its "required" but rather just suggested as it can make the device run smoother after the update is done.
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
Depends on how you rooted.
If you've downloaded the SBF file for the ROM on your device (if you don't have it, see if its available from -> http://sbf.droid-developers.org/phone.php?device=0 ), you can unzip it, and fastboot flash the stock recovery from it onto your device, take the OTA, and then later fastboot flash TWRP back on and install SuperSU again to root.
This assumes you did NOT touch any system files the update will check for prior to running/installing. If you did touch system files, edit build prop, removed/renamed any APK's... then fastboot flash recovery and system before taking the OTA

[Q] Dev Edition - Root but keep OTA?

I have sucessfully converted my AT&T HTC One to the Developers Edition. If install TWRP and root the device, then re-install the stock recovery, can I maintain the ability to receive OTA Updates?
Also can someone confirm that the 4.06.1540 recovery is the latest for 4.4.2 sense 6? (Found Here http://forum.xda-developers.com/showthread.php?t=2545227)
Or if there is a better way to accomplish root etc.
Thank you in advance.

sednafx said:
I have sucessfully converted my AT&T HTC One to the Developers Edition. If install TWRP and root the device, then re-install the stock recovery, can I maintain the ability to receive OTA Updates?
Also can someone confirm that the 4.06.1540 recovery is the latest for 4.4.2 sense 6? (Found Here http://forum.xda-developers.com/showthread.php?t=2545227)
Or if there is a better way to accomplish root etc.
Thank you in advance.
Click to expand...
Click to collapse
That is a good recovery to have in place *before* you start checking for the latest 5.x.x.x OTA. Technically it's not the "latest" (the latest one would be the one you will end up with *after* the OTA) but it's the right one for your situation.
Overall the short answer to your question is yes, you can get OTA's with this plan.
If you remove anything from /system you might not.
If you do more stuff (like downgrading HBOOT, installing a custom kernel, whatever) you might not.
But for most people in your situation, you'll get OTA's.
Generally.
Enjoy.

sednafx said:
I have sucessfully converted my AT&T HTC One to the Developers Edition. If install TWRP and root the device, then re-install the stock recovery, can I maintain the ability to receive OTA Updates?
Also can someone confirm that the 4.06.1540 recovery is the latest for 4.4.2 sense 6? (Found Here http://forum.xda-developers.com/showthread.php?t=2545227)
Or if there is a better way to accomplish root etc.
Thank you in advance.
Click to expand...
Click to collapse
The best thing to do is a nandroid of your stock rom & recovery prior to installing TWRP and obtaining root. If you need to go back to stock you will have it. I haven't seen the stock recovery for 4.4.2 sense 6, it should be 5.11.1540.9.

majmoz said:
The best thing to do is a nandroid of your stock rom & recovery prior to installing TWRP and obtaining root. If you need to go back to stock you will have it. I haven't seen the stock recovery for 4.4.2 sense 6, it should be 5.11.1540.9.
Click to expand...
Click to collapse
Sure it is but unfortunately if has not been possible to (fastboot boot recovery.zip) since hboot 1.44
The best most people can do is after taking the update reflash TWRP and make a backup including recovery. then download and keep the stock recovery with it.

Thank you all for the response. Here is what I would like to do:
1. Backup my existing recovery through adb using the #dd command. Anyone know the correct syntax?
2. Install TWRP and backup the existing unrooted ROM.
3. Root the device. Do not remove any files from /system, no custom kernels (doesn't really matter since I will restore backup). Simply use titanium back to restore my apks and freeze the ones I don't use. I would like to install Xposed though.....
4. See OTA Update. Backup apks, restore unrooted. Restore stock recovery through adb. Anyone know why the syntax??
5. Run the OTA Update.
6. Profit.... Go back to step 1.
What do you all think? Any help with the syntax to dump and restore stock recovery?
Sent from my HTC One using Tapatalk

sednafx said:
1. Backup my existing recovery through adb using the #dd command. Anyone know the correct syntax?
Click to expand...
Click to collapse
doesn't know the #dd command but recovery can be extracted from the firmware package inside the ota.zip
anyway, I have all the latest dev edition recovery so you'll save a little time:
4.06.1540.2 MD5: 2bb3d9df9ce8c8329db8d22781613e2c
4.06.1540.3 MD5: 87eaf7d4a9c4ba1108bf26164b1f3f3d
4.19.1540.4 MD5: 6e25ef0e614c41722b2fb4afbdde5d7c
4.19.1540.9 MD5: b4d31a181a9e44225dc83282bc1bf134
5.11.1540.9 MD5: c487a17382e2e1c207efae66fed00925
you need the one that match your actual version
2. Install TWRP and backup the existing unrooted ROM.
Click to expand...
Click to collapse
Always a good thing to do, also make a copy of that backup on your computer.
3. Root the device. Do not remove any files from /system, no custom kernels (doesn't really matter since I will restore backup). Simply use titanium back to restore my apks and freeze the ones I don't use. I would like to install Xposed though.....
Click to expand...
Click to collapse
no problem using xposed and receiving ota updates
4. See OTA Update. Backup apks, restore unrooted. Restore stock recovery through adb. Anyone know why the syntax??
Click to expand...
Click to collapse
no need to restore your backup if you didnt modified/deleted /system or /preload files and your kernel is stock. Just restore your recovery
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
5. Run the OTA Update.
6. Profit.... Go back to step 1.
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk[/QUOTE]

More Questions on Receiving OTA's
@alray On Step 4, to receive the OTA's, in addition to restoring stock recovery, wouldn't it be necessary to unroot the device and disable Xposed?

gingerlindsey said:
@alray On Step 4, to receive the OTA's, in addition to restoring stock recovery, wouldn't it be necessary to unroot the device and disable Xposed?
Click to expand...
Click to collapse
no need to unroot to be able to apply the ota but you might loose root after the update, in that case, root again after the update.
I have updated mine many times with xposed still enabled and didnt have any issue. But you might want to disable module like ''sense 5 toolbox'' when updating to sense 6... Anyway if you want to be safe, yes you can disable xposed but this is not required.

@alray Thank you very much! I was unrooting and disabling Xposed, etc. Good to know I can "Keep it Simple"!

@alray The link for the latest recovery is 404ed. Can you repost? EDIT: Nevermind. Removed the [/HIDE] from the link and it worked.
Where is the OTA saved BTW?
Thanks again for all the advise. I may update the OP to outline these in detail.

The ota is saved to /sdcard/downloads
Sorry for the bad link, it should work now
Sent from my HTC One using XDA Free mobile app

alray said:
The ota is saved to /sdcard/downloads
Sorry for the bad link, it should work now
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
That path makes perfect sense.... I feel like captain obvious smacked me in the face..... Thanks!!!!!
Sent from my HTC One using Tapatalk

[Q] Android L with custom recovery.

So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance

You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.

PedroAlba said:
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
Click to expand...
Click to collapse
This is asked every time an new OTA comes out, and we get many threads started covering it.
To date...
For the Motorola X 2013, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
None of the OTA's will install if you have TWRP recovery on your phone. Instead you get stuck in a bootloop. (mfastboot erase cache will get you out of the bootloop). You need to have stock recovery on your phone. NOTE: I don't recall what happens when using Philz or CWM as recovery.
Each OTA so far has included a "Pre-Install Verification Check", a manifest of files and their checksum/hashes which the update compares against your phone. If expected files are missing, or the wrong hash, the OTA will fail to install. - So any removed or modified "bloat", system files, etc. need to be in place. Any apps like Xposed which change /system need to be disabled/removed. In some cases Freezing apps using Titanium Backup cause the OTA to fail, and the apps need to be unfrozen. However, some have not had to unfreeze. Using the phone's app manager to disable an app (Settings -> Apps -> open app listing -> DISABLE) does not have to be undone.
If you have version mismatch between GPT.BIN or Motoboot.img and the ROM on your phone, taking an OTA WILL brick the phone. - Grab the FULL SBF for the Stock Moto ROM which matches the bootloader version on your phone, or a newer SBF (i.e. if you have the bootloader version that corresponds to 4.4.2, grab the 4.4.2 SBF or 4.4.4 SBF), and flash it via mfastboot. You may need some extra steps to flash GPT.BIN and Motoboot.img.
If you've used hacks to root/disable write protection because you have a locked bootloader, you may lose root, and wont be able to re-root until a new exploit is found. Those hacks might also get in the way of the OTA's pre-install validation checks.
If you have unlocked your bootloader via mfastboot oem unlock UNIQUECODE or Sunshine, the bootloader will not re-lock.
There have been some posts (twitter and G+) about how Lollipop poses new security features which are a challenge to rooting, even with an unlocked bootloader. Since I don't know the technical ins and outs, all I can say is.. Even with an unlocked bootloader, I wont jump on Lollipop as soon as its available, until I know if I can still root my X.
(I have a little bit more detail posted here -> http://mark.cdmaforums.com/MotoX-OTA.html)

lowvolt1 said:
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
Click to expand...
Click to collapse
For what it's worth, you don't need to uninstall the modules. Just use the Xposed Disabler zip in your SD card, then install the framework again once you've flashed /system and taken the update.
When I did updated to 4.4.4 I disabled the modules in the Xposed UI (not sure if that was necessary or not), but did not actually uninstall any of the APKs for the modules. When I reinstalled Xposed after updating, all I just turned all my modules back on and rebooted.

Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.

mtpease said:
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
Click to expand...
Click to collapse
Not really a bad practice either way, if you clear stuff out now and again. If you try to take an OTA with a modified /system partition, it usually just fails during the hash checks and never installs/modifies anything.

You started your thread title with a [q].... Perhaps the Q&A section would be the section to ask your question? ?

[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.