My main desktop PC (the one I did the disc image restore on) is one I built. I installed the latest chipset and USB drivers from ASUS (motherboard) a couple of months ago.
To the best of my recollection, all USB devices I have ever connected to this PC, including other phones, have worked flawlessly except for my S5 and my friend's S4.
I have also done a lot of testing of this problem on my main laptop which is from Dell. Plus three other PCs. Exact same problem on all of them. It is very odd to me that I'm having this problem on five different PCs.
Peter
Odd indeed. And I feel your pain! This has to be hair-pulling-ly frustrating for you. I presume when you connected OK to your friend's PC you were using the same USB cable you use at home? If so that likely rules out the cable as the cause.
When I've had similar problems with older phones connecting, one thing that sometimes helped was to:
- completely disconnect the USB cable at both ends (I swear I don't know why it matters that I unplugged it from the PC, but it DID. It is like Windows knows the cable is connected even though there is nothing on the other end).
- Reboot the phone, reboot the PC. Then hook up the cable and try again.
When you finally solve this issue, one caveat you may also encounter at that point, once you get the connection, is that your files may refuse to copy. If that happens, look for sources on the phone that have obscenely LONG path names for the files. Card/Android and Card/Evernote (if you use Evernote) are the guilty party for me. I can not copy those folders to my PC. The copy will start, and then just stop, as if it were completed, without copying any files. Once I started deselecting those folders, I was able to copy all the other Card subfolders that do not start with a period in the name. ( Those are system files anyway, so I don't need to back them up).
Someday if android app devs ever realize they need to have a user option to save content and backups to the REAL ExtSdCard for every app they make, we won't have a need to backup any of the Card files anymore.
I keep asking myself the same question. What is "different" about this fellow's home PCs than that of his friend's in another location. I can't think anything wifi related would be involved in this.
I know you won't like this next suggestion, but I think it is worth a try if you have no other options. Reformat the C drive on one of your PCs and install Win7 from scratch, and see if it will THEN connect after you install the Samsung USB driver.
Hey, have you seen this:
"I just spent HOURS on Google trying to figure this out. More than likely this is the answer, somehow your Qualcomm Modem settings got changed.
If you are using Android 4.3 open the dial pad and dial *#0808#
Android 4.2 *#7284#
then under Qualcomm USB or USB settings it should be on MTP or MTP+ADB, it was probably on RMNET + DM + MODEM. Make the change and choose OK.
All should be fine now.
"
Might be worth looking into.
I just read something that brought back some really moldy memories of Windows Gone By ---
First, check Device Mgr. and make sure you don't have any yellow triangles, especially in the USB section. If there are none, then try THIS:
(This is a real zebra hunt move, but at this point I'd be trying it)
Boot SAFE MODE. Look in Device Mgr. for any yellow triangles. Believe it or not, sometimes a device can have multiple listings of the same "unrecognized device" yellow triangles attached to it, and for some odd reason they will NOT show up unless you look in SAFE MODE. If you find any, remove ALL of them. Then reboot normally and check Device Mgr. again. If no triangles, try connecting the phone. If it still doesn't connect, WHILE the cable is still hooked up, check Device Mgr. again. It might yield a clue to what is wrong.
Also, have you ever looked at the Windows System Event Viewer? That might tell you something too from each time you connected the phone. It's under Control Panel / Administrative Tools / Event Viewer. It's often rather cryptic, but it might help.