Related
I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Disable USB debugging.
Unplug/plug in your nexus.
The USB IDs change for some reason when you have USB debugging turned on and the MTP device isn't recognized as such. PTP (camera) mode continues to work for both cases though.
Thanks for the suggestion but It still fails. I disabled debugging and still can't connect. Switching USB modes didn't help either.
If that doesn't work uninstall the adb driver & then plug your tablet back in so it will reinstall
My next suggestion would to reboot the tablet with USB debugging turned off.
If that doesn't work, my next suggestion would be to delete the existing drivers and force reinstall.
All with USB debugging turned off.
johnnyninja said:
I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Click to expand...
Click to collapse
Make sure after you plug in your device you're looking at your tab and click OK on the pop up........
Sent from my Nexus 7
Thanks for all the suggestions. It's working now. I was just about ready to delete the driver and the tablet started to be recognized consistently. I was in the settings screen and toggled debugging on and off while plugging in the tablet. I noticed the info bar at the top alternating between showing "debugging" and "media device" and I selected each one a couple of times when they came up. I think that it finally worked through the ID confusion that was mentions. I'll follow the the rest of the instructions if the problem comes back.
Thanks again.
It's acting up again so I'm going to try deleting the drivers. I thought I knew what to do but I can't find any information. What's the procedure to delete the driver? I'm running os x lion
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
johnnyninja said:
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
Click to expand...
Click to collapse
Rooted my nexus 7 (2012) last night and struggling with my laptop not recognizing it. This thread solved it!
Delete the ADB on my window, toggle off debugging and restart the nexus 7 with usb connected to laptop. works like a charm.
Thank you!
Guys, my N4 got this problem too.. until just a few minute ago
I read somewhere ini goge groups (i think N5 group), and found explanation that we can change ADB or MTP "mode" on device manager. On "Androoid ADB Device" right click and select "Update Driver Software". Click "Browse My Computer for Driver Software" and then "Let me pick from blablabla...." And then select MTP USB Device, "next" and my N4 detected on Windows Explorer.
Hope it will be usefull for you guys.
I just purchased an HTC M8 running software number 1.55.631.4 and I am using Windows 7.
- I first tried plugging in the phone via usb, and Windows notified that the driver install failed.
- Then I tried installing the drivers manually using the All in one toolkit, tried plugging in the phone, and nothing happened.
- Then I uninstalled the driver, and tried installing the HTC Sync Manager (driver included), plugged in the phone, and still nothing happened.
- This problem occurred on an HP EliteBook, so I tried on another HP laptop I have at work, and the driver install failed when I plugged it in as well.
- Now I am here.
Does anyone have any possible ideas/solutions? Any feedback is appreciated.
bump
Install HTC Sync Manager, then uninstall it but leave the drivers. Should then work fine
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
I'm running into the same problem. Have just unlocked bootloader and rooted the phone. I now want to achieve S-OFF. However when I get to the ADB push command nothing happens. I notice the error "HTC MTP Device - Failed" when it tries to update drivers after passing command adb reboot. Tried installing HTC Sync and uninstalling a few times but stuck in the same place. Any way around this?
Thanks
Running Windows 7 64bit. Software version 1.54.161.10
EddyOS said:
Install HTC Sync Manager, then uninstall it but leave the drivers. Should then work fine
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
Click to expand...
Click to collapse
I just tried this, and it didn't work. When I plug in the phone via USB, my computer doesn't even make the notification sound that something has been detected. The red light on the phone shows its charging, but my computer doesn't even show that anything was plugged in or detected. Could this be a problem with my computer?
If another computer works, then yes
andrewjrr said:
I just tried this, and it didn't work. When I plug in the phone via USB, my computer doesn't even make the notification sound that something has been detected. The red light on the phone shows its charging, but my computer doesn't even show that anything was plugged in or detected. Could this be a problem with my computer?
Click to expand...
Click to collapse
what about device menager ?
Maybe you have some other drivers installed for android devices, try uninstalling them first.
wodzini said:
what about device menager ?
Maybe you have some other drivers installed for android devices, try uninstalling them first.
Click to expand...
Click to collapse
Nothing in device manager either.
I do have my Nexus drivers installed. Do you think that could be the problem? Should I uninstall everything previous?
I tried installing HTC sync manager on my work laptop (which has no other phone drivers installed), and it's still the same problem. One thing I've observed though is when I leave the phone plugged in to the computer USB and do a reboot on the phone, the computer detects it at the startup "htc one" screen, but the device disappears seconds later as the phone continues to boot. It's like it detects it initially, then some software with the phone is causing it to fail. Any ideas?
bump.. went through HTC customer service and they pretty much got me to try reinstalling drivers, sync manager, etc.. didn't work. Said they would push me to the next level tech support which would be as long as 7-10 business days and that was last Monday and still haven't heard anything
I have recently root my samsung tab pro 8.4 wifi version. Everything seems to work well, except USB connection to my windows7 desktop. I installed the latest version of Samsung usb driver (download from Samsung's web site for my device). Whenever I connect it, media device mode, the "installing device driver software" icon spins for couple of minutes, then I got the error of "Device driver software was not successfully installed" . In the detail dialog window, it says "MTP USB Device" failed with a red cross. what did I do wrong? thanks.
I have tried several different USB 2 ports on my computers. Also I have Developer mode turned on, with or w/o USB debugging checked. Nothing seems to work. Also the camera mode doesn't work either.
Did you install kies 3 from samsung?, this should install all the drivers you need.
http://www.samsung.com/us/kies/
I tried with this version of kies from samsung's website, not working. Got the same failed to install device driver message.
In windows device mananger, it shows a MTP USB device with yellow "!" mark on it. If I try to update driver from here with the driver installed on my computer, it says I have the latest driver installed already.
dealcrack said:
I tried with this version of kies from samsung's website, not working. Got the same failed to install device driver message.
In windows device mananger, it shows a MTP USB device with yellow "!" mark on it. If I try to update driver from here with the driver installed on my computer, it says I have the latest driver installed already.
Click to expand...
Click to collapse
Try going to Device Manager in Windows, find the device, pick the option to select from the drivers on the computer, then pick the "USB MTP drivers" (generic, not Samsung) and see if that helps.
redpoint73 said:
Try going to Device Manager in Windows, find the device, pick the option to select from the drivers on the computer, then pick the "USB MTP drivers" (generic, not Samsung) and see if that helps.
Click to expand...
Click to collapse
thanks for your help. I tried your suggestion, and
I went to the Device Manager, and select the "MTP USB Device" with yellow "!" mark, choose this menu,
Update driver software->Browse my computer for driver software->let me pick from a list of device drivers on my computer
I see two drivers, however either works for my 8.4 pad. It says "This device cannot start (code 10)"
Also when I open the properties for this device in device manager, it shows its driver running is from Microsoft, driver version 6.1.7600.16385. Should be a driver from Samsung?
dealcrack said:
thanks for your help. I tried your suggestion, and
I went to the Device Manager, and select the "MTP USB Device" with yellow "!" mark, choose this menu,
Update driver software->Browse my computer for driver software->let me pick from a list of device drivers on my computer
I see two drivers, however either works for my 8.4 pad. It says "This device cannot start (code 10)"
Also when I open the properties for this device in device manager, it shows its driver running is from Microsoft, driver version 6.1.7600.16385. Should be a driver from Samsung?
Click to expand...
Click to collapse
Are you running stock TouchWiz ROM? Just to be sure.
Otherwise you could remove all your USB drivers related to Android and start from scratch with just the Sammy driver. I had to do that for my previous OnePlus One, it just wouldn't connect. It chose a wrong driver each time I hooked it up so I had to just remove those from the driver store and then make it choose another one. That was for ADB thought, but I guess it couldn't hurt to try anyways.
The reason I'm mentioning if you're on stock ROM is because this morning, on CM nightly 01-24 I had some troubles with my tablet being read by Windows, it was fixed in 26 so.. Just wanted to mention it.
CuraeL said:
Are you running stock TouchWiz ROM? Just to be sure.
Otherwise you could remove all your USB drivers related to Android and start from scratch with just the Sammy driver. I had to do that for my previous OnePlus One, it just wouldn't connect. It chose a wrong driver each time I hooked it up so I had to just remove those from the driver store and then make it choose another one. That was for ADB thought, but I guess it couldn't hurt to try anyways.
The reason I'm mentioning if you're on stock ROM is because this morning, on CM nightly 01-24 I had some troubles with my tablet being read by Windows, it was fixed in 26 so.. Just wanted to mention it.
Click to expand...
Click to collapse
Yes, I am on the stock TouchWiz ROM, but I rooted it following steps from one thread in this forum. Before rooting, I was able to connect. I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem? Will going to CM ROM solve my problem?
Also, can you tell me steps to remove all my USB drivers related to Android in Windows 7?
dealcrack said:
Yes, I am on the stock TouchWiz ROM, but I rooted it following steps from one thread in this forum. Before rooting, I was able to connect. I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem? Will going to CM ROM solve my problem?
Also, can you tell me steps to remove all my USB drivers related to Android in Windows 7?
Click to expand...
Click to collapse
It may work to install CM11 or CM12, BUT try this toolfirst (uploaded to my personal box account) Find all your mobile device drivers in this list and mark them and go to "File" and click "Uninstall marked drivers", restart your PC and plug in your tablet. Then try plugging in LG after so it gets drivers later. I'm not sure if it will work. But it should apply new drivers. If it doesn't work, uninstall the drivers one more time and download the Samsung drivers from 3rd party and install them and apply then manually to your tablet through Device Manager in Windows.
https://app.box.com/s/7njztz17hekfkpxbjk7h79xsctnmuptn
Anyways, try this first.
dealcrack said:
I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem?
Click to expand...
Click to collapse
Its always a possibility. I'd try to uninstall the LG drivers. You can always re-install later (if needed).
In a perfect world, the Sammy drivers would be what you want. But this is of course not a perfect world. I've had better luck using the "generic" Microsoft MTP USB drivers over the HTC drivers on my HTC devices.
CuraeL said:
It may work to install CM11 or CM12, BUT try this toolfirst (uploaded to my personal box account) Find all your mobile device drivers in this list and mark them and go to "File" and click "Uninstall marked drivers", restart your PC and plug in your tablet. Then try plugging in LG after so it gets drivers later. I'm not sure if it will work. But it should apply new drivers. If it doesn't work, uninstall the drivers one more time and download the Samsung drivers from 3rd party and install them and apply then manually to your tablet through Device Manager in Windows.
https://app.box.com/s/7njztz17hekfkpxbjk7h79xsctnmuptn
Anyways, try this first.
Click to expand...
Click to collapse
I download this tool, and remove all Samsung or Android related USB driver. Restart my computer and connect the pad it's not working. Then I uninstall the Samsung driver software, and all USB driver. Then restart and install a samsung driver from the thread about how to root my pad in this forum. Connect my pad, no luck. Still the same problem. I am about to give up.
redpoint73 said:
Its always a possibility. I'd try to uninstall the LG drivers. You can always re-install later (if needed).
In a perfect world, the Sammy drivers would be what you want. But this is of course not a perfect world. I've had better luck using the "generic" Microsoft MTP USB drivers over the HTC drivers on my HTC devices.
Click to expand...
Click to collapse
I uninstall my LG driver too, along with all Samsung/Android usb driver with the tool from previous reply. No luck, It still shows a MTP device with yellow "!" mark.
Just before I about to give it up, it connects to my another computer now, which is my main computer and it had trouble connecting to. All I did was restart my pad several time and odin twrp recovery to it. It connects after rebooting. No idea what cause this problem, but it works now. thank you for all your help.
dealcrack said:
Just before I about to give it up, it connects to my another computer now, which is my main computer and it had trouble connecting to. All I did was restart my pad several time and odin twrp recovery to it. It connects after rebooting. No idea what cause this problem, but it works now. thank you for all your help.
Click to expand...
Click to collapse
Glad you sorted it out, to some degree or other.
USB connectivity on Android devices is very tricky, at least on Windows (can't speak on other OSes). My HTC phone connects fine to my work laptop with the HTC drivers. On my home computer (also Win7) it frequently drops adb connection and I have to manually select the "generic" Microsoft drivers to make it work (and the HTC drivers never seemed to work completely right either). My Sammy Pro 8.4 seems to connect just fine to my home PC, however. So it seems its just a crap shoot what kind of connectivity you will get, really.
Got a weird one - got the M9, able to connect it at work and on a laptop but not the computer I've got ADB and everything on.
Phone simply does not recognize as a USB drive, I get that it's looking for "Android phone" but it never shows as a device. (MTP, ADB, etc) Suggesting where the HTC drivers I just downloaded results in me getting that they're not what it's looking for.
This is a computer that has worked for my EVO 4G, 3D, 4G LTE, One m7, m8 along with being fine with a host of other devices.
I've uninstalled and reinstalled everything I know to do but no ADB, no MTP. Not a recognizable device to windows other than being "Android Phone" with no drivers findable.
Some things I've done:
Installed HTC Sync
Deleted HTC Sync
installed HTC drivers pack
removed
Bang head on keyboard
Plug into different USB ports
Change cable
Just one computer, the one that I've used with no problem for ages, wants to be a punk
Have you tried enabling USB debugging?
-settings
-about
-software information
-more
-tap build number 7 times
Then go back to settings and enter developer options and check USB debugging
NotSatan said:
Have you tried enabling USB debugging?
-settings
-about
-software information
-more
-tap build number 7 times
Then go back to settings and enter developer options and check USB debugging
Click to expand...
Click to collapse
Yup. I just get "Android Phone" as an unrecognized device. I've also set to Disk Drive, MTP, debugging on and off.
Just plugged in the M8, same issue... so it's something that's not M9 specific...
Well that's as far as my expertise goes haha.
mildlydisturbed said:
Got a weird one - got the M9, able to connect it at work and on a laptop but not the computer I've got ADB and everything on.
Phone simply does not recognize as a USB drive, I get that it's looking for "Android phone" but it never shows as a device. (MTP, ADB, etc) Suggesting where the HTC drivers I just downloaded results in me getting that they're not what it's looking for.
This is a computer that has worked for my EVO 4G, 3D, 4G LTE, One m7, m8 along with being fine with a host of other devices.
I've uninstalled and reinstalled everything I know to do but no ADB, no MTP. Not a recognizable device to windows other than being "Android Phone" with no drivers findable.
Some things I've done:
Installed HTC Sync
Deleted HTC Sync
installed HTC drivers pack
removed
Bang head on keyboard
Plug into different USB ports
Change cable
Just one computer, the one that I've used with no problem for ages, wants to be a punk
Click to expand...
Click to collapse
Was this resolved? Having this same issue...
It looks like you are just trying to get ADB?
* Make sure USB debugging is enabled (I know you said it is).
* Make sure your computer is not blacklisted on your phone from making connections to ADB.
* Make sure any htc sync or driver package is totally removed.
* Make sure your keyboard still works enough after the head banging. You will only need a mouse, enter, space, a, b, c, d, e, i, s and v to complete the following; but more is always better just in case you need an h or something.
Look in Device Manager. Is it an unknown device (is there a yellow exclamation mark or something next to it)?
Try deleting the driver that it's using - like actually choose to delete the driver software from your machine, not just remove the device.
Once you're totally clean and the phone shows up with a yellow !, try update driver -> let me choose -> have disk -> your android sdk's extras/google-usb-driver .inf.
Pick one of the ADB ones, not sure if it'll be composite or the other one, then test with
Code:
adb devices
in your cmd window.
If it shows up, cool. If not try the other ADB usb driver from the inf...
xfinrodx said:
It looks like you are just trying to get ADB?
* Make sure USB debugging is enabled (I know you said it is).
* Make sure your computer is not blacklisted on your phone from making connections to ADB.
* Make sure any htc sync or driver package is totally removed.
* Make sure your keyboard still works enough after the head banging. You will only need a mouse, enter, space, a, b, c, d, e, i, s and v to complete the following; but more is always better just in case you need an h or something.
Look in Device Manager. Is it an unknown device (is there a yellow exclamation mark or something next to it)?
Try deleting the driver that it's using - like actually choose to delete the driver software from your machine, not just remove the device.
Once you're totally clean and the phone shows up with a yellow !, try update driver -> let me choose -> have disk -> your android sdk's extras/google-usb-driver .inf.
Pick one of the ADB ones, not sure if it'll be composite or the other one, then test with
Code:
adb devices
in your cmd window.
If it shows up, cool. If not try the other ADB usb driver from the inf...
Click to expand...
Click to collapse
Thanks. I tried this and nothing helped. Finding the device from ADB devices isn't the issue. It is that the SD card does not show up in Windows Explorer. Other than taking the SD card out and using a micro SD card adapter for my PC, I cannot transfer files via USB. See attached image. The MTP is the issue. Why doesn't HTC Sync/Drivers from HTC.com fix this? -_-;
Oh, I'm sorry I misunderstood your need. Well if adb works yes can always push/pull... Which version of Windows are you on? Is it possibly a 32/64 bit driver issue? I'm reaching here, HTC sync should cure whatever ails you... I hate MTP.
xfinrodx said:
Oh, I'm sorry I misunderstood your need. Well if adb works yes can always push/pull... Which version of Windows are you on? Is it possibly a 32/64 bit driver issue? I'm reaching here, HTC sync should cure whatever ails you... I hate MTP.
Click to expand...
Click to collapse
Windows 7, yea it's probably a64 bit problem.
typhoonikan said:
Was this resolved? Having this same issue...
Click to expand...
Click to collapse
Resolved after I updated to windows 10
mildlydisturbed said:
Resolved after I updated to windows 10
Click to expand...
Click to collapse
Not for me. Would love a solution.
Bump. Help? So annoying.
typhoonikan said:
Bump. Help? So annoying.
Click to expand...
Click to collapse
I' having the same issue. M9 not recognized as an MTP device on Win 10 64 bit. Running CM 12.1. Adb works, and the device shows up in Device Manager as "MTP USB Device" under "Portable Devices" section. Right clicking gives only propertied and scan for h/w change option, there is no option to update device driver. Phone shows up as HTC M9 under "Unspecified" category in "Devices and Printers".
My Lg G2 runs CM12.1 as well and works fine as mtp device. (Adb works too). I have been trying everything to get M9 working, but failed.
EDIT
Solved the issue trying random things! The issue was the xposed module "Xposed Media Scanner Optimizer" which was preventing MTP mode by not allowing media scanner to run.
droidphile said:
I' having the same issue. M9 not recognized as an MTP device on Win 10 64 bit. Running CM 12.1. Adb works, and the device shows up in Device Manager as "MTP USB Device" under "Portable Devices" section. Right clicking gives only propertied and scan for h/w change option, there is no option to update device driver. Phone shows up as HTC M9 under "Unspecified" category in "Devices and Printers".
My Lg G2 runs CM12.1 as well and works fine as mtp device. (Adb works too). I have been trying everything to get M9 working, but failed.
EDIT
Solved the issue trying random things! The issue was the xposed module "Xposed Media Scanner Optimizer" which was preventing MTP mode by not allowing media scanner to run.
Click to expand...
Click to collapse
I do not have that module installed, so that can't be what is keeping Windows from noticing my phone as a storage device.
Also, if i hadn't mentioned it before, I am able to see my device with adb devices in the command prompt.
typhoonikan said:
I do not have that module installed, so that can't be what is keeping Windows from noticing my phone as a storage device.
Also, if i hadn't mentioned it before, I am able to see my device with adb devices in the command prompt.
Click to expand...
Click to collapse
Most likely it is a driver conflict or missing drivers. Uninstall all portable device drivers and start again.
I wish I stole my HTC M9.
typhoonikan said:
I do not have that module installed, so that can't be what is keeping Windows from noticing my phone as a storage device.
Also, if i hadn't mentioned it before, I am able to see my device with adb devices in the command prompt.
Click to expand...
Click to collapse
I have the same issue, nothing! MTP device driver is not present...adb works but MTP nothing.
Please, someone check if the win 10 installed is N version? maybe is this the problem, maybe....
Thanks
Something to try. Connect your phone to the PC, then go into device manager and look for portable devices. The phone should be listed there and most likely you will see a yellow triangle on it. Click on it and choose to uninstall. After it uninstalls, unplug the phone from the PC and then plug it back in. Allow it to fully re-install before doing anything.
DeeZZ_NuuZZ said:
install another theme from themes Manager which is dark, or has dark Keyboard. the easiest way
Click to expand...
Click to collapse
Nope. I've played with device manager for over an hour at a time. Windows doesn't like m9.
Well, my understanding is that the driver used for mtp for Android devices is the same driver that is used for Windows Media Player. When you connect your phone to the PC and open Windows Media Player, is the phone listed there? If not, then you may have something interfering with media scanner. Have you tried starting the M9 in safe mode and then connecting to the PC?
Weird. You must bring it to store to fix
This thread is about the defective installation of the LGE Android mtp device driver. Note that when the phone is on all the drivers seem to work correctly (LGE mobile ADB interface under "android device", G4 driver under "portable devices" and LGE mobile USB serial port).
The issue presents when i switch the phone to "download mode"; in this mode the "G4" driver (which is the LGE Android MTP device) appears not to be working.
The problem persists on three different PCs, either with windows 10 or windows 7 and either with a LG G4 or an LG G3.
I would like to root my G4 device following the firmware flash procedure 10E, but I am not sure that I can flash the device if there is this kind of issue with the drivers. Is it normal that the device appears not to be working?
I am having the same problem as you were. I am using Windows 7 and several versions of the LG drivers with the same result; Everything is fine when my device (a G4) is booted normally but in Download mode I get the same error as you (This device cannot start. (Code 10)).
I have tried everything I can think of, I have uninstalled all the old Android drivers with USBDeview, disconnected the internet to stop windows update installing its own drivers, different USB ports and cables.
Did you ever get your device rooted?
SO... in my case (YMMV - be careful) it turns out there is no need for the device manager to be error free when the phone is in download mode.
I just got root using this procedure from the "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread with no issue. I thought it would work because the LGMobileSupportTool was reporting as being connected to my phone despite the error (This device cannot start. (Code 10)) in device manager. Sure enough everything worked fine. I wish it hadn't taken me (literally) 20 hours of fecking around with drivers to get to this point though...
ETA I have a G4 H815 (EU)
i had a problem too. my device is rooted and i cant access mtp after... what might be the problem?
012512 said:
i had a problem too. my device is rooted and i cant access mtp after... what might be the problem?
Click to expand...
Click to collapse
Edit. Performed a factory reset and it worked as it is.
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
PDAlama said:
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
Click to expand...
Click to collapse
But in my case only greenify is installed module,
Why you only post that After I factory reset my phone. Haha anyway thanks for the information.
PDAlama said:
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
Click to expand...
Click to collapse
This helped me so much when I was trying to upgrade to Android M. After un-checking all my xposed modules, both my pc and laptop were finally able to read my LG G4 and install drivers, mtp, and others correctly without fail.
Same problem here with an AT&T G4. I've tried 2 different Win7 laptops (one of which has never had any Android drivers/tools installed previously), 3 cables, and even performed a factory reset. MTP Drivers work when booted normally, but fail ("Code 10") when in download mode. Any additional suggestions?
EDIT: As suggested by other posts/forums, this issue can be ignored, and isn't an actual problem. ADB works successfully, even if the MTP device isn't working in Windows' Device Manager. (This MTP device appears in Windows' Device Manager the same as it does when a USB Debugging connection hasn't (yet) been authorized on the Android side. My guess is that since Android isn't fully booted while in Download Mode, there's nothing to approve the connection. Either way, it doesn't affect the function of Download Mode, as long as the other Android-related devices in Device Manager have their drivers loaded successfully.)
TL;DR version: When in "Download Mode", as long as the other Android-related device(s) in Windows' Device Manager are working, ignore the "Code 10" error / "yellow triangle" on the MTP device. It's not needed for Download Mode to work.