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

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

worked like a charm!

Note 2 things:

before invoking cat in /cache i had to delete a symlink ...

lrwxrwxrwx 1 root root 14 May 14 16:51 su -> /system/bin/su

when mounting "system" in the CWM menu, i noticed that for some reason /cache was already mounted.

at the end of your process, before reboot, i unmounted /system and unmounted /cache in CWM.

WOW... THANKS
 
Upvote 0
I'm in need of help, I rooted, and unlocked my bootloader earlier, but my phone doesn't have root access! I can't used any root apps, but the Superuser app is installed, I tried to flash the recovery that was mentioned to work when the other doesn't work, but whenever I can't boot into recovery, I get the triangle with the "!" inside it. There's an option in Wug's Toolkit, that says flash recovery, I'm not sure if I should/can use it, any help or insight would be great, thank you!
 
Upvote 0
I'm in need of help, I rooted, and unlocked my bootloader earlier, but my phone doesn't have root access! I can't used any root apps, but the Superuser app is installed, I tried to flash the recovery that was mentioned to work when the other doesn't work, but whenever I can't boot into recovery, I get the triangle with the "!" inside it. There's an option in Wug's Toolkit, that says flash recovery, I'm not sure if I should/can use it, any help or insight would be great, thank you!

FrenchToast,

Apologies for the belated reply...been crazy busy these last few days.

I don't know if you are on 4.0.4 already or not, but it you are, then you'll need to use the su.zip package that works best for 4.0.4:

http://www.box.com/s/jvcf196j7x8f8vrc9cyt

(I would bet that it would work fine on 4.0.2, also).

If your install custom recovery is going away, its because at shutdown time there's a file called /system/recovery-from-boot.p whose presence indicates to Android that the stock recovery should be re-flashed.

You can follow the notes in this post:

How to install ClockworkMod custom recovery

for manually fixing this after you've successfully attained root.

You can also install my (free) app, Android Root Toolkit, which has an option for renaming the recovery-from-boot.p file. Its link is in my signature (which I'm hoping will show up in this post ;)).

edit: nope, didn't, but here it is: Android Root Toolkit

Cheers!
 
Upvote 0
FrenchToast,

Apologies for the belated reply...been crazy busy these last few days.

I don't know if you are on 4.0.4 already or not, but it you are, then you'll need to use the su.zip package that works best for 4.0.4:

http://www.box.com/s/jvcf196j7x8f8vrc9cyt

(I would bet that it would work fine on 4.0.2, also).

If your install custom recovery is going away, its because at shutdown time there's a file called /system/recovery-from-boot.p whose presence indicates to Android that the stock recovery should be re-flashed.

You can follow the notes in this post:

How to install ClockworkMod custom recovery

for manually fixing this after you've successfully attained root.

You can also install my (free) app, Android Root Toolkit, which has an option for renaming the recovery-from-boot.p file. Its link is in my signature (which I'm hoping will show up in this post ;)).

edit: nope, didn't, but here it is: Android Root Toolkit

Cheers!

Worked like a charm! Thank-you Scary Alien!
 
  • Like
Reactions: scary alien
Upvote 0
i looked into this and i guess that symlinks to "toolbox" in /system/bin are different than symlinks to "busybox" in /system/xbin.

i dont think i had busybox.. i had root , but no busybox.

i thought u got BB with root.

i used this method to root and thought that tar / grep would be included with the toolbox? They are not there in the symlinks in /system/bin

What am i supposed to do with root if i want to mount /data and then install a package or an RPM there so that i can do some shell scripting and c work?

I want to move a tar to /data/local and then unpack it. Not able to because tar is not found ??

what i have symlinked in /system/bin

Code:
$ adb shell ls -l /system/bin | grep toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 cat -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 chmod -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 chown -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 cmp -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 date -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 dd -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 df -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 dmesg -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 getevent -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 getprop -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 hd -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 id -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 ifconfig -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 iftop -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 insmod -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 ioctl -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 ionice -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 kill -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 ln -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 log -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 ls -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 lsmod -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 lsof -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 mkdir -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 mount -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 mv -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 nandread -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 netstat -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 newfs_msdos -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 notify -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 printenv -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 ps -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 reboot -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 renice -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 rm -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 rmdir -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 rmmod -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 route -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 schedtop -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 sendevent -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 setconsole -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 setprop -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 sleep -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 smd -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 start -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 stop -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 sync -> toolbox
-rwxr-xr-x root     shell      103248 2012-02-06 21:26 toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 top -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 touch -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 umount -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 uptime -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 vmstat -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 watchprops -> toolbox
lrwxr-xr-x root     shell             2012-02-07 09:59 wipe -> toolbox

what i dont have that i need: (tar / which / grep )

Code:
127|shell@android:/ # which
which
sh: which: not found
127|shell@android:/ # grep
grep
sh: grep: not found
127|shell@android:/ # tar
tar
sh: tar: not found
127|shell@android:/ #
 
Upvote 0
Hey Rob,

Yeah, busybox does not automatically come with rooting--some root packages/methods might do this, but many do not.

The good news is that you can grab one from the Market--there are a few to choose from:

https://play.google.com/store/apps/details?id=stericson.busybox

https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer

(each of the above also has a paid version).

Here's the dump of supported commands for the version that I have installed:
C:\Users\Scary Alien>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
root@android:/ # busybox
busybox
BusyBox v1.19.4-cm9 bionic (2012-02-05 18:40 +0100) multi-call binary.
Copyright (C) 1998-2011 Erik Andersen, Rob Landley, Denys Vlasenko
and others. Licensed under GPLv2. Merged for bionic by tpruvot@github
See source distribution for full notice.

Usage: busybox [function] [arguments]...
or: busybox --list[-full]
or: function [arguments]...

BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as.

Currently defined functions:
[, [[, arp, ash, awk, base64, basename, bbconfig, blockdev, brctl,
bunzip2, bzcat, bzip2, cal, cat, catv, chattr, chgrp, chmod, chown,
chroot, clear, cmp, comm, cp, cpio, crond, crontab, cut, date, dc, dd,
depmod, devmem, df, diff, dirname, dmesg, dnsd, dos2unix, du, echo, ed,
egrep, env, expand, expr, false, fdisk, fgrep, find, flash_lock,
flash_unlock, flashcp, flock, fold, free, freeramdisk, fsync, ftpget,
ftpput, fuser, getopt, grep, groups, gunzip, gzip, halt, head, hexdump,
id, ifconfig, insmod, install, iostat, ip, kill, killall, killall5,
less, ln, losetup, ls, lsattr, lsmod, lsusb, lzcat, lzma, lzop,
lzopcat, man, md5sum, mesg, mkdir, mkdosfs, mke2fs, mkfifo, mkfs.ext2,
mkfs.vfat, mknod, mkswap, mktemp, modinfo, modprobe, more, mount,
mountpoint, mpstat, mv, nanddump, nandwrite, nbd-client, nc, netstat,
nice, nohup, nslookup, ntpd, od, patch, pgrep, pidof, ping,
pipe_progress, pkill, pmap, poweroff, printenv, printf, ps, pstree,
pwd, pwdx, rdev, readlink, realpath, reboot, renice, reset, resize,
rev, rm, rmdir, rmmod, route, run-parts, rx, sed, seq, setconsole,
setserial, setsid, sh, sha1sum, sha256sum, sha512sum, sleep, sort,
split, stat, strings, stty, sum, swapoff, swapon, sync, sysctl, tac,
tail, tar, tee, telnet, telnetd, test, tftp, tftpd, time, timeout, top,
touch, tr, traceroute, true, ttysize, tune2fs, umount, uname,
uncompress, unexpand, uniq, unix2dos, unlzma, unlzop, unxz, unzip,
uptime, usleep, uudecode, uuencode, vi, watch, wc, wget, which, whoami,
xargs, xz, xzcat, yes, zcat

root@android:/ #
Cheers and good luck!
 
Upvote 0
.
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.

This seems like a 1-click method in the thread below. Anything wrong with this?

1-click Galaxy Nexus root toolkit ! Unlock bootloader+ CWM + Su (or) SuperSu
http://androidforums.com/internatio...ck-bootloader-cwm-su-supersu.html#post4656472

IF not, then I'll use it on both my Galaxy Nexus phones when they arrive...

I see it's now been updated to support Jelly Bean.
____________

And what about this one? Any good?

CASUAL One-Click Root and Recovery Tool for Galaxy Nexus
http://www.androidauthority.com/galaxy-nexus-casual-one-click-root-recovery-87400/


__________

And if you want your mind to be blown, go read this:

[GNex TOOLKIT V7.4] Drivers, Backup, Unlock, Root, CWM, Flash, Mods + MUCH MORE [GSM
http://forum.xda-developers.com/showthread.php?t=1392310


___________

This one seems awesome, too:

WugFresh Nexus Root Toolkit v1.5.1
http://www.wugfresh.com/dev/nexus-root-toolkit/

This program has been renamed the ‘Nexus Root Toolkit’ because it now supports all the Nexus devices:

Galaxy Nexus: GSM Models (both yakju and non-yakju builds)
Galaxy Nexus: CDMA/LTE Verizon Models
Galaxy Nexus: CDMA/LTE Sprint Models
Nexus S: Worldwide, i9020t and i9023 Models
Nexus S: 850MHz, i9020a Models
Nexus S: Korea, m200 Models
Nexus S 4G: d720 Models
Nexus 7: Asus Tablet

screenshots from v. 1.4 but you get the idea...

basic_features.png


advanced_utilities.bmp
 
Upvote 0
At the time I wrote that, November 2011, there was no native ICS root exploit for the GNex.

In Feburary 2012, I published this thread regarding the mempodroid exploit: http://androidforums.com/international-galaxy-nexus-all-things-root/502204-galaxy-nexus-root-un-root-without-unlocking-bootloader.html which allowed the rooting of a Samsung Galaxy Nexus without unlocking the bootloader via a known Linux kernel exploit.

Unfortunately, this only works on ICS 4.0.1 or 4.0.2 devices since the kernel exploit was patched for 4.0.4.

This seems like a 1-click method in the thread below. Anything wrong with this?

1-click Galaxy Nexus root toolkit ! Unlock bootloader+ CWM + Su (or) SuperSu
http://androidforums.com/internatio...ck-bootloader-cwm-su-supersu.html#post4656472

IF not, then I'll use it on both my Galaxy Nexus phones when they arrive...

I see it's now been updated to support Jelly Bean.

This appears to be a tool on-par with Wug's Gnex root toolkit. Very nice, but not really new.

And what about this one? Any good?

CASUAL One-Click Root and Recovery Tool for Galaxy Nexus
Samsung Galaxy Nexus: Rooting, BusyBox, and ClockworkMod Recovery install using CASUAL tool

I've read about Adam Outler's CASUAL adb utility/tool. I'm guessing this tool might use the same mempodroid exploit used in the thread I wrote about up-top. The reason I say this is that it won't work on ICS higher than 4.0.2. As far as I know, unless you save/protect root in 4.0.2, the only way to root past 4.0.2 is to boot an insecure boot image file and/or softboot/flash a custom recovery and flash the su.zip file.

And if you want your mind to be blown, go read this:

[GNex TOOLKIT V7.4] Drivers, Backup, Unlock, Root, CWM, Flash, Mods + MUCH MORE [GSM
[GNex TOOLKIT V7.4] Drivers, Backup, Unlock, Root, CWM, Flash, Mods + MUCH MORE [GSM] - xda-developers

Yeah, I've read about mskip's GNex toolkit before. Its very nice and very comprehensive. But again, these are just variations of tools like Wugfresh's toolkit (although I do believe mskip's tool existed before Wug's ;) :)).

Cheers!
 
Upvote 0
At the time I wrote that, November 2011, there was no native ICS root exploit for the GNex.

In Feburary 2012, I published this thread regarding the mempodroid exploit: http://androidforums.com/international-galaxy-nexus-all-things-root/502204-galaxy-nexus-root-un-root-without-unlocking-bootloader.html which allowed the rooting of a Samsung Galaxy Nexus without unlocking the bootloader via a known Linux kernel exploit.

Unfortunately, this only works on ICS 4.0.1 or 4.0.2 devices since the kernel exploit was patched for 4.0.4.



This appears to be a tool on-par with Wug's Gnex root toolkit. Very nice, but not really new.



I've read about Adam Outler's CASUAL adb utility/tool. I'm guessing this tool might use the same mempodroid exploit used in the thread I wrote about up-top. The reason I say this is that it won't work on ICS higher than 4.0.2. As far as I know, unless you save/protect root in 4.0.2, the only way to root past 4.0.2 is to boot an insecure boot image file and/or softboot/flash a custom recovery and flash the su.zip file.



Yeah, I've read about mskip's GNex toolkit before. Its very nice and very comprehensive. But again, these are just variations of tools like Wugfresh's toolkit (although I do believe mskip's tool existed before Wug's ;) :)).

Cheers!

I believe the two bottom ones say they've been updated to work with jelly bean.

I'm at the airport right now and can't look it up well on this esteem. Can't wait to get the bigger screen of nexus. :)

________________

EDIT: yep, at least 3 of the 4 support Jelly Bean for rooting 1 click.


http://forum.xda-developers.com/showthread.php?t=1672708
Tool updated,not a major update though just adding support to jelly bean and few more modifications

http://www.wugfresh.com/dev/nexus-root-toolkit/
Changelog | WugFresh
Added native Jelly Bean support using SuperSU apk and binary and automated adb push scripts

http://forum.xda-developers.com/showthread.php?t=1392310
+Added ToolKit support for JellyBean 4.1.1 (yakju and takju but other models can use either of these to root)
 
Upvote 0
I believe the two bottom ones say they've been updated to work with jelly bean.

I'm at the airport right now and can't look it up well on this esteem. Can't wait to get the bigger screen of nexus. :)

Yeah, you're gonna love the GNex :).

In addition to the above (or maybe they've already reference it?) but you can do many of the same flashing operations using Odin (or Heimdall) vs. using fastboot.

I unfortunately, haven't yet worked with Odin...

So may ways to do things with an unlocked bootloader :) :) :) [its great to have so many options].

Cheers!
 
Upvote 0
I believe the two bottom ones say they've been updated to work with jelly bean.

I'm at the airport right now and can't look it up well on this esteem. Can't wait to get the bigger screen of nexus. :)

________________

EDIT: yep, at least 3 of the 4 support Jelly Bean for rooting 1 click.


Galaxy Nexus & Nexus s,one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu - xda-developers


Nexus Root Toolkit v1.5.1 | WugFresh
Changelog | WugFresh


[GNex TOOLKIT V7.4] Drivers, Backup, Unlock, Root, CWM, Flash, Mods + MUCH MORE [GSM] - xda-developers


I downloaded a couple but ended up using this one.


Nexus Root Toolkit v1.5.1 | WugFresh


Just make sure after you install the Win7 Samsung USB drivers to reboot the PC, then go from there. In the first step you use the Nexus volume button to arrow up and down on the screen to make a choice, then use the power button to "start" the process. During that time there is a graphic on the screen with the instructions, but I was in a hurry, trying to PRESS the screen to make the choices. :eek:

Anyway it all worked fine.
 
Upvote 0
Okay, it won't work without a wipe because of the locked bootloader... gah :)
But how I can make a backup of the apps (won't lose all game-saves again) and homescreen-settings of widgets and icons? The Toolkit saves a 700MB file, that can't be all apps (>6GB)


This thread is useful for your purposes. Go to the link, there's more info I didn't copy and paste including a mention of homescreen icons.


Preparing for Jelly Bean,
xda-developers - View Single Post - Preparing for Jelly Bean,

Before anything make a android if anything should go wrong you can restore.

For messages I suggest SMS Backup and Restore found in the play store.

For apps and all that use titanium backup and restore app+data on jellybean which will import all settings and data the application had on the original backup.

Contacts should have been backed up to the Google servers so you don't really have to worry about that, once you sign in to jellybean for the first time your contacts will be completely restores automatically.

Home screens not possible , to my knowing, unless you use a third party launcher such as Nova which let's you backup home screens
 
Upvote 0
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
Brief description:

- download su.zip flashable root package and proper version of ClockworkMod
- put phone in fastboot mode
- soft-boot or flash ClockworkMod custom recovery
- push the su.zip file to your phone via adb
- flash the su.zip root package in ClockworkMod to install root
- reboot phone

I wanted to use this method to root my JB phone.
Recently I used the ClockworkMod to flash my phone to 4.1.1 and everything seemed to work perfectly. Later I wanted to use the above method to root it and I've encountered a problem - the recovery mode of ClockworkMod won't start. It ends up with android error and I have to take out my battery.
What is the easiest way to root a phone right now? I am a linux user so no windows programs will do it for me (it's quite a lot of struggle to find a friend willing to borrow a computer and then mess around with it...).
Also, wiping data from my cell phone is not an option (bootloader is unlocked though).
Any ideas?
 
Upvote 0
I wanted to use this method to root my JB phone.
Recently I used the ClockworkMod to flash my phone to 4.1.1 and everything seemed to work perfectly. Later I wanted to use the above method to root it and I've encountered a problem - the recovery mode of ClockworkMod won't start. It ends up with android error and I have to take out my battery.
What is the easiest way to root a phone right now? I am a linux user so no windows programs will do it for me (it's quite a lot of struggle to find a friend willing to borrow a computer and then mess around with it...).
Also, wiping data from my cell phone is not an option (bootloader is unlocked though).
Any ideas?

Welcome to the AndroidForums, Bungi! :)

So, are you in fact rooted? (did you previously successfully flash CWM and flash the su.zip file)

It kind of sounds like you just need to make the recovery "stick" (Android will re-write the stock recovery every time you shut down unless you disable a file that tells/allows him to do so).

If this sounds right, then take a peek at the Flashed custom recovery won't "stick"? section in this post:

http://androidforums.com/international-galaxy-nexus-all-things-root/470831-how-all-things-root-samsung-galaxy-nexus.html#post3712027

Also, I created a (free, in the Market) app called Android Root Toolkit that has an option to "make recovery stick".

Please note that after you've taken steps to make the recovery stick, you'll have to re-flash your custom recovery so it's present again (my app also has some custom recovery flashing options for the Galaxy Nexus, so you can re-flash it with it).

Let me know :).

Cheers!
 
  • Like
Reactions: Bungi
Upvote 0
Welcome to the AndroidForums, Bungi! :)
Glad to be welcomed :)

So, are you in fact rooted? (did you previously successfully flash CWM and flash the su.zip file)
Not quite. I was rooted before updating to JB. I didn't delete any files and according to Superuser.apk I have the /system/bin/su file but no root shell.
I wanted to root it the way I used to (fastboot - recovery mode - flash with su.zip) but the phone crashes the moment it boots in recovery mode. It works fine in fastboot but when I switch to recovery and tell it to boot that mode it crashes. I downloaded your app but I reckon I'd need to be rooted first to use it...

Thanks for a quick answer! ;)

EDIT:
I just checked with a terminal emulator - I have no permission to use "su" command.
 
Upvote 0
Glad to be welcomed :)

Not quite. I was rooted before updating to JB. I didn't delete any files and according to Superuser.apk I have the /system/bin/su file but no root shell.
I wanted to root it the way I used to (fastboot - recovery mode - flash with su.zip) but the phone crashes the moment it boots in recovery mode. It works fine in fastboot but when I switch to recovery and tell it to boot that mode it crashes. I downloaded your app but I reckon I'd need to be rooted first to use it...

Thanks for a quick answer! ;)

EDIT:
I just checked with a terminal emulator - I have no permission to use "su" command.

So, you obtained JellyBean as a result of an over-thead-air (OTA) update, right (vs. installing a JB custom ROM)?

If you did install/take an OTA, then yeah, you're going to have to re-root by re-flashing ClockworkMod custom recovery via fastboot and then flash the su.zip (be sure to use the newer, up-to-date su.zip that I mention at the top of the first post in this thread).

OTAs clobber root because the su binary gets re-secured during the installation process. You could have saved root with OTA RootKeeper (or even with my app that I mentioned earlier) since they'll allow you to restore root after having previously saved it.

The good news is that your bootloader is unlocked, so all you really have to do is:

- download / copy the new su.zip file to the top-level of your /sdcard folder
- put phone in fastboot / bootloader mode
- fastboot flash recovery recovery.img (using the proper recovery.img name, of course)
- flash the new su.zip (that you've already copied to your /sdcard)
- reboot

After you reboot, you'll be rooted and you can make your recovery stick as I described in the previous post.

Let me know how it goes! :)

Cheers!
 
  • Like
Reactions: Bungi
Upvote 0
So, you obtained JellyBean as a result of an over-thead-air (OTA) update, right (vs. installing a JB custom ROM)?
Here's what I did:
The system let me know there is an update and it downloaded an upgrade. Then I turned on the phone on recovery mode (up/down button + power) and picked "install .zip from sdcard" and pointed to the upgrade that was downloaded by system itself (I had to cp it to sdcard from cache). And it went fine :)

The good news is that your bootloader is unlocked, so all you really have to do is:

- download / copy the new su.zip file to the top-level of your /sdcard folder
- put phone in fastboot / bootloader mode
- fastboot flash recovery recovery.img (using the proper recovery.img name, of course)
- flash the new su.zip (that you've already copied to your /sdcard)
- reboot
Last (hopefully) quick question. Do I flash the recovery with the ROM that I used for upgrade? Or maybe can i flash it somehow with ClockworkModRecovery (I liked the options it offered in recovery mode).
I would like to mess it up when I'm so close to a happyend :)

EDIT:
Nevermind :) I just flashed the recovery mode from Clockwork and then installed the su.zip and it works perfectly! Thank you so much :)
 
  • Like
Reactions: scary alien
Upvote 0
Just want to say I've used this 1-click solution now on both my Galaxy Nexus phone and now my wife's Galaxy Nexus phone. Worked very well. Mine had ICS 4.01, but hers had received the 4.1.1 Jelly Bean OTA -- it rooted them both just fine. ;)

Even lets you back up and restore the APN.

This package has now been updated to Nexus Root Toolkit v1.5.2.

More screenshots and download link here:

http://www.wugfresh.com/dev/nexus-root-toolkit/




___________

This one seems awesome, too:

WugFresh Nexus Root Toolkit v1.5.1
Nexus Root Toolkit v1.5.2 | WugFresh

This program has been renamed the ‘Nexus Root Toolkit’ because it now supports all the Nexus devices:

Galaxy Nexus: GSM Models (both yakju and non-yakju builds)
Galaxy Nexus: CDMA/LTE Verizon Models
Galaxy Nexus: CDMA/LTE Sprint Models
Nexus S: Worldwide, i9020t and i9023 Models
Nexus S: 850MHz, i9020a Models
Nexus S: Korea, m200 Models
Nexus S 4G: d720 Models
Nexus 7: Asus Tablet

screenshots from v. 1.4 but you get the idea...

basic_features.png


advanced_utilities.bmp
 
Upvote 0

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