Related
put in a new SSD and got Windows 8.1, did a fresh install on a new hard-drive, everything's been working great, My nexus 4 has worked with with ADB./Fastboot and I've been able to transfer files to and from it in MTP mode. Been like that for about 4 days until about 3 hours ago, I had Windows Explorer crash, had to run Task Manager, end the process, and then manually restart explorer.exe My device was plugged in when this happened, and afterwards, I noticed that I could no longer see my Nexus 4 under the Devices & Drives section of "This Computer" (My Computer had a better ring to it lol) First I tried rebooting both my laptop and my Nexus 4, then I tried uninstalled the drivers, rebooting, re-installing, and then rebooting again. Did that like 4 times now, each time re-downloading the drivers, and doing an MD5 hash to create a Checksum, and checking them each time. Also to no avail. ADB shows my device serial number when i enter : ADB Devices, but says it's unauthorized, so if I try anything like: ADB Reboot Bootloader, it says Device is not authorized.
So ! I don't understand wtf is going on. Was working fine before. The drivers are up to date, I just flashed the Official OTA image, and was on the leaked image prior to that. Then earlier this evening I switched to the newest version of the Nexus 5 Port, and everything was still working fine, hadn't made any changes in a couple hours before this happened. When I install the drivers, It acts like it worked. Instead of saying "NEXUS 4" under Other Devices in my Device Manager, it says Composite ADB Interface under Android Devices and MTP under Portable Devices. Sometimes tho the MTP entry will still show the Yellow Exclamation Point. But goes away. Don't know whats up with that either.
Also, it wont let me install drivers unless I am in MTP mode, which Usually you can install them regardless (tho I never tried in Camera mode, I am just assuming about that one) Usually I install drivers without MTP or Camera modes checked, but now if I try it, it says that Windows Cant find the Drivers, even tho I am obviously browsing for them myself and selecting them. And just now I tried updating instead of re-installing them, and it keeps saying that Windows has determined they are the most up to date.
So I am out of I ideas. I even updated windows media player cause that's what fixed my issue on Day 1 of running Windows 8.1 when it wouldn't recognize it at all. So I don't know. Sorry for the long post but I wanted to make sure I got everything in there so hopefully someone can narrow down what the issue is. Cause I've been at it for 3 hours, haven't slept yet, my Nexus 5 gets here today, and I need to get this fixed before I sell it to my buddy. Its brand new, only 15 days old.*
Any thoughts ?*
First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
ADB Devices, but says it's unauthorized
Click to expand...
Click to collapse
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.
eksasol said:
First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.
Click to expand...
Click to collapse
ok I am gonna try that now. And as far as the part about my phone being unauthorized. I already knew about the notification that pops up, i was waiting for it to happen. Never did tho. Maybe it will happen after I do the rest of what you said. thanks, i will post my results in a min
no matter what i do, i cant get MTP working. When i uninstall the ADB entry in Device Manager it gives me the check-box option for removing drivers as well, but not on MTP. And now it wont even give me the option to uninstall, update, or anything at all, even tho I uninstalled it already so it should at least give me the option to install drivers. Even tho it's showing up in Device Manager as a Portable device, if I look in Printers and Devices, it shows up as unspecified device. Disabled USB Debugging, and all that. it says its working but it wont show up in My Computer>Devices and Drives still. For some reason ever once in awhile it will pop up with the Yellow Exclamation Point tho, only for a brief second tho. other then that, its shows it like it's running correctly. Also, nothing pops up saying that windows is installing drivers when i plug it in. Which in Win 7, XP, etc, it always did. Does this not happen in Windows 8.1 ?
Also, under Driver Details, which is the only option it lets me click on MTP, it says the drivers are from 2006 lol
Update - Just reinstalled the drivers for ADB and enabled USB Debugging, and everything is still saying its working even tho its not. But when I take my phone out of MTP mode it shows up in device manager under "Other Devices" as Nexus4, with a Yellow Exclamation, and it gives me the option to update drivers, so i tried, but it says Windows Can't find my driver. This is very frustrating.
Had this problem aswell, which was caused by the N version of Windows 8 versions.
These versions dont have Windows Media Player istalled, which is needed for MTP to work.
So to fix your problem you need to download that latest Windows Media Player (WMP) from microsoft and install that.
I dont have the N version, I have WMP installed, i mentioend your fix in the OP. Had to update it, and it worked. It was working fine for the last few days, then it stopped working suddenly
double post, sorry. dont know why that happened.
Vouch. Since I use win8.1 (no n version) Mtp doesnt work. I tried all known drivers, disabled driver signature and so on. The only working combination for me is Usb Debugging + PTP. Then I use file manager to cut the files. Airdroid would be an alternative as well.
update - SOLVED * Kind of.....I say kind of cause I still don't know what caused it but apparently Flashing to the Nexus 5 Port fixed the issue lol. I am assuming something pertaining to the way USB connectivity is controlled by Android got corrupted, and a fresh install was in order. Whatever it was, it worked and i am back in business. thanks to all those who attempted to help.
Sent From My Nexus 4 via XDA Premium 4
Hello. Im new to the Nexus 10. I downloaded skipsoft Android toolkit, installed adb drivers in the package and rooted the Nexus and installed recovery..it was easy using the toolkit. So the ADB drivers must have worked- at least in the environment it is used in to do these things. But these drivers dont work to transfer files between the nexus and the computer running winxp. I have USB debugging and PTP, have tried every other dirver package that has been mentioned on all available forums, have tried different usb ports, different cables etc. n my computer the device is recognised as a Nexus 10 but clicking on it gives a blank page, so cannot see the Nexux files. WTF this is driving me mad. Any ideas?
Re
Hi Ghosta,
Are you using a USB 3 port? as i have had many strange issues with these the ports. The issue is caused by one of the intel drivers cant remember exactly which way but there is no easy way to fix this. If this is your issues i would try and find if you have a USB 2.1 port you can use or the Esata ports on laptops tend to be usb 2.1 inside...even though they dont look like it haha
Hope this helps
ghosta12 said:
Hello. Im new to the Nexus 10. I downloaded skipsoft Android toolkit, installed adb drivers in the package and rooted the Nexus and installed recovery..it was easy using the toolkit. So the ADB drivers must have worked- at least in the environment it is used in to do these things. But these drivers dont work to transfer files between the nexus and the computer running winxp. I have USB debugging and PTP, have tried every other dirver package that has been mentioned on all available forums, have tried different usb ports, different cables etc. n my computer the device is recognised as a Nexus 10 but clicking on it gives a blank page, so cannot see the Nexux files. WTF this is driving me mad. Any ideas?
Click to expand...
Click to collapse
What does Device Manager show? Device name, its Properties and exclamation mark?
You do know that if your device has a "password" then you must be logged in to see its contents.
peterk-1 said:
What does Device Manager show? Device name, its Properties and exclamation mark?
You do know that if your device has a "password" then you must be logged in to see its contents.
Click to expand...
Click to collapse
Thanks for the replies and suggestions. All shows up OK in device manager, the device is not password protected, and the laptop has usb2 ports. I had another try today, after connecting the nexus it shows up in my computer as a camera, labelled nexus 10, with the camera icon. When I click on the icon it opens a special folder, must be a camera folder and the camera and scanner wizard starts. After a while it detects the photos on the nexus ( I have loaded a lot on it via USB otg using flash drive ), but thumbnails of the photos are not downloaded as I usually see when I connect a camera. The wizard downloads photos back to the computer, but each photo is about 18 kB instead of the 2 mb they originally were. So it appears a connection is happening, but a very strange one. I don't like to be beaten on problems like this one, but searching the net has not given me any answers, and I don't understand the android system well enough to know what to try next.
I think your device is working. If you connect it up as it now is and then go into Settings > Storage and tap the top RH corner menu you get the USB Computer Connection and select that and change it to MTP you should find it is now visible in My Computer or after auto install of the driver it will be visible. I'm brain dead - you said you had a PTP connection!
peterk-1 said:
I think your device is working. If you connect it up as it now is and then go into Settings > Storage and tap the top RH corner menu you get the USB Computer Connection and select that and change it to MTP you should find it is now visible in My Computer or after auto install of the driver it will be visible. I'm brain dead - you said you had a PTP connection!
Click to expand...
Click to collapse
No PTP conection or MTP connection either. The Nexus also shows up in Device Manger under Imaging Devices when USB deugging is on, which is causing the camera and scanner wizard to start, although it doesnt work properly. When i disable it nothing happens at all. No idea where to go from here.
There is or was an issue with XP see http://forum.xda-developers.com/showthread.php?t=2305943
peterk-1 said:
There is or was an issue with XP see http://forum.xda-developers.com/showthread.php?t=2305943
Click to expand...
Click to collapse
Thanks for the suggestion, I had already tried that but I did it again just to make sure. It did not work for me.
Have you tried following the driver install guide from Wug's toolkit? I've never used Skipsoft's but if it doesn't have you delete old drivers properly it's possible there's some old or corrupted driver sticking around from all the installs you've done. If you follow Wug's guide exactly you should end up with the only the correct drivers installed. Also, what ROM and kernel are you using? It's possible the issue is there.
capnkrunch said:
Have you tried following the driver install guide from Wug's toolkit? I've never used Skipsoft's but if it doesn't have you delete old drivers properly it's possible there's some old or corrupted driver sticking around from all the installs you've done. If you follow Wug's guide exactly you should end up with the only the correct drivers installed. Also, what ROM and kernel are you using? It's possible the issue is there.
Click to expand...
Click to collapse
I used a program called usbdeview to uninstall every USB driver with an "android" or "adb" description which should have cleaned up my drivers? Then after reinstalling drivers I tried again no difference. I ran android-tools and can push and pull files to and from the computer and nexus, (from command line) so I believe I have eliminated hardware problems and software problems on the nexus. This leaves the computer, which works perfectly with my other android devices running 4.1.1.
Just in case this helps. In usbdeview I have 5 nexus 10 entries. They all have the vendor id of Google 18d1 and a unique Product ID . Which driver connects is related to the device settings:
PID Device settings
4ee1 MTP
4ee2 MTP + USB debugging
4ee5 PTP
4ee6 PTP + USB debugging
d002 USB debugging
With the device connected I can change settings and see the change in connected driver in USBDeview.
peterk-1 said:
Just in case this helps. In usbdeview I have 5 nexus 10 entries. They all have the vendor id of Google 18d1 and a unique Product ID . Which driver connects is related to the device settings:
PID Device settings
4ee1 MTP
4ee2 MTP + USB debugging
4ee5 PTP
4ee6 PTP + USB debugging
d002 USB debugging
With the device connected I can change settings and see the change in connected driver in USBDeview.
Click to expand...
Click to collapse
This info does provide me with some way forward. With USB , when connected ptp I have a nexus 10 USB composite device and a nexus 10 digital still camera connected with the green light in USB deview, and also a blank device name, connected, description android composite device with a purple light. I'm guessing purple means not working. But changing drivers does nothing to change the purple light. Switching to mpt gives an additional blank name Google nexus adb interface also with purple light shown as connected. All connected devices show vendor 18d1. Drivers tried 1) clockworkmod (supplied with skipsoft); 2) naked drivers 3) Google drivers. Any clues what to try next?
2 things to check. I just tried running usbdeview from Wug's toolkit. It was v2.0 and wasn't the same as the version I have installed v2.3 - and there have been a significant number of changes. If you have XP pro x64 then you must use the x64 version of usbdeview - again I think Wug's may only ship with 32 bit usbdeview http://www.nirsoft.net/utils/usb_devices_view.html You will also find an explanation of the coloured radio buttons.
If you find you need to update usbdeview then I would suggest you uninstall the device drivers (instructions in Wug's toolkit?) then new drivers from http://developer.android.com/sdk/win-usb.html#top and follow the linked install instructions.
peterk-1 said:
2 things to check. I just tried running usbdeview from Wug's toolkit. It was v2.0 and wasn't the same as the version I have installed v2.3 - and there have been a significant number of changes. If you have XP pro x64 then you must use the x64 version of usbdeview - again I think Wug's may only ship with 32 bit usbdeview http://www.nirsoft.net/utils/usb_devices_view.html You will also find an explanation of the coloured radio buttons.
If you find you need to update usbdeview then I would suggest you uninstall the device drivers (instructions in Wug's toolkit?) then new drivers from http://developer.android.com/sdk/win-usb.html#top and follow the linked install instructions.
Click to expand...
Click to collapse
I gave up completely on this, and connect via wifi using ES file explorer. I bought my wife a new tablet an Acer Aconia A1-830 and it has the same problems, impossible to connect via ADB, with exactly the same symptoms. Yet our phones connect via ADB without a problem, but both are Androild 4.1 or earlier and the tablets 4.2 or younger. Obviously an Android generated problem that arose when 4.2 was released and on which has no fix.
Hi everybody.
I have a problem with my Nexus7 tablet, windows 8 can't see it on Devices and drivers and after I plug off the usb cable this error message appears:
Image like: The last USB device you connected to this computer malfunctioned, and Window does not recognize it.
First thing I opened the developer options and checked USB Debugging, after that a strange icon with 4 vertical white rows appears on the notification tab, It was not the usually USB debugging icon.
Then I went on Device Manager and under Acer Devices (Why Acer ???) I found ACER Composite ADB Interface, so I've decided to install again the drivers following this guide:
-----------------
But at the point 8 I can't see "USB composite device" but only "Acer composite ADB interface".
Since yesterday the tablet worked, and I have not update the tablet neither the pc.
What should I do ?
Thanks for the help, sorry for my bad english
* I have few message so I can't upload images or link, sorry for the inconvenience.
I opened now "Devices and Printers" and I saw Nexus7 (with the correct label) under "unspecified", I cannot interact with it
mmm no one ?
I have the same issue with my 8.1 laptop. I think the Acer driver is something which Microsoft pushed in an update to 8.1 recently. I may go in and see if I can revert it. Not sure I am much help as my only workaround was to grab my Win 7 laptop, which worked as it should. I did not have the time or patience to screw with it.
Pickeroll said:
Hi everybody.
I have a problem with my Nexus7 tablet, windows 8 can't see it on Devices and drivers and after I plug off the usb cable this error message appears:
Image like: The last USB device you connected to this computer malfunctioned, and Window does not recognize it.
First thing I opened the developer options and checked USB Debugging, after that a strange icon with 4 vertical white rows appears on the notification tab, It was not the usually USB debugging icon.
Then I went on Device Manager and under Acer Devices (Why Acer ???) I found ACER Composite ADB Interface, so I've decided to install again the drivers following this guide:
-----------------
But at the point 8 I can't see "USB composite device" but only "Acer composite ADB interface".
Since yesterday the tablet worked, and I have not update the tablet neither the pc.
What should I do ?
Thanks for the help, sorry for my bad english
* I have few message so I can't upload images or link, sorry for the inconvenience.
Click to expand...
Click to collapse
You may wish to go to Storage, on the Nexus 2012, and under the 3 dots, USB computer connection menu, and tick/untick Media Device
Windows 7 and 8, appear to have USB storage driver conflicts, when many different devices have been used repeatedly.
Good Luck!
There are other posts, in the General section, that deal, with this annoying issue.
ROLY5573 said:
You may wish to go to Storage, on the Nexus 2012, and under the 3 dots, USB computer connection menu, and tick/untick Media Device
Windows 7 and 8, appear to have USB storage driver conflicts, when many different devices have been used repeatedly.
Good Luck!
There are other posts, in the General section, that deal, with this annoying issue.
Click to expand...
Click to collapse
Thanks for the hep but it didn't work.
Now the "old" icon came back with "connected as a media device" written with it but the tablet remain invisible.
Same problem here.
Fixed it by disconnecting teh device, going to device manager, showing hidden devices and uninstalling everything related to Nexus 7.
This includes Acer ADB, Android, Nexus7 and unknown devices.
After that I downloaded the Android SDK and installed the Google USB driver from it, connected my Nexus 7 and it werks.
pepo930 said:
Same problem here.
Fixed it by disconnecting teh device, going to device manager, showing hidden devices and uninstalling everything related to Nexus 7.
This includes Acer ADB, Android, Nexus7 and unknown devices.
After that I downloaded the Android SDK and installed the Google USB driver from it, connected my Nexus 7 and it werks.
Click to expand...
Click to collapse
Still nothing, I showed the hidden devices and unistalled all the voices under the "Acer" directory, I haven't found anything related to Android/Nexus 7.
Then i went to http://developer.android.com/sdk/win-usb.html and downloaded the USB driver, but the Nexus7 result again as an unspecified hardware.
Now it works ! I didn't touched it in the last 2 hours and now it works. :good::good:
I downloaded latest ADB/Fastboot package to my Win 7 PC.
I installed the Zadig drivers exec to load drivers (as seen in another thread).
Enabled USB debug
Connected phone
ADB devices ... doesn't show phone
Phone shows ADB icon in task bar
In device manager I can see libusbK USB Devices .. ADB Interface (Interface 1) .. when I plug the phone in
I have revoked previous computers and rebooted both PC and phone with no changes
... now I am a bit lost
* Bump * .. I can't do much without ADB ... could someone at least point me to the correct drivers - what I have downloaded from Zadig do't seem to work.
I'm currently having the same problem of not being detected when I type in "ADB devices" in Windows 10 after an auto-update which can't be stopped screwed up my drivers. I found this thread while searching for an answer myself. I tried reinstalling all Qualcomm and fastboot drivers and even though my phone can be detected in Windows again (after manually selecting "MTP USB Device" as a driver update for the A7 in the device manager) I still get nothing when I type in ADB devices. Though I tried flashing something to it anyway (same TWRP recovery I already have since the file was already there) and it seemed to work? Have you tried flashing something to your phone anyway?
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.