Menu
Is free
registration
home  /  Advice/ Installing adb on windows 10. What is ADB driver? What ADB allows you to do

Installing adb on windows 10. What is ADB driver? What ADB allows you to do

The ADB and Fastboot utilities are included in the Android SDK (not to be confused with Android Studio, and even more so to download its cumbersome setup file, unless of course you intend to do Android development). ADB is a debugging tool that allows you to access the Android console from a computer () by connecting a gadget to a PC via USB. In this case, 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: make a backup of applications, record a screencast, put the smartphone into Recovery mode and much more. In addition, you can work with ADB via Wi-Fi. To do this, your device must be rooted, and you also need a special application that connects to your computer over the network. For example, ADB Wireless or WiFi ADB... But this is already material for a separate article.

By using Fastboot, you can install firmware, (or CWM), unblock Bootloader(on devices Htc, Motorola, Sony,,, the latter is locked), 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 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 of the license agreement by checking the "" item, and download the JDK version corresponding to the bitness of your system.

The first way

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

Check the box " Android SDK Platform-tools" (and " Google USB driver"If you have Nexus device) and press " 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_version-windows"" "Will appear, and it will contain“ ADB" 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 prompted to install:

To allow, enter y, that is, “ yes", and press " Enter", After which the installation" "will start.

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

(!) If for any 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 - the Android driver is installed along with the Android SDK, as described above.
  • Huawei - in conjunction 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 based on MediaTek chips: http://online.mediatek.com/Public%20Documents/MTK_Android_USB_Driver.zip
  • Lenovo - select your smartphone, 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 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 choose" Device Manager».

2. Find in the list the device for which you want to install the 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 in front of the device with exclamation mark inside, "manual" installation Android drivers is obligatory 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 your 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 command, we open desired folder:

cd

In my case, it turned out like this:

cd \ tools_version-windows \ platform-tools

You will get ( google developers changed the name of the archive after the initial edition 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 performing 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, paste. Click " OK».

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

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

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

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

Enter the following to check how the PC sees Android (in Windows PowerShell, insert ./ in front of 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.



A presentation of the be quiet! Processor fan was held Shadow Rock TF 2, which uses the powerful TopFlow design. Its system includes a copper base, five 6mm copper heatpipes, a 61-plate aluminum heatsink, and a 135mm axial cooler fixed to the top of the device. It distributes the air flow through the heatsink fins to the base, guaranteeing additional airflow to both the processor port and the nodes located around it (memory modules, power components, ports ...

Announced back in March this year graphics adapter the premium Colorful iGame Kudan 680 still went on sale in China. But the prices for it are not very encouraging, and some buyers may even be frightened. For the 2GB version of the video card, you will have to pay a little $ 893 (5700 yuan), and the iGame Kudan 680 (with double GDDR5 buffer) will cost the buyer as much as $ 940 (6000 yuan).

As for the characteristics of these models, they are briefly described. Frequency parameters: the junior video adapter with 2 GB of memory operates at the nominal 1100/6400 MHz, and the senior one with 4 GB of memory ...

Thermaright has unveiled a relatively affordable Thermaright True Spirit 120 Direct processor fan that can be used with 160W processors AMD platforms Socket AM4, AM3 (+), FM2 (+), as well as Intel Socket LGA1155, LGA1156, LGA1150, LGA1151, LGA2011 (v3), LGA2066.

The new mechanism is made in the usual Tower design. It contains four 6mm nickel plated heat pipes with direct contact to the CPU heatsink, aluminum heatsink and one 120mm cooler. The cooler speed ranges from 600 to 1300 rpm, ...

November 7, 2012 at 02:56 PM

Installing ADB Driver Manually

  • Development for Android
  • 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 that the device was fully operational, but upon request adb devices I got an empty list in the console and, of course, I could not test the application on the tablet.

I wrote a request to the TeXeT support service, they even answered me with a link to the driver itself, which, as I already made sure, 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 start at all, which plunged me into despair ... but not despair.

Here I decided to try my hand at writing drivers using the good old method of scientific typing and opened the inf-file of the driver. Hope was given to me by 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 to manually edit the inf-file, I found a recipe for treating the seasoning of the inf-file so that it was installed and, most importantly, worked.

So let's get started.

Step 1. Download the driver. If you haven't already, open Android SDK Manager, find the Extras section, check the box next to Google USB Driver 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 coveted usb_driver daddy there. Copy it somewhere, and there we will carry out further manipulations. In principle, you can edit the "original" too, but I preferred to keep the original intact for every fireman.

Step 3. Edit the inf file. In the 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_4ID_18D1 & PID_Install
Make a copy of these lines, 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). We open the properties of the device, the "Information" tab, select the item "Equipment ID" in the list and see the following picture.

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_0003stall
In% SingleAdbInterface% we delete the end of the line, as you can see, in% CompositeAdbInterface% we insert the whole. I 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, for this 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 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. Open its properties and select "update drivers", select the installation from the folder, specify the folder with the corrected inf-th and start the installation - our driver is instantly found, but during installation it may swear about incompatibility with the question "should I continue, please?" Let's continue. That's it, the driver is installed.
Step 5. Final. For accuracy, take out the USB port, wait until everything is found, open the console (Win + R, enter cmd) and write adb devices... If everything went well, we see the coveted item on the list, indicating that adb now sees our device.


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

If the adb command doesn't work for you at all. Computer -> Properties -> Environment Variables... We are looking for the Path variable and at the end add(in no case overwrite) at the end a semicolon, and after the address of the folder where adb lives (usually% android-sdk% \ platform-tools \). After 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 / Google's inf-file was written only for native Google devices / in your computer everything was messed up with Higgs bosons) Windows does not want to eat a Google driver for non-Google devices that are not written in the inf file. Apparently, everything there is just tied to these ID equipment. But the software part on the overwhelming majority of android devices in terms of the debugger connector to the PC is identical, therefore the driver should communicate normally with any Android device. Our task is to deceive Windows and force it to accept the device as "driver-suitable", which we did by appending its ID to the driver inf-file.

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

P. S. I have not done mass testing 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. The file had to be edited for each time separately, but I don't think this is such a problem.


If you have an Android phone or tablet, then you probably want to connect it to your Windows 10 device, for example, to transfer files. In this case, we recommend downloading ADB drivers for Windows 10 - special file libraries that simplify the operation of two devices on different OS.

Peculiarities

As a rule, there is no need to download ADB drivers for Windows 10 if all you need is to transfer the files. These drivers have a much broader purpose:
  • Transfer files from device to device;
  • Receive ROOT rights to Android OS;
It is for the sake of the latter that the driver data is downloaded. The full name of the abbreviation ADB is Android Debug Bridge, all other decryptions are erroneous versions. On this page we offer a universal driver package, in its most current version... It is universal in all respects at once, it is suitable for any Android devices, for any version of this OS, and will also allow you to connect your phone or tablet to Windows 10 x64, as well as to the 32-bit version.

If this version drivers suddenly will not suit you, then do not worry, you can always download - this is a universal program for automatic search and installation of any drivers, including ADB.

Despite the fact that the program is completely free, it is very functional. The version is available in Russian and English language... For those who want to simultaneously download and antivirus program in order not to infect your smartphone, we recommend using

The Taiwan Akasa vendor adds to its products range the Pascal MD (A-NUC40-M1B) chassis, designed for mini PCs, built on the Dawson Canyon generation Intel NUC boards. According to the key specs, published on the manufacturer's website, the specialty is compatible with such boards: NUC7i3DNBE, NUC7i3DNKE and NUC7i3DNHE.

The remarkable thing about this framework is its IP65 protection level, making it safe from humidity and dust. Akasa Pascal MD is almost entirely made of aluminum and has the following physical dimensions: 234.6 x 238 x 76.3 mm. Fins on the panels act as a heatsink and are responsible for 15 W Intel Kaby Lake-U chipsets cooling. The supply set includes power cords 2 m long.

Particular attention should be paid to the presence of moisture-proof connectors, USB 3.0, RJ-45 and HDMI interfaces. This high protection degree allows the novelty to be utilized in the industrial sphere, alongside with various embedded systems.

Asus has added to its product line a graceful black-and-white videocard, based on GeForce GTX 950 adapter. The heart of the model is an overclocked GM206-250 GPU. Its key differentiation is the possibility to operate in two modes: Gaming - 1076/1188 MHz (base / dynamic) clock frequency & OC - 1102/1279 MHz (base / dynamic). The customer is free to switch between the profiles where relevant.

The GPU, featuring 768 CUDA cores, 32 ROPs and 48 TMUs, is paired with 2 GB of GDDR5 memory that runs at reference 6610 MHz frequency (128-bit rail). The interface panel consists of three video outputs: HDMI 2.0, DisplayPort and DVI-I.

The PCB boasts the implementation of Super Alloy Power II components as well as totally automatic hardware assembly line. The latter became possible thanks to Asus Auto-Extreme technology.

As far as cooling is concerned, Asus GeForce GTX 950 (codename: GTX950-OC-2GD5) is equipped with a two-slot cooler. Its framework embraces an aluminum heatsink ...

ASRock, a Taiwanese manufacturer of motherboards, is eager to introduce its new elaboration - motherboard H87E-ITX / ac. The new-comer is designed in a compact mini-ITX form-factor and is destined for the creation of compact desktop systems. Chipset Intel H87 Express in combination with Intel Core(4th generation) LGA 1150 processors provide for utmost stability and high performance in the majority of working modes.

ASRock H87E-ITX / ac houses two slots for RAM memory modules of DDR3 type; the maximal volume of supported memory might achieve 32 GB. The board takes power by means of 24-pin ATX and 8-pin EPS connectors. Digi Power system, featuring DrMOS voltage regulators, allots four phases for providing power supply to the CPU. Expansion of facilities becomes possible due to a single PCI Express 3.0 x16 slot, a single miniPCI Express slot, a single eSATA port, and six SATA III 6 Gb / sec ports.

Network facilities are guaranteed by gigabit Ethernet port, Bluetooth 4.0 module, ...