HTC EVO Shift 4G

From RootzWiki
Jump to: navigation, search
EVO Shift 4G
HTC EVO Shift 4G.jpg
Specification
Manufacturer: HTC HTC-icon.png
Released On: January 9, 2011
Android Version: 2.3.3
Shipped With: 2.2
Product Model: PG06100
Product Device: speedy
Model Number: Not Known
P___IMG: N/A
Dimensions: 117 mm (4.6 in) H, 60 mm (2.4 in) W, 16 mm (0.63 in) D
Weight: 167 g (5.9 oz)
Carriers: Sprint
Display: 3.6-inch WVGA capacitive multi-touch LCD
CPU: 800 MHz Qualcomm MSM7630 Snapdragon
GPU:
RAM: 512 MB
Internal Memory: 2 GB
Memory Card: 2 GB Class 2 Micro-SDHC, expandable to 32GB Class 10 Micro-SDHC
Mobile Radios: Dual-band CDMA2000/EvDO Rev. A (800/1900 MHz), 802.16e WiMAX (2.5-2.7 GHz)
WiFi: 2.4 GHz 802.11b/g/n
Bluetooth: Bluetooth 2.1 + EDR
FM Radio: Yes
GPS: aGPS/GPS
Battery: 1500 mAh Lithium-ion
Camera: 5.0 MP rear-facing with auto-focus and LED flash
Secondary Camera: None
HDMI Out: None
USB Connector: Standard micro-USB
Additional Features: 3-axis accelerometer, digital compass, proximity and ambient light sensors
Rooted: Yes pre-2.3.3
Locked Bootloader: User unlockable pre-2.3.3


Contents

Rooting your HTC Evo Shift 4G

This guide is not applicable if you are running Android Gingerbread 2.3.3

Prerequisites

Download the files needed, here, and extract them to the root of your SD card

Android SDK with ADB (Make sure you have working drivers)

Lets Get Started!

1. Gain temporary root using Z4Root or Visionary

2. Open a Terminal or Command Prompt and change directories (cd) to your platform-tools directory (Wherever adb is located)

3. Once in your SDK directory type (Allow SU Permissions when prompted)

adb shell
su
md5sum /sdcard/Shift/hboot_orig.bin 
md5sum /sdcard/Shift/hboot_eng.nb0

The above MD5s should be: 386c19451e8dd18f9b98fad6b11be4c0 hboot_orig.bin & 60ec1006e6ec2e8acb370d6aad35b17e hboot_eng.nb0

If the above MD5's do not match what you got in steps 3 & 4 then redownload the files and DO NOT CONTINUE!

SPL Flashing

This next part involves a slight risk of bricking, especially if you have bad md5sums as listed in the above steps. Take you time on this part!

1. If you happened to exit your ADB shell, reopen it and type su (Allow SU Perms when prompted)

2. Run the following commands and DO NOT REBOOT

dd if=/sdcard/Shift/hboot_eng.nb0 of=/dev/block/mmcblk0p18 

(This last output should read 60ec1006e6ec2e8acb370d6aad35b17e if it does then you can reboot)

dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check.nb0 
md5sum /sdcard/Shift/hboot_check.nb0 

Ignore next paragraph if the above MD5s match

If you get a wrong MD5...

...then it is recommended that you flash back to stock by typing these commands

dd if=/sdcard/Shift/hboot_orig.bin of=/dev/block/mmcblk0p18
dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check1.bin
md5sum /sdcard/Shift/hboot_check1.bin 

The last output should read 386c19451e8dd18f9b98fad6b11be4c0 If it does not then DO NOT REBOOT and keep trying!

Perm Rooting

1. Shut off your phone, then reboot into bootloader by holding power + volume down till it boots into bootloader mode

2. At the top of your display look for the words "s off" If you see that then reboot into Android, if not then you failed somewhere when flashing hboot

3. Put the phone into Airplane Mode (you can do so by holding power until the power menu pops up)

4. Temp root with visionary

5. Once temp root is obtained, attempt perm root with visionary If all goes well then you are Perm Rooted!

Recovery

1. Open an ADB Shell and gain SU by typing
su
2. In the terminal type
dd if=/dev/block/mmcblk0p25 of=/sdcard/Shift/wimax.bin 
dd if=/dev/block/mmcblk0p30 of=/sdcard/Shift/udata_wimax.bin 

You have now successfully backed up your wimax partitions

3. Download this file and extract the .img to wherever fastboot is located on your computer

4. Open a terminal or command prompt and cd to the location of fastboot (as well as your recovery.img)

5. Type the following command

 fastboot flash recovery recovery.img 

6. Now boot into recovery to see if it worked, if so then enjoy your root! :)

Original Guide located here

DISCLAIMER: RootzWiki is not liable or responsible for any damages to your phones, this is solely the users decision to "root" their phone. Enjoy!

Personal tools
Navigation
Google AdSense