Develop Bugs

[Q] ADB not recognizing device

Hi All:
I have the 16GB N7 (2013) with USB debugging enabled. I plug into my Windows 7 box via USB 2.0, and it successfully appears in my device manager as 'Google Nexus ADB Interface'. I just downloaded the current Android SDK, however when I run 'ADB devices' in the command prompt, ADB does not recognize any devices.
Any ideas?
Thanks!

Did you try if it would recognize your device in fastboot bootloader?

Go into I believe its called SDK manager and make sure USB or Google drivers update is checked and then click Install as this will install all drivers needed. But prior to that uninstall any drivers in device manager for your nexus 7 . it should pick it up right away after everything installs! Good luck
Sent from my Nexus 7 using xda premium

highwaybandit said:
Go into I believe its called SDK manager and make sure USB or Google drivers update is checked and then click Install as this will install all drivers needed. But prior to that uninstall any drivers in device manager for your nexus 7 . it should pick it up right away after everything installs! Good luck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for the suggestion, highwaybandit. I tried your idea, but still have the same issue with ADB not recognizing the device, despite the device showing up successfully in Windows device manager.

I have the same problem with Ubuntu. I tried "adb reboot bootloader" and nothing. Unlocked fine with fastboot tho.
Sent from my Nexus 7 using Tapatalk 2

Username invalid said:
Did you try if it would recognize your device in fastboot bootloader?
Click to expand...
Click to collapse
Yes, and it does. I was able to 'fastboot oem unlock'. However, can't issue any adb commands.

My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated

mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
Now that you mentioned it, same issue here, in addition to the ADB issue mentioned above. My N7 doesn't show up as a drive whether I have USB debugging enabled or not.

mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
mickrg123, I forgot to mention: I've been getting around this issue by using Google Drive. Not as fast as moving files directly, but still a decent workaround until we get this figured out.

mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
If you have USB debugging enabled, the USB IDs change and for some reason windows can't find the MTP drivers for the device.
If you turn off USB debugging, then the phone shows up as an MTP device (ie it shows up as Nexus 7, not a drive letter)
If you want it to show up as a drive letter, you probably need to root and enable USB mass storage, otherwise it will behave as an MTP device (ie it behaves more like an FTP server than a USB hard drive)
If you have USB debugging disabled and it still won't show up on your computer in MTP mode (ie labeled Nexus 7), then you probably have some problem with MTP on your PC.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
ddb540 said:
Hi All:
I have the 16GB N7 (2013) with USB debugging enabled. I plug into my Windows 7 box via USB 2.0, and it successfully appears in my device manager as 'Google Nexus ADB Interface'. I just downloaded the current Android SDK, however when I run 'ADB devices' in the command prompt, ADB does not recognize any devices.
Any ideas?
Click to expand...
Click to collapse
Generally, if it doesn't show up at all with adb devices, then it is probably driver problem, cable problem, port problem, or USB debugging didn't properly get enabled. Although since you say it shows up in device manger, it would seem to show that USB debugging was enabled, so you might want to look at driver, cable, or USB port issues (try USB 2.0 port if you are currently using USB 3.0). You can get updated drivers here:
http://developer.android.com/sdk/win-usb.html
You can force windows to update driver by right clicking on the adb device entry and going through the tabs until you find the update driver button.
If it shows up but says device offline, then it is probably the RSA security introduced into adb/android since 4.2.2 (in which case you should update your platform-tools to 16.0.1 or greater)

Also when I check box to load camera it will show as drive

sfhub said:
If you have USB debugging enabled, the USB IDs change and for some reason windows can't find the MTP drivers for the device.
If you turn off USB debugging, then the phone shows up as an MTP device (ie it shows up as Nexus 7, not a drive letter)
If you want it to show up as a drive letter, you probably need to root and enable USB mass storage, otherwise it will behave as an MTP device (ie it behaves more like an FTP server than a USB hard drive)
If you have USB debugging disabled and it still won't show up on your computer in MTP mode (ie labeled Nexus 7), then you probably have some problem with MTP on your PC.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
Generally, if it doesn't show up at all with adb devices, then it is probably driver problem, cable problem, port problem, or USB debugging didn't properly get enabled. Although since you say it shows up in device manger, it would seem to show that USB debugging was enabled, so you might want to look at driver, cable, or USB port issues (try USB 2.0 port if you are currently using USB 3.0). You can get updated drivers here:
http://developer.android.com/sdk/win-usb.html
You can force windows to update driver by right clicking on the adb device entry and going through the tabs until you find the update driver button.
If it shows up but says device offline, then it is probably the RSA security introduced into adb/android since 4.2.2 (in which case you should update your platform-tools to 16.0.1 or greater)
Click to expand...
Click to collapse
I don't care if doesn't show as drive but doesn't even show as nexus 7 so I can't root until I can load su onto sd card.
Have tried different cables and ports. I heard beep when it connects and shows in menu to to eject nexus 7
Any other ideas?

mickrg123 said:
Also when I check box to load camera it will show as drive
Click to expand...
Click to collapse
If you have USB debugging enabled, then my experience is Media device (MTP) mode won't be recognized because it can't find appropriate drivers (even though you have the MTP drivers installed) but Camera (PTP) mode will still work. I don't think you really mean it shows up as a "drive" as in mass storage device. I think you mean you see a folder where you can access your files.
If you disable USB debugging, than both MTP and PTP should work.

sfhub said:
If you have USB debugging enabled, then my experience is Media device (MTP) mode won't be recognized because it can't find appropriate drivers (even though you have the MTP drivers installed) but Camera (PTP) mode will still work. I don't think you really mean it shows up as a "drive" as in mass storage device. I think you mean you see a folder where you can access your files.
If you disable USB mass storage, than both MTP and PTP should work.
Click to expand...
Click to collapse
Yes you're correct shows as a device not drive when in camera ptp, but not when mtp checked. Where do you disable mass storage?

mickrg123 said:
Yes you're correct shows as a device not drive when in camera ptp, but not when mtp checked. Where do you disable mass storage?
Click to expand...
Click to collapse
Sorry, I meant disable USB Debugging, not mass storage (I'll correct the post)
I'm sure you know where, but if not, Settings->Developer options->USB debugging
If MTP still doesn't work, then see if you have ever gotten MTP to work on the PC (ie another device in MTP mode). If not, look up how to install/reinstall MTP support for your OS version. Windows added it as part of user driver framework and one of the new versions of media player.
---------- Post added at 04:39 PM ---------- Previous post was at 04:32 PM ----------
mickrg123 said:
I don't care if doesn't show as drive but doesn't even show as nexus 7 so I can't root until I can load su onto sd card.
Have tried different cables and ports. I heard beep when it connects and shows in menu to to eject nexus 7
Any other ideas?
Click to expand...
Click to collapse
If your goal is just to load files onto the sdcard, have you tried "adb push"?
You don't need to have the phone visible as a device/folder on the computer to use adb to place files on the tablet.

Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed

droider137 said:
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
Click to expand...
Click to collapse
1. Plug in nexus 7, MTP mode
2. Open the device manager
3. Right click the nexus 7 > uninstall drivers > unplug
4. Install drivers > http://developer.android.com/sdk/win-usb.html
5. Plug nexus 7 in, drivers will install, should say adb interface
Open up command prompt > nav to your adb folder > adb devices: device number should pop up. Good to go.

droider137 said:
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
Click to expand...
Click to collapse
For me, when I rebooted the phone into bootloader mode, it came up with a new USB device "Android Bootloader Interface". I had to point the driver install at the Google USB drivers I had previously used for the ADB interface so that the Bootloader Interface could be recognized.

sfhub said:
For me, when I rebooted the phone into bootloader mode, it came up with a new USB device "Android Bootloader Interface". I had to point the driver install at the Google USB drivers I had previously used for the ADB interface so that the Bootloader Interface could be recognized.
Click to expand...
Click to collapse
Finally got it!! Had to uninstall and re install the drivers a few times and also remove MTP from device manager. Also had to do the same thing and point it to the drivers in both cases. Thanks. Also thanks to teh roxxorz!

droider137 said:
Finally got it!! Had to uninstall and re install the drivers a few times and also remove MTP from device manager. Also had to do the same thing and point it to the drivers in both cases. Thanks. Also thanks to teh roxxorz!
Click to expand...
Click to collapse
No problem guy; glad you're up an flashing.

Can't get Nexus 7 to show up on computer

Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far

and yes forgot to put in the title but this is for the Nexus 7FHD 2013

Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.

sfhub said:
Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.
Click to expand...
Click to collapse
tried USB 3.0 as well as 2.0 on desktop doesnt work, shows up as a device on safely remove hardware, and I can also see it under other devices in hardware manager or whatever but doesnt display in computer
USB debugging enabled or disabled on stock doesn't work.. tried going back to stock and doing driver installation etc as well

In device manager are there any unknown devices?

Did you remember to
Originally Posted by Geodude074 View Post
When you uninstall the driver, make sure you check the option to DELETE the driver as well. Otherwise when you try to reinstall it, it will just reinstall the old driver again

Driver instal with WinXP
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.

un1bomber said:
Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far
Click to expand...
Click to collapse
Just go in settings then storage and then computer usb connection by opening preferences in storage and then make sure mtp is checked.

Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!

un1bomber said:
Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!
Click to expand...
Click to collapse
We are always here to help.
I remember few years back I installed miui ROM on my xperia n couldn't connect to PC , only to realise USB wasn't turned to mtp by default. I thought it was a bug, tried everything even to fix it only to realise this.

Thanks a lot !!! This solution worked perfectly for me
You saved lots of time for me
Thanks a ton :good::good::good:
Best regards,
RR215 said:
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.
Click to expand...
Click to collapse

If nothing else here has helped you solve this issue, check my thread, it should be of some help to you...

I'm having an issue where I can connect to my laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager.
Rick

[Q] Cannot Unlock Bootloader on Windows 8.1

Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.

killfire72 said:
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
Click to expand...
Click to collapse
Use another computer if you can.

I had similar problems until I used this version of adb
http://www.mediafire.com/download/e5mieo2vxjd71ws/android-tools.zip
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.

ashyx said:
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
Click to expand...
Click to collapse
That version of ADB didn't work for me either. Anyway I was able to get fastboot to work but not ADB so I was able to unlock and root and everything through a strange method using only fastboot.
Second question, if I am switching between AOSP roms, say for example CM to PA, can I dirty flash or do I have to reset?

ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8

xeron72548 said:
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
Click to expand...
Click to collapse
Not so, I and others have ADB working fine on USB 3.0 ports.
The problem is Windows 8 driver signing enforcement blocking the install of drivers. You need to go to advanced startup options to disable it.
Download these drivers first and extract: http://www.mediafire.com/download/i3lcm7dwl581518/ADB_Fastboot_Drivers_Win81.zip
Follow these instructions to disable driver signing enforcement: http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html
Once fully booted go into device manager and you should see a device called 'Android 1.0' with an exclamation mark.
Right click 'Android 1.0' then 'update driver software' then 'Browse my computer for driver software'
Click the 'Browse' button and then browse to the driver folder 'ADB_Fastboot_Drivers_Win81' extracted earlier then click next to install the driver.
You will get a warning about unsigned drivers, just ignore and continue.
The drivers should install and you should see a new entry in device manager called 'Android phone' which means the ADB driver is installed.
ADB should now be working.

Thank you so much for this. Have been wondering for a very long time
Sent from my HTC One_M8 using XDA Free mobile app

It sounds like you've got plenty of technical help already, but I will say that I use ADB perfectly fine on my desktop with Win 8.1 so it's possible. I also use hassoon's toolkit occasionally with no issue.
Before I could get the desktop to recognize the M8 I had to completely uninstall all drivers related to my previous galaxy nexus as well as remove any mention of the device in Window's USBdeview. After a reboot, I just plugged in the M8 and windows automatically installed the necessary M8 drivers. I can then run fastboot and adb from the toolkit.

I ended up uninstalling the MSFT USB 3.0 drivers and use the Intel USB 3.0 drivers instead on my Win8.1 laptop that has only USB 3.0 ports. Works great.

Pixel C Not recognized anymore!

Since the early October update of Nougat's, my Pixel C is not being recognized, or plainly shows up as MTP device and I'm unable to transfer. When in fastboot And adb the PixC's model# Does register. Ive updated Everything incl. WugFresh, Skipsoft and sdks. Please help!

iamkardde said:
Since the early October update of Nougat's, my Pixel C is not being recognized, or plainly shows up as MTP device and I'm unable to transfer. When in fastboot And adb the PixC's model# Does register. Ive updated Everything incl. WugFresh, Skipsoft and sdks. Please help!
Click to expand...
Click to collapse
Update the drivers on your PC.

Thank you, though have done. Right after i saw reply i found DriverBooster4 and it "updated 13 drivers" but i guess not the right ones

iamkardde said:
Thank you, though have done. Right after i saw reply i found DriverBooster4 and it "updated 13 drivers" but i guess not the right ones
Click to expand...
Click to collapse
You need to do it manually. Google "how to manually update drivers windows 10". Do it via device manager with your Pixel C plugged in.

did do. And also before have tried to "point the update to" sdk and Wug's folders. Am not a total noob, but braincells do die, I cant stop it! If it matters, I did just few days ago clean-"re"install win10 64 but this problem was b4 that.. hence the clean start over. All Im ever getting is MTP USB Device, or wen tab's in fastboot, Android ADB Device. Both say "best is already installed".

also have done the "disable driver enforce", i do that routinely now til this is solved..

iamkardde said:
also have done the "disable driver enforce", i do that routinely now til this is solved..
Click to expand...
Click to collapse
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader

with plugged in, debug on and mtp on, it showed as portable devices/mtp usb device. it did install successfully (again); reboot using f7 and... nothing, still the same

iamkardde said:
with plugged in, debug on and mtp on, it showed as portable devices/mtp usb device. it did install successfully (again); reboot using f7 and... nothing, still the same
Click to expand...
Click to collapse
it no longer shows as "unknown".

iamkardde said:
it no longer shows as "unknown".
Click to expand...
Click to collapse
I can b a bit dense, so in case i forget, Thank you for your help!! will probab say this again later..

Thanks to cam30era for the helping!! Problem was simply my misuse of TB. No mystery or MS/Google conspiracy. I went back to stock, re-rooted and Voila!

Unlock bootloader - "waiting for any device"

I got my OP3 today and am trying to unlock the bootloader. I've tried every tutorial and toolkit out there but they all get stuck at the same point in adb, "waiting for device". The "adb devices" command works fine but anything else gets stuck on "waiting for any device". I've tried googling the issue but none of the suggestions have worked so far. Any input would be great.

did you enable oem unlocking from developer options?

bro you may be running win 10 and to connect fastboot on that u need adb driver which u will find on windows update all u have to do is just connect your phone with data transfer mode and update the window 10 . ull find something name qalllcom its adb drive or i dont but after that it will like charm.

I have all the necessary developer options checked. After futzing with it for hours, I tried a different computer (also Windows 10) and it worked right away. I'm going to see what the driver issue is this evening because I still would like to use the original computer I was using. Thanks for the replies!

What does "adb devices" return?

aadityarulez said:
What does "adb devices" return?
Click to expand...
Click to collapse
Screenshot:

for bl unlock, you need to be at fastboot mode, and installed right driver, for me working any of stock Google USB package fastboot bootloader driver.

Go to fastboot mode and do "fastboot devices", then try unlocking bl.

You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs

harish15 said:
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
Click to expand...
Click to collapse
I've tried everything including disabling driver enforcement on Win 10 but I still have the same issue. I have the wrong drivers installed. I've tried uninstalling and reinstalling the drivers but when I plugin the phone, the wrong drivers get installed. I got it to work on another Windows 10 computer and below are device manager screenshots of the working (with right drivers) and not working (with wrong drivers) computers. I have no idea how to get the right drivers installed on the computer where its not working and unfortunately, its the primary computer I use.

shobuddy said:
I've tried everything including disabling driver enforcement on Win 10 but I still have the same issue. I have the wrong drivers installed. I've tried uninstalling and reinstalling the drivers but when I plugin the phone, the wrong drivers get installed. I got it to work on another Windows 10 computer and below are device manager screenshots of the working (with right drivers) and not working (with wrong drivers) computers. I have no idea how to get the right drivers installed on the computer where its not working and unfortunately, its the primary computer I use.
Click to expand...
Click to collapse
Right click, uninstall the wrong drivers.. Tick delete button too in the dialog prompt. Try installing now.
Sent from my Xiaomi Mi 5 using XDA Labs

harish15 said:
Right click, uninstall the wrong drivers.. Tick delete button too in the dialog prompt. Try installing now.
Sent from my Xiaomi Mi 5 using XDA Labs
Click to expand...
Click to collapse
I've tried this several times over. I do not get the tick option to delete.

shobuddy said:
I've tried this several times over. I do not get the tick option to delete.
Click to expand...
Click to collapse
Pm me, if case, you need some guidance.
Sent from my Xiaomi Mi 5 using XDA Labs

Same here. When I reboot in fastboot mode, the driver adb interface disappears and I get the Android Bootloader Interface (Kedacom USB Driver).
"waiting for any device" each time.
Thx for help

shobuddy said:
I've tried this several times over. I do not get the tick option to delete.
Click to expand...
Click to collapse
Try this:
Connect the op3 to usb port - don't bother changing from "charging"
Right click on "ADB Interface" in dev man and disable it.
Without unplugging the op3 use the buttons to reboot into bootloader.
Hopefully W10 will now detect your op3 and either load the correct "oneplus" driver or create a new entry in dev man of Other Devices > Android Composite ADB Interface. Right click on this and then Update driver software > Browse my computer.... > Let me pick... > and if you're lucky One plus will show up in the manufacturer column and allow you to select the composite interface

peterk-1 said:
Try this:
Connect the op3 to usb port - don't bother changing from "charging"
Right click on "ADB Interface" in dev man and disable it.
Without unplugging the op3 use the buttons to reboot into bootloader.
Hopefully W10 will now detect your op3 and either load the correct "oneplus" driver or create a new entry in dev man of Other Devices > Android Composite ADB Interface. Right click on this and then Update driver software > Browse my computer.... > Let me pick... > and if you're lucky One plus will show up in the manufacturer column and allow you to select the composite interface
Click to expand...
Click to collapse
I tried this but didn't see any new/different entry in DM when I rebooted into bootloader. Didn't see OnePlus under manufacturers either.

cyspak said:
Same here. When I reboot in fastboot mode, the driver adb interface disappears and I get the Android Bootloader Interface (Kedacom USB Driver).
"waiting for any device" each time.
Thx for help
Click to expand...
Click to collapse
Okay so this is the problem. I figured it out 2 days ago.
check the bootloader driver when you're in fastboot. Right click it and update driver, it should be the Android Bootloader 9.00, and not Bootloader 11.00
it's a silly weird fix, but it should be under Android and not Kedacom
I was using the Android SDK Studio Platform Tools and Google Drivers provided from SDK Studio

deleted

Similiar to the previous users post I'll try and be a bit more clear.
unplug your device if plugged in.
boot in to fastboot mode on your device.
Go to your PC and access device manager
plug your device in and you should see
"kedacom" instead of android interface
now inside you wanna click update driver
browse my compute for driver software > let me pick from a list of driver software > "Android adb sooner interface"
if its not that exact one check for the one that does say adb interface.
https://www.youtube.com/watch?v=Gdl6P2akRK0

I created a bootable USB drive with Linux Mint to solve my problem. It was Windows 10 that would recognize my OnePlus 3 in "Fastboot Mode" with Kedacom drivers.