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!
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!
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.
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
xeas said:
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
Click to expand...
Click to collapse
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
clsA said:
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
Click to expand...
Click to collapse
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
xeas said:
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
Click to expand...
Click to collapse
very good
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
qibz said:
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
Click to expand...
Click to collapse
Welcome to XDA
posting your problem with all the needed information in a new thread would help.
when making your post be sure and include
whats on the bootloader screen
and a copy/paste of the results from fastboot getvar all
most likely your not s-off or your not on the correct version of TWRP
also in your new post add @clsA so i get the notification that you posted
My prism 2 phone boots to blue screen. Can't get to fastboot. Can't get to boot loader mode. Only can get to pink screen. Before this I had bootloader unlocked and my phone was rooted and debugging was on. I attempted to use swapped 2 phone rebooted fine next time I rebooted it went to blue screen. And I have clockworkmod recovery.II. Could really use some help if it's out there. Thanks anyone
Experiencing the same Non existant /system mount
ajp87 said:
My prism 2 phone boots to blue screen. Can't get to fastboot. Can't get to boot loader mode. Only can get to pink screen. Before this I had bootloader unlocked and my phone was rooted and debugging was on. I attempted to use swapped 2 phone rebooted fine next time I rebooted it went to blue screen. And I have clockworkmod recovery.II. Could really use some help if it's out there. Thanks anyone
Click to expand...
Click to collapse
My partitions for boot were erased accidentally. Cannot fastboot nor adb. Frustrating, this is my only way to communicate with family and loved ones. I had a pretty robust development of the Stock ROM, but chose to flash these ROMs, and ended up erasing boot partitions in the process. Is there any fix for this and how do I reintegrate the file system? Terrible. I guess we're SOL.
Tried to erase and restore the data from the setting menu and it has been stuck on this thing all day and night. Tried to boot into recovery to reflash but that didnt work, nothing came up when I held the buttons down. I can get into APX more and when its on the green android loading screen thing it shows as ADB device. Thats about all I can do with it.
Any ideas? It was unlocked and rooted
primerars said:
Tried to erase and restore the data from the setting menu and it has been stuck on this thing all day and night. Tried to boot into recovery to reflash but that didnt work, nothing came up when I held the buttons down. I can get into APX more and when its on the green android loading screen thing it shows as ADB device. Thats about all I can do with it.
Any ideas? It was unlocked and rooted
Click to expand...
Click to collapse
What bootlaoder version ?
What recovery make and version ?
Thx Josh