Related
When I connect my Nexus 7 to my Windows XP (SP3) PC via USB, it's obvious the computer recognizes it and it tries to install ADB drivers. Whether I choose to install those drivers or not, I still can't locate my device in the Windows Explorer Tree. I checked Disk Management for the hell of it and nothing but my PC's harddrives were there. There's an attempt to install drivers for "MTP" but that fails and I'm pretty sure that's the cause; however, I'm unable to replicate it, even as I uninstall/reinstall applicable drivers from the device manager the MTP failure never happens anymore. I did some googling and found a thread with someone who had a similiar experience. In turn, I downloaded https://www.box.com/s/2c25e8bc42ecce400afd to try a different set of drivers. Same problem. Driver install is fine for ADB, but still unable to see my device in Windows Explorer. I'm able to successfully connect the device to the PC with PTP for the camera. I can access DCIM and cache which can serve as a work around, but I'm hoping you can provide any ideas you might have. Thank you!
edit - ***resolution***: Ok, I figured it out...I had to disable USB debugging. I don't know if this helped either, but I installed these drivers as an alternative to the drivers that were originally installed: https://www.box.com/s/2c25e8bc42ecce400afd
While connected to PC, I switched to PTP mode because I was about to give up and just use that
I then disabled usb debugging and switched back to MTP at which point the drivers successfully installed and I could now view my device in Windows Explorer. I also believe downloading the drivers in the link above helped since the first crack I took at this was unsuccessful with existing drivers.
install pdanet on pc and it will install drivers for u so it will be recognized
Ok, I figured it out...I had to disable USB debugging. I don't know if this helped either, but I installed these drivers as an alternative to the drivers that were originally installed: https://www.box.com/s/2c25e8bc42ecce400afd
Been battling with this on my XP machine since yesterday. I couldn't even get debugging to work until I installed NakedDriver. And even still, there seems to be no way to get MTP to work without turning debugging off. On my Win7 machine everything worked perfectly, both ADB and MTP, right out of the box. I have the Galaxy Nexus drivers installed on both machines (which I've read are compatible with the N7). I also have the latest version of Windows Media Player (I've read that some older versions have issues with MTP). Is anyone else able to run ADB and MTP on XP?
*edit*
A: Does PDAnet let you use MTP and ADB simultaneously? Because I really don't want to install it if I don't have to. I got rid of it ages ago (too many things starting up at boot time).
B: I have a Galaxy Nexus also, and I have no issues on the XP box.
I wouldn't bother with MTP, it's not always showing the contents of the internal storage properly when viewed in Windows Explorer.
Earlier today when I was trying to set up a backup profile for it, it didn't copy all the files off. On closer inspection I found folders like TitaniumBackup to be completely empty, which is not true according to ES File Explorer on the tablet.
I tried connecting MTP again, with USB Debugging on and off but this made no difference. Also I'm only seeing the Notifications folder instead of 36 folders on the internal storage now, really random how it's working.
asus site now has a usb driver for N7
try that
Nordendorf said:
asus site now has a usb driver for N7
try that
Click to expand...
Click to collapse
Updated with ASUS drivers, still doesn't view internal storage fully.
Salty Wagyu said:
Updated with ASUS drivers, still doesn't view internal storage fully.
Click to expand...
Click to collapse
Same here. No change with the Asus drivers. Still can't use MTP when ADB is turned on.
poo. how do I transfer my audiobooks to this stupid device without working drivers?
1. Please disconnect Nexus7
2. Remove drivers on PC.
3. Toggle ON : Settings->Wireless&Networkings->More->NFC.
4. Re-connect device
Good luck !
GotLoveForAll said:
poo. how do I transfer my audiobooks to this stupid device without working drivers?
Click to expand...
Click to collapse
1. Uncheck MTP, check the one next to it (Camera)
2. Unplug USB
3. Turn off USB Debugging (Uncheck it)
4. Plug in USB
5. Should say connected as camera, then a new window will pop-up allowing you to see your files.
Tell me if it works!
im having trouble too, is there any way to make the device to be recognised as a flash drive?
Internal memory partly invisible from Windows 7 Explorer
Salty Wagyu said:
I wouldn't bother with MTP, it's not always showing the contents of the internal storage properly when viewed in Windows Explorer.
Earlier today when I was trying to set up a backup profile for it, it didn't copy all the files off. On closer inspection I found folders like TitaniumBackup to be completely empty, which is not true according to ES File Explorer on the tablet.
I tried connecting MTP again, with USB Debugging on and off but this made no difference. Also I'm only seeing the Notifications folder instead of 36 folders on the internal storage now, really random how it's working.
Click to expand...
Click to collapse
Same observation here (a few months later) on stock Android 4.1.1 rooted.
It seems that new files in the internal memory remain invisible for a long time, but so far they have become visible eventually, sometimes a day or two later. I have no clue what could possibly cause this, and I have not found any trick or workaround that makes them visible, not even rebooting. Any hint is welcome.
SE4GT said:
1. Uncheck MTP, check the one next to it (Camera)
2. Unplug USB
3. Turn off USB Debugging (Uncheck it)
4. Plug in USB
5. Should say connected as camera, then a new window will pop-up allowing you to see your files.
Tell me if it works!
Click to expand...
Click to collapse
Didn't work. Just shows up as a camera with the limited folder access one would expect.
Workaround
I now use the following workaround.
Install SDrescan from Google Play.
Run it.
If you already had your phone connected to a computer as a media device (MTP) and are watching the contents of your SD card or internal memory in Windows Explorer, press F5 to refresh your view. If not, connect it now.
I'd be curious whether this works for you as well. If it does, press the THANKS button below.
Same issue with an old ibm x40 udated to windows xp pro SP3.
I've installed mtp driver, without success
I've "tried" to install asus driver, without success
I've tried to do as above with the help of the nexus toolkit, without success.
Everytime, the laptop recognize the device as android ADB interface.
Someone could help me?
Thank you in advance
mistershark said:
Everytime, the laptop recognize the device as android ADB interface.
Click to expand...
Click to collapse
Disable USB debugging in your phone.
Same problem with my moto xoom...files not showing in MTP using windows xp...still have not found any solution
hgmichna said:
Disable USB debugging in your phone.
Click to expand...
Click to collapse
+1 have to toggle USB debugging in winXP
hgmichna said:
I now use the following workaround.
Install SDrescan from Google Play.
Run it.
If you already had your phone connected to a computer as a media device (MTP) and are watching the contents of your SD card or internal memory in Windows Explorer, press F5 to refresh your view. If not, connect it now.
I'd be curious whether this works for you as well. If it does, press the THANKS button below.
Click to expand...
Click to collapse
It works! THANKS A LOT!!!
I just turned my nexus 7 32GB on and connected it to the same cable as the 16GB I just returned. It doesn't show up on my computer at all in MTP mode. Only in PTP mode. Any ideas on what to try?
*EDIT*
USB debugging is not on. Tried to install the asus drivers and got an error about there not being a driver for 64-bit in them, despite seeing the x64 drivers in the package.
Also, as MTP, my nexus 7 shows up as VID_18D1&PID_4E41&REV_9999
Again, that's with USB debugging disabled, it shows up only as an ADB device.
*RESOLUTION*
I uninstalled the ADB driver while it was plugged in with MTP mode. I unplugged it and replugged it and now it works fine.
is usb debugging on?
i got drivers from asus site.
deleted all references to N7 and rebooted windows.
un checked debugging on N7.
went to storage and checked mtp.
connected to windows.
when windows wants to install new MTP device, pointed it to the usb_driver folder..
windows installed MTP device..
this all happened to me today.. i am brand new for this device and the N7 board.
i spose this is fine for me but i would still like to see MyComputer show as USB mass storage..
i feel like the MTP doesnt show everything , limiting my access / control..
i would like to know how to do this,
thanx
akusokuzan said:
is usb debugging on?
Click to expand...
Click to collapse
USB debugging is not on. Tried to install the asus drivers and got an error about there not being a driver for 64-bit in them, despite seeing the x64 drivers in the package.
Also, as MTP, my nexus 7 shows up as VID_18D1&PID_4E41&REV_9999
Again, that's with USB debugging disabled, it shows up only as an ADB device.
jptech said:
USB debugging is not on. Tried to install the asus drivers and got an error about there not being a driver for 64-bit in them, despite seeing the x64 drivers in the package.
Also, as MTP, my nexus 7 shows up as VID_18D1&PID_4E41&REV_9999
Again, that's with USB debugging disabled, it shows up only as an ADB device.
Click to expand...
Click to collapse
you didn't uninstall all references to adb first. even if you have to go back to a restore point. then start over for Windows to install as mtp
Hi,
This is my first Nexus device (N4), I know they have an emulated SD card, so I expected to connect it to my Win 7 PC via USB, and for the SD card directory to be shown as a file system / drive in Windows. This doesn't happen.
Phone is in MTP mode, screen isn't locked. Am I missing something here, a driver perhaps, or does this functionality no longer exist?
Thanks,
Des
You should get a Nexus 4 device along with your drives, you open that, then go to 'internal storage'
If you're not getting that, then it's probably driver related.
If it doesn't detect by USB at all, you may have a faulty device like me.
If you plug your phone into the wall with the AC adapter, does it constantly say " charging (USB)" in the battery settings?
This defect means I cannot root or charge the phone properly... It sucks..
Sent from my Nexus 4 using Tapatalk 2
Most likely a driver issue. When I have use the adb driver I cannot see my device as a storage device. Switching to the default driver Windows installs lets me see it but adb no longer works.
I ended up just using AirDroid to do any file transfers.
There are a few reports of the stock charger being reported as USB charging actually, so it might not be all bad.
The phone might be in MTP mode, but has it installed the MTP driver ? Check Device Manager.
On my own XP system, MTP wouldn't work for me until I turned off USB debugging.
Sent from my Nexus 4 using xda premium
steviewevie said:
The phone might be in MTP mode, but has it installed the MTP driver ? Check Device Manager.
On my own XP system, MTP wouldn't work for me until I turned off USB debugging.
Click to expand...
Click to collapse
^ This.
On XP, MTP does not work if USB Debugging is turned on. It may be the same for Windows 7 as well.
Same behavior on Windows 7, just fixed my issues. Thanks!
I got similar problem with my N4, yesterday I flashed Mahdi-ROM 2.4[1/02] then my USB stopped working. I can view files through PC, but cannot upload to phone. It says device has been disconnected, but it's still connected Turning off USB debuging didn't help.
I cannot even flash kernel uploaded through Airdroid, recovery gives error - cannot open zip file.
Edit: Nevermind, its PC problem. With other PC it works normal.
use universal naked drivers.
fastboot adb and mtp and ptp working.
efrant said:
^ This.
On XP, MTP does not work if USB Debugging is turned on. It may be the same for Windows 7 as well.
Click to expand...
Click to collapse
After I rooted my N4 a few months ago same thing, cannot get MTP on WinXP
Works fine on my Win7 machines though, its pretty annoying
Tried ALL the fixes I could find, no go
Uninstal all drivers, reconnect N4 let Windows install drivers, it will probably be adb device drivers, then select in device manager adb device drivers update drivers and check install from specific location and on next screen check don't search!
Then you could be able to select mtp. All of this should be done with USB debugging turned off and USB connection as mtp!
Sent from my Nexus 4 using Tapatalk
Nexus 4
zvecka said:
Uninstal all drivers, reconnect N4 let Windows install drivers, it will probably be adb device drivers, then select in device manager adb device drivers update drivers and check install from specific location and on next screen check don't search!
Then you could be able to select mtp. All of this should be done with USB debugging turned off and USB connection as mtp!
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hey Buudy thanks this helps me
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
4K2K said:
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
Click to expand...
Click to collapse
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Alternative solution is to use KDE Connect app over Wifi. Bonus is that once set up, it is possible to push files from the phone to the PC without any interaction on the PC side - e.g. useful if the PC doubles as a file server.
losteagle said:
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Click to expand...
Click to collapse
Both of my home & works computer (Win10 14959) failed to detect it as MTP or PTP drive. Might have been due to those having previous phone's drivers.
But I faced same problem with fresh out of the box Win8 laptop.
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
ksj0823 said:
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
Click to expand...
Click to collapse
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Citroon said:
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Click to expand...
Click to collapse
Wanted to add my voice here too that I did the same - I had to clean up previous drivers I had installed over time for varios phones and different ADB versions like the one from clockworkmod - once I cleaned that out and installed google drivers from SDK PTP worked and I was able to do Helium restores
I had issue on my Win10 PC, but I found that after I disabled USB debugging, it would work as MTP/PTP, but not for ADB of course. So apparently, I have to toggle USB debugging ON/OFF to switch back and forth from MTP and ADB.
Small pain in the butt.
Solution.
I had the same issue. Drove me NUTS for about an hour. In the end, simply unchecked the USB DEBUGING in developer settings. This will make it pop up immediately.
Update:
I clearly should have read the post above mine first.
Hi,
I've received a couple of days ago two Onplus 5.
They both work great but when I try to connect them to my desktop, they get detected as "qualcomm hs-usb diagnostics 900e" by windows 10 that states the USB device is not recognised.
The issue is reproduced on a laptop, although it did get picked up once by the laptop, only to fail on a second attempt with the same device name "qualcomm hs-usb diagnostics 900e" after I installed the driver provided by Oneplus.
I read on the forum that "qualcomm hs-usb diagnostics 900e" is normally related to Bricked phone issues, which is not my case and I don't know what to do to resolve this.
I also tried to activate the USB debug mode on the phone, but this didn't change the problem.
My windows are all up to date and my phones as well (running Android 7.1.1, OxygenOS 4.5.2)
Has anyone experienced this issue with that phone or any other?
I would greatly appreciate some help and I thank you in advance for reading this and offering advice.
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
dcrnic said:
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
Click to expand...
Click to collapse
Thanks dcrnic, I must have skipped a step with the debugging mode because your procedure did the trick.
Is this a normal process to have to go to Dev mode and Debug mode to be able to connect to a PC?
Thanks again for your help!:good:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Moderators
Please delete ... Today forum is so slow, and it do double posting for some reason even I press reply just once.
Thank you.
FIXED: Use stock op5 cable. The other cable that gave me issues works just fine for op2.
The phone used to be seen by win10, but since oem unlock and superSU, the computer at work doesn't recognize it. Ran the 4.5.2 update with same results. I noticed that in Developer Options -> Select USB configurations charging is selected and greyed out. Going in selecting anything else returns is to Charing.
Device Manager > Find the phone > Right click > Update drivers (or something like that) > Select driver from Computer > Select "MTP USB Device" Enjoy
I'm having the same issue. If I manage to get it to connect to the PC, then after I unplug and plug it again it gives the same not recognised balloon. It only seems to work with USB Debugging On
I ended up using the original op5 cable and it recognizes the phone right away.The cable that didn't work for op5 is not stock, but worked perfectly fine for op2.
Same issue
Even I'm facing the exact same issue on my op5
dcrnic said:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Click to expand...
Click to collapse
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
djsubterrain said:
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
Click to expand...
Click to collapse
Yes, they are on the phone, but computer need to recognize device to see it. It does not, so the drivers on the phone are useless in this case.
I compared this to my ZTE Axon 7. If you choose "Charge only" the Axon 7 is recognized as a USB input device. This should also happen for our OP5 but the driver (which btw. is a windows standard driver) does not contain PID 900E and also does not like to have it forced to a USB input device.
The Axon 7's PID is F006.
However, the real issue is when Windows decides to use Qualcomm's HS USB Diagnostic Interface driver which seems to give even more trouble (at least for me). When I tried to switch to MTP this would not work and my Windows 10 hung itself up when rebooting or shuting down. For now I just disabled the "Unknown device" to prevent such things from happening. Charging still works this way and the phone is correctly recognized when changing to MTP.
If you are facing the same issue, disconnect the Oneplus 5 from your PC, reboot the PC and after that launch the device manager. You need to enable hidden devices in the view menu of the device manager to see disconnected devices. Now remove the device "Qualcomm HS USB Device Interface" and also choose to uninstall the driver itself. After that you can connect your device again and it should pop up as "Unknown device". Then simply disable the device.
Regarding the drivers from Oneplus: this package is lacking a driver for the device we are seeing (VID_05C6&PID_900E).
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
aa_chow said:
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
Click to expand...
Click to collapse
Worked for me, only remember to Uncheck usb debugging BEFORE the update....
Hmm, didn't work for me, same behavior as before the update...Qualcomm HS-USB as soon as phone is plugged in...USB debug was off.
Sent from my ONEPLUS A5000 using Tapatalk
try changing port (and remember to restart the pc)
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
bricky23 said:
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
Click to expand...
Click to collapse
It worked the first time too, but not the second time...at that point connected detected as Qualcomm HS-USB Diagnostic, and computer won't shut down.
And yes I installed it a few time, and it works the first time connecting, but not the second time around.
Sent from my ONEPLUS A5000 using Tapatalk
I don't have my OP5 yet, but I had a very similar and difficult experience with my OP3 when I first received it on Windows 10 Pro. On top of installing the proper drivers, I also had to go into Device Manager and run some steps (I'm going off on memory so they may not be entirely accurate). The root cause is driver signature check enforced in Windows 8+. So by going into Device Manager and seeing "kedacom USB driver", right click and find the oneplus USB driver you installed above and also need to disable the driver signature enforcement (in windows 10 go to advanced startup settings, reboot and choose (I think) #7 then reboot). Then plug in the phone usb go to device mgr right click on kedacom USB driver and choose the oneplus driver.
I don't have all the steps in the right order but it should fix your issue.