• 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

I'm having the same problem
"adbd cannot run as root in production builds"

is this a pattern or did we both mess up somewhere? this is after unlocking the bootloader

Same here. Did the 2nd (slightly easier) method and everything went completely fine until the last step where you enter the adb commands. It shows the device as connected and everything, but I get the production build message.
 
Upvote 0
**?? Also has anybody successfully used this boot.img with the LTE version? dont want it to be GSM only and then I brick this thing before I even get to use it

SO I just answered my own question... guys DO NOT use the boot.img in the OP just tried booting onto it and now I'm stuck in a boot loop at the Google screen... waiting for help over on xda too for an LTE bootimage cause I can get into the loader but stuck on the Google screen. FFFFFUUUUUUUU
 
  • Like
Reactions: raneff
Upvote 0
SO I just answered my own question... guys DO NOT use the boot.img in the OP just tried booting onto it and now I'm stuck in a boot loop at the Google screen... waiting for help over on xda too for an LTE bootimage cause I can get into the loader but stuck on the Google screen. FFFFFUUUUUUUU

i flashed the boot.img and it booted fine. did a factory reset.

went in and turned back on USB Debugging but now it wont let me run adb root or any other commands.

adb devices list the device though
 
  • Like
Reactions: billtvshow
Upvote 0
So just let it keep bootlooping?? Doesnt seem normal

tumblr_l8n0o4phHQ1qa7fnto1_500.jpg
 
Upvote 0
So the root method is not working right now? I was going to use the 2nd method... The slightly easier method... Should I not try it or at what point should I stop?

People were having trouble with the USB drivers from the beginning.

I made it all the way to the boot.img...

It successfully unlocked the bootloader and did the factory wipe.. Now I am stuck.

Im not suggesting anything but I got the worst part out of the way. The mandatory factory wipe. Now I can set it up and root it later without having to reset...

Not saying you should though as someone said he might have gotten into a bootloop by flashing the boot.img
 
Upvote 0
So the root method is not working right now? I was going to use the 2nd method... The slightly easier method... Should I not try it or at what point should I stop?

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.
 
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