First I searched for a help thread and this is my last resort.
this morning i tried to root my evo using this guide http://forum.xda-developers.com/showthread.php?t=838448
log >
It failed
------------ AutoRoot.bat Begin - v2.2 - Sun 02/06/2011 17:09:19.48
------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Phone SN is HT0CWHL07773
Checking for ADB...
PLEN='1' PSTATE='device' RETURNTO='start' STEP='start'
PING ADB State Changed '1' out of '1'. ADB State is 'device' expected 'device'
Found the phone connected as 'device'.
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
'check.bat mtd' returned 'new'
MTD data being saved for phone 'HT0CWHL07773'
'dev: size erasesize name mtd0: 00c00000 00040000 "wimax" mtd1:
00100000 00040000 "misc" mtd2: 00480000 00040000 "recovery" mtd3:
00340000 00040000 "boot" mtd4: 15e00000 00040000 "system" mtd5:
0a000000 00040000 "cache" mtd6: 1aa00000 00040000 "userdata" '
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 100 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1364 KB/s (767044 bytes in 0.549s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN
cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'shell'
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
1375 KB/s (76044 bytes in 0.054s)
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
2490 KB/s (655360 bytes in 0.257s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
2929 KB/s (225014 bytes in 0.075s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
2447 KB/s (225551 bytes in 0.090s)
Pushing res\PC36IMG_UD.zip to /sdcard/PC36IMG.zip...
1577 KB/s (179274182 bytes in 110.963s)
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version '1.17.651.1'
Version Major '1'
Version Minor '17'
hbpreupdate set at '11'
Security is 'on'
Waiting on operator to flash the PC36IMG.zip and reboot into the recovery.
Checking for ADB...
PLEN='1250' PSTATE='recovery' RETURNTO='b2recovery' STEP='recoveryboot'
PING ADB State Changed '1' out of '1250'. ADB State is 'fastboot'
expected 'recovery'
PING ADB State Changed '357' out of '1250'. ADB State is
'disconnected' expected 'recovery'
PING ADB State Changed '362' out of '1250'. ADB State is 'recovery'
expected 'recovery'
Found the phone connected as 'recovery'.
Found the Recovery, proceeding to makenandroid...
Pushing amon_ra_1.8-mod to /...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Recovery type is 'stock'
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
phone showes s-on
hboot-2.10.0001
radio-2.15.00.11.19
try to boot get the evo red ! screen
I know now that I need to run the ruu to restore it. so I fond this http://forum.xda-developers.com/showthread.php?t=874251
what do I do with these files how do I "run the ruu"
bricked phone here please help, my searches are sending me in circles. if someone could point me in the right diretion that would be much appreciated
run the ruu.exe on your computer and should work from there
i dont have a ruu.exe does this "ruu.exe" have to be version specific?
further more where can i find a ruu.exe, and what mode should the phone be in to use the ruu.exe?
Hetrochromia said:
i dont have a ruu.exe does this "ruu.exe" have to be version specific?
further more where can i find a ruu.exe, and what mode should the phone be in to use the ruu.exe?
Click to expand...
Click to collapse
You can find the ruu in the same post that you downloaded that from. It should have given you instructions on exactly what to do when it failed as well. You just download it and run it.
ok thanks
fond the ruu here "cant post forum rules"
RUU to restore 3.70.651.1
turned phone on with power vol down
selected hboot USB
phone connects to pc
device manager shows "android bootloader interface"
run ruu.exe
error 170 can not find phone
tried this next
turned phone on with power vol down
selected recovery
phone shows red !
phone connects to pc
device manager shows "MY HTC"
run ruu.exe
error 170 can not find phone
any input?
dont select recovery just run it like that
When in the bootloader select fastboot, it should then change from hboot in blue to fastboot usb in red. Once you see that it should recognize your phone.
It looks like something was interfering with it talking to your phone, pdanet and apps like that can cause it but usually it's easier to just try with a different computer.
Sent from my PC36100 using XDA App
thanks that did it
now im going to do a fresh install of windows 7 on a laptop and retry the root
Related
while using haus's auto rooting program the cmd prompt timed out and one post from haus said to restart comp and it will pick up where it left off after running the autoroot prog again. no such luck here is my log
Code:
------------ AutoRoot.bat Begin - v2.3 - Tue 03/01/2011 14:35:03.63 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Matt\Desktop\ROOT\'
Phone SN is HT0CEHL02888
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='start' STEP='assess'
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
'check.bat mtd' returned 'new'
MTD data being saved for phone 'HT0CEHL02888'
'dev: size erasesize name mtd0: 00c00000 00040000 "wimax" mtd1: 00100000 00040000 "misc" mtd2: 00480000 00040000 "recovery" mtd3: 00340000 00040000 "boot" mtd4: 15e00000 00040000 "system" mtd5: 0a000000 00040000 "cache" mtd6: 1aa00000 00040000 "userdata" '
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 84 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1635 KB/s (767044 bytes in 0.458s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'shell'
Checking for root...
UID is 'shell'
Restart ADB Server...
Checking for root...
UID is 'shell'
Still no root shell, giving up.
Checking for ADB...
PLEN='0' PSTATE='recovery' RETURNTO='rootlend' STEP='rageit'
------------ AutoRoot.bat Begin - v2.3 - Tue 03/01/2011 14:42:30.70 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Matt\Desktop\ROOT\'
Phone SN is HT0CEHL02888
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='start' STEP='assess'
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
'check.bat mtd' returned 'new'
MTD matches info from INI file.
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 89 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1471 KB/s (767044 bytes in 0.509s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'Got Root!'
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='rageit'
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
1485 KB/s (76044 bytes in 0.050s)
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='movefiles'
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
1792 KB/s (655360 bytes in 0.357s)
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='movefiles'
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
1927 KB/s (225014 bytes in 0.114s)
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='movefiles'
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
1394 KB/s (225551 bytes in 0.158s)
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='movefiles'
rm failed for -f, Read-only file system
Pushing res\PC36IMG_UD.zip to /sdcard/PC36IMG.zip...
1678 KB/s (179274182 bytes in 104.308s)
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version '1.17.651.1'
Version Major '1'
Version Minor '17'
hbpreupdate set at '11'
Security is 'on'
Waiting on operator to flash the PC36IMG.zip and reboot into the recovery.
Checking for ADB...
PLEN='1250' PSTATE='recovery' RETURNTO='b2recovery' STEP='recoveryboot'
PING ADB State Changed '1' out of '1250'. ADB State is 'fastboot' expected 'recovery'
PING ADB State Changed '101' out of '1250'. ADB State is 'disconnected' expected 'recovery'
PING ADB State Changed '103' out of '1250'. ADB State is 'offline' expected 'recovery'
PING ADB State Changed '105' out of '1250'. ADB State is 'daemon' expected 'recovery'
------------ AutoRoot.bat Begin - v2.3 - Tue 03/01/2011 15:26:03.44 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Matt\Desktop\ROOT\'
Phone SN is unknown
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='start' STEP='assess'
PING ADB State Changed '1' out of '0'. ADB State is 'offline' expected 'device'
Couldn't find the phone, Aborting..
Checking for ADB...
PLEN='0' PSTATE='recovery' RETURNTO='start' STEP='assess'
PING ADB State Changed '1' out of '0'. ADB State is 'daemon' expected 'recovery'
Killing ADB server...
------------ AutoRoot.bat End ------------
thanks to anyone that can help
The pc36img needs to be flashed from the hboot before it is able to connect to the recovery. If you hold volume down while turning on the phone it should bring up a white screen asking to update, say yes. Once it finishes tell it not to reboot and then continue on to the recovery. Once that is done it should be able to find the recovery.
Sent from my PC36100 using XDA App
tried that and it brings me to a screen with a red triangle
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that and place on the root of your sdcard. I loaded amon_ra in there for recovery. Boot into the bootloader, and select update and then reboot, and then reboot back into the bootloader, decline the update and don't reboot, then select recovery.
just tried that and same deal, but i did notice that the s-on is still there in bootloader if that makes ant differance at all
I attempted this once and the bootloader failed. I since used RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe to restore my phone and try again. This is the log from the 2nd time around. It produced the same problem as before.... was wondering what I can do to change the BOOTLOADER status to Ok instead of Fail-IC.
Thanks for any help you can provide
Code:
------------ AutoRoot.bat Begin - v2.3 - Tue 03/01/2011 23:27:06.41 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Ben\Desktop\AutoRoot_v2.3\'
Phone SN is HT0BBHL05755
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='start' STEP='assess'
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
'check.bat mtd' returned 'new'
MTD matches info from INI file.
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 100 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1646 KB/s (767044 bytes in 0.455s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'ps'
Checking for root...
UID is 'Got Root!'
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='rageit'
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
1280 KB/s (76044 bytes in 0.058s)
Checking for ADB...
PLEN='0' PSTATE='device' RETURNTO='s4' STEP='movefiles'
rm failed for -f, Read-only file system
Pushing res\PC36IMG_UD.zip to /sdcard/PC36IMG.zip...
1601 KB/s (179274182 bytes in 109.351s)
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version '1.17.651.1'
Version Major '1'
Version Minor '17'
hbpreupdate set at '11'
Security is 'on'
Waiting on operator to flash the PC36IMG.zip and reboot into the recovery.
Checking for ADB...
PLEN='1250' PSTATE='recovery' RETURNTO='b2recovery' STEP='recoveryboot'
PING ADB State Changed '1' out of '1250'. ADB State is 'fastboot' expected 'recovery'
I am trying to root my Evo using the instructions found here:
http://forum.xda-developers.com/showthread.php?t=838448
I am running into a problem on step 5 and it says my hboot can't be determined or is not yet supported.
I would appreciate any help that can be offered.
Also, if this important, I tried rooting before and failed but it still says S-OFF on my bootloader screen. Even after restoring from a RUU that won't change.
Here is the full report
------------ AutoRoot.bat Begin - v2.4 - Wed 03/16/2011 14:27:14.56 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Ronald\Desktop\Rooting Stuff\'
Phone SN is HT05WHL07019
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
'check.bat mtd' returned 'old'
MTD matches info from INI file.
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 61 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
623 KB/s (767044 bytes in 1.201s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'shell'
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
805 KB/s (655360 bytes in 0.794s)
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version 'na'
Version Major 'na'
Version Minor ''
Did not recognize hBoot version! Aborting.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Passed to ERRHANDLER
PING ADB State Changed '1' out of '0'. ADB State is 'disconnected' expected 'recovery'
Killing ADB server...
------------ AutoRoot.bat End ------------
Alright so I attempted to root a buddies Evo 4g with AutoRoot last night and It failed while flashing and gave a dumplog stating to send it to the developer of Autoroot and he'd get back to me. I sent it to him but I figured he'd be pretty busy. I thought I'd post the log here for anyone with skills to see if they see anything obvious. One footnote would be that I was having issue with my firewall blocking the processes at first. Finally just turned off the firewall and that when the script actually started to work. Before that it would error that it couldn't reach the port. Any help would be appreciated.
------------ AutoRoot.bat Begin - v2.5 - Mon 05/02/2011 5:48:43.14 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Documents and Settings\Josh\My Documents\Cell Phone Rooting\Evo 4G\AutoRoot_v2.5\'. Admin='true'
Clearing Temp Files...
The system cannot find the file specified.
Could Not Find C:\DOCUME~1\Josh\LOCALS~1\Temp\autoroot.tmp
---------
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
---------
---------
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
---------
------------ AutoRoot.bat Begin - v2.5 - Mon 05/02/2011 5:56:31.23 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Documents and Settings\Josh\My Documents\Cell Phone Rooting\Evo 4G\AutoRoot_v2.5\'. Admin='true'
Clearing Temp Files...
The directory name is invalid.
---------
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
'tasklist' is not recognized as an internal or external command,
operable program or batch file.
---------
Phone SN is HT05WHL08252
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
'check.bat mtd' returned 'old'
MTD data being saved for phone 'HT05WHL08252'
'dev: size erasesize name mtd0: 00c00000 00020000 "wimax" mtd1: 000a0000 00020000 "misc" mtd2: 00480000 00020000 "recovery" mtd3: 00300000 00020000 "boot" mtd4: 15e00000 00020000 "system" mtd5: 0a000000 00020000 "cache" mtd6: 1aba0000 00020000 "userdata" '
EVO Branding 'sprint'
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 100 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
940 KB/s (767044 bytes in 0.796s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'shell'
Checking for root...
UID is 'shell'
Restart ADB Server...
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
264 KB/s (76044 bytes in 0.281s)
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
952 KB/s (655360 bytes in 0.671s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
937 KB/s (225014 bytes in 0.234s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
881 KB/s (225551 bytes in 0.250s)
Pushing res\dump_image to /data/local/dump_image...
431 KB/s (76028 bytes in 0.171s)
Dumping WiMAX partition...
rm failed for -s, Read-only file system
1030 KB/s (12582912 bytes in 11.921s)
WiMAX partition saved as 'HT05WHL08252_wimax.img'
Backing up Apps...
pull: building file list...
0 files pulled. 0 files skipped.
The system cannot find the path specified.
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version '1.17.651.1'
Version Major '1'
Version Minor '17'
hbpreupdate set at '11'
Security is 'on'
Setting RUU mode...
... OKAY
Sending flash PC36IMG_UD.zip command...
PING ADB State Changed '1' out of '0'. ADB State is 'offline' expected 'fastboot'
ERROR Phone is not in fastboot mode! Aborting!
Passed to ERRHANDLER
Killing ADB server...
------------ AutoRoot.bat End ------------
It looks like it may be your drivers because adb is trying to connect instead of letting fastboot take care of it. If you restart the script it should continue on from there
Thanks for the response. I will try it again and update with the results.
Worked great guys. Thanks for the quick response.
So I just got a brand new HTC Evo replacement because my old one had power button issues.
I tried using Universal AutoRoot 2.5. CMD closed and I got this output:
"------------ AutoRoot.bat Begin - v2.5 - Tue 06/07/2011 23:33:14.63 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Mark\Desktop\AutoRoot_v2.5\'. Admin='true'
Clearing Temp Files...
The directory name is invalid.
---------
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
---------
Phone SN is HT15AHL06321
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
'check.bat mtd' returned 'old'
MTD data being saved for phone 'HT15AHL06321'
'dev: size erasesize name mtd0: 00c00000 00020000 "wimax" mtd1: 000a0000 00020000 "misc" mtd2: 00480000 00020000 "recovery" mtd3: 00300000 00020000 "boot" mtd4: 15e00000 00020000 "system" mtd5: 0a000000 00020000 "cache" mtd6: 1aba0000 00020000 "userdata" '
EVO Branding 'sprint'
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 70 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1593 KB/s (767044 bytes in 0.470s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
1570 KB/s (655360 bytes in 0.407s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
1255 KB/s (225014 bytes in 0.175s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
1159 KB/s (225551 bytes in 0.190s)
Dumping WiMAX partition...
rm failed for -s, Read-only file system
1522 KB/s (12582912 bytes in 8.070s)
WiMAX partition saved as 'HT15AHL06321_wimax.img'
Backing up Apps...
pull: building file list...
0 files pulled. 0 files skipped.
The system cannot find the path specified.
Flashing misc partition...
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version 'ECHO'
Version Major 'ECHO'
Version Minor '' "
----------------------------------------
Now everytime i try to use my phone while it's on:
It doesnt charge while its on
I cant see SD card within the stock ROM
Phone constantly resets after about a minute
However in bootloader i can see the SD card, and the phone charges while its off. I ran the 3.70 RUU which went smoothly, however it did not fix anything =/
Any other ideas? is there a reason why my AutoRoot failed? I've rooted many HTC evo's and never had this problem/problems.
bigblueshock said:
So I just got a brand new HTC Evo replacement because my old one had power button issues.
I tried using Universal AutoRoot 2.5. CMD closed and I got this output:
"------------ AutoRoot.bat Begin - v2.5 - Tue 06/07/2011 23:33:14.63 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Mark\Desktop\AutoRoot_v2.5\'. Admin='true'
Clearing Temp Files...
The directory name is invalid.
---------
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
---------
Phone SN is HT15AHL06321
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
'check.bat mtd' returned 'old'
MTD data being saved for phone 'HT15AHL06321'
'dev: size erasesize name mtd0: 00c00000 00020000 "wimax" mtd1: 000a0000 00020000 "misc" mtd2: 00480000 00020000 "recovery" mtd3: 00300000 00020000 "boot" mtd4: 15e00000 00020000 "system" mtd5: 0a000000 00020000 "cache" mtd6: 1aba0000 00020000 "userdata" '
EVO Branding 'sprint'
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 70 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1593 KB/s (767044 bytes in 0.470s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
1570 KB/s (655360 bytes in 0.407s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
1255 KB/s (225014 bytes in 0.175s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
1159 KB/s (225551 bytes in 0.190s)
Dumping WiMAX partition...
rm failed for -s, Read-only file system
1522 KB/s (12582912 bytes in 8.070s)
WiMAX partition saved as 'HT15AHL06321_wimax.img'
Backing up Apps...
pull: building file list...
0 files pulled. 0 files skipped.
The system cannot find the path specified.
Flashing misc partition...
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version 'ECHO'
Version Major 'ECHO'
Version Minor '' "
----------------------------------------
Now everytime i try to use my phone while it's on:
It doesnt charge while its on
I cant see SD card within the stock ROM
Phone constantly resets after about a minute
However in bootloader i can see the SD card, and the phone charges while its off. I ran the 3.70 RUU which went smoothly, however it did not fix anything =/
Any other ideas? is there a reason why my AutoRoot failed? I've rooted many HTC evo's and never had this problem/problems.
Click to expand...
Click to collapse
Well, I unfortunately don't have any experience with the Auto Root method. Hopefully xHausx will chime in here. Out of curiosity, your replacement phone did indeed have 2.2 on it, right? Because if it was updated to the OTA 2.3.3 that root method won't work. What is your software and hboot version?
Perhaps try running the RUU again?
I believe there is a thread around by Calkulin which addresses the issue of the phone not reading the sd card and not charging. I will see if I can dig that up for you. Good luck.
EDIT: Here is that thread by calkulin. I'm not sure if this will be able to help you out or not, but you can go through it anyways. When you boot to your bootloader, does it show S on or S off? What is the version number?
Flashing misc partition...
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
Click to expand...
Click to collapse
Your phone had some bad blocks there, that's strange for a new one. I can help you try to fix it but tbh your best bet is to run the 3.70 ruu and take it back for another. Otherwise odds are it'll start doing this again somewhere down the line.
xHausx said:
Your phone had some bad blocks there, that's strange for a new one. I can help you try to fix it but tbh your best bet is to run the 3.70 ruu and take it back for another. Otherwise odds are it'll start doing this again somewhere down the line.
Click to expand...
Click to collapse
Thanks Haus. Yea very odd... It's a brand new sealed 0004 model. I hope it's just luck of the straw. I'm going to head back to sprint later and get it replaced again. I just hope not all the new 0004's are like this. They dont have any refurbs in stock so they had to send me a brand new one.
bigblueshock said:
Thanks Haus. Yea very odd... It's a brand new sealed 0004 model. I hope it's just luck of the straw. I'm going to head back to sprint later and get it replaced again. I just hope not all the new 0004's are like this. They dont have any refurbs in stock so they had to send me a brand new one.
Click to expand...
Click to collapse
You should be good with another one, I've only had maybe 4 or 5 people have this happen before and up until now they were all refurbs. Just luck of the draw I guess.
edit: btw that speedtest result is sick, I would love to have a ping like that
The phone had stock 3.70 2.2 froyo. Phone is s-on with 2.10 bootloader, never got that far to get it s off
And yeah, too bad i just graduated from school, no more 100mbit pipe for me, was nice while it lasted
bigblueshock said:
The phone had stock 3.70 2.2 froyo. Phone is s-on with 2.10 bootloader, never got that far to get it s off
And yeah, too bad i just graduated from school, no more 100mbit pipe for me, was nice while it lasted
Click to expand...
Click to collapse
2.10 bootloader should work, it is the 2.19 one i believe that is locked.
So sprint swapped out the phone at the store. I'm pretty excited, he gave me a brand new White evo =)
I got home and autoroot worked flawlessly! Thanks again Haus for all your support and easy rooting techniques.
I'm not sure if this is the possible reason for my old phone bricking like that, but I'd like to share some knowledge.
My original 0004 model that sprint sent me was brand new, as well as the white evo 0004 sprint gave me was also brand new. While attempting to root the first replacement, 'check.bat mtd' returned 'old'. The second replacement white evo returned as "new". Not that i think it matters, but they both came with 2.10 bootloader and 3.70 base.
I have a strange feeling the first replacement had new block size, but for some reason a bug marked it as having the old block size. I just dont see how a brand new just made 0004 evo would have the old block size.
Could this have been the culprit?