yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] dfbonney:
Yes, completely resolved. As in I can use home+end to boot to recovery now... and VOLDown+end to boot to HBOOT screen and of course, just end to boot the phone like I used to be able to. Its posted up now.

I'm only going to mainly monitor the other post from here on out.

If someone wants assistance with this I might be able to help out remotely.
[Hero CDMA Android Development] prittyboy203:
hey valnomien and crash447 im new to posting but i always read up on things but just 3 days ago i flash so many 2.1 roms and when i tryed out the new radios for both roms i wanted to flash back and when i tryed to ruu's it got all the way to 99% and then the phone completely busted on my i was freaking out and i tryed everything i tryed to turn the phone back on nothing the sprint rep tryed something and all he did was turn the phone on while i was talking to him over the phone but it was black but it had a dim light like crash did i had rushed over to radio shack and i told them this crazy story and they swaped it out for a fresh brand new one but ever since then i have not and will not flash a radio again inless i know for sure i can go back to stock radio or get the right radio for the new 2.1 from sprint lol :)
[Hero CDMA Android Development] villeban:
Ohhh men, thank you so much!
[Hero CDMA Android Development] danimal_01:
Umm just forget about this post and go to this one here ...

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

That link will help you out a lot better than this one... :) Not sure why it's not stickied yet ... :/

~Danny
[Hero CDMA Android Development] villeban:
thanks again people!
[Hero CDMA Android Development] smw6180:
It's in the Wiki
[Hero CDMA Android Development] edivens:
have you been able to get it back to stock
[Hero CDMA Android Development] rayborn:
Tried that to no avail

also cant reboot period or you got back to the logo
[Hero CDMA Android Development] justinisyoung:
don't reboot as in turn off your phone, do a command from adb shell

adb shell
#reboot recovery

maybe that'll work? cause then it turns off and loads straight into recovery?
[Hero CDMA Android Development] smw6180:
My phone bricked with the original radio and Fresh ROM 1.1. So it's not a radio issue (at least the people who originally had the issue didn't have anything but the stock radio).
[Hero CDMA Android Development] sffr:
You can RUU to restore the radio. I did it... I also noticed if you try to RUU with the phone on you will see it detects a SW Version of 2.0XXX. instead of 1.56. I noticed when i did a ADB Shell => Reboot Bootloader. It boots into a RUU Mode where if you run RUU it will actually show 1.56 i managed to get mine to RUU again back to factory.
[Hero CDMA Android Development] mrinehart93:
What if we were to inject additional commands and files into the RUU so that the RUU would flash what we needed to the phone, instead of what IT wants (which keeps failing)?

And just to get this straight... I used the 1.56 RUU about a month ago, and a week ago I flashed the Radio. So now if I use the 1.56 RUU again, my phone will get f'ed? Damn this sucks haha. I'll just be extremely diligent with nandroid backups.
[Hero CDMA Android Development] mrinehart93:
Oh, I should mention, AvalaunchMods posted the stock Radio.img somewhere back... so if you want the stock Radio, just flash that instead of doing an RUU.
[Hero CDMA Android Development] sffr:
I did the same thing FLASHED new radio. The ran RUU to restore radio... It worked fine... Successfully Flashed back factory
[Hero CDMA Android Development] willowmp:
Yep I was going to say one could take the radio and pack it up in an update.zip and flash it to their phone. Then RUU and you should be good to go.

Btw if you do decide to flash the factory radio MAKE SURE IT IS THE CORRECT RADIO. Triple check it, cause if you flash the wrong one such as a GSM radio you will have a cinder block of a phone (beyond bricked as in totaled completely).
[Hero CDMA Android Development] sffr:
You dont need to restore radio before ruu. I didnt flash it first.
[Hero CDMA Android Development] willowmp:
Except some people cannot get RUU to run with the new radio. The RUU is giving them an error and does not proceed.

By flashing the original radio to the phone you are basically undoing what you did. Therefore I would assume that after flashing the original radio RUU would once again work.
[Hero CDMA Android Development] justinisyoung:
in Avalaunchmod's thread his update-script was wrong so it just copied the radio.img to /system instead of actually flashing it. i fixed it up for him and i'll attach it here.

there should be no problems with it, but if there is, it's not my fault :D0

so again, this is a signed, ready-to-flash stock radio that should just overwrite the newer radio and put the older radio.
[Hero CDMA Android Development] smw6180:
If you're talking about the 110 errors, it has nothing to do with the radio.
[Hero CDMA Android Development] danimal_01:
agreed I think it has something to do with the fact that it has no recovery image to boot from therefore causing the triangle with the exclamation in the middle. We're already one step closer to figuring this out since we can now boot up via our computers... There just needs to be a way to flash this image file. That's why I had the idea of trying the flash from using that app..

~Danny
[Hero CDMA Android Development] crash447:
How would you flash this without nandroid?

Also I have been trying Daniel's idea thanks to his help tonight and so far no luck. I am still having to use the pc to boot.
[Hero CDMA Android Development] willowmp:
Nandroid flashes nandroid recovery files.

You flash the radio.zip as an update.zip.

Use recovery to flash the update, just as you would a rom.
[Hero CDMA Android Development] crash447:
Sorry, wrong wording I guess. Anyway to flash this without recovery since I am stuck in "semi-bricked" "fastboot oem boot" state?
[Hero CDMA Android Development] scriz:
Flashed through fine, now booting..will update baseband version after it boots fully

edit:

baseband version 1.04.01.09.21, worked like a charm.
[Hero CDMA Android Development] obelisk79:
not sure of the syntax off the top of my head, but i'm pretty sure you can flash images via the android sdk fastboot command. not bricked, cant test this, but in theory should work.
[Hero CDMA Android Development] crash447:
Well I just tried to flash it with fastboot and got an error. It said "12 signature verify fail."
[Hero CDMA Android Development] smw6180:
fastboot flash image.zip

Didn't work for me though. Ended up with a new phone to replace my brick.

Edit:

Yep. That's what happened to me too.
[Hero CDMA Android Development] obelisk79:
which update.zip are you using?

could try using the rom.zip that the RUU places in your temp folder when it runs.
[Hero CDMA Android Development] willowmp:
I too am unsure but I think I remember seeing a method of flashing through sdk at the fastboot screen.

Just throwing an idea out there but could one use a terminal app and run the flash command to reflash the recovery stuff back on to the phone?

That is how I ended up putting RA recovery onto my phone. I put the recovery file onto my sd card and ran the command through terminal and it worked like a charm.

If it is the original recovery that is indeed missing, I assume one could potentially flash the missing recovery through terminal in a similar manner that I used to flash the RA recovery onto my phone?

I dunno just tossing ideas out there...

Edit: If I am remembering correctly in order to flash through fastboot you had to deactivate the signature check on the phone, otherwise you cannot flash it as it will fail the signature validation.
[Hero CDMA Android Development] crash447:
I don't know what "terminal" is, but I tried flashing the recovery with the Recovery Flasher that Daniel sent me tonight and so far I have not had luck.
[Hero CDMA Android Development] obelisk79:
also, if no luck with the update.zip files, have you tried the raw .img file? might be worth a shot.
[Hero CDMA Android Development] willowmp:
Terminal as in the app in the market terminal.

The terminal is like the command prompt on linux systems. You can do things like flashing wiping push pull etc. etc. through terminal.

So if you use that sdk fastboot oem whatever trick to get your phone to boot up, go to the market and download a terminal app, and run the flash command maybe you could take the stock bootloader files, place them on the sd card, and flash it back into the phone, all through the phone without using computer at all.
[Hero CDMA Android Development] crash447:
OK, I will try that. However I think I did successfully flash the recovery files through the recovery flasher, but it still will not boot without the fastboot trick.
[Hero CDMA Android Development] mrinehart93:
I think now you need to open a terminal, type in "reboot recovery", and if it boots the recovery, then flash all the stock stuff you can to get it working.
[Hero CDMA Android Development] willowmp:
I haven't been on the forums in a while so I really kinda just jumped into the whole issue with bricking phones through RUU.

If my understanding thus far is correct, the issue is stemming from for whatever reason the original factory recovery image is being wiped off phones, and because it lacks that original factory recovery img RUU can't work.

My idea, if what I believe the problem to be is in fact true, is that one could use the sdk oem reboot to get the phone to boot up, go to market and install the terminal app (better terminal/etc.), find the img of the factory recovery in RUU or wherever and put this on your sd card, open the terminal and enter the command to flash the factory recovery img to the phone.

Basically I'm basing this off of how I originally flashed the RA recovery to my phone. I put the RA recovery file onto my sd card, entered terminal, entered the command to flash the file and presto RA recovery was working like a charm. Now if you could do the same with the original factory recovery img then the RUU would regain its ability to function.

I believe RUU is throwing an error because it utilizes the factory recovery img to do what it does, and if that is missing then obviously RUU is going to be like wtf..error.
[Hero CDMA Android Development] crash447:
What commands would I use?
[Hero CDMA Android Development] willowmp:
I. Flash a New Recovery Image

1. Find the recovery image you want and MAKE SURE IT IS FOR YOUR PHONE (should say in where you download it what phone it is for).

2. Write down the filename of the recovery image EXACTLY as it is written (i.e. RA-Hero-Recovery-v1.2.2.img).

3. Put the recovery image file on the SD card (not in any folders).

4. Download Terminal from the Market if you don’t already have it and install it (there are a few different terminals in the Market some have an onscreen keyboard and some don’t experiment till you get one, also hold down Menu in some of them to bring up the onscreen keyboard if you don’t see it).

5. Open the Terminal program and type the following (with hitting enter at the end of each line):

su
flash_image recovery /sdcard/name-of-recovery.img

6. In the above text, replace name-of-recovery.img with the name of your recovery image (make sure the .img is on the end).

7. Phone should pause for a second and then show you a new blank line. Turn it off and back on by holding down Home and Power to ensure it flashed correctly. Done.

This is the guide I followed way back when, when I had installed RA's recovery. I'm sure the terminal flash code needs a bit of modding so that it flashes the factory img to where the factory img goes, but this is basically where my theory is coming from.
[Hero CDMA Android Development] crash447:
I just tried this and same result.
[Hero CDMA Android Development] sffr:
The RUU works off Fastboot.

<T221306><DEBUG><CMD>fastboot -s HT9BMHF07510 flash zip C:\Web\RUU_Hero_C_Sprint_1.56.651.2_signed_release\rom.zip</CMD>

</DEBUG></T221306>
[Hero CDMA Android Development] justinisyoung:
you've tried holding down the VOL DOWN button and the power button at the same time before to go to bootloader before right? does it work if you enter fastboot mode through there and try the RUU?

also, i know that the Eris people installed their 2.1 leak through HBOOT. apparently, what they did was rename the leaked ROM to PB00IMG.zip and place that on their phone, and then they started HBOOT, which would find the zip and flash that to their phone. i rebooted to the bootloader to see if we would have the same filename, but i'm at a loss to what the zip file should be named.

i got a few stills of the zip that HBOOT is looking for, and it seems as if its HERCIMG.zip, though i'm not sure. maybe somebody could take the rom.zip from the RUU and rename it to HERCIMG.zip and place it on the sdcard?

my phone isn't bricked like this so i can't really try and cause i need my phone, but it could work. basically,

1. place the rom.zip from the RUU in the sdcard and rename it HERCIMG.zip

2. enter bootloader by holding down the VOLUME DOWN button and POWER

3. press VOLUME DOWN to enter HBOOT, and let it search for the zip files.

somebody try this and report back?
[Hero CDMA Android Development] crash447:
I am having trouble getting this typed in. Is this all one line?
[Hero CDMA Android Development] sffr:
You cant type that in thats the RUU Log.

Technically you could type

fastboot -s *****deviceIDHERE***** flash zip C:\****RUU LOCATION FOLDER****\rom.zip
[Hero CDMA Android Development] obelisk79:
Edited: bad info
[Hero CDMA Android Development] sffr:
It could give an remote: not allowed error.
[Hero CDMA Android Development] AyoJake:
so why dont people want the new radio on their hero now?
[Hero CDMA Android Development] sffr:
I had signal issues with the new radio. Just moving the phone an inch when from 100% signal to 0%
[Hero CDMA Android Development] AyoJake:
oh ok i thought something was wrong with it...its worked fine for me...

hope everything works out.
[Hero CDMA Android Development] sffr:
The radio is good just some people have issues with it.

I'm a computer technician so anything technical i can find any error with it and it will drive me nuts.
[Hero CDMA Android Development] obelisk79:
I'm a technician also, same mentality, if it's wrong I must see it fixed or all resources exhausted in that vein.
[Hero CDMA Android Development] MrTrip:
Well.....glad I read this thread. I have had problems with the radio and wanted to go back with the RUU, but now I guess I'll tough it out....ugh.
[Hero CDMA Android Development] crash447:
OK guys, thanks so much for the help. I tried flashing the RUU in fastboot and I got the same result. Still wondering if I could find a way to flash the old radio if it might help the situation. Thanks again, got to get some sleep.
[Hero CDMA Android Development] sffr:
Most people have had success with reflashing original radio. This thread is about a 110 error which means missing files during RUU.
[Hero CDMA Android Development] obelisk79:
has anyone considered the possiblity of a corrupt filesystem on the boot partition? I'm not 100% familiar with the partition structure of the internal memory.
[Hero CDMA Android Development] obelisk79:
it's dangerous ground to tread but if it's possible to format the partition that contains the bootloader that could provide the missing element to recover from this.

either format it and RUU or format, manually flash then attempt RUU
[Hero CDMA Android Development] obelisk79:
Double-post, poor connection... doh.
[Hero CDMA Android Development] justinisyoung:
hmm... formatting bootloaders...

sounds like a hard SPL. messing with that stuff is SCARY.
[Hero CDMA Android Development] obelisk79:
if you're in a situation like this there surely should be a few people willing to risk it. I'd try.
[Hero CDMA Android Development] sffr:
Hell yea it is
[Hero CDMA Android Development] sffr:
They need to find a way to JTAG the EEPROM to restore the ROM.
[Hero CDMA Android Development] sffr:
I have another idea somebody post the contents of the RUU Log inside

C:\RUU_LOG\ after it fails there might be some good information inside a log file.
[Hero CDMA Android Development] obelisk79:
for the brave...

try the following in fastboot mode!

1. fastboot erase boot

2. fastboot erase recovery

3. run RUU or try fastboot flash boot boot.img

4. fastboot reboot

Safer alternative:

1. enter fastboot

2. extract all .img files from rom.zip obtained from RUU in android sdk /tools directory

3. make sure you are in the /tools directory

4. run the following command fastboot flashall

5. fastboot reboot
[Hero CDMA Android Development] obelisk79:
I'd love it if someone could try what I posted above and report back the results.
[Hero CDMA Android Development] crash447:
I have been trying the "safer alternative" this morning and I am getting a -p product specified nor Android_Product_Out set

I don't know what the product name would be.

Also just to point out when you try and just flash the radio in fastboot it gives a 12 signature verify fail. I will probably not be able to try anything else for a while. Have to go to work. Thanks again for the help.
[Hero CDMA Android Development] crash447:
Here is one my my Log files by the way.
[Hero CDMA Android Development] sffr:
We might have something.

<T003156><DEBUG><OUT>INFOstart image[userdata] unzipping & flushing...</OUT>

</DEBUG></T003156>

<T003156><DEBUG><OUT>INFO[RUU]UZ,userdata,0</OUT>

</DEBUG></T003156>

<T003156><DEBUG><OUT>INFO[RUU]UZ,userdata,100</OUT>

</DEBUG></T003156>

<T003159><DEBUG><OUT>INFO[RUU]WP,userdata,0</OUT>

</DEBUG></T003159>

<T003159><DEBUG><OUT>INFO[RUU]WP,userdata,100</OUT>

</DEBUG></T003159>

<T003159><DEBUG><OUT>FAILED (remote: 51 partition update fail)</OUT>

</DEBUG></T003159>

<T003214><DEBUG><CMD>adb devices</CMD>

I'm at work so i cant see what my logs show after it does Wipe Partition, User Data
[Hero CDMA Android Development] crash447:
When I tried fastboot erase boot it said "FAILED Remote not allowed".

Also I have tried to flash many things including radio.img's rom.zip's and recovery.img's in fastboot and I keep getting "12 Signature Verify Failure". What does that mean?

Thanks again for help.
[Hero CDMA Android Development] sffr:
When i get home from work in an Hour or so i will probably be able to find out why RUU keeps failing. It fails right after it completes the Flash of the User Data Partition. When i get home i will look to see what RUU does right after it finishes writing the User Data Portion then, we know where the investigate further.
[Hero CDMA Android Development] crash447:
OK, thanks. I do want to point out that when the RUU is flashing the green bar that goes across the screen of the Hero flashes red for a split second when it appears it is flashing the radio. I can't tell if it shows that in the log or not. On the PC it does not show any problems until it gets to the 90% mark, which is well after the period it flashes the radio.
[Hero CDMA Android Development] azyouthinkeyeiz:
Had any of the people with a messed up RUU have an a2sd partition, and could that even mess with the bootload sequence?

*Edit...

Thats an sd partition, so no it wouldn't...

..

long day...

..
[Hero CDMA Android Development] crash447:
I do not have an app2sd partition, at least if I do I sure do not know where it came from. Good thinking though.
[Hero CDMA Android Development] willowmp:
I believe it says it is failing the validation because the phone has a built in security feature that checks to ensure that the signature of what you are trying to flash is indeed a legit HTC file.

You need to deactivate the signature validation check on your phone.
[Hero CDMA Android Development] crash447:
How do you do that?
[Hero CDMA Android Development] willowmp:
I honestly don't remember, but I read it in a thread (I think on xda?).
[Hero CDMA Android Development] crash447:
Anyway to flash a radio with ADB. Just trying stuff out to see if something might work.
[Hero CDMA Android Development] obelisk79:
if I recall...

flash_image boot boot.img

flash_image system system.img

flash_image recovery recovery.imgafter re-reading your post, no, not sure about doing radio from adb, most likely possible, I'm just not sure how.
[Hero CDMA Android Development] realmrealm:
I did a quick google search and saw this on htc's site:

webpage: http://developer.htc.com/google-io-device.html#s4

not sure if that can help, but maybe it will shed some light.

-AndyS-
[Hero CDMA Android Development] danimal_01:
It could be possible that this method MIGHT work as I did not try pressing the Home + End buttons together...
[Hero CDMA Android Development] crash447:
I got "adb: permission denied". I also don't know about this because I think ultimately the home and end is to boot into recovery to complete the task which I can't do. Thanks again for all the ideas. I keep thinking one of them will work.
[Hero CDMA Android Development] crash447:
Been reading through some fastboot commands. I know these are not specifically for the cdma hero, but didn't know if anything here could help with the signature verification problem.

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

http://xdaforums.com/showthread.php?t=533240&page=3
[Hero CDMA Android Development] marcusva79:
Crash447 any luck man? I have been reading and nothing. Sorry.
[Hero CDMA Android Development] crash447:
No, man it seems that everything that looks like it should work in ADB or Fastboot seems to come back with a Signature Verification Error or Access Denied. It is so weird, because it seems like it is so close, but nothing has worked. I really appreciate your help. Starting to wonder if I should just take it back, I am just paranoid of a charge showing up on my bill down the line.
[Hero CDMA Android Development] obelisk79:
If I had a bricked phone I might be able to do more, but I'm certainly not going to gonuts trying to figure it out on my perfectly functional one.
[Hero CDMA Android Development] crash447:
I understand completely. I am very thankful for the help everyone has already been.
[Hero CDMA Android Development] danimal_01:
Crash,

Did you try this method detailed here?

http://developer.htc.com/google-io-device.html

Start from the beginning and just download the Android 1.5 stuff see if that works...

~Danny
[Hero CDMA Android Development] phishstics:
hey Crash, I am in the same boat. Rooted, flashed 2.1, wasn't happy with some things I was missing, unsuccessfully tried to go back before getting the 110 error and ended up at this post. I've so far been able to get up and running, but of course cannot reboot (and therefore, cant root again). Wondering if there's been any progress on solving this, or if I should head back to Sprint with an excuse, as I've only had the phone for 2 weeks. Thanks to anyone helping out on this!
[Hero CDMA Android Development] duffkitty:
I'd like to give thanks for this semi solution. I flashed my hero with Modaco and one day it went nuts, force close on lots of apps and radio wouldn't turn on. It would crash when I went to Settings --> Wireless so I reflashed and it wouldn't boot.

I then went to a nandroid backup but I wasn't content with the stock rom and went ahead and flashed Fresh 1.1 this time and same problem, wouldn't boot. Same with Modaco and went into a loop trying to get a costume rom going.

Finally I thought something may be wrong, let's go to stock and re-root the phone and try from scratch, thinking this was a failproof utility for my Hero I tried to use the 1.59 RUU. It gets to the end with a 110 and my phone wouldn't turn on at all. I took it to the Sprint store and they can't exchange it in the 30-day window because I got it from wirefly.... A third party... After a month they can send a replacement from a warehouse and swap my phone, which should be covered by the insurance because I'm sure it's fixable...

Anyways, I couldn't live for another 2 weeks with no phone so thank you very much for this semi solution.