Root UPdated and now Bootloader is locked HELP

[chavo60]

I accidently updated my device... now my bootloader is locked (S-ON)

I am trying to do a manual root and have ADB installed on my computer.. im using these instructions:
How to: Root the HTC Thunderbolt and Unlock the Bootloader - Droid Life: A Droid Community Blog

Im currently on Step 4 "adb reboot bootloader" and trying to flash the ROM and here is where im stuck.

get the message "checking PG05IMG.zip" ... the status bar on the right side of the screen gets all the way to the top and then it goes away... nothing happens after. This is where they device should ask me to update and it doesnt... help!!!

Anyone know what i should be doing?

 

[WormDoes]

Did you check the md5 sum of the radio before putting it on your SD? It's on the root (not in any folders), correct? Are you sure it's named correctly? I've seen some people mistake the "0" for a "O"

 

[scotty85]

grrr i was typing and somethin happend and its all gone

anyway...

verify the md5 of the file you renamed first thing,so we can make sure its not corrupt,or the wrong file. the phone will check anything you name PG05IMG,but it wont try to flash it if it doesnt recognize the contents. the md5 for the downgrade RUU should be: aae974054fc3aed275ba3596480ccd5b

after that,as worm said there are only 2 reasons a PG05IMG are not found:
1)not named correctly. must be neamed exactly "PG05IMG.zip". if your useing windows,it will add and hide the file extension,so typing in the ".zip" will name the file "PG05IMG.zip.zip"
2)your sd card is not formatted FAT32. right click on the drive that is your sd card with the phone plugged in and disk drive mode chosen. click properties. if your card is formatted FAT or anything else,youll have to back it up and reformat it.

 

[scotty85]

hows it coming along?

i just noticed that your using a guide at droid life. if you havent allready completed the root process id highly reccomend switching to the guide on XDA: [ROOT] MR1/OTA PermRoot + Unlock Bootloader - Safer/Easier 5/12/2011 - xda-developers

the droid life guide has a comment in step 5 that is simply a description,but looks like part of the code(To unlock eMMC: )

also,the droid life guide is old. the xda guide contains an upgrade RUU that allready contains clockwork recovery,and allready has superuser set up and working,so you will not have to do steps 7,8,9.

you can even further simplify the process by not using the upgrade RUU from the xda guide. use this one instead: http://androidforums.com/thunderbolt-all-things-root/389462-custom-mr2-upgrade-ruu-new-rooters.html it will leave you on rooted mr2 and yuo wont have to do anything else afterward.

so, to recap:
-switch to xda guide for directions and code
-download the downgrade RUU and exploits files from xda guide
-download upgrade RUU to use in step 7 from http://androidforums.com/thunderbolt-all-things-root/389462-custom-mr2-upgrade-ruu-new-rooters.html

 

[chavo60]

I actually ran out of time since i was trying to root at work during lunch ... ;-)

So now im home and im trying to do the manual root on my MAC ... complicates things just as much.

For some reason adb doest see my thunderbolt when entering the command ./adb devices. I get a return message "No such file or directory"

Note: The directions im reading states that i should be installing "Android SDK Platform-tools, revision 3" in the Android SDK AVD Manager... but when i check to see what packages are available i dont see that file. Could this be the problem?

 

[chavo60]

okay... it sees my device now but cant seem to push the psneuter file

PS: this is the walkthrough im using:[HOWTO] Getting root on your Thunderbolt from start to finish - Mac OS X - xda-developers

I may have to wait until i get back to the office on Monday

I WANT MY ROOT BACK! LMAO FML

 

[scotty85]

what trouble are you haveing? an error message? you should have extracted the exploits file,and put the contents into either "tools" or "platform tools" depending on how you have it set up. if youre getting an error, you may need to change to the directory where you put them,or just move them to the same folder as your android-sdk.

if youre not getting any response,that actually may be what youre sposed to see,depending on the step. heres a copy of my root session,its on windows 7,but still it may help you some as the outputs and such should be basically the same:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HT126S005970    device


C:\Users\Scott>[COLOR="red"]cd c:\android-sdk-windows\flashables[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb push psneuter /data/local/[/COLOR]
1214 KB/s (585731 bytes in 0.471s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb push busybox /data/local/[/COLOR]
1146 KB/s (1062992 bytes in 0.905s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb push misc.img /data/local/[/COLOR]
1462 KB/s (262144 bytes in 0.175s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/psneuter[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/busybox[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]/data/local/psneuter[/COLOR]
/data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
#[COLOR="red"] /data/local/busybox md5sum /data/local/misc.img[/COLOR]
/data/local/busybox md5sum /data/local/misc.img
c88dd947eb3b36eec90503a3525ae0de  /data/local/misc.img
#[COLOR="red"] dd if=/data/local/misc.img of=/dev/block/mmcblk0p17[/COLOR]
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
512+0 records in
512+0 records out
262144 bytes transferred in 0.112 secs (2340571 bytes/sec)
# [COLOR="red"]exit[/COLOR]
exit

[COLOR="Blue"]manually move downgrade RUU to SD card[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb reboot bootloader[/COLOR]

[COLOR="blue"]select bootloader with power button,let hboot flash downgrade RUU,reboot[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT126S005970    device


c:\android-sdk-windows\flashables>[COLOR="red"]adb push psneuter /data/local/[/COLOR]
1440 KB/s (585731 bytes in 0.397s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb push busybox /data/local/[/COLOR]
1693 KB/s (1062992 bytes in 0.613s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb push wpthis /data/local/[/COLOR]
1134 KB/s (679475 bytes in 0.585s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/psneuter[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/busybox[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/wpthis[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]/data/local/psneuter[/COLOR]
/data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
#[COLOR="red"] /data/local/wpthis[/COLOR]
/data/local/wpthis
Build: 25
Section header entry size: 40
Number of section headers: 45
Total section header table size: 1800
Section header file offset: 0x00014e90 (85648)
Section index for section name string table: 42
String table offset: 0x00014cc7 (85191)
Searching for .modinfo section...
 - Section[16]: .modinfo
 -- offset: 0x00000f80 (3968)
 -- size: 0x000000c4 (196)
Kernel release: 2.6.32.21-g2447a8d
New .modinfo section size: 204
Loading module... OK.
Write protect disabled.
Searching for mmc_blk_issue_rq symbol...
 - Address: c02d3114, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02d3000
Kernel memory mapped to 0x40001000
Searching for brq filter...
 - Address: 0xc02d3114 + 0x34c
 - 0x2a000012 -> 0xea000012
Done.
# [COLOR="Red"]exit[/COLOR]
exit

c:\android-sdk-windows\flashables>[COLOR="red"]adb push hbooteng.nb0 /data/local/[/COLOR]
1656 KB/s (1048576 bytes in 0.618s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
#[COLOR="red"] /data/local/busybox md5sum /data/local/hbooteng.nb0[/COLOR]
/data/local/busybox md5sum /data/local/hbooteng.nb0
6991368ee2deaf182048a3ed9d3c0fcb  /data/local/hbooteng.nb0
#[COLOR="red"] dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18[/COLOR]
dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.477 secs (2198272 bytes/sec)
#[COLOR="red"] /data/local/busybox md5sum /dev/block/mmcblk0p18[/COLOR]
/data/local/busybox md5sum /dev/block/mmcblk0p18
6991368ee2deaf182048a3ed9d3c0fcb  /dev/block/mmcblk0p18
#

[COLOR="blue"]manually reboot phone.[/COLOR]

[COLOR="blue"]after phone reboots,manually move upgrade RUU to SD card.[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT126S005970    device

c:\android-sdk-windows\flashables>[COLOR="red"]adb reboot bootloader[/COLOR]

[COLOR="blue"]select bootloader with power button,let hboot flash upgrade RUU,reboot[/COLOR]


c:\android-sdk-windows\flashables>

red are my inputs,blue are just some notations to help show whats going on.

 

[chavo60]

YOU ARE THE MAN!!!! PSNEUTER PUSHED!... now on to the next step.

 

[chavo60]

successfully downgraded... now to root .... AMAZING!!!!

 

[scotty85]

awsome! your cigar and blazer are waiting

edit: when you get to step 7... either use the xda guides upgrade ruu from the sticky,original thread here or use my upgrade MR2.

you wont have to do any of the rest of the junk listed in your mac guide... the other upgrade RUUS all that is allready done,and clockwork recovery allready installed

 

[chavo60]

Already upgrading with MR1 ... step 6 of Hboot as i type (system)... too late?

 

[scotty85]

Already upgrading with MR1 ... step 6 of Hboot as i type (system)... too late?

wich mr1? from the original guide,or from your mack guide?

 

[chavo60]

installed superuser and got this message

"su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary."

say what?! lol

 

[scotty85]

its not really too late... once youre s-off you can flash whatever ruu you want to so all youll have to do is download one of the rooted versions and repeat that step. or you can just go ahead and finish it up since youre that far along. just remember that youll need to flash the rooted mr2 in recovery and the radios in hboot as soon as youre done,and have your recovery installed and working.

if you have trouble with the superuser from the market(things not reciving root permissions,maybe even force closing) then download this superuser and flash it in clockwork recovery. seems last guy we helped root with a mac had issues and had to do this.

its really your call wether you want to go thru the last steps and deal with all that and flashing the new rom/radios,or simply download the custom upgrade mr2 and redo letting the upgrade ruu flash.

 

[scotty85]

installed superuser and got this message

"su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary."

say what?! lol

lol,yup,you need to do this:

if you have trouble with the superuser from the market(things not reciving root permissions,maybe even force closing) then download this superuser and flash it in clockwork recovery. seems last guy we helped root with a mac had issues and had to do this.

 

[chavo60]

Couldn't have done it without ya Scotty! Gonna attempt to flash a rooted ruu...

 

[scotty85]

cool! once you flash the rom... remember you wont have signal with the mr1 radio. this is normal. just flash the mr2 radios in hboot after you flash the rom and all will be well. there are radio/rom flashing directions in the [how to] sticky if you need them

 

[chavo60]

Dont you sleep man? lol

Any recommendations on ruu/radio to use?

 

[scotty85]

The rooted/deodex mr2 we linked on the other thread. I'm actually not at my computer now,lol,so if you need help finding it I can link it later

 

[chavo60]

got it... i referred to the other thread.

In case anyone is following this thread, this is the link to the rooted Deodexed Scottey referenced:
[ROM] Official 1.70.605.0 MR2 OTA Deodexed Rooted Busybox Mirrors Added - xda-developers

 

[chavo60]

downloaded the rooted mr2 and renamed to PG05IMG.zip and placed it on my sdcard.... ran hboot, recognizes ruu but wont flash it.... did i miss a step?

 

[scotty85]

downloaded the rooted mr2 and renamed to PG05IMG.zip and placed it on my sdcard.... ran hboot, recognizes ruu but wont flash it.... did i miss a step?

i think this is what confused you before,when the OTA episode occured. hope that doesnt happen to ya again,lol but i guess if it did youre an expert rooter now

if you scroll down the first post of the thread you linked there are 2 download links...
download rom

download radio

youl need to download both.

the file that you download from the "download radio" link you will rename PG05IMG and flash in hboot. the radio file is considerably smaller than the rom(only 25ish mb) and it is extremely important that you verify its integrity by checking the md5 sum. it should be 7297850061f25630bf6c2885620dd12c

the file you get from the download rom link,youll just move to the root of your sd card-dont rename or extract. then boot into clockwork mod recovery,wipe data,wipe cache,wipe dalvik cache, and then flash the rom.

your phone is checking the file because it properly named PG05IMG,and then not flashing it becasue it is extremely confused by the contents inside. the folders and files inside a CWM flashable .zip are extremely different from the EXT 3 file images inside an hboot flashable ruu

 

[chavo60]

Mission. accomplished..... Mr2 rooted and proper radio

 

[scotty85]

Mission. accomplished..... Mr2 rooted and proper radio

awsome! almost forgot- pickup your cigar and blazer from the table

now youve done a great job rooting your phone manually,and from a mac to boot,wich there is not near as much info/support for,and youve successfully installed the most current rooted firmware and radios.

now theres one last thing id highly reccomend,as it will prevent you in the future from becoming unrooted if you accidentally flash the wrong RUU file,or your phone accepts another OTA.

heres a direct link:
Patched (hard)hboot 1.04 for s-off/eng/fastboot - xda-developers

download the thunderbolt_patched_hboot.zip and open it up. inside youll find a PG05IMG file,and a text doccument. read the "readme" doccument so youll have the md5 sum. move the PG05IMG to the root of your sd card(make sure you delete your radio PG file first) and then check it on your phone with scary aliens AFV or with astro file manager(i prefer scary aliens app) and then boot into hboot and let it flash. make 100% sure you double and triple check the md5 because this is a new bootloader,and if you eff up the bootloader,your phone is a brick

what this does is prevent you from becoming s-on. there is some more discussion of it here: http://androidforums.com/thunderbolt-all-things-root/387290-permanent-s-off-here.html

let me know if you have any questions. if you had had this before,you wouldnt have had to go thru all this to re-root,lol. IMO its a great piece of mind.

 

[chavo60]

What did you put in this cigar? (Cough cough) lol