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 just bought a Galaxy Nexus but it was from Hong Kong and had non Yakju firmware on it. I want to install Yakju 4.0.2. I'm on a mac and oem unlocked my Nexus. I have downloaded the firmware from Google for 4.0.2 but now I need help actually installing it. If anyone could write me up a quick step by step guide I'd appreciate it, or link me to one. I'm on a Mac btw.
When I type in "fastboot flash bootloader bootloader-maguro-primekk15.img" into the command prompt it says command not found.
Bump
Sent from my Galaxy Nexus using XDA App
Wondering same thing....
Extract the archive, locate the .sh script, check the directives it contains, run them manually, or use the script.
Alternatively, do what most of us around here have to do, search. It's been covered already a number of times how to convert to Yakju as well as how to use fastboot on mac.
Edit, for the lazy, in the development section, one of the stickies have a link to this guide: http://forum.xda-developers.com/showthread.php?t=1366806
if you're on a mac, you need to add "./" before the commands in terminal
instead of "fastboot flash bootloader bootloader-maguro-primekk15.img", type in
./fastboot flash bootloader bootloader-maguro-primekk15.img
keep in mind your phone should be in fastboot mode when you do this (power off, then hold vol up + vol down + power"
littleasian said:
if you're on a mac, you need to add "./" before the commands in terminal
instead of "fastboot flash bootloader bootloader-maguro-primekk15.img", type in
./fastboot flash bootloader bootloader-maguro-primekk15.img
keep in mind your phone should be in fastboot mode when you do this (power off, then hold vol up + vol down + power"
Click to expand...
Click to collapse
Not correct, sorry.
You'd be better off following the link I provided above. The correct Mac commands are provided.
xyzulu said:
Not correct, sorry.
You'd be better off following the link I provided above. The correct Mac commands are provided.
Click to expand...
Click to collapse
Haha, thanks man.
Sent from my Galaxy Nexus using XDA App
xyzulu said:
Extract the archive, locate the .sh script, check the directives it contains, run them manually, or use the script.
Alternatively, do what most of us around here have to do, search. It's been covered already a number of times how to convert to Yakju as well as how to use fastboot on mac.
Edit, for the lazy, in the development section, one of the stickies have a link to this guide: http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
I tried to follow that guide and couldn't get it to work. How do you direct the command terminal into the right folder? When they say to put fast boot in that folder do they literally mean just the executable file?
Arcadia310 said:
I tried to follow that guide and couldn't get it to work. How do you direct the command terminal into the right folder?
Click to expand...
Click to collapse
You will probably need to cd into the folder.. ie cd Downloads
When they say to put fast boot in that folder do they literally mean just the executable file?
Click to expand...
Click to collapse
Yes, just the file called fastboot-mac
xyzulu said:
You will probably need to cd into the folder.. ie cd Downloads
Yes, just the file called fastboot-mac
Click to expand...
Click to collapse
Do I just type cd and then the name of the folder?
Sent from my Galaxy Nexus using XDA App
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
neccoguy21 said:
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Know-Fear said:
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Click to expand...
Click to collapse
This is a very helpful way of doing things, but a little too long winded for CWM. But I'm thankful for you taking your time to respond and I'm happy to have this guide handy.
gpfnzl said:
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
Click to expand...
Click to collapse
A similar strategy to know-fear's, but different. Again, thank you very much for your help, but it's not the way I'll handle this one.
ÜBER™ said:
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
Click to expand...
Click to collapse
This was what I was looking for. Thank you so much for your time and help!
Sent from my Galaxy Nexus using xda app-developers app
Long winded perhaps. But it's the same thing for most phones running android. So in essence, once you learn it, you know it for good. I've been using the same method since back in the G-1 days. And honestly, those steps I listed take about 15 seconds to complete. It's just good to be thorough.
So I don't remember having any trouble at all unlocking the bootloader and rooting my original Nexus 7, but things aren't going so smooth this time. Here's what I've done:
1. Downloaded the Kwongger Nexus 7v3 I found here on XDA, unzipped the folder.
2. Turned on the USB debugging after enabling Developer options on my tablet, plugged it into my MAC
3. Opened a terminal, did "CD" (change directory), dragged the folder over to the terminal, and hit enter, and it switched to said directory(the MAC directory within the Kwongger unzipped folder)
4. Tried "fastboot reboot bootloader", "fastboot devices", all I got was "command not found"
5. Manually rebooted the Nexus 7 into bootloader, tried the previous commands, including "fastboot oem unlock", just keep getting the "command not found".
What the heck am I missing here? The MAC info I have found through searching thus far was written for people much more knowledgeable than me. If anyone can help, please put it in as layman's terms as possible. This Mac I'm using is the same one I used to root my Nexus 10, Galaxy Nexus, and original Nexus 7. I have downloaded the SDK or whatever, but don't know if I need that, or what to do with it.
Sorry for the horribly long post, but I wanted to be as clear as possible. Thanks in advance!!!
Add ./ before all the commands.....for example ./fastboot OEM unlock
Sent from my Nexus 7 using xda app-developers app
OP, see this: http://forum.xda-developers.com/showthread.php?t=2388687
Noob again. So I am rooted and I'm currently on build NDE63X on my Verizon 128 gb XL. If i understood the instructions correctly, I have to go back to stock before I can put TWRP on the phone. I know I get the factory images here.
https://developers.google.com/android/images
Do I get the NDE63P image for the phone since that was what was on the phone before I sideloaded the OTA for my current version which is NDE63X or do I just need to download the full image for NDE63X?
Can someone also list the steps needed to accomplish getting phone back to stock? I read Google's instructions and I was a little confused. I understand that I will lose root but should be able to root after installing TWRP since it looks like Chainfire updated the root method for those using TWRP.
Thanks.
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it. ?
Sent from my Pixel XL
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
Thank you. Gonna attempt it this weekend.
Deleted
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Veid71 said:
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Click to expand...
Click to collapse
https://developers.google.com/android/images
Sent from my Pixel XL
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
chipslate said:
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
Click to expand...
Click to collapse
if you are executing the commands, you are in fastboot, not adb.
try fastboot devices
if it doesnt return anything, your computer is not seeing the device.
you will need the computer to see the device in fastboot before you can proceed.
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
first thing to try is to go into fastboot, then unplug the cable, and then plug it back in.
if it is still not recognized, then its either an outdated adb/fastboot issue, or a driver issue (if you are using windows, if not there may be other possibilities).
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
When it finds your phone does it say unauthorized or authorized?
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
chipslate said:
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
Click to expand...
Click to collapse
What happens now when you attempt the next command?
Edit: So after running adb devices, you should be running adb reboot bootloader command next I believe.
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Also, I have the phone in MTP File Transfer mode and USB Debugging enabled.
chipslate said:
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Click to expand...
Click to collapse
You should now use the flash-all command but this is going wipe all of your data.
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
chipslate said:
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
Click to expand...
Click to collapse
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
magestic1995 said:
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
Click to expand...
Click to collapse
It finally worked!!! Thanks again for your help and going back and forth. I finally installed Android Studio and it inserted the ADB drivers at the top of Device manager. Worked like a charm then. Finally, Android 7.1.1 and unlocked bootloader... Bring it on, world!
Congrats! I've only used Android Studio for all this stuff since Im a developer. Congrats on getting it all figured out!
i have been trying to take my pixel xl back to stock but the flash-all.bat script hangs on the part where it should flash the system img zip. it says the file size is to large