I recently followed the unrevoked guide to root my phone and put on the clockworkmod custom recovery image. On the second step, Unrevoked said 'waiting for phone reboot' but the phone got stuck in the white HTC screen. I can boot into HBOOT but not recovery mode, the phone gets stuck in the white HTC screen everytime I try. Anyone know where i go from here to trouble shoot this/reset the device.
Happened to me too when i tried to root. Just root it again with unrevoked and it should be fixed.
I cant ... Unrevoked says 'Waiting for device. Plug phone in now and enble USB debugging. Make sure HTC sync is *not* installed ! ... (its plugged to the phone while the phone is stuck on the white HTC screen)
Bump! ..
Try flashing an official RUU ROM.
You can find a list of ROMs here: http://forum.xda-developers.com/showthread.php?t=695667
I've similar problem. I think I can not use unrevoked because it need to enable debugging mode but my system is stuck at htc logo screen so I can not do that.
I can go to bootloader and here is the information on it.
Code:
Bravo PVT1 SHIP S-ON
HBOOT-0.92.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.09.00.20
Jul 23 2010,16:46:44
the problem started after volume down key and touch ball stopped working and some update was installed.
I can not go to recovery mode as it will just reboot for ever when I chose it from HBoot. I tried to root again but I get
Code:
FAILED (remote: 43 main version check fail)
at some point. The phone is unbranded
Should I start another post?
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)?
Hi,
Let me start with my device info.
HTC Desire
- Bravo PVT4 SHIP S-ON
- HBOOT-0.93.0001
- MICROP-051d
- Touch panel-synw0101
- radio-5.09.05.30_2
- Aug 10 2010,17;52;18
Current image version
RUU_Bravo_Froyo_Chunghwa Taiwan carriers (version: 2.10.751.4)
I'm running Windows Vista x86
That's all I got.
Now, the problem.
Everytime I turn the device on, it get stuck at the White HTC Windows and vibrates several times, I think this is a pretty common problem, so I won't stress this issue too much.
The solutions that I found are.
As my device is S-ON my options are limited. I can't boot recovery, so..
I download the latest RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_32U_5_11_05_27_release_159811_signed_2
Now, I run the ruu until ask to connect, I connect my device, the ruu recognize and identify my device, it ask to update, everything good. Updating process start and suddenly stops and tells me, "error 131, customer id error"
and that I need to use the right RUU utility.?
So I decided to avoid the USB connection and try to flash it directly from the SDCARD, I extracted the rom.zip from the above file, change the name to PB99IMG.ZIP, put it on my device, volume + power, but nothing.
so thinking that something is missing, I select fast boot, the device shows some text in green, even shows the PB99IMG.ZIP file, and is back to the bootloader screen and nothing happens.
What else can I do to bring to life my device, if I choose recovery with the PB99IMG file in the sdcard, the device shows a black screen with a red triangle.
I think is something with that taiwanes RUU, but maybe not.
Could any one please put me in the right direction
Thanks in advance
Sovius
As my device is S-ON my options are limited. I can't boot recovery, so..
Click to expand...
Click to collapse
Can you boot into fastboot? Using revolutionary.io will give you S-OFF and then you can flash a recovery - since you are PVT4, then AmonRa or newest CWM recommended.
You need a goldcard to RUU with that RUU. Download the 2.3.3 RUU from htcdev.com. this should resolve the Id issue.
Sent from my HTC Desire using xda premium
Thanks for you replays
This is what happen now.
davebugyi
In tried to S-Off with Revolutionary, I remove HTC Sync and install the drivers required. > Back + Power > the device is in fastboot screen > connect the USB cable and the device seems to be recognized by the computer but no notification of that is given, except for a beep (like when you plug a USB flashdrive) but no letter is assign to the device or anything. > I double click revolutionary and the program said "waiting for device", I left it for 30min, but nothing.
As I cannot get inside the device, the problem might be that revolutionary requires my device to have "USB debugging on" I don't know if is on or not.
rootSU
How do I create a Gold Card, if I can't get inside the device to set everything up?. Can I use another Gold card or they are exclusive of each device.?.
Your recommendation are Welcome, Please let me know if you need anything from me to have a much clear understanding about what's going on.
I'll make a video to show you exactly what happening and what I'm doing
Cheers
I have a HTC Desire.
My problem is that while booting, the phone won't go beyond the second splash and will get stuck and loop that second splash. I can get to HBOOT/FASTBOOT but I'm not able to mount my SD Card to flash a different ROM or restore my previous ROM.
When I boot with SD Card in, I get a Leedroid second splash and without SD Card I get a different one, but it gets stuck either way.
The problem arose when in ROM Manager whilst running the phone, I downloaded a ROM and flashed it from ROM Manager.
This is the information displayed in HBOOT.
BRAVO PVT4 SHIP S-OFF
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.00.20
Aug 10 2010,17:52:18
Any suggestions?
I've been trying to find a fix all afternoon guys, I need a hand from someone experienced.
you have a usb/sdbrick this is caused by flashing stuff using rom manager on desire. its not been good for desire pvt4 40000 devices
i fixed this for someone else a few days ago on androidforums
here it is
http://androidforums.com/desire-sup...s-help-stuck-cant-mount-sd-card-recovery.html
I've tried countless times to send the command "fastboot oem enableqxdm 0" using the sdk over usb and it hasn't worked. I just tried again after turning it on and for whatever reason it's worked.
Now I just have to see if I can flash a rom..
Okay, everything seems to be fine now. Cheers Rastaman-FB.
if it wasnt working then either you were not booted into the right area or fastboot wasnt set up correctly
I think my USB cable might have been dodgy because if I ran the "fastboot devices" command it would show up some times and not others. heh.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Thanks Lufc, I am a noob!
Hi everyone. My friends Desire seems to be completely dead. What we did:
- we s-offed desire with revolutionary
- we tried several ROMs with no problem
- the last ROM was the Sandvold ICS ROM
- in one day desire doesn't response - whatever you do it ends up in bootloader. Problem is, that we cannot use volume up and down to enter recovery or fastboot. We also wanted to reflash hboot by renaming it to PMG... with no success. It recognized the file in SD card and showed only - "PARSING" for more than half an hour. And nothing else. After taking battery out and power on again it shows only following:
- REVOLUTIONARY-
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
Aug 10 2010, 17:52:18
It seems that the phone has broken navigation arrows (hardware) or something, because you cannot do nothing - if you want to power off the phone, you must take the battery out.
Do you have any idea what we can try? (I also made a golcard and I have working ADB - if necessary).
Many thanks for any reply.
It would seem the phone is hanging in bootloader which is not a very good sign. Some suggestions:-
- Let the phone cool down and try booting.
- Pull battery, start phone with back+power to go directly to fastboot. If it enters fastboot mode this way then there is hope.
- What hboot was in PB99IMG.zip? Was the md5 ok ? With hboot and radio there are no second chances. Did the problems occur after this procedure or before.
handy5876 said:
It would seem the phone is hanging in bootloader which is not a very good sign. Some suggestions:-
- Let the phone cool down and try booting.
- Pull battery, start phone with back+power to go directly to fastboot. If it enters fastboot mode this way then there is hope.
- What hboot was in PB99IMG.zip? Was the md5 ok ? With hboot and radio there are no second chances. Did the problems occur after this procedure or before.
Click to expand...
Click to collapse
Thanks for quick answer. Unfortunately, phone didn't boot into fastboot after pressing BACK+POWER ... Yes, it was PB99IMG.zip. MD5 was for sure correct because I flashed this exact file several times before with success.
This problem occured before trying update hboot.
It looks like R.I.P. for Desire - isn't it?
The phone first boots the radio (modem processor) and thereafter the bootloader(hboot) (application pocessor). They both are the starting points. Without them booting successfully there is no easy access to the phone. Maybe somebody has got better suggestions.