Develop Bugs

cannot access recovery on DHD

hey everyone, i have an sim free desire HD that was rooted and s-off and has been running like that for a while. recently i tried to access clockwork mod to try and flash a new rom but when i did so the recovery does not load. Its just stuck on the htc splash screen, it doesnt even say quietly brilliant. The phone still works but i cannot access recovery. I tried the following procedure in fastboot to re flash the recovery
fastboot erase recovery
fastboot flash recovery recoveryCWM.img
fastboot reboot
after doing this it still has not worked. Any suggestions or a certain fix would be brilliant.
Thanks

You can put the PD98IMG.zip from my downgrade post to your SD card and reboot to bootloader, it will flash you the 1.32 stock ROM and you can start from a clean table.

use an older version of recovery
nemesis2911 said:
hey everyone, i have an sim free desire HD that was rooted and s-off and has been running like that for a while. recently i tried to access clockwork mod to try and flash a new rom but when i did so the recovery does not load. Its just stuck on the htc splash screen, it doesnt even say quietly brilliant. The phone still works but i cannot access recovery. I tried the following procedure in fastboot to re flash the recovery
fastboot erase recovery
fastboot flash recovery recoveryCWM.img
fastboot reboot
after doing this it still has not worked. Any suggestions or a certain fix would be brilliant.
Thanks
Click to expand...
Click to collapse
I had the same problem, with clockwork 3.0.0.6 ... I then flashed 3.0.0.5 (see the bottom of the Rom manager Menu that proposes you to use former recovery roms). I could solve my problem that way.

[Q] Can't boot into recovery?

First of all, I'm running the RUU GPE edition rom for my HTC one M8, I love it. However I want xposed framework, and all of it's goodies too, otherwise imo I should have stuck with Sense version. There is one problem though. I can't seem to boot into recovery, at all. When I attempt to boot into recovery via ADB, or from the bootloader it just shows me the google logo for a while, and restarts back to android homescreen.
Could this be because I may have flashed the wrong recovery? Initially I flashed the "hammerhead" recovery from TWRP, whatever the hell that is(thought I was getting it specific for my HTC one), later once I noticed I did that I simply reflashed the correct recovery. Could this be why, if so, how can I fix that? Can I remove the recovery and reflash it?

Spewed said:
Can I remove the recovery and reflash it?
Click to expand...
Click to collapse
No, flashing a recovery removes the old one, but you should do:
fastboot erase cache

BenPope said:
No, flashing a recovery removes the old one, but you should do:
fastboot erase cache
Click to expand...
Click to collapse
I assumed flashing another recovery merely erased the old one. so I tried "fastboot erase cache", then "fastboot flash recovery openrecovery-twrp-2.7.0.1-m8.img", to no avail, still unable to boot into my recovery by "adb reboot recovery", or any other method. I'm S-off, bootloader unlocked. When I was running sense I had s-off, custom recovery, root and twrp.
Any other ideas?

Spewed said:
I assumed flashing another recovery merely erased the old one. so I tried "fastboot erase cache", then "fastboot flash recovery openrecovery-twrp-2.7.0.1-m8.img", to no avail, still unable to boot into my recovery by "adb reboot recovery", or any other method. I'm S-off, bootloader unlocked. When I was running sense I had s-off, custom recovery, root and twrp.
Any other ideas?
Click to expand...
Click to collapse
Hmm, I assume you don't have a Sprint or Verizon M8?

BenPope said:
Hmm, I assume you don't have a Sprint or Verizon M8?
Click to expand...
Click to collapse
I have the ATT version.
All of this was fine, until I made the switch to GPE, which I was under the impression I actually downloaded the rooted version, seeing as how that is the one I selected. Sadly, no root, so I began the rooting method over, to no avail.

Well, apparently I got twrp on there.
I went ahead and got the HTC One all in one toolkit to see if somehow that might flash the recovery. Of course, the actual transfer of the recovery seemed to hang, and never finish. So I unplugged the phone, it said it failed. I attempted to manually boot into recovery using power and volume down. Of course, it didn't work. Attempted to flash the recovery again using the all in one toolkit. Same scenario, it hangs and fails. Once again, I manually tried to boot into recovery. This time, miraculously it works. What the hell? haha

Issue with flashing roms with s-on

I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated

tt33333 said:
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
Click to expand...
Click to collapse
Update your recovery.img to either of following;either one is good. But make backup of any rom you're on so that you may revert it back in future.
-TWRP 2.7.1.0
-Philz touch CWM
-4EXT Recovery Touch 1.0.0.6 RC 3
By the way which four roms you've tried? if recovery is up-to-date then phone should boot normally.

I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks

tt33333 said:
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
Click to expand...
Click to collapse
Strange....
Well unmark md5 check on restore. And clear cache/dalvic before rebooting it,Let's see how it goes.Also want to know which perticular rom you've tried so far where you were facing this issue. Also did you format devlog partition before installing CM11 nigthlies 20140618 onwards? If not then try doing so and let me know where you gets stuck?
I'm also S-ON where most other already made S-OFF so feel free to ask me. I'll help as much as i know :good:

Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks

tt33333 said:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
Click to expand...
Click to collapse
Except Mokee 4.4.4 Release and CM11 M8.1 i used Philz but before that i was on CWM 5.8.1.5 and i had no issues with it. Also i've tried TWRP 2.7.1.0 too. Works perfect but i'm used to reboot into recovery by default option,which only available in CWM. Other recoveries boots into blank screen,If you powered off the device and put on charge.
Nope there isn't any sequence.... either you flash boot.img first or last it only helps in device to boot and have proper connectivity. Even if you don't flash boot.img then only your device should hang on bootloop or boots but no wifi reception. So these is something different.
Sure i can provide system.img and boot.img of M8.1 which i'm currently on. But how sure you're that it will work? I mean do you have a backup of it? Or fresh install. Also wanted to know have you ever tried format devlog partition and FULL WIPE your device?
Try using following attachments. FULL WIPE it's just an alternative of manual wipes,works with every recovery out there. And devlog partition will be formatted if any means of corrupted or remnant leftover using format_devlog zip. Meanwhile provide me details whether you got backup of M8.1 CM11 or going to flash fresh install. So that i can provide boot and system.img of it.

It's working now. Installed 4ext recovery and ran you'r script.
Thanks for all the help

[Q] S-OFF M8 GPE stuck on boot screen

I have been running a stock GPE 5.1 ROM on my S-OFF M8 for a while now and it just restarted itself out of the blue yesterday. Since then, it's just been stuck on the Google boot screen. I have TWRP so here is what I have tried:
1. Flashing the GPE ROM again: Flashes fine in TWRP but still stuck at boot screen.
2. Flashing another GPE-based ROM (SkyDragon). Goes through AROMA installer but same result.
3. RUUReboot and reflashing the GPE RUU. Boot screen again.
At this point, I'm not sure what went wrong or what else I can do.

I'm no expert by any means but I'd say try returning to stock. Also do you do a full format? Maybe your internal memory needs a wipe too.
Sent from my HTC One_M8 using XDA Free mobile app

stuck at twrp recovery / recovery only starts for a split second

I've been trying to root my HTC m8 and everything was going perfect until I went to load the twrp recovery in order to access supersu. I followed a youtube guide and everything was fine, but now whenever I try to load recovery, it will either say loading recovery and then go into my stock OS, or it will be stuck at the recovery screen and I'll have to power down the phone.
Is it because the twrp recoveries I'm using don't work well with my hboot? I'm completely new to this stuff so I have no idea what the problem could be. My HTC is from At&t and my Hboot is 1.61 and I've used twrp recoveries 2.8.7.0 through 2.8.4.0 and none have worked. I've also used 2.7.0.2 and the philz_touch_6.26.6 with same results.
I've erased the cache after every flash recovery, and rebooted the bootloader before I recover again. If I'm overlooking anything or doing something dumb please inform me! I have no clue what to do now...

Are you sure it's a HTC M8 ? hboot 1.61 is a HTC M7