Go Back   Android Forums > Android Phones > Samsung Galaxy Nexus > (Verizon) 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 Tree6Likes

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

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default [HOW TO] Root the VZW/LTE 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)

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.
In addition to my notes / instructions (click the Show button below) for unlocking the bootloader, here are two other threads that might prove helpful to you:


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)




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

-=< 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; October 10th, 2012 at 09:21 PM. Reason: update w/new JB su.zip package
Reply With Quote
The Following 18 Users Say Thank You to scary alien For This Useful Post:
atltimelord (January 1st, 2012), bevardimus (January 31st, 2012), Cat4699 (December 30th, 2011), ElectroM (January 14th, 2012), jbdan (December 30th, 2011), JM33 (December 24th, 2011), Joey1558 (January 20th, 2012), joeymad (January 27th, 2012), kool kat2 (February 17th, 2012), Lohung (May 25th, 2012), lz5t38 (January 27th, 2012), Podivin (December 22nd, 2011), sdrawkcab25 (January 1st, 2012), trophynuts (December 22nd, 2011), umataro42 (June 11th, 2012), veccster (July 10th, 2012), wildland (January 10th, 2012), zook79 (January 16th, 2012)
sponsored links
Old December 24th, 2011, 04:40 PM   #2 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,160
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 685
Thanked 704 Times in 430 Posts
Default

OK, I've got a technical question. It seems as though the easiest way for now is to either flash CWRecovery or boot recovery CWRecovery, then use the provided "su.zip" file to finish the job. However, my goal is to install busybox at the same time.

A tiny bit of background, I sort of know how to make custom "update.zip" files (at least for the A855/OG Droid), I have template files and guides to do so. With these 'template' files, there is always a path that goes like this:
Code:
META-INF/com/google/android/
and contained therein are usually two files:
Code:
update-binary
updater-script
and it is the "updater-script" file that I know how to manipulate.

However with the "su.zip" file posted here, in the root directory is a META-INF folder and another .zip file starting with "Superuser". If you follow the path to the end in the root META-INF directory, all you find is an "update-binary" file. If you open the "Superuser[etc.].zip" file in the root, then you find the stuff I'm used to seeing; again down to the end of the "META-INF" path, i.e. a "updater-script" file.

Obviously this "su.zip" file works, but how? Is this an update contained in ICS, or the CWRecovery for the i515? I guess what I'm saying is why have a modified "update-binary" that is going to then further install another "update.zip" style file. Is this needed? Or could I just create my own "update.zip" style file to install via CWRecovery; su, Superuser.apk, and busybox through the "updater-script" commands that I am used to?
teddyearp is offline  
Reply With Quote
Old December 26th, 2011, 01:31 AM   #3 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by teddyearp View Post
OK, I've got a technical question. It seems as though the easiest way for now is to either flash CWRecovery or boot recovery CWRecovery, then use the provided "su.zip" file to finish the job. However, my goal is to install busybox at the same time.

A tiny bit of background, I sort of know how to make custom "update.zip" files (at least for the A855/OG Droid), I have template files and guides to do so. With these 'template' files, there is always a path that goes like this:
Code:
META-INF/com/google/android/
and contained therein are usually two files:
Code:
update-binary
updater-script
and it is the "updater-script" file that I know how to manipulate.

However with the "su.zip" file posted here, in the root directory is a META-INF folder and another .zip file starting with "Superuser". If you follow the path to the end in the root META-INF directory, all you find is an "update-binary" file. If you open the "Superuser[etc.].zip" file in the root, then you find the stuff I'm used to seeing; again down to the end of the "META-INF" path, i.e. a "updater-script" file.

Obviously this "su.zip" file works, but how? Is this an update contained in ICS, or the CWRecovery for the i515? I guess what I'm saying is why have a modified "update-binary" that is going to then further install another "update.zip" style file. Is this needed? Or could I just create my own "update.zip" style file to install via CWRecovery; su, Superuser.apk, and busybox through the "updater-script" commands that I am used to?
Ted,

Actually, things are a little different than what it first seems () re. what is going on with this particular flashable su.zip file. There are two very interesting little twists that the authors of this file have implemented and there's nothing unusual involving ICS or even ClockworkMod.

The first twist is the Superuser-3.0.7-efgh-signed.zip file contained within the su.zip. It is a little bit of a red-herring in that while it is indeed a flashable .zip file on its own (at your own risk, of course), it is simply a payload file for the overall su.zip file and it is from here that the su binary and the Superuser.apk file is taken from (and where you would put a busybox if you were so inclined).

The second twist is the real beauty: the update-binary that "belongs" to the su.zip file is actually a shell script and not a compiled binary file at all. It is this file that controls the actions of what takes place when the su.zip file is being flashed--all without the need for the usual updater-script file.

Let me know if you want me to post the one I built and tested with up here...just remember if you do build a "traditional" flashable script that I think CWM now uses the edify format vs. the old ammend format.

Cheers!
scary alien is online now  
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
teddyearp (December 26th, 2011)
Old December 26th, 2011, 11:23 PM   #4 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,160
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 685
Thanked 704 Times in 430 Posts
Default

Quote:
Originally Posted by scary alien View Post
Ted,

Actually, things are a little different than what it first seems () re. what is going on with this particular flashable su.zip file. There are two very interesting little twists that the authors of this file have implemented and there's nothing unusual involving ICS or even ClockworkMod.

The first twist is the Superuser-3.0.7-efgh-signed.zip file contained within the su.zip. It is a little bit of a red-herring in that while it is indeed a flashable .zip file on its own (at your own risk, of course), it is simply a payload file for the overall su.zip file and it is from here that the su binary and the Superuser.apk file is taken from (and where you would put a busybox if you were so inclined).

The second twist is the real beauty: the update-binary that "belongs" to the su.zip file is actually a shell script and not a compiled binary file at all. It is this file that controls the actions of what takes place when the su.zip file is being flashed--all without the need for the usual updater-script file.

Let me know if you want me to post the one I built and tested with up here...just remember if you do build a "traditional" flashable script that I think CWM now uses the edify format vs. the old amend format.

Cheers!
Sean, ah yes, now I see.

For the readers, this may get way over your head, but if you are so inclined you can learn as well . . . . however, much reading before posting should be a requisite.

Scary, the reason I asked, as you well may know, is because in other 'update.zip' style files, the 'update-binary' file was just that, in binary code. But I have had great success using notepad++ to view/edit/modify the 'updater-script' file to my liking and purposes. But now you have enlightened me. The 'update-binary' file in the root /META-INF/com/google/android directory of this particular file is in fact a script that one can view via notepad++.

And for future reader/learners. 'Google' Notepad++, install it, learn how and when to use it, and profit.

Read more, post less.

So that said, even though you say it's not an ICS, nor a CWR thing, I guess I will go ahead and modify the /META-INF/com/google/android/updater-script file within the Superuser-3.0.7-efgh-signed.zip file to include an install of busybox as well. As that is my whole goal. No sense rooting your phone without installing busybox at the same time.

That is why I made my own reservation in this thread in post #4, hehe.

Oh and p.s. to scary and the readers. I only know the 'edify' format as that is why it is now called 'updater-script'. With 'ammend' it was called 'update-script'.
teddyearp is offline  
Last edited by teddyearp; December 26th, 2011 at 11:28 PM.
Reply With Quote
Old December 28th, 2011, 07:28 PM   #5 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,160
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 685
Thanked 704 Times in 430 Posts
Default

@scary:

After further looking at your CWRecovery method, I see that you have two different commands to 'push' the "su.zip" file to the phone:
Quote:
adb push su.zip /sdcard/ (notice the trailing forward slash)

-- or --

adb push su.zip /data/media/su.zip
You have a disclaimer/comment about the second command saying it worked better, however, if you modified the first command to be:
Code:
adb push su.zip /sdcard/su.zip
wouldn't that work just as well and negate the need for the second command?

Just saying/asking . . . .
teddyearp is offline  
Reply With Quote
Old December 28th, 2011, 08:18 PM   #6 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by teddyearp View Post
@scary:

After further looking at your CWRecovery method, I see that you have two different commands to 'push' the "su.zip" file to the phone:


You have a disclaimer/comment about the second command saying it worked better, however, if you modified the first command to be:
Code:
adb push su.zip /sdcard/su.zip
wouldn't that work just as well and negate the need for the second command?

Just saying/asking . . . .
Ted,

I experienced many instances while testing the root methods and particularly the one where you flash the su.zip from CWM where pushing the su.zip to the "/sdcard" mount, with and without the filename, didn't make the filename show-up in the list of files that CWM showed as available for flashing.

Using the alternate path when the first worked (or just doing both) always made the file show-up.

I'm thinking that there's some reason why CWM is not always able to get the mount point for "/sdcard" installed by the time one tries to flash a file (perhaps due to its very large size? Dunno).

I might do some testing and watching the recovery.log file to see if there's anything reported in there that would tell the tale.

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

Thanks: 685
Thanked 704 Times in 430 Posts
Default

@scary: Thanks for putting up with my incessant questions about the SCHi515; especially since i have yet to get this device in my hands.

Unless I see a Motoroogle Developer device available when I finally have the funds to buy this one (~30 days from now), I hope to be able to 'pay it forward' with my own hands on experience(s). And if it goes that way, maybe I/we can figure out where exactly on the phone's internal storage is the partition that CWR 'sees' as "/sdcard/".
teddyearp is offline  
Last edited by teddyearp; December 29th, 2011 at 10:41 PM.
Reply With Quote
Old December 30th, 2011, 10:51 AM   #8 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by teddyearp View Post
@scary: Thanks for putting up with my incessant questions about the SCHi515; especially since i have yet to get this device in my hands.

Unless I see a Motoroogle Developer device available when I finally have the funds to buy this one (~30 days from now), I hope to be able to 'pay it forward' with my own hands on experience(s). And if it goes that way, maybe I/we can figure out where exactly on the phone's internal storage is the partition that CWR 'sees' as "/sdcard/".
Ted,

Hey, no problem...this is a fun device to research with and play around with...

As far as the wonky SD card mount issues in ClockworkMod goes, we do already know that /sdcard is soft-linked to /data/media:

Code:
shell@android:/ # ls -a -d -l sdcard
lrwxrwxrwx root root 2011-12-30 02:35 sdcard -> /mnt/sdcard
This happens in the normal Android's init.tuna.rc file here:

Code:
on early-init
        export EXTERNAL_STORAGE /mnt/sdcard
        mkdir /mnt/sdcard 0000 system system
        # for backwards compatibility
        symlink /mnt/sdcard /sdcard
 .
<snip>
 .
# create virtual SD card at /mnt/sdcard, based on the /data/media directory
# daemon will drop to user/group system/media_rw after initializing
# underlying files in /data/media will be created with user and group media_rw (1023)
service sdcard /system/bin/sdcard /data/media 1023 1023
        class late_start
This results in this service running in Android:

Code:
1|shell@android:/ # ps | grep -i sdcard
media_rw 122 1 988 360 c01bfc00 400f3438 S /system/bin/sdcard
shell@android:/ #
that is NOT found running in ClockworkMod custom recovery--indeed, the "virtual SD card" service is not found in the init.rc file of the ramdisk that's packed with CWM and it appears that /sdcard is simply soft-linked to /data/media (although I can't see an obvious place in the ramdisk or in Koush's code where this is done).

Hope that helps .

Cheers!
scary alien is online now  
Reply With Quote
Old January 2nd, 2012, 03:37 PM   #9 (permalink)
Senior Member
 
ToastPwnz's Avatar
 
Join Date: Jul 2010
Posts: 522
 
Device(s): HTC Droid Eris (retired), Verizon Samsung Galaxy Nexus, HP Touchpad
Carrier: Not Provided

Thanks: 51
Thanked 74 Times in 69 Posts
Default

For some strange reason, whenever I go into "choose zip from sdcard" I get
Code:
Couldn't open directory.
No files found.
I've tried both push methods you listed, but I get the same result with both. If it makes any difference, I'm on a Mac and I used the flash method for CWM.
ToastPwnz is offline  
Reply With Quote
Old January 2nd, 2012, 03:42 PM   #10 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by ToastPwnz View Post
For some strange reason, whenever I go into "choose zip from sdcard" I get
Code:
Couldn't open directory.
No files found.
I've tried both push methods you listed, but I get the same result with both. If it makes any difference, I'm on a Mac and I used the flash method for CWM.
Wow...I just keep seeing more and more folks having problems with seeing their SD card files while in ClockworkMod...

Can you just try restarting CWM and seeing if they show-up?

There is a spot that I've seen in the CWM recovery.log file that shows CWM will wait for 20 seconds to allow the mount for the SD card to finish, but since its really just symlink to the /data/media area, that shouldn't take long (unless its really taking a long time for /data to be mounted).

Dunno...try restarting CWM and see if the su.zip file (I'm assuming that's what you're trying to flash) is now present.

Let us know...thanks!
scary alien is online now  
Reply With Quote
sponsored links
Old January 2nd, 2012, 03:46 PM   #11 (permalink)
Senior Member
 
ToastPwnz's Avatar
 
Join Date: Jul 2010
Posts: 522
 
Device(s): HTC Droid Eris (retired), Verizon Samsung Galaxy Nexus, HP Touchpad
Carrier: Not Provided

Thanks: 51
Thanked 74 Times in 69 Posts
Default

Quote:
Originally Posted by scary alien View Post
Wow...I just keep seeing more and more folks having problems with seeing their SD card files while in ClockworkMod...

Can you just try restarting CWM and seeing if they show-up?

There is a spot that I've seen in the CWM recovery.log file that shows CWM will wait for 20 seconds to allow the mount for the SD card to finish, but since its really just symlink to the /data/media area, that shouldn't take long (unless its really taking a long time for /data to be mounted).

Dunno...try restarting CWM and see if the su.zip file (I'm assuming that's what you're trying to flash) is now present.

Let us know...thanks!
Nope :/, same thing.

Code:
ClockworkMod Recovery v5.5.0.4
Couldn't open directory.
Couldn't open directory.
No files found.
ToastPwnz is offline  
Reply With Quote
Old January 2nd, 2012, 03:59 PM   #12 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by ToastPwnz View Post
Nope :/, same thing.

Code:
ClockworkMod Recovery v5.5.0.4
Couldn't open directory.
Couldn't open directory.
No files found.
Wow....don't know what to say...you've got the same version of CWM that I do, 5.5.0.4...are you sure its the VZW/LTE version of CWM? (I'm fishing for any other differences here...).
scary alien is online now  
Reply With Quote
Old January 2nd, 2012, 04:00 PM   #13 (permalink)
Senior Member
 
ToastPwnz's Avatar
 
Join Date: Jul 2010
Posts: 522
 
Device(s): HTC Droid Eris (retired), Verizon Samsung Galaxy Nexus, HP Touchpad
Carrier: Not Provided

Thanks: 51
Thanked 74 Times in 69 Posts
Default

Quote:
Originally Posted by scary alien View Post
Wow....don't know what to say...you've got the same version of CWM that I do, 5.5.0.4...are you sure its the VZW/LTE version of CWM? (I'm fishing for any other differences here...).
Should be, I downloaded it from the link in this thread.

http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img
ToastPwnz is offline  
Reply With Quote
Old January 2nd, 2012, 04:05 PM   #14 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by ToastPwnz View Post
Should be, I downloaded it from the link in this thread.

http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img
Yep, that's the right one...

How about this...try rebooting back into CWM and give it a minute or two before trying the "chooze zip from sdcard" thing...

Maybe it just needs more time for the mount of /data to finish...?

I'm pretty sure the early times that I had problems with testing of trying to push the su.zip file to the SD card, I was doing things pretty quickly and tried to invoke that function pretty soon after I started-up CWM.
scary alien is online now  
Reply With Quote
Old January 2nd, 2012, 04:26 PM   #15 (permalink)
Senior Member
 
ToastPwnz's Avatar
 
Join Date: Jul 2010
Posts: 522
 
Device(s): HTC Droid Eris (retired), Verizon Samsung Galaxy Nexus, HP Touchpad
Carrier: Not Provided

Thanks: 51
Thanked 74 Times in 69 Posts
Default

Quote:
Originally Posted by scary alien View Post
Yep, that's the right one...

How about this...try rebooting back into CWM and give it a minute or two before trying the "chooze zip from sdcard" thing...

Maybe it just needs more time for the mount of /data to finish...?

I'm pretty sure the early times that I had problems with testing of trying to push the su.zip file to the SD card, I was doing things pretty quickly and tried to invoke that function pretty soon after I started-up CWM.
Nope, that doesn't work either. :/
Well, looks like I won't be able to root. Bleh.
ToastPwnz is offline  
Reply With Quote
Old January 2nd, 2012, 04:29 PM   #16 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by ToastPwnz View Post
Nope, that doesn't work either. :/
Well, looks like I won't be able to root. Bleh.
You might want to re-flash CWM...maybe (long-shot), you've got a bad download / flash, etc. Can you check the MD5 of the file that you downloaded?

File name: recovery-clockwork-5.5.0.4-toro.img
MD5: b2d31c29b7ef785f9c0802a12264d322
File size: 5,263,360 (bytes)

Easy way would from ROM Manager (there's a free version) where you can flash and then launch CWM from there, too.

Other than that, I'm pretty stumped...
scary alien is online now  
Reply With Quote
Old January 2nd, 2012, 04:32 PM   #17 (permalink)
Senior Member
 
ToastPwnz's Avatar
 
Join Date: Jul 2010
Posts: 522
 
Device(s): HTC Droid Eris (retired), Verizon Samsung Galaxy Nexus, HP Touchpad
Carrier: Not Provided

Thanks: 51
Thanked 74 Times in 69 Posts
Default

Quote:
Originally Posted by scary alien View Post
You might want to re-flash CWM...maybe (long-shot), you've got a bad download / flash, etc. Can you check the MD5 of the file that you downloaded?

File name: recovery-clockwork-5.5.0.4-toro.img
MD5: b2d31c29b7ef785f9c0802a12264d322
File size: 5,263,360 (bytes)

Easy way would from ROM Manager (there's a free version) where you can flash and then launch CWM from there, too.

Other than that, I'm pretty stumped...
Its possible, I can't even get my phone to boot now, it just loops to the "Google" screen with the open padlock repeatedly. I'll try reflashing CWM and hope for the best.

I took it back to stock and I'm reactivating it right now. I might give it another go later tonight, but I'm a tad skeptical now. Thanks for the help.
ToastPwnz is offline  
Last edited by ToastPwnz; January 2nd, 2012 at 05:00 PM.
Reply With Quote
Old January 3rd, 2012, 06:04 PM   #18 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,160
 
Device(s): HTC ® HTC6525LVW, Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 685
Thanked 704 Times in 430 Posts
Default

While I don't have the device yet, and I don't know exactly how far 'back to stock' you took it, but I have read that if you get bootloops, go ahead and boot into recovery and do a factory data reset. That should fix the booting problem. Then you will have to re push the su.zip file, since it will have been wiped. Then try again.

Or there's the manual method(s).

good luck
teddyearp is offline  
Reply With Quote
Old January 3rd, 2012, 06:24 PM   #19 (permalink)
Carpe Cerevisi
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: In The Shadows
Posts: 9,501
 
Device(s): LG G2
Carrier: VZW

Thanks: 4,746
Thanked 6,578 Times in 3,499 Posts
Default

I don't even use push for this phone most times. Hook up phone, locate the device Galaxy Nexus and drag/drop the zip into an open area of the storage. They show up in cwr as contents of "SD card". I don't know much about osx but it works nicely on a windows machine. Might give that a shot if you're having push problems.
iowabowtech is online now  
Reply With Quote
Old January 3rd, 2012, 07:49 PM   #20 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by iowabowtech View Post
I don't even use push for this phone most times. Hook up phone, locate the device Galaxy Nexus and drag/drop the zip into an open area of the storage. They show up in cwr as contents of "SD card". I don't know much about osx but it works nicely on a windows machine. Might give that a shot if you're having push problems.
Wow! I just had a revelation when reading your post, iowabowtech!

It made me think about what I did last night when I was discussing the /sdcard mounts and /data partition clears with Yeahha...

Okay, I think I might have figured-out the issue with pushing files to the /sdcard and why it doesn't work at times.

Here's the deal: the /data partition is not mounted until you've navigated to the Apply update from .zip file on SD card menu and you have selected the "choose zip from sdcard" entry!

You'll notice a slight delay the first time you enter that menu--that's when the /data partition is mounted.

So, you can make sure your symlinked /sdcard is mounted by making it to the Choose a zip to apply menu, selecting "+++++Go Back+++++", pushing your .zip file, and then re-selecting "choose zip from sdcard", your file will be present.

I'm thinking that when you push the file to /sdcard or to /data/media too early, i.e., before /data is actually mounted, that file is lost because its actually being done in the ramdisk and not in the proper /data partition.

It all makes sense now, LOL, I'll update my notes and instructions to reflect this.

I should have seen this earlier and it all fits and is consistent with the behavior that I have observed (and re-tested).

Cheers!
scary alien is online now  
Reply With Quote
The Following 2 Users Say Thank You to scary alien For This Useful Post:
jbdan (July 2nd, 2012), ryancmatchett (January 14th, 2012)
sponsored links
Old January 4th, 2012, 12:18 AM   #21 (permalink)
Senior Member
 
ToastPwnz's Avatar
 
Join Date: Jul 2010
Posts: 522
 
Device(s): HTC Droid Eris (retired), Verizon Samsung Galaxy Nexus, HP Touchpad
Carrier: Not Provided

Thanks: 51
Thanked 74 Times in 69 Posts
Default

Quote:
Originally Posted by teddyearp View Post
While I don't have the device yet, and I don't know exactly how far 'back to stock' you took it, but I have read that if you get bootloops, go ahead and boot into recovery and do a factory data reset. That should fix the booting problem. Then you will have to re push the su.zip file, since it will have been wiped. Then try again.

Or there's the manual method(s).

good luck
All the way back, locked bootloader, stock OS, etc.
I got it figured out and I'm rooted and good to go. It was a really stupid mistake on my part that made it not work. For some reason I'm not surprised.
ToastPwnz is offline  
Reply With Quote
Old January 5th, 2012, 08:38 PM   #22 (permalink)
New Member
 
Join Date: Jan 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Notsure

Quote:
Originally Posted by ToastPwnz View Post
All the way back, locked bootloader, stock OS, etc.
I got it figured out and I'm rooted and good to go. It was a really stupid mistake on my part that made it not work. For some reason I'm not surprised.

What exactly did you do wrong? Im having the same problem.
lumberjake is offline  
Reply With Quote
Old January 5th, 2012, 08:44 PM   #23 (permalink)
Senior Member
 
ToastPwnz's Avatar
 
Join Date: Jul 2010
Posts: 522
 
Device(s): HTC Droid Eris (retired), Verizon Samsung Galaxy Nexus, HP Touchpad
Carrier: Not Provided

Thanks: 51
Thanked 74 Times in 69 Posts
Default

Quote:
Originally Posted by lumberjake View Post
What exactly did you do wrong? Im having the same problem.
I forgot the reboot after unlocking the bootloader.
ToastPwnz is offline  
Reply With Quote
Old January 5th, 2012, 09:20 PM   #24 (permalink)
New Member
 
Join Date: Jan 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by scary alien View Post
Wow! I just had a revelation when reading your post, iowabowtech!

It made me think about what I did last night when I was discussing the /sdcard mounts and /data partition clears with Yeahha...

Okay, I think I might have figured-out the issue with pushing files to the /sdcard and why it doesn't work at times.

Here's the deal: the /data partition is not mounted until you've navigated to the Apply update from .zip file on SD card menu and you have selected the "choose zip from sdcard" entry!

You'll notice a slight delay the first time you enter that menu--that's when the /data partition is mounted.

So, you can make sure your symlinked /sdcard is mounted by making it to the Choose a zip to apply menu, selecting "+++++Go Back+++++", pushing your .zip file, and then re-selecting "choose zip from sdcard", your file will be present.

I'm thinking that when you push the file to /sdcard or to /data/media too early, i.e., before /data is actually mounted, that file is lost because its actually being done in the ramdisk and not in the proper /data partition.

It all makes sense now, LOL, I'll update my notes and instructions to reflect this.

I should have seen this earlier and it all fits and is consistent with the behavior that I have observed (and re-tested).

Cheers!

Ok I got it pushed through. But when I try to flash su.zip it says:

--installing: /sdcard/su.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/su.zip
(Status 0)
Installation aborted.

Any advice?
lumberjake is offline  
Reply With Quote
Old January 5th, 2012, 09:25 PM   #25 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by lumberjake View Post
Ok I got it pushed through. But when I try to flash su.zip it says:

--installing: /sdcard/su.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/su.zip
(Status 0)
Installation aborted.

Any advice?
Jake,

Are you on a Mac or did you unpack the su.zip before transferring it to your phone?

It also could be a bad / incomplete download of that file...that's usually the message you get when the su.zip is not "pristine".

Let me know...we'll figure it out.
scary alien is online now  
Reply With Quote
The Following 2 Users Say Thank You to scary alien For This Useful Post:
lumberjake (January 5th, 2012), umataro42 (June 11th, 2012)
Old January 5th, 2012, 09:47 PM   #26 (permalink)
New Member
 
Join Date: Jan 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by scary alien View Post
Jake,

Are you on a Mac or did you unpack the su.zip before transferring it to your phone?

It also could be a bad / incomplete download of that file...that's usually the message you get when the su.zip is not "pristine".

Let me know...we'll figure it out.

Must have been a bad download.

I find that weird considering computers never make mistakes.

Thanks for your help!!!
lumberjake is offline  
Reply With Quote
The Following User Says Thank You to lumberjake For This Useful Post:
scary alien (January 5th, 2012)
Old January 14th, 2012, 07:20 PM   #27 (permalink)
Senior Member
 
AdrianC14's Avatar
 
Join Date: Dec 2009
Location: California
Posts: 776
 
Device(s): Verizon Samsung Galaxy Nexus
Carrier: Not Provided

Thanks: 41
Thanked 62 Times in 46 Posts
Default

I'm on the step where I have pushed su.zip, but I can't install zip from sd card because in CWM it keeps saying E:can'tmount /sdcard/ and other lines. Please help!!!

EDIT: nvm I just reflashed CWM.
AdrianC14 is offline  
Last edited by AdrianC14; January 14th, 2012 at 07:56 PM.
Reply With Quote
Old January 14th, 2012, 09:30 PM   #28 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by AdrianC14 View Post
I'm on the step where I have pushed su.zip, but I can't install zip from sd card because in CWM it keeps saying E:can'tmount /sdcard/ and other lines. Please help!!!

EDIT: nvm I just reflashed CWM.
Adrian,

Good to hear you got that sorted-out.

FYI, I figured-out a week or so ago that CWM doesn't mount the "SD card" (/sdcard -> /data/media) until you get to the "Select zip from sdcard" menu. Once you are there, its mounted and you can finally get your file pushed over.

I'm sure its because the internal SD card is really soft-linked (symlinked) to /data/media and that doesn't automatically happen like it does on other devices where the /sdcard is actual external memory.

You can also download the su.zip file to the /sdcard before you boot into recovery (i.e., while Android is booted-up normally).

Cheers!
scary alien is online now  
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
AdrianC14 (January 14th, 2012)
Old January 14th, 2012, 10:30 PM   #29 (permalink)
Senior Member
 
ToastPwnz's Avatar
 
Join Date: Jul 2010
Posts: 522
 
Device(s): HTC Droid Eris (retired), Verizon Samsung Galaxy Nexus, HP Touchpad
Carrier: Not Provided

Thanks: 51
Thanked 74 Times in 69 Posts
Default

Quote:
Originally Posted by scary alien View Post
Adrian,

Good to hear you got that sorted-out.

FYI, I figured-out a week or so ago that CWM doesn't mount the "SD card" (/sdcard -> /data/media) until you get to the "Select zip from sdcard" menu. Once you are there, its mounted and you can finally get your file pushed over.

I'm sure its because the internal SD card is really soft-linked (symlinked) to /data/media and that doesn't automatically happen like it does on other devices where the /sdcard is actual external memory.

You can also download the su.zip file to the /sdcard before you boot into recovery (i.e., while Android is booted-up normally).

Cheers!
Thats strange, it was mounted for me before I went into the "Select zip from SD card" menu. That is, after I got past my derp moment.
ToastPwnz is offline  
Reply With Quote
The Following User Says Thank You to ToastPwnz For This Useful Post:
scary alien (January 14th, 2012)
Old January 23rd, 2012, 09:36 AM   #30 (permalink)
Junior Member
 
Join Date: Jan 2010
Posts: 36
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

Are there better ways to do this now? I see several "easy solutions" out there. Not sure if thye are legit.
Parafly9 is offline  
Reply With Quote
sponsored links
Old January 23rd, 2012, 09:44 AM   #31 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by Parafly9 View Post
Are there better ways to do this now? I see several "easy solutions" out there. Not sure if thye are legit.
Wugfresh's root utility (Here you go! One Step Unlock/Root or ReLock/Unroot!) is reportedly very good and easy to use...

That being said, I don't think you can go wrong with using something like the ClockworkMod rooting method--its pretty simple and straightforward and you get to see what is actually going on and do it for yourself.

These are the same steps that will be done for you with the aforementioned utility, but the veils are pulled-back for you and you get to take satisfaction in having done it yourself.

Cheers!
scary alien is online now  
Reply With Quote
Old January 23rd, 2012, 10:39 AM   #32 (permalink)
Junior Member
 
Join Date: Jan 2010
Posts: 36
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

Thanks Scary Alien, I did this earlier with my Thunderbolt, going through the whole ADB process, and my OG Droid before that

At this point I want the quick & easy way. I guess I am kinda lazy, it does help to understand what is happening under the covers !
Parafly9 is offline  
Reply With Quote
The Following User Says Thank You to Parafly9 For This Useful Post:
scary alien (January 23rd, 2012)
Old January 27th, 2012, 10:58 PM   #33 (permalink)
New Member
 
Join Date: Jun 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

This might help some people...

I had the same issue, with a bunch of mounting errors. Even going to "choose zip from sdcard" didn't mount anything. I couldn't push the su.zip successfully because of something I did wrong.

Found out that because I am doing it from a Mac, and I followed this guide to unlock the bootloader from a mac they had instructed me to use ./fastboot-mac instead of ./fastboot

Sure enough, changing ./fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img to ./fastboot-mac flash recovery recovery-clockwork-5.5.0.4-toro.img worked like a charm. Then for good measure, I went to "choose zip from sdcard" first, then pushed, then flashed the zip.

joeymad is offline  
Reply With Quote
Old May 30th, 2012, 07:57 PM   #34 (permalink)
Senior Member
 
jova33's Avatar
 
Join Date: Oct 2011
Location: El Paso
Posts: 1,567
 
Device(s): Samsung Galaxy Nexus VZW Casio G'zOne Commando
Carrier: Not Provided

Thanks: 30
Thanked 181 Times in 152 Posts
Default

why isn't this stickied?
__________________
(VZW) Galaxy Nexus. Nexus 7.
& Casio G'zOne Commando - I just use this as a game system and waterproof camera

I love this script ==> V6 SuperCharger.
jova33 is online now  
Reply With Quote
The Following User Says Thank You to jova33 For This Useful Post:
scary alien (May 30th, 2012)
Old May 30th, 2012, 08:09 PM   #35 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by jova33 View Post
why isn't this stickied?
It was at one time, but then we did a bit of housekeeping and tried to make things not so cluttered.

Its linked in the All-Things-Root guide, though, right? Actually, I see that is not! (it used to be..I'll fix that now).

Thanks for the heads-up!
iowabowtech likes this.
scary alien is online now  
Reply With Quote
Old June 11th, 2012, 12:53 PM   #36 (permalink)
Member
 
Join Date: Aug 2010
Location: San Pedro, CA
Gender: Male
Posts: 286
 
Device(s): Galaxy Nexus (Verizon) Nexus 7 (8GB, WiFi) Motorola Droid (retired / pmp)
Carrier: Verizon Wireless

Thanks: 58
Thanked 61 Times in 47 Posts
Default

Quote:
Originally Posted by lumberjake View Post
Ok I got it pushed through. But when I try to flash su.zip it says:

--installing: /sdcard/su.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/su.zip
(Status 0)
Installation aborted.

Any advice?
Quote:
Originally Posted by scary alien View Post
Jake,

Are you on a Mac or did you unpack the su.zip before transferring it to your phone?

It also could be a bad / incomplete download of that file...that's usually the message you get when the su.zip is not "pristine".

Let me know...we'll figure it out.
I was having the same problem, and in my case it looks like an incomplete download. I downloaded it directly to my phone (twice) and was getting that error. Then I tried downloading it to my computer and copying it to my phone (over USB) and it worked.

Also, extra thanks to Scary Alien since I used your Root Toolkit app to apply and keep Clockwork Recovery.

Quote:
Originally Posted by scary alien View Post
Wugfresh's root utility (Here you go! One Step Unlock/Root or ReLock/Unroot!) is reportedly very good and easy to use...

That being said, I don't think you can go wrong with using something like the ClockworkMod rooting method--its pretty simple and straightforward and you get to see what is actually going on and do it for yourself.

These are the same steps that will be done for you with the aforementioned utility, but the veils are pulled-back for you and you get to take satisfaction in having done it yourself.

Cheers!
I was having trouble with Wugfresh's utility - nothing seemed to happen after I tried to root and typed 1 to confirm my device was listed. The Clockwork Recovery method worked right away, once I got a good download of the su.zip file.
scary alien likes this.
umataro42 is offline  
Reply With Quote
The Following User Says Thank You to umataro42 For This Useful Post:
scary alien (June 11th, 2012)
Old July 2nd, 2012, 03:17 AM   #37 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Question Unable to flash CWM file

sorry in advance; first-timer here. hopefully i use the right terminology!

i've unlocked the bootloader (super easy). i am now attempting to root on mac, and am getting stuck. i have the adb, fastboot, and cwm files on my desktop. i run:
Code:
cd Desktop
to change the directory to where the files are located.

i then run:
Code:
./fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
to flash the file, but it says file or directory not found.

suggestions?

EDIT: nevermind. new problem.

i flashed the file just fine. i pushed the su.zip to the device. i applied the .zip file. but when i checked for root (with RootChecker from Google Play), it says no root.

in an attempt to re-apply the su.zip, i tried booting into CWR but all i get is the Android lying down with a red triangle. help!
gdotcom is offline  
Last edited by gdotcom; July 2nd, 2012 at 03:57 AM. Reason: new problem.
Reply With Quote
Old July 2nd, 2012, 10:03 AM   #38 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

gdotcom,

Which version of Android are and you and do you know which su.zip you installed (i.e., which download link)?

There's a newer su.zip that includes an updated su binary that is needed for 4.0.4.

Also, the reason you're seeing the stock recovery is that Android re-flashes the stock recovery upon shutdown unless/until you've renamed a key file to make the recovery "stick".

So, let me know about your Android version and the su.zip download first and we'll get you squared-away with making recovery "stick" (which requires that you be successfully rooted first).

Cheer and welcome to the AndroidForums!
jbdan likes this.
scary alien is online now  
Reply With Quote
Old July 9th, 2012, 10:54 AM   #39 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Stupid question, but here goes.

I unlocked my VZW LTE (On Mac OS 10.7.4) and then ran the install-superboot-mac

It sat on the Google screen for a LONG time, so I took out the battery and it restarted properly.

Now, the stupid question. How do I know it worked and that I am rooted?

ANDROID VERSION
4.0.4

Kernel Version
3.0.8-gda625b
android-build@vpbs1 #1
SMP PREEMPT Fri Apr 13

BUILD
IMM76K

I'm not sure what theme or kernel or whatever I should use. I'm new to all this. Any suggestions would be great!!
natattack06 is offline  
Last edited by natattack06; July 9th, 2012 at 11:43 AM. Reason: Added more questions...
Reply With Quote
Old July 9th, 2012, 11:39 AM   #40 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Welcome to the AndroidForums, natattack06 .

I seem to remember that this is how the Superboot worked on some devices...it probably hung because it was a maguro boot.img instead of the toro one (which is okay if you soft-booted it).

To see if you obtained root, check your app drawer and see if you now have the Superuser app. Also, you can download an app called Root Checker (free in the Market) or my app (Android Root Toolkit, also free) to check your root status.

As far as themes and ROMs and such goes, I think I would wait for a proper source-compiled version of JellyBean if I were you. The ones that are currently out there are a little wonky for some folks and you're liable to have a much better experience when the devs can build one from Google source.

Cheers and again, welcome!
natattack06 likes this.
scary alien is online now  
Reply With Quote
The Following User Says Thank You to scary alien For This Useful Post:
natattack06 (July 9th, 2012)
sponsored links
Old July 9th, 2012, 11:49 AM   #41 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Thanks for the welcome message!

I have the superuser app but when I first clicked on it, it allowed me in application. Now when I click on it, it keeps sending me to the Play store. Does that mean I have to buy it to move forward?

I have bought SetCPU already and it is requesting root access then errors and saying I need to give it permission in SuperUser

*Update* Root check basic says "this device does not have proper root access"
natattack06 is offline  
Last edited by natattack06; July 9th, 2012 at 11:55 AM.
Reply With Quote
Old July 9th, 2012, 11:53 AM   #42 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by natattack06 View Post
Thanks for the welcome message!

I have the superuser app but when I first clicked on it, it allowed me in application. Now when I click on it, it keeps sending me to the Play store. Does that mean I have to buy it to move forward?

I have bought SetCPU already and it is requesting root access then errors and saying I need to give it permission in SuperUser
Yeah, you don't typically need to run/launch the Superuser app itself--it will get called when you try to use another app that requires root access, like you are seeing with SetCPU.

After launching SetCPU, you should be presented with a prompt that actually comes from the Superuser app, asking if you want to allow root access to SetCPU (or whatever app you happen to be trying to use its root access for).

Did you not receive such a prompt or did you tell it "no" (or deny)?
scary alien is online now  
Reply With Quote
Old July 9th, 2012, 12:12 PM   #43 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by scary alien View Post
Yeah, you don't typically need to run/launch the Superuser app itself--it will get called when you try to use another app that requires root access, like you are seeing with SetCPU.

After launching SetCPU, you should be presented with a prompt that actually comes from the Superuser app, asking if you want to allow root access to SetCPU (or whatever app you happen to be trying to use its root access for).

Did you not receive such a prompt or did you tell it "no" (or deny)?
I did get a prompt, it said root was not setup.

I ran the Root checker, and it appears root cannot be verified :/
natattack06 is offline  
Reply With Quote
Old July 9th, 2012, 12:23 PM   #44 (permalink)
not really so scary
Thread Author (OP)
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 16,625
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 30,664
Thanked 14,098 Times in 6,888 Posts
Default

Quote:
Originally Posted by natattack06 View Post
I did get a prompt, it said root was not setup.

I ran the Root checker, and it appears root cannot be verified :/
It appears that the Superboot root install didn't work for you.

The ClockworkMod root install image is actually very simple and straightforward (since I'm guessing you can't use Wug's toolkit due to using a Mac).

Be sure to use the newer su.zip that works best with ICS 4.0.4 (I included references to that in the documentation in the first post).

Give it at least a read through and let me know if you have any questions.
scary alien is online now  
Reply With Quote
Old September 24th, 2012, 01:37 PM   #45 (permalink)
Junior Member
 
Join Date: Dec 2011
Posts: 15
 
Device(s): Galaxy Nexus (Verizon)
Carrier: Not Provided

Thanks: 11
Thanked 2 Times in 2 Posts
Default

So I used this method before on ICS, successfully, but I just got the JB update and wanted to root using this method, and apparently it doesn't work on JB. Is there a new su.zip file necessary for use on JB? Please advise, and please don't tell me to use Wug's root toolkit. I'm anal about this kind of thing; I want to do it myself, not have it automated.

Thanks in advance for any help, and thanks to ScaryAlien for all of his useful posts that I've profited from in the past year!
scary alien likes this.
bevardimus is offline  
Reply With Quote
The Following User Says Thank You to bevardimus For This Useful Post:
scary alien (September 24th, 2012)
Old September 24th, 2012, 01:42 PM   #46 (permalink)
Member
 
mmolitor87's Avatar
 
Join Date: Jul 2010
Location: Collinsville, IL, USA
Posts: 334
 
Device(s): Samsung Galaxy Nexus (Verizon), Rooted HTC Incredible (Retired)
Carrier: Not Provided

Thanks: 32
Thanked 112 Times in 69 Posts
Default

Quote:
Originally Posted by bevardimus View Post
Is there a new su.zip file necessary for use on JB?
This, exactly. http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip

Quote:
Originally Posted by bevardimus View Post
Please advise, and please don't tell me to use Wug's root toolkit. I'm anal about this kind of thing; I want to do it myself, not have it automated.
I think I love you. No homo, though. I'm really tired of seeing "use a root toolkit".
mmolitor87 is offline  
Reply With Quote
The Following User Says Thank You to mmolitor87 For This Useful Post:
bevardimus (September 24th, 2012)
Old September 24th, 2012, 01:56 PM   #47 (permalink)
Junior Member
 
Join Date: Dec 2011
Posts: 15
 
Device(s): Galaxy Nexus (Verizon)
Carrier: Not Provided

Thanks: 11
Thanked 2 Times in 2 Posts
Default

That did the trick! Thanks a bunch, and holy hell that was a fast reply!
mmolitor87 likes this.
bevardimus is offline  
Reply With Quote
Old September 24th, 2012, 02:01 PM   #48 (permalink)
Member
 
mmolitor87's Avatar
 
Join Date: Jul 2010
Location: Collinsville, IL, USA
Posts: 334
 
Device(s): Samsung Galaxy Nexus (Verizon), Rooted HTC Incredible (Retired)
Carrier: Not Provided

Thanks: 32
Thanked 112 Times in 69 Posts
Default

Welcome. I'm extremely bored lol. I work nights on the weekends but days during the week...this is one of my days of staying up a long time.
mmolitor87 is offline  
Reply With Quote
Old September 24th, 2012, 02:50 PM   #49 (permalink)
Junior Member
 
Join Date: Dec 2011
Posts: 15
 
Device(s): Galaxy Nexus (Verizon)
Carrier: Not Provided

Thanks: 11
Thanked 2 Times in 2 Posts
Default

Arrrggg... so now that I'm rooted (on stock JB that was JUST released by Verizon), I am running into one of the main issues I was having with all the JB custom roms that made me decide to go to stock -- the long boot time. It gets stuck on the google logo for anywhere between about 3-6 minutes before booting. This is a pain in my ass. WHY does this happen? Does anybody know how to solve this issue?
bevardimus is offline  
Reply With Quote
Old September 24th, 2012, 03:01 PM   #50 (permalink)
Member
 
mmolitor87's Avatar
 
Join Date: Jul 2010
Location: Collinsville, IL, USA
Posts: 334
 
Device(s): Samsung Galaxy Nexus (Verizon), Rooted HTC Incredible (Retired)
Carrier: Not Provided

Thanks: 32
Thanked 112 Times in 69 Posts
Default

Wipe your cache and davlik cache in cwm. That might help it out.
mmolitor87 is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > Samsung Galaxy Nexus > (Verizon) Galaxy Nexus - All Things Root
Thread Tools

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



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