[GNEX TOOLKIT V11.1.0] Drivers, Backup, Unlock, Root, Recovery, Flash + MORE [GSM]

Search This thread

asdecker

Senior Member
Jun 24, 2011
371
36
mskip thank you so much for this guide! I unlocked first no problem, root I had trouble with so I skipped to install CWM which also worked. Bootlooped a bunch but since fastboot was still working fine I just kept trying and finally root worked. I've never unlocked, rooted, and installed anything this way before so it was an awesome learning experience. Up and running no problems now. Thanks again. Now onto custom roms!
 

dru06

Member
Feb 24, 2010
16
0
Santa Ana, CA
cant boot in recovery

hi,

i followed the guide and everything was perfect i unlocked the phone and rooted it. now i am sorry if this has been asked and answered i just could not find it. i wanted to load a rom and when i tried to boot in recovery it display Google for a couple of seconds then i get the standing android with his stomach open for like a split second then it would change to the android laying down with a red causation sign. again sorry if this is not the right place to post this or if it has been answered already just need a bit of guidance.

thanks in advanced.
 

hogowner

Senior Member
Jul 13, 2010
814
70
NYC #1
How can I tell if I extracted all the files in my c drive..

If I go to start...click on explore,...click on Local Disk c I do see the files there......is that the root?????
this is what I am doing

I installed PDaNet on my puter and my nexus.....before I unplug the USB cable...I start PDanet


I shut phone off.....open up my device manager....and I see android 1.0 with the ! (exclamation)

I update hte driver and it finds the phone....

when I go to the c drive from the command prompt,,,abd type
fastboot-windows.exe devices and hit enter

I do not get the the phones serial # or fastboot.....I only get letters giving me choices ....ie find devices...find serial # etc.....

like -s, -c etc......

what am I doing wrong???

maybe not extracting to the ROOT of the c drive???

thanks for the help
 
Last edited:

jbdan

Senior Member
Aug 30, 2010
3,045
787
Atlanta
Should we still use this 5.5.0.2 CWM or should we substitute the 5.5.0.4 version? Or does it matter
 

dru06

Member
Feb 24, 2010
16
0
Santa Ana, CA
How can I tell if I extracted all the files in my c drive..

If I go to start...click on explore,...click on Local Disk c I do see the files there......is that the root?????
this is what I am doing

I installed PDaNet on my puter and my nexus.....before I unplug the USB cable...I start PDanet


I shut phone off.....open up my device manager....and I see android 1.0 with the ! (exclamation)

I update hte driver and it finds the phone....

when I go to the c drive from the command prompt,,,abd type
fastboot-windows.exe devices and hit enter

I do not get the the phones serial # or fastboot.....I only get letters giving me choices ....ie find devices...find serial # etc.....

like -s, -c etc......

what am I doing wrong???

maybe not extracting to the ROOT of the c drive???

thanks for the help


C:\ is the root of the drive and typicality if you get that message that means it did not understand your command. what you should do is go into the c drive and in an empty space hold Shift and then right click, you will then get an option of open command window here. that is to make sure that you are in the correct spot in the command window, and the command should just be fastboot-windows.exe devices. try that out.
 

MFD00M

Senior Member
Jan 25, 2011
523
63
Thanks for the tutorial, worked just as described on my shiny new gn lte.

Now here's to hoping team win releases TWRP 2.0 recovery for the GN
 

hogowner

Senior Member
Jul 13, 2010
814
70
NYC #1
C:\ is the root of the drive and typicality if you get that message that means it did not understand your command. what you should do is go into the c drive and in an empty space hold Shift and then right click, you will then get an option of open command window here. that is to make sure that you are in the correct spot in the command window, and the command should just be fastboot-windows.exe devices. try that out.



sorry but what do you mean by "go into the c drive and in an empty space hold shift and right click."

works with windows XP?

what is the best way to go into the c drive?

and it also could be I am not extracting the files to the "root"

and just to make sure..I start PDaNet on my phone..hit usb tether..then shut off phone and go into fast boot mode and then go to device manager and make sure I see the drivers?
 
Last edited:

hogowner

Senior Member
Jul 13, 2010
814
70
NYC #1
ok..I am up to rooting my phone....

i typed
the superboot.img command and on my computer it states
downloading boot image............

my phone has the android with open stomach and it is not doing anything...

is this where I wait 10-15 min and pull battery?
on the bottom of phone it says

factory status-okay
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
ok..I am up to rooting my phone....

i typed
the superboot.img command and on my computer it states
downloading boot image............

my phone has the android with open stomach and it is not doing anything...

is this where I wait 10-15 min and pull battery?
on the bottom of phone it says

factory status-okay
The wait is on the google screen so you can pull the battery as it hasnt worked.

Does your fastboot screen say unlocked?

Can you do a fastboot-windows.exe devices to make sure your phone is connected and you get the serial number returned.

If all that is ok and its still stuck on downloading then try redownloading the zip file in the first post and try again.

What model (GSM or LTE) and original build version are you on?

MArk.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
sorry but what do you mean by "go into the c drive and in an empty space hold shift and right click."

works with windows XP?

what is the best way to go into the c drive?

and it also could be I am not extracting the files to the "root"

and just to make sure..I start PDaNet on my phone..hit usb tether..then shut off phone and go into fast boot mode and then go to device manager and make sure I see the drivers?
They mean if you open Windows Explorer and goto the C Drive (top directory where the fastboot files have been copied to) then place your mouse somewhere on that screen that doesnt have files (like at the bottom of the file list), hold down the shift button on the keyboard and right click on your mouse. You will see 'open command window here' in the list and if you select that then it will open a command prompt at that location.

Mark.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
mskip thank you so much for this guide! I unlocked first no problem, root I had trouble with so I skipped to install CWM which also worked. Bootlooped a bunch but since fastboot was still working fine I just kept trying and finally root worked. I've never unlocked, rooted, and installed anything this way before so it was an awesome learning experience. Up and running no problems now. Thanks again. Now onto custom roms!
The whole process sounds and looks very daunting for the first time user but with the knowledge you have now learned and a bit of patience you can step into the world of Android development and make your phone "YOURS" :)

Glad everything worked out.

Mark.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
hi,

i followed the guide and everything was perfect i unlocked the phone and rooted it. now i am sorry if this has been asked and answered i just could not find it. i wanted to load a rom and when i tried to boot in recovery it display Google for a couple of seconds then i get the standing android with his stomach open for like a split second then it would change to the android laying down with a red causation sign. again sorry if this is not the right place to post this or if it has been answered already just need a bit of guidance.

thanks in advanced.
Did you boot back into Android between flash cwm and attempting to load it?

If so then look at the FAQ in post#2 for your answer :)

MArk.
 

hogowner

Senior Member
Jul 13, 2010
814
70
NYC #1
I am fine now!!!
I had to type the commands a few times each before it worked...

but at least it did :)

what rom is everyone using???

Thanks again for everyone's help!!
 

downsay

Senior Member
Jul 11, 2010
213
21
Springfield
You can flash the stock rom back to your device via fastboot which you used to unlock the bootloader.

Go to *THIS* thread and download the file, extract it to your pc and then copy the image-yakju-itl41f.zip to the same folder that you have fastboot. Enter a cmd prompt and goto your fastboot folder, then type:

fastboot-windows -w update image-yakju-itl41f.zip

(or whatever your fastboot program is named).

It will flash the 41F stock rom back to your phone including recovery so you will have to flash that again via fastboot afterwards.

BTW These instructions are for a GSM Galaxy Nexus as you didnt state what you had.

Mark.

Thanks for taking the time out to help me. Unfortunately I do have the lte version.

Sent from my BNTV250 using Tapatalk
 

tryceo

Senior Member
May 27, 2011
77
3
Columbus
Does anyone have a stock image from Verizon lte version? I flashed it without backing up my phone first.


Sent from my Galaxy Nexus
 

JustusIV

Senior Member
Jan 11, 2008
1,370
163
Loved the guide when smooth.

My next mission is to find out the best way for backing up/restoring. I am looking to not reinstall all my apps and have my setting restored. I do own titanium backup. But i have just used that as a precaution up to this point.

Is there a guide out there?
 
Last edited:

nex1685

Senior Member
Oct 20, 2010
450
57
toronto
hope you can help. flashed rom and baseband not there tried to install radio and it says it is installed but when it boots its not there.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 868
    Frequently Asked Questions:

    Q. What is ADB Shell?

    Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).

    From Google:

    Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
    A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
    A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
    A daemon, which runs as a background process on each emulator or device instance.

    ----------------------------------------------------------------------------

    Q. What is FASTBOOT?

    Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.

    It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.

    ----------------------------------------------------------------------------

    Q. I flashed CWM but each time I reboot the Stock Recovery is back

    There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.

    Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.

    OR you can use the ToolKit to rename the files (root access needed).

    ----------------------------------------------------------------------------

    Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader

    1. Download, install and run the Unified Android Toolkit.
    2. Install adb/fastboot drivers (if you havent already done so)
    3. Option 9 to download a Google Factory Image.
    4. After it finishes downloading you will be given the option to flash the image to your device. Do this.
    4. Let the device reboot, then shut it down and re-enter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
    5. Option3, 2 to relock the bootloader.

    Your internal storage will be formatted and data and cache wiped. Your device will now be back to an out-of-the-box FULLY STOCK state and ready to send back.

    ----------------------------------------------------------------------------

    Q. What is the difference between Nandroid and Titanium backup?

    A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.

    Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.

    The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).

    ----------------------------------------------------------------------------

    Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.

    The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.

    ----------------------------------------------------------------------------

    Q. The ToolKit recognises my device in adb mode but not in fastboot mode (or other way round).

    Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.

    You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.

    ----------------------------------------------------------------------------

    Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?

    Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.

    This option will NOT require your bootloader to be unlocked first.

    You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.

    You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.

    The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.

    ----------------------------------------------------------------------------

    Q. I have Windows 8 and cannot install the drivers

    How to Disable Driver Signature Enforcement in Windows 8:

    From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
    Click ‘More PC Settings’.
    Click ‘General’.
    Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
    Wait a bit.
    Click ‘Troubleshoot’.
    Click ‘Advanced Options’
    Click ‘Windows Startup Settings’
    Click Restart.

    When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.

    ----------------------------------------------------------------------------

    Q. I cannot find Developer options to Enable USB Debugging

    With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:

    Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
    When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
    Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
    You can now go into Developer options and enable usb debugging.

    ----------------------------------------------------------------------------

    Q. How do I Update to the latest Google Stock Rom (manually)?

    THE FOLLOWING PROCESS WILL ERASE YOUR INTERNAL STORAGE BACKUP ANYTHING YOU NEED.

    You can use the Android ToolKit which will do everything automatically.

    Or you can follow the instructions and do it manually:

    These steps assume that you have set up your adb/fastboot drivers correctly.

    1. Download it from https://developers.google.com/android/nexus/images
    2. Unzip the .tar file to a folder on your pc
    3. Unzip the needed files from the .tar file to the same folder on your pc
    4. Copy the file fastboot-windows.exe to this folder (you can find the fastboot file in many places including my ToolKit download on post#1) and rename the file to fastboot.exe
    5. Boot the phone into Fastboot Mode (KEEP holding the 'Volume up' and 'Volume down' buttons while pressing the 'Power' button)
    6. Connect your device via the usb cable
    7. Browse to this folder on your pc and run the flash-all.bat file to flash the stock images

    ----------------------------------------------------------------------------

    Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect

    Make sure the code entered is for the correct device being used in the Unified Android Toolkit.

    You need to make sure you start the Toolkit with the toolkit.exe file when activating so the settings can be initialised or the code will not be accepted.

    Also make sure you enter the code correctly as the characters are case sensitive.
    253
    [TOOLKIT] SKIPSOFT ANDROID TOOLKIT -GNEX - GSM- Drivers, Root, Recovery + MORE

    SPRINT MODEL SUPPORTED *HERE*
    VERIZON MODEL SUPPORTED *HERE*

    GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
    SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*

    The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.

    FUNCTIONS OF UNIFIED ANDROID TOOLKIT
    * Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
    * Backup/Restore a single package or all apps, user data and Internal Storage
    * Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
    * Unlock/Re-Lock your Bootloader [Nexus]
    * Root Stock builds
    * Various Root options using insecure boot image or custom recovery
    * ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
    * ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
    * [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
    * Install BusyBox on your device
    * Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
    * Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
    * Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
    * Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
    * Extras, Tips and Tricks section
    * Auto Update ToolKit to latest available version at startup (professional only feature)
    * Program up to 10 Quickpick slots and run them very quickly (professional only feature)
    * Mods section to automatically perform certain tasks on your device
    * Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
    * Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
    * Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
    * Flash Custom Recovery or Google Stock Image to Device
    * Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
    * Rename the Recovery Restore File present on some Stock Roms
    * Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
    * Flash Custom Recovery to Device
    * Boot [Nexus] or Flash .img Files directly from your PC
    * Install a single apk or multiple apk’s to your device
    * Push Files from your PC to your device
    * Pull Files from your device to your PC
    * Disable forced encryption on Nexus6 and Nexus9 devices
    * Install Root Checker app by Burrows Apps
    * Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
    * Install EFS/Partition Backup/Restore app by Wanam
    * Dump selected LogCat buffers to your PC
    * Dump BugReport to your PC
    * Set Files Permissions on your device
    * Open new Command Prompt for manual input
    * Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
    * Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
    * Display Important Information about your device

    --------------------------------------------------------------
    Toolkit_main_menu.png

    --------------------------------------------------------------

    SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*

    DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)

    NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.

    Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.

    --------------------------------------------------------------

    WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
    THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.

    ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
    THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
    THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
    PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).

    MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.

    AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv

    --------------------------------------------------------------

    PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.

    --------------------------------------------------------------

    1. INSTALLING ADB/FASTBOOT DRIVERS

    The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.

    THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.

    If drivers are not installed or there is an exclamation mark next to the device:
    Plug the device in to a usb cable directly connected to your motherboard.
    In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
    Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
    If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
    If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
    Click OK and select Google ADB Interface.

    Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.

    On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.

    --------------------------------------------------------------

    2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT

    When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.

    Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).

    --------------------------------------------------------------

    USEFUL INFORMATION

    How to get into your FastBoot Mode
    1. Turn your phone off
    2. Unplug your usb cable if you have one plugged in
    3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode

    How to get into Recovery
    1. First boot into FastBoot Mode as described above
    2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery

    Show the Menu in the Stock Recovery Screen
    1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.

    --------------------------------------------------------------
    *DISCLAIMER*
    I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
    193
    74
    Manual Rooting Instructions for Galaxy Nexus

    VIDEOS:
    29
    Amazing thread! This thread would probably be really helpful for newbies :)
    Just a few suggestions:
    1.)You might want to include how to flash custom kernels
    and also that you can
    2.)Clockwork Recovery can be instealled through Rom Manager

    Nonetheless, great thread :)
    Thanks :)

    1. Added Step 7, how to flash kernels and Radios via CWM.

    2. Added a Note at the end of the CWM flashing step for the Rom Manager method.

    Mark.