yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] jarvijd:
Cannot boot phone after running autoroot

The autoroot script was running fine but after it got most of the way through it stopped and now I have a triangle with Red Exclamation point. I am able to boot into the bootloader using the power/vol down technique but am not able to go into recovery mode and there is not a pc36img.zip on the card so it will not boot from it. I also tried running RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed but it is not able to find the phone. I attached the autoroot.log file.

Any help/guidance is appreciated.
[EVO 4G Android Development] MedicWill:
same problem again... lets try again...
[EVO 4G Android Development] likeminas:
works like a charm.

the first time I got an error, that was easily corrected by making a factory reset.

now i'm root

thanks OP
[EVO 4G Android Development] MedicWill:
Ok, so you restored with RUU, rebooted the phone, then factory reset it, and then ran AutoRoot again?
[EVO 4G Android Development] Semantics:
Not sure whats going on here, had the million daemon cannot connect errors, had errors all over the place saying that the recovery couldnt be flashed because it is in use by something else, and then I'm getting messages saying I'm nand unlocked with a custom recovery. When I go to recovery I get a red triangle with an exclamation point in it. It seemed much easier to root the phone manually last time, I had to have my evo replaced unfortunately. not sure what to do from here, the phone wont boost past the White EVO 4G screen.
[EVO 4G Android Development] xHausx:
You may need to disable your antivirus and redownload the zip, sometimes they will pick up the exploit and in turn prevent it from working correctly.

An easy way to get past there is to unlock your nand manually and then let the script finish up afterward. With the red triangle showing on your phone run the StartRecovery script and it will bring up the recovery on your phone. Then use that to Flash the URFSOff zip file. Once that finishes you can use the flashzip script to flash the SprintLover-AmonRA zip.

Once that finishes you should be good to go.

It sounds like you may have gotten a bad copy of the zip, be sure to double check the MD5 sum to make sure they match up.
[EVO 4G Android Development] xHausx:
You'll need to flash an updated ROM in order to start the phone up, if your NAND is unlocked you can use FlashZip script to flash the SprintLovers ROM and you should be good as new. Otherwise you'll need to find what is interfering with it and close it down to continue.

Sometimes just rebooting your desktop and starting it again from the stock recovery (red triangle) is enough to let it continue though.
[EVO 4G Android Development] stonemad:
I ran the 3.7 RUU from your list, tried it again and got.the same results. Is it just a bad flash, or should I try re downloading the root to my oc.
[EVO 4G Android Development] Ryno_666:
auto root says cannot find my sdcard but im in charge only and debugging is on any idea?
[EVO 4G Android Development] ffkip911:
a little help

getting this error through comp:

rebooting into the recovery...

waiting for the phone...

**damon still not runningerror: cannot connect to daemon

found the phone connected as 'recovery'

setting up temporary recovery...

**daemon still not runningerror: cannot connect to daemon

ADB server didn't ACK

*failed to start daemon *

error:

hardware 0003

hboot 2.10.0001

With the same specs as the video tutorial on page 1

using v2.3
[EVO 4G Android Development] kphillips85:
Data issue's

Hello,

Is anyone having any data issues where it takes a while to connect or it will time out on it's own without the screen going to sleep?

Thank you!
[EVO 4G Android Development] xHausx:
Depends, it could be something interfering with it as well. The autorootlog.txt file will show what it is doing if you could attach it to a post for me.

Make sure you have plenty of room on it, some of the files are pretty big so you'll need at least a 1 GB free.
[EVO 4G Android Development] xHausx:
It's having trouble staying connected to your phone, there are instructions on the previous page on how to get around or fix that.

Update your profile and PRL from the settings menu and it should help with that.
[EVO 4G Android Development] Ryno_666:
My sdcard is clean any ideas I'm on old 2.1 this phone was never upgraded its clear of everything 1.36 baseband 1.17 build has 18g sdcard
[EVO 4G Android Development] xHausx:
Can you please attach the autorootlog.txt file to a post for me? You may need to mount it as a hard disk and run a scan disk on it first. Sometimes they'll get errors on them that make it do weird things.
[EVO 4G Android Development] kphillips85:
Yep,

done this already. Anything else that might cause this problem?

Thanks so much for the reply!
[EVO 4G Android Development] Ryno_666:
------------ AutoRoot.bat Begin - v2.3 - Mon 02/28/2011 3:17:26.15 ------------

Params=1'' 2'' 3'' 4'' 5'' 6''

Working Directory is 'C:\Users\user\Desktop\New\'

Phone SN is HT07XHL01085

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

Version Major '1'

Version Minor '17'

Battery is at 70 percent.

Checking for root...

UID is 'Got Root!'

Checking for ADB...

PLEN='0' PSTATE='device' RETURNTO='s4' STEP='start'

Checking for needed files...

ERROR No SD card is mounted!

Checking for ADB...

PLEN='0' PSTATE='recovery' RETURNTO='s4' STEP='start'

Attempting to dump the recovery log.

---------RECOVERY LOG DUMP BEGIN---------

/cache/recovery/log: No such file or directory

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

Killing ADB server...

------------ AutoRoot.bat End ------------
[EVO 4G Android Development] ffkip911:
Thanks OP the the huge amount of assistance to everyone who asks.

tried rooting last night and got an error (you suggested it timed out). uninstalled and re installed v2.3 (with all anti virus off) then got a can't find SD error and exited.

I can pull media through the sd via music...unmounted sd, and reset and verified that I can still pull media. debugged and charge only.

cleared storage and trying again----any other help? ohh and would like to flash Sprint lovers new rom...where would I put that to install after a root???? first page said that v2.3 will flash custom after root, but don't know where to put the rom (and do we unzip them) ***(I've been flashing WM for a few years, but Android is a bit different)**

Thanks OP

alright, went back to the first page and went back to bootloader and then recovery....back to the red triangle exclamation point........................but autoroot.bat is "working"

bla bla

phone is running unrevoked forever

....

.....

phone entering bootloader

waiting for the phone
[EVO 4G Android Development] Geauxt:
I rooted using your method, when i get on 4g it works fine. When I try to use the wireless teethering app it kicks me off 4g. Any ideas?

Victory for L---S---U
[EVO 4G Android Development] coiledwire:
Its a limitation with all (free) wireless tethering right now AFAIK. I believe you can still have 4G with USB tethering though.
[EVO 4G Android Development] xHausx:
Going by your firmware version you should already have an unlocked bootloader. Give the FlashZip script installed and it should give you an option to flash the Sprint Lovers ROM.

can you check to see if your phone shows s-on or s-off in the bootloader? If it is s-off you can just use FlashZip to flash Sprint Lovers and the updated recovery and radios are included in it.
[EVO 4G Android Development] ffkip911:
shows : supersonic evt2-3 ship S-OFF

assuming "PC36IMG" stays zipped, how do I get to flash (so different than WM---used to putting the .nbh on the root of SD then bootloader = flash)

alright, think I got it.....thanks OP for your quick help

yep, flashed through with custom----have NO idea what i did, but thanks for your help
[EVO 4G Android Development] stonemad:
the autoroot.txt

here is the autoroot.txt file. What is it I am looking for?
[EVO 4G Android Development] dirtyscout:
good work auto root everything no hassel! Revoked would do a thing for this phone keep it up! :D
[EVO 4G Android Development] tnizzel33:
i need to know what you did because i am stuck in the same place. How do I get to flash zip?
[EVO 4G Android Development] tnizzel33:
now it said congratulations but still in bootloader screen. Help
[EVO 4G Android Development] a63548:
Just received a 0003 replacement from Sprint with 2.10 hboot. Used AutoRoot v2.3 and everything worked perfectly. Thank you for your hard work xHausx :)
[EVO 4G Android Development] bilsoncs:
New Phone , not refurb. use AutoRoot 2.3 and flashing a 3.70 fw everything worked perfect until;

Starting ADB server...

Checking MTD configuration...

Phone uses the old block size.

Firmware version '3.70.651.1'

Battery is at 100 percent.

The ADB Shell does not have root permissions.

Installing exploit...

Rooting...

Looking for Root...

Got Root!

Checking for needed files...

Pushing res\flash_image to /data/local/flash_image...

Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...

Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...

Pushing res\URFSON.zip to /sdcard/URFSOn.zip...

Flashing misc partition...

Rebooting in to bootloader...

Verifying bootloader status...

Bootloader shows Firmware Version '1.17.651.1'

hbootpreupdate set at '11'

Verified the phone has the older MTD setup with hBoot Vers

Verified NAND is locked.

Setting RUU mode...

*

* Flashing Firmware...

*

* It is very important that you do not interrupt this whil

* Unplugging or turning the phone off while it is flashing

* your phone.

*

Rebooting...

Waiting for the phone...

Phone is finalizing the flash, waiting...

Waiting for the phone...

** daemon still not runningerror: cannot connect to daemon

Found the phone connected as 'device'

Giving the phone time to configure itself...

Rebooting into the recovery...

Waiting for the phone...

** daemon still not runningerror: cannot connect to daemon

** daemon still not runningerror: cannot connect to daemon

** daemon still not runningerror: cannot connect to daemon

** daemon still not runningerror: cannot connect to daemon

So I flashed hte PCIMAGE manually and let it reboot but the phone did not have Superuser or root access, and now I start AutoRoot and it said it can't find the SD Card. I can use HTC Sync (new version) and USB set to Charge. Log file attached. What should I try next?
[EVO 4G Android Development] xHausx:
Was your phone ok when you started it up?

Something is interfering with the adb daemon and preventing it from talking to your phone, if you restart your computer it should help with that. If not you should still be able to use the StartRecovery script to bring up the recovery and then flash the URFSOff zip by hand.
[EVO 4G Android Development] tnizzel33:
i had the same problem and i unplugged it and plugged it back in and it finally started up again. it did work for me.
[EVO 4G Android Development] bilsoncs:
Yes, rebooted computer but didn't help. Actual I rebooted computer and phone before starting and turned of anti-virus program.
[EVO 4G Android Development] bilsoncs:
I noticed that there have been several of us that have new phones had problems in the same place, and then not able to access the sd card after. I did manage to get rooted by using Unrevoked, but still can't get an Nandroid back up. I'm downloading Amon Ra now. Just hope the res keys are not gone.
[EVO 4G Android Development] xHausx:
The sd card issue is just from this latest version not recognizing sd cards. The next version will have this fixed along with something to kill any programs that try to interfere with it but I'm doing this all in my spare time so it may not be for a few days.

With all the different types of phones and software versions it's impossible for me to test every single combination.
[EVO 4G Android Development] gpz1100:
TS, did your logs from RA recovery 2.3x show anything unusual? Did you check each log after each restore?
[EVO 4G Android Development] someonenewhere:
So my friend seems to have root on his phone after using this method, but no recovery image..

should i push the recovery image and which one is the best recovery image for this phone????????

another question, how do i get into recovery once i push it? home + power button or vol down + power button?
[EVO 4G Android Development] xHausx:
It sounds like it was unable to finish, the recovery should have been flashed same time the rooted rom was. If you hold volume down while turning that phone on it will bring up the bootloader, from there you can tell if it is unlocked and get to the recovery. If you see s-off it is unlocked.
[EVO 4G Android Development] someonenewhere:
Let me try this again.....thanks Haus, I'll be back and check back with you or anyone willing to offer a hand..

well ****...phone is connected but it can't find SD Card....what are we doing wrong????

Starting ADB server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

Checking MTD configuration...

Phone uses the old block size.

Firmware version '1.17.651.1'

Battery is at 100 percent.

Got Root!

Checking for needed files...

ERROR Could not access the SD card!

Make sure your phone is set to charge only and your phone is reading the SD card

properly.

Press any key to exit...
[EVO 4G Android Development] xHausx:
It's a bug in this version, you can get around it by starting it in fastboot mode. Easiest way to get there is either with adb 'adb reboot bootloader' or you can run the flashzip file and tell it to either flash the sprintlovers rom (if it is unlocked) or cancel so you can run autoroot.
[EVO 4G Android Development] someonenewhere:
Starting ADB server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

Found phone in fastboot mode...

Setting RUU mode...

Flashing ROM, Recovery and Radios...

*

* Flashing Firmware...

*

* It is very important that you do not interrupt this while flashing.

* Unplugging or turning the phone off while it is flashing can easily brick

* your phone.

*

Rebooting...

Congratulations! Your phone is now rooted with a custom recovery capable of

flashing ROMs!

Press any key to exit...

----------------------------------------

so does this mean I'm fully rooted? YES? NO?
[EVO 4G Android Development] xHausx:
Thats what it says yup. The log file is what will sure if anything went wrong though. Look for a file named autorootlog.txt
[EVO 4G Android Development] someonenewhere:
Root went perfectly fine after what you told me what to do...

thanks man! He said he'll be donating some cash sometime this weekend...I'll be joining the team when I get my Evo in a couple of weeks (3rd Evo) haha
[EVO 4G Android Development] siptang:
For some reason, I'm getting error code 67 Registration failure.

Any idea of getting around this?

prl update and profile update fails btw ...

sd card not detected...

thanks in advance!
[EVO 4G Android Development] xHausx:
If the PRL updates fail it may be something with the network in your area. Try turning off your phone and pulling the battery out for about thirty seconds or so. If that doesn't work then you can reactivate your phone and it should reset everything.

If it is just the network in your area and you try to reactive it you may not be able to use it at all until everything starts working again though. When they turned on the 4G here everyones was doing something similar for a day or so.
[EVO 4G Android Development] Amco:
Thanks for this app, i rooted two people's phone yesterday with it. :D
[EVO 4G Android Development] atomlin06:
stuck at daemon still not running error: cannot connect to daemon

phone went through a lot of the process, after saying it is very important that you do not interrupt....

rebooting...

waiting for phone...

phone is finalizing the flash, waiting...

found the phone connected as device

giving phone time to configure itself...

rebooting into recovery...

waiting for the phone...

**daemon still not runningerror: cannot connect to daemon

phone has picture of phone on screen with red triangle and is still connected to cpu... what should i do next to fix this....
[EVO 4G Android Development] StillConfused:
I was wondering if anyone has a torrent of this file that could be downloaded? I am in Afghanistan right now and it seems that every time I get about half way done with the download ( 13 hours ) it locks up and says it failed...

I would like to get this going on my phone to pass time over here..

Thanks.
[EVO 4G Android Development] Action B:
Haus,

I'm still too nervous to try the autoroot myself, however, I went ahead and donated to you for your efforts here on the community and support your applications development. Thanks for helping me and everyone here with rooting.
[EVO 4G Android Development] mojodc3:
I need help bad

I was in the process of rooting and all was going well, when I went to reach for the phone I hit the power button and updated. Im totally lost on where to go next?

Update: turns out I accidentally updated instead of skipping that step..... I just downgraded and everythings better. :)
[EVO 4G Android Development] newvet:
I`m stuck here also. Any way to fix this?
[EVO 4G Android Development] rwebb616:
First time rooting my Evo

Hi,

I have a launch-day Evo 4G. I went through the autoroot and it got past flashing the firmware and hung on setting up a temporary recovery so I rebooted and the phone came up just fine and I attempted to restart the autoroot.bat process and it now says that it can't read my sdcard. I checked my music app and it sees all my music on the card so I know the phone is reading the card. Kind of stuck.. not sure where to go from here.

Here is the last attempt from the log file:

------------ AutoRoot.bat Begin - v2.3 - Fri 03/04/2011 15:47:11.25 ------------

Params=1'' 2'' 3'' 4'' 5'' 6''

Working Directory is 'C:\autoroot\'

Phone SN is HT05NHL11969

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

Version Major '1'

Version Minor '17'

Battery is at 91 percent.

Checking for root...

UID is 'Got Root!'

Checking for ADB...

PLEN='0' PSTATE='device' RETURNTO='s4' STEP='start'

Checking for needed files...

ERROR No SD card is mounted!

Checking for ADB...

PLEN='0' PSTATE='recovery' RETURNTO='s4' STEP='start'

Attempting to dump the recovery log.

---------RECOVERY LOG DUMP BEGIN---------

/cache/recovery/log: No such file or directory

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

Killing ADB server...

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

Thanks in advance!

-Rich
[EVO 4G Android Development] newvet:
nvm. working again
[EVO 4G Android Development] mntbkr:
Had an issue when I first ran it, after getting my phone back from HTC (repaired camera). restored with the RUU, rebooted my pc and ran it again and it took beautifully. Thanks again for you work.
[EVO 4G Android Development] Action B:
Starting ADB server...

adb server is out of date. killing...

* daemon started successfully *

The phone could not be found or was not ready. ADB and Fastboot report it as

'disconnected' instead of the expected 'device'. Make sure ADB debugging is

turned on, the phone is in the correct mode and that you are using HTC's Evo

drivers that come with HTC Sync.

Press any key to exit...

What does "ADB server out of date" mean?

I didn't hook up the phone to my computer I was just getting familiar with the programs and such without the phone connected.
[EVO 4G Android Development] xHausx:
Try restarting your computer and starting the script while your phone is in the same state, something was preventing the script from connecting to your phone.

I don't know of a torrent for it but you can try downloading it from my dropbox if you want. You may have trouble with the antivirus on the computers there though. You'll know if that's the case if it says it is unable to get a root shell, if so it will fail before it has a chance to change anything on your phone.

Hi Rich,

That is just a bug in ver 2.3, you can get around it by using the FlashZip script to put your phone in fastboot mode and then canceling it. Once there you should be able to start autoroot and it'll run like normal.
[EVO 4G Android Development] xHausx:
Thanks for the donation bro. That's normal when it starts up, it resets the connection with your phone when it starts and when it goes to the recovery to make the connection more reliable. The ADB daemon is what runs on your computer and talks to your phone so that is just saying that it is restarting.
[EVO 4G Android Development] bmsmith80:
So something went wrong during auto root and everything froze when it was trying to create a nandroid backup. i tried to run auto root again and it said got root but then couldn't read the sd card. i flashed pcimg36 from the first root back in june so it was still on 2.1, did the OTA to 2.2 and now i have 3.26.... When I try to run auto root it starts, says something about checking mtd configuration, then a couple things flash up that i can't catch because the windows closes. I have no idea what i'm missing. i can access the sd from my evo and from disk drive mode. i've restarted several times, re extracted auto root to another folder after deleting the old folder. ugh, i'm stuck! please help!
[EVO 4G Android Development] bmsmith80:
I was able to catch the split second where it told me something:

Checking MTD configuration

Phone uses the old block size.

Firmware version 'FRF91'

70 was unexpected at this time.

then it shuts down.

Thanks in advance!
[EVO 4G Android Development] coomercove:
I was using the AutoRoot v2.3 to root my Evo when I got an error message. Below is what my Shell was displaying....

Setting auto-update command to flash Unrevoked Forever...

Rebooting the recover...

Waiting for the phone...

Phone is flashing Unrevoked Forever, you should see a circular icon with a green

arrow pointing down for a moment and then it will restart a couple of times...​

My phone screen did not display the circular arrow pointing down. That was when I knew I may be in trouble. Eventually, my shell/command prompt window showed the following.

Timed out while waiting on your phone to reboot.

Please post your autorootlog.txt file to XDA thread or send it to me direct at haus.xda@gmail.com​

It also gave directions on what to do if the phone is not bootable, which mine is apparently not (when I turn on the phone, it shows the white screen with "htc EVO 4G" and does nothing else). It mentioned using FASTBOOT and flashing the RUU. I have the RUU file, but nothing happens when I press the power button to run Fastboot USB.

I've rooted phones before, but I guess this was one I should have left alone. I would appreciate any help to salvage this. I'd be happy to just get back to factory, non rooted status. I hope and pray that I have not "bricked" the phone.

I've attached my autorootlog.txt file if anyone could help me out, I'd appreciate it greatly.

UPDATE:

When I go into the bootloader, the top line is "SUPERSONIC EVT3 SHIP S-ON". I am probably incorrect... but does that mean the phone is not actually rooted? If so, could I possibly take the phone back to Radio Shack (I have the receipt, just bought the blasted thing yesterday), get a new phone, and leave it the heck alone? LOL