Database Users

[HOWTO] Update to 4.0.3 OTA ICS from any version with Root access (For I9020T/I9020A)

Okay First of all download the following files
a)http://android.clients.google.com/packages/ota/google_crespo/VQ8PQk_V.zip (4.0.3 OTA)
b)http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip (2.3.6 Official I9020T Build)
c)http://bit.ly/su2361ef (SU flashable)
d)http://forum.xda-developers.com/showthread.php?t=988686 (Grab recovery form this thread)
e)http://developer.android.com/sdk/index.html (Grab the android SDK installer)
f)http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429 (Radio file only required for I9020A)
Okay so when done with all that proceed as follows
1) Backup your current apps using Titanium Backup (Optional/Recommended)
2) Backup(Nandroid) your rom using backup option in CWM (Optional/Recommended)
3) Do a full wipe, wipe sdcard, system, data, cache Transfer a,b,c,f to your phone.
4) Flash the 2.3.6 Official I9020T Build you had downloaded using the install zip option in CWM (IMP-DO NOT REBOOT RIGHT NOW)
5) Flash the flashable SU file you had downloaded and then reboot.
6) Once your phone is on, continue to set up your account or skip it as you wish. (Optional)
7) Open up market, download the latest SU app, Voodoo OTARootKeeper, Titanium Backup and any other app you use that requires root.
8) Open the updated SU app, hit menu button and click preferences, go all the way down, click on su binary(tap to check for updates) , and make sure it updates to v3.0.3
9) After that is done, open and allow root permissions to all your root apps. (This is important)
9.5) Run Voodoo OTARootKeeper and click on protect root, make sure all options get checked.
10) Turn off phone, keep volume up and power pressed to boot into fastboot.
11) Select recovery with volume buttons and use power to launch.
12) Once you see a android bot image and an arrow image, keep volume up pressed and press power once, then you'll see some options appear.
13) Select apply update option and find the official 4.0.3 OTA file you had downloaded and flash. Reboot.
14) Once you have booted into ICS, go to Voodoo OTARootKeeper and select resture Root, all options should now be ticked, if not something went wrong.
15) Voila, you have root. Now to get back CWM recovery you can follow this -
i) Place the recovery img file in the android sdk platform-tools folder
ii) Switch to the directory where you unzipped the Android SDK & go to "tools"
iii) Then type "fastboot flash recovery yourfilename.img" & hit enter
iv) That should do it.
v) Optionally you may do it form Rom Manager too, if it works.
16) (ONLY FOR I9020A) Reboot phone, turn it off, boot into fastboot, select recovery, CWM should launch, flash the radio file you had downloaded to get radio working on I9020A (ONLY FOR I9020A)
Root only works for the apps that were installed while on 2.3.6
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip , use this root file, flash it in cwm, everything works, permissions etc.
This might work for other variants, tested on I9020A and I9020T, I take no responsibility for anything that might go wrong with your device. I take no credit for any links or procedures provided in this guide, I just tested and compiled.
Thanks and best of luck.

..........

Good guide but first two links are broken.

bajansurfer said:
Good guide but first two links are broken.
Click to expand...
Click to collapse
Thanks, fixed.

Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?

poging22 said:
Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?
Click to expand...
Click to collapse
Might not work, though you can try, if it fails, do it my way, also its impossible to get any kind of root that way.

Link for the ATT Radio doesnt seem to be working

Great work!
wipe SD card?
Is this necessary?

I don't think it's necessary to wipe the SD card, I followed the procedure in http://forum.xda-developers.com/showthread.php?t=1396913 and although it said my SD card would be wiped, everything was still there after I was done!

Anyone on a i9023 tried this?

Hmm...does "any version" includes M200(Korean Nexus S)?
Sent from my Nexus S using Tapatalk

http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429
I think he meant that for the 9020A radio

Link fixed, sorry for that, SD wiping might not be necessary, but I suggest as it makes it cleaner. Might work for I9023 and M200, I have no clue, maybe some experienced developer can answer that better.

Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.

Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?

little hiccup at step 12. im getting the android bot with exclamation mark but i press volume up with power and nothing happens. menu doesnt show up....
Edit: NVM... i pressed it 3 or 4 times and it finally worked

Michie23 said:
Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?
Click to expand...
Click to collapse
You should post it in questions, I cannot answer this.

fromthestars said:
Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.
Click to expand...
Click to collapse
Many ways of doing it, I just am suggesting one, the flashable zip for ics isn't available as yet, what did you flash?

i9020 keeps getting status 7 aborted and my padlock is still unlocked on t-mobile 2.3.6

Has any tried this on an i9023? Thank u
Sent from my Nexus S using xda premium

[GUIDE] Update bootloader locked R800x to GB2.3.4 w/ root & CWM w/out data plan

This guide is strictly for people who have a Verizon R800x and wants to update to Gingerbread 2.3.4 with root and ClockworkMod recovery, without having to unlock the bootloader nor have a Verizon data plan. Without a data plan you can not update the Verizon Play from 2.3.3 to 2.3.4 because they don't allow updating through WiFi. Also if you flash the 2.3.4 ftf image directly, you will not be able to root it, therefor will not be able to install CWM unless you unlock the bootloader. This guide show you to will get around that.
Note: With this method, although you have CWM, you still will not be able to install custom roms and kernels until you unlock the bootloader. This guide was written before Sony allow the Verizon Play bootloader to be unlocked from their site. Go here to unlock your bootloader, which will allow you to flash custom roms and kernels to your Play: http://unlockbootloader.sonymobile.com. If you choose to do this, you can skip this entire guide.
Instructions:
1. You must be running Gingerbread 2.3.3 on your R800x. If you aren't, download the stock Gingerbread 2.3.3 firmware and use Flashtool to flash it. Drag the ftf firmware file onto the Flashtool screen and follow the onscreen instruction to install. This step will wipe all your phone data except the SDcard.
(You might need to install drivers for your device first, you can find "Flashtool-drivers.exe" in the "drivers" folder in your Flashtool folder.)
2. Enable "USB debugging mode" on your device (Settings -> Applications -> Development).
3. Use SuperOneClick created by CLShortFuse to root your R800x. Then reboot the phone.
(This program might trigger a false positive on your antivirus software, so disable your antivirus while using it. This rooting method only work with Gingerbread 2.3.3 for the Play.)
4. Use specifically the "CWM installer v5" created by pvyParts to install ClockworkMod. That's version 5 btw.
Note: At this point, if you are content with using GB 2.3.3 with root and CWM, stop here. Proceed if you want to update to 2.3.4 with root.
5. Download either the "nandroid backup of stock Gingerbread 2.3.4 w/ root" created by netizenment or this NXT Lite CDMA rom which is already debloated and optimized.
(Put the nandroid backup into the correct directory in your microSD card so ClockworkMod will recognize it, it should be extracted into a folder named "backup" within a folder named "clockworkmod".)
6. Boot the phone into ClockworkMod recovery by: Turning it on, when the Sony logo appear, keep pressing the Volume Down button until you see the blue ClockworkMod menu appear.
7. Restore the stock GB 2.3.4 nandroid backup you just downloaded. Then turn off the phone.
(This will only install the system files, it will not install the 2.3.4 kernel.)
8. Installing the stock 2.3.4 kernel:
a. Download the stock Gingerbread 2.3.4 firmware (this is for Verizon only).
b. Drag and drop the ftf onto the Flashtool window. When you see the "Firmware selection" window appears, look to the right column, under "Exclude" and check to exclude all the items in the list, except the kernel. Then flash it.
(This will install just the 2.3.4 kernel while leaving the rest of your rooted Gingerbread 2.3.4 alone. You need to do this for the Camera and WiFi to work.)
9. In the process of restoring the nandroid backup above, the ClockworkMod recovery might become lost. However, you still have root, so you can install ClockworkMod recovery again using the CWM installer.
Other tips: LBE Security Master have can help lighten the bloatware from your rom. Among its many features, can remove system apps and prevent apps from autostarting, which will leave more free rams.
The end.

does this fix the "gtalk" issue, I went back to 2.3.3 from 2.3.4 cause of that issue.

CamachoDjr said:
does this fix the "gtalk" issue, I went back to 2.3.3 from 2.3.4 cause of that issue.
Click to expand...
Click to collapse
It doesn't fix it. Verizon does this sort of thing on purpose. Pushes out a broken update and then goes, "We are working on a fix."

[GUIDE] Easily switch between last updated stock (OTA support) and custom software

If you regularly install/test custom firmwares, ROMs and mods on your HTC One, it can be quite annoying and time-consuming if you want to go back to the latest stock software with official manufacturer OTA support (for example, to check if the latest official OTA update has been released for your region). Flashing the RUU is arguably the easiest and fastest way, but many of us have only older RUU's available which means having to download some quite big OTA updates every time. To avoid this inconvenience, i've done some research about the various methods to return to the latest stock version as hassle-free and as quickly as possible and i've come up with the following solution. This idea is not ground-breaking and might not be new to some (or most) of you, but i believe this guide should be useful for "noobs" or those who never thought of or didn't know how to handle OTAs and also to find the easiest and fastest way to swap any custom software (ROM/firmware) on your HTC One with the last 100% stock installation right before you flashed a custom recovery.
The procedure described below tries to eliminate the need to look for and flash stock firmware and stock ROMs uploaded by others, which may not necessarily exactly match with the original stock software of your phone especially since there exists dozens of HTC One variants. Using downloaded stock firmware/ROM from others might cause incompatibilities, degradation in performance, lost of signal, poor reception, etc. Ideally, you want to be able to flash whatever ROM/firmware and at any time, if you wish, you should be able to switch back to your own stock ROM and firmware. This is usually done by flashing your RUU (Rom Update Utility) according to your phone's MID and CID. However, most of you would need to go through an annoying and time-consuming update process to download several OTAs before finally reaching the current latest stock version. But here's a solution!
Minimum requirements:
1. Your HTC One's bootloader must be unlocked.
If your device is already S-OFF and if you relocked/locked your bootloader, then you can unlock the bootloader without having to use the official htcdev website. Just follow this guide to set the Bootloader as UNLOCKED: http://forum.xda-developers.com/showthread.php?t=2497712
2. You need to find your device's RUU (decrypted is even better as it allows going through the process faster) or your 100% stock software backup (firmware and ROM). If you made a nandroid backup after unlocking the Bootloader, it won't work since some data was wiped from your phone's memory during the unlocking process from the official htcdev website.
It's advised to use the RUU to restore which is specifically designed for a set of devices according to their MID and CID, rather than trying your luck at finding a compatible stock firmware and ROM for your HTC One variant. Here's a thread with a collection of RUUs and stock firmware/ROMs: http://forum.xda-developers.com/showthread.php?t=2428276
3. Your device should be S-OFF.
This is not an absolute requirement but S-OFF makes the whole procedure much easier. For the purpose of this guide, it will be assumed that your device is S-OFF.
Advantages of this method:
1. You will save time by being able to restore back to the latest 100% stock version very quickly (some OTA updates are around 400 MB which can take some time to download). You will only have to download the OTA's one time and then back up these OTA's to use later for updating/restoring your stock software.
2. You won't need an internet connection to update to your last stock version backup. The update process to previously downloaded (and backed up) OTA's will not require an internet connection. However, you will have to download any newer OTA's if available.
3. You will not have to rely on other sources to find your latest stock firmware and stock ROM. Therefore, you can be certain that you're getting a perfectly matching firmware and ROM for your specific HTC One model (the restored firmware and ROM will be exactly as if you never tampered with your device, with official manufacturer OTA support).
4. You will not have to downgrade if using an older RUU or older stock firmware/ROM, and then have to update it again via OTA. Your HTC One will be restored to 100% stock with the same software version just before you flashed a custom firmware/ROM.
5. If you absolutely need to run the RUU to go back to 100% stock, then you will not have to run the RUU process more than once (which will wipe all your nandroid backups as well as all your data, assuming you have a decrypted RUU, otherwise you will have to run the RUU twice only).
Procedure:
To summarize, if you want to go back to 100% stock using the method in this guide, all you will have to do is restore your nandroid backup and flash the firmware from the latest OTA. You will then get stock software with full OTA support within a few minutes from a custom installation. The method itself consists of handling official OTAs and extracting the most recent firmware in order to restore. But you will need a starting point where your device is 100% stock and able to receive and install official OTAs from the manufacturer. Let's assume that your HTC One is 100% stock. Whatever means you used to reach 100% stock, you will need it again. So, keep that RUU (preferably try to find your decrypted RUU zip) or stock files handy.
Check if you have any OTA update available:
No update available
If no OTA updates are available for your device, you can flash your custom recovery and then do a nandroid backup (very important). Then, you can root, flash a custom ROM and if you're S-OFF, you can even flash custom firmware.
Going back to stock: if you want to check for OTA availability at any time or you just want to go back to 100% stock, the easiest and safest way is to run your RUU. But if you found your decrypted RUU zip, you can go back to stock even faster; first restore your nandroid backup and then extract firmware.zip from the decrypted RUU zip and flash it. That's it. You're now back to 100% stock. You can check if there are any available OTAs and then go back to using custom ROMs again if you like.
Update available
Here is the more interesting part of this guide:
1. You will need the original firmware.zip file for your current stock software version. If you ran the RUU to go back to stock, extract rom.zip (follow this guide: http://forum.xda-developers.com/showthread.php?t=2497614) and then extract firmware.zip from the decrypted RUU rom.zip file. If the RUU rom.zip is not decrypted, it will give you an extraction error about all the files contained within being corrupt. In that case, you should try to find a decrypted version of the same RUU or decrypt it yourself (requires Linux, as decrypting an RUU is currently not possible on other OS). Use Winrar/Winzip to open the firmware.zip and extract recovery.img and place it in your adb folder.
2. Check for software update in the Settings menu. If you get OTA update notification, accept it. Note the file size of the OTA download, as it'll be useful to easily identify it later when searching in your device's internal memory. Let it download but do not install it. Select the option "Install Later" when prompted.
3. In the Settings menu, disable fastboot and enable USB Debugging.
4. Flash custom recovery. Root your device. Boot up to Android.
5. Install ES File Explorer from the Play Store (it's free) and give it root permission from its settings. Use ES File Explorer to search for the OTA on your phone. I found Root Explorer to be much faster at searching files although it's a paid app. You will usually find the downloaded OTA in your /sdcard/Download/ folder or /data/data/com.android.providers.downloads/cache/ folder. The OTA will have the keyword "OTA" in its filename and it will be a single zip file. You can also confirm that it's the OTA file by its file size from the earlier OTA pop-up notification. If you still can't find your OTA zip, you can search for "OTA" or "zip" through ES File Explorer or Root Explorer (much faster). Then go through the search results. Here's the original filename of one of my OTA's: OTA_M7_U_JB_50_S_HTC_Europe_2.24.401.2-1.29.401.2_R_P_release_325145_signedn3pctn48i51c9iue.zip. When you've found the OTA, copy it using ES File Explorer to the /sdcard/ location on your phone. Then plug in a USB cable to your HTC One and copy the OTA to a safe place on your PC hard drive.
6. Now, connect your phone via USB, reboot and go to your bootloader. We'll be flashing recovery.img from step 1. Use command "fastboot erase cache" then "fastboot flash recovery recovery.img" and finally "fastboot reboot". Now, you have 100% stock again with OTA support. The SuperUser/SuperSU app will still be visible on your phone but it won't work since the su binary will have been wiped during the stock recovery restore process.
7. Check for OTA software update again from the Settings menu. Install the downloaded file through the update notification menu. But if the update re-downloads, cancel it. Instead, you can manually flash it by copying the OTA zip to the phone's internal memory (don't have to rename the OTA zip but for simplicity, rename it to update.zip) and go to your Bootloader. Select Recovery using the Power button and then press the Power and Volume Up buttons to load the stock recovery menu. Then, select 'apply from phone storage' and navigate the menu as you would in a custom recovery to find update.zip and select it to install. It will follow the official update procedures and will reboot a few times before going back to your homescreen. Check attachments below for the stock recovery menu and options.
8. When your phone reboots, check for OTA again. If update is found, download it but choose "Install Later".
9. Then, just follow the same steps above; 4 through 8. Redo the same steps to copy the OTA to your PC and extract firmware.zip. The principle is that you should backup all the successive OTAs until there are no more updates available. The very last OTA's firmware.zip is the most important file. Keep it separately from the other firmwares. You should also save the previous complete OTA zips to be able to update quickly if you ever need to run RUU again.
10. After you've made a backup for the last OTA zip file, check for software update and install the already download OTA zip through the normal update notification menu. If the OTA update re-downloads, cancel it and do a manual flash for the OTA update that you saved previously, as explained in step 7. Note that an official OTA will update both the firmware and ROM.
11. Then, flash a custom recovery and make a complete nandroid backup to secure your last updated stock ROM. Copy the nandroid backup to your PC. Keep the nandroid backup and the last firmware.zip file (extracted from the last downloaded OTA zip file) safely as these two files are the only ones you will need to restore quickly back to 100% stock with OTA support, unless you were to run the RUU, in which case, you'll have to install all the OTA zip files successively.
12. Now, you can flash whatever you like on your HTC One. If you're S-OFF, you can flash custom firmware as well.
Going back to stock: if you want to check quickly if any OTA's are available or just want to easily go back to 100% stock software, all you have to do is first, restore the last nandroid backup of the stock ROM and then flash the firmware.zip from the last OTA update that you downloaded. That's it. Now, you can check and update easily to any new OTA that might have been released while your device was on custom ROM/firmware. Obviously, you can also backup any available OTA's, by following the same steps above.
I will probably expand this guide further if there is any interest in it.
If this guide was helpful to you, just press the "THANKS" button!

Hi, I found the guide useful, specially now with the upcoming 4.4 OTA. I'm confused thou, I heard you can't apply an OTA having a custom recovery, is this true? If so, shouldn't you have to flash stock recovery after loading a nandroid backup from recovery to be able to receive OTA's?

Arjen_Arg said:
Hi, I found the guide useful, specially now with the upcoming 4.4 OTA. I'm confused thou, I heard you can't apply an OTA having a custom recovery, is this true? If so, shouldn't you have to flash stock recovery after loading a nandroid backup from recovery to be able to receive OTA's?
Click to expand...
Click to collapse
You need to have 100% stock ROM and stock recovery in order to successfully apply an official OTA update. In order words, if you have custom recovery, you won't be able to update. You need to flash in the following order: stock nandroid backup, stock recovery, then download/install any new OTA.

4.4.2 (KOT49H) update fails on rooted device

Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.

Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse

amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/

Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred

Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.

I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..

I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.

[REF][How To] Return to STOCK Recovery (IF rooted) and sideload OTA

By now, with all the OTA's, unless you are brand new to the 2013 X, you know you have to have stock recovery on your phone for an OTA Update or Soak Test to install, and your system can't be modified too much or it will fail the pre-flash validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
If you have an unlocked bootloader, and rooted by flashing a 3rd party recovery (like TWRP, CWM, Philz, etc) and installing SuperSU, you likely didn't put stock recovery back on your phone.
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
The steps in this post help you do that, or get ready to do that, in case you are not near your PC when an OTA comes, of if you just don't want to use your PC.
NOTE: If you have changed too much of stock that the OTA fails, please see -> [FAQ] How to prepare for and take an OTA update (All Carriers)
NOTE: the following worked when updating 4.4 to 4.4.2, and 4.4.2 to 4.4.4 on my VZW Dev Edition X. Since Lollipop has not yet been released for my phone, I can't test this yet.
Note: If you have flashed your phone with another carrier's ROM, or have only flashed "parts" of your phone, these steps may not work!! Or they may cause you to brick!
NOTE: If your Bootloader version does NOT match the one for your phone's software version, taking an OTA could brick your phone!
You must have an Unlocked Bootloader and be rooted for these steps to work:
Obtain the STOCK Moto Recovery image, and TWRP image, for your phone:
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, and Android Version.
Visit one of the sites listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 and obtain the EXACT same ROM/SBF file that is currently on your phone. Download the ZIP to your PC.
Unzip or extract the RECOVERY.IMG file from the SBF ZIP file.
Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading)
the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053
Flashing Recovery
Place your stock recovery.img, the latest TWRP img, and the latest SuperSU.zip in your phone's DOWNLOAD folder.
Install Rashr.
On your phone, launch Rashr.
Scroll down and select other from storage
Browse and select your stock recovery
When it completes, pick the option to reboot to stock recovery.
Your device should reboot and display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. You should be in Stock recovery now.
Reboot your phone as normal.
To reflash TWRP or other custom recovery, as long as you are still rooted, you can repeat the same steps, selecting your custom recovery in step 5.
How to SIDE LOAD an OTA.ZIP via this process
If your carrier has started the push of the OTA ZIP for your phone, but you haven't received it, and you've found the correct OTA ZIP posted online and would like to flash it, the following steps can be used...
Download the OTA ZIP file (usually named as BLUR_XXX.XXX.XXX.zip, where XXX.XXX.XXX is the build number the ZIP will update) to your phone's /SDCard
Perform steps 1-7 under Flashing Recovery above to flash STOCK recovery onto your phone, and reboot into Stock Recovery.
Use the Vol Down key to scroll to Apply Update From SDCard, and press the Power key to select.
Use Vol Down key to scroll to your OTA zip file, and press Power to select.
The install will begin by verifying the update package, then verifying files on your phone match.
If the install fails, it will be reported on the screen, along with why. (usually because you have modified system files, or are not on the correct ROM version). You need to fix these errors and try again.
If verifications are successful, the patching process steps will begin. This may take several minutes.
Your phone should report Script Succeeded and Install from sdcard Complete.
Ensure Reboot System Now is highlighted, and press the Power key to reboot the phone.
The initial reboot may take longer than a regular reboot.
Note: You will see Android Is Upgrading or Optimizing screen during the boot process, that is normal.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
How to Root with unlocked bootloader...
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following ->http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 NOTE: while the thread is titled for 5.1, it works on older Android versions as well.

Good work KidJoe :laugh::good:

I guess this will be more relevant as Soaks start heading out for the 2013 X...

Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )

ks73417 said:
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
Click to expand...
Click to collapse
Yes, the OTA zip is usually stored in /cache (at least is is on the 2013 X, and my past Moto phones). it is usually named for the rom it is upgrading, not what the upgrade takes you to.
I don't see why this wont work on the 2014 X, as it did on older motos too.

Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app

ajsonofgod said:
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
In TWRP you can make a nandroid backup. I've never done it. I haven't had need because I run stock. If I need to reflash, I just reflash the same SBF I've been running.

I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?

ejlmd said:
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
Click to expand...
Click to collapse
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.

KidJoe said:
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
Click to expand...
Click to collapse
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.

there any way to make a dump the stock recovery in Lollipop, without the need root?

ejlmd said:
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
Click to expand...
Click to collapse
Yeah, OTA Update files are often named including the version the phone must be on, not the version it takes the phone to.

Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.

ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
It's ABSOLUTELY BEST you avoid the update............but....
If you can't, it is highly recommended that you clean flash it...kind of the only choice. Flash the 4.4.4 Brazilian stock ROM. And install the update from recovery. You can reroot after adding TWRP back.

I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app

ajsonofgod said:
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Please see the LINK in my signature for sites to download stock SBF files

ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
As explained elsewhere... Xposed makes changes to /system which cause OTA updates to fail their pre-flash validation checks.
It is recommended to boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip then uninstall XPosed.
You will also need to undo any changes to /system or other parts the the OTA tries to validate before installing, or else it will fail.
You are correct that a newer version of Xposed is needed.
You may also want to wait on trying the 5.0.2 Leaks because if they are an early limited early test version, rather than a soak which is nearly ready to be pushed to all, you could be stuck on this version until an SBF leaks.

Update
Does anyone know how to return to stock recovery for lollipop? New update came up today but I have TWRP.

upload the stock recovery lollipop please!!!!

Good work, love your detailed explanations always .