09-21-2016 03:35 PM
43 12
tools
  1. internettoughguy's Avatar
    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:08 PM
  2. Jeremy's Avatar
    Your device is connected to your PC and in fastboot USB mode correct? Also you should be typing fastboot-windows oem unlock

    I use Macs only but I'll keep trying to help you the best I can.
    02-26-2010 10:26 PM
  3. internettoughguy's Avatar
    Thanks, mate!

    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:36 PM
  4. Jeremy's Avatar
    And your device does nothing at all? How long does it say waiting for device?
    02-26-2010 10:38 PM
  5. Jeremy's Avatar
    Ah, make sure you have the proper drivers on your computer... download the Android SDK and make sure you can see your device with that.
    02-26-2010 10:40 PM
  6. internettoughguy's Avatar
    It's been saying that for about two minutes this time. I see nothing happening via my command prompt and nothing happening on the phone.

    Could this be a USB driver issue? I'm running Windows 7 64 bit and it auto installs the drivers it deems necessary.
    02-26-2010 10:40 PM
  7. internettoughguy's Avatar
    I have the SDK, checking now....
    02-26-2010 10:41 PM
  8. Jeremy's Avatar
    And make sure you are entering the Fastboot menu... double check that first.
    02-26-2010 10:42 PM
  9. Jeremy's Avatar
    Highlight HBOOT and press the power button. That should work.
    02-26-2010 10:43 PM
  10. internettoughguy's Avatar
    Where do I see that Android SDK sees the device? I opened the manager and have downloaded the 2.1 SDK and documentation and USB drivers...

    Thanks again for your help!
    02-26-2010 10:44 PM
  11. internettoughguy's Avatar
    Believe I'm in the "Fastboot Menu"

    Says "Fastboot USB" at the top

    Underneath that I can choose from Bootloader, Reboot, Reboot Bootloader, and Power Down
    02-26-2010 10:46 PM
  12. Jeremy's Avatar
    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.

    Thanks.
    02-26-2010 10:48 PM
  13. internettoughguy's Avatar
    Will do, thanks for your help!
    02-26-2010 10:49 PM
  14. internettoughguy's Avatar
    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-26-2010 11:31 PM
  15. Jeremy's Avatar
    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.
    So it was a driver issue like I thought. Glad you figured it out.
    02-27-2010 12:10 AM
  16. internettoughguy's Avatar
    Thanks, yeah.

    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.
    02-27-2010 12:52 AM
  17. garfnodie's Avatar
    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)
    wdfcoinstaller01007.dll
    winusbcoinstaller.dll


    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 02:48 AM
  18. garfnodie's Avatar
    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 03:06 AM
  19. Jeremy's Avatar
    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?
    Merged. Sorry that all of you Windows users are having issues. :o
    03-12-2010 12:30 PM
  20. garfnodie's Avatar
    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 07:26 PM
  21. garfnodie's Avatar
    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!!!
    03-12-2010 08:30 PM
  22. internettoughguy's Avatar
    Sorry mate, didn't see your post until today.

    When you're in the command prompt it is not seeing the phone correct?
    03-13-2010 02:27 PM
  23. internettoughguy's Avatar
    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?
    03-13-2010 02:31 PM
  24. garfnodie's Avatar
    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.
    http://forum.androidcentral.com/goog...html#post48741
    03-13-2010 06:05 PM
  25. internettoughguy's Avatar
    No worries mate. Glad you got it figured out. Enjoy the new ROM, it is night and day better than the stock one.
    03-13-2010 06:43 PM
43 12
LINK TO POST COPIED TO CLIPBOARD