HOW-TO OEM unlock the Galaxy Nexus

**phirewire110** · 12-15-2011, 10:40 AM

When I click on enviroment variables, there are 2 edit buttons.
Which one do I click on?

User or system?

**BlackRN** · 12-15-2011, 10:42 AM

Originally Posted by Pat Beats 808

I installed the SDK properly, as well as installed all the dev packs.... However my computer cannot locate/install the "Android 1.0" USB driver. Anyone have this issue?

Got similar notification..

**Limbo1224** · 12-15-2011, 10:43 AM

Originally Posted by phirewire110

When I click on enviroment variables, there are 2 edit buttons.
Which one do I click on?

User or system?

should be the bottom edit button

**Limbo1224** · 12-15-2011, 10:44 AM

Originally Posted by Pat Beats 808

I installed the SDK properly, as well as installed all the dev packs.... However my computer cannot locate/install the "Android 1.0" USB driver. Anyone have this issue?

Does anybody know how to fix this problem? I'm stuck on this step as well.

**phirewire110** · 12-15-2011, 10:44 AM

Thanks guys.
I have 2 friends picking this phone up today.
Gotta get them setup

**phirewire110** · 12-15-2011, 10:45 AM

Wait, so I would be clicking edit on system variables?
What should be highlighted while clicking edit?

**Limbo1224** · 12-15-2011, 10:46 AM

Originally Posted by phirewire110

Wait, so I would be clicking edit on system variables?
What should be highlighted while clicking edit?

you have to highlight path on the bottom box and then hit edit

**phirewire110** · 12-15-2011, 10:50 AM

That variable is windir with a path of C:\Windows

Does that sound right?

**convectivewx** · 12-15-2011, 10:51 AM

Will I have to reactivate my phone after this?

**Limbo1224** · 12-15-2011, 10:52 AM

Originally Posted by phirewire110

That variable is windir with a path of C:\Windows

Does that sound right?

look for path not windir

**phirewire110** · 12-15-2011, 10:56 AM

Originally Posted by Limbo1224

look for path not windir

Ok, thank you.

**zmenchhofer** · 12-15-2011, 11:02 AM

install ed ADB drivers from this location C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver (windows 7) if you dont have that location then you need to download them with SDK manager (USB Tools)

You may have to run the SDK Manager as Administrator

**jbizzle** · 12-15-2011, 11:23 AM

Anyone else getting "waiting for device"? Frustrated!!!

I have the dll, adb, and fastboot.exe all in the same folder and usb debugging checked...

**kichard** · 12-15-2011, 11:25 AM

Im stuck on waiting for device. what a bummer.

**mattollom1014** · 12-15-2011, 11:26 AM

Originally Posted by jbizzle

Anyone else getting "waiting for device"? Frustrated!!!

I have the dll, adb, and fastboot.exe all in the same folder and usb debugging checked...

Yes, Same issue here.

**EVIL_JIMMY** · 12-15-2011, 11:27 AM

When I type 'fastboot oem unlock' into command prompt, I just get this

'fastboot' is not recognized as an internal or external command, operable program or batch file.

Any tips?

**jbizzle** · 12-15-2011, 11:32 AM

Originally Posted by EVIL_JIMMY

When I type 'fastboot oem unlock' into command prompt, I just get this

'fastboot' is not recognized as an internal or external command, operable program or batch file.

Any tips?

Make sure fastboot.exe, and adb are in the same folder (tools or platform tools), then open that folder. Highlight the address at the top of the folder and type cmd. then try the fastboot oem unlock

**mattollom1014** · 12-15-2011, 11:34 AM

Originally Posted by EVIL_JIMMY

When I type 'fastboot oem unlock' into command prompt, I just get this

'fastboot' is not recognized as an internal or external command, operable program or batch file.

Any tips?

I was getting the same thing so I just manually pointed my command prompt to the C:\Program Files\Android\android-sdk-windows\tools directory and ran it there. Of course now I'm stuck with the waiting on device message.

**gpf2ez** · 12-15-2011, 11:34 AM

Also make sure you are using the command prompt and not powershell.

**ggiedd** · 12-15-2011, 11:37 AM

Ok I am stuck. I ran the fastboot oem unlock, unlocked it and rebooted the phone. Now it keeps rebooting at the google screen. It showed unlocked but wouldnt go further. So I then locked it back, and its still stuck on google and reboots.

I did pull the battery too.

Help!

So after waiting, I put battery back in, went back into fastboot and unlocked again. this time it went past the google screen and went through the animation. Took a long time but eventually rebooted and showed unlocked still and then came up working. whew!

**EVIL_JIMMY** · 12-15-2011, 11:39 AM

Originally Posted by mattollom1014

I was getting the same thing so I just manually pointed my command prompt to the C:\Program Files\Android\android-sdk-windows\tools directory and ran it there. Of course now I'm stuck with the waiting on device message.

I've just done the same, and get the same waiting for device.....

**zmenchhofer** · 12-15-2011, 11:44 AM

if you are getting "Waiting on device" then you do NOT have the correct ADB drivers installed... Install the drivers from the SDK location android-sdk\extras\google\usb_driver

**kichard** · 12-15-2011, 11:51 AM

Originally Posted by zmenchhofer

if you are getting "Waiting on device" then you do NOT have the correct ADB drivers installed... Install the drivers from the SDK location android-sdk\extras\google\usb_driver

This may be a stupid question but how do i install this folder?? i click on everything inside of it and nothing gives me the option to install. All your help is GREATLY appreciated

cant wait to unlock this thing so i can finally start making it MY phone!!

**n0apostrophe** · 12-15-2011, 11:53 AM

When I enter the fastbook oem unlock into the command prompt, I get the following error

This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.

Any ideas?

**zmenchhofer** · 12-15-2011, 11:55 AM

I dont think yall should be rooting your phone if you are not able to fix these issues.

kichard - you need to install SDK Manager

n0apostrophe - you need to install the SDK tools / paltform-tools