In this document • • • • • See also • • If you are developing on Windows and want to connect a device for testing, then you need to install the appropriate USB driver. This page provides links to the web sites for several original equipment manufacturers (OEMs), where you can download the appropriate USB driver for your device. If you're developing on Mac OS X or Linux, then you shouldn't need a USB driver. Instead read. To connect and debug with any of the Google Nexus devices using Windows, you need to.

Aug 15, 2015. As far as I know there are no properly working ADB drivers for Windows 10. I usually use the universal ADB drivers from koush but that's not compatible either. I don't have the OP2 but my HTC One M7 and Nexus 10 are both unlocked and rooted, so I usually fiddle with ADB/fastboot on both devices. Oct 30, 2016 - 2 min - Uploaded by PAKFONESPlease watch: 'Motorola Droid Turbo Google Account bypass new Security 2016 [Part-2 Bypass.

Install a USB driver First, find the appropriate driver for your device from the table below. Once you've downloaded your USB driver, follow the instructions below to install or upgrade the driver, based on your version of Windows and whether you're installing for the first time or upgrading an existing driver. Then see for other important information about using an Android device for development.

Caution: You may make changes to android_winusb.inf file found inside usb_driver (for example, to add support for other devices), however, this will lead to security warnings when you install or upgrade the driver. Making any other changes to the driver files may break the installation process. Windows 10 To install the Android USB driver on Windows 10 for the first time, do the following: • Connect your Android device to your computer's USB port. • From Windows Explorer, open Computer Management. • In the Computer Management left pane, select Device Manager. • In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see. • Right-click the name of the device you connected, and then select Update Driver Software.

• In the Hardware Update wizard, select Browse my computer for driver software and click Next. • Click Browse and then locate the USB driver folder. For example, the Google USB Driver is located in android_sdk extras google usb_driver. • Click Next to install the driver.

Windows 8.1 To install the Android USB driver on Windows 8.1 for the first time, do the following: • Connect your Android device to your computer's USB port. • Access search, as follows: Touch screen: On your computer, swipe in from the right edge of the screen and tap Search. Using a mouse: Point to the lower-right corner of the screen, move the mouse pointer up, and then click Search. • In the search box, type into and then click Device Manager. • Double-click the device category, and then double-click the device you want. • Click the Driver tab, click Update Driver, and follow the instructions.

Windows 7 To install the Android USB driver on Windows 7 for the first time, do the following: • Connect your Android 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 android_sdk extras google usb_driver.) • Click Next to install the driver.

Or, to upgrade an existing Android USB driver on Windows 7 and higher with the new driver: • Connect your Android device to your computer's USB port. • Right-click on Computer from your desktop or Windows Explorer, and select Manage. • Select Device Manager in the left pane of the Computer Management window. • Locate and expand Android Phone in the right pane. • Right-click on Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.

• Select Install from a list or specific location and click Next. • Select Search for the best driver in these locations; uncheck Search removable media; and check Include this location in the search. • Click Browse and locate the USB driver folder. (The Google USB Driver is located in android_sdk extras google usb_driver.) • Click Next to upgrade the driver. Get OEM drivers OEM Driver URL Acer alcatel one touch Asus Blackberry Dell Fujitsu Hisense HTC Click on the support tab to select your products/device. Different regions will have different links.

Huawei Intel Kyocera Lenovo LGE Motorola MTK (ZIP download) Oppo Pegatron (ZIP download) Samsung Sharp Sony Mobile Communications Toshiba Xiaomi ZTE •.

Anyone that has ever tried to mod their Android phone has come across users telling other users to run various different ADB and/or Fastboot commands. The only problem is the average Joe has no idea what ADB and Fastboot are because, well, they aren’t your run-of-the-mill applications.

I was completely lost myself when I first ventured into the world of Android. While yes, developer hubs like XDA-Developers do provide instructions on how to get ADB/Fastboot installed, there are so many convoluted guides out there, it is easy to throw one’s hands up in defeat. Hopefully this guide makes it simple and straightforward to get ADB and Fastboot installed on your computer. What are ADB and Fastboot and why do I need them ADB stands for Android Debug Bridge, while Fastboot stands for, well, Fastboot. Without going into too many technical details (trust me you don’t want technical details), let’s just say they are two command-line tools used when modding/hacking Android phones. You need ADB and Fastboot if you are one of those people that like to mod/hack your Android phone. While many mods/hacks are now becoming more main-stream-user friendly with GUIs (i.e.

They no longer require users to use ADB or Fastboot), there are still times when users need to use ADB and/or Fastboot. (Anyone with a Google Nexus One or Nexus S knows what I mean.) While you may not necessarily ever use ADB or Fastboot (depends on what phone you have, and the type of developer support it gets), it is always nice to have them installed when the time comes that you do need them. BEFORE WE BEGIN In this guide, we will show you two methods on how to install ADB and Fastboot. The first method is the semi-automated method while the second method is the manual method. The first method is a easier to do and recommended for most everyone. If, however, you can’t get the first method to work or you prefer more control, then method 2 is for you. Keep in mind, after installing ADB and Fastboot, you need to ensure you have installed the proper Windows drivers for your Android smartphone or tablet on your computer.

You can download the Windows drivers for your Android smartphone or tablet from. How to Install ADB and Fastboot: Method 1 To quickly and easily install ADB and Fastboot on your Windows XP, Vista, 7, and 8/8.1 computer (32-bit and 64-bit), do the following: • Download the latest ( ).

• Right-click the file adb-setup-1.3.exe and choose “ Run as Administrator“. Iran021 Serial here. • Type “Y” and press Enter to install ADB and Fastboot, and set the environment variables. Enter “N” if you don’t want to do the same and want to just install the drivers. • In the next step, enter “Y” to install the drivers for your device. Enter “N” to skip this step. • Wait till the driver installation finishes up.

That would take only some seconds. • To verify that you have successfully setup ADB and fastboot, open up a command prompt (press Windows key + R ->type in cmd ->OK) and enter “ adb version” (without quotes).

If it returns something like “ Android Debug Bridge version x.x.xx“, then your ADB and Fastboot are all-ready. You are ready to rock! How to Install ADB and Fastboot: Method 2 To manually install ADB and Fastboot on your Windows XP, Vista, 7, and 8/8.1 computer (32-bit and 64-bit), do the following: The following guide is for Windows PCs only, but ADB/Fastboot can be installed on Linux and Mac OS X also. (You just do it differently for Linux/Mac OS X.) Also note that this guide was written on a Windows 7 computer. However, the guide will work on Windows 8/XP/Vista the same way; I don’t know about earlier versions of Windows. • (11 MB) ADB, Fastboot, and other tools.

• Note: The tools found in the download are provided by Google, found in. I have simply extracted the tools and uploaded them for easy access, instead of telling everyone to download the whole SDK. You can get the same tools if you download the Android SDK directly from Google. • Extract the contents directly into your C: partition. You should now have a folder C: Android that looks something like this: • Press Win + R on your keyboard to bring up the Run dialog. Csi Wealth Management Essentials Pdf Reader. • Once the Run box is open, type in sysdm.cpl and hit OK: • Once you hit OK, the System Properties panel should open; click on the Advanced tab: • From the Advanced tab click on Environment Variables.

• At the Environment Variables window find where it says Path under System variables, click on it, and click the Edit button: • When the Edit System Variable window pops up, type in;C: Android at the very end and hit OK: Make sure you type in exactly;C: Android (be sure to include the semi-colon at the beginning). • After clicking OK, close out all windows. You are done! Using ADB and Fastboot Once you have them installed, using ADB or Fastboot is as easy as opening command prompt, typing in adb xxx or fastboot xxx (with xxx being the command you want to run) and hitting Enter on your keyboard to execute the command.

Take note, however, installing ADB and Fastboot is not enough to start using it with your phones. You need to install the on your computer – so your PC recognizes your phone – before ADB or Fastboot will be able to work with it.

If you don’t have any drivers installed, you will get an error similar to the following: If you don’t have the proper drivers installed, read dotTech’s article on. Uninstalling ADB and Fastboot Uninstalling ADB, Fastboot, and the other tools is as easy and undoing what you did when you installed. In other words, delete C: Android and all the files in it and remove the environmental variable you added earlier. Conclusion You have installed ADB and Fastboot – now what? Now go look for guides on modding/hacking your phone.

A good place to start is reading dotTech’s. Another good place to look for Android hacking and slashing is. If you are lucky, the guides you find won’t require you to use ADB or Fastboot; but if they do, you are now prepared because you just installed them. Originally posted Jun 18, 2012.

Updated Nov 16, 2012 to include newer version of ADB and Fastboot. Updated Feb 3, 2014 to include semi-automated method of installing ADB and Fastboot. Installing the correct drivers are the biggest challenge with windows. Also, don’t forget to install the jdk. Here’s a quick doc that I recently wrote up which should help. Android Studio Installation Created by Greg O 1. Install Java JDK Windows: Run ‘jdk-8u40-windows-x64.exe’.

Note: this can be downloaded from Linux: Run command ‘sudo apt-get install openjdk-7-jdk’ 2. Install Android Studio Bundle Windows: Run android-studio-bundle-1-windows.exe Note: this can be downloaded from 3. SDK Manager Windows: Run Note: A USB driver is required for use on Windows only. Use Nexus Root Toolkit v2.0.4 for this installation. Please see instructions below. Linux: ‘wget ‘ Note: To start SDK Manager, ‘cd ~/android-sdk-linux/tools./android’.

Windows USB driver Installation Download the Nexus Root Toolkit v2.0.4 from. Run the Toolkit and follow the Initial Setup instructions. Note: On Windows 8.1 you need to enable ‘Test Mode’ to allow installing unsigned drivers 1. WinKey + C>Settings (Gear icon) 2. Change PC Settings. Update and recovery>Recovery 4.

Advanced Startup>Restart now 5. Troubleshoot>Advanced Options 6. Startup Settings>Restart 7. Wait for computer to restart 8. Select ‘Disable driver signature enforcement’. Now you can proceed to install these drivers. Well the command prompt in Windows starts where the cmd.exe file is located (in a normal case System32).

What you do is type “cd.” to go up to C: Windows and do it again to go to C:. Then you can do “cd Users”, “cd (your username)” then “cd Downloads” to get to the downloads folder. Basically navigating the command prompt is relative to its current directory (indicated by the “C: Windows System32 >” part). Running the adb.exe file will only work if you are in the same directory (I’m guessing Downloads in your case?). If you have a Debian (such as Ubuntu, Linux Mint, or Debian itself) based Linux OS, installation is pretty straightforward. Just open a terminal and type: sudo apt-get install android-tools-adb sudo apt-get install android-tools-fastboot After those two are done, you can readily use adb and fastboot commands, but keep in mind that you have to run the commands with root permissions (by either typing “sudo” before every command to run it with elevated permissions or typing “sudo su” once to log in to the terminal as Root).

Sorry for the digression. I rooted my Nokia X using SuperUser SU but after almost a month of usage, it doesnt look like my phone is rooted anymore because all root privileges are not granted as before. Whenever I opened SuoerUser app to check what could have gone wrong, a message will pop out that “there is no SU binary installed, and SuperSU cant install it.” It will then close immediately. Even trying to reroot the phone with the KingRoot file on the computer didnt work. It said the phone need/cant be rooted. Please help me out.

So i’m trying to put cyanogen mod on my HTC wildfire s. To do this i have to root it first. To do this i downloaded&installed the SDK (with the needed java) and i also got the HTC drivers and android_winusb.inf now i’m at the point where i use device manager. When i use it my computer still see’s my phone as HTC instead of ADB (even tho when i use command prompt and give the command “adb devices” i get a serial number). I tried to update the drivers anyway but that doesn’t work. My question: do you have any idea what i could try to fix this problem?

I have a PendoPad 10.1 inch, model PNDPP410GP, Dual Core Processor: 1.2Ghz, Cortex A9′ RAM 1GB, with Android 4.2.2 kernel 3.0.36. I would like to to update this Tablet to the latest Android version KITKAT 4.4 I’m totally new to updating Android versions. I’ve only just done some reading on this updating android topic.So far I understand that I need RUU file and that I need adb and fastboot, One web site suggests that this particular file is needed: RUU-DoDo Pendo Pad_One_GE-4.4-3.58.1700.5.zip So I have done a web search and used Mac OS to download this file: RUU Zip M7 Google Edition 4.4 3.58.1700.5 I have a Mac computer with OS X, 10.7 of which I could use to help update this android tablet. Can you help me with step by step instructions with a Mac system?

[@] I spoke too soon more searching I just found this: under the heading, Linux (New) Some Android tools (fastboot and adb) are available in distributions’ repositories and can be installed without downloading the entire Android SDK.* Haven’t tried it yet, hope it’s current, hope it works. Bodhi is an Ubuntu variant, so it may be promising. But Ashraf is the expert here, so any comments pro or con would be welcomed.

_____________________________________________________________ *Under Creative Commons License: Attribution Non-Commercial Share Alike •. Hi Ashraf, I would like to get adb and fastboot working on my 701SD netbook, running Bodhi Linux.

I am hoping you have a similar article to this one, showing your simplified installation method for folks who just want to run these utilities on their GNU/Linux systems, and and don’t have to, or want to, work with the full Oracle JDK. So far, everything I’ve read on other Linux boards tells the user to install the ‘full monty’ and I’d rather keep things ‘light’. Any ideas, or links to other sources?

Hi ashraf, sorry for posting in an old thread, but I need help. I have followed your directions — and also added adb_usb.ini to the directory with adb.exe, with an ID of 0x5D04 as its only line. But at the Windows Command Line, typing: adb devices is giving me only a blank line. I have installed the drivers from and now there are no yellow [!] symbols anywhere (before there were lots!). For the reference of others who read this, it is working for a M-Horse 9500mini, with a SC1820 chip. Any ideas, or other links, will be welcome — thank you in advance. Can anyone tell me,??

Why does adb show no devices?? For any users of Samsung Galax S, I installed Darky’s v9.2 Extreme Edition on mine last night, was a trial and error situation. First package I downloaded did not include his version of Odin, hence was waste of quite sometime locating and finding correct one. Not his fault, but mine, it has many of the Gingerbread features pre-installed, includes Voodoo, various root fixes, and so it goes. It is a real hoot, now the phone is working in a manner far better than the stock Froyo.

I am aware this is slightly off topic, but in conjunction with Ashraf’s guide, it works a treat. Anyone who is interested simply Google.

Hey Ash, was wondering your thoughts (that is if you know). Like in the post,, told you i got the Galaxy S Captivate. Right now, the only thing i can see somewhat “wrong” with it is that it is still using 2.1, Froyo 2.2 came out last year and AT&T was “supposed” to upgrade/update to 2.2 in Sept of last year yet they have yet to do so with 2.2, it gives me more options and is supposed to be faster and help eliminate some of the lag going between apps that 2.1 has. Well i made an acct on the XDA site and am reading up on it.

My question that maybe you know would be, what would be my best bet you think?? Do i need to Root it?? Should i look into a Custom ROM? Still learing, and I am guessing that I need to at least root it with that One CLick program and then get the Kies program and update it to 2.2 does this sound about right??

Or is my best bet maybe looking into a custom rom? All still new to me. Though i saw some posts about peeps with a captivate (though its over on the european side on Rogers (no posts for att so far that i saw just yet)) and they are sayin gthey seem to get more lag/slower OS after the upgrade and many have went back to standard install anyway. Figured ask your thoughts:) Other than upgrading to the 2.2, you know any other things i may want to do that would requiring rooting or even a custom rom?