XT1053 OTA 5.1 update unsuccessful - Moto X Q&A

Hi
I've run into a problem while trying to update my Moto X (gen 1) XT1053 from 4.4.4. to 5.1. through standard OTA update. Here is the scenario:
- My phone is not unlocked or rooted, nor does it have modified firmware of any type. It is a fully stock XT1053 purchased directly from Motorola in the US that I have not tinkered with in anyway
- My phone downloaded and applied the update on Saturday morning and after the first section of the install rebooted. It sat at the screen with the M and "powered by android" at the bottom and vibrated once, then the screen went off, the same screen came back on and the phone vibrated again. Then an Android on it's back with a red exclamation and "Command" was shown.
- I figured out how to get into the recovery menu and wiped the cache, rebooted and no change. I then attempted to factory reset the phone, it did this but again no change.
- I spoke with a Motorola chat representative who was unable to help but I managed to follow some instructions on this forum to enter the fast boot menu, download and re-flash android stock 4.4.4 using RSDlite and get the phone working again.
- The phone attempted to apply the 5.1 update again yesterday and encountered the same issue again.
Would anyone have any ideas about what could be going wrong with the update process? Or ways that I can go about getting this to install correctly. The motorola rep seemed to think it was to do with my carrier, but as it was downloaded over wifi can this be the case?
If not, would anyone know how to stop android from continously prompting me to update to 5.1? I'm happy to remain on 4.4.4. if it means the phone will still remain functional.
Thanks in advance for your help.

Did you try going to settings and about phone, update
Sent from my Nexus 4 using Tapatalk

Correct, the update was applied through settings > about phone > system update

Delta117nz said:
Would anyone have any ideas about what could be going wrong with the update process? Or ways that I can go about getting this to install correctly. The motorola rep seemed to think it was to do with my carrier, but as it was downloaded over wifi can this be the case?
If not, would anyone know how to stop android from continously prompting me to update to 5.1? I'm happy to remain on 4.4.4. if it means the phone will still remain functional.
Thanks in advance for your help.
Click to expand...
Click to collapse
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4

dtg7 said:
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
Click to expand...
Click to collapse
Thanks dtg7, I'll give that a try in the next day or so (updating via the recovery menu) otherwise will hold out for the 5.1 firmware and try RSDlite again.

dtg7 said:
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
Click to expand...
Click to collapse
Worked perfectly downloading the OTA update and applying through the recovery screen. Thanks for your help

Related

5.01 OTA disapeared

I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
You're not alone. Several threads on this in general forum and Q&A. Consensus so far is hang tight and the update should resurface.
Sent from my Nexus 6 using XDA Free mobile app
Factory image is still on Google website. Grab it there.
bluh5d said:
I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
Click to expand...
Click to collapse
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
If I manually flash the image will it change where my future otas come from ? Like doesnt a motorola nexus 6 updates come from a different server than a google play nexus 6 ?
Same thing for me, except I was waiting to be able to charge up my phone before installing. By the time I got to a charger it was gone. I'll probably just wait for it to resurface.
Same same here. Fully stock. Is the common theme for people experiencing this that they are on VZW? I am. Tmo bought phone with VZW sim.
Fyi, rebooting and charging havent helped.
I know i can manually update, but I'm hoping to confirm that the OTA process still works correctly with my stock phone running on VZW.
Its not only VZW.. I'm T-Mobile and the same happened
SirRastusBear said:
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
Click to expand...
Click to collapse
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
mlevin said:
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
Click to expand...
Click to collapse
Flashed each separately.
Flash bootloader image
Reboot bootloader (important)
Flash radio image
Flash recovery image
Flash boot image
Flash system image (takes a while)
Flash userdata image ONLY if you want to wipe your own data
Reboot when done
Flash custom recovery
Install SuperSU from custom recovery
Reboot
Profit
Cheers
Those like me who don't want to manually flash.. I just got off the phone with Google, and apparently within 24-48 hours the update will be available again for those devices affected by this hiccup. I'll wait.

[Q] XT1092 in bootloop after update

So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.
Seems you need a .19 stock system partition image to get rid of the bootloop. Hope somebody can backup his system after OTA and share his image,otherwise you have to wait for official release or take risk to downgrade.
----------------------------
If you can boot from TWRP, you can try put the Xposed-Disabler-Recovery.zip in an USB SD card(maybe need formatted to particular filesystem like ext4) linked your phone with otg cable,then mount the sdcard and flash the zip file via TWRP.
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
HAXTREME said:
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
Click to expand...
Click to collapse
Thank you! This seems to have solved the problem (whatever exactly it was) and the mobile data is fine which was what I was most unsure about.
I'm curious, my device was a XT1092GB (or at least, I believe it was a GB) and now shows as a 'reteu' where I believe it used to show as 'retgb'. This isn't a problem as it all seems to work, but should I be expecting the Lollipop OTA update to come through? I deliberately didn't follow through on the last part of that thread and install 5.0 that way, I didn't want to tempt fate! However, I would like the update if possible and am unsure which way to go about doing it.
Again, many thanks for all the suggestions everyone. This is why android is awesome
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
HAXTREME said:
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
Click to expand...
Click to collapse
I guess even if the 5.0 OTA doesn't come through (for the reasons as given here, any following OTA updates should be fine, right?
If not, do you reckon then 5.0 rom given in the link you sent would be appropriate or would this be a better route?
Thanks for the help!

[Q] My Pure Edition has Insomnia w/ the 5.1 OTA

I have a Pure Edition that I recently updated to the 5.1 OTA but I'm having problems with the screen never auto-sleeping.
Easy Stuff:
I have it set to sleep at 2 minutes and my dev setting for always-on-while-charging is turned off. This behavior happens whether it's charging or not.
History
Phone is Unlocked
It was running the first 5.1 Soak Test (i.e. the one that couldn't directly run this OTA)
I downgraded to the 5.0 factory image
After the downgrade, it immediately picked up the OTA and installed without a single visible problem.
I did a factory reset (via settings menu) just to start from a clean slate once on the 5.1 OTA image.
It is still unlocked but I have never rooted/modified this 5.1 OTA. I want it stable before I mod anything. I even still have stock Recovery.
So my assumption is that given that the 5.1 OTA image installed successfully, that's proof that I did a proper/complete downgrade to the 5.0 image. Is this correct?
Any other thoughts on what to look to before starting down the downgrade/wipe/etc. path again? I spoke to a friend who also has a Pure Edition that just went to the 5.1 OTA and he's not having no problem at all like this.
I'm really just guessing here but perhaps it could be an issue with attentive display. Maybe try turning it off to see if it will turn off.
Sent from my XT1095 using Tapatalk
Jaxidian said:
I have a Pure Edition that I recently updated to the 5.1 OTA but I'm having problems with the screen never auto-sleeping.
Easy Stuff:
I have it set to sleep at 2 minutes and my dev setting for always-on-while-charging is turned off. This behavior happens whether it's charging or not.
History
Phone is Unlocked
It was running the first 5.1 Soak Test (i.e. the one that couldn't directly run this OTA)
I downgraded to the 5.0 factory image
After the downgrade, it immediately picked up the OTA and installed without a single visible problem.
I did a factory reset (via settings menu) just to start from a clean slate once on the 5.1 OTA image.
It is still unlocked but I have never rooted/modified this 5.1 OTA. I want it stable before I mod anything. I even still have stock Recovery.
So my assumption is that given that the 5.1 OTA image installed successfully, that's proof that I did a proper/complete downgrade to the 5.0 image. Is this correct?
Any other thoughts on what to look to before starting down the downgrade/wipe/etc. path again? I spoke to a friend who also has a Pure Edition that just went to the 5.1 OTA and he's not having no problem at all like this.
Click to expand...
Click to collapse
Chill bro.. Its a usual bug.. Nothing to worry.. Clean the partition cache in recovery.. You are good to go...
One of my friend did a factory reset in 5. 1 and had this problem...
Sent from my XT1092 using XDA Free mobile app

Update Questions

I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?
Asisentr said:
I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?
Click to expand...
Click to collapse
I'm in the same boat (although mine is not dev edition, I have unlocked the bootloader & rooted running xposed) and would love an answer!
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
You can't update if you've modified the system partition, ex. being rooted, having xposed etc.To update you need to be completely stock.
I received the same notification on my XT1060DEV. I chose to ignore it.
Anyone know what the update is for? Someone posted in the general section to "never update a rooted unlocked XT1060 ever" because it bricked it or something. My guess is they didn't know what they were doing. I've been having issues lately with my XT1060 not wanting to connect to 2.4GHz wireless networks, only 5GHz. I've tried removing apps one-at-a-time but no luck. Maybe a reset back to square one and the update is due.
Not sure what the update is for though.
So I'm unlocked and rooted on 5.1 with TWRP... but I don't have stock recovery. XT1060 verizon dev edition doesn't have a stock recovery for anything but 4.4.4. So how do I flash recovery to take the update? I'm assuming that flashing recovery from 4.4.4 is a bad idea? If so, what's the solution?
i have 2 1060s one is retail 16 gb (one daughter) the oher is 32 gig dev tooted twrp expoesd. dev daugher tried to do the update it failed and hten she rebooted. it kept tying to apply booting to recovery after 3 minutes and and failing until I removed the update form cache.
I shoul have captured it so I could examine and fix the script.
retail 16 gb updated just fine.
anybody know what this is?
if it not an image maybe we can apply the frixes directly
Mike7143 said:
Anyone know what the update is for?.......
Not sure what the update is for though.
Click to expand...
Click to collapse
Its the security update patch upto 1st April, 2016.
https://motorola-global-portal.cust...detail/a_id/110538/p/30,6720,8696/reg/1417809
I'm on completely stock 5.1 ROM but I have TWRP 2.8.7.0, Xposed installed. So in order for OTA to succeed I'll have to undo all the modifications including the removal of Xposed? The other changes I've made to the system are the removal of some of the Motorola bloatware.
The trick is now to get the right SBF from Motorola.
Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!
Mike7143 said:
Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!
Click to expand...
Click to collapse
Marshmallow?!
So far it's not to bad.
What do you mean by Marshmallow update!? This is just a security update so it should still be Lollipop.
Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
If you are boot-looping after trying the update with TWRP, you will have to delete the update file using TWRP.
From the TWRP main menu, Choose Advanced, then File Manager.
Go into /cache, and delete the Blur_Versionxxxxblahblahblah.zip file.
That'll stop your boot loop.

Root 5.1.1 or 6.0.1?

I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!
ota then root
I OTA'ed, now the phone randomly reboots several times a day, and some apps don't work correctly. Great.
factory reset.
*sigh* I was afraid you were going to say that. Now the problem is backing it up. I have a Titanium Backup Pro license, but I only use it on my old rooted GS2. The Note 4 is not rooted so TB won't run on it. All the rooting tutorials say "back up your phone before you root" but you need root to run TB. Chicken or egg? I guess I could try Samsung Kies, don't know if it will back up everything. My photos are backed up to Google Photos, I guess everything else is replaceable, but I would really rather not have to reinstall all my apps one by one after a factory reset.
That brings up another question: when you to go Settings/Backup and Reset, I have "Backup my data" set to On and linked to my Google account, but nowhere can I find documentation of exactly WHAT gets backed up or to WHERE (it says to "Google servers" but what the heck does that mean? I can't find it on my Google Drive or anywhere else on my Google account dashboard.)
I do greatly appreciate your help, by the way.
You could try reinstalling through kies or smart switch. Make sure to clear caches before and after. And see if that works. If it doesnt help, you could flash recovery, root, try to backup as much as you can between reboots and then factory reset. Your apps should automatically download from play store. But without the titbackup files you'll lose settings and data in a lot of apps that Google doesn't backup.
I unlocked your mum's bootloader.
kydar said:
I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!
Click to expand...
Click to collapse
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.
Shad0wsabr3 said:
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.
Click to expand...
Click to collapse
There aren't that many problems with MM. Just superficial stuff like not having mobile data toggle. The problems you are hearing about a factory reset will fix. Like lag, jankyness, apps loading, phone freezing temporarily. You won't be able to do OTA. It will fail because of root. You need to titanium backup or whatever method you prefer of backing up data and flash through kies, odin or smart switch. Probably easier to go that route unless you only did minor things with root like just block ads, then you can probably get away with flashing stock recovery and then OTA. You still might have to factory reset like I had to even though I flashed whole rom through smart switch. If you have xposed or modified something like swapping recent apps and back key like me, then you'll need to flash marshmallow whole and start over after backing up.
Afaik, you can't downgrade to 5.1.1 unless somebody figured out a workaround or you only flashed everything except bootloader.
I unlocked your mum's bootloader.
@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.
kydar said:
@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.
Click to expand...
Click to collapse
Iv never backed up an unrooted device so I wouldn't know. Glad you nrought that up as Iv been meaning to look into that.
Would you happen to know where the downloaded ota file location is? My phone downloaded it and I keep postponing it.
Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.
Where are the root instructions for completely stock 910T with MM update?
vernj123 said:
Where are the root instructions for completely stock 910T with MM update?
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...overy-n910t-t3-marshmallow-pe3-guide-t3406870
kydar said:
Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.
Click to expand...
Click to collapse
I'm still researching what your dealing with. As for me I found the ota file. For those looking for it this is how and where I found it....
With RomToolbox I went to root browser. Then to data folder and a folder named fota. Within the fota folder is the ota update named update.zip. I erased that and then went into Titanium Backup and chose to freeze both software update files. So far no constant reminders that I have an update ready to be installed.
Hope this may help.

Categories

Resources