Any help will be greatly appreciated, If someone can walk me thru it, I will give you my IM information or maybe even remote desktop if possible.
i dont know if i would be available to walk you thru in IM,but some advice: watch the videos,getting ADB set up and seeing your phone is honestly the hardest part. its easy once you get that far,its just a matter if cutting and pasting and following the guide
watch the steps 2-9 video so that you have an idea wht it looks like,but dont try and use it as the guide- get your cutting and pasting and guide steps from the xda thread:
[ROOT] MR1/OTA PermRoot + Unlock Bootloader - Safer/Easier 5/12/2011 - xda-developers
here is a copy of my session,maybe it will help. the red are commands i cut and pasted,the blue is just some additional directions. yours will look alittle different,since youll prolly put your extracted exploits files into the tools directory,assuming youve pasted all of platform tools into tools as i have. so your first line will look like this:
cd c:\android-sdk-windows\tools and your prompt will say
tools where mine says
flashables.
Code:
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"]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]
[COLOR="Blue"]skip past intro and setup,delete upgrade RUU,move ROM of choice and radio(renamed PG05IMG) to root of 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 recovery[/COLOR]
[COLOR="blue"]manually wipe data/dalvik/cache and flash rom in recovery. when the rom is done flashing,do not select "reboot system" go back to comand window and:[/COLOR]
c:\android-sdk-windows\flashables>[COLOR="red"]adb reboot bootloader[/COLOR]
[COLOR="blue"]select bootloader and let hboot flash radio. reboot. set up and enjoy. remove radio PG05IMG from sd card.[/COLOR]
c:\android-sdk-windows\flashables>
i was doing cm7,but you will sub that for the 1.70.605.0 rooted rom. this is how i did it,immediately flashing cm7 during the same session as rooting. this is optional,you could do this part several different ways,but this way is quick and easy since you have adb running and your phone connected. just make sure if you choose to do it differently,that you dont accept any requests to OTA upgrade
last and not least,a couple of common issues:
- not putting the exploit files into the same file as sdk(usually tools) to push them from
- adb stops seeing your phone. try unplugging usb cable,wait a minute,pluf into a different port. make sure usb debugging stays on.(if its off adb will not seey our phone,so make it one of the first things you check)
- prollems with PG05IMG files. makse suree your sd card is formatted FAT32 and the file is named EXACTLY PG05IMG.zip(remember windows automatically adds and hides the extention,so if you try and type it the file may be in reality named PG05IMG.zip.zip
)
ill post up if i can think of any more.
- xda-developers
)