Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
yeah:) said:
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
Click to expand...
Click to collapse
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
alroco20 said:
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
Click to expand...
Click to collapse
This thread is old, and OP is ignorant and wants to blame ROM Manager for his own problems. If you can't get into recovery, chances are you are using one built for another phone. Find the one for the G1.
Or ran into the know issue of cm5.0.7 that fash_image sometimes (more than not) fails.. thus applications using it sometimes fail.
But you have danger spl right? So flash the recovery via fastboot.. and if you don't have fastboot/adb and intended to run these custom roms its about time you installed it.
Hi guys. I think I have bricked my One.
Basically I relocked the bootloader because I wanted to go back to stock however now I am stuck in the bootloader and cannot do anything.
The RUU wont work, everytimre I hit reboot it goes straight back into the Bootloader as it does when I select Recovery and Power Down. Cant get into Recovery or anything.
Any suggestions would be greatly appreciated.
EDIT: Fixed. Unlocked bootloader again now working fine.
I am having quite a problem. I had unlocked the bootloader and rooted my ONE. Suddenly it decided to freeze on the lockscreen so i tried to reboot. It would not reboot and was stuck on the HTC ONE screen. I tried booting into recovery and sideloading the stock rom which did not work. and now i can not even boot into the recovery. please help. When i try to boot it up regularly it gets stuck on the Quietly Brilliant screen.
Daking12794 said:
I am having quite a problem. I had unlocked the bootloader and rooted my ONE. Suddenly it decided to freeze on the lockscreen so i tried to reboot. It would not reboot and was stuck on the HTC ONE screen. I tried booting into recovery and sideloading the stock rom which did not work. and now i can not even boot into the recovery. please help. When i try to boot it up regularly it gets stuck on the Quietly Brilliant screen.
Click to expand...
Click to collapse
This will sound weird but seems to be helping people in the dev sections:
Put the phone under a bright light, and hold the power and volume down buttons.
I haven't had to use this particular method myself, but supposedly it works.
Good evening. I have a HTC One international. I tried to make my phone S-off with a toolkit fownd on another website, and somehow bricked the phone. It starts, but doesn't go past the "htc quietly brilliant" logo. I searched the forum here, because i heard it is the best, but i haven't found a clear answer to my problem.
If someone has the time, please help me.
p.s. i am a beginner in the art of custom roms, rooting and this sort of stuff, so please, keep as simple as you can.
Thanks a lot!
Can you boot to the bootloader by holding volume down and the power button for about 15 seconds?
If so, what is your bootloader screen reading and do you have a custom or stock recovery installed?
As Steve says, can you boot into the boot loader, and do you have a custom recovery installed? If you do, you should be able to re-install your ROM and boot again.
If not, and your boot loader is unlocked, you should be able to flash a custom recovery via fastboot & then install a custom rom to allow you to boot.
I just got my nexus 6 unlocked the bootloader and flashed twrp... TWRP didn't boot up just flashed the logo and the phone wouldn't boot up. I then relocked the bootloader. Why? I don't know. Cause I havent had an unlocked bootloader in a really long time... Can someone please help me now Im stuck in a bootloop no recovery and a locked bootloader.
EDIT: Thank the android people! This worked. http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783
Glad its fixed. please use more descriptive thread titles though.