Database Info

Link to Stock HTC Hero ROM

In case you've experiencing the frustration of your inquiries being met with "search for blah blah blah" here is the direct link to avoid frustration.
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe

If anyone can help me get this installed I'd appreciate it. It times out at the waiting for booatloader screen. I have the recovery ROM installed.

Try this:
Pull your battery
Put it back in
Hold down the Volume down arrow and press power
Press Volume Up, screen should say FASTBOOT USB in red
Start your RUU

If I'm in Fastboot USB Mode when I run the RUU, it fails at Verifying. If I boot into Fastboot while it's waiting to boot into recovery, it still times out.

Hmm, do you have the correct driver installed? Check your device manager under Android devices and see if the ADB driver is installed. If it is, install the driver from HTC Sync. Its called My HTC when it is installed

Yup, I definitely have the driver installed. I can use ADB just fine foe shell and push and so forth.
It connects initially to verify the info on the phone, but the RUU process reboots the phone and seems to expect it to boot into a certain bootloader. But it doesn't. I imagine the recovery ROM I flashed doesn't work with the RUU.
Does anyone have the original recovery ROM?

Had the same situation. I was able to get it to work by messing with the volume keys right after the reboot (pressed up and down a couple times.)

Gah, Windows. =/
Gonna see if I can do it in Parallels.

Having the same problem. It restarts the phone waiting for bootloader and then errors out.
Not sure what's going on. 100% positive I've got the adb driver. I've got HTC Sync working.
Using Win 7 64bit.
So it errors out and says a connection could not be made error 170.
I then disconnect the usb cable and the screen shows RUU but of course it's already disconnected.
No idea what to do.

Not sure why it is not working for you guys. My RUU would not update using the adb driver. I put it into fastboot usb mode. My pc then detected the phone. I went into device manager and checked under android devices. Make sure it says something like 'My HTC' and not 'HTC Dream' or something like that.

Hmm, worked fine for me under Vista. Installed HTC Sync update from the HTC site and all was good afterwards. Updating now.

I installed HTC Sync and now it works (that's with the custom recovery ROM).
Cool.

Yeah, the damned thing wouldn't work unless I installed HTC Sync. Back in business.

what OS are you guys using? I'm using w7 and i'm having absolutely no luck, i think i've tried everything possible...

I'm on Win7. You installed HTC Sync?
There's really no reason to flash the stock ROM anyway,,,

yes i have sync installed.
basically what happened was I lost my recovery backup image, i dunno how where i can get another one and how to apply it to my phone...this RUU thing is not working either, i tried fastboot and reinstalled all the phone drivers

Where is it getting hung up?

By the way, Byggun posted his recovery backup image:
http://rapidshare.com/files/308999685/recovery-backup.img.html

the RUU just says that my phone is not connected, i've checked the drivers and all are up to date.
i dont know exactly what to do to use the recovery image, i've never had to use one before, only had to create one.

it connects to my phone then waits for boot loader, then it says that its not connected anymore

Method for 100% factory restore, unrooted.

This is for those of you that may need warranty work, exchanges whatever. It may or may not be an issue but im sure many of you have noticed that clockwork will pop up whenever the phone is powered off with a usb connection present. Which in most cases would be an immediate red flag for those of you needing work done. This will completely restore your phone and remove the clockwork recovery flash.
Update: I no long have an Aria to try this with but if you guys are running into issues try this as well.
winsettr said:
I'd like to suggest that you update the first post to include a link with the last 2.1 RUU, seeing as the 2.2 RUU breaks the ability of future rooting (for now). I have uploaded what I believe is the updated RUU 09142010 to MegaUpload, linked below. Just thought this might help
http://www.megaupload.com/?d=XXYBORR6
Click to expand...
Click to collapse
1.) Download ATT Original Shipped ROM file from here:
http://www.htc.com/us/support/aria-att/downloads/
2.) Disconnect USB connection to phone.
3.) Power down phone
4.) Boot into Fastboot Menu (hold trackpad on start)
5.) Insert USB
6.) confirm that the phone shows "FASTBOOT USB"
7.) Run downloaded exe file
8.) Process will take a few min at the end you should have a 100% restored and unrooted phone.
It may seem self explanatory now but I was running into issues getting the HTC tool to communicate with the phone and it would fail whenever trying to send the phone into the bootloader. Thought I would just save you guys the headache.

thanks for your solution. was thinking about unrooting my phone and exchanging my aria for a samsung captative...

thanks man. doubt i'll do this, but i might need this just incase ATT and HTC actually come through with a stable update to froyo 2.2 within the next couple months.

I think it will be safe to assume that said 2.2 ROM will begin floating around in a rooted form not before too long, and will be flashable via recovery.

this is great info to have. great work.

???
has anyone actually tried this? because my pc dosent recognize phone when i try

bred904= said:
has anyone actually tried this? because my pc dosent recognize phone when i try
Click to expand...
Click to collapse
install Android SDK USB drivers first

??
i think i did... i installed something from google called android-sdk. and when i connect my phone in bootloader i can see fastboot change to fastboot usb and my pc says driver successfully installed. but when i run the .exe file it never sees my phone. also htc sync wont connect and neither will droid explorer. thanks

i agree with bred, can't seem to restore the original rom. it doesn't recognize it during the process

I have tried this method on 2 computers and the exe can NEVER find my phone.
I have installed the SDK USB drivers, my computer sees the Android 1.0 device and sees it as the HTC booloader. And I see FASTBOOT and FASTBOOT USB when unplugged/plugged.
----UPDATE 2010-07-23----
After further research I was able to determine that even with the device NOT in FASTBOOT mode, that adb couldn't see it, so I thought it might be a driver issue.
I've gotten my computer to recognize the device when it's booted normally. But when put the device in FASTBOOT or the BOOTLOADER, adb can't recognize it and I can't get the recover exe to recognize the device, regardless of mode.
I have the latest clockwork recovery installed and I would like to get everything back to factory to exchange for a captivate.

theres no way to do a nandroid backup or anything like that? curious because i was going to take mine back tomorrow to exchange for the captivate as well. i bought mine from radioshack so i might try my luck and just return it rooted . i did the trade in program with them with my iphone and it was jailbroken and they still accepted it. i dont think i would try that with at&t though... worse comes to worse just return it and say it was like that when you got it! maybe an at&t employee messed around with it before you bought it. they cant prove it was you.

Can anyone confirm this works? Just in case. This might be something I will need to do quick fast and in a hurry in the morning. And I'm hoping that if it comes down to this I won't have any issues.
Sent from my HTC Liberty using XDA App

I have been thoroughly unsuccessful in getting this method to work.
I have tried it on 3 different computers and I can never get the HTC OriginalShipRom.exe to find my phone.
I have tried following the instructions to the letter, I have also tried plugging in while booting the phone into various menus (HBOOT, FASTBOOT, and regular booting), which was advice given to me in the IRC room.
I'm plugging the phone in right after I click "Next" on the "Plug your phone into the usb port" right as it shows the "Verifying data on your PDA" window. I have tried with the phone in HBOOT, FASTBOOT, and while booting the phone, none of these seem to work.
I've also tried it with just plugging the phone in and running the exe. Nothing seems to work. People in the IRC channel are claiming successful factory restores, but I can't seem to get it to work.
So can someone please update the first post with more thorough instructions? Because those instructions don't seem to work.

The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.

OutsiderWV said:
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
Click to expand...
Click to collapse
My problem is with step 3. The second I plug my powered down Aria into the computer via USB, it powers on and goes directly into Clockwork.
If I boot the device into FASTBOOT, then plug it in, and then run the exe, it says it can't locate the device.

If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App

farquep said:
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Hi farquep, can you give me instruction on how to use linux what's the command line?? thanx

If you do it under linux, just download the file and run it like any other program in any other operating system. Although you will have to let the file run as an executable under permissions. I don't know if you need to install WINE which will emulate windows programs. There should be no need for terminal scripts.
Sent from my HTC Liberty using XDA App

Doesnt recognize my device at all. If I'm returning to insurance company, should I even bother taking off clockwork? I already have the replacement.
EDIT:
Update:
Just worked for me. I had to install aria_shipped_rooted_signed.zip first then HTCAriaOriginalShipROM.exe recognized the phone.

SysAdmNj wrote:
> I had to install aria_shipped_rooted_signed.zip first
perhaps that can be added to the original instructions.
the archive can be downloaded from here

[GUIDE] One Click How to Root the Aria with Unrevoked 3.21

I first want to thank everyone at UnrEVOked for what they've done. I'm posting this because there aren't any really detailed instructions. Its an easy enough root, but I know I've been there before and even the simplest things can be tough if things aren't laid out. So here's a step by step tutorial.
Due to some bugs, Unrevoked 3.2 was taken down shortly after being released, but the updated version is now LIVE! So obviously we're going to bring you a video tutorial on how to do it! Thanks to the guys at Unrevoked for giving us this simple solution to rooting the HTC Aria.
LINK TO VIDEO WALKTHROUGH FOR HOW TO ROOT THE ARIA
◄●REQUIRED DOWNLOADS●►
EVERYONE: Unrevoked3. Download the version for your OS.
WINDOWS USERS: unrEVOked modified USB driver
◄●How to Install HBOOT Drivers (Windows Users ONLY)●►
If you're using Windows, you're going to have to install the HBOOT drivers first. You can follow this video tutorial:
How to Install HBOOT Drivers
and follow along with these written instructions provided by the Unrevoked team:
Download the unrEVOked modified USB driver and expand it somewhere you will remember.
Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.
On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
Connect the phone to your Windows machine with a USB cable and wait for the phone to say HBOOT USB PLUG on screen.
Open Device Manager.
Click Start, then right click on Computer, then click Properties, then click Device Manager.
Under Other devices, you should now see the Android 1.0 device.
Right click on Android 1.0 and click Update Driver Software:
Click on Browse my computer for driver software.
Click on Browse and select the Android USB Driver folder on on your computer, click ok, then click next.
You should get a status bar indicating that the driver is installing. If you get any warnings, just click Ok.
Your driver should install.
Click Close and make sure Android Bootloader Interface is listed under Android Phone.
◄●Instructions●►
Make sure you downloaded Unrevoked3 for your OS.
If you're on Windows, make sure you "uninstall HTC Sync or any other program that might talk to the phone over USB (doubletwist, etc). They will cause problems" (Unrevoked.com).
Plug your phone into your computer with USB.
Drag down from the notification bar on your phone and select "Charge Only" and "Remember this"
Make sure your phone has USB Debugging turned on by going to Menu>>Settings>>Applications>>Development and checking USB debugging.
Run the Reflash application that you downloaded.
Unrevoked will run its processes. Follow the few instructions it gives and thats it!
You're now rooted!
kopimi said:
If you're stuck on "Waiting for Device", INSTALL HTC Sync, but do NOT run it.
HTC Sync will load the necessary ADB drivers onto your computer, but so long as you do not let the process run while you are trying to run unrEVOked3, it will NOT interfere. Knowing this would have saved me quite a lot of time, so hopefully someone else reads this and they can salvage their sanity
Also, if you're stuck on "Waiting for Root", go ahead and restart your Android while its connected to the USB. It took me one reboot for the root to go into effect, and right after that, unrEVOked3 finished.
Click to expand...
Click to collapse

Great guide, would have really helped me last night while I was pulling my hair out haha. One thing you may want to add to the OP:
If you're stuck on "Waiting for Device", INSTALL HTC Sync, but do NOT run it.
HTC Sync will load the necessary ADB drivers onto your computer, but so long as you do not let the process run while you are trying to run unrEVOked3, it will NOT interfere. Knowing this would have saved me quite a lot of time, so hopefully someone else reads this and they can salvage their sanity
Also, if you're stuck on "Waiting for Root", go ahead and restart your Android while its connected to the USB. It took me one reboot for the root to go into effect, and right after that, unrEVOked3 finished.

kopimi said:
Great guide, would have really helped me last night while I was pulling my hair out haha. One thing you may want to add to the OP:
If you're stuck on "Waiting for Device", INSTALL HTC Sync, but do NOT run it.
HTC Sync will load the necessary ADB drivers onto your computer, but so long as you do not let the process run while you are trying to run unrEVOked3, it will NOT interfere. Knowing this would have saved me quite a lot of time, so hopefully someone else reads this and they can salvage their sanity
Also, if you're stuck on "Waiting for Root", go ahead and restart your Android while its connected to the USB. It took me one reboot for the root to go into effect, and right after that, unrEVOked3 finished.
Click to expand...
Click to collapse
Thanks man Added to the OP

PS - Others have asked elsewhere if it flashes a custom recovery. Yes, it flashes Clockwork

I rooted my girlfriend's Aria with this and I see SuperUser Permissions (as you would with a root) but when I go to Android SDK and type "adb shell" I get a $ back instead of a 2. I also typed su and got back a permissions denied. I am also unable to do "adb remount" due to permissions. Is there any way around this?
Thanks
-Mike

LTD36 said:
I rooted my girlfriend's Aria with this and I see SuperUser Permissions (as you would with a root) but when I go to Android SDK and type "adb shell" I get a $ back instead of a 2. I also typed su and got back a permissions denied. I am also unable to do "adb remount" due to permissions. Is there any way around this?
Thanks
-Mike
Click to expand...
Click to collapse
You need to give the adb shell SuperUser permission, too. Load the SuperUser app and then make a adb shell connection while the SuperUser screen is up. Then when you type su at the $ prompt, the SuperUser app will give you the Allow/Deny prompt.
Regards,
Tom

tpbklake said:
You need to give the adb shell SuperUser permission, too. Load the SuperUser app and then make a adb shell connection while the SuperUser screen is up. Then when you type su at the $ prompt, the SuperUser app will give you the Allow/Deny prompt.
Regards,
Tom
Click to expand...
Click to collapse
Thanks for helping out and replying to that. I've been swamped with other stuff lately.

I just tried this and can't seem to get it to work. Can anybody help me out? I'm sure that I've done something wrong. I finally got unrEVOked to recognize my Aria, however when I clicked "Ok" (to root it when the message popped up) it said "Failed to push recovery. Terminating." What did I forget to do??

Nevermind... I got it to work finally.

Still shows S-ON

Freak said:
Still shows S-ON
Click to expand...
Click to collapse
Unrevoked 3.21 does not turn S-OFF on the Aria; that is only for a few CDMA phones like the EVO, Incredible, Hero and CDMA Desire.
Regards,
Tom

tpbklake said:
Unrevoked 3.21 does not turn S-OFF on the Aria; that is only for a few CDMA phones like the EVO, Incredible, Hero and CDMA Desire.
Regards,
Tom
Click to expand...
Click to collapse
Yeah don't worry about not having S-OFF, its not something necessary for a rooted phone. As long as you've got Superuser, you're set and rooted.

Sorry for my noobiness on the Aria, but what does using unrevoked to root it do for the Aria?
Sent from my HTC Liberty using XDA App

Still unable to install applications with the phone rooted
Hi, I followed the instructions, after I got the "done" message, i went to nandroid option made a backup, when it was finished i restarted the phone.
I´m trying to use Astro to install Sygic on the phone but I always get the same message.... you phone is blocked.
I see the little ninja in apps... what else is missing? what is wrong?
Thanks for your help...
I´m about to give up and sell this phone
The day i got the phone I upgraded it to the latest firmware available in HTC web page, is that the ugly part of the story?
-------------------------------------------------------
I solved this issue by istalling a custom image.
Last night I istalled the liberated_aria_ddx_R012_signed, I have to say that everythign is going perfect, no problems so far.
But everytime I plug the cable and the phone is off, it starts in recovery mode, so i have to select reboot.
Before flashing the image, I formated the SD card, wiped data, cache and dalvik cache.
If I turn on the phone it starts normally, It´s just happening when I plug the usb cable or the charger.
I also made other test, I plugged the phone when it was on, then I turned it off (with the cable plugged), when it finished the turning off process it automatically started again in the clockwork recovery mode.
Could you please tell me how to solve this?... this is my first Android phone, I donñt want it to start in recovery mode when I just want to charge it.
Thanks in advance

Phone needs to be on while charging. You no longer have to turn equipment off to get a full charge. If you charge while it's off it will go into recovery mode.

echodun said:
Phone needs to be on while charging. You no longer have to turn equipment off to get a full charge. If you charge while it's off it will go into recovery mode.
Click to expand...
Click to collapse
Thanks for your prompt answer.
Is there any way to change it?, i´d like it to work as usual, you plug it you get the green battery charging... that way it is impossible to make misstakes, for the next time i need to get in to recovery mode i would push pwer + volume-.
maybe by applying a mod.zip using clockwork?

0ptimus82 said:
Thanks for your prompt answer.
Is there any way to change it?, i´d like it to work as usual, you plug it you get the green battery charging... that way it is impossible to make misstakes, for the next time i need to get in to recovery mode i would push pwer + volume-.
maybe by applying a mod.zip using clockwork?
Click to expand...
Click to collapse
No way that I know of. It's on my Cyangenmod ROM too. Maybe a product of using the Unrevoked method of rooting. When I plug mine in to the computer charging cable I get a red light for charging and then screen goes off in about 10 secs. Not a big deal to me although it through me for a loop at first too.

echodun said:
No way that I know of. It's on my Cyangenmod ROM too. Maybe a product of using the Unrevoked method of rooting. When I plug mine in to the computer charging cable I get a red light for charging and then screen goes off in about 10 secs. Not a big deal to me although it through me for a loop at first too.
Click to expand...
Click to collapse
I know... it´s not a problem, it´s just that it´s not the way it happened for some years ago since i´ve had a cell phone .
So, the only way to avoid it is to uninstall clockwork recovery?

Cracked my screen on my rooted aria after my camera stopped working and I had filed for a warranty replacement. Was so happy with the original phone that I took the $300 hit they would apply if I sent the bad phone back with physical damage...I decided to keep the new phone and ATT will allow me to pay them in several installments with my monthly bill..
I promptly used your instructions to root this new phone. Took me all of 5 minutes.
Great job.

You can replace the glass on an Aria for a lot less than $300.

[Q] Corrupt bootloader

I was updating my inspire 4g from the HTC's update sense 3.0. I got it directly from their site. My micro-usb cable apparently wiggled loose during the "Installing Bootloader" phase of the installation. Now my phone will turn on after about 20 minutes. It does not respond to me pressing the power button and I can not get it into recovery mode. It hangs at either a Black HTC screen or a White HTC screen. It's different each time it boots. When it boots into the white HTC screen it vibrates for a good 5 minutes then eventually boots up. My phone is not rooted. Is there anything that I can do to fix this?
EDIT: I just booted into recovery after holding the volume down and power button for like 5 minutes. Although, my volume and power buttons do not work in recovery mode :/

fix
235tylerlee said:
I was updating my inspire 4g from the HTC's update sense 3.0. I got it directly from their site. My micro-usb cable apparently wiggled loose during the "Installing Bootloader" phase of the installation. Now my phone will turn on after about 20 minutes. It does not respond to me pressing the power button and I can not get it into recovery mode. It hangs at either a Black HTC screen or a White HTC screen. It's different each time it boots. When it boots into the white HTC screen it vibrates for a good 5 minutes then eventually boots up. My phone is not rooted. Is there anything that I can do to fix this?
EDIT: I just booted into recovery after holding the volume down and power button for like 5 minutes. Although, my volume and power buttons do not work in recovery mode :/
Click to expand...
Click to collapse
I've same problem here
I'm searching for fix about 5-6 hours
If your phone boots up, it's more easy to fix it.
All you need now is to turn you phone fully to android desktop and follow this thread
tau.shadowchild.nl/attn1/?p=188
(I'm new here, i can't use "insert link" option, copy and paste link in browser)
or try this http://forum.xda-developers.com/showthread.php?t=1875134&page=2
Mine even doesn't boot up after 2 hours
Takes up to 20 minutes to enter in hboot, then up to 40 minutes to enter in fastboot
and then another 40 minute for fastboot usb
But still adb doesn't recognize device :/
Any help would be greatly appreciated

uNdea said:
I've same problem here
I'm searching for fix about 5-6 hours
If your phone boots up, it's more easy to fix it.
All you need now is to turn you phone fully to android desktop and follow this thread
tau.shadowchild.nl/attn1/?p=188
(I'm new here, i can't use "insert link" option, copy and paste link in browser)
or try this http://forum.xda-developers.com/showthread.php?t=1875134&page=2
Mine even doesn't boot up after 2 hours
Takes up to 20 minutes to enter in hboot, then up to 40 minutes to enter in fastboot
and then another 40 minute for fastboot usb
But still adb doesn't recognize device :/
Any help would be greatly appreciated
Click to expand...
Click to collapse
It sucks man! but I have finally booted my phone this morning. In order for my phone to boot it must be plugged into my computer for some reason?
is there a way to fix the bootloader while the phone is on and plugged into the pc? Or is there a way to boot into recovery without turning the phone off? BTW my device is not rooted.
EDIT: I attempted to redo the AT&T update and it failed because it took to long for my device to boot. So now, I'm attempting to root it again threw Ace Advanced Hack Kit. I know that this kit is no longer supported but I did use it in the past and it worked flawlessly. So now, AAHK is waiting for my device to boot. AAHK aparently doesnt care how long it takes so I guess thats a plus. My phone will eventually turn on. I'll post the results when/if it finishes
EDIT 2: AAHK aparently did not work. AAHK still says waiting for device after the device booted normally.

235tylerlee said:
It sucks man! but I have finally booted my phone this morning. In order for my phone to boot it must be plugged into my computer for some reason?
is there a way to fix the bootloader while the phone is on and plugged into the pc? Or is there a way to boot into recovery without turning the phone off? BTW my device is not rooted.
EDIT: I attempted to redo the AT&T update and it failed because it took to long for my device to boot. So now, I'm attempting to root it again threw Ace Advanced Hack Kit. I know that this kit is no longer supported but I did use it in the past and it worked flawlessly. So now, AAHK is waiting for my device to boot. AAHK aparently doesnt care how long it takes so I guess thats a plus. My phone will eventually turn on. I'll post the results when/if it finishes
EDIT 2: AAHK aparently did not work. AAHK still says waiting for device after the device booted normally.
Click to expand...
Click to collapse
If you try to run a RUU your device will probably end up bricked. You need to fix that using this:
http://tau.shadowchild.nl/attn1/?p=188
Any other method might leave you with a dead $200 device.

AAHK is not only not supported. The server hosting the files it needs has been taken down.
In any case, you both sound like you have messed bootloaders. In the link in my signature, post #7 has a PDF guide that has, among other things, instructions on how to fix that. Make sure you read carefully.

How to fix Corrupted bootloader with RUU
glevitan said:
If you try to run a RUU your device will probably end up bricked. You need to fix that using this:
Any other method might leave you with a dead $200 device.
Click to expand...
Click to collapse
I've fixed my bootloader with RUU
It was S-ON, so i went to RUU and it worked flawlessly.
AAHK wasn't recognized phone, even when it was connected with Fastboot USB.
I corrupted bootloader when i was trying to manually downgrade from 2.3.5 (Because AAHK don't worked, file server was down)
Phone was unable to boot up (I've waited about 2 hours and it was still stuck on htc logo)
so was adb, when in Device Manager "my htc" was shown, command "adb devices" had no result
I'll tell my way (Full process takes about 3-4 hours, cross your fingers and drink some coffee, let's go..) :
I'm not developer. I tried and fixed my device with this, because other known methods don't worked for me. So read carefully every step and use it at own risk!
First, you need to remove sd card to skip PD98IMG check and make entire process faster
1) remove sd card
2) remove battery (make sure it's charged at least 50-60%)
3) insert battery and go to hboot screen (Press volume down and Power button same time, be patient and keep holding buttons, it will take about 5-10 minutes to show up hboot)
4) Wait until hboot loads fully (takes about 10-20 minute) and when you can go down or up with volume buttons, go to Fastboot
5) Wait there to load fastboot (10-20 minutes or little more) and then connect USB cable
6) Wait there for 15-30 minutes, untill PC recognizes device (Go to Device Manager and check it out if there's "Android USB devices" and "my htc" are shown) for me, it was connected and disconnected 2-3 times, Windows said to check the device and etc, but at least it was shown correctly
7) Make sure that hboot says "Fastboot USB" and run the RUU (I'm new here and can't use "insert link" function, so paste this link in browser and download, --> 4shared.com/file/XORxHMZx/RUU_Ace_Gingerbread_S_Cingular.html )
8) RUU would detect device this time and ask to update system image or radio or hboot (I don't remember what it was exactly) to 2.x.x..,
accept and click next, It would say that device will be rebooted into recovery (black screen with HTC logo)
9) Wait till the device is fully loaded in recovery mode (about 20-30 minutes, check if it's available in Device Manager again)
in 10 minutes RUU would say device isn't recongized or something like that and exit. Don't worry about it
10) When device is recongized in device manager, run the RUU again. It will ask to update to 2.x.x.., like it asked in step 8, click next. This time it wouldn't reboot, because you're already in recovery mode. It will start the update process. Be patient, it would take about 2-3 hours to fully restore. Don't think that it's stuck and don't cancel process, just wait..
Yeaaah, take deep breathe, you have done it
When it finishes, phone would restart and boot up normally with new hboot, it would be android 2.3.3, so you can run AAHK and root&unlock your device without problems
( Sorry for my English )

bananagranola said:
AAHK is not only not supported. The server hosting the files it needs has been taken down.
In any case, you both sound like you have messed bootloaders. In the link in my signature, post #7 has a PDF guide that has, among other things, instructions on how to fix that. Make sure you read carefully.
Click to expand...
Click to collapse
Well, thank you guys. I'm in the process of reading everything. I messed my bootloader up by updating my phone btw not trying to root it. BUT thank you guys for the links. I'll post back with my results after I finish doing everything that the articles insist that I try.

uNdea said:
I've fixed my bootloader with RUU
It was S-ON, so i went to RUU and it worked flawlessly.
AAHK wasn't recognized phone, even when it was connected with Fastboot USB.
I corrupted bootloader when i was trying to manually downgrade from 2.3.5 (Because AAHK don't worked, file server was down)
Phone was unable to boot up (I've waited about 2 hours and it was still stuck on htc logo)
so was adb, when in Device Manager "my htc" was shown, command "adb devices" had no result
I'll tell my way (Full process takes about 3-4 hours, cross your fingers and drink some coffee, let's go..) :
I'm not developer. I tried and fixed my device with this, because other known methods don't worked for me. So read carefully every step and use it at own risk!
First, you need to remove sd card to skip PD98IMG check and make entire process faster
1) remove sd card
2) remove battery (make sure it's charged at least 50-60%)
3) insert battery and go to hboot screen (Press volume down and Power button same time, be patient and keep holding buttons, it will take about 5-10 minutes to show up hboot)
4) Wait until hboot loads fully (takes about 10-20 minute) and when you can go down or up with volume buttons, go to Fastboot
5) Wait there to load fastboot (10-20 minutes or little more) and then connect USB cable
6) Wait there for 15-30 minutes, untill PC recognizes device (Go to Device Manager and check it out if there's "Android USB devices" and "my htc" are shown) for me, it was connected and disconnected 2-3 times, Windows said to check the device and etc, but at least it was shown correctly
7) Make sure that hboot says "Fastboot USB" and run the RUU (I'm new here and can't use "insert link" function, so paste this link in browser and download, --> 4shared.com/file/XORxHMZx/RUU_Ace_Gingerbread_S_Cingular.html )
8) RUU would detect device this time and ask to update system image or radio or hboot (I don't remember what it was exactly) to 2.x.x..,
accept and click next, It would say that device will be rebooted into recovery (black screen with HTC logo)
9) Wait till the device is fully loaded in recovery mode (about 20-30 minutes, check if it's available in Device Manager again)
in 10 minutes RUU would say device isn't recongized or something like that and exit. Don't worry about it
10) When device is recongized in device manager, run the RUU again. It will ask to update to 2.x.x.., like it asked in step 8, click next. This time it wouldn't reboot, because you're already in recovery mode. It will start the update process. Be patient, it would take about 2-3 hours to fully restore. Don't think that it's stuck and don't cancel process, just wait..
Yeaaah, take deep breathe, you have done it
When it finishes, phone would restart and boot up normally with new hboot, it would be android 2.3.3, so you can run AAHK and root&unlock your device without problems
( Sorry for my English )
Click to expand...
Click to collapse
Your english is pretty good
BUT what you suggested is almost exactly what the above said link suggested. only he did not inform you about the Device manager things.
Thanks for the update

235tylerlee said:
Your english is pretty good
BUT what you suggested is almost exactly what the above said link suggested. only he did not inform you about the Device manager things.
Thanks for the update
Click to expand...
Click to collapse
I don't know, when i researched i didn't find bootloader fix with RUU, everyone warned about brick, so i was little confused when tried that.
It was my last hope to fix, because PD98IMG.zip way doesn't worked for me, neither "boot up and ADB" method. Some thread was about making goldcard and then flashing hboot like pd98img, but i hadn't goldcard. Also, i had S-ON and i think there was no way for S-Off
Anyway, thanks to xda and google :good:
Hope this would help you too ))

bananagranola said:
AAHK is not only not supported. The server hosting the files it needs has been taken down.
In any case, you both sound like you have messed bootloaders. In the link in my signature, post #7 has a PDF guide that has, among other things, instructions on how to fix that. Make sure you read carefully.
Click to expand...
Click to collapse
I have attempted what this PDF guide has insisted that I do and I get an error. The cmd prompt says the following
"C:\Users\mine\Desktop\help\tools>fastboot flash zip PD98IMG-HBFX.zip
< waiting for device >
send 'zip' (262 KB)...OKAY [ 0.080s]
writing 'zip'...FAILED(status read failed(Too many links))
finished. total time:1911.686s
C:Users\mine\Desktop\help\tools>'
EDIT: now it booted into something..idk. It says the following
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0019
NUCRIO-0437
RADIO-26.06.04.06_M
eMMC-boot
Dec 27 2010 14:47:30
RUU
NEVERMIND Aparently the article was true..I am a dumbass..I fixed it thank you guys

HElp
uNdea said:
I've fixed my bootloader with RUU
It was S-ON, so i went to RUU and it worked flawlessly.
AAHK wasn't recognized phone, even when it was connected with Fastboot USB.
I corrupted bootloader when i was trying to manually downgrade from 2.3.5 (Because AAHK don't worked, file server was down)
Phone was unable to boot up (I've waited about 2 hours and it was still stuck on htc logo)
so was adb, when in Device Manager "my htc" was shown, command "adb devices" had no result
I'll tell my way (Full process takes about 3-4 hours, cross your fingers and drink some coffee, let's go..) :
I'm not developer. I tried and fixed my device with this, because other known methods don't worked for me. So read carefully every step and use it at own risk!
First, you need to remove sd card to skip PD98IMG check and make entire process faster
1) remove sd card
2) remove battery (make sure it's charged at least 50-60%)
3) insert battery and go to hboot screen (Press volume down and Power button same time, be patient and keep holding buttons, it will take about 5-10 minutes to show up hboot)
4) Wait until hboot loads fully (takes about 10-20 minute) and when you can go down or up with volume buttons, go to Fastboot
5) Wait there to load fastboot (10-20 minutes or little more) and then connect USB cable
6) Wait there for 15-30 minutes, untill PC recognizes device (Go to Device Manager and check it out if there's "Android USB devices" and "my htc" are shown) for me, it was connected and disconnected 2-3 times, Windows said to check the device and etc, but at least it was shown correctly
7) Make sure that hboot says "Fastboot USB" and run the RUU (I'm new here and can't use "insert link" function, so paste this link in browser and download, --> 4shared.com/file/XORxHMZx/RUU_Ace_Gingerbread_S_Cingular.html )
8) RUU would detect device this time and ask to update system image or radio or hboot (I don't remember what it was exactly) to 2.x.x..,
accept and click next, It would say that device will be rebooted into recovery (black screen with HTC logo)
9) Wait till the device is fully loaded in recovery mode (about 20-30 minutes, check if it's available in Device Manager again)
in 10 minutes RUU would say device isn't recongized or something like that and exit. Don't worry about it
10) When device is recongized in device manager, run the RUU again. It will ask to update to 2.x.x.., like it asked in step 8, click next. This time it wouldn't reboot, because you're already in recovery mode. It will start the update process. Be patient, it would take about 2-3 hours to fully restore. Don't think that it's stuck and don't cancel process, just wait..
Yeaaah, take deep breathe, you have done it
When it finishes, phone would restart and boot up normally with new hboot, it would be android 2.3.3, so you can run AAHK and root&unlock your device without problems
( Sorry for my English )
Click to expand...
Click to collapse
My Bootloader hangs up when booted...and i have the same problem as u guyz mentioned! So plz help me

waleedbutt256 said:
My Bootloader hangs up when booted...and i have the same problem as u guyz mentioned! So plz help me
Click to expand...
Click to collapse
write detailed information, how u corrupted bootloader, what u tried to fix it and etc. If u tried my method, on which state it hangs up?

uNdea said:
write detailed information, how u corrupted bootloader, what u tried to fix it and etc. If u tried my method, on which state it hangs up?
Click to expand...
Click to collapse
flashed a froyo hboot on your HTC Inspire/DHD shipped with gingerbread. Phone takes forever to turn on, then it buzzes like cheap vibrator got hit by lightning for two or three minutes – then it finally begins to boot. I tried Using IAMADUMBASS FIX by attn1..which is specifically for this problem but my DHD hangs up in bootloader + when flashing unknown error occurs!

waleedbutt256 said:
flashed a froyo hboot on your HTC Inspire/DHD shipped with gingerbread. Phone takes forever to turn on, then it buzzes like cheap vibrator got hit by lightning for two or three minutes – then it finally begins to boot. I tried Using IAMADUMBASS FIX by attn1..which is specifically for this problem but my DHD hangs up in bootloader + when flashing unknown error occurs!
Click to expand...
Click to collapse
So was my phone too, and attn1 fix doesn't worked. Try that method that I've described above step by step and let me know result))
I've checked RUU download link and it's still working

RUU Error 171 Stuck on waiting for boot loader

As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436

What we're your steps exactly? Did you relock your bootloader

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you