Database Users

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.

Cannot find device with adb (Ubuntu based OS, Dell notebook)

Hi,
adb doesn't detect my ZUK Z1 device.
I followed all instructions and tutorials I could find. I Enabled USB debugging and OEM unlocking, added vendor ID in
Code:
~/.android/adb_usb.ini
(My Galaxy Tab 3 is listed by adb when connected, btw.)
I would first like to know that it's not a hardware / OS / driver issue.
What I find odd is that it doesn't even charge when connected to the PC. Does this indicate a more general problem? (Charging only works with a power adapter with ~2A output.)
PC is a DELL Latitude E6540 which is supposed to have 4 USB 3.0 ports.
I'm running Elementary OS which is Ubuntu 16.04 based. It seems that it's not officially supported by Dell.

The USB cable was the issue.
I replaced it and everything worked like charm.
I didn't think the cable was the problem because it still worked for charging.

ADB not working

Hi guys...
Yesterday my new PH-1 arrived and today I wanted to use ADB with the app "custom navigation bar". My problem is: i can`t get it to work... I´ve used adb several times with different phones, but with the PH-1 it can´t connect with my Windows 10 computer. Is it possible that I can´t get it to work because Ì´m using a different USB-C cable (took 3 different from Xiaomi another manufacturer)?
How do get it to work? Everytime I connect the phone with the computer, I get the message USB debugging is on and I use MTP to work, but the phone doesn`t show the RSA key fingerprint. Any suggestions?

masterchief_2001 said:
Hi guys...
Yesterday my new PH-1 arrived and today I wanted to use ADB with the app "custom navigation bar". My problem is: i can`t get it to work... I´ve used adb several times with different phones, but with the PH-1 it can´t connect with my Windows 10 computer. Is it possible that I can´t get it to work because Ì´m using a different USB-C cable (took 3 different from Xiaomi another manufacturer)?
How do get it to work? Everytime I connect the phone with the computer, I get the message USB debugging is on and I use MTP to work, but the phone doesn`t show the RSA key fingerprint. Any suggestions?
Click to expand...
Click to collapse
Mines wouldn't connect using the usbc cable it came with I had to use a regular usb to usbc cable for it to work

See your device manager. To see if you are seeing "Mata". You have to download the google usb driver and update it from there
I have S8 from my previous computer but i need to re install the driver again

https://www.youtube.com/watch?v=LbAq6d2Du0U
You can also try this tuturial hope that it is working for you.

Try this > Download and install the essential usb driver > go to device manager and update the driver. Choose the option where you can change the source and select the driver in the list > go to the Essential Folder in Program Files and choose the file named "essentialadb.inf" for your pc. That should work
It's and old thread but if there is someone new to this...

My essential wouldnt work with the previous ADB i had installed that had worked fine with all my other devices.
I installed https://forum.xda-developers.com/showthread.php?t=2317790 and worked just fine. Make sure your device isnt connected as anything other than charging. The previous ADB i was using didnt acknowledge my device but on first try with Minimal i was prompted on my phone right away

I had the same problem when attempting to flash my ph-1, when trying to use the cable that came with the device. I used a standard USB-A to USB-C cable and everything worked just fine. I noticed on the 8.1 update notes for side loading that the team indicates that the cable that comes with the phone is "Primarily" designed for charging and not data transfer. So I'm guessing that it is of lower quality and doesn't handle the transfer speeds.

blackbms said:
I had the same problem when attempting to flash my ph-1, when trying to use the cable that came with the device. I used a standard USB-A to USB-C cable and everything worked just fine. I noticed on the 8.1 update notes for side loading that the team indicates that the cable that comes with the phone is "Primarily" designed for charging and not data transfer. So I'm guessing that it is of lower quality and doesn't handle the transfer speeds.
Click to expand...
Click to collapse
Hold either volume button while connecting cable from phone to pc, it will detect automatically. It may work.

Phone not connecting to PC for File Transfer

I had previously connected my Asus X00TD to my laptop for transferring files. The phone doesn't connect to PC from yesterday. Only charging happens after connection, and device doesn't show up on the device manager(no change on list of devices after connection), and no notification sound of device being connected either. There is no notification in my phone as well. Here are the following workarounds I have tried, but failed:
Changing USB cable
Changing PC/laptop
Installing ADB and Qualcomm drivers and again uninstalling them(error code 10 on ADB Driver)
enabling and disabling USB debugging
changing connection mode(nothing works)
Going into safe mode
restarting and connecting multiple times
Kindly help me if possible, and your help will be kindly appreciated

I had a similar problem recently. What ended up working for me was to install some generic Android driver published by Google. I already had the ADB package installed, but without the generic Android driver published by Google, my phone could charge and transfer files, but I could not issue ADB commands through the Windows command prompt.
The package I needed was called "usb_driver_r13-windows.zip"