Android-Charging, ADB, & PTP work, but NOT MTP on my Win. 10 Pro 1903 PC

D

DKW3

Contributor
Joined
Feb 8, 2015
Posts
129
Location
San Diego, CA
I got an unlocked & rooted Samsung Galaxy 9+ phone recently, & when connected to my new custom Win. 10 Pro Build 1903 PC Asus Desktop PC via USB (the phone's ADB Debugging & Transferring Files are enabled under 'developer options') charging, adb commands using platform tools, & PTP image transfer ALL work, but NOT MTP (Media Transport Protocol), the phone is simply not visible on the screen. It initially worked for a few days before I encountered this issue, & the phone comes up instantly on my older Dell Laptop, & my old Macbook Pro, so the issue is not the phone (those suggest Samsung "dial codes" do not work with my s9+ come up as "invalid").

I have used ALL suggested online solutions that have worked for others, including Odin, SFC Scannow, Chkdsk, DISM, right-click installing the wpdmtp file from the INF folder, installing the USB MTP device driver in device manager (states nothing is connected "code 20"), updating the Samsung Drivers, Samsung Switch software (can't see the phone as connected) & installing the MTP porting kit, to NO avail. I could find no Microsoft update other then the anniversary fix, which was prior to build 1903 that I am using, & with Media Player installed for my Pro build, the offered Media Pack for the N version does not apply, here.

I also explored a saved Macrium Windows 10 Image Backup file I had created prior to getting the phone, but didn't see any wpdmtp files from the INF folder to copy over.

I am stumped at this point, so any suggestions outside of those I described above to fix this issue, would be greatly appreciated, thanks.

-DKW3
 
This is not meant to be snarky, but the first thing is to get yourself on an up-to-date version of Windows 10. If 1903 isn't already out of support (and I do think it is) then it will be very shortly.

All sorts of "tiny fixes" to Windows that could have an impact on this have occurred over the last almost 3 years.
 
What version of Android?

In the past, I've always had to toggle the MTP protocol in Developer Options in Android.

Yes, update Windows to the latest version.
 
xrobwx71 said:
In the past, I've always had to toggle the MTP protocol in Developer Options in Android.
Click to expand...

This, too, but I will admit to presuming that had to have been done already for the option to even appear. I know that it didn't when connecting most Android devices via USB until developer options had been enabled. But heaven knows it might be there for someone's flavor or an earlier version of Android that I never touched without Developer options on!

But I'm not going further with this with Windows 1903. The first step is getting that machine up to 21H2. Then we need to look at the Android version, as there are many earlier ones that had issues with different transfer modes no matter what.

This is an instance where the OS versions/builds all need to be explicitly known up front.
 
I'm on Android 10.
I just got my custom PC up and running in November 2021 after months & months of planning, so taking things one step at a time, this MTP issue is an unexpected annoyance.
Win. 10 21H2 was just being fully deployed at the time, with all the surprise Win. 11 news overshadowing it, so I felt it too early to update to another build when I was just getting my feet wet with the final Win.10 1903 after upgrading from a perfectly running Win. 7 Pro on my Dell laptop, & of course updates are never a 100% guaranteed solution.
In any case, thanks for the feedback.
 
21H2 has been declared "ready for primetime for all users" at this stage by Microsoft, and is rolling out to the entire Windows 10 user base.

You really need to get off of 1903. I'll say no more about this. Remaining current (which means within 1 version/build of the current one, if not the current one) in the era of Windows As A Service is essential to the proper functioning of Windows. Right now, unless you are an enterprise user who's paying Microsoft for extended service on an old version, that means you're on either 21H1 or 21H2 of Windows 10.

Worries about "bad updates" are overblown, and always have been. They are, quite simply, rare and when they do occur the fixes are usually fast on their heels.

It's funny that this has popped up right now. Just last week I had a client who got a brand new machine that I set up and it was running Windows 10, Version 1909, which made my jaw drop. I haven't seen an "out of the box" Windows machine with a 19XX version in ages. I immediately triggered Windows Update and it went straight from 1909 to 21H2 without a hitch.
 
Hey peeps, hope you are well. Any updates on this issue? PTP is working on my Poco F3 ; but ever since I updated my machine recently MTP doesn't work for that phone and the same for my Samsung S7 Edge -- which makes me think it is an issue with the MTP drivers... Any thoughts?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top