Develop Bugs

[HOW TO] Unlock Bootloader & Root GSM Nexus (4.0.x devices only)

I know there a few tutorials already on here, however it seems quite a lot of people are eitiher asking questions about the ADB method, or cannot understand other methods. So i'll try and put it all in one easy to follow tutorial. This is for the latest version on Android 4.0.x.
For this method we are going to use Paul O'Briens Superboot.
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Click to expand...
Click to collapse
APPLY THIS AT YOUR OWN RISK!
Download the latest version of Superboot: DOWNLOAD
You might need the drivers, however its worth getting them anyway as you'll probably need them in the future: DOWNLOAD DRIVERS
If you get you might need the USB drivers: DOWNLOAD
Windows
1) Extract the contents of the above file into C:\root
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up cmd and navigate to by typing to following (Hit enter after each line):
cd C:/
cd root
6) Unlock your bootloader by typing - this will wipe your device!:
fastboot-windows oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, double click:
install-superboot-windows.bat
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
Linux
1) Extract the contents of the above file into a folder
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up terminal and navigate to the folder used in step 1
6) Unlock your bootloader by typing - this will wipe your device!:
./fastboot-linux oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, type the following (Hit enter after each line):
chmod +x install-superboot-linux.sh
./install-superboot-linux.sh
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
OS X
1) Extract the contents of the above file into a folder
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up terminal and navigate to the folder used in step 1
6) Unlock your bootloader by typing - this will wipe your device!:
./fastboot-mac oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, type the following (Hit enter after each line):
chmod +x install-superboot-mac.sh
./install-superboot-mac.sh
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
If i've missed any steps out such as downloading drivers etc, let me know what to add in etc. I did mine on OS X and it didn't require me to install anything extra
Update: it would appear some people are having issues with 4.1 rooting. I'll see what I can find an then update it. For the time being, just reflash the vanilla install and you should be fine. I'd imagine there's an incompatibility between this root and 4.1

Very nice indeed, might be worth doing a tutorial on how to return to stock if there isn't already one out there somewhere. Not many people know that it's possible to Fastboot OEM lock, I've tried it

Yeah I'm going to wait until there's a proper system.img about.
I got mine back to stock, however it was a complete bodge and highly advised against.
Locking the boot loader is the easy bit. It's going back to the default rom
Sent from my iPad 2 using Tapatalk

...but this should be moved to general i think. This subforum will br crowded next months.
sent from a kanged gt-i9000 using Tapatalk

It's based on development so I don't see why. General is anything to do with the phone. Unlocking and rooting is the first step of development
Sent from my iPad 2 using Tapatalk

Thank you for your work.
Just a small correction for your original post.
Instead of
fastboot-windows oem unlock
it's actually:
.\fastboot-windows oem unlock

Cheers. I'll edit that. Didn't work for me like that when I did it on a windows PC, however I'll add it in
Sent from my iPad 2 using Tapatalk

Maybe it worth to mention in the first post that many ppl (including me) had issues with this process, because we had no proper drivers installed first, and for that the solution was installing the newest PDAnet software. After that everything went pretty well.

Aylarth said:
Maybe it worth to mention in the first post that many ppl (including me) had issues with this process, because we had no proper drivers installed first, and for that the solution was installing the newest PDAnet software. After that everything went pretty well.
Click to expand...
Click to collapse
Ah yes. Added
Sent from my Galaxy Nexus using Tapatalk

I'm very new to this so prepare for a stupid question!
I'm trying to run this on a Mac, and when I'm trying to run fastboot oem unlock I get the following:
/Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac: No such file or directory
What could cause this?

helen_xxxx said:
I'm very new to this so prepare for a stupid question!
I'm trying to run this on a Mac, and when I'm trying to run fastboot oem unlock I get the following:
/Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac: No such file or directory
What could cause this?
Click to expand...
Click to collapse
Have you navigated to the folder where the files are located? Stupid question but not sure what you've done
Sent from my Galaxy Nexus using Tapatalk

Evostance said:
Yeah I'm going to wait until there's a proper system.img about.
Click to expand...
Click to collapse
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.

Evostance said:
Have you navigated to the folder where the files are located? Stupid question but not sure what you've done
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.

Oppressa said:
Thank you for your work.
Just a small correction for your original post.
Instead of
fastboot-windows oem unlock
it's actually:
.\fastboot-windows oem unlock
Click to expand...
Click to collapse
I am pretty sure you don't need the .\ on Windows? Only Mac & Linux.

StuMcBill said:
I am pretty sure you don't need the .\ on Windows? Only Mac & Linux.
Click to expand...
Click to collapse
Thats what I thought. Worked without the .\ for me at work as its just an exe

helen_xxxx said:
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.
Click to expand...
Click to collapse
OK, If you files are in the folder r2-galaxynexus-superboot, open terminal and just type (after each line hit enter):
cd /Users/
cd extra_ham/
cd r2-galaxynexus-superboot
./fastboot-mac oem unlock
chandlerweb said:
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.
Click to expand...
Click to collapse
I tried that system.img and it bricked my phone. Couldn't get it to launch, it just hung on the animation. I did a boot to CWM, messed with some stuff and then the phone randomly launched. Its not a stock image, missing all the Google apps etc and the Gallery doesn't work. I think for now though, its the closest thing to a stock image we have

Brilliant thank you, will give it a try.
Think I need to tune up on Unix....

helen_xxxx said:
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.
Click to expand...
Click to collapse
On OSX you can just drag the fastboot-mac file from finder into the terminal window and it will automatically fill in the path for you, then type the rest of the unlock command and hit enter

chandlerweb said:
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.
Click to expand...
Click to collapse
The Droid with triangle actually is stock recovery. When you see it just press power + volume down.
Sent from my Galaxy Nexus using XDA App

I hope the LTE version is as easy to root/unlock as this.
Knowing Verizon though...probably not.

[Video] How to Unlock n Root GNex with Superboot

Credit for the written tutorial goes to sbenson1226
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.

Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith

CDMA problem
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
This is something I would like to know too.

Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?

If you have clockworkmod installed with your stock rom. Once you restart the phone it will wipe clockworkmod and install back the stock recovery.
Sent from my Nexus One using xda premium

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
Yes you can unroot by flashing the system image... it requires adb check out my channel , I'll try to post the video here asap
Sent from my Galaxy Nexus using XDA App

Master K said:
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K
Click to expand...
Click to collapse
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App

mikeacela said:
Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?
Click to expand...
Click to collapse
You will still be able to accept ota
Sent from my Galaxy Nexus using XDA App

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Click to expand...
Click to collapse
I did not pull the USB. I did it twice so I know the lock unlock sequence fixes the phone.
I did the unlock without issue and then when I do install-superboot-windows.bat the phone reboots, I get the Google with the unlocked padlock and there it sits. Well past 5min. I did an adb logcat and I can see it is stuck in a bootloop so I pull the battery and lock and unlock again. I rebooted and the phone started up as if new. As I said i went through all this twice (never pulling the USB) and the same result.

I followed this guide letter by letter and it worked perfectly. BTW I have the LTE nexus

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
never mind

I downloaded both links,
installed the drivers,
made sure the newly files (superboot) where in a file named root on the C:\
rebooted phone in to fastboot, then plugged it into the computer
started command prompt
made sure I was in the C:\root directory
typed in fastboot-windows oem unlock
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
the instructions mention pdanet... I never saw that install anywhere so maybe i am missing a step

I can not get the drivers i downloaded from the link to work. It took forever to run the exe and install them, like an hour, and then the install was unsuccesful.

Epicrean said:
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
Click to expand...
Click to collapse
Had to boot the phone back in to the bootloader and rerun the install-superboot-windows.bat. Then my phone rebooted right away. Been sitting on the Google screen for a while...past 5 minutes...so hopefully it will go through.
EDIT: Waiting 15 minutes and phone was still stuck on the black screen with the while Google logo. Pulled battery and phone booted and was rooted. Odd....

is it just me or the download link is down as of 12/18/11?

Followed instructions (although I got the driver from elsewhere, so didn't need the PDAnet files).
Installed loads of apps and such. Turned phone off, then on again. After I rebooted though, my phone appears not to be rooted anymore. Superuser doesn't seem to do anything (although it's on the phone) and Root Explorer says it is denied root permissions from Superuser.
Downloaded Superuser fix from the market which says my phone isn't rooted.
If I just type the "install blah de blah" command again (IE, missing out the unlock oem as the bootloader should still be unlocked), then will it wipe my phone? Don't really fancy installing all the apps again.
Will this then be permanently rooted?

owenbeals said:
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.
Click to expand...
Click to collapse
Hmmm, this tutorial looks strikingly similar to the one I created at DroidForums. A little credit would be nice - or please completely rewrite it. Thanks.
Sent from my Galaxy Nexus using XDA App

The driver failed to install on my phone...when I reboot into my bootloader it looks a bit different from in the video. Mine just has an android and it says start above it. The oem unlock command fails to do anything as well.
Why is nothing ever simple?
Does your phone need to be connected when you install the samsung drivers on it? Or does it install these drivers after booting into the bootloader?
When I install the samsung drivers on my computer with the phone connected, it says the following:
Android phone: No drivers found
Samsung Mobile USB Composite Device: Ready to use
Samsung Mobile MTP Device: Failed
Samsung Android ADB Interface: Ready to use
When I hold the volume buttons and power it on now, it just goes straight to the google logo...not even getting the android logo with the start option anymore. I think I might have accidentally uninstalled the ADB drivers in my device manager because I saw 2 copies and thought I installed it twice...

Try the PDA net application on your comp, it will properly install the Samsung drivers so you can adb
Sent from my Galaxy Nexus using xda premium

[Video] How to Unlock n Root GNex with Superboot

Credit for the written tutorial goes to sbenson1226
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.

Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith

CDMA problem
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
This is something I would like to know too.

Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?

If you have clockworkmod installed with your stock rom. Once you restart the phone it will wipe clockworkmod and install back the stock recovery.
Sent from my Nexus One using xda premium

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
Yes you can unroot by flashing the system image... it requires adb check out my channel , I'll try to post the video here asap
Sent from my Galaxy Nexus using XDA App

Master K said:
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K
Click to expand...
Click to collapse
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App

mikeacela said:
Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?
Click to expand...
Click to collapse
You will still be able to accept ota
Sent from my Galaxy Nexus using XDA App

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Click to expand...
Click to collapse
I did not pull the USB. I did it twice so I know the lock unlock sequence fixes the phone.
I did the unlock without issue and then when I do install-superboot-windows.bat the phone reboots, I get the Google with the unlocked padlock and there it sits. Well past 5min. I did an adb logcat and I can see it is stuck in a bootloop so I pull the battery and lock and unlock again. I rebooted and the phone started up as if new. As I said i went through all this twice (never pulling the USB) and the same result.

I followed this guide letter by letter and it worked perfectly. BTW I have the LTE nexus

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
never mind

I downloaded both links,
installed the drivers,
made sure the newly files (superboot) where in a file named root on the C:\
rebooted phone in to fastboot, then plugged it into the computer
started command prompt
made sure I was in the C:\root directory
typed in fastboot-windows oem unlock
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
the instructions mention pdanet... I never saw that install anywhere so maybe i am missing a step

I can not get the drivers i downloaded from the link to work. It took forever to run the exe and install them, like an hour, and then the install was unsuccesful.

Epicrean said:
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
Click to expand...
Click to collapse
Had to boot the phone back in to the bootloader and rerun the install-superboot-windows.bat. Then my phone rebooted right away. Been sitting on the Google screen for a while...past 5 minutes...so hopefully it will go through.
EDIT: Waiting 15 minutes and phone was still stuck on the black screen with the while Google logo. Pulled battery and phone booted and was rooted. Odd....

is it just me or the download link is down as of 12/18/11?

Followed instructions (although I got the driver from elsewhere, so didn't need the PDAnet files).
Installed loads of apps and such. Turned phone off, then on again. After I rebooted though, my phone appears not to be rooted anymore. Superuser doesn't seem to do anything (although it's on the phone) and Root Explorer says it is denied root permissions from Superuser.
Downloaded Superuser fix from the market which says my phone isn't rooted.
If I just type the "install blah de blah" command again (IE, missing out the unlock oem as the bootloader should still be unlocked), then will it wipe my phone? Don't really fancy installing all the apps again.
Will this then be permanently rooted?

owenbeals said:
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.
Click to expand...
Click to collapse
Hmmm, this tutorial looks strikingly similar to the one I created at DroidForums. A little credit would be nice - or please completely rewrite it. Thanks.
Sent from my Galaxy Nexus using XDA App

The driver failed to install on my phone...when I reboot into my bootloader it looks a bit different from in the video. Mine just has an android and it says start above it. The oem unlock command fails to do anything as well.
Why is nothing ever simple?
Does your phone need to be connected when you install the samsung drivers on it? Or does it install these drivers after booting into the bootloader?
When I install the samsung drivers on my computer with the phone connected, it says the following:
Android phone: No drivers found
Samsung Mobile USB Composite Device: Ready to use
Samsung Mobile MTP Device: Failed
Samsung Android ADB Interface: Ready to use
When I hold the volume buttons and power it on now, it just goes straight to the google logo...not even getting the android logo with the start option anymore. I think I might have accidentally uninstalled the ADB drivers in my device manager because I saw 2 copies and thought I installed it twice...

Try the PDA net application on your comp, it will properly install the Samsung drivers so you can adb
Sent from my Galaxy Nexus using xda premium

How to root your HTC One X (for Windows, Mac and Linux)

In order to root devices with unlocked bootloaders, I normally post a 'superboot' image. However, at the time of writing, the HTC One X (Tegra3) has an issue with it's bootloader whereby it is unable to 'fastboot boot' images, so this is not possible. The superboot is posted below for when this is resolved, however for now I have also included an alternate method.
I am currently working directly with HTCDev to solve the 'fastboot boot' issue.
Your bootloader must be unlocked via htcdev.com to use these solutions.
EASIEST ROOT METHOD - 'RECOVERY + SUPERSU'
The easiest way to get root is now to install the official ClockworkMod release and then flash the latest SuperSU zip file. This approach is highly recommended (I also recommend running a backup as soon as you've flashed clockworkmod!)
ALTERNATE ROOT METHOD - 'INSECURE BOOT AND ROOT'
This zip file contains an insecure boot image to flash to your device and a script which will then push the root (SuperSU) files to your device. This is only tested on 1.27.401.2 / 1.27.401.7. USE AT YOUR OWN RISK!
Download
InsecureBootAndRoot - DOWNLOAD
How to use InsecureBootAndRoot - Windows, Linux and OSX
- Download the InsecureBootAndRoot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-insecure-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-mac.sh' followed by './install-insecure-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-linux.sh' followed by './install-insecure-linux.sh'
The device will now flash the new boot image and reboot. Keep the device attached to USB and when it has rebooted, ensure USB debugging is enabled - the SuperSU files will then be installed.
CONVENTIONAL ROOT METHOD - 'SUPERBOOT' (currently not functioning on shippping devices).
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot - DOWNLOAD
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
P
PS If you find this useful, details on how to donate if you wish to do so are in the topic at MoDaCo.

Hey Paul, as far as I know, it's possible to flash boot.img via fastboot with htcdev.com unlocked One X http://forum.xda-developers.com/showpost.php?p=24341330&postcount=204

mike1986. said:
Hey Paul, as far as I know, it's possible to flash boot.img via fastboot with htcdev.com unlocked One X http://forum.xda-developers.com/showpost.php?p=24341330&postcount=204
Click to expand...
Click to collapse
yes, flashing works (fastboot flash boot.img), but booting (fastboot boot boot.img) does not

blubbers said:
yes, flashing works (fastboot flash boot.img), but booting (fastboot boot boot.img) does not
Click to expand...
Click to collapse
Ah sorry, haven't spotted Paul mentioned "boot" command only!

Correct.
I am working with HTCDev to solve the 'fastboot boot' issue.
P

Do you know if this will 'unlock' the phone as well? I mean open it too all network carriers...

It will not.
P

Thanks for your quick response. Do you know if there is a way to unlock them?

Hey Paul,
is there any chance to root the phone without unlocking the bootloader/S-OFF.
I know that the .img can be only flashed with S-OFF but it would be cool if you would be able to root the phone without using this way.

Any downsides to using the 'insecure' method? Hoping by the time I get my phone there may be a fix for the usual method anyway.

stanny2k said:
Thanks for your quick response. Do you know if there is a way to unlock them?
Click to expand...
Click to collapse
Not yet that i'm aware of.
torxx said:
Hey Paul,
is there any chance to root the phone without unlocking the bootloader/S-OFF.
I know that the .img can be only flashed with S-OFF but it would be cool if you would be able to root the phone without using this way.
Click to expand...
Click to collapse
This will come in time, but it's not an option yet.
Audioboxer said:
Any downsides to using the 'insecure' method? Hoping by the time I get my phone there may be a fix for the usual method anyway.
Click to expand...
Click to collapse
The only downside is the flash of the boot image overwrites your stock one, although you could in theory flash stock back after rooting (if you can source it for your ROM version).
P

Where can i download 1.27.401.2 / 1.27.401.7???

Sorry, 1.27.401.7 is in limited testing atm.
P

Thank you for providing your root solution to XDA.
Broncogr
Forum Moderator

SuperSU by ChainFire? Or Super User?

ShyamSasi said:
SuperSU by ChainFire? Or Super User?
Click to expand...
Click to collapse
SuperSU.
P
Sent from my HTC One X using Tapatalk

hi paul,
many thanks for your work and your efforts with htcdev!!
could you give me the exact command line for adb-windows how to save the current boot.img before i flash the unsecure image?
thanks again!
paulobrien said:
In order to root devices with unlocked bootloaders, I normally post a 'superboot' image. However, at the time of writing, the HTC One X (Tegra3) has an issue with it's bootloader whereby it is unable to 'fastboot boot' images, so this is not possible. The superboot is posted below for when this is resolved, however for now I have also included an alternate method.
Click to expand...
Click to collapse

i confirmed first solution is working !
I have root acces and mike 1986 ROM onboard
I did s-on by htc dev site

nowy57 said:
i confirmed first solution is working !
I have root acces and mike 1986 ROM onboard
I did s-on by htc dev site
Click to expand...
Click to collapse
How install the recovery ?
Thanks

paulobrien said:
Correct.
I am working with HTCDev to solve the 'fastboot boot' issue.
P
Click to expand...
Click to collapse
hmmmm another bugged bootloader.... thanks for the info... this is a VERY important issue for a kernel dev like me...
please keep us posted

Installing BusyBox + Root only (no CWM)?

Hi guys,
I need your advice related to rooting my Nexus phone I got from Google Play.
I will not install any custom ROM's, I simply need to spoof the carrier to T-Mobile, when I'm in Canada.
That said, I looked at few tutorials and from all of them, this one is mostly recommended:
http://forum.xda-developers.com/showthread.php?t=1529058
Before I proceed, I need your opinion about the tutorial and also if is possible to run on my phone just BusyBox, while rooted.
Thank you for your help.

To run root without CWM...
Simply uze the command "fastboot boot RECOVERYNAME.img" rather than the one in the guide.
This won't write a custom recovery to your phone...but boot into it one time only.

Jubakuba said:
To run rooted...
Simply uze the command "fastboot boot RECOVERYNAME.img" rather than the one in the guide.
Click to expand...
Click to collapse
Thank you. I'll work on it and let you know guys how it went.

Everything went very smooth, no issues. Well the hardest part was to get the right ADB drivers, as I did not wanted to install unsigned drivers. I'm going to work now, will post the drivers info when I come back. For reference, I have now root without CWM.
If I decide to revert back to stock, what is procedure?
I have the bootloader locked now, so I guess opening it again will erase everything including the root files. Let me know please.
Edit: To get the drivers rolling in Windows 7 64bits Ultimate, I used this tutorial.

TECK said:
Everything went very smooth, no issues. Well the hardest part was to get the right ADB drivers, as I did not wanted to install unsigned drivers. I'm going to work now, will post the drivers info when I come back. For reference, I have now root without CWM.
If I decide to revert back to stock, what is procedure?
I have the bootloader locked now, so I guess opening it again will erase everything including the root files. Let me know please.
Click to expand...
Click to collapse
As long as you have root...
http://forum.xda-developers.com/showthread.php?p=27878074
Will unlock/lock without wiping.
And as far as returning to stock...you haven't modified much thus far.
So deleting busybox and then superuser will work...if you haven't modified any system files.
Or you could always flash the stock images (this does erase your "SDcard" and everything will be back to an-out-of-the-box state).
https://developers.google.com/android/nexus/images

Jubakuba said:
Or you could always flash the stock images (this does erase your "SDcard" and everything will be back to an-out-of-the-box state).
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thank you sir. Can you please let me know what is the list of commands?
Edit: I got them from the flash-all.sh shell script.
Nexus Images: https://developers.google.com/android/nexus/images
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
Root Device
1) Unlock the bootloader (if locked):
---
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
---
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
---
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
---
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded):
---
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
---
adb reboot bootloader
fastboot oem lock

http://forum.xda-developers.com/showthread.php?t=1626895
Efrant's guide is perfect here.

I got them from the shell script (see above), thanks.

TECK said:
Edit: I got them from the flash-all.sh shell script.
Click to expand...
Click to collapse
Exactly, its that easy.