[HTC EVO 3D] Unknownforce:
First, Thanks to everyone that helped me along the way here... The thanks list is in Post #2 :)

Second, The risk obviously here is your own. This tool is provided AS IS, and I am not providing any warranty or guarantee. So it doesn't cover hail damage to your home, Tornado's taking your dog away, or your phone not working properly after using it... (or anything else that you might try to pin on me ;) )

For all of the processes, linux is required... use your own flavor of linux and use the following to set it up:

Extract the files to somewhere (home folder works best)

Gain a root command prompt (# instead of $) (sudo -s works for most)

Set permissions via "chmod 755 ultimate" (possibly 0755 depending on linux flavor)

Then run the tool using ./ultimate

/=================================================================\
|*******************************************************************|
|****************** EVO 3D Ultimate Recovery Tool ******************|
|*************************** Version 3.1 ***************************|
|*******************************************************************|
| |
| Please Select an Option |
| |
| 1. Create a backup partition from a bricked device |
| 2. Flash a custom partition to a bricked device |
| 3. Downgrade HBOOT |
| 4. Unbrick |
| 5. VM Radio Fix (CDMA ONLY!) |
| 6. Fix radio partition (Manual Radio Fix only) (CDMA ONLY!) |
| 7. Exit |
| |
| |
|*******************************************************************|
|**************** Copyright (C) 2013, Unknownforce *****************|
|*******************************************************************|
\=================================================================/

Latest version is

Here.

(3/14/13)

- URTLiveCD 1.0 is available Here -> http://d-h.st/blY

Recent Updates:

3.1

Added additional check for the misc partition detection

3.0

Fixed and re-implemented VM Radio Fix

3.0 ALPHA

Completely Redesigned and Re-Written

New menu interface

Removed the need for hboot/misc image files to be present, they are now embedded in the program and used as necessary

CID issue fixed for GSM devices

Misc detection implemented

GSM/CDMA detection implemented

Fixed a few missing things from the VM Radio Fix (CDMA Only)

Many minor bug fixes

2.5.1

Mistakenly used an older source of URT when coding 2.5, so I re-applied changes from 2.5 to the correct source and re-compiled. (No Difference for GSM, only radio fix was affected.)

2.5

Added support for GSM EVO 3D's! (add -g or --gsm)

No longer beta or RC or alpha or whatever!

Minor cleanup/optimization.

2.3 RC1

Fixed the ghost MEID issues. (This will not fix devices that got it from the first test, please contact me and I'll work with you to fix that)

Fixed some delays and timing in switching between fastboot and adb

Corrected some wording.

2.2 RC4

Second attempt at fixing output errors... Sorry :/

2.2 RC3

Attempt to fix "sh: 1: Syntax error: Bad fd number" error.

Add -f switch to attempt to fix I/O errors on possibly bad sectored emmc's (This will require being in a temp bricked state before using, if this successfully recovers them, I can add this into the process of the radio fix, for now I want to see if it's going to work at all, so it's a manual process for now, to brick device, Be S-OFF, flash custom hboot(anything but stock) and do fastboot oem writesecureflag 3, done) This is ONLY for those having I/O errors when trying to flash radio config. The usage is ./ultimate -f 19 (19 is partition 19/radio_config)

2.2 RC2

Fixed device detection at first step

Logging to log.txt

Fixed device "wait" after rebooting to system, it will now check properly that there is a device to reboot before issuing the command, rather than just rely on time.

2.2 RC1

Initial release to public

Radio Fix​

Requirements:

1.13 (or 2.08) Stock Unrooted Rom. (MUST be stock, signed, unrooted, yadda yadda, RUU, or otherwise) - 1.13 Link - Mirror

S-OFF

ENG Hboot - Link

VM Firmware (duh) - Link

2.17 Firmware - Link

Ultimate Recovery Tool (Listed above, also included on the URTLiveCD)

Very basic Linux Experience (Helps, but not necessary if you use the URTLiveCD)

A PC (duh)

Functional device (The device does not have to be on an active plan, but it must currently have a functional radio/signal, Just keep in mind if it doesn't have a plan to it, it will continually try to Hands Free Activate after this process)

Instructions:

1.)

First, Backup your current Partition 19, to do this, use the following commands (root required, or do from custom recovery):

adb shell dd if=/dev/block/mmcblk0p19 of=/sdcard/current19.img
adb pull /sdcard/current19.img

2.)

Flash ALL of the following, IN THE ORDER LISTED... There are several Flashes here,

After each flash

you will need to let it boot all the way to the home screen, every flash, other than hboot, will wipe the data on the device, so it will take some time for each one, and you'll have to go through the normal device setup each time as well. Just get it to the home screen each time.

First - Flash 1.13 Stock

Second - Flash VM Firmware

Third - Flash 2.17 Firmware

Fourth - Flash ENG Hboot

3.)

After this you're ready for the tool. Enable USB Debugging on the device. (Applications, Development, USB Debugging) and then boot up to linux and start ultimate or boot to the URTLiveCD, select the option for VM Radio Fix.

Follow the onscreen instructions to the letter, Plug in device when asked, unplug when asked, etc etc. Here is an example output, there are a couple other possibilities, but this is a standard output.

When it starts up, you will see it list out the device type, bootloader version, MEID, and ROM version, make sure these show up correctly.

It will then root the device and pull some more information it needs and then prompt with a message about whether or not you would like to fix rfg_1 (if it finds that it's invalid, it will not ask this and just go right into rebuilding it) if it asks, just tell it not to rebuild, as most of the time it does correctly read that rfg_1 is valid or not.

After it does this, it will reboot the device into bootloader, erase the current RFG_1, flash the fixed RFG_1, erase rfg_5 and flash rcdata.

It then reboots to fastboot once more and writes the secure flag to brick the device. After this it will ask you to unplug the device and remove the battery. Do exactly that, tell it yes to continue, and then plug it in when asked. (without the battery in)

It will reflash the partition and then do the unbrick process.

After it finishes everything properly. You will boot up, it will reboot once while booting up the first time (Normal, security flag toggling causes this) The second time it boots up it will do a Hands Free Activation. Let it go through and do this and the PRL update as well. (if you're on a plan, if not, just press cancel)

Then you will want to re-S-OFF of course so, revolutionary it. This will break activation again. But no matter, let it activate once more.

After that you should be good to go!

Downgrade/Unbrick​

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!!!

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...

Linux and basic linux knowledge (not necessary if you use the URTLiveCD)

This PG86IMG file -> http://d-h.st/3p8 (the bootloader update package)

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 ultimate3.0.zip in the link above or the URTLiveCD

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

(If you're already bricked, start from Step 2)

First Step

VIDEO OF STEP 1 (video says Step 2, but just start here)

[YOUTUBE]YwKduHoIh5w[/YOUTUBE]

VIDEO OF THE WHOLE PROCESS: (Using Battery Pull method)

[YOUTUBE]3v9Y5ZZ2s1c[/YOUTUBE]

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.

(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)

(If you are HTC Unlocked, you MUST RELOCK BEFORE starting)

1.) Take your PG86IMG file from above, put it on the root of your SDCard.

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. Do not press Update yet.

3.) Here you can do one of two things, the first being a little more easier than that second... (See Videos for examples)

3A.) The battery pull. You can interrupt the flash by pulling the battery at the right time. Tell the device to update, Pull off the battery cover (careful not to let the battery fall out) and then watch the screen and pull the battery out during or just before the orange bar shows up during the BOOTLOADER Updating.

3B.) The power pull. You can also do this by using the power cord to kill the power. Pull off the battery cover (again careful not to drop the battery out right away) then plug the device into AC power. Now pull the battery out. Tell it to update and pull the power cord at the right time.

The "right time" is different for all devices. The idea here is to completely interrupt the hboot flash so that it's corrupt. The best thing to do is to watch for the bar in the upper right hand corner, it will only show for a second (or even shorter)

If done correctly, you can plug in the device (to power or USB) and see the charge light very dim. It will need to be SOLID dim, NOT blinking dim.

The main indications that it worked correctly:

The device no longer turns on at all, no bootloader, no boot screen, nothing.

The SOLID, not blinking, dim light mentioned above.

The charge light no longer lights up when plugged in with a battery.

The device, when plugged into a windows PC, shows up as QHSUSB_DLOAD. (And MMC Storage Controller for the first 5 seconds)

The device is now bricked and ready for the next part.

Second Step

Video above shows this as well.

The next step is the linux part.

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

1.) Boot up to Linux (if you use URTLiveCD, skip to step 6)

2.) Extract your ultimate.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 ultimate (if it's not in your home folder, add the full path to it)

5.) Type ./ultimate and press Enter.

6.) Select option for Downgrade HBOOT.

You will see the below output:

IMPORTANT: Do not plug in device until TOLD to do so.

Downgrade selected.

Ready to begin? (y/n):

Type y and press Enter.

Then you will see:

Plug in your device now.
Waiting for device...

[/CODE]

Now... plug the phone in and leave it plugged in, you should see something similar to the below:

Device Found!
Locating misc partition...
Misc found at partition 34.
Changing misc version...
Writing image file...
SUCCESS!

Flashing hboot and unbricking...
Writing image file...
SUCCESS!

All tasks Completed Successfully! Put your battery back in and boot up!

Press Enter to return to the main menu.

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.

DISCLAIMER

This 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.