Database Users

Nexus 7 as Storage via MTP in Windows?

I would like to be able to modify the contents of /sdcard on my Nexus 7 from Windows. With my SGT7, I was able to do this, and also use ADB, but with the N7, it appears I can only do only ADB.

When I plug my Nexus 7 into my Window Vista (64), it mounts as a MTP hard disk. I don't see the entire file system,
but I have no trouble creating directories and copying files both directions.
I will say MTP is a lousy excuse for a file system. To manage my library on the PC I use the Calibre Server, which works great.

MTP is more like FTP than a file system.
On my phone (HTC Rezound), plugging in can cause havoc as it removes access to the SDcard when I am plugging in to the USB port which is a problem as I have many important apps that use that for storage (like Exchange email).
Instead...
I rarely use USB to transfer files anymore. Most of the time I use AndFTP for SFTP connections to my remote server or to my local workstation.
Doing the same for the Nexus 7 was a logical extension of that process... never connect via USB except to see what everyone was talking about.

rmm200 said:
When I plug my Nexus 7 into my Window Vista (64), it mounts as a MTP hard disk. I don't see the entire file system,
but I have no trouble creating directories and copying files both directions.
I will say MTP is a lousy excuse for a file system. To manage my library on the PC I use the Calibre Server, which works great.
Click to expand...
Click to collapse
Do you know which drivers you used for vista x64?

espionage724 said:
Do you know which drivers you used for vista x64?
Click to expand...
Click to collapse
When you plug in the Nexus 7, the Nexus will give you the chance to select USB connection mode. Choose MTP.
Windows automatically installed MTP drivers. Nothing to do with Google.
In Device Manager, the Nexus 7 shows up as device name Nexus 7.
Driver provider is Microsoft. Date 6/21/2006. Yes, MTP is that old...
Driver Version: 6.0.6002.18112
Digital signer: microsoft windows
c:\Windows\system32\DRIVERS\UMDF\WpdMtpDr.dll
c:\Windows\system32\DRIVERS\WpdUsb.sys
c:\Windows\system32\DRIVERS\WUDFRd.sys
c:\Windows\system32\WpdConns.dll
c:\Windows\system32\WpdMtp.dll
c:\Windows\system32\WpdMtpUS.dll
Hope this helps.

rmm200 said:
When you plug in the Nexus 7, the Nexus will give you the chance to select USB connection mode. Choose MTP.
Windows automatically installed MTP drivers. Nothing to do with Google.
In Device Manager, the Nexus 7 shows up as device name Nexus 7.
Driver provider is Microsoft. Date 6/21/2006. Yes, MTP is that old...
Driver Version: 6.0.6002.18112
Digital signer: microsoft windows
c:\Windows\system32\DRIVERS\UMDF\WpdMtpDr.dll
c:\Windows\system32\DRIVERS\WpdUsb.sys
c:\Windows\system32\DRIVERS\WUDFRd.sys
c:\Windows\system32\WpdConns.dll
c:\Windows\system32\WpdMtp.dll
c:\Windows\system32\WpdMtpUS.dll
Hope this helps.
Click to expand...
Click to collapse
Hmm, if you wouldn't mind, could you try:
Find Nexus 7 in Device Manager > Update Driver Software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Tell me what device is listed there?
(may be slightly different on Vista)
When I do that on my Flash drive, it shows me this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I tried selecting the Disk Drive driver on MTP, it failed to start.

Hmm, so I was reading:
http://www.androidtablets.net/forum/le-pan-tablets/34834-mtp-driver-not-installing.html
Which mentions:
On Microsoft Windows, MTP is supported in Microsoft Windows XP if Windows Media Player 10 or later versions are installed.
Click to expand...
Click to collapse
And as it turns out, I'm on Windows 8 Enterprise N (N being the version of Windows that doesn't come with Media Player features)
Edit: Confirmed working on a Windows 7 laptop (non-N). So looks like I'll have to go install a version of Windows that isn't N...

Man I hate dinking with device drivers for a device that is working - but here you go:
Well I still can't copy a screen shot, but it says:
Update Driver Software - Nexus 7
Model
MTP Device
This driver is digitally signed.

Nexus 7 properly detects now (just had to install a non-N version of Windows 8) and I was able to install the ADB driver with Google's USB driver found in the SDK installer.
So all is well

espionage724 said:
Nexus 7 properly detects now (just had to install a non-N version of Windows 8) and I was able to install the ADB driver with Google's USB driver found in the SDK installer.
So all is well
Click to expand...
Click to collapse
To use MTP using any edition of Windows N (theoretically), you must download and install the Media Feature Pack, which includes Windows Media Player, which adds MTP access for Windows 7/8.
https://www.microsoft.com/en-us/download/details.aspx?id=16546
I would do this right here, right now, except when I tried to install it my computer did the big Windows Update thing to install it, then rebooted, then detected an error and rolled itself back. So I might be stuck without WiMP. And without MTP.
Edit 1: Before installing this update, make sure everything else is up to date, even if it's throwing error messages. (I'm getting error messages.)

primetechv2 said:
To use MTP using any edition of Windows N (theoretically), you must download and install the Media Feature Pack, which includes Windows Media Player, which adds MTP access for Windows 7/8.
https://www.microsoft.com/en-us/download/details.aspx?id=16546
I would do this right here, right now, except when I tried to install it my computer did the big Windows Update thing to install it, then rebooted, then detected an error and rolled itself back. So I might be stuck without WiMP. And without MTP.
Click to expand...
Click to collapse
Yea I figured this would work fine on Windows 7, however I was on Windows 8 at the time, and the pack didn't want to install.

Have u guys tried to turn off USB Debugging. I was getting the MTP message but after I turned off USB Debugging it connected fine and I could see every folder on the Nexus.

See here for MTP in windows 8:
http://www.microsoft.com/en-au/download/details.aspx?id=30685

Annihlist said:
See here for MTP in windows 8:
** see link above - I'm still a noob here **
Click to expand...
Click to collapse
Thanks! I am running Windows 8 Enterprise N and was struggling to get my Nexus 7 recognized. This worked perfectly!

What I did
I had this same issue. What I did was connect my Nexus 7 to my PC as MTP.
Went to Start -> Devices and Printers.
Locate the Nexus 7 device.
Right-Click -> Properties -> Hardware -> Properties -> Driver -> Uninstall -> OK.
Then unplug Nexus 7, plug it back in, let it auto install drivers, voila, working.
Hope this helps someone!

muks11 said:
Have u guys tried to turn off USB Debugging. I was getting the MTP message but after I turned off USB Debugging it connected fine and I could see every folder on the Nexus.
Click to expand...
Click to collapse
This fixed it for me.
Just disabled USB Deugging and Win7 64 recognized it in MTP mode.
Yay! Thanks.:good:

Nexus 7 here, just updated to 4.2.1. I'm using Win 7 (64bit). When I plug in the Nexus it comes up in explorer, but when I drag files across, they seem to be copying, but the file(s) never appears in the Nexus after copying - no error in explorer. Strange. Please help! I am new to Nexus, just got it today.
All I'm trying to do is just copy some MKV movies across to the device.

throwback22 said:
I had this same issue. What I did was connect my Nexus 7 to my PC as MTP.
Went to Start -> Devices and Printers.
Locate the Nexus 7 device.
Right-Click -> Properties -> Hardware -> Properties -> Driver -> Uninstall -> OK.
Then unplug Nexus 7, plug it back in, let it auto install drivers, voila, working.
Hope this helps someone!
Click to expand...
Click to collapse
I tried all other method, all failed on me until i got to this one today! I tried to do the same thing in device manager but didnt work also, dont know what's wrong behind windows. (I'm using Win7 x64)
Thanks!:good:

When I ran windows 8 (before I scrapped it and went back to 7) I used the Google USB driver from the android SDK, and that worked perfectly.
Another method you could use to access the whole system, and not just the /sdcard would be to use AndroidExplorer:
http://forum.xda-developers.com/showthread.php?t=1242235
Although for copying larger files, the throughput is not very great, but this affords you the option of browsing the entire filesystem.

Nexus 7 cannot be seen on my Win7 64-bit
throwback22 said:
I had this same issue. What I did was connect my Nexus 7 to my PC as MTP.
Went to Start -> Devices and Printers.
Locate the Nexus 7 device.
Right-Click -> Properties -> Hardware -> Properties -> Driver -> Uninstall -> OK.
Then unplug Nexus 7, plug it back in, let it auto install drivers, voila, working.
Hope this helps someone!
Click to expand...
Click to collapse
This is driving me nuts.
My Win7 64-bit was able to see and transfer files to Nexus 7 before. After updated to 4.2.2, this is not possible. I can see Nexus and MTP USB device in device manager but the MTP drivers always failed to install. Unclicking debugging does not work for me.
I tried the above method- after uninstalling the drivers, my pc cannot see nexus 7. Plugging it in only activates the MTP USB drivers installation which, of course, fail again.
I tried this link's method, to no avail either: http://zacktutorials.blogspot.sg/2012/08/nexus7-android-development.html
I cannot connect my Nexus 7!!!!
Somebody please help!!!!!!

[Q] Windows 7 fails to install MTP driver

I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?

mseebass said:
I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?
Click to expand...
Click to collapse
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.

bigcrav said:
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.
Click to expand...
Click to collapse
Thanks for your help. I allready tried an other usb port. It did'nt work.

I wanted to avoid it but I reinstalled windows. Now it works. Thanks again.

Hmm, messed with this problem for ages yesterday, mtp installed fine in normal mode but refused when in 'usb debugging' mode
simple fix, find your wpdmtp.inf file in windows/inf
edit it like shown, look for the [Generic.NTx86] and [Generic.NTamd64] entries near the top of the file........
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
...then update the driver in device manager, use automatic search
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode

I did a clean install of windows and that solved the issue for me. Thanksfor your help anyway.

I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.

meangreenie said:
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode
Click to expand...
Click to collapse
Just FYI, just got a Nexus 4 from T-Mobile yesterday and the device ID is slightly different:
VID_18D1&PID_4EE2&MI_01
01 at the end instead of 00
---------- Post added at 09:11 AM ---------- Previous post was at 08:53 AM ----------
Fitchman said:
I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.
Click to expand...
Click to collapse
How/where do you install those files/drivers? There are no instructions.

lannister80 said:
How/where do you install those files/drivers? There are no instructions.
Click to expand...
Click to collapse
When Windows asks where the drivers are you point to the folder with the ones you want to use...

EddyOS said:
When Windows asks where the drivers are you point to the folder with the ones you want to use...
Click to expand...
Click to collapse
It doesn't ask. I plug in the phone, and Windows says it can't install the MTP driver.
If I go into Device Manager and find the phone (with the yellow triangle and !) and select Update Driver Software, then navigate to the i386 folder from the Universal Naked Driver (on an i5 system), it tells me that "The best driver for your device is already installed" or something similar.
Of course, if I uninstall the device from device manager (and presumably the bad MTP driver as well), it disappears, so I have nothing to point to to install the drivers.

Earlier today I reinstalled the drivers for my N4 on my work PC (Vista Business) and I had to reboot before it recognised the N4 as an MTP Device - prior to that it only saw it as an 'MTP Device'. Now it sees at 'Nexus 4'

I have a similar problem I have a kindle fire
I have install the ADB driver but am having extreme difficulties getting the MTP drivers to work
I have tried everything (every solution on Google)
and nothing works
I've tried the "Media Transfer Protocol Porting Kit"
I tried to get Microsoft help they gave me the run around and confused me even more
here is the conversation
Microsoft: "Thank you for that information
Nathaniel I was checking your product key and it is blocked that is why you can not connect these devices to your computer, you may be a victim of counterfeit software so in this case since it is an OEM computer which means that the manufacture of the computer installed Windows 7 on your computer I recommend you to contact the manufacture of your computer to see if they have an option in order to resolve this issue you are having."
me: when i contact them what do I ask for?
Microsoft: You need to ask for a new product key
me: I am confused what does this mean? that the manufacturer put windows 7 OS on here illegally? but all PC's come with windows OS so every PC in the world is suspect to counterfeiting
them: No, this could be because someone still some information of your computer and use the product key to try to activate Windows until the product key got blocked
No, the name is not involved in this case it is jut the product key
what do I do?
is there an alternative to MTP drivers?

Solved
Hi, i had the same problem described in previous posts and I managed to solve thanks to what is written by meangreenie.
In practice, in the windows\inf of my Windows 7 the file wpdmtp.inf was no longer present but there is only the "compiled" version (wpdmtp.pnf).
I retrieved the file from an earlier version founded in he folder Winsys and so the LG driver are installed without further problems.

Jon McDougal said...
You might be using the wrong driver (Android ADB) instead of the MTP driver. This happened to me the other day!
If you're in Debug Mode, you've already done the first step I was going to suggest.
Here's the second step that worked for me: Open Device Manager -> Click Android Device (top of my list) which exposes "Android Composite ADB Interface" -> Right click that device -> Update Driver Software -> Browse My computer for driver software -> Let me pick from a list of device drivers on my computer -> then choose "MTP USB Device" -> Next
Mine installed the MTP driver and then the N4 opened normally.
Click to expand...
Click to collapse
That works for me with USB Debug ticked and in MTP Mode but not in PTP Mode (on CM10.2-nightly-20130817). I absolutely can't see my pics in no way... (I suppose this is a bug from Google to be fixed in further updates). ADB and FB are correctly working as tested with NexusRootToolkit 1.7.1 Drivers Test.
May it help to delete original DCIM folder and start from a new one??
edit: Shame on me... I forgot that I've formatted my SDcard, so I've no picture in DCIM folder.... Sorry! So I can say that McDougal trick totally worked for me!

try to check the device manager to check the missing drivers with ! mark

Maybe I'm not completely getting the problem, but just doing this worked fine for me:
danielms22 said:
Enable USB debbuging in your phone. Go to Settings -> about phone -> tap about 10 times on build number item until USB debbuging is unlocked.
Also, on your computer go to the device manager, look for your phone, if you find it, right click on it, then update Driver Software, browse computer, Let me pick from a list of device drivers on my computer, USB composite device
That should do it.
Click to expand...
Click to collapse
No need for additional driver download or anything...

Finally a working solution
Finally I found a solution.
Visit answers.microsoft.com/en-us/windows/forum/windows_xp-hardware/mtp-usb-device-drivers-will-not-install-correctly/0ee71b7c-4ae7-403f-abbb-63c7ed9a79f9?rtAction=1387606800207 and search for the "Bret B"'s answer which has also been marked as the most helpful answer. It works perfectly. He simply says..
Go to the Registry Editor (Start –> Run –>type in, “regedit” (without the quotes) then click OK.
Search the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
Go upto Edit>Find, type in or copy/paste Portable Devices
In the right hand pane you will see the (Default) value “Portable Devices” on the string
Once found, you see a string value called UpperFilters –> delete it!
Reconnect the device. Finished!

[Q] No Drivers Found Windows 7

Kind of frustrating, I can't seem to get my computer to recognize the Nexus 7. I'm running Windows 7 64bit. I do have the Android SDK installed with 4.3 updated to the latest already. Can't imagine what could be triggering this... hmmm

Use the SDK manager to download the Google USB drivers. Head to device manager on your windows, update the driver for the nexus 7 which has an exclamation mark, and select the android SDK folder to install the drivers.
Hope it works for you.. That solved it for me.
Sent from my Nexus 7 using xda app-developers app

You can get latest drivers here:
Description/Download
http://developer.android.com/sdk/win-usb.html
Direct download
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip

will this drivers works under win8 (64)?

They should.

meine12 said:
will this drivers works under win8 (64)?
Click to expand...
Click to collapse
It works PnP on my Win8-64
Sent from my Nexus 7 using xda premium

sWirL said:
Use the SDK manager to download the Google USB drivers. Head to device manager on your windows, update the driver for the nexus 7 which has an exclamation mark, and select the android SDK folder to install the drivers.
Hope it works for you.. That solved it for me.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
sfhub said:
You can get latest drivers here:
Description/Download
http://developer.android.com/sdk/win-usb.html
Direct download
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Hmmm unfortunately still nothing. When I browse either the usb_driver folder or my SDK folder (with the Google USB drivers), I still get a "Windows was unable to install your Nexus 7, Windows could not find driver software for your device." message.

So I've been scratching my head over this one. I tried USB debugging mode, reinstalling the drivers, etc. Basically with USB debugging and the SDK drivers, I can finally get something installed, I see the Android Composite ADB Interface, but MTP is still eluding me. So PTP works fine now, but MTP is so damn annoying...
Once I disable USB debugging, I'm back to square one, its no longer MTP that has the ! sign in device manager, but instead, Nexus 7 again. Searching the SDK folder yields nothing and not even PTP works once USB debugging is gone.

PharaohsVizier said:
So I've been scratching my head over this one. I tried USB debugging mode, reinstalling the drivers, etc. Basically with USB debugging and the SDK drivers, I can finally get something installed, I see the Android Composite ADB Interface, but MTP is still eluding me. So PTP works fine now, but MTP is so damn annoying...
Once I disable USB debugging, I'm back to square one, its no longer MTP that has the ! sign in device manager, but instead, Nexus 7 again. Searching the SDK folder yields nothing and not even PTP works once USB debugging is gone.
Click to expand...
Click to collapse
I created the attached MTP driver inf to see if it would address your issue.
If it works let me know which OS version you are running. I think you mentioned windows 7 64-bit, but sometimes people switch machines in the efforts of trying to get things working.
You can install by telling the driver install not to search and to look for the driver in the path you downloaded and EXTRACTED this zip file.
The other way to install is to right click on the ? question mark entry in devmgmt.msc and go to the tab with the update driver option.

sfhub said:
I created the attached MTP driver inf to see if it would address your issue.
If it works let me know which OS version you are running. I think you mentioned windows 7 64-bit, but sometimes people switch machines in the efforts of trying to get things working.
You can install by telling the driver install not to search and to look for the driver in the path you downloaded and EXTRACTED this zip file.
The other way to install is to right click on the ? question mark entry in devmgmt.msc and go to the tab with the update driver option.
Click to expand...
Click to collapse
Thank you! That worked fantastic, still running Windows 7 64-bit. Can I ask what you did to get this working?
EDIT: This works fine for USB Debugging Mode, but when I turn that off, the Nexus 7 will try and install this MTP driver and get a "this device cannot start" error (on Windows). Although I'm more than happy with this solution, just info for anyone browsing this thread later on.

PharaohsVizier said:
Thank you! That worked fantastic, still running Windows 7 64-bit. Can I ask what you did to get this working?
EDIT: This works fine for USB Debugging Mode, but when I turn that off, the Nexus 7 will try and install this MTP driver and get a "this device cannot start" error (on Windows). Although I'm more than happy with this solution, just info for anyone browsing this thread later on.
Click to expand...
Click to collapse
If you want, you can try the version in this thread:
http://forum.xda-developers.com/showthread.php?t=2391236
This driver inf only affects MTP under USB debugging and will defer to windows for MTP when USB debugging is turned off.
You'll need to go to devmgmt.msc and Portable Devices, find Nexus 7, right-click, find the option to uninstall drivers, choose that, righ-click on Nexus 7, remove device, reboot.
Then specify the new path for the driver install (the one from that thread is mtp_driver, instead of mtp_driver_all in this thread)
Also you may want to post your experiences on that thread so people can find it in the future.

Yep I can confirm this one works as well. Awesome!

PharaohsVizier said:
Yep I can confirm this one works as well. Awesome!
Click to expand...
Click to collapse
Do you still have the issue where it says device could not be started when you turn off usb debugging?

Not sure if I'm having the same problem or just similar.
With usb debugging mode enabled, the tablet appears as Nexus 7 with no drivers found.
Without usb debugging mode, the Nexus 7 doesn't appear at all, not even under "other devices" or as a .USB composite device.
First tried installing Google USB Driver Rev. 8 from the SDK manager, with no luck.
Trying to manually install the extracted WPDMTPNX.INF driver with "Include subfolders" checked gives "Windows was unable to install your Nexus 7" as a result.
ROM: ParanoidAndroid 3.93
Kernel version 3.4.0-g365a6e0

msilby said:
Trying to manually install the extracted WPDMTPNX.INF driver with "Include subfolders" checked gives "Windows was unable to install your Nexus 7" as a result.
Click to expand...
Click to collapse
I sent you a PM.

msilby said:
With usb debugging mode enabled, the tablet appears as Nexus 7 with no drivers found.
...
ROM: ParanoidAndroid 3.93
Kernel version 3.4.0-g365a6e0
Click to expand...
Click to collapse
I attached a modified driver inf for your setup in the referenced post. See if that works for you.
mtp_driver_usbdebug_paranoid.zip
http://forum.xda-developers.com/showthread.php?p=44253804#post44253804
I believe your USB IDs are different from stock because of the ROM you are running.
I don't think it will fix your problem of not seeing the device properly with usb debugging disabled (I think that is possibly a rom issue), but it should theoretically get your device visible with usb debugging enabled.
Right-click on Nexus 7 in start menu->run->devmgmt.msc and choose the tab that allows you to update drivers and specify a folder where you unzip'd the zip file.

sfhub said:
Do you still have the issue where it says device could not be started when you turn off usb debugging?
Click to expand...
Click to collapse
Nope, it works fantastic!

[Q] ADB drivers not working

Hello. Im new to the Nexus 10. I downloaded skipsoft Android toolkit, installed adb drivers in the package and rooted the Nexus and installed recovery..it was easy using the toolkit. So the ADB drivers must have worked- at least in the environment it is used in to do these things. But these drivers dont work to transfer files between the nexus and the computer running winxp. I have USB debugging and PTP, have tried every other dirver package that has been mentioned on all available forums, have tried different usb ports, different cables etc. n my computer the device is recognised as a Nexus 10 but clicking on it gives a blank page, so cannot see the Nexux files. WTF this is driving me mad. Any ideas?

Re
Hi Ghosta,
Are you using a USB 3 port? as i have had many strange issues with these the ports. The issue is caused by one of the intel drivers cant remember exactly which way but there is no easy way to fix this. If this is your issues i would try and find if you have a USB 2.1 port you can use or the Esata ports on laptops tend to be usb 2.1 inside...even though they dont look like it haha
Hope this helps

ghosta12 said:
Hello. Im new to the Nexus 10. I downloaded skipsoft Android toolkit, installed adb drivers in the package and rooted the Nexus and installed recovery..it was easy using the toolkit. So the ADB drivers must have worked- at least in the environment it is used in to do these things. But these drivers dont work to transfer files between the nexus and the computer running winxp. I have USB debugging and PTP, have tried every other dirver package that has been mentioned on all available forums, have tried different usb ports, different cables etc. n my computer the device is recognised as a Nexus 10 but clicking on it gives a blank page, so cannot see the Nexux files. WTF this is driving me mad. Any ideas?
Click to expand...
Click to collapse
What does Device Manager show? Device name, its Properties and exclamation mark?
You do know that if your device has a "password" then you must be logged in to see its contents.

peterk-1 said:
What does Device Manager show? Device name, its Properties and exclamation mark?
You do know that if your device has a "password" then you must be logged in to see its contents.
Click to expand...
Click to collapse
Thanks for the replies and suggestions. All shows up OK in device manager, the device is not password protected, and the laptop has usb2 ports. I had another try today, after connecting the nexus it shows up in my computer as a camera, labelled nexus 10, with the camera icon. When I click on the icon it opens a special folder, must be a camera folder and the camera and scanner wizard starts. After a while it detects the photos on the nexus ( I have loaded a lot on it via USB otg using flash drive ), but thumbnails of the photos are not downloaded as I usually see when I connect a camera. The wizard downloads photos back to the computer, but each photo is about 18 kB instead of the 2 mb they originally were. So it appears a connection is happening, but a very strange one. I don't like to be beaten on problems like this one, but searching the net has not given me any answers, and I don't understand the android system well enough to know what to try next.

I think your device is working. If you connect it up as it now is and then go into Settings > Storage and tap the top RH corner menu you get the USB Computer Connection and select that and change it to MTP you should find it is now visible in My Computer or after auto install of the driver it will be visible. I'm brain dead - you said you had a PTP connection!

peterk-1 said:
I think your device is working. If you connect it up as it now is and then go into Settings > Storage and tap the top RH corner menu you get the USB Computer Connection and select that and change it to MTP you should find it is now visible in My Computer or after auto install of the driver it will be visible. I'm brain dead - you said you had a PTP connection!
Click to expand...
Click to collapse
No PTP conection or MTP connection either. The Nexus also shows up in Device Manger under Imaging Devices when USB deugging is on, which is causing the camera and scanner wizard to start, although it doesnt work properly. When i disable it nothing happens at all. No idea where to go from here.

There is or was an issue with XP see http://forum.xda-developers.com/showthread.php?t=2305943

peterk-1 said:
There is or was an issue with XP see http://forum.xda-developers.com/showthread.php?t=2305943
Click to expand...
Click to collapse
Thanks for the suggestion, I had already tried that but I did it again just to make sure. It did not work for me.

Have you tried following the driver install guide from Wug's toolkit? I've never used Skipsoft's but if it doesn't have you delete old drivers properly it's possible there's some old or corrupted driver sticking around from all the installs you've done. If you follow Wug's guide exactly you should end up with the only the correct drivers installed. Also, what ROM and kernel are you using? It's possible the issue is there.

capnkrunch said:
Have you tried following the driver install guide from Wug's toolkit? I've never used Skipsoft's but if it doesn't have you delete old drivers properly it's possible there's some old or corrupted driver sticking around from all the installs you've done. If you follow Wug's guide exactly you should end up with the only the correct drivers installed. Also, what ROM and kernel are you using? It's possible the issue is there.
Click to expand...
Click to collapse
I used a program called usbdeview to uninstall every USB driver with an "android" or "adb" description which should have cleaned up my drivers? Then after reinstalling drivers I tried again no difference. I ran android-tools and can push and pull files to and from the computer and nexus, (from command line) so I believe I have eliminated hardware problems and software problems on the nexus. This leaves the computer, which works perfectly with my other android devices running 4.1.1.

Just in case this helps. In usbdeview I have 5 nexus 10 entries. They all have the vendor id of Google 18d1 and a unique Product ID . Which driver connects is related to the device settings:
PID Device settings
4ee1 MTP
4ee2 MTP + USB debugging
4ee5 PTP
4ee6 PTP + USB debugging
d002 USB debugging
With the device connected I can change settings and see the change in connected driver in USBDeview.

peterk-1 said:
Just in case this helps. In usbdeview I have 5 nexus 10 entries. They all have the vendor id of Google 18d1 and a unique Product ID . Which driver connects is related to the device settings:
PID Device settings
4ee1 MTP
4ee2 MTP + USB debugging
4ee5 PTP
4ee6 PTP + USB debugging
d002 USB debugging
With the device connected I can change settings and see the change in connected driver in USBDeview.
Click to expand...
Click to collapse
This info does provide me with some way forward. With USB , when connected ptp I have a nexus 10 USB composite device and a nexus 10 digital still camera connected with the green light in USB deview, and also a blank device name, connected, description android composite device with a purple light. I'm guessing purple means not working. But changing drivers does nothing to change the purple light. Switching to mpt gives an additional blank name Google nexus adb interface also with purple light shown as connected. All connected devices show vendor 18d1. Drivers tried 1) clockworkmod (supplied with skipsoft); 2) naked drivers 3) Google drivers. Any clues what to try next?

2 things to check. I just tried running usbdeview from Wug's toolkit. It was v2.0 and wasn't the same as the version I have installed v2.3 - and there have been a significant number of changes. If you have XP pro x64 then you must use the x64 version of usbdeview - again I think Wug's may only ship with 32 bit usbdeview http://www.nirsoft.net/utils/usb_devices_view.html You will also find an explanation of the coloured radio buttons.
If you find you need to update usbdeview then I would suggest you uninstall the device drivers (instructions in Wug's toolkit?) then new drivers from http://developer.android.com/sdk/win-usb.html#top and follow the linked install instructions.

peterk-1 said:
2 things to check. I just tried running usbdeview from Wug's toolkit. It was v2.0 and wasn't the same as the version I have installed v2.3 - and there have been a significant number of changes. If you have XP pro x64 then you must use the x64 version of usbdeview - again I think Wug's may only ship with 32 bit usbdeview http://www.nirsoft.net/utils/usb_devices_view.html You will also find an explanation of the coloured radio buttons.
If you find you need to update usbdeview then I would suggest you uninstall the device drivers (instructions in Wug's toolkit?) then new drivers from http://developer.android.com/sdk/win-usb.html#top and follow the linked install instructions.
Click to expand...
Click to collapse
I gave up completely on this, and connect via wifi using ES file explorer. I bought my wife a new tablet an Acer Aconia A1-830 and it has the same problems, impossible to connect via ADB, with exactly the same symptoms. Yet our phones connect via ADB without a problem, but both are Androild 4.1 or earlier and the tablets 4.2 or younger. Obviously an Android generated problem that arose when 4.2 was released and on which has no fix.

problem with the adb interface driver (install/uninstall drivers)

hi,
im having issues installing drivers for my oneplus 2 device.
here's what i've tried doing:
iv'e tried connecting the device with usb debugging and without. without usb debugging it finds the name of the device normally.
the first thing i've done is uninstall every driver that was resembled any phone, google or usb storage driver.
and tried to install the drivers from this tool: (which i think is the source of my problem i dont know how to remove this.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it went ok with no problems, but it didn't find my device. (when i typed adb devices)
i've uninstalled the drivers again via programs and features and usbdeview tool (this time i've found older samsung device driver from regedit and removed it also).
rebooted (as every step of driver removal and install).
i've tried again with no luck.
so i've decided to install those drivers from the android sdk but when i've tried to install it from the device manager it shows up this:
i also tried downloading samsung drivers to see if it works. i saw in one of the threads that said it's ok to use them because they were universal too. (i removed it again from the regedit when i couldn't find the drivers)
i tried to use the oneplus one toolkit's for it's universal driver i thought maybe it will work
how can i fix this? i want to start over again clean. i can't find it in USBdeview or programs and features or regedit. what am i missing?
the photos are after trying to install the drivers from the sdk tool and uninstall it back with reboots several times now
+as im seeing in other threads, it supposed to be an android device and not adb interface.
+there is nothing else in the driver selection list that resembles any device
thanks to everyone who helps!
EDIT:
whatever i did i couldn't remove this marshall driver and i really don't know how i got it there. so i decided to format my pc. start over clean.
i've downloaded the sdk tools this time and before connecting my phone to the pc (maybe the windows 10 has to do anything with installing these marshall drivers.) i have installed these drivers from the sdk, rebooted the pc and connected the device. now everything works! the cmd find my device i type "adb reboot" to make sure everything works BUT when i go into fastboot mode (in order to unlock the bootloader)
the pc doesn't recognize the device. it says "android" with an question mark icon near it, ok so i just need to install the driver like in image #1 right? so i did, and it didn't show up this android adb interface driver. instead i've found this marshall driver AGAIN! i went inside it and i'm seeing marshall drivers and google inc drivers INSIDE this marshall driver selection (like image#2)
i really don't know from where this marshall london device is coming from
although setting it up as the marshall device, it works... but it's a marshall device not my oneplus 2
this doesn't make any sense to me. i never owned marshall product, beforehand i guessed it came from the toolkits i installed but this time i went clean and there's no way it came from those toolkits.
if im unclear about anytning im willing to share my teamviewer or screenshots.
this how it looks like:
EDIT2:
Q: what if i decide to ignore that marshall device? because it seems to find the device and im able to reboot from the commands. is it ok? should i ignore the name?

Hi, I used Universal ADB drivers.
I had to manually chose the .inf file with the have disk feature to make it work.

I used the Oneplus two toolbox to install my drivers.
forums.oneplus.net/threads/oneplus-2-how-to-unlock-bootloader-install-custom-recovery-root-efs-backup-more.345478
I didn't even bother with the 15 second ADB installer.

've found the problem.
apparently the drivers name was "marshall london device". i accidently clicked on it and there was an option to choose adb interface driver (like the image #2)
EDIT:
well it worked for the first try and it stopped working.
what is marshall london device? it seems to have a bunch of drivers like clockworkmod and marshall composite adb interface

Noahsoskha said:
i've found the problem.
apparently the drivers name was "marshall london device". i accidently clicked on it and there was an option to choose adb interface driver (like the image #2)
it works now
EDIT:
well it worked for 1 try and it stopped working.
what is marshall london device? it seems to have a bunch of drivers like clockworkmod and marshall composite adb interface
Click to expand...
Click to collapse
It's an Android phone design for Marshall (the music / sound gear company).

Theberge43 said:
It's an Android phone design for Marshall (the music / sound gear company).
Click to expand...
Click to collapse
i still don't get what that driver is doing in my pc
i can't install the inf file it tells me it's not supported.

for some retarded reason the usb drivers that i downloaded from google are being installed into marshall device. i don't know why but it's the second time my pc thinks my phone is a marshall device. it works if i type adb reboot, but only once. now i have to delete this marshall thingy that i don't even know how the hell it got there...

anything?
i really need help, i think i've made this problem as clear as possible.

Bump! same problem. This all happened as soon as i installed the latest version of OS. Oxygen 2.1 . Adb worked perfectly before i flashed this new OS. now windows wont read the devices with adb drivers. it keeps saying Marshall London Device.. sigh.. anybody? i tried all the same things in this thread to fix it. I also wiped all drivers using USBDeview and reinstalled to no avail.
Noahsoskha said:
anything?
i really need help, i think i've made this problem as clear as possible.
Click to expand...
Click to collapse

azenus said:
Bump! same problem. This all happened as soon as i installed the latest version of OS. Oxygen 2.1 . Adb worked perfectly before i flashed this new OS. now windows wont read the devices with adb drivers. it keeps saying Marshall London Device.. sigh.. anybody? i tried all the same things in this thread to fix it. I also wiped all drivers using USBDeview and reinstalled to no avail.
Click to expand...
Click to collapse
before that what did it detect? the device name? or adb interface?
are you running windows 10?
i managed to ignore the name of the driver because like the third image i posted says that inside the marshall driver there is "google inc" and then that the adb driver...
so i think it's windows 10 that's causing this. but i've tried ignoring it and adb commands are working for me. i don't know whether it's safe to unlock and such but i managed to make it reboot into recovery...

I am running windows 10. I tried another computer of mine with windows 7 which worked perfectly before the new OS update. That computer as well cannot detect any ADB devices. I managed to get windows to install the proper ADB Android drivers in windows 10 and 7 now. However, whenever I load One plus 2 into Fastboot Mode windows DOES detect the device but ADB wont connect to it.
I have made sure that i am in debugging mode and that I authorized the connection when prompted. any ideas?
Thank you
Noahsoskha said:
before that what did it detect? the device name? or adb interface?
are you running windows 10?
i managed to ignore the name of the driver because like the third image i posted says that inside the marshall driver there is "google inc" and then that the adb driver...
so i think it's windows 10 that's causing this. but i've tried ignoring it and adb commands are working for me. i don't know whether it's safe to unlock and such but i managed to make it reboot into recovery...
Click to expand...
Click to collapse
---------- Post added at 04:25 PM ---------- Previous post was at 04:12 PM ----------
Figured out why adb wouldnt connect. Even though usb debugging was on and permissions granted for some reason the Developer Mode toggle was hidden again. I enabled the toggle again, turned off usb debugging mode. Turned it back on 10 seconds later and it all works now. *sigh*

useranonymous said:
I used the Oneplus two toolbox to install my drivers.
forums.oneplus.net/threads/oneplus-2-how-to-unlock-bootloader-install-custom-recovery-root-efs-backup-more.345478
I didn't even bother with the 15 second ADB installer.
Click to expand...
Click to collapse
Thanks! Worked for me too!

Hi there,
my problem is very similar to this.
Suddenly all my android devices (OPO and OP2) are recognized as marshall london devices.
adb devices finds them but I am not able to get the authorization of my PC showing up on my phones.
adb tells me the device is not authorized.
I tried resetting the usb authorization from the development options, changing usb ports, changing cables, disabling and enabling of usb debugging, mtp mode and such.
Nothing works so far. The google adb drivers show up under the marshall london category like in the first post. It all startet after I rebooted the OP2 in fastboot once.
Any ideas?
Thanks
-howgie
Update:
I was able to get rid of the marshall london entry by removing it from the registry manually. But the problem of the unauthorized device remains...

I am also getting this error, I was able to select google devices before and had adb working but after it unlocked the bootloader and rebooted the phone it wasn't detecting anything correctly, just the marshal london device and adb doesn't detect anything, also on windows 10. Will try tomorrow on my windows 7 work machine.

Same Problem! Please Help!
For some reason "Marshall London Device>Marshall London Bootloader Interface" keeps installing itself every-time I hit Scan for hardware changes, after trying to uninstall it. ADB doesn't recognize my OPT even when my phone is in fastboot mode. Running Windows10

In windows 10 use manual choose driver from list, then choose proper driver.... If you can't find it I'll post screens tomorrow
Sent from my ONE A2005 using Tapatalk

cosmicsquid said:
Same Problem! Please Help!
For some reason "Marshall London Device>Marshall London Bootloader Interface" keeps installing itself every-time I hit Scan for hardware changes, after trying to uninstall it. ADB doesn't recognize my OPT even when my phone is in fastboot mode. Running Windows10
Click to expand...
Click to collapse
I have same problems. Have someone found a solution for this?

I deleted all drivers and it says unknown USB device (Device Descriptor Request Failed). I can't get it to install Oneplus2 drivers, Android ADB or Samsung drivers and be recognised.
Again I concur and think this is a Windows 10 issue, I am not using the official cable, are others using it and having the same issue??

I used a different cable and it worked, strange as I tried one unofficial and one official and in the end my new Anker one I just purchased worked okay.

howgie said:
Hi there,
my problem is very similar to this.
Suddenly all my android devices (OPO and OP2) are recognized as marshall london devices.
adb devices finds them but I am not able to get the authorization of my PC showing up on my phones.
adb tells me the device is not authorized.
I tried resetting the usb authorization from the development options, changing usb ports, changing cables, disabling and enabling of usb debugging, mtp mode and such.
Nothing works so far. The google adb drivers show up under the marshall london category like in the first post. It all startet after I rebooted the OP2 in fastboot once.
Any ideas?
Thanks
-howgie
Update:
I was able to get rid of the marshall london entry by removing it from the registry manually. But the problem of the unauthorized device remains...
Click to expand...
Click to collapse
where is it in the registry pls? (marshall london device)