• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root S-off evo user needs help

akazabam said:
Does it ever prompt you to flash a pc36img (ie does it even find it) or does it just load hboot normally?



I think you're thinking of recovery :). This is hboot.
Click to expand...

it has never prompted me to flash. never finds it. and recover always fails on authenticating.
 
Nomad397 said:
is there any way i can use an update.zip file to recover ? have you ever heard of a phone being this stubborn ? i called a guy from craigslist who charges for root service. went to see him and he could not get any image or update to take. one was able to take but was missing files and aborted anyway. he basically told me he did not have the right image file or update file. what do you think ?
Click to expand...

Those sorts of things are always scams, as far as I'm concerned.

Nomad397 said:
it has never prompted me to flash. never finds it. and recover always fails on authenticating.
Click to expand...

Ok, so let's see, you can actually get into recovery, right? What recovery is it (type and version)? Where are you getting an error about authentication? Oh, and do you have s-on or s-off? I never got that answer.

Hunterbeav said:
sorry...thought I was on to something lol
Click to expand...

lol, no worries.
 
ok in hboot
supersonic evt2-3 ship s-on
hboot-2.10.001
microp-041f
touch panel-atmelc03_16ac
radio-2.15.00.11.19
Oct 15 2010, 12:07:00

no image or wrong image!

recovery

android system recovery <2e>

at the middle bottom in yellow is says E:can't open /cache/recovery/command
-- Install from sdcard...
Finding Update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
 
akazabam said:
How are you getting the PC36IMG files to the root of your sdcard? hboot-usb or...?
Click to expand...

sdcard and adapter on my laptop. the phone automatically looks for the pc36img file when i power + vol dwn
and i can put it into hboot-usb to make it look for the file on the sd card

i tried useing the sprint ruu but i always got error 170 usb connection error and adb cant detect device
 
on a side not do you think a sprint corp service center would just give me a refurb phone replacement under insurance if i walked in tomorrow ? and charge me $100 ? im not sure ... the phone is not rooted and it is less than 1 yr old and still under warranty.
 
Well, you never did get s-off, and unless I misunderstood you, you don't even have a custom recovery, so it doesn't sound like they'd have a clue. Do you have insurance?

That being said, I'm sure we're just missing something simple. You said you did the autoroot method. What step did you get to?
 
i do have insurance tep esrp and erp. yea auto root screwed my junk lol. i got to step 7 and thats when things got ugly. i bought the phone second hand and the only physical issue with it is a cracked camera lens cover which does not effect the pictures. do you think they would charge me the $100 to replace it ?
 
If the phone has to be replaced, you have to pay $100. Really, though, if you can get to hboot, we should be able to fix it. Do you have the phone connected via usb while booting into hboot? Leave it unplugged, turn the phone off, then turn it back on. Is that what you've already tried (assuming you still have the pc36img.zip on your sdcard)?
 
akazabam said:
If the phone has to be replaced, you have to pay $100. Really, though, if you can get to hboot, we should be able to fix it. Do you have the phone connected via usb while booting into hboot? Leave it unplugged, turn the phone off, then turn it back on. Is that what you've already tried (assuming you still have the pc36img.zip on your sdcard)?
Click to expand...

yes tried it almost every way. no reboot for me because the only way to get the phone to respond when turning on is with vol dwn button. odd. its as if its bricked but i have recovery and hboot. yea usb is broken because the computer no longer can sync (or abd) i have to get some sleep and figure out what i'm going to do. thank you for all the help. ill be checking the forum first thing in the morning if you do come up with anything.
 
It's just the fact that it won't read the pc36img that doesn't make sense. You're absolutely positive that it's named PC36IMG.zip, exactly? It didn't get extracted or anything, right? I'll see if I can find anything else on this.
 
for sure the name is correct. and its only named PC36IMG on the sd card because when i go to details it says the full file name is PC36IMG.zip . ive tried it both ways
 
Nomad397 said:
for sure the name is correct. and its only named PC36IMG on the sd card because when i go to details it says the full file name is PC36IMG.zip . ive tried it both ways
Click to expand...

Is that what you see from windows or from the phone (I'm guessing windows. I don't know where else you'd see details).

I'm not sure what else I can do to help you. Typically, if you cat get into hboot, you can fix things, but not being able to flash a PC36IMG is odd. Have you tried starting from scratch? Redownload the file, make sure it doesn't unzip, rename it to PC36IMG.zip (if you don't see an extension on it after the download, just don't add one when you rename it), copy that over, and try again. Maybe the file got messed up in the process before.
 
ive been trying on a 2gb sd card i found but the stoc one did not come with the phone i bought. i also have a 16gb card that was in the phone when it crashed during rooting. this is the log file from when the autoroot was trying to root the phone


------------ AutoRoot.bat Begin - v2.0 - Fri 01/07/2011 16:55:11.83 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''


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...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
'check.bat mtd' returned 'new'
Firmware version '*'
Version Major '*'
Version Minor ''

------------ AutoRoot.bat Begin - v2.0 - Fri 01/07/2011 16:57:44.37 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''


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'
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 92 percent.

Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk

Success

1454 KB/s (767044 bytes in 0.515s)
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'
Restart ADB Server...

Checking for root...
UID is 'Got Root!'

Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
781 KB/s (76044 bytes in 0.095s)
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
1612 KB/s (655360 bytes in 0.397s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
1255 KB/s (225014 bytes in 0.175s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
635 KB/s (223773 bytes in 0.344s)
Pushing res\PC36IMG_UD.zip to /sdcard/PC36IMG.zip...
1635 KB/s (179274182 bytes in 107.046s)
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 'disconnected' expected 'recovery'
Cannot find the phone. State shows it as 'disconnected'
Killing ADBD...

------------ AutoRoot.bat End ------------


------------ AutoRoot.bat Begin - v2.0 - Fri 01/07/2011 17:24:57.30 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''


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'
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

1534 KB/s (767044 bytes in 0.488s)
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'
Restart ADB Server...

Checking for root...
UID is 'Got Root!'

Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
1142 KB/s (76044 bytes in 0.065s)
Pushing res\PC36IMG_UD.zip to /sdcard/PC36IMG.zip...
1462 KB/s (179274182 bytes in 119.731s)
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 '558' out of '1250'. ADB State is 'disconnected' expected 'recovery'
PING ADB State Changed '563' 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...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Recovery type is 'stock'
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

---------RECOVERY LOG DUMP BEGIN---------
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
----------RECOVERY LOG DUMP END----------

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...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
* daemon not running. starting it now on port 5037 *
* 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 COMMAND DUMP BEGIN-------
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
--------RECOVERY COMMAND DUMP END--------

adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:

Checking for ADB...
PLEN='20' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflash'
Phone rebooted into recovery mode. Waiting on it to reboot again...
PING ADB Counter - State Changed '2' out of '180'. ADB State is 'server' expected 'recovery'
Phone rebooted.

Checking for ADB...
PLEN='60' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflashreboot'
PING ADB State Changed '1' out of '60'. ADB State is 'recovery' expected 'any'
Recovery type is 'stock'
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:

Checking for ADB...
PLEN='60' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflashreboot'
PING ADB State Changed '1' out of '60'. ADB State is 'daemon' expected 'any'
PING ADB State Changed '3' out of '60'. ADB State is 'server' expected 'any'
PING ADB State Changed '4' out of '60'. ADB State is 'recovery' expected 'any'
WARNING Rebooted back to the recovery...
Recovery type is 'na'

---------RECOVERY LOG DUMP BEGIN---------
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
----------RECOVERY LOG DUMP END----------


Checking for ADB...
PLEN='60' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflashreboot'
Recovery type is 'custom'

---------RECOVERY LOG DUMP BEGIN---------
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
----------RECOVERY LOG DUMP END----------


Checking for ADB...
PLEN='60' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflashreboot'
WARNING Rebooted back to the recovery...
Recovery type is 'na'

---------RECOVERY LOG DUMP BEGIN---------
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
----------RECOVERY LOG DUMP END----------


Checking for ADB...
PLEN='60' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflashreboot'
PING ADB State Changed '1' out of '60'. ADB State is 'daemon' expected 'any'
PING ADB State Changed '11' out of '60'. ADB State is 'server' expected 'any'
PING ADB State Changed '12' out of '60'. ADB State is 'daemon' expected 'any'
PING ADB State Changed '14' out of '60'. ADB State is 'server' expected 'any'
PING ADB State Changed '15' out of '60'. ADB State is 'daemon' expected 'any'
PING ADB State Changed '17' out of '60'. ADB State is 'server' expected 'any'
PING ADB State Changed '18' out of '60'. ADB State is 'device' expected 'any'
Rebooting into the bootloader from 'device'...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

Checking for ADB...
PLEN='60' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflashreboot'
Rebooting into the bootloader from 'device'...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

Checking for ADB...
PLEN='60' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflashreboot'
PING ADB State Changed '1' out of '60'. ADB State is 'server' expected 'any'
PING ADB State Changed '3' out of '60'. ADB State is 'device' expected 'any'
Rebooting into the bootloader from 'device'...
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:

Checking for ADB...
PLEN='60' PSTATE='any' RETURNTO='b2bootloader' STEP='autoflashreboot'
PING ADB State Changed '1' out of '60'. ADB State is 'server' expected 'any'
PING ADB State Changed '2' out of '60'. ADB State is 'daemon' expected 'any'

------------ AutoRoot.bat Begin - v2.0 - Fri 01/07/2011 18:01:26.10 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''


Checking for ADB...
PLEN='1' PSTATE='device' RETURNTO='start' STEP='start'
PING ADB State Changed '1' out of '1'. ADB State is 'disconnected' expected 'device'
Cannot find the phone. State shows it as 'disconnected'
Killing ADBD...

------------ AutoRoot.bat End ------------


------------ AutoRoot.bat Begin - v2.0 - Fri 01/07/2011 18:01:46.72 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''


Checking for ADB...
PLEN='1' PSTATE='device' RETURNTO='start' STEP='start'
PING ADB State Changed '1' out of '1'. ADB State is 'disconnected' expected 'device'
Cannot find the phone. State shows it as 'disconnected'
Killing ADBD...

------------ AutoRoot.bat End ------------


------------ AutoRoot.bat Begin - v2.0 - Fri 01/07/2011 18:02:28.85 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''


Checking for ADB...
PLEN='1' PSTATE='device' RETURNTO='start' STEP='start'
PING ADB State Changed '1' out of '1'. ADB State is 'recovery' expected 'device'
Cannot find the phone. State shows it as 'recovery'
Attempting to dump the recovery log.

---------RECOVERY LOG DUMP BEGIN---------
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -

----------RECOVERY LOG DUMP END----------

Killing ADBD...

------------ AutoRoot.bat End ------------
 
you were right. i was finally able to get it going with my 16gb card. odd huh ? than you soo much for your help ! what do you think is the safest way to root this phone now ?
 
im gonna save the root for some time next week since i want to swap out this phone anyway because the camera lens is cracked and my 4g does not work. my gf (who i live with) has a steady 2 bars of 4g service and my phone is always scanning/obtaining ip/disconnecting every day. THANK YOU !
 
You must log in or register to reply here.
Back
Top Bottom