November 7, 2012 at 02:56 pm

Manual installation of ADB driver

  • Android Development
  • tutorial

And here an unpleasant surprise awaited me - either the native driver turned out to be crooked, or Windows, or a wire ... in general, the driver got up, the dispatcher Windows devices reported on the full performance of the device, but on request adb devices in the console, I received an empty list and, of course, it was not possible to test the application on a tablet.

I wrote a request to TeXeT support, they even answered me with a link to the driver itself, which, as I already saw, did not work. I started searching the internet for an answer and found a bunch different assemblies this driver and manuals, but still none of them started up properly, and even the native driver from the SDK did not become at all, which plunged me into despondency ... but not despair.

Here I decided to try my hand at writing drivers the good old method of scientific poke and opened the inf file of the driver. Hope gave me the understanding that the software part of the adb interface from the side of the tablet should be identical for all devices, and USB worked anyway. And so, after several unsuccessful attempts to manually edit the inf-file, I found a recipe for curing the seasoning of the inf-file so that it is installed and, most importantly, it works.

So let's get started.

Step 1. Download the driver. If you haven't already, open the Android SDK Manager, find the Extras section, check the Google USB Driver box, and click Install Packages. Everything is simple. Wait for it to load.

Step 2. Find the driver and make a copy of it in a separate folder. Go to the %android-sdk%\extras\google\ folder and you will see the cherished usb_driver folder there. Copy it somewhere, and there we will carry out further manipulations. In principle, you can also edit the "original", but I preferred to keep the original untouched for every fireman.

Step 3. Edit the inf file. In daddy, open the android_winusb.inf file and look for lines like this:
;Google Nexus One %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
Make a copy of these lines, replace Google Nexus One on the %your_device_name% for identification in the future and ... open the Windows Device Manager. We are looking for our device there ( Android, Android Composite ADB Interface or something like that). Open the properties of the device, the "Details" tab, select the item "Hardware ID" in the list and we see such a picture.

We copy the line that is most similar to the one shown in the figure (It is, in theory, just a little shorter), and paste it into our inf file.
;TEXET TM-7025 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
In %SingleAdbInterface% we delete the end of the line, as you can see, in %CompositeAdbInterface% we insert the whole thing. You probably don’t need to repeat everything twice, but I already have everything and I’m too lazy to experiment :)
We save (be careful - in some cases you need to run notepad with administrator rights, because in user mode you will not be allowed to overwrite the inf file).
Step 4. Installing the driver. Now that everything is ready, we return to the device manager and remove all previously installed adb drivers (if any). We update the list of devices and see our device without drivers. We open its properties and select "update drivers", select the installation from the folder, specify the folder with the corrected inf and start the installation - our driver is instantly located, but during installation it may swear about incompatibility with the question "should I continue, nasyalneka?". We continue. Everything, the driver is installed.
Step 5. Final. For accuracy, we do take out the USB port, wait until everything is detected, open the console (Win + R, enter cmd) and write adb devices. If everything went well, we see the coveted list item, indicating that adb now sees our device.


From now on, you can safely run eclipse and build programs, enjoying convenient automatic assembly, installation and debugging right on our device.

If the adb command does not work for you at all. Computer -> Properties -> Environment Variables. We are looking for the Path variable and at the end we add(in no case do we overwrite) at the end with a semicolon, and after the address of the folder where adb lives (usually %android-sdk%\platform-tools\). After a reboot it should work.
Sometimes adb does not start automatically at system startup. Start manually.

What was it?
In fact, everything is simple. For some reason (Windows mastday / progers have crooked hands / the Google inf file was written only for native Google devices / Higgs bosons ruined everything in your computer), Windows does not want to eat the Google driver for non-Google devices that are not recorded in the inf file. Apparently, everything there is just tied to these ID equipment. But after all, the software part on the vast majority of Android devices is identical in terms of the debugger connector to the PC, so the driver should communicate normally with any Android device. Our task is to deceive Windows and make it accept the device as a "suitable driver", which we did by adding its ID to the driver's inf file.

I hope this manual will help someone to get their own Chinese or other device, for which they forgot to make a normal adb driver when assembling the system, or for those who need to download the official driver from the device manufacturer (this can be so hemorrhoids that it’s faster to do all of the above - it happened to me with the driver for the LG E510 phone).

P.S. I didn't do mass testing this method, so I can't guarantee that it will work 100% in all cases. But it worked for me on Windows 7, and after that on Windows 8. The file had to be edited for each time separately, but I don’t think that this is such a problem.

Universal ADB Driver (UAD) is a GUI based application that allows you to quickly install the Google ADB Driver on your Computer in a few Clicks only.

Here, we have tried to share the latest version of Universal ADB Driver along with the previous releases. If you are searching for Drivers for your Android device then this is a treat for you.

Features of Universal ADB Driver

Quick Installer:

It allows you to quickly install the Google ADB Driver in a few seconds only. Simply connect the device to the computer and run the Universal ADB Driver Setup and follow the screen instructions.

Supports every Device:

It supports almost every Android Device, whether it is from Major brands like Samsung, HTC, Sony or from Minor brands. It automatically detects the chipset of your device and install the driver accordingly.

Detects Manufacturer & Model:

It automatically detects the Manufacturer name and Model Number of your device and shows it under the Manufacturer and Description List.

Refresh Button:

It allows you to quickly refresh the device list that is attached to the computer. This feature is introduced in version 2.0 and is not available in version 1.0.

Supports Windows x86 and x64 Bit:

It automatically detects the BITs of you computer and allows you to install the ADB Driver on Windows XP, Vista, Windows 7, Windows 8, Windows 8.1 and Windows 10 easily.

Readme Once :

[*] Compatibility: It supports Windows Computer only, including Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1 and Windows 10.

[*] Support Nokia and Amazon: It supports Nokia devices including Nokia X, Nokia XL Series. It also supports all the Amazon Devices.

[*] How to Install: If you want to learn How to install the setup then head over to the Page.

[*] Best Alternative: Although Universal ADB Driver is perfect in all sense, but there is a great alternative available, called . Beside installing the adb driver, it also install the fastboot files on your windows computer.

[*] Credits: Universal ADB Driver is created and distributed by universaladbdriver.com. So, full credits goes to them for sharing the Driver for free.

Android Firmware

Choose your device 5Star Adcom Advan AG Mobile Alcatel Ambrane Amoi Archos Arise Bassoon Bedove Blu Bluboo Boss Style BQ Bsnl Byond Celkon Champion Cheers Cherry Colors Coolpad Croma Cubot Datawind Dexp Digiflip Elephone Eurostar Evercoss Fero Fly Gfive Gionee GoodOne Gplus Haier Hdc Hello Hitech Hotwav HSL Huawei iBall Infinix Infocus Innjoo Intex (Page 1) Intex (Page 2) Itel K-Touch Karbonn Kata Koobee Lava Leagoo Lemon Lenovo Lyf M-Horse M-Tech Magicon Malata Maximus Maxx Meizu Micromax (Page 1) Micromax (Page 2) Mobicel Mycell Nexus Obi Okapia Oplus Oppo Panasonic QMobile Rage Reach Salora Samsung Simmtronics Siwer Smile Soja Sony Xperia Spice SunUp Swipe Symphony Tecno Thl Tianhe Timmy Tooky Ubtel Ulefone Verykool Videocon Vivo Vodafone Walton Wellphone Wiko Winmax Winstar Wynncom XBO Xiaomi Xolo Xplay Xtreamer Yu ZD Real Zears Zen Ziox Zolo Zopo Zync

Choose your device 5Star Adcom Advan AG Mobile Alcatel Allview Amazon Ambrane Amgoo Amoi Archos Arise Asus Bassoon Bedove Blu Bluboo Bmobile Boss Style BQ Bsnl Byond Celkon Champion Cheers Cherry Mobile Cloudfone Colors Coolpad Croma Cubot Dell Digiflip Doogee Elephone Evercoss Evertek FireFly Fly Gfive Gigabyte Gionee Gmango GoodOne Grand Haier HCL Hello Hitech Hotwav HP HSL HTC Huawei Icemobile Infinix Innjoo Intex iPro Itel Karbonn Kata Kyocera Lava Leagoo Lemon Lenovo LG Lyf Malata Massive Maximus Maxwest Meizu Micromax Mito Mobicel Mobistel Motorola Mtech Mycell Nexus NIU NYX Obi OnePlus Oplus Oppo Orange Panasonic Pantech Philips Pipo Plum Posh Prestigio Qmobile Rage Rivo Samsung SKG SKK Smile Sony SPC Spice Symphony T-Mobile TCL Telego Timmy Toshiba TWZ Ulefone Uniscope Unnecto Uoogou UUK Verykool Vivo Vodafone Voicetel Vsun Walton WE Wiko Winmax Winstar XBO Xgody Xiaomi XMI Xolo Xplay YBZ Yezz YU Zen Ziox ZTE Zync ZYQ

ADB is not a program, but drivers for Windows 10. You need to download the file in order to not only introduce your PC and your smartphone to Android based, but also so that you have a convenient tool for rooting and getting full access to your mobile phone.

If you are wondering how to root your cell phone, then you are at correct page. No, here you will not find a program to carry out this procedure, but here you will get a convenient driver, without which you will not succeed. No matter how powerful and advanced the program for obtaining administrator rights on your device you have, you still will not be able to connect and get full access at the same level as you get after installing adb drivers.

We have already described the main task above. But let's take a closer look at exactly how you can use this product. Let's start with the basics - this package is not exactly what you need. This is a universal utility -. The utility will select necessary components and you don't have to do anything extra. If this idea appeals to you, then follow the following procedure:

  • Install universal ;
  • Connect phone;
  • Run component selection and install it.

Rebooting the PC is required only in the most extreme cases. But if Windows 10 asks you to, then of course, you have no choice but to agree. After all, until you restart, you will not be able to apply the changes that occurred during the installation process.

How to use adb drivers

Since this solution is not a full-fledged utility, which is, for example, Peers.tv or any other classic utility, you will not be able to use it. She has neither visual interface, no physical abilities. Why download it then? Everything is simple and exactly the same as in the case of any other drivers for your computer. You need to install them in order for everything to work as correctly as possible. And specifically in this case, so that your PC on Windows 10 normally picks up the phone or simply sees it.

Note that the ADB driver is free to download. This means that you do not need to pay money to those who sell a component for Windows 10 on a paid basis. Also, you do not need to select the necessary assembly depending on your OS, because the installation file is so versatile that it is suitable for both 32-bit and 64-bit systems. Also note that if he himself is in Russian, this does not mean that there is an ADB driver for your phone also in Russian. It is likely that it will be in English, because. this is the case with all popular phone models from XiAomi, Samsung, HTC, Sony and others.

Android Debug Bridge (ADB) is a console application that allows you to manage a wide range of functions mobile devices working on the basis operating system Android. The main purpose of ADB is to perform debugging operations on Android devices.

Android Debug Bridge is a program that works on the principle of " client-server". The first launch of ADB with any commands is necessarily accompanied by the creation of a server in the form of a system service called a "daemon". This service will continuously "listen" on port 5037 waiting for a command.

Since the application is a console application, all functions are carried out by entering commands with a certain syntax into the command line Windows (cmd).

The functionality of the tool in question is available on most Android devices. An exception can only be a device with the possibility of such manipulations blocked by the manufacturer, but these are special cases.

For ordinary user application android commands Debug Bridge, in most cases, becomes a necessity when restoring and / or flashing an Android device.

Usage example. View connected devices

All the functionality of the program is revealed after entering a specific command. As an example, consider a command that allows you to view connected devices and check the readiness factor of the device to receive commands / files. The following command is used for this:

adb devices

The response of the system to the input of this command is two-way. If the device is not connected or not recognized (no drivers are installed, the device is in a mode that does not support work via ADB, and other reasons), the user receives the answer “ device attached" (one). In the second option, - the presence of a device connected and ready for further operation, its serial number (2) is displayed in the console.

Variety of possibilities

The list of features provided to the user by the Android Debug Bridge tool is quite wide. To access the use of the full list of commands on the device, you will need to have superuser rights (root-rights) and only after receiving them can we talk about unlocking the potential of ADB as a tool for debugging Android devices.

Separately, it is worth noting the presence in the Android Debug Bridge of a kind of help system. To be more precise, this is a list of commands with a description of the syntax, displayed as a response to the command:

adb help

Such a solution very often helps many users to remember a forgotten command to call a particular function or its correct spelling

Advantages

  • A free tool that allows you to manipulate the Android software, available to users of most devices.

Flaws

  • Lack of a Russian-language version;
  • Console application requiring knowledge of command syntax.

adb Free download

The Android Debug Bridge is an integral part of the Android developer toolkit (Android SDK). Android Tools The SDKs are in turn included in the Android Studio Components Kit. Downloading the Android SDK for your own purposes is available to all users absolutely free of charge. To do this, you just need to visit the download page on the official website of Google.

The ADB and Fastboot utilities are part of the Android SDK (not to be confused with android studio and even more so download its cumbersome installation file, unless, of course, you are going to develop for Android). ADB is a debugging tool that allows you to access the Android console from a computer () by connecting the gadget to a PC via USB. At the same time, it should be. Fastboot is designed to work with the device when it is loaded in the mode of the same name (if there is one on your device).

With the help you can control your smartphone/tablet from your computer: backup apps, record a screencast, put your smartphone into recovery mode and much more. In addition, you can work with ADB over Wi-Fi. To do this, your device must be root-rights, and you will also need special application that connects to a computer over a network. For example, ADB Wireless either WiFi ADB. But this is material for a separate article.

Using Fastboot you can install firmware, ( or CWM ), unlock bootloader(on devices HTC, Motorola, Sony, , , the last it is blocked), clean up system partitions.

1. First of all, go to the official website where you can download the Android SDK: https://developer.android.com/studio/index.html. We go down the page to the section "" and select the download of the archive for Windows.

2. Check the checkbox " I have read and agree with the above terms and conditions” and press the button “

3. Download it and unzip it to the root of the Disk " C:».

4. You also need to download the Java Development Kit from official page. Go to the site, agree to the terms license agreement, ticking the box "", and download the JDK version corresponding to the bitness of your system.

First way

Go back to the Android SDK folder, open " tools" and run " android».

Check the box " Android SDK Platform-tools" (as well as " Google USB driver" if you have a Nexus device) and click " Install Packages».

Read about installing drivers for other devices below.

Select " Accept License" and press " Install».

My log showed that an error occurred during the installation process. But in the end, everything ended successfully.

After completing the above steps in the folder " tools_windows-version"," will appear, and it will contain the " adb" and " fastboot».

Second way

Go to the folder " sdk-tools-windows-version» → « tools» → « bin» and holding down the « Shift”, click right click mouse over an empty area. Select " Open command window" or "", if one of the latest is installed on the PC or laptop Windows builds 10.

Paste the command into PowerShell or the command line (in PowerShell, add ./ at the beginning):

Click " Enter' to execute the command. The files will download and you will be prompted to install:

To allow, enter y , i.e. " yes", and press " Enter', then the installation of '' will begin.

At the end, the command line will display a message that the procedure completed successfully. And the folder "" with ADB and Fastboot inside will appear in " sdk-tools-windows-version».

(!) If for some reason you cannot install ADB and Fastboot using the previous methods, use the third option - just download archive"" and unzip to disk " C:».

smartphone or tablet, you need to download the USB driver:
  • Samsung - the driver is included in the Kies utility: http://www.samsung.com/ru/support/usefulsoftware/KIES/ or you can download it separately by selecting the desired model: http://www.samsung.com/us/support/downloads
  • HTC - as part of HTC Sync Manager: http://www.htc.com/ru/software/htc-sync-manager/
  • Nexus - The Android driver is installed with the Android SDK, as described above.
  • Huawei - together with the HiSuite utility: http://consumer.huawei.com/minisite/HiSuite_en/index.html
  • LG - Install LG PC Suite: http://www.lg.com/en/support/software-firmware
  • Motorola - see this page: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
  • Sony Xperia - FastBoot drivers for all models can be found here: http://developer.sonymobile.com/downloads/drivers/
  • Xiaomi - Mi PC Suite: http://pcsuite.mi.com
  • MTK - for Chinese devices on MediaTek chips: http://online.mediatek.com/Public%20Documents/MTK_Android_USB_Driver.zip
  • Lenovo - select the model of smartphone, tablet and download the ADB driver: http://support.lenovo.com/us/en/GlobalProductSelector
  • Look for solutions for devices from other manufacturers on their official websites.

There are various universal ADB driver installers (for example, this one: http://adbdriver.com/downloads/) - they can also be used, for example, when for some reason it was not possible to establish an official solution.

If your model comes with a driver without an installer, you will have to follow these steps:

1. Go to " Control Panel» → « Device Manager". In Windows 10, just right-click on the menu " Start» and select « Device Manager».

2. Find the device for which you need to install drivers in the list. Right click and click " Update drivers».

As you can see, the computer correctly recognizes my Nexus 7 tablet. If your PC detects the smartphone incorrectly or there is a yellow triangle opposite the device with exclamation point inside, "manual" installation of Android drivers is a must for you.

3. Select " Search for drivers on this computer».

4. Specify the path to the folder with the drivers on the PC.

Wait for the installation to complete and then reconnect the gadget to the computer via USB.

Working with ADB or Fastboot is carried out from the command line, you can enter in two ways:

Method 1: Right click on " Start' and select ' Command line(administrator)". Next, using the commands, you need to go to the folder with ADB and Fastboot (after entering each, press " Enter»).

To return to the root of the disk " C:\", use:

cd /

Thanks to this team, we open desired folder:

cd

In my case it turned out like this:

cd \tools_windows-version\platform-tools

You will get ( Google Developers changed the name of the archive after the initial version of this instruction was written):

cd \sdk-tools-windows-version\platform-tools

The path to Fastboot and ADB is indicated, now we are working with them from the console.

To avoid doing these steps every time, add the path to "" to the variable " Path". First, go to the folder, in the navigation bar, right-click on "" and select "".

Go to " Control Panel". To do this, click " Win» + « R” and in the “Open:” field, insert . Click " OK».

Select " System» → « Extra options systems» → «».

Find the variable " Path”, highlight it and select “ Change…».

Click " Create", paste the path to the folder "" and click " OK».

2: Go to " sdk-tools-windows-version» → «», then holding « Shift", right-click on an empty space and select " Open command window" or "".

Type the following to check how the PC sees Android (in Windows PowerShell, insert ./ before the command):

adb devices

Don't forget that USB debugging must be enabled to work with ADB! More useful commands you will find in the last article, the link is at the beginning of this post.