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.
wont re boot
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
What root rom did you use? Were you ever able to boot to the system? Did you try forcing bootloader thru adb > fastboot reboot bootloader
myvwrocks said:
What root rom did you use? Were you ever able to boot to the system? Did you try forcing bootloader thru adb > fastboot reboot bootloader
Click to expand...
Click to collapse
did you disable fastboot in phone settings?
fastboot erase cache will solve your recovery problem
Related
ok. so i just htc unlocked and need to install a recovery, but when i try to install it in fastboot it says it installed, but when i boot to it, the phone goes black and reboots to system. Please help
fixed it
Tried to flash Amon Ra recovery in order to flash a new rom that doesn't play nice with other recoveries.
To be to the point, apparently the flash failed. Now I cannot access the bootloader, and when i try to it goes and boots to the rom. Which sadly was the rom I flashed before that didn't work with other recoveries. So now I cannot enable debugging, go to the bootloader or recovery, or even go to the googleplay store and install rom manager.
I have class at 8 (8 hours from now), so any help is appreciated. Been working on this for about 2 hours now and going crazy
Couple things:
1. It's not clear from your post, but you can't boot into the ROM at all? what's the issue? does it just bootloop or something?
2. Have you tried using ADB commands to boot into bootloader? from there you could flash a recovery.
fo0you said:
Couple things:
1. It's not clear from your post, but you can't boot into the ROM at all? what's the issue? does it just bootloop or something?
2. Have you tried using ADB commands to boot into bootloader? from there you could flash a recovery.
Click to expand...
Click to collapse
Every once in a while it would boot into the rom, however the settings would crash and I can't do anything other than toggle the quick settings. When trying to boot to recovery it just "skips" over the bootloader and recovery.
ADB commands aren't working because it isn't recognizing my device.
Also it seems that now it cannot even boot to the rom
weirdest thing just rebooted again and it worked.... Dont know how or why but im not gonna argue
I unlocked the boot loader, then I rebooted my phone, then rebooted into recovery mode. Once I install either a custom rom, or supersu, even if it works to install, once i try to reboot, it only reboots to TWRP. Even when I reboot to system it still does that. Is my phone just bricked?
bobbymacy said:
I unlocked the boot loader, then I rebooted my phone, then rebooted into recovery mode. Once I install either a custom rom, or supersu, even if it works to install, once i try to reboot, it only reboots to TWRP. Even when I reboot to system it still does that. Is my phone just bricked?
Click to expand...
Click to collapse
No its not bricked.. maybe soft bricked, but not bricked bricked how are you flashing recovery? are you using
fastboot flash recovery twrp.img
or
fastboot flash boot twrp.img
2nd way is incorrect. Try
fastboot flash recovery twrp.img
fastboot erase cache
then boot to twrp and flash rom and let me know what happens. Make sure you are using correct gsm twrp if you are on an att phone.
He probably followed these instructions here which direct you to flash twrp to boot instead of recovery just like you said above.
I don't know why he leaves it up there like that but seeing as it's the first link on Google when you search "root att HTC one m8" , he needs to change it cause I'm sure it's causing plenty of headaches.
Sent from my HTC One_M8 using Tapatalk
an0ther said:
No its not bricked.. maybe soft bricked, but not bricked bricked how are you flashing recovery? are you using
fastboot flash recovery twrp.img
or
fastboot flash boot twrp.img
2nd way is incorrect. Try
fastboot flash recovery twrp.img
fastboot erase cache
then boot to twrp and flash rom and let me know what happens. Make sure you are using correct gsm twrp if you are on an att phone.
Click to expand...
Click to collapse
I did
./fastboot flash recovery twrp.img
because I'm using mac. I didn't erase the cache though. Also on twrp, it says my phone has no os, and installing a custom rom failed to install.
Hey guys i have a htc m8 with 4.4.4 unlocked bootloader s-on but can't get into twrp recovery anymore, every single time that i try it tried for about 10 seconds then boots back to the phone. Any suggestions?
nillyizback said:
Hey guys i have a htc m8 with 4.4.4 unlocked bootloader s-on but can't get into twrp recovery anymore, every single time that i try it tried for about 10 seconds then boots back to the phone. Any suggestions?
Click to expand...
Click to collapse
To be clear, you are in hboot, and when you select recovery, it just reboots to OS?
And you don't get a red triangle (stock recovery)?
If the above are true, try fastboot erase cache, and install TWRP again. This solves a great many instances of failure to boot into recovery. Or try a different TWRP version if it still doesn't work.
No matter how I try to flash the TWRP recovery image to the recovery partition, TWRP gets replaced by the crappy stock recovery!! This is absolutely maddening!
Specifically, it seems that no matter what method to use to flash the TWRP recovery, it gets overriden by the stock loader when the phone reboots.
My bootloader is UNLOCKED and I've installed a custom rom just fine by using the command fastboot boot twrp.img to boot into the twrp image. This is the only way I'm able to use TWRP at all.
I've tried:
fastboot flash recovery twrp.img
Booting into TWRP, and flashing the image over the recovery partition
Flashify to flash the TWRP over the recovery partition from within the rom
Trying to flash cyangenmod's recovery from within the rom (was pretty desperate at this point..)
I've also tried many different versions of TWRP, I can boot into them just fine but none of them stick when I flash them to the recovery partition.
It always says it's successful when I try to flash it, I reboot into recovery, and it boots into the piece of crap EmUI stock recovery screen every time
Anyone have any pointers here? It's not the end of the world but it's pretty aggravating having a completely useless recovery if I'm not near a computer,.
Try using Flashify or Flashfire.
Sadly didn't work. It doesn't seem to matter how I flash the recovery, the bootloader replaces it with the stock recovery when it boots. I'll update the OP to clarify, but thank you
I am having same issue have you found a fix
Have you tried starting completely over? Like, downloading the official MM build (b331, C564D003) from Huawei (Assuming you're on L24)?
On the new, freshly installed ROM, make sure that USB Debugging is and enable OEM Unlock are on in the developer settings.
Then, try flashing this build of TWRP again.
Before rebooting, do a Cache/Dalvik Wipe.
Boot up into the stock rom, then use 'adb reboot recovery' to see what happens next. It should work...
Hi mate,
It'd be easier to help you if you could post a screenshot of your FASTBOOT screen. There will be a line that will say FRP=LOCKED/UNLOCKED something like this.
if it is locked,
you have to install stock rom & enable OEM unlock from setting.
Then relock the boot loader. Then again unlock the boot loader.
For myself, I unlocked my BL unofficially, & this problem occurred . I solved it this way...
Hope it helps.
Cheers!