Develop Bugs

[Q] Can't get ADB to work, have tried everything

Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies

expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.

Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Hi Dave, thanks for the reply.
I definitely have USB Debugging enabled - I also am 100% sure that I have installed the hboot driver before (I did it when rooting for the first time ages ago), and can confirm this by booting into Bootloader and having "Android Bootloader Interface" appear as a known device.
Also, with the HBOOT-Driver, it lists the phone as "Android 1.0" when Unknown, whereas my situation lists "Android Phone" as the unknown device.

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Click to expand...
Click to collapse
Same here.

Have you added the environment variable for the sdk directory? It won't work if you don't.

Also.. install .. HTC Sync.. .and try.. and again uninstall only HTC sync.. and leave the HTC driver and try

I've had issues getting it working too and haven't quite figured out the sequence to get it to work. All I remember is the Android SDK drivers don't work, you need to use the HTC ones. You don't need to uninstall HTC Sync (try re-installing it though). You might then need to run update drivers on the unknown device for it to find them.
I can confirm that it does work with HTC Sync still installed. I sometimes find ADB devices takes a few attempts or restarting ADB to actually work.

vnvman said:
Have you added the environment variable for the sdk directory? It won't work if you don't.
Click to expand...
Click to collapse
Hi vnvman.
Thanks for the reply - I have indeed, my "PATH" value is as below:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\XviD MPEG-4 Video Codec 1.2.2 64-BIT;C:\Program Files (x86)\Common Files\Teleca Shared;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools
Click to expand...
Click to collapse
However, even if I cd in CMD to the platform-tools folder and run adb from there, no luck. ADB itself works perfectly, but it just doesn't recognize my phone.

bobsie41 said:
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Click to expand...
Click to collapse
Like some others users posted here, win 7 x64 is working for me without any problems.
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
Try to reinstall android sdk completely following this guide:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

Hi MatDrOiD.
Thanks for the reply, I'll give that a shot as well as try jhonybravo4u and Antcodd's ideas.
Appreciate all input. If I get it working, I'll be sure to update this post so that anyone else who might have this problem has a solution

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
What i meant is that windows 7 seems 64bit seems to cause more problems than any other windows os. I had a windows 7 64bit computer and after days of pratting about i managed to get it working now, further down the road, and a bit more knowledgable(i think!) i have a new more powerful windows 7 64bit machine and i can't for the life of me get it working.
I know run adb from my wifes vista laptop and had no trouble whatsoever in setting this up.

If u tried "everything", u better don't ask for more ;-p
Sent from my HTC Desire using XDA Premium App

It worked for me last time, but then I formatted my drive, and now can't get it to work for the love of god. Actually I can, but I have to change the driver every time Android phone pops up in the device manager using have disk.

[Q] ADB error device not found

Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance

JT-on said:
Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
Click to expand...
Click to collapse
To use ABD you need to be connected in recovery or a booted device.

nlooooo said:
To use ABD you need to be connected in recovery or a booted device.
Click to expand...
Click to collapse
Brilliant. Like you said, ADB recognized my device in both booted OS and recovery. However, I needed to be in recovery to push files to the system directory. Thanks.

You're welcome. You can push in booted device you just need to enable superuser rights in adb shell.
Sent from my HTC Desire using Flashes and Thunders

JT-on said:
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
Click to expand...
Click to collapse
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:

Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?

rmp5s said:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
Click to expand...
Click to collapse
You can't. Both the n4 and the n7 have their memorys formatted as ext4, partition type that windows can't access normally. MTP was the only sollution google had.

Phone isnt recognized in fastboot

Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.

crazyg0od33 said:
Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.
Click to expand...
Click to collapse
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.

andybones said:
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.
Click to expand...
Click to collapse
So just install and plug my phone in and the drivers will be installed?
Sent from my HTC6500LVW using Tapatalk 4

EDIT - that didnt do anything
Looks like I need to try something else...

crazyg0od33 said:
EDIT - that didnt do anything
Looks like I need to try something else...
Click to expand...
Click to collapse
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!

andybones said:
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!
Click to expand...
Click to collapse
My BMP is the same but my HTC Driver Installer is 4.0.3.001
Maybe I can find that other one and it will work for me

Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL

eL_777 said:
Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
-snip-
-eL
Click to expand...
Click to collapse
Yeah I'm going to try it out on my roommates laptop that only has samsung drivers and the ADB installed and see what happens. Can't reformat the PC cause it's my School desktop and I've got work on there.
Once my macbook pro comes back from repairs I'll use that though, since I've never had issues running adb commands on my mac

Found a soultion
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:

gald said:
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:
Click to expand...
Click to collapse
MPT USB Drive isnt one of my options
However I've found that it's microsofts USB3 drivers, which override the Intel ones.
I just got my macbook back from repairs and it has USB3 ports as well so I was worried it wouldnt work, but its working fine from there

I'm having this same problem and nothing I do is working. I even tried from another computer but had no luck. adb finds the phone fine but fastboot just won't work. This is keeping me from getting S-Off. Someone please help.
Edit: Nevermind I think the issue is that I'm using Windows 8.1

I'm having the same problem I'm windows 8 64bit...
I have a nagging feeling that it's pda net.. I need to look into it today sometime
Sent from my HTC6500LVW using xda app-developers app

ADB can't see my Swift

Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B

Bump - anyone? Bueller? Bueller?
B

finnfather said:
Bump - anyone? Bueller? Bueller?
B
Click to expand...
Click to collapse
If you're trying to root then see the method I added to the end of the ROOT thread (can't post link, new account).
In short, you can get directly into the flashed recovery without it going back to normal and getting over written first without needing to use ADB to send it back to recovery mode.
Just take the back off, then once you have flashed the crackling recovery: pull the battery.
Plug it back in with the volume down held and power the device on, holding volume down.
You'll get into the recovery and can install superSU.
Hope that helps.

finnfather said:
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Click to expand...
Click to collapse
I had the same problem on my Windows 10 that was upgraded from 8.1.
To fix it, I removed completely Android SDK and reinstalled it. For some reason this was the solution for me.
I tried the same things as you before that (except factory restore as it is a pain) and got the same results - no device listed.
As for Linux and OSX, the Swift got recognized without a problem.

finnfather said:
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Click to expand...
Click to collapse
Hi everyone,
@finnfather I think I have solved the issue. Today, I decided to manualy install (cm-12.1-YOG7DAS2FI) the latest cyanogen update as my phone didn't recive it as an OTA. I downloaded the zip package here and installed it through the atock recovery. And now, adb works! Also, this has fixed a few problems with themes. Now I can use helium! I hope this helps,
Jev

Hi
Windows 10, android sdk installed and google drivers.
Fastboot shows 8bce440 fastboot when fastboot devices is tried in cmd (admin priv) and "waiting for any devices"
ADB list devices is also empty.
Any help appreciated.

Have you installed the SDK after getting Windows 10 on the machine? For me removing and re-installing the SDK helped as it was placed there when I still had Windows 8.1 on my desktop PC. I know it is a pain but it helped me remove a lot of old stuff that just wasted space as well.
What do you get from Device Manager? It is also worth it to try different USB port.
Are you using COS or CM?

Pak0St said:
Have you installed the SDK after getting Windows 10 on the machine? For me removing and re-installing the SDK helped as it was placed there when I still had Windows 8.1 on my desktop PC. I know it is a pain but it helped me remove a lot of old stuff that just wasted space as well.
What do you get from Device Manager? It is also worth it to try different USB port.
Are you using COS or CM?
Click to expand...
Click to collapse
Hi Cheers for replying.
I have now tried it on Win 10 (clean install) win 8.1 (clean install) and windows 7 (clean install)
Reinstalled sdk on 8.1 and 10 twice but no joy. I cant see anything under device manager for it (in fastboot)
Under devices and printers it shows Android
Any help appreciated.
---------- Post added at 06:31 PM ---------- Previous post was at 06:25 PM ----------
adb_usb.ini could this help? I have tried creating a file manually. But no joy

In fastboot mode, it should come up as Marshall London Bootloader Interface under Device Manager. From Devices and Printers you can check what driver is currently installed when it's displaying "Android".
Windows 8/10 is very insistent on using verified drivers. You could try to uninstall the current driver and re-connect the device so that Windows can try to find the verified ones.
For me it automatically installed the fastboot drivers, although it wasn't fast enough and the Swift rebooted before the drivers were finished with installation.

No fastboot devices but can use adb devices.

Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks

I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

ELoTRIX said:
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Yeah me too, same ROM and PC OS. Very strange

CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10

But phone starts ok in OOS system?
If, yes, download TWRP 3.0.2.1 original & TWRP 3.0.2.1-19 modified. Put them in phone sd card. Download FLashify from Play store and flash recovery .img. Then go recovery to test if it works.
One of those will work.

inflames19 said:
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
Click to expand...
Click to collapse
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....

Thanks for the different solutions, I'll try it for myself.
But I'm still wondering why the unlock worked because there it used fastboot too

1
me too its says : Witting for devices !!!
Rom: OOS 3.2.7
PC: Windows 10

CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.

1
rpsgrayfox said:
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
Click to expand...
Click to collapse
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem

Since there are a lot of people complaining I think the problem is bigger than we think :/ My OP3 nor OPO are seen

CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Sir Mohd said:
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Click to expand...
Click to collapse
I'm sorry to hear it didn't work, I'd try to reinstall adb and fastboot then using Minimal Adb and Fastboot found in this thread http://forum.xda-developers.com/showthread.php?t=2317790

ELoTRIX said:
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Click to expand...
Click to collapse
Please tell us how you did That ,
Ty.

Sir Mohd said:
Please tell us how you did That ,
Ty.
Click to expand...
Click to collapse
I have just installed on my Windows 10, a Virtual Machine (VMware) with Windows 7 installed all driver oneplus 3 and adb+fastboot and it works

I have the same issue. Got my OP3 yesterday and have been trying in vain to get my Windows 10 install to recognise the phone in fastboot mode, but to no avail. I am unable to unlock my bootloader.

I think the problem is with Windows 10. My laptop did an update yesterday, I think that's the problem.

Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help

It appears to be an issue with Windows 10 drivers. I have used an ancient install of Xubuntu on an older EeePC in order to unlock the bootloader and flash TWRP and SuperSU. I've still had no luck getting fastboot to be recognised on Windows 10, though on Xubuntu, it is recognised instantly with no issues.

inflames19 said:
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
Click to expand...
Click to collapse
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u

Sir Mohd said:
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Click to expand...
Click to collapse
I'm not at my pc atm but I'll try my best:
If you plugin your op3 there will be a cd mounted with the setup for the driver.
I just installed this driver with the setup.exe (on a complete new instance of Windows 7).
After the installer was finished, I opened cmd.exe and could use adb and fastboot.