[Q] Unable to access HBOOT menu. What to do? - Desire Q&A, Help & Troubleshooting

I am not able to access the hboot menu on my HTC Desire (8181) with power+vol down keys after rebooting. It is running Froyo 2.2 and I think the hboot version was 0.93 ( from what I remember from before).
How much ever I try, the phone just boots normally & continues to load the ROM (official 2.2 load). I have tried the suggestions on other threads to remove the battery for some time & then try (same behavior), disabling fast boot option in applications (which does not exist in Froyo for HTC desire), keeping the SD card out etc without any success.
I want to load a custom rom (ICS probably) and hence want to check the HBOOT version (S-off status, PVT4 or not etc) for the next steps, but I am just not able to access the hboot menu screen.
Any recommendations please on how to access the HBOOT menu on my HTC Desire?
Thanks

Maybe your volume down button is broken?

Thanks. Let me check that. I never thought of that possibility. If it is broken, then I better leave it as it is.

For accessing bootloader in adb issue command adb reboot bootloader.

Related

[SOLVED] HTC Desire SLCD Screen Black After Flashing Stock Rom

OK, so I have found a few guides that try to resolve this, but as yet nothing that completely got me where I need to be.
The background:
I have a UK T-mobile HTC Desire (Bravo) with HBOOT 0.93.0001, with an SLCD screen, with the latest OTA updates and now running MIUI ROM 1.5.13.
The problem:
Condensation under the screen meant that I needed to send back under warranty. To do this I needed to restore my phone to stock T-Mobile ROM.
I got hold of a stock T-Mobile RUU (available at Shipped Roms), tried to run this but got an error as the version of my current ROM and HBOOT was newer than what I was trying to put on the phone.
I did a bit more digging and realised that I was doing a few things wrong, did not have goldcard and realised that because I was on HBOOT 0.93 this would not work. Therefore I needed to downgrade HBOOT (http://forum.xda-developers.com/showthread.php?t=768256). This guide will put an unbranded RUU on the phone if followed completely, but obviously I needed a T-mo branded version and so used the RUU mentioned above.
This would prove to be my mistake.
This updated my phone to HBOOT 0.80 which unfortunately does not play nice with the SLCD screen.
Net result: my phone turned on (could feel the vibration when turning phone on).
Here is how I solved it....
The disclaimer:
This worked for me, it may not work for you ... etc etc .. I'm not responsible, etc etc.
OK, so to recap - I had:
- Created a gold card (TIP: always create a gold card by accessing your microSD in your phone over USB, I tried it in a card reader and it does not work properly)
- Downgraded to HBOOT 0.80 (http://forum.xda-developers.com/showthread.php?t=768256)
- Ran a T-Mobile Stock RUU (available at Shipped Roms)
The next steps:
- Go and get the latest T-Mobile OTA update (again, from Shipped Roms)
- Get your gold card (or create if required. Remember this must be done with the SD card in a phone, can be a different phone but must be your goldcard image)
- Rename the OTA update to update.zip and copy to root of SD card
You know need to boot in to recovery and run update.zip. All of this will be without the screen, so you need to follow the exact steps and make sure you wait where told - wait longer if in any doubt
- turn the phone off (battery out is sure fire way)
- Hold volume down (and keep held), press and release power whilst keeping volume held down (3-4 seconds)
- Now in HBOOT menu
- Wait 20 seconds
- Volume down * 1, press power button (phone go in to recovery)
- Wait for 30 seconds (reading SD card)
- Hold volume up and press power (go in to Android system recovery)
- Volume down *1, press power button (select "Apply sdcard:update.zip")
- Wait for 15 minutes (the update.zip on SD card is being read and applied)
- Press power *1 to reboot system
- After reboot you must wait a while and then you will see some green graphics on the screen... just wait it out
- You should then see the little pink circle and you can be happy
You will need to change language as the phone starts in German or Turkish, once done you will need to reboot to get everything completely back to English (some things such as vmail seemed to stick until reboot)
I hope this helps for anyone that was also terrified that they had broken their phone!!
There are also several methods for getting the phone in to USB debugging as it allows you to do much more with the phone and has some of it's own options to get you out of this mess. Obviously this requires going blind, these are the steps I went through:
- Turn off phone
- Turn on phone
- Wait until fully booted
- Press power and slide finger down to unlock
- Press and hold finger on screen until vibrate to verify you unlocked the screen
- Press back
- Menu
- Right 3 times, Down 1, click (Settings menu)
- Up *15 (to get to top of menu), down *10, click (Applications menu)
- Down * 3, click (Development menu)
- Click (USB debugging)
- Click (Confirm)
Hope this helps all!!
Cheers,
Pete
have the same issue with my htc desire but the problem is i have a usb brick so can't create a gold card.any help?
Hello!
Thanks for your guide. But for me it was a little different.
About my phone: HTC Desire with SLCD and T-Mobile Branding. S-Off via Alpharev
Preparing: Made a Goldcard out of my SD-Card with only one partition
Step 1: Downgrade HBOOT to original version (bravo_downgrade.img). Only necessary if you installed a Alpharev HBOOT.
Step 2: Downgrade the phone to Android 2.1 like here
Step 3: Install T-Mobile RUU. I used "RUU_Bravo_Froyo_TMO_AT_2.12.112.1_Radio_32.46.00.32U_5.10.05.17_2_release_143754_signed.exe", you can find it at shipped-roms.com.
Result: No Black Screen, Downgraded Phone with original T-Mobile ROM.
I had problems with the RUU. So I started the RUU and found in the Temp-Folder the rom.zip. I renamed it to PB99IMG.zip, copied it on the SD and installed the rom in the Bootloader.
Cheers
Kobi-P

[Q] Can not escape bootloader - volume and power keys unresponsive?

Hey guys,
I hope you're all well.
Great forum by the way.
I've searched extensively for solutions to my problem, yet I've been unable to find anything.
I think the problem started yesterday, when I restarted my phone and for some reason it went into safe mode.
I didn't lost any functionality so I didn't care too much until this morning, when I tried to get out of safe mode.
My phone has taken me to the bootloader (white screen with skateboarding Android) and for some reason, the power key (used to select options) and the volume keys (used to scroll) are not functioning.
As a result I cannot click or choose anything and the white bootloader screen persists in limbo.
I desperately need some suggestions, any help is very much appreciated.
Just so you know:
I've taken the battery out and put it back in, which takes me straight back to the bootloader screen, same with sim card.
The phone is running Coredroid (can't remember which version).
Has S-OFF.
Sorry I'm not much of an expert...
Also, on startup, phone says something along the lines of:
SD Checking...
LOADING... [PD98DIAG.zip]
NO IMAGE!
LOADING... [PD98DIAG.nbh]
NO IMAGE OR WRONG IMAGE!
LOADING... [PD98IMG.zip]
NO IMAGE!
LOADING... [PD98IMG.nbh]
NO IMAGE OR WRONG IMAGE!
Kind regards,
- Ric
Something has become corrupted.
Best bet would be to use an ruu 2.36.405.8 and lower, once loaded up, skip through the setup and then root again.
http://driphter.com/index.php?topic=3867.0
after you've done all that, install rom manager, and then restore your last backup.
Just a quick update.
Managed to get into Clockwork Mod Recovery.
Got the SD Card to mount.
Formatted it in windows.
Copied over Coredroid.
Went thru the install process.
Installed without error.
Booted up.
Took it's time, displayed the Coredroid animation but then vibrated and took me straight to Bootloader again.
Any advice or best to do this RUU thing?
Would this:
RUU_Ace_HTC_WWE_1.32.405.3_Radio_12.28b.60.140e_26.03.02.15_M3_release_155032_signed
Be ok?
Am I in the right ballpark?
Truly got no clue when it comes to this stuff
use the 2.36.405.8 RUU, then you wont have to spend your time updating the radio and such, that version of gingerbread is rootable using gingerbreak (so just follow that path of my method and you're set)
JSLEnterprises said:
Something has become corrupted.
Best bet would be to use an ruu 2.36.405.8 and lower, once loaded up, skip through the setup and then root again.
after you've done all that, install rom manager, and then restore your last backup.
Click to expand...
Click to collapse
Hello mate,
Just a quick question.
How do I get my computer to recognize my phone prior to running this RUU thing?
Considering I can't scroll or select anything in bootloader screen?
Can I run this RUU thing from ClockworkMod?
Kind regards,
- Ric
you run it from your pc. its an advaced installer that pushes the stock rom to the device and overwrites everything... it will put the phone into a different bootloader state than the one you can nav through.
Also, sometimes the phone is booting into bootloader, while other times it is booting into ClockworkMod.
It seems I have no control over which screen it initially boots to.
I DO HAVE options in ClockworkMod because my volume keys allow me to scoll and my power button allows selection, whereas in bootloader, the keys do not function.
Could you PLEASE provide some advice on how to boot into ClockworkMod rather than bootloader?
Kind regards,
- Ric
JSLEnterprises said:
you run it from your pc. its an advaced installer that pushes the stock rom to the device and overwrites everything... it will put the phone into a different bootloader state than the one you can nav through.
Click to expand...
Click to collapse
Yes I do realize I run the RUU from the PC.
I don't think I was very clear.
I was trying to ask you what state the phone needs to be in?
Do I have to mount the SD Card from ClockworkMod?
Or can I run the RUU while in Bootloader?
Does it matter?
Neither have worked.
I get a 170 error (USB Connection error).
The RUU cannot see my phone.
I was wondering if there's a way to fix this?
I have also now tried to install Leedroid and Gingervillian.
Both have installed perfectly but refuse to boot all the way.
Instead taking me back to Bootloader...
Ok, Leedroid somehow booted.
No network or anything though.
Very unstable...
if the phone is running leedroid now and you have the htc sync tools installed (but without sync running, just needs to be installed for the drivers)
leave it as it is connected to your pc, doesnt matter if debugging or anything else is on or off. just leave it alone sitting where it is on your desk or wherever it is...
Start the RUU, and then just follow the path the installer takes you through, then let it do its magic...
Ended up d/l Cyanogen.
Installed it.
Working, detected networks, wifi is connected.
All good I suppose.
That was a bit scary!
Thanks for your help mate.

HTC Desire -- Stuck at HBOOT after RUU

Hopefully I'm just being blind here -- and I have tried a number of guides to fix this -- but I'm pretty stuck.
Couple of days ago the volume down button started playing up, then the menu and search keys stopped working. At the time I had rooted the phone with unrevoked and installed CM7.3 (iirc), and taken the S-OFF with Alpharev 1.8. I figured it was probably a software issue and for some reason decided to go back to run an RUU (rather than just running a different ROM, don't really know why on earth I did that). Kind of having a feeling that I was very dense and ran the wrong RUU, as now the phone is simply stuck at HBOOT.
When I say stuck, I mean as soon as I turn on the phone it goes directly into the stock HBOOT (FASTBOOT -- RECOVERY -- CLEAR STORAGE -- SIMLOCK) yet NONE of the buttons work (so I cannot navigate it at all). Perhaps it is actually a hardware issue, which would make sense as it boots straight into HBOOT, no HTC screen or anything. When it runs the SD check it comes back with wrong / image missing in all the checks.
Tried running ADB, couldn't find the phone. Other RUU's return error 170 as though they can't find the phone. Phone does register "HBOOT USB PLUG" when plugged in though, and my Windows 7 machine does recognise it, but as there's a new RUU on there USB debugging is not enabled and I cannot access the SD card through the phone.
The full info on the HBOOT screen is --
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
Any help would be much appreciated... Later on today I'll pick up a card reader, figure my only option now is to try and get through to it that way?
Hmmmm!
I'm not sure but it actually could sound like a hardware issue. You have the STOCK HBOOT and then ran the RUU for the HTC Desire? If u did so I cant see it as a software brick. PM me if you need some more help. I had a Desire for some month ago that i bricked A LOT more than yours, and i got it fixed (by myself... took some nights thought :/
Yeah I thought that as well, but before I flashed the RUU, although the phone was powering directly into HBOOT, I could use the buttons to navigate the menu. Now, I simply can't.
I should maybe add that when it checks the SD it returns with wrong / missing image (can't remember the exact wording -- pops up then goes pretty quickly).
Also this afternoon I opened up the desire and checked and reseated the buttons, all seem to be working as normal. Seeing as it's stuck at HBOOT, I think I'll just need to buy a new SD card and put whatever the image it's looking for is on it?
Edit: I was thinking that reformatting the SD card (through a PC USB reader) as FAT32, then placing the PB99IMG.zip from the latest 2.3 HTC WWE RUU might work? I can't see any reason why not -- think the Desire is unbranded so no goldcard required.
Edit2: Still waiting on a new adapter, but was wondering why the RUU failed -- the file was RUU_Bravo_Froyo_Vodafone_UK_2.33.161.2_Radio_32.49.00.32U_5.11.05.27_release_157522_signed.exe from shipped-roms. Don't see any reason why flashing it would have ended up leaving me in this position -- even if it was a hardware issue underlying it.
Sorry to double post...
Tried putting the PB99img from the RUU (and tried the 2.3 update PB99img) to no avail on both the SD card that I'd been using recently and the one that had originally come with the phone -- no luck; once HBOOT detects the img and runs through it, it gets stuck at the "parsing... [1] [2] [3]" etc page.
Any help would be massively appreciated, would be appalled if I have managed to brick this in my enthusiasm for fixing a volume button problem -.-
Already checked bortak's troubleshooting guide?
Yep and anything else I could find really. Starting to think this little droid is doomed.

May have bricked DHD after using AAHK

So, figured I'd attempt to root the thing today via the AAHK on my locked DHD. According to the effen manual, I won't need to gold card it beforehand either.
I went through the process, and I was told that the ROM that I had installed (2.5.3? Sense 3.0) had to be downgraded, so I went ahead with it. After downgrading, I was brought to an unresponsive bootloader. Being patient enough, I let it sit while I watched a movie, yet nothing happened after. I took out the battery and restarted it, and all I got was the Hutchinson 3G (my carrier) logo and it just stops there.
When I try booting in recovery mode to get to the bootloader, it does so, but it hangs.
After enough tinkering, I noticed the bootloader was only responsive once I rebooted without the memory card inserted. The phone itself is still inaccessible as it just stops at the 3G logo.
So far, I've tried to restore it through an RUU, but since it's still (I assume) carrier locked, I have to find the ROM that shipped with it. Unfortunately, I can't find a ROM that caters to Hutchinson 3G ROI (Ireland), so right now I'm downloading a UK version of it to see if it works. Apart from that, any recommendations on what I could do next?
Thanks :3
people are gonna need a little more info eg. what does it say on the boot screen s-off etc
what rom your trying to flash, formatted sd-card or not, possibly a corrupted download
AAHK does the business well, but can baulk at the slightest thing.
fairly new to some of this myself, but learning, my DHD took 4 attempts to finally do now on JT R4
Oh, mmkay:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
eMMC-boot
Apr 12 2011, 0:55:45
-----------------------------
Anything else I should include up there?
As for the ROM, I wasn't trying to flash anything bar the one that was downloaded through the AAHK client itself during the downgrade process.
After more tinkering, I've decided to leave it till today afternoon. Though I've made a few observations; so far
- The bootloader works fine when I turn it on WITHOUT the memory card
- The phone gets detected under the name "Android 1.0" when plugged in via USB both in hboot and fastboot. The fact that it gets detected I'll assume is a good thing
- Which leads to the second bit; it can be restored, since I've tried an Asian DHD ROM. It didn't complete because I was apparently supposed to find the appropriate ROM for it, which I assume is the H3G ROI version of it
- Aaand, the ROM still won't load up, and gets stuck at the H3G boot logo.
- According to the effen manual, it could be that my SD card was corrupt, so now my intention is just to merely restore it until I can actually afford to attain another memory card, which will be in a good few weeks and I don't wanna be smartphone-less for that period of time. But the only problem is; how?
if memory serves there isnt a rom in AAHK. the zip you intend using should copied be on your sdcard and initiated via recovery - vol down and on button. you should also be "s" off - did it offer to downgrade first [if needed]
from the manual
Insert the SDCard into the phone
Boot the phone
Turn on USB Debugging (Yes, plug it IN - use original cable plugged directly into the system board.)
IMPORTANT: Turn phone to charge-only mode. The phone stays in charge-only mode throughout this entire process. To make sure of this, check the default (menu > settings > connect to PC > charge only)
Win7/Vista: Right click on hack-ace.cmd and start as administrator (This will start the tool and bring you to the main menu)
option - 1
Install Clockworkmod
Clockworkmod version 5.0.2.7 -- yes
How to flash a custom ROM with ClockworkMod Recovery
Place the zipfile to be flashed on the sdcard. Do NOT unzip it.
Froyo disable Fast Boot: Menu > Settings > Applications > uncheck fast boot
Gingerbread disable Fast Boot: Menu > Settings > Power Options > uncheck fast boot
Turn phone off, no usb connected
Hold down vol- button, then press power to start, keep holding the vol- down button until Hboot menu shows up
Use the vol- down button to scroll down to recovery after some file checks are done (they will flash by quickly)
Press power to start recovery
Use vol down button to navigate, and the capacitive search button (bottom row of buttons, far right) to select
NOT VERY OPTIONAL/STRONGLY RECOMMENDED: If recommended by rom author or if flashing over another rom type (ex: cyanogenmod over anything else), wipe data/factory reset in Clockworkmod Recovery
Install zip from sdcard > choose zip from sdcard > select zipfile > Yes - (name of zipfile)
Repeat choose zip from sdcard for any add ons (gapps, themes, kernels, etc)
Press back button when flashing is complete until "reboot system now" is at the top of the screen.
Press power to reboot the system.
If desired, return the fast boot setting to ON in settings. (See above)
once yu crack it you'll see where you were going wrong
radio flashing is the easiest way to brick if you dont know exactly what your doing 99.9% of other stuff is recoverable
restoration is a more complicated path than rooting for noobs
I'm aware that there's no ROM included with the AAHK, I'm referring to the one that was downloaded THROUGH the AAHK when it said I'm gonna have to downgrade it beforehand.
And with reference to hboot, that's where another problem lies; my memory card is the one causing hboot to freeze. Hence, removing it prior to booting is the only way to get to it.
can you rerun AAHK and make a goldcard during setup and go that route -- wont help i know but being as its still "s"on you can return under warranty aslong as you dont send sim and sd-card tell them it wont go past h-boot.
if you have a card reader then format the card to make sure its clean, the drag and drop the required files on it - i have a lappy solely for this job with AV etc permanently turned off
Well, I'll rerun AAHK when I can find the SD card adapter, but since I've only recently moved house, it's gonna be near impossible until I get time off to unpack, which, till then, I'm still gonna need a functioning phone, so right now, I'm just looking for ways to return it to stock :3
i cant assist any further then as i've not yet RUU'd any devices as of yet.
hope you get it sorted
Thanks for trying anyways :3
I've been searching for an Irish RUU. Currently trying a UK version of it hoping it MIGHT just work. Anyone have more ideas?
Edit: Ok it didn't. Posted on the Three Ireland support boards trying to see if I can get an RUU

[Q] can someone Help with fixing my DINC after Unrooting gone wrong?

Ok, so have a serious issue
at first i was able to successfully root and flash clockwork mod recovery on my DInc using the rooting method from unrevoked 3 and was running Clockwork mod recovery +Cyanogen mod7 through the Rom manager (cannot remember exactly which versions.) it was all running fine, then just decided to unroot it with a few different methods (one didnt work and the others failed as well, maybe because i mismatched the stuff i used during the First try at the unrooting process..but because i tried one method after the other, and it was soo long ago, i forgot exactly how i ran into this problem
basically somehow i screwed up the Unrooting process.
SO now I am Having the System UIDs are inconsistent message every time i start my Incredible, Tried recovery that didnt work, tried factory reset+ erase all data on phone SD card (i probably accidentally erased the recovery image) it seems to reboot and be all restored, like a stock image, but weirdly the Superuser Ninja holding the AR15 still shows up in my app drawer (even after i unrooted and restored everything.) so i i decided to check out if the permissions were still enabled and they were not... SU shows up and doesnt function (just blank). I investigated further by downloading ROMmanager and then everything ended up forceclosing over and over again...I went to download "# Root Checker" and pressed "check" and it proclaims that its not rooted but under "User" it said "root"... i guess that its saying im rooted but im not?!?! LOL
anwhyo here are my DInc Specs as of Right now:
my DInc is an SLCD, running android 2.3.4. baseband is 2.15.10.07.07
Kernel 2.6.35.13-g03546aa
[email protected]#1
Fri Oct 7 10:52:52 CST 2011
software number 4.08.605.2
im still able to Access HBOOT and the screen says
*** UNLOCKED***
INCREDIBLE XD SHIP S-ON,
HBOOT-1.02.0000
MICROP 0417
TOUCH PANEL- ATMELC03_16ac
RADIO-2.15.10.07.07
DEC 21 2011,23:37:16
when i tried to see if i can reflash it through fastboot, the device manager in my W8.1 Pro 64 bit says "Device failed Enumeration" and USB notification popped up from the system tray saying that the device wasn't recognizable
so the drivers provided by Unrevoked for enabling the phone to be detected dont work, and the HTC Sync program doesnt even detect the Incredible.
However,,,,
the Fast boot, Boot Loader, and HBOOT still works upon pressing the Volume-down + Power and am still able to access Internal Phone Memory AND the SD card when the Phone is plugged into my computer via micro USB (so it looks like im able to flash things to it, but stuck as to how and what)
Because im still able to access the the SD card and internal Memory,
I tried putting PB31mg.zip on the root of the SD and ran HBOOT> and i gave it a second to detect the file.. then it said "Main Version is older Update Fail!"
the guy in this thread http://forum.xda-developers.com/showthread.php?t=1286223 seems to have had Similar problems..... I have added symtoms and issues on top of the whole 2.3.4 with S-on and Radio 2.15.10.07.07....
I just want to get back to vanilla-stock on my incredible with absolutely no modifications and without the System UID/feeling lucky pop up bugging me. and dont care what route i take, weather it be rerooting and reflashing , just reflashing. i just dont know what to do to get it that way from here.
Can anyone please help me figure out how to get back to normal with this DInc???
Im sorry if i dont make any sense im having a hard time explaining it. if you do understand me, i would appreciate your help. also if you need me to clarify things just ask me.
I'm a little rusty, but I remember this was the preferred method for rooting because of problem with the 1click unlockers,
(nuts, can't post links yet)... Google, "[HOW TO](gaining root)unlock,downgrade,and achieve s-off with htcDev" and look for it on androidforums.com
Try picking it up from step2, just keep the unlock_code.bin from miniadb_inc files from step1 on the phone. As long as typing 'adb devices' displays your phones serial number, you should be ok. As a long shot, you could try a PC with Windows7.
Try this ruu thru hboot http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip

Categories

Resources