[TOOL][ROOT] Shift ROOTility [1.13.13]

CNexus

Senior Member
May 17, 2012
9,009
13,993
263
~/android
You've been waiting patiently for it and it's finally here.
Welcome to the





Code:
Combination of easiest methods
Integrated Console
All-in-one root
99% Automization (e.g. Not possible to detect fully booted phone through adb/shell)
Logging enabled for easy debugging
Will be updated periodically (as, and if, new versions are released)





Q. Will this root the latest OTA (2.77.651.8)?
Yes. This utility supports all releases of Android for the EVO Shift

Q. Does this work on Linux?
Mostly. I am still ironing out a couple bugs, but since this is written in java, a large chunk of the work is already taken care of by that.

Q: My phone goes into a bootloop after rooting 2.3.4. Did I do something wrong?
No. That is supposed to happen. Assuming you already have the downgraded PG06IMG.zip on the root of your sdcard, you can immediately click "OK" in my utility when prompted so that it takes you to the bootloader to downgrade. If not, you need to turn off your phone, get the PG06IMG.zip on the sdcard and then manually go into bootloader (Power off/Battery pull then Power + VolDown)

Q: After downgrading to 2.2, I tried to temproot with Visionary and it gives me a black screen. How can I fix this? Thanks @asbrand!
Press the home button to exit Visionary, then open it again and attempt to temproot, it should go through this time. I dont know why this happens, but I've had it happen to me as well.

Q: Does this tool give me full S-OFF / unlocked bootloader? Thanks Nooblube
This tool gives you S-OFF (Nand unlocked), and also gives you an unlocked bootloader.


Before starting: Make sure you have installed the HTC USB drivers. If you have not, go to THIS thread, download the ZIP and install both files. Additionally, make sure your phone is formatted to FAT32. If not, make a backup, format it to FAT32, move your files back, and get started.
Windows only: If you have adb in your $PATH, you do not need to download the zip.
Linux only: You MUST download the adb_linux and place the files into the same directory as the utility, even if you ALREADY have adb in your $PATH (absolute file path must be used by utility when running on Linux)
The latest version of Java must be installed to run this utility. (Java 7)

Rooting 2.2
  1. Downloads adb_windows, adb_linux, or adb_mac depending on your OS
  2. Download the root2.2.zip file
  3. Download the utility.jar file
  4. Place the adb files into the same folder as the jar
  5. Extract the root2.2 folder into the same directory as the jar (see picture). DO NOT RENAME THE FOLDER TO ANYTHING BUT "root2.2" OR IT WILL NOT WORK.
  6. Run the utility, thoroughly following ALL prompts and prerequisites

Rooting 2.3.3
  1. Run the 2.3.4 RUU (either one, preferably the 2.77.651.3 version)
  2. Follow the instructions for rooting 2.3.4
Note: There is a method for rooting 2.3.3 directly but I couldn't test it (no RUU found)


Rooting 2.3.4
  1. Follow steps above for rooting 2.2
  2. Download the root2.3.4.zip and extract the FOLDER into the same directory as the utility (same way as with root2.2 folder)
  3. DO NOT RENAME THE FOLDER TO ANYTHING BUT "root2.3.4" OR IT WILL NOT WORK.
  4. Run the utility, throughly following ALL prompts and prerequisites

Folder structure


Warning
You will be on older radios after rooting. Download the ZIP with the most recent radios, WiMAX, and touchscreen firmware from HERE.
Instructions to update:
  1. Download the file from the URL above. Make sure that it is named "PG06IMG.zip" (without the quotes, on Windows 7 the extensions are hidden by default so make sure you are not naming it "PG06IMG.zip.zip" by accident)
  2. Place the file on the root of your sdcard (meaning not inside any folders, just copy and paste to main sdcard drive)
  3. Turn off your phone and go into bootloader by pressing Power+VolDown
  4. Your phone should find the PG06IMG.zip file and commence the update process, follow the onscreen prompts to update the firmware on your phone
Note: This does not eliminate your root privileges or unroot your phone, it merely updates the radios and touchscreen.
IMPORTANT: Your sdcard must be formatted to FAT32 for this to work. If it is not, make a back up, format, and then move your files back and then start this update process.

Note: Please realize that I am only one person with one phone. I could not have possibly tested all scenarios, so if you find a bug, post what the bug is and I will fix it as soon as possible.

As a precautionary note, also check the md5sum of the files on your own. The utility checks some core files, but the rest is up to you, I recommend using THIS commandline one.

DISCLAIMER: I take no responsibility for your actions. However, I would be more than happy to troubleshoot any problems you encounter, post what your problem is and attach the log file too.
 
Last edited:

CNexus

Senior Member
May 17, 2012
9,009
13,993
263
~/android
Last edited:

CNexus

Senior Member
May 17, 2012
9,009
13,993
263
~/android

Code:
[B]1/13/13 - v0.50 [/B]
 - Added ability to flash files to different partitions
 - Reboot menu is now fully functional (no longer experimental)
 - Added link to standalone "FlashImage Tool v1.0" in OP, also packaged in the utility now

[B]12/10/12 - v0.49 [/B]
 - Internal md5sum checking for all dependent files (no need to download md5sum.exe anymore)
 - Optimized code, removed unnecessary files -> significantly smaller file size. (50.48 KB)
 - Reboot menu now included ( Advanced tab > Reboot Menu) [[B]Experimental[/B]]

[B]12/2/12 - v0.47[/B]
 - Miscellaneous bug fixes. 2.77.651.8 root now works (accidentally checking Android version instead of firmware number)

[B]11/30/12 - v0.46[/B]
 - Added the ability to toggle ADB connection between Wifi and USB.

[B]11/29/12 - v0.44[/B]
 - [B]IMPORTANT[/B]: Fixed the 2.3.4 not running (accidentally running 2.3.3 root, which I had left unimplemented, hence the window staying blank and the log being blank as well). The utility should now function correctly for everyone using it.

[B]11/27/12 - v0.42[/B]
 - Fixed md5sum checking for hboot_eng.nb0 that would sometimes be faulty.

[B]11/26/12 - v0.41[/B]
 - Added support for Linux. Still a couple bugs, but they will be ironed out quickly. Note: Must give adb and md5sum executable permissions for it to work.

[B]11/22/12 - v0.4[/B]
 - Initial build released, tested from all software versions
 - Integrated console added
 - Logging added
 
Last edited:

CNexus

Senior Member
May 17, 2012
9,009
13,993
263
~/android
If you broke your phone, how can we know this is safe? I'm hoping it is, because if so it's greatly needed and appreciated.
I broke my phone testing...but ive also dropped it. This tool is try at your own risk, but it is safe to use, to the best of my knowledge.
I believe my problem is a hardware issue anyway.

Sent from my JB'd speedy
 
Last edited:

cmags

Senior Member
Dec 22, 2010
130
12
0
Lowell, MA
Perfect timing on this, I had done the 2-step unroot process becuase I was going to sell my Shift on craigslist after upgrading to the Photon Q, but the Q is proving to have all sorts of problems, especially with the LTE network, so I think I may follow Vicodan's footsteps and return to the Shift. I figure if his expertise can't overcome the software and network problems on the Q, I can't either.

---------- Post added at 11:16 AM ---------- Previous post was at 10:58 AM ----------

Ok, so first attempts aren't going so well. First a couple notes:

Might want to include a note about Java being required to run a .jar - new PC didnt have it installed yet and double-clicking the .jar didn't do anything at all).

Also, in the instructions you don't mention downloading md5sum.exe and putting it in the folder, but I see it later in the directory tree. My first run of the utillity I didn't have it there, second attempt its there, but same results:

When I run the utility (v0.42), it comes up with the Prerequisites screen, I confirm my settings, then click next (or ok, or whatever the button said). The utility recognizes my phone and software version (2.77.651.3). I click Root Now! and the utility's console blanks out, and nothing happens, either in the utility or on my phone. Is there anything I can do to see what its hanging up on?

Edit: Here's my directory tree:

Code:
c:\RootEvoShift>dir
 Volume in drive C has no label.
 Volume Serial Number is 104A-11BE

 Directory of c:\RootEvoShift

11/28/2012  11:09 AM    <DIR>          .
11/28/2012  11:09 AM    <DIR>          ..
11/28/2012  10:50 AM           191,488 adb.exe
11/28/2012  10:50 AM            96,256 AdbWinApi.dll
11/28/2012  10:50 AM            60,928 AdbWinUsbApi.dll
11/28/2012  11:04 AM                 0 log-11282012.log
11/28/2012  11:09 AM                 0 log-11282012.log.lck
11/28/2012  11:07 AM             2,048 md5sum.exe
11/28/2012  10:50 AM    <DIR>          root2.2
11/28/2012  10:49 AM    <DIR>          root2.3.4
11/28/2012  10:48 AM            41,821 speedy-root-utility-v0.42.jar
               7 File(s)        392,541 bytes
               4 Dir(s)  367,063,105,536 bytes free
 

CNexus

Senior Member
May 17, 2012
9,009
13,993
263
~/android
Perfect timing on this, I had done the 2-step unroot process becuase I was going to sell my Shift on craigslist after upgrading to the Photon Q, but the Q is proving to have all sorts of problems, especially with the LTE network, so I think I may follow Vicodan's footsteps and return to the Shift. I figure if his expertise can't overcome the software and network problems on the Q, I can't either.

---------- Post added at 11:16 AM ---------- Previous post was at 10:58 AM ----------

Ok, so first attempts aren't going so well. First a couple notes:

Might want to include a note about Java being required to run a .jar - new PC didnt have it installed yet and double-clicking the .jar didn't do anything at all).

Also, in the instructions you don't mention downloading md5sum.exe and putting it in the folder, but I see it later in the directory tree. My first run of the utillity I didn't have it there, second attempt its there, but same results:

When I run the utility (v0.42), it comes up with the Prerequisites screen, I confirm my settings, then click next (or ok, or whatever the button said). The utility recognizes my phone and software version (2.77.651.3). I click Root Now! and the utility's console blanks out, and nothing happens, either in the utility or on my phone. Is there anything I can do to see what its hanging up on?

Edit: Here's my directory tree:

Code:
c:\RootEvoShift>dir
 Volume in drive C has no label.
 Volume Serial Number is 104A-11BE

 Directory of c:\RootEvoShift

11/28/2012  11:09 AM    <DIR>          .
11/28/2012  11:09 AM    <DIR>          ..
11/28/2012  10:50 AM           191,488 adb.exe
11/28/2012  10:50 AM            96,256 AdbWinApi.dll
11/28/2012  10:50 AM            60,928 AdbWinUsbApi.dll
11/28/2012  11:04 AM                 0 log-11282012.log
11/28/2012  11:09 AM                 0 log-11282012.log.lck
11/28/2012  11:07 AM             2,048 md5sum.exe
11/28/2012  10:50 AM    <DIR>          root2.2
11/28/2012  10:49 AM    <DIR>          root2.3.4
11/28/2012  10:48 AM            41,821 speedy-root-utility-v0.42.jar
               7 File(s)        392,541 bytes
               4 Dir(s)  367,063,105,536 bytes free
Thats odd, I downgraded my phone from 2.77.651.3 before I even posted...the thing is I can't even test it anymore because my phone will not show up in ADB (hardware issue, I'm gonna be taking it in soon)
Can you attach the log file the utility makes?
And also, try running the utility again, when it hangs, open a cmd window and type "adb kill-server" and then "adb devices" and make sure your device is showing up as "device"

Sent from my JB'd speedy
 

cmags

Senior Member
Dec 22, 2010
130
12
0
Lowell, MA
Adb shows my device, but the logfile is 0 byte. Nothing to see in it. Any way to get at the backend java console to see what's happening, or maybe you have a debug build?
 

CNexus

Senior Member
May 17, 2012
9,009
13,993
263
~/android
Adb shows my device, but the logfile is 0 byte. Nothing to see in it. Any way to get at the backend java console to see what's happening, or maybe you have a debug build?
Did you install the latest version of java? My program runs using java 7

Sent from my JB'd speedy
 

CNexus

Senior Member
May 17, 2012
9,009
13,993
263
~/android
Yes, installed the latest today from java.com.
Sorry dude, I don't know why its not logging or why it hangs :\
I'll take a look at the code again and see, but I swear that I downgraded from 2.3.4 just the other day...

I will try to test it on my own phone but I've been having issues connecting it to adb

Sent from my JB'd speedy