I love my new phone, but I can't seem to figure out how to access its recovery. I rooted on the first day(way to go, community!) and have confirmed that root access is working. Titanium is doing its thing without an issue.
My question: How do I access the recovery on my HTC EVO 4G LTE? Read on for what I've done so far that hasn't been successful, to avoid the forum back-and-forth.
I installed a custom recovery(twrp), and I want to access it to confirm it actually did install, but it appears that the recovery is not accessed in the same way as with the OG EVO. I've tried holding down one or both volume buttons as the phone powers on, and all that accomplishes is a quick blinking of the HTC branding splash page, and then a black screen for as long as I hold down the buttons(I've held them for as long as three minutes, and the result is the same). As soon as I let them go, the system boots normally, with no option available to enter the recovery.
I tried asking on the #HTC-EVO-LTE channel, but it wasn't much help as the people there aren't as interested in user q&a as they are in development. That's just fine by me. Just a misstep on my part.
+ewalk486 did PM me and advise me to turn on fastboot, which I did. But the behavior is unchanged. Any help would be great.
try using the goomanager
Goomanager, which is what I used to install my recovery, and what told me that the install had succeeded, booted me to the boot menu. I've noted that the phone still says S-ON, which is troubling.
Anyway, I select BOOTLOADER and then RECOVERY, and it just drops me back to where I was. No recovery comes up.
bahua78 said:
Goomanager, which is what I used to install my recovery, and what told me that the install had succeeded, booted me to the boot menu. I've noted that the phone still says S-ON, which is troubling.
Anyway, I select BOOTLOADER and then RECOVERY, and it just drops me back to where I was. No recovery comes up.
Click to expand...
Click to collapse
there is no s-off yet bro
where did u get that info? lol
What info? I reported what appears to be wrong. I selected BOOTLOADER and then selected RECOVERY, and no recovery came up. That's where the discussion is.
Related
Hey,
I'm trying to flash a ROM on my phone and I'm currently running "Flashback 2.1" or whatever it is. When I try to reboot into recovery using the Volume +, I get a picture of the Eris with a red triangle/exclamation point.
So, my lovely Eris users, does anyone know what this means and how I can fix it, before I call Verizon and demand a new phone?
Thanks!
That is normal behavior for a stock phone - it is the "stock" recovery boot.
When that image is on the screen, press Vol-up+End (once more), and you will see the stock recovery menu.
You said you installed the "FlashBack21" ROM - which returns your phone to stock, including the recovery boot. (As it states in bold red print in that ROM's thread).
What you are seeing is stock behavior.
Time for you to root again - if that's what you are trying to do.
bftb0
PS: Here's what the different Eris Recovery "splash screens" have looked like over time
http://i756.photobucket.com/albums/xx209/erisuser1/recovery_boot/RecoverySplashComparison-small.jpg
I've tried what you said and I can't get it into recovery. I got it once, but I can't seem to get it again... Help?? Please.
queenybee8289 said:
I've tried what you said and I can't get it into recovery. I got it once, but I can't seem to get it again... Help?? Please.
Click to expand...
Click to collapse
Well, I only suggested that so you would see that there is nothing wrong with your phone. The "stock" recovery is of almost no use to you at all - you want a custom recovery (Amon_RA)
You need to re-root your phone, let's say using Jcase's "One Click" app. After doing that there will be a usable recovery available to you, from which you can flash other ROMs. (Again, the "FlashBack21" ROM UNROOTS a phone - returns it to factory software).
Thank you! I apologize for the blond moment I'm not a noob, I swear.
queenybee8289 said:
Hey,
I'm trying to flash a ROM on my phone and I'm currently running "Flashback 2.1" or whatever it is. When I try to reboot into recovery using the Volume +, I get a picture of the Eris with a red triangle/exclamation point.
So, my lovely Eris users, does anyone know what this means and how I can fix it, before I call Verizon and demand a new phone?
Thanks!
Click to expand...
Click to collapse
/facepalm
Flashback 2.1 is not a rom, it's a zip that when you flash it, it unroots you and sends you back to stock. Reroot with the one click root apk and flash a rom. You'll be fine.
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Ok, this is my first post so be gentle. I tried to root my sons phone and now it's useless. I went thru HTC's website to unlock bootloader due to having HBOOT 1.5. I'm unlocked and thinking life is good but, I loaded several different ROM's and get the same result. It starts to load the ROM and reboots, sometimes it goes into a safemode with the Viper Rom. I've been jacking with this for 2 days and need some help. I can't find a good link for the RUU or PG86...bla bla bla, I would take it back to stock and surrender but, can't even do that. I've installed TWRP and CWM, just to try different stuff, but get all the same reults.
I think you need to flash the boot.img separately. I'm not sure though. There's a thread for flashing with 1.50 somewhere in the development section
We're comin from a pure power source.
I am having the same issue here, I installed several ROMS, it works for a day, but then the reboot attack starts. Constant lockups and random restarts, sometimes 3 reboots in a row.
ROMs I tried to flash:
1. Xperia XE
2. Titan Trinity 3 HD
3. Nocturnal Adrenaline 1.0.2
Maybe it's the kernel, is there a list of kernels that I can flash?
This worked for me
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
armydude13090 said:
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
Click to expand...
Click to collapse
Unroot my phone?
Is it possible to re-root it?
Thanks all for the posts. I will give some of this a shot and see what happens. I can get to fastboot, and have loaded a couple of things thru the cmd prompt to try and help, but nothing so far. I'm not really sure if the kernel thing is what's stopping the roms for loading. I can't get the S-OFF, I'm unlocked. I can send anything I want thru the cmd prompt, and also flash zips thru twrp or cwm. Would like to start over but ca't even find a way to do that. Thanks again for the posts.
Cardmastr, we're on the same boat, pg86 takes forever to download, so as I'm waiting patiently, keep me in on the loop with what you're doing.
RUU didn't cut it, kept failing. have not found an image file to flash thru the cmd prompt. Still no luck. What can I throw into fast boot that might help me?????!!!!!!
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Which recovery did you install? Twrp 1.1.1 is your best bet.
The 2.x version twrp or cwm do not okay nice with some phones.
S3nt from my 3D wond3rland
I used the TWRP 1.1.1. Might of messed up with some of the cmd prompt stuff I'm going back thru.
thefsfempire said:
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Click to expand...
Click to collapse
Everyday is Halloween for u dude!! UR a Monster! This little tidbit hooked me up. Thanks to you we are back in game.
When installing a ROM, doesn't it wipe /data, /system, etc for us?
I have the HTC One X Plus International and recently recovered from it only being able to go into Bootloader Mode because of the System being erased without a backup. I finally was able to learn how to find the correct RUU for my make and model to bring it back to life. Before accomplishing this, this current problem still existed.
Each time now when I boot-up, it starts perfectly well, no problem. But when I try going into Bootloader Mode and choose Recovery, it shuts itself down. So, since I am unable to Root it, or at least I don't know how to do so under these circumstances, how do I get around this obstacle? Thanks.
Jussi31 said:
I have the HTC One X Plus International and recently recovered from it only being able to go into Bootloader Mode because of the System being erased without a backup. I finally was able to learn how to find the correct RUU for my make and model to bring it back to life. Before accomplishing this, this current problem still existed.
Each time now when I boot-up, it starts perfectly well, no problem. But when I try going into Bootloader Mode and choose Recovery, it shuts itself down. So, since I am unable to Root it, or at least I don't know how to do so under these circumstances, how do I get around this obstacle? Thanks.
Click to expand...
Click to collapse
I don't know if this is too obvious.. but have you flashed the recovery again??
When you run the RUU, it is overwritten. You need to download a recovery and flash it through fastboot:
fastboot flash recovery recovery.img
Actually, around six or seven times now, with no luck. Now when attempting to get into Recovery, it hangs on the white screen. The thing is, I successfully had TWRP 2.5.0.0 on it. (Long story.) I am now trying to figure out how to root it through Fastboot, if that's even possible. Otherwise, I am out of ideas.
Through trial-and-error, I finally was able to get it rooted. However, no matter how many times I try flashing TWRP-Touch (various versions), it maintains its inability to boot into Recovery Mode. Go figure.
I use twrp venom without any issues, maybe try that one?
http://forum.xda-developers.com/showthread.php?p=37300312
Sent from my Viper One X+
Oh wow, it actually worked! God love you. Thanks much.
No problem
Sent from my Viper One X+
When you were hanging on the white screen, did it say anything on the screen?
I can't recite it exactly, HTC, something. But know that it is the first screen you would see upon rebooting.
Update
00mpollard said:
No problem
Sent from my Viper One X+
Click to expand...
Click to collapse
Hey 00mpollard, I just wanted to thank you for both recommending a working Recovery IMG (that works great) for my HTC One+, and as well as introducing me to the corresponding Viper One X+ ROM, that I also decided to install, and I couldn't be happier. Thanks again.
No problem, glad i could help!
I love Viper rom, very stable & lots of customizations Can't go wrong!
Jussi31 said:
I can't recite it exactly, HTC, something. But know that it is the first screen you would see upon rebooting.
Click to expand...
Click to collapse
I was just curious because if it said something about waiting on SD card or SDdata, something along those lines, I get that issue when the phone is plugged in. Unplugging the cable allowed me to enter hboot with no issues.
Hello,
Got a Xperia Z2. It's rooted, installed TWRP Manager (ROOT), tried to install recovery manager. seemed to work but coulden't boot into recovery mode. I remember i had blocked bootloader and went through that and probably unlocked it. As no issues and every step went fine.
Tried now to start my phone, I only see background image and those waves. then it stucks for a second and reboot on it's own. And does that again and again.
Everything worked with phone until i unblocked the bootloader. also made sure i typed the right numbers and letters, and I did. Also no error at all when unlocked the bootloader.
but now I can't get my phone running. I still can boot into "fastboot mode", (volume up and power button and the led is blue).
So now I wonder if there is any way to get my phone running again, either with stock rom or something else. I really don't care how much I need to do, as long it might get the phone running again.
If you got any solution, or think you might have, try to explain as good as possible, as I'm not too familiar with these issues.
Thanks in advance.
TForsman said:
Hello,
Got a Xperia Z2. It's rooted, installed TWRP Manager (ROOT), tried to install recovery manager. seemed to work but coulden't boot into recovery mode. I remember i had blocked bootloader and went through that and probably unlocked it. As no issues and every step went fine.
Tried now to start my phone, I only see background image and those waves. then it stucks for a second and reboot on it's own. And does that again and again.
Everything worked with phone until i unblocked the bootloader. also made sure i typed the right numbers and letters, and I did. Also no error at all when unlocked the bootloader.
but now I can't get my phone running. I still can boot into "fastboot mode", (volume up and power button and the led is blue).
So now I wonder if there is any way to get my phone running again, either with stock rom or something else. I really don't care how much I need to do, as long it might get the phone running again.
If you got any solution, or think you might have, try to explain as good as possible, as I'm not too familiar with these issues.
Thanks in advance.
Click to expand...
Click to collapse
i think, now you can flash stock ftf thru flashtool.
and get it rooted again by xperia rootkit, and install xzdual recovery.
Jhon998 said:
i think, now you can flash stock ftf thru flashtool.
and get it rooted again by xperia rootkit, and install xzdual recovery.
Click to expand...
Click to collapse
Thanks, worked fine to use flashtool to get it to work again. Installed recovery and rooted it. Also custom rom. Thanks again