yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] thefredelement:
I have added "fastboot.zip" to the OP, it's just the fastboot executable.

To make sure your device is connected from cmd prompt, get to where ever you put the exe and type:

Your Evo should be listed (while it's on the white screen that says "fastboot usb")

Then you can go ahead with the flashing of the recovery.
[EVO 4G Android Development] josh4trunks:
Got the fastboot.zip, unzipped it, ran it with the recovery.img from the pc36img_recovery.img you recommended in the same folder.

I ran

fastboot flash recovey recovery.img

this is what I get... =[

sending 'recovery' (4080 KB)... OKAY [ 1.150s]
writing 'recovery'... FAILED (remote:image update error)
finished. total time: 1.408s

Now clicking on recovery on phone just brings me a white screen with 3 skateboarding androids (and a small vibration). I feel like I'm much closer. Thanks, maybe I need to look for a different recovery.img

Thanks again, if you could help me solve this I would be a happy camper =]
[EVO 4G Android Development] josh4trunks:
K well I'm able to run

fastboot boot recovery.img

but all it does is bring me a black screen where if I press the powerbutton it goes back to fastboot. I'm gonna see if I need to find a certain recovery for my hardware.
[EVO 4G Android Development] thefredelement:
What does the black screen say?
[EVO 4G Android Development] josh4trunks:
Nothing just all black, top light on phone is orange. a power button press brings me back to fastboot usb screen. I think it's actually just off, cause it's then same state as off.

Do you have any idea why I'm getting the remote:image update error (from above)?
[EVO 4G Android Development] josh4trunks:
I tried flashing and booting to the evo-testing.img recovery from this thread/post. Same exact results (boot to off, flash to error). I might have hardware version 0004 (I really don't know how to check). I'm gonna look if there is a recovery for that version, as Amon_Ra was made for 0003.

http://xdaforums.com/showpost.php?p=9286422&postcount=27
[EVO 4G Android Development] thefredelement:
man alright, take the hboot image out of the hboot_76 zip file in the OP and copy it to your fastboot folder, make sure it's called hboot.img if not rename it, then do this:

fastboot flash hboot hboot.img
[EVO 4G Android Development] josh4trunks:
Got similar error as earlier, not looking too good.

sending 'hboot' (512KB))... OKAY [ 0.320s]
writing 'hboot' ... FAILED (remote: image update error)
finished. total time: 0.493s

------------

Going off a whim, maybe my fastboots are incompatible, but fastboot does see my device so I'm probably wrong there.

"fastboot devices" gives

123456789012 fastboot

when on fastboot usb screen

"????????????" when on hboot screen

"" (blank) when device is turned off
[EVO 4G Android Development] josh4trunks:
Following some other threads with serial #123456789012 I tried

*getting the stock rom for my radio

*put it on the sdcard

*renaming it PC36IMG.zip

*going into bootloader

Here it tries to flash it put stops after I see parsing. (I think what I tried really made no sense)

After I ruined my new EVO I rooted/romed my nephew (bought at same place/time), his is now working perfectly. The only reason I tried to downgrade was to get clockwork recovery, which I really don't care about. I just thought I needed it to flash kernels. Now I'm paying the price, lol I truly am an idiot.
[EVO 4G Android Development] thefredelement:
Can you get access to bootloader?
[EVO 4G Android Development] CraigCraig:
I think I just got bricked using this..
[EVO 4G Android Development] Karadorde:
Doubtful. Can you get to the Bootloader?

Swyped from my Evo.
[EVO 4G Android Development] CraigCraig:
I have no screen, and when the phone vibrates it registers on my computer as attached, I did fastboot devices and the serial is 123456789012 and I can't RUU, it reboots the phone but it hangs on waiting on bootloader and times out with the USB error
[EVO 4G Android Development] josh4trunks:
Yes. thats how I tied flashing the stock ROM for my radio, by opening up bootloader.
[EVO 4G Android Development] CraigCraig:
What exactly did you do? And could you see your screen? I can't see mine.
[EVO 4G Android Development] josh4trunks:
When I turn on my phone I go to FASTBOOT, I can then select BOOTLOADER

It then say SD checking..., but trying to flash something there doesn't seem to work.

So basically I can choose to be in a fastboot screen, or another HBOOT Screen which has menus

FASTBOOT

RECOVERY

CLEAR STORAGE

SIMLOCK

HBOOT USB
[EVO 4G Android Development] thefredelement:
Alright what have you tried flashing from the sd?
[EVO 4G Android Development] josh4trunks:
not sure.

I tried the stock ROM from here for my radio (renaming it) (This doesn't ask me to flash)

http://xdaforums.com/wiki/index.php?title=HTC_Supersonic/ROMs

I tried PC36IMG_Recovery.zip from here

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

errors on

Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!

both I renamed PC36IMG.zip and tried flashing.

I might need another ROM or recovery.img
[EVO 4G Android Development] josh4trunks:
I don't know if this is too extreme but I might start posting my problem with as much relevant information on several forums and see if I can get a fix that way.

Probably on

* xda - evo - q/a

* sdx - evo - 2.2development

* androidcentral - evo - roms/hacks

* evo4gforum - evo4grooting

I'll probably try this forum blasting in an hour, I'm gonna feel like a beggar after, I just wanted to get my phone working so my older sister (who got me it) doesn't freak out.
[EVO 4G Android Development] bfroehlich:
Thank you very much. Worked perfectly. HW 003
[EVO 4G Android Development] scottydont07:
I followed directions and now when I rebooted from flashing zip file it does the pc36img check and then it says model id inncorrect and now i noticed at the top it says

- supersonic unknown eng s-off

- hboot-2.10.001 ( then alot of random characters)

anyone know how to reload I have been trying everything I knw and I can not get it up and running
[EVO 4G Android Development] snandlal:
From my experience...and I know you don't want to hear it but...if your phone says serial # 123456789012, your screwed for now. We don't have the tools/program to fix this issue. Im sorry. I screwed up a phone messing with hboot and downgrading.
[EVO 4G Android Development] josh4trunks:
Yeah!!! lol, well I'm gonna

*post on a bunch of forums

*wait about 3 days, then offer maybe $30 to the first dev/ poster who can help me unbrick my phone

* send it to HTC...
[EVO 4G Android Development] CorePrime:
Worked for me too. Same hardware.
[EVO 4G Android Development] thefredelement:
Hey man I think you can just flash the 3.7 PC36IMG in bootloader and hopefully be alright.

One thing is for sure, as of now, DO NOT run the RUU, another poster had major issues after that.

Just to make it clear for me, your hboot is 2.10 but ENG correct?
[EVO 4G Android Development] josh4trunks:
EDIT: I found it, I'm gonna try and flash it in bootloader, got it from the end of the first post in this guide http://xdaforums.com/showthread.php?t=829045

I really hope I'm not doing the RUU thing you said, all I'm doing is

-moving it to SD card

-rename it from pc36img_3.70.zip to PC36IMG.zip

-boot phone, then press power on bootloader

-pray that it flashes correctly, and gets me a recovery

-see what to do from there.
[EVO 4G Android Development] thefredelement:
Hopefully that does it. That's the recovery that I started with in the OP.
[EVO 4G Android Development] BuddaBelly:
My phone is hardware ver 003 and came with hboot .97. I had updated to 2.10 awhile back and followed the OP instructions and everthing went perfect. After flashing the hboot file from recovery my backup wouldn't boot. I did however reflash my original rom after flashing my back up and was able to keep all of my data.
[EVO 4G Android Development] josh4trunks:
It actually ran but i got a fail for everything except radio_V2

Now a regular power button turn on brings me to skateboarding androids and nothing else.

A (power button + vol down) brings me to recovery where it tries to get me to flash image again. So now do I try and fastboot and flash a recovery?
[EVO 4G Android Development] thefredelement:
I'm pretty sure I know why after reading over your posts.

You have HBOOT ENG (even though it say 2.10 on it)

You need to install a recovery that works with your hboot, so lets do this:

Get this file:

http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-supersonic.img

rename it to "recovery.img"

Put it in the same folder as fastboot.

boot your phone with volume down & power button, so it says "fastboot usb" at the top (while connected to your computer)

type:
[EVO 4G Android Development] xHausx:
Hate to say it but you all are probably better off getting your phones replaced. Anything you flash through the hboot will be flashed to the wrong partition table. If you can get it to manually write to the correct offsets you may be able to do something with it but there is still the chance that you have written over your esn or something else that can not be replaced.

HTC is shipping some phones with the new bootloader and older partitions and that is why some people are ok doing this.

Of course I could be wrong though, this is all just what I've gathered from helping others who have been in this situation.

Edit: If you can get that modified amon ra to work by booting it through fastboot you may be able to do something
[EVO 4G Android Development] thefredelement:
When I went to 2.10 and .76 - I noticed when I ran the update to 2.10 through bootlaoder the phone had to reset to complete installation, I think at this point it wrote new partitions (I took measurements of them before and after and on the same phone they are different depending on the bootloader), as well when you go through this method and install .76 through recovery it needs to reboot to complete the installation, also I think to install to the partition sizes native to that hboot.

When I went through either way I saw my own partitions being re-written - it's why the roms have to be re-installed and a nandroid won't work, because of the partition size mis-match. (on boot especially).

I get what you're saying but I don't know how htc would have a ruu for 3.7 that can run on 002 - 004 hardware and be OK for both and not have the reverse be true for the hboot.
[EVO 4G Android Development] josh4trunks:
Sorry for all the effort you've had to put into helping e get my phone fixed. Anyway same exact thing with that recovery as earlier (remote: image update error)

I don't know why I get this error...

Anyway I'll try reflashing the 3.7 you recommended and see if I don't fail on everyone again...

And to xHausx, I am very stubborn, I probably will eventually send it in but that could cost me money and I'd feel like a total waste if I couldn't fix it on my own. I'm on winter break right now for another week, if I can get it fixed in a few day I my just need to give up and send it in.
[EVO 4G Android Development] xHausx:
It has to reboot because the hboot can not write over itself. Its possible it adjusted the partition size but I would think your /proc/mtd would stay the same
[EVO 4G Android Development] thefredelement:
http://xdaforums.com/showthread.php?t=883636 - here take a look at the first post there, I had saved my data there and asked others with 004 to help out.
[EVO 4G Android Development] josh4trunks:
So you were saying don't use ruu (which I could try from fastboot)

http://xdaforums.com/showthread.php?t=829045&page=56

recommend to do it but I haven't read through the result of yet
[EVO 4G Android Development] thefredelement:
I was talking with CraigCraig before, and he ran the RUU after he ran in to trouble and wasn't able to access his Evo via fastboot or anything else after that, so I'm weary of it.

I didn't know about that fastboot oem code to put the phone in a "ruu ready" state.
[EVO 4G Android Development] josh4trunks:
In your opinion should I try thefastboot ruu command?
[EVO 4G Android Development] thefredelement:
Attached hboot_2.10.0001.img.zip - contains just the img file for use via fastboot and

PC36IMG.zip for use via bootlaoder.
[EVO 4G Android Development] xHausx:
Yeah, your phone has the old mtd setup. The new ones show:

Checking MTD configuration...

dev: size erasesize name

mtd0: 00c00000 00040000 "wimax"

mtd1: 00100000 00040000 "misc"

mtd2: 00480000 00040000 "recovery"

mtd3: 00340000 00040000 "boot"

mtd4: 15e00000 00040000 "system"

mtd5: 0a000000 00040000 "cache"

mtd6: 1aa00000 00040000 "userdata"
[EVO 4G Android Development] thefredelement:
Attached stock recovery for 3.7 software.
[EVO 4G Android Development] Youthanasia:
just a recommendation for the op

could you change the " rename it to PC36IMG.zip "

to " rename it to PC36IMG " for the noobs like me.

if you copy PC36IMG.zip to your sd card bootloader won't read it......It will change it to PC36IMG.zip.zip

PS: worked great on an older 003 went from .97 to 2.10 ( have no freakin idea why i did that ) now back to .76 :D
[EVO 4G Android Development] leenypost:
Just a quick question... Is there 2 different hboot 0.76's ? An ENG one and a non ENG one? What's the difference?
[EVO 4G Android Development] illogos:
.76 is the engineering build hboot. It supports extended fastboot commands that the higher version hboots do not support. Honestly, there really is no reason to really need .76.

Do not try downgrading if you have hboot 2.02 or 2.10. Seriously... don't.
[EVO 4G Android Development] leenypost:
I already downgraded successfully. If your phone came with 2.02 or 2.10 it would be a problem... But I came with 0.97, then upgraded to 2.10 when I accepted the OTA so it was no problem for me.

2.10 did not play nice with Amon-Ra so I needed to downgrade... Figure if I was going to downgrade might as well flash the most useful one, LOL
[EVO 4G Android Development] alekosy:
Thank god that I'm not naive or stupid about my HBOOT, It is still 0.76 Hardware 003 White EVO :D :D :D :D :D Thank you for this thread cause it's good for a guy who thinks with an EVO like me, and says "Hmm? Am I going too overboarded with my EVO here?"

I remember one day I completely "bricked" my phone but had 0.76 S-OFF Hardware 003 EVO White! Completely Brand new and I successfully rooted using toastcfh's old thread but yeah, I had trouble one day and RUU'd back my phone to normal with the help of the guys here and there. Thank god for XDA Forums. :D
[EVO 4G Android Development] leenypost:
Huh? LOL

naive or stupid about hboot?

What are you talking about?

If you have all the latest radios and software versions without ever upgrading your hboot I'd say you are pretty naive about flashing radios.... An hboot doesn't do much for you and there is always a way to root after and official upgrade that is guaranteed to keep your 4g working, etc... So I prefer to naively upgrade my **** the right way and then re-root... And a already noted I now have 0.76 back with all my upgrades done in a way to ensure I keep my RSA keys 100% in tact.

P.S. - I see you love your white evo, LOL
[EVO 4G Android Development] dan0412:
Same here... my phone came with 0.97. After rooting, I upgraded to 2.10.0000 recently and was able to downgrade to .76.2000 (primarily because of the setup of my phone). The caveat is to ensure your phone has the 'old' mtd config, as explained here. Thus, you risk bricking your phone if you run this downgrade BEFORE verifying the mtd config.
[EVO 4G Android Development] Vega:
hey guys im very new to hboot . wondering what are the advantages and disadvantages to upgrading or downgrading. currently at .93.
[EVO 4G Android Development] leenypost:
For most people there is no difference. .76 just has a few extra commands available that the average user would never use. The only thing that is important is that your hboot is ENG.. Recoveries seem to have a problem occasionally if they aren't.

You can see if it's ENG when you power up into your HBOOT... Somewhere in the line (next to supersonic i believe) it should say ENG.
[EVO 4G Android Development] gpz1100:
On the topic of hboot versions, my phone came with 2.10.

I followed this guide to root;

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

At the bootloader screen, it indicates 2.1.0001 as my hboot version. Is this an ENG hboot? Or rather, what hboot does the above guide install?
[EVO 4G Android Development] leenypost:
If it is ENG it will say ENG somewhere on the white screen where you read the version number.

If your phone came with 2.10 already or is HW version 004 DO NOT TRY THIS MOD , IT WILL BRICK YOUR PHONE!!
[EVO 4G Android Development] George M:
Well I knew I should have left well enough alone.

My phone was:

Hardware 0003

hboot 97

S-Off

RA Rocovery

Running Spring Lovers latest 12-21

I wanted to get hboot back to 76 so I had all the fastboot commands to correct the MAC of my WiFi

Anyway I followed the directions.

After step two I was booted back to bootloader.

Now showed hboot 76 with S-Off

Tried to restore nandroid, but booted back to fastboot.

Sent the full Sprint Lover Rom to the sdcard.

When restarting it checks the PC36IMG.zip, but finds errors so doesn't load it.

After reading the forums I thought maybe I now had the wrong recovery so I flashed a different one. Bad move. Now I cannot get into recover at all. It stays at the white screen with

htc EVO 4G

Since I cant get into recovery, I cant use adb and send any other images to the card.

Sure could use some guidence here, please.
[EVO 4G Android Development] Bizdady:
Try getting a SD Card reader or use another phone to load your card to the pc so you can drop in a different PC36IMG zip
[EVO 4G Android Development] leenypost:
You had .97 when you tried to flash this? This is for 2.10 or 2.02.....

You could have just flashed .76 as .97 and earlier are able to be pushed back.
[EVO 4G Android Development] George M:
I dont have a reader for that size card, or another phone.
[EVO 4G Android Development] George M:
Of all the forums I have read (many over the last week), and seeing other people have the same question - I never saw that stated anywhere. Sure wish I had seen it.

However, What are my options now? Should I run an RUU program?
[EVO 4G Android Development] Bizdady:
Ruu to get back up

Sent from my Evo CM6
[EVO 4G Android Development] thefredelement:
Or you can boot to fastboot usb and flash the recovery back.

with recovery.img being the name of the recovery, Clockwork recovery has been updated today or yesterday you can get the latest image here: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-supersonic.img
[EVO 4G Android Development] George M:
Thats what a I did. Back up and running again with hboot 76.

Tkanks
[EVO 4G Android Development] octify:
Hey you guys since step 3 is kind of left up to the end user I thought I'd let you know what I did. After running the P36IMG file and flashing the hboot file in recovery, I performed a nandroid back up. I then mounted usb, transfered the nandroid to my PC. I also deleted the p36img file since the hboot downgrade was complete. I then downloaded a p36img file with the .93 hboot in it, I downloaded this from one of the "unbricking" threads on here, it has gotten me out of trouble alot. Now heres the trick take your nandroid .img files and copy them into the P36IMG.zip file you downloaded with the .93 bootloader, it will overwrite the .img files with your nandroid ones. Now copy that over to your sdcard, boot into the bootloader and let it detect the file, and press volume up to start the update. This will get your phone unbricked, and on hboot .93 and it will boot and everything will work great. I think this works well because since its a higher hboot but still a good hboot it allows the update and flushes everything out.
[EVO 4G Android Development] Madatsubomi:
Worked just as you stated, except.. I couldn't get my recovery running again.

I'll simply push those files back in and everything should be good.

Though, I was poking around and came across Calkulin's Radio/WiMax/PRL/NV collection and he mentioned kernel would have to be reflashed if you do a hboot update/downgrade.

Perhaps if someone reflashes their kernel after this, they wouldn't need to install from scratch?

Just a thought was all. :)
[EVO 4G Android Development] leenypost:
Might be possible, Try it and let us know if that works.
[EVO 4G Android Development] leenypost:
Fred, is there a flashable zip file for this particular version of clockwork?
[EVO 4G Android Development] xHausx:
Yup, just flash the kernel and you should be good to go.

On a different note I'm surprised to see how many people with .9x hboots, or who upgraded from .9x, are using this when it's completely unnecessary. It's kind of funny. I guess some just like doing things the hard way lol
[EVO 4G Android Development] thefredelement:
You can just use the image to flash it via fastboot, I'll make a PC36IMG for it later I guess and add it here. (when I get home from work)

Or you can just grab it via rom manager. :)
[EVO 4G Android Development] leenypost:
Cool, thanks. Do you know if this version supports the new partitions as well as the old ones?
[EVO 4G Android Development] sac23:
dude did anyones phone just die doing this my phone doesent even turn on anymore anybody have this problem??
[EVO 4G Android Development] thefredelement:
I'm not sure, I know there was some fstab work done: https://github.com/CyanogenMod/android_bootable_recovery/commits/

I tweeted at koush when he replies I'll update.
[EVO 4G Android Development] thefredelement:
What hardware version are you on?
[EVO 4G Android Development] sac23:
i think 004 my lil bro decided to do this withut reading can someone help

it starts but no screen
[EVO 4G Android Development] Bizdady:
Hold the volume down button while turning on and see if it boots into recovery.
[EVO 4G Android Development] sac23:
tryed it i think it does boot but theres just no screen

does anyone know a work around
[EVO 4G Android Development] thefredelement:
Take it to Sprint and tell them it just quit turning on. It's in the first year warranty so they should give you a new one on the spot.
[EVO 4G Android Development] gpz1100:
Alright... At present, it does not say ENG at the hboot screen. However, during the rooting process, I do remember seeing one hboot screen that did show 0.76 ENG. When the rooting was done, a different hboot was flashed (part of the rooting guide in my post earlier). I'm guessing the 2.1.0001 i'm seeing now came from that later hboot flash.

With that in mind, why did hboot need to be updated further in the first place after .76 was installed?

At present, my mtd looks like this

Checking MTD configuration...

dev: size erasesize name

mtd0: 00c00000 00040000 "wimax"

mtd1: 00100000 00040000 "misc"

mtd2: 00480000 00040000 "recovery"

mtd3: 00340000 00040000 "boot"

mtd4: 15e00000 00040000 "system"

mtd5: 0a000000 00040000 "cache"

mtd6: 1aa00000 00040000 "userdata"
[EVO 4G Android Development] Wire P. Snyder:
Was ducking around with my Evo last night and noticed I couldnt flash the Splash screen. This must be one of the few commands that are with the old .76 Hboot. My old evo was stolen on the 10th of dec and I got a brand new replacement Hardware 004 With the new Hboot 2.10.0001 Rooted and went back to Cyanogen couple days ago now that the new hardware is supported. Any word or development on If and or when we will be able to downgrade? I know the partitions Layout is different which is why some people here are left with bricked phones (Lmao) Always read the OP always.... Anywho thanks again and always.
[EVO 4G Android Development] snandlal:
Yes extended fastboot commands with hardware 0004 would be sweet. Anyone know anything bout this task?