My phone is rooted running a stock 5.1 ROM.
I just got a prompt to install a system update with a security patch, etc so I clicked to install but it gets stuck in TWRP recovery instead of installing the update.
So now every time my phone boots up it restarts trying to install that update.
EDIT: Ok, after a couple reboots the update cancelled on its own. Now I'm wondering if there's any way I can still install this update without it getting stuck in TWRP.
kloan said:
My phone is rooted running a stock 5.1 ROM.
I just got a prompt to install a system update with a security patch, etc so I clicked to install but it gets stuck in TWRP recovery instead of installing the update.
So now every time my phone boots up it restarts trying to install that update.
EDIT: Ok, after a couple reboots the update cancelled on its own. Now I'm wondering if there's any way I can still install this update without it getting stuck in TWRP.
Click to expand...
Click to collapse
In twrp erase cache. That will erase the update file that downloaded.
Sent from my XT1095 using Tapatalk
Thanks yep that's what I did so it boots fine again. I read in another thread some issues people are having with installing this update if their phone is rooted so I'm just gonna skip it. I've grown tired of all the hoop jumping Android requires.
kloan said:
Thanks yep that's what I did so it boots fine again. I read in another thread some issues people are having with installing this update if their phone is rooted so I'm just gonna skip it. I've grown tired of all the hoop jumping Android requires.
Click to expand...
Click to collapse
If you have a custom recovery, you can flash this rom:
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
It has the latest stagefright patch now, and it has OTA disabled to prevent bricking issues for people that have downgraded systems or systems that are modified with root/xposed/busybox/etc.
Before I do that, will I have to reinstall my apps or change all of the system settings again? Sorry, it's been a while since I flashed a ROM, I can't remember what's affected.
You shouldn't need to factory reset considering this is a stock rom and you are coming from the same android version. 5.1 to 5.1. But the fact that your phone had issues before may be an issue. You can try it without factory reset since it won't cause any damage to see if it works.
As far as what is modified, it should only be system apps. Anything you installed or configured should remain the same as long as you don't factory reset.
Sent from my XT1095 using Tapatalk
You have to go back to stock rom first to ensure you have system partition 100% stock. You can just flash the system.img and recovery.img, then apply the OTA. If you want to do it from twrp, you dont need flash the recovery.img and apply the zip file from romracer.
Sent from my XT1095 using Tapatalk
I had the same problem. I cleaned cache and was able boot properly. But now my phone asks me to update every 2 minutes and it is annoying the crap out of me. If I unroot and remove TWRP, will I be able to update to this OTA.
Related
Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?
Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.
mrcobain said:
Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?
Click to expand...
Click to collapse
Flash stock recovery first.
MediocreFred said:
Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.
Click to expand...
Click to collapse
i think you have to install stock recovery and maybe relock bootloader
skinsfanbdh said:
i think you have to install stock recovery and maybe relock bootloader
Click to expand...
Click to collapse
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.
MediocreFred said:
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.
Click to expand...
Click to collapse
abort and restore you backup
Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)
MediocreFred said:
Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)
Click to expand...
Click to collapse
you may be able to get it to install if your on a stock rom but im not sure about it
Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.
MediocreFred said:
Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.
Click to expand...
Click to collapse
or just flash the ruu for your phone
But, doesn't flashing the RUU wipe apps/data? I'd like to do this in the least destructive way possible. If I can get away with just flashing original recovery, installing the OTA update and flashing CWM back, I'll be happy.
yes it will. if you can get away with that then go for it
I have cwm installed on my htc one and I couldn't ruu my one back to a stock image. It would freeze up during the flash image process in the beginning.
No harm in trying the 401 or 707 recoveries ... if OTA doesnt work, just hard reboot and flash another
AND REMEMBER - NO NEED TO RELOCK FOR OTA UPDATES !
Ok got this to work and here's how, it goes without saying that this was my experience and the steps I used and I by no means accept any responsibility for any of these steps functioning on any other device...
I was using TWRP 2.5 and was rooted but otherwise was still on the stock rom that my developer edition shipped with.
I went here and downloaded the stock recovery for .16.
I opened the rar file which included other bat files to push the recovery but I didn't use that. I went to the fastboot folder and pulled the recovery.img file and dropped it in my M7 all in one tool kit folder under data and recoveries.
I then plugged in the phone and opened the toolkit and flashed my own recovery and followed the directions in the toolkit. After reboot the device came up and wanted to load the update which I let it do.
It went through and loaded and the scroll bar went all the way to the end and stuck. I waiting ten minutes and when it didn't restart I held the power button for about 15 seconds (until buttons stopped flashing) and the device screen went blank and I let go of the power button.
At this point it went through a couple screens where it appeared to be loading the update. Scroll bar went to the end and the device restarted and did that again. On the third restart it did a full boot and was good.
I then went back to the toolkit and flashed the TWRP recovery and then after reboot I went into recovery and flashed supersu to get root back.
Not sure if this helps anyone but wanted to share my experience...
MG
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
pairustwo said:
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
Click to expand...
Click to collapse
1. - You do not need to unfreeze apps. The apps are still there untouched in the file system, and in recovery the OS hasn't booted enough to know that the apps are "frozen". By the way, frozen apps are basically just tagged in the OS as not available....so with the OS not running (just recovery is), they aren't "frozen" in recovery.
2. - Yes, fastboot to flash stock recovery. Boot to bootloader mode, fastboot flash recovery recovery.img (you don't need mfastboot for recovery, though you can still use it.)
3. - Accept the OTA. Since yours is trying to install, you should be able to boot to bootloader, flash stock recovery and on reboot it will start the install of the OTA. When done and booted.....reflash TWRP if you like.
That would be the way to go, yes.
Flash stock recovery and try to upgrade. If you cannot, try to unfreeze all sys apps. That should do it. ?
OK. So maybe not such a huge PIA as I had thought. I will track down the recovery file and read the instructions for flashing.
Thanks
@pairustwo
Every time another OTA comes out, people who modify their phones ask the same question. I've written up a FAQ based on the past OTA's.. -> http://mark.cdmaforums.com/MotoX-OTA.html if you want to read it to get more info.
Part of the issues you are talking about when taking an OTA is that the OTAs want to patch and replace only SOME files on your phone, so it checks to make sure the update is for your phone and its android version by evaluating certain files on the phone, that they exist and that their check sums match what the update expects.
i.e. change/modify/delete files the OTA update checks before installing, and the OTA will refuse to install.
If it didn't do this, the wrong update could possibly flash to your phone, replacing files with incompatible versions and making a big mess.
So yeah, "getting back to stock" (or as close to it as you can) is always recommended before taking an OTA so the "check" doesn't fail and prevent the OTA from applying.
In the past, freezing apps with Ti Backup was enough of a modification to cause the OTA's to fail. So often it is still suggested to un-freeze those done with TiBackup.
The OTA zip file (as downloaded) will only flash from Stock Recovery. TWRP and CWM for example don't properly process and flash them, so if you try to install when stock recovery is NOT on your phone, you get stuck in a bootloop. Using mFastboot to flash stock recovery back on is fine for those with unlocked bootloaders. Locked Bootloader users, is another matter.
There is a way "side load" the OTA, IF you have stock recovery, your phone hasn't received the push from Moto or your Carrier yet, and the OTA Zip file has leaked. But it still requires you get back to stock, etc. just as if you were getting it OTA.
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
pairustwo said:
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
Click to expand...
Click to collapse
Answered here -> http://forum.xda-developers.com/moto-x/moto-x-qa/dead-android-red-exclamation-t2778189
and I made this -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
i have a tmobile xt1053 and i tried installing the OTA 4.4.4 update. it went right into recovery and didn't update. now everytime I boot the phone up a min or two in, it just turns off into recovery. Is there any way to fix this? I dont care for the update, just want it to stay on. i'm rooted, stock with a few xposed mods.
Unlocked bootloader with custom recovery? If so, taking an OTA will always fail.
killerb777 said:
i have a tmobile xt1053 and i tried installing the OTA 4.4.4 update. it went right into recovery and didn't update. now everytime I boot the phone up a min or two in, it just turns off into recovery. Is there any way to fix this? I dont care for the update, just want it to stay on. i'm rooted, stock with a few xposed mods.
Click to expand...
Click to collapse
There are two ways you can go about it. Either let it load up and install a file explorer (I use Root Explorer)(would have to do this quick). Then quickly go the the cache folder on the root of the sd card and delete the OTA. The other way would be to enter the recovery menu manually and clear cache. The second way would probably be the easiest way. Please note though that you will be prompted to download the OTA again. To avoid this you may want to consider freezing MotorolaOTA 1.0 service.
this is the way to fix your problem
nhizzat said:
Unlocked bootloader with custom recovery? If so, taking an OTA will always fail.
Click to expand...
Click to collapse
Correct. Go here and do what it says to get back to good -
http://www.reddit.com/r/MotoX/comments/2c8vb5/guide_updating_your_bootloaderunlocked_moto_x_to/
in short, you have to flash stock recovery, then let the phone reboot and install the ota, then you can finish by reflashing custom recovery and get root back. good luck!
thanks guys. before I could see your posts i just tried to wipe cache in recovery and it booted with an unsuccessful error. seems to be working now.
I have a rooted Verizon Moto X 2013 Developer Edition (XT1060) with Android 4.4.4, TWRP and SuperSU installed. I rooted the phone so I could install a wi-fi tethering app that I frequently use. Last night I noticed that the Lollipop OTA was available, and being a dumas, I proceeded to download it without coming to xda-developers first to educate myself on the correct process and potential issues with the upgrade (one such issue being whether I will be able to run my tethering app after the upgrade). Consequently, after I downloaded the upgrade, my phone restarted and booted to the TWRP screen, and I don't know where to go from there to complete the upgrade, if it's even possible to do so.
This is my only phone, so it's more important that I get my phone up and running in the next 1-2 hours than it is to complete the upgrade. With that in mind, what should I do next? Is there a way to quickly abort the upgrade process, perhaps by simply deleting the update file "Blur_Version.212.166.3.ghost_verizion.Verizon.en.US.zip" in my cache folder using TWRP's File Manager and rebooting my phone? Or is it possible to complete the upgrade process in the next 1-2 hours? If so, how should I proceed?
By the way, TWRP is displaying the following error messages:
Error executing updater binary in zip '/cache/Blur_Version.212.166.3.ghost_verizion.Verizon.en.US.zip'
Error installing zip file '/cache/Blur_Version.212.166.3.ghost_verizion.Verizon.en.US.zip'
Thanks in advance for helping me recover from my dumas behavior.
The OTA update file does not work with TWRP, IMHO. It only works with the stock recovery.
If you just boot back out of TWRP (boot back to regular system) your phone should still be functional.
kschang said:
The OTA update file does not work with TWRP, IMHO. It only works with the stock recovery.
If you just boot back out of TWRP (boot back to regular system) your phone should still be functional.
Click to expand...
Click to collapse
Thanks, kschang. Your suggestion worked, but not right away, so there appears to be a twist involved that other users should be aware of if they get stuck in the same situation I was in.
As I indicated in my original post, after downloading the update, my phone would power off and boot to TWRP. From TWRP's main menu I would click on "Reboot," then "System." I tried this a number of times, and each time my phone would reboot to what it appeared to be before I downloaded the upgrade, but only for about 10 seconds, then it would power off and reboot to TWRP again--except for just now, when the phone displayed a message that the upgrade had failed and no changes were made to my phone! Apparently the upgrade process has to fail a certain number of times before it finally aborts. I don't know what the number is, but I must have tried rebooting my phone at least 10-15 times before the upgrade process aborted.
So thanks again for your suggestion. It encouraged me to keep trying to reboot until it ultimately worked:good:
I had the same issue with my phone rebooting so I forced the system update app to freeze via Titanium Backup and that seemed to work.
My phone now is kinda messed up though. To get it to boot I have to hold the volume key while powering it up and choose "boot normally". Any time I just restart my phone or power it up while it's off I get a black screen because like the OP I tried to update to Lollipop without reading XDA first. Doh!!
Any first impressions on the update for this phone by the way? Battery life improve or get worse? Can I still use Xposed on Lollipop? Rooting still possible? Wifi tethering for us on unlimited data?
Same situation. Want to upgrade but not sure how now... waiting for an angel to answer my prayers!
daddylonglegs said:
I had the same issue with my phone rebooting so I forced the system update app to freeze via Titanium Backup and that seemed to work.
My phone now is kinda messed up though. To get it to boot I have to hold the volume key while powering it up and choose "boot normally". Any time I just restart my phone or power it up while it's off I get a black screen because like the OP I tried to update to Lollipop without reading XDA first. Doh!!
Any first impressions on the update for this phone by the way? Battery life improve or get worse? Can I still use Xposed on Lollipop? Rooting still possible? Wifi tethering for us on unlimited data?
Click to expand...
Click to collapse
Root is still possible. The only issue i had was after flashing Twrp, if i rebooted the phone and then tried to boot the recovery Twrp was gone. So i reflashed Twrp while i was still in fastboot i selected "recovery" it booted into Twrp and i flashed a SuperSU zip.
After that i could reboot into Teamwin without issue. I haven't tried Xposed yet. Battery life is great on my end.
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
rice923 said:
Same situation. Want to upgrade but not sure how now... waiting for an angel to answer my prayers!
Click to expand...
Click to collapse
The way i did it was to fastboot flash the dev edition 4.4.4 files to unroot. Then i used Verizon upgrade assistant to take the small update that came out awhile ago. After that i factory reset the phone, checked for updates and the first of two updates installed then it updated to 5.1
I reinstalled Twrp and regained root access.
James L said:
The way i did it was to fastboot flash the dev edition 4.4.4 files to unroot. Then i used Verizon upgrade assistant to take the small update that came out awhile ago. After that i factory reset the phone, checked for updates and the first of two updates installed then it updated to 5.1
I reinstalled Twrp and regained root access.
Click to expand...
Click to collapse
Would flashing dev 4.4.4 unroot as well as remove twrp? Twrp seems to be the main obstacle to get past in order to get the update going. If so, I might just do this tomorrow
The immediate way to get out of the failed flash and reboot-cycle is to (quickly) use a file explorer such as ES File Explorer and migrate to your internal cache folder and delete the Verizon flash file. That stops the reboot cycle in its tracks. You'll get the "failed" message before too long, too.
I found I had more like a minute before a reboot occurred after a failed flash. In other words, I'd be stuck on TWRP, clicked to reboot system, it would reboot. Then, I had about a minute to do stuff before it would shutdown/reboot again. During that time, I would just go to ES File Explorer and delete the Verizon update file from the cache folder, and problem solved.
Of course, it will download again shortly thereafter, but won't do anything until you agree to go ahead and install it.
Guess I'm going to have to flash all the 4.4.4 files like stated above to get back to stock (lame!) and then do the OTA updates. I seem to recall someone had figured out how to flash OTA on a previous update without having to go back to stock, though.
rice923 said:
Would flashing dev 4.4.4 unroot as well as remove twrp? Twrp seems to be the main obstacle to get past in order to get the update going. If so, I might just do this tomorrow
Click to expand...
Click to collapse
Yes it would remove Twrp if you flash the stock files.
---------- Post added at 10:34 AM ---------- Previous post was at 10:25 AM ----------
You could take the little update prior to the 5.1 update by reflashing the stock recovery that will stop the bootloop from the smaller update.
I didn't lose root and just reflashed Twrp. Then after a bit the 5.1 update was released so i just took the jump and flashed stock files to unroot, and took the update. Is it possible to update to 5.1 with root and a stock recovery?..... Not sure i was going to try it but didn't
Root is still possible. The only issue i had was after flashing Twrp, if i rebooted the phone and then tried to boot the recovery Twrp was gone. So i reflashed Twrp while i was still in fastboot i selected "recovery" it booted into Twrp and i flashed a SuperSU zip.
Click to expand...
Click to collapse
Verizon MotoX Developer Edition (2013) - I am having the same issue installing TWRP after reverting to stock and receiving/installing the 5.1 OTA. If I try to flash TWRP via fastboot, it doesn't seem to take. The flash shows as a success, but when I reboot to recovery I'm still in stock. I've tried flashing TWRP then using the volume rocker to immediately boot into TWRP, with no success. I've also tried holding down the bootloader key combo immediately after "fastboot reboot", with no success. When I boot up, though, my apps will optimize every time. Am I missing something?
EDIT: Resolved the problem, turns out I was not using the volume up button to enter recovery immediately after flashing...smh
Just signed up for the beta program a couple of days ago, downloaded/installed Preview 4 with no issues. I recall it booting back to TWRP, a script ran in TWRP, and then the phone rebooted back to system. Everything was OK at that point, other than I lost root and TWRP. I reflashed TWRP with fastboot, SuperSU via TWRP, and now I'm back in business.
I got the notification a few minutes ago that Preview 5 was now available for me to install. It downloaded, rebooted to TWRP...and nothing. The script didn't run this time like it did last time. Plus, every time I try to boot back to system it goes right back into recovery.
...help?
Same thing for me. I had to run the preview 4 twrp zip
Sent from my Nexus 6 using XDA-Developers mobile app
Gromlakh said:
Just signed up for the beta program a couple of days ago, downloaded/installed Preview 4 with no issues. I recall it booting back to TWRP, a script ran in TWRP, and then the phone rebooted back to system. Everything was OK at that point, other than I lost root and TWRP. I reflashed TWRP with fastboot, SuperSU via TWRP, and now I'm back in business.
I got the notification a few minutes ago that Preview 5 was now available for me to install. It downloaded, rebooted to TWRP...and nothing. The script didn't run this time like it did last time. Plus, every time I try to boot back to system it goes right back into recovery.
...help?
Click to expand...
Click to collapse
You could flash the stock recovery from a factory image then follow the instructions on this page to flash the OTA which will preserve data, but if you don't care about data you could flash the factory image fromthis page. If you don't need the device ASAP you could also wait for RatchetPanda to upload a flashable system on this thread, but IDK how long that'll be (although he's generally pretty fast).
Good news: got the phone to boot by going to bootloader first, then telling it to boot to system from there. So the phone works again, but the update didn't stick.
Will try flashing stock recovery in a bit. Thanks!
Sent from my Nexus 6 using Tapatalk
mrjiggywiggy said:
You could flash the stock recovery from a factory image then follow the instructions on this page to flash the OTA which will preserve data, but if you don't care about data you could flash the factory image fromthis page. If you don't need the device ASAP you could also wait for RatchetPanda to upload a flashable system on this thread, but IDK how long that'll be (although he's generally pretty fast).
Click to expand...
Click to collapse
One quick question: I have the phone booted back up now, and I can get back to recovery (TWRP) whenever I want. The OTA flash instructions from the first link say to use stock recovery + adb sideload to flash. Can I just flash the OTA from TWRP and not mess with stock recovery? I would assume yes, but I figured I'd at least ask the dumb question first before my phone starts bootlooping on me after a bad flash.
EDIT: Never mind, found the answer: apparently not.
Gromlakh said:
One quick question: I have the phone booted back up now, and I can get back to recovery (TWRP) whenever I want. The OTA flash instructions from the first link say to use stock recovery + adb sideload to flash. Can I just flash the OTA from TWRP and not mess with stock recovery? I would assume yes, but I figured I'd at least ask the dumb question first before my phone starts bootlooping on me after a bad flash.
EDIT: Never mind, found the answer: apparently not.
Click to expand...
Click to collapse
nope
Problem ultimately solved by flashing the zip from here: http://forum.xda-developers.com/nexus-6/general/android-n-preview-5-beta-npd90g-t3421459 (method 1). Everything is working just fine now.