Related
This post is now deprecated there are new ways of rooting more easily here is the link to one of those
http://forum.xda-developers.com/showthread.php?t=1392310
just kept for reference
link no longer works as it is a very old boot img, if you wanna go this way use latest superboot
Rooting your Galaxy Nexus
Download this file contains necessary files and also lastest samsung drivers in case you dont have them, probably you need android sdk drivers for fastboot
Download
credit to @peteralfonso for the insecure boot.img which allows this to remount system and this way install su binary and Superuser.apk
This are the instructions for Galaxy Nexus
they require basic knowledge of fastboot adb and using command prompt/terminal
works same way on linux and windows
Be sure to have fastboot and adb ready and working
extract somewhere and you will get 4 files su, Superuser.apk , boot.img and drivers
turn off the phone
Boot into bootloader mode (Vol UP+ Vol Down + Power) then execute this command, be sure to have fastboot and boot.img on same folder or be ready to type a long path pointing to your boot.img
REMINDER: by doing fastboot oem unlock you will completely wipe your device so be sure to backup anything important
execute this command
Code:
fastboot oem unlock
fastboot boot boot.img
edit: thanks chirality forgot the oem unlock
the device will reboot and start in unsafe mode where you can enable adb as root usually on production devices this is not posible
Be sure to enable adb debugging on menu
back to command prompt
Code:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
and you are done and youve got your Galaxy Nexus rooted
This process does not involve flashing another boot.img, it just boots once with it and after that returns to original boot.img
As usual
YOU ARE PERFORMING THIS AT YOUR OWN RISK! I AM NOT RESPOSIBLE FOR ANY BRICKS OR PROBLEMS!
Which wont happen we are just pushing 2 files to our phone
edit2: sorry for the bad paths of adb was too late and didnt notice my error
Don't you have to do "fastboot oem unlock" first before being able to boot off the insecure image? I thought they fixed that with the Nexus S already.
Thanks for the post - apparently people are having problems with the Superboot method, so I'll give this a go when mine arrives today.
I guess this comes with all the usual "at your own risk" and "will void your warranty" warnings?
(sorry if that's a stupid question - this is my first Nexus, so I'm not sure where I stand on rooting, unlocking bootloaders, and the warranty etc.)
Great - worked without issue for me and I can now use the Entree VPN client for connecting into work. (the HD screen is great for remote desktop work)
Minor typo in the permissions lines though - should read:
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
Thanks very much,
Chris.
Thanks for this davioxx for putting together the guide, chriscole for the fixes and @peteralfonso for the insecure boot.img.
I'm now succesfully rooted.
It seems Root Explorer needs an update for the GN though. Only opens in the bottom left corner of the screen for me, and is comprised of static.
Sorry for the newbee question, been quite a while since rooting my nexus one...
Do i need to enable adb debugging on phone menu before executing the fastboot oem unlock code and then enable it again after it reboots and starts in safe mode?
w00t!
Thank you
You may want to change the path names on the chmod part, I blindly followed the instructions and the files were in diffrent places from where I pushed them to
But thanks \o/
I haz root!
Tnx, easy like all nexus devices, now need some you tube for that!
Sent Via My HTC Desire HD
looks pretty simple ... hopefully it will be the same process for us in the States
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
majikdragoon said:
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
Click to expand...
Click to collapse
Are you doing it via adb or fastboot?
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
majikdragoon said:
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
Click to expand...
Click to collapse
Hi probably you dont have the bootloader driver installed, that has to be done manually at least for my win 64 machine, check this thread about that
Set Up ADB, fastboot and drivers Nexus S it is practically the same for your Galaxy Nexus
Oh ok! I'll look at that now. Thanks fellas
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
there isnt a custom recovery yet and stock recovery needs signed recoveries
actually not hard you take 3 mins in all process
Babydoll25 said:
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
Click to expand...
Click to collapse
Babydoll25 said:
Unless there isn't a custom recovery available yet...
Click to expand...
Click to collapse
Ding ding ding.
Also some people don't want to flash a custom recovery anyway.
Sent from my Nexus S using XDA App
Drivers
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
coleburns said:
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
Click to expand...
Click to collapse
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
el3ctrik said:
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks for that, managed to get it working with pdanet.
however when i try to run the adb commands, i get the adbt cannot run as root in production builds
how did you get rooted?
thanks
I have always been able to get ADB working over USB in Clockwork Recovery. Recently I tried out TWRP as an alternative, and I really like it, but I couldn't get ADB to work. Is that just not available in TWRP, or are there other drivers I need to install? Or is there an option I need to enable?
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
I have always been able to get ADB working over USB in Clockwork Recovery. Recently I tried out TWRP as an alternative, and I really like it, but I couldn't get ADB to work. Is that just not available in TWRP, or are there other drivers I need to install? Or is there an option I need to enable?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It should work... What driver are you using?
Mount /data?
Make sure your pushing to /data/media?
Is adb not working period like adb devices returns nothing or it won't push?
Sent from my Galaxy Nexus
Also could you do adb devices? This will show if the adb detects your phone or not. If you see a serial number, then the adb recognizes your phone and you're doing something wrong ( such as wrong command or won't directory)
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
ADB devices works when booted into the OS, and works from CWM. I get nothing listed under ADB devices when in TWRP.
I'm using whatever drivers I installed when I first bought my GNex.
It's TWRP v 2.3.1.0, installed from the Goo Manager app.
EDIT: Odd, I unplugged/replugged the phone and now it does show up in recovery. Maybe it doesn't click in if I reboot with the phone attached.
Let me further amend... it does not appear on adb devices until I open up Windows Device Manager and tell it to scan for hardware changes. Then after about a minute the phone appears in adb devices.
With CWM it appears instantly in adb devices, no delay.
well, post your issue in TWRP [email protected] section
bk201doesntexist said:
well, post your issue in TWRP [email protected] section
Click to expand...
Click to collapse
Where is that thread? I'm also facing the same issue in my ZTE V970M...
Nevermind, sorry for the necroposting. I solved it by installing ZTE Composite ADB Device in the C:\Program Files\ZTE <whatever>\Driver\amd64 folder. Using Win8 x64 btw.
I've never used adb push or pull successfully. I'm trying to pull my CWM backups from the phone to mac. Im on 4.2.1, and CWM backups store in data/media/clockworkmod. No matter how I try [/data/media/clockworkmod/, etc.], I get terminal output of "remote object does not exist". I wonder if this is because it is not the sdcard, and it is protected? Do I need to mount as writable, and how would i issue the pull command in a shell (seems unlikely)? Anybody have any idea why i cannot get this to work?
bodh said:
I've never used adb push or pull successfully. I'm trying to pull my CWM backups from the phone to mac. Im on 4.2.1, and CWM backups store in data/media/clockworkmod. No matter how I try [/data/media/clockworkmod/, etc.], I get terminal output of "remote object does not exist". I wonder if this is because it is not the sdcard, and it is protected? Do I need to mount as writable, and how would i issue the pull command in a shell (seems unlikely)? Anybody have any idea why i cannot get this to work?
Click to expand...
Click to collapse
Since you are on 4.2, your CWM backups should be moved to /data/media/0.
Code:
[I]adb pull /sdcard/clockworkmod[/I]
^should work.
Alternatively,
Code:
adb pull /data/media/0/clockworkmod
^should work as well.
Old ones, yes. New ones will be in /data/media/clockworkmod
Sent from my Galaxy Nexus using xda premium
"Macintosh:3 x09177310519$ ./adb devices
List of devices attached
...002 device
Macintosh:3 x09177310519$ ./adb pull /data/media/0/2LatinImeGoogle.odex
remote object '/data/media/0/2LatinImeGoogle.odex' does not exist
Macintosh:3 x09177310519$ ./adb pull /sdcard/2LatinImeGoogle.odex
2890 KB/s (642672 bytes in 0.217s)
Macintosh:3 x09177310519$ "
I have a backup of my stock keyboard .odex on the sdcard. So why can i pull it from the directory sdcard, but not /data/media/0? This is the essence of my question, since the backups are in data/media.
SOLVED
So after browsing the CWM image thread, I've got a working solution, in case others need this:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Finally, I've been waiting on this for a while.
Again, in case anyone else is looking for this, I've got a second solution: adbd insecure by chainfire.
bodh said:
So after browsing the CWM image thread, I've got a working solution, in case others need this:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Finally, I've been waiting on this for a while.
Again, in case anyone else is looking for this, I've got a second solution: adbd insecure by chainfire.
Click to expand...
Click to collapse
Thanks man, just what i needed
bodh said:
So after browsing the CWM image thread, I've got a working solution, in case others need this:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Finally, I've been waiting on this for a while.
Again, in case anyone else is looking for this, I've got a second solution: adbd insecure by chainfire.
Click to expand...
Click to collapse
Thanks,I'm it,but i dont know why cannot copy /data/media/clockworkmod?
bodh said:
So after browsing the CWM image thread, I've got a working solution, in case others need this:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Finally, I've been waiting on this for a while.
Again, in case anyone else is looking for this, I've got a second solution: adbd insecure by chainfire.
Click to expand...
Click to collapse
Old but still helpful ! Thanks!
It worked for me using "adb pull /mnt/shell/emulated/clockworkmod/backup C:\nandroid"
bodh said:
./adb pull /mnt/shell/emulated/clockworkmod/
pull: building file list...
Click to expand...
Click to collapse
Still helpful! I wonder why the intuitive command does not work?! Something to do with permissions maybe?
My kf2 was working fine but I ran out of room to install apps. I deleted unneeded apps still not enough room. I booted into twrp did a full wipe and now I can't side-load any roms to install. Twrp shows no OS installed. It will boot into twrp fine but nothing else. I have a fastboot cable. My computer recognizes my kf2 as an adb device but I can't seen to get anything to load. Some of the commands in KFFAID work but not all. I am trying to load cm11 and kitkat back. Any help would be appreciated.
James
getnby said:
My kf2 was working fine but I ran out of room to install apps. I deleted unneeded apps still not enough room. I booted into twrp did a full wipe and now I can't side-load any roms to install. Twrp shows no OS installed. It will boot into twrp fine but nothing else. I have a fastboot cable. My computer recognizes my kf2 as an adb device but I can't seen to get anything to load. Some of the commands in KFFAID work but not all. I am trying to load cm11 and kitkat back. Any help would be appreciated.
James
Click to expand...
Click to collapse
if sideload doesnt work then just do this, put the rom you want to flash and its gapps in the folder that adb is in, and run this while booted into twrp: adb push romnamegoeshere /sdcard/
then you can install the rom from inside twrp
didn't work
stunts513 said:
if sideload doesnt work then just do this, put the rom you want to flash and its gapps in the folder that adb is in, and run this while booted into twrp: adb push romnamegoeshere /sdcard/
then you can install the rom from inside twrp
Click to expand...
Click to collapse
Here is what happened. It said the device was not found. In the device manager it shows adb device under kindle fire.
Look on your task manager and kill every instance of adb.exe that you see and try again, I had that happen before when multiple instances were running. As long as it is in twrp then adb should work. If it continues to not work then uninstall the adb driver and if you see the MTP kindle device still there remove it as well, there might be a composite device that needs removing too, I find it a pita going between fastboot, recovery and whatever ROM os flashed if I use windows because of this, the drivers constantly have to be reinstalled when you change modes for me, hence why I avoid working with my kindle in windows and instead just use Linux. If you see any USB composite devices, check the hardware id's for a vid of 1949, if it has that then feel free to uninstall it. This may sound a bit complex, if you need more of an explanation just tell me.
Sent from my Amazon Kindle Fire HD using Tapatalk
No luck
stunts513 said:
Look on your task manager and kill every instance of adb.exe that you see and try again, I had that happen before when multiple instances were running. As long as it is in twrp then adb should work. If it continues to not work then uninstall the adb driver and if you see the MTP kindle device still there remove it as well, there might be a composite device that needs removing too, I find it a pita going between fastboot, recovery and whatever ROM os flashed if I use windows because of this, the drivers constantly have to be reinstalled when you change modes for me, hence why I avoid working with my kindle in windows and instead just use Linux. If you see any USB composite devices, check the hardware id's for a vid of 1949, if it has that then feel free to uninstall it. This may sound a bit complex, if you need more of an explanation just tell me.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
My computer only recognizes the kindle as an adb device in fastboot mode. I haven't been able to use any of the adb commands on it with any luck. It says device not found. This only shows in kffaid version 4.1.87-beta.
*facepalm* you don't use adb commands with fastboot, you use fastboot commands with fastboot. When it is in twrp it should have adb access though...
Sent from my Amazon Kindle Fire HD using Tapatalk
I think I have a driver issue. I forgot to thank you for your help. If I could send the zip rom and gapps I could get it back to where it was. Is there anyway to start all over from the original kindle OS at this point?
Thanks you
You coukd restore it in fastboot using kffa but it seems like unnecessary work. I would boot a ubuntu 13.10 live cd/usb and just attempt it from there since there won't be any driver issues.
Sent from my LG-P769 using Tapatalk
I tried Ubuntu 12.04 LTS and it was to much trouble. I will try Ubuntu 13.10. I will have to learn the commands to use it.
Thanks
getnby said:
I tried Ubuntu 12.04 LTS and it was to much trouble. I will try Ubuntu 13.10. I will have to learn the commands to use it.
Thanks
Click to expand...
Click to collapse
these commands should do the trick assuming the repos are all active in the downloadable section of the software updates control panel.
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
and after that the fastboot command will work but keep in mind to give it superuser privis with sudo or it probably wont work, i had forgotten that recently on my own pc since i don't deal with fastboot too often. ex: sudo fastboot -i 0x1949 getvar product
I had to work all weekend. I tried to get access through ubuntu 13.10. I used the commands you provided (sudo apt-get update). This command worked fine. When I used this command (sudo apt-get install android-tools-fastboot) It said I had to enable universe. I did some research and got that working and tried to use this command again (sudo apt-get install android-tools-fastboot) then this one worked fine. Then I tried the last command with my kindle in fastboot mode flashing green light (sudo fastboot -i 0x1949 getvar product ). The message was cannot connect to otter-2 ... device. Same thing I have been getting all along.
I think when I wiped the system I cleared all the software to connect to any external device. I don't know if I can even get access to restore the original OS. If you haven't guessed by now I an a noob. I think you realized that with my adb commands with fastboot enabled. I got the impression you knew when I saw the *facepalm* comment the the beginning of you post. When my kindle is booted to twrp my computer does not recognize it. My computer will recognize as an adb device when in fastboot mode. My computer will recognize it as a kindle (with a yellow triangle in the device manager) when it is trying to boot with the white and blue logo. I don't know what to do at this point. Here is a screen shot with adb side load from twrp.
Interesting, seems that data didn't want to mount. Have you tried adb from Linux while in twrp? Just run "sudo apt-get install android-tools-adb" to install the command, if you can get adb access at least then I may be able to help fix this depending on what exactly is wrong. BTW I didn't exactly think you were a noon with that facepalm, I just see people get that misconception a lot about adb and fastboot commands. What exactly did that fastboot command report back, I was surprised it was an error when I saw otter2 in the error considering that was what that command was sort of supposed to report back.
Sent from my Amazon Kindle Fire HD using Tapatalk
Here is where I am. See below. Now where do I put the file in ubuntu so I can access it from the terminal window. I am running ubuntu from a live CD. I tried the push command but it says no such file or directory. I told you I was a noob!
[email protected]:~$ adb devices
List of devices attached
0123456789ABCDEF recovery
Since adb is in a system path must out it in the current directory you are CD'd into, if you left the terminal alone it should be in ~ (the home folder of the Ubuntu account) so photo the home folder and drop it in there and run "adb push filename /sdcard/"
Considering that /data doesn't want to mount and that /sdcard os technically in /data, that command might not work depending on what's going on. I reccomend seeing if you can first and if not goto the months and mount /cache if its not mounted already, and they pushing a twrp update into it to try to reflash twrp, its small enough I think it should fit into the cache, though I don't think a ROM would fit.
Sent from my Amazon Kindle Fire HD using Tapatalk
I installed ubuntu on my laptop with windows 7. It seems to work better. I put the files in the home folder and the user folder. I mounted the cache and ubuntu said instead of unable to mount it was unable to access kindle now. Here is the terminal window results.
[email protected]:~$ sudo apt-get install android-tools-adb
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
android-tools-adb is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[email protected]:~$ adb push cm-10.2-20130908-UNOFFICAL-otter2.zip /sdcard/
cannot stat 'cm-10.2-20130908-UNOFFICAL-otter2.zip': No such file or directory
[email protected]:~$
Um OK well the filenames are case sensitive in Linux so lookout for that. Also if it was in your home folder then it should have worked as long as you didn't CD anywhere else in the terminal first.
Sent from my Amazon Kindle Fire HD using Tapatalk
Problem Fixed
I fixed my problem. I had to restart my kindle into recovery mode and connect the fastboot cable to the computer and kindle before it booted into TWRP. At that point while booted into TWRP I used the push command in ebuntu terminal to sideload cm11 and gapps. After I loaded them I installed them with TWRP and rebooted. Now it is restored to where it was when I wiped it. I will not do the advanced wipe again.
adb push cm-11-20140202-NIGHTLY-otter2.zip /sdcard/
adb push gapps-kk-20131119.zip /sdcard/
Thanks for your help stunts513
Click to expand...
Click to collapse
Let me start by first saying that "adb root" is not related to or the same thing as running adb shell then su. adb root is a way to run adb directly in root mode enabling to be able to push/pull files directly to /system, or other write protected directories. So please, lets not get into the whole "just copy to sdcard, mount system and cp file with adb shell." This is not what I am trying to accomplish. Now that that's out of the way, here is my situation. HTC10 Viper 4.4.0 US unlocked firmware. Generally speaking, in the past you could modify the boot.img and edit default.prop and set ro.debuggable=1 and/or ro.secure=0 and repack and flash. Problem solved. This does not seem to be the case now, with this device. I also tried compiling from source adbd from aosp, modified to ignore ro.secure etc... Packed it in the boot.img and reflashed. I get the same results. I get a message on boot about slow charging, and debugging mode is not running on the phone. Tried stopping and starting it, same thing. Can anyone please help me figure out what is going on? I assume HTC has some built in security check that disallows this modification, but im not sure. Thank you in advance.