• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root HTC Desire HD - Needs to be brought back to life!!!

Excellent ! Very glad to see it worked for you :cool:

He can start using the phone now,but its on old firmware.

Coincidentally, it is on the correct firmware to simunlock,s-off,and supercid :D

If you're up for it I will walk you thru entering a few commands to accomplish that. That way any future rescues should be easy

Alternately,you could simply run a newer ruu and be good to go :)
 
  • Like
Reactions: D-U-R-X and DVSimz
Upvote 0
Excellent ! Very glad to see it worked for you :cool:

He can start using the phone now,but its on old firmware.

Coincidentally, it is on the correct firmware to simunlock,s-off,and supercid :D

If you're up for it I will walk you thru entering a few commands to accomplish that. That way any future rescues should be easy

Alternately,you could simply run a newer ruu and be good to go :)
Yes, he's definitely looking for the best possible "firmware". I think this is how this whole mess started. He wanted to update his phone with a better software. If I could do this for him now, he won't have to screw around with it anymore :)

I cannot thank you guys enough for all of this!!!
 
Upvote 0
Yes, he's definitely looking for the best possible "firmware". I think this is how this whole mess started. He wanted to update his phone with a better software. If I could do this for him now, he won't have to screw around with it anymore :)

I cannot thank you guys enough for all of this!!!

you are quite welcome. :) im glad its worked out for you,after all your work and patience. i assume this means youre willing to go ahead and simunlock,s-off,and superCID. this will make it much easier to mod the phone and flash new software,and to rescue it if anything goes wrong.

there are just a few more adb commands,everyting you need is allready inside mini-adb_inspire.

things should go smoothly since were dealing with a working,booted phone and not having to adapt the commands to work in recovery.

so heres what you do(each line is a seperate command):


6)s-off,superCID,simunlock with gfree

once booted to the old firmware, skip the startup stuff,enable usb debugging. open a cmd window then:

adb devices
cd c:\mini-adb_inspire

adb push psneuter /data/local/
adb push busybox /data/local/
adb push wpthis /data/local/
adb push gfree /data/local/

adb shell
chmod 0755 /data/local/psneuter
chmod 0755 /data/local/wpthis
chmod 0755 /data/local/gfree
/data/local/psneuter (to get temp root again)

adb shell

/data/local/wpthis (to disable emmc write protect)
/data/local/gfree -f (this will supercid, simunlock, and s-off phone)

exit to get back to your mini-adb_inspire> prompt

adb reboot bootloader boot you to bootloader. verify s-off

fastboot getvar all will output a few variables

fastboot reboot to reboot your phone

and heres what the commands will look like in your cmd window:
Code:
c:\mini-adb_inspire>[COLOR="Red"]adb push psneuter /data/local/[/COLOR]
1371 KB/s (585731 bytes in 0.417s)

c:\mini-adb_inspire>[COLOR="red"]adb push busybox /data/local/[/COLOR]
1408 KB/s (1062992 bytes in 0.737s)

c:\mini-adb_inspire>[COLOR="red"]adb push wpthis /data/local/[/COLOR]
1429 KB/s (679475 bytes in 0.464s)

c:\mini-adb_inspire>[COLOR="red"]adb push gfree /data/local/[/COLOR]
1458 KB/s (134401 bytes in 0.090s)

c:\mini-adb_inspire>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]chmod 0755 /data/local/psneuter[/COLOR]
chmod 0755 /data/local/psneuter
$ [COLOR="red"]chmod 0755 /data/local/wpthis[/COLOR]
chmod 0755 /data/local/wpthis
$ [COLOR="red"]chmod 0755 /data/local/gfree[/COLOR]
chmod 0755 /data/local/gfree
$ [COLOR="red"]/data/local/psneuter[/COLOR]
/data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

c:\mini-adb_inspire>[COLOR="red"]adb shell[/COLOR]
# [COLOR="red"]/data/local/wpthis[/COLOR]
/data/local/wpthis
Build: 25
Section header entry size: 40
Number of section headers: 45
Total section header table size: 1800
Section header file offset: 0x00014e90 (85648)
Section index for section name string table: 42
String table offset: 0x00014cc7 (85191)
Searching for .modinfo section...
 - Section[16]: .modinfo
 -- offset: 0x00000f80 (3968)
 -- size: 0x000000c4 (196)
Kernel release: 2.6.32.21-gf3f553d
New .modinfo section size: 204
Loading module... OK.
Write protect disabled.
Searching for mmc_blk_issue_rq symbol...
 - Address: c02a9e00, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a9000
Kernel memory mapped to 0x40001000
Searching for brq filter...
 - Address: 0xc02a9e00 + 0x34c
 - 0x2a000012 -> 0xea000012
Done.
# [COLOR="red"]/data/local/gfree -f[/COLOR]
/data/local/gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
 - Section[16]: .modinfo
 -- offset: 0x00000a14 (2580)
 -- size: 0x000000cc (204)
Kernel release: 2.6.32.21-gf3f553d
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
 - Address: c02a9e00, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a9000
Kernel memory mapped to 0x40000000
Searching for brq filter...
 - Address: 0xc02a9e00 + 0x34c
 - ***WARNING***: Found fuzzy match for brq filter, but conditional branch is
. (0xea000012)
Patching and backing up partition 7...
patching secu_flag: 0
Done.
# [COLOR="red"]exit[/COLOR]
exit

c:\mini-adb_inspire>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\mini-adb_inspire>[COLOR="red"]fastboot getvar all[/COLOR]
INFOversion: 0.5
INFOversion-bootloader: 0.85.0007
INFOversion-baseband: 26.03.02.26_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.32.405.6
INFOserialno: HT18LT211769
INFOimei: 358920041110039
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9812000
INFOcidnum: 11111111  [COLOR="Blue"]<-superCID[/COLOR]
INFObattery-status: good
INFObattery-voltage: 4196mV
INFOpartition-layout: Generic
INFOsecurity: off  [COLOR="Blue"]<- s-off[/COLOR]
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-7eafc656
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.024s

c:\mini-adb_inspire>[COLOR="Red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.215s

c:\mini-adb_inspire>
 
Upvote 0
Guys,

I cannot thank you enough for all your assistance through this. It was frustrating for me at times, so I can only imagine how frustrating it was for all of you while trying to help a "newbie" out with this.

My brother is happy, I'm happy, everything is working GREAT with the phone!

You guys are pros and I'm glad and extremely thankful that there are people like you out there who give up their free time to help fix other ppl's issues.

YOU GUYS ARE AWESOME!!!!
 
  • Like
Reactions: iowabowtech
Upvote 0
Guys,

I cannot thank you enough for all your assistance through this. It was frustrating for me at times, so I can only imagine how frustrating it was for all of you while trying to help a "newbie" out with this.

My brother is happy, I'm happy, everything is working GREAT with the phone!

You guys are pros and I'm glad and extremely thankful that there are people like you out there who give up their free time to help fix other ppl's issues.

YOU GUYS ARE AWESOME!!!!

we are glad to help! :D

just curious,what did you end up doing with the phone? is he using it as is? or did you do the extra adb commands? or did you just run the newer ruu i linked in post 79?

*high fives all around :D
 
Upvote 0
we are glad to help! :D

just curious,what did you end up doing with the phone? is he using it as is? or did you do the extra adb commands? or did you just run the newer ruu i linked in post 79?

*high fives all around :D
I ran the RUU from post 79! It works like a dream....my bro's happy, and now I'm happy cause I don't have to hear him busting my balls anymore!!! ;) :D

Thanks again to all involved!!
 
  • Like
Reactions: scotty85
Upvote 0
have the same problem with other version ... can you somehow help me?

C:\Users\Ljube\Downloads\mini-adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.00.0030
INFOversion-baseband: 26.17.14.11_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 3.20.502.52
INFOserialno: HT1AWT204213
INFOimei: 358920047023590
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9812000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4182mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 62d2f26e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.010s
 
Upvote 0
have the same problem with other version ... can you somehow help me?

C:\Users\Ljube\Downloads\mini-adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.00.0030
INFOversion-baseband: 26.17.14.11_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 3.20.502.52
INFOserialno: HT1AWT204213
INFOimei: 358920047023590
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9812000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4182mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 62d2f26e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.010s

what same prollem do you have? prolly want to start a new thread,describing your issues,and how they came to be,with as much detail as possible,and we will help you :)
 
Upvote 0
Hey Guys,

I have almost the same problem on my htc desire HD
cannot boot into home screen,just stop with htc logo screen
I had follow all the steps here

and cannot pass the step

C:\mini-adb_inspire>fastboot flash zip RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.6
0.140e_26.03.02.26_M_release_155891_signed.zip
sending 'zip' (293949 KB)... OKAY [ 51.768s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 96.352s

this maybe the goldcard not right
but i tried to make again with this tools
h**p://forum.xda-developers.com/showthread.php?t=2288012
it's create a goldcard.img and build a goldcard sdcard
but still not pass the step

This is what hboot shows:
This is what it shows:

*** UNLOCKED ***

ACE PVT SHIP S-ON RL
HBOOT-2.00.0030
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Feb 20 2012, 16:03:18

HBOOT

to previous item
to next item
to select item

FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC

==================================
fastboot getvar all

INFOversion: 0.5
INFOversion-bootloader: 2.00.0030
INFOversion-baseband: 26.14.04.28_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.31.405.3
INFOserialno: [REMOVED BY MOD]
INFOimei: [REMOVED BY MOD]
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: HTC__621
INFObattery-status: good
INFObattery-voltage: 4169mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 62d2f26e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.010s

Can any one help me please !!
or send me a goldcard.img to try again
Thx a lot

i forgot to say that
my phone already have CWM 5.0.2.0 in my recovery
 
Upvote 0
i have got the cid of the phone

/sys/devices/platform/msm_sdcc.4/mmc_host/mmc2/mmc2:0001 # cat cid
cat cid
1b534d303030303010758891b700cc68

and use goldcardtool download here
hXXp://forum.xda-developers.com/showthread.php?t=2288012

still fail to flash RUU

C:\mini-adb_inspire>fastboot flash zip RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.6
0.140e_26.03.02.26_M_release_155891_signed.zip
sending 'zip' (293949 KB)... OKAY [ 51.768s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 96.352s
 
Upvote 0
I success make a new goldcard and pass cid check when flash zip RUU

but something more serious happen

C:\mini-adb_inspire>fastboot.exe flash zip RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.2
8b.60.140e_26.03.02.26_M_release_155891_signed.zip
sending 'zip' (293949 KB)... OKAY [ 48.495s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[radio] unzipping for pre-update...
INFOstart image[radio] flushing...
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,51
INFO[RUU]WP,radio,59
INFO[RUU]WP,radio,68
INFO[RUU]WP,radio,76
INFO[RUU]WP,radio,85
INFO[RUU]WP,radio,95
INFO[RUU]WP,radio,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 178.044s

after i pull the battery and put back
it just show a orange light
can not boot to hboot
>.<
 
Upvote 0
I success make a new goldcard and pass cid check when flash zip RUU

but something more serious happen

C:\mini-adb_inspire&gt;fastboot.exe flash zip RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.2
8b.60.140e_26.03.02.26_M_release_155891_signed.zip
sending 'zip' (293949 KB)... OKAY [ 48.495s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[radio] unzipping for pre-update...
INFOstart image[radio] flushing...
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,51
INFO[RUU]WP,radio,59
INFO[RUU]WP,radio,68
INFO[RUU]WP,radio,76
INFO[RUU]WP,radio,85
INFO[RUU]WP,radio,95
INFO[RUU]WP,radio,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 178.044s

after i pull the battery and put back
it just show a orange light
can not boot to hboot
&gt;.&lt;


That is a normal response. You just need to run the flash command again.

You currently are stuck in ruu mode.

You should be able to plug back in and get to fastboot/ruu mode and flash the file.

Sorry for the short answer, I'm at work at the moment. I'll try and watch if you have further questions :)
 
  • Like
Reactions: D-U-R-X
Upvote 0
I have a similar problem, but not quite the same. I've trolled across the internets trying to find a solution but it seems that each case of 'soft brick' is slightly different. Here's mine:

Last time I used the rooted and S-OFF DHD it was running an android 4.2 custom rom.

The phone has been sitting for a few months without being turned on... Last night I managed to get it to charge while turned off (constant orange light while plugged in) after removing the battery a few times. Then I left it charging for a couple hours to give me some juice to play around with.

Now the phone will turn on and give the HTC logo screen, but then freezes here. I can also get to HBOOT, but can't seem to load recovery. When I select recovery from HBOOT I just get a black screen. Last time I used this phone I had Clockworkmod recovery installed - but it seems to have disappeared along with the rom! I should also mention that the SD card that was in the phone last time it was used has been removed, reformatted and used in a different phone.

I've tried a few methods to flash recovery via fastboot, but I keep getting a fastboot error message saying "FAILED <remote: not allowed>".

A few forums have indicated that this error message means that I don't have S-Off. But I can confirm that HBOOT indicates that I do in fact have S-Off.

Can anyone point me in the right direction for a link to the allusive pd98img.zip file that I've heard about that will flash cwm again? I have already tried one pd98img.zip that seemed to flash but when I reboot to recovery I get a blank screen - so I'm not sure that I'm using the right file. Is there a specific pd98img.zip for an Australian dhd?
attachment.php

I promised my little brother I would get this phone working again. Any advice would be greatly appreciated. This is driving me nuts!
 
Upvote 0
I would recomend to run an ruu. If the phone is working after that,we can add recovery and root. Since you are s off,you are hopefully supercid as well,so you can run any ruu you wish.

You're getting the "remote not allowed" error because you're using a normal SHIP hboot. In order to fastboot flash recovery imagename.img you need either an eng hboot,or an unlocked htcdev hboot.

Let us know the results of the ruu :)
 
Upvote 0
I would recomend to run an ruu. If the phone is working after that,we can add recovery and root. Since you are s off,you are hopefully supercid as well,so you can run any ruu you wish.

You're getting the "remote not allowed" error because you're using a normal SHIP hboot. In order to fastboot flash recovery imagename.img you need either an eng hboot,or an unlocked htcdev hboot.

Let us know the results of the ruu :)

Thank you very much for your help and fast reply!

How do I install and RUU rom without being able to enter recovery? Sorry for the noob question!

thanks again
 
Upvote 0
How do I install and RUU rom without being able to enter recovery?

An RUU is an exe file that you run from your computer, with your phone plugged in - you wouldn't need to get in to recovery mode :)

Sorry for the noob question!

thanks again

No need to apologize - you only find out by asking question ;)
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones