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 .
Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay
jayp57 said:
Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay
Click to expand...
Click to collapse
the thing is that not always the 'unroot' works for doing a system update, the unroot (have you performed the full one?) could leave behind modified binaries or maybe apps you installed have did that (for eg if you installed busybox it will leave the new binary) and the first step of the OTA update is to do a check of all the files that are going to be updated (patched) and if one of them doesn't match the sha1 checksum the update will abort (will not change anything on your tab when aborting). you can fix it by:
1. (complicated) restore the orginal files (you can check the recovery log on your cache partition to see where it failed)
2. (recommended) flash a stock rom matching your existing Android (you are on lollipop so you can use this for a stock lollipop install)
ps. factory reset doesn't save, that one just erases 'data' partition, has nothing to do with the ota (that usually updates files on the 'system' one or the 'boot/recovery/fastboot' partitions)
Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay
jayp57 said:
Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay
Click to expand...
Click to collapse
if you start with tmp_root it will open an early adb shell as root (regardless of whether your tab was or not rooted)
check after you shell in to see if the /cache is mounted (input a simple mount) and if it is not you need to mount it
afterwards you will need to go and do an adb pull on your recovery log (if i recall is on /cach/recovery ) and check inside to find on what did the ota failed
however this is cumbersome and even if you find on what it fails you still will have to find the original files (and after you try to OTA again it can fail many more times on other files as the OTA is aborted on the first non matching file and if there are many you will need to repeat these steps over again). i never did this, i am just saying that it could be done, but why would one waset maybe hours just so he can bring his system back to the same state it could bring in 3 minutes by flashing a stock rom? but if you want the complicated way feel free
if i were you i would just flash the stock rom in 3 minutes (that is how long it takes) and move along
what security reasons you are talking about?
I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.
jayp57 said:
I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.
Click to expand...
Click to collapse
oh, i see... i doubt they are tampered by anyone (except Lenovo of course ) the files i provide have already been used by others (and if they were to be tampered they would have failed future OTA's, the boot image is checked and it won't load if modified etc)
as a personal thought, to tamper a stock rom (to whatever purpose one would want) so that they cannot be detected by a future ota requires a level of knowledge that i think keeps us safe (i think one who is able to do such a thing would not 'waste' his time and resources on doing it to a normal/casual user like we are), so if you are able to take ota's you can safely assume that the files are the ones Lenovo put in there (not to say that Lenovo could not do funny things tho)
i wish you to become so important that one day this could be a real concern
yeah you are right.
thanks for your support. i managed to update my tablet.
Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.
saupiquet said:
Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.
Click to expand...
Click to collapse
the link is in my first reply here
Hi.
After reading many threads, I can say I haven't found the answer to my issues, so I wanted to ask you guys for some help with this:
I bought a latin american BTW-W09, and since we haven't received the Nougat update yet, I tried using Firmware Finder and install the American FW (Full OTA C128). I used the "dload" method, but after a few tries I just got to an incomplete install (No working Bluetooth, many system apps missing, including Updater). I panicked, and found a way to rollback to MM, using the European FW (C100).
I'm now on MM (BTV-W09C100B0006) and everytime I try to upgrade to N, I get the same results: Bluetooth is broken and missing system apps.
Keep in mind, I've tried using 3 different methods: HiSuite/Firmware Updater, Firmware Finder/Proxy in the tablet itself and I've even unlocked the bootloader, installed TWRP (Greatslon mod) and flashed the Zip files.
So after all of that...
Is it possible to update using files from another region?
Thanks a lot
Hi, everybody!
I have a couple questions and couldn't find clean answers.
I have an unlocked and rooted Moto G5 Plus (XT1683, build number NPNS25 . 137-15-5 - POTTER_BRAZILDSDS_CUST).
As you all may know, after a root process, you're not fully stock anymore.
1 - I have received the OTA August update (NPNS25.137-15-11) and i'm planning on installing it after restoring my device to stock. Since the update may not show up immediately after restoring the device, i'd like to download it and make it a flashable zip or something like that instead of waiting for a update notification that could take sometime to come back again.
Also, I couldn't find this OTA on the internet. How can i do that?
2 - I know I can find stock images/firmware at https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ but I still have some doubts.
As said, my device's build number is NPNS25.137-15. At the link above, the firmware is named as NPN25-137-15. Also, I've found some people talking about NPN25 instead NPNS25. Are they all mistyping or is it really a different Moto G5 Plus version?
About the last NPN25.137-15 (Last updated 10-09-2017) file in the link: Is it the August update?
3 - What's up with all these variants for just one device? NPNS25-137-15, NPNS25-137-13, NPNS25-137-35, NPNS25-137-69. XT1681, XT1683, XT1685 in just one country. What a mess!
I know this questions may sound lame but I couldn't find solid answers and I don't intend to mess anything up. Better safe than sorry, right?
So you are currently rooted, correct?
Install a root file manager and make sure you can access /.
Download the OTA update.
Once it is finished downloading, you will find it in the /cache directory; copy it to your device storage, then to PC.
Since you don't want to take the update right away, reboot into recovery and wipe /cache; this will remove the ota file from /cache so that you don't accidentally auto update.
If you would be so kind, please upload the OTA and share the link.
I can make a TWRP flashable zip with it, as I have with other recent OTA files:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
*edit*
You said your current build is NPNS25.137-15-5?
The closest available fastboot file available currently is NPN25.137-15, which means that I would also need the OTA file from NPN25.137-15 to NPNS25.137-15-5 for the current file to be of any use.
You could use the fastboot file to flash back to NPN25.137-15 and pull that OTA, or maybe even a larger OTA that goes from NPN25.137-15 directly to NPNS25.137-15-11.
Hi, thanks for your help!
Yes, i'm rooted and on NPNS25.137-15-5 right now. I'll upload the OTA file tonight when i'll be in no rush!
The closest available fastboot file available currently is NPN25.137-15, which means that I would also need the OTA file from NPN25.137-15 to NPNS25.137-15-5 for the current file to be of any use.
You could use the fastboot file to flash back to NPN25.137-15 and pull that OTA, or maybe even a larger OTA that goes from NPN25.137-15 directly to NPNS25.137-15-11.
Click to expand...
Click to collapse
-That means that NPNS25.137-15 is an updated version from NPN25.137-15?
Anyway, i'll upload the OTA file tonight!
Q9Nap said:
So you are currently rooted, correct?
Install a root file manager and make sure you can access /.
Download the OTA update.
Once it is finished downloading, you will find it in the /cache directory; copy it to your device storage, then to PC.
Since you don't want to take the update right away, reboot into recovery and wipe /cache; this will remove the ota file from /cache so that you don't accidentally auto update.
If you would be so kind, please upload the OTA and share the link.
I can make a TWRP flashable zip with it, as I have with other recent OTA files:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
*edit*
You said your current build is NPNS25.137-15-5?
The closest available fastboot file available currently is NPN25.137-15, which means that I would also need the OTA file from NPN25.137-15 to NPNS25.137-15-5 for the current file to be of any use.
You could use the fastboot file to flash back to NPN25.137-15 and pull that OTA, or maybe even a larger OTA that goes from NPN25.137-15 directly to NPNS25.137-15-11.
Click to expand...
Click to collapse
I have uploaded the 93-8 OTA (March 2018 security patch)..if you could please convert it into a flashable ZIP we'd greatly appreciate it!
https://drive.google.com/file/d/1EihHeSrnj03usOKrLkZkWqdEjeMeIZQb/view?usp=sharing
I have an Axon 7 European version ZTEA2017GV1.1.0B1
It has some bugs, for example the weird Google problem I still haven't solved. Since the Nougat update 7.1.1 is available, is there any way I could upgrade my phone from android 7.0 to 7.1.1? I tried to find links for .zip files but couldn't find any. I'd like to see if those bugs go away with the update, but some things I read said that I can't upgrade from 7.0 to 7.1... Help would be much appreciated.
https://forum.xda-developers.com/axon-7/how-to/download-a2017g-n-b08-german-brand-t3699743?nocache=1
https://www.ztemobile.de/support/downloads/?product_id=2100#
I'm downloading it from the German website right now.
https://www.ztemobile.de/support/downloads/?product_id=2100
If you've been using the phone a while and have plenty of user data, or have issues, for best results you should do a factory reset first to clear it of any junk and have maximum memory available. Backup your data. Also backup your call and message data. Make sure it's charged. Put the zip on the root of the SD card and go to updates in settings and point it to the zip file. It may find and run it on a reboot too. I can't remember.
You could also download the B04 zip and overwrite it first?
Australia has B10 MM and now B11 MM then you can update to B04 Nougat.
B08 seems only available from Germany. Still not sure whether I'll update to B08 or stay on B04 till we see if ZTE give us Oreo.
Here's the open device firmware page. Don't use A2017 or A2017U firmwares on an A2017G phone. Same goes for other models using the wrong firmware. The cellular support will be messed up and then need to fix it. Probably ruins partitioning too. Easiest just to use the correct firmwares.
The B11 MM zip seems also able to rollback to MM from Nougat.
http://www.ztedevice.com/support/detail?id=CF924E214F0D466A9712B8F09523F0CF
RobboW said:
I'm downloading it from the German website right now.
https://www.ztemobile.de/support/downloads/?product_id=2100
If you've been using the phone a while and have plenty of user data, or have issues, for best results you should do a factory reset first to clear it of any junk and have maximum memory available. Backup your data. Also backup your call and message data. Make sure it's charged. Put the zip on the root of the SD card and go to updates in settings and point it to the zip file. It may find and run it on a reboot too. I can't remember.
You could also download the B04 zip and overwrite it first?
Australia has B10 MM and now B11 MM then you can update to B04 Nougat.
B08 seems only available from Germany. Still not sure whether I'll update to B08 or stay on B04 till we see if ZTE give us Oreo.
Here's the open device firmware page. Don't use A2017 or A2017U firmwares on an A2017G phone. Same goes for other models using the wrong firmware. The cellular support will be messed up and then need to fix it. Probably ruins partitioning too. Easiest just to use the correct firmwares.
The B11 MM zip seems also able to rollback to MM from Nougat.
http://www.ztedevice.com/support/detail?id=CF924E214F0D466A9712B8F09523F0CF
Click to expand...
Click to collapse
I checked the update history and it says the phone has been updated from B10 to B01? Is B01 a newer version then?
And could you instruct further how to do that .zip thing, last time I tried it didn't work even though I put the file to the root of the internal sd card. Do I need a removable sd card in order for the updating to work or what went wrong? I have mifavor 4.2 but it's B01.1. should it be like that?
B10 was MM and sounds like B01 is an old Nougat.
Should be able to directly update to B04 or B08 from B01.
Even B04 is MiFavor 4.2 still. Probably need B08 to get to MiFavor 5.
Did you have the actual update zip file extracted out of the main downloaded zip?
Update.zip, not the whole lot with PDF etc. Should be on an SD card. I haven't tried it using internal storage. Did both mine from SD.