I've suddenly got MTP driver issues. Tried everything I've found Googling and nothing has worked.
Anyone had any issues with the G3 on Win7 32bit and 64bit and managed to resolve it?
Thanks!
So after trying various combinations (even hard reset) to get MTP working, what seemed to work for me is to install just the LG suite and not the Unified Drivers (v3.11.3).
Note, Windows 7 did seem to recognise MTP using some default drivers, but I found them to be very unstable, it nearly corrupted my SD card.
Related
Couple days ago i installed a Windows 8 RTM and tried plugging in my gnex in USB.
Nothing happened, it wasn't recognized and shown in Explorer.
I saw that WindowsUpdate offered Samsung Mobile MTP device driver but it fails to install.
Can anyone confirm this andor offer a workaround or help?
Thanks
solved problem.
I had issue with Windows 8 Enterprise N build, when i installed non-N build phone got recognized regularly.
Seems that absence of WindowsMediaPlayer causes issues with MTP device.
I still have issue with windows media player installed. It always locks up when I try and copy my pictures off
Okay, so I'm trying to copy files from my PC to my Nexus 7 FHD. First tried on a Windows 8.1 PC and when I plug in the N7, it installs the MTP drivers (driver date is 2006 from Microsoft). Shows up in my file explorer and I try to copy some photos but after about 5-10 seconds, it will just freeze and basically file explorer crashes.
Read another thread about MTP driver issue (http://forum.xda-developers.com/showthread.php?t=2380978) but none of that helped. Uninstalled the driver, restart, install new driver. No matter what the MTP driver is the same.
Read somewhere else that it could be a Windows 8 issue so tried on a Windows 7 laptop and same result.
No matter what, file transfers over USB wont work.
So, is this a Nexus 7 issue as a whole (as I had no issue with my N4) or just my particular device as if so, I'll return it for another one.
Any help would be appreciated.
Cheers.
EDIT: Noticed that I'm getting an error on the N7 that I hadn't noticed: Unfortunately, the process android.process.media has stopped. Looks like I might need to reinstall the OS from an image to fix it.
Hi,
I'm having some issues where the MTP driver fails to load. Tried all the obvious stuff and did a lot of reading of forums and stuff but can't find a fix. Could anyone help me to fix it please?
Here's what hardware I have and what I've tried so far:
Tab Pro 8.4 16gb wifi UK model, rooted.
Connected via cable to Dell XPS 17, latest USB drivers installed, win 7 x64.
First of all, I enabled USB debugging and windows installed drivers for all except MTP.
Tried installing the Samsung driver package, same problem. Uninstalled at present.
Installed kies, didn't work, wouldn't even connect to the device. Uninstalled.
Followed the instructions on the wiki but the suite software installs the driver succesfully but then windows won't accept the driver. Tried the workarounds in the wiki but still no luck.
Tried rebooting the tablet and leaving the cable connected.
Tried wiping the cache.
Tried restarting both the tablet and laptop after reinstalling software and drivers, still no luck.
Found several workarounds on my travels, one was a command line for windows to add to usergroup ( it's on the laptop downstairs, will add it to the post tomorrow).
One post said to change a registry entry...really? Tried that, and another registry trick, but still no.
Using the same laptop, I had similar problems trying to flash a custom rom onto an s4, but the CM installer worked first time. I've done a fresh install of win 7 since then.
Can anyone shed any light on this for me please? Is there any kind of workaround? Running out of ideas!
Thanks
Fixed this, well, kind of. Here's a quick rundown of what I did, for people like me who are struggling with connection problems.
I thought I had tried everything, was going to dump the whole thing and then remembered that I'd fixed some previous USB problems (sound card) by doing a clean boot.
First, remove Kies.
The only other thing that is required are the samsung mobile drivers from their website. I tried with and without and this would only work with them installed.
Restart your tablet, make sure MTP is selected.
You can find out how to do a clean boot for you version of windows here.
Leave your device connected via USB cable. Once you have clean booted into windows, windows will attempt to install the drivers from windows update, let it do this. It can take a minute or two to complete. You should then see a green tick in the notification area rather than the dreaded red cross.
If, for some reason, the driver doesn't install first time, you can unplug and then plug back in the USB cable and this should do the trick.
What I did find, is that the connection wasn't consistent, I could restart either my laptop or tablet and then it wouldn't connect, so I'd have to go through the above process again to get it to connect.
Doing this allowed me to flash the Clockworkmod recovery with odin 3.09, but for whatever reason, I was still unable to use the recommended Eimdall suite to flash cyanogenmod.
In the end, I downloaded the CM11 zip file to my tablet (via http) and then used ES file manager to move it to the SDCard root and then clockworkmod picked it up from there.
Also, once CM was installed, there were no connection problems at all, as far as I can see.
Hopefully this will help others in the same predicament.
I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.
Hey guys,
I'm facing a problem: my W10 PC won't install the phone's usb drivers at all. It stay with the yellow sign and can't find the drivers anywhere - not even through Win Update.
I searched for them everywhere I could and without any positive results.
Do you know or have the USB drivers for this phone so I can install them manually?
On my laptop, there are no problems and I tried exporting all the drivers installed on the laptop and load them onto the PC but didn't find any driver so the PC could extract them. I can't access my internals on my PC cause of this.
Anyone?
Thanks in advance.
Solved: Apparently, Windows 10 Home Ed. is not capable of installing any kind of USB drivers (MPT, file transfer, fastboot, USB-debugging - nothing worked) for the device but re-installing with the Windows 10 Pro version, the phone got detected instantly and fully without any problems. Razer CC wasn't helpful at all, this time.