MTP Drivers for Windows - Nexus 10 Q&A, Help & Troubleshooting

Does anyone know where I can find the MTP drivers for the Nexus 10? I made a mistake and need to re-install it for my PC to be able to transfer files to my N10 vice versa. Any help would be much appreciated.

MTP Drivers shouldn't typically be needed for Windows. If you have just standard Windows (not N or KN), MTP should be included with the OS (at least for Vista+)
N and KN versions of Windows need a Media Pack from Microsoft (free download).
Also, you could try installing the Google USB Driver from Android SDK if you haven't already; may or may not make MTP appear if it doesn't appear under normal circumstances.

version 1.5.15.0 (32 and 64 bit) from this last August:
http://www.mediafire.com/?qp9gw2i9lwbr3qb
Also the ADB interface driver if you need that:
http://drivers.softpedia.com/get/Ot...-29505831-for-Vista-Windows-7-Windows-8.shtml

Thank you. Exactly what I was looking for. Works now

EniGmA1987 said:
version 1.5.15.0 (32 and 64 bit) from this last August:
http://www.mediafire.com/?qp9gw2i9lwbr3qb
Also the ADB interface driver if you need that:
http://drivers.softpedia.com/get/Ot...-29505831-for-Vista-Windows-7-Windows-8.shtml
Click to expand...
Click to collapse
The Google USB driver from Android SDK doesn't work? I'm confused as to why you would need either of those drivers; thought MTP was just a standard thing in Windows, and that those drivers were specifically for ADB purposes?

espionage724 said:
The Google USB driver from Android SDK doesn't work? I'm confused as to why you would need either of those drivers; thought MTP was just a standard thing in Windows, and that those drivers were specifically for ADB purposes?
Click to expand...
Click to collapse
IDK. Im just providing a link to the drivers that were asked for. Samsung says those are their mobile drivers so thats what I post. If the ones that come with the SDK work then no need to bother with these. For all I know they could both be the exact same thing, but the OP says his problem is fixed and things work now. So I guess they are good for something if you are having problems

espionage724 said:
The Google USB driver from Android SDK doesn't work? I'm confused as to why you would need either of those drivers; thought MTP was just a standard thing in Windows, and that those drivers were specifically for ADB purposes?
Click to expand...
Click to collapse
I downloaded the SDK but I couldn't find where the Google USB Driver was located. It said sdk >> extras >> google >> google_usb_driver
but I have sdk >> extras >> android >> support >> XXXXXXXXXXX
it then splits off into folders for samples, v4, v7, and v13. None of them had the usb drivers.
If you could help me find out where I can find a legitimate copy of the usb driver from the download it would be much appreciated.
What enigma posted worked after I uninstalled everything android driver related from my computer so they might have a connection?
I would still like the official google version but I just can't locate it within the sdk download.

espionage724 said:
MTP Drivers shouldn't typically be needed for Windows. If you have just standard Windows (not N or KN), MTP should be included with the OS (at least for Vista+)
N and KN versions of Windows need a Media Pack from Microsoft (free download).
Also, you could try installing the Google USB Driver from Android SDK if you haven't already; may or may not make MTP appear if it doesn't appear under normal circumstances.
Click to expand...
Click to collapse
keyword being 'typically', if this POS was working right, we wouldn't be in here looking for friggin drivers. there are tons of threads with people like me that cannot get MTP to work. We just want to transfer some files; why can't **** just work?
---------- Post added at 09:39 PM ---------- Previous post was at 09:38 PM ----------
EniGmA1987 said:
version 1.5.15.0 (32 and 64 bit) from this last August:
http://www.mediafire.com/?qp9gw2i9lwbr3qb
Also the ADB interface driver if you need that:
http://drivers.softpedia.com/get/Ot...-29505831-for-Vista-Windows-7-Windows-8.shtml
Click to expand...
Click to collapse
the mediafire link seems to be for Samsung drivers... why would that fix a Nexus 10 (or 7 which i have)

drumtrucker said:
keyword being 'typically', if this POS was working right, we wouldn't be in here looking for friggin drivers. there are tons of threads with people like me that cannot get MTP to work. We just want to transfer some files; why can't **** just work?
Click to expand...
Click to collapse
But with MTP drivers; you would either have OS support, or have to download Microsoft's media pack; drivers shouldn't have anything to do with MTP. If MTP doesn't "just work" then:
- Your on an unsupported OS (below Vista (such as XP); or a N/KN version of Vista+)
- If on a N/KN OS, you need the Media Pack from Microsoft (N/KN lacks the needed media features by default)
- If on Linux, you'll most likely need something to read MTP (gMTP on Ubuntu worked fine)
- You have "messed up" ADB drivers (in which case; uninstall them, and MTP should immediately become available on a supported OS; I had this happen a few times, but it wasn't too common, nor do I even know why it happened lol)
- USB port (on computer or Nexus 10), driver (on computer), or cable itself is malfunctioning in some way
As for ADB however; in order to have it with the Android SDK, you need to download the USB drivers with the SDK executable (I think it actually automatically checks itself anyway when you open the SDK for the first time). But ADB and MTP shouldn't affect one another.
I've installed Windows 7 and 8 numerous times, and even messed with Linux a bit. On 7 and 8, MTP just worked. Linux (Ubuntu) needed some program to read MTP, but worked just fine afterwards.

espionage724 said:
But with MTP drivers; you would either have OS support, or have to download Microsoft's media pack; drivers shouldn't have anything to do with MTP. If MTP doesn't "just work" then:
- Your on an unsupported OS (below Vista (such as XP); or a N/KN version of Vista+)
.
Click to expand...
Click to collapse
On windows 7HP... and it doesn't just work. Before posting above whine I had tried all the solutions that seemed even vaguely appropriate. Before installing SDK kit to apply 'fresh drivers' it would see as 'unidentified device'. After installing ADB stuff, it will see as Android device if debugging on and MTP if debugging off... BUT 'MTB' drivers do NOT install... no driver installs for MTB function.
Tried another posters work around of going to camera mode (which it will do) and moving files into the DCIM folder and moving with Astro (or some such) afterward. It worked once then kept rejecting my .avi and .mkv files because 'camera [would not like them]. Then it started letting me do it again. Also found AirDroid and WiFi File Explorer as way to accomplish file transfers.

drumtrucker said:
On windows 7HP... and it doesn't just work. Before posting above whine I had tried all the solutions that seemed even vaguely appropriate.
Click to expand...
Click to collapse
I imagine your also on the latest Service Pack, know for a fact your not on a N/KN OS, and also have nothing intentionally blocking MTP (Group Policy Settings, Security Clients, Automatic-Tweak Programs, etc.)?
The MTP device appears whether or not my ADB drivers are installed, and whether or not Android USB Debugging is enabled. Not sure what else I could suggest to get yours working other then a fresh (non-OEM) re-install of Windows.

espionage724 said:
I imagine your also on the latest Service Pack, know for a fact your not on a N/KN OS, and also have nothing intentionally blocking MTP (Group Policy Settings, Security Clients, Automatic-Tweak Programs, etc.)?
The MTP device appears whether or not my ADB drivers are installed, and whether or not Android USB Debugging is enabled. Not sure what else I could suggest to get yours working other then a fresh (non-OEM) re-install of Windows.
Click to expand...
Click to collapse
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!

drumtrucker said:
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!
Click to expand...
Click to collapse
this has worked for me, thank you

Related

[USB Drivers] Galaxy S GT-I9000 (Working on ICS)

Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.

X64 and MTP not showing up?

My nexus 7 isnt showing up on my Windows 7 x64 machine... any help on what I can do?
numus said:
My nexus 7 isnt showing up on my Windows 7 x64 machine... any help on what I can do?
Click to expand...
Click to collapse
This is part "bump" and part assistance. You can at least get the Nexus 7 connected via ADB using these steps:
enable USB debugging
install the Android SDK (from Android's developer site)
from the SDK manager install the latest version of the USB driver too.
Make sure your Nexus 7 is hooked up.
Go into your device manager (Start > Control Panel > Device Manager)
navigate to the right Nexus device (not MTP in this case),
right click it,
click Update Device Drivers.
Choose your own driver manually.
When asked for a folder, navigate to C:\[your username]\AppData\Local\Android\android-sdk\extras\google\usb_driver
make sure searching in folders is checked
...that should at least get the ADB driver running. From there you can PUSH or PULL files or open the SHELL, but I don't know of a client-side file manager that makes those things easy yet. This is just one step of many, I bet...
2 things
Have you the latest win media player installed on PC? If not, update it.
Is n7 USB debugging on? If so, turn it off.
That should allow MTP to begin. If not, try the previous post
Sent from my Nexus 7 using xda app-developers app
If your using a N or KN version of Windows 7, you can't use MTP. N and KN versions of Windows have media foundation and other media-specific features stripped from it; and MTP itself does not work.
If you are on such an OS, then this media pack may help:
http://www.microsoft.com/en-us/download/details.aspx?id=16546
espionage724 said:
If your using a N or KN version of Windows 7, you can't use MTP. N and KN versions of Windows have media foundation and other media-specific features stripped from it; and MTP itself does not work.
If you are on such an OS, then this media pack may help:
http://www.microsoft.com/en-us/download/details.aspx?id=16546
Click to expand...
Click to collapse
Other MTP devices show up... I have my epic 4g touch hooked up right now and it shows MTP... just the google nexus 7 wont...
primetechv2 said:
This is part "bump" and part assistance. You can at least get the Nexus 7 connected via ADB using these steps:
enable USB debugging
install the Android SDK (from Android's developer site)
from the SDK manager install the latest version of the USB driver too.
Make sure your Nexus 7 is hooked up.
Go into your device manager (Start > Control Panel > Device Manager)
navigate to the right Nexus device (not MTP in this case),
right click it,
click Update Device Drivers.
Choose your own driver manually.
When asked for a folder, navigate to C:\[your username]\AppData\Local\Android\android-sdk\extras\google\usb_driver
make sure searching in folders is checked
...that should at least get the ADB driver running. From there you can PUSH or PULL files or open the SHELL, but I don't know of a client-side file manager that makes those things easy yet. This is just one step of many, I bet...
Click to expand...
Click to collapse
ADB works without a problem.. it is just hte MTP that wont show up
I have the same issue. If I select PTP, the camera shows. Once I switch back to MTP, it goes away and no disks are displayed. In Device Manager I see Android Phone, I installed Google drivers and adb works. I have a Google Nexus also and is OK.
You're not alone, Sir.
http://forum.xda-developers.com/showthread.php?t=1821536
Anyone who found a fix for this? Couldn't get it to work on W7, on Windows 8 still no MTP. I can use it for debugging with the ADB, but everything I tried failed. Now I'm using AirDroid, but this option is the way slower.
reemprive said:
Anyone who found a fix for this? Couldn't get it to work on W7, on Windows 8 still no MTP. I can use it for debugging with the ADB, but everything I tried failed. Now I'm using AirDroid, but this option is the way slower.
Click to expand...
Click to collapse
Either the PDAnet or official Asus drivers work for me.
Sent from my Nexus 7 using Tapatalk HD
on 4.4.2
Here's the official documentation from Google for enabling this protocol.
"Transfer files through USB" (Google this** and click the link by support.google.com)
Relevant Info:
On your device, make sure that the USB computer connection is set to “Media device (MTP).”
Go to Settings > Device > Storage. Then open Menu > USB computer connection.
MTP should be selected by default, but you may have to uncheck MTP, check and uncheck Camera (PTP), and then recheck MTP.
** Unfortunately I'm not able to post external links having fewer than 10 posts, so I'll update this when I'm able. If I forget, just ping me.

[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!

Nexus 4 appears as unknown device

Hello, I am trying to connect my nexus 4 to my computer to put some music on. This used to work, but now it is being detected as an unknown device. I tried updating the drivers to the Universal Naked driver, but it just says the best driver is already installed. I tried with USB debugging on and off, no difference. Also tried 2 different usb cables.
Cyanogenmod Version: 10.1.1-mako
Build: JDQ39E
Thank you for any help!
jining said:
Hello, I am trying to connect my nexus 4 to my computer to put some music on. This used to work, but now it is being detected as an unknown device. I tried updating the drivers to the Universal Naked driver, but it just says the best driver is already installed. I tried with USB debugging on and off, no difference. Also tried 2 different usb cables.
Cyanogenmod Version: 10.1.1-mako
Build: JDQ39E
Thank you for any help!
Click to expand...
Click to collapse
What OS are you using? Windows? Mac? A linux distro?
Also, are you sure you're using MTP instead of PTP (Settings > Storage > menu > Usb Computer Connection) ?
You can try to install google's drivers from the android sdk as well.
vorbatello said:
What OS are you using? Windows? Mac? A linux distro?
Also, are you sure you're using MTP instead of PTP (Settings > Storage > menu > Usb Computer Connection) ?
You can try to install google's drivers from the android sdk as well.
Click to expand...
Click to collapse
I am using Windows 7, it was set to PTP, I just set to MTP, but it still does the same thing. I have turned off my USB debugging in the developer menu as well.
jining said:
I am using Windows 7, it was set to PTP, I just set to MTP, but it still does the same thing. I have turned off my USB debugging in the developer menu as well.
Click to expand...
Click to collapse
I know this is a silly thing to ask, but have you tried rebooting your phone? Something like this happened to me before and a reboot fixed it.
Also, if you have a custom kernel, check that you have USB fast charge disabled. And after that fails, try installing google's drivers. Sorry, I'm just spouting out random ideas at this point.
vorbatello said:
I know this is a silly thing to ask, but have you tried rebooting your phone? Something like this happened to me before and a reboot fixed it.
Also, if you have a custom kernel, check that you have USB fast charge disabled. And after that fails, try installing google's drivers. Sorry, I'm just spouting out random ideas at this point.
Click to expand...
Click to collapse
Thanks for the suggestions. I am using Franco kernel, how do I turn off fast charge?
jining said:
Thanks for the suggestions. I am using Franco kernel, how do I turn off fast charge?
Click to expand...
Click to collapse
Use trickster mod and go to the Kernel Specific page. If fast charge is ticked off, there's not much we can do from there.
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Also, have you tried to install google's drivers or make a nandroid and reflash a clean rom?
EDIT: You could also try Koush's universal driver: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I'm afraid I'm out of ideas at this point
vorbatello said:
Use trickster mod and go to the Kernel Specific page. If fast charge is ticked off, there's not much we can do from there.
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Also, have you tried to install google's drivers or make a nandroid and reflash a clean rom?
EDIT: You could also try Koush's universal driver: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I'm afraid I'm out of ideas at this point
Click to expand...
Click to collapse
Hmm I am in the trickster mod on the kernel specific screen, but I don't see anything about USB fast charge Where might I get googles drivers? I can't seem to install any drivers because as soon as I uninstall the unknown device, it auto installs some drivers.
Thanks for the help!
jining said:
Hmm I am in the trickster mod on the kernel specific screen, but I don't see anything about USB fast charge Where might I get googles drivers? I can't seem to install any drivers because as soon as I uninstall the unknown device, it auto installs some drivers.
Thanks for the help!
Click to expand...
Click to collapse
So I tried installing the newest Franco kernel Milestone (3), and the USB fast charge is off. I also tried installing a different CM mod, but there is no difference. I also tried installing the universal you gave me, but that didn't work, and i installed the google driver from SDK and that didn't work.
I don't know what else to do...
Hi, try to completly unninstall ALL drivers for nexus, samsung or android related, than install official drivers for nexus 4 and then connect nexus 4. Should work.
maxiiik said:
Hi, try to completly unninstall ALL drivers for nexus, samsung or android related, than install official drivers for nexus 4 and then connect nexus 4. Should work.
Click to expand...
Click to collapse
I tried that, no luck...I don't know what else to do, I have tried 3 different cables. I tried using the drivers that come with the nexus 4 toolkit, but no luck. It charges when plugged in, but i get nothing else. Also it seems like half the time its not even in the device manager as an unrecognized device, and then it intermittently pops up a window saying unrecognized device detected... maybe my USB port is broken on the phone?
Is there something simple I have overlooked to get 4.2.2 to work with my computer?
jining said:
I tried that, no luck...I don't know what else to do, I have tried 3 different cables. I tried using the drivers that come with the nexus 4 toolkit, but no luck. It charges when plugged in, but i get nothing else. Also it seems like half the time its not even in the device manager as an unrecognized device, and then it intermittently pops up a window saying unrecognized device detected... maybe my USB port is broken on the phone?
Is there something simple I have overlooked to get 4.2.2 to work with my computer?
Click to expand...
Click to collapse
Have you managed to solve this? I'm facing almost the same problem!
No, I tried for hours with no luck. I am glad I am not the only one, hopefully a solution will come to us. I have been using airdroid to transfer files from my phone in the mean time.
Im also having the same issue except my computer only recognizes my phone when its connected as a camera.
Sent from my Nexus 4 using xda app-developers app
I am having a similar problem with my daughter's Nexus 4 phone, which is not rooted nor unlocked - it is still completely stock. It was just updated to Android 4.3, however I can't say that this is the cause of the problem because she never attempted to connect her phone to the desktop machine before.
I have a Windows 7 x64 box at home, and spent over two hours last night trying to get the computer to correctly recognize the Nexus 4 phone. I was hoping that the standard MTP Windows driver would handle it perfectly, but no luck. I tried the Google usb drivers, and the ADB interface was recognized, but still no access to the internal storage. I then gave the Naked Drivers a try, and no joy there either.
I am beginning to suspect that the MTP drivers on my desktop are munged, but do not relish the thought of a Win 7 wipe and reinstall.
Anyone else have any ideas?
Thanks much!
I am having a similar problem where I have USB storage set to MTP and Windows doesn't pick it up, whereas PTP Windows will pick up but I can't access any folders other than the camera related folders like DCIM.
So my workaround is doing it the old fashioned way through CMD in windows using adb push.
Example:
Assuming you have all the stuff you want to transfer in a folder called stuff, adb is located in C:\adb, and your folder known as stuff is also in C:\adb:
C:\adb>adb push stuff /data/media/0
The above command starting from the ">" will transfer all files in the folder called stuff to the root of /sdcard. In the N4, /sdcard is symbolically linked to /data/media/0.
Of course you need USB debugging enabled for this to work...
Device Manager (Hopefully this helps)
In the start menu type device manager, in that window you should see android and or something similar at the top. You want to drop the menu down and right click what should say Google ADB Interface and delete it, make sure you check the confirmation box. After reboot your computer! Once booted plug your phone in a viola!!!
I'm having a similar issue.
I can open device manager but there in no Android anything listed. All that comes up when I plug my phone in is 'unrecognized usb device'. I have 5 different cable I have tired. The OS will only bring up the usb error in a USB 3.0 port. It will not do anything if I use the 2.0 port.
I have gone and tried to manually update the drivers through the device manager but when I select the drivers from Android SKD or any of the other driver packs I get an error that it is not a x64 driver.
I found one suggestion about modding the driver to include the device but windows will not even recognize the device other than a unknown usb.
I'm going to have a bricked computer soon. Any help would be appreciated.
Roktgr said:
I'm having a similar issue.
I can open device manager but there in no Android anything listed. All that comes up when I plug my phone in is 'unrecognized usb device'. I have 5 different cable I have tired. The OS will only bring up the usb error in a USB 3.0 port. It will not do anything if I use the 2.0 port.
I have gone and tried to manually update the drivers through the device manager but when I select the drivers from Android SKD or any of the other driver packs I get an error that it is not a x64 driver.
I found one suggestion about modding the driver to include the device but windows will not even recognize the device other than a unknown usb.
I'm going to have a bricked computer soon. Any help would be appreciated.
Click to expand...
Click to collapse
First, Google universal naked drivers xda. Try those. If they don't work go into device manager and go to where it says let me choose drivers from my computer. Then look for the android composite adb interface.
If you're on win 8 you'll need to allow unsigned drivers. Google how to do that
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
First, Google universal naked drivers xda. Try those. If they don't work go into device manager and go to where it says let me choose drivers from my computer. Then look for the android composite adb interface.
If you're on win 8 you'll need to allow unsigned drivers. Google how to do that
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#1 is the phone doesn't do anything in USB debug mode. I keep seeing references to having to approve the computer connection but I haven't seen that yet. I have tired 9 usb ports. 6 on my main computer will not bring anything, not even the usb drive. 3 on the labtop will only bring up a 'unrecognized usb drive'.
#2 is the computer will not recognize the device in anything other than a 'unrecognized usb drive' (UUD). Everyone keeps mentioning the Android Composite ADB interface. It's not there, it doesn't show up or as an option. I can go into the device manager and find the UUD and try and update the driver via the manual method with a disk but it doesn't list any type of hardware that is related to Android or ADB.
Roktgr said:
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#1 is the phone doesn't do anything in USB debug mode. I keep seeing references to having to approve the computer connection but I haven't seen that yet. I have tired 9 usb ports. 6 on my main computer will not bring anything, not even the usb drive. 3 on the labtop will only bring up a 'unrecognized usb drive'.
Click to expand...
Click to collapse
Hello,
"#1 is the phone doesn't do anything in USB debug mode." This is normal!
How I experienced the USB debugging option is that, if turned ON:
1. The Nexus does not appear in my Windows env
2. BUT when in recovery mode, I can use the "adb" commands
If USB debugging turned OFF:
1. Then I CAN see the Nexus in my Windows env
2. BUT I cannot use the "adb" commands in recovery mode.
So you definitely need to have the USB debugging option turned off if you want to see your nexus in Windows, IMO
---------- Post added at 04:16 PM ---------- Previous post was at 04:02 PM ----------
Roktgr said:
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#2 is the computer will not recognize the device in anything other than a 'unrecognized usb drive' (UUD). Everyone keeps mentioning the Android Composite ADB interface. It's not there, it doesn't show up or as an option. I can go into the device manager and find the UUD and try and update the driver via the manual method with a disk but it doesn't list any type of hardware that is related to Android or ADB.
Click to expand...
Click to collapse
I think you really have an issue with the drivers. I would install the Google USB drivers. Maybe a bit heavy but then you can be sure that drivers are fine:
http://developer.android.com/sdk/win-usb.html

[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!

Categories

Resources