Related
[size=+1]THIS THREAD IS OUTDATED!!!!!!!!!!!!! DO NOT USE THIS METHOD TO ROOT UNLESS YOU ARE RUNNING 3.1.[/size]
I recommend using this root method courtesy of solarnz: http://forum.xda-developers.com/showthread.php?t=1242241
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
Follow these instructions after unlocking your Xoom to acquire root access on your Xoom. Comes in handy if you just installed the OTA and lost root.
[size=+1]DOWNLOAD:[/size]
WiFi_RootTool_3.1.zip
[size=+1]SUMMARY[/size]
Pushes Superuser, su, and other root files. Sets correct permissions to enable functioning root
Enables external SD card storage (in /sdcard/external)
Prevents system from over-writing custom recovery
Enables USB On-The-Go
[size=+1]ASSUMPTIONS[/size]
You've unlocked your Xoom (this will wipe your data)
You've downloaded the WiFi_RootTool_3.1.zip
You've downloaded a recent ClockworkMod recovery image to your PC: ClockworkMod Recovery (make sure to download the .img, not the .zip)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
You've configured the Android SDK on your PC, with adb functioning properly
You've downloaded fastboot and have it functioning properly (usually alongside adb in platform-tools)
[size=+1]PROCEDURE[/size]
Read through this once before you do it. After performing step 2 you will have to do step 3 immediately or you will have to repeat step 2.
1. Prepare your SD Card
Using an SD Card reader (or Android phone?), move the XOOM_RootTool_3.1.zip file from your PC to the root of your SD Card. Once that is done, install the SD Card into your Xoom. Alternately you can mount the SD Card through the Xoom in recovery after you boot into recovery in step 3 by selecting 'mounts and storage > mount USB storage'. It's always nice to have options.
2. Flash ClockworkMod recovery.img
Connect the usb cable from your PC to your Xoom. Make sure USB Debugging is activated in the Application settings menu.
Connect the usb cable from your PC to your Xoom.
Open up your command prompt naviagate to the folder with adb, then (change 'XXXXXX-XXXX' in code to match filename):
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
fastboot reboot
3. "Catch the boot" to boot into recovery
This requires some quick reflexes. As soon as you send the 'fastboot reboot' command in the previous step, your device will reboot. You have to boot into recovery right away or your Xoom will reflash the stock recovery over the custom recovery you just installed. Here's how to "catch the boot" and reboot into recovery.
When you see the Motorola logo appear, wait approximately 3 seconds.
Tap the Volume Down button. You should see the words "Android Recovery" appear at the top of the screen. Now tap the Volume Up button to boot into recovery.
If when attempting to "catch the boot" it says 'Starting Fastboot protocol support' then you hit Volume Down too soon. Hold Vol UP + Power to reboot and try again.
4. Flash WiFi_RootTool_3.1.zip
In ClockworkMod Recovery, select "install zip from sdcard"
Select "choose zip from sdcard"
Select "WiFi_RootTool_3.1.zip"
Select "Yes - Install WiFi_RootTool_3.1.zip"
After install select "Reboot System Now"
5. Enjoy root!
Im not an Android noob. Ill give this a shot.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
lrs421 said:
Im not an Android noob. Ill give this a shot.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Click to expand...
Click to collapse
I just added the fact that you have to unlock first! I'll be adding those instructions to the OP right now.
I have to ask. Has this been tested
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
lrs421 said:
I have to ask. Has this been tested
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Click to expand...
Click to collapse
I tested in on my WiFi Xoom and it works perfectly.
Hmm, I'm certain I have the right drivers installed because I successfully unlocked the bootloader last night but now I'm stuck at the "starting fastboot protocal support" screen. Any ideas?
lrs421 said:
Hmm, I'm certain I have the right drivers installed because I successfully unlocked the bootloader last night but now I'm stuck at the "starting fastboot protocal support" screen. Any ideas?
Click to expand...
Click to collapse
This is the screen where you enter your ADB Commands. You should be able to flash the ClockworkMod recovery from that screen. If you have trouble just reboot (Vol UP + Power button)
Make sure you enter "catch the boot" to enter recovery after entering the "fastboot reboot" command.
publicanimal said:
This is the screen where you enter your ADB Commands. You should be able to flash the ClockworkMod recovery from that screen. If you have trouble just reboot (Vol UP + Power button)
Click to expand...
Click to collapse
I got it to reboot in that in doesn't appear to recognize adb commands. Nothing was listed under adb devices for me. Can't be a driver issue because I unlocked the bootloader just fine and usb debugging is enabled.
I just tried adb with the unit powered on and it worked just fine. In the loading fastboot screen, no dice.
lrs421 said:
I got it to reboot in that in doesn't appear to recognize adb commands. Nothing was listed under adb devices for me. Can't be a driver issue because I unlocked the bootloader just fine and usb debugging is enabled.
Click to expand...
Click to collapse
That's weird, because you had to have entered ADB commands from the exact same screen when you unlocked your Xoom last night.
lrs421 said:
I just tried adb with the unit powered on and it worked just fine. In the loading fastboot screen, no dice.
Click to expand...
Click to collapse
Are you sending the adb commands from the Android\android-sdk\platform-tools folder? Do you have fastboot installed in that folder?
publicanimal said:
Are you sending the adb commands from the Android\android-sdk\platform-tools folder? Do you have fastboot installed in that folder?
Click to expand...
Click to collapse
Yup and yup. Trying again.
Ok, I'm business. Flash just completed, recovery installed. Do I now wipe data/factory reset before rebooting?
lrs421 said:
Ok, I'm business. Flash just completed, recovery installed. Do I now wipe data/factory reset before rebooting?
Click to expand...
Click to collapse
Not necessary.
publicanimal said:
Not necessary.
Click to expand...
Click to collapse
Ok, rebooted. SU installed, data intact, downloading busybox now to confirm root.
Ok, all is well. You've done good sir, first lab rat came out unharmed
lrs421 said:
Ok, all is well. You've done good sir, first lab rat came out unharmed
Click to expand...
Click to collapse
I appreciate your intrepidity. Are you on a WIFI or a 3G Xoom?
publicanimal said:
I appreciate your intrepidity. Are you on a WIFI or a 3G Xoom?
Click to expand...
Click to collapse
USA Wifi.....
I just did everything in the post exactly and now i am stuck in a bootloop on the honey comb screen plz help. Using 3g Xoom
emh870621345 said:
I just did it everything and now i am stuck on a boot loop on the honeycomb screen plz help.
Click to expand...
Click to collapse
The first boot might take a while. Perhaps you need to do a factory reset on 3G Xooms? I should have had someone test on a 3G Xoom before saying it would work. You know what they say about assuming.
Taken FROM http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-broken-adb-method-dont-use/
With the big change of YOU WILL BOOT LOOP WAIT FOR ADB TO RESPOND and push all the commands then pull the battery and disconnect your USB cable and reboot normal you should have perm root!
**As always RootzWiki nor myself are responsible if something goes wrong. Root your phone at your own risk with the understanding it will void your warranty and there is always a chance of something going wrong.**
*This method WILL WIPE YOUR DATA*
First download Galaxy Nexus FYA Root Package and extract it to c:\gnexroot (for the purposes of this guide)
Also if you wipe and format remember to re-enable Debug mode before restarting processes listed above.
Method
1. First, navigate to C:\gnexroot and install the Samsung drivers (Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe)
1. If those drivers dont work download pdanet from here http://forum.xda-dev....php?p=19709279 and let pdanet install the drivers for you. Worked for some of us.
2. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode.
3. Navigate again to C:\gnexroot, and hold SHIFT on your keyboard, and right click in the white space. Then, click 'Open command window here'
4. In the command prompt, type:
fastboot oem unlock
You will be prompted to confirm that you wish to unlock the bootloader. You do, of course.
5. Once the bootloader has been unlocked, it's time to boot up the device using the insecure boot.img (ro.secure=0 set in the ramdisk). This essentially means you have permanent root for the duration of this boot session. In order to boot up using that boot image, simply type:
fastboot boot boot.img
Don't expect to see anything wildly different during the boot process - it will boot as normal.
6. Once the phone has booted, in the command prompt window, type the following commands, pressing enter after each line:
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
Again I did NOT write these steps nor did I take credit for this procedure. My goal was to have all this information easy to access here so people don't brick their new device
Edit:
If you get stuck at the google logo and cannot push adb commands, pull the battery and usb cable then reinsert and reboot. If this doesn't work Reboot into recovery and wipe everything and start over.
12/17/2011
If you do a factory restore remember to boot at least once after and re-enable debug mode.
anyone had the issue of not being able to unlock the bootloader?
i ran the command "fastboot oem unlock" and it just sticks at the response: <waiting for device>
but nothing shows on my phone.
aldouse said:
anyone had the issue of not being able to unlock the bootloader?
i ran the command "fastboot oem unlock" and it just sticks at the response: <waiting for device>
but nothing shows on my phone.
Click to expand...
Click to collapse
I would guess your computer is not recognizing the device. Try installing the drivers and connecting the phone to the computer while it is in normal mode not the bootloader. It should install the drivers correctly that way and your computer will then recognize it when you boot into the bootloader and the commands should work.
yea... you are right... it was the samsung drivers not fully loading. re-installed the drivers then doing a windows update showed that there's a new set of samsung drivers on the windows update that needed to be installed. that did the trick.
The superboot method worked just fine for me.
Sent from my Galaxy Nexus using Tapatalk
SomeGuyDude said:
The superboot method worked just fine for me.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
same though I had a bootloop but it did root itself.
Sent from my Galaxy Nexus using Tapatalk
aldouse said:
anyone had the issue of not being able to unlock the bootloader?
i ran the command "fastboot oem unlock" and it just sticks at the response: <waiting for device>
but nothing shows on my phone.
Click to expand...
Click to collapse
You must be in recovery mode. Turn the phone off, press volume up and down as well as power. Keep it there until you're in recovery and then unlock.
Sent from my Galaxy Nexus using Tapatalk
innov8ion said:
You must be in recovery mode. Turn the phone off, press volume up and down as well as power. Keep it there until you're in recovery and then unlock.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Its not recovery mode, but fastboot mode. If you are in recovery fastboot won't be recognized. Looks like he got it fixed by checking his drivers.
can you also use this method for a Verizon Galaxy Nexus???
http://forum.xda-developers.com/showthread.php?t=1392310
is there any difference?
Superboot method actually does the same thing as this method from what I read just one is automatic and one is manual.
Being I didn't see anyone else rooting from Verizon I took the time to figure out a manual method so i can verify each step and figure out issues if I ran in to any. With Superboot its either it works or it doesn't there is no playing with procedures.
This should work for other carriers to, I can only verify it for Verizon though.
I get past <adb reboot bootloader> just fine but then when I do a <fastboot oem unlock> it just says "waiting for device" forever. everything is installed but under my drivers it says;
"Android 1.0" drivers not installed.
plz someone help, ive searched all over the net but only found help for HTC phones and 2007 old posts.
edit: I am in "Fastboot mode"
Update the Samsung ADB driver under device manager while you are sitting in the bootloader. I'm bootlooping after pushing the boot.img
got it working, "Note: 1" under this guide fixed it.
http://forum.xda-developers.com/showthread.php?t=1392310
thanks again XDA!!
GOod. Mine is still bootlooping back to the Google screen with a lock on it.
Booted into recovery, formatted. At least i can boot up now.
fatsix said:
GOod. Mine is still bootlooping back to the Google screen with a lock on it.
Booted into recovery, formatted. At least i can boot up now.
Click to expand...
Click to collapse
Sounds like you didn't successfully unlock your bootloader. Have you resolved this?
Done and rooted. Pushing APK's now.
I would recommend doing a full wipe first. I think something got corrupted during the forced wipe when unlocking.
After wiping, I started over. Unlocked and flashed the boot.img. Got a full normal reboot. Flashed it a second time, and it stayed at the google screen and i could connect to it with ADB. Pushed all the commands and rebooted. Works great.
Thank you.
I assume you need to have adb installed before doing this? Or do the command prompts perform from windows?
Sent from my SCH-I500 using Tapatalk
I had it previously installed. If you download the zip. its already in there, just run it right from the directory you unzip it from.
I would like to return my phone to stock. Locked, unrooted, and available for OTAs. Is there a way to do this yet?
craighwk said:
I would like to return my phone to stock. Locked, unrooted, and available for OTAs. Is there a way to do this yet?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1394051
After you complete that Run:
fastboot oem unlock
From the main instructions and simply relock it.
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
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
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Potetsjokolade said:
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Click to expand...
Click to collapse
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Username invalid said:
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Click to expand...
Click to collapse
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Potetsjokolade said:
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
Click to expand...
Click to collapse
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
bananagranola said:
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
Click to expand...
Click to collapse
Tried both manually with adb, and with WugFresh toolkit. I got WugFresh to run TWRP temporarily.
Potetsjokolade said:
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Click to expand...
Click to collapse
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
How can I do that when my N7 does not show up on
adb devices
Click to expand...
Click to collapse
Getting "waiting for device"
Potetsjokolade said:
How can I do that when my N7 does not show up on
Click to expand...
Click to collapse
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Username invalid said:
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Click to expand...
Click to collapse
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Potetsjokolade said:
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Click to expand...
Click to collapse
openrecovery-twrp-2.6.3.0-flo.img is for the WiFi model. TWRP for the LTE model is openrecovery-twrp-2.6.3.0-deb.img.
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
EDIT: Nevermind that stupid question
Potetsjokolade said:
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
Click to expand...
Click to collapse
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Username invalid said:
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Click to expand...
Click to collapse
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Potetsjokolade said:
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Click to expand...
Click to collapse
What do you see if your computer Device Manager with USB Debugging on?
Username invalid said:
What do you see if your computer Device Manager with USB Debugging on?
Click to expand...
Click to collapse
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Potetsjokolade said:
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Click to expand...
Click to collapse
I've never had that problem so I can't speak from experience.
http://forum.xda-developers.com/showthread.php?t=2428061&highlight=mtp
http://forum.xda-developers.com/showthread.php?p=44219641#post44219641