I was playing with my splash screen and boot animation, and I changed the PB31IMG file on my sd card to a custom splash image. I went to hboot (.92 i think) and it gave me the error "no image found" or something like that. I turned off the phone, and tried to boot up into hboot again by holding volume down+power. As soon as I did, my phone vibrated maybe four times and stayed at a black screen. I can't turn the phone on now, or boot into recovery. Has this happened to anyone else? More importantly, does anyone know how to fix it?
Just to add more information (Im really not sure what's relevant), I was running virtuous 2.6 with hydra #1, 2.15 radio. Also, the image error happened before when I was trying out a different splash screen. That time I deleted the file and re-transfered it my sd card. Hboot was able to recognize it as a splash screen when I rebooted it that time. I'm not sure, but my phone might have booted into clockwork recovery after hboot checked the img file.
One other thing that might be a problem was that I might've been running low on battery. I didn't check, but it was the end of the day and I'm usually almost dead by the time I charge it again.
Never mind.
(Unrevoked forever wiki)
When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.
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)?
Seeing as this is a old phone, which had to be replaced two times, I figured I may as well do something with it.
Its old, and the issues were so bad, that it just became unusable. I had to pay full price for my new Droid Bionic because this flaming bag of you know what was still under contract. The Dinc only had a 1 year warranty for replacement(I guess?) which had camera issues with the first, and this second had some MAJOR rebooting issues. It got so insanely hot it made the serial number, model number all that, come off the back of it. As I said, I got a new phone which is GREAT.
The issues with this old Dinc is:
1)rebooting loop, it WILL NOT enter the phone menus(main screen, etc). It will stay at the "HTC Incredible" white screen and just self-reboot over and over until it runs out of battery power.
2)I have replaced the battery, it did nothing for it.
3)In the HBoot menu, Factory reset, recovery does nothing(info for all those versions there will be posted later in this post).
4)I have all of the HTC/Android usb drivers installed, it does not pick up anything. No SD cards(if it does at that point?), nothing, but the Hboot menu does say "HBOOT USB" at the top.
HBoot information below
Code:
INCREDIBLEC XD SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.20
JUL 23 2010, 18:06:51
was hard to read this small text, but there ya go.
Keep in mind, I CANNOT even get past the "HTC Incredible" white screen too turn on USB debugging. I have tried alot of methods, nothing has seemed to work. I'm starting to think I should have some fun with this thing, take it out back.
Also, I have never rooted, changed roms, flashed or anything to this phone. I don't do that to phones I am using, but seeming as this phone is not being used...why not?
Hmm, that is unusual. Do you think you could download the Froyo RUU under the subheading "Stock Images" from here:
www.pvillecomp.com
and install that via hboot? If this works, you should be able to boot into the phone to begin the rooting process if the phone functions fine.
SlimSnoopOS said:
Hmm, that is unusual. Do you think you could download the Froyo RUU under the subheading "Stock Images" from here:
and install that via hboot? If this works, you should be able to boot into the phone to begin the rooting process if the phone functions fine.
Click to expand...
Click to collapse
Connected the phone to the USB cable and I got an error, screenshot attached.
You can access hboot but doing anything via usb cable results in nothing. That said, could you use the bionic or some other phone to place that RUU onto the root of the sd card then place place that sd card back in the Incredible and try installing it the RUU from hboot?
Side question: when you boot into hboot normally, does the incredible check for any files on the sd card like it is supposed to?
SlimSnoopOS said:
You can access hboot but doing anything via usb cable results in nothing. That said, could you use the bionic or some other phone to place that RUU onto the root of the sd card then place place that sd card back in the Incredible and try installing it the RUU from hboot?
Side question: when you boot into hboot normally, does the incredible check for any files on the sd card like it is supposed to?
Click to expand...
Click to collapse
yeah, it wont even pick up the phone via usb from my computer.
The Bionic SD Card thing is a GREAT idea, I will try that. Gees, why didn't I think of that.
What possibly went wrong (you can skip it if you guys like, I'm not entirely sure if it'll be helpful but I just wanted to be thorough.)
My G2 was working fine for the past year and I had it rooted and running CM since I can remember having it. No problems have ever occurred for me on this phone until today. I woke up and was checking my email on the gmail and yahoo mail app but the yahoo mail app kept crashing so I decided to force close it with Manage Applications and tried to reopen it, but then my phone froze. This was all going on while some of my other apps were updating. I waited for a good 30 minutes but nothing happened so I decided to pull the battery out.
My issues and what I've tried:
So my issue now is that whenever I boot my phone up again the HTC logo would show up like usual but when it transitions to the Cyanogenmod logo with the arrow circling around the Droid icon it becomes a black screen instead or it might be that the phone turns off (I cant tell but to be more specific no lights are on when this happens such as the home or menu button, etc.).
The next thing I tried is to boot into Hboot and do a recovery, but when I run recovery the same thing happens as above. The HTC screen shows up and then it goes into a black screen (I'm almost certain this isnt a hardware issue because I've never damaged my phone enough for the screen to have issues).
Seeing that recovery was hopeless, in a desperate attempt I tried to factory reset the phone through hboot, but it restarts my phone and just hangs at the HTC logo screen indefinitely. On top of all this, whenever I plug the phone to an outlet, the orange led light lights up for a few seconds and then turns off which indicates my phone isnt charging or loses connection with the cable so maybe it's a hardware issue after all?
I've spent the past 4-5 hours trying to find posts with people who've had similar situations, but either the issue was unresolved or the solution provided wasn't specific enough for me to follow (I am next to clueless with software mods). Please help me, I cannot afford a new phone at the moment and will be pretty screwed if I don't get this fixed by Monday. Thank you guys so much in advance!
A little info:
I'm running Cyanogenmod 7.2 I believe, it's the recently updated one.
This is what I see (excluding the options like fastboot, etc.) when I boot my phone while holding vol-
Vision pvt eng s-off
hboot-0.76.2000 (pc1010000)
microp-0425
radio-26.02.01.15_m2
eMMC-boot
Aug 20 2010, 16:51:01
see if you can pull a logcat while booting lopping/black screen
also you can try fastboot. try this
you need fastboot.exe from sdk (in tools or wherever)
open cmd from here (windows hold shift then right click in that folder)
in cmd type
fastboot devices
if your phone pops up you good to proceed if you get waiting for device we need to test some more
if good, continue (in the same folder as fastboot.exe have a recovery image, name it recovery.img)
in cmd type
fastboot -w
then
fastboot flash recovery recovery.img
then
fastboot reboot bootloader
(maybe its fastboot reboot-bootloader)
any way once back to hboot on your phone see if recovery works
Sent from my HTC Vision using xda premium
I'm pretty sure I tried this already, but I just tried it again. Rebooting bootloader makes my phone hang at the HTC screen. I used the img from the clockworkmod site directly and everything worked fine up until the reboot so I guess technically nothing worked :/.
I pulled the battery out and booted into Hboot and then recovery. It still becomes a black screen. Thanks for your help though. I would make a log but I dont know how, mind showing me the steps? Also I'm not 100% sure, so correct me if I'm wrong, but my case isn't with boot loops right? My phone doesnt restart over and over again by itself, it just sort of goes into a black screen and stays there for eternity. It's probably a distinction without a difference though, nothing works.
EDIT: I got past the original issue. Please see post #4 instead,
I'm trying to determine if my hardware has gone bunk or whether it's repairable system errors.
_____________________________________________________
Original post:
Hi guys,
I see several recent posts about similar topics but I can't begin to troubleshoot because I can't get past the bootloader.
Here are my specs from the bootloader screen:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.10.07.07
Jul 23, 2010, 18:06:51
I use ClockworkMod recovery, but I can't remember the last ROM I had installed, it might have been MIUI 2.3.2.
___________
When I try to start the phone normally it just hangs at the first white "htc Incredible" screen. Tried without an SD card inserted: same behavior.
If I boot into hboot instead and try to launch Recovery, it goes to the white "htc Incredible" screen and hangs indefinitely, whether SD card is in or out.
If instead, from hboot, I try to Factory Reset, it goes to the white "htc Incredible" screen and hangs indefinitely, whether SD card is in or out.
At this point I can't get past the white "htc Incredible" screen no matter what I do.
____________
I issued the "oem enableqxdm 0" command through fastboot to ensure the SD card could be mounted, then took a fresh SD card and loaded the Stock_inc_4.08.605.15 image from dinc.does-it.net and flashed it in hboot. It loaded the image, went to "Parsing…" for a few seconds, then reset to the main hboot screen (not sure if that means it was successful). Still the same outcome: stuck on the first white "htc Incredible" screen, whether simply powering on, launching recovery, or trying to factory reset.
The phone had some previous issues I can describe if anyone thinks it would help (bootlooping unless I held the phone in the freezer long enough to launch AnTuTu and underclock the CPU way down, suggesting a heat issue).
Really I would just like to get some data off of a few saved Nandroids, if I can get the phone working again as a toy for tinkering with that would just be a bonus.
Can anyone tell what my problem is?
Sounds like your recovery is borked somehow. Try fastboot flashing your recovery again (I recommend latest TWRP), and start over.
PonsAsinorem said:
Sounds like your recovery is borked somehow. Try fastboot flashing your recovery again (I recommend latest TWRP), and start over.
Click to expand...
Click to collapse
Thanks for the reply.
I tried flashing the stock recovery image (4.08.605.2) through fastboot but I kept getting the "FAILED (remote: not allowed)". I was able to load it as a .zip through the bootloader though. After rebooting and entering recovery through hboot the recovery partition would flash open, then immediately restart to the white "htc Incredible" screen again where it would hang as long as I let it.
I did notice it was getting really hot just sitting at that white screen so I popped it in the freezer to cool off for a minute. When I opened the freezer a minute later BOOM it's sitting at the home screen, fully booted. Keeping the phone in the freezer, I've since been able to reflash CWM 5.0.2.0 recovery and load my saved Nandroids. As soon as the phone is out of the freezer for 1-2 minutes it does and goes back to the white "htc Incredible" screen and either hangs or bootloops.
So right now I'm running back and forth between the freezer and the charger trying to load each of about a dozen Nandroids, backup my photos, call and sms logs, and move on to the next one. Seems like this method will at least allow me to get my saved data out of the Nandroid backups even if it takes all night.
Two questions:
1) It seems like the phone has a hardware overheating issue. After rescuing my data, I'll probably try to load an undervolted/underclocked kernel to see if it will stay alive under a reduced load...any input on the best choice for such a ROM & kernel?
2) To access my nandroid backups, do I need to load them on to this specific phone? Is there a runtime environment or can BlueStacks or something allow me to virtually load a nandroid backup from my dinc for purposes of getting the data off?
Thanks again.
Here's the situation now:
EDIT: phone went in the trash, life is less stressful.