• 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!!!

OK so I flashed this ROM. Before I did I wiped cache and dalvik cache.

It installed with no issues. When I go to reboot the phone, it brings me to a different screen. This one is a white screen (not as bright as the regular screen) with the HTC logo. But under the logo it says "quietly brilliant" in black writing. It's been stuck on this screen for about 5 minutes now.
 
Ok. I know its prolly getting tiresome,but try the adb steps one more time and.see.if.the outcome is any different
 
I'll try that out iowa. But where is the /tmp directory?? Probably a dumb question but I have no idea where to locate it.

Thanks again guys!

It would be done after pushing the file to the tmp folder. Then:

adb shell
cd data/local/tmp
ls -l

Should list the contents of the tmp directory. I had another idea too. Try redoing the commands both including the misc_version ending and withouth the misc_version ending but in both cases, try ending the command with a trailing backslash. So like this:

adb shell chmod 777 /data/local/tmp/misc_version/

or

adb shell chmod 777 /data/local/tmp/ <---that last backslash was added on both commands.
 
Ok. I know its prolly getting tiresome,but try the adb steps one more time and.see.if.the outcome is any different
This time the ADB commands worked without any issues:

C:\Users\daniels>cd c:\mini-adb_inspire

c:\mini-adb_inspire>md5sums RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.0
3.02.26_M_release_155891_signed.zip

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
Type md5sums -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inspire\]
RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28... 100% c3d244a9f056e48ee3851a14ff52204c

c:\mini-adb_inspire>fastboot devices
HT11ZTZ02579 fastboot

c:\mini-adb_inspire>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 0.626s]
booting... OKAY [ 0.001s]
finished. total time: 0.627s

c:\mini-adb_inspire>adb devices
List of devices attached
HT11ZTZ02579 recovery


c:\mini-adb_inspire>adb shell
~ # exit
exit

c:\mini-adb_inspire>adb shell /data
/sbin/sh: /data: Permission denied

c:\mini-adb_inspire>adb shell mount /data

c:\mini-adb_inspire>adb shell mount /system

c:\mini-adb_inspire>adb push misc_version /data/local/tmp
1189 KB/s (15837 bytes in 0.013s)

c:\mini-adb_inspire>adb shell chmod 777 /data/local/tmp/misc_version

c:\mini-adb_inspire>adb shell /data/local/tmp/misc_version -s 1.31.405.3
--set_version set. VERSION will be changed to: 1.31.405.3
Patching and backing up partition 17...

c:\mini-adb_inspire>adb reboot bootloader

c:\mini-adb_inspire>fastboot devices
HT11ZTZ02579 fastboot

c:\mini-adb_inspire>fastboot getvar mainver
mainver: 1.31.405.3
finished. total time: 0.001s

c:\mini-adb_inspire>fastboot getvar cid
cid: TELUS001
finished. total time: 0.001s

c:\mini-adb_inspire>


-------

So now I am at the stage where I need to re-lock the oem. Should I proceed?
 
So as soon as I tried the OEM lock, I got another error msg.

C:\Users\daniels>cd c:\mini-adb_inpsire
The system cannot find the path specified.

C:\Users\daniels>cd c:\mini-adb_inspire

c:\mini-adb_inspire>md5sums RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.0
3.02.26_M_release_155891_signed.zip

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
Type md5sums -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inspire\]
RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28... 100% c3d244a9f056e48ee3851a14ff52204c

c:\mini-adb_inspire>fastboot devices
HT11ZTZ02579 fastboot

c:\mini-adb_inspire>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 0.640s]
booting... OKAY [ -0.000s]
finished. total time: 0.640s

c:\mini-adb_inspire>adb devices
List of devices attached
HT11ZTZ02579 recovery


c:\mini-adb_inspire>adb shell
~ # exit
exit

c:\mini-adb_inspire>adb shell mount /data

c:\mini-adb_inspire>adb shell mount /system

c:\mini-adb_inspire>adb push misc_version /data/local/tmp
991 KB/s (15837 bytes in 0.015s)

c:\mini-adb_inspire>adb shell chmod 777 /data/local/tmp/misc_version

c:\mini-adb_inspire>adb shell /data/local/tmp/misc_version -s 1.31.405.3
--set_version set. VERSION will be changed to: 1.31.405.3
Patching and backing up partition 17...

c:\mini-adb_inspire>adb reboot bootloader

c:\mini-adb_inspire>fastboo devices
'fastboo' is not recognized as an internal or external command,
operable program or batch file.

c:\mini-adb_inspire>fastboot devices
HT11ZTZ02579 fastboot

c:\mini-adb_inspire>fastboot getvar mainver
mainver: 1.31.405.3
finished. total time: 0.016s

c:\mini-adb_inspire>fastboot getvar cid
cid: TELUS001
finished. total time: -0.000s

c:\mini-adb_inspire>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s


c:\mini-adb_inspire>


------

Right when the error msg popped up, the phone rebooted, and now it is stuck at that same white logo screen with "quietly brilliant" again.

Now it Says this on the HBOOT SCREEN again!

*** RELOCKED ***

ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011, 14:28:19

HBOOT

<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item

FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC

----
 
+1. Here's hoping you're back up and running!?!
No, not up and running yet.

I keep getting stuck at: c:\mini-adb_inspire>adb shell chmod 777 /data/local/tmp/misc_version.

It always looks like this....I tried soooo many times lol, same thing:

C:\Users\daniels>cd c:\mini-adb_inspire

c:\mini-adb_inspire>md5sums RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.0
3.02.26_M_release_155891_signed.zip

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
Type md5sums -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inspire\]
RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28... 100% c3d244a9f056e48ee3851a14ff52204c

c:\mini-adb_inspire>fastboot devices
HT11ZTZ02579 fastboot

c:\mini-adb_inspire>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 0.633s]
booting... OKAY [ 0.001s]
finished. total time: 0.634s

c:\mini-adb_inspire>fastboot devices

c:\mini-adb_inspire>adb devices
List of devices attached
HT11ZTZ02579 recovery


c:\mini-adb_inspire>adb shell
~ # exit
exit

c:\mini-adb_inspire>adb shell mount /data

c:\mini-adb_inspire>adb shell mount /system

c:\mini-adb_inspire>adb push misc_version /data/local/tmp
1189 KB/s (15837 bytes in 0.013s)

c:\mini-adb_inspire>adb shell chmod 777 /data/local/tmp/misc_version/
chmod: /data/local/tmp/misc_version/: Not a directory

c:\mini-adb_inspire>adb shell chmod 777 /data/local/tmp/misc_version
chmod: /data/local/tmp/misc_version: Not a directory

c:\mini-adb_inspire>adb shell chmod 777 /data/local/tmp/
chmod: /data/local/tmp/: Not a directory

c:\mini-adb_inspire>



 
when i said "continue on" i meant just run the commands to run the ruu. litterally,just go on to the next steps after fastboot oem lock

that command relocks your bootloader(wich is why it reads relocked after you run it) so that you can run the ruu. the "failed,too many links" error is par for the course,not really an error,so i just meant to ignore it.

once again,sorry for that confustion.

at this point,youve done all the steps and got the desired result:
c:\mini-adb_inspire>fastboot getvar mainver
mainver: 1.31.405.3
finished. total time: 0.016s


so heres what to do:

*stop beating yourself up with the adb steps and errors :)

put your phone in fastboot. from the ace recovery you can simply:
adb reboot bootloader

do this one more time just to verify the outcome:
fastboot getvar mainver

assuming you still get 1.31.405.3,then:

fastboot oem lock
expect the failed error,and the reboot,and the stuck on quietly brilliant.

pull the battery

power on to hboot,select fsatboot

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed.zip (if you get a cant open error,check for a space between 26 and .03. or any other spaces. there should not be any)

hopefully it will send,write,check,etc. then stuff will start flshing on the screen. if not,tell us the error

when it says 'finished'
fastboot reboot-bootloader
tell us the hboot info now

fastboot reboot
*cross fingers
 
It would be done after pushing the file to the tmp folder. Then:

adb shell
cd data/local/tmp
ls -l

Should list the contents of the tmp directory. I had another idea too. Try redoing the commands both including the misc_version ending and withouth the misc_version ending but in both cases, try ending the command with a trailing backslash. So like this:

adb shell chmod 777 /data/local/tmp/misc_version/

or

adb shell chmod 777 /data/local/tmp/ <---that last backslash was added on both commands.
When I check whats inside the /tmp folder it shows me this: (this is after pushing misc_version)

/tmp # ls -l
ls -l
-rw-rw-rw- 1 root root 4769 Jan 8 16:42 recovery.log
-rwxr-xr-x 1 root root 255904 Jan 8 16:42 update_binary
/tmp #
 
heres what the ruu flash will look:

Code:
c:\mini-adb_inspire>[COLOR="Red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.167s]
finished. total time: 0.168s

c:\mini-adb_inspire>[COLOR="red"]fastboot flash zip RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed.zip[/COLOR] [COLOR="Blue"](if you get an error check for spaces)[/COLOR]
     sending 'zip' (336097 KB)... OKAY [ 55.460s]
                 writing 'zip'... INFOzip header checking...
INFOshift signature_size for header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
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,100
...
...   [COLOR="blue"](many lines of similar [/COLOR]
...   [COLOR="blue"]removed for simplicity)[/COLOR]
...
INFO[RUU]UZ,dzdata,0
INFO[RUU]UZ,dzdata,100
INFO[RUU]WP,dzdata,0
INFO[RUU]WP,dzdata,100
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO[RUU]WP,rcdata,100
OKAY [ 78.951s]
finished. total time: 135.884s

c:\mini-adb_inspire>[COLOR="Red"]fastboot reboot-bootloader[/COLOR]
     rebooting into bootloader... OKAY [  0.155s] [COLOR="Blue"]will reboot to fastboot. verify 0.85.0007[/COLOR]
finished. total time: 0.155s

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

c:\miniadb_inspire>
 
When I check whats inside the /tmp folder it shows me this: (this is after pushing misc_version)

/tmp # ls -l
ls -l
-rw-rw-rw- 1 root root 4769 Jan 8 16:42 recovery.log
-rwxr-xr-x 1 root root 255904 Jan 8 16:42 update_binary
/tmp #

DVSimz,see above(post 63)... we dont need to keep messing with the adb commands
 
when i said "continue on" i meant just run the commands to run the ruu. litterally,just go on to the next steps after fastboot oem lock

that command relocks your bootloader(wich is why it reads relocked after you run it) so that you can run the ruu. the "failed,too many links" error is par for the course,not really an error,so i just meant to ignore it.

once again,sorry for that confustion.

at this point,youve done all the steps and got the desired result:
c:\mini-adb_inspire>fastboot getvar mainver
mainver: 1.31.405.3
finished. total time: 0.016s


so heres what to do:

*stop beating yourself up with the adb steps and errors :)

put your phone in fastboot. from the ace recovery you can simply:
adb reboot bootloader

do this one more time just to verify the outcome:
fastboot getvar mainver

assuming you still get 1.31.405.3,then:

fastboot oem lock
expect the failed error,and the reboot,and the stuck on quietly brilliant.

pull the battery

power on to hboot,select fsatboot

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed.zip (if you get a cant open error,check for a space between 26 and .03. or any other spaces. there should not be any)

hopefully it will send,write,check,etc. then stuff will start flshing on the screen. if not,tell us the error

when it says 'finished'
fastboot reboot-bootloader
tell us the hboot info now

fastboot reboot
*cross fingers
So I got an error right at the very end!!

c:\mini-adb_inspire>adb reboot bootloader

c:\mini-adb_inspire>fastboot getvar mainver
mainver: 1.31.405.3
finished. total time: 0.002s

c:\mini-adb_inspire>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.163s

c:\mini-adb_inspire>fastboot devices

c:\mini-adb_inspire>fastboot devices
HT11ZTZ02579 fastboot

c:\mini-adb_inspire>fastboot erase chache
erasing 'chache'... FAILED (remote: not allowed)
finished. total time: 0.002s

c:\mini-adb_inspire>fastboot erase cache
erasing 'cache'... OKAY [ 0.465s]
finished. total time: 0.466s

c:\mini-adb_inspire>fastboot oem rebootRUU
... OKAY [ 0.154s]
finished. total time: 0.155s

c:\mini-adb_inspire>flash zip RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26
.03.02.26_M_release_155891_signed.zip
'flash' is not recognized as an internal or external command,
operable program or batch file.

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 [ 49.783s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 93.234s
 
crap! ok that means that your gold card is not made correctly,or it is not in the phone :eek:

assuming it is in the phone,we have a couple options:
1)you can try and remake it so we can run the ruu were trying to run(for wich i have additional motives :D)

2)we can simply try running a telus branded ruu that will pass the cid check.

the important thing is that we have successfully lowered the main version,so findning an ruu for you now is going to be fairly easy :)
 
crap! ok that means that your gold card is not made correctly,or it is not in the phone :eek:

assuming it is in the phone,we have a couple options:
1)you can try and remake it so we can run the ruu were trying to run(for wich i have additional motives :D)

2)we can simply try running a telus branded ruu that will pass the cid check.

the important thing is that we have successfully lowered the main version,so findning an ruu for you now is going to be fairly easy :)
OK i will try to re-make the gold card now.
 
OK i will try to re-make the gold card now.

you are so close now! i hate that the gold card is what is tripping you up.

as i said,if you get tired of messing with it,there are a couple other ruus you can try that should pass the CID check,so give yourself a high 5,as you have accomplished alot by successully chaning the main ver.
 
i have to step out for a bit,but if it comes down to it,i think this is the ruu you should try: Shipped ROMs

it is not the newest telus ruu,but we dont want to jump right to the newest,as that will change the main version back to a higher number,and not leave any ruus to run. if we start with the oldest,and the phone boots,we can then OTA or run an ruu for the newer software. if it continues to not boot,we can always keep runing newer ruus until either it works,or we run out of ruus to flash :)
 
i have to step out for a bit,but if it comes down to it,i think this is the ruu you should try: Shipped ROMs

it is not the newest telus ruu,but we dont want to jump right to the newest,as that will change the main version back to a higher number,and not leave any ruus to run. if we start with the oldest,and the phone boots,we can then OTA or run an ruu for the newer software. if it continues to not boot,we can always keep runing newer ruus until either it works,or we run out of ruus to flash :)
So tried the original RUU and it didn't work again. I am currently downloading the last one you just sent:

Shipped ROMs

But i noticed that it is an .exe file. How would I run this file type??

Do I use the same method even though its not a zip file??
 
Easiest way will be to just place the phone in fast boot,and then run the utility as administrator if possible(if not,just run it) and then plug the phone in wen the utility directs you.

If the utility has prollems running,I can upload a .zip,or give you instructions on how to extract "ROM.zip" from the utility. You can then run that using the same method as you did before :)
 
you are so close now! i hate that the gold card is what is tripping you up.

as i said,if you get tired of messing with it,there are a couple other ruus you can try that should pass the CID check,so give yourself a high 5,as you have accomplished alot by successully chaning the main ver.
IT WORKED!!!!!!!! I Followed all the steps again using:

fastboot flash zip RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed.zip

This is what it showed at the end of alot of lines:

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
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO[RUU]WP,rcdata,100
OKAY [327.246s]
finished. total time: 376.496s

c:\mini-adb_inspire>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.165s]
finished. total time: 0.166s

c:\mini-adb_inspire>fastboot reboot
rebooting...
finished. total time: 0.161s



It Finally loaded to the home screen!!!! It says no Sim Card Inserted. I'm sure my brother can just put his in!!

am I ok to start using the phone now, or is there a better RUU that I can install for him??

Thank you guys sooooo much for ALL YOUR HELP!!!!!!!!!!!
 
Back
Top Bottom