Forgive me here. I have a VZW dev edition.
Currently running 4.4.4 stock rom. I had it rooted before and I think I recently lost root. Forgot why but I didn't really need it.
EDIT: I remember now. I did a factory reset. Did I lose root?
anyways the OTA that came a few weeks ago the small one will not install. I have enabled my apps again that I had disabled. I do not remember if I did a tether hack before which was just replacing a file. Bootloader is unlocked still.
So after the OTA downloads and reboots the android shows up the bar starts to move and then red exclamation mark.
Update unsuccessful.
What do I need to do? I also do not want to wipe data.
The OTA alert is annoying me to no end.
It sounds like the pre-flash validation checks are failing for some reason.
A few things don't add up in your post...
You have a Dev Edition, so to root you unlock the bootloader, flash TWRP, boot into it, and when it prompts you too, allow it to root (or if you don't get rooted, install SuperSU while booted to TWRP). IN that state, a Factory reset doesn't remove root. So did you root by some other method? If so, that is why the OTA is failing.
Next.. you say you did a tether hack that was just replacing a file. Did you put the ORIGINAL file back? If no, that will cause the OTA to fail.
The only way to really know exactly why is to NOT install the OTA, instead just download it. Move the OTA zip from /cache to your /SDCard (which takes root) after it finished downloading. Again Do NOT install it the "normal way". Make sure you have a working STOCK Recovery on your phone. Manually boot to stock recovery and apply the update zip via the menu options. When it errors, it will pause and tell you why, what caused the issue. You need to correct it and try again.
One final option... See -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 you can take some time and read the first post... then skip to Post #2, and use the Requirements section, and Option 2.
Related
I rooted my phone via PwnMyMoto when I first got my Moto X. Then the OTA happened, and I held off on it until someone came out with a new root method (RockMyMoto). So I used the Moto X Toolkit to restore my recovery.img from a file titled "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml" and proceeded to take the OTA. However after my phone finished rebooting, I got an error message saying something to the effect of "the software update has failed!". But I checked my version #s and they seemed to be up-to-date with the OTA, and I can't pull any more software updates... and my root was gone. I then ran RockMyMoto and all the steps seemed to go smoothly. Can someone confirm that I have the right version #s?
Current: first attachment
"Status: Update Failed": second attachment
Thanks!
ikarios said:
I rooted my phone via PwnMyMoto when I first got my Moto X. Then the OTA happened, and I held off on it until someone came out with a new root method (RockMyMoto). So I used the Moto X Toolkit to restore my recovery.img from a file titled "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml" and proceeded to take the OTA. However after my phone finished rebooting, I got an error message saying something to the effect of "the software update has failed!". But I checked my version #s and they seemed to be up-to-date with the OTA, and I can't pull any more software updates... and my root was gone. I then ran RockMyMoto and all the steps seemed to go smoothly. Can someone confirm that I have the right version #s?
Current: first attachment
"Status: Update Failed": second attachment
Thanks!
Click to expand...
Click to collapse
idk what flashed and what didn't flash when you tried to take the ota but it doesn't seem to have flashed everything or maybe anything. Your FW is still .51 not .57 which is the ota FW version. restoring recovery might not have been enough because if your /system was changed by any rooted apps then the update would have failed (which is probably why it did). There are several options for how to take the ota, and you would benefit the most from learning how to use fastboot/adb instead of toolkits because then you will know what is done and what hasn't been done. you can also just flash the ota to your phone as well instead of taking through the phone itself. You will lose your data flashing it though. But if you want to take the ota, just flash recovery.img and system.img in fastboot and then put the "ota file" in your /cache folder. Do some reading and you can solve your problems and won't run into close to as many in the future because you will actually know whats going on with the phone instead of using toolkits for the phone.
Today my XT1068 offered me the 22.26.1.en.GB update, but it's failing to install.
The phone reboots and attempts to install the update. The progress bar gets to approximately 1/4 to 1/3 of the way across before a red triangle appears and the phone reboots back to KitKat.
My phone was rooted (using SuperSU), but I used SuperSU's built-in clean-up feature to unroot my phone before applying the Lollipop update.
The bootloader is unlocked, but the recovery is stock; I did not install a custom recovery but instead booted TWRP temporarily to install SuperSU.
I'm comfortable fiddling with adb and fastboot, and with digging around the filesystem. Any suggestions of where I can look to find any error messages which might shed some light on why the update failed? Could the failure be related to the previous rooting of my phone, or could something else be breaking the update?
@Loganberry
Have you modified /system files in any way?
If yes you have to restore them back.
If nothing helps, with unlocked bootloader it's propably much faster to just flash your stock firmware again and do ota than to search why it doesn't work.
I can confirm that ota update can be performed on rooted phone .I was thinking that is not possible but I was curious and tried.
I was on unlocked bootloader and rooted KK , german firmware 21.85.23 with instaled xposed framework and gravity box.
Update was successful without any error and for now everything work ok.
Loganberry said:
Today my XT1068 offered me the 22.26.1.en.GB update, but it's failing to install.
The phone reboots and attempts to install the update. The progress bar gets to approximately 1/4 to 1/3 of the way across before a red triangle appears and the phone reboots back to KitKat.
My phone was rooted (using SuperSU), but I used SuperSU's built-in clean-up feature to unroot my phone before applying the Lollipop update.
The bootloader is unlocked, but the recovery is stock; I did not install a custom recovery but instead booted TWRP temporarily to install SuperSU.
I'm comfortable fiddling with adb and fastboot, and with digging around the filesystem. Any suggestions of where I can look to find any error messages which might shed some light on why the update failed? Could the failure be related to the previous rooting of my phone, or could something else be breaking the update?
Click to expand...
Click to collapse
flash the GB 4.4.4 in my signature then try to update OTA again
dpdp73 said:
@Loganberry
Have you modified /system files in any way?
If yes you have to restore them back.
If nothing helps, with unlocked bootloader it's propably much faster to just flash your stock firmware again and do ota than to search why it doesn't work.
Click to expand...
Click to collapse
reefuge said:
flash the GB 4.4.4 in my signature then try to update OTA again
Click to expand...
Click to collapse
Yeah, I'd forgotten about Busybox and a couple other apps which modifed /system. Reflashing from scratch was the easier option.
I flashed GB 4.4.4 as advised and the Lollipop update then applied without any problems. Thanks for the assistance.
Hello, I just today found out about the update to the Lollipop 5.0. I checked and attempted the download. It got all the way to the restart and install and then it stopped and instantly booted back up. It came up with the notification "Update Interrupted" or something very similar. I tried again after resetting the phone back to factory mode. It did the same thing. I have seen people have the problem of not enough storage but i had plenty. Especially after the factory reset. I know that this is an over wifi update and i am trying to understand why my phone isn't accepting it or why it isn't working. Thank you for any help you can offer.
Alan1727 said:
Hello, I just today found out about the update to the Lollipop 5.0. I checked and attempted the download. It got all the way to the restart and install and then it stopped and instantly booted back up. It came up with the notification "Update Interrupted" or something very similar. I tried again after resetting the phone back to factory mode. It did the same thing. I have seen people have the problem of not enough storage but i had plenty. Especially after the factory reset. I know that this is an over wifi update and i am trying to understand why my phone isn't accepting it or why it isn't working. Thank you for any help you can offer.
Click to expand...
Click to collapse
If you have rooted or modified the system apps in any way then the update is going to fail. You have 2 options:
You can wipe your phone and start with a clean stock ROM; or
You can follow the guide to retain root on OC6. You don't have to be rooted for this method, but this method will allow you to update if you've modified your system.
Devo7v said:
If you have rooted or modified the system apps in any way then the update is going to fail. You have 2 options:
You can wipe your phone and start with a clean stock ROM; or
You can follow the guide to retain root on OC6. You don't have to be rooted for this method, but this method will allow you to update if you've modified your system.
Click to expand...
Click to collapse
My system has been rooted before but it no longer has root access.
When you say wipe and start with a fresh rom, isnt that also the same as resetting the device?
Alan1727 said:
My system has been rooted before but it no longer has root access.
When you say wipe and start with a fresh rom, isnt that also the same as resetting the device?
Click to expand...
Click to collapse
To explain a bit further, the way the update works is there's a program built into the OTA. This program checks the signature of all the system files on your phone against a database included in the OTA. If all the signatures match then the update will proceed, but if even 1 of the signatures doesn't match then the update will fail as you have experienced.
When you root your phone you are exploiting a weakness in some aspect of android that allows you to modify system files. Once you modify system files by rooting you change their signature. Even if you unroot, it is impossible to change the signatures back to what they originally were. This is the reason that even if you unroot the update will fail.
By resetting the device you are essentially deleting all the user apps and settings, the system files go virtually unchanged. So if you unroot, your signatures still don't match and when you factory reset the device the system files don't get touched so the signatures still won't match. The only thing you can do to get the signatures to match is to flash the NE3 full Odin package. This will completely wipe out our phone and install everything (the bootloaders, modems, system files, etc.) from scratch.
So like I said you have 2 options:
Follow the guide I linked to above; or
Flash the NE3 Odin package and take the OTA.
Either way you have to use Odin at some point.
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
aeb401 said:
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
Click to expand...
Click to collapse
Try using your favorite applications manager for root and freeze MotorolaOTA. This will prevent the update from being downloaded and you won't get messages about installing the OTA update.