Go Back   Android Forums > Android Phones > Samsung Galaxy Nexus > (International / GSM) Galaxy Nexus - All Things Root

Find everything you need for the Galaxy S5 and discuss it in our S5 forum!
Have you seen that OnePlus One's awesome camera?? The forum is over here!

Like Tree1Likes

test: Reply
 
LinkBack Thread Tools
Old November 26th, 2011, 01:48 AM   #1 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default [HOW TO] Root the GSM/HSPA+ Samsung Galaxy Nexus

.
There is no "root exploit" required to root the Samsung Galaxy Nexus since it comes with an unlockable bootloader. So, this means that there is not soon likely to be a 1-click or easy rooting app to run that exploits something in Ice Cream Sandwich in order to root the phone.

Here are the basic steps that need to be done in order to root the GNex:

1. Unlock the bootloader (warning: this does wipe the internal "SD card" portion of your phone)
2. Gain write access to the /system partition
3. Install the root binaries (su / Superuser.apk)

~ ~ ~ note about su.zip for ICS 4.0.4 (when flashing from ClockworkMod) ~ ~ ~

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

~ ~ ~

Unfortunately, the biggest hurdle for folks using Microsoft Windows will be issues relating to getting the proper Samsung USB drivers installed and working properly. Please take note of the several options listed at the bottom of this post. For Mac and Linux users, this is fortunately not an issue.

The second biggest hurdle will be getting the adb and fastboot utilities installed and understanding how to use them.

Note: I did experience some hangs while using the fastboot and adb utilities when my USB cable was plugged-in to a USB 3.0 port; these issues disappeared when I reverted back to a USB 2.0 port.

Quick notes about adb / fastboot:



Your best bet will be to take your time, do your reading and research, and make sure you understand what you are about to do before doing it. Perusing the threads and posts here will go a long way towards letting you see what other issues folks have encountered.

Unlocking The Bootloader

*** Warning *** unlocking your bootloader will completely wipe your device's internal "SD card", so backup what you need / want to beforehand.

All of the rooting methods require that you have an unlocked bootloader. I've included this section here first and made reference to it in the root methods below it.

Code:
Note: be aware that the first reboot after you've unlocked the
bootloader (via fastboot oem unlock) can take up to five (5) 
minutes to finish; you'll see two cycles of the boot animation 
before it finishes.

Since unlocking the bootloader does a factory reset, the dalvik-cache, etc. 
needs to be rebuilt upon reboot (this takes times); just be patient and do not 
pull the battery...let the reboot complete.

If you do/did get antsy and pulled the battery before the boot completed, 
just relock (fastboot oem lock) and unlock (fastboot oem lock) the device 
and then reboot.
Click the Show button below for in-line instructions to unlock the bootloader:




- = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = -

Wug's Galaxy Nexus Root Toolkit

Pros:

-- guides you through all the tasks
-- works for both GSM and LTE versions of the device

Cons: none, really

AF link and discussion:

Here you go! One Step Unlock/Root or ReLock/Unroot!

Direct link:

Wug's Galaxy Nexus Root Toolkit

- = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = -

ClockworkMod Method (courtesy of Koushik Dutta)

Pros:

-- simplest and fastest from what I've found
-- works for both GSM and LTE versions of the device
-- does not require a special (insecured) boot.img file

Cons: requires both adb and fastboot USB connectivity




- = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = -

Superboot Method (courtesy of Paul O'Brien of MoDaCo)

Pros:

-- simpler method for rooting (installs root binaries for you)
-- works for both GSM and LTE versions of the device

Cons: you'll still need to use fastboot to unlock your bootloader (if you haven't already)




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

(Slightly) Easier Manual Method (for now, GSM devices only!)

Pros: like the manual method, but doesn't require that you install Android SDK for adb / fastboot
Cons: still requires that you enter fastboot and adb commands




- = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = -

-=< Root Warning / Disclaimer >=-




-=< Credits (Peter Alfonso / Paul O'Brien / XDA's davioxx) >=-




-=< Windows USB drivers >=-
(alternative versions contributed / suggested by various people):




-------------------------------------------
Cheers and thanks!

scary alien is online now  
Last edited by scary alien; May 14th, 2012 at 01:36 PM. Reason: update w/new su.zip package
Reply With Quote
The Following 51 Users Say Thank You to scary alien For This Useful Post:
2010 ZR1 (December 17th, 2011), asheehanjr (June 29th, 2012), bevardimus (January 2nd, 2012), BIGPHILWA (December 17th, 2011), brister (December 29th, 2011), cbeng (December 21st, 2011), CheeseJam (December 18th, 2011), chriv (December 20th, 2011), cusjs (December 16th, 2011), danaj (September 27th, 2012), darkcyber (December 20th, 2011), El Presidente (December 3rd, 2011), elektroshok (January 5th, 2012), foo (December 16th, 2011), Frisco (December 16th, 2011), GalaxyNexus (December 20th, 2011), haleybob1228 (December 22nd, 2011), ItsASamsung (December 13th, 2011), jaydotelloh (December 15th, 2011), jbdan (December 15th, 2011), jrennie (January 8th, 2012), jseyfert3 (December 17th, 2011), kbgeoff (December 16th, 2011), kogvos (December 30th, 2011), Laxstar785 (December 16th, 2011), Lunacy (January 31st, 2012), meisterle (November 29th, 2011), MetalMessiah78 (January 19th, 2012), metlcat (December 15th, 2011), mfecik (December 18th, 2011), minibee041 (January 10th, 2012), misterfish (December 23rd, 2011), NCTurner (January 30th, 2012), nj02vette (December 4th, 2011), RaptorHawk (May 18th, 2012), rexdog1888 (November 26th, 2011), rowntreerob (May 14th, 2012), Rrrracer (November 28th, 2011), scotty85 (December 15th, 2011), sgrinavi (December 15th, 2011), Snazzy (January 18th, 2012), soy.lor.n (December 16th, 2011), Stigy (November 28th, 2011), trophynuts (December 6th, 2011), urs74 (January 18th, 2012), VeryEvilAsh (December 21st, 2011), vijaya1028 (August 17th, 2012), Wolfedude88 (December 7th, 2011), WormDoes (December 5th, 2011), Yeahha (December 16th, 2011)
sponsored links
Old November 26th, 2011, 11:19 AM   #2 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default [HOW TO] Install ClockworkMod Custom Recovery

-
To install Koushik Dutta's ClockworkMod custom recovery for the Samsung Galaxy Nexus, you'll need to:

  • unlock your bootloader
  • download the appropriate (GSM or LTE) 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
  • enjoy your new custom recovery


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:
For MS/Windows:

- command for Verizon / VZW CDMA recovery:

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

- command for GSM recovery:

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

For Mac/Linux:

- command for Verizon / VZW CDMA recovery:

./fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img

- command for GSM recovery:

./fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img

- after you've flashed the recovery, use the volume keys to change the 
green "Start" arrow/banner to the red "Recovery mode" one

- select that mode by pressing the power button--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:



H. optionally root your phone while you're here





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)

- 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


Mini-FAQ

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
- use the power button to select an entry

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

A: Yes, for the VZE LTE GNex, you can flash this stock recovery image

(I'll dig-up a link for the GSM stock recovery image and post it here, too)

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

A: no, but you can root via custom recovery (see above and in the first post above)

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: three ways (so far):

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

  • 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
scary alien is online now  
Last edited by scary alien; December 19th, 2011 at 11:06 PM. Reason: finished updating how-to instructions
Reply With Quote
The Following 5 Users Say Thank You to scary alien For This Useful Post:
brister (December 29th, 2011), darkcyber (December 27th, 2011), RaptorHawk (May 18th, 2012), Rrrracer (December 16th, 2011), trophynuts (December 6th, 2011)
Old November 28th, 2011, 07:24 AM   #3 (permalink)
Senior Member
 
EddyOS's Avatar
 
Join Date: Apr 2010
Location: Liverpool, Merseyside
Posts: 1,681
 
Device(s): HTC Sensation, HTC Desire
Carrier: Not Provided

Thanks: 9
Thanked 284 Times in 226 Posts
Default

Paul O'Brien's method just has a Windows batch file to do it all for you - it's a lot easier
__________________
HTC Sensation (Z710e)
ROM: 3.32.401.5 EUR (IML74K) | HBOOT: 1.27.0000 S-OFF | Recovery: Clockwork Mod 5.0.2.0 | Radio: 10.58.9035.00U_10.15.9035.02_2 | Kernel: Stock
EddyOS is offline  
Reply With Quote
Old November 28th, 2011, 08:14 AM   #4 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by EddyOS View Post
Paul O'Brien's method just has a Windows batch file to do it all for you - it's a lot easier
Yes, that's the third option above (Superboot).

Some Windows folks might get a little tripped-up if they haven't yet unlocked their bootloaders with fastboot, though (i.e., requiring installing the Samsung USB drivers and getting fastboot installed).

I'm also going to be updating the first (or second) post with how to root by unlocking the bootloader, installing a custom recovery, and flashing an su.zip type file.

Cheers!
scary alien is online now  
Reply With Quote
Old November 28th, 2011, 08:29 AM   #5 (permalink)
Senior Member
 
EddyOS's Avatar
 
Join Date: Apr 2010
Location: Liverpool, Merseyside
Posts: 1,681
 
Device(s): HTC Sensation, HTC Desire
Carrier: Not Provided

Thanks: 9
Thanked 284 Times in 226 Posts
Default

To be honest, if they don't know how to setup adb/fastboot then they shouldn't really be trying to unlock their phone!
EddyOS is offline  
Reply With Quote
The Following 3 Users Say Thank You to EddyOS For This Useful Post:
Caveman419 (December 19th, 2011), scary alien (November 28th, 2011), teddyearp (December 1st, 2011)
Old December 1st, 2011, 10:29 AM   #6 (permalink)
New Member
 
Join Date: Aug 2011
Location: Candia, NH USA
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 3 Times in 3 Posts
brianbreinhold@gmail.com
Default

When you say that 'fastboot devices' will completely wipe your phone does that mean the entire operating system or JUST the applications and setups that I have personally installed and any data that is due to my actions? In otherwords, am I back to a 'fresh' operating system or do i have to re-install the operating system?
Gyannea is offline  
Reply With Quote
The Following User Says Thank You to Gyannea For This Useful Post:
scary alien (December 1st, 2011)
Old December 1st, 2011, 10:43 AM   #7 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by Gyannea View Post
When you say that 'fastboot devices' will completely wipe your phone does that mean the entire operating system or JUST the applications and setups that I have personally installed and any data that is due to my actions? In otherwords, am I back to a 'fresh' operating system or do i have to re-install the operating system?
Oh, apologies here, Gyannea! Definitely my bad and a mistake in where that warning ended-up.

A "fastboot devices" will NOT wipe the device... I added that section after I put the warning about the "fastboot oem unlock" (which WILL wipe your device) and failed to move the warning to the proper place (which I have now down, by the way).

So, just to be clear, the "fastboot devices" is simply to ensure that the fastboot utility can see / communicate with your device.

The "fastboot oem unlock" command will actually wipe the device (I'm guessing that its similar to a factory reset).

You won't have to reinstall the operating system, but I'm pretty sure you'll lose your "setup" (apps and data settings, etc.). This is why you normally do this right after you get your device and before you've done any setup that you would have to re-do as a result of unlocking the bootloader.

Does that make sense?

Sorry again for the misunderstanding .

Cheers!
scary alien is online now  
Last edited by scary alien; December 1st, 2011 at 01:08 PM. Reason: added note that I did fix the OP
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
rexdog1888 (December 3rd, 2011)
Old December 1st, 2011, 02:53 PM   #8 (permalink)
New Member
 
Join Date: Aug 2011
Location: Candia, NH USA
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 3 Times in 3 Posts
brianbreinhold@gmail.com
Default

Okay, thanks. It does. I already did a fastboot oem unlock and I did lose a trivial amount of stuff (one app that I am developing anyways). My real goal is to install hcidump on the phone because the new HDP Bluetooth implementation appears to be having issues at the connection level.
However, when I try push, remount, mount, etc. I get a 'not allowed. If I do an 'su' in the adb shell I get that the command doesn.t exist. I've been sweating with USB drivers and unlocking since yesterday evening ALL to put hcidump in system/xbin!!
Gyannea is offline  
Reply With Quote
Old December 1st, 2011, 03:25 PM   #9 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by Gyannea View Post
Okay, thanks. It does. I already did a fastboot oem unlock and I did lose a trivial amount of stuff (one app that I am developing anyways). My real goal is to install hcidump on the phone because the new HDP Bluetooth implementation appears to be having issues at the connection level.
However, when I try push, remount, mount, etc. I get a 'not allowed. If I do an 'su' in the adb shell I get that the command doesn.t exist. I've been sweating with USB drivers and unlocking since yesterday evening ALL to put hcidump in system/xbin!!
Are you are looking at / using the first, manual method above?

Did you do the "adb root" before the "adb remount"?

Also, after you do the soft-boot (step K) of the unsecured boot image, it only "lasts" for one reboot cycle...i.e., for the purpose of the manual method, its just booting the unsecured boot image so that you'll be able to do the adb commands shown in step N to insert the root binaries (su and Superuser.apk).

You could insert your hcidump binary at the same time / place that you are doing the su/Superuser.apk files--you'll just need to make sure you've done the soft-boot right before trying to connect with adb to push the files.

Does that make sense?

Hope that helps!

Cheers!
scary alien is online now  
Reply With Quote
Old December 1st, 2011, 04:17 PM   #10 (permalink)
New Member
 
Join Date: Aug 2011
Location: Candia, NH USA
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 3 Times in 3 Posts
brianbreinhold@gmail.com
Default

I'm going to do the manual method. This sequence (from the read me file in the boot image and su package you referred to):

fastboot boot boot.img:

the device will reboot and start in unsafe mode where you can enable adb as root usually on production devices this is not possible.
Be sure to enable adb debugging on menu.
Back to command prompt and then

adb root

adb remount

adb push su /system/bin

adb push Superuser.apk /system/app

adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk

my additions:

adb push hcidump /system/xbin
adb push hciconfig /system/xbin
etc.

adb reboot

Just to add to this story was the frustration I was having was finding all the necessary USB drivers to run both adb and fastboot for this phone. On this model, GT-19250, fastboot will not run without a second special driver (the adb driver is the Samsung_USB_Driver_for_Mobile_Phones_v1_4_8_0.exe which seems to be well known). Took me forever to even find out that I needed a second driver for fastboot. If I am permitted (and learn how) I should upload these files to this site so someone else can be spared the agony.
My only concern is that this is a very new phone with ICS on it that I need in order to make an app that used the new HDP Bluetooth....which unfortunately seems to have some holes. I'm just not sure this older stuff wont be 'bricking' this device!

and to top it all off I am very new to Android!
Gyannea is offline  
Last edited by Gyannea; December 6th, 2011 at 05:30 PM. Reason: goof! saw the miss in the original but forgot to add it everywhere
Reply With Quote
sponsored links
Old December 1st, 2011, 04:34 PM   #11 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Yes, that sounds and looks right to me...I carefully cobbled-together the instructions from the XDA page that I referenced above and added some additional notes that I thought would help clarify things.

I wish I had my hands on my VZW Galaxy Nexus...

Are you an app dev? I've got a couple out there on the market...its a fun "hobby", LOL.

Good luck and let me know how it goes .
scary alien is online now  
Reply With Quote
Old December 1st, 2011, 05:35 PM   #12 (permalink)
New Member
 
Join Date: Aug 2011
Location: Candia, NH USA
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 3 Times in 3 Posts
brianbreinhold@gmail.com
Default

It was successful. After 24 hrs of searching for drivers and trying to figure out why things dont work, hcidump and friends are finally loaded on the phone and I have actually used them.

WHOW! How hard it can be to copy one small file.
Gyannea is offline  
Reply With Quote
The Following User Says Thank You to Gyannea For This Useful Post:
scary alien (December 1st, 2011)
Old December 1st, 2011, 05:52 PM   #13 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by Gyannea View Post
It was successful. After 24 hrs of searching for drivers and trying to figure out why things dont work, hcidump and friends are finally loaded on the phone and I have actually used them.

WHOW! How hard it can be to copy one small file.
Glad to hear!

I did a search for the Samsung_USB_Driver_for_Mobile_Phones_v1_4_8_0.exe file you referenced and came up empty...can you link the download / reference place for us?

Cheers and thanks!
scary alien is online now  
Reply With Quote
Old December 1st, 2011, 11:21 PM   #14 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,159
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 681
Thanked 701 Times in 428 Posts
Default

@scary, now I am a total n00b as far as this phone is concerned, but from what I have read about rooting the Nexus S, I am _thinking_ that step J _should_ be sufficient and will give the user a warning on the phone's screen about voiding their warranty and such and (maybe) step K _might_ not be needed since the bootloader is now unlocked?

Total speculation at this point, I doubt I will have one of these in my hands until next year because of finances . . . .

Just checking . . . . .
teddyearp is online now  
Reply With Quote
Old December 2nd, 2011, 08:37 AM   #15 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by teddyearp View Post
@scary, now I am a total n00b as far as this phone is concerned, but from what I have read about rooting the Nexus S, I am _thinking_ that step J _should_ be sufficient and will give the user a warning on the phone's screen about voiding their warranty and such and (maybe) step K _might_ not be needed since the bootloader is now unlocked?

Total speculation at this point, I doubt I will have one of these in my hands until next year because of finances . . . .

Just checking . . . . .
teddyearp,

Well, the bootloader comes locked and you still have to manually unlock it with the "fastboot oem unlock" command. So, the phone is locked but is unlockable.

Does that make sense?

Cheers!
scary alien is online now  
Reply With Quote
Old December 2nd, 2011, 10:57 AM   #16 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,159
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 681
Thanked 701 Times in 428 Posts
Default

Quote:
Originally Posted by scary alien View Post
teddyearp,

Well, the bootloader comes locked and you still have to manually unlock it with the "fastboot oem unlock" command. So, the phone is locked but is unlockable.

Does that make sense?

Cheers!
Oh yes, it makes perfect sense, I'm not quite that much of a noob. I was speculating that all we need to do is fastboot oem unlock and then go right to the moving and chmod of the su binary and Superuser.apk without the boot.img step.
teddyearp is online now  
Reply With Quote
The Following User Says Thank You to teddyearp For This Useful Post:
scary alien (December 2nd, 2011)
Old December 2nd, 2011, 11:49 AM   #17 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by teddyearp View Post
Oh yes, it makes perfect sense, I'm not quite that much of a noob. I was speculating that all we need to do is fastboot oem unlock and then go right to the moving and chmod of the su binary and Superuser.apk without the boot.img step.
Ah, yes...I understand you now--that's kind of what I thought before I started digging around and that's why I started this thread: so that I would be prepared with what I needed to know and figured I'd share it with you guys.

I'm guessing that the unsecured boot.img that we have to soft-boot is somewhat akin to having S-OFF on HTC devices and allows you to remount the other partitions as read/write.

This is all new to me, too...wish I had a device in-hand so I could post screenshots, etc. ...soon....soon .

Cheers!
scary alien is online now  
Reply With Quote
Old December 2nd, 2011, 12:34 PM   #18 (permalink)
Member
 
Penguissimo's Avatar
 
Join Date: Feb 2010
Posts: 272
 
Device(s): Galaxy Nexus (VZW)
Carrier: Not Provided

Thanks: 634
Thanked 94 Times in 63 Posts
Default

Thanks for the great guide, mate! Just one question—is it possible to relock the bootloader and leave no trace of it having ever been unlocked? I know that unlocking the Nexus One left a permanent mark, but I've read that the NS could be relocked...do you know which is true of the GN?
Penguissimo is offline  
Reply With Quote
Old December 2nd, 2011, 12:48 PM   #19 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by Penguissimo View Post
Thanks for the great guide, mate! Just one question—is it possible to relock the bootloader and leave no trace of it having ever been unlocked? I know that unlocking the Nexus One left a permanent mark, but I've read that the NS could be relocked...do you know which is true of the GN?
I did not know that about the Nexus One leaving an unlocking trace...interesting--and I haven't heard anything about this for the GNex, but I'm not sure it matters...the device is being released with the ability for it to be unlocked (and re-locked), so I would think that there wouldn't be any worries involved (unless you tried to make a warranty claim / return with a phone that was clearly still unlocked).

Oh, I'm sure its just a "fastboot oem lock" counterpart to the unlock command to re-lock it (preceded by flashing/restoring the stock image of course).

There's info / threads on XDA and elsewhere about this already for the GSM (maguro) stock boot image, but I don't think we have the VZW stock image yet.
scary alien is online now  
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
Travillion (December 6th, 2011)
Old December 2nd, 2011, 09:24 PM   #20 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,159
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 681
Thanked 701 Times in 428 Posts
Default

I just want to point out a couple more things, if I may. First, I would be wary of using any file that is designed for the GSM version of this phone, i.e. the CWRecovery. In my past experience with other phones there can be just enough differences to make a disaster sometimes occur.

Second, there are a couple of typos here and there. In the OP, in one of the 'code' sections you left out one of the 'r's in Superuser.apk, so those who do come along and just copy/paste those commands will have trouble. Also, in Gyannea's post above where the text was copied from the 'readme.txt' file in the manual .zip file, we are told to adb push su to /system/bin and Superuser.apk to /system/app, but then the chmod 0755 is missing the full path (so I added it in red):
Code:
chmod 0755 /system/bin/su
chmod 0755 /system/app/Superuser.apk
I know this is fixed in the OP, but it's the little things like that that usually trip people up. Plus with the A855 we used to 'mkdir /system/xbin' and put the su and busybox binaries in there, just for kicks.

And speaking of busybox, I think it would be good if we, as this thread matures, include installing that right in the same 'breath', shall we say, as rooting. The following is somewhat shortened, but after pushing su, busybox, and Superuser.apk, we could then just drop to adb shell in one command, do the other chmod commands listed above without 'adb shell' at the beginning and then add this:
Code:
cd /system/xbin (or cd /system/bin)
chmod 0755 busybox
busybox --install .
I know I'm going on too much, but with the A855 we used 'chmod 6755' for su, don't know if this makes that big a difference and finally, in the 'resources' file in the OP, the fastboot file for windows is named pretty much that, "fastboot-windows.exe" so if we issue the command, "fastboot oem unlock" our windows machines will give a "file (or command) not found" error.

OK, I'm done with my dribble, I hope this isn't taken that I am stepping on anyone's toes.

Thanks
teddyearp is online now  
Last edited by teddyearp; December 2nd, 2011 at 09:37 PM.
Reply With Quote
The Following 2 Users Say Thank You to teddyearp For This Useful Post:
scary alien (December 2nd, 2011), Travillion (December 6th, 2011)
sponsored links
Old December 2nd, 2011, 09:42 PM   #21 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

teddyearp,

Hey, great feedback--I appreciate it a lot and appreciate the careful reading.

I fixed the mis-spelling of the Superuser.apk that you pointed-out (thanks!).

I can't (am not allowed) to fix other folk's posts without their permission, so hopefully, Gyannea will see this and make the edits that you mentioned.

Yes, I agree with you that pushing a busybox at the same time as root would be good. I'll find a good, public download link and publish that in the above (hopefully tomorrow)--if you've got one handy, let me know .

Re. the fastboot-windows.exe thing, I've had a fastboot.exe hanging-around my desktop and laptop for quite a while and have only recently been seeing references to both versions. Many are making references like "use fastboot (or fastboot-windows.exe as appropriate)", so I'll edit my stuff above to reference things the same way.

I've also got something cooking to make installing / using fastboot and adb a little easier...should have something additional to update the first posts by tomorrow.

Also, as you might have noticed, I'm gathering notes for publishing information about installing and using custom recovery in the second post.

Its a work in-progress (both post one and two) and I very much appreciate your attention to this detail and your feedback! Thank you!

Cheers!
scary alien is online now  
Last edited by scary alien; December 2nd, 2011 at 09:44 PM.
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
GalaxyNexus (December 19th, 2011)
Old December 2nd, 2011, 10:33 PM   #22 (permalink)
Resident Ninja
 
VoidedSaint's Avatar
 
Join Date: Feb 2010
Posts: 8,153
 
Device(s): Moto X
Carrier: Verizon

Thanks: 1,280
Thanked 2,146 Times in 1,369 Posts
nick.keatts@gmail.com
Default

*stickied*
VoidedSaint is offline  
Reply With Quote
The Following 4 Users Say Thank You to VoidedSaint For This Useful Post:
GalaxyNexus (December 19th, 2011), scary alien (December 2nd, 2011), teddyearp (December 3rd, 2011), trophynuts (December 6th, 2011)
Old December 2nd, 2011, 10:35 PM   #23 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by VoidedSaint View Post
*stickied*
LOL, took you long enough!

Thought it would be bad-form to sticky my own thread this early (at least until I actually got the flipping phone, eh?).

Thanks!
scary alien is online now  
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
GalaxyNexus (December 19th, 2011)
Old December 3rd, 2011, 12:43 AM   #24 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,159
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 681
Thanked 701 Times in 428 Posts
Default

scary alien, thanks. And to VoidedSaint, thanks. It's late for me, but I think I have everything we need to put together a great root/busybox guide (I found the best stuff in the "GNexus-root-package-FYA" file in the OP). Oh yeah, as far as a good public download link, look no further than my sig (well, until that computer decides to go down~every 3-5yrs or 6-8months, depends).

More tomorrow morning or at the latest tomorrow eve.
teddyearp is online now  
Reply With Quote
The Following User Says Thank You to teddyearp For This Useful Post:
GalaxyNexus (December 19th, 2011)
Old December 3rd, 2011, 09:09 AM   #25 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,159
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 681
Thanked 701 Times in 428 Posts
Default

Well, I took the above file, extracted it, took out the driver package (some people will already have them) and then put in busybox. Direct link:

http://ted.servepics.com/gnex/GNexus-root-busybox-package-nodriver.zip

It's in my i515 folder below, but please go ahead and put it in a dropbox as well since my server can get cranky sometimes.

Ooops, edited my sig and now its gone. . . .

and now it's back . . . lol
teddyearp is online now  
Last edited by teddyearp; December 3rd, 2011 at 09:18 AM.
Reply With Quote
The Following User Says Thank You to teddyearp For This Useful Post:
GalaxyNexus (December 19th, 2011)
Old December 3rd, 2011, 09:13 AM   #26 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by teddyearp View Post
Well, I took the above file, extracted it, took out the driver package (some people will already have them) and then put in busybox. Direct link:

http://ted.servepics.com/gnex/GNexus-root-busybox-package-nodriver.zip

It's in my i515 folder below, but please go ahead and put it in a dropbox as well since my server can get cranky sometimes.
Awesome...downloading now...

LOL, I tried the link before you fixed it with the .zip suffix--figured-it out, though .

I'll incorporate this into the first post.

Thanks!
scary alien is online now  
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
GalaxyNexus (December 19th, 2011)
Old December 4th, 2011, 07:08 PM   #27 (permalink)
Junior Member
 
Join Date: Sep 2010
Posts: 41
 
Device(s):
Carrier: Not Provided

Thanks: 24
Thanked 41 Times in 23 Posts
Default

I just installed android-sdk. I have adb, but I can't find fastboot anywhere. I thought it should have been installed with the sdk. How do I find it? I run linux, and all I can find to download are for windows.
saulback is offline  
Reply With Quote
The Following User Says Thank You to saulback For This Useful Post:
GalaxyNexus (December 19th, 2011)
Old December 4th, 2011, 07:25 PM   #28 (permalink)
Junior Member
 
Join Date: Dec 2011
Posts: 20
 
Device(s): Galaxy Nexus CDMA AOS 4.0.2 rooted
Carrier: Not Provided

Thanks: 6
Thanked 14 Times in 8 Posts
Default

Is there some advantage to having the SuperUser.apk in /system/app, or would it be equally effective to gain root by running

adb root (restart adbd daemon with root permissions)
adb remount (remount /system partion in read/write mode)
adb push su /system/bin (copy su program to the phone)
adb shell chmod 06755 /system/bin/su (re-secure w/root permission/access)

and then installing the current SuperUser.apk from Android market after reboot?
John Markley is offline  
Reply With Quote
The Following 2 Users Say Thank You to John Markley For This Useful Post:
GalaxyNexus (December 19th, 2011), scary alien (December 4th, 2011)
Old December 4th, 2011, 07:42 PM   #29 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by John Markley View Post
Is there some advantage to having the SuperUser.apk in /system/app, or would it be equally effective to gain root by running

adb root (restart adbd daemon with root permissions)
adb remount (remount /system partion in read/write mode)
adb push su /system/bin (copy su program to the phone)
adb shell chmod 06755 /system/bin/su (re-secure w/root permission/access)

and then installing the current SuperUser.apk from Android market after reboot?
John,

First, welcome to the AndroidForums and glad you signed-up .

LOL, I don't think I've ever done it separately, but I'd think you'd need to install it (the Superuser.apk app) like in the above so that the app is owned (and will therefore execute) as root.

The version of Superuser.apk that I have installed on my Droid X is owned by root vs. system like regular apps are:

Code:
# ls -a -l Super*
-rw-r--r-- root     root               196521 2010-12-18 16:58 SuperUser.apk
Hope that helps.

Cheers!
scary alien is online now  
Reply With Quote
The Following 2 Users Say Thank You to scary alien For This Useful Post:
GalaxyNexus (December 19th, 2011), John Markley (December 4th, 2011)
Old December 4th, 2011, 08:01 PM   #30 (permalink)
Junior Member
 
Join Date: Dec 2011
Posts: 20
 
Device(s): Galaxy Nexus CDMA AOS 4.0.2 rooted
Carrier: Not Provided

Thanks: 6
Thanked 14 Times in 8 Posts
Default

Quote:
Originally Posted by scary alien View Post
John,

First, welcome to the AndroidForums and glad you signed-up .

LOL, I don't think I've ever done it separately, but I'd think you'd need to install it (the Superuser.apk app) like in the above so that the app is owned (and will therefore execute) as root.

<snip>
Hope that helps.

Cheers!
Thank you, that does help. The only reason I asked is because in the dev's market description he says

"Note: App and binary will have different versions. The app is updated more often than the binary is.
This app cannot be uninstalled if it was installed with your ROM or root. If there is no uninstall option, it's because you placed it in /system/app, not me."
implying, it seems, that there might be some reason to want to uninstall it, though I cannot think why.
John Markley is offline  
Reply With Quote
The Following 2 Users Say Thank You to John Markley For This Useful Post:
GalaxyNexus (December 19th, 2011), scary alien (December 4th, 2011)
sponsored links
Old December 4th, 2011, 08:15 PM   #31 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by John Markley View Post
Thank you, that does help. The only reason I asked is because in the dev's market description he says

"Note: App and binary will have different versions. The app is updated more often than the binary is.
This app cannot be uninstalled if it was installed with your ROM or root. If there is no uninstall option, it's because you placed it in /system/app, not me."
implying, it seems, that there might be some reason to want to uninstall it, though I cannot think why.
Yeah, I've read this on ChainsDD's Market app description (https://market.android.com/details?id=com.noshufou.android.su) and just now on his web page (Superuser).

I'm still a little fuzzy on how exactly this would work separately like you originally asked. That's a great question and I'll continue to think about it (and maybe try it when I get my GNex (hopefully this coming Thursday )).

I've seen some folks that wanted to be able to remove the Superuser app (which would show up in the app drawer) before turning their device in to make a warranty claim.

There are various ways to do this (i.e., removing the files we referenced above from an "adb shell" or on-phone terminal emulator session), so if you are savvy-enough (which you very much seem to be ), uninstalling these root components should be no problem.

I hope that helps.

Cheers!
scary alien is online now  
Reply With Quote
The Following 2 Users Say Thank You to scary alien For This Useful Post:
GalaxyNexus (December 19th, 2011), John Markley (December 4th, 2011)
Old December 4th, 2011, 08:24 PM   #32 (permalink)
Junior Member
 
Join Date: Dec 2011
Posts: 20
 
Device(s): Galaxy Nexus CDMA AOS 4.0.2 rooted
Carrier: Not Provided

Thanks: 6
Thanked 14 Times in 8 Posts
Default

Quote:
Originally Posted by scary alien View Post
I'm still a little fuzzy on how exactly this would work separately like you originally asked. That's a great question and I'll continue to think about it (and maybe try it when I get my GNex (hopefully this coming Thursday )).

I've seen some folks that wanted to be able to remove the Superuser app (which would show up in the app drawer) before turning their device in to make a warranty claim.

There are various ways to do this (i.e., removing the files we referenced above from an "adb shell" or on-phone terminal emulator session), so if you are savvy-enough (which you very much seem to be ), uninstalling these root components should be no problem.

I hope that helps.

Cheers!
Thanks. I have the same hope (GNex on Thursday...Friday...??). I thought of the desire to remove the app for warranty but, since that would require some adb shell or similar work anyway to remove the su and to relock, it seems irrelevant.
John Markley is offline  
Reply With Quote
The Following User Says Thank You to John Markley For This Useful Post:
GalaxyNexus (December 19th, 2011)
Old December 4th, 2011, 11:48 PM   #33 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,159
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 681
Thanked 701 Times in 428 Posts
Default

If I may clarify. Pushing the su binary and then the subsequent chmod of said binary to 6755 (or something similar) is what gives ANY application, process or anything else superuser access to your android phone. Consider the Superuser.apk as the guardian. Without installing Superuser.apk AT THE SAME TIME your phone is vulnerable to ANY app using root privileges without your knowledge. That is why it is ABSOLUTELY IMPERATIVE to install Superuser.apk at the same time as the su binary. Do not let any version numbers, etc. get you confused, or even make you think about putting Superuser.apk in /data/app or anywhere else than /system/app. Please do not even speculate about this.

After all, those of you that have done this, every single time an app asks for su, Superuser pops up and asks for permission, right? Think about the alternative. Any app could call for su without your knowledge until you decide to install Superuser.apk from the market. And then, Superuser.apk will be installed to /data/app and a simple factory data reset will remove it until you reinstall it, all the while su will remain in /system/xxx wide open.

I hope this is clear enough and removes all doubt about how important it is to install Superuser.apk AT THE SAME time as the su binary.

good luck
teddyearp is online now  
Reply With Quote
Old December 5th, 2011, 01:24 AM   #34 (permalink)
Senior Member
 
WormDoes's Avatar
 
Join Date: Aug 2010
Location: Massachusetts
Posts: 3,199
 
Device(s): G2 & Nexus 7
Carrier: Trapped on Verizon

Thanks: 605
Thanked 1,288 Times in 672 Posts
tren8622@gmail.com
Default

This is a wonderful guide, Scary! Thanks for organizing everything, it's going to help a lot of people and avoid confusion, hopefully . Quick question, if one were to use the "super boot" method to root, would they just need to "fastboot oem unlock" then run the .bat file (Windows PC)?
WormDoes is online now  
Reply With Quote
The Following User Says Thank You to WormDoes For This Useful Post:
scary alien (December 5th, 2011)
Old December 5th, 2011, 07:43 AM   #35 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by WormDoes View Post
This is a wonderful guide, Scary! Thanks for organizing everything, it's going to help a lot of people and avoid confusion, hopefully . Quick question, if one were to use the "super boot" method to root, would they just need to "fastboot oem unlock" then run the .bat file (Windows PC)?
Hey WormDoes, thanks for the kind words (it was a lot of work, but you guys are worth it ).

Yes, the Superboot method assumes you've already done the "fastboot oem unlock" on your phone before you execute the batch file for your particular platform.

I'll go back and bold those notes so it stands out a little better (it really doesn't right now).

Cheers and again, thanks!
scary alien is online now  
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
WormDoes (December 5th, 2011)
Old December 5th, 2011, 08:16 AM   #36 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by teddyearp View Post
If I may clarify. Pushing the su binary and then the subsequent chmod of said binary to 6755 (or something similar) is what gives ANY application, process or anything else superuser access to your android phone. Consider the Superuser.apk as the guardian. Without installing Superuser.apk AT THE SAME TIME your phone is vulnerable to ANY app using root privileges without your knowledge. That is why it is ABSOLUTELY IMPERATIVE to install Superuser.apk at the same time as the su binary. Do not let any version numbers, etc. get you confused, or even make you think about putting Superuser.apk in /data/app or anywhere else than /system/app. Please do not even speculate about this.

After all, those of you that have done this, every single time an app asks for su, Superuser pops up and asks for permission, right? Think about the alternative. Any app could call for su without your knowledge until you decide to install Superuser.apk from the market. And then, Superuser.apk will be installed to /data/app and a simple factory data reset will remove it until you reinstall it, all the while su will remain in /system/xxx wide open.

I hope this is clear enough and removes all doubt about how important it is to install Superuser.apk AT THE SAME time as the su binary.

good luck
Teddy,

I think that you actually can install just the su binary without the Superuser.apk app without any ill-effects or security issues. The reason I say this is these two parts from ChainsDD's website (Superuser) about how the su binary and the Superuser.apk app interact with each other:

Superuser.apk runs as any other app and gives you, the user, a place to see what apps you have allowed or denied, as well as view a log of what apps have used su when.

The su binary is what other apps call when they need superuser rights. The binary checks the database maintained by Superuser.apk to determine if you have already granted rights to the requesting app, and if not tells Superuser.apk to display a prompt asking you for permission.


So, my impression is that if you don't make any su / root requests, then there's nothing to fail. If you do make an su / root request, then that request will fail because the Superuser app has not yet been installed (it won't execute if it can't get permission via the Superuser whitelist app).

I think this also clears-up John Markley's question about installing the Superuser.apk separately (presumably to support great devs like ChainsDD by downloading the app from the Market).

That's my take anyways .

Cheers!
scary alien is online now  
Reply With Quote
Old December 5th, 2011, 10:27 AM   #37 (permalink)
Member
 
headbanger51's Avatar
 
Join Date: Feb 2010
Posts: 186
 
Device(s): OG Droid, FROYO, Pete's BB and one of Fabolos's Themes
Carrier: Not Provided

Thanks: 12
Thanked 15 Times in 13 Posts
Default

the beauty is, I'm sure it won't be long before there's a video of how to root the SGN on youtube. I'm a tech idiot when it comes to this stuff, even though I rooted my OG Droid. I think I still watched a few vids before I did it.
Thanks for posting!
headbanger51 is offline  
Reply With Quote
Old December 5th, 2011, 10:34 AM   #38 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,159
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 681
Thanked 701 Times in 428 Posts
Default

Quote:
Originally Posted by saulback View Post
I just installed android-sdk. I have adb, but I can't find fastboot anywhere. I thought it should have been installed with the sdk. How do I find it? I run linux, and all I can find to download are for windows.
saul, I have it in my collection:

http://ted.servepics.com/gnex/fastboot-linux

Quote:
Originally Posted by scary alien View Post
Teddy,

The su binary is what other apps call when they need superuser rights. The binary checks the database maintained by Superuser.apk to determine if you have already granted rights to the requesting app, and if not tells Superuser.apk to display a prompt asking you for permission.
I would rather err on the side of caution, as this does not say what su does when there is no database to refer to at all. Something in my mind tells me that su would just go ahead and grant any request since there's nothing saying not to. I guess we could ask ChainsDD, maybe I will.

That's my take.
teddyearp is online now  
Reply With Quote
Old December 5th, 2011, 11:52 AM   #39 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by saulback View Post
I just installed android-sdk. I have adb, but I can't find fastboot anywhere. I thought it should have been installed with the sdk. How do I find it? I run linux, and all I can find to download are for windows.
Saul,

Apologies for missing your post but thanks to teddyearp catching that and replying.

You can also find fastboot.exe / fastboot-windows.exe in this FAQ guide:

http://androidforums.com/faqs/443072-adb-guide-updated-12-04-2011-a.html

here at AF. I added a "Mini-SDK for Windows" section this past weekend that has an sdk-tools.zip file (downloadable in that page--its also referenced here in this thread in post #2 above (whose contents I'm still tweaking for getting custom recovery installed)).

The sdk-tools.zip file basically just contains adb.exe and the .dll files that it needs to run and the fastboot executables. Should make it so that you don't actually need to download and install the full Android SDK.

Let me know if you have any questions.

Cheers!
scary alien is online now  
Reply With Quote
Old December 5th, 2011, 04:08 PM   #40 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,159
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 681
Thanked 701 Times in 428 Posts
Default

Quote:
Originally Posted by saulback View Post
<snip>I run linux, and all I can find to download are for windows.
scary, he wants/needs the linux version. That is why I took it out of one of the packages and linked him to it only.
teddyearp is online now  
Reply With Quote
The Following User Says Thank You to teddyearp For This Useful Post:
scary alien (December 5th, 2011)
sponsored links
Old December 5th, 2011, 04:20 PM   #41 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by teddyearp View Post
scary, he wants/needs the linux version. That is why I took it out of one of the packages and linked him to it only.
Oh, thanks Teddy and apologies again, Saul ...

I'm gonna go slink away in my little corner now...
scary alien is online now  
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
teddyearp (December 5th, 2011)
Old December 5th, 2011, 08:43 PM   #42 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,159
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 681
Thanked 701 Times in 428 Posts
Default

Sorry, scary. I didn't mean to make you feel like you had to 'slink' off . . . . . lol.
teddyearp is online now  
Reply With Quote
Old December 5th, 2011, 08:47 PM   #43 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by teddyearp View Post
Sorry, scary. I didn't mean to make you feel like you had to 'slink' off . . . . . lol.
LOL, I felt worse that I overlooked Saul's post...and then I missed the important part about Linux (I'll half-blame a busy day at work ).

Better now...still catching-up on a lot of PMs and posts.

Thanks for keeping an eye-out here, too...we all appreciate it .

Cheers!
scary alien is online now  
Reply With Quote
Old December 6th, 2011, 06:40 AM   #44 (permalink)
Member
 
Travillion's Avatar
 
Join Date: Oct 2011
Location: State College, PA
Posts: 216
 
Device(s): Nexus 5
Carrier: Not Provided

Thanks: 1,210
Thanked 345 Times in 184 Posts
Default

Hi all,

I hope this is the proper venue for my question. I am anticipating getting the Verizon G-Nex this week and have been thinking about how to get my data on my existing phone over to my new phone. I have all my existing data backed up with Titanium backup. However, I was hoping to keep my G-Nex as "untinkered" with as possible (since it's a pure(r) Google experience phone, I'm not interested in flashing ROMs and interrupting the updates direct from Google). However, I am going to have to root the G-Nex in order to transfer my app data via Titanium Backup.

So I guess my real question is: Can I simply unlock and root the G-Nex without flashing an alternative recovery mode, etc., which would allow me to run apps that require root (such as Titanium Backup) but also not interfere with receiving direct updates from Google?

Thanks in advance.
Travillion is offline  
Reply With Quote
Old December 6th, 2011, 09:10 AM   #45 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,623
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,653
Thanked 14,096 Times in 6,887 Posts
Default

Quote:
Originally Posted by Travillion View Post
Hi all,

I hope this is the proper venue for my question. I am anticipating getting the Verizon G-Nex this week and have been thinking about how to get my data on my existing phone over to my new phone. I have all my existing data backed up with Titanium backup. However, I was hoping to keep my G-Nex as "untinkered" with as possible (since it's a pure(r) Google experience phone, I'm not interested in flashing ROMs and interrupting the updates direct from Google). However, I am going to have to root the G-Nex in order to transfer my app data via Titanium Backup.

So I guess my real question is: Can I simply unlock and root the G-Nex without flashing an alternative recovery mode, etc., which would allow me to run apps that require root (such as Titanium Backup) but also not interfere with receiving direct updates from Google?

Thanks in advance.
Travillion,

Yeah, you should be able to follow one of the above rooting methods... None of these involve installing a custom recovery or re-flashing any of the boot images.

The rooting methods above basically have you soft-boot (i.e., in memory) the unsecured boot image so that you can remount /system in read/write mode to allow the root binaries (su and Superuser.apk) to be installed on your phone.

After that, you'll have root and can use TiBu to restore your apps!

Does that help and/or make sense?

Cheers!

edit: the stuff in post #2 re. ClockworkMod custom recovery is still under construcution at this point and isn't necessary for rooting. I'll add a little disclaimer in that post .
scary alien is online now  
Last edited by scary alien; December 6th, 2011 at 09:13 AM.
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
Travillion (December 6th, 2011)
Old December 6th, 2011, 09:22 AM   #46 (permalink)
Member
 
Travillion's Avatar
 
Join Date: Oct 2011
Location: State College, PA
Posts: 216
 
Device(s): Nexus 5
Carrier: Not Provided

Thanks: 1,210
Thanked 345 Times in 184 Posts
Default

Quote:
Originally Posted by scary alien View Post
Travillion,

Yeah, you should be able to follow one of the above rooting methods... None of these involve installing a custom recovery or re-flashing any of the boot images.

The rooting methods above basically have you soft-boot (i.e., in memory) the unsecured boot image so that you can remount /system in read/write mode to allow the root binaries (su and Superuser.apk) to be installed on your phone.

After that, you'll have root and can use TiBu to restore your apps!

Does that help and/or make sense?

Cheers!

edit: the stuff in post #2 re. ClockworkMod custom recovery is still under construcution at this point and isn't necessary for rooting. I'll add a little disclaimer in that post .
Yes, that is most helpful! Thank you. My primary concern is to not disqualify myself from the direct updates from Google. As long as I can unlock and root without needing the custom recovery, I don't care about flashing ROMs, etc. I wasn't sure if adding the su binary or superuser.apk would mess with google updates for some reason, but it sounds like it won't.

Thanks for putting all the time into this thread. It's a great resource!
Travillion is offline  
Reply With Quote
The Following User Says Thank You to Travillion For This Useful Post:
scary alien (December 6th, 2011)
Old December 6th, 2011, 10:23 AM   #47 (permalink)
Carpe Cerevisi
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: In The Shadows
Posts: 9,485
 
Device(s): LG G2
Carrier: VZW

Thanks: 4,736
Thanked 6,569 Times in 3,494 Posts
Default

Fastboot for Linux/Mac/Windows from Koush:
Index of /G1

If anyone needs them.
iowabowtech is online now  
Last edited by iowabowtech; December 6th, 2011 at 10:27 AM.
Reply With Quote
The Following User Says Thank You to iowabowtech For This Useful Post:
scary alien (December 6th, 2011)
Old December 6th, 2011, 04:34 PM   #48 (permalink)
Senior Member
 
Wolfedude88's Avatar
 
Join Date: Jan 2010
Location: Plainfield, Indiana
Gender: Male
Posts: 2,754
 
Device(s): HTC Droid DNA(Red)
Carrier: Verizon

Thanks: 356
Thanked 555 Times in 357 Posts
Default

Not sure what I am doing wrong, Here is the screen shot below. I get adb devices to shows but not fastboot devices to show. Any ideas? I thought I had all the right drivers installed.

Wolfedude88 is offline  
Reply With Quote
Old December 6th, 2011, 04:41 PM   #49 (permalink)
Junior Member
 
Join Date: Dec 2011
Posts: 20
 
Device(s): Galaxy Nexus CDMA AOS 4.0.2 rooted
Carrier: Not Provided

Thanks: 6
Thanked 14 Times in 8 Posts
Default

Quote:
Originally Posted by scary alien View Post
Travillion,

Yeah, you should be able to follow one of the above rooting methods... None of these involve installing a custom recovery or re-flashing any of the boot images.

The rooting methods above basically have you soft-boot (i.e., in memory) the unsecured boot image so that you can remount /system in read/write mode to allow the root binaries (su and Superuser.apk) to be installed on your phone.

After that, you'll have root and can use TiBu to restore your apps!

Does that help and/or make sense?

Cheers!

edit: the stuff in post #2 re. ClockworkMod custom recovery is still under construcution at this point and isn't necessary for rooting. I'll add a little disclaimer in that post .
Scary Alien - Am I correct in the context of this thread that if after unlocking, but before rooting, I were to boot, not flash, the cwm .img thusly,

fastboot boot recovery-clockwork-5.5.0.2-maguro.img

and run a nandroid backup of the virgin OS, reboot, and then root, that there still would be no residual to derail the condition Travillion wants to achieve ?
John Markley is offline  
Reply With Quote
The Following User Says Thank You to John Markley For This Useful Post:
Travillion (December 6th, 2011)
Old December 6th, 2011, 04:44 PM   #50 (permalink)
Junior Member
 
Join Date: Dec 2011
Posts: 20
 
Device(s): Galaxy Nexus CDMA AOS 4.0.2 rooted
Carrier: Not Provided

Thanks: 6
Thanked 14 Times in 8 Posts
Default

Quote:
Originally Posted by Wolfedude88 View Post
Not sure what I am doing wrong, Here is the screen shot below. I get adb devices to shows but not fastboot devices to show. Any ideas? I thought I had all the right drivers installed.

Is your fastboot shell by any chance fastboot.exe? If so, try

fastboot.exe devices
John Markley is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > Samsung Galaxy Nexus > (International / GSM) Galaxy Nexus - All Things Root

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


LinkBacks (?)
LinkBack to this Thread: http://androidforums.com/international-gsm-galaxy-nexus-all-things-root/452146-how-root-gsm-hspa-samsung-galaxy-nexus.html
Posted By For Type Date
lucky patcher galaxy next - Virgilio Ricerca Web This thread Refback May 11th, 2012 07:26 AM
Untitled document This thread Refback March 5th, 2012 02:38 AM


All times are GMT -5. The time now is 09:48 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.