yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] Alex-V:
i read this...:

i downloaded the RUU from XDA-Developers and used RUU_Bravo_hTC_Asia_WWE_1.19.707.7_Radio_32.36.00.2 8U_4.06.00.02_2_release_126179_signed.exe to unroot my phone. yes there is newer HBOOT now, it's 0.83 if i'm not mistaken (it comes from HK froyo rom we talked about earlier). so if you flash the official froyo rom, you will probably not be able to root it back for some time till someone solves it, if nobody solves it means you will never be able to root it again.

from here:

http://forum.lowyat.net/topic/1469656/+1260

and the ruu here:

http://htcpedia.com/forum/showthread.php?t=2907

but don´t know if i understand it right...sorry i´m german
[Desire Q&A, Help & Troubleshooting] SavageCore:
Ok I used RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed.exe from fastboot and managed to get my phone working again.

Thanks for all the help. Will await 0.83 root...
[Desire Q&A, Help & Troubleshooting] Alex-V:
:):):):):p:p:p Congratulations:p:p:p:p:):):):)

with kind regards...Alex
[Desire Q&A, Help & Troubleshooting] mmm_ok:
Hey, could you please tell me exactly how you did this with fastboot. Thanks!
[Desire Q&A, Help & Troubleshooting] Alex-V:
mmhh..i think you are off..if you read this...exlpain a bit more please... :)

edit: and make a link in modaco :)
[Desire Q&A, Help & Troubleshooting] SavageCore:
Okay so these were my steps.

Held down back and power

Waited a few seconds

Plugged in USB

Checked device manager and saw bootloader (could check with fastboot devices)

Ran http://shipped-roms.com/shipped/Bra...1.00.32U_4.08.00.09_release_137222_signed.exe

Gave error about battery percentage, restarted with holding back

Ran again and everything worked by following prompts

Good luck!
[Desire Q&A, Help & Troubleshooting] mmm_ok:
It still doesn't work for me

I get error 140 doh!
[Desire Q&A, Help & Troubleshooting] Alex-V:
i think that this must be the driver...correct...??

i go to bed now....good luck...with kind regards...Alex
[Desire Q&A, Help & Troubleshooting] SavageCore:
Yes actually I just remembered. Once when I was trying my various things device manager said the device could not be started because the driver was in memory so I disconnected everything, waited a few secs and started again as I explained earlier.

Hope this helps more...
[Desire Q&A, Help & Troubleshooting] sandervanzijl:
you restarted the phone by holding the back key?

could you explain that step, because i am in the same load of ****.

only as an extra, booting and connecting to windows does not work very well
[Desire Q&A, Help & Troubleshooting] man00va:
And this was with 0.83? Which carrier are you with?
[Desire Q&A, Help & Troubleshooting] SavageCore:
I mean I turned it off and on again but with holding power and back.

0.83 unbranded Orange.
[Desire Q&A, Help & Troubleshooting] mmm_ok:
That's weird. On my voda branded 83 I get bootloader version error 140.

I wonder what's different?
[Desire Q&A, Help & Troubleshooting] SavageCore:
Have you tried various RUU's from http://shipped-roms.com/shipped/Bravo/? I was getting 140 from some until I found that current one.
[Desire Q&A, Help & Troubleshooting] teppic74:
You used RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed.exe ? Does this contain HBOOT 0.83?
[Desire Q&A, Help & Troubleshooting] sandervanzijl:
I cannot get it to work. i keep getting the error.

i think i have hboot 0.75 or 0.83, but nothing wants to flash.

the solution for this requires you to be able to use the phone, but since the screen is dead.......

anyone have another ruu that always works?
[Desire Q&A, Help & Troubleshooting] SavageCore:
It does, sadly.

Which error? When holding power and back it should be in fastboot and technically you don't need to see anything. Just plug in usb and flash with RUU...
[Desire Q&A, Help & Troubleshooting] teppic74:
So it's either hboot 0.83 or the updated radio that fixed it, as the software version is the same otherwise. It's a shame we don't have an RRU with hboot 0.80 and radio 4.08 - if that worked it'd solve all the problems.
[Desire Q&A, Help & Troubleshooting] mmm_ok:
I'm having the same problem...

My screen is dead, but I can get into fastboot (i can fastboot devices)

but when I try to run the RUU:

RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed.exe

I get error 140.

I'm wondering if the error is not the hboot version but a problem with the CID, it worked fro Savage, but he had an unbranded phone

If only I could Enable USB debugging... anyone know how to do this without using the device screen?
[Desire Q&A, Help & Troubleshooting] teppic74:
You must have used your goldcard to apply the downgrade in the first place? It should still be ok to use that.

You could try the debrick method. This will update your MISC partition and might get rid of the 140 error.
[Desire Q&A, Help & Troubleshooting] mmm_ok:
yes I used the goldcard to apply the downgrade... I'm pretty sure the problem is that this is a SLCD Desire variant and that the downgrade described puts on AMOLED display drivers.

I tried to do the MISC partition, but I can't enable use debugging because I can't use the screen grrrrrr

I need to have USB debugging on to do the MISC partition thingy, right?
[Desire Q&A, Help & Troubleshooting] beanyforever:
I'm in the same boat as you mmm_ok. Have a voda Desire and used unrevoked3 to root it. I then used the ROM Manager App to install a custom ROM. Now I have a phone I cant use and cant root. If only Vodafone released their RUU it would be a simple fix as fastboot works fine. I have tried the RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed ROM and it has the correct radio and bootloader versions but because the software build number is 1.21 not 1.24 it throws up error 140.

Three options:

1. somehow force the phone into reporting a version lower than the above RUU

2. hope that a vodafone RUU will hit the internet with version 1.24

3. send phone back
[Desire Q&A, Help & Troubleshooting] teppic74:
USB debugging isn't necessary for using fastboot. Though if you root with unrevoked3 I guess you won't be able to apply the debrick update unless you can see the screen, unless there's a definite way to do it blindly.

One more option is to use the r6 root method and try it that way. There's info on that here:

hxxp://android.modaco.com/content/htc-desire-desire-modaco-com/309939/usb-brick-rickrolled-b0rked-fixed/
[Desire Q&A, Help & Troubleshooting] SavageCore:
Surely the creator of unrevoked could fix this display driver issue? There must be a solution.
[Desire Q&A, Help & Troubleshooting] beanyforever:
@teppic74 - the r6 method only works for 0.80, the voda desire is on 0.83 so you get a main version error with that method too (this time for the boot ROM instead of the main ROM). Basically we need a r7 method for use with 0.83

@SavageCore - You are correct, this is simply a driver issue, the new SLCD screens use a different driver. If ClockworkMod Recovery release an image with the driver then we could use ClockworkMod to sort out this mess :-(
[Desire Q&A, Help & Troubleshooting] teppic74:
He has applied this downgrade, so is now on hboot 0.80 and 1.21 - and this is what seems to stop the display from working. So the r6 method should work, though applying a recovery image blindly might be difficult.

The error with the RUU could be because the misc partition has the wrong information in it, which the debrick method should fix. Normally this is simple to fix.
[Desire Q&A, Help & Troubleshooting] mmm_ok:
Yep, I tried the r6 root method, but I get this:

C:\android-sdk-windows\tools\mo>step1-windows.bat

Desire Root Step 1

Erasing cache and rebooting in RUU mode...

erasing 'cache'... FAILED (status malformed (1 bytes))

... FAILED (status malformed (1 bytes))

About to start flash...

sending 'zip' (138708 KB)... FAILED (status malformed (1 bytes))

sending 'zip' (138708 KB)... FAILED (status malformed (1 bytes))

Rebooting to bootloader...

rebooting into bootloader... FAILED (command write failed (Unknown error))

Step 1 complete - now use the bootloader menu to enter recovery mode.
[Desire Q&A, Help & Troubleshooting] teppic74:
This may be because you are in hboot rather than fastboot. When you power on use the back key instead of vol down.
[Desire Q&A, Help & Troubleshooting] mmm_ok:
Ah well spotted you're right!

I'll crack on and let you know how it goes
[Desire Q&A, Help & Troubleshooting] mmm_ok:
ok step 1 completed, there are some failures though... it this ok or not, do you know?

Erasing cache and rebooting in RUU mode...

erasing 'cache'... OKAY

... OKAY

About to start flash...

< waiting for device >

sending 'zip' (138708 KB)... OKAY

writing 'zip'... INFOadopting the signature contained in this image...

INFOsignature checking...

INFOzip header checking...

INFOzip info parsing...

INFOchecking model ID...

INFOchecking custom ID...

INFOchecking main version...

FAILED (remote: 43 main version check fail)

sending 'zip' (138708 KB)... OKAY

writing 'zip'... INFOadopting the signature contained in this image...

INFOsignature checking...

INFOzip header checking...

INFOzip info parsing...

INFOchecking model ID...

INFOchecking custom ID...

INFOchecking main version...

FAILED (remote: 43 main version check fail)

Rebooting to bootloader...

rebooting into bootloader... OKAY

Step 1 complete - now use the bootloader menu to enter recovery mode.
[Desire Q&A, Help & Troubleshooting] Alex-V:
Sounds good ;)
[Desire Q&A, Help & Troubleshooting] teppic74:
I think that means it has failed to flash the rooted image. I don't know much about the r6 method so can't really help there. The threads on modaco.com might be helpful.

There will be a way of applying the misc partition fix update using unrevoked3, but it will be more difficult without a display.
[Desire Q&A, Help & Troubleshooting] mmm_ok:
Luckily I've got my desire here to help step me through the fastboot menus, otherwise I would know the order LOL

The MISC fix didn't work though, I think it's because of the failure of the root :-(
[Desire Q&A, Help & Troubleshooting] teppic74:
Someone who has unrevoked3 should be able to tell you which buttons to press to apply the update.zip image to fix the misc partition. Once that is done, hopefully you will be able to flash the RUU.
[Desire Q&A, Help & Troubleshooting] Alex-V:
OK: so for a update.zip

1.Vol Down (hold) +power

2.wait (check sd)

3.Vol down (without hold) and power

4.wait (because load) ->now in recovery of unrevoked

5.vol down and press trackball

6. 7x vol down and press trackball

7. now it should be flash (i think wait 15 min because flash) and then reboot
[Desire Q&A, Help & Troubleshooting] mmm_ok:
I can't use unrevoked becuase I can't enable usb debugging :-(
[Desire Q&A, Help & Troubleshooting] Alex-V:
but you can acsess recovery now...?
[Desire Q&A, Help & Troubleshooting] mmm_ok:
Well, i can access the "normal" recovery... Does that make sense? It's not the recovery that you get when you're rooted, but the recovery with only a few options... sorry I'm a bit of a noob
[Desire Q&A, Help & Troubleshooting] teppic74:
I thought you could run unrevoked3 from the phone in fastboot. If not then I'm not sure what to suggest other than trying to get the r6 method working, or maybe trying to flash stock FroYo (it may work now you have unbranded software).
[Desire Q&A, Help & Troubleshooting] teppic74:
If you just want to get the phone working and don't care about root/custom roms, you could try the FroYo update. To do this, download this image:

hxxp://liveimage.htc.com/OTA_Bravo_Froyo_HTC_WWE_2.09.405.8-1.21.405.2_release4dua3bcrut4wrv30.zip

And rename it to update.zip and just do a 'normal' recovery. It will update hboot to 0.92 and that might get the display working again.
[Desire Q&A, Help & Troubleshooting] qwertylesh:
Unless Ive followed this thread incorrectly, you unrevoked but then it was when you ran the very first rom that messed up the display right?

if so, then when you very first vol down + power, then when you press vol down once in that screen (I do know the irony since you cant see it) but that selects an option in that first recovery menu, called recovery, you should be able to see it on your unbricked desire. if you chose that, it will reboot the phone and go into the unrevoked recovery.

in short, if the unrevoked didnt mess up the display (and quite possibily even if it did) the instructions should still work, provided that unrevoked did install onto your flatmates desire the very first time.

I think its worth trying what Alex has suggested blindly, my only concern is if the trackball will move around the highlighter in the unrevoked menu, Im checking it now.

I just checked and the trackball touch sensor does move the unrevoked highlight/selection bar, so be careful. It may even be worth instead of 7x vol down, to actually do 7 swipes then pres into the trackball without swiping up or down.
[Desire Q&A, Help & Troubleshooting] marinierb:
Here's a silly question, but if the SLCD screen requires a special driver, will the custom ROM's work? ie. do all Android distributions have that special display driver?
[Desire Q&A, Help & Troubleshooting] teppic74:
I think that they require 0.83 or higher hboot. But you can't flash custom roms with this hboot anyway.
[Desire Q&A, Help & Troubleshooting] SavageCore:
So I decided to flash 2.2

Anything over hboot 0.83 have the new display drivers? so if I follow the downgrade guide here i'll have no display you think?
[Desire Q&A, Help & Troubleshooting] teppic74:
Do you have an SLCD display? It seems that it needs hboot 0.83, so it should be fine with froyo (the update has 0.92). You won't have any safe way to downgrade, rebrand or root your phone though.
[Desire Q&A, Help & Troubleshooting] heavymetalmage:
I would almost guarantee that nothing below 0.83 has the display drivers. 0.92 might.
[Desire Q&A, Help & Troubleshooting] sandervanzijl:
wrong bootloader error.

everything goes okay, until after updating of the signatures, then i get the bootloader version error.

i have not found a good ruu yet
[Desire Q&A, Help & Troubleshooting] SavageCore:
Okay thanks

Only real reason I would have rooted was to remove start up noise but there's an app for that, should be ok. Unless it turns off without shutting down.

Don't know what to suggest sorry. Apart from trying various RUU's till it actually flashes.
[Desire Q&A, Help & Troubleshooting] teppic74:
I saw a post somewhere else where someone had lost their display by using this downgrade, fixed it with the latest RUU flash, and then successfully upgraded to froyo OTA and everything was fine.
[Desire Q&A, Help & Troubleshooting] heavymetalmage:
Hmm... 0.92 must support the SLCD screens then. All that would be needed would be a custom recovery (i.e. clockworkmod) that would support those screens. From there I'm not sure if the custom ROM would need to have any modifications to support the screen or not.
[Desire Q&A, Help & Troubleshooting] sandervanzijl:
i read it too, but it is not working for me.

what i did was apply a downgrade over a clockworkmod that did not show the recovery screen. then applied a rom.

so now i do not know exactly which bootloader i have, and i can not acces anything because i do not have a display.

i have no way of getting any image on my phone, because aomehow the microsd card is inreadable when i cannoct the phone, and i have no computer to use a microsd card in.

the only possibility for me, is if a could find a ruu that works.

the onces suggested here, do not work at all.
[Desire Q&A, Help & Troubleshooting] heavymetalmage:
Is your phone branded?
[Desire Q&A, Help & Troubleshooting] :
Just a suggestion. How about downgrading your HBOOT? Did you try the PB99IMG.zip trick?

Just a thought, it may not work.

I have a branded Desire (A8183) and when I flashed the UK ROM 1.21.405.2 and updated to Froyo. I used the PB99IMG.zip to downgrade my HBOOT from 0.92 to 0.80.

I know that you have problems with your screen but you can always take the SD card out of the phone and plug it in your PC\Laptop and transfer the PB99IMG.zip file and then put it back on the phone and reboot. Hold down volume down button and press power to reboot. and that's all you have to do. And then it will ask you if you want to update and you just press the volume UP button and the process will start.

I know you can't see the screen but just wait for a minute or two and just press the volume up button if you still have no screen.
[Desire Q&A, Help & Troubleshooting] TymmyD:
Has any one tried Rom manager with a gold card to boot a new Rom? we know the unrevoked root works and it might be just the display drivers causing the problem , so flashing a new Rom might work. Only thing is when it boots into recovery you can't see if all went well or not until it reboots itself. I have a friends desire in the root state but just cannot see the recovery. But have managed to do a Rom backup (nandroid) using Rom manager. Vodafone 0.83.
[Desire Q&A, Help & Troubleshooting] marinierb:
I think *you* should try it. :D
[Desire Q&A, Help & Troubleshooting] heavymetalmage:
I think that a FroYo based ROM should support the SLCD screen. I could be wrong though. I think you should try it but flash at your own risk!
[Desire Q&A, Help & Troubleshooting] jokeyrhyme:
In the early days if you sent a phone back to the manufacturer in that condition, the support guys would lazily assume the motherboard was broken and replace it for free. Not sure if they actually test for the obvious signs of ROM tampering yet.
[Desire Q&A, Help & Troubleshooting] Jam Sandwich:
I'm in the same situation as sandervanzijl. I can see via fastboot that the HBOOT version is now 0.80 and obviously that's why I can't see anything on my screen (Vodafone UK branded desire btw).

So... how do I upgrade 0.80 to 0.92? By installing the latest OTA? If I can't do that via RUU - it wont work, for any version - does that mean I have to get the sdcard fix first or is there a way to update purely using fastboot? Should I try blindly downgrading from 0.80 to something else?

Just trying to get my head round my options here :)
[Desire Q&A, Help & Troubleshooting] Jarua:
Same problem here. Tried upgrading, screen no longer functioned. I can't find a single RUU to get it working again. I managed to downgrade hboot to 0.8 (as far as I know, it's hard to tell without a screen... but it seems the annoying HTC chime on-boot is back).

So, now the rom update utility is telling me that I have 1.21.405.2, but I can't find any RUU that'll both run and restore the screen. I'd try updating to 2.2 via update.zip, but doing that without a screen is going to be impossible right?
[Desire Q&A, Help & Troubleshooting] Jam Sandwich:
I'm going to try the latest OTA, renamed to update.zip, using the instructions in post 74 of this thread.

Might take a while, the only way I can get access to the SDCard is by chucking it in my unreliable old nokia and mounting it that way (unless someone knows how to mount an sd card in ubuntu once I use fastboot to enable it)
[Desire Q&A, Help & Troubleshooting] Jarua:
Let me know how you get on Jam.

Re: the Froyo driver situation, just a bit of extra info - I upgraded to 1.22.771.1 (3 UK distribution) in a desperate attempt to get the screen to work, and it didn't. Hopefully the generic 2.2 update will be different?

Edit: I've found an RUU that should work fine with the screen, but I get the infamous error 140. If I can manage to root the phone, does that make it possible to install any version from an RUU?

Edit 2: Hmm, it looks like rooting it without a screen is next to impossible anyway.
[Desire Q&A, Help & Troubleshooting] teppic74:
Almost all of the 2.1 RUUs have hboot 0.80 and so will not restore the screen. The one that will work may not install correctly because of the problem with the misc partition, that is normally easily fixable by rooting. The FroYo update (which can be installed by update.zip instead of an RUU) will still probably work if you've debranded, but you won't be able to downgrade without losing the display again.
[Desire Q&A, Help & Troubleshooting] Jarua:
I'd be fine with never having to downgrade, the only thing preventing me from trying the update.zip method is not being able to find any instructions that don't mention unrevoked a lot. (AlexV's/qwertylesh's instructions in post 74, for example)

I didn't mess around with unrevoked, I just had a stock Desire which I applied the RUU to (breaking the screen in the process). Is unrevoked relevant to those instructions?

Edit: It looks like instructions for a normal recovery (when a user hasn't used unrevoked) is different to the instructions provided... I don't suppose anyone could talk me through the button presses for a normal recovery to update with update.zip?
[Desire Q&A, Help & Troubleshooting] teppic74:
You don't need to root or do anything unusual in order to apply the FroYo update, you only need that for custom recovery. It's not impossible to do with a broken screen, just do this:

1. Make sure the update.zip file is on your goldcard and correctly named.

2. Take the battery out first to ensure the phone is powered off. Then hold vol down and press the power button, and hold vol down for about 5 seconds. That will get you into the bootloader even though you can't see it.

3. Press vol down once. This will select recovery.

4. Press the power button once. This will start the recovery. The phone will vibrate briefly.

5. Wait 20 seconds or so. Then press vol up and the power button and wait a few seconds. You'll now be in system recovery.

6. Press vol down once to select 'apply sdcard:update.zip'.

7. Press the power button once to start the recovery.
[Desire Q&A, Help & Troubleshooting] Jarua:
Done, thanks for the instructions. Hopefully it's installing the update now.

Edit: Presumably I won't know when the update is complete... so it's a safe bet to leave it for an hour, then restart by removing the battery?
[Desire Q&A, Help & Troubleshooting] teppic74:
I don't think that you need to do anything more for the upgrade to run but I'm not certain. If it doesn't work you may want to try the downgrade to 1.21 again first as this is what people are normally updating to froyo ota from.
[Desire Q&A, Help & Troubleshooting] trenwei:
Which bootloader did you have? unbraded/branded??
[Desire Q&A, Help & Troubleshooting] teppic74:
I missed this part. If you successfully flashed a branded ROM you almost certainly won't be able to update to FroYo using the recovery method. You'll need to reapply the downgrade (as per HBOOT 0.92 to 0.80) first. Then try the recovery again.
[Desire Q&A, Help & Troubleshooting] Jarua:
teppic74: Your instructions were perfect, the screen is back in action - thanks!

Edit: After the 3 UK update, I managed to roll back to an earlier generic version using the hboot downgrade technique. (Which is why the update.zip method worked.)
[Desire Q&A, Help & Troubleshooting] teppic74:
Ah, great! This method should then work for anyone then.
[Desire Q&A, Help & Troubleshooting] wickedpenguin:
If you are getting an 140 error when running RUU then its probably due to the fact that you have the wrong Android phone driver. Same issue happened to me.

You need to boot your phone into recovery, then go into device manager and uninstall the driver for " Android Phone "

Once thats uninstall unplug your device and plug back in, it should download the correct driver, not the unrevoked one.

Once that is done, reboot your phone as per normal, then reboot your PC, try running RUU again and it shouldn't have that error.

Let me know the results.
[Desire Q&A, Help & Troubleshooting] sandervanzijl:
yes it is branded, but i hoped to have created a goldcard.

maybe something is wrong with the goldcard.

i have access to the sdcard by putting it in my girlfriends phone.

but i can not get my phone to update from it.

it does not help that i cannot see what it is doing.