[Q] Phone stuck on fastboot/hboot, buttons unresponsive - Desire Q&A, Help & Troubleshooting

Hi there,
I noticed the back and search physical buttons on my HTC Desire were not working so I rebooted it. However, it now goes straight to the fastboot white screen (or hboot if I power on with vol down) but none of the physical buttons (vol or power) appear to work - I can't select any options. This happens whether the SD card is in or not.
Hboot recognises when I plug a usb cable in (says 'HBOOT USB PLUG').
Can anyone help? Given that I can't actually do anything with the phone I guess I need a PC-based solution - I'm running linux mint 12. I'm willing to try anything at this point as my only other option is to get a new phone!
details are:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
I was running Nick's Phone V1.2 Based on Oxygen 2.3.2, with the Thalamus 2.6.35.14_r4 kernel.
Like I say, everything was running fine till the back/search button stopped working and I rebooted.
I'd be very grateful for any help/advice!
Cheers,
Martin
A bit more info - when I start it up in HBOOT with the sd card in (but not without it), after about 10 seconds a message flashes up really quickly relating to:
PB99IMG.zip .... no image or wrong image!
...so I guess I need to get this zip file on there somehow.
Any ideas?
Thanks,
Martin
More info: the message that flashes up is:
SD Checking ...
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading...[PB99IMG.zip]
No image!
Loading...[PB99IMG.nbh]
No image or wrong image!
I tried putting a new PB99IMG.zip on a fresh sd card and starting HBOOT with that - it flashes but then I'm still stuck at the HBOOT screen with no norking buttons/way to select anything. Suppose I need the other .zip and .nbh files.

same problem
Im having the exact same problem. Used Nicks rom aswell and the power button became unresponsive and glitchy..went into hboot..cleared storage.
Now hboot is unresponsive and cant select anything
I flashed differnet hboots back and forth from cm7 r2 to oxygen
currently stuck on oxygen
S OFF
SLCD

I have same problem.. Is there anyone to help us ?

is your phone recognised by 'fastboot devices'?
any back up made prior problems?
fastboot oem gencheckpt - this command will take you to recovery from fastboot usb plug screen
@ Martin:
don't worry about pb99xxx.xxx check everyphone does that approx. for 10 sec.
what recovery you have?
@ Jerome: post hboot version
@Both:
Tried different Roms? (it could be coincident as both of you running the same ROM)
best thing will be revert to stock via 2.29 RUU matching your phone (or WWE with goldcard) and test buttons

Hi, I'm on clockworkmod v2.5.0.7 - couldn't tell you the exact version but it's quite recent. I've got a back-up of my sd card from about a week ago when I was using Mildwild before switching to Nick's phone.
Have copied my back-up to a spare sd card (that PB99IMG.zip file was still on there) and that let me get to recovery - the vol and power buttons started working.
I wiped everything on the phone, flashed mildwild and rebooted - but straight back to unresponsive fastboot and HBOOT is unresponsive too. I thought I was making progress!

Tried to flash 2.3.3 RUU??

Martin Quinn said:
Hi there,
More info: the message that flashes up is:
SD Checking ...
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading...[PB99IMG.zip]
No image!
Loading...[PB99IMG.nbh]
No image or wrong image!
I tried putting a new PB99IMG.zip on a fresh sd card and starting HBOOT with that - it flashes but then I'm still stuck at the HBOOT screen with no norking buttons/way to select anything. Suppose I need the other .zip and .nbh files.
Click to expand...
Click to collapse
Hi Martin,
First of all, the flashing up message and the searching for those files is normal. It scans the root of the sdcard for those filenames and flashes them if found. I remember I once flashed something in this way, but no idea why and what I do remember you need both the zip and corresponding nbh file. Do you think it's possible that your keys are physically broken?
Maybe you can flash recovery files using fastboot but I don't know if that'll help. Do you have fastboot via command line, or in your case terminal working? You might wanna check this out, don't know if it helps: http://wiki.cyanogenmod.com/wiki/Fastboot
Also, trying a RUU flash might be a good idea too, they're links to them in one of the stickies.
EDIT: More on the scanning for zip and nbh files: http://forum.xda-developers.com/showthread.php?t=880268

Thanks everyone for all your help - I've been doing a lot of reading up!
I got the 2.3.3 RUU and extracted the rom, renamed it and flashed the zip file hia HBOOT (it would not work via windows, probably because my phone could not get past HBOOT) however, I got:
Main Version is older!
Update fail
then vol +/- to reboot (the vol buttons work for this)
I think my next port of call will be making a goldcard - would this allow me to 'update' to an older version of android?
Thanks,
Martin
So I don't think I can make goldcard from my device because I can't get a CID code out of it. However, I should be able to make one using my friend's Desire - hopefully this will work and I can downgrade to 2.3.3 - should be able to get my hands on that midweek so I'll keep you posted.
At least I'm reasonably confident that this will work (with a goldcard) because the phone appears to be capable of flashing PB99IMGs (as it at least tried to flash 2.3.3 but couldn't because it was an older version than that currently on the phone).
Fingers crossed!

Goldcard bypasses the Carrier ID check, which usually gets done when one flashes RUU.
If the RUU you want to flash is not older than your phones original state, you should be able to install nearly every RUU.
Sent from my HTC Desire using XDA

update
SO,
I got hold of my friend's working desire (running cyanogenmod) and booted it with a blank sd card in it. When I put this blank sd card into my desire, it booted up (although the back/search button still did not work). I could also reboot into clockworkmod recovery. However, when I then rebooted the device......... straight back to unresponsive fastboot.
However, I've set up the android sdk on my laptop and fastboot recognises my device, so at least I might be able to do something with it tomorrow when I'm less tired!
So, this means that the rom is OK, and recovery is on there. I think my first point of call might be reflashing hboot....
It has also just occurred to me that the back button might be stuck 'on' (ie always pressed) - this would explain why my phone always boots straight into fastboot when you press the power button.
UPDATE - yes, I can recreate my phone's problems on my friends' phone just by holding down the back button and keeping it pressed ie it boots into fastboot by default (with volume buttons unresponsive until i let go of the back button), and I can get it to boot into hboot by also holding vol- and back when powering on, and the vol buttons are then similarly unresponsive while the back button is down. I think I need to look into this!
-------------------------------------------------------------------------------------------------
Right. So I took my phone apart using the guide at tjworld.net -blog -htc-desire-tear-down [if that's helpful for anyone - I can't post outside urls yet!]
and gave the buttons a good clean with Switch Cleaner from Maplins. Put it back together and it was the same.
So I went to fastboot, and fastboot reboot boots the phone perfectly (although the back/search buttons are still unresponsive).
I think that pretty much means the software is fine and I need to replace the buttons, so I've ordered some from ebay ('Genuine 4 Htc Desire G7 Keypad Membrane Flex Trackpad Bravo A8181 Keypad Uk' from Onlinemarket, £15).
Will give this a try when they turn up. In case I'm wrong, could there be any software problem causing this? I can flash a new hboot, recovery and ROM using fastboot so I should pretty much be able to replace all the software on the phone, right?
Cheers
more updates as they come in!

SOLVED
Replaced the button assembly and the phone boots as normal.
The trackpad doesn't work so I've ordered a new one of those too (only ~£5) - guess the whole lot got fried. I can live without a trackpad for a while though!

Related

[Q] Boot Loop and No recovery console

Hi,
I have become really stuck with this issue
ROM - 2.29.405.2
I origonally had a rooted phone with clockworkmod installed. I subsequently wanted to put it back to stock. Which i ran the latest RUU with the goldcard. I now am getting a continuous white HTC screen then vibrates and keeps doing this. No matter what i do i cannot get the phone into the recovery menu it just starts the reboot loop again.
I can get on fastboot and resend the same RUU to the phone. This installs without any issue and says that it is going to reboot the phone and going straight back to the rebooting loop.
I somehow need to get clockworkmod reinstalled so i can resolve this problem as it seems that the recovery partition is damaged somehow. I have s=on so i cannot force the restore of the recovery console with the colckworkmod as i get signature failure.
Is there an origional HTC recovery file i can use which gets past the signature failure??
"Clear storage" from HBOOT.
And give a try to the other way - download this zip , rename it "PB99IMG.zip" put it in the root of your SD card (not in a folder) , pull battery , plug it back , enter HBOOT (power+volume down) and apply it.
Edit: use goldcard if you are branded. If I understand you correctly, you say this "I subsequently wanted to put it back to stock. Which i ran the latest RUU with the goldcard" - if you flashed your original stock ROM, then you didn't need a gold card.
Branded
Yes i am branded.
Sure i tried this last time where it showed a blue meter on the right hand side. Went all the way and rebooted to the same if i rememeber.
But i will give it another go see if it works. Cheers.
I managed to get it to run the PB99IMG in the end which updated all parts without an issue. On rebooting of the phone it still does it boot loop.
I really done know what is causing this.

[Q] Stuck on S-Off Screen

Hi, i've been using LeeDroid for a few months now and all has been well, however yesterday my Desire turned itself off and now won't come back on. Each time i try and power it up it freezes at the Alpharev S-Off screen. I went into the menu's with volume down + power, but i can't get into my recovery - it takes me to the same frozen screen as does trying to reboot etc. And i don't think it's being recognized by usb either. So i really don't know what to do now.. is my phone bricked? I was a complete noob before rooting and flashing a custom rom before, so now that i've hit a problem i'm clueless all over again. Any help would be greatly appreciated
can you use fastboot? If so just flash a new recovery and all should be fine... chill out it can be fixed
What would i need for that? That's going into new territory
j3nni said:
What would i need for that? That's going into new territory
Click to expand...
Click to collapse
Can you access recovery? If no can you access bootloader (vol down + power on)
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
j3nni said:
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
Click to expand...
Click to collapse
Use amon_RA ... Download and flash onto ur phone and ur phone should be fixed
Plenty of guides around man, good way of learning fastboot
to use fastboot you need to download several things. Instead of using fastboot with cmd, I'd just recommend using fastboot commander, which does the job for you. In order to use that however, you will need the adb drivers, and Java SDK.
Once you've got all that, simply boot into fastboot, run "fastboot commander.exe", go into the "misc" tab, wipe Recovery, system, cache, boot, and userdata. Once you've done that download recovery, navigate to the "Hboot, radio & Rec" tab on fastboot commander, select recovery, find the recovery.img you just downloaded, and flash it. Once you've done that just boot into recovery and install any ROM you want.
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
j3nni said:
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
Click to expand...
Click to collapse
try do a full wipe of everything like I've mentioned before and then a different HBOOT
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
j3nni said:
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
Click to expand...
Click to collapse
www.alpharev.nl download a HBOOT and flash it through fastboot. Just make sure to check MD5 (you need a MD5 utility AFAIK)
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
j3nni said:
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
Click to expand...
Click to collapse
For any sense UI ROMs you would use the Sense HBOOT, remember to nandroid backup before you do so! because you might find that you get a bootloop after flashing the HBOOT.
And don't worry about asking questions! it's what we're all here for.
By the way if you don't know what different HBOOTs do: they change the partition sizes for /system /cache and /data. So by using a different HBOOT instead of the stock one you may get more storage for apps etc. if you choose one with a larger /data partition.... if that makes sense
Ok the sense one it is =)
Ah i see! Thanks for explaining cos underneath the nerd in me would have been wondering what it did lol.
Not sure how to get a nandroid done when i can't get into recovery though
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
j3nni said:
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
Click to expand...
Click to collapse
Hi.
As I can see the only way to restore is using a RUU to go back to stock then root and S-Off the phone again.
First: Preparation.
1. If you have a custom HBOOT (e.g.: 6.93.0001) you need first to flash the HBOOT Downgrader (found on alpharev site), then flash the RUU.
2. You will gonna need a Gold Card if your phone was branded.
Second: Starting
1. Make your Gold Card using someone's else phone (it has to be running Android) - the Gold Card is unique per SD Card, not per phone.
2. Use this tool to make the Gold Card: HERE
3. Guide how to make a Gold Card in Linux: HERE
4. get the latest RUU WWE 2.29.405.5. Extract the PB99IMG.zip file from the RUU: here it is how: http://forum.xda-developers.com/showthread.php?t=880268 -2nd post.
5. Reboot in bootloader (Volume-Down + Power)
7. Select fastboot
8. Flash the HBOOT Downgrader (don't forget to check the MD5 of the file you have downloaded from alpharev)
9. Extract the PB99IMG.zip and put it on root of SD Card.
10. Reboot in bootloader (scroll to REBOOT and select)
11. It will automatically load the img and ask you if you want to install
12. Check Yes and follow onscreen progress.
13. Wait untill it finnishes
14. I think it will reboot itself, if not scroll down to the Reboot obtion and press Power button to select.
IMPORTANT WARNING!!!
droidzone said:
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
Click to expand...
Click to collapse
Or if you want to go to stock and it is an unbranded phone you can just run ur ruu when the phone is in fastboot
Sent from my HTC Desire using XDA App
Think i may be the happiest girl in the world today lol i finally got it all fixed. I had a bit of trouble making the goldcard as at first my sd card kept saying it needed to be reformatted after, but after formatting it with SD Formatter program rather than Vista's own, it worked. All the rest went without a hitch. Now just gotta root, s-off and grab my new ROM and this past week can all get forgotten about =)
Thankyou so much to everyone that helped!
Incase anyone does read this far, is the procedure still the same as when i first used it back in April.. from here? http://forum.xda-developers.com/showthread.php?t=1016084
It is still the same.
If you like sense -
http://forum.xda-developers.com/showthread.php?t=1054435
░█░ [ROM][28/06] ✰.Reflex S v2.1.7 Gingerbread 2.3.3· ░█░ · |SenseGingerB 2.1+3.0|
You might like it...

unbricking an Wildfire? AKA stuck at fastboot

Hi All
Sorry if this has been resolved before but I can't see the solution.
I have just got hold of an HTC Wildfire that's stuck on Fastboot:
BUZZ PVT SHIP S-ON
HBOOT-0.80.007
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.15.31
Aug 9 2010,22:37:43
Lets assume its never been rooted - what are my options
Currently none of the buttons work in Fastboot.
When I hold the power and volume down it enters HBOOT but as before non of the buttons or touch sensor works, tho if I plug in the usb cable it changes to HBOOT USB PLUG.
Any ideas on how I can bring it back to life?
TiA
I.
I am definitely lost here. I have no idea what you mean by "Stuck at Fastboot". Fastboot is a special mode enabled when you S-OFF the device using AlphaRev / Revolutionary, which allows special Fastboot commands, previously only allowed on engineering sample devices and developer devices. AFAIK, there is no such thing as "Fastboot" on a never rooted HTC Wildfire.
Anyway, it seems everything is in order (Because, I dont know what happens when you are trying to turn on the phone normally). But, note that when in HBOOT mode, you have to wait a while for the phone to scan through the sdcard for PC49IMG files. Once the scan is over, only then you can navigate through it. Also, navigation is achieved using the side volume buttons, and, to select an entity, use the power button. No other button, and the touch will not respond in the HBOOT Mode, and it is normal.
Now, assuming your device is not booting, try installing the Stock ROM over it again, but since installing an RUU will not be possible since the device is not booting, you will have to extract the ROM.zip from one.
- Download the Froyo WWE 2.22.405.1 RUU from here - (It is an EXE File) - http://shipped-roms.com/index.php?category=android&model=Buzz
- Extract the ROM.zip file from the RUU. Follow this method (Assuming you have a Windows PC) http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
- Once you have that file, rename it to PC49IMG.zip, place on your SDCard, then reboot in HBOOT mode. It will attempt to install the ROM itself. Remember again, only use the Power button to select stuff in HBOOT mode, and side volume keys to navigate.
Thanks for the reply: Sorry I failed to report that the device jumps straight to HBOOT from power on. Downloading the required files I'll do an update once the steps have been followed.
UPDATE:
Loading PC49IMG.zip
Checking PC49IMG.zip
CID incorrect!
Update FAIL!
Press <POWER> to reboot.
It's going to need a Goldcard in that case. Create one using this guide:
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
Alternately, use this GUI App to that:
http://android.modaco.com/topic/308798-pc-application-goldcardtool/
Thanks but correct me if I am wrong but don't you need to have a working Wildfire to generate a Gold card? (debug mode on)
Got an interesting update,
As I'm getting CID error's I'm guessing its down to the phone being a branded model.
Looking at the Phone, I ruled out Orange and Virgin as they usually plaster their logo all over the the phone.
Did I few keyword searches with keywords from the Part number and other digits on the box.
It started to look like a H3G (Three) Phone.
Using the link above I downloaded:
RUU_Buzz_H3G_UK_1.16.771.2_Radio_13.45.55.24_3.35.15.31_release_131501_signed.exe (Eclair version)
Followed the steps and above and it gave me the following error:
Main Version is older!
Update Fail!
So success! (well sort off). does anyone have a H3G (Three) UK signed Froyo image (exe) RUU?
Thanks
I.
There is an OTA update.zip available for H3G UK. Look for this file on Shipped ROMs:
OTA_Buzz_Froyo_H3G_UK_2.33.771.1-1.26.771.1_release_163490jq8do89dc3y83p6w.zip
Now, I am not 100% certain on how to install this, since I personally have never tried it, but, try this procedure nevertheless.
- Download that file
- Rename to update.zip
- Then, place it on your SDCard
- Reboot in HBOOT mode
- Navigate to RECOVERY in HBOOT Mode, Press Power button. This will show you a red triangle with an exclamation mark
- Now, Press VOL UP + POWER simultaneously, this should take you to the Stock Recovery
- Here, select apply SD:update.zip. It will again automatically attempt to update the ROM.
Again thanks for your help... I'm so close
Remember none of the keys are responsive even waiting for the timeout of the loading.
Also using a different method I've think I've created a goldcard. (If it works I'll post how I did it.)
What do I do once I have a goldcard?
What file should I be looking to install?
A generic WWE one in that case, (Froyo WWE 2.22.405.1 as I linked earlier, or, Eclair 1.37.405.1, both available as EXE's)
Remember though, Goldcards are device specific. But, the defective keys are indeed a problem. In such a case, I guess the only method that remains is the one I posted in post #2
Good Luck
FECK!
So if my goldcard was working, using the extraction rom.zip process in Step 2 it would override the CID incorrect issue, am I correct?
Currently I am still getting the same error message...
Back to the drawing board...
Yes, that is about correct. Also, some sdcards do not like being made into goldcards, so, if possible, try with another. (If even after retrying, it doesn't work)
Well I'm one step closer...
Created a Goldcard and I was able to install the ROM.zip it reported that it worked, however when I powered the unit back on it went straight back for fastboot....
:/
Are you sure it's an undamaged phone? Now it seems that it's sort of damaged. (Board / button damage). The RUU flash should have solved any software issues, because, as you verified, it did flash successfully.
BTW, can you tell me which RUU you flashed, and what do you get as the first few lines of HBoot? (Which initially was Buzz PVT SHIP S-ON, HBOOT 0.80.0007... etc)?
Checked all the buttons - seem to be ok, I can hear the micro switches clicking:
It has been updated:
HBOOT-1.01.0001
MICROP-0622
RADIO-3.35.20.10
Downloading SUnAaBh v1.1 will see if that will work.
You can't flash Sunaabh / Other ROM's using this method. Official one's only. The buttons may click, but, if they are not doing what they are intended to do, it's obviously damaged,
Hmm, ok can I force a clockworkmod flash?
It's going to need the S-OFF exploit by Revolutionary to push Clockworkmod Recovery, which I guess needs USB Debugging on.
http://revolutionary.io/
Well
Volume down and power button works - otherwise it would not have gone into HBOOT and Volume up button works otherwise I would not have been able to start the flash.
Def a strange one...
See if you can do a "Clear Storage" in HBoot, although it's not going to help, it's worth a shot IMO.
BTW, doesn't the phone automatically enter in HBoot when you turn on just using the Power key?

Bootloop After Trying to Unroot

Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.
That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.
Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?
double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...
I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?
double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.
double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe
Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.

BOOTLoader Stuck HTC Wildfire

Hi guys. Sorry if this is a repost but... i cant find anything useful..to help with my problem...
So i have this HTC Wildfire Buzz... The first wildfire ever made, and it gets stuck in bootloader, I cant change options with volume keys, i cant do nothing. It freezes up in bootloader, i cant even turn it off. i need to take out the battery to turn off the phone..
What to do? I dont know how to install a RUU and which one. Please help?
BUZZ PVT SHIP S-OFF
HBOOT--1.01.0001
MICROP-0622
TOUCH PANEL-ATMELC03_16AC
RADIO-3.35.20.10
Nov 17 2010
Try update with PD98IMG ZIP find something like that, put it on sdcard and boot to HBOOT it should start updating ROM.
throw183 said:
Hi guys. Sorry if this is a repost but... i cant find anything useful..to help with my problem...
So i have this HTC Wildfire Buzz... The first wildfire ever made, and it gets stuck in bootloader, I cant change options with volume keys, i cant do nothing. It freezes up in bootloader, i cant even turn it off. i need to take out the battery to turn off the phone..
What to do? I dont know how to install a RUU and which one. Please help?
BUZZ PVT SHIP S-OFF
HBOOT--1.01.0001
MICROP-0622
TOUCH PANEL-ATMELC03_16AC
RADIO-3.35.20.10
Nov 17 2010
Click to expand...
Click to collapse
you need to take out the sdcard. the bootloader is failing because the stuff on it is too large or its a dud card.
using a different sdcard go to the "how to downgrade from hboot 1.02.0000 to hboot 1.01.0001" thread in the general section and download the package. open it and rename the 1.01.zip to pc49img.zip (making sure its not.zip.zip) and then put it onto the sdcard. put that into the phone and reboot to bootloader. assuming all is well it will find the "update" and ask you to flash it. select volume up to flash. wait for complete install and full reboot into stock rom. job done
nop didnt work, any other idea??????
i rename the 1.01.zip to pc49img.zip and then i put it into the sdcard
i start the phone holding the "down volume" boot into bootloader mode after 3 sec started
searching image.. image not found..image not found..image not found..
and back to bootloader without can move any button.
i'm 6 hours trying to find a solution even adb i tried but this not founding device cause i cannot debug usb.
plz HHhhheeeeelp
angelos83gr said:
i rename the 1.01.zip to pc49img.zip and then i put it into the sdcard
i start the phone holding the "down volume" boot into bootloader mode after 3 sec started
searching image.. image not found..image not found..image not found..
and back to bootloader without can move any button.
i'm 6 hours trying to find a solution even adb i tried but this not founding device cause i cannot debug usb.
plz HHhhheeeeelp
Click to expand...
Click to collapse
Your sdcard is incompatible (make sure its a genuine card, like sandisk ect and is preferably under 4gb) or you have renamed it to pc49img.zip.zip, if you are using windows search on Google for how to enable file extensions and see if its named zip.zip
Sent from my HTC Sensation using Tapatalk
im not that rookie
the file extension is correct.
and the sd card is 2gb from my other mobile(st15i)
Also, just because your card came from another phone and is 2gb does not mean a htc bootloader will like it. Sometimes they just reject reading from some cards. Nothing wrong with them other than the hboot simply not liking them. Try a different card if possible.
Please do not post private correspondence in public. Especially in the manner that it did. Please be patient when asking quesitons, as others do have personal lives and cannot respond instantaneously.
Hi,
I just have the exact same pb (except my HBOOT is 1.01.0002 and it is branded Bouygues). I had no SD card in my phone. At first I thought it was hardware because I found some other thread saying that this could be a short circuit resulting in power + vol down behing hold at all time, hence the bootloader and kesy not responding but it turns ou it was not it... So hope for you I guess.
* I download a RUU : RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe
* plugged the phone without battery
* put battery in (which resulted once again in bootloader screen)
* waited for the device to be installed on my computer
* after that I run the RUU.exe which wipped user data, did some other stuff... (meanwhile the screen went from bootloader to HTC) and at some point the instalation failed with a error 131 id client (because the version was older than the one installed on the phone)
* after that the phone restarted normally and everything is fine now
well, nevermind..
It works as long as I don't turn off the phone.... This is driving me nuts. I managed to downgrade the HBOOT to 1.01.1001, gained S-OFF with revolutionnary (couldn't install clockwork recovery though). I even run the RUU successfully but if I turn off the phone, next time I power it on, I end up on the bootloader screen and power and volume buttons are not working.
[Edit] I found more info in this thread http://forum.xda-developers.com/showthread.php?t=2354199#post58713960.
Instead of running the RUU, I can skip the bootloader by simply running the command :
fastboot reboot
I don't want have to do this every time I turn off my phone to make it work again. So, I'm still looking for a more definitive fix.
heavy_metal_man said:
Hmm. When your in your stock rom does the volume buttons work?
Click to expand...
Click to collapse
Actually I managed to solve this 2 days ago (I am pretty sure I already posted to say that, can't find the reply though) by copying a CMW 5.0.2.8 PC49IMG.zip (http://www25.zippyshare.com/v/70647552/file.html) file in my sdcard and inserting it in the phone.
I could boot the phone in normal mode without going through bootloader screen (even without flashing anything...).
After I restarted to bootloader (willingly this time) keys were working, it prompted for the update, so I could install CMW and after CM 7.
So everything is fine now thank you.
Fatsebz said:
well, nevermind..
It works as long as I don't turn off the phone.... This is driving me nuts. I managed to downgrade the HBOOT to 1.01.1001, gained S-OFF with revolutionnary (couldn't install clockwork recovery though). I even run the RUU successfully but if I turn off the phone, next time I power it on, I end up on the bootloader screen and power and volume buttons are not working.
[Edit] I found more info in this thread http://forum.xda-developers.com/showthread.php?t=2354199#post58713960.
Instead of running the RUU, I can skip the bootloader by simply running the command :
fastboot reboot
I don't want have to do this every time I turn off my phone to make it work again. So, I'm still looking for a more definitive fix.
Click to expand...
Click to collapse
Hmm. When your in your stock rom does the volume buttons work?
You can install clockworkmod recovery by using fastboot commands pal. If your on your stock rom and dont have advanced reboot you can download an app called quick reboot and use that to reboot. We need to work out if its your volune buttons that are broken or not. If they are we may be able to replace them, or worst case senario we can disable them.
Sent from my LG-D802 using Tapatalk

Categories

Resources