Stuck on "Waiting for Device" trying to unlock bootloader
I am coming over from the blackberry world (where I did a lot of playing around with my blackberries software).
I am however quite new to this whole platform and am obviously not doing something right while trying to root my Nexus One.
I have the necessary file downloaded and unzipped and have the command prompt open. When I try to run the command "fastboot.exe oem unlock"
I get a "waiting for device" message....
What am I missing?
- 02-26-2010, 10:26 PM #2
I am connected to pc and in fastboot USB mode. I mistyped above. I have been entering "fastboot-windows oem unlock"
Always get the "waiting for device" message.
I really want to load the HTC Desire ROM. So tired of my calendar not syncing (and really don't like touchdown)
Thanks for the help
- 02-26-2010, 10:38 PM #4
- 02-26-2010, 10:40 PM #5
- 02-26-2010, 10:42 PM #8
- 02-26-2010, 10:43 PM #9
- 02-26-2010, 10:48 PM #12
Check out this thread here. Many people stuck with "waiting for device". I'm at work and will be leaving shortly so I will be away from the computer for a while. Please update this thread with what you find so I can update the ROM guide in this forum to help other Windows people.
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.
- 02-27-2010, 12:10 AM #15
Windows 7 users, if you right click on "Computer" and select "Manage"
Once the computer management window opens click on "Device Manager"
In the list on the right window you will see your Android Device (assuming your Nexus One is plugged in). Select it and then select "update driver"
Browse for the driver you downloaded with the android sdk.
Once you've updated the driver unplug your phone from the computer and then plug it in to another usb outlet.
You should then be able to get through the whole process.
- 03-12-2010, 02:48 AM #17
Fastboot problems on Windows 7 64bit
I'm having a problem getting my N1 to be seen by fastboot-windows to start the rooting process. As I mentioned in the title, I'm running a Windows 7 Pro (clean install couple of weeks ago), Core2Duo mobile(T8100) with 4gb of Ram. Installed Android SDK, got all drivers installed.
When I boot phone into fastboot, windows see's the phone and shows up in device manager as "Android Bootloader Interface" and it shows up in Safely Remove utility at "Android 1.0"
I then run "fastboot-windows devices" or "fastboot-windows oem unlock" and they do not see the phone.
The drivers referenced by device manager are:
winusb.sys (can't move or replace, windows won't allow it)
Did some searching and came across some stuff about issues with the winusb.sys file and was wondering if this could be my problem and if anyone knows how to go about fixing this?
The phone shows up in windows just fine as a usb drive while in normal operating mode, in case that helps at all.
- 03-12-2010, 03:06 AM #18
Sorry, I didn't see a previous thread similar to my problem (http://forum.androidcentral.com/goog...ootloader.html) Could a mod possibly merge my thread into the other one to help keep things simple?
- 03-12-2010, 12:30 PM #19
- 03-12-2010, 07:26 PM #20
Ok, so I tried using a Vista 32bit machine, fresh clean install of the drivers, then plugged it into a different usb plug and it still can't see the phone. It still shows up in device manager as android bootloader interface, but fastboot-windows will not see it.
- 03-12-2010, 08:30 PM #21
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!!!
- 03-13-2010, 06:05 PM #24
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 *** 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.