yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] seaweedopm:
That made no difference although this time I ripped the phone off the USB cable before pressing exit on the RUU installer. It jumped to the fastboot screen and this time had additional information in the second (larger) text box.

Parsing...[downloaded ZIP]
[1] BOOT - OK
[2] BOOTLOADER - OK
[3] RADIO_V2 - FAIL-PU
[4] RECOVERY - OK
[5] SPLASH1 - OK
[6] SYSTEM - OK
[7] USERDATA - OK
Partition update fail!
Update Fail!

Andrew, I got this phone last week off craigslist. I was planning on going to the sprint store, if I absolutely have to, and saying that the phone was working but I found it off. When I turn it on, it has a black back-lit display. Is this similar to what you said? I had them switch my service to my Mighty Mouse TP2 last night but made sure they documented that I intended to repair my Hero.
[Hero CDMA Android Development] KBizzle:
Try formatting with swap at 0.
[Hero CDMA Android Development] andrewl2020:
Similar I told them I tried the ## codes they told me to do, nothin worked. I turned it off, and it wouldn't turn on next day.

I blamed them for the brick lol.
[Hero CDMA Android Development] andrewl2020:
If I do one click method instead, will I be able to get the 2.o upgrade

It just seems a lot easier to do that method,

Less steps=less chances of messing up right?

Thanks
[Hero CDMA Android Development] KBizzle:
Personally, I dont trust the one click method. I found I can root my phone in under 10 min manually. I have helped two people root manually without issues. I tried fresh's auto root but I was on a windows 7 machine and it didnt work. Just my .02.
[Hero CDMA Android Development] Kcarpenter:
You shouldn't update when sprint releases it. You won't have root after that - more than likely a long while after that until someone comes up with a new root method. And if it's anything like the Eris, you may never get it.

Edit:

Have you guys tried using the old RUU?
[Hero CDMA Android Development] turboek99:
HTC HERO stuck on htc logo too

mine is doing the same thing it shows 90% complete then shows missing/open file and i unplug it before it closes and i get:

Parsing...[downloaded ZIP]

[1] BOOT - OK

.[2] BOOTLOADER - OK

[3] RADIO_V2 - FAIL-PU

[4] RECOVERY - OK

[5] SPLASH1 - OK

[6] SYSTEM - OK

[7] USERDATA - OK

Partition update fail!

Update Fail!

if i unplug it after i close the ruu it shows a diffrent screen hboot some say

is there anyone that can help me with this, i work at sprint and can help someone with some certain issues(no free hero's,sorry), i have rooted before and installed ruu and stuff but this one is like missing files or something. imma try on a xp PC. but thanks on any input my email address is turboek99@hotmail.com, TIA
[Hero CDMA Android Development] wtphoto:
just wondering but could this have anything to do with the last PRL update? did you guys even do the PRL update? im mean it may have nothing to do with it but just thinking out loud here.
[Hero CDMA Android Development] andrewl2020:
or maybe the ones claiming it works, could upload their version?

just incase the source dl files are corrupted....

or replace the radio.img in the rom folder in the ruu....

i dont know, but at this point its worth a try right?
[Hero CDMA Android Development] seaweedopm:
Yeah, at this point I'd install something from a porn site.
[Hero CDMA Android Development] wtphoto:
I would upload it but even just the radio image in a zip is too big. shoot me a pm with your email and I can send it to you though.
[Hero CDMA Android Development] barkerja:
I'm a Mac user and have one Windows laptop here and for some reason I can't get the drivers installed.. specifically the adb one. It continuously fails saying something about "My HTC".

I have tried everything possible.... uninstalled HTC Sync, restarted, reinstalled HTC Sync, downloaded drivers I found with others having the same issue, I'm running out of ideas...

And this problem is preventing the RUU from seeing my phone, which really sucks because I need to unroot or something as one of the roms I've previously installed has altered my kernel causing some issues.
[Hero CDMA Android Development] wtphoto:
please try the search next time this has been covered several times. you need to copy the adb.exe, fastboot.exe and adbwinapi.dll from your sdk file into the RUU file it has something to do with those files in the RUU being our of date.
[Hero CDMA Android Development] barkerja:
I have been "searching" now for over 3 hours (literally).. it's difficult to find what you're looking for when you're unclear on exactly what you need or are looking for.

In any case, I recall this working once before (as I used flipz kitchen) but HTC Sync was recently upgraded to 2.0.8, is there a known problem with Vista with it?
[Hero CDMA Android Development] wtphoto:
as far as I know there arent any problems in vista this is normaly a problem with windows 7 I have a vista box and a 7 box and the ruu worked just fine on my vista box but had to do what I posted above to get it to work on 7 but try it and see if it works.
[Hero CDMA Android Development] barkerja:
Well my problem is beyond the RUU.. I can't even get HTC Sync to recognize the phone. Under device manager the adb is showing as not being properly installed. Everytime I try to reinstall the driver is when I get the error which is pretty vague, just returns "HTC Sync"
[Hero CDMA Android Development] wtphoto:
wish I knew more about macs but I have seen before that instead of un-installing and reinstalling connect the phone to comp go ito device manager and find the device and choose the update driver option let it auto update and it should work. hopw you can translate that mac speak lol.
[Hero CDMA Android Development] barkerja:
Btw, this is the error I am encountering: www[dot]grab[dot]by/2wH8 -- Obviously replace the [dot] with .'s :)
[Hero CDMA Android Development] wtphoto:
when was the last time you actually updated sdk? if its been a bit then update sdk and try again.
[Hero CDMA Android Development] barkerja:
This was taken right after I downloaded the most recent SDK.
[Hero CDMA Android Development] seaweedopm:
Thank you for the radio wtphoto. Apparently it doesn't like it when I recompress the files into the rom.zip. Now I'm sure I'll have to go spend 4 hours at the sprint store and then end up waiting for it to be mailed. Thank god for the updated MightROM for the TP2. My WM phone is almost usable. Thanks MightyMouse.

Below is a section of my RUU log file. The RUU installer failed with an ERROR [132]: SIGNARURE ERROR.

And yes, the error message said "SIGNARURE".

</DEBUG></T024301>
<T024301><DEBUG><CMD>fastboot -s MySN flash zip C:\Backups\RUU_Hero_C_Sprint_1.56.651.2_signed_release\rom.zip</CMD>
</DEBUG></T024301>
<T024302><DEBUG><OUT>sending 'zip' (104813 KB)...</OUT>
</DEBUG></T024302>
<T024516><DEBUG><OUT>OKAY</OUT>
</DEBUG></T024516>
<T024516><DEBUG><OUT>e checking...</OUT>
</DEBUG></T024516>
<T024541><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T024541>
[Hero CDMA Android Development] andrewl2020:
Yea mm is cool, specially like the rom upadate notification!

War rom is nice, like that hd2 ish.

Sucks about this ruu, for the ones that are having the problem.

Wonder how everyone will act when they go for 2.1 and more ppl brick.

Only thing i could think of now, is finding another ruu total package(not just radio)

Thanks
[Hero CDMA Android Development] Mistamike17:
I'm getting an interesting new error. I've probably screwed something up but here goes:

ERROR [180]:PPST UNSUPPORTED ERROR

<LOG>
<T193256><INFO><VERSION>0, 9, 7, 4029</VERSION></INFO></T193256>
<T193258><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
HT9B9HF02135 device
</OUT>

</DEBUG></T193258>
<T193258><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T193258>
<T193310><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T193310>
<T193311><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
HT9B9HF02135 device
</OUT>

</DEBUG></T193311>
<T193312><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
HT9B9HF02135 device
</OUT>

</DEBUG></T193312>
<T193313><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
HT9B9HF02135 device
</OUT>

</DEBUG></T193313>
<T193314><DEBUG><CMD>adb -s HT9B9HF02135 shell cat /sys/class/power_supply/battery/capacity</CMD>
<OUT>66</OUT>

</DEBUG></T193314>
<T193315><DEBUG><CMD>adb -s HT9B9HF02135 push DMData00.DAT /data/data/dmdata/DMData00.DAT</CMD>
<OUT>9 KB/s (131 bytes in 0.014s)</OUT>

</DEBUG></T193315>
<T193317><DEBUG><CMD>adb -s HT9B9HF02135 push DMData01.DAT /data/data/dmdata/DMData01.DAT</CMD>
<OUT>14 KB/s (131 bytes in 0.009s)</OUT>

</DEBUG></T193317>
<T193318><DEBUG><CMD>adb -s HT9B9HF02135 push DMData02.DAT /data/data/dmdata/DMData02.DAT</CMD>
<OUT>12 KB/s (133 bytes in 0.010s)</OUT>

</DEBUG></T193318>
<T193319><DEBUG><CMD>adb -s HT9B9HF02135 push DMData03.DAT /data/data/dmdata/DMData03.DAT</CMD>
<OUT>11 KB/s (131 bytes in 0.011s)
</OUT>

</DEBUG></T193319>
<T193319><DEBUG><CMD>adb -s HT9B9HF02135 shell PPST</CMD>
<OUT>PPST: not found
</OUT>

</DEBUG></T193319>
<T193321><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
HT9B9HF02135 device
</OUT>

</DEBUG></T193321>
<T193321><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
HT9B9HF02135 device
</OUT>

</DEBUG></T193321>
<T193322><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
HT9B9HF02135 device
</OUT>

</DEBUG></T193322>
<T193325><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
HT9B9HF02135 device
</OUT>

</DEBUG></T193325>
<T193326><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
HT9B9HF02135 device
</OUT>

</DEBUG></T193326>
<T193327><DEBUG><CMD>adb kill-server</CMD>
<OUT />

</DEBUG></T193327>
</LOG>
[Hero CDMA Android Development] Mistamike17:
Anyone have any idea why the PPST isn't being found?
[Hero CDMA Android Development] RTessi:
I am running into the Error 110 issue and have tried all the recommendations that I have seen from swapping the 3 files, to drivers to different computers etc. nothing is working.

I can run fastboot commands, but no adb commands and when i research the RUU logs i notice that as soon as thh final fastboot command checking battery level is completed, it then turns into a series of failed adb commands.

what do i need to do to get adb working again or how can i get around this?

i'm not sure if this matters, but in the 6 hours i've been trying to figure this out, i deleted all the files on my SD card, so currently there is nothing on it. Do i need anything on the sd card for the RUU/adb commands to work properly?

I'd really appreciate help as I'd prefer to not have to return the phone, but more importantly learn what is going on with the phone, but don't have enough knowledge at the moment for myself to be able to repair it on my own.
[Hero CDMA Android Development] gibsontest:
Same here.

I've tried replacing adb.exe, AdbWinApi.dll and fastboot.exe with the ones from the SDK, no dice. I tried replacing rom.zip with a modaco build (for giggles), no dice. Everytime, it gets to around 90% and then dies with error 110. I've tried running as Administrator. I've pulled the battery, rebooted, tried again.

Some notes:

This is a CDMA phone (sprint).

The phone has been rooted, had installed modaco 2.2 with success.

Was receiving some error 67's, so I wanted to unroot before I felt like I had to send it in. (And I just wanted more rooting experience, tbh)

Unplugging USB shows fastboot, plugging back in, HTC logo, etc etc

RUU 1.29 doesn't work.

adb devices shows nothing.

fastboot devices shows my device and fastboot

At the moment I am redownloading the RUU (as per xdaforums.com/showpost.php?p=5655347&postcount=113 ) and will report here with my success (or failure).

I would greatly appreciate any other guidance in this before I start talking to my "guy" at Sprint. And thanks to the devs for their hard work: my problems regardless, it seems to work for more people than less. ;)

EDIT: New RUU doesn't work either. Going to reinstall HTC Sync and see what happens.

EDIT2: I'm attempting 'fastboot boot recovery.img' using recovery-RA-heroc-v1.2.3.img

Currently command prompt says:

>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting...

And it's been sitting here for about 10 minutes. Can anyone comment on whether this is a good/bad idea and how long I should expect to wait for it to finish 'booting...' ? Again, I appreciate any guidance.
[Hero CDMA Android Development] gibsontest:
As an update (and bump) to my situation above:

I unplugged the USB cord when error 110 first shows up and (like someone else reported earlier in the thread) I see:

[COLOR="Lime"]Parsing...[downloaded ZIP]
[1] BOOT - OK
[2] BOOTLOADER - OK
[3] RADIO_V2 - [/COLOR][COLOR="Red"]Fail-PU[/COLOR]
[COLOR="Lime"][4] RECOVERY - OK
[5] SPLASH1 - OK
[6] SYSTEM - OK
[7] USERDATA - OK[/COLOR]
Partition update fail!
[COLOR="Red"]Update Fail![/COLOR]

In addition to that little bit of data, radio version is 1.04.01.09.21.

Is it possible that I just to format my SD?
[Hero CDMA Android Development] RTessi:
Gibson,

I feel like you are running into the smae issue I am, which is that the adb commands are not working... Have you look at your RUU Log files that should be in the c:\ruu_log directory?

All my fastboot commands work properly, but once it transitions into adb, I get continued device not found errors... and in my eyes if the adb commands don't work, its not a matter of the RUU being faulty, but rather our phones being "locked out" of the adb functions.

I think I read somewhere else that adb is disabled in the HBOOT, which is that HTC / HBOOT menu when its plugged in or not...

I'm going to try again today and i'll keep you posted too, but i feel like the RUU File Error is more related to our phones than the RUU file itself...

I also experiences the booting... screen and it never changes so i'm not sure it will ever do anything other than booting...
[Hero CDMA Android Development] RTessi:
I am on a 1500 minute to landline unlimited ervtyhing else plan with 2 other phones (2 heros & 1 standard phone)... Just switched over 2 weeks ago, so I am within the 30 "return" window luckily if we can't figure this out...

i rooted then updated to fresh 1.1, the a bunch of clearscreens, clear keyboard, godzson taskbar, 2.1 icons and clear rosie. i think that was it.

then since i had figured out how to get my phone to where i liked it after doing a lot of other minor updates and fresh 1.1 updates (because sometimes things don't work until you reflash the fresh etc...) i decided that i should do a factory wipe to remove any old baggage i thought might be around from all the previous iterations i had tried... worked perfectly on one of the heros (luckily the work one) and then when i went for my personal one, i got error 110 and have been stuck working on it for almost 8 hours now...

i think error 110 seems to be irrepairable because of the adb "lockout", but I'm not giving up hope as I'd like to see my phone fixed and understand what happened vs having to go in and replace and hopefully just have it traded out for a new one...

just finished download the RUU again, will report back in 5 minutes if i also have the same unluck as you...

R
[Hero CDMA Android Development] RTessi:
I also have no love when I redownloaded the RUU file...

:( its looking gloomier and gloomier for the 110 crowd...

R
[Hero CDMA Android Development] gibsontest:
I agree about the gloom.

I tried something else (don't have much else to lose, though I wouldn't recommend this if you don't want a real brick, which is what I have now):

fastboot flash zip rom.zip
sending 'zip' (104813 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (status read failed (Too many links))

And now the phone won't even respond to the power button (or any combination of buttons, thereof.

Looks like I'll really come to appreciate that 30-day window.

EDIT: Revising my statement, now I see the HTC logo... I don't get this phone sometimes...
[Hero CDMA Android Development] RTessi:
you may have just drained the battery... mine did that too after a long battle with it and i was a little concerned until i recharged and after 5 minutes i was back into the same place where i've been stuck... although i think i would have preffered a brick vs. android teasing me with fastboot mode and nothing to do about it...

i'm off to the sprint store right now... i'd love to find a solution, but i need my phone more than i need to figure out the possible solution as fun and rewarding as that might be to fix...

R
[Hero CDMA Android Development] gibsontest:
I'm also taking the easy (maybe only) route here, too... I've called in for a replacement. In the mean time I'll keep futzing with the phone and see if I can't fix it.
[Hero CDMA Android Development] wtphoto:
I wish there was something I could do to help you guys but I really have no idea what the issue is. Just for ****s and giggles I just ruued my phone and it went off without a hitch.
[Hero CDMA Android Development] RTessi:
...................
[Hero CDMA Android Development] mercado79:
I find this pretty disturbing. Haven't tried to RUU and hope I never have to! Anyway, just thought I'd share a few thoughts.

The HTC site originally (back in October/November) had the 1.29 RUU available for download. They took it down and never uploaded this one, 1.56. Maybe there's a reason for that. Maybe they knew it would cause problems (or could cause problems) if people flashed the wrong RUU for their phone/hardware version. If I need to RUU in the future, I think I'll stick with the RUU that came straight from the HTC site, i.e. 1.29. That's the ROM that was on my phone when I got it, so...I'm guessing it's probably safest to start there.

I've found that some software like Droid Explorer will disrupt normal ADB commands from running. This is because Droid Explorer runs its own ADB instance as a service within Windows. So, it's probably best to stop the service before running the RUU (assuming you installed the program).

Are most people running the latest recovery menu 1.5.2 or the original 1.2.3? Maybe that's playing a factor? Anyone running into issues should probably specify that as well.

I wonder if since our phones were built using Android 1.5, we should be using an older SDK. In some of the posts here in this thread, it was suggested that the ADB in the RUU be updated with the latest one. Maybe not?

Anyway, just thinking aloud here! I don't have any solutions, but thought I'd try and keep track of some ideas. Here's to hoping someone figures out what's happening in these (thankfully) few cases where phones are being bricked.
[Hero CDMA Android Development] smw6180:
Had to take my Hero back to Best Buy (only had it a couple of weeks) due to the 'dust under the screen' issue. Decided to try the RUU (next time I'll just restore the stock nandroid, trust me on this). I ran into the same Error: 110 problems others have had.

Basically at that point you're done. The phone fails on partition 51, midway through the flash, and asks for a 'proper' RUU. You can re-run the RUU utility but it just dies in the same place every time. Being unable to find another RUU I just said screw it. It was going back to Best Buy anyhow.

Anyhow it seems the phone never gets to ADB...just sits in fastboot. And there's no way to reboot recovery at that point.

So like I said, in the future instead of playing with the RUU I'll just restore my nandroid backup which I always do right after rooting and before swapping roms.
[Hero CDMA Android Development] gibsontest:
No problem. I'm just worried more people are going to try RUUing with 1.56 and brick their phones like we did. Although, you and many others seem to being doing just fine. :o

I'm wondering if there's a more recent RUU that could be used? Or possibly some other method of unrooting?

I was running 1.5.2 It's possible that this could cause issues.

I'm sorry to hear you've hit the wall as well. I'd personally like to develop some kind of unrooting solution that is more friendly than the RUU but I'm now a bit more scared that I'll brick my next Hero. :(
[Hero CDMA Android Development] RTessi:
I was also running 1.5.2 when I tried to RUU, vs the one that went off without a hitch being a 1.29...

Also, I read something interesting today that was possibly a reason why i ran into the "brick"... I installed PDANet and from what another poster mentioned on another thread, ADB is disabled when it gets installed... my mind can't sotp thinking that PDANet prevented the RUU from working if that is indeed correct...

Gibson, Did you have PDANet installed?

R
[Hero CDMA Android Development] gibsontest:
No PDANet here.

I've received my new hero today (glee). I'm going to hold off on rooting it straight away and first see if i can't unbrick my first hero.

If anyone who knows anything about the various RUU's or other methods of "emergency" flashing is reading this thread, would you care to shed some light on what kind of interaction with the phone is possible when it boots into fastboot's "RUU mode"? (Apparently this isn't just fastboot anymore...)
[Hero CDMA Android Development] xparadigm:
I got bricked as well.

I was running 1.5.2, and running 2.2, and yes i manually rooted.

I get stuck with error 110, on the radio during install. Like everyone else says... every OTHER part of the install works flawlessly.

The phone is NOT recognized by adb. The phone IS recognized by fastboot.... so heres my question:

Using the "fastboot boot" command is it possible to use a .img file to get the phone to boot further so we can get adb to work, and then from there re-install a custom ROM?

Any and all replies would be helpful.
[Hero CDMA Android Development] gibsontest:
You would think that might work. However, I've tried every combination of 'fastboot boot' and an img. My phone ends up dying from low battery before anything useful happens (after like 30 -45 minutes). By all means give it a shot, I would love to see someone get a 110'd phone working again. :D
[Hero CDMA Android Development] RTessi:
By all means try what you want, but between Gibson and myself i think we ran the gamut of options unsuccessfully... Please do report back with your findings, as I fear the day I need to re-RUU with my experience so far...

R
[Hero CDMA Android Development] xparadigm:
Well then. Since i could not get the RUU to work, and my first 30 days had not passed, i went in and got a brand spanking new phone.

TO HELP NEUTRALIZE THIS FROM HAPPENING AGAIN

I am going to make a completely stock nandroid backup, and post it on here. Assuming that is, that a nandroid backup wont corrupt someone else's phone.

If that is the case, then i'll just keep it to myself. If it seems useful, then i'll make sure to host it somewhere free and share the love.
[Hero CDMA Android Development] Mistamike17:
You are the man! That would be absolutely amaaaaaazing. I somehow skipped the first nandroid backup and don't have a way of going back. If you could do this, I would be forever grateful.

Can we get some confirmation that it would be OK to use a nandroid backup from a different phone?
[Hero CDMA Android Development] xparadigm:
Im waiting for someone to verify that is okay for someone to use a stock nandroid restore from a different phone.

Again, this is fresh out of the box with Sprint. The ONLY application i installed was flashrec, and i did it outside of the market. So the nandroid wont even have a google account association. I kept that in mind while making these.

I currently have two saved nandroid backups that i am waiting to post. One with the v1.2.3 patched .img, and one with the v1.5.2 .img. I dont think there will be any difference, but in case people are lazy [like me] and dont want to flash a new .img to their phone... ive backed up both as to allow the user to download whichever they see fit.

I also made a stock flashrec .img backup for those interested.

Again, im waiting for a mod, or someone with better knowledge of these phones, to verify that it is alright to use a nandroid backup from a different phone.