USB file access from Windows 10 - Motorola Photon Q 4G LTE

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.

Related

LG Incite CT810 - Problem with USB

So I got my shiny new LG Incite at Best Buy yesterday. I knew I was getting it a while ago, so I downloaded a bunch of games and apps to load it up with as soon as possible. I get home from the store, play around with it and let it charge for a while, then I try to connect it to my computer (After installing ActiveSync 4.5 from the included disk, as well as both of the USB drivers on the disk). Windows comes up with that "found new hardware" stuff and asks where to look for the driver to install. I tell it to look on the CD, as well as the directories where the USB drivers from the disk were installed. It looks like it's working at first, but then I get this error:
(Error: "The data is invalid.")
Then it gives me the message balloon about how there was an error during installation and my new hardware may not work properly, etc. Now when I go to Device Manager, a number of things showed up with that little yellow exclamation point that I'm pretty sure were not there before, but I could be wrong:
- IEEE 1394 Bus host controllers: VIA OHCI Compliant IEEE 1394 Host Controller
- Network Adapters: Unknown device, WAN miniport (L2TP), WAN miniport (Network Monitor), and Windows Mobile-based Device
- Ports (COM & LPT): Communications Port (COM1)
So I tried reinstalling the drivers from a link I found in a thread on these boards (after clicking uninstall for "Windows Mobile-based Device" and having it tell me that the device is necessary to boot up the computer), but the same thing keeps happening. I also tried having ActiveSync scan for devices, but it never finds anything (Just says that USB is "available").
Please help, I really want to start putting pictures, music, and all that good stuff on my brand new phone
(btw, I'm pretty sure the problem is with the software/drivers on the computer, because when I plug in the USB cable the phone starts to charge. Other than that, nothing happens on the phone.)
If at all possible, I would try using the phone with another computer. For quite some time I was only able to sync data with my laptop and not my desktop, so I knew it was a software issue and not the phone itself.
would say it's down to
dead activesync install and no uninstalling it is not enough one have
to remove all traces of it in registry too
and it could also be an issue with usb drviers for the motherboard
chad.pflughaupt said:
If at all possible, I would try using the phone with another computer. For quite some time I was only able to sync data with my laptop and not my desktop, so I knew it was a software issue and not the phone itself.
Click to expand...
Click to collapse
Well, I'm not going to have another computer until September at least, so I really want to get it working on this computer, but I guess I could test it out on a friend's pc to see if my computer is the problem.
Rudegar said:
would say it's down to
dead activesync install and no uninstalling it is not enough one have
to remove all traces of it in registry too
and it could also be an issue with usb drviers for the motherboard
Click to expand...
Click to collapse
Know of any links or tutorials that would tell me all of the registry entries I'd have to remove?
(Sorry for the double post, but no one was replying...)
So I found my bluetooth adapter for my PC, and after I installed the proper software I could connect to my phone no problem. After that, I just used the bluetooth adapter's software to transfer files to my phone via FTP. (ActiveSync still just sat there, even when I set my phone to sync with bluetooth instead of USB, and I allowed wireless connections in ActiveSync)
So I'm glad I can finally transfer files, but I still want to get USB working. No one has any ideas at all?
(Triple post... sorry)
Ok, something happened to the bluetooth drivers and software now. I turned my computer off for the night after using bluetooth to transfer files to my phone, but when I turned on my pc today and clicked the shortcut to start the bluetooth software, I got a message saying that the program the shortcut was linking to no longer existed. Sure enough, the folder was gone from my Program Files directory. Now, every time I try to reinstall it, I get an error 183 that installation was interrupted.
So now I'm back to having no means of transferring files to my phone.
Please, any suggestions at all will be helpful to me at this point. I'm at my wits end!
Any progress on this?
I have a similar problem. I think usb sync worked on my laptop at one point, but hasn't for at least a week.
I was able to fix the problem at least temporarily by disconnecting the device, deleting it from ActiveSync and reconnecting. ActiveSync happily added it back and resynced everything. Now I can install the new Xcite ROM.
Still nothing...
Now my computer doesn't do anything at all when I plug my phone in, not even make a noise or ask about drivers. My phone, however, still recognizes that it's plugged in.
At least I got bluetooth working again, but still, USB would be nice.
It's hard to believe that out of every member on this forum, no one has even the slightest idea of where to start...
Menu - settings - connections - USB to PC.
Uncheck Enable advanced ...
OK TO ALL AND READY

[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] Trouble connecting Nexus 5 to new laptop in MTP mode

Not sure how many would read such a long post for a question, but here goes...
Any help is appreciated!!
1. Problem
In short, I plugged in my Nexus 5 to my laptop in MTP mode, it does not show up in "My Computer".
I just wanted to transfer files to my phone via USB, not even using ADB yet.
I have yet to solve the problem after googling around for a bit.
Relevant XDA threads that I remember reading are this, this, this, this and this.
I have tried numerous combinations of (un)plugging my phone / (un)installing drivers / rebooting my laptop and phone / switching usb ports / turning USB debugging on and off / connect in PTP mode / ...
As a workaround, I am now transferring files using the AirDroid app, which is really convenient with acceptable speed.
Still, it would be nice to know why the problem occurred and see if others have similar problem.
Below I will describe the devices I have on hand and more details on the failures I have encountered will follow.
2. My Devices
A. an old Galaxy Note
B. the new Nexus 5 with the stock micro USB cord
C. new laptop
- 64-bit Windows 8 Pro (not upgraded to 8.1 yet)
- only USB 3.0 ports
D. old laptop
- 32-bit Windows XP Home
- only USB 2.0 ports
3. Details
Scenario A. Nexus 5 not showing up in "My Computer"
Naturally, the first thing I tried is to simply plug my Nexus 5 in to my new laptop. I was used to Android devices working just like that!
However, my Nexus 5 does not show up in "My Computer" after a loooong wait.
On a closer look, my Nexus 5 (only) appears in the "Device Manager" under "Portable Devices" as "MTP USB Device".
It shows my device to be "working properly". However, I cannot uninstall/disable it when my phone is plugged in (normal?)
Frustrated, I decided to unplug my phone. I have the option to "Unplug Nexus 5" under "Safely Remove Hardware", but the operation always times out, so I simply unplugged it.
Then I tried with my Note using the same cable. It works flawlessly either in MTP mode or Mass Storage mode.
Scenario B. Nexus 5 shows up, but is really sloooooooooooooow
At some point, I turned on USB debugging.
With USB debugging on, my phone appears under "Portable Devices" as "Nexus 5" (and in some other places according to what drivers I have installed).
I was quite pleased for a few seconds as my Nexus 5 now shows up in "My Computer"!
However, it took a few minutes to list the folders I have under my phone's internal storage.
Attempting to copy a 12MB file to it gives an estimated time of over 2 hours.
Scenario C. Success?
After tinkering with it for some time to no avail, I was beginning to worry if I have gotten a defective hardware.
Then I remembered I had an old laptop stashed somewhere, so I tried connecting my Nexus 5 to that.
And... voila! It works without a hitch (MTP mode, USB debugging off).
A maybe useful note is that I have used both the old and new laptops to transfer files to my Note before.
4. Possible causes
While many seems to have solved the issue by simply unplugging and letting Windows reinstall the drivers, I have no such luck.
I sincerely hope that it is not due to any hardware defects since
a) my Note can talk to my new laptop through the same micro USB with no problems, and
b) my Nexus 5 can talk to my old laptop.
I feel that this is a driver-related issue but I am not sure.
Is it possible that there are compatibility issues with using USB 3.0 port (which should be backward compatible...) or a 64-bit Win 8 Pro?
Any help is appreciated!
It is so strange..
I just bought a USB 2.0 hub and connected my phone to my new laptop through it.
Guess what... it works perfectly!
Apparently my problem was that my new laptop only had USB 3.0 ports for me to test on?
Doesn't make sense... thought 3.0 is backward compatible and my old Note works on it!
Maybe I'm missing something but I'm happy it is solved for me now
This solution worked for me. Go to http://forum.xda-developers.com/showthread.php?t=2512549 and see post #5. Be sure to thank n7of9 for the link and WugFresh for his toolkit solution. Enjoy.
Hey,
I basically seem to have the same problem as you do.
My laptop also only has USB 3.0 ports and Windows 8.1 Pro 64-bit installed.
The Nexus 5 doesn't get installed, in MTP mode it is just shown with the yellow exclamation mark in Device Manager. Downloading different USB drivers including Google's and trying to manually install it doesn't work at all. I specifically checked that all older similar drivers are gone, so I doubt that older Android devices could be interfering.
On the other hand, as you noted, using an older computer with USB 2.0 works perfectly, I had the same result.
To be honest, I'm not much of a developer or Android tinkerer, so I'm not really making any progreess... In the end, I think I will follow your example and test it with a USB 2.0 adapter.
Did you manage to get it to work without this workaround?
Kind regards! :fingers-crossed:
I'm using Linux Mint. Just plug the Nexus in. It shows up as a folder. No hassle
Sent from my Nexus 5
SabinSnorlax said:
Hey,
I basically seem to have the same problem as you do.
My laptop also only has USB 3.0 ports and Windows 8.1 Pro 64-bit installed.
The Nexus 5 doesn't get installed, in MTP mode it is just shown with the yellow exclamation mark in Device Manager. Downloading different USB drivers including Google's and trying to manually install it doesn't work at all. I specifically checked that all older similar drivers are gone, so I doubt that older Android devices could be interfering.
On the other hand, as you noted, using an older computer with USB 2.0 works perfectly, I had the same result.
To be honest, I'm not much of a developer or Android tinkerer, so I'm not really making any progreess... In the end, I think I will follow your example and test it with a USB 2.0 adapter.
Did you manage to get it to work without this workaround?
Kind regards! :fingers-crossed:
Click to expand...
Click to collapse
I had a lot of issues with my S3 and my work computer (windows XP SP3) and it was because I had half installed some USB driver that windows tried installing.
I fixed the problem in device manager by manually uninstalling EVERY SINGLE USB DEVICE attached to the computer while I had my phone plugged in.
Word of caution: You'll probably uninstall your mouse/keyboard doing this.
Once everything was uninstalled I reinstalled the Samsung drivers and it worked fine.
The same computer only required me to install the Google drivers for my N5. If I enable USB debugging, I all of a sudden can't install MTP drivers, but USB debugging disabled works fine.
USB & MTP mode
I have the same problem with my Nexus 5. The only workaround to transfer files to my phone from a computer via USB cable is to enable USB debuging, set the phone to PTP mode instead of MTP and then it shows in My Computer as a camera. I can only access the DCIM and Pictures folders but for now I have to settle for this...I copy all the files I need to let's say Pictures and then using a file explorer (on the phone) I cut and paste them to the folders I wish...e.g. movies to Movies, music to Music and so on...
I had same problem. Developer Mode...USB Debugging ON worked.
I have this problem too, but I got it to work using a galaxy s3 cable. for some reasons the cable that came with N5 did not work.
Its usually just missing drivers.. You can get them straight from Google or a toolkit as mentioned! (P.s you need to download a little applet like thing from Google if you want to hook up your Mac to your n5)
See andoid.com/filetransfer for the drivers.
This worked for me when all else failed: http://forum.xda-developers.com/showpost.php?p=35854664&postcount=7
Hope that helps!
The problem I am having now connecting is that my phone got wet recently. I dried it immediately and used dessicant to withrow the water and now it works (sort of). Now when I plug my phone into my pc, the usb debugging icon doesn't even show up.
I tried connecting to both my work pc and home laptop and they both say the same thing, that the usb device has malfunstioned and that windows doesn't recognize it.
Is it time for a new phone?
islandboy_2000 said:
The problem I am having now connecting is that my phone got wet recently. I dried it immediately and used dessicant to withrow the water and now it works (sort of). Now when I plug my phone into my pc, the usb debugging icon doesn't even show up.
I tried connecting to both my work pc and home laptop and they both say the same thing, that the usb device has malfunstioned and that windows doesn't recognize it.
Is it time for a new phone?
Click to expand...
Click to collapse
Sounds like the usb is shorting. How long did you let it dry. Give it more time and try it again.
jd1639 said:
Sounds like the usb is shorting. How long did you let it dry. Give it more time and try it again.
Click to expand...
Click to collapse
Yeah maybe thats what happened. It's been drying now for about a week. The screen was the major problem at first but has since dried there mostly.
Hopefully it will come back. Would suck to have to buy a new phone because of that.
Thanks. :good:
MTP connecting problem solved
Going back to the subject of the thread: I am pretty sure that ADB drivers and SDK (I am confident that a lot of nexus users have their devices rooted and that means they must have the above installed) is what is causing some sort of conflict when trying to connect the Nexus 5 as MTP. After I reinstalled the windows (W8) on my computer and connected my Nexus 5 it took @1-2 minutes to auto install the drivers and then worked fine...I have no ideea what happens if I install ADB and SDK again...
ASepi said:
Going back to the subject of the thread: I am pretty sure that ADB drivers and SDK (I am confident that a lot of nexus users have their devices rooted and that means they must have the above installed) is what is causing some sort of conflict when trying to connect the Nexus 5 as MTP. After I reinstalled the windows (W8) on my computer and connected my Nexus 5 it took @1-2 minutes to auto install the drivers and then worked fine...I have no ideea what happens if I install ADB and SDK again...
Click to expand...
Click to collapse
If you tell the SDK not to install the drivers it'll be fine
The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!
njoy
Resolved. nexus 5 PC Connectivity
hackdisk said:
Not sure how many would read such a long post for a question, but here goes...
Any help is appreciated!!
1. Problem
In short, I plugged in my Nexus 5 to my laptop in MTP mode, it does not show up in "My Computer".
I just wanted to transfer files to my phone via USB, not even using ADB yet.
I have yet to solve the problem after googling around for a bit.
Relevant XDA threads that I remember reading are this, this, this, this and this.
I have tried numerous combinations of (un)plugging my phone / (un)installing drivers / rebooting my laptop and phone / switching usb ports / turning USB debugging on and off / connect in PTP mode / ...
As a workaround, I am now transferring files using the AirDroid app, which is really convenient with acceptable speed.
Still, it would be nice to know why the problem occurred and see if others have similar problem.
Below I will describe the devices I have on hand and more details on the failures I have encountered will follow.
2. My Devices
A. an old Galaxy Note
B. the new Nexus 5 with the stock micro USB cord
C. new laptop
- 64-bit Windows 8 Pro (not upgraded to 8.1 yet)
- only USB 3.0 ports
D. old laptop
- 32-bit Windows XP Home
- only USB 2.0 ports
3. Details
Scenario A. Nexus 5 not showing up in "My Computer"
Naturally, the first thing I tried is to simply plug my Nexus 5 in to my new laptop. I was used to Android devices working just like that!
However, my Nexus 5 does not show up in "My Computer" after a loooong wait.
On a closer look, my Nexus 5 (only) appears in the "Device Manager" under "Portable Devices" as "MTP USB Device".
It shows my device to be "working properly". However, I cannot uninstall/disable it when my phone is plugged in (normal?)
Frustrated, I decided to unplug my phone. I have the option to "Unplug Nexus 5" under "Safely Remove Hardware", but the operation always times out, so I simply unplugged it.
Then I tried with my Note using the same cable. It works flawlessly either in MTP mode or Mass Storage mode.
Scenario B. Nexus 5 shows up, but is really sloooooooooooooow
At some point, I turned on USB debugging.
With USB debugging on, my phone appears under "Portable Devices" as "Nexus 5" (and in some other places according to what drivers I have installed).
I was quite pleased for a few seconds as my Nexus 5 now shows up in "My Computer"!
However, it took a few minutes to list the folders I have under my phone's internal storage.
Attempting to copy a 12MB file to it gives an estimated time of over 2 hours.
Scenario C. Success?
After tinkering with it for some time to no avail, I was beginning to worry if I have gotten a defective hardware.
Then I remembered I had an old laptop stashed somewhere, so I tried connecting my Nexus 5 to that.
And... voila! It works without a hitch (MTP mode, USB debugging off).
A maybe useful note is that I have used both the old and new laptops to transfer files to my Note before.
4. Possible causes
While many seems to have solved the issue by simply unplugging and letting Windows reinstall the drivers, I have no such luck.
I sincerely hope that it is not due to any hardware defects since
a) my Note can talk to my new laptop through the same micro USB with no problems, and
b) my Nexus 5 can talk to my old laptop.
I feel that this is a driver-related issue but I am not sure.
Is it possible that there are compatibility issues with using USB 3.0 port (which should be backward compatible...) or a 64-bit Win 8 Pro?
Any help is appreciated!
Click to expand...
Click to collapse
Hello !!!
I faced the same problem with mine...
Couldn't connect my phone with my laptop.
It installs the driver but not displaying the folder in my computer.
I uninstalled the Existing samsung driver in control panel.
Then the issue has been solved,
Or uninstall previous mobile's drivers
Try this!?!
Search for Universal Driver here in XDA. Had the same problem most of you are having. First try and BAM! Works like a champ...
NEXUS 5
Problem solved for me
I have no more issues what-so-ever after I unninstalled ADB & SKD drivers...Windows(8) installed my phone by itself after a restart and it works as it should in MTP mode and PTP mode.

[Q] Nexus/Android with Win 8 is a pathetic story

Hello
:crying:
I got my N5 today, and like my wife's N7 and my N10, NONE of them will show up on windows explorer (windows 8.1)
I can unlock, root, install custom recovery, all good, but as far as actually SEEING my device on the computer so I can drag and drop stuff, well, I literally have been spending almost a day trying to sort that out and have not got any closer at all. It is really pathetic.
I've changed the windows Unsigned drivers thing (though the drivers must be ok if I can do all that other rooting etc)
But yet when I uninstall the drivers to try installing them again, win8 says "Android ADB Interface. The third party INF does not contain digital signature information"
But I'm pretty sure that when I reinstall them AGAIN, I will still nto be able to see any of my Nexus devices on Windows explorer... despite them showing up in the Windows Notification under USB, and they are mounted there... I can UNmount them!
Something is way off kilter here, its with 3/3 devices, perhaps win8.1 is completly Android unfriendly, or?
Advice/help MUCH appreciated for someone who is going nuts here.
tx
Mark.
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Hello guys,
lowandbehold said:
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Click to expand...
Click to collapse
I did turn it iff to ADB but do not see where I would turn it back on, but that may be it with my N5...
EddyOS said:
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
Click to expand...
Click to collapse
I really dont know. I have 4 PC's in the house, and sometimes my old dell laptop (also 8.1) seems to be the most reliably connect-able.
hotleadsingerguy said:
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Click to expand...
Click to collapse
There has to be a physical reason for it (unless we are to consider the metaphysical - past lives, re-incarnation of gadgets, Steve Jobs curses and stuff...) and it does amaze me that it still seems so hit and miss. When I first got onto android a few years back, you just plugged your phone into USB, ANY ONE ON ANY COMPUTER and whammo, you'd get both Ext SD adn Int SD mounted... reliably. I'm sure that was causing security and stability issues so all manufacturers seem to have snuffed that out.
so that MTP toggle is at settings > Storage > settings in storage
but it makes no difference still not vis in WinExplorer
Cheers
Mark.
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
lowandbehold said:
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
Click to expand...
Click to collapse
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
fredphoesh said:
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
Click to expand...
Click to collapse
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
ZeroAlphawolf said:
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
I must say, I did leave that part out of my replies. I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Enable USB debugging in developer options.
Sent from my Nexus 7 using Tapatalk
Nexus Root Toolkit includes a variety of USB drivers you can try, as well as a few utilities to help you diagnose and fix android driver problems. That's where I would start. You don't need to use it to root or anything (unless you want to) but the driver utilities in the toolkit have fixed a number of problems I've had with android drivers over the years. I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Not really the same at all but I had a hard time getting my S3 to be recognized on my computer at work running XP.
In the end the problem was the generic USB drivers that were installed had to be manually removed; even the official Samsung drivers wouldn't overwrite them. After a bit of digging and prodding I got it to work.
My Nexus was recognized without issue on my Win 8 machine.
You'll have to try a variety of different drivers to get it to show up properly. My N4 and Note 3 had no issues showing up, but the N5 wouldn't. I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
This happens to me every single time with a new device so I know exactly what to do now. It's not a driver issue, it's a problem with windows 8 and how it searches for drivers.
If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Another problem I had was remembering to accept the ADB on my phones end, I never had to do that with my HTC one, so when going through rooting the raw drivers were likely unnecessary, I just hadn't noticed the primly on my phone when the first drivers I installed worked.
Hello guys, thanks for the various responses...
ZeroAlphawolf said:
Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers
--------also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
lowandbehold said:
I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Click to expand...
Click to collapse
I did initially install the raw drivers as they sounded like they would be best... will try the camera toggle and MTP toggle
rabidfurball said:
I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Click to expand...
Click to collapse
Encouraging!!! I know from my SGS3 and 4 and some generic chinese tablets ive had that the driver installation can be a major PITA but eventually you do the same thing for the 5th time, and it works, with no (seemingly) logical reason.
Stories said:
I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
Click to expand...
Click to collapse
I did a fresh install of windows 8.1 just yesterday... so it was pretty clean!
KiNG OMaR said:
It's not a driver issue, it's a problem with windows 8 and how it searches for drivers. If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Click to expand...
Click to collapse
Yeah, i have tried that and it says I have the best drivers already installed. Oddly I can use Nexus Root Toolkit fine, so there has to be something right about the drivers... just not the part that shows up on a computer.
I'm convinced there HAS to be some scientific way of doing this, its such a common problem, it would be great to really figure it out. The problem is, one has to try 100 things before it works, so it becomes almost impossible to know which actions to attribute as the solution!
tx again,
Mark.
a solution - possibly useful...
Hello guys
Following Wugfresh's instructions to the T...
I tried drivers Option 1, (Universal) and the result was exactly as with the Raw (Option 4) drivers... So I uninstalled the drivers, ran ran USBDeview and uninstalled 7 devices like "Google Nexus ADB Interface" and "USB Composite device" and "Nexus 10".
Then tried Option 2.
The installation did not go exactly according to Wugfresh visual guide, so I cant be certain, but I do know that installingPDANET drivers only work if you select MTP, otherwise it will not find the tablet/phone.
After the instalation, the app called PDANET installed on computer, not on my tablet. My PC showed a pop up notification when tablet USB debugging is turned on, but again, it was not visible in windows explorer.
I then was going to try Option 4 again, and Uninstalled drivers in device manager WHILE I STILL HAD THE TABLET STILL PLUGGED IN, so I am guessing though PDANET uninstalled, the drivers remained (which I think is what Wugfresh's process would have done if it had run according to plan. I ran USBDeview and uninstalled the same 7 devices.
Then
Plugged tablet back in to attempt Raw drivers, but all of a sudden, the device was recognised and for the first time visible fully in Internet Explorer!
So basically it seemed to be the PDANET drivers that worked, though I have no idea if that would have worked had I tried these drivers in the first place.
I hope that helps someone!
Cheers
Mark.
OP, are you running W8.1 64 bits or 32 bits ??
I had my Sony Viao running W8 64 bits & hated it, downgraded to W7 64 bits and it's very happy getting along with Nexus 7 - going to play with N5 later on. Good old Dell Latitude is running W7 32 bits and it's my main machine to unlock, root & flash and so far so good - yet, I was reading about someone running Vista and had issues with the usb drivers.
I have 2 fully licensed W8 safely tucked away and the way it's looking, I might never get out of W7 - let alone then upgrading to 8.1 for free - getting reminders from $S a few things already.
Most of the time, the mess are caused by conflicting drivers installed & loaded - I keep a clean & lean desktop to do these bench work, and even though it is a PITA, starting clean with minimal programs (and apps) installed is often a good start - turn off antivirus & firewall, especially if connectivity is not needed - enabled access only if it is required and/or necessary.
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Hello guys
Letitride said:
OP, are you running W8.1 64 bits or 32 bits ??
Most of the time, the mess are caused by conflicting drivers installed & loaded
Click to expand...
Click to collapse
64 on the two PC's in the same room, HTPC's and laptop are 32 I think, but I have not tried them. I did a fresh Win 8.1 install on Tuesday and had no drivers from any devices other than the ones I manually installed with Wug.
KiNG OMaR said:
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Click to expand...
Click to collapse
Yeah, well try the PDANET (worked for me, though was my last resort as I don't like to install stuff that is a/ meant for something else, b/has some software I dont need that comes with it... but I did manage to keep the drivers and UNinstall PDANET software by keeping the tablet plugged in when I uninstalled PDANET... try it.
tx
Mark.

Oneplus One is not recognised at all by Windows 10

I've been having this problem for a long time, can't remember how much exactly. No matter what I've tried, I haven't managed to get my computer recognize my opo. I am still running Cyanogen 13.0, as it was the latest OTA update I got.
When I connect it via usb, absolutely nothing happens (I've also tried two cables). I have the device manager open and it doesn't even flash as it used when I had similar problems, which means that the device is not recognized at all. Therefore, I cannot find/update/remove the drivers anyhow.
Developer options on my phone have a bunch of things but none seems relevant, apart from open/close Android debugging (adb) and select USB Configuration (Charging/MTP/PTP etc). I've tried several options, nothing seems to change.
I've also installed some Windows MTP drivers (see here) which were supposedly solving the issue caused by a Windows 10 update, but no luck (which could have been the issue, but can't be sure-I can't remember the last time I was able to browse my phone's memory).
Any ideas?
tony.crete said:
I've been having this problem for a long time, can't remember how much exactly. No matter what I've tried, I haven't managed to get my computer recognize my opo. I am still running Cyanogen 13.0, as it was the latest OTA update I got.
When I connect it via usb, absolutely nothing happens (I've also tried two cables). I have the device manager open and it doesn't even flash as it used when I had similar problems, which means that the device is not recognized at all. Therefore, I cannot find/update/remove the drivers anyhow.
Developer options on my phone have a bunch of things but none seems relevant, apart from open/close Android debugging (adb) and select USB Configuration (Charging/MTP/PTP etc). I've tried several options, nothing seems to change.
I've also installed some Windows MTP drivers (see here) which were supposedly solving the issue caused by a Windows 10 update, but no luck (which could have been the issue, but can't be sure-I can't remember the last time I was able to browse my phone's memory).
Any ideas?
Click to expand...
Click to collapse
If win10 causing that much issues,why don't dual boot win7 alongside?
Edit- I personally use Win8.1 Pro and it works fine without any issues.
I've been running Windows 10 insider builds for a while and run Into the same issue at some point, I'm not sure on which build you are currently on, I've reported that on the insider HUB but got no reply. I found a "solution" which is selecting PTP in the options and the phone will be mounted as a media device and you'll be able to access DCMI folder and pass files. It doesnt mount always, but you need to try some extra times.
Another workaround is to use an USB drive and the use an OTG cable.
Apparently, it was just the cables' fault. I didn't figure it out immediately, as I had two faulty cables instead of one, but after all I came over a working one and the opo was recognized and mounted as usual.
Thanks anyway
tony.crete said:
Apparently, it was just the cables' fault. I didn't figure it out immediately, as I had two faulty cables instead of one, but after all I came over a working one and the opo was recognized and mounted as usual.
Thanks anyway
Click to expand...
Click to collapse
Cheers!
tony.crete said:
Apparently, it was just the cables' fault. I didn't figure it out immediately, as I had two faulty cables instead of one, but after all I came over a working one and the opo was recognized and mounted as usual.
Thanks anyway
Click to expand...
Click to collapse
I wish I had the same issue ?

Categories

Resources