Stuck on "Waiting for Device" trying to unlock bootloader

[garfnodie]

Hey man, got it done. This webpage really helped.

How To: Root the Nexus One (Updated 01.11.10) | The Unlockr

I had to play with the USB drivers a bit, if you have anyone running Widows 7 that is having issues, feel free to send them my way.

You say you had to play with the drivers a bit, what did you have to do? I've now tried to unlock the bootloader on three completely different machines(win7 64bit, Vista 32bit & XP 32bit) and fastboot-windows still will not see the phone. How does the phone show up under device manager for you? For me it says "Android Bootloader Interface" under "Android Phone". Maybe I don't have the correct drivers, even though I've updated the Android SDK.

This is really frustrating as I REALLY want to get my phone rooted so I can use Cy's ROM. I messed around for close to five hours last night a couple today and still "waiting for device".

Someone please help!!!

 

[internettoughguy]

Sorry mate, didn't see your post until today.

When you're in the command prompt it is not seeing the phone correct?

 

[internettoughguy]

Did you download Superboot?

When you open a command prompt are you going to the superboot directory?

i.e. c:\superboot

once there have you tried typing:

fastboot-windows devices (then hit enter)

does your Nexus One's serial number show up after you try this?

 

[garfnodie]

Odd, upon reading your questions, I went to the superboot folder and saw a copy of fastboot in there. I had downloaded fastboot by itself from the directions I had read and that was the one not working, I also downloaded superboot linked from the same direction. So I tried fastboot that was contained in the superboot folder and it see's the phone. I feel like such an ass now as I could have fixed this two nights ago. There is obviously a difference in the two fastboot files I got and this should be noted in the directions on here.

These are the directions I was following that need to be corrected.
http://forum.androidcentral.com/google-nexus-one-roms-hacks/7366-how-install-custom-roms-your-nexus-one.html#post48741

 

[internettoughguy]

No worries mate. Glad you got it figured out. Enjoy the new ROM, it is night and day better than the stock one.

 

[garfnodie]

Just to update, I got the phones bootloader unlocked, rooted and Cyan's mod on there. Even got a different launcher on there as well.

I have to say though, I see some of the visual changes the Cyanogen's mod does, but I don't see what makes it "night and day's better" as you said. Maybe there are under the hood kinds of stuff I don't really know about, what is it that makes it so much better in your opinion? Don't get me wrong, it's not bad, but I want to know how to fully use and appreciate it. The Launcher that I installed ([MOD] Launcher2 - QUICK SHORTCUTS! [10/03/10] - xda-developers) seems to have the most benefits that I can see so far.

 

[internettoughguy]

I'm not running that ROM. I loaded up the Sense UI ROM and as a business user, much prefer it (built in sync with calendar as well as contacts and email for exchange).

Also prefer the extra home screens and the ability to look at my mail, calendar, etc without having to click on any icons.

 

[djasif]

New to nexus one

Hey man, got it done. This webpage really helped.

How To: Root the Nexus One (Updated 01.11.10) | The Unlockr

I had to play with the USB drivers a bit, if you have anyone running Widows 7 that is having issues, feel free to send them my way.

good mornign mate


I have window 7 and having the same problem as you, can you please help me will really apprieacte ur hard work thank you

 

[djasif]

I have window 7 and having the same problem as you, can you please help me will really apprieacte ur hard work thank you

 

[lobeezhold]

My phone was recently activated. Now when I'm not using it, it will shut off and when I try to turn it back on the motorola light comes on but then it says bootloader on top then toward the middle it says battery ok, ok to program. What is going on with my phone? Can anyone help me please!!!!!!

 

[internettoughguy]

I have window 7 and having the same problem as you, can you please help me will really apprieacte ur hard work thank you

Can you be more specific... where exactly are you stuck?

 

[internettoughguy]

My phone was recently activated. Now when I'm not using it, it will shut off and when I try to turn it back on the motorola light comes on but then it says bootloader on top then toward the middle it says battery ok, ok to program. What is going on with my phone? Can anyone help me please!!!!!!

This is the Nexus One forum.... Can't really help you with a Motorola. Sorry mate.

 

[LCW]

my work machine that i first tried to use for rooting my Nexus is a Windows XP 64-bit machine... just could NOT get the adb function to work to even see and recognise the Nexus over usb... had the correct driver, uninstalled and reinstalled it like 5 times... the computer sees the Nexus, can mount the SD, etc. no problems... but over ADB... no go...

so instead of fighting, i just used my macbook pro... worked like charm... no driver needed first of all... and secondly, OS X is a unix based OS, just like the Linux based Android OS... so communication between them is flawless... now i'm rooted, and running the Desire ROM... went smoothly once I ditched fighting with the windows machine... windows = winblows...

 

[garfnodie]

For anyone having problems getting fastboot to see your phone, here is what it took for me.

In the instruction that Jeremy posted, he had you download fastboot and superboot. The problem for me was that fastboot-windows contained in the fastboot.zip was not seeing the phone, but if you use the same file contained in the superboot.zip file, it works just fine. You still need to follow all the directions, just when it says to use fastboot-windows, use the one contained in the superboot.zip and it will most likely work.

I have already contacted Jeremy about looking into this and changing the directions. His reply that he's not using windows so he may not have been able to research the problem yet.

 

[spiderx]

I had this same problem, here's what fixed it:
1. Install the SDK
2. Download the USB drivers
3. Go to device manager, click on 'android device' and 'update drivers'. Choose the drivers that you downloaded.
4. Copy these two DLL files to the fastboot folder: AdbWinApi.dll, AdbWinUsbApi.dll
5. Do your fastboot business.

 

[grayzweb]

If your still stuck on >waiting for device<

With phone still connected:
- start menu - right click Computer > Manage > Device manager > right click Android device> update driver
then navigate to where your sdk is installed > extras> google> usb driver folder> OK

I got warning it wasn't signed or something, then continue... worked for me.

 

[orfali]

Hi, any chance you might know where to find those files? they got deleted from the link

 

[charles cheong]

Hi, Thanks for your link dude.

it's helped me a lot.

 

[churchydallday]

hey internettoughguy really having issues with nexus 4 being recognized. let me know what to do man. pulling hairout

 

[Cam Smith2]

This is probably my one and only post.

But.... with the truth, part truths and red herrings you get on the internet, this took a day and a half for me to resolve.

"Waiting for device" was down to the USB driver. The HTC driver Windows almost insists is installed, doesn't work for bootloader. I had to disconnect the phone, then remove the driver. In device manager you need to get the phone to show as android device (not HTC One), removing the driver / disconnect the handset did this for me. Down load the android developer kit ADK, and get the google USB driver to a easy access location. Manually load the driver into the android device. At that point using HTCdev delivered the script as it should do, sending the unlock code. I had a further issue with it not loading the root binary using superSU, superuser 4.3 flashed sorted this out. Bingo one rooted phone.