[GUIDE] Unlock bootloader for Nexus S

Search This thread

BigRick10

Senior Member
Jun 10, 2010
809
121
[*] shutdown the phone

[*]hold down volume up + power

[*]Now you are in the standard recovery mode

[*]assuming you have 2.3 SDK installed with fastboot (Google around for that info..), now on terminal/windows
or Windows cmd depending on OS type "fastboot devices" to check your device can be seem via USB

[*]assuming you device is seen via fastboot devices, now type "fastboot oem unlock"

[*]accept...and new bootloader is unlocked...

[*]now we need a custom recovery from clockworkmod or amon_ra, and we'll be good to go

Credit goes to gandalf44


Seems like a lot of people are having issues with the amd64 driver from the 2.3 SDK. Here's a workaround:

  • Go to the PdaNet homepage and download the Windows 7 x64 version of the PC software Download PdaNet
  • Make sure your phone is not connected to the computer. Install the app from PdaNet. Ignore the warning about HTC sync if you get it, that doesn't matter for what we're doing.
  • At the end of the PdaNet install, you'll be prompted to connect your phone. Make sure USB debugging is on, and connect to a high speed (as in not through a hub) USB port.
  • Follow the prompts and accept the unverified driver warning. Let it finish, then reboot your phone into fastboot mode -- power off, then hold volume UP and power.
  • Open the device manager in Windows (right click My Computer, properties, choose Device Manager from the list on the left.
  • Find the Android 1.0 entry, with the yellow exclamation mark beside it. Right click and choose to update the driver.
  • Select to search your computer for the driver manually, and point it at C:\Program Files (x86)\PdaNet for Android\. You will see a warning about an unknown/unsigned driver for sure this time, accept it.
When it finishes, at the command prompt (in the sdk\tools\ directory) type
Code:
fastboot devices
you should now see your Nexus S listed.

Credit to Gbhil
 
Last edited:

demo23019

Senior Member
Dec 9, 2007
2,216
613
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
 
Last edited:

crazifyngers

Senior Member
Nov 15, 2007
102
13
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64

if you are in fastboot mode right cick on android 1.0 and update manually choose the driver and select android bootloader interface. good luck
 
  • Like
Reactions: DOHCtor

DOHCtor

Senior Member
Apr 10, 2009
1,109
121
Southern California
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery

Technically, it's not rooted, but in essence, we all know that once the bootloader is unlocked, we can fastboot flash a custom recovery. And from there, we can flash custom roms or just the su and superuser.apk into the stock rom from recovery. So yea, it is kind of rooted.
 
  • Like
Reactions: Hylianotaku148

jacksonj51

Senior Member
Oct 2, 2008
198
140
So-Cal
Seems I can't update my Android 1.0 device driver.... I've updated everything in my SDK 2.3 but keep getting this ... Hmmmm
 

godsfilth

Senior Member
Mar 31, 2009
140
13

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    [*] shutdown the phone

    [*]hold down volume up + power

    [*]Now you are in the standard recovery mode

    [*]assuming you have 2.3 SDK installed with fastboot (Google around for that info..), now on terminal/windows
    or Windows cmd depending on OS type "fastboot devices" to check your device can be seem via USB

    [*]assuming you device is seen via fastboot devices, now type "fastboot oem unlock"

    [*]accept...and new bootloader is unlocked...

    [*]now we need a custom recovery from clockworkmod or amon_ra, and we'll be good to go

    Credit goes to gandalf44


    Seems like a lot of people are having issues with the amd64 driver from the 2.3 SDK. Here's a workaround:

    • Go to the PdaNet homepage and download the Windows 7 x64 version of the PC software Download PdaNet
    • Make sure your phone is not connected to the computer. Install the app from PdaNet. Ignore the warning about HTC sync if you get it, that doesn't matter for what we're doing.
    • At the end of the PdaNet install, you'll be prompted to connect your phone. Make sure USB debugging is on, and connect to a high speed (as in not through a hub) USB port.
    • Follow the prompts and accept the unverified driver warning. Let it finish, then reboot your phone into fastboot mode -- power off, then hold volume UP and power.
    • Open the device manager in Windows (right click My Computer, properties, choose Device Manager from the list on the left.
    • Find the Android 1.0 entry, with the yellow exclamation mark beside it. Right click and choose to update the driver.
    • Select to search your computer for the driver manually, and point it at C:\Program Files (x86)\PdaNet for Android\. You will see a warning about an unknown/unsigned driver for sure this time, accept it.
    When it finishes, at the command prompt (in the sdk\tools\ directory) type
    Code:
    fastboot devices
    you should now see your Nexus S listed.

    Credit to Gbhil
    8
    Using supercurio's root method I rooted my Nexus S then using ChainsDD's Superuser zip from http://xdaforums.com/showthread.php?t=682828
    I install su to /system/bin/su and Superuser.apk to /system/app
    (If doing this note you will need to "mount -o remount -w /system /system" and need to "chmod 4755 /system/bin/su" and you can copy files from your usb storage using "cat /sdcard/su > /system/bin/su")

    Then I rebooted to stock boot image and ran adb shell and ran su and was set, then I captured some images for you guys:

    Stock boot 4c12cbe2c0cb62532a727b44944e4e34
    http://teslacoilsw.com/android/nexuss/dump/mtdblock2_boot.img
    Kernel from stock boot 2254ab60a9d532cef948b3defd85e048:
    http://teslacoilsw.com/android/nexuss/dump/kernel.gz

    Stock (unlocked) bootloader 8afc4d83941cd9f9ad851efb9f070d67:
    http://teslacoilsw.com/android/nexuss/dump/mtdblock0_bootloader.img
    Stock Recovery 692bda2e140476d3c9418845fd06eaf6:
    http://teslacoilsw.com/android/nexuss/dump/mtdblock3_recovery.img
    Stock Radio ef88f13a1e91b7397fb8c798bbf5512a:
    http://teslacoilsw.com/android/nexuss/dump/mtdblock5_radio.img

    System with only modification being /system/bin/su and /system/app/Superuser.apk 1ced0c2bd493819ef407fb5b44775fca:
    http://teslacoilsw.com/android/nexuss/dump/system.img
    6
    This version is fine :) http://project-voodoo.org/downloads/NSroot/root4.img

    fastboot boot root4.img

    cd /getroot

    ./su-init

    You're root !
    2
    just a fyi. fastboot oem lock will relock the bootloader!!
    1
    someone help please before i lose my mind...
    Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
    im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
    im on win7x64

    if you are in fastboot mode right cick on android 1.0 and update manually choose the driver and select android bootloader interface. good luck