Develop Bugs

[Q] HTC Desire Dead Screen

I have an A8183 from Telstra Australia. I rooted it using the revoked method, following the Telus Desire HBoot 0.83 Root and Flash guide on these forums. (new member unable to link).
I had the Cyanogen mod installed on the phone but didn't really like it. I wanted the HTC sense ui back so I tried to run a few generic RUU to get it back to normal.
Of course I got the Error 130 (Model error) or whatever it was. So I tried the Telstra RUU. I then got Error 140 (Bootloader error) and read around and found out I needed to downgrade to bootloader 0.80. Obviously did not realise this would affect the SLCD screen and remove the display drivers for SLCD to work.
I now have a phone with no screen, it boots and I hear the noises, but no display - not even in the bootloader or recovery mode. I tried putting the FroYo OTA on my gold card, renaming it "update.zip" but it didn't work, probably because I think I have a custom recovery mod I got from following the thread I linked above. Can someone please give me a noob guide to fixing this?

Use your gold card and flash WWE RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
Your screen is going to come back(the above RUU is SLCD compatible) and then download your Telstra RUU and flash with your goldcard(make sure RUU is SLCD compatible)

I've tried lots of RUU's and it takes about an hour to download one. The ones you just linked look similar to the ones I've already tried. I'm currently downloading it, as well as the Froyo one.
Will post back in an hour or two as to what happens.
EDIT: It says there is a problem with the USB connection whenever I try to run the RUU...How do I fix that? My computer recognises there is something plugged in, and the charging light is on my phone.

I tried this:
1. Remove the battery
2. Insert the gold card
3. Hold down volume down then press power
4. Blindly press power again to get into fastboot???
5. Run: RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe
and/or Run: RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
On step 4, windows recognises a USB device but fails to install the driver. I went into the device manager and there is "Android 1.0" listed there. I tried to update the drivers manually by using the ones in the AndroidSDK. I'm assuming this has something to do with what happens on step 5. *UPDATE* Installed HTC Sync with the driver, uninstalled HTC Sync, windows picked it up. Windows required a restart before I was able to flash any ROMs.
On step 5 it gets up to the screen where it says "Gathering information about your android device" (or something). It times out and says Error 170 - Usb connection error.
*UPDATE* restarting the RUU fixes the USB connection error, however ALL of them give Error 130 - Model invalid. The only RUU that works is RUU_Bravo_Telstra_WWE_1.15.841.14_R4_Radio_32.30.00.28U_4.05.00.11_123851.exe and unfortunately that has already been flashed onto the phone - so it does not fix the screen. If anyone knows of an RUU that will work with my phone? Or perhaps a Telstra one that actually works and restores my bootloader or something.
Someone pleeeeeeeeease help

From what you say, I think the LCD is bricked but the phone is working otherwise. Just to confirm power on the phone and let it boot normally. You should hear the boot sound and then after 2-3 mins try calling from another number to see if it rings.
Once it is at that stage, connect the mobile to PC via usb. Ensure htc sync software is installed (Not the drivers alone, but the full htc sync software). Then run the .exe that is compatible with SLCD. Your phone should get flashed. You cannot see anything on the mobile screen yet, but you can see the status on your computer.
I am not sure if RUU flashing will work from recovery/fastboot screen..... I am guessing you get the timeout error cos the phone is not booted. Give it a try.

Yes, Yes to all of that. Like I said, the only RUU that works is the Telstra one atm, and that is already on the phone. Like I said, I flashed that after downgrading to bootloader 0.80. All the other RUU's that I have tried to flash give a model id error.
If anyone can point me to an RUU from Telstra that enables use of the screen I would like a link please

I may be giving you a wrong advice, but have you tried to turn the phone on while pressing the back button? (not the volume down, the back button), and flash a compatible RUU?

Yea I've tried that with most of the RUU's that I've downloaded. It just gives model ID error. The only compatible RUU that I've come across is this one Telstra one that I've found on this forum. None of the other generic ones seem to work. I can't seem to find another Telstra RUU that will work. I have no idea if the phone is even still rooted, or what version the bootloader is (My guess is still 0.80 - even though it needs to be 0.83).
I'm unable to re-root the phone with a method like unrevoked because I can't enable USB debugging (can't see anything) and unrevoked doesn't find my phone.
At the moment I'm just playing around with flashing different RUU's remaking my gold card, installing/uninstalling HTC sync, flashing RUU in what I think is the bootloader screen, what I think is the fastboot screen, and when the phone is fully booted. (This would be a whole lot easier if I could see what was happening).
The only luck I've had is re-flashing the original Telstra RUU which does nothing to the screen...
(not the volume down, the back button)
Click to expand...
Click to collapse
- What does that do?

Turning the phone on with the volume down key pressed takes you to HBOOT menu
Turning the phone on with the back button pressed takes you to the fastboot menu directly, if I'm not recalling bad you need to be there to flash a RUU, It's worth the try...

I tried it with the back button - Same deal Error 130 - Model ID Error.
Apparently you can fix that with a new gold card. I read somewhere else to remake your gold card step by step. One of the steps requires USB debugging to be on your phone to record the serial numbers listed in the command prompt with the phone plugged in. I already have goldcard.img and have tried putting it on multiple microSD cards, I now have no more to try out.
Anything else I can try?? This is my only phone :S

I am not an expert on flashing, but I had bricked the LCD on my desire before. But mine was unbranded and flashing a unbranded RUU that got my phone and display working again.
What I would suggest is you can try flashing an unbranded WWE Froyo RUU that is compatible with the SLCD desire. If you have the gold card, you can flash any RUU to your phone (That is my understanding)
If you are not able to flash any other RUU, maybe the gold card is not proper. As far as I know, you should use the .img only on the sdcard which was in the mobile when you executed the commands. using .img generated with one card on another sd card will not work I think. At least it didnt for me.
Also the RUU is not bothered about the Hboot version on the phone. An RUU will have it's own bootloader and it will flash it onto the device over the existing bootloader
And above all, do not panic. The device can be recovered and restored. It is just a matter of time and patience and trying out a few things.
Edit: I forgot to ask, Do you have a nandroid backup done immediately after rooting?? If you have done it you could save yourself a lot of time by just restoring it.... If you have not backed up, then Lesson No 1 in rooting -> ALWAYS do a nandroid backup before you do things.

I think I have to agree. After about 20 hours of trawling forums I am 90% sure that I screwed up the initial gold card. (unrevoked doesn't require a gold card - so I thought it worked).
Is there a way to create a new gold card without an android phone? If you could point me to a guide that would be awesome. Obviously I'm prepared to buy a new microsd card to fix my $900 phone :S

Do you have USB debugging enabled?? If it is enabled, you just need the phone to be booted to create goldcard. Insert a formatted sd in the phone and boot it up, connect via adb and generate the CID numbers and try to make one.
If usb debugging is not enabled, then you can play "blind" game and try to enable it without the screen. It's tricky but certainly possible.

It was, but unfortunately the flash that ruined my screen returned it to default, which I assume would turn debugging "off". The blind game? never thought of that, I guess I could try look around for a youtube video of someone doing it or something. If anyones got spare time some STEP BY STEP exact instructions would be awesome

lordmitchell14 said:
It was, but unfortunately the flash that ruined my screen returned it to default, which I assume would turn debugging "off". The blind game? never thought of that, I guess I could try look around for a youtube video of someone doing it or something. If anyones got spare time some STEP BY STEP exact instructions would be awesome
Click to expand...
Click to collapse
If you search for lcd brick fixed, you should find a step by step guide to turn usb-debug on.
To flash a ruu, your phone needs to be booted in android normally, the ruu reboots it in fastboot itself. If you get an error flashing the ruu, try updating the android phone drivers. Even if Windows said it didn't update, try the ruu again. It worked for me with a friends phone.
Sent from my HTC Desire using XDA App

Well here are the steps..
1.Power on the phone and after 2-3 mins, press the power button to load the lock screen
2.Swipe down to unlock.
3.You should be in homescreen if device just booted. Press menu and then press the spot immediately above the search button. This should take you to settings screen
4.Now swipe long strokes with your finger "down to up" 4-5 times on the screen.. you are now swiping down the list.We need to make sure we reach the end of it.
5.Once you reach the settings list's end, the "Applications" link will be located just below the volume "+" key. about 5-7mm below the + mark. press the spot.
6.Now you should be inside the applications. Now keep swiping down on the trackpad. Do it for 10-15 times no problem. There are only 4 items in the list and doing it many times will ensure the selection is now on "Development" which is the last item in the list
7.Press the trackpad. The development should now get selected
8.Wait for a second. Press the trackpad again(No up/down). USB debugging will get selected.
9.Wait a second. Press the trackpad again. The popup "ok" button will get selected.
And you are good to go
Connect to PC and see if you can connect via abd.
This is assuming that Debugging is turned off. If it is already ON, then doing this will turn it off. So first check if you can connect via adb before attempting this.

I followed all the steps in this guide: http://forum.xda-developers.com/showthread.php?t=750852
I even spent an hour getting the debugging to turn on.
I managed to root my Desire again and got down to step 35. Unfortunately that RUU gave a model ID error. Just like all the rest.
Thanks for all your help guys, although this is driving me insane :S

*BEGIN DANCING*
thanks to the awesome guys at http://code.google.com/p/androidscreencast/
After playing the blind game and turning on USB debugging, I was able to use my computer as a screen which made things a whole lot easier.
After following the guide linked in the post above:
- I bought a new microSD
- re-made the gold card
- Followed steps 30 onwards...
- ran the RUU several times (it finally worked whilst in boot mode)
- AND MY SCREEN TURNED ON F*%K YEA!

Great to hear!!!
Now do a Nandorid backup and then you can go about trying out any mod/rom you want and you can always get back your original state with a simple nandroid restore.
And that ScreenCast looks interesting... will give it a try

HTC Desire Z feared bricked. (Perhaps stuck in bootloader)

I appoligise if this has been asked before.
I have a HTC Desire Z which I have rooted using the Cyanogen Wiki Method which i believe was successful, I wanted to check whether I was S-Off before loading custom roms.
wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting
I read on a forum you should bootload to check, so i held power and VOL up on restart however now i have a black screen with a flashing red led at the top and am unable to get out of this mode does anyone have any advise what I need to do?
Anything would be helpful I'm in the UK military currently deployed on OPS this is my only means of comms to family. Thanks in advance.

Crap, so you're stuck in bootloader huh? Well if you have a PC with you then thats good news. Cause you can just flash something via your bootloader if you have ADB set up.
Wait, you said it has a red led lit right?... the battery might have died on you in all honesty because that's the only time a red/amber led would come on. If this is the case just leave it charging for like 20 minutes before try to turn it on.
Anyways, if that isn't the issue try getting the screen onto that bootloader page. As soon as you get to that you can start fixing it. It should say FASTBOOT_USB or something similar to that. Now on your pc start up your CMD Prompt (Run > 'cmd'). From there try typing Fastboot devices and it should list your device as HT########. If you can get to that then we're doing well.
BEFORE you try this, just note I've never fastboot flashed a ROM and I only posted this because you seem to need it urgently. If you can wait, then post what you've actually done to the phone so I can provide you with a more tailored solution that will work. (post whether the phone is rooted, s-off or superCID or just the guides and where you got stuck)
Now what you need to do is plug your microSD into your laptop and do this:
Aegishua said:
Before you do this please do the following:
1a. Download the RUU I’ve linked (it should be a ~300mb exe file)
1b. Run the setup until you get to the screen with the tick boxes
1c. Goto C:\Users\<your account name>\AppData\local\temp. Then right click and Sort By Date Modified. Look for the most recently created folder which should look like {xxxxxxx-xxxxxx-xxxxxxxx}. Then navigate into it and its parent folder. Look for rom.zip and copy that to your goldcard/memory card.
1d. Rename the rom.zip on your memory card to PC10IMG.zip
1e. Mount your sd card back onto your phone.
Click to expand...
Click to collapse
In this case you want it to be called update.zip. Now you can pop the microSD back into your phone and from there get back into your bootloader and switch to fastboot. Now when it says fastboot_usb you can run this on your PC's CMD Prompt. fastboot update /sdcard/update.zip

did you try something as simple as a battery pull? also, I noted you said power + vol up, you need to do power + vol down to enter bootloader. I seem to remember something similar happening to me back in the day.
chances are it's fine. I'd do a battery pull and boot it normally just to make sure, then power off and enter bootloader to ensure you are s-off by pressing power + vol down.

It is supposed to be volume DOWN + power, I just tried volume up, my phone vibrated 3 times and an orange light flashed continuously, but it was solved by a battery pull, and it was back to normal
Sent from my HTC Desire Z using XDA App

only charge led shows lifesigns.
**moved to new post**

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] 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... .. ;-)

[Q] Need HELP PLEASE!!!...USB Issues/Stuck in HBOOT

My mother powered down her phone and when she turned it back it comes back up to this screen
Bravoc DVT2 Ship S-0N
HBOOT-1.06.0000
MICROP-051e
TOUCH Panel-SYNT0101
Radio-2.15.00.02.17
Dec 22 2010 16:16:39
HBOOT USB PLUG
<vol up> to previous item
<vol down> to next item
<power> to select
FASTBOOOT
RECOVERY
CLEAR STORAGE
SIMUNLOCK
a few secs after the phone starts up it flashs PB99diag.zip and pb99img.zip missing
the buttons on the phone do not function
I have tried installing android-sdk, htc sync, hboot drivers and cannot get the phone to found when on my Windows 7 64 bit machine, so I can push a new pb99img.zip to the phone...but i cannot get the phone to be found.
In device mananger it shows up as Android 1.0.
I can manually install the drivers but adb will still not show the device as listed.
The phone is not in USB debugging mode since none of this was intentional.
If anyone has any tips or advice it would be most aprreciated.

Did you root the phone previously? Did you install a custom ROM on it?
What you see is the HBOOT menu. To move the marker down you press the volume down button, to move it up you press the volume up button, and to make a selection you press the power button. Can you tell me if this works?
What happens if you take out the battery, put it back in and press the power button? I doubt it that the phone enters the HBOOT menu on it's own. Is that what you are saying? Normally you need to press and hold down the volume down button and the power button to enter this menu. So to stop entering the HBOOT menu just stop holding down the volume button when you power it on. If it enters HBOOT menu by its own will then something is wrong.
When you enter the HBOOT menu the phone will automatically look for a file called PB99img.zip or PB99diag.zip. This is sort of a fail-proof mechanism. It allows you to flash images or diagnose the phone when everything else fails, like in the case you loose button control. If it doesn't find any such file it will skip the operation. This is normal. It's the equivalent of putting a bootable CD or DVD in your Windows computer - if it's present at system boot it will boot off the CD/DVD and if it's not it will just skip it and continue booting current OS.
As for the ADB driver, check this out. You may need to change the hardware IDs in the driver INF file (android_winusb.inf).

Fractalogic said:
Did you root the phone previously? Did you install a custom ROM on it?
What you see is the HBOOT menu. To move the marker down you press the volume down button, to move it up you press the volume up button, and to make a selection you press the power button. Can you tell me if this works?
What happens if you take out the battery, put it back in and press the power button? I doubt it that the phone enters the HBOOT menu on it's own. Is that what you are saying? Normally you need to press and hold down the volume down button and the power button to enter this menu. So to stop entering the HBOOT menu just stop holding down the volume button when you power it on. If it enters HBOOT menu by its own will then something is wrong.
When you enter the HBOOT menu the phone will automatically look for a file called PB99img.zip or PB99diag.zip. This is sort of a fail-proof mechanism. It allows you to flash images or diagnose the phone when everything else fails, like in the case you loose button control. If it doesn't find any such file it will skip the operation. This is normal. It's the equivalent of putting a bootable CD or DVD in your Windows computer - if it's present at system boot it will boot off the CD/DVD and if it's not it will just skip it and continue booting current OS.
As for the ADB driver, check this out. You may need to change the hardware IDs in the driver INF file (android_winusb.inf).
Click to expand...
Click to collapse
Thank you for the quick reply...apparently my mother spilled something on the phone and it was acting up a little so she powered it down and when you powered it back up it came up to the HBOOT screen. The phone is stock it has never been rooted and no custom roms either. When I pull the battery the phone turns off, I can then put it back in and press power and then i am stuck at HBOOT. Once on the HBOOT screen none of my buttons function, not the volume or power buttons none of them. I have made sure to only press the power button when powering up and yes it still enters HBOOT. Thanks for the link on the adb driver info I will check it out with all haste.
Thank you for ADB driver info it was truly appreciated...my Hardware IDs are correct...the driver installs as Android ADB Interface yet adb or htc's ruu utility neither one acknowledges the phones existence. Is is possible that the phone is hosed?

have you tried selecting fastboot and then selecting reboot?

Flash the stock HBOOT image
sadklown2 said:
Thank you for the quick reply...apparently my mother spilled something on the phone and it was acting up a little so she powered it down and when you powered it back up it came up to the HBOOT screen. The phone is stock it has never been rooted and no custom roms either. When I pull the battery the phone turns off, I can then put it back in and press power and then i am stuck at HBOOT. Once on the HBOOT screen none of my buttons function, not the volume or power buttons none of them. I have made sure to only press the power button when powering up and yes it still enters HBOOT. Thanks for the link on the adb driver info I will check it out with all haste.
Thank you for ADB driver info it was truly appreciated...my Hardware IDs are correct...the driver installs as Android ADB Interface yet adb or htc's ruu utility neither one acknowledges the phones existence. Is is possible that the phone is hosed?
Click to expand...
Click to collapse
I'm thinking that maybe... only maybe... the spilled liquid was sticky (and surely conductive) so that the volume down button is kept depressed, so when you press the power on button it acts as you are pressing volume down and power button. It's probably far fetched but it is possible that the volume down button is depressed for one or another reason.
Yes, I think it will say like "Android ADB Interface" when you plug the phone in while in HBOOT. It will say something else I think when you plug it in while in recovery, etc.
I don't think you can use ADB commands while in HBOOT. I think ADB commands only work when the phone is booted up. If you can enter fastboot mode you can use Fastboot commands to flash a new HBOOT for instance.
But since you can't control the interface at all and no button seems to work on the phone, I think you have to try flashing a new HBOOT by placing a ZIP file on the SD card.
Go to AlphaRev website.
Download PB99IMG_stock.zip
Rename it to PB99IMG.zip.
Take out the SD card and put it in the computer.
Copy the PB99IMG.zip file to the SD card.
Take out the SD card and put it in the phone.
Insert the battery and power on the phone.
It will now automatically flash it with stock HBOOT image. Keep in mind that this may or may not erase personal data from either the phone or the SD card. I don't take any responsibilities for any data loss. I know you can't access the phone apps and internal data right now, but you can at least take a backup of the SD card, most apps are storing data on the SD card so you could use that to restore at least parts of the data later.

Fractalogic said:
I'm thinking that maybe... only maybe... the spilled liquid was sticky (and surely conductive) so that the volume down button is kept depressed, so when you press the power on button it acts as you are pressing volume down and power button. It's probably far fetched but it is possible that the volume down button is depressed for one or another reason.
Yes, I think it will say like "Android ADB Interface" when you plug the phone in while in HBOOT. It will say something else I think when you plug it in while in recovery, etc.
I don't think you can use ADB commands while in HBOOT. I think ADB commands only work when the phone is booted up. If you can enter fastboot mode you can use Fastboot commands to flash a new HBOOT for instance.
But since you can't control the interface at all and no button seems to work on the phone, I think you have to try flashing a new HBOOT by placing a ZIP file on the SD card.
Go to AlphaRev website.
Download PB99IMG_stock.zip
Rename it to PB99IMG.zip.
Take out the SD card and put it in the computer.
Copy the PB99IMG.zip file to the SD card.
Take out the SD card and put it in the phone.
Insert the battery and power on the phone.
It will now automatically flash it with stock HBOOT image. Keep in mind that this may or may not erase personal data from either the phone or the SD card. I don't take any responsibilities for any data loss. I know you can't access the phone apps and internal data right now, but you can at least take a backup of the SD card, most apps are storing data on the SD card so you could use that to restore at least parts of the data later.
Click to expand...
Click to collapse
No, no, no. Whats flashing hboot going to do? the phone is "water damaged". Also his phone is s-on and never rooted and u can only use alpharev hboots while s-off. Also he has a BravoC so i dont think Alpharev hboots work. Please learn some basic stuff before telling other to do things that r wrong and wont work.
@ OP i have no solution really apart from taking the phone apart and cleaning it maybe. but its water damaged so i think the only solution would be to run the correct ruu for ur phone and hope it boots or take it to a repair shop. If it was me, i would take it apart, clean it, put back together and try the ruu for ur device. But thats just my opinion. Seeing that the phone is not working then its prob worth a shot.

jmcclue said:
No, no, no. Whats flashing hboot going to do? the phone is "water damaged". Also his phone is s-on and never rooted and u can only use alpharev hboots while s-off. Also he has a BravoC so i dont think Alpharev hboots work. Please learn some basic stuff before telling other to do things that r wrong and wont work.
@ OP i have no solution really apart from taking the phone apart and cleaning it maybe. but its water damaged so i think the only solution would be to run the correct ruu for ur phone and hope it boots or take it to a repair shop. If it was me, i would take it apart, clean it, put back together and try the ruu for ur device. But thats just my opinion. Seeing that the phone is not working then its prob worth a shot.
Click to expand...
Click to collapse
Ooops!! Me bad... sorry! Thanks for correcting me though. So his only option is running the RUU for a BravoC?
Where can you find RUU for a BravoC? On Shipped-ROMs I can only find BravoC for AllTel, Verizon and VZW. Do you have to take carrier name into consideration when choosing RUU? Are there no BravoC that are not locked to a carrier?

Nice suggestions, but I'm pretty sure the phone is just physically broken. Take it in and see if you can get a replacement/fix. BravoC is hard to wrestle with.

droid_<3er said:
Nice suggestions, but I'm pretty sure the phone is just physically broken. Take it in and see if you can get a replacement/fix. BravoC is hard to wrestle with.
Click to expand...
Click to collapse
Thanks for all the suggestions...I had tried running the ruu from htc, but since i could never hammer out the usb issues the utility kept saying that the phone has less than 30% power and would promptly fail...anyway mom decided to turn it in on the insurance so its all a moot point now...again thanks to every one who tried to help and all the great guides/info on this site at least i learned quite a bit...