• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[International / GSM] [How To] All Things Root Samsung Galaxy Nexus

Status
Not open for further replies.
.
Note: this step is not necessary for Mac or Linux users since adb and fastboot seem to connect right out of the box for those platforms.

Unfortunately, Microsoft Windows uses need to install special USB drivers in order to establish USB connectivity with the adb and fastboot utilities.

There are several options for doing so and I'll list them in the order in which I've heard folks indicate their success:

1. PDAnet drivers



If prompted, specify "Samsung" as your device manufacturer; you can also un-install PdaNet itself afterwards, but leave the USB drivers intalled.

2. ADB/FB Driver Naked Samsung Driver 1.7 [ADB/FB Driver] Naked Samsung Driver 1.7 - xda-developers

This driver worked very well for me on my Windows 7 Professional (64-bit) system. Here are some detailed notes that I took when I installed this driver on my system (click the "Show" button below to expand the details):
- download the Naked Samsung 1.7.zip driver referenced above

- extract that files contents to a folder like Naked Samsung 1.7

- first, put your phone into fastboot / bootloader mode by powering-down your phone and restarting it by pressing and holding the volume-up AND volume-down AND the power buttons UNTIL you see the little green Android laying on his back with door on his chest open (you'll also see "Start" in big, green text at the top and "FASTBOOT MODE" in very small red text just below the Android

- connect your phone to your Windows PC via the USB cable

- fire-up your Device Manager:


  • Windows Start button
  • Control Panel
  • Hardware and Sound
  • select Device Manager from under the Devices and Printers section

- identify the Other devices section

- right click the Galaxy entry and select Uninstall

- right click the Galaxy entry and select Update Driver Software...

- select Browse my computer for driver software

- use the Browse... button and navigate to the folder where you extracted the Naked Samsung 1.7.zip file (make sure the Include subfolders checkbox is checked)

- browse to that folder name and click the OK button

- you'll be returned to the Update Driver Software - Galaxy screen; click the Next button

- you might see a red-tinted Windows Security warning saying "Windows can't verify the publisher of this driver software";

- that's okay, click the Install this driver software anyway section

- the driver software will then be installed

- after installation, you should see the window is now titled: Update Driver Software - SAMSUNG Android ADB Interface and it will say "Windows has successfully updated your driver software", etc.

- press the Close button

- notice the the yellow warning icon is now gone and you now have a new SAMSUNG Android Phone section in the Device Manager window and a SAMSUNG Android ADB Interface entry underneath it

- you should now be able to communicate with your device with adb or fastboot (when in the appropriate mode for each)
3. Other drivers



Still having USB connectivity issues after having tried the drivers above? Try a different USB port on your computer and/or a different USB cable (sometimes its NOT the software ;)).
 
Upvote 0
.
The adb (Android debug bridge) and fastboot are two utilities that are usually involved in rooting operations for the Samsung Galaxy Nexus (as well as other Android devices, of course).

The adb utility used to be pretty easy to install because it came in the base Android SDK installation. Google recently changed this to require that the adb utility be installed in a separate, secondary step (i.e., the platform-tools installation).

The fastboot utility also used to be pre-packaged with the Android SDK, but it hasn't been included with it for quite some time.

You can follow this guide ADB Guide that will help you install the Android SDK for the purposes of acquiring the adb utility.

Additionally, there's middle section in that thread, labeled "Mini-SDK", that references a downloadable file, sdk-tools.zip, that contains versions of the adb and fastboot tools for Microsoft Windows, Mac, and Linux and how to extract these files a folder on your PC.
 
  • Like
Reactions: pngwolffman
Upvote 0
.
*** Warning ***
Unlocking your bootloader will completely wipe your device's internal "SD card", so backup what you need / want to beforehand.

*** Please Note ***
The first reboot after you've unlocked your bootloader may take about four or five minutes to complete. So, please be patient and do not pull your battery...let the boot complete (you'll see two cycles of the boot animation).

The reason for this is that you've just wiped your device, including the dalvik-cache. This dalvik-cache area needs to be rebuilt during that first reboot and that is what accounts for much of the boot time.

If you do pull the battery before this first reboot completes, just re-lock and unlock the bootloader again.

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

Here's the "TL;DR" (too-long, didn't read) version for those that don't have USB connectivity issues and already know how to use fastboot:

Code:
fastboot devices         (verify fastboot connectivity)
fastboot oem unlock      (unlock the device)
-----------------------

And here are the full, detailed instructions (click the "Show" button below):
A. if you already have the Android SDK installed with both the adb and fastboot utilities, go ahead and skip to step B.

If you don't have both adb and fastboot installed anywhere, it might be easiest to download and extract the sdk-tools.zip file referenced in the "Mini-SDK" section of this thread ADB Guide to a folder on your PC of your choosing (take note of this folder/directory's name).

B. turn off (power down) your device

C. connect the USB cable between the phone and your PC if you haven't already

D. on your PC, start-up a terminal session (Windows Command Prompt for Windows; Terminal for Mac or Linux) and navigate to the directory/folder where the adb and fastboot utilities are located:

+ for Windows, you need to start-up a Windows Command Prompt (DOS window) and type the following (for example, assuming that your adb / fastboot files are in the c:\sdk-tools folder):

Code:
cd c:\sdk-tools

+ for Mac/Linux, start-up a Terminal session and type the following (for example, assuming that your adb / fastboot files are in the sdk-tools folder):

Code:
[B]cd sdk-tools[/b]

E. next, boot your phone into fastboot mode (press and hold both the volume-UP and volume-DOWN buttons and then press the power button)

F. if you are using Windows, install the appropriate Samsung USB drivers

http://androidforums.com/galaxy-nex...construction-check-back-soon.html#post3711706

G. let's verify that fastboot can "see" your device

note: for simplicity's sake, I'm using the generic "fastboot" command name here; your fastboot utility might actually be named:

+ for Windows: fastboot.exe or fastboot-windows.exe
+ for Linux: fastboot or fastboot-linux
+ for Mac: fastboot for fastboot-mac

- from your PC, enter the following to verify that the fastboot utility can see your phone:

For MS/Windows:
Code:
[B]fastboot devices[/B]        (list connected devices)

For Mac/Linux:
Code:
[B]./fastboot devices[/B]        (list connected devices)

- you should see something similar to this:
Code:
sdk-tools> [B]fastboot devices[/B]
<device serial #>   fastboot

J. next, you'll unlock the bootloader

*** Warning *** the next command (fastboot oem unlock) will completely wipe your device's internal "SD card"), so backup what you need / want to beforehand

Also, please note that after you issue the unlock command, you will be asked, on your phone, to acknowledge that you want the bootloader to be unlocked and that you understand that doing so will void your warranty. Use your volume rocker/keys to select the confirmation and press the power button to actually confirm.

For MS/Windows:
Code:
[B]fastboot oem unlock[/B]            (unlock the bootloader)

For Mac/Linux:
Code:
[B]./fastboot oem unlock[/B]            (unlock the bootloader)

J. That's it, your bootloader should now be unlocked and you are ready for your next step. You phone should still be in fastboot mode at this point.

If you simply wanted to unlock the bootloader and now want to reboot your phone, you can issue a "fastboot reboot" (for Windows) or "./fastboot reboot" (for Mac/Linux) to reboot the device normally (note/warning: since unlocking the bootloader does a factory reset, your next reboot after unlocking will take about five minutes to complete--so be patient and wait for the boot animation to finish-up).

If you are not ready to reboot, but need to do other fastboot-related operations, then your phone is still in fastboot mode and ready for you.

In addition to my notes / instructions above, here are some other threads that might prove helpful to you:


 
Last edited:
Upvote 0
.
Here are the instructions for re-locking your bootloader, which you'll usually want to do if you need to return your phone for a warranty claim.

Note / FYI: re-locking the bootloader does NOT wipe your device (unlocking does, however).

Here's the "TL;DR" (too-long, didn't read) version for those that don't have USB connectivity issues and already know how to use fastboot:

Code:
[COLOR="Purple"][B]fastboot devices[/B][/COLOR]         (verify fastboot connectivity)
[COLOR="purple"][B]fastboot oem lock[/B][/COLOR]        (re-lock the device)
-----------------------

And here are the full, detailed instructions (click the "Show" button below):
A. if you already have the Android SDK installed with both the adb and fastboot utilities, go ahead and skip to step B.

If you don't have both adb and fastboot installed anywhere, it might be easiest to download and extract the sdk-tools.zip file referenced in the "Mini-SDK" section of this thread ADB Guide to a folder on your PC of your choosing (take note of this folder/directory's name).

B. turn off (power down) your device

C. connect the USB cable between the phone and your PC if you haven't already

D. on your PC, start-up a terminal session (Windows Command Prompt for Windows; Terminal for Mac or Linux) and navigate to the directory/folder where the adb and fastboot utilities are located:

+ for Windows, you need to start-up a Windows Command Prompt (DOS window) and type the following (for example, assuming that your adb / fastboot files are in the c:\sdk-tools folder):

Code:
[B][COLOR="purple"]cd c:\sdk-tools[/COLOR][/B]

+ for Mac/Linux, start-up a Terminal session and type the following (for example, assuming that your adb / fastboot files are in the sdk-tools folder):

Code:
[B][COLOR="Purple"]cd sdk-tools[/COLOR][/B]

E. next, boot your phone into fastboot mode (press and hold both the volume-UP and volume-DOWN buttons and then press the power button)

F. if you are using Windows, install the appropriate Samsung USB drivers

http://androidforums.com/galaxy-nexus-all-things-root/470831-big-how-thread-under-construction-check-back-soon.html#post3711706

G. let's verify that fastboot can "see" your device

note: for simplicity's sake, I'm using the generic "fastboot" command name here; your fastboot utility might actually be named:

+ for Windows: fastboot.exe or fastboot-windows.exe
+ for Linux: fastboot or fastboot-linux
+ for Mac: fastboot for fastboot-mac

- from your PC, enter the following to verify that the fastboot utility can see your phone:

For MS/Windows:
Code:
[B][COLOR="Purple"]fastboot devices[/COLOR][/B] [COLOR="blue"]       (list connected devices)[/COLOR]

For Mac/Linux:
Code:
[B][COLOR="Purple"]./fastboot devices[/COLOR][/B] [COLOR="blue"]       (list connected devices)[/COLOR]

- you should see something similar to this:
Code:
sdk-tools> [B][COLOR="purple"]fastboot devices[/COLOR][/B]
[COLOR="Blue"]<device serial #>   fastboot[/COLOR]

J. next, you'll re-lock the bootloader

For MS/Windows:
Code:
[B][COLOR="Purple"]fastboot oem lock[/COLOR][/B]            [COLOR="blue"](re-lock the bootloader)[/COLOR]

For Mac/Linux:
Code:
[B][COLOR="Purple"]./fastboot oem lock[/COLOR][/B]            [COLOR="blue"](lock the bootloader)[/COLOR]

J. That's it, your bootloader should now be re-locked and you are ready for your next step. You phone should still be in fastboot mode at this point.

If you simply wanted to re-lock the bootloader and now want to reboot your phone, you can issue a "fastboot reboot" (for Windows) or "./fastboot reboot" (for Mac/Linux) to reboot the device normally.

If you are not ready to reboot, but need to do other fastboot-related operations, then your phone is still in fastboot mode and ready for you.
 
Upvote 0
.
Here is the rooting guide for the GSM/HSPA+ version of the Galaxy Nexus:

.........[HOW TO] Root the GSM/HSPA+ Samsung Galaxy Nexus

I would suggest using the ClockworkMod rooting method (its the same for both versions of the phones) and is pretty straightforward.

1- Download ClockworkMod Recovery for the Galaxy Nexus

.........Original Clockwork Recovery

................-- or --

.........Clockwork Recovery Touch

2- Place that file in your platform-tools folder (same place as your adb.exe).

3- Download the root binaries (su.zip): Superuser

Note: some users who have upgraded to Android 4.0.4 have reported that the above su.zip from the clockworkmod site does not give them root. You can use this file: View attachment su.zip (from su.zip - File Shared from Box - Free Online File Storage) instead which IS reported to work).

4- Place that file in your SDK's platform-tools folder (same place as adb.exe)

5- Open a command prompt from within your platform-tools folder and type the following:

.........adb push su.zip /sdcard/

6- Then reboot into the bootloader:

.........adb reboot bootloader

7- When the boot menu loads, flash the new recovery image:

.........If you're going to use the "Original Clockwork Recovery", then

..............fastboot flash recovery recovery-clockwork-5.5.0.4-maguro.img

.........If you're going to use the "ClockworkMod Recovery touch screen version", then

..............fastboot flash recovery recovery-clockwork-touch-5.8.0.2-maguro.img

8- When that finishes, use the volume keys to highlight
 
Upvote 0
.
This post will discuss how to return your phone back to stock, which will un-root it.

That is in contrast to just removing the root components (su binary, Superuser.apk, custom recovery, possibly busybox, other root apps, etc.) from your device. You can just remove the root components, but that would be a manual process and is not what most folks want or talk about when they say "un-rooting".

Here's a quick (un-tested) list of what I would do if I simply wanted to "un-root" and not reflash a set of stock images (note: again, this is not a true substitute for returning your phone back to stock and re-locking the bootloader):
  • un-freeze / thaw any apps you've previously frozen
  • optional: uninstall your obvious root apps (Titanium backup, Root Explorer, etc.)
  • start up an on-phone Terminal session or an adb shell
  • get root access while in the shell/terminal with the "su" command (your prompt will change from "$" to "#")
  • remove your busybox binary if installed (its probably in /system/bin/busybox or /system/xbin/busybox)
  • remove your Superuser.apk (should be in /system/app/Superuser.apk or /system/app/SuperUser.apk)
  • remove your su binary (should be in /system/app/su and/or /system/xbin/su)
  • note: once you exit your Terminal/shell session and reboot your device, you should no longer have root access
  • optional: re-flash the stock recovery over any custom recovery you have installed

This is just an outline...there's quite a few combinations of having root-related components on your device--it really just depends on what you have done and install for what you'd need to undo / uninstall. This is not a true substitute for returning your phone back to stock and re-locking the bootloader.
The main difficulty in documenting a return to stock procedure is that the stock images / packages are device and version dependent and specific and will change from release to release.

You need to know and be aware of the differences in how the stock image files are named:


  • The other GSM/HSPA+ version of the Galaxy Nexus is also often referred to as "yakju" or "maguro".

Here's an outline of the steps you'd need to take (click the "Show" button below to expand the details):
  • backup any files from your internal "SD card" up to your PC

  • download the proper stock image file (current name format: <model>-<version>-factory-<hex code>.tgz file) to your PC

    All current stock images (for various O/S versions) can be found here:

    Factory Images for Nexus Devices - Google Support for Nexus Phones and Flagship Devices - Google Code

    It is highly suggested that you double-check the MD5 or SHA1 checksums after downloading any of these large files (you wouldn't want to flash a bad file and end-up with a bricked device, would you?).

  • extract the contents of the stock image file to a working folder; there will be a subfolder/directory created that should contain files similarly named like the following:

    • bootloader-<code name>-primekk15.img
    • flash-all.sh
    • image-<model>-icl53f.zip
    • radio-<code name>-<version>.img

  • note: you'll need to use your fastboot command, so if you don't have the directory where your fastboot utility is in your PATH environment variable, then you might need/want to copy the fastboot utility to the same directory where the above files have been extracted

  • put your phone into fastboot / bootloader mode

  • connect your phone to your PC via the USB cable (I recommend using a USB 2.0 port--I had issues during several sessions using a USB 3.0 port)

  • view the contents of the flash-all.sh script (this will be the template for the commands you'll enter)

  • start-up a terminal/command session (i.e., Windows Command Prompt for MS/Windows, or a Terminal session for Mac/Linux)

  • cd (change directory) to the folder where the subfolder where the flash-all.sh file is

  • now, carefully copy and paste the fastboot commands from the flash-all.sh script (the name of your particular fastboot command may differ based on the type of PC you are running on (i.e., it might be "fastboot-windows.exe" for MS/Windows or "./fastboot-mac" for Mac or "./fastboot-linux" for Linux)

  • take a little break (five seconds) or so between each fastboot command

  • note: some of the commands will take a minute or two to finish...be patient

  • after the last command (fastboot -w update...) completes, your phone will reboot back into Android and you should be completely back to stock (note: that reboot might take 4 or 5 minutes--be patient and give it some time)

  • if you are returning your device for warranty purposes, you might want to re-lock your bootloader (return to fastboot mode and type "fastboot oem lock")

  • note: here's the sample output of the when I did this for my phone (note: your specific commands may be different depending on which phone you have and the version of the Android stock image files):
    c:\gnex\mysid-icl53f>fastboot flash bootloader bootloader-toro-primekk15.img
    sending 'bootloader' (2308 KB)... OKAY [ 0.297s]
    writing 'bootloader'... OKAY [ 0.283s]
    finished. total time: 0.581s

    c:\gnex\mysid-icl53f>fastboot reboot-bootloader
    rebooting into bootloader... OKAY [ 0.006s]
    finished. total time: 0.006s

    c:\gnex\mysid-icl53f>fastboot flash radio radio-toro-i515.ek02.img
    sending 'radio' (10496 KB)... OKAY [ 1.324s]
    writing 'radio'... OKAY [ 1.226s]
    finished. total time: 2.551s

    c:\gnex\mysid-icl53f>fastboot reboot-bootloader
    rebooting into bootloader... OKAY [ 0.006s]
    finished. total time: 0.007s

    c:\gnex\mysid-icl53f>fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
    sending 'radio-cdma' (3713 KB)... OKAY [ 0.474s]
    writing 'radio-cdma'... OKAY [ 93.264s]
    finished. total time: 93.739s

    c:\gnex\mysid-icl53f>fastboot reboot-bootloader
    rebooting into bootloader... OKAY [ 0.007s]
    finished. total time: 0.008s

    c:\gnex\mysid-icl53f>fastboot -w update image-mysid-icl53f.zip
    archive does not contain 'boot.sig' (this message is okay--no worries)
    archive does not contain 'recovery.sig' (this message is okay--no worries)
    archive does not contain 'system.sig' (this message is okay--no worries)
    --------------------------------------------
    Bootloader Version...: PRIMEKK15
    Baseband Version.....: I515.EK02
    Serial Number........: xxxxxxxxxxxxxxxxxxxxx
    --------------------------------------------
    checking product... OKAY [ 0.007s]
    checking version-bootloader... OKAY [ 0.007s]
    checking version-baseband... OKAY [ 0.007s]
    checking version-cdma... OKAY [ 0.007s]
    sending 'boot' (4074 KB)... OKAY [ 0.517s]
    writing 'boot'... OKAY [ 0.272s]
    sending 'recovery' (4406 KB)... OKAY [ 0.563s]
    writing 'recovery'... OKAY [ 0.327s]
    sending 'system' (325583 KB)... OKAY [ 40.796s]
    writing 'system'... OKAY [ 31.954s]
    erasing 'userdata'... OKAY [ 5.934s]
    erasing 'cache'... OKAY [ 0.186s]
    rebooting...
    finished. total time: 80.611s

    # note: here's the optional command for re-locking your bootloader if you are returning your phone for a warranty claim (since the previous command will automatically reboot your phone, you'll need to return/reboot back into fastboot mode first in order to re-lock your bootloader):

    c:\gnex\mysid-icl53f>fastboot oem lock
    ... OKAY [ 0.100s]
    finished. total time: 0.100s
Here are the current contents of the GSM/HSPA+ flash-all.sh script for ICS 4.0.2:
Code:
#!/bin/sh

# Copyright (C) 2011 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
[COLOR="blue"]fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-yakju-icl53f.zip[/COLOR]
As you can see from the different and specific filename references between the two, its very important that you use the flash-all.sh script as your reference when flashing back to stock.
 
Upvote 0
.
To install Koushik Dutta's ClockworkMod custom recovery for the Samsung Galaxy Nexus, you'll need to have already unlocked your bootloader.

There are two (*) ways to install ClockworkMod custom recovery:

1. Via the Koush's ROM Manager app
  • download and install the ROM Manager app from the Market
  • select "Flash ClockworkMod Recovery" from the main menu
  • when prompted to "Confirm Phone Model", select the "GSM"" or models of the Galaxy Nexus from other carriers
  • ROM Manager will then ask for root right (if you haven't already granted it) and then ClockworkMod will be flashed
2. Manually by flashing via the fastboot utility while in fastboot mode
Overview


  • download the appropriate GSM CWM .img file for your particular device
  • don't forget to verify the MD5 checksum of the download before you flash it!
  • put your phone into fastboot mode
  • flash the CWM .img file via fastboot


Instructions

A. unlock your bootloader (see the Unlocking The Bootloader section in the first post (#1) above)

B. download the version of ClockworkMod appropriate / specific to your carrier:



C. place the selected ClockworkMod recovery .img file in the directory with your fastboot and adb utilities

D. make sure you phone is connected with the USB cable to your PC

E. next, boot your phone into fastboot mode (press and hold both the volume-UP and volume-DOWN buttons and then press the power button)

F. start-up a command prompt (Windows) or Terminal (Mac / Linux) session as outlined in the Unlocking The Bootloader section above and change to the folder / directory where your fastboot utility, adb utility, su.zip, and selected recovery .img file are located

Note for Windows users: we will be using both the adb and the fastboot utility below, so you'll need to make sure you have USB drivers installed that will recognize your device while in both modes. The [ADB/FB Driver] Naked Samsung Driver 1.7 - xda-developers works very well and there are other USB driver options listed at the bottom of the first post above.

G. okay, now we will flash (install) the selected ClockworkMod custom recovery image to your phone's recovery partition:

Code:
[B]For MS/Windows[/B]:

- command for [COLOR="Blue"][B]GSM [/B][/COLOR]recovery:

[COLOR="purple"]fastboot [B]flash recovery[/B] recovery-clockwork-5.5.0.2-maguro.img[/COLOR]

[B]For Mac/Linux[/B]:

- command for [COLOR="Blue"][B]GSM [/B][/COLOR]recovery:

[COLOR="purple"]./fastboot [B]flash recovery[/B] recovery-clockwork-5.5.0.2-maguro.img[/COLOR]

- after you've flashed the recovery, use the [B]volume keys[/B] to change the 
green "[COLOR="Green"]Start[/COLOR]" arrow/banner to the red "[COLOR="Red"]Recovery mode[/COLOR]" one

- select that mode by pressing the [B]power button[/B]--that will actually 
launch the new custom recovery

* * * * * * * * *

If you wish to simply soft-boot (load ClockworkMod into your phone's memory from your PC and boot it without flashing / over-writing the currently installed (presumably stock) recovery, you can use this process:
Code:
For MS/Windows:

- command for [COLOR="Blue"][B]GSM [/B][/COLOR]recovery:

[COLOR="purple"]fastboot [B]boot[/B] recovery-clockwork-5.5.0.2-maguro.img[/COLOR]

For Mac/Linux:

- command for [COLOR="Blue"][B]GSM [/B][/COLOR]recovery:

[COLOR="purple"]./fastboot [B]boot[/B] recovery-clockwork-5.5.0.2-maguro.img[/COLOR]

- your phone should now boot into ClockworkMod custom recovery
H. optionally root your phone while you're here
- download the su.zip flashable (via CWM) root package and place in same folder with the adb utility

- once ClockworkMod custom recovery is booted-up and showing on your screen, you'll need to push (send) the su.zip (flashable root package) to your phone's internal memory ("SD card") via the adb utility:

Code:
[B]For MS/Windows[/B]:

[COLOR="purple"]adb push su.zip /sdcard/[/COLOR]       [COLOR="Red"](notice the trailing forward slash)[/COLOR]

-- or --

[COLOR="purple"]adb push su.zip /data/media/su.zip[/COLOR]

[COLOR="Blue"](I included the second version of this command because the first didn't work 
for me at times (CWM wasn't always "seeing" the file I just pushed))[/COLOR]

[B]For Mac/Linux[/B]:

[COLOR="purple"]./adb push su.zip /sdcard/[/COLOR]      [COLOR="Red"](notice the trailing forward slash)[/COLOR]

-- or --

[COLOR="purple"]./adb push su.zip /data/media/su.zip[/COLOR]

[COLOR="Blue"](I included the second version of this command because the first didn't work 
for me at times (CWM wasn't always "seeing" the file I just pushed))[/COLOR]

###

here's what the output looks like on my Windows PC:

c:gnexsdk-tools> [B]adb push su.zip /sdcard/[/B]
[COLOR="blue"]4346 KB/s (1126078 bytes in 0.253s)[/COLOR]

- next, we'll need to navigate in ClockworkMod to flash the su.zip root package

navigation tips:


  • use the volume key / rocker to navigate up and down in the menus
  • use the power button to select an entry
  • note: many have reported the volume rocker can be a little sensitive (i.e., it will move more than one entry when pressed)

what to do:

- select the "install zip from sdcard" entry

- select the "choose zip from sdcard" entry

- navigate to the bottom of the displayed menu options, you should see your "su.zip" entry there; select it

- after you flash the su.zip file, navigate to the "*****Go Back*****" entry; select it to return to the prior menu screen

- navigate back again to the first / main screen

- select the "reboot system now" entry

- when you phone finishes rebooting, you should now have root :)
* -- there's actually a third way by using the flash_image utility (which is similar to the fastboot command, but you don't have to be in fastboot mode); this is what ROM Manager would be using to flash ClockworkMod


Flashed custom recovery won't "stick"?

Do this:

- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)

- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak

(note: you could delete it, but renaming is much safer since its easily reversible)

- here are notes for doing this using ES File Explorer (free in the Market):
- download / install / launch ES File Explorer

- press the menu icon (bottom right)

- select Settings

- select Home Directory

- change your Home Directory to "/" (without the quotes, of course)

- return to the Settings screen

- scroll down to the bottom of the screen

- check the "Root Explorer" box in the Root Settings area (you'll get the Superuser whitelist app's pop-up asking for permission for this app)

- when you want to mount / and /system as writeable, check the "Mount File System" box under the "Root Explorer" checkbox

- hit the back button to return to the file navigation

- press the "Up" directory icon in the toolbar at the top of the screen--that should take you to the / (root) filesystem

- from there, you should be able to navigate to the /system filesystem and look for the recovery-from-boot.p file

- long-press the recovery-from-boot.p file and select "Rename" (I suggested adding a suffix like "-bak" or "-old", etc.)
- you could also do this manually in an adb shell or on-phone Terminal session:

+ mv /system/recovery-from-boot.p /system/recovery-from-boot.p-bak

+ after you've renamed the file, you might have to re-flash your CWM if it had been missing previously (which led you here)


Mini-FAQ / Tips / Notes

Q: what's a custom recovery good for?

A: several cool things:


  • making and restoring Nandroid (full phone) backups
  • flashing / installing custom ROMs and update.zip type files
  • wiping / clearing various phone partitions, battery stats
  • fix permissions

Q: how do you navigate the menus in ClockworkMod for the GNex?

A: navigation tips:


  • use the volume key / rocker to navigate up and down in the menus
  • use the power button to select an entry
  • note: many have reported the volume rocker can be a little sensitive (i.e., it will move more than one entry when pressed)

Q: Anyway to change the number of "No" options on the action/confirm page?

A: Yes! Cool tip (thanks to XDA's zyonee):

Create a simple (can be empty) file named /sdcard/clockworkmod/.one_confirm

Here's one example of how to do this: adb shell touch /sdcard/clockworkmod/.one_confirm

Q: can I flash the stock recovery back if I no longer want a custom recovery?

A: Yes. If you return completely back to stock, this will happen when you do the final "flash -w update..." command of that process. You can also just flash the recovery.img file taken from your appropriate device's stock / factory image set (i.e., from inside the image-<model>-<version>.zip file).

Additionally, in lieu of extracting the recovery.img file, you could download them from Koush's site below, but I would caution you that these files do not match (in size) the files you would extract from the stock images--presumably because they were created with a saveprt2sd or similar partition dump command):



Q: do you have to install a custom recovery to become rooted?

A: no, but you can root fairly easily via custom recovery by flashing a .zip file that installs root (su / Superuser.apk) for you

Q: how do you put your phone in fastboot / bootloader mode?

A: from a powered-off state, press (and hold!) volume-UP and volume-DOWN and power (keep holding all three until you see the little green Android laying down with his chest plate open)

Q: how do I get into recovery (custom or stock)?

A: four ways (so far):


  • use the (free) Market app Quick Boot (Reboot) and select "Recovery"

  • put your phone in fastboot / bootloader mode (see above) and use the volume keys to toggle the mode (displayed at the top of the screen) to "Recovery" and select that mode by pressing the power button

  • via an adb reboot recovery command

  • via the ROM Manager app's "Reboot into Recovery" option on the main menu
 
  • Like
Reactions: pngwolffman
Upvote 0
.
Why would you need to restore the stock recovery? To be able to successfully install an over-the-air (OTA) Android update from Google or your carrier.

Note: if, when you installed ClockworkMod custom recovery, you renamed your /system/recovery-from-boot.p file to make ClockworkMod "stick", you should be able to rename it back to its original name and then reboot to cause the stock recovery to be automatically re-flashed for you.

Many of the details that you would need to follow are already covered in the How to restore stock recovery post (please reference that post for additional details). However, you really only have one file to enter a fastboot flash command for to return your recovery back to stock. Here's an overview:

- acquire the stock recovery image, by either:


  • download the appropriate 4.0.2 stock recovery images for each device:

    View attachment stock-GSM-HSPA-402-recovery-image.zip (contains recovery.img file)

  • - download the proper stock image file (<model>-<version>-factory-<hex code>.tgz) for your partition device to your PC

    - extract the stock image file to a working directory

    - extract the contents of the image-<model>-<version>.zip file to a working directory

    - copy the recovery.img file from the extracted image-<model>-<version>.zip file to the directory that contains your fastboot utility (note: we're assuming you already have fastboot USB connectivity between your phone and your PC)

- start-up a terminal/command session (i.e., Windows Command Prompt for MS/Windows, or a Terminal session for Mac/Linux)

- put your phone into fastboot / bootloader mode

- type the following fastboot command to flash the stock recovery:

Code:
[COLOR="blue"][B]fastboot flash recovery recovery.img[/B][/COLOR]
(the name of your particular fastboot command may differ based on the type of PC you are running on (i.e., it might be "fastboot-windows.exe" for MS/Windows or "./fastboot-mac" for Mac or "./fastboot-linux" for Linux)

- that's it...you should now have your stock recovery again

- to reboot your phone, you can type fastboot reboot to restart Android
 
Upvote 0
.
- be sure to read the ROM developer's compatibility and installation instructions / details that you may need to consider:


  • kernel compatibility
  • wipes that are required
  • additional packages (like Google apps (often referred to as "gapps")) that will also need to be flashed
  • note: some additional packages / mods require that you are using it with a deodexed ROM

- download the ROM's .zip package to your PC or phone (do NOT unzip it!)

- be sure to verify the MD5 checksum of the .zip file you will be flashing (http://androidforums.com/faqs/443074-md5-verification.html); you certainly don't want to be flashing a bad ROM

- if you downloaded the .zip file to your PC, copy / place the .zip file to the root / top-level directory or folder of your phone (the top-level folder should show-up as "Internal Storage" under the "Galaxy Nexus" drive when you've connected your phone to your PC via the USB cable

- boot your phone into ClockworkMod custom recovery

- if the ROM dev's thread indicates you need to perform any wipes, do those at this point


  • note: a "wipe data/factory reset" will delete the contents of the /data partition, but will leave the /data/media folder (subdirectory) where the /sdcard (the internal "SD card") is symbolically linked to intact (i.e, your "SD card" will not be touched)

- select install zip from sdcard

- next, select choose zip from sdcard

- you'll next be presented with a list of files and folders in the /sdcard mount point, use the volume rocker to scroll to the downloaded .zip file that you wish to flash

- at the Confirm install? / THIS CANNOT BE UNDONE. screen, scroll down to the Yes - Install <zip filename> entry and press the power button to select and start the flash

- pay attention to the results of the flashing status to see if any errors / issuses were encountered

- when the flashing has completed, scroll to the +++++Go Back+++++ option at each screen until you return to the main screen

- if the ROM dev's thread indicates you need to install any additional .zip files (like Google apps, etc.), flash those at this point (using the same process as outlined above)

- on the main screen, select the reboot system now option to reboot your phone and see the result of your flashing operation
 
  • Like
Reactions: pngwolffman
Upvote 0
.
- note: for kernels, you need to make sure that the ROM that you will be flashing the kernel for is compatible with the version of Android that is installed (i.e., 4.0.2 kernel goes with a 4.0.2 compatible ROM; 4.0.3 with 4.0.3, etc.)

- note: for kernels, be sure to read the developer's compatibility and installation instructions / details that you may need to consider

- download your kernel or radio .zip package to your PC or phone (do NOT unzip it!)

- be sure to verify the MD5 checksum of the .zip file you will be flashing (see http://androidforums.com/faqs/443074-md5-verification.html); you certainly don't want to be flashing a bad kernel or radio

- if you downloaded the .zip file to your PC, copy / place the .zip file to the root / top-level directory or folder of your phone (the top-level folder should show-up as "Internal Storage" under the "Galaxy Nexus" drive when you've connected your phone to your PC via the USB cable

- boot your phone into ClockworkMod custom recovery

- select install zip from sdcard

- next, select choose zip from sdcard

- you'll next be presented with a list of files and folders in the /sdcard mount point, use the volume rocker to scroll to the downloaded .zip file that you wish to flash

- at the Confirm install? / THIS CANNOT BE UNDONE. screen, scroll down to the Yes - Install <zip filename> entry and press the power button to select and start the flash

- pay attention to the results of the flashing status to see if any errors / issuses were encountered

- when the flashing has completed, scroll to the +++++Go Back+++++ option at each screen until you return to the main screen

- on the main screen, select the reboot system now option to reboot your phone and see the result of your flashing operation
 
  • Like
Reactions: pngwolffman
Upvote 0
..
Q: how to enter into fastboot / bootloader mode?

A: three ways:


  1. from a powered-off state, press (and hold!) volume-UP and volume-DOWN and power (keep holding all three until you see the little green Android laying down with his chest plate open)

  2. if you are already in fastboot / bootloader mode, you can issue the "fastboot reboot-bootloader" command to re-launch

  3. if you are in an adb mode (i.e., USB debugging is enabled while Android is running or you have custom recovery (ClockworkMod) running), you can issue an "adb reboot bootloader" or "adb reboot-bootloader" command to put your phone in fastboot / bootloader mode

----------------------------------------------------------------------------
.
Q: how to enter into recovery (custom or stock)?

A: several ways:


  1. put your phone in fastboot / bootloader mode (see above) and use the volume up/down keys to toggle the mode (displayed at the top of the screen) to "Recovery" and select that mode by pressing the power button

  2. use the (free) Market app Quick Boot (Reboot) and select "Recovery"

  3. via the ROM Manager app's "Reboot into Recovery" option on the main menu

  4. via an adb reboot recovery command (only when you are in adb mode)

  5. many custom rooted ROMs also support a boot-into-recovery option in the same menu that you get when you long-press the power button to shut down
 
  • Like
Reactions: pngwolffman
Upvote 0
Status
Not open for further replies.

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones