[FAQ] How to prepare for and take an OTA update (All Carriers)

[KidJoe]

This is a reserection of -> http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735 and -> http://mark.cdmaforums.com/MotoX-OTA.html

With Verizon pushing a maintenance release for their Stock 4.4.4 (which doesn't change the Android version number), I wanted to post this sooner rather than later because questions are coming up....

Whenever a new OTA comes up, there are always questions like "what do I need to do to take the OTA?" or "I got prompted to take the OTA, but xxx is happening." This thread is intended to provide that information in once place.

This information is based on the past OTA updates for the Verizon, T-Mobile, and ATT Moto X phones, and threads on various forums. It should apply to all OTA updates.

Please note: If you have tried downgrading by flashing only parts of a rom, or have mismatched files on your phone for any reason, DO NOT TAKE AN OTA or you will likely brick your phone!! First flash your phone with a full SBF of the latest ROM for your carrier before attempting to take future OTA's. For more on Downgrading and the risks associated with it, see -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG

These are the most common Questions and Issues we've seen in the past...

1. If you could NOT get your bootloader unlock code directly from Motorola and rooted by some other process, you should *WAIT* on taking an OTA update as it may patch any vulnerability being exploited to root your phone. And you may not be able to ROOT on this new version!!
2. If you used Sunshine, or got your Bootloader Unlock code from the China Seller or Middleman... You should BE CAUTIOUS and *WAIT* on upgrading past 4.4.4. Please see -> [LOLLIPOP WARNING]Those Who Unlocked Via Sunshine or Purchasing a Code from China
3. You should expect to lose root when you take an OTA.
4. For the Motorola X, 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.4 OTA, your phone needs to be on 4.4.2 (or 4.4.3 depending on your model/carrier). 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.
5. Inside the OTA is a "Pre-flash Validation Check" to ensure your phone is on the correct version BEFORE it will flash. It includes a manifest file that contains a list of files and their check sums the OTA expects to be on your phone. If the files are missing from your phone, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. NOTE: The more files patched by the update, the more strict the pre-flash validation will be. So an update from 4.4.4 -> 5.1 will be more strict than the recent Verizon 4.4.4 maintenance patch.
6. Because of #5, you must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, may need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update. NOTE: Back in the "early days" of the 2013 X, all apps frozen with TiBu had to be unfrozen. Later updates that hasn't been much of a problem. I don't use it, so I can't say for sure.
7. If you have XPosed installed on your phone, it often does make changes that will cause the Pre-Flash Validation to fail. You may be able to just disable it, rather than fully removing it, and then take the OTA. (To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) NOTE: There is a newer version of Xposed needed for Lollipop!!
8. The OTA Updates will only install via Stock Recovery. If your Root method has replaced stock recovery with something else, you will need to use mfastboot to flash stock recovery on your phone BEFORE you attempt to take the update. Not having Stock Recovery on your phone when you take the OTA can result in your phone doing a boot loop. NOTE: You can use fastboot erase cache to delete the update zip file from your phone which will stop the boot loop.
9. There are several options to get back to "stock" without loosing your data. (I will add them to Post #2 of this thread at a later date), some are more technical, some are more noob friendly. The one you use, depends on how much, or how little, you have modified your phone away from stock.
10. In some cases, using mfastboot to reflash stock Recovery.IMG and System.IMG can be enough to get you back to "Stock" and take the OTA update.
11. 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/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 Please be sure to use the latest TWRP fastboot IMG file (Alternate Link) and Installable ZIP of SuperSU
12. Any tethering hacks you have done will likely need to be undone in order to take the OTA (see #5 above), and may not work after the OTA is installed.

Some FAQ's...

• I've tried taking the OTA, but I'm stuck in a loop. It wants to keep rebooting. - This is usually caused by having a 3rd party recovery, like TWRP/CWM, on the phone. Re-flash the stock recovery to install the OTA update, or use fastboot erase cache to delete the update zip file from your phone which will stop the boot loop. (instructions will be added to Post #2 of this thread in the future)
• I've tried putting back my bloat, and taking the OTA, but it fails. - You likely missed something the Pre-flash Validation check is looking for. If you are able to capture the OTA ZIP and use the SIDE LOAD AN OTA instructions (which will be added to post #2 of this thread in the future), you can watch progress of the OTA install. It will tell you the error, and/or what file doesn't match.

In the past we've seen error codes 252 and 410. These have been related to files on the phone not matching the OTA's pre-flash validation checks.

 

[KidJoe]

[NOT YET SPELL CHECKED!!!]

How to return to stock & Unrooted... (Windows options only, as I don't have a Mac) Note: Some Windows 8/8.1 users have had issues, so when possible, please use Windows 7.

The following are listed in the order I originally posted them HERE and HERE


Requirements: These are the same no matter which option you use.

To repeat what I said in the OP, Do NOT attempt to downgrade your phone!! Please be aware of the risks -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG

1. Know what version ROM is on your phone before you touch anything. Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites that host leaked ROMS until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
   
   So for example: If your phone model is XT1058 and under about phone it reports...
   
   android version is 4.4.4
   system version is 212.44.26. ghost_row.RCI.en.ca
   build nunber is KXA21.12-L1.26
   
   That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, and you'll find... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
   
   (notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
   
   IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files
2. You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
3. mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools can NOT flash the SYSTEM.IMG on Moto phones!!
4. Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
5. Your battery has an 80% or greater charge!!
6. MicroUSB Cable.
7. Know how to start your phone into the Fastboot AP/Bootloader mode...
   • Unplug phone
   • Power down phone.
   • Hold Volume Down and Power
   • After a few seconds release Power, you should be in Fastboot AP menu on phone.

The Options...

NOTE: I most often recommend option 5.

Option 1... The "Moto X Tool Kit"

This is the most newbie friendly.. But it can be a little complex to prepare and put your SBF in the right place, etc.

See -> [TOOL] Moto X Toolkit v1.4.4 [Backup/Restore,Drivers,Return to stock,Root,Bootani]

It is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. The only thing it does not appear to include would be Roms for your particular phone, so, you'll likely need to download the ROM for your phone separately. As noted in the ToolKit thread, if they are available, you can get them from here -> http://sbf.droid-developers.org/ghost/list.php your "build number" or part of it, should be in the file name you are downloading.

Again, I haven't used this tool, so for install, setup and usage, I'll have to point you to that thread to ask. Two main options you'll be interested in... UNROOT (which keeps your data and apps) or FLASH BACK TO STOCK (which will likely also completely reset your phone and wipe any/all data, settings, applications, etc).



Option 2... mFastboot flashing individual parts of your phone's firmware.

This will not erase your data and apps. It is a good option if you are stuck in a boot loop.

If you have made very few changes to your phone and already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept an OTA without losing data/apps.

NOTE: you may need to disable and/or uninstall Xposed before doing this.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!

After you have the requirements as listed above, the steps would be as follows...

1. Start the phone in Fastboot AP/Bootloader mode.
2. Connect phone to PC via USB cable.
3. open command prompt file and change to the folder you unzipped the ROM file to.
4. type the following, pressing enter after each command, and wait for it to finish before going onto the next...
   mfastboot flash boot boot.img
   mfastboot flash recovery recovery.img
   mfastboot flash system system.img
   mfastboot reboot

phone should reboot and be back to stock and ready for the update.

NOTE: to combat a 410 ERROR while doing the update, some users have also had to also do the following

fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn

See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)



Option 3... Fully flash your phone using RSDLite while attempting to keep your data and settings

NOTE: this has the potential to erase your data if you don't edit the XML properly before flashing.

Follow this guide -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash) using SBF of the ROM currently on your phone, or newer for your carrier and model. HOWEVER, before doing it, as part of STEP 4 while editing the XML file, also remove the line that says...

<step operation="erase" partition="userdata" />

Failure to remove this line will result in your data/apps/settings being erased from your phone!!



Option 4... Fully flash your phone using RSDLite

Note: this WILL ERASE YOUR USER DATA AND APPS, and put you back to a "fresh" phone.

Follow this guide -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash) using the ROM from your carrier.




Option 5... Using mFastboot to manually flash your phone's firmware (without wiping data).

This is very similar to using option 3, but uses Moto fastboot instead of RSD, however it adds a few steps which aid in flashing when your GPT.BIN and MOTOBOOT.IMG are mismatched from the rest of your rom, and refuse to flash.

As written, these steps will NOT erase your data and apps. Because of this you may need to disable and/or uninstall Xposed before doing performing these steps.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!

After you have the requirements near the top of this page, the steps would be as follows...

1. Start the phone in Fastboot AP mode.
2. Connect your phone to PC via MicroUSB cable.
3. open a command prompt and change to the folder you unzipped the ROM/SBF file to.
4. type the following, pressing enter after each command, and wait for it to finish before going onto the next... NOTE: yes, there are a few commands being repeated, but this is intentional!!!
   • mfastboot getvar max-download-size
   • mfastboot flash partition gpt.bin
   • mfastboot flash motoboot motoboot.img
   • mfastboot reboot-bootloader
   • mfastboot flash partition gpt.bin
   • mfastboot flash motoboot motoboot.img
   • mfastboot flash logo logo.bin
   • mfastboot flash boot boot.img
   • mfastboot flash recovery recovery.img
   • mfastboot flash system system.img
   • mfastboot flash modem NON-HLOS.bin
   • mfastboot erase modemst1
   • mfastboot erase modemst2
   • mfastboot flash fsg fsg.mbn
   • mfastboot erase cache
   • mfastboot reboot

The phone should reboot and and be ready. (it could take a little longer than a normal reboot)

NOTE: if you wish to erase your data and apps during this process, just before the final reboot command, issue... mfastboot erase userdata

Option 6... Flash only stock recovery.

This option is useful if all you did was unlock your bootloader, flash TWRP recovery, and rooted. It can be used if you've haven't installed Xposed, or modified any stock apps, and only run rooted for apps like BigTinCan's Adaway, Root Explorer, Wifi Tether for Root, etc.

1. Start the phone in Fastboot AP mode.
2. Connect your phone to PC via MicroUSB cable.
3. open a command prompt and change to the folder you unzipped the ROM/SBF file to.
4. type the following, pressing enter after each command, and wait for it to finish before going onto the next...
   mfastboot flash recovery recovery.img
   mfastboot reboot-bootloader
5. Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
6. The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
7. Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
8. The device will start in Stock Recovery display additional menu options (Text will appear in BLUE)
9. While in Stock Recovery, use the VOL DOWN Key to scroll and the POWER Key to select the option you wish to use.
10. You may now use the option to reboot the phone.

 

[KidJoe]

{reserved}

 

[aptalca]

KidJoe,

Thanks so much for this. Even though I manually returned all changes to stock, the ota still kept quitting with an error.

It was really annoying because after each error, I would have to redownload the entire ota, 696MB, which was downloading rather slowly.

Anyway, I followed option number 2 from the original post to flash boot, recovery and system and it was smooth sailing after that

Thanks again

 

[summit15]

[NOT YET SPELL CHECKED!!!]

Option 2... mFastboot flashing individual parts of your phone's firmware.

This will not erase your data and apps. It is a good option if you are stuck in a boot loop.

If you have made very few changes to your phone and already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept an OTA without losing data/apps.

NOTE: you may need to disable and/or uninstall Xposed before doing this.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!

After you have the requirements as listed above, the steps would be as follows...

1. Start the phone in Fastboot AP/Bootloader mode.
2. Connect phone to PC via USB cable.
3. open command prompt file and change to the folder you unzipped the ROM file to.
4. type the following, pressing enter after each command, and wait for it to finish before going onto the next...
   mfastboot flash boot boot.img
   mfastboot flash recovery recovery.img
   mfastboot flash system system.img
   mfastboot reboot

phone should reboot and be back to stock and ready for the update.

NOTE: to combat a 410 ERROR while doing the update, some users have also had to also do the following

fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn

See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)

[/list]

KidJoe, thanks for the help. I have an XT1095. All I am pretty sure I did was root. I've never installed TWRP or even used root apps other than Greenify. In that state I was not able to accept the recent 5.1 OTA. I used the option in Supersu to full unroot (which also uninstalled Supersu). That did not fix the problem. I am now just finding your guide but other searching has led me to your conclusion that Option 2 should be all I need to do plus it won't wipe my phone.

The confusion I have now involves the system.img file. I requested the 5.0 download from Moto, but they never responded. I found the proper zip file elsewhere (TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip). When I unzip it, I see all the files. The recovery.img file is there but the system.img file is broken up into eight different files all named system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, etc.

Do I have the right files? Do I flash all of them individually? I'm not very experienced in this and don't want to screw this up. Any information you could provide would be greatly appreciated. Thanks.

Edit: After posting this, I found this site: http://www.usoftsmartphone.com/t279221.html that showd me how to extract the system file from all the sparse files. Step one creates a system.img file from all of them. Step two seems to unzip them. I am guessing that the file created after step 1 is the file I would need to flash?

Again, thanks for your help here!

 

[KidJoe]

KidJoe, thanks for the help. I have an XT1095. All I am pretty sure I did was root. I've never installed TWRP or even used root apps other than Greenify. In that state I was not able to accept the recent 5.1 OTA. I used the option in Supersu to full unroot (which also uninstalled Supersu). That did not fix the problem. I am now just finding your guide but other searching has led me to your conclusion that Option 2 should be all I need to do plus it won't wipe my phone.

The confusion I have now involves the system.img file. I requested the 5.0 download from Moto, but they never responded. I found the proper zip file elsewhere (TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip). When I unzip it, I see all the files. The recovery.img file is there but the system.img file is broken up into eight different files all named system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, etc.

Do I have the right files? Do I flash all of them individually? I'm not very experienced in this and don't want to screw this up. Any information you could provide would be greatly appreciated. Thanks.

Edit: After posting this, I found this site: http://www.usoftsmartphone.com/t279221.html that showd me how to extract the system file from all the sparse files. Step one creates a system.img file from all of them. Step two seems to unzip them. I am guessing that the file created after step 1 is the file I would need to flash?

Again, thanks for your help here!

Keep in mind that the XT1095 is NOT a 2013 X, so its files may be different.

 

[Cristian314]

So I'm using a cm12 based rom and I've wanted to return to stock lately, let me see if I got this straight. Using rsd lite and erasing the line:
<step operation="erase" partition="userdata" />
Won't erase internal memory like music, photos, etc?
It's safe? I'm wondering if I'm going to have problems with the apps since they're running on ART on lollipop or if the system settings will have issues when I return to stock KitKat

 

[summit15]

OTA Accepted

For anyone who finds themselves in my same situation (all I really did to my phone was root it and install Supersu, no custom recovery or big time changes and I wanted to apply the OTA without wiping my device), I got my OTA update applied by doing the following:

Did a "Full Unroot" from within the Supersu app which then uninstalled itself.
I found the proper Moto ZIP file that contained Lollipop 5.0.
I then used mfastboot to flash the boot.img and the recovery.img
I then boot the phone up and told it to check for system updates.
It found the update, downloaded it, and then applied it.
It worked and I can move on with my life now.

NOTE: Most of my confusion in this process centered around my being told I needed to flash the system.img file. My problem was that inside the Moto ZIP file were eight different system_sparse files. I didn't know what to do with all them. I found a site in the previous link that showed me how to essentially combine all them into one system.img file. I followed those directions and it created the file. However, when I tried to flash it, I got an error that seemed to suggest that the file was corrupt.SO, this was after I had already flashed the boot and recovery files. I gave the OTA a shot just hoping it would work. Turned out it did.

Thanks again to KidJoe for this guide.

 

[KidJoe]

For anyone who finds themselves in my same situation (all I really did to my phone was root it and install Supersu, no custom recovery or big time changes and I wanted to apply the OTA without wiping my device), I got my OTA update applied by doing the following:

Did a "Full Unroot" from within the Supersu app which then uninstalled itself.
I found the proper Moto ZIP file that contained Lollipop 5.0.
I then used mfastboot to flash the boot.img and the recovery.img
I then boot the phone up and told it to check for system updates.
It found the update, downloaded it, and then applied it.
It worked and I can move on with my life now.

NOTE: Most of my confusion in this process centered around my being told I needed to flash the system.img file. My problem was that inside the Moto ZIP file were eight different system_sparse files. I didn't know what to do with all them. I found a site in the previous link that showed me how to essentially combine all them into one system.img file. I followed those directions and it created the file. However, when I tried to flash it, I got an error that seemed to suggest that the file was corrupt.SO, this was after I had already flashed the boot and recovery files. I gave the OTA a shot just hoping it would work. Turned out it did.

Thanks again to KidJoe for this guide.

Again.. you have an XT1095... which is NOT a 2013 X... this guide is in the 2013 X section, so things can/will be different for a 2014 X...

But thanks for sharing.

 

[Malba14]

Awsome Tutorial!!

I'm really a noob, so I still have some questions...

After that you should get the OTA update by going to setting -> about phone -> update??

because if so, I'm not.

Another thing i may done something wrong. On this step:

4. Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!

I needed to move the ROM/SBF to the phone right? At any folder? Because I didnt do that and I opened the command prompt in the pc folder that the ROM/SBF was unziped. Nothing wrong happened to my phone, apparently.

Should I remake the tutorial moving the unziped file to the sdcard folder of my phone?
sorry for so many doubts.

 

[KidJoe]

I'm really a noob, so I still have some questions...

After that you should get the OTA update by going to setting -> about phone -> update??

because if so, I'm not.

The OTA update hasn't rolled out for all phone models and carrier variants yet. So there is a VERY GOOD chance it wont be available for you yet.

Another thing i may done something wrong. On this step:

4. Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!

I needed to move the ROM/SBF to the phone right? At any folder? Because I didnt do that and I opened the command prompt in the pc folder that the ROM/SBF was unziped. Nothing wrong happened to my phone, apparently.

Should I remake the tutorial moving the unziped file to the sdcard folder of my phone?
sorry for so many doubts.

No, you do NOT move the SBF, or parts of it, to your phone. Leave it on your PC.

The tools to flash (RSDLite and mFastboot) are tools ON YOUR PC... they need the file to be on your pc.

In the post I talk about figuring out what file to download and use the example of the Rogers XT1058, and the correct file being XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip so sticking with that example.. you visit one of the sites (from your PC), download XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip ... and unzip it on your PC to a folder... If you are following option 2, 5 or 6 and using mFastboot, then you need to open a command prompt and change drive and directories to where you unzipped XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip to BEFORE you start entering the mfastboot commands. NOTE: you could just SHIFT-RightClick on the folder and "open command window here" as that will open a command prompt in that path/folder.

 

[Malba14]

The OTA update hasn't rolled out for all phone models and carrier variants yet. So there is a VERY GOOD chance it wont be available for you yet..

The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button and then every time I turned my phone on, after 30 seconds it rebooted to TeamWin. This kept going until I clicked on recovery or system (I dont remember - under the reboot page) and the cycle went off saying that has been some kind of problem with the update.

No, you do NOT move the SBF, or parts of it, to your phone. Leave it on your PC.

The tools to flash (RSDLite and mFastboot) are tools ON YOUR PC... they need the file to be on your pc.

In the post I talk about figuring out what file to download and use the example of the Rogers XT1058, and the correct file being XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip so sticking with that example.. you visit one of the sites (from your PC), download XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip ... and unzip it on your PC to a folder... If you are following option 2, 5 or 6 and using mFastboot, then you need to open a command prompt and change drive and directories to where you unzipped XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip to BEFORE you start entering the mfastboot commands. NOTE: you could just SHIFT-RightClick on the folder and "open command window here" as that will open a command prompt in that path/folder.

This part I did it right, i think. I fount the one that describe my phone better.
XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml
Actually I just reallized it is .xml. Is that ok? On my PC it opened with winrar just like any zip.

 

[KidJoe]

The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button and then every time I turned my phone on, after 30 seconds it rebooted to TeamWin. This kept going until I clicked on recovery or system (I dont remember - under the reboot page) and the cycle went off saying that has been some kind of problem with the update.

Rebooted to TeamWin and said there was a problem with the update?? Yeah, because you need STOCK recovery on the phone. (as stated in the OP)

This part I did it right, i think. I fount the one that describe my phone better.
XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml
Actually I just reallized it is .xml. Is that ok? On my PC it opened with winrar just like any zip.

There maybe an XML inside the ZIP... you need to uncompress the entire file (extract all) BEFORE you can flash it, other wise RSDlite or mFastboot wont find the files you are trying to flash.

 

[Malba14]

Rebooted to TeamWin and said there was a problem with the update?? Yeah, because you need STOCK recovery on the phone. (as stated in the OP)

There maybe an XML inside the ZIP... you need to uncompress the entire file (extract all) BEFORE you can flash it, other wise RSDlite or mFastboot wont find the files you are trying to flash.

Thanks for the help man. I'm sorry for the noob questions.

I actually did the hole tutorial before. I extracted this hole file and opened the command prompt in it and did the tutorial number 5.

Sorry if I wasnt clear before but the problem with the update was just a backgroud history to what I was aiming to know. That is: after I do the tutorial, what I have to do to get the OTA update now?

And how can I know that I did it right?

Your are awsome man!

 

[KidJoe]

The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button....

I forgot to mention... for the models IT has started pushing for, they were sending it out in waves... IF you missed your turn (which you eventually did by not installing), you usually need to wait until the end, when the waves are done.. Because of when the BR Xt1058 push was started, I'd say that might be in the next week, or two.

Thanks for the help man. I'm sorry for the noob questions.

I actually did the hole tutorial before. I extracted this hole file and opened the command prompt in it and did the tutorial number 5.

Sorry if I wasnt clear before but the problem with the update was just a backgroud history to what I was aiming to know. That is: after I do the tutorial, what I have to do to get the OTA update now?

And how can I know that I did it right?

Your are awsome man!

As long as you flashed the latest 4.4.4 rom, your bootloader is consistent with the ROM you flashed, are you 100% completely stock, you just sit and wait until the OTA becomes available to your phone again. You can manually keep checking...

OR you can see if the 5.1 SBF is available for your carrier/model in this thread -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 download and flash it instead, which will take you right to 5.1...

OR you can see if the official OTA zip has been posted, download the zip to the /SDCard of your phone, and follow the SIDE LOAD section of -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079

 

[Malba14]

I forgot to mention... for the models IT has started pushing for, they were sending it out in waves... IF you missed your turn (which you eventually did by not installing), you usually need to wait until the end, when the waves are done.. Because of when the BR Xt1058 push was started, I'd say that might be in the next week, or two.

As long as you flashed the latest 4.4.4 rom, your bootloader is consistent with the ROM you flashed, are you 100% completely stock, you just sit and wait until the OTA becomes available to your phone again. You can manually keep checking...

OR you can see if the 5.1 SBF is available for your carrier/model in this thread -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 download and flash it instead, which will take you right to 5.1...

OR you can see if the official OTA zip has been posted, download the zip to the /SDCard of your phone, and follow the SIDE LOAD section of -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079

Thanks a lot!!!

 

[RohanAditya]

Option 5... Using mFastboot to manually flash your phone's firmware (without wiping data).

This is very similar to using option 3, but uses Moto fastboot instead of RSD, however it adds a few steps which aid in flashing when your GPT.BIN and MOTOBOOT.IMG are mismatched from the rest of your rom, and refuse to flash.

As written, these steps will NOT erase your data and apps. Because of this you may need to disable and/or uninstall Xposed before doing performing these steps.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!

After you have the requirements near the top of this page, the steps would be as follows...

1. Start the phone in Fastboot AP mode.
2. Connect your phone to PC via MicroUSB cable.
3. open a command prompt and change to the folder you unzipped the ROM/SBF file to.
4. type the following, pressing enter after each command, and wait for it to finish before going onto the next... NOTE: yes, there are a few commands being repeated, but this is intentional!!!
   • mfastboot getvar max-download-size
   • mfastboot flash partition gpt.bin
   • mfastboot flash motoboot motoboot.img
   • mfastboot reboot-bootloader
   • mfastboot flash partition gpt.bin
   • mfastboot flash motoboot motoboot.img
   • mfastboot flash logo logo.bin
   • mfastboot flash boot boot.img
   • mfastboot flash recovery recovery.img
   • mfastboot flash system system.img
   • mfastboot flash modem NON-HLOS.bin
   • mfastboot erase modemst1
   • mfastboot erase modemst2
   • mfastboot flash fsg fsg.mbn
   • mfastboot erase cache
   • mfastboot reboot

The phone should reboot and and be ready. (it could take a little longer than a normal reboot)

NOTE: if you wish to erase your data and apps during this process, just before the final reboot command, issue... mfastboot erase userdata

Hey.
I wanted to return to stock by flashing the parts manually.
I followed your steps but when i executed the command a message popped out saying 'Variable not supported' and it continued the execution.
I did not find any change in the system when I checked after the whole process was completed.
The message I mentioned earlier was shown for every step.
Example Code:

mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [  0.280s]
writing 'partition'...
(bootloader) This may take a few seconds, if a 
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions 
OKAY [  0.534s]
finished. total time: 0.819s

I also flashed boot, logo, system and the others parts.
But the same message was shown every time.
And after the process was complete I restarted the phone but the 'Bootloader Unlocked Warning' screen appeared.
I hadn't removed this after I rooted the phone.
I thought it would be removed when I flashed motoboot, boot and logo.

Phone Details:
Current Android Version: 4.4.4
System Version: 212.44.26.ghost_row.AsiaRetail.en.03
Build Number: KXA21.12-L1.26
Kernel Version: 3.4.42-g50861a7

I used this image:
Drive Link:
https://docs.google.com/file/d/0B5XNxZ2OcfKtdDROTk5kb21ObU0/edit?pli=1
File Factory Link:
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip

I desperately need your help.
What should I so to flash the stock image properly?
Thanks in advance.

 

[KidJoe]

Hey.
I wanted to return to stock by flashing the parts manually.
I followed your steps but when i executed the command a message popped out saying 'Variable not supported' and it continued the execution.
I did not find any change in the system when I checked after the whole process was completed.
The message I mentioned earlier was shown for every step.
Example Code:

mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [  0.280s]
writing 'partition'...
(bootloader) This may take a few seconds, if a 
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions 
OKAY [  0.534s]
finished. total time: 0.819s

I also flashed boot, logo, system and the others parts.
But the same message was shown every time.
And after the process was complete I restarted the phone but the 'Bootloader Unlocked Warning' screen appeared.
I hadn't removed this after I rooted the phone.
I thought it would be removed when I flashed motoboot, boot and logo.

Phone Details:
Current Android Version: 4.4.4
System Version: 212.44.26.ghost_row.AsiaRetail.en.03
Build Number: KXA21.12-L1.26
Kernel Version: 3.4.42-g50861a7

I used this image:
Drive Link:
https://docs.google.com/file/d/0B5XNxZ2OcfKtdDROTk5kb21ObU0/edit?pli=1
File Factory Link:
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip

I desperately need your help.
What should I so to flash the stock image properly?
Thanks in advance.

Based on what you posted, I'm not completely sure of your question. I mean if you think you are not stock because you still have the unlocked bootloader warning message after flashing, that is normal if you've ever unlocked your bootloader.

Out of box LOCKED bootloader shows Locked Status 0... After unlocking, it shows Unlocked Status 3. If you attempt to relock it, it will show as Locked Status 2. We don't have a way to get back to Locked Status 0. That being said... If the status is NOT 0, you'll always get the Unlocked Bootloader Warning when using the stock/standard LOGO.BIN.

 

[RohanAditya]

Based on what you posted, I'm not completely sure of your question. I mean if you think you are not stock because you still have the unlocked bootloader warning message after flashing, that is normal if you've ever unlocked your bootloader.

Out of box LOCKED bootloader shows Locked Status 0... After unlocking, it shows Unlocked Status 3. If you attempt to relock it, it will show as Locked Status 2. We don't have a way to get back to Locked Status 0. That being said... If the status is NOT 0, you'll always get the Unlocked Bootloader Warning when using the stock/standard LOGO.BIN.

Okay I unlocked it. The code is 3.
Thanks
But how do I know if I'm ready to receive the OTA?
Is there a way to find out if I can receive it without it resulting in a brick?
And is the Variable not supported message normal?
Or have I done something wrong?
Thanks in advance

 

[KidJoe]

Okay I unlocked it. The code is 3.
Thanks
But how do I know if I'm ready to receive the OTA?
Is there a way to find out if I can receive it without it resulting in a brick?
And is the Variable not supported message normal?
Or have I done something wrong?
Thanks in advance

Variable not supported is normal and nothing to worry about.

Because each OTA is different and looks at different aspects of the phone (based on what it will upgrade, or not), there is no way to tell you exactly what should be checked.

If you returned to stock by flashing the COMPLETE STOCK ROM (all parts of SBF) for your carrier/model with mFastboot, and received no errors (other than variable not supported), and your bootloader version is consistent with the ROM on your phone (i.e. you didn't attempt to downgrade), then you should be ready for the OTA...