[TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade HBOOT)

Search This thread

Unknownforce

Retired Recognized Developer
Nov 18, 2008
2,044
4,268
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:

  1. Extract the files to somewhere (home folder works best)
  2. Gain a root command prompt (# instead of $) (sudo -s works for most)
  3. Set permissions via "chmod 755 ultimate" (possibly 0755 depending on linux flavor)
  4. Then run the tool using ./ultimate
Code:
 /=================================================================\
|*******************************************************************|
|****************** 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 (This includes URT 3.0)

Recent Updates:

3.1
  • Added another check to 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
  • Removed Radio Fix for now, some bug I can't figure out yet... Meh
  • Fixed a few missing things from the VM Radio Fix (CDMA Only) (when 3.0 is Final)
  • 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


Radio Fix is for CDMA ONLY!
See the CDMA Thread -> here


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 a higher version of hboot, you can just downgrade via a sdcard PG86IMG containing the lower hboot, being S-OFF will let it flash anything ;)

For the S-ON Downgrade... Things you'll need...

  • Linux and basic linux knowledge (not necessary if you use the URTLiveCD)
  • The RUU ZIP image that MATCHES your current ROM version
  • You'll also need the 1.20 or 1.22 RUU EXE (All the RUU's can be found here -> http://www.filefactory.com/f/4ef0ef536face67a/)
  • Download the ultimate3.0.zip listed above or the URTLiveCD if you do not have linux
  • Backup your apps/data if you need to, this process will wipe EVERYTHING

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

(3/12/13 - PENDING UPDATE
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/showthread.php?t=1563342

First Step

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


VIDEO OF ENTIRE PROCESS (Done with the battery pull method and on a CDMA device)


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 ZIP image from your CURRENT ROM RUU, 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. 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:

Code:
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:

Code:
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:

Code:
Device Found!
Locating misc partition...
Misc found at partition 31.
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.49.0007 :)

(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.20 or 1.22 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.
 
Last edited:

Unknownforce

Retired Recognized Developer
Nov 18, 2008
2,044
4,268
The Thanks List!

MOVZX
RussianBear
Fuses
Dexter93
TrevE
Crackanug
closeone
USSENTERNCC1701E
jcase
agrabren
chad.goodman
wwjoshdew
The Fer-Shiz-Nizzle
jlechner
The entire Revolutionary team
And pedja1 for getting me the info I needed to get the GSM port done! :)

FAQ's

Can I do this on Windows?

Currently there is no way to do this on Windows. It's unlikely that there will be a way to do it on windows, Windows USB is too slow and doesn't detect the device the same as Linux does.

Can I do this in (Insert virtual PC software)?

The only one I've heard that works is VMWare, however You're again relying on Windows to pass the device to a virtual machine, which isn't ideal. I know for a fact that VirtualBox does not work, and Cygwin also does not work.

Common Errors

I can't get my phone to brick, I've tried a million times!

Patience is a virtue. This step is the hardest part of all, HTC Designed their phone to be brick proof for a reason. I believe the trick here is to let the device sit on the update screen for a minute or two, then do the update and count out 5 seconds. Also there's the update bar that appears in the upper right hand corner, much like the bar that is there when it's checking the zip file before the update prompt. The INSTANT you see that, pull the power. This is typically 5-6 seconds after it says updating, but only after it's been sitting for a bit... I believe the trick is to let it sit for a bit before pressing Volume up to update.

My PG86IMG.zip is not detected or the phone checks it and it doesn't prompt me to update it

There are several possibilities:

  • The phone is HTC Unlocked - You must re-lock.
  • The phone is S-OFF - Don't even try to brick it because you'll permanently brick it.
  • The phone is Re-locked, but still has a custom rom/recovery on it. - This will show a security warning and not allow the PG86IMG.zip to be flashed. - You must put the phone in FASTBOOT USB and run the RUU exe that matches your software version.
  • The File is not named correctly, it's PG86IMG.zip (Make sure it's not PG86IMG.zip.zip)
  • The PG86IMG.zip is either corrupt, not signed properly, or modified in some way. - Download another one.

I press Volume up to Update, and my phone shuts off

  • First make sure you're using a standard HTC A/C Adapter and cable. These are designed to charge at 1000 mA, other manufacturer's chargers typically only hit 900 mA. The phone needs it all to stay on and update properly without the battery in.
  • Second, make sure you're not using a higher end SD Card. This will draw too much power and not let the phone update when it comes to that time because the power drain to have the screen on, the sd card powered and the update running is more than what the A/C adapter can output. - My 16GB Class 10, shuts the phone off, my Class 4, 2 GB, does not. YMMV.
  • Third, if you're stuck with the high end SD card, or think it could be the cause, simply pull it after you pull the battery and BEFORE you press volume Up to update. The phone will still update. However, I don't know if this affects the speed of the update at all... so just watch it the first time and time it, then time your pull accordingly.

I'm getting Permission Denied when trying to run the linux commands

You don't have root, either type su or sudo -s, your prompt should have a # at the end and not a $.
Or, you didn't set the chmod correctly on the ultimate file. This is again chmod 755 ultimate (or /path/to/ultimate)

I get Misc image is missing!!! or HBOOT image is missing!!! or Recovery image is missing!!!

The hboot.img and misc.img and recovery.img files must be in the same location as the ultimate file, they are hard coded into the ultimate tool to be in the same location, their names are also hard coded, so don't rename them.

I'm getting Error 16 after running the radio fix.

This can happen, there are two things, most likely it goes away after attempting to place a few calls. If it doesn't, just remain on the line, and they can fix the problem for you.
 
Last edited:

ramjet73

Senior Member
Jan 12, 2006
9,191
9,654
Honolulu, Hawaii
I hope the GSM users appreciate the significance of this thread. By working together on porting this tool for the GSM model, unknownforce and pedja1 have made it possible for those of you who have gotten motherboard replacements and can't use the htcdev unlock to get S-OFF and root your phones without the need for that. :)

Essentially, this is an alternative to the JuopunutBear wire trick that does not require an unlocked bootloader as a prerequisite.

ramjet73
 

Unknownforce

Retired Recognized Developer
Nov 18, 2008
2,044
4,268
I hope the GSM users appreciate the significance of this thread. By working together on porting this tool for the GSM model, unknownforce and pedja1 have made it possible for those of you who have gotten motherboard replacements and can't use the htcdev unlock to get S-OFF and root your phones without the need for that. :)

Essentially, this is an alternative to the JuopunutBear wire trick that does not require an unlocked bootloader as a prerequisite.

ramjet73

Oh yes, thanks to pedja1. Definitely a perfect test subject. :)

I'm also going to look into another method of temp-bricking the device, that doesn't require special timing or anything, more of a one-click smash and flash. But that will have to wait until I get my old EVO 3D back in a few days hopefully, when I can start testing on it.

It will be nice to be able to test without it being tied to my own number, Having a second phone is so helpful. :p
 

Unknownforce

Retired Recognized Developer
Nov 18, 2008
2,044
4,268
Here's a little preview of 3.0 ;)
 

Attachments

  • 3.0preview.JPG
    3.0preview.JPG
    59.1 KB · Views: 1,387

zemaniel

Member
Mar 30, 2009
38
8
Decin
To get back to a bootable rom and revolutionary, select FASTBOOT, connect it to the PC and run the 1.20 or 1.22 RUU EXE all the way through, (NOT the zip) then just revolutionary (a few times) and have a beer. :)

If you make only RUU to 1.20, then phone start normaly, but with ICS, no IMEI and random reboot. Must do flash 1.20 like PG86IMG. Then all OK. I had this.

---------- Post added at 04:06 AM ---------- Previous post was at 04:02 AM ----------

Here's a little preview of 3.0 ;)

Windows version? :)
 

Unknownforce

Retired Recognized Developer
Nov 18, 2008
2,044
4,268
If you make only RUU to 1.20, then phone start normaly, but with ICS, no IMEI and random reboot. Must do flash 1.20 like PG86IMG. Then all OK. I had this.

Oh, yes the first time you RUU might not fully flash everything the first time, you might have to do it a couple times.

Windows version? :)

Not possible, unfortunately. :(
 
Last edited:
D

Deleted member 4303594

Guest
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)

A small observation.
Originally ( on ICS before downgrade) my misc partition was 32
After I downgraded to gingerbread with ruu, last partition is 31.

ICS = 32
GB = 31
Whichever last(official ruu or pg86img) you flashed tells you your misc partition

Sent from my HTC EVO 3D X515m using Tapatalk 2
 

ray650128

Member
Mar 10, 2008
9
0
Taipei
I very want to unlock my phone, but my motherboard has replace.
So I can't unlock by HTCDev.com...
Does any GSM users can use this tool downgrade 1.53.0007 to 1.49.0007?
 

Unknownforce

Retired Recognized Developer
Nov 18, 2008
2,044
4,268
I very want to unlock my phone, but my motherboard has replace.
So I can't unlock by HTCDev.com...
Does any GSM users can use this tool downgrade 1.53.0007 to 1.49.0007?

Yes, this will work for just about any version of hboot, you just need the RUU zip image from your ROM you currently are on.
 

ray650128

Member
Mar 10, 2008
9
0
Taipei
My CID is HTC__621. But now I type "fastboot getvar cid" command , it show CID is 0202.
Then I type "fastboot oem readcid" command, it show "HTC__621"
But it can't flash "1.20.401.8 PG86IMG" to my phone...(3.28.709.3 too)
 

Unknownforce

Retired Recognized Developer
Nov 18, 2008
2,044
4,268
My CID is HTC__621. But now I type "fastboot getvar cid" command , it show CID is 0202.
Then I type "fastboot oem readcid" command, it show "HTC__621"
But it can't flash "1.20.401.8 PG86IMG" to my phone...(3.28.709.3 too)

Have you tried the RUU EXE while in fastboot USB?
 

zemaniel

Member
Mar 30, 2009
38
8
Decin
Thank you very much!
I use your tool success downgrade to 1.49.0007.
But now my CID is HTC__621. I can't flash GB rom.
How can I do?

I successfully performed the procedure using URT 2.5.1.
After this I flash PG86IMG.ZIP RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed
where HBoot is 1.49.0007. (using phone botloader)

Then use Revolutionary without Recovery flash - now phone REVOLUTIONARY-HBoot 1.49.0007-S-OFF

Then From PC use RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed - now phone is LOCKED-HBoot 1.53.0007-S-OFF

Then flash PG86IMG.ZIP 4EXT (using phone botloader)

Then from 4EXT flash root-OTA-ICS.zip (using phone botloader and recovery)

All OK. Phone rooted, CID_032. Original CID was also 032. No problem. Check with app CID GETTER from GPlay
 
Last edited:

Unknownforce

Retired Recognized Developer
Nov 18, 2008
2,044
4,268
I successfully performed the procedure using URT 2.5.1.
After this I flash PG86IMG.ZIP RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed
where HBoot is 1.49.0007. (using phone botloader)

Then use Revolutionary without Recovery flash - now phone REVOLUTIONARY-HBoot 1.49.0007-S-OFF

Then From PC use RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed - now phone is LOCKED-HBoot 1.53.0007-S-OFF

Then flash PG86IMG.ZIP 4EXT (using phone botloader)

Then from 4EXT flash root-OTA-ICS.zip (using phone botloader and recovery)

All OK. Phone rooted, CID_032. Original CID was also 032. No problem. Check with app CID GETTER from GPlay

OK, so I have a couple confirmed working... but it still doesn't sit right with me that it's not reading the CID correctly.

I'm pretty sure I know why it might have happened (the misc partition stores the CID I believe...) but I can't explain why it didn't happen for some. But I've also fixed that possibility as well in version 3.0.

Anyways, I'm leaving the link down for now, as I don't want anyone else to damage their phone this way.

I'm working on 3.0 right now, which is coming along nicely I might add. I simplified so much of the code, made it much more user friendly, and fixed a lot of the minor bugs and holes in the programming that would allow for unexpected results... Including this CID issue I believe.

Also fixed the way it writes to the log file, so it will be much easier when people can just post their log file. :good:

Once I get my device back and run through as much testing on 3.0 as I can with my own device, I'll release it for you all. :good:

I'm also looking into a better brick method, but I'm not going to release that until I actually test it... I don't know what damage it could do yet. :/

I might ask for some help from some people in the GSM world for copies of certain partitions, but more on that when I have my device back.
 

posedatull

Senior Member
Sep 15, 2012
795
253
Copenhagen
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)

No chance of getting this to work on Windows? Unfortunately my linux skills are very limited, and that combined with my lazyness to install it... I hope you get the point.
In any case, this tool seems more than awesome, great job :D

Sent from my HTC EVO 3D X515m using XDA Premium HD app
 

Notorious

Senior Member
Aug 23, 2011
8,182
5,167
Sydney
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)

No chance of getting this to work on Windows? Unfortunately my linux skills are very limited, and that combined with my lazyness to install it... I hope you get the point.
In any case, this tool seems more than awesome, great job :D

Sent from my HTC EVO 3D X515m using XDA Premium HD app

Nope windows can't detect certain things like Linux can

Sent from my SPH-L710 using xda app-developers app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 31
    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:

    1. Extract the files to somewhere (home folder works best)
    2. Gain a root command prompt (# instead of $) (sudo -s works for most)
    3. Set permissions via "chmod 755 ultimate" (possibly 0755 depending on linux flavor)
    4. Then run the tool using ./ultimate
    Code:
     /=================================================================\
    |*******************************************************************|
    |****************** 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 (This includes URT 3.0)

    Recent Updates:

    3.1
    • Added another check to 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
    • Removed Radio Fix for now, some bug I can't figure out yet... Meh
    • Fixed a few missing things from the VM Radio Fix (CDMA Only) (when 3.0 is Final)
    • 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


    Radio Fix is for CDMA ONLY!
    See the CDMA Thread -> here


    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 a higher version of hboot, you can just downgrade via a sdcard PG86IMG containing the lower hboot, being S-OFF will let it flash anything ;)

    For the S-ON Downgrade... Things you'll need...

    • Linux and basic linux knowledge (not necessary if you use the URTLiveCD)
    • The RUU ZIP image that MATCHES your current ROM version
    • You'll also need the 1.20 or 1.22 RUU EXE (All the RUU's can be found here -> http://www.filefactory.com/f/4ef0ef536face67a/)
    • Download the ultimate3.0.zip listed above or the URTLiveCD if you do not have linux
    • Backup your apps/data if you need to, this process will wipe EVERYTHING

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

    (3/12/13 - PENDING UPDATE
    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/showthread.php?t=1563342

    First Step

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


    VIDEO OF ENTIRE PROCESS (Done with the battery pull method and on a CDMA device)


    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 ZIP image from your CURRENT ROM RUU, 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. 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:

    Code:
    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:

    Code:
    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:

    Code:
    Device Found!
    Locating misc partition...
    Misc found at partition 31.
    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.49.0007 :)

    (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.20 or 1.22 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.
    7
    The Thanks List!

    MOVZX
    RussianBear
    Fuses
    Dexter93
    TrevE
    Crackanug
    closeone
    USSENTERNCC1701E
    jcase
    agrabren
    chad.goodman
    wwjoshdew
    The Fer-Shiz-Nizzle
    jlechner
    The entire Revolutionary team
    And pedja1 for getting me the info I needed to get the GSM port done! :)

    FAQ's

    Can I do this on Windows?

    Currently there is no way to do this on Windows. It's unlikely that there will be a way to do it on windows, Windows USB is too slow and doesn't detect the device the same as Linux does.

    Can I do this in (Insert virtual PC software)?

    The only one I've heard that works is VMWare, however You're again relying on Windows to pass the device to a virtual machine, which isn't ideal. I know for a fact that VirtualBox does not work, and Cygwin also does not work.

    Common Errors

    I can't get my phone to brick, I've tried a million times!

    Patience is a virtue. This step is the hardest part of all, HTC Designed their phone to be brick proof for a reason. I believe the trick here is to let the device sit on the update screen for a minute or two, then do the update and count out 5 seconds. Also there's the update bar that appears in the upper right hand corner, much like the bar that is there when it's checking the zip file before the update prompt. The INSTANT you see that, pull the power. This is typically 5-6 seconds after it says updating, but only after it's been sitting for a bit... I believe the trick is to let it sit for a bit before pressing Volume up to update.

    My PG86IMG.zip is not detected or the phone checks it and it doesn't prompt me to update it

    There are several possibilities:

    • The phone is HTC Unlocked - You must re-lock.
    • The phone is S-OFF - Don't even try to brick it because you'll permanently brick it.
    • The phone is Re-locked, but still has a custom rom/recovery on it. - This will show a security warning and not allow the PG86IMG.zip to be flashed. - You must put the phone in FASTBOOT USB and run the RUU exe that matches your software version.
    • The File is not named correctly, it's PG86IMG.zip (Make sure it's not PG86IMG.zip.zip)
    • The PG86IMG.zip is either corrupt, not signed properly, or modified in some way. - Download another one.

    I press Volume up to Update, and my phone shuts off

    • First make sure you're using a standard HTC A/C Adapter and cable. These are designed to charge at 1000 mA, other manufacturer's chargers typically only hit 900 mA. The phone needs it all to stay on and update properly without the battery in.
    • Second, make sure you're not using a higher end SD Card. This will draw too much power and not let the phone update when it comes to that time because the power drain to have the screen on, the sd card powered and the update running is more than what the A/C adapter can output. - My 16GB Class 10, shuts the phone off, my Class 4, 2 GB, does not. YMMV.
    • Third, if you're stuck with the high end SD card, or think it could be the cause, simply pull it after you pull the battery and BEFORE you press volume Up to update. The phone will still update. However, I don't know if this affects the speed of the update at all... so just watch it the first time and time it, then time your pull accordingly.

    I'm getting Permission Denied when trying to run the linux commands

    You don't have root, either type su or sudo -s, your prompt should have a # at the end and not a $.
    Or, you didn't set the chmod correctly on the ultimate file. This is again chmod 755 ultimate (or /path/to/ultimate)

    I get Misc image is missing!!! or HBOOT image is missing!!! or Recovery image is missing!!!

    The hboot.img and misc.img and recovery.img files must be in the same location as the ultimate file, they are hard coded into the ultimate tool to be in the same location, their names are also hard coded, so don't rename them.

    I'm getting Error 16 after running the radio fix.

    This can happen, there are two things, most likely it goes away after attempting to place a few calls. If it doesn't, just remain on the line, and they can fix the problem for you.
    6
    Got the phone pieced together last night and it's working well. I was able to use 3.0 to get it downgraded (after fixing several bugs) I'm still doing a little testing...

    The things I have tested: Unbrick, Downgrade, Backup

    The things I have not tested: Flash Custom, VM Radio Fix.

    The misc partition detection works, so that removed the need to specify GSM or CDMA, or set that "mode." It will set the hboot partition based on the number of the misc partition, and write them accordingly. Below is a small chart... If ANYONE has a device that differs from this. PLEASE let me know ASAP.


    Last partition on device(misc) -- 31 32 33 34 35

    Corresponding Hboot partition -- 12 12 NO 13 13


    I also fixed the GSM's CID related issues as well, I hope. I have no way to test this for certain, but I'm 99.99% sure it's resolved.

    The menu interface works well. It's still got some minor bugs that I need to iron out, but such is the case when you completely re-design something...

    I was able to use the backup function without issue. However, this I would like to figure out a better way to put the backup in a location that isn't deleted in a LiveCD Environment. Booting to a LiveCD stores everything in RAM (temp memory) and naturally when you reboot, the memory is flushed so you can use fresh for your next boot up, And so your backup is lost to the abyss.

    If you know Linux well enough you can just specify the location with the file name to backup to and that will work, but not everyone knows how to do that or how to know where to write to, and besides you're likely not going to need the LiveCD if you know Linux well enough. ;) It needs some other location to store the backup. This isn't a major concern, and I won't be looking into this anytime soon. And it won't stop me from releasing 3.0 as it was this way in 2.5.1 as well, so it's not a show stopper.

    Anyway, to the main point, I'm wrapping up a few loose ends in the code and I should have it finished either tonight or tomorrow night. (I work from 8-5 every day, so I can only work on this after work)
    3
    Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)

    Take your time..no one wants tool which will brich his phone pernamently:D

    Odesláno z mého HTC EVO 3D X515m pomocí Tapatalk 2

    Oh haha no that would be a major bug! I still don't know how I managed to Perma brick the other one I bought :(

    But as soon as I get out of work I plan to do a few more tests and hopefully it will be resolved by then.
    3
    Bad news...

    I managed to permanently brick the device I had for testing with 3.0, so I'm glad that I didn't release it...

    I can't be certain what happened, because I have no way to read from it now... but I'm guessing the misc detection failed somehow and it wrote the GSM hboot to it... and now it doesn't know how to boot properly, and doesn't go into the brick mode I need to see it and write partitions to it anymore. It's now a permanent brick, so that is unfortunate. Quite a setback in both time and money...

    But, the good news is, I found another device that I can use for relatively cheap, but this is the last time I'm spending money on this.

    Obviously I'm going to be more careful with this one and put in some checks before I do the writing, or simulate the write to somewhere other than the device, but still if something should go wrong, I'm not going to throw more money into a fire.

    This obviously sets back the release until I can test it further, I should have the device by Monday.

    I plan on changing the way the misc detection works and putting some more checks in to avoid detection issues, and then test the crap out of it, so it functions properly...

    I might change it back to a "two plug" method, where the first plug, does the detection, and then asks the user to verify that it's a CDMA or GSM device, if not, then give them the option to specify it, with a long warning that clearly indicates that if you select the wrong one, you will end up with a paperweight, and then the second plug actually does the writing...

    Either way, we've been set back by about a week :(
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone