• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root The Nexus Root Toolkit

Just got through unlocking and rooting my new 32 GB N7 using the Wugfresh toolkit. It is a charm. I made a couple mistakes and went ahead and installed PDA Net on tab and PC but no problem. I just uninstalled on both Tab and on PC and picked up the instructions where it left off. The drivers were still in place and Everything went smoothly from there. Now waiting for my OTG adapter and case and will be ready whenever a super exciting rom comes along. :)
 
I recommend this toolkit at every opportunity I get.

It's highly recommended and he gives excellent support on his XDA thread (Not that most people need it, the tool is that intuitive).
 
Bigdog999 said:
Noobie question my friends. The root kit worked great. Now I only rooted my Nexus 7, should I have flashed with the custom recovery or not. I only want to use rooted apps especially backup and not install custom roms.
Click to expand...

Flash the recovery so you can do a full backup with TWRP. It will also give you the ability to wipe your dalvik and cache if things get buggy.

I'm right there with you on ROMs. I love the stock romantic, now that I've removed a few system apps and installed a custom kernel.
 
You'll want to install the custom recovery so you can do nandroid backups.

I was on the stock ROM for almost a month, but I recently flashed paranoid android and I think I'll be sticking with it.
 
Lightswarm said:
I'm fairly new to the Nexus 7 section of the forum and I have a couple questions.

Can I root my Nexus 7 via the NRK program above?
Is there a guide for rooting my device with Android 4.1.2?

Thanks, and reply is appreciated.
Click to expand...

I posted a thread in this forum with a link to a YouTube video. "... Rooted, and now what"

Very easy to do.
 
colchiro said:
My only complaint with Nexus Root Toolkit is the buttons need to be wider for those of us with high-resolution laptop screens (i.e. custom dpi set to medium - 125% under display)

The problem is most noticeable on the driver installation screens.
Click to expand...

This issue is resolved. All screens I checked seem to be completely readable. :D
 
so.. i just got a nexus 7 16gb from craigslist.org

is 1.5.5 still the latest? I see that this is version 1.6.2
do i need to confirm which nexus7 i have? there is seems to be 4 hardware versions running around.

i dont know if it has been rooted or if the boatloader has been unlocked...
before i use this tool kit...How can i check these things?


first thing to do .. is to turn on debugging..in Settings.. developer Settings.
but on my Nexus7, running 4.2.1 and ADW Launcher.
there is no "developer settings"??
is it because of ADW Launcher? how do i make it go back to stock nexus homescreen??
 
dan330 said:
so.. i just got a nexus 7 16gb from craigslist.org

is 1.5.5 still the latest? I see that this is version 1.6.2
do i need to confirm which nexus7 i have? there is seems to be 4 hardware versions running around.

i dont know if it has been rooted or if the boatloader has been unlocked...
before i use this tool kit...How can i check these things?


first thing to do .. is to turn on debugging..in Settings.. developer Settings.
but on my Nexus7, running 4.2.1 and ADW Launcher.
there is no "developer settings"??
is it because of ADW Launcher? how do i make it go back to stock nexus homescreen??
Click to expand...

You need to go to Settings -> About Tablet -> Build Number. Tap Build number 7-8 times and you'll get a toast to tell you you are a developer. Then Developer settings will appear.

You'll know the bootloader is unlocked because there will be a little unlocked padlock icon at the bottom of the Google Screen when you turn it on. Rootchecker will check for root.

The latest toolkit is 1.6.2 and you can get it here: http://forum.xda-developers.com/showthread.php?t=1766475

When it boots, it will check to see if it's the latest version and download and install if not.

Re the version, check your build number, make sure that matches the build number in the toolkit and Bob's your Uncle. :)
 
ok.. i am now getting to this project..
have read over the ROMs.. and i guess i am going with the:
Dirty AOKP
http://forum.xda-developers.com/showthread.php?t=2087555
it seams pretty good.. and is stable

using the ROOTKIT... on nexus7
i enable the USB debugging and plugged it in to my PC..
PC tries to install drivers.. i dont have these files..so it cant install.
use the ROOTKIT to get the drivers..
but it ask me to delete a bunch of installed drivers..part of Step1:
- Use USBDeview to uninstall any;
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- ... or ANYTHING else you see that resembles your Nexus.

- In particular look for devices with Vendor ID
- "18d1" or... "04e8"

i have a Samsung Galaxy S3.. and I still want to be able to plug in my phone to my PC and do things. how will this affect that?
 
dan330 said:
ok.. i am now getting to this project..
have read over the ROMs.. and i guess i am going with the:
Dirty AOKP
http://forum.xda-developers.com/showthread.php?t=2087555
it seams pretty good.. and is stable

using the ROOTKIT... on nexus7
i enable the USB debugging and plugged it in to my PC..
PC tries to install drivers.. i dont have these files..so it cant install.
use the ROOTKIT to get the drivers..
but it ask me to delete a bunch of installed drivers..part of Step1:
- Use USBDeview to uninstall any;
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- ... or ANYTHING else you see that resembles your Nexus.

- In particular look for devices with Vendor ID
- "18d1" or... "04e8"

i have a Samsung Galaxy S3.. and I still want to be able to plug in my phone to my PC and do things. how will this affect that?
Click to expand...

When you plug in your s3 the drivers will be reinstalled. If not, you can reinstall them from samsung after you get your nexus working with the toolkit
 
so.. nexus drivers and samsung drivers .. cannot live on my PC at the same time???

for mounting the drives...
 
dan330 said:
so.. nexus drivers and samsung drivers .. cannot live on my PC at the same time???

for mounting the drives...
Click to expand...

The absolutely can exist at the same time. But in the event you remove one or the other accidentally, it gets reinstalled when you plug in the device
 
Duh!!!! the drivers are still in my PC... so they would just reinstall..
well that is the theory...
 
I've also got a SGS3 so I only uninstalled the 18d1 ones that also had a N7 description, and unlocked/rooted successfully so you should be fine leaving the Samsung ones.
 
it went well.. and afterwards.. when i plugged in my S3... the drivers reinstalled themselves again.

all good.. and rooted!
 
Not sure this is the right place to post, I'm a newbie, but here it goes anyway.

I have a nexus 7 that I rooted with the Nexus toolkit and I made the fatal mistake of updating android to 4.2.2 and last night I noticed that I couldnt tx files through my USB drive anymore. So I went on the forum to do a bit of resaerch and installed root checker pro and it says that root access is not properly configured.

Here is the report


Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
SuperSU application - version 1.04 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root shell 96144 2013-02-05 14:58 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1

I can see stickmount in SuperSU and when I try to moiunt manually it says busy. When I connect the drive it flashes and stickmount searches for the drive but comes back with an error message that card is not mounted or empty.

I went back to the toolkit and it won't let me root becase I get stuck in "ADB is listed but offline".
I tried all the steps recommended changed port, cable, verify that port 50.. is listening, rebooted device and computer, ticked and unticked usb debugging etc but no success.
I'm stuck and don't know what to do next. I'm new to android, have had the tablet only for 3 months. I thought I was on top of it, but not.

I shouldn't have updated, I did it with trepidation, I have to travel soon and I need the tablet to be able to read the external storage.

Can anyone help please or redirect me to the right place?
 
You must log in or register to reply here.
Back
Top Bottom