• 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

Count me in with the "able to unlock bootloader" and "cannot run as root in production builds"

FWIW, I had received the 4.0.2 OTA update before I attempted all of this.
 
So you are still able to use your phone its just not rooted only unlocked bootloader? that's fine w/ me as long as I can use my phone ;p.

billtvshow said:
I can tell you confidently I did that method perfectly on mine up until the time to enter the adb commands and it gives me the same production build message that others are getting. It did unlock the bootloader with relative ease though, so I'm kind of in civicsisedan's boat in that it's nice to have that wipe out of the way and I'll have to come back and check for updates to get rooted later.
Click to expand...
 
billtvshow said:
I can tell you confidently I did that method perfectly on mine up until the time to enter the adb commands and it gives me the same production build message that others are getting. It did unlock the bootloader with relative ease though, so I'm kind of in civicsisedan's boat in that it's nice to have that wipe out of the way and I'll have to come back and check for updates to get rooted later.
Click to expand...

Wasnt this method just booting the boot.img not necessarily flashing it. So if we restart our phones then its gonna go back to the original boot image.. correct me if I'm wrong
 
bootloader unlocked fine for me, its then when I ran the next command to boot the boot.img it went to the Google screen with the unlock logo, then just goes into a loop and vibrates, Google, Google, Google. Can still get into the bootloader so as long as I can get an LTE boot.img im assuming can still send it from there..

just came across this ..boot loop seems to be an issue lol...
 
I'm not really interested in unlocking the boot loader because I'm not interested in alternate ROMs. I just want root so I can access the command line to use cron and to have my own ringtones as system sounds.

I thought having a Nexus device would make obtaining root access very easy.
 
I got the "production build" hang when I rooted 4.0.1 and just tried again after a reboot. It took the second time no problem. Obviously, I can't speak to the process of rooting 4.0.2, but I know I did NOT loose root during/after the OTA.

Scratch that. Turns out I DID loose root with the OTA. Damn. Gonna have to wait 'til I get home to re-root.
 
Just went to the forum.xda-developers.com/showthread.php?t=1352413 after i got the bootloop of Google and unlocked icon with the OP boot.img (I had Verizon LTE 4.0.2 and bootloop, this FIXED it)

I did all the same steps except fastboot boot boot.superboot.img and I am back to working. Superuser app installed. Currently installing APKs that require root to figure out if it is fully working.
 
residualimages said:
Just went to the forum.xda-developers.com/showthread.php?t=1352413 after i got the bootloop of Google and unlocked icon with the OP boot.img (I had Verizon LTE 4.0.2 and bootloop, this FIXED it)

I did all the same steps except fastboot boot boot.superboot.img and I am back to working. Superuser app installed. Currently installing APKs that require root to figure out if it is fully working.
Click to expand...

So what did you do here exactly?
 
getting stuck at 'fastboot boot boot.img'

i tried fastbooting into CWM and it worked, so i'm guessing there might be some problem with that boot.img maybe?
 
efApple said:
Wasnt this method just booting the boot.img not necessarily flashing it. So if we restart our phones then its gonna go back to the original boot image.. correct me if I'm wrong
Click to expand...

I just unlplugged mine and rebooted it and nothing went wrong, booted up normal speed.

The guide says: note: you are not flashing a new boot image here--you are just soft-booting an unsecured one that will allow the /system partition to be remounted in read/write mode

Of course we weren't able to get those commands to work, so I guess once there is a boot img that will allow us to do that, we would have to do a new soft boot with that img and hopefully the adb commands would work then. That's, of course, assuming it ends up being that simple.
 
For those stuck on Google screen,
Boot into bootloader (Battery pull, vol+/vol-/power)
Tpye - Fastboot oem lock
Fastboot oem unlock
Then restart device.
Originally posted on Rootzwiki (can't find OP at the moment - not me!)
 
Trying to follow here...i'm still on 4.0.1, is there an advantage to NOT updating yet? Is the 4.0.2 what's causing root problems?
 
You must log in or register to reply here.
Back
Top Bottom