Phone got hung up during a super wipe and i held the power button down and turned it off. It felt stupid while I was doing it, but I waited a good 30 minutes and really felt like I didnt have a choice. I can get into my bootloader but not recovery. Keeps rebooting to splash screen. Tried to fastboot flash the recovery image but i get failed remote: not allowed. not sure what else to do. If anyone has any ideas, I would be greatful.
s-off
hboot-2.09.0000
openrecovery-twrp-2.6.3.0-jewel-selinux.img
Nevermind. I dont know what happened. I left it on the splash screen for a while and the boot animation for the rom started. It never did boot, so i went back into bootloader, tried to fastboot flash the recoverery image again - failed. Tried recovery again and it started. Restored my backup - and my phone is back from the dead once again.
Related
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
You should reflash your recovery to TWRP using fastboot. Then boot into recovery using fastboot. From there you should be able to do a complete wipe and flash a ROM. It is outlined in the thread you linked OP and second post. Feel free to come into the d3rp q+a thread in my sig if you need more help.
It worked thanks you
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
unomillionaire said:
It worked thanks you
Click to expand...
Click to collapse
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
joeykrim said:
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
Click to expand...
Click to collapse
So you mean, stuck at the splash screen(HTC with white screen) and reboot again and again is because of the recovery destroyed? My phone stuck at the splash screen for about 10 seconds and then reboot again and again. I have tried to flash many recovery images, includeing twrp 1.0.3, twrp 1.1.1, cwm-1.0.4, cwm-1.0.5, cwm-5.0.2, all failed to boot up into recovery:-(
Thanks in advance!
so yesterday i powered down my phone completely to put a screen protector on it. when i turned it back on i noticed i do not get the red lettering anymore at start up. i am unlocked and rooted with regaw. i booted into the bootloader this morning it shows version 1.12 and says fastboot under that. i had the options to reboot, reboot bootloader and power off i beleive. ... what happened to the option for recovery??? i also updated to TWRP 2.2
p.s. fastboot is turned off in android.
edit: i can boot into recovery from android, but since it is not showing in the bootloader what do i do if i need to get into it from there??
Edit 2: I can boot into recovery from cold boot, but when I try from a warm boot it says fast boot...anyone have any ideas?
That's how it is on this phone. Mine does that too.
ok i was alittle worried at first!
Hello all,
I have followed several tutorials here on XDA, and even more video tutorials on YouTube, but I am stuck at the seemingly simple task of rebooting into recovery. I've rooted every Android device I have ever had, but this one is throwing me off...
I flash TWRP (from adb), erase cache, and then when I'm still in the bootloader, I go to bootloader>recovery and then for a split second I see the HTC logo with the pink "booting into recovery" text then it reverts back to the clean HTC logo and proceeds to reboot into the OS.
I've tried the whole process again and again, and still nothing. It doesn't say "TAMPERED" above UNLOCK (in the bootloader) either.
Any suggestions would be greatly appreciated, and thank you in advance
---
EDIT:
I managed to get it working. I let the phone sit (powered 100% OFF) while I brewed a pot of coffee (1-2 minutes), when I tried it one last time; it listed "TAMPERED" then "UNLOCKED" and allowed me to flash into recovery with no issues. I think the key is to let the phone sit for a bit while it is powered off. [MODs - Feel free to remove this thread if needed]
Interesting thing happened today which has basically put my phone in a death spiral state. The battery died and after charging it a while I went to power it back on and found it in a boot loop state. I can get into the bootloader, but from there if I select recovery it reboots and the white bar on the right side of the screen fails to fill up, then the phone reboots. I've tried flashing two different versions of TWRP from the bootloader and it still exhibits the same issue.
HBOOT 1.12.1111
RADIO 1.12.11.1210
S-OFF
I was running CM10.1 without much issue until the power issue.
Any thoughts?
Thanks to Zanzibar for helping me work through this on IRC. Eventually the steps outlined here: http://forum.xda-developers.com/showthread.php?t=2338391&highlight=boot+loop did the trick.
fastboot erase cache
fastboot reboot
The device started booting but hung on the CM logo for far too long. I hard rebooted and installed an updated version of TWRP and then wiped and flashed the ROM over again. More updates to follow.
Well the device worked for the night but when I rebooted it this morning it immediately began the boot loop situation again. I RUU'd once and it got stuck in another boot loop. I got it to boot after hard powering down and it loaded the factory ROM. I rebooted back to the bootloader and flashed TWRP 2.5.0.0 and tried to reboot. Another boot loop. Hard power cycling didn't solve it either, so I pushed the RUU for a second time. Now the device refuses to boot into anything other than the boot loader -- the initial issue from this post -- and no amount of hard power cycling makes a difference.
The phone is currently showing as LOCKED in the boot loader so I dropped it off at the Sprint store to see if they could find anything physically wrong etc. More updates as they are discovered in the hopes that if someone else ever experiences this, they have something to reference.
Thanks for posting. Did you solve the problem? I think I'm having something similar.
I recently tried a factory reset on my phone after finding that one of my apps was sending out spam texts to random people and racking up my text plan. Upon the first boot, it showed a green android man with a blue orb thing spinning in its stomach and kept going for hours.
My phone was previously running an unofficial build of CM12 and was unlocked and rooted.
Now, I just figured that I could just flash a new recovery to the phone and flash a new ROM to get it back up and running, but I also keep having troubles getting it to flash. Using 'flashboot devices', I see my phone's serial, but when I try to use 'flashboot erase recovery' or 'flashboot flash recovery recovery.img' seems to hang up. I finally got it to write clockwork recovery to the phone somehow, but the device still boots to the green android man w/ blue instead of clockwork. I thought it was an issue, so I have been trying to flash TWRP, and it just hangs, and doesn't even give the <waiting for device> text, so I know it sees it.
Can anyone help me figure out a way to get my recovery flashed correctly? From that point, I should be good to go, as long as it loads into recovery.
Tampered
I have tried everything I can think of, and it still stalls while it is supposed to flash the new recovery, then fails with the error "too many links".
Also, now the **TAMPERED** flag pops up at the top of the bootloader. It still lets me into the FASTBOOT portion, so I don't believe that it is effecting anything, so I will probably just have to worry about that later, if I really feel like going through the whole rumrunner/revone process.
TWRP
Not sure if it is a good sign or not, but I replaced the USB cable and was able to get TWRP to install and actually load once. There were errors after it booted, and I choose to do a full factory wipe to hopefully start over fresh, and the phone rebooted itself. Now TWRP seems to endlessly load while it the splash screen flashes on and off, almost as if it is in a bootloop. I tried reflashing with a slightly older TWRP for my phone, and no luck.
Also, another strange thing is that when I flash a new recovery file, it shows that it only takes a total time of 2.607s. If feel like this is quite short and I remember it taking a bit longer in the past. I just feel like it is not writing the entire recovery, hense the blinking teamwin logo that seems to be stuck in a bootloop.