Database Info

[RUU] RUU_Hero_C_Sprint_1.56.651.2_signed_release.exe

Today I was reminded that being nice to people can pay off! I was lucky enough to get my hands on the new Sprint RUU thanks to syscrasher13!
What is this?
RUU (radio unit upgrade) is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
The 1.29 RUU has always been available, however people that purchased phones that came with 1.56 on them were unable to use that RUU: http://geekfor.me/news/sprint-ruu-fails/
This is the updated version for those people that have "with Google" branded phones that came with software version 1.56 on them.
What can I do with it?
You can use this to "unroot" your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can't fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it's not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn't.
You can flash this on a phone that originally came with 1.29 on it, just know that once you do you will no longer be able to use the 1.29 RUU. You will have to use this one.
How do I use it?
Download the file below and run the exe.
Go in to the folder that the exe created and run ARUWizard.exe
What else do I need to know?
The phone is still rootable. I tested it successfully using the auto-rooter in the pre-kitchen.
Fresh ROM still works just fine (as should any 1.56 based rom)
You will not be able to use the 1.29 RUU after this one, but I don't know of any reason that you would want to
Although some img's in the RUU have different dates than the original it appears that they are identical other than system.img
You don't need to run this unless you are trying to return your phone to stock. You won't get anything special from running it.
Download here: http://geekfor.me/news/sprint_ruu_156/

Thank you so much flipz!! As always sharing the goods with the comunity!!!
Amazing work

thanks for sharing!

appreciate this very much!

thanks flipzmode....always a chance this could come in handy at some point

THANKS! was worried about having a with Google phone until now

thanks flipz

Many thanks!
Now, with this file on hand, I think it might be time to go ahead and root my new phone. Mostly I just want proper control over the device -- not likely to flash any ROMs until they evolve a little more -- but your work looks real solid and I plan on keeping up with it. Good show!
(on a side note, fwiw -- jumping ship from the Touch Pro to the Hero, after being with WinMo since the i730, has been my most satisfying smartphone experience, ever)

Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Ooops: You did - on this page. Sorry.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Click to expand...
Click to collapse
I've included md5 values on my releases since fresh 1.0. It's not in this post but if you click the link to go to the download page you'll see it there.

This definitely needs to be stickied...I know myself and others have often referenced the RUU in many troubleshooting posts throughout my (admittedly short) stay at xda so far.
Thank Flipz for getting and posting this stuff!

Thanks for this! Looks like we can root non Sprint CDMA Heroes now. (Cellular South, Bluegrass Cellular)
Any idea exactly how we managed to get this? From HTC? From Sprint?
I really want to find one for Cellular South and might as well try for Bluegrass Cellular since it has its own CID as well.
Doesn't look like the different version radio will be an issue, but would be nice to have the RUU around just in case.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
Click to expand...
Click to collapse
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.

posguy99 said:
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.
Click to expand...
Click to collapse
Sprint and HTC aren't exactly providing an md5 on a file that hasn't been officially released. But I did create an md5 when I uploaded it so you know the file downloaded is the same one I uploaded.
Additionally the zip of the images located inside of the RUU are unmodifiable which is why we couldn't modify the old RUU to work with the new phones. When you start the RUU it will push the files to your phone and then check them. If they aren't what they are supposed to be, it will fail.

someone share the direct download link(eg, rapidshare link) to me?
i live in China and i cannot use the bit.ly services(because the gov blocked it)

fyi to those who are wondering this will work on a non google branded phone...however it does not fix the Rev 0 Rev a problem as it does not appear to update the pri to match that of the "with google" phones.
I dont care what sprint says and what htc says. My non google and my wifes google phone have two different speeds...
im exchanging mine for a with google phone today

Thanks!
this saved my phone. I was about to throw it away.

USB Connection Error
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.

nemesys504 said:
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.
Click to expand...
Click to collapse
Just because we always have to ask to rule out the obvious...did you run it as administrator? (Right click on the file, select "Run as Administrator")

Same Problem
I am having same issue as above on Win 7 64 bit. However everything else works from this machine to my phone. Rooting it, usb mount of SD, screen shots, etc. Please help me. I want to flash back to starting point and start over.
Thanks.
Jamie

How I learned to love the bomb..oops, I mean how I finally got CWM working :D

Okay, here goes the story-
1.Got an Inspire
2.Did the Hack Kit and then installed the Rooted Stock ROM (Discontinued), everything went okay but when trying to reboot into CWM, I got the HTC Screen for a few seconds then blackness, I later determined it was working I just couldn't see it for whatever reason.
3.Okay, I thought I'd try Bubby's One Click and see if that would fix it, it went great too, but CWM still no workie, getting frustated now.
4.I thought I'd try flashing a non-AT&T ROM, since so many have been having issue running one and getting the working, but black screened CWM, I chose CoreDroid's.
5.I put CoreDroid's ZIP on my SD Card, went into ROM Manager and installed it, making sure clear memory and backup current ROM were checked.
6.It rebooted into CWM, which of course I couldn't see, then about 10 minutes later it rebooted, and the beautiful CoreDroid Animation came up, and a few minutes after that I had CoreDroid up and running.
7.Well, I thought, CWM should work fine now, EHHHHH Sorry Johnny (which sounded weird, since my name is Mike ), wrong answer, I rebooted into CWM and there it was again, total blackness.
8.Okay, I noticed in CoreDroid that to be able to flash new Radio's, you had to have Eng S-OFF, so I ran the One Click Eng S-Off Tool found here http://forum.xda-developers.com/showthread.php?t=855403 , making sure to check the box saying I already have S-Off.
9.It ran, and said it was successful, and I now had Eng S-Off, so I rebooted into Hboot to check, and at the top sure enough, it said Eng S-Off, I then hit PowerDown, which it did, but then....well, go to 10
10.It rebooted into...yep, CWM! Clear and beautiful, it looked wonderful! So booted back up, went into ROM Manager and told it to boot into CWM, it did so and it came up again, no problems! I did it again to make sure it wasn't a fluke, nope, all was well now in CWM Land!
So, how's that for a saga? Ahh, now I can kick back, it's Miller Time, or Dr.Pepper Time in my world, I don't drink
Use this at YOUR OWN RISK! I take no responsibility for bricked or ruined phones, I just posted this in hopes it might help out people having CWM issues. DO NOT send me hate mail because this didn't work for you

Good job bro!! I don't personally have the problem, but I've been following tons who have. Well done!

i did step 8 throu 10 and it works great thanks a mill!

No prob, I'm glad I could help you guys out!

congrads!!! i'm gonna try it out, i really wanna try some of these awesome roms available

Thanks Epic, let me know how it goes for you! I can't figure out what it did, other than maybe some files were corrupted or missing, and doing the Eng S-Off pushed and refreshed whatever was corruped or missing, either way I am glad to have it working again

Very nice discovery, I will in cooperate this into the next version of my program. Thanks a ton.

bubby323 said:
Very nice discovery, I will in cooperate this into the next version of my program. Thanks a ton.
Click to expand...
Click to collapse
No Prob Bubby, I'm glad I could help and give something back! I am in full support of you by the way, I think it's pretty slimy how they ganged up on you like that, when all you did was try and make things easier for the community. If I can help out in any way, let me know!

californiarailroader said:
No Prob Bubby, I'm glad I could help and give something back! I am in full support of you by the way, I think it's pretty slimy how they ganged up on you like that, when all you did was try and make things easier for the community. If I can help out in any way, let me know!
Click to expand...
Click to collapse
Will do.

I believe (if I'm not mistaken) that ENG S-OFF is the Engineering bootloader... it's not the best way to S-Off, because it puts the Engineer's Test HBOOT onto your phone, which causes some problems for other things. Also, to get back to complete stock, you'll now need to flash a stock HBOOT as well, if I remember correctly.
For that very reason, I would *NOT* incorporate this into your one-click, bubby... it worked for me perfectly the way it is, WITHOUT an Engineering HBOOT. I'd leave this as a possible solution for the ones that actually have the problem.

ClearD said:
I believe (if I'm not mistaken) that ENG S-OFF is the Engineering bootloader... it's not the best way to S-Off, because it puts the Engineer's Test HBOOT onto your phone, which causes some problems for other things. Also, to get back to complete stock, you'll now need to flash a stock HBOOT as well, if I remember correctly.
Click to expand...
Click to collapse
I haven't had any issues yet, so hopefully I'm good I wouldn't have even ran it except for the fact that to flash other radios, you need to have it on there. I don't mind doing whatever I have to do to go back to Stock, which I don't plan on doing unless I have to send it in for warranty or insurance.
That said, I just posted it so that it might be of help to others, so I guess try it if you are having problems with CWM showing up properly, otherwise leave it alone

californiarailroader said:
I haven't had any issues yet, so hopefully I'm good I wouldn't have even ran it except for the fact that to flash other radios, you need to have it on there. I don't mind doing whatever I have to do to go back to Stock, which I don't plan on doing unless I have to send it in for warranty or insurance.
Click to expand...
Click to collapse
No doubt. I hope I never have to, either... I just remember that with an engineer hboot on the desire, it was a LOT harder to get it back to stock, and had several other issues, and that's why they did away with it in favor of non-ENG HBOOT options. I like how it opens up the phone, though. This is indeed a great find that it works with ours!
EDIT: Ahh, I found it. It's in the G2 Wiki here.
"INSTALLING ENGINEERING HBOOT (DZ/G2/DHD) - OPTIONAL and UNNECESSARY!
Assuming you've backed up your phone with Clockwork's nandroid, you can install the engineering HBOOT (bootloader), which among other things allows you to use fastboot flash (or flashing-over-usb from your computer). This is unnecessary for most users but provides additional functionality for developers.
This is totally optional and dangerous - if the write to the phone partition fails the phone will be bricked. At the moment there is no cure for a phone that has been bricked by a failed hboot install."
That very last line is why Bubby should NOT include this in his one click... you think problems are bad now, wait till someone bricks a device and we can't unbrick it! D:

ClearD said:
No doubt. I hope I never have to, either... I just remember that with an engineer hboot on the desire, it was a LOT harder to get it back to stock, and had several other issues, and that's why they did away with it in favor of non-ENG HBOOT options. I like how it opens up the phone, though. This is indeed a great find that it works with ours!
EDIT: Ahh, I found it. It's in the G2 Wiki here.
"INSTALLING ENGINEERING HBOOT (DZ/G2/DHD) - OPTIONAL and UNNECESSARY!
Assuming you've backed up your phone with Clockwork's nandroid, you can install the engineering HBOOT (bootloader), which among other things allows you to use fastboot flash (or flashing-over-usb from your computer). This is unnecessary for most users but provides additional functionality for developers.
This is totally optional and dangerous - if the write to the phone partition fails the phone will be bricked. At the moment there is no cure for a phone that has been bricked by a failed hboot install."
That very last line is why Bubby should NOT include this in his one click... you think problems are bad now, wait till someone bricks a device and we can't unbrick it! D:
Click to expand...
Click to collapse
Thanks for posting that. I was just going by what they said to do in the CoreDroid thread, and it worked for me, thankfully
"
FAQ:
Again, it's recommended that you flash radio 26.04.02.17_M2 (Orange ES 1.75.75.2 / HTC WWE 1.72.405.3) or radio_26.06.03.24_M2 (TELUS WWE 1.84.661.1) or Radio 26.05.05.27_M3 - (Orange UK 1.84.61.2)
How do I flash a new radio?
In order to flash other radios you need to have ENG S-OFF. Once your device has that read this thread to learn how to flash a radio.img
How to get ENG S-OFF:
Download the attached "easy S-OFF.zip" at the botton of this FAQ.
Extract to a folder of your choice.
Connect your phone to a computer (make sure you have USB Debugging enabled. Connect charge only!)
Open my "Desire HD easy s-off.exe", click "S-OFF it"! Allow possible SuperUser request on your phone.
There could be force closes after the process, just reboot and everything will be fine.
Done. (in bootloader it should now show ENG S-OFF)"
http://forum.xda-developers.com/showthread.php?t=965207

No doubt, still a great find. It's definitely a temp cwm fix, so use as necessary, just be careful and DO NOT unplug your phone while it's flashing!

ClearD said:
No doubt, still a great find. It's definitely a temp cwm fix, so use as necessary, just be careful and DO NOT unplug your phone while it's flashing!
Click to expand...
Click to collapse
For me, it was a permanent CWM fix

Use this at YOUR OWN RISK! I take no responsibility for bricked or ruined phones, I just posted this in hopes it might help out people having CWM issues.
I just put that in my first post, hopefully it will do it's job

I could get into cwm, no black-screen for me though. Still couldnt do radios. Used this and bam new radio....Thanks for the info.

Lol Cali, remind me to "thank" you tomorrow I've been trying all night, but I'm at the 24 hr limit for "thanks". I appreciate the post update, and this really is a great find. I can't stress that enough lol. In the right hands, an engineering HBOOT is great.

btdt13 said:
I could get into cwm, no black-screen for me though. Still couldnt do radios. Used this and bam new radio....Thanks for the info.
Click to expand...
Click to collapse
You are very welcome!

ClearD said:
Lol Cali, remind me to "thank" you tomorrow I've been trying all night, but I'm at the 24 hr limit for "thanks". I appreciate the post update, and this really is a great find. I can't stress that enough lol. In the right hands, an engineering HBOOT is great.
Click to expand...
Click to collapse
No problemo, as the Terminator would say

[Q] How do I flash new radio using ace hack kit

Im running Android Revolution and now I would like to flash the recomended radio. However i do not have eng s off so fastboot flash radio radio.img does not work for me.
After reading the effen manual, what i understand is that to flash a new radio I need to
1. rename the desired radio zip file to rom.zip
2. place it in the romzip folder
3. open hack ace cmd menu and select to install my own radio
Heres where im confused. When I follow the link provided to here the instructions seem to conflict each other.
Ive studied this as much as I can over the past two days but havent found much solid info.
I also tried using visionary b4 I even flashed the AR ROM but it did not work.
Could someone confirm that it is as easy as stated above or if im wrong please help a brother out. I just need to flash the recommended radio and havent found a solution im confident with. Please and Thanks to anyone who can help me out.

I personally go by the instructions from the link you provided. Just rename the zip, put it in the root of.your SD card, and flash via hboot. And that's it.
Sent from my TARDIS using XDA App

no no no
this is how it's done for me, minus the links needed to flash the radio, as they are not mine.
You should also flash the matching RIL file (radio interface layer) that HTC pushed out with this new radio. Here are the steps to do all of this:
Below is a link to my dropbox folder containing the P98IMG.zip file containing the new radio. Download this file to your computer. Now we need to check to make sure the file didn't get corrupted during the download process (extremely slight chance of this happening, but we don't want to flash a corrupt file to your phone and risk bricking it). Download md5.exe from below and run it, and browse to the P98IMG.zip you downloaded. The MD5 hash it displays should match this number exactly:
33BAEBAD8B1E7A20F4603AFF0BA66468
You can paste this number into the MD5 program so you can compare them.
Now that we've verified the file is good, copy this file to the root of your SD card and reboot your phone into bootloader mode. Once you're in the hboot/bootloader screen, select bootloader and wait a few seconds and it will automatically find the .zip file and then prompt you to proceed. This process is what flashes the new radio, it takes about 20 seconds or less. Once it's done, reboot into your ROM like normal. Go into settings>>about phone and check your radio version; it should now show 26.06.06.30.
Now we need to flash the matching RIL file. Download the file below and copy it to your SD card. Don't worry about checking the MD5 hash. Reboot your phone into clockwork recovery mode, and then select install zip from sdcard>>choose zip from sdcard then select the RIL .zip file and flash it. Reboot back into your ROM. We are done! Let me how it works for you. You might give it a few days before making any decisions, it seems like some ROMs need to adjust to new radios/RIL files before the battery life settles down to normal (that is my experience anyway).
credit to HenryBravo

My goal is to flash the radio recommended for AR HD. I did so by moving it to root of sd and hboot. But i dont think it took becasue baseband does not match up. It stayed the same after two tries. I would really like to follow the devs instructions for the radio. However I cant seem to successfuly flash it.

NARRRRRRRRRRR did you even read what i typed?
direct instructions

Dude my bad man. Is this the radio for AR HD...radio 12.54.60.25_26.09.04.11_M2 ? the numbers did not match up. I dont see a link for your dropbox though? I really apologize for being dense if i am and I really appreciate your quick reply and patience. thank you

We are going to need more specifics on what you did. But following wdkingerys instructions are exactly what you need to do
Sent from my TARDIS using XDA App
Sent from my TARDIS using XDA App

What I did was
1.rename the radio 12.54.60.25_26.09.04.11_M2 (radio recommended by dev) to PD98IMG.zip
2.boot into hboot it found it i got the progress bar on the right had side it took about 5 seconds or so
3. Then i went into fastboot to select power down and then i turned it back on

I want to follow your directions but I dont see the dropbox links. Like i said earlier I really appreciate your patience

Ok I checked out the AT hd thread and yes 12.54. Is the recommended radio. Wdkingery mentioned the stock ATT radio. When you check the radio/baseball in about phone what does it say? It should match to what your trying to flash
Sent from my TARDIS using XDA App

Thats what I thought but it doesnt. I went in the IRC (dont remember which) and have gotten a copy of everything wdkingery said and will follow his instructions. It currently says baseband# 12.28b.60.140eP_26.03.02.26
-i think the problem was that the AR HD recommended radio is for a DHD not sure

I've flashed dhd radios, so that shouldn't be the problem. Though in my case the dhd radios were never as good as stock. Again that was me as plenty of others have gotten better results with other radios. It more of a trial an error in my opinion and flashing radio does have its risks so I tend to stay away.
Sent from my TARDIS using XDA App

I think your right, apparently that radio required eng s off and again thank you.
Im now rockin 06.06.30 and about to load the RIL. Will follow up with results

Got the RIL installed and im good to go speedtest.net app shows 3 down 1 up. Not great but im gonna bet thats more to do with the tornados that just came through here. The network has been iffy throughout the city anyways. Also ill follow the advice given to wait a couple days b4 makin any real judgments. Thank you again to both of you guys. I think ive managed to get my head wrapped around this a little better.

Glad I could help . I think I might have figured it out . I downloaded the 12.54 radio and compared it to my stock zip. The AR ZIP does not contain Android Info text file. This is the first time I've ever looked I.side the zip, so.this is new to me. I believe this file is needed in the zip. Somebody correct me if I'm wrong.
So from reading the flashing radio thread. They state to replace the radio images (with the one you want)so the txt file is probably important and hence it not working for you.
You should try out the stock like you said, and see if it works for you. If not I with this new Info, we should be able to get you on 12.54
On a slightly different note. Eng s-off is not needed. And is even riskier than hboot, trays why many devs prefer the hboot method
Sent from my TARDIS using XDA App

Great thank you. I might still want to try 12.54 in the future so ill keep that in mind. I would like to know exactly why one radio is better than the other anyways so for now im happy with this one. I was in the AR HD irc for a while but couldnt get anyone. Ill get to the bottom of it sooner or later. Thanks again

[Q] Quasi-Bricked?

Hello! I'm a long-time lurk and this is my first post. Why? Because you folks at XDA are extremely knowledgeable and very helpful! I actually enjoy reading the forums and usually can find my answer using search. Call me a masochist, I guess. I just wish I had the chops to develop and not just be a continuous noobish sponge. I have successfully rooted my own Inspire with Bubby’s method and have flashed several radios and ROMs, no problem (knock on wood).
Anywho, I have searched and have seen similar issues to mine, but I have what I consider a more unique problem (which, if I’m wrong, I’m sure you fine folks will let me know). I attempted to root my brother’s Inspire over the weekend and it is currently showing a black screen with three vibrations and amber light (If I try to go to Hboot manually, I get five whole vibrations with a green light). I can, though, pull the battery for 5 minutes or so, then the phone will boot normally. Although I think it’s on the downgraded ROM, because it shows the funky AT&T splashscreen instead of HTC. What I did was attempt root with Bubby’s and got stuck at the boot screen when the phone was trying to flash the PD98IMG.zip (downgrade I believe) after making the goldcard. It would show that it was trying to read the zip, however I never would get the “volume up to upgrade” option. I tried this three times. When that failed, I tried rooting with the Ace Hack Kit and after creating the goldcard image, when the script tried to reboot the phone to install the downgrade, I got the black screen, amber light with the 3 vibrations. My problem is that I don’t have root, can’t get to recovery from the Hboot screen (shows red exclamation with triangle) and was unable to install Clockworks Mod thru ROM manager because I’m not rooted, so no SuperUser privileges.
What can I do at this point? Maybe off base, but I believe I have somehow corrupted the boot partition or the like, including screwing up Hboot. Is it possible to fix this if I am not able to reboot without pulling the battery? I have tried going thru Bubby’s and the Ace kit again, but always fail when the phone reboots.
Thanks for your help!

I am far from an expert, or even a novice, but to me it sounds like you have a corrupted download for the bubbys one click.... Have you checked the Md5 on the downloaded file?
Sent from my Inspire 4G using XDA App

I could lie and say yes, but no I didn't check md5 the first go around (although I did the 2nd time I reinstalled, after it screwed up). I did have all antivirus programs uninstalled and firewall turned off.

It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk

@OP:
Follow the files and instructions in this post to get back to stock so u can start fresh. I followed these to get back to stock only today evening, and it worked.
--------------------
TO RETURN TO STOCK:
Make sure you S-ON (if able) BEFORE you Unroot. The S-On tool needs root permissions to function.
--------------------
Turn the phone on, connect to computer, and perform step 1. Make sure USB debugging is enabled.
Step 1 (S-On):
Run Bubby323's S-On tool: S-On Tool
Step 2 (STOCK ROM in ZIP FORMAT):
Place this .zip file on the root of your SD card. Disable fast boot in settings > applications. Turn off your phone. Hold down the volume down button and the power button at the same time. The phone will reboot into hboot. It will load the ROM automatically. Follow the steps to flash the ROM.
http://www.multiupload.com/JELMZNSKDF
I did this like a couple hours back, and mine's back to stock.
Note: I consolidated the links here from various posts on this forum.

Diablo: Was posting the reply below, when I saw your message. Would you still recommend I follow your steps to unroot, return to stock and run hack again?
Update: Well, I went thru Bubby’s root process again and was able to get the phone rooted (had to pull battery and wait 4 minutes when it needed to reboot). And I have confirmed root was successful. I also used Bubby’s fix to Eng S-Off (couldn’t hurt, right?). The phone now has the latest Android Revolution with Sense and the radio has been flashed (including full wipe and EXT4 wipe). However, it STILL won’t reboot correctly. I can boot directly into Clockwork from ROM Manager, but if I try to reboot normally (hold down power button and select restart), I get the black screen, amber light and 3 vibrations. Again, pull battery and wait 4 minutes and either power button to boot normally or power and volume down to get to Hboot works fine and goes to Clockwork from Hboot fine also. I guess I can keep up with the batter pull only when I have to manually restart, but WTH? There has got to be a fix for the reboot issue. Any ideas?

fernandezhjr said:
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.

ogarlen said:
...I also used Bubby's fix to Eng S-Off (couldn't hurt, right?)...
Click to expand...
Click to collapse
Well, actually, wrong, it could hurt. I'm not saying that's the cause of your problems, but you really should've read up a little more before clicking on stuff so nonchalantly.
Eng s-Off means the engineering bootloader. If that process were to fail while in the midst of performing it on your phone, it would most likely hard-brick it.
Not to mention it's unnecessary. It was only included in that rooting method at the time for flashing radios, I believe, and since then a safer method for doing so has come into standard usage that doesn't require eng s-Off.
It's also one method of resolving the cwr blackscreen people were having, where you're actually in cwr, but the screen is black so you can't see what your doing. Not the same black screen your seeing, I don't think, because you're able to at least get into cwr.

ogarlen said:
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
Click to expand...
Click to collapse
The vibrations with the blinking led, I have seen a few posts with this. Sadly, I haven't seen anyone post a fix yet.
Sent from my Desire HD using Tapatalk

Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.

ogarlen said:
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
Click to expand...
Click to collapse
Heh. Now that you explain it, I can see the sarcasm. I'm usually good a picking up on it, but you know how these internet textual posts go....smilies are crucial...
As to your problem, there seem to be a few posts in recent days describing the led/vibrations type of symptom.
I don't know if they're interrelated or not. I don't have an answer, but I'm curious and will drop in if I manage to come across any pertinent information.

Thanks for the replies! I will continue to research and update this thread if I find a solution. I really believe that it has something to do with the startup processes or boot cache or some other $10 phrase related to what happens when the phone is attempting to startup normally. I appreciate all help.
Sent from my Inspire 4G using XDA App

Just wanted to add a quick update for anyone searching that comes across this post: The phone in question is now working flawlessly (knock on wood). Restarting, power down and battery pulls work with no problems (no vibrations or flashes). I am honestly unsure what I did to cause this error or what the resolution was and can only speculate. Since my last post, I have made a Nandroid backup and flashed a couple ROMs (namely AR with Sense, then Virtuous Unity with full wipes in between), so I assume that somewhere in there the corrupted boot files (or whatever) were corrected. All's well that ends well...

Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.

Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.

seems like you got yourself a good taste of rom flashing issues. that's a good thing. i know that you have everything working flawlessly now, BUT i would still HIGHLY recommend that you download the Super Wipe script from the Android revolution thread and use that to completely wipe and format your partitions, then do a FULL wipe through clockwork and then install whatever ROM you would like. but i cant stress enough, MAKE SURE that the Md5 sums match always. this can be the difference between a working rom and a bricked phone. also i would like to add that through my experience i usually find that the first time you root the inspire, the very first rom you install on it almost always has issues. that's how it is for me atleast. Ive rooted plenty of Inspire's and all of them have had some sort of issue on the first flash. and as always, follow the directions per rom to the T or else it might not work.
P.S. Some roms run better with matching Radio and RIL. flashing these is AWLAYS good practice to get your phone to tunr the best possible.

Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
Thats why I posted the full steps in the guide , to s-on and ruu back to stock. On a side note bubbies s-on tool does not always work.
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.

mudknot2005 said:
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
Click to expand...
Click to collapse
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.

Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
You are correct. I should have re phrased that differently. I know that S-Off would survive the RUU procedure so I should have said "almost out of the box". The RUU is still a very handy thing to have.

Gene Poole said:
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Click to expand...
Click to collapse
Please, sir.
Seriously, this would be, imo, a profound contribution to this phone.

[Resolved] [Q] HTC Desire Stuck in Fastboot - Noob!

I know its been asked plenty of times before, but everything I found either didn't work or I didn't understand...
So before I start, I'll apologize ahead of time for any annoyance or stupid questions, cause I'm gonna need some explanations.
I'm on an HTC Desire (U.S. Cellular) rooted and S-Off. Earlier today it was working fine. I went to restore a ROM backup through ROM Manager that I had and everything was going ok. ClockworkMod Recovery started to install the backup, but after a couple seconds it looked like it froze. I waited a while and I proceeded to do a battery pull (I've actually had to do this many other times when installing roms, and I never had problems). Right as I took the battery out I saw the Desire's screen, and it was just starting to continue the installation as I pulled the battery.
No problem, I thought. But when I went to reboot my phone, it took me directly into Fastboot. So I pulled the battery again, and the same thing happened. I cleared my storage with no luck. And after searching countless threads (like I said before), I either don't entirely understand what people are suggesting or their suggestions aren't working.
That's when I decided to join XDA to get a personalized answer. Can anyone help me with this in a (very) explained/easy to understand way?
I don't know if it will help, but here's what the HBOOT menu says at the top:
-Revolutionary-
BRAVOC DVT2 SHIP S-OFF
HBOOT-6.06.1002
MICROP-051e
TOUCH PANEL-SYNT0101
RADIO-2.15.00.11.16
Thanks in advance!

You need to find a .zip of the current ROM you're running and install it from ClockWorkMod recovery (if you can access it and have it installed). Seeing as you can still access Fastboot, all hope is not lost just yet
As much as everyone likes making backups, they really introduce a lot more problems and quirks than they're worth A clean flash each time, while more work, produces better, cleaner results. A lot of the issues people see relating to flashing and bugs have more to do with restoring their app/system backups than the actual ROM itself!
Failing that, you'll need a stock US Cellular RUU (ROM Update Utility) from HTC to return the unit - including recovery, bootloader and radio (you'll lose S-OFF too) - completely to stock. Extreme, but often when you find yourself stuck outside the OS it's better to go back and start from scratch
If there's anything else you need let me know!
Good luck!

juzz86 said:
You need to find a .zip of the current ROM you're running and install it from ClockWorkMod recovery (if you can access it and have it installed). Seeing as you can still access Fastboot, all hope is not lost just yet
As much as everyone likes making backups, they really introduce a lot more problems and quirks than they're worth A clean flash each time, while more work, produces better, cleaner results. A lot of the issues people see relating to flashing and bugs have more to do with restoring their app/system backups than the actual ROM itself!
Failing that, you'll need a stock US Cellular RUU (ROM Update Utility) from HTC to return the unit - including recovery, bootloader and radio (you'll lose S-OFF too) - completely to stock. Extreme, but often when you find yourself stuck outside the OS it's better to go back and start from scratch
If there's anything else you need let me know!
Good luck!
Click to expand...
Click to collapse
As far as the first method, I just drop it into my SD card on my computer correct? Under computer is D: Recovery (I'm on Windows). Would I drop it in there or in the Recovery folder within it?
Also, when I'm in CWM Recovery and I select any of the options, the ROM Manager icon pops up (its normally just a watermark). This has been a common problem for me, I don't know if I'm doing anything wrong.
I'll work on the USCC RUU as well, at this point I really don't mind if I lose everything as long as I get it working again!
Thanks for the help!

AndrewPR52 said:
As far as the first method, I just drop it into my SD card on my computer correct? Under computer is D: Recovery (I'm on Windows). Would I drop it in there or in the Recovery folder within it?
Also, when I'm in CWM Recovery and I select any of the options, the ROM Manager icon pops up (its normally just a watermark). This has been a common problem for me, I don't know if I'm doing anything wrong.
I'll work on the USCC RUU as well, at this point I really don't mind if I lose everything as long as I get it working again!
Thanks for the help!
Click to expand...
Click to collapse
Yep, grab the .zip and put the SD card in a reader. Once it shows, just paste it onto the card (root directory, not in any folders). Then boot into CWM and 'flash zip from SD', 'choose zip file' and flash away.
I wouldn't stress about the icon popping up, as long as the recovery is doing what you're telling it to
My most recommended option is the RUU. It'll sort out all your quirks, it just takes a little while to get everything back the way you like it. The benefits are there, though
---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------
This thread will help you a lot. There's USCC RUUs in there!

juzz86 said:
Yep, grab the .zip and put the SD card in a reader. Once it shows, just paste it onto the card (root directory, not in any folders). Then boot into CWM and 'flash zip from SD', 'choose zip file' and flash away.
I wouldn't stress about the icon popping up, as long as the recovery is doing what you're telling it to
My most recommended option is the RUU. It'll sort out all your quirks, it just takes a little while to get everything back the way you like it. The benefits are there, though
---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------
This thread will help you a lot. There's USCC RUUs in there!
Click to expand...
Click to collapse
Ok, I'm downloading the stock 2.2 RUU now (hopefully that's the right one?). As far as CWM Recovery, the icon pops up and that's all that's on the screen, until I press the power button again and it brings me back to the menu. None of the actions work at all.
Anyway, I'm hoping this RUU works. There aren't any other pre-requisites that I need for this, are there? I just download it, run it, and bam?

AndrewPR52 said:
Ok, I'm downloading the stock 2.2 RUU now (hopefully that's the right one?). As far as CWM Recovery, the icon pops up and that's all that's on the screen, until I press the power button again and it brings me back to the menu. None of the actions work at all.
Anyway, I'm hoping this RUU works. There aren't any other pre-requisites that I need for this, are there? I just download it, run it, and bam?
Click to expand...
Click to collapse
Sounds like your recovery's corrupt or something, too.
Nah just stick the phone in fastboot, connect, install drivers (if necessary) and run the RUU. It should fix everything else for you

juzz86 said:
Sounds like your recovery's corrupt or something, too.
Nah just stick the phone in fastboot, connect, install drivers (if necessary) and run the RUU. It should fix everything else for you
Click to expand...
Click to collapse
Yes!! Everything went well, I thought I was doomed! Haha thanks for your help

AndrewPR52 said:
Yes!! Everything went well, I thought I was doomed! Haha thanks for your help
Click to expand...
Click to collapse
Anytime mate. Thanks for posting in the correct section and being specific in your opening post, it helps a lot. Make sure you mark your thread as 'resolved' so others can learn from you
Take care, hope to see you around the forums more!