Manual installation of the ADB driver. What are ADB drivers? Manual installation of adb drivers wind xp

Universal ADB Driver (UAD) is a GUI based application that allows you to quickly install the Google ADB Driver on your Computer in 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.

[*] Supports 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 Acer 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

• Tutorial

And here an unpleasant surprise awaited me - either the native driver turned out to be crooked, or Windows, or the wire... in general, the driver stopped working, the dispatcher Windows devices reported that the device was fully operational, but upon request adb devices in the console I received empty list and, naturally, 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 was already convinced, did not work. I started looking for an answer on the Internet and found a bunch of different assemblies of this driver and manuals, but still none of them started up properly, and even the native driver from the SDK didn’t work at all, which made me despondent... but not despair.

Here I decided to try my hand at writing drivers using the good old method of scientific poking and opened the driver inf file. What gave me hope was the understanding that the software part of the adb interface on the tablet side should be identical for all devices, and USB worked anyway. And so, after several unsuccessful attempts at manually editing the inf file, I found a recipe for treating the inf file seasoning so that it would install and, most importantly, work.

So let's get started.

Step 1. Download the driver. If you haven't already done so, open Android SDK Manager, find the Extras section, check the Google USB Driver box, and click Install Packages. It's 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 see the treasured usb_driver folder there. Copy it somewhere, and we will carry out further manipulations there. In principle, you can edit the “original”, but I preferred to keep the original intact just in case.

Step 3. Edit the inf file. In the folder, open the file android_winusb.inf 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_Insta ll, USB\VID_18D1&PID_4E12&MI_01
Make a copy of these lines and replace Google Nexus One on %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 device properties, the “Details” tab, select the “Equipment ID” item in the list and see this 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 line. There’s probably no 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. Driver installation. Now that everything is prepared, go back 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 found, but during installation it may swear about incompatibility with the question “should I continue, nasalneka?” Let's continue. That's it, the driver is installed.
Step 5. Final. To be precise, unplug 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 treasured list item, indicating that adb now sees our device.


From now on, you can safely launch eclipse and build programs, enjoying convenient automatic assembly, installation and the ability to debug directly on your 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 it) at the end there is a semicolon, and after that 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 when the system starts. Start manually.

What was it?
It's actually simple. For some reason (Winda is a must-have / progers have crooked hands / the Google inf-file was written only for native Google devices / the Higgs bosons have ruined everything on your computer), Windows does not want to use the Google driver for non-Google devices that are not recorded in the inf-file. Apparently, everything there is tied to these ID equipment. But the software 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 force it to accept the device as a “driver-compatible” device, which we did by adding its ID to the driver inf file.

I hope this manual will help someone 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 are bothered to download the official driver from the device manufacturer (this can be so annoying that it’s faster to do everything described above - This happened to me with the driver for the LG E510 phone).

P.S. I have not conducted mass testing of this method, so I cannot guarantee that it will work 100% in all cases. But it worked for me on Windows 7, and then on Windows 8. I had to edit the file separately for each time, but I don’t think that’s such a problem.

ADB and Fastboot utilities are included in the kit Android development SDK (do not confuse it with Android Studio, much less 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 your computer () by connecting the gadget to your PC via USB. At the same time there should be . Fastboot is designed to work with the device when it is loaded in the mode of the same name (if your device has one).

Using this you can control your smartphone/tablet from your computer: make a backup of applications, record a screencast, put your smartphone into Recovery mode and much more. In addition, you can work with ADB via Wi-Fi. To do this, you must have root rights on your device, and you will also need a special application that connects to your computer over the network. For example, ADB Wireless or 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 time it was blocked), clean up the 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 to the bottom of the page to the “” section and select downloading the archive for Windows.

2. Check the “ I have read and agree with the above terms and conditions" and click the "

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

4. You also need to download the Java Development Kit from official page. Go to the website, agree to the terms of the license agreement by checking the “” box, and download the JDK version that matches the bit size of your system.

First way

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

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

Read below about installing drivers for other devices.

Select " Accept License" and press " Install».

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

After completing the above steps, in the folder " tools_version-windows"will appear" and it will contain the ones we are interested in " A.D.B." And " Fastboot».

Second way

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

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

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

To enable, enter y, i.e. " yes", and press " Enter", after which the installation will begin "".

At the end, a message will be displayed on the command line 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 - included in HTC Sync Manager: http://www.htc.com/ru/software/htc-sync-manager/
• Nexus - Android driver is installed along 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/ru/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 are 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 your smartphone or tablet model 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 install an official solution.

If your model comes with a driver without an installer, you will have to do the following:

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

2. Find in the list the device for which you need to install drivers. 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 with an exclamation mark inside next to the device, “manual” installation Android drivers is required for you.

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

4. Specify the path to the driver folder on your PC.

Wait until the installation is complete and then reconnect the gadget to your computer via USB.

Working with ADB or Fastboot is done from the command line; you can enter it 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 command we open the desired folder:

CD

In my case it turned out like this:

cd \tools_version-windows\platform-tools

You will succeed ( Google developers changed the name of the archive after the original version of this instruction was written):

Cd\sdk-tools-windows-version\platform-tools

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

To avoid having to do this 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» → « Advanced System Settings» → «».

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

Click " Create", paste the folder path "" 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 test 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 previous article, the link is at the beginning of this post.

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

Android Debug Bridge is a program that works on the client-server principle. 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 to arrive.

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

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

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

The entire functionality of the program is revealed after entering a certain command. As an example, consider a command that allows you to view connected devices and check the readiness of the device to receive commands/files. To do this, use the following command:

The system response to entering this command has two options. If the device is not connected or not recognized (drivers are not installed, the device is in a mode that does not support operation via ADB, and other reasons), the user receives the response “device attached” (1). In the second option, when there is a device connected and ready for further operation, it is displayed in the console serial number (2).

Variety of possibilities

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

Separately, it is worth noting the presence of a kind of help system in Android Debug Bridge. More precisely, this is a list of commands with a description of the syntax, output as a response to the adb help command.

This solution very often helps many users 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 Russian version;
• Console application that requires knowledge of command syntax.

Download ADB for free

Android Debug Bridge is an integral part of the toolkit designed for Android developers (Android SDK). The Android SDK tools, in turn, are included in the . Download Android The SDK for your own purposes is available to all users absolutely free. To do this, you just need to visit the download page on the official Google website.

If you don't need to download the full Android SDK containing the Android Debug Bridge, you can use the link below. It allows you to download a small archive containing only ADB and Fastboot.

ADB, or Android Debug Bridge, is a console application for PC that allows you to manage your Android device directly from your computer. It looks like this: first, the ADB toolkit and drivers for Android are installed on the computer, then the mobile device is connected to the PC via a USB cable in debugging mode, and finally, after launching ADB, special commands are executed in the console (command line) to initiate certain actions with a gadget. detailed information about the principle of operation of the debugging tool itself is presented on the official website of the developer, so we will not dwell on this, but will immediately move on to the capabilities of ADB and how to install it on a computer.

What does ADB allow you to do?

First, let’s point out why ADB is needed at all. With it you can:

• Reboot the device in various modes;
• Exchange files/folders with your phone;
• Install/uninstall applications;
• Install custom firmware(including TWRP Recovery);
• Produce;
• Execute various kinds of scripts.

The ADB tool is usually installed in conjunction with the Fastboot console application.

Installing ADB and Fastboot from the Android SDK

This method involves using the official Android Studio application development and testing tool. Go to the page https://developer.android.com/studio/index.html and find the heading “Get just the command line tools”. Below we download the SDK tools archive for Windows (before downloading, we agree to the terms of use).

We unpack the archive to drive C. In our case, the files were extracted to the folder sdk-tools-windows-3859397.

We go to the directory, and then go to the directory tools/bin. Here we are interested in the file sdkmanager, which will help you install ADB and Fastboot on your computer.

Now you need to open the folder with sdkmanager, for which you should run the command in the console cd C:\sdk-tools-windows-3859397\tools\bin, Where C:\sdk-tools-windows-3859397\tools\bin– path to the sdkmanager.

If you unpacked the Android SDK not to drive C, but to some other location, then the full address can be found using the top line of Explorer (right-click on the destination folder and click “Copy address”).

So we moved to tools\bin and now we need to run the command sdkmanager "platform-tools", which will install the Platform-tools package containing the ADB and Fastboot files.

During installation, review the license agreement and press Y to complete the operation.

If everything went as it should, a directory will appear in the root folder of the Android SDK platform-tools with the necessary files adb.exe And fastboot.exe.

Minimal ADB and Fastboot

The second method is even simpler. On the developer forum Xda Developers you can download the package Minimal ADB and Fastboot with all the necessary files. To do this, go to the page https://forum.xda-developers.com/showthread.php?t=2317790 and, by clicking on the link, download the installation exe file.

We launch it and follow the instructions.

We installed Minimal ADB and Fastboot in the root of the same drive C.

Basically, that's all. All that remains is to check the presence of files.

Checking the operation of ADB and Fastboot

After installing applications using any of the above methods, you need to make sure that the utilities are working correctly. To do this, through the command line, go to the folder with the adb and fastboot files (command cd C:\sdk-tools-windows-3859397\platform-tools or cd C:\Minimal ADB and Fastboot), and then run the command adb help. She should print the version installed Android Debug Bridge and list of ADB commands. If you see something similar to the screenshot below, then everything is working correctly.

Now you should connect your mobile device to your PC and check if the ADB application sees it. We connect the phone (or tablet) to the computer using a USB cable, set the MTP (file sharing) connection mode in the settings and go to the section Settings – For Developers.

If there is no such item in the settings, then go to the “About phone” page and click on the line with the build number seven times.

Developer Mode will be activated and the “For Developers” section will become available. Go into it and enable the “USB Debugging” option.

After all these manipulations with the gadget, in the Windows command line, enter the command adb devices. It will display information about the connected device in approximately the same format as in the screenshot.

Thus, we tested ADB and Fastboot and made sure that the Android Debug Bridge is functioning normally, which means that you can now control the phone via a computer.

If communication with the device cannot be established, then you need to check the availability and correct installation of Android drivers. To do this, with debugging mode enabled, go to the “Device Manager” and look for exclamation marks in the “USB Devices” branch, “ADB Interface” item (may be called a little differently).

If problems are detected, we try to reinstall the drivers. You can download them on the phone manufacturer’s website or at https://adb.clockworkmod.com/.

We hope that the article was useful to you.