yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Deksloc:
Only the two things I circled in the picture I posted last show up. "Android Phone > Android Composite ADB Interface" and "Portable Devices > Nexus 7". This is with USB-Debugging on, and MTP on.

And I've deleted everything with the VendorIDs of 18d1 and 04e8 (in fact, nothing under 04e8 comes up to begin with). I'm not sure where I'm going wrong. I've attached the HTML report from USBDeview as a PDF and in a RAR (XDA doesn't allow HTML file uploads, and in case you don't like opening random internet PDFs). It's sorted by VendorID so you can easily see there's nothing left from 18d1 or 04e8, but you guys might be able to see if I'm missing something else.
[Nexus 7 (2013) Android Development] Pandae:
Strange it's bringing up the first one, but you have the second one to play with: right-click it, select Update Driver Software, then point it to the drivers from Google (which you'll have to unzip first to a directory).
[Nexus 7 (2013) Android Development] Deksloc:
So I've gotten my drivers to work I think. I tried updating them from the Device Manager launched by the shortcut on Step 1's page of the NRT, but none of the buttons for "Update Driver" or "Uninstall" or "Disable" would actually do anything when pressed. They weren't even grayed out. So on a whim I went into Computer Management which let me get to the Device Manager as an admin, and there I was actually able to update the "Android Composite ADB Interface" (this guy was the issue!). I think it might be worth noting that the shortcut doesn't give you admin privileges, so it might help someone.

Now I'm trying to root + install the custom recovery. I don't think this is going to work, since it's been hanging on "Booting modified boot.img to enable running privileged commands..." for about 10 minutes now. I'm just going to kill the process and retry without the custom recovery option checked.

Thank you guys so much for your help getting my drivers sorted out!

Edit: I'm not out of the woods yet...

I've been trying to get the toolkit to root my Nexus, but it's still hanging. Here's the log the toolkit gives:

Live log initiated.

Information: Checking ADB Status

adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

serial #	device

ADB Status: Device Connected

Information: Rebooting your device into bootloader mode...

adb reboot bootloader

Information: Checking Fastboot Status

fastboot devices

serial #	fastboot

Fastboot Status: Device Connected

Information: Booting modified boot.img to enable running privileged commands...

fastboot boot "C:\Program Files (x86)\WugFresh Development\data\Modified_Boot\modified_boot_nakasi_4.4.2_KOT49H.img"

I've tried it with the custom recovery option unchecked, with different USB cables, with different USB slots, and with the alternate syntax for fastbooting boot.img files, which are what was recommended for others with the same issue in other threads for the NRT. I've also tried using a different download source for the modified boot image and deleting the one I had already downloaded.
[Nexus 7 (2013) Android Development] Pandae:
There I cannot help you, sorry. I haven't used Wug's kit in a long time and have forgotten. I do things manually, if you'd like to start another thread for that. :)
[Nexus 7 (2013) Android Development] daddlefan:
:angel:ß

Version of fastboot/adb.exe (plus dll´s) must be younger or equally old than adb/fastboot drivers (check " winusb.inf" for info).

If the date (version) of adb- and fastboot.exe ( plus dll-files) is older than the adb/fastboot-drivers date (version), you might run into problems. Or they don´t start or malfunction !

You can check driver´s date (version) before installing by opening the xxx.inf -file. In the top you find the version-number and the release-date.

With preinstalled drivers you can see the release-date and version in device-manager !

The fastboot- and adb.exe - files are easily identified by its size. Actual is Google Version 8.0 for drivers, size fastboot exe = 160 768 bytes and size adb.exe = 816 200 bytes!

Did you check these? Normally, with freshly installed toolkit, you als get the newest exe's, but after you fiddling around manually with the driver installatin some things might have got mixed up.
[Nexus 7 (2013) Android Development] Deksloc:
Ok so since you recommended I make sure the .exes were newer than the drivers, I ran the SDK Manager to update them, and when it finished, I still couldn't get the NRT to root my Nexus. So I uninstalled and re-installed the NRT and tried again, and now it won't reboot the tablet into bootloader mode. The original problem.

This has proven to be the most frustrating Android device I've ever had when it comes to rooting, etc, which is ironic considering it's supposed to be so development friendly.
[Nexus 7 (2013) Android Development] daddlefan:
Sorry for you, but I am a little bit mixed up. In your posts before you mention: "it's been hanging on "Booting modified boot.img to enable running privileged commands..." for about 10 minutes now". Now you say: "it won't reboot the tablet into bootloader mode" but say its the original problem again? Well, booting in "bootloader mode" and booting "modified boot.img" are two different things

Whatever, try to go into bootloader mode manually first [pressing Vol.(-) and Power for a couple of seconds] and check in Device-Manager if the Android Phone-entry shows > Android Bootloader interface, then press Power-Button while the Bootloader Screen shows the green arrow labeled "Start" and check in device.manager again if the Android Phone sub-entry changed to "Android Composite ADB Interface".

And run in Wug´s Toolkit "Step3" by checking in first screen "Full Driver Installation Guide" , then in Step3 "Full Driver Test". If this test returns "Success" and still the Rooting stops with an error "the modified boot-image failed", then you might have a hardware problem.

Last chance, did you start Wug´s Toolkit with administrator privilege ?
[Nexus 7 (2013) Android Development] Deksloc:
Sorry if I was unclear. After your last post, I updated the Android SDK on my computer to make sure that I had the most up-to-date fastboot.exe and adb.exe, but then I realized that the Nexus Root Toolkit comes with its own set of the SDK tool files, so to update those ones, I uninstalled the NRT, and then re-installed it.

I think something is wrong with my ADB/Android SDK installation, or at least the one in Wug's NRT folder. Before updating and re-installing the NRT, the tookit's log returned this:

Information: Checking ADB Status

adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

(serial #)	device

ADB Status: Device Connected

Information: Rebooting your device into bootloader mode...

adb reboot bootloader

Information: Checking Fastboot Status

fastboot devices

serial #	fastboot

Fastboot Status: Device Connected

Information: Booting modified boot.img to enable running privileged commands...

fastboot boot "C:\Program Files (x86)\WugFresh Development\data\Modified_Boot\modified_boot_nakas i_4.4.2_KOT49H.img"

As you can see, it reboots successfully into the bootloader, and then begins booting the modified boot.img. It never actually does anything.

Now, the toolkit's log returns this:

Information: Checking ADB Status

adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

(serial #)	offline

ADB Status: Device Connected

Information: Rebooting your device into bootloader mode...

adb reboot bootloader

adb server is out of date. killing...

* daemon started successfully *

Information: Checking Fastboot Status

fastboot devices

And then I get a message saying that NRT can't detect fastboot, and it's because the tablet never reboots into the bootloader automatically. Before I did the updating and re-installing, I had got it working to reboot automatically, which hadn't been working before. Hence my stating that I was back at the original problem. Running the full driver test previously returned with the success popup, but now it doesn't. And when I tried using the root + install custom recovery function of the toolkit, it never returned the error "the modified boot-image failed", as you think, it simply never actually did anything. Instead, it would sit hanging with the message "Booting modified boot.img to enable running privileged commands...". So I don't think it's a hardware issue, but I won't rule that out completely.
[Nexus 7 (2013) Android Development] daddlefan:
I do think it is time for Wugfresh to help you out!

You have to get your Fastboot- and ADB-Drivers working, both in ADB-mode (System) as well as in fastboot-mode=(bootloader-mode) .

Check in Device-Manager the drivers date and version both booted in system and booted into bootloader.

It should say for example Google Version 8. date 07.09.2013 when you installed the drivers downloaded with the SDK.

The Version 8 definitely works with the adb- and fastboot.exe Wugs NRT makes use of.

Why did you install sdk? Google drivers Version 8 are to be found in Path:

c:\Wugfresh´s folder\data\Drivers\RAW_Drivers\Google_Drivers\

, and the adb- and fastboot exe´are in Path:

c:\Wugfresh´s folder\data\ (inclusive the two needed dll´s)

You don´t have to download any other drivers, they are all in the toolkit! Thanks to Wugfresh!

So doing drivers installing manually you can always specify your path to the needed drivers in your Wug´s Toolkit - folder. Just insert the correct folder path-name wherein your Toolkit is installed.

Knowing this you can use usb-deview, started as Administrator (rightklick on usbdeview and choose "Starting with Admin privileges" in Path:

c:\Wugfreshs Folder\data\Drivers\Driver_Utilities\

,

to deinstall again all with your Nexus 7 linked entrys VID_18D1&PID_4E40 , VID_18D1&PID_4E42&MI_01, or VID_18D1&PID_4E44&MI_01,

then reboot your windows (which Version, 7 or 8?), check in device-manager that there is no entry for AndroidPhone , otherwise start usb-deview again to delete remaining drivers or redo driver uninstalling with Wug´S toolkit. After reboot finally there should be the entry "Unknown Device" with yellow print/exclamation mark in device-manager. Do not start installing new drivers before this "Unknown Device" shows up!

Then install drivers again, as described above for manual installing or use Toolkit´s driver installation.

Which Driver Step did you use before? I would prefer Step 4 Raw Drivers/Google Drivers! Then try again to root.

Edit: Which Version Drivers you get when you check in Device Manager your last installed drivers? It should say Google drivers Version 8.0!

You did choose the right Model Type and Android-Build in the Toolkit Basic Features: V1 or 2, Mobile or WiFi type?

[MENTION=3110798]WugFresh[/MENTION]: i have the feeling that it is always difficult to get the drivers completely deinstalled which are installed by exe-files, like PDA-Net drivers or Universal-Drivers, , except you use the uninstall-routine which comes with them, and even then. Is that correct? Thanks
[Nexus 7 (2013) Android Development] neiko:
Smashing work, had to set mine the camera to find the device
[Nexus 7 (2013) Android Development] username4this:
Can you actually restore stock ROM with this automatically or do I have to get the ZIP file from somewhere else?
[Nexus 7 (2013) Android Development] mdamaged:
It gets all the files you need automatically.
[Nexus 7 (2013) Android Development] WugFresh:
Make sure you selected the correct N7 device in the toolkit or make use of the auto detect.

Hanging on booting the mod boot.IMG is indicative of selecting the wrong device or build.

Sounds like your drivers are configured so you can stop messing with that.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] Mentalist_:
I can't get past the booting boot.img, my device just freezes:(
[Nexus 7 (2013) Android Development] memaro_maro:
it is a new kernel (boot.img) that you flashed?? not enough info for a solution.

~just flash another kernel that you used before or modified boot.img (fastboot). that bootloop didnt cause by wugfresh toolkit
[Nexus 7 (2013) Android Development] mrbarnie:
changing from dalvik to ART

Hi,

does anybody know who I can permanently switch from dalvik to ART runtime?

I read an article which says that it will improve speed a lot.

Unfortunately it doesnt work for my rooted device.

Nexus 7 V2 LTE

Android 4.4.2. (KOT49H)

I am looking forward for you suggestions ;)

Thanks

MrBarnie
[Nexus 7 (2013) Android Development] memaro_maro:
haha.. ??? wrong thread.. !!

setting > developer options > select runtime.. ART there.. reboot.... wait until fully boot up (maybe 15- 30min)

try your own.. its good, but i dont like it..
[Nexus 7 (2013) Android Development] kersey:
Can I restore from a stock factory .tgz file that I've got on my pc if I wanted to?
[Nexus 7 (2013) Android Development] Acres4:
Does it work on stock 4.4.2?

Does this work on stock 4.4.2 Nexus 7 2013?
[Nexus 7 (2013) Android Development] mdamaged:
Yes, to both of you.

[MENTION=1802311]kersey[/MENTION], select flash stock, select other/browse, then navigate to the tgz.
[Nexus 7 (2013) Android Development] mdamaged:
Yes, as long as you have the correct drivers installed, and are careful to select the correct model, and you follow the onscreen prompts to the letter. It will not flash a custom recovery unless you select it (by checking the check box next to Custom Recovery), if you do not select it, it will temporarily boot twrp but this will not overwrite the recovery you had on there.
[Nexus 7 (2013) Android Development] Acres4:
Thanks, do I have my N7 turned on when i do this?
[Nexus 7 (2013) Android Development] mdamaged:
Yes. Start it as you normally would, Wugs toolkit will do the rest, and remember, select the correct model from the dropdown and follow the prompts to the letter.
[Nexus 7 (2013) Android Development] Acres4:
Thanks so much. When I do a backup in the toolkit, after I have rooted and unlocked boot loader do I just press restore and I will have all my data?
[Nexus 7 (2013) Android Development] mdamaged:
With the android backup under "Backup all Apps", I can't say for sure, I did not use it myself, and based on what I've read, YMMV. I would probably suggest that is the app data is super important, one boot into twrp and do a nandroid backup BEFORE trying that other backup. You can do this in the tookit under Advanced Utilities, just click on "Custom Recovery" under the Boot Temporarily section, then do the nandroid from with in TWRP, this will not overwrite your recovery. That way if the app backup does not restore you can always go back to the nandroid and try again.

I _think_ that the Create Nandroid w/Custom Recovery within the backup/restore does the same exact thing, but I went the manual route in case it flashed twrp instead of booting it temporarily. (At that time I wanted to keep stock recovery, I've since gotten passed that and have multirom with it's customized twrp making wugs toolkit, as awesome as it is, obsolete for me).

You can also try Helium backup, which I've heard great things about and does not require root.
[Nexus 7 (2013) Android Development] WugFresh:
To clarify, that feature does just temp boot it.

But yeah - either way works. :)

Yeah, once rooted there are some great backup apps. I typically use the toolkit for automating nandroids and Titanium Backup for selective backups.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] mdamaged:
Thanks, wasn't sure how that worked.
[Nexus 7 (2013) Android Development] merwin:
Root not working

I was able to successfully unlock my Nexus (brand new). That part of the process worked smoothly. However, when it goes to root/flash custom bootloader, it reboots into fastboot mode with a big green START on the top, says it's booting a temporary bootloader, and then just sits there doing nothing, and is effectively hung. I have to hold power to get it to respond (by turning off).

Any clue what I'm doing wrong here? Followed the instructions to the letter. There's not much in the way of instructions for this part of it. Click, wait.

Appreciate the help.
[Nexus 7 (2013) Android Development] WugFresh:
Be certain that you selected the correct device and build. Or make use of the auto-detect feature. Then try again.
[Nexus 7 (2013) Android Development] merwin:
Yeah, I'm stupid. I didn't pick the V2 nexus 7 from the device list. I went back and checked that right after writing the post, since it seemed like it was locking up on booting the image, which points to the wrong image.

Oops :)
[Nexus 7 (2013) Android Development] WugFresh:
The new KVT49L build is now officially supported for the N7 (2013) LTE version. Just initiate a toolkit update to get the latest masterlists; then you will see that build listed in the toolkit model/build selection window. Cheers.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] md1008:
Not usually a fan of toolkits but this helped me install the necessary drivers on windows 8. Thank you!
[Nexus 7 (2013) Android Development] jazzy__b:
I managed to goof my N7 FLO by incorporating system updates into ROM using Titanium Backup (tip: Google Play Services doesn't like that). I now want to reflash stock but I get a product not recognised message. Is it safe to use the 'force flash' setting?

Update: my bad, I still had settings from rooting my son's N7 v1 so the tool was doing The Right Thing. Stock ROM flashed and appears to be booting fine now. I guess force flash would have been bad in this case.
[Nexus 7 (2013) Android Development] mdpatterson:
I have scoured the internet for almost 3 days straight(10 hours total sleep) for a solution to my problem. not that anyone cares, but just to show Im not asking for help without doing everything I can and should first. I have a nexus 7 2013 wifi (flo). I used this toolkit on windows to install TWRP, and root. I left stock rom on there. I am also currently in the middle of a windows rebellion. I have dumped windows and installed ubuntu 12.04. I made some mistakes when attempting to load ubuntu on the nexus 7. I was able wipe, then push a custom rom and then flash it, and it worked....PureRom or something like that(its on the nexus 7 2013 page ROM page). I was also able to get abd and fastboot installed(android sdk). although running wugfresh through wine either a.) recognizes adb when i have both MTP and PTP unchecked (with debugging on) or b.) recognizes fastboot with MTP checked. It will not recognize adb when MTP is checked, and it will not recognize fastboot if neither MTP or PTP is checked. So essentially, i can not have both adb and fastboot work and thus cannot do what I want. That brings me to my ultimate goal. I want to return flo to factory image, but keep TWRP and root. I have tried numerous was to send via terminal but all I get is <waiting for device>. As if I didnt screw things up even more, I fastboot erased the cache and system(thinking i would be able to flash the factory image I downloaded). So now even when I boot into the ROM i have on my sdcard, it just stays at the boot animation for that rom. I waited a while too thinking that the ROM just needed a bit to finish booting for the first time. I can successfully however get into fastboot, and TWRP. Help, Ive fallen and can't get up....
[Nexus 7 (2013) Android Development] mdamaged:
You're not going to be able to get back your factory flo ROM and keep root, once you restore that ROM you will have to reroot (but at least your bootloader is unlocked so you will not lose anything).

You will need a windows machine for the following to work, if you do not want to use windows, see below.

Did you try reading and following all the steps 1-3 (as required) in the Full Driver Configuration Guide in the toolkit? Most people have had luck with the RAW drivers, but try them all until you find one that works, doing the test each time in Step 3 until you get a Success message.

If that fails you have 2 more things you can try, either install these, or follow this.

If you do not want to do all that, first do a nandroid of the whole device (in case) then you can download the flo rom from here to your device directly (you want kot49h_flo.zip), along with SuperSU, and use twrp to flash the rom, make sure you wipe dalvik/cache afterwards, let it boot, then reboot back into twrp, and flash supersu to get root back, then install busybox from the playstore, etc.
[Nexus 7 (2013) Android Development] mdpatterson:
I will go through the options you gave and see if it works. I did go through the driver setup a few times but Ill try it again.

---------- Post added at 04:33 PM ---------- Previous post was at 03:41 PM ----------

with the ROM adb pushing method--keep getting this message when trying to push with adb "cannot stat 'kot49h_flo.zip': No such file or directory" Didnt get that before when I pushed PureRom. I put the flo rom in the same platform-tools folder that I put the PureRom in. I get what it's saying, but I dont understand why. I copied the name of the file straight from the properties.

attempting the others ...
[Nexus 7 (2013) Android Development] mdamaged:
Forget adb, forget the PC, get the kot49h_flo.zip onto the device by downloading it from that link directly using a browser on the device, then boot into twrp and flash it.
[Nexus 7 (2013) Android Development] mdpatterson:
Thats my issue. The only way I can open a browser on the device is to have a working rom. The only rom I have on there is that PureRom, and it just stays at the boot animation screen indefinitely. So pushing with adb is my only way to get the rom on there
[Nexus 7 (2013) Android Development] mdamaged:
Oh, derp on my part, have you tried using twrp to load them through OTG/USB?
[Nexus 7 (2013) Android Development] mdpatterson:
Still pretty noob at a lot of this, and very eager to learn but I only know enough to get by and do the basics. So, Im not sure how to do that, or even what is meant by that.

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

and if you have the time, i definitely want to know
[Nexus 7 (2013) Android Development] mdamaged:
TWRP supports loading files from a USB stick, but you need a OTG cable to do it, it connects to the mini-usb on the device and has a female USB post on the other end so you can plug in a USB thumbdrive. You can buy an OTG cable or make one yourself.

Whether you decide to go that route or not, I highly suggest anyone with a OTG capable device have one on hand, they are invaluable.

Anyhow, it's that or working to get those drivers working, or trying fastboot, the driver installer I posted earlier, really should have worked, and if it did not, then I would suggest you either try a different USB port (don't use USB 3.0 or external USB hubs), or a different PC, as those drivers are pretty much bullet proof with regard to adb working.

Also did you try restore to stock from within Wugs? Select the Soft brick/bootloop radio button and give it a try.

If that just wont; work, then you may want to try this: http://xdaforums.com/showthread.php?t=2381582

Just make sure you edit the script and delete the -w if you have data on the tablet you don't want wiped...else you can run it as is, you also will not have to do the 'fastboot oem unlock' part.

If you prefer manual, it basically does this:

To see if the PC sees the tablet properly run this: fastboot devices

If it shows a device ID then:

fastboot flash system <path to system.img>

fastboot flash recovery <path to recovery.img>

fastboot flash boot <path to boot.img>

fastboot -w <-- this wipes the data, leave out if you need to

fastboot reboot

This has to be done in fastboot mode, obviously.
[Nexus 7 (2013) Android Development] mdpatterson:
If I want to keep TWRP can I just skip the recovery flash? or is that recovery necessary to the process?
[Nexus 7 (2013) Android Development] mdamaged:
You can skip it.
[Nexus 7 (2013) Android Development] mdpatterson:
Excellent!! There needs to be a better merit system on here....A thanks meter just doesnt seem to cut it. I suppose the donate button is a pretty good reward. I can always count on XDA to solve issues, thanks a bunch man.