[S-OFF] Juopunutbear S-OFF for windows...

[S-OFF] Juopunutbear S-OFF for windows... - HTC Amaze 4G

[S-OFF] Juopunutbear S-OFF for windows...
here is the htc amaze 4G Juopunutbear S-OFF tool for windows,i decided to upload it since http://unlimited.io/ is not supporting windows anymore...
INSTRUCTIONS:
# - Be on the Stock RUU. No other ROMs are supported, Fresh ROM will not work regardless of what you have read elsewhere.
# - Ensure that your battery is fully charged.
# - External SD card (2GB - 16GB) in your device.
# - The original HTC USB cable for your device.
# - Perform a full backup or replace your SDcard with one that you are willing to wipe - it is possible that during these steps all data may be lost.
# - You must be directly connected to a USB 2.0 port on your computer - USB 3.0 and USB hubs will NOT work!
# - Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
# - Verify - You are HTC Dev Unlocked
# - Turn ON USB Debugging on your device (Settings > Developer Options)
# - Verify fast boot is turned OFF (Usually found under Power Settings)
# - Connect your device and set to "Charge Only"
# - temporary disable any antivirus,htc sync,i-tunes,kies or any smartphone related software
first extract the ControlBearRelease_ruby_GB_WIN.zip for GB and ControlBearRelease_ruby_ICS_WIN for ICS into one folder,
1- Run ControlBear.exe as administrator.
2- follow the on screen instructions from controlbear.
3- Do not press any of the buttons on the phone during the process.
WIRE TRICK,,,
The "wire trick" is an essential part of the JuopunutBear S-OFF procedure.
1) - Obtain an insulated wire of appropriate length and gauge. Suitable wires are: a SINGLE core (strand) from an ethernet cable or a core from a coaxial cable.
2) - see the attached image for the PIN and GND points needed for completing the wire trick.
When instructed to do so by the program you must perform the "wire trick" as follows:
3) - Hold one end of the wire into the hole where PIN is indicated in the picture below, ensuring that a firm contact is made with the metal contact at the bottom of the hole.
4) - Briefly touch to other end of the wire to the contact marked GND in the picture.
5) - Wait approximately 1.5 seconds and then again touch the wire to the marked GND.
* If that timing does not work the first time try: TAP (pause 1.25 seconds) TAP
6) - Allow the program to continue.
IMPORTANT: If you get the error Still Sober all you need to do is re-run ControlBear after you have verified that you meet all of the pre-requirements.
if i've helped you then don't forget to hit the thanks button...
[team unlimited.io rejected to give permissions to repost thier tools,so links are removed]

This should help out the newbies and people who don't have Ubuntu or are too lazy for downloading a live cd.
Sent from my HTC Ruby using Tapatalk 2

SuperAfnan said:
This should help out the newbies and people who don't have Ubuntu or are too lazy for downloading a live cd.
Sent from my HTC Ruby using Tapatalk 2
Click to expand...
Click to collapse
yup.... i hope it should..

Did you get permission to do this? If not your gonna be in some trouble my friend.. I recommend removing these links unless you have permission. Just letting you know, trying to help u out
Sent from my HTC_Amaze_4G using xda premium

i have unlimited.io s off zips with me and i see all the fastboot exe,adb exe,adb win api,adb winusbapi files are missing in your zips maybe the reason why the jbear hboot doesnt flash after the s off procedure and get stuck in CID 0202 and get softbrick ultimately :/ your trying to help but your making all the new comers brick their devices softly are you trying to become wise more than the unlimited.io actual developers?

ravike14 said:
i have unlimited.io s off zips with me and i see all the fastboot exe,adb exe,adb win api,adb winusbapi files are missing in your zips maybe the reason why the jbear hboot doesnt flash after the s off procedure and get stuck in CID 0202 and get softbrick ultimately :/ your trying to help but your making all the new comers brick their devices softly are you trying to become wise more than the unlimited.io actual developers?
Click to expand...
Click to collapse
It is not necessary to flash the Eng. jbear hboot once S-Off is gained. I'm still on the stock hboot with S-Off, don't have any issues.
However, some adb/fastboot files are missing in the zip though.

uvt_novice said:
It is not necessary to flash the Eng. jbear hboot once S-Off is gained. I'm still on the stock hboot with S-Off, don't have any issues.
However, some adb/fastboot files are missing in the zip though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2236134 refer to that post until the supercid it is necessary to have the ENG hboot or 1.93.0002 hboot or else you cant supercid your phone when the eng hboot doesnt flash during the s off process you get stuck in a wrong hboot and in a cid called 0202 which has happen like very few times in xda in that softbrick point you cant flash any ruu's roms or anything cuz the cid doesnt support!! in that post his problem is more worse cuz he dont have a working device to try anything...after doing the supercid you can use the stock hboot till then they have to have the eng hboot or the stock 1.93.0002 to flash supercid :S

ravike14 said:
i have unlimited.io s off zips with me and i see all the fastboot exe,adb exe,adb win api,adb winusbapi files are missing in your zips maybe the reason why the jbear hboot doesnt flash after the s off procedure and get stuck in CID 0202 and get softbrick ultimately :/ your trying to help but your making all the new comers brick their devices softly are you trying to become wise more than the unlimited.io actual developers?
Click to expand...
Click to collapse
thanks for pointing this out ravike,updating zips now...

aj_2423 said:
Did you get permission to do this? If not your gonna be in some trouble my friend.. I recommend removing these links unless you have permission. Just letting you know, trying to help u out
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
thanks aj...links are removed, ravike is right though , i am trying to be wise with a thanks meter of 29...
now contacting team unlimited...see where this goes..

aj_2423 said:
Did you get permission to do this? If not your gonna be in some trouble my friend.. I recommend removing these links unless you have permission. Just letting you know, trying to help u out
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
team unlimited.io rejected to give permissions to repost their tools...

hatim_rajput said:
team unlimited.io rejected to give permissions to repost their tools...
Click to expand...
Click to collapse
Knew that was going to happen they have a stric post in there page lol
Sent from my HTC_Amaze_4G using xda premium

ravike14 said:
http://forum.xda-developers.com/showthread.php?t=2236134 refer to that post until the supercid it is necessary to have the ENG hboot or 1.93.0002 hboot or else you cant supercid your phone when the eng hboot doesnt flash during the s off process you get stuck in a wrong hboot and in a cid called 0202 which has happen like very few times in xda in that softbrick point you cant flash any ruu's roms or anything cuz the cid doesnt support!! in that post his problem is more worse cuz he dont have a working device to try anything...after doing the supercid you can use the stock hboot till then they have to have the eng hboot or the stock 1.93.0002 to flash supercid :S
Click to expand...
Click to collapse
I'm on stock ICS HBOOT which is 1.93.0002 with SCID and S-Off, sooo? Never flashed Eng JBOOT, but able to flash via fastboot whatever I want. Updated radio to the latest yet my device was Telus (Canada) branded but I'm with Windmobile (Canada).
---------- Post added at 11:10 AM ---------- Previous post was at 11:09 AM ----------
ravike14 said:
Knew that was going to happen they have a stric post in there page lol
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
+1, Surely, they would not allow this (to post their past work) if they dropped windows support.

uvt_novice said:
I'm on stock ICS HBOOT which is 1.93.0002 with SCID and S-Off, sooo? Never flashed Eng JBOOT, but able to flash via fastboot whatever I want. Updated radio to the latest yet my device was Telus (Canada) branded but I'm with Windmobile (Canada).
Click to expand...
Click to collapse
Well yea as i told to supercid you have to have the eng hboot or the 1.93.0002 hboot you've missed that part in my post, read it again you'll catch it to that guy called Andy his cid is 0202 and his hboot is 1.90.004 or something and he's s off aswell but he can't do anything cuz he got both of above requirements wrong! :good:
Sent from my HTC_Amaze_4G using xda premium

i have error
Starting up......
Connecting to device...
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (6/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (2/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (4/60)
Waiting...
Waiting...
Waiting ADB.... (2/60)
Test (2.1): Booting FAILED (2)
Press ENTER to exit.....

dxbboy said:
i have error
Starting up......
Connecting to device...
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (6/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (2/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (4/60)
Waiting...
Waiting...
Waiting ADB.... (2/60)
Test (2.1): Booting FAILED (2)
Press ENTER to exit.....
Click to expand...
Click to collapse
sorry pal...unlimited.io team doesn't support windows anymore, i mentioned it earlier in this thread, so this tool is discontinued ...
please read as much as you do before doing anything with your device...
search for hasoon tool kit for amaze or take a look at this thread...might come in handy..
http://forum.xda-developers.com/showthread.php?t=2437057

i was trying this on my sensation pyramid

any way i got it working changed some file .. and zupaakk em s-off

hatim_rajput said:
[S-OFF] Juopunutbear S-OFF for windows...
here is the htc amaze 4G Juopunutbear S-OFF tool for windows,i decided to upload it since http://unlimited.io/ is not supporting windows anymore...
INSTRUCTIONS:
# - Be on the Stock RUU. No other ROMs are supported, Fresh ROM will not work regardless of what you have read elsewhere.
# - Ensure that your battery is fully charged.
# - External SD card (2GB - 16GB) in your device.
# - The original HTC USB cable for your device.
# - Perform a full backup or replace your SDcard with one that you are willing to wipe - it is possible that during these steps all data may be lost.
# - You must be directly connected to a USB 2.0 port on your computer - USB 3.0 and USB hubs will NOT work!
# - Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
# - Verify - You are HTC Dev Unlocked
# - Turn ON USB Debugging on your device (Settings > Developer Options)
# - Verify fast boot is turned OFF (Usually found under Power Settings)
# - Connect your device and set to "Charge Only"
# - temporary disable any antivirus,htc sync,i-tunes,kies or any smartphone related software
first extract the ControlBearRelease_ruby_GB_WIN.zip for GB and ControlBearRelease_ruby_ICS_WIN for ICS into one folder,
1- Run ControlBear.exe as administrator.
2- follow the on screen instructions from controlbear.
3- Do not press any of the buttons on the phone during the process.
WIRE TRICK,,,
The "wire trick" is an essential part of the JuopunutBear S-OFF procedure.
1) - Obtain an insulated wire of appropriate length and gauge. Suitable wires are: a SINGLE core (strand) from an ethernet cable or a core from a coaxial cable.
2) - see the attached image for the PIN and GND points needed for completing the wire trick.
When instructed to do so by the program you must perform the "wire trick" as follows:
3) - Hold one end of the wire into the hole where PIN is indicated in the picture below, ensuring that a firm contact is made with the metal contact at the bottom of the hole.
4) - Briefly touch to other end of the wire to the contact marked GND in the picture.
5) - Wait approximately 1.5 seconds and then again touch the wire to the marked GND.
* If that timing does not work the first time try: TAP (pause 1.25 seconds) TAP
6) - Allow the program to continue.
IMPORTANT: If you get the error Still Sober all you need to do is re-run ControlBear after you have verified that you meet all of the pre-requirements.
if i've helped you then don't forget to hit the thanks button...
[team unlimited.io rejected to give permissions to repost thier tools,so links are removed]
Click to expand...
Click to collapse
where is the link ???

i think you should read the link again.
feroz2u said:
where is the link ???
Click to expand...
Click to collapse
I think if you could read THE THREAD again you will find something interesting written there.
Try it i dare you.

Related

[TOOL] HBOOT Downgrade Toolkit Live CD (or USB) - Free Your Phone. S-OFF.

Hello everyone. This is a breakoff from Unknownforce's HBOOT 1.50 to 1.40 downgrade thread. I created a Live CD to help make the downgrade process a bit easier.
Just a little housekeeping before we start:
Please! If you have a question, do not post it in both downgrade threads. Doing so makes it hard to follow what you've already done. Many people frequently visit both threads and will see your question. Thank you for your cooperation.
All credit goes to Unknownforce for making it possible to downgrade the EVO 3D. I take absolutely no credit for the downgrade method. My aim in creating the HBOOT Downgrade Toolkit was to make Unknownforce's downgrade method as easy and painless as possible. Thank you to him and everybody else listed below.
See post #3 for:
- Full Step-by-step directions
- Bootable USB flash drive instructions
- Other useful resources (How to burn an ISO to a CD)
Important! Please Read this!
- This is for CDMA phones only! DO NOT USE THIS IF YOU HAVE A GSM EVO 3D!
- Test that your computer will boot the Toolkit before Bricking! Use the 'Check device status' function in the Toolkit to see if your phone is being recognized (USB debugging must be enabled on your phone (Settings -> Applications -> Development -> USB debugging).
See Unknownforce's thread for bricking instructions.
- Do not do this if you already have S-OFF! If you aren't sure whether your already S-OFF, boot into the bootloader on your phone (Power off -> Hold down 'Volume Down (-)' and the power button). If you see S-ON, you're fine. If you have any questions, feel free to post them inside the thread.
- Charge up your battery - know that you have at least a decent (even 50 or 60%) amount of battery power going in. It will save you a lot of frustration later.
- If you are flashed to a different carrier: you must keep a record of the settings for your phone, as they will be wiped when you do this process.
Again. This is less scary than it sounds! I promise.
LATEST VERSION (STABLE): (should work perfectly when burned to a CD; if a USB flash drive is used, follow the NEW instructions in the second post to make the drive bootable)
Version 0.8.2
Download
- Device Test now properly states how to start the test
- Device Test does a Fastboot test, and an optional ADB test
- Help option gives a brief overview of the Downgrade process
- Some more information given before doing tests
- Downgrade will no longer snap back to the main menu after finishing
MD5 Checksum: c6b6889c7f12681621feaec26580f695
Click to expand...
Click to collapse
PREVIOUS STABLE VERSION: (should work perfectly when burned to a CD; if a USB flash drive is used, follow the NEW instructions in the second post to make the drive bootable)
Version 0.7.0
Download - Thanks WTLORd!
Mirror - Thanks notsointeresting! (+d-h.st)
Mirror #2 - Thanks disturb3d1/wwjoshdew!
* Run Revolutionary from the Toolkit (Beta code required)
* HTCDev Relock support integrated
* Flash either ClockworkMod 5.0.1.0 or 4.0.1.4
- Menu has been cleaned up (cleared up some wording as well)
- Fixed bug with shutdown not being allowed in some cases
I encourage you to try it and please let me know how it runs! Thanks everyone!
MD5 Checksum: c69c796c13a39b589d28a6ebe26b18d2
Click to expand...
Click to collapse
Thanks to
Unknownforce for bringing us the EVO 3D downgrade method.
notsointeresting and WTLORd for mirroring these downloads.
Mpgrimm2 for his awesome advise and assistance!
lowetax for kindly helping with the downgrade inside and out of the thread.
madmaxx82 for permitting me to bundle 4EXT Recovery
ClockworkMod
The Core Project (Tiny Core)
Personal thank you to the Revolutionary Team
Thanks to everyone who tested the CD and reported their findings.
If I forgot someone, please PM me, and I'll add you to the list.
I will also quote Unknownforce's thank you list, as I'm pretty sure that most of the programs in the downgrade CD method have some relation to them.
MOVZX, RussianBear, Fuses, Dexter93, TrevE, Crackanug, USSENTERNCC1701E, jcase, The entire Revolutionary team
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Questions
What is this?
This is a Live-Bootable Linux-based CD that attempts automates many of the steps that are required for the downgrade process. It's designed to make the task less daunting to users unfamiliar with Linux. It does not install anything onto your computer, and contains the drivers right inside of it.
Is there risk involved?
I won't lie. There is a small amount of risk using this. Then again, there is a small amount of risk with almost everything you do with your phone. There's even some risk in the HTCDev method. Doing this is a lot less scary than it sounds. Many people have used this method, and many have used the Toolkit to simplify the process. If you have questions, you may always post them inside the thread.
Is this a one-click method?
No. Not quite. It will still require you to use short commands.
Will I still have to work in a Terminal?
Yes... But don't leave yet. Most of the processes are done for you, and require entering a single letter to run a process.
Should I backup my phone before doing this?
Yes. Whenever doing something like this, you should always make backups! Also, this method will require you to flash a RUU after you are done downgrading and doing the Revolutionary S-OFF. You WILL lose all data on your phone (not SD Card) when applying the 1.13 RUU.
How do I know that my phone is bricked?
If the screen powers on and displays anything at all, it is not bricked.
I'm unlocked using the HTCDev method. Do I have to do anything different?
You will have to lock your bootloader before starting. Since you likely already have the benefit of backing up, do that before locking. Lock your device by using the HTCDev Relock feature in the Toolkit, or the command: fastboot oem lock while in the bootloader (Fastboot-USB mode) on your phone. If you are running a custom ROM, there is a chance that your phone will reboot and give you a Security Warning. You will have to apply a stock 2.08 or 2.17 RUU before proceeding. Get the 2.17 RUU from here, rename it to PG86IMG.zip (If file extensions (.zip, .doc, .mp3) are set not to show in Windows, just rename the file 'PG86IMG'.) and place it on the root (main directory) of your SD Card. Boot up your phone and run the RUU all the way through. Remember, running this RUU will erase all data on your phone (not SD-Card though). Now, continue as if you hadn't taken the HTCDev Unlock.
Click to expand...
Click to collapse
The HBOOT Downgrade Toolkit Live CD is a bootable version of Linux (don't worry! ) that simplifies a lot of the process of Downgrading your HBOOT from 1.5 to 1.4.
Old Versions.
0.8.0t - Download
0.6.5s - Download - Thanks WTLORd!
Mirror - Thank you notsointeresting!
0.2.2 - 0.5.1 - Download - Legacy
Click to expand...
Click to collapse
Support
Please make sure to keep this thread limited to questions and comments on the live CD. For support with the Downgrade method, it's probably best to keep discussion in Unknownforce's thread. I will try my best to support the CD, but I cannot guarentee that I will be able to continue to answer questions about the CD.
Click to expand...
Click to collapse
Changelog
Code:
0.8.2 - Device Test now properly states how to start the test
- Device Test does a Fastboot test, and an optional ADB test
- Help option gives a brief overview of the Downgrade process
- Some more information given before doing tests
- Downgrade will no longer snap back to the main menu after finishing
0.8.0t* Fix error with messages flooding the screen on some hardware
* Fix error with hardware not working too nicely with USB
- No other changes
- Same version number cosmetically (forgot to change it before building)
- MD5 Checksum: 0246fe0f8a80197bc1e63599eeda83ee
0.8.0 - Rebuilt (again) from the ground up
- New menu-driven interface
- 4EXT Recovery now included (Thanks madmaxx82)
- Usability fixes
- Broadened device test
- Boot directly into the bootloader
- Easily exit utilities without rebooting
- More instruction while using
- Built off of Micro Core
- MD5 Checksum: 9e0b883f013ab8db46101663dc188cdb
0.7.0 - Run Revolutionary from the Toolkit ([URL="http://www.revolutionary.io"]Beta code required[/URL])
- HTCDev Relock support integrated
- Flash either ClockworkMod 5.0.1.0 or 4.0.1.4
- Menu has been cleaned up (cleared up some wording as well)
- Fixed bug with shutdown not being allowed in some cases
- MD5 Checksum: c69c796c13a39b589d28a6ebe26b18d2
0.6.5s- It's been (pretty much) rebuilt from the ground up (new Base OS - TinyCore Linux)
- It's 93% smaller than the previous version of the Toolkit Live CD.
- It's a lot faster booting up.
- Should only require about <128MB of RAM, and <500MHz Processor.
- It's text based only, but that's okay (trust me). It boots; press 'd' to downgrade. That's it.
- I have integrated the ability to Flash ClockworkMod 5.0.2.0.
- MD5 Checksum: 4884fbcd21e37e7cd3f1ea2f7ddef8da
0.5.1 - No longer need to do step 1 - Type 'downgrade' into the Terminal to do the downgrade. You no longer
need to flash an RUU at the beginning, or temp root.
- MD5 Checksum: 5014B2E79B834173887941C5BE71E7A3
0.4.1 - New version of emmc_recover - No need to open four terminal windows anymore! - Thanks Unknownforce!
- MD5 Checksum: f6be045551ed18c6c22912a6e46f1cd6
0.3.4 - zergRush Temp Rooting
- Mainver version change and verification
- Start command that lists the names of all commands available to the user.
- Step Three HBOOT flash for partitions sdb13, sdc13, sdd13, sde13.
- MD5 Checksum: 03eac19c68672f3334526580ac91d5bb
0.2.2 - Step Three HBOOT flash for partitions sdb13, sdc13, sdd13, sde13.
- MD5 Checksum: 40c1de37fd66f0348770f2a7a53d0998
If ClockworkMod or the Revolutionary Team wants me to remove their software (ClockworkMod Recovery and Revolutionary, respectively) from the toolkit, I will comply with that request.
Obligatory Disclaimer - This software is distributed in the hope that it will be useful, but without any warranty. You take full responsibility for the usage of the software. I am not liable for anything that goes wrong with this Live CD, including, but not limited to, "bricked" (otherwise unusable) phones, or anything else that happens to your phone(s), computer(s), or anything else. You take full responsibility for your use of these tools.

Toolkit To Do
?
Click to expand...
Click to collapse
Thread To Do
?
Click to expand...
Click to collapse

Table of Contents (for this post)
Step By Step How-to Downgrade With the HBOOT Downgrade Toolkit
Burning the HBOOT Downgrade Toolkit to a CD
How to run the HBOOT Downgrade Toolkit from a Flash Drive
Preparing to run Revolutionary
OLD VERSION - Step By Step How-to Downgrade With the HBOOT Downgrade Toolkit - OLD VERSION
Resources
Step By Step How-to Downgrade With the HBOOT Downgrade Toolkit
Updated for the new version! 0.8.0+
Test that your computer will boot the Toolkit before Bricking! Use the 'Check device status' function in the Toolkit to see if your phone is being recognized (Power the phone off completely. May require you to pull the battery and put it back in. Plug the phone into the computer).
Please follow the steps as closely as possible! Even if a step seems redundant or unnecessary, there's a reason that you are doing it. If you have any questions about the guide, please feel free to ask in the thread.
Read the Important Information section in the first post (at the very least) before starting!
1. Download 2.17 RUU Zip, 1.13 RUU EXE, Latest Version of Boot CD
2. Backup your phone
3. Burn the CD or USB flash drive with the instructions below
4. Ensure that you can boot into the HBOOT Downgrade Toolkit before bricking!
--IF YOU ARE HTCDev UNLOCKED--
5. Reboot your computer into the Toolkit (CD/USB flash drive)
6. Power off your phone completely (you may have to pull the battery and put it back in after powering off)
7. Plug the phone into the computer without powering it on
8. Use the 'Bootloader' command. This should power back on the phone. (If not, Hold Vol - and press the power button) - Ensure that you are S-ON. (If you see the word 'FASTBOOT' highlighted in red, hit the power button)
9. If you are HTCDev Unlocked -> Run the 'Relock' command from the main menu.
10. Reboot your computer and continue.
-----
11. Copy 2.17 RUU to the SDCard. Make sure that it's named PG86IMG.zip.
--Bricking the phone (Temporarily)--
12. It's best if you read Unknownforce's instructions for bricking.
13. It's always best to check that you have bricked successfully to save yourself frustration later on.
14. > Put the battery back into the phone. Wait about 7-8 seconds.
15. > Press the power button. If charge light is solid-dim, or doesn't come on at all and the screen does not power on, you've successfully bricked the phone.
16. > If the charge light is blinking, (and/or the screen turns on), the phone isn't bricked. Keep on trying!
-----
17. Once the phone is in a bricked state, boot up into the HBOOT Downgrade Toolkit.
18. Leave the battery OUT OF your phone. Don't plug it in yet.
19. From the main menu, use the 'Downgrade' command.
20. Read the on-screen instructions carefully.
21. Press enter until you see the words "Waiting for device..."
22. While holding down the Volume - button, plug the phone in. (REMEMBER: No battery in phone)
23. Follow the on-screen instructions.
24. It should ask you to unplug the USB cable and press enter.
25. When you see the words "Waiting for device..." move on to the next step.
26. While holding down the Volume - button, plug the phone back in.
27. If it worked, then you have successfully downgraded your Bootloader. Put your battery back into your phone, Hold down Vol - and press power.
28. Now. Reboot into Windows and run the 1.13 RUU EXE that you downloaded.
29. When that's done, reboot back into the HBOOT Downgrade Toolkit.
30. Power back on phone into Android.
31. Run Revolutionary from the menu. You'll be required to input your beta code from the Revolutionary website.
32. You may need to let Revolutionary rerun several times.
33. When you see "-Revolutionary-" at the top of your bootloader, you have achieved Revolutionary S-OFF!
34. Flash Recovery from the main menu.
35. Remove the PG86IMG file from your SD Card! Do NOT let it run again!
36. Optional: Run the 2.17 Firmware Update ZIP from here. Place it on your SD Card just like the PG86IMG file that you used to brick the device with. Boot up into the bootloader and let this run all the way through. (Recommended)
WARNING: DO NOT BRICK YOUR DEVICE AGAIN AFTER GETTING S-OFF. THIS WILL PERMA-BRICK THE DEVICE. RECOVERING FROM THE CD WILL NOT WORK. THE PHONE WILL NOT GO INTO THE SAME RECOVERY DOWNLOAD MODE AS AN S-ON DEVICE WOULD.
IMPORTANT: If you decide to stay with the stock ROM, DO NOT EVER take OTA (Over-The-Air) updates! Taking one will likely put you back on HBOOT 1.50.
36. I recommend that you flash a custom ROM. If you want to stay on a (mostly) stock ROM, I would recommend that you flash one of Mr.Esp's Stock Rooted ROMs. They will not "upgrade" your bootloader to HBOOT 1.50.
37. After you have done that, go ahead and make a Backup in your custom recovery.
After running Revolutionary, it is normal for your bootloader's version number to be 1.40.1100.
Have fun on HBOOT 1.40 S-OFF!
Click to expand...
Click to collapse
Burning the HBOOT Downgrade Toolkit to a CD
Windows Vista/7
1. Download the latest version of the HBOOT Downgrade Toolkit from above.
2. Insert your CD-R
3. Navigate to the location of the HBOOT Downgrade Toolkit on your hard drive.
4. Right-click on the .iso file. Hover over 'Open with' and select 'Windows Disc Image Burner'
5. Select your CD burner from the drop-down menu
6. (recommended) Tick 'Verify disc after burning'
7. Click Burn
Other Windows Method
PoorCollegeGuy's guide to Burning an ISO to a CD
Mac OS X - Thanks MikeC84!
Open disk utility, drag the ISO to disk utility. Make sure "make disk bootable" is checked, Click burn....
Check out lpjzfan2005's Mac OS X tutorial for running the CD!
Note: Mac support is limited. It's been confirmed the CD will run on a Mac though.
Click to expand...
Click to collapse
How to run the HBOOT Downgrade Toolkit from a Flash Drive
I've realized that there is enough demand for being able to run the HBOOT Downgrade Toolkit from something other than a CD-ROM drive.
Thanks to Disturb3d1/wwjoshdew and Mpgrimm2 for the suggestion!
Instructions for 0.6.5s or Higher
What you'll need:
A 256MB USB Flash Drive (Almost any flash drive you have laying around)
HBOOT Downgrade Toolkit ISO 0.6.5s or Higher (Above)
Core2USB
Step 1. Simply download Core2USB from here.
Step 2. Choose your USB Flash Drive and format it (This will delete all files from it, so back them up).
Step 3. Run the Core2USB software. It won't install anything on your computer.
Step 4. Browse to the HBOOT Downgrade Toolkit ISO.
Step 5. Double-click on the letter of your USB Flash Drive. Make sure that this is the correct drive.
Step 6. Click Install
Step 7. Reboot your computer with the USB Flash Drive inserted, and follow the onscreen instructions to downgrade your HBOOT.
Don't pull the flash drive out while you are booted into the HBOOT Downgrade Toolkit Environment!
Click to expand...
Click to collapse
Preparing to run Revolutionary
If you plan to run Revolutionary from the HBOOT Downgrade Toolkit, follow these directions to get started.
Head over to the Revolutionary website.
Under the heading 'Downloads,' click 'Download for Linux.' Cancel out the download.
Set the dropdown menus as follows:
Your operating system: Linux
Your device: HTC Evo 3D CDMA
HBOOT version: 1.40.0000
Serial number: [YOURPHONESSERIAL] (and yes, it has to be correct. Revolutionary will not without the key corresponding to your phone's serial number)
Click 'Generate key.' Make note of the key for when your ready to run Revolutionary (remember: the key is case sensitive).
Click to expand...
Click to collapse
OLD VERSION - Step By Step How-to Downgrade With the HBOOT Downgrade Toolkit - OLD VERSION
Test that your computer will boot the Toolkit before Bricking! Use the 'Check device status' function in the Toolkit to see if your phone is being recognized (USB debugging must be enabled on your phone (Settings -> Applications -> Development -> USB debugging).
Please follow the steps as closely as possible! Even if a step seems redundant or unnecessary, there's a reason that you are doing it. If you have any questions about the guide, please feel free to ask in the thread.
1. Download 2.17 RUU Zip, 1.13 RUU EXE, Latest Version of Boot CD
2. Backup your phone
3. If you are HTCDev Unlocked -> Read Instructions in FAQ above
4. Boot into your bootloader (Power off your phone -> Hold Vol - and press Power button)
5. If you get a Security Warning or you were HTCDev Unlocked, Power off your phone. Put SD Card into your computer. Skip to step 12 if this doesn't apply to you.
6. Copy 2.17 RUU to SDCard. Make sure that it's named PG86IMG.zip.
7. Power on the phone by pressing Vol - and Power. (If you see the word 'FASTBOOT' highlighted in red, hit the power button)
8. The Bootloader should should start checking the File.
9. After it finishes checking. Press the Vol + button to flash the image.
10. Let it flash all the way.
11. Once done, reboot back into the Bootloader.
12. Run the 2.17 RUU again, except this is where you will brick the phone (on purpose) -> It's best if you read Unknownforce's instructions for bricking.
13. Once the phone is in a bricked state, boot up into the HBOOT Downgrade Toolkit.
14. Leave the battery out of your phone. Don't plug it in yet.
15. From the main menu, type 'd' and press enter.
16. Read the instructions on the screen carefully.
17. Press enter until you see the words "Waiting for device..."
18. While holding down the Volume - button, plug the phone in.
19. Follow the on-screen instructions.
20. It should ask you to unplug the USB cable and press enter.
21. When you see the words "Waiting for device..." move on to the next step.
22. While holding down the Volume - button, plug the phone back in.
23. If it worked, then you have successfully downgraded your Bootloader, if it didn't, put your battery back into your phone, and press power. If the phone powers on, go back to step 12. The phone wasn't bricked.
24. Now. Reboot into Windows and run the 1.13 RUU EXE that you downloaded.
25. When that's done, reboot back into the HBOOT Downgrade Toolkit and power on your phone.
26. Run Revolutionary from the menu. You'll be required to input your beta code from the Revolutionary website.
27. You may need to let Revolutionary rerun several times.
28. When you see "-Revolutionary-" at the top of your bootloader, you have achieved Revolutionary S-OFF!
29. Make sure to flash a custom recovery image onto your phone. You can flash ClockworkMod Recovery 5.0.1.0 or 4.0.1.4 from the toolkit. You may also flash (Such as TWRP or Clockworkmod Recovery) using the command: fastboot flash recovery [NAMEOFRECOVERY].img
IMPORTANT: If you decide to stay with the stock ROM, DO NOT EVER take OTA (Over-The-Air) updates! Taking one will likely put you back on HBOOT 1.50.
30. I recommend that you flash a custom ROM. If you want to stay on a (mostly) stock ROM, I would recommend that you flash one of Mr.Esp's Stock Rooted ROMs. They will not "upgrade" your bootloader to HBOOT 1.50.
31. After you have done that, go ahead and make a Backup in your custom recovery.
After running Revolutionary, it is normal for your bootloader's version number to be 1.40.1100.
Have fun on HBOOT 1.40 S-OFF!
Click to expand...
Click to collapse
Resources
Unknownforce's [DOWNGRADE HBOOT/UNBRICK] HBOOT 1.50
PoorCollegeGuy's instructions for Burning an ISO to a CD
Mpgrimm2's list of 2.17 Links
Mpgrimm2's list of Stock & 2.17 ROMs
How To: Pull PG86IMG.zip from Evo3D RUU.exe (Mpgrimm2)
lpjzfan2005's Live CD Mac OS X tutorial
joefanelli's Using a FLASH phone? (Read this if you are flashed to a different carrier!)

Hey man thanks for the tool! I have already downgraded with the original tutorial but I bet this will help a lot of people get the guts to do it!
Oh and if you want I will go ahead and download and mirror for you if you would like

notsointeresting said:
Hey man thanks for the tool! I have already downgraded with the original tutorial but I bet this will help a lot of people get the guts to do it!
Oh and if you want I will go ahead and download and mirror for you if you would like
Click to expand...
Click to collapse
Thank you! And that would be awesome! Thank you!

closeone said:
PLEASE do not ask about them. I am not asking for them. If the CD worked. Just let me know! If you wish to donate, please send a donation to the guy who actually spent his time working to come up with the method. If it wasn't for Unknownforce, I wouldn't be posting this CD.
Click to expand...
Click to collapse
Just take the money! If it wasn't for Fuses, Unknownforce wouldn't have his method. Now if it wasn't for you, some people wouldn't have 1.4
But seriously, good job

So I haven't even finished Downloading them, let alone uploading them but when they are done they will be HERE
I say give it 30 minutes and the first iso will be up their, I will post when it's done
(Don't worry I pay for Mediafire Pro so their shouldn't be a problem)

This looks very promising. Good work!
Once I can get people to verify that this works without fault mind if I post this on my site?

EGOvoruhk said:
Just take the money! If it wasn't for Fuses, Unknownforce wouldn't have his method. Now if it wasn't for you, some people wouldn't have 1.4
But seriously, good job
Click to expand...
Click to collapse
Thanks EGOvoruhk. I'd have to think about it. The last thing I want to do is have anyone angry at me. I want to stay on as many people's good sides as possible, and that includes Unknownforce's as well.

notsointeresting said:
So I haven't even finished Downloading them, let alone uploading them but when they are done they will be HERE
I say give it 30 minutes and the first iso will be up their, I will post when it's done
(Don't worry I pay for Mediafire Pro so their shouldn't be a problem)
Click to expand...
Click to collapse
Thanks again notsointeresting!
JJsax said:
This looks very promising. Good work!
Once I can get people to verify that this works without fault mind if I post this on my site?
Click to expand...
Click to collapse
Thanks JJsax. If you go into Unknownforce's thread, there are quite a few success stories from the 0.2.2 version of the CD. But, absolutely, I'd be honored.

closeone said:
Thanks JJsax. If you go into Unknownforce's thread, there are quite a few success stories from the 0.2.2 version of the CD. But, absolutely, I'd be honored.
Click to expand...
Click to collapse
Perfect. I will get started on the post tonight. Will probably go live tomorrow. I lost track of the downgrade thread. It's hard to get caught back up when you're 20+ pages behind LOL.

JJsax said:
Perfect. I will get started on the post tonight. Will probably go live tomorrow. I lost track of the downgrade thread. It's hard to get caught back up when you're 20+ pages behind LOL.
Click to expand...
Click to collapse
Thanks. I will still need a few people to test the new version though. I can't guarantee that it's working fully. Old version is going strong as far as I'm concerned.

Sorry closeone for some reason the upload restarted ,should be up in about 45 minutes (both of them)
Edit: test iso is now there

since zergRoot supports 2.08 ruu i would have to convert from 2.17 since tacoroot isnt in the new release

NICE! This is awesome. I'm sure someone will come up with a one click though.
Here is another mirror to, I hope you don't mind!
http://ifile.it/tndhc19/HBOOT_Downgrade_Toolkit.i686-0.3.4.iso

disturb3d1 said:
NICE! This is awesome. I'm sure someone will come up with a one click though.
Click to expand...
Click to collapse
Most likely not. It requires you at least boot into Linux after finished changing your mainver in windows so you can't have a full one click, plus the whole part about bricking your device can't be one clicked you have to Pull the AC power on your phone at the exact right time to brick .
And the Linux step requires you to pull the plug on phone at the right time.
So a one click won't happen. They can only make it slightly easier.
Although its not hard at all.

yeah, but a short delay, like "press enter when phone boots" or something.
Sent from my Transformer Prime TF201 using Tapatalk 2 Beta-3

dadda said:
since zergRoot supports 2.08 ruu i would have to convert from 2.17 since tacoroot isnt in the new release
Click to expand...
Click to collapse
dadda, at this moment, your best bet would be to do Tacoroot in Windows. I'm sorry. I'm looking into it.
disturb3d1 said:
NICE! This is awesome. I'm sure someone will come up with a one click though.
Click to expand...
Click to collapse
Thanks! Understandable. But until then, the Boot CD is out, and will hopefully be helpful to anyone who's nervous working in a Terminal.
Edit: Thank you for mirroring the file too!
Double Edit: I just checked the link, because the link goes to a site you have to register for, I'm pretty sure I can't put that in the original post per xda rules. I'm sorry.

not a problem do your thing im not in a rush cause i have to unroot my current phone and take it back to the store do to extra low in-call headset volume
closeone said:
dadda, at this moment, your best bet would be to do Tacoroot in Windows. I'm sorry. I'm looking into it.
Click to expand...
Click to collapse

Great job man! I know a lot of ppl needed this, great to see things moving forward...
Sent from 3D A.W.E.S.O.M-O

[Guide] Quick And Dirty Evo 3D/V Root & S-OFF (Sprint and Virgin Mobile Only)

This Quick And Dirty Evo 3D/V Root & S-OFF (QADERSO) guide is for current Sprint and Virgin Mobile (VM) S-ON users, rooted or not, who want to get to a rooted S-OFF configuration of the Sprint or VM ICS stock ROM. There are many other ROM and bootloader options that can be pursued from there.
I know that there are similar guides available already, but this one is going to be simple with no choices. If you want another recovery or aren't on Sprint or VM go check out one of the other ones, because this is the "Model T" of guides and will get you exactly the following configuration, which I believe is the best base for the Sprint Evo 3D or Virgin Mobile Evo V at this time:
1. Rooted Sprint ICS build 2.89.651.2 or VM ICS build 1.13.652.2
2. 4EXT Recovery with Updater or Control App
3. JuopunutBear S-OFF with JBear Sprint ICS (1.58.5858) bootloader or JBear VM ICS (1.57.5757) bootloader
If you want to modify this configuration and know how, feel free, but I'm only documenting how to get from your current configuration, whatever that is, to the one above. I am providing tips and references if you get stuck, but please don't ask about other configurations, recoveries, etc., in this thread.
Should you decide to modify the procedure, please explain that in any post made in this thread for assistance. That's your choice, but it would help me and any one else trying to provide support in this and other threads to have that information.
There are tips and references for each step at the end of this post in case you get stuck, but if you read all the instructions and follow this procedure carefully, hopefully you won't need them.
Prerequisites:
1. Sprint Evo 3D or Virgin Mobile Evo V phone that is S-ON, on any ROM, rooted or not.
2. Windows PC or notebook to run the utilities and access the websites.
3. MicroUSB to USB cable to connect the phone to the computer.
4. Shielded wire for the JuopunutBear wire trick.
5. Something to drink while the RUU.exe runs for about 10 minutes.
Before you start, download the QADERSO-V2-S.zip (mirror) file (for Sprint users) or QADERSO-V2-VM.zip (mirror) file (for Virgin Mobile users) and unzip it to somewhere on a Windows PC. It includes all the software you need to complete this procedure.
If you would like a Microsoft Word version of this guide and detailed instructions for the JuopunutBear wire trick, you can download it from here. Thanks to mpgrimm2 for putting that together.
Flashing the RUU.exe in Step1 will reset all the partitions on your phone except those on the SD card so I'd also recommend backing up anything you want to keep to the SD card before starting. If you don't have root yet, MyBackup is a good alternative to Titanium Backup and other utilities that require root.
***Step1: Install ICS RUU
If you are using this guide with a new/replacement unrooted phone you can go to Step2 since flashing the RUU returns the phone to the same stock configuration. VM users should apply the OTA update from the "System updates" options in system settings before starting Step2 if it hasn't already been done since that requires a stock configuration.
VM users: If the November VM OTA update (1.14.652.0) was installed and the phone is rooted with a custom recovery and ROM, please see this post for instructions on how to prepare the phone to run the RUU.exe. If both the November and March OTA (2.95.652.5) were installed there is no way to flash the RUU so proceed to Step2, or if already rooted flash a stock rooted ROM from this post then go directly to Step3.
Sprint users: If the March OTA ((2.95.651.5) is installed and the phone is unrooted proceed directly to Step2. If the March OTA is installed and it's rooted see this post for instructions on how to prepare for flashing the RUU.
Click to expand...
Click to collapse
Start by installing the Sprint 2.89.651.2 RUU.exe or Virgin Mobile 1.13.652.2 RUU.exe from Windows. It doesn't take much longer than flashing a stock ROM and includes all the firmware so the phone will be totally in sync with the official ICS build. Flashing the RUU can also resolve problems with the HTC unlock process if the OTA was used to update to the official Sprint ICS version or a custom recovery and ROM have already been flashed.
If you are already HTC unlocked, relock the bootloader using the "fastboot oem lock" command. You should know how to run fastboot commands from a PC if you have already unlocked.
If you have never HTC unlocked or have relocked successfully, connect the phone to the PC via a USB cable in "fastboot USB" mode then run the RUU.exe from the /QADERSO/RUU directory in Windows. The program has a GUI interface and is pretty much self-explanatory, but there is a readme.doc in the same directory that covers the process and possible errors.
VM users: Now would be a good time to download and install the OTA updates since they will flash updated firmware and patches to the stock software, and cannot be installed once a custom recovery is flashed in Step2. Just go to Settings/System updates/HTC Software, press check now, then download each of the two OTA updates (November and March) and follow the instructions to install them. The software patches will be overridden once a custom ROM is flashed, but the firmware updates will remain and should improve radio reception.
Sprint users: Installing the March OTA at this point will avoid having to flash the firmware only zip file for that update after getting S-OFF. To do that go to Settings/System updates/HTC Software, press check now, then download the update and follow the instructions to install it.
Click to expand...
Click to collapse
***End of Step1
***Step2: HTC Unlock, flash 4EXT recovery and superuser
Navigate to the /QADERSO/Root directory and open a command prompt by clicking on the "cmd" file in that directory. If you have HTC Sync installed go to the Windows control panel and uninstall just the sync program but leave the drivers installed. This is required by the JuopunutBear utility in Step3. If you don't have the HTC Sync program or drivers installed and are not using Windows 8, double click the HTCDriver3.0.0.007.exe file in the /QADERSO/Root directory to install only the HTC USB drivers. If you are using Windows 8 and don't have the HTC USB drivers already installed a compatible .exe setup can be downloaded here.
If you have never done the HTC unlock procedure, go to htcdev.com and signup then follow the instructions to get your bootloader unlocked. The programs you need to do the HTC unlock procedure are already in the /QADERSO/Root directory, so you can skip step 5 on the htcdev website.
If you have already HTC unlocked, you know the routine and need to do it again after flashing the RUU. You can use the same unlock_code.bin from your previous unlock.
Put the phone in "fastboot USB" mode by removing/replacing the battery, holding Power+VolumeDown buttons until the bootloader starts up, highlighting the "fastboot" entry by using the VolumeUp/VolumeDown buttons to navigate, selecting it with the Power button, then connecting it to your computer. The "fastboot" status should change to "fastboot USB".
When the phone is in "fastboot USB" mode, enter the following commands from the prompt:
"fastboot devices" (should show the serial number of your phone, beginning with "HT")
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
After the phone reboots into 4EXT recovery, select the "toggle usb storage" menu item from 4EXT recovery and copy the SuperSU-v0.96.zip file from the /QADERSO/Root directory on the PC to the root of the SD card on the phone. Eject the SD card from the PC and go back to the main menu of 4EXT.
Flash SuperSU-v0.97.zip from 4EXT recovery using the "Install from sdcard" menu item and selecting it from the root of the SD card. Go back to the main 4EXT menu and select "reboot now" from 4EXT and perform the initial setup of the stock ICS ROM after the boot completes.
Your phone now has the 4EXT custom recovery and a rooted stock ICS ROM with SuperSU.
Once the procedure is complete and you've booted into your rooted, stock configuration, you need to install either 4EXT Recovery Updater from the 4EXT website, or better yet purchase and install 4EXT Recovery Control from the Play Store. Then use the update function in the app you chose to get the current version of 4EXT.
You should start the SuperSU app to make sure it is working properly and updated to the current version. BusyBox also needs to be installed from the Play Store for 4EXT and other root apps and I recommend the installer by Stericson.
***End of Step2
***Step3: Perform JuopunutBear (wire trick) to get S-OFF status
Important Note:
The unlimited.io team has withdrawn support for all Windows versions of the JBear utility (controlbear.exe). Do not go to their IRC channel for support while following this guide as they will not be willing to help anyone using Windows instead of Linux for the wire trick. If you are unable to get S-OFF using this guide you will need to flash the RUU again and go to the the unlimited.io website to download a Linux version and follow their procedures.
Since the JuopunutBear wire trick now requires Ubuntu Linux to use the supported procedure Evo 3D users might also want to consider unknownforce's Ultimate Recovery Tool 3.0 which has recently been updated and streamlined. Unfortunately it won't work for Evo V 4G users since there is no Virgin Mobile GB RUU that can be used as part of that S-OFF process.
Click to expand...
Click to collapse
The wire trick is not difficult, but it can be a little confusing. It would be worth spending a little time reviewing the tips and references for Step3 at this point so the process goes smoothly.
Connect the phone to your PC with your stock rooted ROM booted and the USB debug option on in the developer settings.
Navigate to the /QADERSO/JBear directory, right click on controlbear.exe and "run as administrator", and then follow the prompts on the PC and the phone screen. Make sure to have an insulated wire ready for the wire trick, and select the JBear version of the bootloader when that prompt comes up. Yes, it's really that easy to get S-OFF.
If you flash a stock bootloader later it will show ***LOCKED*** as the status, but that's usually not a problem if the phone is S-OFF. It's actually good since that means there is no indication that the phone was ever unlocked, unlike the ***RELOCKED*** status after doing the HTC unlock/relock. By selecting the JBear version of the bootloader, the same fastboot commands will be available from a PC as with an unlocked bootloader.
You may have to activate your phone again after performing the wire trick. That is normal and should be done automatically from the phone on your first boot if it is required.
***End of Step3
WARNING: When you are S-OFF, PG86IMG.zip files can be flashed from the bootloader without being signed, which means you can flash any bootloader or firmware you want. But be careful and always make sure the stuff you are flashing is designed for your phone, or you may have serious problems if you force something to flash that was designed for another carrier or phone.
If you need to change the bootloader (hboot) version to run GB or AOSP ROM's you can find them in post #7 of mpgrimm2's thread on bootloader differences. There are instructions in this post for how to flash another bootloader with this configuration in place if you used this guide.
The following informational posts have been added to this thread:
1. Troubleshooting RUU.exe problems
2. Security questions about rooting and S-OFF
3. S-ON versus S-OFF
4. Information for users already S-OFF
5. How to change bootloader (hboot) when S-OFF
6. Temp root for current GB users
7. Recovery Comparison: TWRP2 versus 4EXT
8. Returning to stock configuration
9. Information on the Aroma installer
10. Updating 4EXT Recovery
11. QADERSO Version 2 with Virgin Mobile added
12. OTA Updates for Virgin Mobile users
13. OTA Update for Sprint users
14. Information for Linux users
15. JuopunutBear update
Please post any suggestions for making this process simpler and easier in this thread, but I intend to keep this guide as barebones as possible.
Tips and References for Step1: Flashing the RUU.exe
Tips
1. Make sure to put the phone into "fastboot USB" mode in the bootloader by removing/replacing the battery and using VolumeDown+Power to boot into the bootloader. The RUU is also supposed to work if you connect the phone to the PC while booted into Android, but I've found fastboot USB to be more reliable.
2. If you get a 17x error it has something to do with the USB connectivity. Make sure your phone is properly connected to the PC and in "fastboot USB" mode and try again.
3. If the RUU.exe stops in the middle of flashing the update, it's OK to cancel the Windows utility and restart it. This has happended to me a few times when I've had custom bootloaders installed.
References
1. HTC Readme.doc for flashing an RUU.exe is in the /QADERSO/RUU directory.
2. Download for HTC driver installer compatible with Windows 8.
3. The mpgrimm2 guide for flashing RUU's.
Tips and References for Step2: HTC Unlock, Flashing 4EXT Recovery and Superuser
Tips
1. On current Windows systems you can open a command prompt in a specific directory by using Windows Explorer to navigate to that directory and pressing Shift+MouseRightClick on blank area, then selecting "Open a command prompt here".
2. Make sure the phone is in "fastboot USB" mode and the bootloader has been HTC unlocked after flashing the RUU.exe or the fastboot commands will fail.
3. If you need to manually boot into recovery it can be done from the bootloader.
References
1. The HTC unlock overview diagram is in the /QADERSO/Root directory
2. The mpgrimm2 guide for flashing recovery and superuser.
3. The HTC Developer website.
4. The 4EXT Recovery website and HTCEvoHacks installation instructions for 4EXT Recovery Updater with video.
5. Instructions for installing 4EXT apps.
6. The SuperSU XDA thread.
Tips and References for Step3: JuopunutBear (wire trick) S-OFF Method
Tips
1. Watch this zedomax video and this timing video before attempting the wire trick and it will be a lot easier.
2. Make sure to backup your SD card to a PC before using it for the wire trick.
3. Remove the back cover to prepare for the wire trick but make sure to watch the phone's screen for superuser requests that need to be approved.
4. Do not touch the uninsulated part of the wire with your fingers while performing the wire trick.
5. Only short taps are required for the wire trick.
6. If unsuccessful with the wire trick try a smaller capacity SD card.
7. If the SD card used for the wire trick gets corrupted it can be reformatted and restored from the backup on the PC.
References
1. JuopunutBear overview, basic instructions and prerequisites.
2. JuopunutBear instructions and downloads for the Evo 3D.
3. Troubleshooting and Support pages on the unlimited.io website.
4. JuopunutBear thread on XDA.

Thanks for the tutorial, I'll let you know if I run into any issues. This will be the first time I root my Evo3D.

Kiotofl said:
Thanks for the tutorial, I'll let you know if I run into any issues. This will be the first time I root my Evo3D.
Click to expand...
Click to collapse
OK, thanks and good luck!
I've updated the download file and the instructions to include the HTC USB drivers for those that don't have them installed already so everything should be in that file to get you to rooted and S-OFF.
ramjet73

Thanks for this!

you sir, are a god among men. I will try this tonight and post the results.
Thanks!

rino655 said:
you sir, are a god among men. I will try this tonight and post the results.
Thanks!
Click to expand...
Click to collapse
Just wanted to say big thank you for posting this guide!
I managed to get Hboot 1.58 S-off. I had 1 failure with JuopunutBear (wire trick) but after 2nd try I was able to succeed.
One advice I can give is to uninstall all drivers and HTC sync and install HTCDriver3.0.0.007.exe from QADERSO\Root folder.
Everything else went smooth.
I've installed MeanROM ICS v2.6 | Sprint 2.89.651.2 but WiFi tether still does not work it seems like its matter of finding correct profile.

JohnnyBeGood113 said:
Just wanted to say big thank you for posting this guide!
I managed to get Hboot 1.58 S-off. I had 1 failure with JuopunutBear (wire trick) but after 2nd try I was able to succeed.
One advice I can give is to uninstall all drivers and HTC sync and install HTCDriver3.0.0.007.exe from QADERSO\Root folder.
Everything else went smooth.
I've installed MeanROM ICS v2.6 | Sprint 2.89.651.2 but WiFi tether still does not work it seems like its matter of finding correct profile.
Click to expand...
Click to collapse
Thanks!
Are you using the WiFi Tether app that came with MeanROM ICS? What usually works with MeanROM ICS is the generic ICS profile with the routing fix checked. I believe the OP for MeanROM ICS says to check MSS clamping as well, but some of the newer versions of WiFi Tether don't have that option, and I've never needed it.
ramjet73

ramjet73 said:
Thanks!
Are you using the WiFi Tether app that came with MeanROM ICS? What usually works with MeanROM ICS is the generic ICS profile with the routing fix checked. I believe the OP for MeanROM ICS says to check MSS clamping as well, but some of the newer versions of WiFi Tether don't have that option, and I've never needed it.
ramjet73
Click to expand...
Click to collapse
I was trying to get WiFi Tether to work and it would not start correctly it would give "starting softap" and "WiFi interface" error is "Show Log".
I even uninstalled one that came with ROM and installed latest wifi_tether_v3_2-beta2.apk from their site and still would not work.
What worked for me is selecting Menu > Change Device-Profile and selecting Generic ICS/JB (wlan0) and of course selecting "MMS clamping" + "Routing fix"
I was just selecting "Generic" and it would not work.
Hope it helps out someone.

Nice guide Ramjet73. The way u put it together should get everyone around all the common errors.
I will definitely get this linked to my other threads as soon as I can.
Sent from my "Up all night, Sleep all day" EVO3D!

Thanks ramjet73.
This is quite thorough. Very nice.
I'm almost wondering if I might be able to automate some of this somehow. Don't hold me to it though. I don't have a whole lot of time, but if I can, I'll see if I can maybe do that.
I guess then, that I'll "hold" the tenth spot just in case.
Thanks,
~co~
Edit: What in the world am I doing? Sorry ramjet73. Still if I come up with something, I'll message you.

closeone said:
Thanks ramjet73.
This is quite thorough. Very nice.
I'm almost wondering if I might be able to automate some of this somehow. Don't hold me to it though. I don't have a whole lot of time, but if I can, I'll see if I can maybe do that.
I guess then, that I'll "hold" the tenth spot just in case.
Thanks,
~co~
Click to expand...
Click to collapse
That would be great!
It would be nice to have it as automated as possible.
ramjet73

ramjet73 said:
That would be great!
It would be nice to have it as automated as possible.
ramjet73
Click to expand...
Click to collapse
Beat me to my edit. I'll see if I can do something. but, no guarantees.
~co~
Edit: I reedited my edit and put back what was originally there, resulting in this post being edited from its original unedited state as well. <- Meta

This is exactly what I was looking for
I am also looking to do my first root. I am still reading other posts. But, my main questions are around restoring the phone back to stock. I have Best Buy protection and if things go bad, I plan to use them and I am trying to figure out what steps I need to take to ensure I can potentially return back to the stock state before going down this path.
Overall, this is probably the simplest guide I have seen so far. Thanks again.. if you have any pointers for me around EVO 3D on Sprint, please let me know.
Thanks.

rosahas said:
I am also looking to do my first root. I am still reading other posts. But, my main questions are around restoring the phone back to stock. I have Best Buy protection and if things go bad, I plan to use them and I am trying to figure out what steps I need to take to ensure I can potentially return back to the stock state before going down this path.
Overall, this is probably the simplest guide I have seen so far. Thanks again.. if you have any pointers for me around EVO 3D on Sprint, please let me know.
Thanks.
Click to expand...
Click to collapse
If you choose the JuopunutBear bootloader as recommended and leave the bootloader status as ***LOCKED*** going back to complete stock is as easy as running the same 2.89.651.2 RUU.exe again, then issuing the "fastboot oem writesecureflag 3" to set it back to radio S-ON. Verify that you have successfully flashed the stock 1.58 bootloader before issuing that command or you could brick the phone.
ramjet73

ramjet73 said:
If you choose the JuopunutBear bootloader as recommended and leave the bootloader status as ***LOCKED*** going back to complete stock is as easy as running the same 2.89.651.2 RUU.exe again, then issuing the "fastboot oem writesecureflag 3" to set it back to radio S-ON. Verify that you have successfully flashed the stock 1.58 bootloader before issuing that command or you could brick the phone.
ramjet73
Click to expand...
Click to collapse
Question... If you have hboot 1.4, and run flash the latest update that has the new hboot, you ARE S-OFF, but it says LOCKED... Correct? Also, if you were to write the secure flag thing to S-ON, and you have the latest hboot, you are TRULY S-ON like you just bought your phone or never had S-OFF and updated, correct? Or is my hypothesis wrong?

wwjoshdew said:
Question... If you have hboot 1.4, and run flash the latest update that has the new hboot, you ARE S-OFF, but it says LOCKED... Correct? Also, if you were to write the secure flag thing to S-ON, and you have the latest hboot, you are TRULY S-ON like you just bought your phone or never had S-OFF and updated, correct? Or is my hypothesis wrong?
Click to expand...
Click to collapse
Yes, that's pretty much true, assuming you never HTC unlocked the phone or the S-OFF method you used returned the bootloader to the ***LOCKED*** status. I know the JBear method does just that, but I've never done the 1.4 downgrade. At one point mpgrimm2 said his bootloader showed ***UNLOCKED*** and I know he did the downgrade to hboot 1.4 to get S-OFF, so I'm not sure that method resets the bootloader S-OFF status.
In the worst case, if your bootloader is currently ***UNLOCKED*** and your radio is S-OFF, you could flash the RUU then set S-ON, root and do the wire trick to get the bootloader status back to ***LOCKED*** but that's a lot of work. OTOH, if you don't do that you can only set the bootloader status to ***RELOCKED*** with the "fastboot oem lock" command and that leaves a flag to HTC/Sprint that your phone was rooted. That's why I always recommend using a custom bootloader instead of HTC unlocking the stock bootloader if you are radio S-OFF and want to run more of the fastboot commands.
The custom bootloaders will usually mask the bootloader locked/unlocked status with a name like "Revolutionary" or "JuopunutBear" so the only way to verify what you currently have for your bootloader status is to flash a stock bootloader.
ramjet73

I had to reread the middle paragraph 3 times to understand it, but that's my understanding too. My hboot does say unlocked/relocked (RL) on it because I did the HTC Unlock at one point, without the Jbear for s-Off.
Sent from my "Up all night, Sleep all day" EVO3D!

ramjet73 said:
When the phone is in "fastboot USB" mode, enter the following commands from the prompt:
"fastboot devices" (should show the serial number of your phone, beginning with "HT")
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
Click to expand...
Click to collapse
I try to enter "fastboot devices" in the Quaderso\root directory, and it tells me
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
What is the problem? I spent 2 hours on something that I will have problems with. Great.
Found out I had to move the files back to the Root Directory. Thanks for an awesome guide!

RevolcFael4 said:
I try to enter "fastboot devices" in the Quaderso\root directory, and it tells me
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
What is the problem? I spent 2 hours on something that I will have problems with. Great.
Click to expand...
Click to collapse
Sounds like you are not in the the \quaderso\root directory when the "fastboot devices" command is being issued from the prompt. See tip #1 for Step2 to open a command prompt in the \qaderso\root directory.
You can also Start/Run "cmd" then use the "cd" command to navigate to the \qaderso\root directory. Either way you should issue a "dir" command from prompt to make sure the contents of the directory are as follows:
C:\tmp\QADERSO\Root>dir
Volume in drive C is OS
Volume Serial Number is 6CF6-A9B2
Directory of C:\tmp\QADERSO\Root
09/16/2012 03:07 AM <DIR> .
09/16/2012 03:07 AM <DIR> ..
09/05/2012 05:52 PM 7,047,406 4EXT_Recovery_Touch_v1.0.0.5_RC6.zip
05/07/2010 12:48 PM 578,611 adb.exe
05/07/2010 12:48 PM 96,256 AdbWinApi.dll
07/16/2011 01:05 PM 183,651 fastboot.exe
07/30/2011 10:31 AM 13,783,568 HTCDriver3.0.0.007.exe
08/14/2012 05:09 PM 7,077,888 recovery.img
09/15/2012 05:53 PM 684,154 SuperSU-v0.96.zip
09/15/2012 06:48 PM 169,793 Unlock_Bootloader_Workflow.pdf
8 File(s) 29,621,327 bytes
2 Dir(s) 291,896,774,656 bytes free
ramjet73

mpgrimm2 said:
I had to reread the middle paragraph 3 times to understand it, but that's my understanding too. My hboot does say unlocked/relocked (RL) on it because I did the HTC Unlock at one point, without the Jbear for s-Off.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
Yeah... I NEVER ONCE ran htc dev on my Evo 3D. The moment I bought it, I declined all updates and waited until THIS DAY happened, and S-OFF'd immediately. I knew better than to update, after knowing about all the trouble people had with the shift and the og evo. Updates are bad, mmmk?
Anyways, I S-OFF'd that night and never looked back... Still have 1.4, and don't feel like giving up my virginity to HTC.
YOU KNOW YOU WANT TO CLICK ME!

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

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

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.

wohohoho...great work

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

ramjet73 said:
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
Click to expand...
Click to collapse
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.

Here's a little preview of 3.0

Unknownforce said:
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.
Click to expand...
Click to collapse
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 ----------
Unknownforce said:
Here's a little preview of 3.0
Click to expand...
Click to collapse
Windows version?

zemaniel said:
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.
Click to expand...
Click to collapse
Oh, yes the first time you RUU might not fully flash everything the first time, you might have to do it a couple times.
zemaniel said:
Windows version?
Click to expand...
Click to collapse
Not possible, unfortunately.

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

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?

thanks for your hard work, this is a massive point for evo's modding :highfive:

ray650128 said:
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?
Click to expand...
Click to collapse
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.

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?

ray650128 said:
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?
Click to expand...
Click to collapse
Hmm, what was your CID before this or what is it supposed to be even?

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)

ray650128 said:
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)
Click to expand...
Click to collapse
Have you tried the RUU EXE while in fastboot USB?

ray650128 said:
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?
Click to expand...
Click to collapse
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

zemaniel said:
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
Click to expand...
Click to collapse
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.

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
Sent from my HTC EVO 3D X515m using XDA Premium HD app

Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)
posedatull said:
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
Sent from my HTC EVO 3D X515m using XDA Premium HD app
Click to expand...
Click to collapse
Nope windows can't detect certain things like Linux can
Sent from my SPH-L710 using xda app-developers app

[GUIDE][TOOL]FUU HTC Evo 3D

General Information
This Has Been Made To Help Those How Have No Clue What There Doing When Upgrading There Firmware Note And Want A One Click That Mimiks HTC RUU
New From Prism Pirate Chest of goodies here it is FUU For The HTC Evo 3D
FUU Definition
Firmware Update Utility
There are a few Firmware flashing threads and lots of zips and good and bad instructions. However, i noticed that many users asked about what they get when they flash what they download and also about how to flash it with S-OFF on various threads. This confusion has occasionally lead to people losing their custom kernels and custom recoveries and/or their SDcard partitions being unintentionally wiped.
I am writing this because i believe in "responsible" sharing. Since the full RUU's aren’t shared but only components (modified as well as unmodified) with often insufficient documentation, which in turn leads to a lot of confusion among the lesser informed users, i will try to catch some of that. I believe that sharing full RUU's would be a lot safer, as only those who actually know enough about it can disassemble them. RUU’s do always reassure users that there is a guaranteed and safe way to go back.
FUU How To
[*]Download the firmware you want
[*]then run the installer
[*]install it to folder you want to any folder will do
[*]then run the tool and upgrade or downgrade your firmware
Prerequisites:All you need is a Windows System with current drivers and maybe HTC Sync Manager installed, it is better to have HTC Sync uninstalled and only the drivers left. Just try if the FUU runs without HTC Sync. On my system, i am always greeted with an “Error 170" if i try to run the FUU on a booted Android - it doesn’t recognize the phone with ADB. This is a typical driver and/or ADB error. Solution here: make sure you have the latest driver suite. FailSafe way to get them is to install HTC Sync Manager (remove it if you don’t like it afterwards but leave the drivers in the sytem!).
ZIP Flash HowTo
Step-By-Step:1. If device is booted into Android, reboot into bootloader by running:
Code:
adb reboot bootloader
1.a Or else, if your device is in a different state or you just prefer the button method:
Press Power for 15 seconds and hold Vol Down at the same time, when the screen and charging LED go dark immediately release Power but keep holding Vol Down until you see the bootloader screen. Notice: If the device refuses to reboot, you might need to hold it to a bright light with its light sensor. This is a very specific bug in the HTC ONE. The light trick always works.
2. Now place the Firmware_named_something.zip into your adb/fastboot folder
3. Now run:
Code:
fastboot oem rebootRUU
4. Followed by:
Code:
fastboot flash zip Firmware_named_something.zip
(replace "Firmware_named_something.zip" with the name of your zip)
5. Now check the console output. It should approximately look like this:
“flush" certainly means “Flash" so press the arrow up key on your keyboard and enter to run the flash command again without reboot...
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot! The bar will only fill up to 100% once you type the following command:
6.
Code:
fastboot reboot-bootloader
Error handling strategies:IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL it could not boot up anymore! It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (dont use hubs! Always straight-to-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot... there are many possible sources for flash fails.
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 you did not lock your bootloader (Needs a relock for S-ON phones that want to update the firmware.)
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn’t help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader is required. This error won’t show on S-OFF phones.
- Error 155 can also mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of wrong region lock.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers or ADB/Fastboot binaries. One way to solve is to run the exe with the phone already in Fastboot mode. Else you will have to dig into your windows driver system and try to fix there. Best option: re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn’t work with ADB and Fastboot.
I always test all of these zips on my own device. But as always, flash at own risk. You're writing to critical parts of your phone. If anything goes wrong along the way, you might be bricked.
FUU Downloads (Windows only)
Update: added Hboot 1.58 FUU
Download
MD5: 995a8b883a5e39af471a93a84b4ff52d
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.57
Download
MD5: 87acbac59f169b32900e58f34e3390e1
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.50
Download
MD5: 233943ae4117d2fe64726afed8231b18
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.40
Download
MD5: 054e40f479b2075a20f12d5426d44bc3
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.30
Download
MD5: 04b13923379267a82d93cf913de62040
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.04 ENG
Download
MD5: 476a819ce37ff8fae2960de9dc2969a2
This FUU is A Stock Hboot. Contents: Hboot from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
CreditsThank You Sneakyghost For The Tool And The Op
ramjet73 My mentor for HBOOT Modding
ramjet73 For The Hboots Witch I Modify Of off
DisclaimerYou are aware that writing to the security protected partitions increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on various phones at time of posting, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.

Five star guide flashalot much appreciated
Sent from my PG86100 using XDA Premium 4 mobile app

Nice job!! Thank you!

busventinc said:
Five star guide flashalot much appreciated
Sent from my PG86100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cant take credit for the guide thank @Sneakyghost
I just made the proper edits for the evo and my one s
newdad23 said:
Nice job!! Thank you!
Click to expand...
Click to collapse
No problem

Thanks so much for this Flashalot!
Question on these, apologize in advance if its off base or nonsense.
Currently have a friend who is running 1.58 hboot S-ON, unlocked bootloader (htcdev) with MIUI 3.2.22 ROM. Would it be possible to use these to downgrade his hboot version and run revolutionary S-OFF and/or install JB ROM? Or would it be best to relock, revert fully to stock and use JuopunutBear method?
Thanks in advance

snackle said:
Thanks so much for this Flashalot!
Question on these, apologize in advance if its off base or nonsense.
Currently have a friend who is running 1.58 hboot S-ON, unlocked bootloader (htcdev) with MIUI 3.2.22 ROM. Would it be possible to use these to downgrade his hboot version and run revolutionary S-OFF and/or install JB ROM? Or would it be best to relock, revert fully to stock and use JuopunutBear method?
Thanks in advance
Click to expand...
Click to collapse
This is for s-off only sorry this is what you need
http://forum.xda-developers.com/showthread.php?p=31617712 it has it instructions on how to s-off
Sent from my PC36100 using Tapatalk 2

Flashalot said:
This is for s-off only sorry this is what you need
http://forum.xda-developers.com/showthread.php?p=31617712 it has it instructions on how to s-off
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply Flashalot
Exactly what I was expecting but figured I should ask just in case. Thanks again for your time.

snackle said:
Thanks for the quick reply Flashalot
Exactly what I was expecting but figured I should ask just in case. Thanks again for your time.
Click to expand...
Click to collapse
FYI, depending on the current firmware level of the phone you may not be able to run an ruu after the 2.89 base (they don't exist) without being s-off. If jbear doesn't work for you see..
See my reference post in Unknownforce's Ultimate Unbricking and hboot Downgrade Tool thread. It is known to work by bricking it twice.
Sent from my TouchPad using Tapatalk

mpgrimm2 said:
FYI, depending on the current firmware level of the phone you may not be able to run an ruu after the 2.89 base (they don't exist) without being s-off. If jbear doesn't work for you see..
See my reference post in Unknownforce's Ultimate Unbricking and hboot Downgrade Tool thread. It is known to work by bricking it twice.
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up mpgrimm2. I believe he has a nandroid backup from just after he completed the htc unlock, still running stock rom. If it does turn out to be 2.95.651.6, would he able to restore this nandroid and continue with jbear method?

I know jbear will need to be mostly stock if not full stock. That nand backup may work depending on if jbear requires a relock and stock recovery or not but I don't recall. Things got a little vague when they moved support off of xda to their own site and stopped supporting windows based installers.
I'm sure Ramjet73 had some FAQ's in his thread for the old windows version that would answer it though.
Either way I know Unknownforce's Tool will work for s-off.
Sent from my "Up All Night Sleep All Day" Nexus 5!

Solved CDMA Sprint Hboot 1.58 Total noob guide for S-off[ROOT]

Hey, I am trying to root my HTC evo 3d phone with hboot 1.58. I followed all 12 steps on htcdev.com, except on the final step I punch in: fastboot flash unlocktoken Unlock_code.bin and enter, then noting happens. The phone is supposed to reboot with the unlock option..but nothing happens
Also, the phone is Sprint CDMA if that makes any difference, so no sim card
....................................................................................................................................................................
THREAD SUMMARY
K finally got th phone rooted so here is what you have to do. The following applied to my ***locked*** S-ON Sprint HTC Evo3d with hboot 1.58 but should work with any other version higher than hboot 1.40.
The purpose is to get S-OFF(ROOT the phone) and also continue to use your factory HbOOT 1.58 and main version in the end.
1. Brick the phone carefully following steps outlined in unknownforce's [TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset). Scroll down to the "Downgrade/Unbrick" section and begin the bricking process with the PG86IMG.zip he mentions in "things you'll need".(place the zip on SD card in the main directory and name it PG86IMG)
2. Once phone is bricked(indicated by SOLID and very dimly lit charge light with the AC charger connected. Also the phone will not turn on or boot), download latest version of URT 3.1(first link in [TOOL] thread), continue to the second step 2 which involves booting up with Linux live boot CD on your PC, OR you can use URTLiveCD 1.0 and you will not need Linux
I did it the hard way an used latest version of URT with Ubuntu v12.04 LiveCD. I would recommend URTLiveCD 1.0 as you will boot straight to the tool and will not need the Ubuntu terminal.
3. After successfully completing downgrade with URT 3.1 downgrade, boot up to your new HBOOT 1.40 bootloader screen and enter fastboot USB mode. CHECK THAT THE MAIN VERSION HAS BEEN LOWERED ALONG WITH THE HBOOT.
Log back into windows
3.(A) If you haven't done this yet, get a fastboot PC command directory to retrieve all phone identification info from the bootloader. I used ROOTEVO3DNEW to check my phone's identity info at this point(though there are many programs that do the same thing). Create a new folder in C:\ and name it rootevo3dnew. Unzip all rootevo3dnew.zip contents into that folder.
Now open the command prompt with the phone connected to PC in fastboot USB. Type cd \rootevo3dnew and enter. Now type the following: "fastboot getvar all" (without quotations) and enter. A list should appear. Check that you have: (bootloader) version-main: 0.01.651.1. If this number is still 2.95.XXX.XXX or something close to it, then YOU MUST BRICK THE PHONE AGAIN. See posts starting at #35 of this thread for a more detailed guide through the second brick. It may be very tricky but very much the same process!!!!!
4. After successfully lowering HBoot to 1.40 and the main-version to 0.01.651.1 you can run the 1.13 RUU.exe found HERE: http://d-h.st/h1p . Connect the phone to fastboot USB and RUN the .exe....after the 1.13 .exe successfully runs, your main version should now be 1.13.651.7...again, checking using your rootevo3dnew tool from 3.(A) above....
5. REVOLUTIONARY S-OFF. Very simple, download for windows(or Linux) and fill in your info and retrieve you BETA key. Run REVOLUTIONARY application (which will run in the command prompt) and after successfully completely revolutionary S-off, YOU ARE ROOTED...continue to step 6
6. RESTORE your main version to 2.95(from 1.13) by running the 2.89 zip (HERE . Place this .zip in your main directory(RENAME IT PG86IMG) on the SD card and let it unzip and install it from the bootloader.
After that, you are pretty much finished!! boot up to android(main version 2.89) and let system updates detect and bring you back to 2.95.xxx.xxx..
....
Download and Install a custom recovery. Rename that .zip PG86IMG and install from bootloader as you did with the 2.89 zip. Now you have a custom recovery where you can backup and restore, install ROMS or other software without having to rename it PG86IMG every time, wipe partitions and lots of other stuff...
Now, download this and place it on your SD main directory. Then, using your new recovery(by selecting "recovery" in bootloader menu), select "install from sdcard" and "choose zip from sdcard", select the SuperSU zip and let it install. Reboot, get to homepage, and install SuperSU from the play store. You now hae an administrative super APP that will let you choose which apps are given root access.
Custom ROMS can be installed the same way from the custom recovery. I am currently using Negalite BluRom and loving it
...
THE 6 STEPS OUTLINED HERE PRETTY MUCH COVER EVERYTHING FROM THIS THREAD
HUGE THANKS TO USERS MPGRIMM2 AND BRIAN706 FOR NEARLY 3 DAYS OF HARD WORK !!

Did you get your motherboard replaced at some point of time?
Can't think of a good sig

donkeykong1 said:
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
Click to expand...
Click to collapse
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?

otto325 said:
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
Click to expand...
Click to collapse
On the phone?
Can't think of a good sig

donkeykong1 said:
On the phone?
Can't think of a good sig
Click to expand...
Click to collapse
Oh ok, what the hell..No, I just got the phone on ebay for $30, currently locked and I am trying to root it. Some Brittney girl owned according to phone identity info left on the phone

Do I need to downgrade the hboot from 1.58 to 1.4? Sorry I'm really new to smartphones, any help is really appreciated

Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.

Brian706 said:
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Click to expand...
Click to collapse
THANKS
main version 2.95.651.5. If I factory reset the phone and discard updates, will the main version reset to 2.89 making the RUU possible?
EDIT: factory reset and no updates did not bring main version down to 2.89
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
Also check most recent post (#508) in the guide thread.
http://forum.xda-developers.com/showthread.php?t=1889438&page=51

Factory reset won't affect your main version

As DK mentioned, a factory reset only resets your current build. It would only take you back to the point of the last OTA update.
Unfortunately, you can't lower the mainversion without the bootloader unlocked, so it's a catch 22 there.
As a long shot, you might look into the new towelroot, thought I really don't think it will work for this phone because HTC locks down the /system partition. It would at least be worth looking in to.
As far as the hboot downgrade method (I assume you mean THIS) it was intended to downgrade from 1.50 Gingerbread to 1.40 Gingerbread. I have no idea if it will work to downgrade from 1.58 ICS?? You might want to ask around a little about that.
Okay... I just saw your posts in the other thread, have you actually received the unlock token from HTC?
IE, you received a file via email named Unlock_Code.bin that you placed in your fastboot directory and then typed the command: fastboot flash unlocktoken Unlock_code.bin ??
Also, when you say nothing happens after running the command, something must happen whether it's the intended results or not. Can you tell us what the command prompt returns after running the command? Maybe just copy/paste it here.
There will either be an error or a confirmation after running the command.

Comes up as successful on the command prompt. But the phone does not reboot or direct to the unlock screen. I just remains on the fastboot USB screen and does nothing.
C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.163s

Thanks for that... That's a bummer. Looks to me like you have the motherboard swap issue. It really sucks that you can't RUU.
It looks like someone answered the question in the other thread though about the hboot downgrade method.

So I got the HBOOT downgrade(0.8.2) boot for a disk but it says the phone needs to be bricked before the downgrade..
That's where I'm at now basically, I'm going to do a little more reading on bricking...
Also would be good to have confirmed that this downgrade will work starting with hboot 1.58, so I don't mess anything up
mpgrimm2 may have found found his way over here from from the [Guide] thread
Also I hope I am downloading the correct RUU's. I had to fish them from various searches because the link supplied in Unknownforce's thread is invalid:
2.17 RUU:
http://d-h.st/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
1.13 RUU:
http://d-h.st/Xrp

mpgrimm2 said:
Well. Post that in Unknownforce's Ultimate Recovery Tool thread so you are not "off topic" here.
I haven't used the Evo3d in a while but you should probably look over my ...
Post 781 in Unknownforce's thread and the follow up posts right after.
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself)
Click to expand...
Click to collapse
Fyi, I think Unknownforce indicated in one of his first 3 posts that u can brick with the last 2.95 PG86IMG.zip file he linked and then downgrade to 1.13 for s-off. Have to go check...
Keep in mind that you may want to considering posting any issues with the URT/Downgrade tool in Unknownforce's thread if you want any chance of assistance from him.
Bad link in his op but this post has it...
Unknownforce said:
Well, with the 2.95 OTA, they included the HBOOT in the firmware, so it's now much faster of a load time for PG86IMG when doing the brick.
I pulled the new PG86IMG.zip from the OTA update, and it's only 19MB, which takes only 15-20 seconds to fully load and be ready to press volume up to update... this will significantly cut down on the time it takes to downgrade, as you can re-try over and over very quickly now.
Here's the PG86IMG file -> http://d-h.st/3p8
Click to expand...
Click to collapse
And just as a reference for you later I will quote myself from Ramjet73's 2.95 ota update thread
mpgrimm2 said:
ramjet73 and others. I see we still don't have any source for the 2.95.651.6 RUU's. Since I just went ahead and reset my 2 Evo3d's back to stock/S-off as a backup here are the files I had to step through if you want to add or host them directly:
- PG86IMG 2.89.651.2.zip - 449.18 MB
Full RUU.zip for use in bootloader (rename to PG86IMG.zip & place on /sdcard)
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.5-2.89.651.2_release_307948lagg6bmccb9c63ip.zip - 51.11 MB
2.89.651.2 update to 2.95.651.5 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
This is the last official update that just downloaded to my phone after the other Ruu's/updates that were posted previously
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z.zip - 10.59 MB
2.95.651.5 update to 2.95.651.6 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
Wish someone with HTC/Sprint access would post up the latest full RUU. It was a bit of a pain stepping through the updates, but definitely easier being s-Off. Seems that if someone is S-On with the 2.95.651.6 update and can't get past step 13 of the HTC Unlock or needs to RUU back, their only option is Unknownforce's Hboot Downgrade Ultimate Toolkit and "Brick it Twice" to get back to an earlier version for Revolutionary S-Off and then go through the updates from 2.89 on up.
Hope this helps others.
EDIT:
I may be too tired at the moment to figure this out, but for some darn reason both the official OTA Updates would not flash from the bootloader on a stock 2.89.651.2 phone with S-Off (both phones actually). Didn't matter if it was renamed PG86IMG.zip or left as officially downloaded to sdcard/download and booting into the stock recovery. The MD5 of my 651.5 update file matches Ramjet73's as well. But If I connect to wifi, do a system update, let it download (how I got the files) and reboot automatically, it works fine and updates without issue.
Click to expand...
Click to collapse

Forgive me for being such a noob with this stuff.
I'm reading about hboot 1.58 needing to be bricked twice to be able to run the 1.13 RUU.
So to start, do I place the 18.7mb PG86IMG .zip (from the second quote in your last post) in the "download" folder of the sd card?
The stock
(OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z)
Click to expand...
Click to collapse
is there, so do I remove that one and replace it?
I don't think so but just to be sure, I drop the 18.7 PG86IMG zip folder in downloads and begin the brick process, then run the hboot 0.8.2 to downgrade?
*EDIT* ok, place in the MAIN directory. It's working and is unloading the .zip in bootloader
I need a new data sync cable, mine has started intermittently losing connection off and on...going to wait until I have a new one before I go any further.
Also, the latest version of ubuntu that Linux offers did not work. I found an earlier version(12.04) and the boot disk works so I am good to go on that

What is Hboot 0.8.2 ? Are you using Unknownforce's URT 3.1 Tool and following the "Downgrade/Unbrick" section?

This one:
http://forum.xda-developers.com/showthread.php?t=1563342

Yep, that is an outdated/earlier version. You need to use the Ultimate Recovery Tool from Unknownforce's thread as I linked earlier (URT v3.1) and use the LiveCd link.
see here
Sent from my "Up All Night Sleep All Day" Nexus 5!

THANKS
Well I just did a dry run with the Linux boot disk and terminal. Extracted downgrade.zip to HOME folder, ran the commands. I'm getting the correct code returns in the terminal. I got up to the:
Code:
Step 1... Plug in Device while holding down Volume Down key...
Waiting for device...
Just a matter of getting a new data sync cable now and I can do this...
Again thanks for your help, I'm pretty new to this process I've never altered a devices firmware manually before so it's an awesome experience as well..
Will report back in a couple days, hopefully with a newly rooted phone
--------
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?

otto325 said:
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
Click to expand...
Click to collapse
Yep. Previously...
mpgrimm2 said:
....
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself) <<<--- HERE
Click to expand...
Click to collapse
Sent from my "Up All Night Sleep All Day" Nexus 5!

Better Mobile App

welcome