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)?
Never knew this day would dawn on me, but I have no idea what to do right now
My phone boots in to fastboot just fine
- but, when i try to flash a boot.img or adb devices, they say waiting for device and blank
However, when i was in my system and i adb devices, my device serial showed up.
I really wanted to flash faux004b4, so i tried countless times trying to flash the boot.img in fastboot using different cables, but to no avail. This has never happened, in my 2 months of owning and flashing this device.
I know the steps to what I should be doing. But I just cant believe fastboot wont recognize the device.. ( in fastboot usb of course)
NOW...so i went into recovery, with viper X and faux004b3 installed, and formatted data, system and cache, hoping to resolve the problem, but no, it doesnt boot now..FML, so i tried relashing faux004b3 modules, and still doesnt work. Tried fastboot, nope, still says waiting for device.
SO, can anyone please help a senior member out, in saving my phone, and getting everything back in order.
BTW: Before, in fastboot, I was able to switch between fastboot and hboot while plugged in. But right now, I can only unplug my phone to get back to hboot. Maybe something here is the problem? I have no idea
PROBLEM RESOLVE: reinstalled htc drivers, and things worked themselves out. Sorry for adding one more thread to this place, but this could act as useful to many others who may face similar issues.
Hey There,
I'm sort of at my wits end with this issue.
I think I know what I've done wrong. I went to flash a new 10.2 rom, along with Gapps to my original Kindle Fire. However, I forgot to factory reset (more like I started it and then felt like it was taking way too long, so I skipped that step). Anyways, I flash the new roms and reboot the device. Now I'm stuck at the revolving Cyanogen logo (off center and going off the screen).
I forgot to install FireFireFire before any of this (yeah, two dumb things so far). So now when I connect the device to my computer, it shows up as this in KFU:
ADB Status: Online
Boot Status: Unknown
When I try to set fastboot via ADB command prompt commands, it says it can see the device, but can't do anything because it is "offline"
Meanwhile reinstalling drivers does nothing,
rebooting the device while KFU is < waiting for device > does nothing,
changing USB slots does nothing.
Device doesn't show up as connected right away via my PC, either. It takes until the CM logo is running before my PC notices it is there.
I've heard I'll need to buy a fast boot cable and that will instantly fix the device by getting me into TWRP again, but if I can fix this locally I would love to hear a method that doesn't involve waiting weeks for a cable to ship to me.
Thanks in advance!
Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
SyrStorm said:
Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.
dottat said:
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.
Click to expand...
Click to collapse
I can get into hboot and all that just fine. The phone won't boot, and I can't get into recovery is my problem. Oh and the fact that the computer doesn't recognize my phone in fastboot
Update: I just whipped out a really old computer running Windows XP and I installed the platform-tools and HTC One drivers on it. I hooked the phone up to the computer, and the drivers worked. I flashed TWRP and it flashed successfully according to fastboot, but it won't go into recovery still. What should I do now? I know I can RUU somehow (I'm not really sure how though), but I want to try and avoid that, if possible. Any suggestions? Thanks people!
EDIT: NVM it actually booted! What a success! This stuff is crazy!
My phone's screen was broken, I could only use my phone with some tools like screenshot. Today before I was about to repair the phone, I wiped all the things (including system, I don't know what I was thinking about, I thought I was doing a factory reset) in TWRP recovery. So now the thing is tricky. I cannot boot my phone, and I don't know what is going on there because the screen is broken. I connected my phone to PC, and after typing "adb devices", I saw that device was offline(but at least there was a device listed, though it was offline instead of attched).
So I cannot use adb, I tried 4.4.3 stock RUU, but it said that "ERROR 170 USB CONNECTION ERROR". I've installed HTC Sync Manager, it couldn't detect my phone, either.
I cannot enter the recovery, either. I don't know what to do now. Wonder if anybody here could help me. Any help appreciated.:crying:
mycityofsky said:
My phone's screen was broken, I could only use my phone with some tools like screenshot. Today before I was about to repair the phone, I wiped all the things (including system, I don't know what I was thinking about, I thought I was doing a factory reset) in TWRP recovery. So now the thing is tricky. I cannot boot my phone, and I don't know what is going on there because the screen is broken. I connected my phone to PC, and after typing "adb devices", I saw that device was offline(but at least there was a device listed, though it was offline instead of attched).
So I cannot use adb, I tried 4.4.3 stock RUU, but it said that "ERROR 170 USB CONNECTION ERROR". I've installed HTC Sync Manager, it couldn't detect my phone, either.
I cannot enter the recovery, either. I don't know what to do now. Wonder if anybody here could help me. Any help appreciated.:crying:
Click to expand...
Click to collapse
Finally it worked, I kept pressing volume up and power button to reboot to fastboot, then pressed volume down and power in order to recovery, now RUU worked just fine. Cheers!