Database Users

[Q] Nexus 4 usb file transfer

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

How to get USB Debugging mod to work?

I have a nexus 7 2012 and i am trying to install 4.3. Of course since i have rooted it and have twrp on it i cant just ota update, so i tried plugging it up to my computer. Right now everytime i plug in the device and use it as a media device it works until i turn on developer mode and enable usb debugging. As soon as i turn on debugging the device disconnects at the bottom right showing my N7 (on windows 7), and whenever i look in my computer its not there also. The only way i can find it in this mode is in device manager in which it says "android phone". I figured maybe i have a driver problem, but if you look for drivers and try to install it says it already has them.
So does anybody know how to get it to work so i can reset it?

Delete the current drivers than manually choose the n7 drivers you downloaded from xda.
Or use a free program called usbdeview for windows to seek out all drivers associated with a device to make sure you uninstalled them correctly. Also I highly recommend dual booting a Linux distro which is much less finicky than windows when using android
Best of puck
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
Delete the current drivers than manually choose the n7 drivers you downloaded from xda.
Or use a free program called usbdeview for windows to seek out all drivers associated with a device to make sure you uninstalled them correctly. Also I highly recommend dual booting a Linux distro which is much less finicky than windows when using android
Best of puck
Sent from my Nexus 7 using Tapatalk 2[/Q
Can you inform me on how to delete the current drivers?
when i connect with usb debugging mode turned on it connects as nexus 7 with a description as Android Composite ADB Interface. Also it is not recognized under the my computer setting at all. In usb deview it also has a purple dot all the way to the left beside the name instead of a green dot.
When i connect to the pc without usb debugging on the computer recognizes it as nexus 7 \ media device and i can use it as storage back and forth and in usb deview it has a green dot beside the name
Click to expand...
Click to collapse

If MTP, PTP does not work (If you can't acces phone storage with PC)

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.

Oneplus 5 not recognised in Windows 10

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.

Windows 10 Installs 8 Pro as CD Drive

Just got my 8 Pro and found a quick problem. Windows 10 only recognizes the phone as a CD drive. I checked in Windows Device Manager, and sure enough it shows up there as a CD drive. I have uninstalled and reinstalled the OnePlus USB drivers with no success. I've gone into Developer Options on the 8 Pro and set Default USB configuration to File Transfer without any improvement. Adb recognizes the device as attached.
Any suggestions on getting Windows 10 to recognize the phone as connected USB device would be gratefully appreciated.
Abort, Retry, Fail?
P. S. The problem seems to be caused by enabling USB debugging in Developers Options. With USB debugging enabled, the phone disappears from Windows. Toggling the USB enabled option off returns the phone to Windows. As long as I keep USB debugging toggled off in Developers Options the phone appears as IN2025 in Windows. All is now well; I'm TWRP'd and rooted.

Glad it worked out for you and thanks for the feedback!

galaxys said:
Glad it worked out for you and thanks for the feedback!
Click to expand...
Click to collapse
I spoke too soon. After the factory reset the 8 Pro connected, but now the same problem has returned.