yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] thefredelement:
Find out your hardware version: From the home screen, (on a sense based ROM) go to menu > settings > about phone > hardware information, if you're phone is hw 004 don't even read this thread.

First of all, Thank You Joeykrim - I've been trying to do this forever (2 days) and my evo is so much happier now. You're awesome and Evo owners with BS hboots thank you.

DISCLAIMER: IF YOUR PHONE EXPLODES THAT SUCKS AND I'M SORRY BUT IT'S NOT MY FAULT, THERE'S ALWAYS A CHANCE ANYTHING CAN GO WRONG

If you're doing this on late hardware models 003/004 (with new partitions) then you should stop reading now and probably not do it. I'm not sure if the new recovery can fix up your stuff after you do this

This should also work on 2.02 hboots but I haven't tried it yet, please confirm if you give it a shot, if not I'll make another PC36IMG.zip just for you 2.02ers.

Second of all:

THIS WILL HURT YOUR PHONE (TEMPORARILY) - YOU NEED TO HAVE A RECOVERY INSTALLED BEFORE YOU DO THIS! YOU WILL NEED TO RE-INSTALL (NOT NANDROID) YOUR ROM! THEN RE-FLASH RECOVERY AND THEN RESTORE A NANDROID, YOU CAN PROBABLY DO THIS ALL IN BOOTLOADER BUT HERE'S WHAT I DID:

1) you have to be S-OFF, so at one point in time if you're on hboot 2.10 you would have needed to flash unrevoked-forever.zip, if you're not there yet follow this and get there: http://xdaforums.com/showthread.php?t=829045

2) There are two files attached to this post: PC36IMG_210-76.zip - You need to rename this file to: PC36IMG.zip - This file is a hex edited version of the .76 hboot, it's been changed to 2.10 to fake the Evo in to accepting the update. The other file is the original .76 hboot in a zip that you can install via recovery.

Your first step, copy PC36IMG_210-76.zip to your SDCARD, rename it PC36IMG.zip, also at the same time copy Evo_hboot_0.76.2000.zip to your sdcard.

Second step, reboot in to fastboot, choose bootloader, when asked, apply the update, third step, hit NO to reboot your phone, select Recovery, from recovery go to install zip and pick the Evo_hboot_0.76.2000.zip. Reboot to complete the installation.

Next Step: My phone at this point, only booted straight to fastboot, I went to recovery and installed a nandroid and it didn't work so I had to install cm6.1.1 from scratch, reflash clockworkmod (was using RA) and then restore a different nandroid. - That is the long way home but when I got there I had my rom and hboot .76!
[EVO 4G Android Development] thefredelement:
reserved for faq, updates, new versions, etc...
[EVO 4G Android Development] hammysink:
I had to learn how to do this the hard way, a guide is a very nice thing. Thanks for posting it up.
[EVO 4G Android Development] snandlal:
Will this work with hardware 0004??
[EVO 4G Android Development] thefredelement:
I'm not sure, if it does please let me know and I'll update the post.
[EVO 4G Android Development] snandlal:
Man I wanna do this so bad but last time I tried downgrading hboot with zikronixs modified 2.02.0001, it erased half of my partitions and created badblocks. That phone has no use now. I'm just weary. Did joeykrim modify the hboot?
[EVO 4G Android Development] leenypost:
Why do you want to do it so badly? Do you actually use the extra commands 0.76 enables during hboot? If not there is no difference between any hboot so long as you're rooted.
[EVO 4G Android Development] thefredelement:
I modified the hboot and this is exactly what I did:

I opened hboot image for 2.10, next to it I opened hboot image .76, I searched for the text string for each (2.10 & .76) and found them, they were right at the start of the file.

So in the .76 file - I just changed it to 2.10.(whatever the last 4 digits were), saved the file, zipped it as a pc3img.zip file, put it on my sd card and went to boot loader to update and it worked just like that.

It was Joey's idea for the hex edit as I've been trying to force open hboot through fastboot or any other way with no success.
[EVO 4G Android Development] leenypost:
Also, if your phone came with hboot 2.10 I would not install clockwork. It would be much safer to install the newest edited Amon-ra recovery that can be found in the thread that zikronix made as a guide to rooting hboot 2.02 & 2.10 phones.
[EVO 4G Android Development] leenypost:
You are a brave man, kudos to you!
[EVO 4G Android Development] thefredelement:
I think this is a hw v004 thing, as I've fully updated to 2.10 with the RUU on 003 hw and was able to break it all back down again - we even compared partition sizes between a .97 hboot and 2.10 and they were exactly the same. (weren't able to find anyone on hw004 to compare with)
[EVO 4G Android Development] snandlal:
So do you think the hardware 0004 will run safely on .76 hboot?
[EVO 4G Android Development] thefredelement:
Probably you'll just have to re-install your ROM but it's impossible for me to tell, if you want to get a list of your partition sizes for comparison from adb shell type:

and compare with my hw 003 results:

- even that being said I don't think anyone will know until it's tried. If you're close to a sprint store and have an account in good standing, go for it!! It's got 'til next June for it's 1 year warranty - lol, but seriously.
[EVO 4G Android Development] leenypost:
Yes that is correct. It is a hardware 004 thing but it dies also apply to sone late made 003 phones as well. As a general precaution I would advise anyone that has the new camera not to install clockwork and Im highly uncertain that this will work on anyones phones that came preinstalled with 2.10 or posdibly 2.02 as well because those are the phones that have the different partitions. If you upgraded to those from an earlier hboot your partitions would not change, however if you purchased your phone with one if those hboots already I would advise extreme caution in attempting this.
[EVO 4G Android Development] thefredelement:
I just wonder if they'll have to re-install their rom and just not be able to write anything, I put up another thread asking someone on hw4 to get a list of their partitions and post them up.
[EVO 4G Android Development] snandlal:
My cat /proc/partitions shows no loop or dm partitions. Also mtd1 shows 640, mtd3 shows 3072, and mtd6 shows 437888. All others are the same. Except mmc of course. I guess ill hold off on this. Hardware 0004.
[EVO 4G Android Development] xHausx:
It seems like they are mixed, I've talked to some people who had 003s with the newer partitions and some have 004s with the older set up. An easy way to tell is to cat /proc/mtd. The older config has an erase size of 20000 while the new ones are 40000.

Edit: More info can be found here

http://xdaforums.com/showthread.php?t=843342
[EVO 4G Android Development] nemesys504:
@ thefredelement

Well this was a good starting point for me. I have a ver 003 evo and updated the hboot to 2.10 and had to root my phone using the latest method which made me flash the latest 3.70 ruu.

One problem I ran into was after I flashed the pc36img.zip you included, I could not boot into recovery and was stuck at the white HTC bootscreen. Tried a few more times to boot into recovery with no luck. My remedy to this problem was to remove my sdcard and used my laptop's card reader to remove the pc36img.zip from the card and loaded the pc36img.zip from this thread which flashes the .76 hboot and amon ra's 1.7.0.1 recovery. I booted into bootloader and flashed that pc36img.zip and everything was smooth sailing from there. I am now back on .76 hboot with no bad blocks or broken partitions. This may be a big YMMV thing but it was worth the risk for me.

So my steps were to flash your pc36img.zip, power off, remove sd card and insert into a card reader, remove your pc36img.zip file, load the pc36img.zip from this thread to the card, re-insert card to phone, boot into bootloader, flash then reboot. Again you will need unrevoked s-on for this work but this could not have worked without your hex edited hboot file. THANK YOU!
[EVO 4G Android Development] Igotsanevo4g:
Sweet.

Should help promote general welfare. ;)
[EVO 4G Android Development] jostrander:
HW04 HBOOT 2.10, Originally came with 2.02, used latest PC36IMG to update after a horrible accident.

# cat /proc/partitions

cat /proc/partitions

major minor #blocks name

31 0 12288 mtdblock0

31 1 1024 mtdblock1

31 2 4608 mtdblock2

31 3 3328 mtdblock3

31 4 358400 mtdblock4

31 5 163840 mtdblock5

31 6 436224 mtdblock6

179 0 7761920 mmcblk0

7 9 15360 loop9
[EVO 4G Android Development] billodell:
I have hw 0004 but I have the old partitions :-) downgraded yesterday with no problems, thanks!!!
[EVO 4G Android Development] cordell12:
I just did mine, hardware 003 20k partitions. It went so smooth and fast I thought something was wrong! lol

Thanks

EDIT...Do I need to re-install my nandroid of stock sense to get my RSA keys restored for WiMax?

TY
[EVO 4G Android Development] jrgutier:
So I think I went thru this wrong, and I ran an RUU before reading through all this thread... I'm getting a "Model ID incorrect! Update Fail!" whenever I try to update using any PC36IMG.zip. Help!
[EVO 4G Android Development] jrgutier:
I was able to get it to get it to at least read the PC36IMG.zip by doing the following commands in fastboot.

fastboot oem changeCid SPCS_001

fastboot oem writemid PC3610000

fastboot oem writebcid SPCS_001

fastboot oem writeserialno HTXXXXXXXXXX

I'm still unable to revert back to a stock HBOOT, leave the bootloader, or write to any partition except the radio.
[EVO 4G Android Development] snandlal:
U getting bad blocks?
[EVO 4G Android Development] thefredelement:
What RUU did you run?
[EVO 4G Android Development] jrgutier:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe

Right now it's stuck at the HTC RUU splash screen, and I'm getting Fail-PU on everything except RADIO_V2 and SYSTEM.
[EVO 4G Android Development] pnoy40785:
Am I bricked to the point of no return??

Here's what I did:

1. Rooted via unrevoked3 reflash.exe

2. placed the PC36IMG_210-76.zip in the root of my SD card, renamed it to PC36IMG.zip like the instructions said.

3. Placed the Evo_hboot_0.76.2000.zip in the root of the SD card

4. Rebooted into bootloader and applied the update

5. After, I selected "no" to reboot phone, and selected "recovery" and installed Evo_hboot_0.76.2000.zip. Rebooted to complete installation.

ALL Downhill from here on out. Ever since that last step, I just get a single vibration pulse with no screen response at all upon trying to power it on. Plugged in the computer, upon looking in device manager, it reads the phone as "Android USB"

Here's what I've tried so far;

1. Official RUU.exe - Gets stuck at "rebooting into bootloader" and eventually a usb connection error

2. ADB - "no device"

3. Pulled out the SD card and placed the extracted rom.zip (from official RUU), renamed it PC36IMG.zip - didn't work either becuase it simply does not boot up to anything.

Every single time same response, single vibration pulse...that's it...screen stays off.. After leaving it alone for a while, plugged in the charger and got a charging LED, but when I try to power it on, you guessed it, same vibration pulse and charging LED goes off.

Here's my device info:

Hardware version 003

Software Version 3.26

Radio 2.15

Didn't check my partitions in adb to see if I had the new or old ones. I may have found out the hard way that I have the new ones.

Any input or advice greatly appreciated.
[EVO 4G Android Development] xHausx:
give this a try and see if it will let you flash any of the partitions afterward,

fastboot -n 4096

edit: sorry, actually meant to quote jrgrutier. This should help if your phone has the new block sizes but it sounds like there is more to it with your phone pnoy
[EVO 4G Android Development] snandlal:
Same problem. Your serial no shows as 123456789012 huh? You will get bad block errors. There isnt any fix yet. Probably be some kind of .exe to fix this, besides ruu. Yes it gets stuck at rebooting into bootloader. This is a known problem but not too well known. Sum helped a member on irc awhile back with no success. I have this same paper weight, but maybe someone one day will have a fix
[EVO 4G Android Development] pnoy40785:
Where'd you see the serial no? lol I didn't even get that far...
[EVO 4G Android Development] jrgutier:
Still no dice.

fastboot.exe -n 4096 flash hboot hboot_2.10.0001.img

sending 'hboot' (512 KB)... OKAY [ 0.328s]

writing 'hboot'... FAILED (remote: image update error)

finished. total time: 0.625s

fastboot.exe -n 2048 flash hboot hboot_2.10.0001.img

sending 'hboot' (512 KB)... OKAY [ 0.313s]

writing 'hboot'... FAILED (remote: image update error)

finished. total time: 0.625s

This is my partition table:

fastboot oem listpartition

INFO[radio]:(OTHER) block start=0, size=497 (0 KB)

INFO[hboot]:(RAW) block start=497, size=6 (768 KB)

INFO[misc3]:(RAW) block start=503, size=7 (896 KB)

INFO[mfg]:(RAW) block start=510, size=6 (768 KB)

INFO[sp1]:(RAW) block start=516, size=9 (1152 KB)

INFO[wifi]:(RAW) block start=525, size=5 (640 KB)

INFO[recovery]:(RAW) block start=530, size=40 (5120 KB)

INFO[boot]:(RAW) block start=570, size=20 (2560 KB)

INFO[system]:(YAFFS) block start=590, size=2800 (369600 KB)

INFO[cache]:(YAFFS) block start=3390, size=1280 (168960 KB)

INFO[userdata]:(YAFFS) block start=4670, size=3421 (451572 KB)

INFO[wimax]:(RAW) block start=8091, size=96 (12288 KB)

INFO[misc]:(RAW) block start=8187, size=5 (640 KB)

INFO[rcdata]:(OTHER) block start=0, size=0 (0 KB)

INFO[cpld]:(OTHER) block start=0, size=0 (0 KB)

INFO[microp]:(OTHER) block start=0, size=0 (0 KB)

INFO[a1026]:(OTHER) block start=0, size=0 (0 KB)

INFO[tp]:(OTHER) block start=0, size=0 (0 KB)

INFO[nv]:(OTHER) block start=0, size=0 (0 KB)

OKAY [ 0.078s]

finished. total time: 0.078s
[EVO 4G Android Development] snandlal:
Same exact as above. Damn HTC! Go and make partitions self destruct
[EVO 4G Android Development] xHausx:
Did you try flashing anything beside the hboot? I wouldn't worry about that at this point, youre going to want to keep the fastboot commands.

Right now your best bet is to leave the hboot and the radio be.
[EVO 4G Android Development] theoner1:
I understand with HBoot 0.76 you'll have full access to fastboot and all, but are there any other benefit in having HBoot 0.76 over newer HBoot 2.10?

My old Evo (rip poor thing) got run over when I drop it and had Hboot 0.76 on it all along while rooting it via Toast method but never really have the need to use fastboot. Now I got a replacement comes with Hboot 2.10 but with old partition (able to downgrade to 0.76).

My question is after rooting it with xHausx Universal Auto Root (thank you sir).

Is it worth it to downgrade to the Hboot to 0.76 with my replacement phone (comes with old partition) or just leave it since I don't use fastboot anyways.

Thought I'd ask to see what others are benefiting from downgrading to 0.76 Hboot. Thanks in adavce.
[EVO 4G Android Development] jay7264:
i also have a paper weight

i willgive this paper weight to some unlucky soul that lives in longisland im so pissed off at this thing. i had to come out of pocket and pay for it it was a customers
[EVO 4G Android Development] jay7264:
Never mind I threw it out the window on i495 stupid htc
[EVO 4G Android Development] danielt14:
THANK YOU FOR THIS!!!!!!!!!!!!!!

Like a dumb ass i updated to the 2.10... And now i am good THANK YOU!!!!
[EVO 4G Android Development] aaanadie:
Hello,

My hboot do not recognize PC36IMG.zip because I have a 16gb sdcard with compatibility issues, everything works perfect except this.

I have HBoot_2.10.0001, I reflashed from RA 2.3 but still same issue.

Any fix? or any alternate way to flash PC36IMG.zip files? I do not want to go back to my 8gb sdcard.

Thanks in advance for your help.
[EVO 4G Android Development] :
Uhm, why don't you just use your good 8GB card to do this downgrade, and then go back to your bad 16GB card?
[EVO 4G Android Development] aaanadie:
I put my old 8gb class 2 card on my evo with PC36IMG.zip file (wake up fix from other forum), went hboot, no problem this time flashing file, turned phone off, put my new 16gb class 6 again, boot normally on CM7 nightly #104, everything seems to be ok, I checked calls, msg, cameras, hdmi.

Thank you very much.
[EVO 4G Android Development] github:
FWIW, I was able to do this on HBOOT 2.16.0001 (I was/have been s-off, so don't get all excited) and get back to 0.76 HBOOT to get my fastboot commands back. I just downloaded the modified HBOOT and updated the android-info.txt to the current version and then hexedited the HBOOT header to match (2.16.0001).

If this has worked for you in the past (going back to 0.76 hboot) then it can work for you again. I'm not going to post my modified file because this is pretty risky and such only people who know what they are doing should attempt.
[EVO 4G Android Development] ckoadiyn:
damn i was going to ask you to post it haha
[EVO 4G Android Development] m4f1050:
I can't get my EVO's digitizer to work with hboot .76 and older boot, the phone boots but I can't use the touchscreen... :(

With newer boot the phone boots into bootloader...

Here is a PC36IMG.zip with hboot.76, older boot and amon-RA v2.3
[EVO 4G Android Development] :
have anyone tried this on hw 0003 or 0004. just wanted an update.
[EVO 4G Android Development] mattykinsx:
Pretty sure its been said if you have the new partitions (which newer 003 and 004s have) doing this will brick the phone.
[EVO 4G Android Development] Lacedaemon:
Perfection!

This worked perfectly on my Evo and I was successfully able to flash a custom boot splash screen through fastboot. Thanks to thefredelement for this amazing guide!

The only problems I ran into however is that I didn't have any other nandroids to restore from, as my only one would restore successfully but boot me straight back to fastboot. I had to install MIUI 1.11.11 from scratch and rebuild from there. After installing most of my root apps again, I made another nandroid backup with the same recovery--Amon Ra 3.08. Should I make a nandroid with CWM or the recovery right now is fine? Because I don't want to mod it, then restore my nandroid only to find it's jack...

---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------

My Evo is hw 0003 and no problems so far. I read, earlier in this thread I think, that some hw 0003 and 0004 ship with the same partitions as the old ones. I guess I'm one of the lucky ones but I'd say go ahead and try it. ;)
[EVO 4G Android Development] mrc1330:
Destroyed

I think i just destroyed my phone doing this..

i think its a 0004 (MicroP-041F

It was Hboot 2.10

was already rooted and S-off and on SprintLovers...

Followed steps to the "t" and now NOTHING.. no RUU will work, NO PC36IMG will work.

With PC36IMG files i get a FAIL-PU with ALL items except MICROP and system and sometimes RADIO...

Once it fails i press RECOVERY and it stays on the "skateboarders"...

I tried to REDO the process with the 1st PC36IMG file and still same result.

Can someone please tell me how to fix this issue...
[EVO 4G Android Development] snandlal:
Its hungry hippo time! I knew this was no good for hardware 0004.
[EVO 4G Android Development] snandlal:
So....? Did you fix it??
[EVO 4G Android Development] thefredelement:
What is your hboot version on that screen?

If you're on .76 or if it says 2.10 but ENG then from adb do:

fastboot flash recovery recovery.img

with recovery.img being a recovery image file, since you're on 004, i would get this out of the pc36img.zip recovery file at the BOTTOM of this thread: http://xdaforums.com/showthread.php?t=829045

The problem you're most likely having is that the new hboot re-did some partition info on the 004 hardware and it can't write to any of the partitions through the bootloader. Get that recovery up.

After it's up format all of your partitions, and re-install your ROM via recovery.
[EVO 4G Android Development] khshapiro:
+1 on what he said
[EVO 4G Android Development] josh4trunks:
Same thing happened to me exactly. I'm gonna try the comment two above mine and see if this fixes it. hopefully I'll atleast still be rooted after this.

BTW for the thread starter I tried this on newer hardware. (Not sure where to find out the number) and started with 2.02 and used the s-off thread. As of currently I can't boot into recovery.

I need to stop messing with my phones as I'm running out of excuses to tell my girlfriend why I can't call her, lol

==============

BTW thefredelement/khshapiro I was able to 7zip the recovery.img out/put it into adb folder

I was wondering

-what do I boot into / command do I do?

I turned my phone on with just power button to a white screen that says

SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36*****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04

FASTBOOT USB

<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item

BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN

+ " adb flash recovery recovery.img " - isn't working

+ also clicking on recovery doesn't seem to do anything, I'm not sure what I gotta do to run the commands (getting device not found in windows command shell), or what command exactly to run

If you guys can can you help me out I would be very great-full, Thanks
[EVO 4G Android Development] leenypost:
Works fine on 003 hw with old camera chip.
[EVO 4G Android Development] Karadorde:
Freeza and I worked together on a similiar thread awhile back. It has since been buried in the Dev Forum and doesn't come up much. Merely posting it here as a reference for all and to make myself feel important :D. Don't know if it will help out but I figure it is better to have a lot of information on the subject rather than not enough.

ENG bootloader (0.76 needed for CM6) extended fastboot commands
[EVO 4G Android Development] josh4trunks:
Thanks for the reply, so no adb in command line. Where do I wanna go on my evo menu to run fastboot commands? I can't get into recovery right now...
[EVO 4G Android Development] Karadorde:
For lack of a better explanation, Fastboot commands are like ADB commands. Both are used in the Command Prompt/Terminal. The .76.2 HBOOT is what allows you to use the Fastboot commands in Command Prompt/Terminal for stuff like flashing splash screens.
[EVO 4G Android Development] josh4trunks:
Hmm, I wonder what hboot I have... I had 2.02, tried to use this guide to go to 0.76, but now my screen says 2.10 (as seen above). So does that mean I can't use fastboot commands because my hboot say 2.10 (even though it only says that cause of this guide)?

I hope my EVO isn't bricked, only had it for a day lol. Wow I suck.

Anyways to see if fastboot commands work? I tried being in adb directory and running fastboot and that obviously didn't work, I'm guessing I need something else to run fastboot commands? Thanks for all your help.

_______________________

So I tried finding hboot 0.76 (and tried uncompressing the hboot_0.76.2000 file attached to this thread), I'm guessing I need and exe cause I just keep getting " 'fastboot' is not recognized as an internal or external command..."
[EVO 4G Android Development] Karadorde:
If it doesn't say .76.2 then I would say you don't have .76.2. I am not entirely sure how this guide works though, so I may not be fully comprehending what you are saying. My apologies.

It is not bricked. Do not worry.

And you are absolutely correct. You will need the Fastboot executable in order to use the commands. I haven't looked, but it should be easy to find.
[EVO 4G Android Development] josh4trunks:
Lol so I went even deeper in the rabbit hole, went from 2.02 to 2.10, lol. K, I'm not to worried. Thanks for your help, I'm gonna just keep looking around/ waiting for help.
[EVO 4G Android Development] thefredelement:
You should be using:

not ADB flash - as when you're stuck on fastboot only fastboot commands will work.

You currently have the ENG hboot loaded (it says on the top line ENG) but it's the version that was made to fake the Evo in to thinking it's 2.10 - so you're just one step away really!
[EVO 4G Android Development] thefredelement:
You're really on .76, it just says 2.10 so the Evo would accept the update.