Related
Here is a very simple instruction on rooting LG GT540 when Universal Androot doesn't work:
1. Download and extract the attached package.
2. Connect the phone in "USB Debbuging Mode"
3. Doubleclick "root.bat" (extracted from the package)
4. Wait for the console to shut down and the phone to reboot.
The credit for this method goes probably to people from Modaco.
Since this is my first post and i am still not allowed to post links from external servers i won't give any mirrors for unregistered users. Sorry.
Any confirmation that this works?
It sounds just too easy!
Bakuj, you can PM me with link to the modaco forum, I cant find topic with this root method!
Cheers!
Rooted yesturdamy with this, works fine
I rooted my phone yesterday using that method.
I ran each line of code separately though as i had issues running the .bat file
Thanks a lot
Froyo?
I have a TMO Optimus T w/ FROYO. Will this work on it?
You can give it a try. But first look at the name of this forum section. It is for GT540.
I have made a new version which includes both root and app2sd.Named 1 click autorootapp2sd .
You can access the guide at modaco . The file is attached.Turn on usb debugging mode and run autorootapp2sd.bat.
Nice and handy ^^ thanks
ROOT for recovery:
1. Grab this file mediafire.com/?rc8g496og3482dx
2. Update.zip copy directly to an SD card
3. Reset the phone and start the recovery mode
4. Select the option to apply sdcard: update.zip
5. Root been made
Application was added to the package:
root explorer, superuser and busybox
Thanks a lot arekl1988r
but how can i unroot it?
flash the original GT540 ROM with lg software?
Yeah it should work. Also you can try a factory reset (never tested).
Hi Rooting will void my warrenty??
Im trying to root my phone.
I have USB debugging mode on the phone, and i tried running root.bat both as an administrator and a user.
I get stuck here (see attachement)
What have i done wrong?
I can see: device not found, try Turn USB Debugging ON
It is on, i also rebooted the phone.
Ok, so try this way: http://forum.xda-developers.com/showthread.php?t=803682
I found out that i cant even connect my phone to LG Pc suite.
USB storage works well, but Suite never finds the phone. I have installed all the drivers from LG.
Whats the next step?
gordito_gr said:
LG Pc suite
Click to expand...
Click to collapse
Which one I had the same problems with III, but version IV fixed it all
Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
So do this version allow sideloading?
awww yeahhh
PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?
Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?
s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.
drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.
Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.
tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?
Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...
when i run beforeupdate i get backup failed to execute properly
am i missing something?
Currently Beta:
THIS IS UNTESTED. I don't have my Atrix anymore, so I need volunteers to test this for me. Ideally, whoever can test this will have access to a PC to reflash the SBF. If you are willing to do so, please run the beforedebug and afterdebug versions and PM me the output
Some Notes:
- As this is Ririal's script translated to bash (see here: http://forum.xda-developers.com/showthread.php?t=1016060), this shouldn't work on Bell Atricies
- Since RSDLite is a windows only program, it is not possible to flash the SBF back to 1.2.6 on a Mac as far as I know. In other words if you've upgraded already, you're out of luck until you can find a PC to flash back to 1.2.6
PS: Since the method I used to turn the scripts to executables last time caused some PATH issues, I've decided to leave this as .sh files
Instructions:
1) Download the zip and decompress it to the Desktop
2) Make sure you're Atrix is hooked up w/ ADB debugging enabled
3) open up a terminal (What follows will be instructions to run)
cd ~/Desktop/aRootMacV2
./beforedebug.sh
4) Run the update on your phone( Settings -> About phone -> System updates)
5) Back to the terminal
./afterdebug.sh
6) Make sure to allow the SU request on your phone when prompted
Once this has been tested to make sure it's working correctly I will update this thread with more thorough instructions. In the mean time if you don't have a PC, make sure not to update.
Download: http://www.mediafire.com/?djxt3d8j519yk9m
Thanks for this. Ill try to get a pc so I can downgrade and test this.
Sent from my MB860 using XDA Premium App
I get this when trying to run beforedebug.sh
new-host-5:aRootMacV2 AJ$ /Users/AJ/Desktop/aRootMacV2/beforedebug.sh
-bash: /Users/AJ/Desktop/aRootMacV2/beforedebug.sh: /bin/bash^M: bad interpreter
EvilEvo said:
I get this when trying to run beforedebug.sh
new-host-5:aRootMacV2 AJ$ /Users/AJ/Desktop/aRootMacV2/beforedebug.sh
-bash: /Users/AJ/Desktop/aRootMacV2/beforedebug.sh: /bin/bash^M: bad interpreter
Click to expand...
Click to collapse
the "bad interpreter" message is caused by ^M (Windoze carriage returns) being embedded in the script file. If you do this
Code:
cat beforedebug.sh | tr -d '\r' > beforedebug.sh.new
cp beforedebug.sh.new beforedebug.sh
that should do the trick.
At the risk of jacking phoneixx's thread, I had done something similar for Mac based on Ririal's GladRoot and DesignGears aRoot.
There actually is an SBF flasher for Linux and Mac found on OPTICALDELUSION's blog.
I had originally posted this on AndroidCentral but since XDA is the site of record then I guess it should go here too
(I tried to link to the OPTICALDELUSION blog and AndroidCentral article but the XDA spam filter won't let me post a link to an outside site until I have 8 more posts, lol. I may make some more posts elsewhere and edit this post to include the proper links )
_____________
Hello, all of you frustrated Mac users out there!
This method is tested on my MacBook Pro (10.6.6)
Linux users should be able to use this if they replace the copy of adb that is in the zip file with the appropriate executable from Linux version of the SDK. If you know enough to run Linux then you can do that on your own
Warning -- AT&T Atrix only! No Bell!
So you're on 1.5.7 -- let's root it!
Part A -- Revert software back to 1.26
1. Download this file and unzip it (Deposit Files)
2. Make sure your phone is FULLY CHARGED
3. Turn off your phone
4. Remove your SIM card and SD card if you have one
5. Turn your phone ON and hold the Volume UP button
6. It will say “Starting RSD protocol support” at the top of the boot screen
7. Connect your phone to the computer via USB
8. Run the downgrade.sh script. This will reflash your phone to 1.26 so that we can gain root access.
9. it can take up to 5 minutes to flash depending on your computer speed. My MacBook Pro takes just under 4 minutes. If you get any errors that look something like
>> uploading RDL03: 0.0%usb_bulk_write -5
>> uploading RDL03: failed at 00000000/00300000
!! failed
>> rebooting
usb_bulk_write -104
Don't get nervous! That happens occasionally. Just run the script again.
10. Phone will reboot and it takes longer than usual to come up
11. disconnect USB and power down.
12. Put your SIM and SD cards back in
13. Power up and verify that you are running 1.2.6 in Settings -> About Phone. You'll have to reenter your Motoblur account info.
Part B -- Root it!
14. Enable USB debugging (Settings -> Applications -> Development).
15. Connect your phone and set USB Connection to 'None'.
16. cd to the aRoot directory and run aRoot.sh and follow the on-screen directions
If you see this:
…
Getting temporary root access...
mmap() failed. Operation not permitted
…
then the rooting operation failed. Try running the aRoot.sh script again. If it fails manually run this:
./adb kill-server
If it keeps failing you may not have flashed back to 1.26 successfully. Start again.
17. Verify that there are no errors before updating.
18. Go to Settings -> About phone -> System updates
19. Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
20. The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
21. When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
22. Run afterupdate.sh
23. Make sure you allow the superuser request on your phone or it WILL fail.
24. All done! Enjoy your rooted Atrix on 4.1.57!
thanks to
OpticalDelusion (OPTICALDELUSION)
DesignGears([SCRIPT] aRoot for Atrix 4G [ root - init.d - sideloading - tethering ] - xda-developers)
Ririal ([SCRIPT] GladRoot v4 (Bell 0.37.4, AT&T 1.26/1.52/1.57 Supported) - xda-developers)
Kennethpenn ([GUIDE] Flash SBF to Motorola Atrix 4G - xda-developers)
Ok, I have a N7000 with stock gb and KK2 kernel and I want to load the Paranoid Android ICS rom. First I see that I must route my phone, so I tried following the instructions at:
http://www.android.gs/how-to-root-samsung-galaxy-note-n7000/
These instructions make it sound darn simple, but perhaps I am really dumb? Ok, so first I downloaded the latest kies as well as "CF-Root-SGN_ZS_MUL_KK1-v5.0-CWM5.rar"
After installing kies, I got it to connect to my note although not without heart ache. Eventually I found that it would only work if I first disabled USB debugging. But that wasn't enough. Then I had to reboot the phone. (Without that step it wouldn't work). It wasn't clear to me if I even needed to make it connect to kies. The instructions didn't say I needed to. Ok, so then I start "not-rooted-yet.bat" which displays this:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
(3) enable "UNKNOWN SOURCES"
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
(7) !!! PUT A CF-ROOT zImage FILE IN THE zImage FOLDER !!!
I can only easily do items 2-5. It's hard for me to imagine that I should just ignore the other 3 items.
Instruction #1 confused me. How do I accomplish that? It seems that the adb drivers come with the android sdk but the instructions don't say anything about installing that. That seems like a big deal and if it was required it seems that it would surely be mentioned?
Plus I found this post which also indicates that the sdk is not required.
> victorlht88:
> no u don't need the android sdk to root.
> just install kies, plug your phone with usb debugging enabled
> and let it install the drivers.
> restart your comp and plug your phone in (download mode),
> downgrade the firmware (if need be) with odin and simply
> root using cf root.
> its not that tough.
However those instructions seem about as clear as mud, since if I plug in my phone with usb debugging enabled, kies just hung forever saying "connecting".
Do the adb drivers get installed just by installing kies or do you somehow have to coerce kies to do this?
And then there is step 6. But I don't get any prompt of any kind when I plug in the phone to the pc.
And then there is step 7. I don't know what this means, but my guess is that I have to copy the zimage\zimage file to somewhere on the phone. However where exactly? There is no zImage folder on my phone! Plus even if there was, I couldn't copy anything to it after checking "USB debugging" (mass storage mode) I can no longer see my phone in explorer. What happens when I plug the phone in is that the phone says "USB connected" and then two new drives appear on my PC. However if I try to click on either of those I see "No disk drive. Insert a disk and try again". I even tried rebooting my pc, but then I get even more than two new drives showing up briefly, but they always give the same error message as before.
... yet I know that thousands of people have routed their phones ... so I am left pretty mystified. If anyone can clarify these instructions it would help me greatly, and maybe others as well.
Thanks
~Paul
Follow dr. Ketans thread in the development section.
And once on download mode with usb connected, CLOSE KIES. Otherwise odin will not work.
Sent from my GT-N7000 using xda app-developers app
Hi, your guide is taken from here. I think there is a missing step, which is to download the InitialCFRootFlasher.zip from the end of post #2, and you need to follow the instruction step "1.2. If you are not rooted yet: Using the zergRush exploit".
Btw, adb drivers are included when you install Kies in your PC. Once Kies is installed, you have to close it. Make sure your phone is in USB debugging mode before starting the procedure.
praetorius said:
Follow dr. Ketans thread in the development section.
Click to expand...
Click to collapse
Ok, those instructions seemed more clear. Different script as well although perhaps not significantly so? In any case it worked. I'm not rooted! Thanks all
~Paul
you said your kernel is kk2, then why did you use CF Root KK1?
Cf root kernel for KK1 and KK2 is same.
Hi everyone,
I see more people than usual having issues with Rooting their Nexus 7 because of problems with booting into CWM recovery post flash - thought I would do a nice plain and easy to follow guide including instructions for booting into CWM recovery from a command point (thanks to Wugfresh for his Toolkit which is used in the guide).
http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
Porting the full guide here, first the text because that is a simple cut n paste job, images to follow soon:
Before we get down into the nitty-gritty of the guide itself you should familiarise yourself with our usual disclaimers at the beginning of this post. I say this not because we don't care if you have problems, it's just that our capacity to trouble shoot is limited, and you shouldn't have embarked on an adventure to Root your device unless you did your due diligence first and had some understanding of what you were up to. One final disclaimer weasel-word at the off: the CWM recovery ports for the N7 are still a little iffy at this stage and even when taking appropriate steps to make it permanent you may only be able to boot into it via a command prompt window. Expect updates once fixes are available.
Disclaimers out of the way, here are the things you will need:
A Nexus 7, fully charged
A windows PC (the guide may work on macs via Windows virtual environments, but that isn't confirmed by us and is outside the scope of this guide)
The appropriate Nexus 7 USB drivers, there are several ways to get these:
Preferred method - Go to this thread at XDA-Developers and download and install the Root Toolkit there, which has an automated drivers installation included (this is preferred because it is what the guide that follows is based on because the Toolkit is probably going to be the most straightforward for the majority to use, and even if it fails and they have to resort to using command prompts that is more easily done from the Toolkit). Many many thanks to WugFresh at XDA for producing such a noob-friendly Rooting application - please consider making a donation to him here.
Install the Android SDK from here. Please note if you are already an SDK user that the Google USB drivers in the SDK have updated with the release of the Nexus 7 and Jelly Bean and you should update your drivers from within the SDK itself
Install the universal drivers from this post at XDA-Developers, but please make note of how you will need to adjust fastboot commands if you are using these drivers
Go to this post at XDA-Developers and install the USB drivers from there if you have no luck whatsover with any of the other methods
OK, now that you've got the Root Toolkit let's proceed (if you plan to do this with the SDK and command prompts then you should be advanced enough to follow the guide here, I did the first time and if you've done this stuff before the process is trivial).
Open the Root Toolkit, at the prompt to select your device scroll down to the bottom and select the Nexus 7 and the version number that corresponds to the firmware installed on your Nexus 7 (you can find this out in Settings --> About tablet --> Android version)
You'll be greeted with a screen that looks like this:
Click on Initial Setup and use the automatic driver installation facility from here to install USB drivers, it will check that ADB and Fastboot commands are working before dropping you back to the install window.
Turn on USB Debugging in the Nexus 7 by navigating to Settings --> Developer options. Turn on Developer options using the toggle in the top right hand corner, and then turn on USB debugging
Connect your Nexus 7 to your computer with the micro USB cable that came in the box. At this point it is vital that your computer recognises the Nexus 7 as a connected device, you will know if it has because a Nexus 7 "AutoPlay" window should pop up and ask you what action you want to take. If it doesn't show up, pull down the notification tray and press on the notification that says "Connected as a media device". A new menu will open and select the "Camera (PTP)" option. You should now get the AutoPlay window.
Head back to the Toolkit, and select "Unlock" from here, be aware that this will wipe your device (you might want to take a backup if you've already installed a lot of stuff on the device, that's just a button click away also in the Toolkit)
This will boot the device up to a screen giving you the option to unlock the bootloader, with "Yes" selected hit the power button. You'll see some text in the top left corner telling you it is unlocking the device, and then you will see the red "Locked" text toward the bottom of the screen change to "Unlocked". Moments later the device will reboot, and because it will have been wiped you will need to either set it up again or just skip past set-up and get back to the homescreen.
Once you're back onto the home screen, connect as you did before and take the same steps to turn on USB debugging and get the AutoPlay prompt to appear. Then go back to the Toolkit and select the Root option with permanent CWM recovery. All things going well the process will be fully automated from here, it will check that ADB and Fastboot are working, push the SU and CWM files to the device, boot the Nexus 7 into it's bootloader, flash CWM recovery to the device, and then reboot with Root privileges and a fresh new recovery permanently installed.
...or so the theory goes. Using this method I get Root, but CWM recovery is only accessible via command prompt, and I see others having the same problem. So...
Accessing CWM recovery:
In the Root toolkit go to Advanced Utilities by launching it here:
On the next screen select Launch CMD Prompt:
Once the command prompt appears type: ADB reboot recovery - the phone will boot into CWM recovery for you, so you can do things like make Nandroid backups, install zip files and so forth
Installing the 4.1.1 update post-Root and installation of CWM recovery:
Install OTA Rootkeeper by Supercurio from the Play Store here
Open the app once installed and grant it SuperUser privileges
In the app select "Protect Root", and then "temp unroot" the device
Download a zip of the 4.1.1 update here.
Copy it to the internal SD of the Nexus 7
Access CWM recovery as per the instructions above. In this version of CWM recovery you will navigate the options with the volume keys and press the power button to select an option - do that to navigate to "Install zip from SD card" and press the home button
On the next screen go to down "Toggle signature verification" and toggle it until it says "disabled" at the bottom of the screen (it should be set to default to disabled, but you lose like 5s making sure)
Go up to install zip, navigate to the zip file you downloaded in step one and install it
When the device reboots go to OTA Rootkeeper and restore Root, viola! You're done!
So, after all is said and done you should have a Rooted Nexus 7, running the 4.1.1 update, and with a custom recovery that can only be accessed via command prompt. Don't forget to shout WugFresh, the Toolkits developer, a coffee - make a donation here.
Would be nice if you posted that guide on this forum too.
Thanks for the guide.
Oooohh pictures
Caliyork said:
Oooohh pictures
Click to expand...
Click to collapse
You know, for the totally acopic
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Dillon610 said:
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Click to expand...
Click to collapse
No idea. You can simply downgrade to an older stock image using his Toolkit though and then follow the same process used in the guide to update to the latest build.
"Meh" at requirement #2:
A windows PC
Click to expand...
Click to collapse
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
JaSauders said:
"Meh" at requirement #2:
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
Click to expand...
Click to collapse
"Windblows"
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
There's a wiki on cyanogenmod.com that explains root.
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
Should be doable on mac in a windows virtual environment, which seems to be how most mac users are doing things here at XDA.
Actually looking for someone to write "for mac" guides, if anyone is up for that!