Develop Bugs

[Q] HTC Desire, locked,0.93.0001 (Rootable?)

Hi,
Just got my first ever htc phone the htc desire locked on 3 (UK)
I was looking around and I am preparing to root the phone using this guide:
http://forum.xda-developers.com/showthread.php?t=1016084
It says however that your device must be hboot 0.93 or lower. I checked and it says my phone is 0.93.0001 is it still okay to use this guide to root it?
Also will rooting my phone unlock it or must the phone be unlocked to root it?
Thanks in advanced and sorry if this is a noob question.

Unrevoked 3 will work.

I have the exact same Hboot version, and I got a custom rom on it.(rooted, s-off, alpharev Hboot)

[Q] Help! I can not restore a stock (S-on) Hboot

Hi all,
The touch screen on the HTC Desire Z has stopped working and as its still under warranty we want to return it. Now it has been running CM7 with an S-Off hboot.
I have followed the instructions from the guide and installed the stock software (RUU_Vision_HTC_WWE_1.82.405.1_R_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168383_signed) however when going into the boot loader it still says S-OFF.
Any help will be much appreciated,
Many Thanks.

[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.

Desire HD S-OFF help

Hello,
a friend of mine has HTC Desire HD but it stucks on the HTC boot logo. I tried to go into recovery but it does not have any custome recovery only Hboot. It says it is S-On. Now, the problem is, I have s-unlocked and rooted many phones. But, for unlocking boot loader, almost all the procedures i found requires enabling usb debugging mode from settings...but since the phone does not even start the OS...how can I do that? So, any idea how to unlock the boot loader when there is no custom recovery or os working on the phone?
Thanks.

As far as I know, you unlock the bootloader from fastboot, not ADB.

bananagranola said:
As far as I know, you unlock the bootloader from fastboot, not ADB.
Click to expand...
Click to collapse
Yes, the problem is the hboot on my device is 2.00.0027 and i searched around and people say it should be upgraded to 2.00.0029 before i can unlock the bootloader..but the prob is..which RUU to download to upgrade it? plus there is another method available htc tool or something like that but for that i have to have usb debugging on which i cant since the phone does not start..any help?

zealouszee said:
Yes, the problem is the hboot on my device is 2.00.0027 and i searched around and people say it should be upgraded to 2.00.0029 before i can unlock the bootloader..but the prob is..which RUU to download to upgrade it? plus there is another method available htc tool or something like that but for that i have to have usb debugging on which i cant since the phone does not start..any help?
Click to expand...
Click to collapse
Well the Ruu files are here but you have to know which one to use for your phone depending on carrier and where you live I believe

I used this guide for my Telus Desire HD: http://forum.gsmhosting.com/vbb/f66...-os-s-off-change-imei-cid-hxc-dongle-1548982/
I couldn't get the token from HTC until I upgraded to 2.00.0029 from .27.

Flashed hboot-eng.img on HTC desire HD and phone wont boot

Hi,
I have flashed the hboot-eng.mg in an attempt to get s-off onto my htc desire hd, and now it wont boot at all, no signs of life. The battery has died though, and now if i plug it in to my windows computer I can use ADB, but I cannot get into fastboot or hboot. I need help getting back to stock hboot. Before getting bricked, it was s-on, unlocked bootloader, running cyangenmod 12 with twrp 2.8.7.0. Any help would be much appreciated
PS I am new to XDA forums, this is my frist post

If you still have access to adb shell you could try adb command to get you to fastboot or RUU mode.
So practically you could flash a normal updated hboot and get full s-off through your rom by unlocking your bootloader with htc_devs way.
I have answered before how to flash a 2.00.0029 hboot and unlock your device here.
You can also chexk here and here how to S-OFF your device after hboot unlock.