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
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.
Hello!
I was trying to apply the Stagefright OTA on my XT1058, but I soft bricked it. Whenever a new update comes out, I prefer to flash stock image to avoid any unecessary issues that may arise from dirty flashing and not having the system requirements to apply the update without having problems. So that's what I did:
- I flashed the 5.1 stock image for my carrier (Vivo) using RSD and it worked fine, phone booted normally and etc.;
- I skipped the Google account setup and got the Stagefright OTA notification. Since I had already downloaded it before, I wanted to test it by sideloading it from Recovery. So I did it, I entered recovery mode and sideloaded the OTA. All went fine, no errors in the log. Rebooted phone. New bootanimation. Apps optimized;
- But I was getting 'gapps process has stopped' error and couldn't log into my Google Account, so I decided to reflash the stock image (I guess this was my error) using RSD;
- gpt partition flash fails;
- Phone stops booting, it just gets to the recovery menu or to the 'No command' screen;
- I tried flashing everything manually, doesn't work;
- I tried flashing gpt.bin from a Brazilian Retail firmware. It flashes without errors, but phone doesn't boot either;
Is there a way to recover from that? I have a TWRP backup from before I started all this process, but it looks like I can't restore it because my PC doesn't seem to recognize the sdcard when mounted.
Thanks in advance!
EDIT: managed to restore it using the steps from option 5 in Mark Venture's guide here. It was the only one that worked. BUT I had to flash gpt.bin and fsg.mbn from the OTA zip. Only then the phone booted. Then I took OTA normally and it installed without any hassle. So it looks like hash mismatches do not happen in this version of the firmware.
Hi. I had miui7 running on my Mi3 and I wanted to run cm13. I used cm12 before but went back to stock miui7.
But I needed to update baseband to update to cm13 so i used the cm13update.zip from jrizzoli.github.io/dotfiles/ and it had TWRP (modified maybe?) as the recovery and I easily installed CM13 after that. Later I updated via OTA several times and it went fine until the last time when it would not boot anymore and would stay stuck in bootloop or if i went to recovery, it would start installing the last cm13 update and then end with error 7 and would give system partition has unexpected contents error.
I tried to do EVERYTHING I could to make the phone show ANYTHING other than the cm13 updating in recovery screen or the ANNOYING cm13 logo. NOTHING worked.
I tried using miflash to flash old kitkat 4.3 rom, 4.4 rom (would give partition error but i replaced the flash_all.bat from a tutorial to bypass the partition erro) and the latest 6.0 chinese developer rom and it would finish successfully within under 100 seconds and would either go back to the cm13 bootloop or go to recovery and update cm13.
I tried QPST and emmc download with 4.4 rom and it would end with no error and go right back to bootlogo. tried flashing that rom with miflash and it would end within 80 seconds and go back to boot logo.
I tried QFIL with the latest miui8 chinese dev one with firehose and it would fail when it would go near userdata. dont remember the exact error but it was something like cannot divide by zero.
The ONLY time i could flash a different recovery is when i would use the same cm13update.zip and replace the recovery.img with another img such as cwm or mi stock recovery. when i used cwm, it would also try to install cm13 and fail as well.
I tried taking the battery off and shorting the two points which made it easier to get into EDL mode to try to use QPST with no luck.
among so many tries I booted to cm13 a few times. never could it go to homescreen though. once it would not go past the password lockscreen even if i put in the proper password and another time it would but ALL the apps would crash and i would not be able to even swipe the home screens.
sometimes when i tried flashing the cwm ota roms that was in the phone previously or the latest cm14 with otg usb, i would get
INSTALL ZIP SUCCESSFUL on top of twrp but the whole screen would fill up with red writing which said
Error opening : 'data/data/cyanogenmod.platform' (no such file or directory)
and the same thing about every app that was there on the phone.
i do not care about my files theyre all backed up. I just want to use the phone again. Any help is appreciated. thanks.
bump
Hello there, I can make and upload twrp backup of miui v8 dev version. Have you tried to restore a backup?
You'll have to make new partition for this backup ( there are so many threads like "extend partition mi3" or smth like that)
http://en.miui.com/thread-99430-1-1.html
Tried the ones from this thread?
http://forum.xda-developers.com/xia...instruction-to-restore-mi4-mi3-t3279927/page5
Hey all,
after a long time i've came back on xda and i rooted my android phone (rog phone 3). easy steps all done right.
then apps started to suddenly crash, i've flashed RAW 17.0823.2102.143 everything is still ok (unrooted state)
but when i press check for system updates nothing appears so i guess no OTA updates anymore ?
is there a way to completly revert to stock with ota ?
so i figured out there's a new firmware Version WW-17.0823.2104.147 on the website of asus and when i download it, its in a zip format. Already tried to put the firmware zip onto the root on my phone storage and nothing pops up (according to what i could find from asus was to put zip onto the root folder and restart would update to the firmware but nothing happened)
all goes fine with the newest firmware with TWRP (tried this method but had to relock bootloader)
but i want everything back to stock with ota if that is possible please someone help me out with this
*Edit: firmware zip did work eventually after several restarts, but still not sure about the ota