• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root htc desire bravo stuck in bootloop- can anybody assist me in cracking this with adb

thanks once againespecially to scotty 85, and hadron for all the info in this,.

so i think ive been using the correct rom.zip file
i was extracting it from the ruu.exe by running the ruu and then locating the file in a temp folder, relocating to fastboot folder then flashing with adb to the phone.
i was running this as instructed to try and see where it was failing rather than just running the ruu.exe.

i have just noticed the at some point during all this mucking around my hboot has updated from 0.930001 to 1.02.0001.

another ignorant question: how do i check the md5sum of the rom.zip?

i am aware that there maybe faulty hardware on the phone but am still pushing to try and get it to accept a new recovery or rom.
iether way i am getting cid and remote signature verify fails.
i tried running

fastboot oem get_identifier_token

but only get an error message even though the phone is recognised as a fastboot device.
hmmm,
i will keep trying for now.
cheers all
 
Haven't much time today, but something has run, at least partially: 1.02 is the hboot that ruu installs.

You need a utility to calculate the md5 sum, which you then compare with the value on the website. It's built into OSX and Linux, but on Windows you have to install one. Unfortunately I don't use Windows, so don't know the name of one offhand.
 
battymatty007 said:
thanks once againespecially to scotty 85, and hadron for all the info in this,.

so i think ive been using the correct rom.zip file
i was extracting it from the ruu.exe by running the ruu and then locating the file in a temp folder, relocating to fastboot folder then flashing with adb to the phone.
i was running this as instructed to try and see where it was failing rather than just running the ruu.exe.
ok. sounds like you are using the correct file. and the phone is booting to ruu mode,correct?(black screen with silver htc)

sounds like you have experienced an hboot pre-update.typically,the update will update the hboot,sometimes the radio and other firmware,then give the following(or something similar):

failed! hboot preupdate failure. please flush again immediately

at thit time,you simply enter the command to flash again( fastboot flash zip rom.zip ) and the ruu should flash the remaining partitions. i cannot image why youd be getting the cid or signiture errors with this particular ruu,unless its somehow tied to whatever hardware issues it has.

i have just noticed the at some point during all this mucking around my hboot has updated from 0.930001 to 1.02.0001.

another ignorant question: how do i check the md5sum of the rom.zip?

i am aware that there maybe faulty hardware on the phone but am still pushing to try and get it to accept a new recovery or rom.
iether way i am getting cid and remote signature verify fails.
i tried running

fastboot oem get_identifier_token

but only get an error message even though the phone is recognised as a fastboot device.
hmmm,
i will keep trying for now.
cheers all
Click to expand...

what error message are you getting? does your new hboot have the pink ***locked*** at the top?
 
no pink locked/unlocked on hboot screen
nothing at all there infact only:

bravp pvt4 ship s-on
microp-051d
touch panel-synt0101
radio-5.10.05.30
jul 22 2011,16:19:16
RUU

i can only access hboot screen by plugging phone into pc then unplugging- it then exists RUU and enters hboot.

fastboot oem get_identifier_token
info [err] command error

fastboot getvar cid
orang001
anybody know which roms may have this cid?

i will try downloading the stock android 2.3 update and running again.

perplexing
 
ahh. the update did not install an hboot compatible with htcdev,so you will not be able to unlock it. your best bet will be to continue trying to run the ruu. you might also try just runing the .exe file and see if it does anything differently.

unfortunately,given hadrons info that no orange ruus were leaked,the 2.3 update is likely the only one that is compatible with your ORANG001 cid :( (see posts 15 and 17)
 
ive run the 2.3 ruu multiple times, both as the .exe app and by fastbooting the .zip file.
both to no avail.
is there anyway to modify a rom or in some way trick the 1.02.0001 hboot into accepting a rom?
i think i will have to accept defeat.
it was almost certain that if we managed to restore the device to 'working' that it would still have a fatal hardware issue anyway.
i am very happy to have learnt so much and tempted to buy a few desire bravos that are stuck in bootloop to see if my new knowledge can salvage them.
many thanks to all, any more ideas please let me know.

:smokingsomb:
 
What error did the RUU give?

The one remaining thing you could try is to go to HTCDev.com and follow the instructions for unlocking the bootloader. This will involve downloading a different RUU, which will install the unlockable bootloader (1.06 or 1.07 IIRC). If it gets that far, and nothing else is fouled up, you could then flash a custom recovery then see whether you can install a ROM.

As I said above, because this hboot stops you using some other tools I generally don't recommend it, but if the 2.3 one isn't going to work and you're going to write it off otherwise, there's nothing to lose from doing this - you'll get some experience of a more "standard" unlocking procedure if it works :)
 
thanks hadron, will give it a go.
getting muddled as have tried so many roms now.
as I remember the 2.3 android update gave me a remote signature fail when run as a zip through fastboot.
if I try the htcdev unlock should I select desire or all other models from the list? not sure what covers the bravo.
just hoping the phone will give me the unlock identifier when requested.
I will let you know what happens.
 
Yes, it's just "HTC Desire" in that list.

It's also possible that the RUU will just run to completion. If it does you don't even need to worry about unlocking the bootloader unless you wish to.
 
brilliant,
that cracked it.
an hboot for the original orange rom (2.17.61.3) on the htcdev site.
the hboot is 1.03.0003.
adb comand provided the identifier token with no problem and the phone is now unlocked.
i am pretty certain it will bootloop with 7 vibes again but i will try for a custom revovery then wipe everything clean and flash a custom rom to see what happens.
its been really informative and satisfying to have made it this far.
big big thanks
x
 
well, thats about it.
just getting hboot and fastboot, but no recovery to flash a new rom.
tends to just give me the 7 vibes each time i try, did load once but i didnt have an sd card in that time.
still it seems pointles as its clearly messed up hardware
thanks once again all.
 
Last edited by a moderator:
battymatty007 said:
Hello, i am stuck and hoping someone can assist me.
Im a beginner with this stuff so my understanding is basic and instructions need to be idiot proof!
I have purchased an htc desire (G7) bravo on ebay as faulty: crashes regularly and only restarts after an hour or so, hangs on white startup screen with green htc logo.
Phone details:
Bravo PVT4
Samsung amoled by looking at the LCD
Ship S-on
Hboot 0.93.0001

Since purchase i have tested it and the above is true. I am wondering if this could be a solvable software issue rather than hardware at fault.
I have noticed that there are a screen full of unusual control widgets that i cannot get rid of by factory resetting, and that i cannot locate on downloaded apps menu- i wonder if someone has pushed these into the phone and caused this problem.
So far i have rooted using unrevoked 3 and recovery RA 2.0.1 (as PVT4 and uncertain if 40,000 or 20,000).
It took me sometime to get success because the phone would freeze but eventually with a bit of luck i got a success message from unrevoked and the phone entered recovery mode (black with green text).
I powered down the phone hoping to complete later on but on restarting it now just hangs up and i cant get it to boot or enter recovery. Is this a bootloop?
In addition sometimes it just vibrates 7 times before freezing on startup- what does this mean?
I can access hboot and fast boot with power+vol down and these are stable.
I have since set up adb on my computer and in command the phone responds to fastboot by providing its serial no.
I am unsure exactly where to go from here.
Is it possible to flash the operating system from fastboot?
Or even the kernel? (i am uncertain how to aquire and use a boot.img file? and have had no luck so far tring to install one)
I have tried downloading and flashing cm7.zip from the adb folder. i have tried the same with superuser, but i get the error message: failed registery (or something similar as i remember).
So as you can tell i am well out of my depth but finding this very interesting and am eager to crack it (with some help).
I am hoping to be able to use adb to rectify the problems or wipe the lot and start again.
Any such help greatly appreciated,
Regards,
Mat.
Click to expand...



Im 100% positive it doesnt have nothing to do with your software .the problem is your on/off button .im a technician and i see this problem constantly . :Solution bang your phone lightly on the side were your on/off switch is an i garantee your phone will boot up. bang the phone lightly against a table ,try it and let me know ,Good luck
 
Salsero said:
Im 100% positive it doesnt have nothing to do with your software .the problem is your on/off button .im a technician and i see this problem constantly . :Solution bang your phone lightly on the side were your on/off switch is an i garantee your phone will boot up. bang the phone lightly against a table ,try it and let me know ,Good luck
Click to expand...
Well, hopefully the op no longer has to worry about it as this thread is well over a year and a half old and hasn't been seen since.....but, perhaps others can benefit ;)
 
You must log in or register to reply here.
Back
Top Bottom