yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] joeykrim:
First off, great job to the OP! Appreciate the time and willinginess it takes to risk your device in performing alllll these tests and dangerous methods with unknown outcomes.

Can't thank the OP enough!

have yet to hear of my tool not working. if so, please post up in my thread and not clutter this one! in fact, if you didn't have a boot loop before using the tool, but have one after wards, as you indicate, then you know my tool properly flashed the kernel, but either the kernel isn't compatiable with the device OR isn't compatiable with the ROM!

Hard to say how far into the RUU the device is loading the files, at least based on all the feedback so far.

At this point in the discovery, to be safe, would recommend using RUU's specific to your carrier. If the current directions are correct, you'll need an RUU containing a bootloader compatible with HTC unlock to initially load and then an older RUU with a bootloader from prior to the HTC unlock feature. Also, will need to adjust to at least or less than the main version to the software version of the prior/older RUU.

That is all based on the assumption this process works, which there haven't been success stories, YET.

Hope that helps illustrate the steps which would need to be modified for other carriers. As more information comes out, this might change.

I also had this same understanding. The most surprising part of this process, in my opinion, is the bootloader will flash any PG86IMG.zip in the root of the sdcard after the PG86IMG.zip file has passed the security check. From a security stand point, would make a lot more sense to copy to a secure location, then verify, then prompt.

Although, anything is possible and perhaps HTC changed their bootloader code in newer versions and "overlooked" this previous security "feature"?

Hope to see more success stories! This will be incredible news!

Seems at this point, we're in need of more testers to verify this process is consistently working and iron out the bugs. If anybody is having issues, hope they post up the issues so we can work together to resolve them!
[HTC EVO 3D] Unknownforce:
Yes, start with a "valid" zip with an Hboot that would normally flash... then swap the card to another "valid" zip, but with an hboot that is of a lesser version and it will attempt to flash it and go kaboom.

There are a few ways to identify the hboot, the best way is to temp root, and do a adb shell dd if=/dev/block/mmcblk0pXX of=/sdcard/blah.img (XX is the number of the partition from 0 all the way to like 40 or something... you'll have to go through one by one till you find it, but look around someone can probably tell you which one it truly is) Then open that img file with a hex editor, it's jumbled, but you'll be able to make out something that says HBOOT SPL and the version of the hboot. Which is near the very top of the hexdump.
[HTC EVO 3D] con247:
Most of us are already perma-rooted with the official HTC unlock. Will that wrench anything? Someone is gonna try it soon I think and I want to make them as informed as possible.
[HTC EVO 3D] d0cx:
so... has anyone actually succeeded on doing this?
[HTC EVO 3D] Unknownforce:
I don't believe so, but I suggest flashing back to stock 2.17 first before starting. (that's what I started with)
[HTC EVO 3D] Unknownforce:
Other than myself, I haven't seen anyone say that it's worked for them yet. stay tuned, tonight I'm going to Re-1.5-S-ON my phone and then make a video on this, showing exactly what I did. It seems like people aren't getting the brick to happen.
[HTC EVO 3D] con247:
Well that doesn't apply to us... we don't have 2.17 RUU. We have a 1.x and a 2.x. So we will be forcing the Rezound to attempt a hboot downgrade of 2.11 to 2.10
[HTC EVO 3D] Unknownforce:
Right, sorry, kind of doing 15 things at once here (I'm at work at the moment)

But same concept. take the higher valid one first, let it check it, then swap to the lower one.
[HTC EVO 3D] con247:
Ok. If someone tries it I will post info about it here.
[HTC EVO 3D] doeboy711:
I'm in as well on trying it out when a windows or Mac method is made. I am a noob when it comes to Linux. But, when a windows/mac method comes out, I will be definitely trying this out. Thanks for all of your hard work on making this happen!
[HTC EVO 3D] Evil Bob:
And just when I had given up hope and thought that HTC had finally come up with a bulletproof method of enforcing HBOOT. This is simply awesome!

My son had to replace his 1.3 HBOOT phone with the ****ty 1.5 when his screen died, it was a sad day to use the HTC unlock.

I'm also liking the idea of this being un-brickable in most situations, makes me want to play with it more.
[HTC EVO 3D] monkey3ddd:
Ok, pardon my ignorance, as I am a newb, but what would be my motivation to downgrade? I am at 1.5 and the htc unlock, I can flash roms and kernels.

Right now I DO have to jump through a few hoops, but not too bad. I just want to know my options..

Not trying to thread crap, in fact congrats!
[HTC EVO 3D] powduh09:
Nothing wrong with staying at 1.50, this just eliminates the need for flashimagegui app or for fastbooting recovery from pc to flash kernels, and let's you flash splash screens...
[HTC EVO 3D] trentreed:
Would this work on a Mac as well?
[HTC EVO 3D] dgomez720:
It gives you full control of your device once again!! Muahahaha!!!
[HTC EVO 3D] Unknownforce:
S-OFF grants the ability to flash anything, to anywhere, with no restriction, with HTC Unlock, you're still S-ON, which, you cannot flash radios, other hboots, splash screens and several other things. Basically HTC Unlock is just a little more limited in it's capabilities. For most people, HTC Unlock works just fine, All they want is superuser(root) and a different rom, but for the more advanced/heavy flashers, it's much better to have S-OFF, it unlocks everything.

Also, if you were not HTC Unlocked already, I would say the main motivation would be to maintain your warranty under any circumstance, because with this, they don't have your serial number on file, nor can they tell it's been rooted. But with HTC Unlock, they now have your serial number on file that sprint most likely has access to and can simply look it up :)
[HTC EVO 3D] kMogs17:
Unknownforce, Crackanug, and the entire Revolutionary team -- thank you. you are gods and this could not have come at a more perfect time. i recently had to bring my phone in to get the touch screen replaced and i told them not to update it because i didnt want to be ****ed over with hboot 1.5 and they said "OK" and then when i got it back it was updated! and i was like WTF!!!!! and argued with them for about an hour and got nowhere. and now you have releases this! thank you once again! XD
[HTC EVO 3D] anothen:
well that's just depressing lol- I didn't even think about the code posting to htcdev was my serial number. derrrr.... Hoping we can figure this out regardless for the Rezound!
[HTC EVO 3D] Unknownforce:
Ok, it seems that many people are having issues Bricking the device (Step two) So, again, I'm going to re-up my phone and re-lock it and start from scratch tonight, I will record my every step and upload the video when done, It's possible I've overlooked something here, it's ALSO possible that my sd cards are in some way special... Unfortunately I cannot do this until tonight because I'm at work until 5 PM CST. But, I shouldn't have anything stopping me from going straight home and doing this tonight.
[HTC EVO 3D] kMogs17:
Thanks i plan on using your method tonight too so any additional info you can provide is greatly appreciated
[HTC EVO 3D] mustang_52:
ok this may sound dumb but now that im downgraded and ran the 1.13 ruu, how do i know whats safe to run without updating the hboot? can I run something like meanrom now?
[HTC EVO 3D] mpgrimm2:
Make sure you run xhausx's 2.17.651.5 Radio update (no Hboot 1.50 in zip):

Firmware

w/o hBoot

, System, Boot and Recovery partitions. (Must be S-OFF)

http://xdaforums.com/showpost.php?p=21441428&postcount=403

MD5: 25442C4C8EDDD628391FA6E3CD9924B0

I've read that you should check any "update/radio" files (look inside the zip) to verify that there isn't an Hboot 1.50 file included. But once your S-Off, your always S-Off (I think).

- Remember to make backups

- Once your radio is up to date, you can flash any 2.17 based ROM like MeanRom, No More Fastboot! I'm on MR 2.9 & Athx rls04 now. (had issues restoring my TWRP 2.0 backup, but flashed rom/kernel fine from fresh wipe. Went back to CWM 5 Touch).
[HTC EVO 3D] mustang_52:
Thanks so much. Got it flashed!
[HTC EVO 3D] z50king:
Do we know if the upcoming ICS updates will fix this 'security issue' that allows us to downgrade?
[HTC EVO 3D] Unknownforce:
Do WE know? No. We don't, no-one but HTC knows that, since it's not released yet...

What we do know is that this is a hardware thing that is most likely in place for THEIR use. I don't they would remove the feature itself, as it would eliminate the ability to recovery a bricked device on their end.

However, there are a few things I could think of right off the top that they could do to patch it, but there's no need to publicly announce them unless they actually patch them. :D
[HTC EVO 3D] Jim M:
I can't "Brick" my phone, after it loads and checks the PG86IMG.zip it just goes back, it doesn't ask if I want to update.

Any help would be great.
[HTC EVO 3D] ptran:
Same thing happened to me. Was a bad download for some reason, although didn't appear that way when I downloaded it. Check the md5sum and cross reference to make sure.
[HTC EVO 3D] z50king:
I was asking because phones are getting OTAs with ICS in other countries. I heard the sensation got it in parts of Europe. I'm just hoping they don't get it fixed so if I need a replacement I can do this method when it comes with 1.5

You sir, are a gentleman and a scholar
[HTC EVO 3D] Unknownforce:
See the FAQ in post #2.
[HTC EVO 3D] johnsonjs:
Is the dim red light the only indicator that the phone is "bricked", other than it will not boot into the bootloader?

I successfully downgraded and ran the 1.13 RUU but dumbsh!t me took all of the OTA updates and it put me back on 1.5 HBOOT ... so now I'm on my second go 'round with this.

The first time I easily bricked it when I was HTC relocked, running a 2.17-based ROM and using the 2.08 RUU zip to load in bootloader.
[HTC EVO 3D] Unknownforce:
Read the new guide and read the FAQ, I explain the process a little more in detail and I think I found why people were having issues with timing.
[HTC EVO 3D] Will32:
So you downgraded to get s-off, then you took an ota, right? Are you still s-off? Just curious, I've read that you stay s-off but id like to hear it from someone that took the ota.
[HTC EVO 3D] .Elite_The_King.:
So you say in the video that we need to be 2.08 so we wont have problems running the 1.13 ruu or is cool just running it off 2.17. The phone has never been htcdev unlock but it is on 2.17. Ima bout to try this later on tonight. I have everything I need just asking to confirmed this thanks Unknownforce.:D
[HTC EVO 3D] Genesis Nova:
2.17 works just fine, use the 2.17 rom.zip from the RUU, rename it PG86IMG.zip(if windows isnt hiding extensions don't want .zip.zip) and you're ready for the brick part. Did it myself on 2.17.
[HTC EVO 3D] johnsonjs:
Thank you UNF! Oddly enough, I "bricked" then ran closeone's program to emmc_recover and my phone booted right into the stock 2.17 ROM I had installed, with HBOOT 1.4, with no need to run the 1.13 RUU :)

---------- Post added at 07:27 PM ---------- Previous post was at 07:24 PM ----------

Went from S-OFF to ON. After downgrading to 1.4 and then running the 1.13 RUU I took ALL of the OTA's (3 or 4 I think) and not sure which one ... probably the final one changed my HBOOT to 1.5 S-ON :(

Successfully downgraded again, though.
[HTC EVO 3D] KL45SiiK:
when i put the 2.17 ruu zip on my sd it reads the zip but doesn't tell me to update??

Can anyone help?

EDIT: It was a bad download..
[HTC EVO 3D] closeone:
Just out of curiosity, why run the 1.13 executable? Back when I did it, I had placed the zipped up version on my SD card and then run the RUU from the bootloader. Did something change that I missed? Oops.

By the way, if you get a chance to look at it, does the updated FAQ in my thread look sound?

~co~
[HTC EVO 3D] Will32:
Ok, 1 more question... After downgrading the first time, you ran revolutionary, correct? Did revolutionary go all the way through for you, did it install cwm?
[HTC EVO 3D] johnsonjs:
No, I did not run revolutionary after downgrading. I'm not sure if that had anything to do with my HBOOT changing from 1.4 to 1.5 taking the OTA's ... but I was S-ON the entire time...
[HTC EVO 3D] ccaudio1:
REV will give you S-Off, thats why you were still S-On
[HTC EVO 3D] Will32:
Ah, I see now, thanks for explaining. Your hboot should change to 1.5 with the 2.08 or 2.17 ota whether you're s-on or s-off. But the s-off is "supposed" to stick even through hboot upgrades. But I haven't done it myself and haven't had someone that actually took the 2.17 confirm that for me.
[HTC EVO 3D] johnsonjs:
Well, now I can't get Revolutionary to root my phone. I'm on S/W #2.17.651.5 and HBOOT 1.4 and have tried rooting at least 10 times, with no luck :(

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

Waiting for device...

Found your device: PG86100 (shooter-1.40.0000, Android: 2.3.4, ROM version: 2.17

.651.5)

This is a beta release and requires a beta release key.

Please visit: http://revolutionary.io for more information.

Enter beta key [ serial: xxxxxxxxxxxx ]: xxxxxxxxxxxxxxxxxxxx

Beta key accepted - thank you for participating!

Zerging Root... this might take a minute or so.. Failed to get Root! :(

Press (almost) any key to exit.
[HTC EVO 3D] Will32:
You have to do it while on 1.13

Edit. I think you need to change your main version to run the 1.13. I can't tell you how to do it. It was in the op.

Actually, I think if you change your main version, you wouldn't need to run the ruu. You could just run revolutionary.
[HTC EVO 3D] .Elite_The_King.:
You're suppose to run the 1.13 RUU.exe so it puts you back to a stock rom to be able to run revolutionary that 1.13 is the hboot which why you did the whole process to be able to run that hboot to get s-off.

Youre still on hboot 1.5 but its just says hboot 1.4 until you run the 1.13 ruu.exe that the whole process of emmc, < it allows you to run the hboot 1.40
[HTC EVO 3D] johnsonjs:
Yeah, strangely enough, after bricking ... then downgrading to HBOOT 1.4, my phone booted just fine into the existing 2.17 stock ROM I had installed. The 1.13 RUU won't run either ... it gives me an Error [140] Bootloader version error. Guess I have to run the 2.17 RUU and start all over again...
[HTC EVO 3D] .Elite_The_King.:
Yeah I don't think you were supposed to boot up after you ran the 1.13 ruu
[HTC EVO 3D] king_89:
Gotta finish the process from OP also make sure usb debugging is checked on ur phone and uninstall htc sync on pc if you have installed good luck
[HTC EVO 3D] Unknownforce:
You should just re-run the 2.17 ruu to bring back to full stock and start from scratch... Not sure why you went back to 2.17 after downgrading...
[HTC EVO 3D] closeone:
And, to add to this, if you really want practically stock 2.17, check out Mr.Esp's ROMs. I have not personally tried them, so I cannot vouch for them, but they seem to be well received.

Also. Remember. DO NOT TAKE OTAs. DON'T TAKE OTAs. NO NO OTA! They will likely end up bringing you back to HBOOT 1.50. /endFriendlyReminder :)

Also, it's a good idea to complete all of the steps in the OP before doing anything with your phone.

~co~
[HTC EVO 3D] Jim M:
Well, I've been trying to brick my phone for quite a while now, as soon as I hit the volume up button it starts:

{Bootloader}-unzipping (real fast),

{Bootloader}-installing (real fast) and if I wait a few seconds it already has moved on through to

{Boot}-unzipping

{Boot}-installing

So where would I need to pull the power plug, in Bootloader installing or Boot installing?

Please help :(
[HTC EVO 3D] Unknownforce:
Wait 2 full minutes before pressing vol up to update, and then press update, count to 5 and pull AC
[HTC EVO 3D] Jim M:
@Unknownforce, I'll give it a shot, but in watching your video your phone has not passed through the installing Bootloader installation, if I am seeing it correctly.

Trying again, and I have been pulling the battery after plugging the power in, waiting a while with the battery out.
[HTC EVO 3D] Unknownforce:
You'll get it, it just takes patience and the right timing.
[HTC EVO 3D] banccalif:
ive followed all steps in the op, and successfully bricked my device but im stuck on the 1st step of linux. i plug in holding vol down and it just waits there doing nothing. any insight would be much appreciated
[HTC EVO 3D] Unknownforce:
Put your battery back in and try to boot to bootloader, does it boot?
[HTC EVO 3D] banccalif:
omfg yea it does.. repeating steps to brick again. after ACTUALLY bricking it, how long will it take for the terminal to locate the phone and begin writing?
[HTC EVO 3D] Unknownforce:
Only takes seconds
[HTC EVO 3D] b1gsby_02:
To brick my device, I let it detect the zip, wait til it gets to the screen where it asks you to update, wait a full minute, plug in ac power, and pull the battery out 2 seconds after plugging in. Then 5 seconds after pulling the battery, I started the update. Counted to 4 seconds then unplugged...you want to pull the power cord right before it finishes updating the bootloader. On my device it would finish updating the bootloader at the 4-5 second mark....so counting to 5 wouldn't work for me, lol. Hope this helps.
[HTC EVO 3D] Unknownforce:
Correct, waiting the 2 minutes I believe is what helps it delay the bootloader flashing slightly enough to match what my video represents.
[HTC EVO 3D] banccalif:
got it all complete! hboot 1.4 thanks Unkownforce.. with the 1.13 should i allow it to boot after running the ruu? or battery pull and run revolutionary?
[HTC EVO 3D] Unknownforce:
Revolutionary requires the device to be booted to work properly.
[HTC EVO 3D] banccalif:
gotcha much appreciated on the speedy responses
[HTC EVO 3D] Unknownforce:
No problem, glad it worked!
[HTC EVO 3D] eyeisdasteve:
Before i bricked my phone i wanted to make sure the linux part would work.

Am i doing something wrong? I thought i typed it correctly and i have root prompt (#)

I know this is updated but i figured i'd go the old school way. haha :D

any help?

EDIT: Will the linux part not do anything unless my phone is bricked? Shouldn't it try to atleast do something? haha. so confused.
[HTC EVO 3D] Unknownforce:
Please tell me this is a joke, cause... there surely isn't a linux app out there that downgrades your hboot lol...

Let me rephrase that... there isn't one that you can use apt-get to downgrade with... haha...

You need to copy the files to that linux PC and do exactly as it says in step 2.
[HTC EVO 3D] Unknownforce:
And on top of that... emmc_recover is the old tool... get yourself a copy of the new one... and follow the new guide...
[HTC EVO 3D] eyeisdasteve:
lol. yes. that part was a joke. hahaha.

i tried even using the downgrade command. even that wouldn't work. said permission is denied. but I had root in terminal.
[HTC EVO 3D] Semantics:
Where does one find "the new guide"? The OP says updated 3/21/2012, it appears.

I think its amazing what you have accomplished here, but its confusing as all hell trying to figure out what is going on between this thread and the toolkit one. I can't make heads nor tails of it. At least you have a guide, the live cd toolkit has no instruction at all that I can find.
[HTC EVO 3D] .Elite_The_King.:
The guide has gotten pretty easy

-Download files

-copy your stock ruu to the sd card

-run the ruu on the sdcard

-wait 2 minutes then flash it

-brick it

-run the the downgrade tool in the linux environment

-then exe the 1.13 RUU

-boot up the 1.13

-Revolutionary to get s-off

-Update radios

-Start flashing ROMS

Its pretty simple
[HTC EVO 3D] closeone:
Semantics, I am working on a guide for my Live CD. My first priority has been making sure that I get a stable piece of software out before anything.

The Live CD Toolkit used right after you brick the device. If you are HTCDev unlocked and have a custom ROM installed, there are instructions in the FAQ in my thread as to what to do. If not, go ahead and download the 2.17 RUU from here. Place it on your SD-Card making sure to rename it to PG86IMG.zip. Continue with Step 2 of Unknownforce's directions for bricking the device.

After you have the device bricked, make sure that the battery is out of the device. If you decide to use my CD, boot up into the environment. Open a Terminal window. Type in the command 'downgrade'. Press Enter three times until it says that it's waiting for a device. Now, holding the Volume down key the entire time, plug the phone into the computer. The command window should spring to life. "Foundit!" and should exit with a return code of 0.

Finally. You can reboot your computer back into Windows. Grab the 1.13 EXE RUU from here and run it from Windows.

Once done. Boot up the phone. Go to http://revolutionary.io and get the Revolutionary unlock download, and also get your unlock key.

You will need to run Revolutionary three times. The third time, the bootloader should show -Revolutionary- at the top.

Now, just flash a Recovery image like TWRP or Clockworkmod while booted into the bootloader. Use the command fastboot flash recovery [NAMEOFYOURRECOVERYHERE].img.

You should be done with the downgrade part of the downgrade. ;) What you do afterwards is up to you. Have fun. :) I would install a custom ROM, or you could use one of Mr.Esp's Rooted Stock ROMs if you want to stay with as much stock as possible. These will not "upgrade" your bootloader to 1.5. Make sure to make a backup inside your recovery before and after you flash the new ROM, just in case. Just make sure that if you are asked to do an OTA (Over the air) update, that you ignore it. You will likely end up back on HBOOT 1.5 again.

~co~

.Elite_The_King. beat me to the punch by a couple of minutes. ;)
[HTC EVO 3D] nicksimmons336:
I have tried 4 or 5 different 2.17 RUUs and everyone of them have ran through and never give me the option to update. my phone is 2.08 so do i need to be using the 2.08 ruu or are the downloads im using messed up?
[HTC EVO 3D] miggsr:
I just re-locked my bootloader the issue I have is it now say *Relocked* instead of *Locked* is there a way to get it to say *Locked*..... Any ideas or recommendations
[HTC EVO 3D] uh60james:
I am having the exact same problem, it acts like its loading it at then it just goes back to fastboot. Tried to flash 2.08 and it wont let me since it's older than the installed version. Surely someone else has had this happen and figured it out.
[HTC EVO 3D] HooliganAMA:
Great success!

Took 2 hours to find an RUU zip that I had the option to install.

5 tries to brick the phone.

4 tries with revolutionary.

I am officially downgraded and s-off.

Thanks so much!
[HTC EVO 3D] b1gsby_02:
That isn't an issue...it's supposed to say re-locked. You can now move forward and brick your device.
[HTC EVO 3D] Jim M:
Well, after finally bricking my phone (I had to unplug immediately when it starts the update), I never got a dim light either, I then ran Closeone's Live CD Tool, remember to leave the battery out.

Ran the 1.13 RUU

Now I only ran revolutionary once, but after it ran it says

-Revolutionary-

SHOOTER XC SHIP S-OFF RL

HBOOT-140.1100

RADIO-0.97.10.0530

eMMC-boot

Jun 8 2011, 17:20:22

My question - Do I really need to run Revolutionary 3 times?

I know it won't hurt, but it looks fully rooted to me at this point

EDIT - LOL, I started to run Revolutionary again and the program says "Your device is already S-OFF, what exactly do you think you're doing, blah blah blah...

Then it just asks if I want to download CWMod recovery?

Guess I all done, thanks a million to everyone that made this possible!!!!!!
[HTC EVO 3D] Warboy:
I got to step 3 in the linux part where I needed to plugin the phone a 2nd time, I unplugged, hit enter and nothing happen. Terminal just sat there and didn't say to plug the phone back in. What should I do?