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

[RohanAditya]

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

Thanks a lot buddy

 

[regular_]

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.

If I currently have Xposed installed and uninstall it via TWRP, could I use this method to only flash stock recovery.img?
Also, does this procedure erase root from the phone?

----------------------------------

Edit: So, what I did was the following:

1. Backup via TWRP
2. Uninstall Xposed Framework via TWRP (with official uninstaller zip)
3. Followed the steps in Option #5
4. Updated via OTA
5. Profit.

Everything went fine, no errors (except some "Variable not supported messages), no bootloops, no FC's. I lost Root, but I'll just flash Super SU again. Thank you KidJoe!

 

[jkalsch]

I am using a Dev edition XT1060 with twrp and SU, I don't think I changed anything else. I tried to flash stock recovery and I recieved the maintenance update and my system is now 212.166.4 and the update is unsuccessful when I try to get OTA to Lollipop. Can I use the file I got from Verizon labeled with system 212.55.26 and use option 5 even though the version is older or do I need a different recovery file? What are my other options?

 

[KidJoe]

I am using a Dev edition XT1060 with twrp and SU, I don't think I changed anything else. I tried to flash stock recovery and I recieved the maintenance update and my system is now 212.166.4 and the update is unsuccessful when I try to get OTA to Lollipop. Can I use the file I got from Verizon labeled with system 212.55.26 and use option 5 even though the version is older or do I need a different recovery file? What are my other options?

I would just get the FXZ/SBF and flash it..

See -> http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519

 

[PackerDroid]

Stock boot image before OTA?

Hello, I posted this elsewhere but I think I might have better luck here. Do you have any feedback/guidance for my issue in my situation? Thank you!
-----------------------------------------------------------------------------------------------------------
I was just able to take the EMR update first through system update OTA. Now it won't give me the 5.1 OTA. I currently have stock recovery, no root, with no system mods. I tried manually installing the 5.1 OTA but it doesn't work. It says it was aborted because the package expected a different build fingerprint. But I'm on 212.154.2.ghost_row.RepublicWireless.en.US Any suggestions for getting the OTA to work, or do I have to get root and TWRP back and flash the 5.1 SBF? If so, is the 894.64 MB zip from file factory for sure the one I need for Republic Wireless? I just don't want to brick my phone. Thanks!
-----------------------------------------------------------------------------------------------------------
I was doing some research and I think I forgot 1 step to make sure I'm 100% back to stock. I made no system mods and I did flash stock recovery, but I forgot about the boot image I was using so I wasn't seeing the bootloader unlocked message. Would that make the manual OTA fail/abort and/or also make system update not recognize 5.1 is needed? I'm guessing it does. So I'll try getting TWRP back and flashing the correct stock boot image for 4.4.4, then remove root/TWRP again and see if it will take the OTA, either from system update or manual OTA. Hopefully this works, or at least reminds others to take this step if necessary. Thanks for any feedback!
-----------------------------------------------------------------------------------------------------------

 

[KidJoe]

Hello, I posted this elsewhere but I think I might have better luck here. Do you have any feedback/guidance for my issue in my situation? Thank you!
-----------------------------------------------------------------------------------------------------------
I was just able to take the EMR update first through system update OTA. Now it won't give me the 5.1 OTA. I currently have stock recovery, no root, with no system mods. I tried manually installing the 5.1 OTA but it doesn't work. It says it was aborted because the package expected a different build fingerprint. But I'm on 212.154.2.ghost_row.RepublicWireless.en.US Any suggestions for getting the OTA to work, or do I have to get root and TWRP back and flash the 5.1 SBF? If so, is the 894.64 MB zip from file factory for sure the one I need for Republic Wireless? I just don't want to brick my phone. Thanks!
-----------------------------------------------------------------------------------------------------------
I was doing some research and I think I forgot 1 step to make sure I'm 100% back to stock. I made no system mods and I did flash stock recovery, but I forgot about the boot image I was using so I wasn't seeing the bootloader unlocked message. Would that make the manual OTA fail/abort and/or also make system update not recognize 5.1 is needed? I'm guessing it does. So I'll try getting TWRP back and flashing the correct stock boot image for 4.4.4, then remove root/TWRP again and see if it will take the OTA, either from system update or manual OTA. Hopefully this works, or at least reminds others to take this step if necessary. Thanks for any feedback!
-----------------------------------------------------------------------------------------------------------

So you have a Republic Wireless XT1049, and you want to update it to 5.1? The best way is to just download the 5.1 SBF/FXZ file -> http://www.filefactory.com/file/27kl2ef9ngk7/XT1049_GHOST_REPW_5.1_LPA23.12-39-R-15_cid6_CFC.xml.zip and use Option 5 in the second post of this thread to flash it.

If your bootloader is already unlocked, it will stay unlocked after flashing this way. Also, you'll get the stock logo.bin file, so you'll get the "Unlocked bootloader warning" graphic on reboot.

NOTE: if your bootloader was NOT unlocked already, and you want to root 5.1, you need to unlock your bootloader BEFORE you flash 5.1. I haven't paid attention lately, so I don't know if there was a way to use Sunshine to unlock the 4.4.4 and up bootloaders. Last time I looked it was for 4.4.2 and lower.

 

[PackerDroid]

Thank you so much for your reply! I'm sure that option 5 is the best/safest route, but I'm wondering if there might be another easier way that would still be safe, especially since I remembered that I flashed non-stock logo bins and animations. From what I can remember, I think I flashed the 5.1 logo bin and animation, even though I was on 4.4.4, not realizing it would create an issue for the OTA. That must be why the OTA aborted. So, if I just flash back the stock logo bin and animation for 4.4.4, then I think I should be able to take the OTA. Is that correct? Yes, I am unlocked having used sunshine, but all that I did with root was install the xposed framework (and flash different boot logos/animations). I uninstalled xposed, disabled superSU, flashed stock recovery (I had TWRP), PLUS I did a factory reset and wiped internal storage. So now I know I have stock system, stock recovery, and now I can flash stock logo bin and animation. Then I should be able to take the OTA, right?
If I still can't get the OTA to work, and I have to flash the full 5.1 SBF, can I do that through TWRP? Or do I have to use a PC? I'm asking because I recently erased my PC to do a fresh installation of Windows 10. So I'd have to get all of the files/ADB/drivers again to use the PC method. Right now I have an app that allows me switch back and forth between stock and custom recoveries.
Thank you again for your help!

 

[KidJoe]

Thank you so much for your reply! I'm sure that option 5 is the best/safest route, but I'm wondering if there might be another easier way that would still be safe, especially since I remembered that I flashed non-stock logo bins and animations. From what I can remember, I think I flashed the 5.1 logo bin and animation, even though I was on 4.4.4, not realizing it would create an issue for the OTA. That must be why the OTA aborted. So, if I just flash back the stock logo bin and animation for 4.4.4, then I think I should be able to take the OTA. Is that correct? Yes, I am unlocked having used sunshine, but all that I did with root was install the xposed framework (and flash different boot logos/animations). I uninstalled xposed, disabled superSU, flashed stock recovery (I had TWRP), PLUS I did a factory reset and wiped internal storage. So now I know I have stock system, stock recovery, and now I can flash stock logo bin and animation. Then I should be able to take the OTA, right?

Here is the problem.... custom Logo.bin does not get in the way of an OTA update. Nor does non-stock boot animiation (at least usually)...

Notice the BOLD I highlighted in your reply? Its possible that you will forget something else that you tweaked or customized... OR you won't sufficiently undo your changes. That is why OTA updates will fail for users who customize their phones. "Undoing the changes" and doing a factory reset does not ensure you are stock. The only 100% sure and fool proof way to return the phone to stock is fully flash it with the SBF (either parts or whole). Now, if all you did was modify contents of the system partition, then sure, flashing only system.img via mfastboot might be enough.

Based on what you are typing, I'm willing to bet you miss something and the OTA fails.

If I still can't get the OTA to work, and I have to flash the full 5.1 SBF, can I do that through TWRP? Or do I have to use a PC? I'm asking because I recently erased my PC to do a fresh installation of Windows 10. So I'd have to get all of the files/ADB/drivers again to use the PC method. Right now I have an app that allows me switch back and forth between stock and custom recoveries.
Thank you again for your help!

To flash a STOCK ROM you either use RSDLite or mFastboot. You can not flash a stock rom/SBF via TWRP. If you could, it would be one of the options in the 2nd post. Sure for RECOVERY, IF you are still rooted, you can use something like Rashr to flash stock or custom recovery (see -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079 ). And *IF* you haven't changed much of system, you can use that thread to take the OTA... BUT it relies on /system and the other parts not being modified so it can pass the the pre-flash validation checks.

I know you don't want to hear it, but your best, safest, and quickest way to 5.1 is to just use mfastboot or RSDLite and flashing the entire 5.1 SBF since you have it.

At this point, if you really want to go the ota route your process will be this...
1. Hope you undid root, Xposed, SuperSU, and any other customization done to your phone. (to pass pre-flash checks)
2. revert to Stock recovery
3. make sure all parts of your phone match and are consistent with the rom version on your phone. (includes bootloader, modem, etc)
4. Attempt to take the OTA.
5. If the OTA fails, spend the time trying to figure out why it failed, and fix that.
6. attempt to re-download the OTA Zip file and try to install it again.
7. If it fails, go back to step 5.

Or, you could take 10 minutes to install Android PlatformTools/ADB/mFastboot, the Moto drivers, and flash the 5.1 SBF directly and be done. (if you wont be customizing or tweaking the phone again so you don't want to install the Android SDK on your PC, you might be able to find a portable Platformtools/adb setup to try... then the only that will be "left" installed on your PC would be the moto drivers. just keep in mind that the "portable" ADB installs that you just "unzip" can get out of date which could cause issues)

 

[PackerDroid]

Thanks again for your help. I'll try the OTA again and if it fails then I'll move forward with option 5. If I have difficulty with option 5, will a full manual flash including data retain the unlocked status from sunshine?
One other question just for my own knowledge/learning about this... I've flashed custom ROMs on one of my tablets with TWRP before with no issues. What's the difference between flashing custom or stock ROMs through TWRP that allows custom to work but not stock?
The only step I may have a question about is step 3 of option 5, "open a command prompt and change to the folder you unzipped the ROM/SBF file to." I can't remember, what do I actually type to change to the folder I need? For example, if the folder is on my desktop and it is called "SBF file" then what do I need to type for the command prompt?
I'm not sure when I'll get a chance to work on this again, but when I do, I'll try to remember to post back with how it goes. Thanks!

 

[bvsbutthd101]

I'm having trouble locating the SBF file. I'm on Megatron007 AICP 11.0 unofficial rom but I'm still on the kit kat bootloader. Trying to update to the lollipop one. I was hoping to do option 5 so I could keep my data and apps.

 

[KidJoe]

I'm having trouble locating the SBF file. I'm on Megatron007 AICP 11.0 unofficial rom but I'm still on the kit kat bootloader. Trying to update to the lollipop one. I was hoping to do option 5 so I could keep my data and apps.

you're signature says VZW XT1060 Dev... SO look at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images there are Moto X, VZW Dev Edition: images of 4.4.2, and 4.4.4. flash back to those and take the OTA's, or..

in the OP of this thread, as well as my signature I point to -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 which has sites which host some of the roms... take a look through each site... I know at least the file factory link works.. and if you scroll through, you should find XT1060_GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip

 

[bvsbutthd101]

you're signature says VZW XT1060 Dev... SO look at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images there are Moto X, VZW Dev Edition: images of 4.4.2, and 4.4.4. flash back to those and take the OTA's, or..

in the OP of this thread, as well as my signature I point to -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 which has sites which host some of the roms... take a look through each site... I know at least the file factory link works.. and if you scroll through, you should find XT1060_GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip

So only one those links works in OP. I found the XT1060_GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip file. Since I'm on a marshmellow rom is using that file gonna be a problem? I was hoping to keep my data

 

[KidJoe]

So only one those links works in OP. I found the XT1060_GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip file. Since I'm on a marshmellow rom is using that file gonna be a problem? I was hoping to keep my data

You said you have a KK bootloader... but you are running a custom rom based on 5.1 now.. I usually suggest wiping data when doing that, only because I don't know what tweaks, etc were done in that rom vs stock, and if that will have any impact.

If it was stock KK, and you wanted to flash stock 5.1, then I'd say go for it (make sure you don't exectue the erase userdata parts), you're chances of not needing to wipe are better.

Also keep in mind that fully flashing a STOCK 5.1 rom will update your bootloader, motoboot.img and gpt.bin. That being said, I've seen some have issues trying to keep KK bootloader and only upgrading parts of their phone with Stock 5.1.

 

[bvsbutthd101]

You said you have a KK bootloader... but you are running a custom rom based on 5.1 now.. I usually suggest wiping data when doing that, only because I don't know what tweaks, etc were done in that rom vs stock, and if that will have any impact.

If it was stock KK, and you wanted to flash stock 5.1, then I'd say go for it (make sure you don't exectue the erase userdata parts), you're chances of not needing to wipe are better.

Also keep in mind that fully flashing a STOCK 5.1 rom will update your bootloader, motoboot.img and gpt.bin. That being said, I've seen some have issues trying to keep KK bootloader and only upgrading parts of their phone with Stock 5.1.

Thanks for the help. I was able to successfully update my bootloader while still retaining my data. Everything appears to be working fine now. All the problems I was having before seemed to be fixed. I was having the speaker phone bug and when people would call me they couldn't hear me. Would have to call them back. Working now :good: