Database Info

[Q] Phone wont be recognized by computer

My Samsung Intercept wont connect to my computer, everytime I plug it in, I get USB device not recognized, how can I get it to be recognized? Im running android 2.2.1, and my computer is running Windows 7 Ultimate 64-Bit

I tried posting a link but the spam prevention police apparently wont let me post links until I have 8 posts. So I'll just quote:
First I tried to use Win 7′s XP mode, which was a total failure. The Windows stock Virtual PC cannot control any devices, it just reads them as belonging to the real computer. After a lot of searching I found the open source Oracle Virtual Box, which is Windows Virtual PC on crack. With Virtual Box, you can mount any number of operating systems to play around with. As a bonus it has the capability to see external devices as its own. All you need is an install disk for your operating system of choice. I had gotten the Intercept to work with both XP and 7 32 bit, so I chose to install a Win 7 32 virtual machine.
For all the specifics on how to install a virtual operating system in Virtual Box, read the user manual. Its large and technical, but skimming the first two chapters should tell you all you need to know to get started. The short version, you set up a partition for your virtual machine, you then “boot” the virtual machine with the install disk of your operating system of choice. You then go through all the normal installation steps, and bingo-bango you now have a virtual copy of XP/7/whatever.
Here is where things get hazy. I was under the impression that the virtual machine would be where I would see the phone. However for mysterious reasons, suddenly the phone now gives me the option to mount and my main Windows 7 64 has no problem letting me into the phones drive!
I don’t know why. I can close the virtual machine and still have access when I plug in. I wish I knew what the heck was going on and how a virtual 32 bit 7 convinced a real 64 bit 7 that the Intercept is OK, but I do not. All I know is that Virtual Box somehow worked for me, perhaps it can work for you. Other than that Virtual Box is a nifty tool I should have had long ago. Good luck!
UPDATE: I wrote this a couple months ago and while it did work, I have a funny feeling that its all just pure luck as to if Windows will bother to recognize the phone. I have computers it works fine on and some that refuse to see the phone no matter what I do. The whole key is to just keep trying, something will work eventually. If all else fails get an app like SwiFTP and move on with your life.
Click to expand...
Click to collapse
Retrieved from wordpress.

Thank you very much for this information, I will get to trying the Virtual Box and the SwiFTP, thank you again.

The above information you gave still didnt work :/, do you or anyone else know what I could do to fix?

Hello, I wanted to say that the whole process for the computer to see the Samsung Intercept is buggy to say the least. I have a good knowledge base of computers as I work as a Desktop Support technician for the past 10 years. I read many posts and replies. None seem to be concrete on a resolution. I tried the usual methods. I downloaded the Samsung SWUpdate+Patch. I downloaded the Sprint USB Modem drivers from Samsung's Web site. I also downloaded the custom files for the Kernel and custom recovery. The first thing I tried on all four of my computers was to install the Samsung USB Modem drivers. The second thing I did was to install the SWUpate+Patch software. My first test computer was a Compaq D500 desktop. Windows XP-SP3 with USB 1.0 ports and a USB 2.0. I placed my phone in USB Debugguing Mode. I then powered off my Phone. I held down the three magic keys to get the phone in "Download" mode. I checked Add/Remove Programs both programs were installed- Samsung USB Modem Driver and the SWUpdate. I first opened the Samsung SWUpdate program. I followed the onscreen instructions of the Samsung program. The program could not communicate with the phone. Bottom right corner of the program said disconneted. I tried chaning the Port Settings in the program to COM1, COM2, etc. All said disconnected. I tried opening the Samsung program several times. Restarting the phone, unplugging the battery etc. I also tried using a different USB cable besides the one that came with the phone. No communication. I tried the same process on another PC which had Win7Pro 32Bit SP1. Almost same results, but I had the computer install these three devices when I opened the Samsung program and connected my phone:Android UMS, S3C6410 Android ADB, CDC Abstract Control Model (ACM) I thought I was good. Status still Disconnected. I restarted the computer tried the whole process again. This time the computer gave me three messages of "Device not Recognized." So I tried a few more different was to get the drivers into Device Manager nothing worked. I even tried that PDA2net app that app wouldn't see the phone wither. Then I looked into the PDA2net directory and saw some drivers .INFs that I thought might work.. I would get a little farther, but then the driver seemed to install and partially recognize the devices, but then a message said that it could start "Error 10" So I tried another computer. Windows 7-64bit. I knew this was going to be a long shot..and it was.. Samsung USB Modem Driver not supported on this version of Windows. So I tried my work computer Win7Enterprise 32Bit. Same issues Device not recognized three or four times. I tried the two USB cables for my phone the OEM one and Aftermarket. No luck. So I had my old trusty Dell D600 laptop. WinXP-SP3 32bit USB 1.0. I installed the Samsung USB Modem driver then the Samsung SWUpate app. I got my Recover.tar file dropped into the Bin dir. I opened the Samsung SWUpdate app and holy **** the damn program was able to connect to my phone I couldn't believe it.. I wanted to take a screen shot of it working just so I could make sure it wasn't B.S. I used my laptop with an Aftermarket USB Cable. I'm not sure if it's a Data USB cable or just a charging cable. I don't think there is two different cables as I've read many times on different fourms. I'm not sure why my laptop works with the phone. When my phone did finally connect it connected on COM3. So maybe it's a port setting/IRQ. I also turned off my Firewall each time just incase it was blocking communication.
If anyone has any questions please feel free to reply. I will try to help in any way possible. I wanted to say thanks to XDA Forum and to Super-6-1 on YouTube..you guys Helped Me more than you know.!!!!!

[Q] Help: GT-P6210 not detected by W7 32 bit Enterprise at all.

Hi,
Quick background: Former sys admin with some Unix experience. Already own a Toshiba Thrive rooted with CWM. Gave that to the wife and got me the GT 7+. Read the forum here prior to buying. Rooted on day one.
Stats: GT-P6210 Build: HTJ85B.UEKL1 P6210UEKL1
PC: Windows 7 21 Bit Enterprise SP1
Kies: Kies_2.1.1.11124_17_6
Later on the first day, after installing aps, I installed latest version of Kies and plugged it in with the supplied usb cable in order to transfer some files to my Sandisk 32Gb microsd. Kies already running and debugging off as per the instructions. Results: Tab plays a notice and I see the MTP connected icon. My pc does NOTHING. No sound, no notice, Kies does nothing.
I unplugged and tried the other 3 ports. 2nd port gives me same result and on the 3 & 4 port I lose the tab's MTP notice and it begins charging.
So, this is what I have done in order:
1. Re-installed Kies--->same result. No MTP notice on tab.
2. Debugging on--->same
3. Tried in on my room mate's W7 machine---> Alas! I get a driver installation and I am able to see both drives. I quickly unplugged and thanked him.
4. Cleaned my pc by:
a. Deleting all USB controllers
b. Deleting all USB installations on registry (HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTOR)
c. CCLEANER the whole system.
d. Turn off. Pull off battery. Press power button to drain motherboard.
e. Restart and re-install USB controllers.
f. Restart again.
5. Plug in again--->Tab plays a notice and I see the MTP connected icon. My pc does NOTHING. No sound, no notice, Kies does nothing.
6. Pull my hair, bang my head, wished I would have kept the Thrive. (just plug, and drag and drop)
Left it plugged to the pc overnight. Next morning I see the found new device on systray and it is trying to find drivers. I quickly open Kies and see some activity as it tries to connect. and after a few seconds, it stops. Result: No drivers installed, no Kies recognition, no drive letters, nothing.
8. At this point I ask my room mate to let me plug in on his pc to see if he still sees it and nothing happens on his pc.
9. I wipe the table back to stock.--->Tab plays a notice and I see the MTP connected icon. My pc does NOTHING. No sound, no notice, Kies does nothing. Then after I tried other ports, it begins charging and I lose the MTP notice.
10. I re-roo,t reconfigure the beast, and do a backup. Tablet is running smooth as silk, but it never connects. This all happened in the last three days.
11. Last thing I did, as I am writing this with the tablet plugged in to the pc and MTP notice on, was to un-mount the microsd and remount. MTP re-initializes and it does nothing.
I may be suspecting a cable and unfortunately, I am in no position to get my hands on another one in a timely manner. At this point, I could reflash back to a stock firmware, send back to amazon and wait for another one to come in three to four weeks (I am deployed to a remote area) and I just don't want to do that.
The tab runs great. Love the size and speed. I guess I can continue taking out the microsd card out every time I want to add a file, but I am afraid that it may eventually end up ruining the card and possibly the tablet.
Please help. I have scoured the internet, but all I ever find is solutions that I already have tried.
Thanks in advance,
Sal

you could use adb over wifi.. There are a few apps in the market for this. Does adb recognize the tab when its plugged in via USB?
Also try Android commander, it is a GUI based adb server, you should be able to navigate to sdcard/extstorages/ and your external card should be there
Sent from my HTC Glacier using Tapatalk

You could also use a file explorer like Root Explorer and Dropbox to transfer files back and forth.

Have you tried a different USB port on the PC? like one round the back.
Also, try without the sdcard in.
Ticked/unticked USB development/debugging on the tablet?
If it works on another computer though it would suggest its your own PC which has the problem, not the tablet.
tried with Linux on the same PC?
Does Odin see the tablet when in download mode?
if you have clockwork mod recovery, doesn't that have a USB mount option ? It does on my gs 2. My tab isn't with me to check.
Oh and kies has an option to reinstall the driver. Did you try with the older version of kies again?
Sent from my GT-I9100 using xda premium

ringnutz said:
you could use adb over wifi.. There are a few apps in the market for this. Does adb recognize the tab when its plugged in via USB?
Also try Android commander, it is a GUI based adb server, you should be able to navigate to sdcard/extstorages/ and your external card should be there
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
I'll try adb. I will install it and see if how it works. Time is tight so I will report later.
Sal

crunchie-uk said:
Have you tried a different USB port on the PC? like one round the back.
Also, try without the sdcard in.
Ticked/unticked USB development/debugging on the tablet?
If it works on another computer though it would suggest its your own PC which has the problem, not the tablet.
tried with Linux on the same PC?
Does Odin see the tablet when in download mode?
if you have clockwork mod recovery, doesn't that have a USB mount option ? It does on my gs 2. My tab isn't with me to check.
Oh and kies has an option to reinstall the driver. Did you try with the older version of kies again?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I have done all that you mentioned with the exception of Linux and Odin. I am not going to get into Linux as that would start a whole other project. I will install ADB to see if I can force the drivers.
I just tried the CWM mount USB mount but get "E: Unable to open ums lunfile (No such file or directory)"
Also, on my friend's pc worked once but not after that.
I will continue to explore the ODIN suggestion.
Thanks,
Sal

chad_k69 said:
You could also use a file explorer like Root Explorer and Dropbox to transfer files back and forth.
Click to expand...
Click to collapse
I use ES Explorer (wonderful app!) now. My end-state is not to have to remove the card every time I transfer a file.
Sal
EDIT: Sorry, I see now the dropbox suggestion. Yes that would work for smaller files, but I am not sure that dropbox can handle movie size files. It would be a last resort solution.
Thanks,
Sal

Adb is probably going to be your best bet. It can be a pain to set up at times, but in the long run is a must have for any Android device. Kies normally installs the drivers that adb uses, so hopefully you can get them to install. If it still doesn't work I would suggest swapping it out for a new tab, as much as that sucks. If you need help, I constantly check these forums, so I should be able to provide some support
Sent from my HTC Glacier using Tapatalk

ringnutz said:
Adb is probably going to be your best bet. It can be a pain to set up at times, but in the long run is a must have for any Android device. Kies normally installs the drivers that adb uses, so hopefully you can get them to install. If it still doesn't work I would suggest swapping it out for a new tab, as much as that sucks. If you need help, I constantly check these forums, so I should be able to provide some support
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Well, got ADB installed and running. Set the path and ran it. Plug the tab with debugging clicked on, and got "MTP connected" on the tab's screen. At this point I am excited since I never seen the "MTP connected " on debug mode. I typed the "adb devices" command and got "List of devices attached" ___________________.
Yep, blank. Obviously the pc is not seeing it. My conclusions are the following:
1. Bad cable
2. Bad device
The fact that it recognized once on my room mates' pc and then none at all, and the fact that it was recognized on my pc for a brief random time, then it means that the device can't handshake with the motherboard and thus is a communication issue.
I'll try my luck with Samsung tech support and see if they can replace the cable.
Just thought of something, would installing Windows XP Mode under a Windows Virtual PC recognize new devices or just feed from the Windows 7 library?
Sal

saldman said:
Well, got ADB installed and running. Set the path and ran it. Plug the tab with debugging clicked on, and got "MTP connected" on the tab's screen. At this point I am excited since I never seen the "MTP connected " on debug mode. I typed the "adb devices" command and got "List of devices attached" ___________________.
Yep, blank. Obviously the pc is not seeing it. My conclusions are the following:
1. Bad cable
2. Bad device
The fact that it recognized once on my room mates' pc and then none at all, and the fact that it was recognized on my pc for a brief random time, then it means that the device can't handshake with the motherboard and thus is a communication issue.
I'll try my luck with Samsung tech support and see if they can replace the cable.
Just thought of something, would installing Windows XP Mode under a Windows Virtual PC recognize new devices or just feed from the Windows 7 library?
Sal
Click to expand...
Click to collapse
Hmm, that is strange.. I was new to samsungs and when I tried to root it it took me a while because I didn't know that kies installed the drivers. After I installed it though adb devices showed my tab connected...
Sent from my HTC Glacier using Tapatalk

You still haven't tried Odin in download mode though.it could just be a bad flash
Sent from my GT-P6210 using xda premium

crunchie-uk said:
You still haven't tried Odin in download mode though.it could just be a bad flash
Sent from my GT-P6210 using xda premium
Click to expand...
Click to collapse
I placed the tab on download mode and queried it from adb and got nothing. I then queried it via ODIN3 and got no response as well.
I have come to terms that it has to be the device or the USB cable. Just ordered two (yes, two) different type cables to test out the theory. If they don't do it, then I am sending the tab back to Amazon.
It takes about a week to get stuff shipped where I am at so I'll check in later and report.
Sal

Just an update.
I bought a cheap cable from Amazon for $ 3.31 US to test the cable theory and guess what? It worked.
Curse you Samsung for your lack of QC with your cables. I have read throughout most of the forums (not just this one) and it seems that cables for these devices are notoriously finicky.
While on the one hand, I am glad that I got a cable that works, Samsung owes me over thirty hours of my life that I had to spend on troubleshooting a brand new device.
The part that I hate the most is that when I tried to contact Samsung's tech support, all they kept telling me is that it must be my pc even after I told them all the troubleshooting that I had done. Yes, they played the blame game.
My Toshiba Thrive worked right out of the box with a standard micro usb cable.
Ok. Rant off.
Sal

Glad to hear you got it working. Personally I have a ftp server set up on my comp that I use to transfer files back and forth. Much easier IMO than having a cable every time I need something transferred
Sent from my HTC Glacier using Tapatalk

[Q] Transformer USB Cable Issue

I've been searching for days for an answer to this and I can't find it. The biggest issue is that every time I plug my TF101 into my computer, I get Windows' wonderful "One of the USB devices attaching to this computer has malfunctioned" message. I get this using the OEM cable and brand new after-market cables. I've found a lot of different forums with similar problems but my symptoms list is different. Here's what's going on:
* The tablet charges just find through all of the cables despite not connecting properly through the computer.
* The dock (keyboard) works without issue and charges properly.
* Flash drives work properly in the USB ports on the dock.
* Android phone (Razr MAXX HD) recognizes that it's plugged into a device, the tablet briefly acknowledges a device (quarter of a second) but then stops reading the phone is plugged in.
* Maybe of note or maybe another issue, it doesn't want to connect to bluetooth devices, either. It recognizes them but refuses to connect.
* Everything is stock.
I've tried a hard reset and deleting every driver associated with the device properly installed and not. I don't have another computer to plug it into so I can't test that. I fear it may be a hardware issue but I don't want to resign to hardware issues but rather definitively know that the issue is a hardware issue.
Any thoughts?
Thanks,
- Robby

Linux emulated through VirtualBox, see if that detects it.

Thing O Doom said:
Linux emulated through VirtualBox, see if that detects it.
Click to expand...
Click to collapse
Tried it through VirtualBox with Ubuntu and another system (mine is Windows 7 Pro, the other system is Windows XP Pro). No dice on any of them.

My thoughts - bad USB cable.
You probably will say - BUT IT STILL CHARGES....
Yeah, mine does that too. But, one of the pins needed for computer connections is shorted. I used my cable 3 weeks ago to ADB, then last week nothing (trying to ADB to do the Ubuntu Touch resolution fix). Got a new OEM cable (and wall wart) from Office Depot, all better.

Virtualbox/ESXi/VMWare etc... I've had problems with all of them even in USB bridging mode. Nothing beats native.
Make sure the right drivers are installed; remove (not deinstall) completely the current ones as they may be corrupted and redownload ASUS Pad PC Suite from Asus' support site for your OS version, I believe it provides more recent Asus drivers (not 100% sure).

Also try the Universal 'naked' drivers for adb, I always have used those and they work flawlessly, and I included them in my peri tool because of this..

Here's where I'm at:
Don't have access to another OEM cable (hopefully fixing that in the next couple of days) so I can't test that. I did, however, install Ubuntu onto my system natively, plugged it in, and got zero response from the system using every cable that I have. I will buy that drivers may cause erratic behavior and such but not having the system recognize that a device was even plugged in makes me doubt the driver issue.
Thank you all for responses. I'll get another OEM cable and cross my fingers that solves the problem.

Just FYI, I know it's not convenient because it takes a month to get it, but I bought this cable and it works fine for data and charge. No need for an overpriced Asus branded one.

presbypenguin said:
I've been searching for days for an answer to this and I can't find it. The biggest issue is that every time I plug my TF101 into my computer, I get Windows' wonderful "One of the USB devices attaching to this computer has malfunctioned" message...
- Robby
Click to expand...
Click to collapse
I've run into this problem with another device on my PC. Turned out to be a double whammy: the USB port on the PC acted up; and the driver for that device was partly corrupt. Tried it on another USB port to find out. It's not always the cable.

graphdarnell said:
I've run into this problem with another device on my PC. Turned out to be a double whammy: the USB port on the PC acted up; and the driver for that device was partly corrupt. Tried it on another USB port to find out. It's not always the cable.
Click to expand...
Click to collapse
3 ports later I decided it wasn't a port issue (but I do appreciate the sentiment; I've been there with devices in the past).

Lethe6 said:
Just FYI, I know it's not convenient because it takes a month to get it, but I bought this cable and it works fine for data and charge. No need for an overpriced Asus branded one.
Click to expand...
Click to collapse
I'm gunna try it; the worst that happens is I have another charging cable when I (inevitably) lose the three that I have now :fingers-crossed:

presbypenguin said:
I'm gunna try it; the worst that happens is I have another charging cable when I (inevitably) lose the three that I have now :fingers-crossed:
Click to expand...
Click to collapse
I had the exact problem lol, I thought my cable went bad, I order another and threw that old cable away... damn what a bum, all it was was just the driver? Not sure, but when it does find the drivers and tried to install it, after installing the drivers knocked my wireless Ethernet off and disable too.

Still no dice
One, thanks everyone who has tried to help this out. I'm not tossing out "Thanks" yet because nothing has worked but I am thankful that people have tried.
Two, here's what I've done thus far that hasn't worked.
* Uninstalled and reinstalled (including fully deleting) every driver known to work with this device (including naked drivers). No dice.
* Uninstalled the driver while it was still plugged in and scanned for device changes. No dice (but this got me the closest; it "successfully" installed an "Unknown Device" and had me restart the computer).
* Used peri and hoped it would magically work after it installed the Naked drivers. No dice.
* Went through "[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" (no linking for me yet) hoping I missed something when I was installing. No dice.
* Installed Ubuntu and tried from the other operating system. No dice.
* Plugged into a Windows XP computer. No dice.
* Purchased the recommended cable. No dice.
* Prayed that it would work. No dice.
I'm stuck. I thought about sending it to Asus to have them repair it but I've not heard wonderful things about their repair service and I can't be without it for longer than a couple of days. It just frustrates me that Windows knows I've plugged something it but it simply refuses to recognize it, like it's taunting me into staring uselessly into a computer screen for hours without any solution (and hampering the work that actually means something to my life/career/marriage/etc.)
Any other thoughts? The only thing I haven't tried it is installing the drivers to plug it into my fiance's Mac to see if it will magically recognize it. I just wish I knew for sure it was a bad port on the bottom so I knew that I had to send it in to get fixed...
Thanks again!
- Robby

[Q] RT RECOVERY, NO recovery, NO USB BOOT

OK...First I have a surface RT.. It is a colleges tablet as I am a network admin at a telecom company..
I have never seen anything other than the surface logo with no "spinning wheel"
I have tried the 3 reboots, booting normally on the 4th...volume up and power for days .....the keyboard boot options (backspace, win key +everything, F8, F11 for the hell of it..) I tried holding down in different sequences every possible combination with power, volume up/down and the windows soft key (onthe tablet)
I have created USB's with a kingston 16GB, a sandisk 8GB, sandisk cruzer 16GB, a USB3 128GB, and a micro 32GB card in a USB adapter. I extrated 2 different zip files to them all after formatting fat32, using diskpart to make the part active. both oft these compressed files were from microsoft that I downloaded after registering the device.
I tried formatting the sticks with a USB format tool as opposed to win 8. I tried 2 other compressed recovery images I found elsewhere. Furthermore I I attempted 2 different ISO files and 2 different IMG fliles using rufus, usbit, and universal USB installer...both 8.0 and 8.1 recovery images/ISO's/ZIPS. At first I observed the access light on the USB Drives blink once right after booting but now no light at all...for the hell of it I even tried to connect it to a win 8.1 machine via 2 different USB-USB cables I had.
Please advise if there are any other options?? and do you want me to post the video of me smashing this POS in this thread?
thank you for your time...

Just to make sure, the bootable USB drives were GPT partition scheme formatted, right?

Go to a Microsoft store. Seems like a hardware defect if you cannot boot off of a USB stick.

Ok no expert here. I just bought a used SP2 I5-4300u and downloaded Ms recovery disk. One USB I made would not boot on the tablet.. another would only get to 70-80% quit. The last one just an old usb2 8g and it worked flawless.
I have a usb3 and it works on 3 computers at home.. it will NOT boot on this tablet where others will. So it might just be your usb nothing else.. maybe

Zeblade said:
Ok no expert here. I just bought a used SP2 I5-4300u and downloaded Ms recovery disk. One USB I made would not boot on the tablet.. another would only get to 70-80% quit. The last one just an old usb2 8g and it worked flawless.
I have a usb3 and it works on 3 computers at home.. it will NOT boot on this tablet where others will. So it might just be your usb nothing else.. maybe
Click to expand...
Click to collapse
Am in the same boat, although mine is the surface pro 2. wont boot from any usb device I have tested the usb stick on other surfaces and it boots those. when the surface is working it see the usb stick and allows me to select it to boot from but once it reboots it just skips the usb stick and boots the int hdd

Same Thing
coops82517 said:
Am in the same boat, although mine is the surface pro 2. wont boot from any usb device I have tested the usb stick on other surfaces and it boots those. when the surface is working it see the usb stick and allows me to select it to boot from but once it reboots it just skips the usb stick and boots the int hdd
Click to expand...
Click to collapse
I have a Surface RT running both 8 & 8.1 and it does the same as yours with the ignoring of the boot selection.
Has anyone found a fix to this yet?
-FU

Bootloader, secure boot violation?

USB file access from Windows 10

I'm posting cuz I've literally spent hours and hours searching, trying things, etc, and am stuck. I have several PQs with various CM/LineageOS ROMs. It is not a ROM issue because if I plug via USB into my desktop pc running win 10, they all work as I want. Presumably, it's a driver issue or something related to my specific laptop - I recently bought an old used laptop, originally shipped with win7. After purchase I immediately removed all partitions and installed win10 from disc (fyi, you can d/l win10 iso from microsoft and use win7 oem key to legally install fresh win10, even now the free upgrade stuff is over - that surprised me).
I cannot, no matter what I do, get file access via usb to my phone. I've tried lotsa things. I don't remember if/what I had to do to make my win10 desktop see them - maybe it was automatic, i dont remember, if it wasnt, I easily downloaded/installed what was necessary - but nothing I've tried makes my win10 laptop load the drivers, although it does detect something when I plug it in, and something else when I select MTP on the phone (vs charge). But just exclamation points in device manager and nothing in explorer. Among other things, I've tried MotorolaDeviceManager_2.5.4
It's especially annoying as I have a video on my phone I wanted to send out tonite and can't, spent another couple hours trying. Bluetooth works fine for pictures but freezes at 10% for video, no idea why. But I'd much rather just use a cable than figure out any wireless BS.
Incase it's something specific to this laptop and someone is curious, it's a Sony VPCF115FM. That 'base system device' and "unknown device" are always "!", MTP with "!" only appears when phone plugged in.

Yea definitely a driver issue. When you plug the PQ into your desktop (which seems to work) what shows up in device manager?
Have you tried to right click on the devices with yellow exclamation points and update the driver from Windows update?

I never followed up on this, but still haven't found a solution, and kinda forgot about it. It does work in PTP mode. And works for a newer Moto (Lenovo) phone on this laptop. Yes, I tried the windows 10 device manager update auto search thing (in fact, just tried it again minutes ago before I read this). I'm about to wipe and install fresh as this phone is running crazy slow lately and wanted to copy everything off before I wipe which is what reminded me of this issue - funny thing is that a google search of this problem ("mtp driver motorola photon q windows 10") found this thread as the third search result and I completely forgot I posted it. I vaguely recall I read your reply but was waiting to see if anyone else responded and then just forgot to follow up when it wasn't on my new list...

PROBLEM SOLVED! It happened in TWRP too and sideload was failing (for another reason) but made me try to figure out MTP again.
Found solution here for anyone with similar issue:
https://answers.microsoft.com/en-us...0-solved/d2226a54-65db-41ba-9398-a12196cc279c
Gotta update driver and manually select "MTP USB" from list of devices, in my case I found it under portable devices.