ok,we are gonna do it a lil differently,since the original temp root exploits do not work on gingerbread. were also going to use shadowmites permanent patched hboot instead of the original eng hboot.
prolly the best way to transfer large PG05IMG files is via an sd cardreader.
1)
downlaod the exploits:
mini-adb_TB_exploits.zip
md5:mini-adb_TB_exploits.zip
f99b7ec00d7bc49cc299baf050ae16fb
-
download downgrade firmware:
PG05IMG_downgrade
md5
G05IMG_downgrade.zip
aae974054fc3aed275ba3596480ccd5b
you can empty the contents into your tools or platform tools,if you wish,or just extract it and use it instead,its got everything we need.. extract,place on root of C drive on your PC
2)install revolutionary drivers:
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
3)install this wifi over adb app on your phone:
WiFi ADB im sure others will work,but i used this one and it worked great.
4)
prepair your phone
-charge battery to 100%
-go to settings/display and set your time out to NEVER sleep. *this is important.
-launch the app
-touch the "turn on" button
.
5)
connect and downgrade
-open a cmd window(on windows 7,click start bubble,type "cmd" or "command" in search box. other versions of windows may be same or similar)
-change to your mini-adb_TB_exploits directory by typing this command in your command window:
cd c:\mini-adb_TB_exploits this should change your command prompt to: "
c:\mini-adb_TB_exploits>"
-enter the command on the screen of your phone to connect to adb over wireless. in my case it was :
adb connect 192.168.1.68:5555 i have no idea if it will be different in other cases
from this point forward,all adb commands will be
bold,copy and paste them into the cmd window. additional comments will be
red or
blue and shouldnt be copy/pasted
adb devices should return your serial number
adb push busybox /data/local/
adb push misc.img /data/local/
adb shell chmod 777 /data/local/busybox
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF fre3vo will start,and do a bunch of stuff.at the end youll see "exploiting device..." then your promt will reapprear
adb shell if fre3vo worked,youll see a #
/data/local/busybox md5sum /data/local/misc.img should output c88dd947eb3b36eec90503a3525ae0de if its not,dont panic,its just the misc image. but youll need to re-download the exploits file,swap out the "misc" images and try again.
if the md5 matches,then:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
exit
at this point,you can flash the downgrade firmware. rename it PG05IMG and place it on the root of your sd card. power off,then on into hboot. it should find the file,check it,and ask to update. tell it yes its a long process,and a long first boot,so be patient.
after the old firmware is booted,youll have to deal with the hassle of signing into google and redownloading the adb wireless app. repeat step 4 and get reconected to adb. remove PG05IMG from your sd card
adb devices
adb push psneuter /data/local/
adb push busybox /data/local/
adb push wpthis /data/local/
adb shell chmod 777 /data/local/psneuter
adb shell chmod 777 /data/local/busybox
adb shell chmod 777 /data/local/wpthis
adb shell
/data/local/psneuter gain temp root. will throw you out of your root shell
adb shell
/data/local/wpthis disables emmc write protect
exit
ok,heres the scary part where you want to make sure the md5s match
adb push hboot_sm_perm_1.04.0000_110223.nb0 /data/local/
adb shell
/data/local/busybox md5sum /data/local/hboot_sm_perm_1.04.0000_110223.nb0
output must be 95ecb03e355003af6fc0be393ab2fba7 if so,then procede. it doesnt match,stop. youll need to redownload the exploits file,swap out the hboot files, and try again.
if the md5 matched,write the new hboot:
dd if=/data/local/hboot_sm_perm_1.04.0000_110223.nb0 of=/dev/block/mmcblk0p18
confirm proper write:
/data/local/busybox md5sum /dev/block/mmcblk0p18
again,output must be 95ecb03e355003af6fc0be393ab2fba7 if it is,then REBOOT. if not, DO NOT REBOOT
you can reboot the phone manually,or with the following:
exit to get out of your root shell and back to normal prompt
adb reboot
once the phone reboots,you should be running stock,old firmware with shadowmites permanent patched hboot you can power off,power on into hboot and verify that you are s-off
if so,its just a matter of running an ruu of your choice to get back to current,up to date firmware,then install a recovery of your choice as a PG05IMG file in hboot,then flash superuser files or the rom of your choice in recovery.
you can use
PG05IMG_no_hboot_2.11.605.19 from the root/unroot thread to upgrade,as its the most current radio,etc. note that shadowmites hboot will not allow itself to be overwritten,so if you run an ruu,or recieve an OTA,you will remain s-off.
choose a recovery from here:
http://androidforums.com/thunderbol...0-radios-recoveries-hboot-updated-9-24-a.html
if you wish to root the stock firmware,flash this in recovery:
superuser 3.0.7
or consider just flashing jrockers rooted stock rom:
http://androidforums.com/thunderbol...ted-5-21-12-rooted-ota-2-11-605-19-files.html
last and not least,ill get the downgrade ruu link up as soon as it uploads,and if you want to wait till later this afternoon,ill run through it on my phone and makde sure theres nothign i forgot
if youre confident and comfortable in the cmd window,youre welcome to go ahead and try it
ill be doing fathersday stuff until prolly 3 or 4,tho,and unavailble for advice if somethin happens