[SUPERCID] Ancient Method (Worthless) - Sprint HTC EVO 4G LTE

I give credit to DesignGears for finding this for the HTC One X. So be sure to give him thanks for his find!
SuperCID will allow ruu'ing back and forth from newer to older builds and vice versa.
ADDED- WILL NOT ALLOW FLASHING OF RUU WITH OLDER HBOOT VERSIONS.
Added- great explanation of supercid benefits http://forum.xda-developers.com/showthread.php?t=1548083
Please follow the instructions VERY carefully as any error in the process can and very easily WILL BRICK YOUR DEVICE. I am in no way recommending this procedure and am not responsible for any device damaged from the following guide.
It's not very difficult if you just follow instructions, so don't be discouraged from the warnings, just pay attention
Pre-requisites -
Rooted HTC EVO 4g LTE
Pc with working HTC drivers
Adb and general knowledge of use
Fastboot and general knowledge of
use.
USB debugging enabled
A hex editor on your pc for modifying the partition we are going to pull(HxD is free on cnet)
2ND WARNING-
This procedure will be modifying a partition and pushing it back to device. If modified incorrectly it WILL BRICK your device.
Plug device into pc and select charge only on the device
Open up your command prompt and cd to your folder with adb and fastboot.
Type -
adb shell
Su
You should now see
"[email protected]: #"
Next we are going to take a copy of partition and save to the external sdcard
Type -
dd if=/dev/block/mmcblk0p4 of=/sdcard2/mmcblk0p4
Hit enter, should get a readout of
2+0 records in
2+0 records out
You now have a copy of partition 4 saved on external sd.
Type - exit, then exit again and you should now be in your fastboot/adb dir. In your command prompt. Minimize the window don't close, we'll be right back.
Now mount your phone as disk drive and open your sdcard on your pc. You will see a file on it named mmcblk0p4. Copy and paste a copy to your pc desktop.
Once copied, right click and go to properties, and WRITE DOWN THE SIZE OF THE FILE,
Should be 1,024 bytes.
after we modify the partition the modified one must be IDENTICAL in size or there's 100% chance of brick when push it back to the device.
Now, open the file mmcblk0p4 in your hex editor
Scroll to offset 00000210, you will see
"...SPCS_001XXXX" X's being 4 numbers we arent going to touch.
ANOTHER WARNING-
Here's where you need to be extremely careful,
we are going to change
"SPCS_001" to. "11111111"
best way to do this is highlight ONLY "SPCS_001" then press "1" eight times, so your replacing 8 characters with eight 1's. Now the full line looks like
"...11111111xxxx".
Three dots before the "1" and four numbers after the last "1". Most likely being 9900.
ADDED- Pic of b4 and after hex edit
http://db.tt/ziScPZBl
Now go to >file>save as and name the file mmcblk0p4MOD and save it to desktop.
Open your external sdcard folder again on pc and put a copy of your new mmcblk0p4MOD in there. Right click it, properties and verify it is the same size as the original. Go back and mount phone as charge only.
14th WARNING:
Hope u followed closely, if you made a mistake here's where u brick!
Maximize your command prompt window from earlier and type-
adb shell
Su
You'll be back at the [email protected] command prompt
Type-
dd if=/sdcard2/mmcblk0p4MOD of=/dev/block/mmcblk0p4
Hit enter and you should get the same readout from before-
2+0 records in
2+0 records out
Your all done, now to confirm you have superCID type exit, then exit again then
Adb reboot bootloader
Once in bootloader type-
Fastboot oem readcid
Readout should say
INFOcid: 11111111
Confirmed, you were successful. You SHOULD now be able to run any ruu a available for the device, enjoy and don't forget to hit THANKS
Sorry if all the warnings are annoying but I don't want any "you bricked my phone, help!" Posts

---

So this would benefit those who took the OTA while they were S-on (on accident) and want to be S-off now?
Sent from my EVO using xda app-developers app

---

I had 4 dots before the first 1

---

I haven't followed closely to the new ota problems, but if they can still root after the ota, then yes they should be able to ruu back to the previous firmware.
Good, Bad and EVO

---

As long as you replace the 8 characters with eight 1's you will be fine. will post a b4 and after pic of the hex edit in OP,
Pic Added!!
Good, Bad and EVO

---

This is fascinating. Thanks for bringing it to us, I'm sure this will help a couple people out.

---

This is interesting.
I wonder if this would allow me to RUU back to the 1.13 ROM? The error I got was due to the HBOOT version being too old. Would SuperCID somehow allow this?
I guess there's only one way to find out . . .

---

This should allow you to ruu, any firmware for the device
Good, Bad and EVO

---

18th.abn said:
This should allow you to ruu, any firmware for the device
Good, Bad and EVO
Click to expand...
Click to collapse
Well, great instructions & walkthrough. I was able to do this painlessly.
Now I'm trying to flash an RUU. Let's see what happens!

---

Added a link in op that explains well the benefits of supercid
Good, Bad and EVO

---

is it wrong that I love you? I had to get a new lte from sprint and the guy there did the ota as part of activation. happy there is a way back

---

18th.abn said:
Added a link in op that explains well the benefits of supercid
Good, Bad and EVO
Click to expand...
Click to collapse
Well, here's the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like the 1.15 HBOOT is SuperCID-proof .
It's the same error I got when I tried to flash the PJ75IMG. The main version wasn't an issue, but the HBOOT version apparently prevents the RUU from running.

---

Dang, sorry its not letting you. Supercid let's all cid verifications pass allowing flashing of any firmware, but I guess if it has a older hboot, it kills the deal. Will edit op that it won't downgrade hboot versions.
Good, Bad and EVO

---

So if I understand this correctly since we took the ota and have the new hotboot with s-on we still screwed for now. has anyone tried to run the lazy panda after doing this on the post supercid current hotboot
rockin my EVO 4G LTE

---

Yes, seems that way. Click the link in op about benefits of supercid. It explains it really well.
Good, Bad and EVO

---

motcher41 said:
So if I understand this correctly since we took the ota and have the new hotboot with s-on we still screwed for now. has anyone tried to run the lazy panda after doing this on the post supercid current hotboot
rockin my EVO 4G LTE
Click to expand...
Click to collapse
That would be me, two posts up.

---

Captain_Throwback said:
That would be me, two posts up.
Click to expand...
Click to collapse
Didn't see anything about lazypanda saw it was ruu proof still. But I guess that must be a yes we screwed still. I never take ota updates but never thought soff woulda been locked worse then before Thanks for the info
rockin my EVO 4G LTE

---

Has the new ota hboot blocked lazy panda? Is this confirmed?

---

{ParanoiA} said:
Has the new ota hboot blocked lazy panda? Is this confirmed?
Click to expand...
Click to collapse
Yes, confirmed. The lazy panda dev's are working on an updated tool.

---

Once again, this is why you NEVER accept an OTA while rooted or planning to root.
I understand captn took one for the team here, but everyone else shame on you.
:fingerwag: