yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Bob Smith42:
Thanks for your Nexus Root Toolkit. I am using it on my Nexus 7 3G and it works great. My favorite.

I started with the Nexus 7 ToolKit, which is good but I found some bugs. For example, its one step unlock-root-etc does *not* install a tilapia based recovery.

I think each tool has its advantages and disadvantages, but now I'm sticking with yours. :D
[Nexus 7 Android Development] :
toolkit

thank you.rooted and installed TWRP custom recovery on my nexus.PDA method worked fine although i downloaded and installed myself,but,other than that perfect
[Nexus 7 Android Development] cerj:
Wug, I opened my N7 yesterday, then I downloaded your toolkit last night. This afternoon I rooted and flashed TWRP recovery. The whole process took about 5 - 10 mins ( I installed the drivers via your toolkit as well ). Now my N7 is rooted and I have a custom recovery. On to flashing Roms. I have a GS2 Epic 4G touch, that I rooted as well. Pretty simple to root my E4GT, but I didnt know till I was finished if I was doing it right. The Pop Ups and Toast's you have written in your toolkit, Guiding and explaining thru the whole proccess, leave little room to fail. Thank you for creating this incredible tool. Cant thank you enuff, so I Donated, Confirmation number: 96023051J1149203X. Simply Amazing work

---------- Post added at 04:56 PM ---------- Previous post was at 03:59 PM ----------

Just performed a successful nandroid with your toolkit as well. I can tell how much work went into putting this together, it is appreciated. Again Thank you
[Nexus 7 Android Development] jesusrah:
I'm just posting to say Thank you, you did an awesome job and the way you guide newbies with your software is really appreciable :laugh:

Thanks again!
[Nexus 7 Android Development] WORF84:
ADB is not working for me in Win7 x64

Successfully unlocked by manually going to recovery mode.

Now I want to do that again with the root image since ADB thing is not working for me.

The file "modified_boot_nakasi_4.2.2_JDQ39.img" do I flash it to BOOT or to system in advanced utilities?

I guessing BOOT since it says boot in the filename...
[Nexus 7 Android Development] WugFresh:
If you want to root your device manually, you should follow a guide. My toolkit uses a modified boot img specifically for the purpose of automating processes that wouldn't be possible without the increased file access. Don't just start flashing things to partitions. The toolkit never flashes that file, it just boots it temporarily.

The basic procedure for manually rooting, is unlocking, flashing/booting custom recovery, and flashing a superuser.zip. There are some other things the toolkit does like renames certain system files if you are flashing recovery so that it sticks, and installing the busybox installer app, but you can do those things yourself manually if you want as well.

So to reiterate, that modified boot image isn't a "root image". It is just a modified file that when booted, temporarily allows the toolkit the additional file access neeeded to fully automate the root process.

I hope that helps clarify some things.

Cheers,

{{ WugFresh }}
[Nexus 7 Android Development] WORF84:
Thanks I will dig deeper. =)
[Nexus 7 Android Development] xfuze:
Hey Wugfresh, love your program but was having problems with writing system hanging on the toolkit, so i uninstalled, deleted the wugfresh development folder and now when i attempt to reinstall i get an unexpected end of archive when installing. Ive tried all the mirrors except goo.im as it seems to hang on 49.1mb which is weird.

Nexus 4 4.22
[Nexus 7 Android Development] WugFresh:
Sorry that you are having difficulties but there is no way for me to help you with your internet problems. Maybe try another computer or Internet connection. If others are also having problems with the links then I will make sure to upload more mirrors.

{{ WugFresh }}
[Nexus 7 Android Development] Dan330:
Thanks again for this tool kit.

just had to replace my N7 because of broken glass.

N7 4.2.2

rooted fast and simple.

thanks!
[Nexus 7 Android Development] xJU1C3x:
Thanks Wugs! Awesome tool....I just bought my N7 yesterday, and immediately got it unlocked and rooted super easily, thanks to your toolkit. Many thanks, and let me know via PM if you'd like any further assistance in your development...
[Nexus 7 Android Development] ksnax:
Donated. The time saved in not having to figure out how to recover my soft-bricked 7 by other means was worth the cash.

This kit makes it all easy!

It's been months since I last flashed a ROM, and today it was boot-looping out of the blue with no access to anything but the bootloader. I was able to start fresh with no trouble. Back to unlocked and rooted stock 4.2 for now. :victory:
[Nexus 7 Android Development] sim36:
same situation

same here. I'm sad.
[Nexus 7 Android Development] T90:
Wanted to say thank you for the excellent and easy to use tool kit! Easy peasy!! Unlock, root and backup was a breeze!
[Nexus 7 Android Development] ashik992:
First thing is to say thanks to you for a great work like this...

Just a little question; when is NRT gonna install TWRP 2.5 itself??
[Nexus 7 Android Development] pizza65:
Hi, just got my nexus7 and this worked great! It hung when rooting while attempting to set file permissions - I simply closed the tool and tried again and everything was great, but it's still a bug report :)

I made the mistake of not flashing CWM when rooting however, foolish. I see that I can do it now by picking the 'Flash (Permanent)' option in the Advanced Utilities and picking the img file, but which of the img's is the right one for the nexus? Going through the data folder, I'm guessing it's

recovery-clockwork-touch-5.8.0.2-nexus7-modaco.img

but wanted to check. Also, that won't force another wipe, correct?

Thanks for making an amazing tool!
[Nexus 7 Android Development] nikon120:
I'm using these drivers without an issue, thankfully. (Win7 32-bit)

My issues with drivers all revolved around having USB Debugging enabled. Without that feature enabled the "Nexus 7" driver installed immediately upon connection. When I enabled USB Debugging and connected the device, the drivers failed to install.

The device that failed to install was labeled "Nexus". I then proceeded to uninstall the SDK USB driver and all previous installs from Google, Inc. I left my Samsung driver since I still need it for my Epic 4G.

I finally stumbled upon the PdaNet and Universal Naked drivers. I didn't want the PdaNet package installed on my system, so I went the Naked driver route. Luckily they worked and I was finally able to use this tool.

I also ran into the ADB status hanging issue, but that was due to the drivers. I just don't get why ASUS didn't release drivers upon announcement at Google I/O.
[Nexus 7 Android Development] nicksoph:
with or without Debug?

Hi - could you tell me did you first install the naked drivers with debugging enabled?
[Nexus 7 Android Development] nikon120:
I first enabled USB Debugging and connected the device

Let the driver install fail

Opened the Device Manager

Right-clicked on the unknown device "Nexus"

Selected Update Driver

Pointed to folder I extracted the Naked files to

Profit

Hope that helps you out.
[Nexus 7 Android Development] Laridia:
Yep, done this, no difference.

I'm using:

Windows 7 Ultimate x64

Nexus 7 with stock 4.1.1

What happens is that whenever Toolkit tried to run an ADB command, it launches two adb.exe processes. One will disappear after a second or two, as if it is completing. The other will just sit there and Toolkit just says it is waiting for ADB or waiting for the device to reboot or waiting for <whatever it is trying to do>. If I manually kill the leftover process, then Toolkit will carry on. Sometimes it carries on by launching another two ADB processes and hanging on the second one again, or sometimes it just continues as if whatever it was doing as worked. I guess some things take multiple ADB commands and that's why I see it repeating. I just keep killing the leftover one and it'll carry on.

Some things are working properly with the above method. The device will reboot into recovery just fine, and the unlock command worked. It wasn't able to reboot my device back into Android. During root, the recovery flash didn't work, SuperSU didn't install (binary or APK), but BusyBox installer did.

I'm pretty sure at this stage we just need to wait for an update to the Toolkit because something is definitely not right with it.

I tried the x64 driver bundle that was posted, I'm not sure if I was just supposed to install it but that didn't make any difference. I wiped all relevant drivers etc. after every try.

Thanks for working on this Wugs :) .
[Nexus 7 Android Development] djd338:
I too was stuck while the tool searched for adb. I was trying to outsmart the tool thinking I didn't need any extra drivers installed because I already had the PDA app and most every driver there is already installed. Well, it's like the tool recognized them all, and couldn't decide which to choose so it was like stuck in a search "bootloop".

I finally went step by step, all 8 of them, while RE-installing the Samsung driver The very first step gives you a great tool to delete all those drivers. Please use it! I only deleted the drivers I had installed that were of the 2 numbers mentioned within the tool on step 1. It works fantastic. The other step checks booloader, adb, reboot, etc. before you even start the unlock process. Including doing all the steps, I was unlocked, rooted within 15 minutes.

After set up, I used Rom Manager to run new backups straight from the app. As mentioned above, the new cwm 6.0 is out and you can flash it straight from the Rom Manager app. 6.0 now has the "TWRP-type" speed, and does a backup in about 2 mins. Your first backup may/will take longer, but subsequent ones will be done quicker due to "incremental" BU's.

I hope this helps, because this is a great tool if you allow it to help you with the drivers.
[Nexus 7 Android Development] nikon120:
So just used the Advanced option to flash the official CWM recovery file. The app booted the device into the bootloader properly, but the application hung at the waiting for bootloader step. I had to kill the ADB process for the next step in the flashing process to kick off.
[Nexus 7 Android Development] nicksoph:
ADB - hangs

For those who have the toolkit hang when it calls adb.exe you may still be able to use the toolset if you have the same problem as me.

If you run task mgr and notice there is an instance of adb.exe running and then kill the process the main program just carries on normally, you might find that some tasks will call adb.exe several times - if you watch task manager you will see two adb.exe's start then one will end - just kill the one that doesnt end and you may see another two adb.exe's one of which will end... just keep ending the additional process.

Cant say I can recommend it. - on your own head etc

my next post is about collating driver details for those of us that are having this problem.
[Nexus 7 Android Development] Laridia:
I've deleted every single driver from Samsung and Google and anything with Android in the name, multiple times. When I connect my N7 it is instantly detected and installed with three drivers:

USB Composite Device

Nexus 7

Android ADB Interface

As a whole it is displayed as "Nexus 7". I don't know where these drivers are coming from since I've deleted them a whole bunch of times.

I'm a software developer so I'm not alien to the concept of drivers and Device Manager and such, I'm pretty sure that I'm not doing something wrong here.

Edit: Wait, I wonder if the Android SDK is doing this. That has drivers in it. Yeah, I bet that's it. Screw it, I'm just going to do this manually, heh.
[Nexus 7 Android Development] nicksoph:
ADB.exe hangs - What drivers show?

Thanks for the info

I have just tried again and made some notes along the way to see if they might help.

Using USBDeview I uninstalled nearly all usb that were not actually connected except the devices relating to usb3 ports and vmware usb controllers.

I plugged in the nexus in debugging mode and the pc installed a set of drivers - noted the details of the drivers loaded

Went to device manager and found Android Phone - Google Nexus 7 ADB Interface - selected have disc and installed the Naked 0.7 drivers - saw they were the same drivers as previously noted - shown below

18d1	USB Composite Device	Google Inc.	Microsoft USB Generic Parent Driver	6.1.7601.17586	usbccgp.sys

18d1	Nexus 7	Google Inc.	6.1.7600.16385	WUDFRd.sys

18d1	Google Nexus 7 ADB Interface	Google Inc.	Android USB Driver	4.0.0.0	WinUsb.sys

checked - same issue - two adb.exe's

My spec

win7 64bit, i7 with hyperthreading (turning it off didnt make any dif), vmware on machine but not running at the time
[Nexus 7 Android Development] Surnom:
Worked great thank you.
[Nexus 7 Android Development] FiveOhFour:
Did the toolkit function at all with the drivers from the SDK or did you not try it?

Mine behaves as follows, i already had the program open from last night still, i opened task manager, one instance of adb.exe open, when i hit unlock it begins to ping or query or what have you another instance opens up and near simultaneously to doing so it closes. Im not a developer or programmer so forgive me here but what exactly does this alone hurt, as in is your tool not loading the drivers, or it works fine but you are just curious as to the nature of the two instances? I guess my only point is to assure you that on my 32 bit atom netbook it behaves the same way, only difference being its completely succesful for me once i manually load the driver from the pdanet files.
[Nexus 7 Android Development] zedorda:
Does this work with the JDO03D Build because I don't see it in the list?
[Nexus 7 Android Development] gsuslikesme:
I am having the exact same issue...did this get resolved?
[Nexus 7 Android Development] iDoc21:
Followed the driver install instructions in the toolkit and everything worked perfectly. Thanks!
[Nexus 7 Android Development] nicksoph:
What drivers show in USBDeview 4 u?

Am I understanding you - you had an instance of adb.exe running before hitting unlock? Makes me think you manged to leave an instance of adb running from the bad drivers and then install the new drivers and run the program without interference. Im hoping that others who have this problem will publish their machine and driver details from USBDeview to see if we can discover whats going wrong.

If it is simply a driver issue then we are making a whole lot of fuss but somehow I think it might not be as simple as that because I cant see how Im not installing the right drivers but hopefully we'll see.
[Nexus 7 Android Development] kenikh:
Windows 8 x64 Users...Success!

I was able to get everything installed using Windows 8 64 bit. The Steps:

Phase 1: Set Up

Download the 64 bit drivers...

Unpack them , but don't install the drivers...yet.

Download the Kit...

Install the kit

Set Compatibility Mode to Windows 7 by right-clicking on the installed executable > properties

Download and Run USBDeView...

Remove all drivers with vendor IDs: "18d1" and "04e8"

Phase 2: Disable Driver Signature Enforcement

*CRITICAL* You must reboot Windows 8 to suppress driver signing enforcement. This is how it is done:

From the bottom right of the screen, click Settings > Change PC Settings > General

Look at the right side of the screen. Under Advanced Startup, click Restart Now

This will reboot you into the troubleshooter. Once ready:

Click Advanced Options

Click Windows Startup Setting

Click Restart

After Reboot, click Disable Driver Signature Enforcement

This will reboot you into Windows with signature enforcement off, but only until next reboot!

Phase 3: Driver Installation

NOW, install the drivers, called: drivers (64bit).exe

Follow the instructions when installing the drivers

Run Nexus Root Toolkit v1.5.2!

Click the "Full Driver Installation Guide - Automatic + Manual" button

Click the "Automatic Driver Configuration (Windows 7 Only) button

Let it do its thing...success!

Phase 4: Back to Regularly Scheduled Programming...

With the drivers successfully installed, you can now follow the regular instructions for unlocking and rooting your device.

This worked for me, I hope it worked for you. As always, I'm not responsible if you screw something up.
[Nexus 7 Android Development] clockcycle:
Is the stock recovery included in the kit or does it require one to have had backed it up previously?
[Nexus 7 Android Development] cjb110:
Excellent tool, far too many posts assume a *lot* of knowledge, this gathers everything in one place, with straight forward prompts too.
[Nexus 7 Android Development] FiveOhFour:
Yes, i had an instance of it open because like i said the program was still running from rooting the night before. Upon ending all tasks and re-opening i of course dont have adb.exe open until i begin a process that utilizes it, if i hit unlock, two adb.exe's show up in task manager and one quits itself moments later, this behavior is identical regardless of whther adb check finds a connected device or not. I guess my point was to let you know that the issue is in fact one of drivers and not some issue with having two of them running, driver installation is a fickle process as you know. Im not at all saying its user error im more saying its trial and error, try following the post two above mine by kenikh, i didnt have to use a couple of those steps but they all make sense especially if you are encountering an error, they are necessary steps just depending on your existing configuration they may be able to be skipped over with out consequence.
[Nexus 7 Android Development] aggrogade:
Not Working Anymore

I just tried to update to the new version, and it said that there was another instance already running, uninstalled and checked to make sure all entries in registry were gone, and all directories were deleted. Rebooted system and reinstalled and same error message. any one else haev this problem or see this before.
[Nexus 7 Android Development] jetvis37:
Thanks...
[Nexus 7 Android Development] howard bamber:
Please tell me I can save my gnex, with this...

Got a triangle with andy digging.

Think it needs bootloader etc.oh there's apic of a computer screen from what I remember

SENT BY POST...
[Nexus 7 Android Development] cerj:
Wug, since I rooted, added TWRP and made a nandroid, using your toolkit, I have flashed plenty of roms. I havent had even a hiccup while flashing, pushing files or doing all that we do. Today I was simply flashing a rom, and my beautiful N7 did not want to boot. Just stayed on the splash screen ( screen with the unlocked- lock ). Tried turning it off, and booting into recovery and It just went right back to the same screen. I could not get into recovery to restore any of my nandroids. Thought to myself, I may end up turning this into an expensive EtchaScetch for my daughter. Nah, I started searching for a fix on google, and it hit me, "wugfresh's toolkit". I remembered reading when I downloaded your kit or in the instructions, that the toolkit is helpful not only to root and flash a recovery, but it will get us out of a jam if it gets borked. So I plugged the N7 into my PC, opened your ToolKit, tapped on advanced Utility;s, then tapped on reboot recovery. ( Im doing this blind, with no directions or idea if it would work ). And to my joy, it booted into recovery, so I unplugged my N7 from the PC and restored a nandroid. Moral of this story is, dont wait till somethin happens before knowing what to do ( Like myself ). And trust in WugFresh cuz he's got your back. Another great reason to download this Toolkit, and if possible Donate. Man you make it easy for us. Again Wug, Thank You Thank You Thank You.
[Nexus 7 Android Development] BionicPizzaMan:
I tried to download with Chrome and it said "virus scan failed." Then I tried IE and it said the file may have been moved or deleted.
[Nexus 7 Android Development] mrozilla:
I use this Toolkit.

I click unlock - all ok

I pointed custom revocery (CWM) and click ROOT - flash the CWM, running temporary TWPR and stop (not flash any files), i'm manuall click reboot/system, N7 turn on, but there is no menu SuperSU and Busybox.

Why TWPR no flash SuperSU and Busybox?

Unlock and Stock works great.

I do not know why you can not see ROOT...

And why CWM is the old version 6.0.2.3 where 6.0.3.1 is the latest?

Also SuperSU is 1.04 and the latest version is 1.25
[Nexus 7 Android Development] _azeroth_:
Hi i would like to clarify that if i use this tool to root my nexus 7 wifi on 4.2.2 i need to unlock it first that will wipe data on my tablet? did i understand it correctly? or no unlock needed?:)
[Nexus 7 Android Development] BriVG:
Yes, you have to unlock to root and it will wipe the device so back up any important stuff first
[Nexus 7 Android Development] wtherrell:
Also does not have the correct version of TWRP. NRTK shows 2.4 something while I already have 2.5 something. Kinda hesitating to use this anymore. It has been excellent in the past, though.
[Nexus 7 Android Development] WugFresh:
Its simply telling you what file it finds in the local directory, not on your device. When I update the program to v1.6.4 I will be able to stay on top of updating the masterlists with the latest files, so there shouldn't be a difference. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] ryomakun:
i want to ask, if right now im using smoothrom 5.1 jb4.2.2 and i want to back to full stock (lock and no root), in Nexus Root Toolkit, i select device into Nexus 7 (Wi-Fi Tablet), but for android build that currently running have to i choose "CUSTOM ROM (WIFI TABLET) JB" or "NAKASI GROUPER ANDROID 4.2.2 BUILD JDQ39" ??
[Nexus 7 Android Development] iamhacked:
Ever since I rerooted my nexus 4 (because I did a factory reset) dalvik cache is clearing every reboot. What's wrong?
[Nexus 7 Android Development] WugFresh:
Custom ROM since that's what you are running. Although either would work for performing that task.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Couldn't tell you exactly why this is happening in your case however I can tell you that it is unrelated to rooting. You should try re flashing stock if this problem persists.

{{ WugFresh }}
[Nexus 7 Android Development] EeeK:
Used this to root my Nexus 7, work like a charm!

There a way to root without unlocking bootloader (link here), maybe can include that as an option in the future release.
[Nexus 7 Android Development] ashik992:
I don't understand why would someone want to root without unlocking the boot loader?? To keep the warranty??!!

---------- Post added at 03:34 PM ---------- Previous post was at 03:24 PM ----------

I did a little mod myself and it worked for me.

Here's what I did:

* Downloaded TWRP 2.5 from here.

* Renamed it to "openrecovery-twrp-2.4.1.0-grouper.img"

* Replaced the original TWRP with the downloaded one in my desktop. (C:\Program Files\WugFresh Development\data\Recovery_Custom\TWRP in my case)

* Normally flashed the custom recovery using the NRT.

=======================================

Please press the thanks button if you find this helpful
[Nexus 7 Android Development] EeeK:
So you can have root access without losing data on stock, duh....
[Nexus 7 Android Development] ashik992:
I don't care about the data. And you can always use some backup if you care.

Just my opinion. Everyone has their own opinion. And yours and mine just doesn't match. It's not a big deal. :)
[Nexus 7 Android Development] WugFresh:
Sorry you had to even do that. I just finished my senior thesis so I should have some time to finish coding v1.6.4. Also, just to note.. there is an option called "alternative recovery" in the options menu, where you can chose your own recovery image.. no renaming files needed. That said, the toolkit should just update to latest file versions automatically, I need to finish v1.6.4 and all will be well with that again. :)

Cheers.

{{ WugFresh }}