I activated Developer Options" and check "USB debugging". I installed google usb driver on sdk.
But still Android studio doesn't recognize my mobile (one plus one).
I tested my mobile on my friend's laptop, it works. Also my android studio recognises Samsung when I install drivers.
But it doesn't recognize one plus one and nexsus.
Do you have any suggestion?
As I said in comment above, when I wanted to debug my app with my OPO today I got the same problem, after moving around to figuring it out, I found out it was because of ADB Driver (which for some unknown reasons got uninstalled from my system).
At first, check you Device Manager, if you see a yellow mark beside your phone, it is absolutely because of ADB Driver, so follow the steps below to install it:
Install the latest Samsung drivers: SAMSUNG USB Driver v1.5.33.0
Restart the computer (very important)
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Select ADB Interface from the list
Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yes to continue.
Done!
Hope it will help you.
More on this
-Enable developer mode and usb debugging on OPO
-Open Android SDK manager either from Android Studio or the directory the SDK is saved in.
-Tick Google USB Driver and click ok to download
-Connect OPO
-Open Device Manager
-OPO should show as unknown device
-Right Click on it
-Update or install driver
-Select from list
-Android ADB Interface
-Click ok
Information from this link OnePlusOne helped me to resolve the Chrome://inspect device not detected - Authorize popup prompt issue
Phone: One Plus One
OS: Cyanogen Version 13.1.2
Content from the link is added here :
Quick guide:
Pre-requisite : Download Google USB Driver from here
Connect your device with Android Debugging enabled to your PC
Open Device Manager of Windows from System Properties.
Your device should appear under 'Other devices' listed as something like 'Android ADB Interface' or 'Android Phone' or similar.
Right click that and click on 'Update Driver Software...'
Select 'Browse my computer for driver software'
Select 'Let me pick from a list of device drivers on my computer'
Double-click 'Show all devices'
Press the 'Have disk' button
Browse and navigate to [wherever you have extracted the downloaded file]\google-usb_driver and select android_winusb.inf
Select 'Android ADB Interface' from the list of device types.
Press the 'Yes' button
Press the 'Install' button
Press the 'Close' button
Now you've got the ADB driver set up correctly. Reconnect your device if it doesn't recognize it already.
For One Plus Phones, here is what I did and it worked. I use a One Plus 7T Pro. Before you begin, ensure Android Studio is up and running.
Go to Settings > System > Developer options.
Under Debugging, Tap on Revoke USB debugging authorisations and Tap on Ok when prompted
Switch Off the Developer Mode and Switch it back On
Switch On the Stay Awake option (if you need it)
Under Debugging, Switch On USB debugging option
Remove the USB cable from your device and reinsert it. On the device, you will be prompted to Allow USB debugging for your device ID. Tap on Allow
You should now be able to see the device detected in Android Studio.
This should work for all devices of different brands that are not automatically recognised in Android Studio.
For me the issue was in wrong USB file type transfer "Default USB configuration" option.
It was set to "No data transfer" and I needed to set it to "PTP" under
For me it was much simpler then that:
Under Developer Options
Enable developer mode and usb debugging
Under Debugging subcategory
Enable Android debugging
And my device showed right up on Android Studio 2.2 deployment target dialog.
** Android version 6.0.1
** Cyanogen OS Version 13.1.2
The previous answers didn't work for me. But following the advice from here helped me resolve the issue.
I have provided the steps I followed, but they have been lifted stright from the above link and all credit goes to them. There were a couple of deviations I had to take to make it work which were:
step 9 showed ADB device which I clicked
step 13 shows ADB didnt work but device mamanger now picks up the device and so does VS
Setup ADB & Fastboot Drivers
Step 1. To get started, download the 15-second adb/fastboot installer here and run the file on your windows desktop.
Step 2. Press Y/Yes to install ADB and Fastboot drivers and follow all the steps to continue the driver installation. Once completed you will see fastboot/adb folder on your C drive (C:\adb).
ADB-Installer
Step 3. Now the Files are installed on your desktop, next step is to configure them and setup the drivers.
Step 4. Pick your phone up and go to Settings > About Phone and tap on Build Number 7 times until you’ve enabled Developer Options, then go back to the main settings menu and go to Developer Options that magically appeared right above About Phone. And Enable Android Debugging / USB Debugging mode.
Step 5. Now connect your phone to the PC with USB cable and open Device Manager and look for your phone. It will show up under Portable Devices as your phone model number or Other Devices or ADB Interface or Android. See the screenshot below:-
ADB-Interface
Step 6. Right-click on it and select update driver software.
Update-Driver-Software
[wpsm_ads1]
Step 7. Now new popup windows will appear on your screen. From here click on the “Browse my computer for driver software”
Browse-Computer-For-Drivers
Step 8. Now from the next screen click on the “Let me pick from a list of device drivers on my computer” and hit the next button.
Let-Me-Picks-Drivers
Step 9. From the next screen click on the “Android Device” option and hit the next button to proceed.
Android-devices
Step 10. Now on the next screen you will see all the ADB drivers that are installed on your windows. Here select the “Android ADB Interface” and click on the next button to complete the setup process.
ADB-Drivers-Setup
Step 11. ADB Drivers are now properly installed. To check it is working or note. Go to the ADB folder on your C Drive which the installer created on Step 2.
Step 12. Connect your phone to the PC and open a command window in your fastboot/adb folder (C:\adb). To do this Hold Shift button on your keyboard and right-click on the empty space of the folder. See the screenshot:-
ADB-FIles
Step 13. Now the command prompt windows will appear on your desktop. And enter the following command and you will see the screen with a list of devices attached. This means the drivers are properly installed and your android is successfully connected to the window PC.
adb devices
So I want to use my new Nexus 5 for debugging my apps.I tried to install the Android USB driver via the device manager
But my nexus is listed as portable device and uses the default windows driver.How can I replace the windows MTP-USB driver with the android driver?When I click update driver software und select "\sdk\extras\google\usb_driver", it tells me that the driver software is up-to-date.
Edit:
USB Debugging is already activated
Edit 2:
Sorry my fault there are actually two Nexus 5 in my Device Manager. The other one accepted the android driver.
First you'd want to make sure you device is in 'debug mode' or 'usb debugging' - set through development settings in your phone's 'system settings'
then run adb devices from your adt-bundle folder/platform-tools to see if it got your device.
Edit:
if it doesn't work try, from your 'drivers' tab-
Update Driver -> Browse for driver software on my computer -> Let me pick from a list of device drivers from my computer -> Have Disk -> Navigate to your usb_driver folder
Notice the extra step near the end, you don't submit the folder in the "Browse for driver software on my computer" tab
download this usb driver: http://dlcdnet.asus.com/pub/ASUS/EeePAD/nexus7/usb_driver_r06_windows.zip
go to the device manager , right click the nexus device and choose properties, choose "hardware" and then choose update your driver , choose manualy and pick the folder you opend the zip file to and press apply.
open your setting in nexus . go to : "about the device" , at to the bottom of the page and press it strong text7 times .
open the developers menu and enable debug with usb.
finally press storage from the setting menu and click the menu that apears at the top left corner. press the connect usb to the computer, choose the second option (PTP).
that should do the trick.
The way I got the drivers installed for my nexus 5 was by following these instructions but I had to turn off my phone and do the steps below but for following the first set of instructions for the link below:Nexus 5 Driver installation instructions
power off your phone.
press and hold Volume Down and Power buttons simultaneously
- an Android robot will show up and the Fastboot Mode text is listed.
connect the Nexus 5 to your PC via USB Cable.
After doing this the drivers installed but had a yell warning sign. However I was still able to get it to take commands and for it to be seen by the ADB devices command. I currently am using windows 7, and I have the adb setup in my environment variables so I can run commands from the command line.
In the command line before you call the adb devices, make sure you navigate to the android platform tools folder '\Android\android-studio\sdk\platform-tools then from here call the adb devices and you will know for sure if your device is being detected!
Just to highlight the key step that solved the problem for me using a Nexus 5.
Follow the steps by Neeraj, just replacing the first one by the drivers in http://developer.android.com/sdk/win-usb.html
Key point is to make sure you change the usb connection to use PTP and try to install the driver from the Nexus 5 under other devices.
That solved the issue for me.
Another related issue:
Every time you connect a device through USB 3.0, Windows 7 automatically installs its own drivers that can't be updated. Removing them does nothing, as they will just be immediately installed again upon reconnection.
To get get around this, you need just need to use a USB 2.0 slot.
To allow usb debugging for an lg f60 d390 in Android Studio I had to install LG PC Suit.
I had same issue, Uninstall the existing driver. Then your device will be listed under Android Device -> Composite ADB interface in device manager. You then can follow steps to update the Google - USB driver.
This answer worked for me.
Switch the USB port you use.
For whatever reason once I did this Windows recognized my device.
I am attempting to install an Android app on my brand new Nexus 10. I have a .apk file. I have downloaded the Android SDK, installed "Android SDK Tools", "Android SDK Platform-tools", and Google USB Driver. I have checked the setting on my Nexus 10 for "Unknown Sources".
When I run "adb devices" from the command terminal, it doesn't list any devices. I attempted to follow this recommendation, because it was identical to a suggestion I had previously found here on Stack Overflow. After following those steps, "adb devices" still returns an empty list and to make it worse, when I connect my Nexus 10 to my PC, Windows doesn't show any folders within the device.
I have undone the steps in that link, along with everything else I have done so far, as well as uninstalling my Nexus 10 from Device Manager and reinstalling it, but I am still not seeing any folders in the device.
Is there anything I am missing to get my device to show up in ADB devices?
What can I do to get Windows to see the folders within the device?
Windows 8 wouldn't recognize my Nexus 10 device. Fixed by Setting the transfer mode to Camera (PTP) through the settings dialogue on the device.
Settings > Storage > Menu > USB Computer connection to "Camera (PTP)"
For Windows 8 users:
After trying every solution given here, with no success, I found this:
Go to Device Manager
Browse my computer for drivers -> Let me pick from a list of device drivers on my computer
Choose Android Device and then Android ADB Interface.
Now I have my devices listed at adb devices.
This situation seems to arise with some ADB drivers. I have encountered the same thing with a couple of Google devices and installing the Universal ADB windows driver has fixed it for me every time.
Use another cable.
Just found out that one of my regular charging cables had Vcc, Gnd pairs, but no Data+, Data-.
https://en.wikipedia.org/wiki/USB#Pinouts
Make sure to Enable USB debugging in Settings -> Developer options
Also, run "adb devices" after getting into the platform tools folder in the Android SDK (unless you have that folder on your system path already), otherwise the command won't be found.
The device may not be visible for debugging if it is in MTP mode. Some devices only work in PTP mode (or even in "charging only" mode).
This can be changed in Settings > Developer Options > Networking > Default USB configuration > PTP.
Also, you'll get a notification on your android device asking you for confirmation about USB configuration setting change and to allow it.
Note: You can turn on developer options by following the link below:
enable developer options
I have found a solution (for Windows 7):
Connect your Nexus 10 to PC
Go to Windows Device Manager
RClick on ADB Interface -> properties
Details -> Hardware Ids.
You will see two records like these:
USB\VID_18D1&PID_4EE2
USB\VID_18D1&PID_4EE2&MI_01
5 Open the android_winusb.inf file (I have it in "C:\Users\<username>\AppData\Local\Android\android-sdk\extras\google\usb_driver" directory)
6 Create such records in [Google.NTx86] and [Google.NTamd64] sections using Hardware Ids from properties of ADB interface:
;Google Nexus 10
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
7 Save the file, and update driver for ADB Interface with showing the path to "C:\Users\\AppData\Local\Android\android-sdk\extras\google\usb_driver" directory
Sometimes ADB loses connection to the device, and needs to be reset. If you have everything else working (ie USB driver installed, Developer settings enabled on the device), and still can't see your device, you need to reset the ADB process.
This is available in the DDMS Perspective (from within Eclipse), Devices tab (the triangle on the far right includes a menu item to perform the reset).
Otherwise from the command line, you can reset it with the following 2 commands:
adb kill-server
then
adb start-server
Enable Developer options in your device. To enable the developer mode, setting->About phone, tap Build number option 8 times continuously
Go to Settings-> Developer options and Turn on USB debugging
From the above steps it didn't work try this step, Go to Settings->Security and turn on Allow Unknown Resources
You have to download the drivers from the SDK manager (extras → Google USB Driver)
Then you have to install the USB driver in Windows (it works for me in Windows 8.1):
(Copy and paste from http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver:)
Connect your Android-powered device to your computer's USB port.
Right-click on "Computer" from your desktop or Windows Explorer, and select "Manage".
Select "Devices" in the left pane.
Locate and expand "Other device" in the right pane.
Right-click the device name (such as Nexus S) and select "Update Driver Software." This will launch the "Hardware Update Wizard".
Select "Browse my computer for driver software" and click "Next."
Click "Browse" and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.)
Click "Next" to install the driver.
After downloading the Google drivers via Android SDK Manager (available via Eclipse, Intellij or Android Studio), I had to update the driver in Computer Management > Device Manager > Other Devices > ADB - right clicking and clicking on update driver and browsing for updated driver finally did the trick.
BTW, a total nightmare for me as well. I continue to be bewildered that setting up a dev environment should be the most difficult task imaginable, with each new inexplicable failure leading to another one. Jeesh! Good luck.
On my Windows 8.1 64bit (Nexus 5 did not show up), only manually installing the USB driver fixed it:
http://developer.android.com/sdk/win-usb.html
The "Google USB Driver" in "Android SDK Manager" was installed already.
I still get this once in a while and it usually works if I unplug it and plug it back in a different port. I'm on Linux but had the same thing happen on Windows before.
Installing Samsung Kies and using their tool to reinstall device drivers, is what finally worked for me with my Galaxy S3 and Tab S 8.4
Normally SDB will download the driver in the **android-sdk-windows\extras\google\usb_driver** path
Here are the steps that worked for me:
Enable USB debugging.
Do to device manager, right click on ADB device and click update driver software.
Select "Browse my computer for Driver Software"
Select "Let me pick from list of Device drivers on my computer"
Click on "Have Disk" option.
Select the driver path **android-sdk-windows\extras\google\usb_driver** (path of sdk)
7.Select 1st driver out of list of drivers shown.
And hopefully, it will work.
Edit: I recommend you DO NOT run ADB under VirtualBox if you are using a Windows Host. Somehow I got VirtualBox to lock the device drivers on the host, eventually making it so that the ADB wouldn't work on the client nor the host for any device I plugged in. To fix, I removed VirtualBox extensions on the host and ran http://www.nirsoft.net/utils/usb_devices_view.html to delete the incorrect drivers. I could not get the correct drivers to load while VirtualBox extensions were installed, and this problem was a complete bastard to diagnose and fix.
Edit 2: Also the following is probably out of date, now that Google have released an integrated ADB extension for Chrome.
What an installation nightmare... Here are the steps I needed to get my Nexus 10 recognised on an XP virtual machine running under VirtualBox:
If you get asked to install Nexus 10 drivers, make sure to untick "don't ask again" (you WANT to be asked again!).
Plug in the Nexus 10 USB connection
Turn on debugging in the Nexus 10 settings Developer menu (tap "About Tablet" 7 times to get that menu).
In your virtual machine settings (host), add the samsung Nexus 10 device to the USB Device Filters (important - selecting it from the devices menu didn't seem to work).
In guest install java jre (if you don't have java installed). In Control Panel, change Java settings so that java doesn't run in the browser (to help prevent security issues).
In guest get the adk zip file and put it somewhere permanent. I needed to delete the .android config directory from the user directory because I moved the directory.
Run the SDK Manager.exe - if it doesn't work, try running sdk\tools\android.bat which seems to give better error reporting.
From SDK Manager install the Google USB driver package.
Unplug the Nexus 10 and plug it in again, and install the Google USB driver package.
Restart the guest.
running c:>[...]\sdk\platformtools> adb devices finally shows me the device...
For the Blu Studio 5.5s ADB drivers, you have to go through this hoop. I am certain it is the same with all Blu phones or maybe for all non-Google mfg phones, I am not sure. First of all if you connect the Blu device with USB cable and USB Debuggin off, you will see that Windows 7 loads a generic driver for you to copy on/off files to the phone and SD storage. This will appear when the USB cable is first plugged in and appears as a device icon under Control Panel, Device Manager, Portable Devices, BLU STUDIO 5.5 S (or the device you are working with). Do not bother getting the hardware ID yet - just observe that this happens (which indicates you are good so far and don't have a bad cable or something).
Go to the phone and switch on USB Debugging in the Developer section of your phone. Notice that an additional item appears as an undefined device now in the device manager list, it will have the yellow exclamation mark and it may have the same name of the phone listed as you saw under Portable Devices. Ignore this item for the moment. Now, without doing anything to the phone (it should be already in USB debug mode) go back to the Portable Devices in Device Manager and right-click the BLU STUDIO 5.5 S or whatever phone you are working with that is listed there without the exclamation mark (listed under Portable Devices). Right click on the icon under Portable Devices, in this example the name that appears is BLU STUDIO 5.5 S. On that icon select Properties, Details, and under the pull down, select Hardware IDs and copy down what you see.
For BLU STUDIO 5.5 S I get:
USB\VID_0BB4&PID_0C02&REV_0216&MI_00
USB\VID_0BB4&PID_0C02&MI_00
(Note if you do this out of turn, the HW ID will be different with the phone USB debugging turned off. You want to copy the value that it changes to when the USB debugging is ON)
Now do as the instructions say above, of course customizing the lines you add the the INF file with those relating to your own phone, not the Nexus 10. Here is what to customize; when you downloaded the SDK you should have a file structure expanded from the ZIP such as this:
\adt-bundle-windows-x86_64-20140321\sdk\extras\google\usb_driver
Find the file named: android_winusb.inf in the usb_driver folder
Make a copy of it and name it anything, such as myname.inf
Edit the myname.inf and add the lines as instructed above only modified for your particular phone. For example, for the BLU STUDIO 5.5 S, I added the following 2 lines as instructed in the 2 locations as instructed.
;BLU STUDIO 5.5 S
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&REV_0216&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_00
Note that you add these lines to both the 32 and 64 bit sections, matching how the example in the tutorial reads.
Now go back up to the unknown device that appeared in Device Manager when you switched on device USB debugging and right click on this item (has yellow exclamation mark), right click on it and then select Update Driver Software, and then Browse My Computer, Let Me Pick, click on the Have Disk button and browse to find the myname.inf. Continue to agree to all the prompts warning you it might not be the right driver. As the final step, Windows should have identified the device as Android ADB Interface and once that is done, you should be able to go back, open your CMD window and run the command "adb devices" as instructed in this tutorial and now you should see that the phone is now discovered and communicating.
Now you can go have fun with the adb command.
At first Thanks #rmsyk's post.
For my issue and after long time suffering with Meizu C9 Pro witch require just android ADB drivers (no special drivers) referring to manufacturer and it solved in my Windows 7 PC by the bellow steps.
Make Sure to
Install latest version of ADB & Fastboot with the needed drivers.
Enable Developer options & USB Debugging.
Enable Media File Transfer (MTP Mode).
Manually replace C:\Users\USERNAME\.android with the folder included here ,Then kill process 'adb.exe' if found from Windows Task Manager and use adb devices and finally my device listed successfully and just confirm the PC as trusted.
Notes:
Android Studio was uninstalled in earlier time and also i tried to reinstall but was not a solution at all.
Tried adb kill-server & adb start-server but was not a solution too.
As well as the usual settings (enable USB debugging) I also had to select Enable OEM unlock in the Developer options.
This supposedly makes the device less secure, but it's your device and you know what you want to do.
Once checked the device behaved as expected and appears in the adb devices list.
You can always reverse all these settings once you're finished.
Confirm you have the correct platform SDK tools
For Windows 10, had to manually download the latest platform SDK tools from Android as the version supplied through Visual Studio 2017 EMDK for Xamarin was not sufficient. Everything else except adb.exe devices worked.
https://developer.android.com/studio/releases/platform-tools
After the platform tools were manually downloaded, device showed up regardless of USB configuration (charging, MTP, etc.)
Installing an emulator device at this stage is also helpful to see whether the problem is with adb or your physical device.
List of devices attached
12345D1234 device
emulator-5554 device
There could be two reasons why adb devices command is not working for you. Either your phones USB drivers are not installed properly or you have not enabled USB debugging mode.
I created a tool that makes installing USB drivers a one click thing.
Just connect your phone in USB debugging mode to PC.
Run my tool
It will detect and install drivers specific to your phone and also install the latest ADB & Fastboot binaries with it.
The tool is available at my GitHub Repo
It's so easy, just turn off your Android device, and then hold down both "Volume Down" key and "Power" at the same time. Wait a few seconds till it start in recovery mode, done.
Now type adb devices, and you'll see your device.
I had the same problem with my Windows 8. The Android/SDK USB driver was installed correctly, but I forgot to install the USB driver from my phone. After installing the phone USB driver ADB works fine.
I hope this will help.
Turn on debugging in the Nexus settings Developer menu (tap "About Tablet" 7 times to get that menu).
Freaking Google tricks!
Have you had an android update recently? I updated to Lollipop and all the sudden I had no adb devices. Boo! I spent awhile trying a few things to no avail. Then I went into my developer options and lo and behold, "USB debugging" had been turned off. Silly Google. After turning it back on, it immediately showed up and I'm back in business!
GoTo DeviceManager, then right click on the android device and click uninstall driver.
Unplug and plug the device back...then a pop will come on your device while your pc installs the required drivers. Click "allow" on the popup.
You can see your device when you type "adb devices" in command prompt.
For Windows, just end all the processes related to Blue stacks or any such emulator if you are using.
Worked for me.
There's obviously a ton of different problems that could be causing this (and a ton of different solutions to go along with those problems). So think about all the solutions!
If you've gotten this phone and computer pair to work together before, but they aren't working any more, it might be a specific program on your computer rather than a problem on your phone. Some programs install/use their own adb, and only one of these can connect to your phone at a time. I think this makes a race condition, so sometimes it'll connect fine.
Some programs that run adb:
HTC Sync Manager - uninstall this.
chrome://inspect - lets you view localhost on your phone. Just close the window when you're done with it.
To have ADB in MTP mode
If you don't find any ADB device (nothing with exclamation mark) in the device manager (with all developers settings on phone checked), do this:
In Device Manager :
UpdateDriver->Manuel Install->Search on my computer->Select from installed driver list -> then select the one with the word usb in it (not MTP).
Edit: after that, you'll then have 2 or 3 peripheral, one for USB and one for ADB, install adb driver using usual method (see first answers)
For my Nexus 6P downloading drivers from Google helped resolved the issue. Here is the URL with documentation. And here you can download the driver itself.
P.S. I saw some people advice to download some drivers from random places on internet. While this might help it's too dangerous in my mind to download unknown drivers from unofficial places. So the one from Google worked well for me :)
I have installed Windows 8 release preview
and I cant install android USB drivers, it says this:
and
"the third party INF does not contain digital signature information"
what to do?
Disable device signature confirmation on Win8 and follow the guide here. www.androidsim.net/2009/08/how-to-1-how-to-install-usb-driver-on.html
I had the same issue a while ago. Seeing that the USB driver hasn't been updated since, the simple (and probably unsatifying) answer is revert back to windows 7. I've seen some scetchy drivers around but not for your device.
Windows 8 is still in preview/developer stage and I doubt we'll see proper drivers until it's closer to release. Just keep checking the SDK Manager and try again when the USB driver has an update.
Disable driver signing
Run Command Prompt as an administrator
Paste and run the following commands:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
or:
Win+c => parameters => Shift + restart and then like a links below...
http://windows.microsoft.com/en-us/windows-8/windows-startup-settings-including-safe-mode
http://www.fotoclubinc.com/blog/how-to-disable-driver-signature-enforcement-to-allow-installation-of-windows-7-printer-drivers-on-windows-8/
I had the some problem, and this how I fixed it.
On windows 8, Hold any SHIFT on your keyboard and Click Settings on the right corner of your PC or laptop, than the Menu bar of Settings will appear, than click Power, than click restart
You will see the Choose an Option, than you choose Troubleshoot
Under Troubleshoot choose Advanced options, and Under Advanced options choose Startup Settings, than click Restart, than press 7. After your PC or Laptop restart your will be able to Install Android ADB Drivers or any Drivers
I hope this will help you too
BLU VIVO AIR had same issue. I blogged about getting the generic google usb driver to install here with step by step and no funny links or ads - http://www.devfish.net/post/2015/07/20/android-usb-adb-drivers-for-blu-phones-vivo-air.aspx . Windows 8.1 ....
Use a USB cable to connect the Windows PC and your phone .
Open up Device manager. You'll see the BLU VIVO AIR show up in "Other Devices" as unavailable.
Download and install the Google Generic USB Driver from http://developer.android.com/sdk/win-usb.html#top .
Note down and remember the location where you install the google driver to.
Right mouse the BLU VIVO AIR, select Update Driver Software…
Select "Browse for driver software on your computer"
Navigate to where you installed the Google USB Driver software
Select "Let me pick from a list of device drivers on my computer"
Select "Show all devices"
Select "Have Disk"
Navigate to where you installed the Google USB driver, select the android_winusb.inf file
In the Update Driver Software - VIVO AIR dialog select "Android ADB Interface"
Ignore the "Update Driver Warning" message.
You will now see the Android Device -> Android ADB Interface in Device Manager, and VIVO AIR will be gone from "Other Devices". You should now also be able to turn on things like USB/Mass Storage Mode on the phone so you can view files from Windows Explorer as well as debug to the device.