Develop Bugs

[Q] HTC Desire Stuck at Why so serious?

hi i have used evo3 on my htc desire to root and then used alpharev and boht said succussfull. Now phone starts and only shoes joker and written why so serious? doesnt go further at all. any help please
Regards

got a bootloop.. try running an RUU file (this will flash back to stack, get rid of root)
then try to root again, just a different method?
hope this helps!

how to flash with ruu if your phone is stuck not even being detected by PC. any detail please thanks regards

faisal_sherry said:
how to flash with ruu if your phone is stuck not even being detected by PC. any detail please thanks regards
Click to expand...
Click to collapse
First of all: be sure you know what you're doing. The below listed solutions might help but might also end up bricking your phone dead.
If you can enter fastboot (back while powering on the phone) and if you have a nandroid backup, you can try to flash it back using the fastboot flash command.
OR
It's possible to run the RUU update while in fastboot or hboot usb mode (back button while powering on the phone) I had the modified usb drivers installed http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install, not sure if that is needed - but the original drivers didn't work very well with my setup in general: Win7 x64 , also I uninstalled HTC Sync.
OR
If that fails, you can try to extract the rom.zip from the RUU and flash it manually (help on extracting http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html ) JUST DON'T USE THE ROM FROM THAT TUTORIAL, THE LINK IS JUST FOR REFERENCE ON HOW TO EXTRACT THE rom.zip
The offcial RUU are in this thread, just BE SURE TO USE THE CORRECT ONE http://forum.xda-developers.com/showthread.php?t=695667
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom.zip

@quanchi, thanks for your help i'll try and let you know tomorrow thanks again
Regards

hi i have tried the method putting phone in fastboot mode pressing back and power phone was detected and then flashed with this rom 'RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed'' and it was successufll now my phone is not turning on when i press power it vibrates but nothing on the screen but good thing is when i connect the phone with pc it still detects it its not brick yet i think any help
Regards

faisal_sherry said:
hi i have tried the method putting phone in fastboot mode pressing back and power phone was detected and then flashed with this rom 'RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed'' and it was successufll now my phone is not turning on when i press power it vibrates but nothing on the screen but good thing is when i connect the phone with pc it still detects it its not brick yet i think any help
Regards
Click to expand...
Click to collapse
Is your phone SLCD? I reckon you may have flashed an incorrect RUU, in which case you'll need to get a more up-to-date one and flash it again. In case that's the most recent one for T-Mobile, you'll need to make a gold card and then flash a generic RUU. Hope that helps.

hi thanks for your reply i don't know what is slcd? and let me tell you the stat of the phone now
when i press power phone vibrates i can see button lights on the phone but nothing on the lcd screed. Phone is not going in boot mode when i press back and power nothing happens, volume up and power nothing happens. Phone is being recognized in device manager as a usb mass storage and i can see battery light on the top of the screen as well. I dont know what is the real state of my phone and what do you call it but its a t mobile UK phone that's what i know and what should i do now thanks
Regards

SLCD is a type of display present in some Desires, earliest Desires had an AMOLED display. You most probably flashed your SLCD Desire with RUU prepared for an AMOLED Desire, hence the display problems. Search the forum for "SLCD BRICK". Your phone should be able to enter fastboot/hboot, but doesn't display anything because the display handling is screwed up. Before trying to resolve your situation BE SURE TO READ ALL THE INFO ON SLCD UNBRICKING.
I have no experience with SLCD models so can't help you much on the subject, but there are numerous threads on xda detailing dealing with this particular issue.
I don't want to sound rude or holier than thou (as I had my share of bricks and semi bricks) but I did write that you should make sure you get the correct RRU...
best of luck
Sent from my HTC Desire using XDA App

hi thanks for your reply i'll try n post the result here
Regards

So here I will describe what I did to solve the exact same issue.
Remove the battery from the phone
Copy the proper RUU file to the root of my SD card naming it PB99IMG.zip
Insert battery
Power on phone holding the power and the back buttons until the fastboot menu opens
Choose recovery
Then it will go through a bunch of stuff and ask you if you want to flash the file you put on the SD card, I said yes then a few minutes later Bobs your uncle I was back to factory.

faisal_sherry said:
hi thanks for your reply i'll try n post the result here
Regards
Click to expand...
Click to collapse
Faisal, it seems apparent that your device is an SLCD Desire. When you put Alpharev on it, it did S-OFF and your boot got corrupted for some reason and looped. When you ran the RUU (which was incompatible for your SLCD, and actually meant for an AMOLED Desire), you effectively unrooted it, though not restoring it.
Check my thread for a similiar problem.
If you had made a Goldcard earlier, you're in luck. You can restore your device with a generic SLCD RUU available for your device, by either running the RUU or by flashing the rom.zip from the RUU.exe file (Tip. This file gets extracted to %TEMP% folder when you run an RUU)
Things you need to know before you try solving your problem:
Know how to use adb from the command prompt,
Search for the links to shipped-roms site containing the list of Bravo (Desire) ROMS
How to create and use a goldcard
How to navigate to the temporary folder of your Windows PC
How to turn your device on into Recovery mode and Fastboot without seeing the screen
Simple search on XDA can unravel these simple mysteries.
Now, the steps to go about solving your problem:
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code which prevents you from flashing a ROM meant for any other brand and also blocks a Generic RUU. If you're from India, it is branded with HTC Asia_India. If you're unbranded, things are looking much easier for you, as generic RUUs for SLCD are easily available.
Check if you have a goldcard (A goldcard is a special microsd card you made while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA)
If you dont have a goldcard, you might try to see if Recovery can be booted up. Poweroff phone, then power it on by pressing Vol- and Poweron key, then wait 30sec and press Vol Down and Poweron button again. At this time, phone gets detected in Windows (as shown by the icon in the bottom right of taskbar and a notification sound.
Type:
Code:
adb devices
If this displays a code SH**** after "List of devices", you're in luck. You can issue an adb command and get a CID of your device, following which you can create a goldcard.
After creating a goldcard, it will allow you to run a generic SLCD RUU. Check my thread for a latest RUU.
If you dont have a goldcard, and adb doesnt show the device in Recovery mode, it means Recovery is corrupted too. In this case, Power off device. Then Poweron by pressing Back key and Power on key. Again try adb devices command. If it shows the device, follow the steps of previous step.
You can also create a goldcard by putting your microsd card into a friend's phone and following the steps needed to create a gold card
If adb doesnt show your device in either Fastboot (previous step) or in Recovery, then you're in trouble. The only way to unbrick your softbricked device is to get a Generic RUU for your device (Check shipped roms site, or search XDA), and flash it. There is also a method if you have the original OTA zip for your device. Check teppic74's posts on XDA for this method.
If you have an Indian Desire, you're done for as I found out. If you dont have a goldcard for an Indian Desire, or the OTA zip, you have no option than to return it to HTC. Dont worry about Warranty being lost if it is a new phone. HTC has to repair it according to their Warranty policy.
Goodluck. I've summarized all methods available to unbrick an SLCD. For more details on any one method, try searching with the appropriate keywords from my post. It's all on XDA.

@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
"switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery."
pc detects the phone but when i run ruu it doesn't find the phone and i have OTA downloaded as well and i have copied to micro sd but i dont know how to use this OTA. i'm sorry for being very basic
Regards

faisal_sherry said:
@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
"switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery."
pc detects the phone but when i run ruu it doesn't find the phone and i have OTA downloaded as well and i have copied to micro sd but i dont know how to use this OTA. i'm sorry for being very basic
Regards
Click to expand...
Click to collapse
@Faisal,
No prob. Everyone is a newbie at the beginning!
But, you need to search and find out some things on XDA, and there are a lot of newbie centric guides over here which explain procedures step by step..
You need to do these by yourself though:
1. Install Android SDK. It just involves downloading the setup file, running it, and finding out where in Windows it has been installed. In the main installation folder, there is a Folder called Tools. You need to open a command prompt in that folder and run adb.exe for most of the procedures. Follow this guide to install the SDK.
2. After you have the sdk installed, boot your phone into recovery using the procedure you quoted. As you said, the phone will be detected in Windows. At this point, run the following command from a command prompt in your tools folder.
Code:
adb devices
This will output "List of devices" followed by a code starting with SH. If it does, you're in luck. You can now create a goldcard, and proceed. Follow this guide for this.
3. If the "adb devices" does not show any devices (in recovery/Boot mode), and you dont have a goldcard, you've run out of luck, pal. Honestly, no one on any forum has solved the issue with this combo.
There would still be a solution, if you have the RUU. I dont see why your RUU does not run. Try to run it in one of the following modes.
a. Switch off phone
Switch it on by pressing Back key followed by Back+Power key, then slowly releasing Powerkey while keeping Back key. This is the bootloader mode.
b. Recovery mode. Power off, power on by Vol down + Power key, then slowly release Power key. After 30 sec, press Vol down once, then power key once. Wait 1 min and see if pc detects device. Else press power key once again.
In either of these modes, the RUU you downloaded should down. If it is the incorrect RUU for your location, it will give a customer id error. If it has an incorrect bootloader version, it will show a Bootloader version error. In either of these cases, try the newest generic SLCD RUU from shipped roms. If this still gives one of the above errors, your phone is a branded phone. In this case, you WILL NEED a gold card to work.
Note that if adb devices shows your phone, then you can create a goldcard at this point.
If adb does not show your devices, and the latest generic RUU does not run, and you cant find a correct RUU for your device, then tough luck. I am yet to find a solution to this problem. Return it to HTC.

faisal_sherry said:
@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
Click to expand...
Click to collapse
Yes, you need to have HTC sync installed for the drivers. But the HTC sync main program should not remain in the system tray (bottom right). If it is, close it by rightclicking and Exiting.
The problem with what devin mm said is that an SLCD desire doesnt show anything on screen if bricked. Yet, recovery may be selectable for some, without seeing anything. But if you ran the RUU, then most probably the recovery itself is corrupted and selecting a zip file on memory card wont be possible at this point.
Sorry that I wont be able to follow this thread for the next few days. I'm travelling, and since my Desire is with HTC repair centre, no Net. Hopefully, someone else on XDA can help out with any more qns..

HTC Desire Stuck on HTC logo - Recovery not Working - NOT SOLVED!!

Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30

Cyanoid said:
Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Click to expand...
Click to collapse
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.

Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it says "Android Bootloader Interface" in Windows Device Manager, that it says "HBOOT USB PLUG" on the HBOOT screen when connected via USB, and that I am able to issue FASTBOOT commands from the PC. But I can't issue adb commands, so it appears I can only "partially" communicate with the phone from the PC.
Should I try CLEAR STORAGE, or could that fully brick my phone?
On the HBOOT screen, these are the status messages that load:
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nbh]
No Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99DIMG.nbh]
No Image or wrong image!
waynestir said:
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Click to expand...
Click to collapse

USB Brick
For me, it sounds like a typical usb brick :/ I hope you still have rooted ROM. Search through this forum for unbricking guide.

Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.

HTC Desire Stuck on HTC logo - Recovery not Working - SOLVED!!
madcr0w said:
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
Click to expand...
Click to collapse
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.

sorry for delayed responce. I'm sure you had already found a solution by now but in the off chance you didn't.
you have to load fastboot not hboot.
from a power off state hold back button and power on phone. this will load fastboot and ruu will find device when run.
Cyanoid said:
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it o Image!
Click to expand...
Click to collapse

Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.

expza said:
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
Click to expand...
Click to collapse
+1 There is a good guide to fastboot commands on the android wiki:
http://android-dls.com/wiki/index.php?title=Fastboot
Should be a case of wiping system, data, cache, then flashing recovery image. Then boot into that and restore a backup or flash a rom.

Cyanoid said:
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
Click to expand...
Click to collapse
can u plz help me frm with post u solved ur probs....i m stuck too

1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional

Does your phone get hot and overheated during the htc logo? It did so to me and it turned out to that my CPU had melted and overheated. Take it to your retailer and they will fix it for free because it's not your fault, it's the phone that overheated.

Try this:
-download this with ur pc and rename it a PB99IMG.zip (not PB99IMG.zip.zip ok?)
-then put it on the root of ur sdcard (not in some folder) through an sd card reader
-ensure the battery is charged much than 30%..better more
-with the phone off (remove battery and put again) press and HOLD the volume down key and press (still holding the volume down key) and hold the power button..hold both and wait to enter in the hboot
-there wait a bit, and it will ask to u if u want apply the update, select yes with the volume keys and confirm with power button

awayra said:
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Click to expand...
Click to collapse
Just go to my troubleshooting guide, you'll probably find an answer there.

Send it back for warranty repair.
Sent from my Motorola Startac running Atari 2600 software!

@nhrsak - you save me, thanks very much!!

Did you try getting s-off with Revolutionary?
I had problems when i was s-on, but when i s-offed, everything went fine.

Have you tried flashing recovery.img via AndroidFlasher(from XDA)?

[Q] Unrooting trouble

Tried to search but found no real answers. Please point me in the right direction of I missed something.
I want to unroot my Desire. Android 2.2, 2.10.405.2
First I discovered my phone had to be mounted to the pc in removable disk mode, not htc sync mode like some guides say. When in htc sync mode none of the RUUs I downloaded would seem to run at all.
I tried the newest (?) RUU_Bravo_Froyo_HTC_WWE_2.29.405.5. It stopped pretty fast with the error message "Disk full while accessing c:\ruu_log\RUU_110526T233117.log". (C is the drive letter associated with the phone.)
I also tried 2.10.405.2, got the same error message. Ok, so then I tried something older, namely RUU_Bravo_HTC_WWE_1.21.405.2. This got a bit further, but stopped with the error message "Runtime Error! Program:........\ARUWizard.exe". At this point my desire screen said HTC in glowing black letters. I unplugged it and it was at some kind of recovery menu, showing hboot version and some other stuff (think it was version 093.000.1 or something like that).
Thanks for all the guidance I have found here at xda previously. Any help in this matter would be greatly appreciated

Don't mount usb. Just plug the phone in so it's in charge mode with usb debugging then run the ruu. I guess the errors that your receiving are down to you bring in the wrong mode or partly. Give it a try in charge mode with debugging and report back.
Swyped...

Charging only mode, usb debugging activated.
Run RUU_Bravo_Froyo_HTC_WWE_2.29.405.5 [...].exe
The InstallShield Wizard window opens, preparing the installation. The progress bar reaches the end. Then nothing happens. (Just tried this right now.) The same goes for RUU_Bravo_HTC_WWE_1.21.405.2.

Boot in to fastboot then run the ruu
Sent from my HTC Desire using XDA App

Try this:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102

Solved
Solved:
I downloaded PB99IMG.zip from the ultimate dropbox thread by SUroot at androidforums. You could also follow the guide provided by EddyOS (how to extract rom from ruu). Then be sure that the filename is exactly 'PB99IMG.zip', nothing more or less. Put it in the root of the sd card, power on the phone holding volume down button pressed. Wait a few seconds. It detects the .zip all by itself. Then you have to confirm that you want ro update and later you have to select reboot. That's it! Stock phone.
My problems during this: I never got to the first sted in EddyOS' guide because the main window of the ruu file (on the PC) never appeared. So I downloaded this file instead, but failed to rename it, so hboot didn't pick it up.
Thanks! Now I can sell my pretty Desire to normal people

Yep, if the RUU doesn't run then you'd be stuck!! Just as well the dropbox has the file in there!!
Glad you're sorted though

[Q] Did I brick my desire?

Hi.
I was recently experiencing some problems with my desire and I believe that I might have rushed into bricking it.
I woke up the day of the bricking. I had just installed the newest version of GingerVillain (version 2.4). My phone had run out of power the day before so I started recharging it. After it had charged for a couple of hours I went to the market to update some apps. During the update my phone suddently rebooted. I thought that it was nothing and went back to the market and continued updating. A few minutes later it rebooted agian. It kept on rebooting with less and less time in between after each attempt until it chose to reboot at the splash screen continuesly.
This is when I thought of starting the phone in recovery and do a NAND restore. As I tried to enter the recovery mode the phone froze at a black screen. I pulled out the battery and retried a couple of times without success.
I read a little on the internet about ADB and tried doing some stuff but I kept on getting errors when running commands in the tools directory. At this point I was getting desperate because I needed the phone to work as I was expecting an important call. I tried flashing a new RUU (through the installer on my PC) while the phone was in fastboot (but without using any ADB and CMD stuff). After this installation almost had finished I got an error saying that the version of the rom wasn't the right one for my phone and the phone shut off.
Since then I haven't been able to boot it into bootloader or even boot it at all. Whenever I hold down power + volume down nothing happends and if I try only pressing the power button the phone vibrates and other than that nothing else happends. Not even the screen turns on.
I since then set up ADB and got it working. I then tried to see if the phone was still able to fastboot through the following commands:
Code:
adb devices
and
Code:
fastboot devices
but found that this was not the case.
Whenever the battery is in the phone though, the bottom of the phone starts to get warm, a little like it's actually using the battery to perform some actions or something. I was also able to recharge it through my computer.
I really need a phone and as it seems I have got my hands on a spare one, but only for a limited time. I'm really thinking of handing it in to the HTC Concept Store so they can send it to the repair department and hopefully get it back as fast as possible.

Its seems.. S-LCD Brick
try This
http://forum.xda-developers.com/showthread.php?t=748498
or
http://forum.xda-developers.com/showthread.php?t=831734

Ohh dude! I BELIEVE YOU MIGHT JUST HAVE SAVED MY LIFE! TY! TY! TY! TY!
My stationary just killed itself because of the hot weather and a little bit too much work. If I was going to hand in my phone and they couldn't repair it since I had "destroyed" it, I would be forced to buy a new one, and with that I wouldn't be able to afford new components for my stationary.
I will get right on with trying this method as soon as I get home and then I will give feedback asap. It will probably be the most fun "digging in the dark" I will ever do if it turns out to work.
I was almost sure I had killed my beautiful phone, and with it only being a couple of months old that would have been a pain in the ass.
Once again TY so much!!

I have been at this for almost 4 hours now and still no result. I believe the guides could have been more noob friendly. I've been to hell and back reading all the kinds of guides out there to get it all to work and now I'm tired and believe I won't be able to fix this, or atleast doesn't have the capacity to keep on trying.
I pretty much believe that I had this SLCD-brick, but trying out different RUU's is killing me inside and stealing my time. I'd rather just hand in the phone and recieve it as it was from the beginning again to start all over.
Trying to repair a smartphone with a blackscreen is is not something I have the capacity to do. Besides I have my recently deseased stationary computer to take care of as well.
I do have a goldcard, pushed the PB99IMG.zip file to my /sdcard/ through adb and tried starting up fastboot and do as described here.
But somehow I did not find any changes to the problem and the guide itself was wierdly written although the only guide I could find on this problem.
But now I'm giving up. I seriously just hope they will repair my device at no cost.
Regards,
Me

Man.. what happen when you connect your mobile to PC.. is it showing android device and under that bootloader interface.. dont lose hope... lets try some steps...
connect your mobile to PC and see in your device manager.. can you see android.. if yes than your driver are installed...
than remove the phone from pc.. take out the battery.. and put back battery.. and start by volume down and power.. and than after 10 sec just press power button again.. and connect to pc again... and cehck device manager.. and you should see the same if not.. than install your adb driver.
Point is.. install ADB driver.. when you are on hboot screen.. as well fastboot screen..
Than your RUU will detect your phone.

Well I tried all the steps for this. I can see the phone when booting it with the following combos:
Code:
1: Volume down + Power
2: Power
1: Volume down + Power
2: Volume down
3: Power
When using the first method I should as far as I can understand myself enter fastboot and the other one is recovery. Even when running the fastboot devices / adb devices commands in ADB it tells me what state my devices in, that is either fastboot or recovery. So that's for certain.
I tried running the following RUU when I had connected my device with fastboot:
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
The RUU found my device and I ended up with a 140 Error. I read in some guide that this error could be to blame of different windows drivers so I tried grabbing the rom.zip from the RUU (from Temp folder) and renamed it to PB99IMG.zip and put it on the phone. As I couldn't get access to my SD card since I can't see what's on my screen in fastboot and recovery mode I used:
Code:
adb push PB99IMG.zip /sdcard/
with the PB99IMG.zip placed in my tools folder for the transfer. It completed and now the PB99IMG.zip should be placed on the root of my sdcard.
As a notice I live in Denmark and the above RUU should as far as I can understand be the one I need and should as well be SLCD compatible.
When I try to trace the steps in the "not able to see your screen guide" placed here I get none of the desired outcomes:
http://forum.xda-developers.com/showthread.php?t=880268
I find the guide a little but confusing though. When to use the right commands to trace through a black screen fastboot/recovery and stuff isn't really "noob"-friendly.
When I tried using the following command I didn't get the desired result either:
Code:
fastboot oem gencheckpt
Which should return a HTC_<number> that could tell me whether my phone is branded or not, but instead resulted in an error. As far as I can remember I did make my sdcard a goldcard when I rooted my phone, without knowing whether I would need it, so this number should be irrelevant. So I kept on going at this point.
I have basicly tried everything that I can find guides for and have traced all the steps in detail as far as I understand the guides anyhow. I feel like at a dead end. I am having doubtsg whether the PB99IMG.zip is run when I boot my phone.
Having a clean slate (but still the PB99IMG.zip on the sdcard I have now tried the following:
Code:
Volume down + Power
Windows reported a connected Android 1.0 device and the Android Bootloader Interface.
Power once more (should now be in fastboot)
fastboot devices
confirmed the above, but using ADB devices only return a result if the phone is in recovery mode
So far so good..
I'll give this one more day which will be when I return home at 17:00 today. Then I'll head to tech support at my HTC Store.

Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..

jhonybravo4u said:
Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..
Click to expand...
Click to collapse
Okay. I'll try this and should I run it while in recovery like I did with the other one?
Does it matter if my SD card is out of the phone?
EDIT 1:
I tried with the sdcard out of the phone and with the RUU installed through windows. I now see a HTC Logo on the screen.. and an installing bar below the logo.. Seems like you were my divine interception mate.. ty a lot. I will write once the installation is done.. whether or not it succeeds.
EDIT 2:
My phone is now working. Booted with HTC Sense and a pin code request. Currently setting it up.
I guess I should now be able to re-root it again and get back to the state I was in before I SLCD-bricked it.. or what?
And in what way do I easiest remove that PM99IMG.zip file from the sdcard..? I booted my phone without the sdcard in it to avoid it running the PM99IMG.zip file..
One little question more.. I don't have any phone signal.. could this be to blame for the radio? I can connect to wifi though.. or can I simply run that other RUU I used earlier with the bootloader error to get back my signal?
So happy right now..
EDIT 3:
Nvm. I tried shutting down the phone, put in the sdcard, boot it up again. I found that the ADB push command on that PM99IMG.zip file didn't work. The file wasn't there.. and I suddently got back my signal. Only question is, can I now re-root it again and get back to my previous state without any problems?

Yes Ofcourse you can re root it.. with Unrevoked rooting wont be a big problem... and as soon as you root... just take a nandroid backup from it and be safe..
Enjoy the victory you earned... .. ;-)

URGENT HELP REQ! HTC Desire wont load past bootloader, no keys work. REWARD!

Hiya guys,
I recently purchased a HTC desire and its been nothing but trouble. THe phone simply refuses to function. It loads directly into the boot loader after around 3 seconds after I press the power button. It will NOT go into recovery mode, I have tried many times but nothing. Even worste when it enters bootloader all buttons cease to function and I cannot scroll to select an option or enter FASTBOOT, no buttons function whatsoever.
The devices is detected via usb, fastboot commander gives me this error when reading the device details -
Code:
HT05PPL02709 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: failed.
Radio version: failed.
Main software version: failed.
cid: failed.
cpld: failed.
getvar:product failed (command write failed (unknown error)).
getvar:mid failed (command write failed (unknown error)).
getvar:security failed (status malformed (1 bytes)).
getvar:build-mode failed (command write failed (unknown error)).
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
Within the bootloader itself I get this information -
HTML:
BRAVO PVT1 SHIP S-OFF
RIFF: 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
AUG 10 2010, 17:52:18
When the USB is plugged in I get "HBOOT USB PLUG"
Devices is detected as "MY HTC"
I tried flashing with official htc update utility but I get error 170 (bad usb connection). The device charges etc but that's about all I have been able to do thus far.
I will provide further details if needed, I just really want this fixed.
A small reward of £10 (around $18 dollars) will be issued via Paypal to the first one to fix my problem as a token of goodwill. Would appreciate any help here guys!

Ensure to have the correct drivers (uninstall all htc drivers u have and install the latest htc synch from htc website)
then run the latest ruu for the desire 2.29.405.5
ps. no reward needed

poweroff and hold BACK and POWER. this boots you directly into fastboot mode.
From there you can issue the command
Code:
fastboot oem gencheckpt
which boots you into recovery. Try to flash a rom or restore a backup and get back at us
And yeah we don't help people for profit

bortak said:
poweroff and hold BACK and POWER. this boots you directly into fastboot mode.
From there you can issue the command
Code:
fastboot oem gencheckpt
which boots you into recovery. Try to flash a rom or restore a backup and get back at us
And yeah we don't help people for profit
Click to expand...
Click to collapse
When powered off back and power, or any combination of keys still just instantly load the boot-loader. This is what makes my problem ever more difficult to solve.
The 'reward' is merely a token of my appreciation. Anyone have any ideas please let me know!

I would say put the relevant PB99IMG.zip on the sd card via whatever means you can and return it to stock via the bootloader.

rootSU said:
I would say put the relevant PB99IMG.zip on the sd card via whatever means you can and return it to stock via the bootloader.
Click to expand...
Click to collapse
hardware keys don't work so he won't be able to begin the update :/

bortak said:
hardware keys don't work so he won't be able to begin the update :/
Click to expand...
Click to collapse
Thats exactly my problem. The strange thing is the buttons do actually work but the boot loader just doesn't. So i'm stumped! Is there any solution, i'm starting to lose hope!

Im confused. How do you know the buttons work if you can only get into bootloader and the buttons dont work in teh bootloader?

rootSU said:
Im confused. How do you know the buttons work if you can only get into bootloader and the buttons dont work in teh bootloader?
Click to expand...
Click to collapse
Well I assume they work since the power button works just fine to turn it on to the bootloader. And since they ceases to respond once there I thought perhaps the same could apply to the other buttons.
When I plug in the usb it says "HBOOT USB PLUG" and when I unplug it it simply says "HBOOT" perhaps that is relevant in any way shape or form?
Thanks for sticking by!

So when it goes into hboot, it shoudl highlight fastboot. Pressing power at that point does not take you to fastboot?
Has the device ever had water damage? It could be that the volume button is stuck down or thinks its stuck down.
Also thats an old radio you have there, from 2.1
has this device every worked for you?

rootSU said:
So when it goes into hboot, it shoudl highlight fastboot. Pressing power at that point does not take you to fastboot?
Has the device ever had water damage? It could be that the volume button is stuck down or thinks its stuck down.
Also thats an old radio you have there, from 2.1
has this device every worked for you?
Click to expand...
Click to collapse
It does simply not respond whatsoever to input from the buttons. I ran the command 'fast boot devices' and it did find a device and listed its ID. But when I try reboot or flash witt fastboot I get a 'malformed bytes' error code.
No water damage

crackmunky said:
It does simply not respond whatsoever to input from the buttons. I ran the command 'fast boot devices' and it did find a device and listed its ID. But when I try reboot or flash witt fastboot I get a 'malformed bytes' error code.
No water damage
Click to expand...
Click to collapse
Have you tried running RUU? You can try running the 2.2 RUU and if that doesn't help, 2.3. As your device recognizes that it's plugged in, it could respond to RUU

matus.karahuta said:
Have you tried running RUU? You can try running the 2.2 RUU and if that doesn't help, 2.3. As your device recognizes that it's plugged in, it could respond to RUU
Click to expand...
Click to collapse
RUU recognizes it I think, It alerts me if the battery is lower than 30%, once charged it then loads for about 40 seconds than I receive error 170, USB error. Perhaps this is a sign that it could possibly work.
I have googled the error 170 and alot of people seem to think its a driver issue? However after installing, re-installing and installing again the official, latest HTC sync files it still refuses to work.
Any ideas where to go from there?

Are you using the original cabe? Aftermarket cables seems to work, but using mine original cable, resolved all errors for my colleague who could not flash a RUU.
And try the driver from Unrevoked: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
I NEVER used the official HTC drivers nor HTC sync, but I was able to do everything with the modified USB drivers.

The unrevoked files are currently down FYI
Sent from my HTC Desire using xda premium

Trying a different cable with Unrevoked drivers, will port back shortly. Thank you for the replies thus far guys!

Dam no luck, still 170 error! Tried with two separate cables. Anything else which would cause this?

This is usually only fixable by using PB99IMG.zip but you're stuck there. Really not sure what you can do now. I think you're stuck
Sent from my HTC Desire using xda premium

crackmunky said:
Trying a different cable with Unrevoked drivers, will port back shortly. Thank you for the replies thus far guys!
Click to expand...
Click to collapse
can you take the sd card from the mobile and download "PB99IMG_downgrade" from alpharev.nl, save as PM99IMG.zip in the SD card via PC. put the SD card in the mobile and switch it on. if it is successful, then try the RUU. Hope it helps you.

kmaq said:
can you take the sd card from the mobile and download "PB99IMG_downgrade" from alpharev.nl, save as PM99IMG.zip in the SD card via PC. put the SD card in the mobile and switch it on. if it is successful, then try the RUU. Hope it helps you.
Click to expand...
Click to collapse
I will try this as soon as I get home. Will this work since I cant hit any keys? How will this take effect without me bein able to 'apply' it? or will its presence on the sd card stimulate some kind of effect? Thankyou for the reply!