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.
Related
Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'
Hi all,
I'm trying to install Cyanogenmod following techbeasts.com tutorial but I'm stuck at the first step : installingTWRP (or CWM).
I followed precisely all the instructions (I allow debugging mode, I installed samsung drivers, I start the phone in download mode, I connect it with OEM cable, I start Odin, it sees the phone, I select the tar.md5 file.), Odin confirms it went well (green box writing "PASS"), but when I try to boot the recovery mode by holding Volume up + Home + Power it seems to boot another recovery software that doesn't offer a backup or a flashing options: "Android system recovery <3e>"
Can't get it to run TWRP or CWM... Can't install the supersu package.
What I'm I doing wrong? Can someone help?
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
adbhitman said:
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
Click to expand...
Click to collapse
Great it worked, thanks a lot !
But now I'm stuck on the next step : flashing CM11
I rooted my phone, booted TWRP, chose "install>cm11" (the zip downloaded from nova fusion) but it says "failed" after a few sec...
I would post my TWRP log but the forum prevents me doing so...
Well I get few things that you could check first.
1. Do factory reset for example from twrp. Factory reset is needed/recommended before installing custom rom from offical OS.
2. Sometimes just installing fails almost immediately if you have ticked check zip signature.
After you have installed new rom clear cache and davilk cache just in case. I'll do that every time if I install or update custom roms. Also don't forget to install right gapps package after you have installed rom.
Sorry my english and try to understand.
ok just realized i downloaded the wrong cm image (the odin one, not the recovery)
everything running smooth now
Okay happy to hear that everything is fine now. Happy playing with custom roms
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 was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.
Hello, I've been trying to bring back to life this old XT1068.
In the past years, I had installed several ROMs until one day the phone stopped working (probably I made some mistakes like flashing something not supposed to be flashed on this device, probably) and since that moment if I turn it on it remains stuck on the boot animation (the coloured google dots moving...).
I tried everything. I have TWRP 3.1 installed, I tried to wipe everything, I tried factory reset, I tried to erase the internal storage, I tried to install new ROM, including a stock ROM and the stock recovery. The result is always the same: no errors at all in TWRP, but it's like nothing changes. It does not boot and if I go to TWRP I can still see files that I put in the phone years ago, after I tried every possible wipe. Imagine that I still see the WhatsApp folder of years ago.
As I already mentioned, I also tried to flash a stock recovery: the process finishes without errors but if I reboot to recovery, I always end up in TWRP.
The only thing I can do is to reboot into recovery or fastboot.
The phone is recognized by the computer ("adb devices" / "fastboot devices").
Does anyone of you guys ever experienced something like this?
Thanks in advance.
I have exactly the same issue. Did you find a solution?
I never got that problem, is pretty strange, i think some zip you flashed before is still installed automatically, for example, there is some option on supersu called survival mode, if you enabled that, i think an supersu uninstaller zip could work, also you can try to install any rom, install supersu and check on supersu settings
---------- Post added at 07:15 PM ---------- Previous post was at 07:14 PM ----------
Also probably some partition got damaged or anything, i recommend to flash an stock rom that flashes many things except for nvdata and nvram partitions because it could make you can't get signal if those partitions are from another zone
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
eagledipesh said:
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
Click to expand...
Click to collapse
Hello!
I`ve done the process to install via mfastboot the stock IMG, no errors at all. When the phone reboots it goes into the previous installed rom boot animation and stays there at bootloop.
I even tryed to install an updated TWRP recovery (3.4) via fastboot. Is shows "OK" but when it loads it is still the previous version.
It looks like the phone is "write pretected".
Any further suggestion?
Thanks in advance.
Allisson
Same problem here. I can accces the fastboot menu via "VOLUME DOWN + POWER" but whatever I try, the red error message comes up. I can boot into twrp via USB/PC but i cannot install it. I cannot factory reset.
when I reboot from TWRP I come to lineageOS boot loop.
ANY IDEAS?