I could not get the correct drivers to load while VirtualBox extensions were installed, and this problem was a complete bastard to diagnose and fix.Įdit 2: Also the following is probably out of date, now that Google have released an integrated ADB extension for Chrome. To fix, I removed VirtualBox extensions on the host and ran to delete the incorrect drivers. Somehow I got VirtualBox to lock the device drivers on the host, eventually making it so that the ADB wouldn't work on the client nor the host for any device I plugged in. What can I do to get Windows to see the folders within the device?Įdit: I recommend you DO NOT run ADB under VirtualBox if you are using a Windows Host. Is there anything I am missing to get my device to show up in ADB devices? I have undone the steps in that link, along with everything else I have done so far, as well as uninstalling my Nexus 10 from Device Manager and reinstalling it, but I am still not seeing any folders in the device. After following those steps, 'adb devices' still returns an empty list and to make it worse, when I connect my Nexus 10 to my PC, Windows doesn't show any folders within the device.

I attempted to follow this recommendation, because it was identical to a suggestion I had previously found here on Stack Overflow. When I run 'adb devices' from the command terminal, it doesn't list any devices. I have checked the setting on my Nexus 10 for 'Unknown Sources'. I have downloaded the Android SDK, installed 'Android SDK Tools', 'Android SDK Platform-tools', and Google USB Driver. I am attempting to install an Android app on my brand new Nexus 10.

Install adb usb driver