Home

Share this Story

How to: Unlock the Galaxy Nexus Bootloader

galaxy nexus bootloader

We may be just days away from the release of the Galaxy Nexus on Verizon, and I’m sure that many are starting to think about this whole bootloader unlocking process. As a Nexus device, the bootloader does not have to be bypassed or hacked like you have probably had to do to your last couple of phones. It’s a developer device that is made to be open. You can unlock your G-Nex within a couple of minutes as long as you have all of the right tools in place.

To get you prepared, we have put together a set of instructions that should cover the whole process. The big trick here is to get the Android SDK installed and to have it recognize your device through adb. Once you have done that, you should be able to unlock your phone with 2 simple commands and a quick volume press on the device.

And we are telling you about this now, because unlocking the bootloader of your Nexus should be step 1 before you get into customizing it to your like, downloading your favorite apps, etc. Unlocking the bootloader wipes your phone clean, so you will want to take care of this step from the get-go instead of having to start over on your phone down the road. Once your phone is unlocked, you won’t have to worry about unlocking it ever again.

So your homework until the phone arrives, is to check out the first 7 steps that we have below to get your Windows computer all set up for adb through the SDK. If you can get your phone to reboot to the bootloader by typing “adb reboot bootloader” then you should be all set. Your current Android phone should work just fine in getting this all set up.

Ready?  

Instructions:

*Windows only.

*You will need to install this Samsung driver.

*If that driver does not work, you may want to try this one.

1.  Most important piece to this, is getting the Android SDK set up properly. [Instructions]

This can be one of the most difficult things to get set up, however, you cannot go forward without the SDK and adb set up and working. The instructions we linked should get you setup. Once the SDK is installed, you can move on to step 2.

2.  Place a fastboot.exe file in your SDK/Tools (or Platform-Tools) folder (same as your adb.exe file) if it is not there already. [Download]

*You may also need to move AdbWinApi.dll into the same folder as your adb.exe and fastboot.exe if you are running into issues. I believe in the latest SDK, that everything defaults to SDK/Platform-Tools rather than SDK/Tools. Just depends on the version you are using. The big thing, is to get adb.exe, fastboot.exe, and AdbWinApi.dll into the same folder.

3.  On your device, turn USB Debugging on.

Settings>Developer options>USB debugging

4.  Plug your phone into your computer.
5.  On your computer, head into your SDK/Tools folder or wherever your adb.exe and fastboot.exe files are.
6.  Hold SHIFT and right click – choose “Open command window here.”

7.  Type the following command:

adb reboot bootloader

8.  Your phone will turn off and reboot to the bootloader.

9.  Type the following command:

fastboot oem unlock

10.  Your phone will then ask if you want to unlock.

11.  Using the volume keys, highlight “Yes” and then press the power button to select it.
12.  Your bootloader will now be unlocked.

13.  Choose to start your phone and it will factory reset itself and reboot.

*During reboot, DO NOT BATTERY PULL. The phone may loop and loop, but battery pulling will soft brick you and you will have to flash factory images to reset yourself. I was able to unplug from the computer while it was looping and the phone then rebooted itself. Or you may just have to wait a while since it is factory reseting during this first boot.

14.  You are now operating with an unlocked Galaxy Nexus.

Quick video instructions:

YouTube Preview Image

Tips:

-We know that many of you are running into a “waiting for device” issue when apply the fastboot oem unlock command. This is a driver issue and one that a reader has a suggestion for:

1.  Open device manager on your PC.
2.  Right click on Android 1.0 with the yellow ! mark on it.
3.  Choose update driver.
4.  Choose browse my computer.
5.  Choose Let me pick from a list.
6.  Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7.  It will give you a warning about installing the driver, just click yes.

Alternate USB driver:

-And if that driver still does not work, try this one.  [Download]

Questions:

-Can I still receive OTA updates after unlocking the bootloader?

-Answer:  Yes. Your phone really does not change at all when you unlock the bootloader. You will still receive updates from Google. Now, if you start putting on custom recoveries and  rooting, you may run into issues with receiving OTA updates. The good news is that Google usually releases the system image files for their Nexus phones which makes it a breeze to go back to stock for updates.

_____________________________________

If you run into issues along the way, be sure to drop them in the comments and we will all do our best to help you get through them. The SDK portion will be the most difficult, but there are countless resources out there to get you fully up and working in that department. Once the SDK is ready to go, this really only takes about 5 minutes.

  • windexh8er

    Just finished – did it in Parallels (Windows 7) on a Mac and worked well.  After the OEM unlock portion mine took about 5 minutes on the first boot, rebooted itself and then came back up into the sign on screen.  I had it connected to the guest VM throughout that but – just a note that at least one reboot seems “normal”.

  • http://twitter.com/tjubb Tom Jubb

    I’m getting a “Device cannot start. Code 10″ error after updating the USB drivers.  Any thoughts?

  • Tomgillotti

    I’m getting the prompt. I attempted to open the device manager and right click and update driver, but there is no “update driver” option…. HELP!!

    Email me if you can, tomgillottiATyahoo.com

    Thank you!

    • Tomgillotti

      Got it… nevermind

  • Dshudson

    When I try this,(
    Open up the android-sdk-windows folder and launch the SDK Manager. ) Command Prompt just flickers and nothing happens? 

    • Mikehen08

      Had the same problem. You need to install the Java SDK..download and try to install the installer_r16-windows.exe  from http://developer.android.com/sdk/index.html instead of the zip. It will tell you that you need to install the Java SDK and take you to the site.

  • Mike

    just wanted to add my 2 cents. have to boot to bootloader, waiting for device, installed Samsung drivers manually, unlock, yes, start…

    went into boot loop. on second loop held volume up/down + power, went to start screen. done. 

  • Anonymous

    Samsung drivers no longer available on the Samsung site.

    • Vaglvr

      click on software

  • Toonz

    How can I do this on a MAC?

  • http://www.facebook.com/Max4DSC Darren Surratt

    Got to the end where its rebooting phone,  went to boot animation hung there for few min,  then i unplugged the usb and it was the same for a few min.   Then i removed the batt and powered back on  now its looping at the google screen!!!!!!!!!!!!!!!!!!

    HELP!

  • Mike

    cant seem to get abd to work, keep getting “‘abd’ is not recognized as an internal or external command, operable program or batch file..”  Help…

  • Ryan

    I cant seem to find the driver to update the android 1.0 device can anyone walk me through it please. when you say manually find the driver where do i go?

    thanks for any help

    • Nybandit2000

      I had same problem with it waiting for device. What I did at that point was:
      1-open device manager
      2-right click on Android 1.0 with the yellow ! mark on it
      3-choose update driver
      4-choose browse my computer
      5-choose Let me pick from a list
      6-scroll down and find Samsung driver with newest date. Should be from driver you downloaded and installed from DL link. ( mine was dated 11/25/2011 ).
      7-It will give you a warning about installing the driver. just click yes.

      That should be it. It worked for me but no guarantees. I take no responsibility if you try this!
      Hope it helps.

      • Dshudson

        my samsung driver has like 20 folders?

  • Whytecountry

    I don’t understand. fastboot oem unlock doesn’t work. it says waiting for device and it does nothing. I’ve installed all the drivers, I still don’t know what “AdbWinApi.dll”. The instructions say I may have to put that into platform-tools, except it doesn’t say what it is or where it comes from. And I haven’t gotten any “AdbWinApi.dll” specific errors. But it’s installed all the drivers, so I don’t see what the problem is.Anyone?

    • Nybandit2000

      I had same problem with it waiting for device. What I did at that point was:

      1-open device manager

      2-right click on Android 1.0 with the yellow ! mark on it

      3-choose update driver

      4-choose browse my computer

      5-choose Let me pick from a list

      6-scroll down and find Samsung driver with newest date. Should be from
      driver you downloaded and installed from DL link. ( mine was dated
      11/25/2011 ).

      7-It will give you a warning about installing the driver. just click yes.

      That should be it. It worked for me but no guarantees. I take no responsibility if you try this!

      Hope it helps.

      • Jothen2002

        Just to clarify.. You mean device manager  ( ie printers etc.) 
        I see the Android 1.0 with the yellow exclamation but no option to choose update driver…just trouble shoot ..then nothing…

        Maybe I did not install the driver correctly in the first place? Is this the driver link form the Samsung website ?? file version 1.4.6.0??? 

  • http://twitter.com/xwera43 Bob – Ex-WERA #43

    Can instructions for Mac OS X be added to the OP? The SDK part is easy enough (although I should update my SDK version) but it’s the fastboot.exe portion that leaves me scratching my head. As well as the face my phone won’t arrive until tomorrow.

    Thanks!
    X

  • Jrboldt76

    Ok. So ive got the list of Java SE Development Kit 7u2 on my computer screen. Which one do i pick?

  • Anonymous

    So say I had to take it in for a hardware issue. If I relock the bootloader can they tell it was ever unlocked?

    • http://profiles.google.com/jyonke15 Joseph Yonke

      Since more employees will simply attempt to boot the phone, and won’t see the unlocked icon, meaning its still locked, they will assume nothing. They don’t plug it in a run a diagnostic test on it.

  • Tom Craig

    Hey guys, quick question.  This is my first Android device, so I’m new at this so please bear with me!  I have the SDK all installed, and followed the directions linked above in the Wiki.  When I initially run “adb devices” it kicks back a device, but it is listed as offline.  Then, when I try to run “adb reboot bootloader” it says error: device not found.  Any ideas? Thanks!

    • Clayton Dukes

      Same here – did you find out what the problem was?

      • Clayton Dukes

        I figured it out – put the phone back in usb debug mode

  • Testingchip

    Great instructions guys.  Worked like a charm.
    Thank you

  • Nickles96

    @Kellex – can you please post another Sammy driver link? Original is 404.

  • Erick

    Where do i type “fastboot oem unlock” ??

  • http://profiles.google.com/jyonke15 Joseph Yonke

    For those who are stuck in the Google boot load. There are some instructions for getting out of this that might be getting burred down in the reply’s. So here it is again at the top.

    Pull your battery and boot into the bootloader by holding down down volume buttons and the power botton at the same for a few seconds. The bootloader will load up. Now go back to your tools/platform tools folder. I used put my files in the platform tools folder. Run the command prompt out of that. Type “fastboot oem lock”. Now do it again and type fastboot oem unlock. Accept to unlock your Nexus and LET THE BOOT LOADER RUN. It colorful bootload screen took a while, then it went back to the Google screen, then the colorful bootloader again and then it was fine. just let it go, it will be fine.

  • Big Red

    After going through a broken GNex with 4.0.2 update, using Superboot is the easiest and only method that worked.  Follow those instructions, wait for up to 10 minutes on the softboot.  Yes, it takes a very long time.  Just wait.  Once done, you are rooted.

  • Italia1918

    theres no drivers on the link above?

  • Jeff Tycz

    when i try “adb reboot bootloader” it tells me “error: device offline” any help with that?

  • Matthew Marshall

    Does unlocking delete the contacts on the phone?

  • http://twitter.com/adrianr1189 Adrian

    I’m having a problem after doing adb reboot bootloader. It shows the Start screen with the android on it but my computer doesn’t recognize it anymore. When I fastboot oem unlock it says waiting for device. I installed the Samsung driver and the SDK.

    • Dshudson

      same here

  • Christopher LaPointe

    ADVICE: If you get stuck in a loop with just the Google screen and the unlock icon, DON’T freak out (I took the video to mean to reset your device manually if it keeps showing the colorful animation for a few minutes- that’s a bad idea).  Enter the bootloader by holding down both volume buttons and then the power button, lock the bootloader, unlock it again, and then just be a bit more patient for the first couple of boots and resets.

    • http://profiles.google.com/jyonke15 Joseph Yonke

      How did you get past the command prompt? It will not recognize that the Nexus is attached while its in the bootloader.

  • Haproot

    I get to the point of running fastboot oem unlock, however my computer can’t seem to find a driver for “Android 1.0″  I’m pretty sure I followed the instructions exactly even the SDK instructions.

    • Anonymous

      I am right there with you. I followed everything to the T. Even replaced the driver file, ran the update in device manager. What the F?

    • http://twitter.com/adrianr1189 Adrian

      I’m having the same problem.

      • http://an.droid-life.com/ Dan

        I ran into the same problem. I ended up downloading the driver from here http://forum.xda-developers.com/showthread.php?t=1362957

        “If you get “waiting for device” you might need the USB drivers: DOWNLOAD” – This is the section where you should download the driver if you get this problem. 

        Once downloaded, go to your device manager and update the driver manually using the zip (which you extracted somewhere). You can then run the “fastboot oem unlock” command and unlock your device

        • wookaru

          Perfect. Exactly what I needed to do for the “Android 1.0″ driver issue. Thanks!

  • Anonymous

    HELP! I have done EVERYTHING. My computer will see my phone as an adb device under command prompt in normal mode. When in bootloader mode, my computer will not see it. I get all the way to the “fastboot oem unlock” command and I get the “waiting for device” message.
    Can someone help me?

    • GALAXYNEXUSFANATIC

      I have the same exact problem

      • Anonymous

        Scroll down, Nadeem has the solution. Run the first step and get into bootloader mode. The go look for the Android 1.0 under device manager. It will be there. Do the fix exactly how Nadeem says. You will get the driver to install then. Enter the “fastboot oem unlock” after. It will run. It will seem to bootloop, but just wait.
        Welcome to unlocked Galaxy Nexus baby!!!
        Thanks Droidlife!!!!!

      • Anonymous

        As do I….

  • Anonymous

    I have the “waiting for device” problem as well. but in the device manager, I do not get the “android 1.0″ choice. The only weird one I have says “USB Device” under “other devices”. Any advice?

    • Anonymous

      I am right where you are. It seems the computer sees the device until its in bootloader mode, then the device is not visible.

  • http://profiles.google.com/steven.r.sears Steve Sears

    Help, everything went fine, it said it was unlocked, I have the unlock symbol when the phone starts up again, but it keeps rebooting itself, never leaving the google logo screen. Please tell me I did not just throw $700 out the window

    • http://profiles.google.com/steven.r.sears Steve Sears

      Got it, had to go back to fastboot and relock, the unlock again, and after a couple loops, it started. Thanks for the directions.

      • wookaru

        Yeah, mine did 2 complete reboots before it came up. I wonder if that is part of the wipe process…

  • Anonymous

    First off, be patient. Worked fine after a couple of glitches. MAKE SURE you have the right path, otherwise you will get the “not recognizing” command. Then, AFTER “adb reboot bootloader” install the driver dated 11/25, (thank you gentlemen for the tip!!) and then DO NOT pull battery. The phone will cycle for a couple of minutes. LEAVE IT ALONE!!! That’s what worked for me. Btw, after “fastboot oem unlock”, it wouldn’t reboot by itself. I had to turn it off and then back on. Thanks again for the tips…..

  • Peterobri

    How can I get root access to install titanium backup and restore from that?

  • Jaeson Han

    I did everything and I unlocked the phone, but it’s under a reboot cycle and it won’t stop even if I unplug the phone.  I held down power and volume down and it says, “Downloading…”

    Did I brick this thing already?

    • http://profiles.google.com/gonnadie4thegov Jeremy Wray

      took about 5 min and 3 bootloops for it to finally boot up for me

  • Sean Couch

    just unlocked the phone.  Had the looping issue too but just connected the phone to my computer and fired up the command prompt screen and did fastboot oem lock then fastboot oem unlock. It unlocked the bootloader again. I waited for the device to boot up and do the whole color looping thing and it was fine

  • Keyston

    I ended up having to install PDANet and use the drivers from there, then on reboot the phone stayed at the google screen for 20+mins.. I ended up doing adb root and finished my rooting process just fine, then did a battery pull

  • Grant Fritts

    LOOPING AFTER UNLOCK….

    So jut like at the end of this video, I had to pull the USB plug, however, now all that the phone will do is loop on the black Google   screen over, and over…

    • Grant Fritts

      sorry looks like others posted the same problem, but not seen a solution yet….

    • Grant Fritts

      Sinp3cadoCollapse
      In case someone else has this problem, Skillz posted a response:I was stuck at the google looping screen too, i made the mistake of taking the battery out while it was looping through all the colors. Hold the volume up and down keys at the same time along with the power button. This should take you back to the bootloader screen. Next you need to connect the phone to your computer and fire up the command prompt screen and do fastboot oem lock then fastboot oem unlock. next unlock the bootloader again. the device should boot up and do the whole color looping thing. i left mine plugged in and after 5 minutes it finally came back on. i guess the key is not to power down while its looping through the colors. just be patient and it will go to the login screen. hope this helps

  • http://www.facebook.com/barbie.doll.keri Keri Newsom

    Question, is there a way to get it in DIAG mode?

  • Sinp3cado

    I am boot looping on the Google start up with the unlocked lock… Any help?

    • Grant Fritts

      uhhh…yeah, me too…fun, eh?  Wife: “so you’ve already wrecked your new phone?”  Me: “But I need to get my titanium backups…”
        

    • Sinp3cado

      In case someone else has this problem, Skillz posted a response

      I was stuck at the google looping screen too, i made the mistake of taking the battery out while it was looping through all the colors. Hold the volume up and down keys at the same time along with the power button. This should take you back to the bootloader screen. Next you need to connect the phone to your computer and fire up the command prompt screen and do fastboot oem lock then fastboot oem unlock. next unlock the bootloader again. the device should boot up and do the whole color looping thing. i left mine plugged in and after 5 minutes it finally came back on. i guess the key is not to power down while its looping through the colors. just be patient and it will go to the login screen. hope this helps 

      • Grant Fritts

        w00t!  I guess I was being too impatient…didn’t think to relock the unlock to recyle!

  • Anonymous

    Tip, you can do this on Linux too.  I just did.  Download this: http://www.filesonic.com/file/4047388074  Then extract.  From terminal, run ‘./adb-linux reboot bootloader’.  Then run ‘sudo fastboot-linux oem unlock’.  The rest is the same.

  • Mike

    i actually cant reboot to the bootloader… typie in abd reboot bootloader and “‘abd’ is not recofnized as an internal or external command, operable program or batch file..

    what gives?

    • Mike

      anyone?

  • Upr0ck1718

    Noob here how do i open command prompt windows xp? Dont know how to open within folder? Shift and right click doesnt seem to work.

  • Benjamin Mackie

    HOLY CRAP! just ran a speed test, im getting 32mb/s!!! Almost twice my normal internet speed!

  • Kristofer Fitze

    Is there a list of complete updated instructions with all the changes(in instructions) that have been recommended by the posters on this topic?

  • http://twitter.com/daltonmarks Dalton Marks

    To those confused about getting a waiting for device message:  Android 1.0 will appear in Device Manager AFTER you run adb reboot bootloader.  Once you see that, navigate through and manually add your SAMSUNG Android Phone device driver (“Let me pick”) – should be dated 11-25.  This is the driver you downloaded from Samsung.

    • Anonymous

      Promote the above comment. This happened to me as well and this is exactly how I fixed it. BTW, you have to be an admin to update from the device manager (or under printers and devices.)

    • Jason

      I was hung up there for awhile on this.  Thanks for your help!

    • Ironmanchevy

      Thank you so much!! I was stuck on this for hours. Worked after first try!

    • Paticao

      thank you dalton

    • Guest

      That did it. I, like others, was stuck at the damn waiting for device. I followed the instructions posted further down but did nothing. Found the Samsung drivers I downloaded and it worked great.

    • http://twitter.com/jasonhuntington Jason Huntington

      Thanks bro. Worked perfect.

    • Tnfan2k12

      Thanks a million that was about to get the best of me. The easiest way is to pick from a list of drivers and find the Samsung driver there. Thanks Again

    • richard melcher

      This took me hours to figure out, finally found a fix on XDA’s site. 

      http://forum.xda-developers.com/showthread.php?t=1392310

      under “1. Installing ADB/Fastboot Drivers”
      and “Note: 1″

      • reeby

        same here thanks ALOT! for the link. fixed it right away after hours of messin with it… wish i had read this a few hours ago lol

      • Anonymous

        thank you very much sir.

    • http://www.facebook.com/joshbelile Joshua Belile

      Well done, Sir.  Fixed my “waiting for device” issue.  Much relief.

    • babadush

      Thank you for this that stumped me. Mad props!

    • http://twitter.com/izzledizzle28 Alex Niehaus

      Thanks man!

    • Btpetrina

      Can someone please help me, I am getting the waiting on device message but when I go to my devices it is listed as unknown device?  

    • stanlet

      Thanks, man!  Very helpful.

    • Anonymous

      Thanks for the info, but I am still having some trouble. I downloaded/installed the driver at the link provided. However when I try to manually select the driver, in my SAMSUNG/USB Drivers folder I have a list of ~25 folders. nothing is labeled Samsung Android Phone device driver or dated 11-25. What am I doing wrong? thanks in advance for your help

      • Jeff

        did you ever get an answer to the trouble you pointed out in your comment . I too see this list of “drivers” nothing with any date 11/25…just wondering if you ever heard. Thanks

        • Anonymous

          Dont use the browse function that comes up with the auto play. Go to the control panel and bring up the device manager. You will see the android 1.0 device listed there. I wrote this reply on my unlocked nexus!

          • Tony bag o donuts

            Bumpster, 
            Mine appears there but still needs a driver.I installed the samsung drivers before doing the sdk and have the list of 25 folders starting with 01_Simmental all the way through 25_escape.  my path is c:program filessamsungusb drivers(and all the folders above)
            Any ideas?

          • Anonymous

            Like I said, Do not click install driver balloon on the lower left of the screen. Actually go into your Control
            Panel. Then select the DEVICE MANAGER. It should bring up the entire list of all the devices/hardware on your computer. There, you will see the Android 1.0 with the exclamation point. Right click on that, and it will provide you with an option to update. then follow the instructions.

          • tony bag o donuts

            Yeah that didnt work as i thought. I didnt choose samsung or android dricers. I chose foogle and it finally worked

    • Anonymous

      finally figured it out! Thanks for the help!

    • sw

      i’m not having any drivers populate the SAMSUNG Android Phone device driver list… 

      • sw

        “(Unable to find any drivers for this device)” despite installing the samsung driver linked above. please help. thanks.

    • Thebird36

      none of mine are dated 11-25 and is it under Google Inc. or Samsung Electronics cause there is ADB Interface for both of them

    • http://www.facebook.com/malik.a.khan1 Malik Ali Khan

      Hi Dalton I am having major issues. I tried your way where i did pick the driver but it says there is a code 10 error? Do you have any idea what that is or does anyone cos it is totally bricked atm

    • al_dizzle419

      +1 to @twitter-15596546:disqus .was stuck on the “waiting for device” error, then i scrolled down and read this. IT WORKED FLAWLESS. this tip should be added to main post

    • Peterwlio

      i already ran adb reboot bootloader and android 1.0 still isn’t showing up – please advise!!

      • Peterwlio

        it appears as “Unknown Device”. not sure what to do

        • Michael Mason

           Richard Melcher post was the solution for me with the same issue. 

          This took me hours to figure out, finally found a fix on XDA’s site. 

          http://forum.xda-developers.co

          under “1. Installing ADB/Fastboot Drivers”and “Note: 1″

    • http://www.facebook.com/people/Ben-Keen/841668468 Ben Keen

       So glad I scrolled down all the way through this post before going through the steps.  Your tip saved me from what would probably be hours of head hitting off my desk.  Great tip @twitter-15596546:disqus

    • jdiflam

      And to think, the comprehensive advice was in the user COMMENTS section. +1

  • Anonymous

    Thank you so much. The combination of this tutorial and some thoughtful comments from people having the same issue I was having (“waiting for device”) has really empowered me to do some basic Android hacking. Enjoy!

  • Jon

    can the bootloader be re-locked later?

  • BalinorTx

    Thank you guys, it worked great, even the FIX for the Drive issue… Android 1.0 driver could not be found, you have to PICK the Samsung driver you just installed… and I did have the reboot reboot reboot issue ever after I unplugged from the computer… but it did finally boot up .. 

    • Steven Beck

      what is the exact name of the samsung driver. I go to update driver once I see Android 1.0 and then if I select ADB Devices I can choose from 3 different sammy drivers.

  • Guest

    I don’t see the “extras/google/usb_driver” area…anyone know why?

    • Alexa White

      I didn’t have one either.  Now I’m stuck after trying to move ahead (added the directories myself) because the device showed up in the list, but nothing else is happening.

  • Melantus

    the problem he had at end of video is happening to me and my phone is unplugged. Can anyone help?

  • Wizard

    Unlocked the bootloader and now its stuck at the “google” prompt, with an unlocked lock. It won’t boot. Please help!

    • Asdf

      Same here.. unlocked en and endless Google screen/reboot cycle

      • Zyork

        Same here. Did you find a fix?

    • http://profiles.google.com/jyonke15 Joseph Yonke

      Same here

    • Zyork

      Same thing is happening to me. Did you find a fix??

    • bemyax

      Yeppir. Same here. Stuck at Google. If I hold up/down/power (all three), I can break the loop and get back to fastboot mode. But no choices from there will work.

      • Zyork

        I held Down and Power and it took me to the screen that says “Start” and underneath the Android guy it says “Downloading” “Do Not Turn Off Target!!”
        Is this what you’re looking at too?? Blahhhh

  • http://www.facebook.com/nadeemqasem Nadeem Qasem

    wcdave wrote these instructions for everyone having problems. 
    OK! I’ve worked it out (much like others here)

    I had windows 7 so it made it a bit more confusing.

    if you’re stuck at the part where it says waiting for device, you’ve already downloaded the drivers, and it’s saying ‘android 1.0′ on device manager,try this

    Go to device manager, right click on android 1.0, click ’properties’
    click ‘update driver’ 
    click ‘browse my computer for driver software’
    click ‘let me pick from a list of device drivers on my computer’
    click ‘show all devices’ then ‘next’
    click ‘have disk’
    click ‘browse’
    go to the folder you saved the new usb driver in (/extras/google/usb_driver) – you dont need to go into the subfolder
    it should offer 3 options – choose the top one

    that should do it!!

    • Zyork

      I don’t know if I am doing this correctly but I can’t find
        ”C:android-sdk-windowsextrasgoogleusb_driver replacing the “stock” android_winusb.inf.” to copy the new driver into?

    • http://twitter.com/BiGGiE_Q Biggie Quan

      You are the man!

    • http://twitter.com/adrianr1189 Adrian

      Thank you!