yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] zikronix:
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
[Hero CDMA Android Development] fred43:
Thanks!

this saved my phone. I was about to throw it away.
[Hero CDMA Android Development] nemesys504:
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.
[Hero CDMA Android Development] thecodemonk:
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")
[Hero CDMA Android Development] frazmanw:
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
[Hero CDMA Android Development] Mistamike17:
I would certainly recommend that people stop using this until someone figures out what is wrong with this utility. Why people are still using it is beyond me.
[Hero CDMA Android Development] troyboytn:
Another legit reason to not RUU just for the update is that you will loose root (could be permanently). If you want to keep root and still use the new "official" Sprint rom coming soon, just wait...as it will be ported by the great devs here and you will be able to flash it just as any other rom.
[Hero CDMA Android Development] Clipt:
wow this is horrible, I was on Fresh 1.1 and I tried to go to the new damage rom. once i updated i was hit with a bunch of FC's so i decided to RUU back to stock but then i was hit with the 110 error.

my phone wouldn't boot at all! I have it a couple of hours to rest and I tried again. When I kept trying it finally went through and I was back at stock, but now my root wasn't going through. I was trying to root via windows but no luck, so I went and tried on osx. It went through but it didn't want to flash recover 1.5.2.. so i tried the next best thing. 1.5.1.

the 1.5.1 worked great and once i was in nandroid i restored an image i made the day before. I hope you guys can get it sorted out! good luck don't lose hope
[Hero CDMA Android Development] looneylu:
This hasn't happened to me, but I am starting to believe that everyone having trouble ruuing is because they've tried ruuing from a 2.1 rom... I may be wrong, but the one time I RUU'ed I did it from a 1.5 rom and it worked no problems... Have any of you had this issue RUUing from a 1.5?
[Hero CDMA Android Development] Clipt:
I definitely think this is a 2.1 issue. I've ruu from 1.5 with no issues in the past but when i tried to come back from a 2.1 roms i was hit with that 110 error. I'm just glad I got my phone working again
[Hero CDMA Android Development] looneylu:
anymore confirmations???? This is good information to know
[Hero CDMA Android Development] sinistermeshes:
Assuming fhe issue is 2.1 to stock simy isnt going to work; in theory, could we flash a 1.5 rom, then ruu?

Assuming THAT works, what of the new radio? Ive read threads where people have bricked phones from new radio to ruu. On a sidenote not related to ruu, is it possible to dkwngrade the radio? From what I understand, sprint has uldated the prl a couple times since 2.1 has been leaked into the community. All THAT aside, id like the old radio back, and was curious if there is a surefire way to downgrade?

Only had to ruu once, before 2.1 was leamed. Scared to do it now :-0
[Hero CDMA Android Development] tyrnight:
Yes.. flash a 1.5 based rom (fressh) after wiping. once you have rebooted into the 1.5 rom, you can run the RUU without issue..

I have done this many times..

If you have updated your radio.. dont worry about it.. 1.5 works fine with the updated radio..(but dont downgrade it, thats where the bricking happens if not careful)
[Hero CDMA Android Development] sinistermeshes:
So that leaves the question; am I stuck with the new radio? I cant truely unroot my phone RUU-wise unless the radio is stock also, correct?
[Hero CDMA Android Development] tyrnight:
I would check that thread on the radio for more information....

http://xdaforums.com/showthread.php?t=643796&page=18

some one said they managed to get back to original
[Hero CDMA Android Development] aaron130:
Ive also RUU'd from 1.5 a few times now with NO PROBLEMS at all! I was running Damage and nand restored back to 1.5 before i RUU'd and had no prblem and i just did this yesterday!
[Hero CDMA Android Development] looneylu:
This should probably be stickied so everyone knows and no more people get nice paperweights!
[Hero CDMA Android Development] wtphoto:
so far I have RUU'd three times straight from DC 1.0 and no problems.
[Hero CDMA Android Development] looneylu:
so much for that theory...
[Hero CDMA Android Development] looneylu:
has anyone bricked ruuing from 1.5? or have the cases been going from 2.1?
[Hero CDMA Android Development] wtphoto:
lol sorry bout that. I think it has more to do with either past setup of maybe when the phone was purchased. I got the one that I have now.
[Hero CDMA Android Development] smw6180:
Yep. Mine did.
[Hero CDMA Android Development] robchaos:
Has anyone that had successfully RUU'd before end up with a brick on subsequent RUU's or has every brick been on first time RUU's?
[Hero CDMA Android Development] smw6180:
Mine was a first (and ONLY) time.

Edit: I haven't tried it since.
[Hero CDMA Android Development] robchaos:
there has to be something common to the bricked devices. I see in the log for my succesfull RUU, the utility connects in ADB mode first to check battery status and push files to /data/data/dmdata, then run ADB SHELL PPST.

What is PPST? Doesn't that have to do with the PRI and PRL? Could this error have been caused by something as simple as the phone not being recognized as connected by adb when the RUU is started? I've had many instances where I've plugged in my phone and it wasn't recognized by ADB devices, I have to start up HTC sync from the phone then shut it off immediately then it is recognized when I type ADB devices.
[Hero CDMA Android Development] Darii:
Mine is a sprint hero (with google) that came with the latest 1.5. I rooted and moved it up to the damage control 2.1. Everything was fine.

Decided to go back to the original stock so as not to interfere with upcoming updates and a few things that worked better in stock release. I got the 110 error and checked the log and it appears to be strictly related to ADB not recognizing the phone.

I had attempted the ruu from home. I had never used ADB on my home computer before so I get the feeling it is a driver issue. All work I had done on the phone I had done on my work computer. I know ADB connected to it just fine there. However, it is no longer possible to do that from work anymore since it constantly boots to the fastboot and shows RUU in the dialogue.

Unless I can figure out a way to force the driver and make ADB see it in it's current state, it is bricked and I'll most likely have to pay for it as it's obviously my fault due to the way it is booting now.

Anyway...that's my "two cents". Best guess is the driver issue. If I'd done it at work instead of home from the beginning, it would probably be just fine.
[Hero CDMA Android Development] wtphoto:
ok so here is a question that I have not seen asked before how did you guys that bricked root? did you use the one step method, the fresh kitchen, or did you go the long way and go through the guide that theresthatguy wrote up? im wondering if it doesnt have something to do with that but more specificaly as was stated the drivers not being present. to do it the long way you have to have the drivers and thats the only way I have done it. if you did it another way without having to install sdk and all the proper drivers then perhaps that is where the problem lies.
[Hero CDMA Android Development] Darii:
I rooted using the flashrec method found @ http://xdaforums.com/showthread.php?t=584029
[Hero CDMA Android Development] wtphoto:
ok so there is one, the more I think about it the more I really belive that this is the problem.
[Hero CDMA Android Development] looneylu:
Hopefully we will get to the bottom of this... I really want to know because

I plan on selling my hero and getting one of the new devices, but I need to make sure whoever buys it will have no problem activating it...
[Hero CDMA Android Development] smw6180:
I used the long method, didn't use Flipz, or Flashrec...

As far as RUUing from your work vs home computer, it wouldn't have mattered. If the RUU is going to fail, it's not going to fail because you did/did not have ADB installed. I did mine with fully functional ADB and it bricked anyhow.
[Hero CDMA Android Development] looneylu:
hmm... there has to be a common factor though
[Hero CDMA Android Development] smw6180:
Probably so. But I haven't seen one yet. As far as I can tell it's random (which doesn't mean it IS random, it just means no one has found a common denominator yet. I personally am blaming sunspots)
[Hero CDMA Android Development] Darii:
OK. I went back and double checked my ruu logs. The first time I tried it the adb accessed the phone just fine until the phone rebooted. After the phone rebooted to do the actual flash is when the adb function stopped working properly. Once the progress bar on the phone gets to about 50%, a triangle with an exclamation point appears at the end of the bar. Right then you know that it's bricked. The phone after that, if plugged into the computer, stays on the HTC screen. If you unplug it from the computer it goes to what appears to be a boot loader screen which has some general info for the phone and the letters RUU in what appears to be a dialogue box further down. Now, no matter what, the phone no longer triggers the proper drivers in the windows operating system. It loads a USB driver under android phones named MY HTC. I successfully got it to load one other driver properly from the SDK but it still will not get adb access after that,... only fastboot access is allowed.

On a side note, I took my 1 1/2 month old phone to the sprint store to see if they could repair it. They told me that the screen was dead. Thank goodness for either lazy or stupid (or possibly just overly kind) technicians. :) replacement under warranty on the way.
[Hero CDMA Android Development] litlebuddie:
I am so frustrated with this issue...there is no solution out there, and if there is anything that I hate it's not being able to fix something lol. Luckily my sprint store "couldn't fix it" either...so they are ordering me another...will be here on Tuesday lol. Hopefully we will have a fix for this soon, because without being able to go back to stock, a lot of us won't root.
[Hero CDMA Android Development] alexj81:
(110) i ran ruu hero 1.56.65 on a stock hero to down grade it to root yeah bunk info now its just blank screen with a red RUU in a cmd looking area. HTC comes up on the screen with usb. i
[Hero CDMA Android Development] riddlebox1980:
is there anyway to flash this from linux? I cannot get it to work with wine, or virtualbox?
[Hero CDMA Android Development] BigBallin:
im trying to run this via parallels but the ruu isnt finding the phone. i click connect via virtual machine but it wont reconize it. is there a place for me to download the drivers for windows?
[Hero CDMA Android Development] rrr571:
If anyone has had an unrootable phone after this RUU, I need help. My Hero went from Fresh1.1 to unrootable after this.
[Hero CDMA Android Development] grandpasghost:
Please use with CAUTION - this is semi-bricking some phones.

Many people on this board have had bad results from using this RUU. The phone will boot to a semi bricked -blank screen state. I'm assuming this doesnt happen to everyone, or else this forum would take down this likely corrupt file/

this crippling update has caused a lot of grief and luckily users have helped out on this post on how to fix the problem.

xdaforums.com/showthread.php?t=645002

xdaforums.com/showthread.php?p=6013654

(dont have the authority to post real links yet )
[Hero CDMA Android Development] thatguythatdid:
I would welcome a semi bricked phone right now just to take it back to radio shack and get a replacement for "software" damages
[Hero CDMA Android Development] menzo44:
I am looking to use this to UN ROOT my phone and go back to factory so I will be ready for the official sprint 2.1 update that is on its way ;) Can someone tell me if this is still working and a good way to do so? I am on a 2.1 ROM right now but plan on using my nandroid back up that I made when I rooted (the stock 1.56) then flashing this ruu after that? Is this the smartest thing to do?
[Hero CDMA Android Development] rt1oo:
easier: http://xdaforums.com/showthread.php?p=6070797#post6070797
[Hero CDMA Android Development] menzo44:
thankyou!!:D
[Hero CDMA Android Development] Zexter:
Very glad to see this is still around. Though the site used for the upload is horrifically slow :-P
[Hero CDMA Android Development] bairds1:
This RUU worked great today! Thanks Flipz!

I just ran it today and everything went through fine without a hang up :D

Here's some info on my phone:

-I was running Fresh 2.3.3 w/ 1.6.3 recovery

-Windows XP SP3

-I've only used Fresh's ROMs and never tried a radio update

Let me know if you have any questions!

Thanks!

Stephen
[Hero CDMA Android Development] Jaimemex:
Link is broken! Could U Plz Fix it!
[Hero CDMA Android Development] Tibson:
This RUU is obsolete, no reason to fix the link.
[Hero CDMA Android Development] vidaljs:
use this instead... its easier and faster

http://xdaforums.com/showthread.php?t=804692

good luck
[Hero CDMA Android Development] obelisk79:
did you try the 1.29 ruu also? just curious.
[Hero CDMA Android Development] frazmanw:
yes Same problem. Other than not being able to run RUU everything everything else works on my phone and on others.... weird. Same problem with 2 windows 7 64bit computers
[Hero CDMA Android Development] david279:
try these...

http://handheld.softpedia.com/get/Drivers/HTC-Hero-Drivers-81097.shtml

helped me with windows 7
[Hero CDMA Android Development] nemesys504:
Tried everything I could.

I did try to run it as administrator, disabled my firewall, disabled USB debugging. Nothing worked. I have the right drivers installed. Cant understand why I cant get it to run.
[Hero CDMA Android Development] thedudejdog:
Iy

Have you tried bootloader?
[Hero CDMA Android Development] flipzmode:
^^ what he said. start it from bootloader.
[Hero CDMA Android Development] shawn_diggidy:
Worked perfectly for me. No problems whatsoever and a completely fresh rom for me. Thanks!
[Hero CDMA Android Development] oxeneers:
I used this and it changed my MEDI DEC # and when I went to ESN swap it, I used the ESN from the Box and then it wouldn't activate the phone until I realized the RUU reset the MEID DEC #. Is this normal?
[Hero CDMA Android Development] travo1:
That should not be normal... I worked for sprint for 5 years and I had never seen anything change the DEC outside of insurance phones coming out in pairs of the same dec...
[Hero CDMA Android Development] oxeneers:
Yeah, mine straight up changed, so when I went to activate the ESN off the box, the phone wouldn't even activate any cell/text service which normally is activated instantly. I know data takes a while, but it was weird.

So anyways, what I did was go ##786# and find the MEID DEC that the phone displayed (what the new one was) which was completely different... went and activated that new ESN and then it gave me a working master subsidy lock number that I could reset the data services with.

What a weird, weird day.
[Hero CDMA Android Development] zippy-man:
Ok so i am having a huge problem here i cannot RUU my phone. I have tried it on windows 7 by running as admin. i have re installed the htc sync and the SDK i have used the 1.29 ruu and 1.56

i am also trying it on another computer running windows xp and it still will not detect the phone.

i can run a cmd line and it will detect the phone so i know windows can see it but the RUU just will not pick up the phone.

I have tried running it from bootloader on both computers and it is a no go any idea's

I really need to RUU the phone and i cannot get it running.

-James
[Hero CDMA Android Development] theresthatguy:
Try to RUU from fast boot mode. I had some weird issue and that was the only way I could do it.
[Hero CDMA Android Development] linkinx64:
Enable USB debugging :D
[Hero CDMA Android Development] realmrealm:
for the people with the USB issue...

for some of the people that are getting the USB error, I found that it was because you don't have the driver installed for your phone.

the easiest way (in my opinion) to do this is to install the HTC sync program found here:

http://www.htc.com/us/support/hero-sprint/downloads/

Please be patient with the installation, it takes a long time on some computers, and appears to freeze, just give it time (it took almost 10 minutes on Vista for one machine I installed it on)

After installation run RUU again, and all should be well.

Good luck!

:)

-AndyS-
[Hero CDMA Android Development] realmrealm:
oh yeah....

For some of the people running into problems with Windows 7 you may want to try:

1. Right-click on the executable file "ARUWizard.exe" and then go to "properties"

2. I believe there is a tab called "Compatibility" or something, click on it.

3. there should be a place for you to click next to a "run this program in compatibility mode" put a check there

4. below that there should be a drop down box, try choosing "Windows XP SP3" (or something similar to that)

5. near the bottom should be a place to check "run as administrator" check that.

6. click "ok" and then try running the program again.

I'm in front of a windows xp computer right now, not windows 7, so excuse me if i don't remember the options correctly, but I should be pretty close.

I also don't even know if this will work, but it's definitely worth a shot.

-AndyS-
[Hero CDMA Android Development] flipzmode:
I'm on Windows 7 64 bit and haven't had any issues. The likely explanation is the one mentioned above... that you guys are missing the adb driver. The RUU reboots the phone in to fast boot. There are two reasons that process will fail:

1) Your phone just reboots and loads right back in to the OS. If that happens then just close the RUU and run it again. If it happens again then you need to start with your phone in fast boot by doing it manually (with it powered off hold volume down, then hit power. When you get the hboot screen hit volume up)

2) Your phone is rebooting in to fast boot just fine (or you put it there) but the RUU still gives you a USB error... you are probably missing the adb driver. Check device manager on your computer when your phone is in fastboot and plugged in and I'd be willing to bet you're missing the driver. Get it from htc sync as mentioned earlier.
[Hero CDMA Android Development] crunchybutternut:
It's pretty odd actually.. I have used the RUU 1.56.651.2 on my phone without a problem before, but it no longer works.

I still receive the "ERROR [170]: USB..." message even though all drivers are installed (same computer I used before) for the phone (fastboot and otherwise).

I even attempted realmrealm's suggestion of XP Compatibility mode. Guess I'll try another computer after work and see what happens.
[Hero CDMA Android Development] flipzmode:
For those of you having problems, please post your last RUU log. Should be in c:\ruu_log\ . Put them on pastebin.com if they are long.

Directly from the RUU's readme

Having the error log will help figure out where the problem is.
[Hero CDMA Android Development] crunchybutternut:
RUU Log.

Here it is:

Hope that isn't too long. :confused:
[Hero CDMA Android Development] flipzmode:
So you can see over and over:

I assume that everyone else with this error will see the same thing. The RUU is checking in adb and fastboot and not seeing your phone. It tries the command "adb devices" and "fastboot devices" about 10 times and then it just fails because it can't find it.

Possible resolutions would be:

1) Putting it in to fast boot and trying it again. Check your error log if it fails and seeing if it identified your phone this time.

2) Open a command prompt and "cd" to the folder where your \sdk\tools\ folder and type in "adb devices" and hit enter and see if it sees your phone. If not then that's your problem. If it DOES see your phone then enter the following command

3) adb shell reboot oem-78 -- that will reboot your phone in to RUU-ready fastboot. If you had the RUU still open then close it. Then open it and try running again.
[Hero CDMA Android Development] crunchybutternut:
adb devices shows my phone, so I ran the adb shell reboot-78 command. My phone rebooted, but sat on the htc screen for over 10 minutes. I figured this must be what the RUU-ready fastboot looked like so I ran the RUU. Still no dice.

Edit: I unplugged the USB cable and the RUU Fastboot screen showed up. I plugged it back in and it went back to htc. Same response on each plug/unplug.

I also ran adb devices while it was plugged in after RUU-ready command and it's not detected.
[Hero CDMA Android Development] flipzmode:
Yea, it will sit on the HTC screen. Try this:

adb shell reboot-78

Once you are there and sitting on the HTC screen, go back to your command prompt and type:

fastboot devices

Does it show your phone?
[Hero CDMA Android Development] crunchybutternut:
Yeah, that displays my phone, but I am still getting the repetitive RUU log as before.
[Hero CDMA Android Development] crunchybutternut:
Just had a thought.. after updating my HTC Sync software the adb included with my RUU might be out of date. I copied adb.exe, AdbWinApi.dll and fastboot.exe from C:\AndroidSDK\Tools and overwrote the files in the RUU folder. Then I ran it without a hitch.. weird, eh?
[Hero CDMA Android Development] nemesys504:
Replaced the files you mentioned and the RUU worked flawless. Thanks for the info.

EDIT: Still cant enter bootloader.
[Hero CDMA Android Development] kanyewest:
how come when i double click ARUWizard.exe nothing happens?
[Hero CDMA Android Development] zippy-man:
Thanks that got it working perfect for me
[Hero CDMA Android Development] SPIK3:
I followed those steps but still nothing, then I uninstalled HTC sync and it worked.
[Hero CDMA Android Development] simplicity baby:
Thank you! I was getting irked from those USB error messges, then I tried this (uninstalling HTC Sync) and wouldn't you know...the thing worked. Go figure. :o
[Hero CDMA Android Development] aaron130:
I got a question. Ive "unrooted" and used the old RUU I think 1.29 because I have one of the 1st phones (with google) and after running the RUU I would just run the update that Sprint had to fix the 100% awake time. If I just run this RUU that would mean i wouldnt have to even run the update correct? Or can I not even use this RUU cuz mines came with the 1.29?
[Hero CDMA Android Development] flipzmode:
Correct, if you use this RUU instead then it will not only already have the MR in it but it fixes the rev0/revA typo in the phone. Just know that you won't be able to use the 1.29 RUU anymore, but there is no reason that should be a problem.
[Hero CDMA Android Development] david279:
This fixes the rev o/rev a problem?
[Hero CDMA Android Development] flipzmode:
Sure does.
[Hero CDMA Android Development] leenypost:
Sorry if this is a dumb question but...

Is this RUU an official Sprint release? I used this to upgrade a phone I just purchased from 1.29 to 1.56.... When 2.1 becomes available will my phone be able to just get it OTA or do I need to somehow get the phone back to official Sprint settings in order for me to connect to the firmware update check on the phone?

Is there any difference at all between this and say having 1.29 and completing an OTA update to 1.56? or is just flashing this RUU giving me an exact identical product?