[URGENT HELP NEEDED] Recovery not working, can not boot past fastboot - Verizon HTC One (M8)

I went from stock to unlocked, installed TWRP using fastboot, made a backup of stock, flashed nV RLS 1.1 no problem. Went to install nV RLS 2 today and TWRP screwed up the clean install somehow, it booted, but with FCs everywhere. I booted back to recovery, wiped for another clean install and TWRP did a hot reboot of the sorts, then it would just boot to the boot animation and reboot. Went back into TWRP, tried to restore a nandroid, and it failed. Hot reboot from recovery again. I thought it was just a problem with TWRP, so I installed PhilZ through fastboot. I was able to boot into PhilZ, went to do a full wipe, it started, then hot reboot. I attempted to install nV RLS 2 from Philz, and in the middle of the aroma installer, hot reboot. I reinstalled TWRP through fastboot, and it just does a hot reboot about 3 seconds into it.
I've never had this problem with any other phone. Frustrating. I can't get it to stay in recovery long enough to pull the internal storage to the computer. Any fix for this?
EDIT: Success. I did the RUU back to stock thing, then reinstalled TWRP, then I was able to restore one of my TWRP backups. I posted this at 1:16 AM, and now it's 4:40 am. That was a painful learning experience. I must've messed up one of the partitions somehow. I don't really know.

jova33 said:
I went from stock to unlocked, installed TWRP using fastboot, made a backup of stock, flashed nV RLS 1.1 no problem. Went to install nV RLS 2 today and TWRP screwed up the clean install somehow, it booted, but with FCs everywhere. I booted back to recovery, wiped for another clean install and TWRP did a hot reboot of the sorts, then it would just boot to the boot animation and reboot. Went back into TWRP, tried to restore a nandroid, and it failed. Hot reboot from recovery again. I thought it was just a problem with TWRP, so I installed PhilZ through fastboot. I was able to boot into PhilZ, went to do a full wipe, it started, then hot reboot. I attempted to install nV RLS 2 from Philz, and in the middle of the aroma installer, hot reboot. I reinstalled TWRP through fastboot, and it just does a hot reboot about 3 seconds into it.
I've never had this problem with any other phone. Frustrating. I can't get it to stay in recovery long enough to pull the internal storage to the computer. Any fix for this?
Click to expand...
Click to collapse
what happens if you just do: fastboot boot <recovery name>? i can't say ive had this issue b4, but its something to try

izzaeroth said:
what happens if you just do: fastboot boot <recovery name>? i can't say ive had this issue b4, but its something to try
Click to expand...
Click to collapse
well somehow Philz works for adb purposes. Hot reboot if I try and actually do anything with it though. I'm doing an adb pull /data/media/0 right now. I think I'm just going to do that RUU and factory reset this thing and start over.
edit: fastboot boot twrprecovery.img yields the same results as trying to boot it from the phone.

And from now on TiBu backups are going on the SD card.
Edit: I fixed the problem some 3 hours later. Still don't know wtf happened though. Had to revert completely back to stock to restore a nandroid.

Related

Please help, TWRP took over my phone

This is what I get for trying to do this before I need to get some sleep. I s-off'd my M8 just a few minutes ago, and installed TWRP. Now I can't get out of twrp. If I reboot it reboots right into twrp. So I tried flashing CWM in fastboot mode, and it still boots into TWRP. However if I go into twrp and select reboot into recovery, it reboots into CWM. So if I go into CWM and select reboot system, it goes to TWRP. Somehow I have two recoveries on here. I'm really tired and would love to get some sleep.
Never mind, just installed a new rom.

[Q] Can't get into recovery, can't flash new recovery

Ok, so I have an MZ601. Flashed with R.A.H._TWRPv2.6.3_BigPart_selinux and omni-4.4.2-20140321-1754+0100-everest-HOMEMADE (updated with latest omni versions as they became available).
Everything been working fine until two days ago, when Xoom froze. It had happened before a couple of times and a reboot had solved the problem. Did that, and this time it got stuck in a bootloop, only getting as far as the Omni splash screen before rebooting. Few reboots later, nothing improving, and then it didn’t get past the Motorola M splash screen.
Tried booting into recovery, frozen at teamwin splashscreen. Nothing was working. Rebooted few time, same thing. Connected to power, charged til green, left for extra 30 minutes, tried again, same problem. Switched off. Came back to it today and....
All of the following done via Fastboot:
Tried flashing non bigpart TWRP (R.A.H._TWRPv2.6.3), still stuck at teamwin splash screen. Flashed Clockwork recovery, booted into recovery fine, but couldn’t see memory card. Flashed Clockwork recovery touch version, same problem. Flashed back to TWRP non bigpart, and it booted into recovery fine, sdcard mounted fine, seeing all files. Excellent. Decided to reflash bigpart version, used reboot option in TWRP, it tells me there is NO OS INSTALLED.
Ok, that’s a bit odd. Must be corrupted or something, but might explain the original freeze and bootloop and then not even getting to Omni splash screen. Swiped to reboot. Flashed bigpart version of TWRP. Rebooted into recovery. Back to original problem, stuck at teamwin splash screen. Left it for 10 minutes just to be sure. No joy.
Tried retracing steps, flashing Clockwork recovery. Reboot. Teamwin splash screen. WTF? Try flashing Rogue recovery. Reboot. Teamwin splash screen.
Kinda confused. It’s like it’s telling me it’s successfully flashed but it hasn’t actually done anything. Power everything down, disconnect everything. Start again. Flash Clockwork recovery, reboot, displays teamwin splash screen, sticks. Flash TWRP, non bigpart, displays teamwin splash screen, sticks. Reboot. Flash TWRP bigpart. Reboot, displays teamwin splash screen, sticks.
Walk away in disgust so as not to throw something at Xoom.
Ok, TL-DR recap.
Worked fine for months
Two days ago, froze on Omnirom logo, got stuck in bootloop
After few reboots didn’t even make it to Omnirom logo, stuck on M screen
Flashed TWRP recovery, non bigpart, stuck at teamwin splash screen
Flashed Clockwork recovery, got into recovery, no SDcard
Flashed Clockwork recovery, touch version, same problem
Flashed TWRP non bigpart, got into recovery, could see SDcard and files, rebooted from within recovery to flash bigpart version, tells me NO OS installed
Reboot
Now, regardless of which recovery I flash it goes straight to teamwin splash screen and stays there.
Help
Bump
Come on guys, 100 plus views and no replies? Surely somebody has an idea?
At the bottom of your tldr
Flashed twrp.. booted into recovery flashed bigpart twrp then says no OS.
It will say no OS cause bigpart would have wiped everything to resize the partition.
I've updated my TWRP to support bigpart and a few other things. Grab it from the pined thread by myself flash it and wipe everything but sdcard.
THen from the terminal in twrp type
df
Ensure the system is around a gig if so then you have repartitioned your /system
Then flash your bigpart Rom and gapps should be good to go from there
sent from::§::
Cheers for the reply, but I'd already had it flashed and running fine for about three months, as I said in my first line:
Ok, so I have an MZ601. Flashed with R.A.H._TWRPv2.6.3_BigPart_selinux and omni-4.4.2-20140321-1754+0100-everest-HOMEMADE
Actually, reading that back, it may not have been clear enough that I meant I'd been running it that way for a while.
Oh, also in the TLR, I meant I rebooted so that I could flash TWRP bigpart from ADB/FASTBOOT, not that I flashed it from within TWRP (which is what I should have done since it turned out to be the one and only time I managed to get past the splash screen). It told me there was no OS installed after I flashed the non bigpart version of TWRP and before I rebooted from within the recovery.
My point is I can't get past the splashscreen, no matter what I do, so I can't use any of the recovery / flash options in TWRP. I also can't flash any other recoveries using ADB or FASTBOOT because no matter what I flash it still stays stuck on the TWRP splashscreen when I reboot into recovery, whether I use FASTBOOT REBOOT or reboot using the volume rocker.
runandhide05 said:
At the bottom of your tldr
Flashed twrp.. booted into recovery flashed bigpart twrp then says no OS.
It will say no OS cause bigpart would have wiped everything to resize the partition.
I've updated my TWRP to support bigpart and a few other things. Grab it from the pined thread by myself flash it and wipe everything but sdcard.
THen from the terminal in twrp type
df
Ensure the system is around a gig if so then you have repartitioned your /system
Then flash your bigpart Rom and gapps should be good to go from there
sent from::§::
Click to expand...
Click to collapse
codliness1 said:
Cheers for the reply, but I'd already had it flashed and running fine for about three months, as I said in my first line:
Ok, so I have an MZ601. Flashed with R.A.H._TWRPv2.6.3_BigPart_selinux and omni-4.4.2-20140321-1754+0100-everest-HOMEMADE
Actually, reading that back, it may not have been clear enough that I meant I'd been running it that way for a while.
Oh, also in the TLR, I meant I rebooted so that I could flash TWRP bigpart from ADB/FASTBOOT, not that I flashed it from within TWRP (which is what I should have done since it turned out to be the one and only time I managed to get past the splash screen). It told me there was no OS installed after I flashed the non bigpart version of TWRP and before I rebooted from within the recovery.
My point is I can't get past the splashscreen, no matter what I do, so I can't use any of the recovery / flash options in TWRP. I also can't flash any other recoveries using ADB or FASTBOOT because no matter what I flash it still stays stuck on the TWRP splashscreen when I reboot into recovery, whether I use FASTBOOT REBOOT or reboot using the volume rocker.
Click to expand...
Click to collapse
I'm stuck in TWRP v2.6.3.0(RunAndHide05 Edition) cant mount system, wipe any data tried or install any rom. Tried flashing different recovery via fast boot but stays the same
*No Os installed error
@crazylegs90 did you figure this out man? Im stuck at twrp start screen..

TWRP

When I attempt to go to Cofface's Baidu page to download his 5.1 TWRP version, I get a message saying the content is no longer available. Specifically, Google Translate shows "Lol, you visit the page does not exist." Does anyone happen to have a copy they're willing to share? Or is there some issue with the 5.1 version that would suggest that I shouldn't use it? If I shouldn't ask for some reason, I apologize. Otherwise, thanks in advance.
https://yadi.sk/d/5YI63uiAhz5UD/Recovery/TWRP
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
wpennhokie said:
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
Click to expand...
Click to collapse
Did you unlock your bootloader?
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
wpennhokie said:
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
Click to expand...
Click to collapse
Thats the same problem I have. I used the other twrp recovery https://mega.nz/#!l5kmUByA!41uExNuasZRgLBML9TTSp8myX-_F6UgQZuE2F2BRZUE
This one worked with out boot loops for me. you can give it a shot.
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
I had that exact same problem twice on Kangvip B015. When I would restart it would all of a sudden automatically boot into TWRP every time and never boot into the OS. When that happens, in TWRP make a backup, then Fastboot flash the stock ROM (system, boot, cust, recovery, user data etc) then when it boots do a factory data reset, then reroot, flash TWRP and restore from the backup you made. The OS will boot from your backup. I dunno why this happens, maybe it has something to do with with Kernel.
I've tried it a couple of times now, and I'm still not getting it to boot past TWRP once I flash the recovery. It was able to take a backup with TWRP, but when I restored it, I still had to restore the stock recovery before I could boot into the system. At worst, at this point, I can always flash TWRP, take a backup, flash the stock recovery, and then have my system back. It's a few extra steps, but I think I'll do this until I find a custom ROM that I like. I greatly appreciate the help so far.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
Reflash the stock b106 recovery and wipe user data and cache, Then reflash twrp recovery and restore your backup. It should boot then.
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
wpennhokie said:
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
Click to expand...
Click to collapse
By any chance, did you delete anything from the Cust Folder at any point?
ajsmsg78 said:
By any chance, did you delete anything from the Cust Folder at any point?
Click to expand...
Click to collapse
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
wpennhokie said:
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
Click to expand...
Click to collapse
I don't think so. It's weird how some of us have different problems than others. I've had zero issues with TWRP but lately my screen has been going crazy. My touches don't work, things jump it's like my digitizer is messed up but when I restart everything is fine again. So I reloaded everything and the problem went away. I guess I debloated too much last time.

Multiple recoveries installed

I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
theoden144 said:
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
Click to expand...
Click to collapse
To solve this, you could get phone into Fastboot and flash Dottat's RUU for the M8 - he made several versions.
For sure, add HTC_Fastboot.exe to your ADB folder and use it, NOT regular fastboot.
It will overwrite your previous recovery with stock and fix your phone. Then later, you could flash TWRP 2.8.7 thru Fastboot.
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
cntryby429 said:
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
Click to expand...
Click to collapse
I would flash firmware or ruu, if indeed he flashed recovery to wrong partition, that partition needs the correct one which firmware wlil do, and ruu will 100% do.
Personally I'd run ruu, go to stock recovery and run a factory reset.
theoden144 said:
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
Click to expand...
Click to collapse
Gotta use ADB and HTC_Fastboot.exe
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
theoden144 said:
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
Click to expand...
Click to collapse
Twrp manager is not a safe way to flash recovery because they aren't flashing by block name yet. They are still hard-coded to block number. The partitions have changed during ota already...so the app does hose things up a bit.
Sent from my Nexus 6 using Tapatalk

Oneplus One TWRP Bootloop

Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.
Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?
This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?

Categories

Resources