yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] zavex:
Just tried using the 1.6 method with my hboot 0.97.0000 phone. Everything was going fine, it got root, and it appears to have flashed PC36IMG_UD.zip, but then it exited, and it is sitting at the white bootloader screen. Below is the script output and the log is attached. What do i need to do next to finish up?

Here is the program output

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

C:\Users\user\Desktop\AutoRoot_v1.6>AutoRoot.bat

Checking for ADB...

Found the phone through ADB.

Checking MTD configuration...

Phone has the old partition structure.

Checking for root...

The ADB Shell does not have root permissions.

Pushing res\rageagainstthecage-arm5.bin to /data/local/tmp/rageagainstthecage-ar

m5.bin...

*This will take a few moments, please do not disturb this window or your phone

until it finishes...

Looking for the phone...

Found the phone through ADB.

Checking 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...

Pushing res\oldkernel.zip to /sdcard/oldkernel.zip...

Flashing misc partition...

Rebooting in to bootloader...

Setting RUU mode...

Verifying bootloader status...

hBoot version '0.97.0000'

FirmWare version '1.17.651.1'

hbootpreupdate set at '11'

Verified older phone with hBoot Version 0.97.0000.

Verified NAND is locked.

*

* 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...

Looking for the phone...

then was unexpected at this time.

C:\Users\user\Desktop\AutoRoot_v1.6>

-------------------------------------------------------
[EVO 4G Android Development] xHausx:
You had something like three people tell you to run the RUU on page 41 and Page 42, why didn't you try that? :)

I also have directions in the OP under step 3 on how to get the phone out of RUU mode.
[EVO 4G Android Development] xHausx:
There was a bug in 1.6 for phones with the older config, 1.7 should run it all the way through. To continue it from where it left off you can use 'autoroot flashudzip'
[EVO 4G Android Development] zavex:
Ok, now with 1.7 I made it further.

Script output:

C:\Users\user\Desktop\AutoRoot_v1.7_-_No_PC36IMGs>autoroot flashudzip

Rebooting...
Waiting for the phone...
echo was unexpected at this time.

C:\Users\user\Desktop\AutoRoot_v1.7_-_No_PC36IMGs>

and log

------------ AutoRoot.bat Begin - v1.7 - Tue 12/14/2010 12:25:17.57
Params=1'flashudzip' 2'' 3'' 4'' 5'' 6''

sending 'zip' (175072 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOshift signature_size for header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[microp] unzipping & flushing...
INFOstart image[radio] unzipping & flushing...
INFOstart image[rcdata] unzipping & flushing...
INFOstart image[recovery] unzipping & flushing...
INFOstart image[sp1] unzipping & flushing...
INFOstart image[system] unzipping & flushing...
INFOstart image[tp] unzipping & flushing...
INFOstart image[tp] unzipping & flushing...
INFOstart image[userdata] unzipping & flushing...
INFOstart image[wimax] unzipping & flushing...
INFOstart image[boot] unzipping & flushing...
INFOstart image[hboot] unzipping & flushing...
OKAY
Sending 'fastboot reboot' command...
rebooting...

Checking for ADB...
PLEN='120' PSTATE='any' RETURNTO='b2recovery' STATE=''

Phone has rebooted to what looks like a clean install. Is it done or do i need to do more?
[EVO 4G Android Development] oohoy:
so per ur step 5

It will then flash the engineering bootloader and the recovery through fastboot. Once it is finished you can use the bootloader menu to boot into the recovery and make a NANDroid, flash a ROM, radios, etc.

does that mean once autoroot finishes, it wont flash the sprint lover rom included in the zip ? i have to flash that rom manually ? if so, i dont have to use that rom and use other roms instead , say the myra version ? what if i dont flash new roms ? will i still be able to boot into stock rom ?
[EVO 4G Android Development] skeith223:
Wow I need this please my phone has the same software...
[EVO 4G Android Development] skeith223:
Is this a new script that has been added, or is it the same as yesterday Ive been out of the loop since last night...
[EVO 4G Android Development] zavex:
So i think it made it to the step where it is trying to make a nandroid backup. Can i run 'autoroot makenandroid' to let it continue from there?
[EVO 4G Android Development] agrenwa:
when I'm clicking on AutoRoot.bat the CMD window opens and closes right away, same thing happens if I run as administrator, am I missing something?
[EVO 4G Android Development] xHausx:
Hmm ok, looks like there is something else in there it doesn't like so it is canceling the script.

Try 'autoroot tst' while in fastboot mode

Edit: if you start it over normally it should see the nand is unlocked and flash a recovery for you
[EVO 4G Android Development] xHausx:
Correct, it just flashes the recovery and leaves the pre-release 2.1 rom and older radios on the phone. From there you can put whichever rom you want to use on your sd card to flash. It will also leave the radio updates on your sd card for you but it won't flash them.

You'll still want to make a nandroid before doing anything though
[EVO 4G Android Development] xHausx:
Did it make an autoroot.log file? Is not you may need to a open a cmd window through the start menu and use it through there
[EVO 4G Android Development] zavex:
In fastboot mode (bootloader->select fastboot, then changes to fastboot usb), nothing happens. The error at the end of the log is

error:device not found

also running adb devices results in no devices being listed.
[EVO 4G Android Development] xHausx:
Sorry, I told yo wrong. I guess you do need to be in the rom.

After I told you that I also remembered that it should flash the recovery automatically if you run it again normally. Either way you'll still need to make a nandroid and update your rom & radios afterwards
[EVO 4G Android Development] skeith223:
How long is it suppose to check for adb....its just flashing checking for adb for 5 min. now...
[EVO 4G Android Development] Jbcarrera:
had the same problem try this in the autoroot file there is a icon that says adb click on that and let it run and close on its own then click on the autoroot.bat file that should fix it
[EVO 4G Android Development] skeith223:
Did this acouple of times still no go...
[EVO 4G Android Development] xHausx:
You may need to reinstall the stock adb drivers.

It should automatically close itself though, I don't know why it its hanging. You can also delete the log file if you want to get rid of all that. It will make a new one.
[EVO 4G Android Development] skeith223:
Do you mean reinstall the auto root file itself or where do I get the stock adb drivers...
[EVO 4G Android Development] xHausx:
The stock ones will try to install when you plug the phone in.
[EVO 4G Android Development] zavex:
Just running autoroot (from in the ROM) results in:

C:\Users\user\Desktop\AutoRoot_v1.7_-_No_PC36IMGs>autoroot

Checking for ADB...
echo was unexpected at this time.

C:\Users\user\Desktop\AutoRoot_v1.7_-_No_PC36IMGs>

I think was able to make a nand backup by running 'autoroot makenandroid', i ended up with a folder BCD... that contained multiple files with a total size of about 330 MB. Does that seem right? I also grabbed my RSA keys for safe keeping.

In the script itself i see the following steps listed:

:: Process is as follows:

:: 1. Check for ADB, Root, MTD configuration

:: 2. Run rageagainstthecage to get a root shell

:: 3. Copy needed files to the phone

:: 4. Flash the misc partition

:: 5. Reboot into RUU mode

:: 6. Check Security status and bootloader version

:: 7. Flash PC36IMG_UD if NAND is still locked

:: 8. Reboot into the Recovery

:: 9. Make a NAND backup using a temporary Amon_RA 1.8 setup

:: 10. Set autoupdate commands to flash Unrevoked Forever

:: 11. Reboot the Recovery and let it flash Unrevoked Forever

:: 12. Reboot into RUU mode

:: 13. Flash the modified Sprint Lovers ROM

:: 14. Flash recovery with older kernel for pre 2.02 phones

So i think i have made it through step 9 at this point. I am unsure if 10 has also been done, flash Unrevoked Forever. How would i tell if this has been done? If not how do i do it manually (I am guessing i need to). Also you mention updating radios, Earlier in the process i seem to remeber it updating them, i think when flashing PC36IMG_UD, do they need to be updated further?

Thank you for your help so far. Any further help would be appreciated, even if it is just pointing me in the correct direction to finish things up manually.
[EVO 4G Android Development] skeith223:
Installed new drivers and even tried on different computer still hangs at checking for adb, I also redownloaded the auto root file still nothing....
[EVO 4G Android Development] xHausx:
By the looks of it you just need a custom recovery, without your logs I can't be sure though. The bug thats tripping it up for you is in a routine that gets called anytime it looks for the phone so you won't be able to get it to run normally.

from the ROM use 'adb reboot bootloader' to reboot your phone, when it does look to make sure it says S-OFF at the top. If it does use 'autoroot flashrom' to finish rooting.
[EVO 4G Android Development] cmdrogogov:
*nvm* .. .. .. .. .. ..
[EVO 4G Android Development] skeith223:
Mine is doing the same thing even on different computers....
[EVO 4G Android Development] ezsoulja:
does this updated version work on 3.30.651.3
[EVO 4G Android Development] dan0412:
@ Steak, your autoroot log file shows you are still running ver1.6 of the script. Try downloading the current version (1.7) from page #1, and see if it makes a difference.
[EVO 4G Android Development] steak:
Can I run the 1.7 while on the white screen?
[EVO 4G Android Development] dan0412:
You may need to start afresh by flashing the RUU_pc36img.zip (see link on first page).

1. Reboot to your ROM.

2. Download that file (make sure to download the correct version for your phone). 3. Name the file PC36IMG.zip, place it on the root of your sdcard. Power off your phone.

4. Hold lower volume button + Power button -> this will boot you into bootloader.

5. Press power button on bootloader option, and allow it to update your phone.

When done, reboot THEN start afresh with ver 1.7.

HTH
[EVO 4G Android Development] skeith223:
Has anyone figured out why the checking adb hangs in 1.7....
[EVO 4G Android Development] dan0412:
I can confirm it the earlier edited version works on build 3.30.651.3 with hardware version 0003 - very important (not sure about hdware 0004 . So, if your EVO matches these specs, you should be good to go.

EDIT: It seems a couple routines [:_PINGADB], _B2BOOTLOADER in ver1.7 are broken (hence the error : echo was unexpected at this time at startup and midway). Should be easy to fix by xHausx.
[EVO 4G Android Development] steak:
deleted....
[EVO 4G Android Development] gambles:
edit: deleted
[EVO 4G Android Development] ezsoulja:
Damnit.. why i gotta have the damn 0004... Im still **** out of luck and not in the mood to brick the #2nd phone :mad:

thanks tho.. back to waiting
[EVO 4G Android Development] steak:
Thanks... this worked , however I had to pull the microSD card out of the phone and save the PC36IMG.zip manually, rebooted and it finally parse the zip file but still wouldn't do the update, so I took the battery off for a few secs then reboot it in to boot loader and I was able to do the full update of the zip file on the MicroSD... now the phone is back to virgin state...

This is a version 4 Evo, so I think I am going to wait a bit... there are still some users reporting errors when they try to root version 4 phones...
[EVO 4G Android Development] dan0412:
Well, good to know ..... yup, you might want to hold off for a lil bit.
[EVO 4G Android Development] deviantgeek:
Sorry if this comes along as stupid, but im new to rooting. I have the:

2.02 hboot

3.30.651.3 build & software

0004 hardware

Can i root with these specs, or should i wait for the new unrevoked.
[EVO 4G Android Development] steak:
IMO 0004 hardware should wait until further testing....
[EVO 4G Android Development] FrankBlank:
I have the exact same specs. Rooted and flashed a custom ROM a few days ago using the following method: http://xdaforums.com/showthread.php?t=829045

Worked flawlessly.
[EVO 4G Android Development] xHausx:
run 'autoroot flashrom' and you should be good to go, just remember to make a nandroid once you get your ROM set up how you like it.
[EVO 4G Android Development] jesuscakes:
I also forgot to mention that my phone appears to be correctly connected using the right drivers. I have it in usb debug mode and charge only. When I run adb it gives me my phones serial too like it's supposed to yet when I try and run the script it won't work for some reason.
[EVO 4G Android Development] xHausx:
What version of windows do you have? It should work in all of them XP and up but I haven't tested it in anything other than win7 myself. I found a few bugs and fixed them in v1.8 but Im not sure if they will help because I wasn't able to get it to 1.7 to fail with my computer/phone.
[EVO 4G Android Development] jesuscakes:
I am using Windows Vista x64.
[EVO 4G Android Development] jesuscakes:
Maybe I have bad adb usb drivers. Can you link me to some different one's?
[EVO 4G Android Development] kabrutus:
Help please!!! Mine failed and i am at the 4 Triangles and dont know where to go from here? I dont know where to download the RUU from or fastboot??

(Note: If it fails and leaves you with the HTC logo and four triangles you will need to flash the RUU from there. I trust you downloaded the proper one already right? 'fastboot flash zip PC36IMG.zip' will work too.)
[EVO 4G Android Development] xHausx:
You could try installing the android SDK. If you have any other apps besides HTC Sync that connects to your phone installed you'll need to uninstall them also. Those are known to cause issues with ADB

http://developer.android.com/sdk/index.html

It is in the OP under the Links section, all you should have to do is download and run it.
[EVO 4G Android Development] t3project:
the RUU link is in the OP of this thread but here it is again

http://xdaforums.com/showpost.php?p=8826738&postcount=1
[EVO 4G Android Development] t3project:
xHausx

did you ever get it worked out as to why some of the newer phones were getting stuck in RUU mode?
[EVO 4G Android Development] jesuscakes:
When I try to load the drivers from the SDK it doesn't find any.
[EVO 4G Android Development] skeith223:
Still getting the checking for adb hang any suggestions...
[EVO 4G Android Development] xHausx:
I'm guessing that is just something htc added to fastboot to keep people from rebooting after an incomplete flash. In this case that's what we are wanting though. I've been looking for a way to get out of it but I may have to add a step to manually flash it from the hboot in the mean time.
[EVO 4G Android Development] steak:
Are you using a USB hub?

Have you try a different computer.

Sounds like your Drivers are corrupt.

Try these below, they work with Win7 64

http://rs101tg.rapidshare.com/#!download|101l32|283873136|HTC_Driver_64.zip|1476
[EVO 4G Android Development] xHausx:
@Jesuscakes & skeith, could you guys do me a favor and run 'adb devices' from the autoroot directory? Make sure you ate using the newest version as well, 1.8

When I get home I'll make a simplified version (code wise) of the .bat to see if that will help it work
[EVO 4G Android Development] FrankBlank:
It might not be your drivers, it's because you are using a 64bit based system. The guide specifically says to use a 32bit system if possible because that's what it was tested and made on. I have two laptops, one is Windows 7 x64 and the other one is running Windows Vista 32bit. I could only get it to work on the 32bit machine...
[EVO 4G Android Development] xHausx:
Wrong thread, I made this one in 64bit win 7. I didn't even know people still used 32 bit windows :)
[EVO 4G Android Development] steak:
So it looks like xHausx Autoboot v1.8 did it on my Evo Hardware 04

Testing as I type...

Everything went smooth.. I am running Windows 7 64bit, I ran it from the cmd.exe included in the package, took a couple of disconnecting my phone and reconnecting for Adb to catch on.

Here is the log...

C:\AutoRoot_v1.8>autoroot

Checking for ADB...
Found the phone through ADB.
Checking MTD configuration...
Phone has the old partition structure.
Checking for root...
The ADB Shell does not have root permissions.
Pushing res\rageagainstthecage-arm5.bin to /data/local/tmp/rageagainstthecage-ar
m5.bin...

*This will take a few moments, please do not disturb this window or your phone
until it finishes...

Waiting for the phone...
Found the phone through ADB.
Checking for root...
Got Root!
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
Flashing misc partition...
Rebooting in to bootloader...
Setting RUU mode...
Verifying bootloader status...
hBoot version '0.97.0000'
FirmWare version '1.17.651.1'
hbootpreupdate set at '11'
Verified NAND is locked.

*
* 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...
Waiting for the phone...
Setting RUU mode...
Reflashing the userdebug firmware...
Rebooting...
Waiting for the phone...
Giving the phone time to configure itself...
Attempting to reboot into the recovery...
Waiting for the phone...
Found the phone through ADB.
Pushing amon_ra_1.8-mod to /...
Making NANDroid backup, this will take several minutes. Please wait...
NANDroid finished, dumping recovery log...
Setting RUU mode...
Verifying bootloader status...
Verified NAND is unlocked.
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.
*

Flashing recovery...
Rebooting...

Congratulations! Your phone should now be rooted with a custom recovery capable
of flashing ROMs.

The system cannot find message text for message number 0x232b in the message file for Application.

Not sure if the last message "The system cannot find message text for message number 0x232b in the message file for Application." is just a useless line of code he needs to get rid off.

... anyways off to test the Rom and make sure everything works as it should...

Enjoy the beers xHausx, and keep up the great work.

Steak
[EVO 4G Android Development] dan0412:
I was also able to root build 3.30.651.3 hboot 2.02 with this version 1.8.

At first, I got the echo was unexpected at this time warning. Just run 'adb devices' to refresh the connection, and run autoroot again.
[EVO 4G Android Development] xHausx:
Awesome, glad to hear this new one worked for you. The cmd.exe file was actually left in there by accident. lol I was trying to find a way to help skeith run it and forgot to delete it when I zipped everything up. That is where the error message at the end came from.

Thank you for the donation, they are always appreciated.

ohh ok, I think I know what it is doing. Do you remember if it said anything along the lines of "restarting ADB daemon"?
[EVO 4G Android Development] t3project:
let me know. i'd really like to get this other phone rooted.
[EVO 4G Android Development] dan0412:
Yes, that was it.
[EVO 4G Android Development] MedSchool26:
I've tried downloading autoroot from 3 different mirrors now and when I try to extract in winrar I get "the archive is either in unknown format or damaged"?
[EVO 4G Android Development] xHausx:
I used 7zip to zip it, they should be compatible but you may want to try using that instead. It's open source so it is free.

http://sourceforge.net/projects/sevenzip/
[EVO 4G Android Development] Vegasden:
I know this is not in the OP..but will this work with the new 2.10 HBoot?
[EVO 4G Android Development] xHausx:
I was kind of hoping you would be able to tell me :) I don't think anyone has tried it yet
[EVO 4G Android Development] Vegasden:
:D...well I'll give it shot tomorrow am. Soon to work & I would like a phone... :rolleyes:
[EVO 4G Android Development] skeith223:
when I run adb devices it scrools real fast and close and it still hangs in checking for adb also I have tried 2 different computers with the same results...awaiting further instructions...Thanks...
[EVO 4G Android Development] skeith223:
Is the adb devices in the folder that says adb? If not I dont see a adb devices folder...
[EVO 4G Android Development] luckylui:
Im gonna have to try it to as i jackd myself went from 0.76.2 to 2.10 and totally unrooted. Sux, but gotta give it a try..

Thanx OP
[EVO 4G Android Development] Robes1:
is there anything for me?

hboot 2.10.0001 is there any way to root available for me yet?
[EVO 4G Android Development] xHausx:
Give this one a try, unzip it to your autoroot directory and try running it. You should see it say "* daemon started successfully *"

If it doesn't you may need to open a dos prompt and enter the commands through that. You can open it by typing "cmd" in the box you see when you bring up your start menu. Once in it just use 'cd' to move to the autoroot folder. an example would be "C:\Users\(yournamehere)\autoroot\"

Sorry for the slow responses but have been at work
[EVO 4G Android Development] xHausx:
Right on, let me know how it goes

Not sure yet, it just came out so there hasn't been that much testing done with it.
[EVO 4G Android Development] skeith223:
Ok I done this and it did say daemon started successfully, press any key to continue...twice then closes....
[EVO 4G Android Development] bulldogimaging:
I have been trying the Autoroot method and my phone continues to reflash the userdebug firmware. Any suggestions on what I should do thanks in advance

dave