yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] RaptorMD:
Hello all. I'm a little late to the Nexus 7 party but I got my 32GB WiFi version last weekend and wanted to get it rooted and unlocked so having enjoyed Wufresh's work in the past I found it here again.

One question I have is during setup it asks which device and ROM are you running, device is obvious, but I am running the stock 4.2.1 but the listed ROM's seem to be custom ones to me, unless they are the stock ROM's and I just didn't recognize them.

My goal is to unlock get TWRP on it and flash Scotts CleanROM 3 for the Nexus 7.

Thoughts, comments, suggestions.
[Nexus 7 Android Development] FReaKRaNT:
You should be good with the provided USB cable.

Cheers, FReaKRaNT
[Nexus 7 Android Development] wtherrell:
Soft bricked my Nexus 7. Wugs got me back.

I soft bricked my Nexus 7. While on 4.2 Stock rooted deodexed I flashed a kernel I thought was compatible. Turns out it was strictly a 4.1 kernel.

Ouch. Wugs got me back to stock 4.2 and re rooted. Thanks, WUGS. Sometimes I doubt you and can't get things to work but it always seems to come back around in the end.

There are some tricks and tips that need to be compiled I think. That would have saved me a lot of sleepless nights and midnight oil.
[Nexus 7 Android Development] Doctor Dedroid:
Driver setup...

the driver set up on the toolkit suggest that you should remove all the existing drivers related to your Android device. The specifications seems to indicate those related to a Samsung type such as a Galaxy Nexus or the Nexus 7 or the Nexus 10 etc. it happens that I still have on my laptop, motorola drivers that I used to root my original Droid ( using RSD lite). Do i need to remove those as well? I did look for the answer to this question in this thread but there are 233 pages to go through and I could very easily have missed it.

Thanks in advance.
[Nexus 7 Android Development] ankushkool:
Stuck on driver installation

I am stuck on RAW driver installation step 6, i am not getting the below screen:

i am getting this:

and after rebooting into bootloader i dont get anything (no portable device)!

what am i doing wrong?
[Nexus 7 Android Development] reade0871:
Did you perform the driver tests for fastboot and adb from the toolkit? Otherwise put your phone in fastboot and run fastboot devices from the directory where you have ADB installed. If the device ID shows up then drivers are working.
[Nexus 7 Android Development] funktron:
Durrrr. Wrong thread!
[Nexus 7 Android Development] rodem77:
Did you remove all possible drivers before starting to install new ones? Did you reboot your PC after each driver installation? Did you try different USB port (the best ones are the ones on the back of your PC)?

Anyway you have to install drivers 2 times: one when your device is in android system and again when your device is in bootloader. Only in this situation you are sure that your drivers are properly installed. In the step 6 try to search something like your device, maybe that your PC see a different device than "portable", you have to choose it and install driver on it; anyway if you have any doubt I suggest to repeat all procedure from step 1
[Nexus 7 Android Development] tamanaco:
I just noticed that there's new 2.3.3.0 release of TWRP. Should I go ahead an update it via Goomanager or should I wait until it's added to the toolkit? Just want to make sure that if I use a different method to update the components that I flashed using the toolkit it does not cause me problems later on. In other words, is it necessary for the toolkit to be aware of the versions of the components the toolkit flashed in my N7 if I subsequently update these components using a different method?
[Nexus 7 Android Development] FReaKRaNT:
No, you can update it on Goo. Toolkit will not be affected.

Cheers, FReaKRaNT
[Nexus 7 Android Development] NinetoFive:
I rooted using this tool for my nexus 7 on 4.2.

I can't receive the OTA for 4.2.1 (rather i receive it but can't apply it).

I tried downloading the zip and flashing it using TWRP but it didn't work as well.

Is restoring to complete stock the only way to update OTA?
[Nexus 7 Android Development] ando roido:
Rooted Nexus 7 4.2.1. But unable to create nandroid backup with temporary TWRP. Says cannot find android secure.
[Nexus 7 Android Development] reade0871:
Yes. Flash stock unroot take ota then use toolkit again
[Nexus 7 Android Development] NinetoFive:
Thanks for the reply. Nothing on the phone will be wiped from doing this, will it? I suppose I could backup nandroid to be on the safe side.
[Nexus 7 Android Development] reade0871:
Flashing stock will wipe. Backup apps via titanium backup first. Nandroid backs up the current rom you are running.
[Nexus 7 Android Development] MrRedPants:
I thought this was going to be a 64bit issue (on Win 7 64 bit) - ADB was failing to see device. When I changed USB setting to camera (PTP) from MTP - everything worked as it should. Not sure why this made a difference but it was on another blog so I tried it. Now all is well. Hope this helps someone in the future.
[Nexus 7 Android Development] GD3tyrone:
thanks
[Nexus 7 Android Development] AlexM555:
This worked great!

I just used this root kit on my Nexus 7 32GB with 4.2.1, and it worked great! Thanks a lot! :D
[Nexus 7 Android Development] rodem77:
Hi, to install an OTA you have to remove TWRP and come back to stock recovery (this don't delete your data) after this, if you are sure that you have not apply any other modification to your system you can apply a downloaded OTA using ADB command read here:

http://xdaforums.com/showpost.php?p=32875165&postcount=94

I've a rooted phone and with this method I was able to apply OTA.

It is for Nexus S but procedure is almost the same for all Nexus devices.
[Nexus 7 Android Development] ando roido:
I kind of remember that my Nexus 7 connected to my 5G wifi. After rooting it says my 5G wifi is not in range. Strange.
[Nexus 7 Android Development] dalanik:
Hello everyone,

just rooted my N7 and everything went fine. Prior to root, I did backup using Root Toolkit and now I'm trying to restore. My backup is 1 .ab file about 6Gb in size, and it has been running for like 3-4 hours now. Yes, I know writes on SD memory are slower than reads, and yes, I have iGo with like 3Gb of maps worth, but still... how do I know it is running or it just stalled? The process is showing 40% CPU activity in task manager. On Android side of things, I don't see free space changing (in settings). What will happen if I interrupt? Can I re-run? Or should I just leave it running?
[Nexus 7 Android Development] landstander:
Not necessarily... I've installed OTA updates on rooted, but otherwise stock, Galaxy Nexus (Verizon) and Nexus 7 devices a couple of times without any issue. The only oddity was that the update file resides under /cache instead of /sdcard, assuming that the device downloaded it automatically, but once you browse there it can be flashed just like any other update.
[Nexus 7 Android Development] SteveC485:
Forgive me if I'm being dense here :). But why this desire to go to 4.2.1 via the OTA anyway? You are already rooted, so why flash back to stock just so you can get the OTA, then re root to get rid of most of the crap on the OTA? I can see it I suppose if you like the tool kit so much you just want some quality time with it. But if you already have a rooted tablet, just flash one of the several flavors of a 4.2.1 custom ROM and just be done with it? The custom ROM route offers rooted stock 4.2.1 ROM options if you want to stay stock as well. Anyway it seems like a couple of recent posts were how do I get to OTA from a rooted Nexus 7. Different deal to take the OTA then root if you haven't yet rooted the Nexus.
[Nexus 7 Android Development] rodem77:
My device was rooted too, root don't influence the OTA, modifications to sysmem files and recovery may stop the OTA.
[Nexus 7 Android Development] Grandroidster:
Can someone please help me out .. I attempted to Root my N10 and it ended up staying in the boot loop (i let it go for about an hour or so and still boot looping) .. it IS unlocked and the drivers and everything were installed according to instructions,but i wanna know how i can stop it from Boot looping.. ive restarted it over and over again via the button combo,but still boot loops.. i'm heading on Vacation ina few hours and wanted to mess with it so any help as soon as possible would be awesome ,thanks :)-
[Nexus 7 Android Development] n7of9:
did you have the correct device selected in the Toolkit? i only think of this because you are currently in the N7 thread rather than the N10 and thought maybe you did the same in the Toolkit?
[Nexus 7 Android Development] Alucard291:
N10 goes into bootloop after the unlock of the bootloader. (My friend's did when I was unlocking it).

One needs to enter recovery http://factory-reset.com/wiki/Nexus_10 (just in case you don't know how to)

and do a factory reset there. Seems to work afterwards.
[Nexus 7 Android Development] cmonsterf50:
Worked great. Took some sorting to get the drivers sorted. Great UI, super friendly. Thanks (Nexus 7 WiFi)
[Nexus 7 Android Development] Dark Jedi:
Must say I was never a fan of one touch root programs and I have rooted the od, dinc and bolt but I was getting confused on the nexus 7. So I said what the hay I'll give it a try and it worked almost flawlessly. I had issues with the drivers but solved that in 5 min with tour help files. Great little program. I'll hit the thank button after posting this.
[Nexus 7 Android Development] FingerBlastJ:
does this work on the vzw s3? im getting this message non stop and i tried everything and im running out of ideas?
[Nexus 7 Android Development] safesinger:
Can the Nexus 7 with 4.2.1(JOP40D) be rooted without unlocking the bootloader?

I've read on the nets here and there that it can be done on the 4 & 10 but haven't seen 7 in the list at all.
[Nexus 7 Android Development] RaptorMD:
I seem to be stuck getting the installation fully set up and though I am following the directions correctly, I am not able to get into Fastboot. Any suggestions?

**Edit - while I am starting over again in step 2 of setting up the drivers manually I am supposed to browse to " C:\Program Files\WugFresh Development\data\Drivers" and I do but it automatically pulls up the Samsung drivers which I suspect are in fact signed and while Wug's next step indicates to agree to unsigned drivers I don't have that option.

** Edit #2 - If I do opt for the Samsung drivers I get Android Composite ADB Interface
[Nexus 7 Android Development] Dark Jedi:
What I did was put the n7 in bootloader mode connected to the computer then I updated the driver and it worked for me.
[Nexus 7 Android Development] bby144:
The automatic installation of drivers isn't shown on this version, only the manual setup. Anyone know why?
[Nexus 7 Android Development] forpulse:
This is the easiest Rooting I ever done. I'm the noobest when it comes to rooting. But this toolkit made me feel so smart (although I did not do sh*t except clicking the root button). Just rooted my Galaxy Nexus (4.2.1) using Window XP.
[Nexus 7 Android Development] i root SGH i777:
so do i unlock first and then click root or do i just need to click root?
[Nexus 7 Android Development] reade0871:
Backup, unlock, root in that order
[Nexus 7 Android Development] mdwbeex:
+1

In a word: Badass.

This thing is awesome. Great work.
[Nexus 7 Android Development] reverepats:
Hey guys. Just got my Nexus 16gb last night. Now I come from the Sprint GSIII section. This is my first tablet ever. So ill get straight to the point. I've tried both tool kits here on XDA and even manually to install the drivers on my Win8 machine. For the life of me they jsut simply won't install, which in turn. I can't root my Nexus. I've done every step (that I can at least think of). Even if I head into Device Manager, right click then select "update drivers", and manually select the folder that has the derives. My PC just simply won't install them. I've been at this since yesterday morning. So I figured it was time to ask for help lol. So right now im at the point where i am installing the RAW Drivers. Went thru the correct process for this one. Each folder i select for the driver, Windows keeps giving me the error that it cant find the drivers. Any ideas why this is? Im now at my breaking point with this haha, no joke. THanks guys. Much appreciated

EDIT....Heres a Screenshot of the error that i get each time i select the driver folder.

EDIT...OMGGGGGG...Nevermind...FIanllly!!!....lol what a pain in the ass. Man oh man. Ive newver in my life had so much trouble.. THis was the best and most info on Drivers. Thanks again!!!...Time to Root...Hopefully that goes well now lol
[Nexus 7 Android Development] eagles20015:
I cant seem to restore my backup I made before I unlocked the bootloader and rooted my device. I did a backup of all my system apps + data. I tried to restore everything but when I attempt to hit restore my backup on my N7 it just reboots and nothing appears to happen. I am on 4.2.1 and my backup is from the same version. Anyone know how to fix this?
[Nexus 7 Android Development] Mallikanth:
Wug - I don't know if this is just me or an issue with how your script reacts to the latest TWRP........

Problem:

Attempting to run a Nandroid Backup from within the toolkit The N7 boots into TWRP but stops at the main screen of TWRP with the PC saying 'waiting for backup to finish and the device to re-start'. Nothing ever happens unless I intervene.

Software:

TWRP 2.3.3

NRT 1.6.1

ROM on the N7 is PA 2.99 Beta 9 (4.2.1)

Solution:

I've noticed when I do a manual Nandroid backup TWRP needs its settings re-set to default otherwise it stops almost straight away with a backup saying it can't find drive 'E'.

Manually re-setting TWRP and starting the backup within TWRP appears to make your script continue although I'm not convinced it manually copies the backed up files to your PC. Obviously this can be done manually but it defeats the object of using the tool to automate this.
[Nexus 7 Android Development] WugFresh:
v1.6.2 is near completion, I am in finalizing stages now, and testing. So I will look out for this behavior and see if I can reproduce what you experienced. The automation relies on a script file being pushed to your devices cache partition, which can only be accomplished with a modified boot.img. Try deleting your 4.2.1 modified boot.img in the toolkits \data\modified_boot directory, and letting it re-download that and try again. I may have re-uploaded that file. (this assumes you are on 4.2.1.. if you are on a different build, then do the same for that one). If that file is never pushed properly, then that would explain TWRP just sitting there. Let me know. I will test some things myself, that should not happen.

Looking forward to getting this new version out, lots of fixes and improvements. I completely rethought the updating process, and now it will be way more streamlined, and won't affect peoples download cap per day on Goo.im, because the text based update files are now hosted on pastebin. That is one of the changes among many other fixes. Stay tuned. :)

{{ WugFresh }}
[Nexus 7 Android Development] barrizzle:
Ok, love the tool, so easy to use, but I have one problem (not a problem per-say, really, but it is annoying). For some reason I can't mount my Nexus 7 through USB normally anymore after rooting and have to have USB Debugging on. I don't know if I accidentally deleted a driver I shouldn't have, but I thought I should still be able to add files normally, right? It won't pop up in my devices unless I have debugging on..help please :)?
[Nexus 7 Android Development] FReaKRaNT:
No, you must have debugging on.

Cheers, FReaKRaNT
[Nexus 7 Android Development] barrizzle:
Thanks a lot! I was freaking out thought I may have messed something up. :)
[Nexus 7 Android Development] jirafabo:
already running error

I installed on my 64bit windows 7 pc and I keep getting "An instance of Nexus Root Toolkit is already running..." popup warning when trying to run it for the first time.

I thought there might be remnants of a recent rooting of my girls Evo Lte running so I restarted. Still had the same problem, and the toolkit was the ONLY thing I opened after reboot.
[Nexus 7 Android Development] WugFresh:
That is really strange. Add me on gchat and hit me up. I haven't heard of that happening to anyone. Have you checked task manager? Maybe you try to run it and aren't giving it enough time to start? Use the included uninstaller and then try reinstalling it.

{{ WugFresh }}
[Nexus 7 Android Development] Mallikanth:
Perhaps accidental double clicks? I've seen my wife do this with a browser. She double clicks twice without realising it.

Restart the pc, right click NRT and then select 'open' . Does it complain then?
[Nexus 7 Android Development] jirafabo:
I restarted a million times, reinstalled 3 times, nothing in task manager related to anything android or adb, then I gave up. I even noticed on install when it starts itself after the end of installing, it still had the pop up error. After about an hour I gave up and used that other toolkit. I really appreciate your offer to join in chat and help. I'm sure it's something to do with my 6 year old laptop.

---------- Post added at 07:56 AM ---------- Previous post was at 07:55 AM ----------

I even tried right clicking and "run as administrator" same problem. Also, wasn't double clicking, error was happening even when the installer started the toolkit after installation.
[Nexus 7 Android Development] olfyboy:
I'm pretty frustrated right now...:confused:

I'm trying to install the drivers but I'm pretty stuck. I got the adb drivers installed once, but they didn't work, so I uninstalled them. Now, I can't install them again, and my N7 with usb-debugging enabled is recognized as an "unknown device". My PC won't let me install the adb drivers again. WHAT TO DO?

regards.
[Nexus 7 Android Development] WugFresh:
Version 1.6.2 is up, I will be updating the OP and the changelog on my site shortly. The update package is live as well, so you can get it through the toolkit via Help > About..

Lots of general fixes, code improvements, and some major enhancements to the updating system. Enjoy! ^_^

{{ WugFresh }}
[Nexus 7 Android Development] xI mEzMeRiZe Ix:
Awesome! Keep up the great work man. I just started using your toolkit the other day and I really love it. I used to use the ones from mskip, which are amazing as well, but it's much more convenient to use a single toolkit that handles multiple devices. Thanks for all of your work.

Sent from my Nexus 7
[Nexus 7 Android Development] whoamigriffiths:
Thanks for all your hard work

Thanks very much . I used this tool months ago to set up my N7 . But it is so great I keep it installed and updated just in case :good:Have all of my unnused thanks for today:silly:
[Nexus 7 Android Development] TheByteSmasher:
@WUG: I think I love you... in a totally hetero sorta way...maybe... :) Anyway, though you have done so much for us already, I still have the audacity to request a feature, if it's not too much... The ability to save multiple devices. I know, it's not that hard to pick a new device but I am inherently lazy so... Having a N7 and a N4 (and dreaming about a N10) it would just seem simpler... But either way, you've done a fantastic job already.
[Nexus 7 Android Development] Bigzinewicz:
Windows 7 or 8 driver install

Just connect device to PC with stock USB cable either running Windows 7 or 8, as I have tested, and enable USB debugging. Pull down notification bar and select USB options or go into storage and select the three dots in upper right hand corner and change from MTP device to camera and drivers for ADB should install themselves. If not install Android SDK and Eclipse plug in form Android developers website. Once ADB installed you will be good to go with or without any toolkits though this particular one is really, really, good. Thanks again to WugFresh for his hard work man this toolkit is the only one I will even bother to use on any of my Nexus devices not taking anything away from the other developers but this one just works.
[Nexus 7 Android Development] WugFresh:
Thank you for your hetero love.. Lol. I actually like your feature request, but I am not entirely clear on how you would want me to implement that. Like, you would still have to switch between the two devices.

Here is one way I could implement something like that off the top of my head:

I could make something in options menu, that would autogenerate custom Nexus Root Toolkit shortcuts for the end user; ones that would automatically open the program for a specific device. So for example: you would see two icons on your desktop one would say "Nexus Root Toolkit - N4", and the other would be "Nexus Root Toolkit - N7." - Both shortcuts would effectively launch the same toolkit, they would just open it with the settings for that device.

If you have another idea, or way to do this let me know. I am not entirely sure I understand your vision.

{{ WugFresh }}
[Nexus 7 Android Development] fredox19:
Thank you worked flawlessly
[Nexus 7 Android Development] TheByteSmasher:
That's one way, but it would require 2 shortcuts. My thought was radial buttons in the left hand pane. Like a "my devices" section with my devices listed underneath with a radial button next to each. The program would open up with the last used device, and its pick the one I want but here is the cincher... the update feature would see what devices I have and update the files for all of them at once instead of picking each and updating. Also an "auto update files for my devices at program start" option would be perfect. That way, I could A. Easily switch between devices. B. Update all files for all devices at once. C. Never worry about forgetting to update because it would look and get the required files for all devices at start. Whaddya think?
[Nexus 7 Android Development] FierceMist:
Very nice program. However I did notice one little bug. When downloading TWRP the progress bar just goes to 1% and doesn't go any further. The hash is always fine though and I believe that TWRP gets downloaded fully either way.
[Nexus 7 Android Development] WugFresh:
? Which device. You are telling me it says a hash match after only going to 1%? I don't see how that is possible. It could say "complete" but then hashcheck mismatch. If you are running this latest version, it has a built in contingency plan, and brings up an interface to download the file manually. Can you confirm you are running v1.6.2?

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
All that auto updating per your specific device when starting the toolkit is already done in this release. So B and C are already done. My problem with your idea with the radio buttons is that it doesn't let you choose your build. The Change.. Button does what I want. I will think it over and see if I can come up with an idea that gives you the functionality you are after.

{{ WugFresh }}
[Nexus 7 Android Development] TheByteSmasher:
OK, so instead of radio buttons how about choose buttons next to each device? Also, it doesn't update for EACH device on startup because it doesn't know what devices I own... it only updates after I press the choose button, to cut down on unnecessary downloads, right? So of our knew what devices I own... get it?
[Nexus 7 Android Development] Mr-Glass:
Wug - I am getting the "complete" when it is not - with the hashcheck mismatch. I was able to download manually, but was wondering why this was happening, the only thing different for me is I am now on Win8 with v1.6.2 compared to Win7 with v1.6.1 when I originally used the Toolkit.
[Nexus 7 Android Development] WugFresh:
Again.. what device? Nexus 7? Just making sure. Maybe I need to reupload the file. The issue is server side, not with the toolkit.

{{ WugFresh }}
[Nexus 7 Android Development] Mr-Glass:
Sorry about that - Nexus 7 Wifi JOP40D