yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Kiszonyogor95:
Yeah I know it ;)

But honestly if I know sth I always wanna share this knowledge with others ;) thats why this forum exists ;)

Good luck, Im happy I could help You ;D

Tapnięte z mojego Galaxy S3
[Nexus 7 (2013) Android Development] rraaka:
i used Wugs method to unlock, root, custom recovery, busyboxed my N 7 yesterday and i wanted to share my experience too.

the driver issue is a BIG one, the pda method worked for me

after unlocking again the driver issue posed a problem ....at one point i switched off MTP but later when i wanted to find it i couldnt :cyclops:

googled and found it in storage section :o

after everything was over i wanted to transfer files and couldnt see internal card- googled and found this post - it got 11 thanks - "Here's what worked for me:

I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted" .- maybe they are kiszons not sure and yes it worked for me too.

at one point i wished the toolkit would also act as a file manager - i could install apks through it but not tranfer files.

im scatter brained and was all over the place yesterday - but alls well that ends well :)

this thread should be sticky in general section - im sure i would have cried if id chosen the manual method there, i found this thread from the video comments mentioned there.
[Nexus 7 (2013) Android Development] Kiszonyogor95:
In my case, file transfer was workin ok with debugging on.

But generally if you couldnt do sth with your device connected, you should follow these steps:

1. Choose the mode you want (mtp, usb debugging and so on)

2. Plug nexus into computer

3. Delete adb drivers

4. Reboot nexus when its still plugged

5. Let windows install the correct drivers

6. Have Fun!

Hope that know no one should have any problems with usb connection ;D

Cheers!

Tapnięte z mojego Galaxy S3
[Nexus 7 (2013) Android Development] mmoreimi:
Fantastic tool! Worked great, as usual.

Question -

If I unlock the bootloader only, will I still be able to receive the 4.4 OTA without any "messing around"

same question for rooting. Will I be able to still accept the 4.4 OTA? I won't be flashing an alternate recovery or kernel, etc... just rooted stock.

Thank you much!
[Nexus 7 (2013) Android Development] LoopDoGG79:
My experience with flashing, you can only receive an OTA update you have to be fully stock. Locked bootloader, not rooted.
[Nexus 7 (2013) Android Development] WugFresh:
Short answer to your question is yes you can - assuming that the none of the root apps you may run make any system modifications to your device (build.prop tweaks, overclocking, etc.).

Taking an OTA will make you lose root, so you will just have to re-root afterwards. Since you will lose root from updating, you might as well unroot before accepting the OTA in the first place which you can easily do from within SuperSU's settings menu (Full Unroot) - however this is probably not necessary.

A more detailed answer is here: http://www.wugfresh.com/faqs/can-i-still-take-an-ota-after-i-unlock-and-root-2/

Personally I never bother with OTAs. I just use my toolkit or Titanium Backup to backup my apps and then use the "Flash Stock + Unroot" button to directly flash to the new version.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] jsonger121:
hey wugfresh! thanks a lot for the tool kit! worked like a charm!!

just one question, ive been out of the "game" here lately and haven't been on here in a while, and was wondering if the jss15r was the latest build number?

i just did the flash stock+unroot option and was wanting to accept the 4.4 ota when i get it and i know you have to be on the latest build for it to work so...

thanks again for all the work you put in!
[Nexus 7 (2013) Android Development] r-l:
QUESTION !!

i'm getting back to stock 4.3 and the programm is stuck (i think) on erasing 'boot' .. it's on that for almost 10 minutes.

how long does it take to go further ???

edit: i needed to switch usb ports
[Nexus 7 (2013) Android Development] tommi.a:
And my experience: I received the JSS15R update OTA with open bootloader and rooted but with stock recovery.

Afterwards i had to reroot.
[Nexus 7 (2013) Android Development] doubleho:
any chance rooting an kitkat???
[Nexus 7 (2013) Android Development] WugFresh:
? If you are asking if this toolkit roots KitKat Nexus devices.. Then the answer is yes.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] doubleho:
so should i choose nexus7v2 wifi with.custom rom?coz the newest i can see is jss15r(i mean when i choose the version of my device)
[Nexus 7 (2013) Android Development] WugFresh:
Oh. For rooting KitKat on devices that Google hasn't released the factory image packages yet, use "Any Build" mode (for now). I will get them listed in NRT when Google publishes those packs.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] cinco312:
Yep. I rooted it last night after the update. Great tool!
[Nexus 7 (2013) Android Development] doubleho:
i rooted it just now,thz
[Nexus 7 (2013) Android Development] giank30:
tried again to root my N7 v2 WIFI after upgrading to KitKat... all went without probs... but in the end it keeps on saying that my device is not rooted... moreover i cant find the supersu app on the app drawer.

Please help....
[Nexus 7 (2013) Android Development] cinco312:
Flash the SuperSu in recovery

http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip
[Nexus 7 (2013) Android Development] giank30:
COOOL!!!tt thank-you
[Nexus 7 (2013) Android Development] cinco312:
You're welcome! Be sure to hit the thanks button for me :good:
[Nexus 7 (2013) Android Development] fergiet:
Just updated to KitKat on my Nexus 7 2013 and rooted with TWRP. Many thanks Wug's toolkit made it so easy and no need to wait for the OTA.

Great work "Wug"
[Nexus 7 (2013) Android Development] redeuxx:
I just wanted to get root on KitKat without flashing a custom ROM or recovery. Is this possible with Wug's toolkit?

Thanks!
[Nexus 7 (2013) Android Development] tommi.a:
Yes, of course!
[Nexus 7 (2013) Android Development] tennessee_titan:
Took me 6 hours yesterday to get root. Could not make the drivers stay installed. Had to continually reinstall. Finally got it though, and it works great!
[Nexus 7 (2013) Android Development] WugFresh:
That seems really strange. Did you check the RSA prompt, "always allow from this computer". Check out this video Either way, glad you got it working.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] tgyberg:
Awesome toolkit got me out of a jam! Donated some beer money!
[Nexus 7 (2013) Android Development] ChadtheBuilder:
Re-Root

I used this toolkit to root my Nexus 7 almost as soon as it was released. Now I have gotten a bit tired of flashing ROM's, and all that, and I plan on returning to stock, and then rerooting so that I can still use apps that need root permission, but be using the stock Google ROM. Whenever I am rooting again, do I need to check the option to flash custom recovery? I don't need to be able to use one, since I won't be flashing anything. I just wanted to know if this is mandatory to gain successful root.

Thanks
[Nexus 7 (2013) Android Development] tommi.a:
Root w/o custom recovery then you can even get OTA updates.

At least for JSS15R this worked for me.
[Nexus 7 (2013) Android Development] ChadtheBuilder:
OK, that's what I want. I want to be able to get OTA updates and then just reroot after them. I only need root access for apps.
[Nexus 7 (2013) Android Development] tommi.a:
Yep, same for me.
[Nexus 7 (2013) Android Development] tgyberg:
^ Why, just flash a pre rooted zip of any new update. They are available about 5 minutes after the update starts rolling out! :)
[Nexus 7 (2013) Android Development] timrock:
hangs on Booring twrp Temporarily. tried about 5 times. I just unchecked the option and rooted it.
[Nexus 7 (2013) Android Development] dezzo77:
Well, I've tried all the steps and the troubleshooting, and no matter what I do, when I run the Full Driver Test it always says, "ADB device was not found".

I tried it on my Windows 7 desktop and Windows 8.1 laptop and it was the same result.

On Step 1 section 2 it says to delete the drivers from device manager and click the "Delete the driver software for this device", but that option is not available when I delete "Nexus 7" from device manager. That is the only part of the instruction that doesn't match up with my computer. I'm not able to delete the local driver files when removing the device.

- I deleted all references to Nexus 7 from the device manager.

- I used the USBDview and removed Nexus 7 references (even even some for my Samsung S3) and restarted the computer.

- I ensured USB Debugging was OFF and MTP mode was ON and then connected the tablet again via USB as instructed in Step 2 section 1.

- Windows 7 detected and installed the drivers for MTP.

- Step 2 section 2 tells me to re-enable USB Debugging again. At this point Windows 7 starts detecting devices and tries to install new drivers. "USB Composite Device" and "Nexus 7" both say "Ready to Use", but the second "Nexus 7" item says "No Driver Found". At this point in device manager, Nexus 7 shows with a yellow exclamation symbol and say "driver for this device are not installed."

- At this point I installed the Universal Drivers and moved on to Step 3. After running the Full Driver Test, it still says "ADB device was not found".

I ran the entire procedure again using the RAW drivers, and got the same result.

I also tried the Universal Drivers on Windows 8.1 and still got the "ADB device was not found" message.

I didn't try any further on Windows 8.1 as it started to require more steps to install the other drivers and by this point I was just sick of it all.

I'm using the official ASUS USB cable, and I've tried several different ports.

So, what do I do now?
[Nexus 7 (2013) Android Development] LoopDoGG79:
Connect Nexus 7 to PC

Open up device manager in Windows.

Go here and download the latest Nexus drivers.

http://developer.android.com/sdk/win-usb.html

Extract zip.

Update drivers by browsing PC, and directing to the folders where you extracted the Google Nexus drivers.

Hope that helps!
[Nexus 7 (2013) Android Development] cinco312:
I had the same issue on Win 8.1. I installed the Samsung driver and got it working after that.
[Nexus 7 (2013) Android Development] dezzo77:
I managed to get it working after installing the "pdanet" drivers and forcing the google USB driver to update via device manager.

At least, that's what I think I did... it's hard to remember everything since I spent so many frustrating hours on it.

In the end I got Android 4.4 installed and unlocked and rooted using Wug's toolkit.

Unfortunately, I'm now having some WiFi issues on the tablet.

A lot of websites are not loading unless I try multiple times, Plume is having some issues loading certain things, and YouTube was cutting out and refusing to continue playing. I've never had these issues before on the Nexus 7,so I'm going to do a factory reset and see if that clears it up.
[Nexus 7 (2013) Android Development] jessejames44:
I think the best thing to do is install multirom run a few Roms pick and choose what you want.
[Nexus 7 (2013) Android Development] Philly Jim:
Did you ever manage to get everything working properly,? Because I've tried like you for hrs on end and I get the same error message you where getting , my neighbor and I both purchased these last Thursday night , and after 3 separate computers 4 different usb cables , I still have two stock unrooted tablets .................
[Nexus 7 (2013) Android Development] yosh76:
Dear Wug's, It would be nice if you always check and change incorrect spelling/word on your toolkit.....for example (Unistall ----- should be Uninstall) ---> on Full Driver Configuration Guide section...hope you aware it :). This is part of the update/fix too...
[Nexus 7 (2013) Android Development] WugFresh:
I was not aware of it. Can you blame me? I am staring at over 10 thousand lines of code when I work on this.. The text in message boxes is the last thing I notice.. Lol. :)

Thank you for notifying me. If you ever see typos please let me know. I am just one person building this so chances are if you see a typo - I am not aware of it.

I will add it to my to-do list for v1.7.9

:) Cheers.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] LoopDoGG79:
Finally decided to unlock and root. Was completely hassle free and quick on my stock kit Kat build. Though, I did run into a problem........

Deciding what ROM to flash first!! :D:D:D
[Nexus 7 (2013) Android Development] dezzo77:
Ugh... I hate to even respond to this because I honestly don't remember exactly how I got it working and I don't want to waste your time. :)

It was my first time modifying an Android device and I screwed with it for hours and hours and had a number of rage moments along the way... so it's hard to remember with clarity. lol

This is what I *think* I did to fix it...

Download the latest version of the Google USB Driver and extract the contents. There is a file included with those drivers called "android_winusb".

At this point, I think my Nexus 7 was still showing under "Portable Devices" in Device Manager as having an error (no driver present).

No matter what I would do, Windows 7 would always fail to install the driver for it automatically.

If you turn on Debugging Mode while connected via USB, a new item should appear in the Device Manager called "Android Device" with a sub-item that I can't remember the original name of (but there was only one item for me).

Go to the Properties of that item and "Update Driver..."

Then, "Browse my computer for driver software" --> "Let me pick from a list of device drivers on my computer" --> "Have Disk..." --> "Browse..."

Point it towards the "android_winusb.inf" that you extracted from the Google USB driver kit.

Now, I think the one I selected was called "Android Composite ADB Interface"... but at the moment it shows "Google Nexus ADB Interface" under "Android Device" instead, and it shows I'm using the ClockwordMod driver from 2012... and not the newer Google USB/ADB driver I'm talking about here... another reason why I'm unsure of what really happened.

But I DO remember updating that driver and messing with it some more, then finally got it working... somehow.

And I think that is when I got the Nexus 7 item under "Portable Devices" to stop complaining about the driver not being installed. (Win7 kept failing to install it). When I check the driver for that item, it shows I'm using a default Windows driver from 2006, so I know that's not the one I updated. I think updating the ADB driver is what made it all work.

I think I got the clue about updating the ADB driver from a link to another discussion that was mentioned somewhere earlier in this thread.. but the steps it gave me for updating the driver weren't totally accurate and I had to figure it out on my own by playing with it a few times.

I might have had to toggle the "Show compatible hardware" option after pointing the driver updater to the "android_winusb" file.

Again, reeeally I hate to offer advice when I'm uncertain on details... but, it's something you can try anyway if you're still having the problem.

Sorry I can't be of more help than that. :/

Also, the problems I had with WiFi and touchscreen completely went away after I restored back to stock, then repeated the process of flashing, rooting and installing custom recovery again.. all is fine now.
[Nexus 7 (2013) Android Development] ilikegoogle:
I'll try that as I am also having problems using Windows 8.1. I flashed back to stock 4.4 using the toolkit, but when I try to root it, it does not recognize the drivers. I probably have to uninstall then install them again on the pc.
[Nexus 7 (2013) Android Development] cinco312:
Just install the Samsung driver through the toolkit. That seemed to work for me on Windows 8.1
[Nexus 7 (2013) Android Development] Foulwx:
Thanks for the great program. Earlier today I unlocked and rooted my N7 with NRT. Then this evening I found a one-click program that installed KRT16s, but with that upgrade I lost root and custom recovery. Since the NRT is only updated to KRT16O, can I still use this to root right now? Thanks in advance!
[Nexus 7 (2013) Android Development] LoopDoGG79:
Yes you can, I rooted and flashed a custom recovery on KRT16S with no issues.
[Nexus 7 (2013) Android Development] BDR456:
That is exactly the trick. Make sure that setting is checked in options and restart the toolkit.:thumbup::thumbup:
[Nexus 7 (2013) Android Development] banshee28:
Still having an issue. Device Manager sees the device as a Sumsung>Nexus7. Not sure why its Samsung vs Asus. I DID fully uninstall all the Samsung,Google, and any other android drivers using the USBDevice utility. Then I reinstalled from this tool and it installs and see it fine, no errors, but wont complete the Full Driver Test saying Device not found. Its in USB debug mode and I have cycled that and rebooted 3-4 times, but same issue. Maybe the drivers are just wrong, but this is what installed when I choose the option 1 drivers.
[Nexus 7 (2013) Android Development] Ibkevin:
I assume this toolkit is only for PC right? I want so badly to unlock/root and install recovery on my new nexus 7 but I only have an iMac to root with and can't seem to find anything for rooting the latest with Mac?
[Nexus 7 (2013) Android Development] mssam:
You might have to play around with installing the drivers (or deleting something) through the Full Driver Configuration Guide a couple of times. Not sure if you're using win7 or win8, but I'm using win8 and in device manager, the n7 shows up as Android Composite ADB Interface. Also, when I eject from the taskbar it shows up as Eject MTP and it can complete the test with success...
[Nexus 7 (2013) Android Development] Semantics:
Is there any reason my AV program is flagging a Trojan on this install? I've never had that happen on a toolkit install. Just trying to see if its a false positive or something.
[Nexus 7 (2013) Android Development] Stanlehh:
I'm running JWR66N, didn't update to JSS15J as I'm afraid of the touch issues that some other users face after updating but I don't see this build option available for me to select under model type, please advise, thanks!
[Nexus 7 (2013) Android Development] GrandMstrBud:
Can't do CWM recovery it's greyed out. Also took a while to get it to work right. Thinking the manual way is much easier. Took about 3-5 times to get it to unlock the bootloader and on root it hangs up at waiting for device. The other toolkit doesn't even recognize the device and yes ADB is killed and recognized in DM and USB debugging is enabled.
[Nexus 7 (2013) Android Development] aiiee:
Best one out there bar none. And he doesn't even make fun of you or try to belittle you when you ask questions, unlike *some* ( ONE ) dev here...

( yeah you )
[Nexus 7 (2013) Android Development] Gareee:
I ran into the same issue as others, and had to turn on the setting to temp boot twrp. After that, it was smooth sailing.

Maybe that option should be toggled on by default?

One question though.. I don't see the tablet connecting as a media device when I plug it into the usb now, so I can't manually put files on the tablet.

How do I restore the normal usb connectivity now?
[Nexus 7 (2013) Android Development] wrichards2009:
Hey so I did this installed the drivers device detected, everything was going fine, unlocked, and went to root. And now I can't turn it on. It has the padlock unlocked but it goes to an android with a red ! afterward. Can't do anything from there I've tried every button combination...

---------- Post added at 02:49 AM ---------- Previous post was at 02:31 AM ----------

OK so i can still get back into android, but after I press root + install recovery it goes to bootloader, supposedly flashes recovery, reboots into android, supposedly pushes root files, reboots into recovery and THEN it gets the red x...

Does that mean its failed to install a recovery?
[Nexus 7 (2013) Android Development] banshee28:
Well I am using an old XP install on a Netbook!! LOL

So since this did not work, I uninstalled all drivers and tried the next one. It did the same thing, so I went down the list and uninstalled the old, rebooted and tried each new one all the way to the RAW drivers and same thing. It installs fine, DM shows it good with no errors but always get the device not found when doing the Full test or trying to do something like boot to recovery. I was about to go get the official android drivers and try that, but not sure if thats the same as through this app?
[Nexus 7 (2013) Android Development] Gareee:
In case anyone else has the issue.. home screen, settings, storage, settings usb connection, media device
[Nexus 7 (2013) Android Development] wrichards2009:
If anyone wants to know... the issue I was having about getting the red screen.. it was failing to install recovery. Not to be a jerk or a troll but I used hasoons version and it worked the first time..
[Nexus 7 (2013) Android Development] Gareee:
I considered hasoon's, but the instructions on where to put the base files was unclear, and there were a lot of people with install issues, so I opted for this one.

I''m still having an issue though, and I suspect its usb driver related.

I can connect usb as a camera, but if I connect as a media device, it never shows up in windows so I can browse to the phone and drag n drop files. And I hate to fiddle with the drivers again, because getting adb to work completely took more time than root and unlock.

Anyone with fix ideas for this issue?
[Nexus 7 (2013) Android Development] wrichards2009:
Do you have windows xp?
[Nexus 7 (2013) Android Development] Gareee:
Nope.. windows 7 64 bit.

I can move files into the camera folder for now, and then relocate them where I want them on the tablet, but I need to resolve this at some point.

It looks like I can install roms and such with twrp, and I'd only need adb if I wanted to unroot return to stock, so if I can't resolve this in a few days, I'll remove the drivers on my pc, and then let windows do them automatically to see if it fixes the issue.

Something else I just noticed.. on stock, there is no google search bar on home, but on this install, its at the top of the home screen, and stays put even between homescreens. And there apparently is no way to remove it.

Kind of redundant, since you can long press home to pull it up.

I'm considering cleanrom, and that might clear that issue up. 9Waiting for the author to upload a new update)

EDIT: managed to correct the issue after much googling.

connect nexus to usb

open device manager

uninstall the adb driver

unplug the nexus, wait a few seconds, and plug it back in

It should reinstall a driver and you should now see it as nexus 7, not google adb device

The Caveat of course, is now that the nexus works properly again with the usb port, the wug driver checker now fails, and wug no longer works because the drivers no longer pass.

:sigh:
[Nexus 7 (2013) Android Development] hhhstonehhh:
I cant download nexus 7 v2 flash stock + unroot file
[Nexus 7 (2013) Android Development] fstbusa:
Does it say it's not available? I don't believe Google has released the code/stock build yet so I don't think it's available to download.
[Nexus 7 (2013) Android Development] danvee:
Nope.

Until Google releases it, you can't download it...
[Nexus 7 (2013) Android Development] Valkurm Emperor:
I unlocked my phone and installed CWM but for some reason now the sdcard isn't mounting, whenever I try to install a zip from it I get:

E: can't mount /sdcard/

Nor can I boot into my system, like it never existed.
[Nexus 7 (2013) Android Development] ddskier:
I have been trying to flash TWRP on my Nexus 7 that has been newly updates to KRT16S. It boots up to the bootloader menu, but when it tries to flash the custom recovery the Nexus device freezes and nothing gets updated. I end up having to power cycle the unit.

I have tried setting the firmware on the rootkit to both Any firmware and KRT16S. Both fail.

What am I missing here?