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

Root HTC Desire HELP!

No, you don't need "disk drive" mode. You want the phone to be in "fastboot" mode, which is what steps 2 and 3 will do.

I've never run an RUU, but I'm pretty sure that you don't need HTC Sync because (a) the phone isn't running Android during this, and (b) SUroot would have said if anything else was needed (he's the guru here).
 
No, you don't need "disk drive" mode. You want the phone to be in "fastboot" mode, which is what steps 2 and 3 will do.

I've never run an RUU, but I'm pretty sure that you don't need HTC Sync because (a) the phone isn't running Android during this, and (b) SUroot would have said if anything else was needed (he's the guru here).

Great. I think i'm going to let the phone charge for about 30 minutes before I begin. I'll post my results once i'm done.
 
Let it charge fully. There's no rush, and you really don't want an RUU flash to be interrupted by loss of power.

One step forward, two steps back? Ok, I can see my screen now, however it just sits on the booting screen. (It just shows "htc" with a white background.)

I can however, access the menu by pressing the volume down and power button. I am back to Hboot 1.06, Radio 2.15.00.11.16, and it is now S-ON.

What would you guys advise I do? (I would still like to eventually root my device.. D:)
 
Hmm. Could try clearing storage see if that helps...

I don't think revolutionary will s-off without android booting so getting booting is all we can do
 
Hmm. Could try clearing storage see if that helps...

I don't think revolutionary will s-off without android booting so getting booting is all we can do

That didnt work. By the way, I forgot to mention that the process you had me do from windows with the RUU failed. Mabye thats why the screen works but it wont boot. I'm about to try the process again.
 
That didnt work. By the way, I forgot to mention that the process you had me do from windows with the RUU failed. Mabye thats why the screen works but it wont boot. I'm about to try the process again.

I got the same results as before: ERROR [131]: CUSTOMER ID ERROR

The ROM Update Utility cannot update your Android phone.

Please get the correct ROM Update Utility and try again.
 
You may have done it right but it just didn't work. There's a goldcard tool. Have a read of the rootingfaq, there's a goldcard section
 
It's the root faq, in the "all things root guide" sticky thread.

You really need to read all these faqs, before you do anything else.
 
Usb debugging only works in android so its irrelevant.

Goldcard is the only way. Have you another sd to try?
 
Sorry, offline most of last night & today will be no better.

One thought: is it worth trying the PB99IMG method? See Droidzone's faq http://androidforums.com/desire-all...rd-bricking-ruu-fastboot-recovery-others.html

Also, TimTim, what does it say at the top of the white screen? If the cid check failed every time I'm surprised that the RUU did anything at all, so want to check whether the alpharev hboot has bee replaced.

This is what it shows in the Debug Log:
"Executing adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
Reading adb output
------------------------
* daemon not running. starting it now *
* daemon started successfully *
------------------------
Could not locate CID in output"

Note: This is when I have the phone on the menu with the three little android guys on it.. If I try to start my phone normally, (Which it gets stuck on the HTC screen remember..) It pops up with an error code on my computer telling me that access to a certain file is denied..

I suppose i'll try the other method now.. Do you have a link to the zip file? Thanks.

Update: Ok, after following the guide and getting thr ROM file, renaming it and putting it onto the SD card.. It failed. It said "CID Check Failed.."
 
Damn, I was hoping that the CID check might not happen with the PB99IMG.

What does it say at the top of the white screen with the little androids?
 
Not sure if it helps but a screen shot from official ntelos documentation for the original ota to froyo shows the Rom is actually a utstarcom generic build.
 
Back
Top Bottom