[Desire HD Q&A, Help & Troubleshooting] RichardPNL:
Hi guys and gals,

I'm new here, and I'm just recovering my confidence after the video they make noobs sit through. I have also searched related threads, and have around 20 tabs open in Firefox right now. Alas, no solutions found yet so I'm finally going to make my own thread. The problem is as follows:

I have used MIUI v4 for a while, but it was becoming very slow, battery inefficient and not letting my call or send texts. Therefore I went on to flash the Revolution HD 6.3.1 ROM, which I used when I first flashed my DHD and used to be very stable. After having succesfully flashing the ROM and booting, I was flooded with errors of .acore processes, rendering my DHD unusable. Fortunately USB debugging was still on by default. I then went on to use AAHK, thinking I could flash everything back to the situation when I first rooted and flashed my phone.

After taking well over an hour of being non-responsive, my PC (Win 7) froze up and I had to restart. Hoping the AAHK had finished, I unplugged my phone only to discover that it wouldn't do anything other than show the white screen with the HTC logo. At this point I was already starting to sweat, but when I couldn't even get into the bootloader I fell down to my knees letting out a big NOOOO.

I then finally managed to properly hold down the vol- and power buttons, and I was soon basking in the cold white light emanating from the hboot screen. Unfortunately, selecting either RECOVERY or FACTORY RESET leads to the same white HTC screen. FASTBOOT however, does work, and after reading some other threads I have acquainted myself with SDK, adb and fastboot. adb doesn't seem to work, and it also doesn't show any devices when using the 'adb devices' command. 'fastboot devices' does show my phone, and I can use some commands.

Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:

"fastboot erase cache" which got an OKAY.

and

"fastboot oem rebootRUU" which also got an OKAY.

I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:

sending 'recovery' <3650 KB>...

OKAY [ 0.607s]

writing 'recovery'...

FAILED <remote: not allowed>

finished. total time: 0.609

This leads me to believe that because USB debugging isn't enabled, I can't write to the flash.

Then tried this:

"fastboot update PD98IMG-GB2.zip"

(short wait)

Whoops: didn't find expected signature

read_central_directory_entry failed

error: failed to acces zipdata in *jibberish*

I'm at a loss as to anything else I might try. The HBOOT still works, and the phone is S-OFF, but I can't seem to flash anything to my phone. I'm hoping some of you gurus here might know something else. My deepest thanks in advance.

EDIT: with Fastboot Commander I made a print of my device:

-----------------------------------.

SPL/hboot version: 0.85.0024.

Radio version: 26.03.02.26_m.

Main software version: 1.32.405.6.

cid: 11111111.

cpld: none.

product: ace.

mid: pd9810000.

security: off.

build-mode: ship.

-----------------------------------.

EDIT 2: After a horrible day of thinking my phone was dead, but still trying to revive it, I have managed to find a solution! In this thread: http://xdaforums.com/showthread.php?p=26844128#post26844128 there was the suggestion to rename PD98IMG-GB2.zip to just PD98IMG.zip. As soon as I did this, copied the file to my SDcard through another phone, and booting into the bootloader, I was asked if I wanted to upgrade. Hell yeah! After a short wait, I now have my phone up and running again, in a very stock configuration!