i have recently purchased this phone. i installed just the usb driver for s3 but after connecting my phone it shows error code 10 device cannot be started. i am on xp may be sp2. what should i do
solved
thanks to all. i found the solution ( on the net obviously ) i downloaded and installed the following from the net.
windows media player 11
pdaneta302.exe
mtppk12.exe
it solved my problem hope it solves your.
Don't mean to sound like a troll but get a new OS!! XP is over ten years old; it won't work with new devices forever.
Sent from my iPad using Tapatalk HD
XP is over ten years old; it won't work with new devices forever.
Click to expand...
Click to collapse
While I agree with you, it's terrible practice by developers and hardware manufacturers to expect everyone to spend money on perfectly fine computers to get even more silly-looking and power-hungry versions of operating systems.
Windows XP is officially supported by Microsoft until mid-2014.
i installed just the usb driver for s3 but after connecting my phone it shows error code 10 device cannot be started.
Click to expand...
Click to collapse
Are you on XP 64bit SP2 or XP 32bit SP2? The latter is no longer supported by Microsoft and it's highly recommended to upgrade to Service Pack 3.
You need Media Player 10 installed for MTP mode, but it's (according to other people, I don't have a Windows XP computer anymore) very cumbersome and problematic. I'd recommend using a filesharing app such as AirDroid to connect the phone to your computer.
haha i am still on 32bit xp sp3 @ home pc , works fine, make sure you install latest kies
here is the requirement for kies
OS Windows XP, Windows Vista, Windows 7 (32/64bit are supported)
CPU Intel Core 2 Duo 2.0GHz or above (recommended)
Minimum memory size (RAM) 1.00GB (recommended)
Free hard drive space At least 500MB (recommended)
Screen resolution 1024 x 768(600), 32 bit or above
Required software Net Framework 3.5 SP1 or above, Windows Media Player 10 or above, DirectX 9.0C
* For Windows Mobile, ActiveSync (Windows XP) or Device Centre (Windows Vista/7)
I got this error on my windows 7 64bit, I searched the net for hours up on hours. I did not find a solution so I did a fresh install of windows and that did the trick
Sent from my GT-I9300 using xda app-developers app
Anybody else got problems with connecting to the PC with the USB cable?
What "problems" are you having?
The Windows Explorer does not start, though there is the sound when connecting the USB. Tried uninstalling the driver and letting the system reinstall upon connecting, but still cannot see Nexus 9 in Windows explorer. In Linux get the the notification and clicking on the "open with File Manager" gives a quick error message - too quick to read. So I am wondering if anyone got this problem??
Sent from my Nexus 9 using Tapatalk
Same here
I updated my SDK files, but that didn't seem to work either. It does show up as a camera when I change from MTP, so I just started sideloading apps, files, and books to the picture folder, then using a file explorer to move them to the correct folder.
+chuckie59 So I am not alone with this problem! Have used AirDroid to copy things over.
Sent from my Nexus 9 using Tapatalk
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Same for me. Only ptp working. Google USB ADB drivers instaled
mkygod said:
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Click to expand...
Click to collapse
You'll never get it to show up as a driver letter. Android gave up on mass storage a couple of versions ago.
Sent from my Nexus 9 using XDA Free mobile app
If you are on W8.1 then you may have the "ACER Composite ADB Interface" - A Microsoft upgrade fault.
A search for "ACER Composite ADB Interface remove error delete" should give plenty of hits. Here's the first post from http://forums.androidcentral.com/google-nexus-7-tablet-2012/362325-nexus-7-not-recognized-computer-2.html :
Would you happen to know if any Acer drivers are installed on your computer? Here recently there was a Windows Update that installed the wrong driver and made it so that I had the exact same problems as you're having. Here's how I fixed it.
Go To> Control Panel>Hardware and Devices>Device Manager. In Device manager look for something along the lines of "ACER Composite ADB Interface", at least in my case I had the wrong ADB interface installed. You'll know if you have the wrong drivers if you go to Devices and Printers and right click your Nexus 7 and go to it's properties. It should be under the hardware tab where it lists it. If it doesn't just say Nexus 7 then follow these instructions. Once you find it in the Device Manager (once again in my case it was the ACER Composite ADB Interface causing the issue) right click and and uninstall it. There should be a dialogue box that pops up right after which will ask you if you want to delete the drivers. Check this box and proceed with the uninstall. After successfully uninstalling the drivers plug in or unlplug and plug back in your Nexus 7. It should show up now with the correct drivers installed.
Thanks, but I am on Windows 7. Driver is ClockworkMod Ver 7.0.0.1 dated 2012-08-27, which Windows reports as up to date (?). Works for PTP but not MTP.
I have had problems with other devices including the nexus 5 and nexus 10 to connect over mtp. Previously i used the nexus root toolkit which has some wizard to guide you to install proper drivers for mtp and adb. The toolkit is yet to support nexus 9 but you can still use the wizard to uninstall the old drivers and reinstall correct ones
Updating sdk. Uninstall and installing again driver did the trick for me
SORTED!! (sort of) Updated sdk and uninstalled and installed the driver again, but it did not do the trick for me. Gave up on Win7.
Instead had a go on XP. Initially everything the same. Noticed two choices of compatible hardware given: "Google Nexus ADB Interface" (the one I had installed already) and "USB Composite Device". Tried the latter one, and yes it did install. In the device manager it turns up as "Portable Device/Nexus 9" (and not as "Android Phone/Google Nexus ADB Interface" as before).
In Windows Explorer it is shown as "Nexus 9/Internal storage" with all the directories, and actually when inserting the USB I do get auto start. By the way, was having the USB debugging disabled. The driver is Microsoft dated 2006-02-22 version 5.2.5326.4762 - which is not what I would have expected. But it works!
Will try to get something similar to work on Windows 7
SORTED! Yes also Win 7 - and it was easy. Uninstalled the driver, plugged in the USB and it installed! Also got the auto start to choose action. It now turns up as "Portable Devices/Nexus 9" in the device manager and as "Nexus 9/Internal storage/etc" in Windows Explorer. The driver is now Microsoft ver 6.1.7600.16385 dated 2006-06-21. Strange. As long as it is working!
MTP suddenly stopped working on my desktop running Windows 10 Pro N and I can't transfer files between my devices through USB. I already install the Media Feature Pack for windows before, I reinstalled it but it didn't solve the problem.
In windows Explorer there is just a grayed out USB-Drive and I can't do anything with it.
In the device manager the MTP device is in the 'Other devices' category with a yellow exclamation mark. I tried deleting the driver and updating the driver by selecting 'MTP device' from the driver list but it didn't help.
I tried it with a Oneplus One and a Nexus 7 (2012) and neither of them worked. Adb works fine and MTP works on my laptop, which also runs Windows 10 Pro N with the Media Feature Pack update.
Any help would be appreciated.
bump
Info: Nexus 5x Build NPF26F, v 7.1.1 , Developer option, OEM unlocking & USB debugging enabled, Windows 7 x64
Install USB drivers for Nexus 5x (latest_usb_driver_windows.zip)
Trouble is the inf file does NOT contain Hardware Id for this phone (Just purchased Nexus 5x 11/2016)
Windows Device Manager Hardware Id --> USB\VID_18D1&PID_4EE2&REV_0310
I have added this ID to the inf file (%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&REV_0310)
With this addition to the inf file, the driver is installed. Device manager reports the 5x as "SAMSUNG Android Phone", "Android ADB Interface
After doing this the 5x is still not recognized in by adb
Because of the Hardware Id has changed the driver/adb are hosed.
btw I have also install via Android Studio, Android SDK Manager method.
and used the zip file from here developer.android.com/studio/run/win-usb.html
Any thoughts
Thanks
Hi guys, I have this problem, my mobile doesn't connect to MTP in Windows 10, I tried another PC with Windows 10 and it didn't work the same, I tried with Windows 7 and 8.1 and if it works, change the cable and I tried to installing INF archive but not working ,I also copied the Windows 8.1 files for Windows 10 and still no MTP installedCan you help me? I would really appreciate it, Thank you