UPDATE 3/21/12

DO NOT BRICK YOUR DEVICE IF YOU ARE S-OFF, THE DEVICE WILL NOT GO INTO EMMC MODE AS EXPECTED, AND YOU WILL HAVE A TRUE BRICK IN YOUR HANDS!!!

A linux PC and some very basic linux knowledge...

The 2.17 RUU ZIP image

You'll also need the 1.13 RUU EXE (All the RUU's can be found here -> http://www.filefactory.com/f/4ef0ef536face67a/)

Download the downgrade.zip in the attachment (includes downgrade tool, hboot 1.40.0000(hboot.img), and misc.img)

Backup your apps/data if you need to, this process will wipe EVERYTHING

closeone has posted a "all in one" Tool to do much of the following. (No, it's not a one click, there likely won't be a one click using this method, don't ask about it)

First Step

(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)

(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)

(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)

Second Step

Do not plug your phone in to the linux box until you are told to do so.

Code: ==== Original emmc_recover tool written by Fuses ==== ==== Downgrade v 1.0, written by Unknownforce ==== Ready to Downgrade? Press ENTER for yes, or Press Ctrl+C for no.

Code: Step 1... Plug in Device while holding down Volume Down key... Waiting for device...

Code: Found the Correct Device! Writing image file! 511+1 records in 511+1 records out 1047808 bytes (1.0 MB) copied, 0.36689 s, 2.9 MB/s SUCCESS! Step 2... Unplug the device now. AFTER device is removed, press Enter to proceed to next step.

Code: Step 3... Plug the device back in while holding the Volume Down key again. Waiting for device...

Code: Writing image file! 511+1 records in 511+1 records out 1047808 bytes (1.0 MB) copied, 0.36689 s, 2.9 MB/s SUCCESS!

DISCLAIMER

Firstly, I want to thank the guys that made it all possible...MOVZXRussianBearFusesDexter93TrevECrackanugcloseoneUSSENTERNCC1701EjcaseThe entire Revolutionary teamNow on to the goodies...If you're already S-OFF, but on 1.50, you can do one of two things... I have attached the PG86IMG.zip with the 1.40 bootloader on it, download it copy to sd card and flash via bootloader.The other option is to simply re-run 1.13 RUU, this will downgrade it as well, but this will also erase all data in the process.For S-ON... Things you'll need...(If you're already bricked, start from Step 2)I have not personally tested it, but the idea is sound and if he's done it correctly it should work just fine, If you wish to try it, it is here (Yes, it still uses Linux, but on a bootable CD) -> http://forum.xda-developers.com/show....php?t=1563342 VIDEO OF STEP 1 (video says Step 2, but just start here)BRICK (Yes, I said brick) your device. BUT in a CERTAIN way.You need to brick your device by corrupting the HBOOT during the HBOOT Update.(If you are HTC Unlocked, you MUST RELOCK BEFORE starting)1.) Take your 2.17 ZIP image, put it on the root of your SDCard, call it PG86IMG.zip.2.) With the phone on Battery power alone, Reboot to BootLoader, let it detect the zip and read and get to the point where it wants you to press Vol-Up to update.3.) LET THE DEVICE SIT FOR AT LEAST a Minute or Two.4.) Pull off the battery cover (careful not to let the battery fall out) and plug the device into AC power. (HTC Power charger, other chargers have been known not to work for this, the reason for this is that the HTC's power adapters output more power than the standard ones.)5.) Pull the battery out. (The device should stay on, if it doesn't, start over and try again) Also, leave the battery out through the REST OF THIS GUIDE until told to put it back in.6.) Here's the tricky part, Read this a couple times, be ready to pull the ac cable out at the right time... press the vol up key in, Give it approximately 5 seconds from the START of it saying the word "Updating" next to Bootloader (The very first one it flashes) Then Pull the charger cord promptly, and plug it right back in, if this worked right, you'll see the red charge light be VERY(VERY VERY) DIM, and it should stay solid for the most part. (See the FAQ in post 2 for more info on this step, if you're having issues.)The device is now bricked and ready for the next part.VIDEO OF STEP 2 (Removed for now, it's outdated)The next step is the linux part.1.) Boot up to Linux (I used Ubuntu, but I am guessing that any Linux OS will work)2.) Extract your downgrade.zip file to the linux PC, Home folder is the best spot and is the easiest to work with.3.) Open up Terminal, gain root, (su, or sudo -s)(give it your password)4.) Run the command chmod 755 downgrade (if it's not in your home folder, add the full path to it)5.) Type ./downgrade and press Enter.You will see the below output:Press Enter here, then you'll get the following:Now... Hold down the Volume Down key, (and keep holding it down) and plug the phone in, you should see something similar to the below:Unplug the device, and press Enter again, you will see the following:Plug the device in again holding down the Volume Down key the entire time again, you should see the following:From there, pull your SD Card out (so it doesn't try to update from the PG86IMG.zip...) throw your battery back in, boot up to bootloader. 1.40.0000(Some people have said that they needed to "let the device sit" for a few minutes here, mine works immediately every time, YMMV)To get back to a bootable rom and revolutionary, select FASTBOOT, connect it to the PC and run the 1.13 RUU EXE all the way through, (NOT the zip) then just revolutionary (a few times) and have a beer.A few side notes:When you run Revolutionary, you might have to do it a few times... I also didn't get to the point where it asked to flash a recovery... so I did this via fastboot, and simply used TWRP 2.0 .img file.Use fastboot flash recovery blahblahblah.img -- this did NOT work when it was just regular 1.40.0000 S-OFF, only when it was revolutionary 1.40.1100 S-OFFThis is NOT a guarantee... because I'm sure it could come back... But in basic terms... I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE, I have given you a method that worked for me, and SHOULD work for you, but if your house burns down, your car gets a flat tire, or your phone stops working... You are responsible for any and all of those things.