I have had my Droid turbo since launch and as such followed the path the getting root on it for some time. I used Mofo to get root back on android 4.4.4, used it again to upgrade to 5.1 while keeping root, used sunshine to unlock the bootloader when that came out, and finally installed TWRP recovery on it. I had not done much to it since, but had Intended to install cyanogenmod for a while.
Well I thought I would finally get to it this weekend. I made a nandroid back-up with TWRP, copied it to my computer, backed up some files I didn't want to lose, and went ahead and installed the latest version of cyanogenmod 13 for quark (Moto MAXX and Droid Turbo) and the necessary gapps. It all went very well. I booted into cyanogenmod just fine, and signed in to google.
I was in the process of setting things up, like preferences/wallpapers/wigets etc, while google downloaded my apps. Not long after I started doing this, nova launcher would repeatedly crash, as well as cyanogenmod's built in launcher. I got fed up with it and rebooted. But the phone shut down and started acting odd. It would show what looked like the bootloader, but the open android guy was not there, and I had no options at the top. Sometimes it would just say AP Fastboot Flash Mode (Secure) with no other text.
I got it to go to the bootloader after holding down the power and volume down button, and got it to boot to TWRP. But TWRP said there is no OS installed, and it refused to install anything, wipe anything, and TWRP itself crashed after a bit when I left it there to try and use ADB to push my nandroid back up to it.
Now TWRP will not load from the bootloader, and I cannot flash anything. I wanted to just re-flash the stock firmware. So I downloaded fresh copies of it from the root thread here on XDA, but no matter what, i get the error "(bootloader) Failed to erase partition" It does this for anything. I tried flashing TWRP and the fresh system image. I tried following the steps on the root thread that flash things that you need to prepare the phone for the system image, but all attempts to flash fail with the same message.
I also tried using mofo to flash a clean system image. But it just stops and quits at 7%. I have had this problem before, and got around it by using mofo 0.0.2. But I no longer have that version.
I am at a loss here. I need my phone back ASAP. Any help would be much appreciated.
Related
I just got my motorola yesterday. I did quite a few things like unlocking it and rooting it..After my first initial root it worked fine but earlier today i decided to install lollipop. I was using the twrp version 2.7 to install the rom but i realised it wasnt working till i tried a few more time and it finally it. I tried back up my stock 4.4.4 room before i installed my new rom but it failed several times because i think the recovery was faulty to say the least. Anyways my lollipop worked very fine but i notice anytime i restarted the phone it took a long freaking time to restart but it was working normal as usual until i restarted my phone another time and realised i couldn't go past the bootanimation.It takes forever but i never get past it. I then decided to flash the twrp 2.8.0.1. After flashing i realised I could do a backup but it was too late. I tried a few tricks I've always used to get past the bootanimation like mounting the storage but it never shows up on my pc. I also tried side loading the rom using the adb sideload command but it never workedd.it always shows up saying "error: device not found" but when i go back to the bootloader and use the fastbootdevices command it shows up my device. IS there any recovery that will allow me to sucessfully mount my storage or sideload my rom without all this hussle?
rom:TitanPrimeROMv1.3-XT1068-69_RC1
XT1068
Rooted
TWRP 2.0.8.1
Window 8.1 64bit
I already have my mini sdk files
Can you fastboot flash the factory images?
If you can confirm you can get into either bootloader where ADB works or TWRP
i will make you a either a TWRP backup of a clean 4.4.4 GB UK xt1068 restore (boot.img + system folder)
or i will make a ADB mfastboot flashable (in bootloader) of the 4.4.4 GB UK ROM
LMK which you need/prefere?
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
Hi, I updated my rooted OnePlus 3t with an OTA update (dumb, I know, I wasn't thinking). It failed and the device needed to be wiped. I've since tried to go through the process to reinstall twrp and supersu and I can no longer get it to boot when TWRP and superSU are installed. The weird thing is, I AM able to use it with the stock recovery and non-root, but any subsequent flashes fail, despite it appearing as if everything has been installed properly.
One last wrench to throw into this: I cannot access recovery (whether TWRP or stock) without running
Code:
fastboot boot recovery.img
. When I run that, I'm able to get into recovery, however if I go through the phone itself on the main menu after unlocking the phone, it just reboots and brings me right back to where I was.
Any ideas on what I may have done wrong and how to fix it? I've been following the guide from the oneplus forums, I've run that process about 5 or 6 times over the past day to no avail.
P.S. Have flashed the newest version of dm-verity
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.
After flashing the latest TWRP 3.3.1 image file from TWRP 3.2.3 and upon reboot I got an error "Could not do normal boot" and it took me to ODIN mode. Thinking maybe it was a corrupt file I flashed the .tar file from Odin and it successfully completed and rebooted into the system. Okay great. So I tried to boot into recovery from the system and it took me back to the same error. Tried several times to flash recovery from Odin and each time it completes successfully, boots into the system. Everything looks great and works - until I try to boot into recovery. Tried powering down completely and giving it a few minutes but the same thing happens when I power up. the only way I can get back into the system is to flash the TWRP tar file again from Odin and let it boot the system upon finishing.
I have searched the forums and the web without finding any solution that doesn't include going back completely to stock. In those cases the system was corrupted as well. Not really wanting to do that since everything works except booting to recovery. Any suggestions?
Update - I was finally able to download XAR-T813XXS2BSJ3_T813XAR2BSA2-20191016 and install it so I currently have the latest stock I can find for my T813. I have not tried to install TWRP yet on this version. I am a little leery to do so at this point since I've had no luck on any previous attempt.
Well, SSDD! No matter what version TWRP I flash, when I try to boot into recovery I get "Recovery Booting....Could not do normal boot" and it takes me to download mode (Odin Mode). I give up. I guess I am doomed to using a stock tablet and all of my previous apps and set up is no longer accessible. If by some miracle somebody has a fix I'm all ears.
Update - Finally was able to root with CF-Auto-Root through Odin. While it is not my root method of choice it is the only way I can root since TWRP will not load for me. At least I can get to my TB backups and restore most of my apps. Also, I can get rid of the bloat that pure stock sticks on the tablet. If I hadn't just bought a new laptop, I would seriously consider replacing this tablet.