Root Heeeellp!!!! Arghh!

[Killfox]

Im new to rooting and android and to be honest ive been on ios for the past 2 years.... Its easier XD

Well im trying to unlock the bootloader on my htc evo 4g and ive hit a roadblock.

I tried going to cmd prompt i did the whole fastboot oem_get_identifier_token and it said <waiting for device

Figured... hey let me pull out the battery again and do fastboot -> bootloader
and it says :

SD checking....
Loading [random crap too fast i cant read.zip]
No Image!
Loading [random crap too fast i cant read.nbh]
No Image!
Loading [random crap too fast i cant read.zip]
No Image!
Loading [random crap too fast i cant read.nbh]
No image or wrong image!

I cant get into my phone using fastboot and I'm pretty sure thats required for the root to work...correct me if im wrong.

Here is the top information

*** LOCKED (OOW)***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICOP-014F
...... blah blah blah

Android version:2.3.5

Im not bricked because pulling the battery out give me normal boot... htc Evo 4g -> Sprint -> 4g and then my home screen

Im stumped..... also when i select recovery i get that wierd phone with the triangle and "!" that are red.....

PLEEASE HELP I'm stuck at waiting for device....

 

[markzombie82]

are you using the revolutionary program to root from what ive read its t e perfered method. im just here researching how to root this phone. so your further than me.

 

[bigbear6708]

what is your software version...4.67..etc? if so, its a little more complicated..not sure how "advanced" you are, so excuse my ignorance! in my experience when I rooted..."waiting for device" meant first that I did not have the HTC drivers installed on my comp..then when I did my wifes EVO, it meant my usb cable was messed up.'

 

[Killfox]

are you using the revolutionary program to root from what ive read its t e perfered method. im just here researching how to root this phone. so your further than me.

Heres the guide I'm using.... Captain Throwbacks method

http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html

Im using Htc dev to unlock the bootloader and downgrading my hboot to 2.10....Then Ill use unrevoked to finish root.... Im stuck at the end of htc dev method....
the simple problem is that on my cmd prompt it says "<waiting for device>"

the rest is stuff i just found when trying to start my phone from that wierd simple boot menu

 

[markzombie82]

http://wiki.cyanogenmod.com/wiki/HTC_Evo_4G:_Full_Update_Guide
latest guide from cyogenmod

 

[Killfox]

what is your software version...4.67..etc? if so, its a little more complicated..not sure how "advanced" you are, so excuse my ignorance! in my experience when I rooted..."waiting for device" meant first that I did not have the HTC drivers installed on my comp..then when I did my wifes EVO, it meant my usb cable was messed up.'

I am running 4.67.651.3 and im pretty sure i have the correct drivers installed..... if you could give me a download link itd be much appreciated

 

[ocnbrze]

Heres the guide I'm using.... Captain Throwbacks method

http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html

Im using Htc dev to unlock the bootloader and downgrading my hboot to 2.10....Then Ill use unrevoked to finish root.... Im stuck at the end of htc dev method....
the simple problem is that on my cmd prompt it says "<waiting for device>"

the rest is stuff i just found when trying to start my phone from that wierd simple boot menu

I am running 4.67.651.3 and im pretty sure i have the correct drivers installed..... if you could give me a download link itd be much appreciated

if you go to the first method in the guide you linked, there is a link to the htc drivers. when you get the waiting for device, make sure that you have the phone on usb debugging and that it is on charge only.

 

[Killfox]

if you go to the first method in the guide you linked, there is a link to the htc drivers. when you get the waiting for device, make sure that you have the phone on usb debugging and that it is on charge only.

victory!!!! thanks i think i got it from here XD.... what I did was fastboot USB and that got me through the token retrieval and the unlock....

 

[ocnbrze]

ah yes. sorry yeah you needed to be in fastboot for the command to work. sorry about that.

glad you got that part working. now downgrade your hboot and go and get your root on!!!!

 

[TylerHunn]

Im a Total l newbie to this. Had the same problem with the evo 4g.Was on htc dev site for unlock bootloader. I picked all other devices supported in the devices list, also I tried exact steps in the evo 4g+ korea telecom one in the devices list. I downloaded all the required files and installed sdk manager and htc sync. I updated the tools in sdk manager so i could access the files i needed like fastboot.exe and the other three. Followed all the direction on the htc dev unlock bootloader instructions. I opened command prompt I did cd c:\android, then id type fastboot oem get_identifier_token in command prompt. It would say "waiting for device" forever. trust me i waited. I went in every forum looking for an answer. Ive tried so much stuff. I redid drivers like 4 or 5 times. then back to the original, tried downloading pdanet for its drivers, didn't work
then i learned other commands like adb devices to type in command prompt. so it would say list of devices but nothing would ever show up. So I did more searching and some said remove htc sync and re install. so I did that and then after I'd type adb devices in command prompt and it showed my device. I was excited because I had been at it for hours. so I typed in command adb reboot bootloader and my phone shut of and loaded in the bootloader screen. my computer beeps and says htc boot loader interface under android in device manager. so I type command CD c:\android, then type fastboot oem get_identifier_token. It still says waiting on device for ever again. Restarted both the phone and the pc. did some more research
and tried other commands in command prompt while on the bootloader interface thing like adb kill-server, and a bunch more i was at it for over an hour trying to figure this out. I decided to delete and redo everything and still didnt work. im so pissed by now. i spent 12 hours messing with this in two days.i went to sleep. yesterday i thought why dont i try it on my girlfriends win 7 laptop. btw i was using win xp home edition sp3 on an old skinny gateway pentium 4. dont know if it matters. but an old computer.. So i reinstalled everything on her computer. sdk, platform tools, htc sync, all of it.. drivers downloaded automatically and one difference i did notice that when installing htc sync. on my xp computer it always said error installing driver.3.0.0 ### a dont know exactly but it stared with that.. this time on the windows 7 computer it didnt. everything worked fine. i made sur3e my three files were in the folder i made called android. under C:\android. i opened command prompt with my phone i=on charge only with usb debugging on and fastboot turned off( the one in applications ).. II typed in cd c:\android
adb reboot bootloader
phone shuts down and goes into bootloader mode\usb
then fastboot oem get_identifier_token.
it pops up in like the blink of an eye.
I right clicked it and copied it then restarted my phone since this whole time the only way I have internet is through easy tether. I wait for it to load then went back to where you copy the token into. it sent me an email with a file as an attachment. I put that into the android folder I created under c:\android.. Vlc media player was reading it as a video file or something but i put it in the folder anyway. it was called unlock_code.bin. Now i go to command prompt and type in fastboot flash unlocktoken Unlock_code.bin. now it does its thing and my phone restarts. takes a lil longer than normal but its ok. only bad part was the phone goes back to how it was when i first bought it. everything is still on my memory card though so its ok. I then rooted it and put mikg rom on it. but that was the easy part. kinda cool watching it change. I feel like I got a new phone. and my wifi unlocked. so hope this helps.