Develop Bugs

[Q] Have i killed my desire?

Hi All,
Apologies for my first post being a cry for help but im seriously screwed at the moment.
I have a UK t-Mobile Desire that came preinstalled with 2.1, and so the story of my rooting failure begins.
First of all i tried using Unrevoked 3.1 and apparently this worked, but i was no longer able to enter recovery mode at all.
Following this i tried applying the Amon Ra loader to my device. Once this was completed the phone was seemlingly working fine but i still could not get into recovery mode, it would jsut hang on the circular logo.
By now im pretty fedup with the whole thing and i decided to unroot my device using the unlocker video guide and the unmodified RUU from this site.
Now my device boots (i guess) but the screen no longer works, at all. All i want to do is restore my phone to its factory state so i can use it.
Can please anyone help a poor newbie out.

You haven't killed it, but you should have read this:
http://forum.xda-developers.com/showthread.php?t=749551
That includes a link to fix it, though it's not easy.

thanks for the response but according to the boot screen i had hboot 0.75

Your problem is SLCD. The bootloader is not relevant.

Sorry to be a complete numpty, but what process do i need to complete, there seem to be several options on that link.
thanks, i really appreciate any help

If you want to upgrade directly to Froyo just install this RUU (easy):
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
If you want to try to get Android 2.1 back then this thread (difficult):
http://forum.xda-developers.com/showthread.php?t=750852

I just tried the "easy" option and got the following error message from the Rom update utility.
ERROR[131]: CUSTOMER ID ERROR
The ROM Update Utility cannot update your android phone
Please get the correct ROM Update Utilility and try again.

You need a goldcard in the phone.

Ok, thanks for your help.
I will dissapear for an hour or two and see if i can get this fixed.
Eitherway many thanks for your help

Insert the goldcard, run the RUU, and it will be fixed.

when i try to create the goldcard i get an "error: device not found" message when running the adb ****** command

you create the gold card in your pc not the phone. i think

I am doing it on my pc, but it would seem that my pc cant "see" the desire. Im guessing that either USB debugging is off, or the phone is connected to the pc in anotehr "mode"
sigh

you make the goldcard on pc. then insert it into the phone

It must be that USB debugging is off. Does anyone know how to turn this on remotely or without seeing the screen?

Just use the goldcard you originally used with the RUU that broke your screen.

Or did you use a t-mobile branded RUU?

I dont have it

I used the tmobile branded one

When you flash an RUU you are restored to factory defaults, so usb debugging is off.
It is possible to enable usb debugging blindly if you read the other link I posted. It's difficult. Without a goldcard you cannot flash an SLCD-compatible RUU, which is the only way you can recover the phone. There aren't any branded RUUs available that support SLCD.

[Q] Root via fastboot?

Are there ways to root using fastboot? Have usb brick but working fastboot, and guide using android emulatro doesnt work. Have latest RUU with 0.93 hboot

Have you tried running an RUU from HTC? They completely restore your phone to how it was, and your device only needs to be turned on on the bootloader screen for it to work. (power up with volume down pressed)
Note that this wil completely wipe the phone's internal memory. (though not the sd card)
You can find the RUUs here. If you have an unbranded device (meaning it wasn't customized by the carrier), this is probably the one you're looking for.
Remember: if the device powers on, it isn't bricked!

That post of RUUs is VERY old, here's the site which has them all...
http://shipped-roms.com/index.php?category=android&model=Bravo

It was rooted originally with oxygen. When brick, I used downgrade tool, pimg.img zip from sdcard in hope for it to fix itself. Installed upgrades from htc to froyo. No luck
but if possible to push ruu using fastboot I will try it. Strange thing, it will only charge if rebooting via fastboot, and its then detected as in need of qualcomm drivers.. no luck finding working drivers to that.. Haven't found similar case in any forums. ideas?

Blubba10 said:
It was rooted originally with oxygen. When brick, I used downgrade tool, pimg.img zip from sdcard in hope for it to fix itself. Installed upgrades from htc to froyo. No luck
but if possible to push ruu using fastboot I will try it. Strange thing, it will only charge if rebooting via fastboot, and its then detected as in need of qualcomm drivers.. no luck finding working drivers to that.. Haven't found similar case in any forums. ideas?
Click to expand...
Click to collapse
For drivers you should install htc sync.

I know, but it doesn't take.. Thanks for hint though

Update. When I tried to run RUU in windows I only get 170 connection error, also in fastboot mode. Found it as PB99IMG file and ran it through SDcard, but it didnt fix usb problem.. Is there a difference between those two methods when i comes to degree of restoring? Dont think so, anyway..

I'm not entirely sure, but you can try this: when the device's powered on and connected in bootloader mode, go into the Device Manager, and find your phone in the list. Right click and choose the option to install a new driver (I don't know the exact function name in English, my system's locale is Dutch). Then, go to the screen where you can select a driver. Select HTC in the vendor list and install the driver. That should fix your 170 error.
If that doesn't work, try this, and optionally the above again.

http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ download zip from here and flash from recovery after renaming it update.zip
Blubba10 said:
Update. When I tried to run RUU in windows I only get 170 connection error, also in fastboot mode. Found it as PB99IMG file and ran it through SDcard, but it didnt fix usb problem.. Is there a difference between those two methods when i comes to degree of restoring? Dont think so, anyway..
Click to expand...
Click to collapse

Big thanks, but I´ve sent it in for repair. Hope to get in on garantee, but if not, I will just get it returned and try it out..

You need root for that though which he (and me) probably has not.

No, you don't. You can flash update.zip through the stock recovery.
Do you have access to that?
Sent from my HTC Desire using XDA App

I've never had to do a usb-brick fix, but from what I understand, you should have root to flash that particular "update.zip", because otherwise you'll end up with a sig ver error or some sort of that.
As said in the first step "1. Follow this r5 rooting guide to do Step 1 of the rooting.That will give you a basic ROM to work with, with root capability."
The reason I think you need to flash it as an "update.zip" file is because the r5 method in itself does not flash a custom recovery (from which you can flash files without regard to the name).

3722 said:
I've never had to do a usb-brick fix, but from what I understand, you should have root to flash that particular "update.zip", because otherwise you'll end up with a sig ver error or some sort of that.
As said in the first step "1. Follow this r5 rooting guide to do Step 1 of the rooting.That will give you a basic ROM to work with, with root capability."
The reason I think you need to flash it as an "update.zip" file is because the r5 method in itself does not flash a custom recovery (from which you can flash files without regard to the name).
Click to expand...
Click to collapse
Yup...And now we need 10chars.

I eneed up using rageagainstthecage method to apply usb fix.. Only way wich worked..
Sent from my HTC Desire using XDA App

[Q] Big problem with htc...

I rooted my phone 6 months ago and 1 month ago it started restarting out of a sudden. Another problem was that it did not turn on the first time, so i had to get the battery out and try again to turn on the phone. When i saw that i decided to upgrade with the official Gingerbread Rom for the Desire. Now the problems started getting more and more serious. My phone remains stuck in the htc logo screen...it does not go into recovery and when i tried installing the initial ruu, to try to take it back to warranty it said that the bootloader version is not good. Any ideas how to solve this problem? I would really appreciate some help...

Maybe providing some info, like bootloader information, phone information....

Current Hboot is 1.02.0001, radio 5.17.05.23 and i wish to install RUU_Bravo_Froy2_UK_2.14.207.1_Radio_32.44.00.32U_5.09.05.30_2_release_144166_signed. I have tried to install the ROM by puting the rom file from the ruu on the memory card and renaming it as PB99IMG.zip. Once i turn on the phone in hboot, it loads the image and after 3 minutes is says "Main Version is older! Update Fail!". I have also tried to install the ruu by connecting it to the computer and booting the phone in fastboot. It said the current image version is 3.14.405.1 and the version I will install will be 2.14.207.1. After about 5 minutes in the install process it gets stuck in "Updating Signature" and after that the process stops and the following message is shown:
"ERROR[140]:BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again."
I am currently quite desperate..

Your HBOOT is newer than the one you want to flash.
You nned to downgrade it, which means you have to S-Off your device with revolutionary.io AFAIK.
Then flash one of the HBOOTs from alpharev.nl (downgrader) - then you can flash the RUU.

davebugyi said:
Your HBOOT is newer than the one you want to flash.
You nned to downgrade it, which means you have to S-Off your device with revolutionary.io AFAIK.
Then flash one of the HBOOTs from alpharev.nl (downgrader) - then you can flash the RUU.
Click to expand...
Click to collapse
Can you please give me a more detailed instruction of how to do that? Where can i get revolutionary.io AFAIK from and how do i use it? Thanks in advance

Revolutionary (aka alpharev), from here
http://revolutionary.io/
Not sure where you would get an AFAIK, but As Far As I Know, it doesn't actually exist

777ace said:
Revolutionary (aka alpharev), from here
Not sure where you would get an AFAIK, but As Far As I Know, it doesn't actually exist
Click to expand...
Click to collapse
Can you please tell me how to s-off the phone if the phone cannot start?i tried in fastboot but the software on the computer didn't detect the phone...

You need to be running fastboot in the CMD.exe...
You need to follow the guide for ADB first, then you can use fastboot to flash a new image!

danycosarca said:
Can you please tell me how to s-off the phone if the phone cannot start?i tried in fastboot but the software on the computer didn't detect the phone...
Click to expand...
Click to collapse
Enable USB debugging and connect your phone to PC. Then start revolutionary.

Terepin said:
Enable USB debugging and connect your phone to PC. Then start revolutionary.
Click to expand...
Click to collapse
How can I enable USB debugging if my phone gets stuck at the HTC logo? sorry for being such a pain guys but i am not very experienced in this stuff..

Did you manage to solve it ? I have the same problem , stuck with the boot loop issue after flashing Official RUU 2.3 upgrade. Only have access to fastboot, can't use adb to downgrade.

ridhavm said:
Did you manage to solve it ? I have the same problem , stuck with the boot loop issue after flashing Official RUU 2.3 upgrade. Only have access to fastboot, can't use adb to downgrade.
Click to expand...
Click to collapse
do u previously had any aplharev hboot? like cm7/oxygen hboots?

andQlimax said:
do u previously had any aplharev hboot? like cm7/oxygen hboots?
Click to expand...
Click to collapse
Yes, I had s-off with alpharev. The problem started with boot loop on alpharev screen. I flashed amoled RUU by mistake and had slcd brick.
Now I have installed the correct RUU but still either get stuck on boot loop or on HTC screen. Wonder if the system partitions are screwed up or if they can be restored without adb or s-off.

i did not manage to do anything. all i want to do is to put back the initial ruu so i can take the phone back to warranty. But i don't know how to downgrade hboot.

can anyone please tell me how can i downgrade my hboot? The biggest problem is that i cannot enable usb debugging because my phone is stuck with the bootloop.

danycosarca said:
How can I enable USB debugging if my phone gets stuck at the HTC logo? sorry for being such a pain guys but i am not very experienced in this stuff..
Click to expand...
Click to collapse
Boot into Fastboot and then run RUU. Setup should see it.

I managed to reinstall the official Android 2.3 RUU but the problem is that i want to install the RUU_Bravo_Froy2_UK_2.14.207.1_Radio_32.44.00.32U_5.09.05.30_2_release_144166_signed RUU. From what i have been told, i firstly have to downgrade hboot. Can anyone give me some detailed steps of how to do this?

If I were you, I'd S-OFF with revolutionary, flash recovery and flash a ROM.. when you're S-OFF, there is a way to downgrade... I just haven't got time to search now sorry
That's from my understanding that you re-did the 2.3 RUU and your phone now works.. right?

Unfortunately the phone doesn't start now either

but did it work before? have you tried leaving it for about half an hour and tried turning it on again? (I've seen faults like that). If not try the RUU again, then S-OFF - which makes life SOOOOOOO much easier

[Q] Bricked Desire - Can't get past bootloader

After reading Bortak's guide, I was still unable to fix this bootloop as I don't have a goldcard, and it seems like you need a functional Desire to create one.
The situation is:
> Desire can boot into Fastboot (Power button + back button), but attempting to enter recovery causes a boot loop (Carrier splash screen)
> Attempting to enter recovery directly (Power button + volume down) causes a boot loop
> I lost the MicroSD with this phones' recovery on it, all I have is a spare blank MicroSD
I'm wondering, is it possible to flash a new recovery off the SD card, through fastboot?
Or, can I do this through a USB connection somehow? (I currently have the latest HTC Sync installed)
Thanks for any help!
Edit: My Desire is S-ON (I swear it used to be S-OFF, but who can remember, I haven't picked this phone up for ages) and HBOOT is 0.75.0000

S-on users cant flash a custom recovery through fastboot. It can be done only via the unrevoked method. What exactly did you do to cause this? Dont you have your own RUU?

I've got similar problem, but i don't have root.
I made S-OFF with revolutionary and rovolutionary couldn't flash clockworkmod. Previously, I didn't know that I have to do root... so i wanted to do s-on to do this root. I downgraded phone to hboot 0.80 as they said on alpharev website. But now, I can't get out from fastboot. Every time, when i'm robooting, it goes to fastboot.
Please, could You help me?

Flash 2.3.3 RUU via fastboot and use revolutionary again.

Which one from those
http://forum.xda-developers.com/showthread.php?t=695667
is 2.3.3?
-----EDIT----
MatDrOiD said:
Flash 2.3.3 RUU via fastboot and use revolutionary again.
Click to expand...
Click to collapse
OK, I found it on official htc site, or sth, and it works!! Thank you very much!

Do not forget to use thanks-button.

Droidzone said:
S-on users cant flash a custom recovery through fastboot. It can be done only via the unrevoked method. What exactly did you do to cause this? Dont you have your own RUU?
Click to expand...
Click to collapse
When I got my Desire HD, I flashed Oxygen rom on this Desire and gave it to a friend. I have no idea how it got in its current state. I'm downloading the latest official RUU now.
If someone could provide some instructions on how to flash the RUU with the phone in it's current state that would be awesome

As long as you can get into fastboot not all is lost, there will be a way of flashing it was a stock rom

chongo_au said:
When I got my Desire HD, I flashed Oxygen rom on this Desire and gave it to a friend. I have no idea how it got in its current state. I'm downloading the latest official RUU now.
If someone could provide some instructions on how to flash the RUU with the phone in it's current state that would be awesome
Click to expand...
Click to collapse
Boot phone into fastboot mode, connect phone to computer and start the downloaded RUU.exe on your computer.

The RUU recognized the phone, but it refused to update due to wrong bootloader version. Looks like my RUU was not the right one, back to searching again.

If you have GSM and not a hboot with nummber 6.93.1002, the 2.3.3 RUU should work for you:
http://www.htcdev.com/process/legal_download/152

Ok I found the correct RUU (Telstra) and was able to flash everything except the radio, which failed. Attempted to retry twice but same result.
Now I have the grey HTC logo with the exclamation triangles in the corners.
Does anyone have any suggestions?

Sorry mate, but radio brick is unfixable (as far as I know).

MatDrOiD said:
If you have GSM and not a hboot with nummber 6.93.1002, the 2.3.3 RUU should work for you:
http://www.htcdev.com/process/legal_download/152
Click to expand...
Click to collapse
Thanks, that RUU flashed successfully! It said rom update complete and so on. At least now I'm making progress.
However, the rom doesn't load and I get a bootloop. I've now got the normal white HTC splashscreen appearing, then the screen flashes black, the phone vibrates 5 or 6 times, and I'm back to the splashscreen again.
I'm able to boot into bootloader (HBOOT 1.02.001 apparently) but not recovery.
I'm not familiar with adb and all that, all I can do is follow instructions, but in short, without being able to load a rom to tick the box for usb debugging, is there any way to S-OFF and or flash CWM if I can get the computer to recognise the phone (while its sitting in bootloader or fastboot mode) with the HTC Sync USB drivers or equivalent?
I'm going to say some probably unrelated words and phrases that I've read in the last days forum trawling, maybe it will jog someones memory:
> Fastboot commands
> Revolutionary hboot drivers
> USB brick
I know its probably time to lay the old Desire to rest, but I'd love to squeeze some more use out of it, I loved that phone.
Greatly appreciate the help

You did not get any errors when flashing RUU? Okay, cool. Check if you still have an ext-partition on your SD card. Maybe this let the romboot loop.
With revolutionary you will be able to get S-OFF and root in two simple steps:
http://revolutionary.io
But read the documentary site very carefully before doing anything!

Hi i'm in the same situation (desire branded how boot loop update with RUU 2.3.3 and boot loop again)
had you fixed your desire ?

Xims said:
Hi i'm in the same situation (desire branded how boot loop update with RUU 2.3.3 and boot loop again)
had you fixed your desire ?
Click to expand...
Click to collapse
Please read the thread. The solution is in there!

ok i had try revolutionary but it never find the device ( as on hboot or fastboot)
i have the htc fastboot driver so i don't see how i can user revolutionary

If you use Android Flasher while connected to the PC you can flash a recovery in fastboot mode. Either the latest Clockwork or 4EXT Recovery will make you able to flash a Desire(d) rom again

Hi to use android flasher i had to be S-off or woth the RUU of 2.3.3 i'm back S-on and i haven't find a way to go S-off from fastboot or hboot ...

[Q] still "s-on" after using the aahk kit => what can I do?

Hello
I tried to root my desire hd by using the aahk kit. I strictly followed the efffen manual, but somehow the bootloader still states that the device is in "s-on" mode. I can install custom roms, but I only get the screen showing the htc logo when rebooting the device. I can only access the bootloader and the recovery mode. (the connection to my computer works)
I already tried:
to unlock the bootloader with the help of htcdev.com (=> worked)
to apply the aah Kit a second time => does not work (I get the message that no device is found. Alternatively I can start the hack while the device is switched off. This way the device is found, but the hack doesn't succeed.
Is there anything else I can try? I hope somebody has an advice.

Steph.xda said:
Hello
I tried to root my desire hd by using the aahk kit. I strictly followed the efffen manual, but somehow the bootloader still states that the device is in "s-on" mode. I can install custom roms, but I only get the screen showing the htc logo when rebooting the device. I can only access the bootloader and the recovery mode. (the connection to my computer works)
I already tried:
to unlock the bootloader with the help of htcdev.com (=> worked)
to apply the aah Kit a second time => does not work (I get the message that no device is found. Alternatively I can start the hack while the device is switched off. This way the device is found, but the hack doesn't succeed.
Is there anything else I can try? I hope somebody has an advice.
Click to expand...
Click to collapse
You can't use AAHK on an unlocked bootloader. Relock it and try AAHK again if you want S-OFF. If you are okay with S-ON, you need to flash the boot.img each time you flash a ROM. Otherwise, your phone will hang on the HTC screen like yours is right now.
You might have used AAHK to downgrade the first time, which would be why you were still S-ON. If your phone is on 2.3.5, AAHK needs to be run twice: once to downgrade, once to root.

bananagranola said:
You can't use AAHK on an unlocked bootloader. Relock it and try AAHK again if you want S-OFF. If you are okay with S-ON, you need to flash the boot.img each time you flash a ROM. Otherwise, your phone will hang on the HTC screen like yours is right now.
You might have used AAHK to downgrade the first time, which would be why you were still S-ON. If your phone is on 2.3.5, AAHK needs to be run twice: once to downgrade, once to root.
Click to expand...
Click to collapse
Thanks for your quick reply! I successfully relocked the bootloader. However, as you may see in the screen shot the AAHK doesn't work properly.
Anyway, I do not necessary need S-Off. Where can I find information about how th flash the boot.img? (Is the boot.img extracted from the stock RUU suitable?) What's the best way to continue? Flashing the boot.img and installing a custom rom directly afterwards?
in addition:
I tried to use a different sd-card => same error.
As suggested I flashed the boot.img. It worked but I still can't use custom ROMs. What do I do wrong???
== >> Got it If anyone else has a similar problem: http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396

Steph.xda said:
Thanks for your quick reply! I successfully relocked the bootloader. However, as you may see in the screen shot the AAHK doesn't work properly.
Anyway, I do not necessary need S-Off. Where can I find information about how th flash the boot.img? (Is the boot.img extracted from the stock RUU suitable?) What's the best way to continue? Flashing the boot.img and installing a custom rom directly afterwards?
Click to expand...
Click to collapse
For AAHK: I think your sdcard may be corrupted for use as a goldcard, which can happen when it's improperly dismounted; though you can access data, you can't use it for AAHK. Get a brand-new one and try it.
For boot.img when S-ON: look in post #7's PDF in the Ace Think Tank thread linked in my signature. Instructions are in there someplace, but I can't remember the page number off the top of my head. You will need to flash the ROM, then fastboot flash the boot.img, each time.

Steph.xda said:
Thanks for your quick reply! I successfully relocked the bootloader. However, as you may see in the screen shot the AAHK doesn't work properly.
Anyway, I do not necessary need S-Off. Where can I find information about how th flash the boot.img? (Is the boot.img extracted from the stock RUU suitable?) What's the best way to continue? Flashing the boot.img and installing a custom rom directly afterwards?
in addition:
I tried to use a different sd-card => same error.
As suggested I flashed the boot.img. It worked but I still can't use custom ROMs. What do I do wrong???
== >> Got it If anyone else has a similar problem: http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
Click to expand...
Click to collapse
That seems to be a connectivity issue. Have you installed the drivers with the phone unplugged?