Develop Bugs

[q] hboot 0.93.0001

Hi,
I just received a couple of new Desires with HBOOT 0.93.0001 preinstalled.
Has anyone seen this before, and is it safe to root?
Thanks,
Adam

Go into settings and about and list firmware details.u might have a new radio too.
Hoot prob 4 slcd tho
Sent from my HTC Desire using XDA App

You don't root a bootloader. But if you have Froyo, you will not be able to root it. You'll have to downgrade the software first.

Did you get the Desire from Vodafone UK? I know their new 2.2 OTA update changes the HBOOT to 0.93 apparently (which can't be rooted at present)

Thanks for the quick responses.
The Desires did indeed come from VF UK, and yes they are SLCD.
The radio version is the same as the one I've seen on this site: 32.44.00.32U_5.09.05.30_2
Looks like I'll have wait until one of the hacking ninjas works out an easy way to get a root applied to a Froyo desire...

adfrad said:
Looks like I'll have wait until one of the hacking ninjas works out an easy way to get a root applied to a Froyo desire...
Click to expand...
Click to collapse
Yes yes , say again . .Need to wait though .

well mine is 93.001 but AMOLED i cant downgrade it for some reason!

I just got mine back from HTC after a repair. It was Hboot 0.80
Now its a new Mobo and case
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
1. Can it be rooted
2. Is it slcd or amoled

It can be rooted my desires hboot is the same. I think its amoled but you can ring HTC and they will tell you.
Sent from my HTC Desire using XDA App

If it was just the mobo and you were on 0.80 then you're on AMOLED...either way you can root without issues

Yes it can bee rooted mine is also 0.93
look at this : http://forum.xda-developers.com/showthread.php?t=776696

same hboot,radio and slcd and i was able to root using unrevoked 3.21

Tried unrevoked 3.21 (4 - 5 times) and it would not root it. Spoke to guys on irc and they dont know why it did not work.
Wondering if I should go down the downgrade 2.2 to 2.1 then root then use a custom rom back to 2.2. I want to try the cyanogen rom really.
OH and thanks guys

What happens (or not) when you try?

Bascially it says its doing it but it aint.
Waiting for boot when its already rebooted.
Pushing recovery when its not.
connect device.

duryard said:
Bascially it says its doing it but it aint.
Waiting for boot when its already rebooted.
Pushing recovery when its not.
connect device.
Click to expand...
Click to collapse
Any success yet?
Did you buy yours with this version of Hboot or was it upgraded via OTA? when?
a couple of mates have same problem can't root 0.93.0001

Yeah all sorted now thanks. Followed the "how to" at the unlocker
Rooted with unrevoked
Rom manager failed to flash 2 or 3 different roms so I flashed with Leedroid 2.2f using clockwork.
reports that you can flash cyanogen rom with amom ra bit not tried that way yet.
Happy with leedroid for now any way.
I had to send my .80 boot back to HTC for repair (GPS problem) and it came back with a new mobo and software.
You can root if you follow the correct "How to" some miss a few things out

EddyOS said:
Did you get the Desire from Vodafone UK? I know their new 2.2 OTA update changes the HBOOT to 0.93 apparently (which can't be rooted at present)
Click to expand...
Click to collapse
I think my case also similar i cant root my Desire
My Desire:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
Unrevoked3 on Windows 7 hanging with "Waiting for root... (safe to restart if this doesn't work). Any workarround for this issue?

swcom said:
I think my case also similar i cant root my Desire
My Desire:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
Unrevoked3 on Windows 7 hanging with "Waiting for root... (safe to restart if this doesn't work). Any workarround for this issue?
Click to expand...
Click to collapse
Just rooted mine last night, no problems.
Am on T-Mobile UK, HBOOT 0.93.0001, radio etc all same as yours, all latest s/w from TMUK as I had just received it back from repair recently.
My steps:
Used Unrevoked 3.22.
Download htc sync, install, then uninstall the sync application, leaving the drivers on. Didn't need to mess with hboot drivers in my case.
Attached device, connected in disk drive mode with usb debugging enabled.
Ran Unrevoked.
That was it.
My PC runs Windows 7 Professional 32-Bit.

I follow the same steps still same hanging with "Waiting for root... (safe to restart if this doesn't work). My ROM is:RUU_Bravo_Froyo_HTC__ARA_2.32.415.3_Radio_32.49.00.32U_5.11.05.27_release_157343_signed.exe

Unroot mistake !!important!!

Hey Guys,
I just tried to unroot my HTC Desire cause of warranty.
So I tried a ruu but it doesn't worked.
So i crated a PB99IMG an went to bootloader.
The bootloader made all but suddenly it said:
Main version is older / update failed !
Now I can't do anything than go to recovery
And at bootloader top those is standing:
BRAVO UNKNOWN SHIP S-ON
HBOOT-0.75.0000
MICROP-031d
TOUCH PANEL-SYNT0101
Radio-4.05.00.11
Ma 5 2010,21:12:15
Someone is able to tell me,what I can do that my phoen will work again (equal if rooted or unrooted)

tried my guide? I bet you haven't, and I bet this thread was pointless

bortak said:
tried my guide? I bet you haven't, and I bet this thread was pointless
Click to expand...
Click to collapse
Didn't tried it yet.
But I tried teh same RUU which you told. and there I'm getting the error that Main version is older !
So I'm actually s-on cause of an otehre ruu which i used before which amde me s-on but didn't flash a rom.
EDIT:
I downloaded your RUU again.
Made a PB99IMG and went to bootloader.
now it ask if I want to run update !
BUT my vol. up butten is broken (the reason why i want warranty)
so i cant confirm,any way to confirm without vol up ?

The error it's giving is impossible since you're flashing a RUU that is MUCH newer than what you appear to have there.. try the 2.3.3 RUU (since a WWE RUU won't cover warranty), that HAS to work.. and even if it gets stuck on the HTC screen or something it doesn't matter since you're getting it fixed anyway.

[Q] Can't flash stock ROM

For a few weeks my Desire has been playing up and unpredictably reboots, seemingly at random. Initially I thought it might be a software issue with the ROM I was using, but the same thing happened with various other ROMs I've tried since. So I'm thinking it's a hardware issue and I'll need to send my Desire in for service.
Normally I'd thoroughly read the forums and work out how to go back to a stock ROM, but I'm running out of time - only a few days left under warranty. Therefore this cry for help...
When I got the device it came with a 2.29.405.2 ROM and a 32.49.00.32U_5.11.05.27 radio ROM. I used unrevoked3 to root the phone and have been using custom ROMs since.
I've downloaded RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe, but every time I'm trying to flash it, the process aborts during 'updating signature...' and I end up with:
Code:
ERROR [131]: CUSTOMER ID ERROR.
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Not sure what I'm doing wrong. Maybe I'm using an RUU for the wrong area? I'm pretty sure the original ROM was WWE though (it definitely was 2.29.405.2 / 32.49.00.32U_5.11.05.27). I've read somewhere that you can't just flash an RUU if it has a lower HBOOT version... Do I need a goldcard or what's the best way to go back to the stock ROM?
Any help would be much appreciated...
Just in case, here's what my bootloader info:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18

You only need a goldcard if you are branded right now..
So is your phone branded with a carrier rom, then you must make a goldcard.
I think customer id error is due to incorrect goldcard.
There is a newer version, 2.29.405.5 I dont know if that's gonna work but worth a try.
You can also try to put the zip on your sd card instead of running an exe on your pc, assuming that you run the exe.

Thanks for the quick response.
My Desire was unbranded, so I guess I won't need a goldcard then.
I've downloaded the newer RUU version you mentioned, but got the same error message...
So far I've only tried the .exe, but I'll see if I have more success with the .zip.
Could the issue be that my current HBOOT version is higher than that of the RUU?

You can try to flash 2.3.3 from htcdev.com it's works for all hboots and without goldcards

boy_in_oz said:
My Desire was unbranded, so I guess I won't need a goldcard then.
Could the issue be that my current HBOOT version is higher than that of the RUU?
Click to expand...
Click to collapse
Since you get a CID error, I would definitely try a goldcard.
You can also try flashing the downgrader from alpharev first.
ETA: I think the latter would help.
from alpharev site: said:
# Downgrade protection, these HBOOTs cannot be overwritten by an OTA or RUU, unless you flash a downgrader HBOOT first.
Click to expand...
Click to collapse
-Jobo
@MatDrOiD (vv post below) Good point. I failed to notice that.

@touch of jobo:
Flashing downgrader from AlphaRev is not possible, the OP is S-ON.
@OP:
Check bortak's guide to bring your phone back to stock.

Have you tried step 7 in Bortak's guide? (http://forum.xda-developers.com/showthread.php?t=1275632) It was the solution for me! I skipped the downgrading part (had the same hboot as you have, so that shouldn't be a problem) and went on with phase 2.
If your phone was indeed unbranded, the goldcard should not be a problem as I understood..

Thanks guys. I'm at work at the moment but will give Bortak's guide a shot when I get home tonight and report back then.

The definition of unbranded is a bit different. Unbranded does not exactly mean that there isnt a carrier logo. HTC manufactured and sold phones in India as an example is for all intents a branded Device. It's the INFOCID property that defines whether branded or unbranded.
fastboot oem gencheckpt
Click to expand...
Click to collapse
Inside an RUU zip is a small text file. Open it and see if your INFOCID value is included. If not, you cant flash that RUU without a goldcard. See my sig for the unbricking guide, which explains this.
From my Guide:
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code (Customer ID) which prevents you from flashing a ROM meant for any other brand and also blocks a Generic WWE RUU. If you're from India, it is branded with HTC_038. If you're unbranded, things are looking much easier for you, as generic WWE RUUs for SLCD are easily available. Run the following code from the sdk folder to find out if your device is branded
Code:
fastboot oem gencheckpt
This displays the CustID Code as HTC__ (and a number). If these numbers are the same as included in the cidnum value in the file android-info.txt, your device is unbranded. I have noted the following cidnums are unbranded: HTC__001, HTC__E11, HTC__N34, HTC__203, HTC__102, HTC__K18, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__016, HTC__032. I'm not sure whether it is an exclusive list. To find out if an RUU is compatible for your ROM, the value displayed by fastboot oem gencheckpt has to be included in the cidnum list of the RUU. If it isnt included, you will need to use a goldcard to bypass the cidnum checks done by the RUU.
Check if you have made a goldcard (A goldcard is a normal microsd card modified to become special while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA or allow you to switch between software meant for different regions). The purpose of a goldcard is that when apparently incompatible ROMs are flashed with a goldcard inside the device, the flashing process skips certain checks like the Customer ID check (and hence no CID error). Note however that you cannot ordinarily install software of a lower version just because you have a goldcard. Note also that it is the software version which is important, and not the Bootloader version. Note that if you want to downgrade your software to a lower version, it is easiest to use Teppic74's utility (Link1 or Link2), and downgrade to his version of the RUU (1.21), then upgrade to your version of RUU. If your device is SLCD, always make sure the software you're about to flash does support an SLCD screen. As a general rule of thumb, flashing any version <2.0 may be dangerous. Teppic74 assures us that the version 1.21 his utility comes with, is compatible with SLCDs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Wow, I would have never guessed this... With fastboot oem gencheckpt I found that the CID is T-MOB101... i.e. my Desire is actually branded! I bought it from mobicity in Australia as an imported unlocked phone and *assumed* that it was unbranded... So it's not surprising that the RUU gave me a customer ID error. (This also explains why the OTA update failed while I was still using this ROM).
What's really weird though is that the version of the ROM that the phone came with was definitely 2.29.405.2 with baseband ROM 32.49.00.32U_5.11.05.27... I did some googling today, but couldn't actually find a T-Mobile ROM with these version numbers
My guess is that mobicity imported the phone and flashed a stock HTC WWE ROM so they could sell it in Australia...
Any thoughts on this? I'm assuming that means that I do need a goldcard after all to go back to the stock ROM?

Ok, as I couldn't find a T-Mobile ROM with the aforementioned version numbers, I eventually decided to make a goldcard and flash RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe. The whole process worked fine without any error messages and the RUU reported success at the end.
Unfortunately my bootloader still displays the same info as in post 1, i.e. I'm still on HBOOT 0.93.0001. I would have expected this to revert back to 0.93... Did something go wrong with the updating procedure?
The issue is obviously still that the original ROM seemed to be a T-Mobile ROM (in fact I think a German one as fastboot oem gencheckpt reports the carrier as TMD), so I'm not sure if the service point will accept the unbranded WWE ROM I flashed.
The other option might be to flash the official HTC Desire Android 2.3 Upgrade from www.htcdev.com, but I think it's not compatible with T-Mobile Germany Desires... If I could flash this, it would at least be an official release and the service point shouldn't complain. Does anyone know how easy it is to root/S-OFF/install custom recoveries/ROMs afterwards? From what I read, I would need to use revolutionary, right?
Any alternative suggestions would be much appreciate...

Your are totally fine with 2.29 RUU. Hboot would only update if you flash 2.3.3 RUU. Did not read about guys who "bricked" their phone by using 2.3.3 RUU on a desire by T-Mobile.
Sent from ICS with Transparent XDA App

[Q] Bad repairman + bad ROM = what next?

So after getting frustrated trying to fix things myself, I decided to just hand the phone over to a repairman. I chose the worst possible one.
So now I have a Desire with Android Freedom by MONI69 installed with all its Sense and bloatware. And 64MB free internal memory. And doing a factory-reset does nothing (so this ROM is essentially as-new-factory-condition).
Should I...
a) just flash Oxygen as one normally might?
b) use revolutionary first?
c) something else, for which there is an easy-to-follow guide online?
I'll be upgrading in about 5 months, so I don't need to be pushing it to be all it can be. Just functional with Oxygen.
Relevant bits:
clockworkmod 2.5.0.1
android 2.3.3
baseband 32.56.00.32U_5.17.05.23
kernal 2.6.35.10-g3f43272
[email protected] #1
build number 3.14.405..1 CL96875 release-keys
Android Freedom 2.2.2 V1 by MONI69
Webkit/533.1
Bravo PVT-1 S-on
HBoot 0.80.0000
microp 031d
toouchpanel synt0101
radio 5.17.05.23
mar 29 2010 21:34:33

Well you can flash Oxygen but it will not really fix your internal memory issues since you are on Stock HBoot. I'd S-off first change Hboot or Oxygenr2 then flash Oxygen.

stankyou said:
Well you can flash Oxygen but it will not really fix your internal memory issues since you are on Stock HBoot. I'd S-off first change Hboot or Oxygenr2 then flash Oxygen.
Click to expand...
Click to collapse
Thanks. According to revolutionary.io, that tool only supports
HTC Desire (bravo) 0.93.0001, 1.02.0001
While I'm on 0.80.000
Is that a recipe for disaster? I can probably coast on what little memory I'll get back with Oxygen for 4-5 months.

Check unrevoked.com and see if it covers your hboot.. I bet someone here can verify this.
Or you can upgrade to the Official HTC Gingerbread RUU then use revolutionary.

stankyou said:
Check unrevoked.com and see if it covers your hboot.. I bet someone here can verify this.
Or you can upgrade to the Official HTC Gingerbread RUU then use revolutionary.
Click to expand...
Click to collapse
Unless I missed something, unrevoked just roots but leaves S-ON. Unrevoked forever doesn't work with GSM Desires.
So upgrading to official HTC Gingerbread RUU will alter the HBOOT to something revolutionary-friendly?

My bad. Sorry. http://alpharev.nl/ should get you s-off and the correct hboot to flash.
Check this guide to be sure.. http://forum.xda-developers.com/showthread.php?t=1275632
Item number 3.

[Q] Deeply confused by unbrick attempt - can anyone help ?

Hi All,
Apologies in advance... I'm a noob.
Well for a long time I was a happy camper running the excellent Marange MIUI ROMs on my HTC desire (which had been replaced by a PVT4 motherboard version). This was S-OFF and running HBOOT 0.93... but then one day a couple of months ago I got into a boot loop where all I got was the MIUI boot logo... not really a loop more just stuck at the logo.
So I tried several clueless attempts to reimage using the TeamWin TWRP boot loader... but nothing I did worked. So after several failed RUU attempts and random PB99IMG boots and one successful run of:
RUU_Bravo_Telstra_WWE_1.15.841.14_R4_Radio_32.30.00.28U_4.05.00.11_123851
I had what I imagined was a stock phone running an ancient Telstra release (it is a Telstra branded phone - the other world wide English RUUs refused to recognise the phone - 130 error).
I tried re-flashing the baseband radio, ClockworkMod v2.5.0.7 Recovery and MIUI... and wound up back to square one stuck in the MIUI logo and the RUU I used to get back to stock is now refusing to do anything) and this time I noticed my phone reports:
BRAVO UNKNOWN SHIP S-ON
HBOOT 0.75.0000
MICROP-051d
TOUCH PANEL-SYMT0101
RADIO-5.17.05.23
Mar 5 2010, 21:12:15
So somehow my PVT4 S-OFF 0.93 changed to the above. Which I don't understand... I thought that only a Goldcard could do something like that. None of the recovery tools seem to want to deal with HBOOT 0.75 and the fact that I'm S-ON would appear to be a pain.
The other thing that really confuses me is that how come if the phone is S-ON it lets me wipe everything and install the latest Marange MIUI ROMs ? Surely if it's S-ON then these would have to be signed (maybe they are for all I know).
Finally, if I use adb when the phone is stuck in it's MIUI boot logo I'm amazed I can get a root shell.
Anyone got any advice on how my phone got into such a mess, how to fix HBOOT and get a decent ROM running again ?
Any help hugely appreciated. The more detail the better.
Many AtDhVaAnNkCsE
Cheers,
Doug
"The big print giveth and the small print taketh away..."

How where you s-off, with hboot 0.93? Alpharev hboots have 6.93 etc.
Anyways, did you try the 2.3 RUU? Check my sig.
You can flash roms with s-on, but you can't change recovery.

Hi abaaaabbbb63
abaaaabbbb63 said:
How where you s-off, with hboot 0.93? Alpharev hboots have 6.93 etc.
Anyways, did you try the 2.3 RUU? Check my sig.
You can flash roms with s-on, but you can't change recovery.
Click to expand...
Click to collapse
To be honest I couldn't quite remember the state of my HBOOT I just new that it had been newer than 0.75, possibly 0.80, and that I had S-OFF and PVT4.
Your suggestion worked perfectly! I ran the RUU without issue to upgrade to 2.3 which gave me a new 1.x HBOOT and then I ran revolutionary and was then able to install MIUI. Smooth as...
Thank you so much!
I find the howto guides out there have lots of how but not too much why. I like detail on why things work or don't. Like why did that RUU work when so many others I tried didn't... did HTC make RUU 2.3 more forgiving in it's identification of supported phones ?
Anyway, once again many thanks for your kind help.
Cheers,
Doug

dscoular said:
Hi abaaaabbbb63
To be honest I couldn't quite remember the state of my HBOOT I just new that it had been newer than 0.75, possibly 0.80, and that I had S-OFF and PVT4.
Your suggestion worked perfectly! I ran the RUU without issue to upgrade to 2.3 which gave me a new 1.x HBOOT and then I ran revolutionary and was then able to install MIUI. Smooth as...
Thank you so much!
I find the howto guides out there have lots of how but not too much why. I like detail on why things work or don't. Like why did that RUU work when so many others I tried didn't... did HTC make RUU 2.3 more forgiving in it's identification of supported phones ?
Anyway, once again many thanks for your kind help.
Cheers,
Doug
Click to expand...
Click to collapse
the 2.3 ruu is not supported by htc but is there if u wanted it. so they just made a 1 for all update if u like, basically any brand (o2 etc) any region and so on.