ADB is a universal driver for connecting an Android device to a computer. Installing ADB, adb drivers and Fastboot in one click Installing adb and fastboot

Many of us are already familiar with ADB (Android Debug Bridge), since, as the owner of an Android device, quite often we have to perform such simple actions as adb push And pull, or adb reboot etc. But for many novice users, just the sight of the command line is already scary, and it seems prohibitively possible. Although in fact everything is quite simple, experienced users will not let me lie, and the biggest difficulty is to remember all these commands, although this is not necessary to do either, since the Internet is always at hand and finding the right command is not difficult.

Android Debug Bridge, which is part of the Android SDK emulator, allows you to communicate between your computer and an Android device connected to it. By the way, if you need some software, you can download the programs for your laptop for free here. What can I do with ADB? Its capabilities are quite wide, for example, the most popular actions: copy files from an Android device to a computer, upload files from a computer to Android, execute many Linux commands, receive error reports, etc.

So if you're new to this and want to learn a little more about ADB than just what it is, then I suggest you check out my little basic guide to learning ADB.

What you will need

1. Android Debug Bridge (ADB) for Windows 32bit - download

2. Android Debug Bridge (ADB) for Windows 64bit - download

3. Computer with Windows OS installed.

Now let's move on to the active phase:

1. Download the required zip archive and extract it wherever you want, for example, drive C.

2. Now go to the directory C:/adb/sdk/platform-tools. Here you will find a set of files as shown in the image below.

3. Hold down the Shift button + right-click and launch the Windows command line from the current directory.

4. Enter the command adb start-server.

5. To make sure that your device is connected correctly and has been recognized by the computer, enter the command: adb devices. If all is well, you will see something similar to this:

Now that your device is connected and everything is working, let's play with it a little.

Reading LOGCAT via ADB

The easiest way is to run the command: adb logcat. As a result, the entire contents of the device log file will appear on the screen. To get logcat in a separate file run: adb logcat > logcat.txt.

BUGREPORT

You can run the command: adb bugreport, but you will receive a notification that the generated report will not be readable, so it is better to use: adb bugreport >result.txt.

ADB together with ROOT access rights

To work from ADB with full access rights, you need to root the device. If the device is already manual, then run the command: adb root and we see what is shown in the picture below (reboot ADB with root rights).

Installing applications via ADB

To install the application, make sure that there are no spaces in the apk file name and you need to know exactly the correct path to it. Well, then we run the command: adb install+ name of the installation file. In my example, I installed the papertoss game, so if everything goes well, you will get this picture on the screen:

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 Windows Device Manager reported that the device was fully operational, but upon request adb devices I received an empty list in the console and, naturally, I was unable to test the application on the 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 FastBoot is a separate component from the package that allows you to perform various service operations with a portable device based on the Android operating system connected to a computer. ADB commands are universal and can be used on almost all devices, except those on which they have been blocked by the user.

Specifically, the FastBoot tool makes it possible to flash smartphones and tablets. With its help, you can install a software update from an IMG file, as well as clean up system partitions, reboot if the system freezes completely, and much more.

Installation and use

Due to the lack of a graphical shell (we remind you that this is a console application), only experienced users will be able to work with ADB FastBoot. First of all, after downloading and unpacking the archive with the application, you need to add both programs (ADB and FastBoot) to the “Environment Variables” section. To do this, you need to go to the Windows Control Panel, then go to the sections “System and Security” - “Advanced system settings”. After that, click on the “Environment Variables” button at the bottom of the window that opens, select “System Variables” and specify the path to the unpacked folder.

If you did everything correctly, then after opening the Command Prompt and entering the “adb version” command, the version of the installed component should be displayed. In this case, you can begin flashing the firmware and performing other system operations. You can find information about ADB commands and their purpose on thematic forums. We will not study this issue in depth within the framework of this review. In general, instead of working “directly” with the command line, it is recommended to use ready-made GUIs, like the same and other similar programs.

Key Features

installation of new firmware versions for Android devices;
performing other service operations;
the need to perform complex initial setup (when used separately from the Android SDK);
lack of its own graphical shell (GUI);
compatible with all versions of Windows.

Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb , and systrace . These tools are required for Android app development. They"re also needed if you want to unlock your device bootloader and flash it with a new system image.

Although some new features in these tools are available only for recent versions of Android, the tools are backward compatible, so you need only one version of the SDK Platform-Tools.

Downloads

If you"re an Android developer, you should get the latest SDK Platform-Tools from Android Studio"s SDK Manager or from the sdkmanager command-line tool. This ensures the tools are saved to the right place with the rest of your Android SDK tools and easily updated.

But if you want just these command-line tools, use the following links:

Download SDK Platform-Tools for Windows
Download SDK Platform-Tools for Mac
Download SDK Platform-Tools for Linux

Although these links do not change, they always point to the most recent version of the tools.

Revisions

29.0.4 (September 2019)

adb
- Hotfix for Native debugging timeout with LLDB issue(https://issuetracker.google.com/140369526)

29.0.3 (September 2019)

adb
- adb forward --list works with multiple devices connected.
- Fix devices going offline on Windows.
- Improve adb install output and help text.
- Restore previous behavior of adb connect without specifying port.

29.0.2 (July 2019)

adb
- Fixes a Windows heap integrity crash.
fastboot
- Adds support for partition layout of upcoming devices.

29.0.1 (June 2019)

adb
- Hotfix for Windows crashes (https://issuetracker.google.com/134613180)

29.0.0 (June 2019)

adb
- adb reconnect performs a USB reset on Linux.
- On Linux, when connecting to a newer adb server, instead of killing the server and starting an older one, adb attempts to launch the newer version transparently.
- adb root waits for the device to reconnect after disconnecting. Previously, adb root; adb wait-for-device could mistakenly return immediately if adb wait-for-device started before adb noticed that the device had disconnected.
fastboot
- Disables an error message that occurred when fastboot attempted to open the touch bar or keyboard on macOS.

28.0.2 (March 2019)

adb
- Fixes flakiness of adb shell port forwarding that leads to "Connection reset by peer" error message.
- Fixes authentication via ADB_VENDOR_KEYS when reconnecting devices.
- Fixes authentication-when the private key used for authentication does not match the public key-by calculating the public key from the private key, instead of assuming that they match.
fastboot
- Adds support for dynamic partitions.
Updated Windows requirements
- The platform tools now depend on the Windows Universal C Runtime, which is usually installed by default via Windows Update. If you see errors mentioning missing DLLs, you may need to manually fetch and install the runtime package .

28.0.1 (September 2018)

adb
- Add support for reconnection of TCP connections. Upon disconnection, adb will attempt to reconnect for up to 60 seconds before abandoning a connection.
- Fix Unicode console output on Windows. (Thanks to external contributor Spencer Low!)
- Fix a file descriptor double-close that can occur, resulting in connections being closed when an adb connect happens simultaneously.
- Fix adb forward --list when used with more than one device connected.
fastboot
- Increase command timeout to 30 seconds, to better support some slow bootloader commands.

28.0.0 (June 2018)

adb:
- Add support for checksum-less operation with devices running Android P, which improves throughput by up to 40%.
- Sort output of adb devices by connection type and device serial.
- Increase the socket listen backlog to allow for more simulataneous adb commands.
- Improve error output for adb connect .
fastboot:
- Improve output format, add a verbose output mode (-v).
- Clean up help output.
- Add product.img and odm.img to the list of partitions flashed by fastboot flashall .
- Avoid bricking new devices when using a too-old version of fastboot by allowing factory image packages to require support for specific partitions.

27.0.1 (December 2017)

adb: fixes an assertion failure on MacOS that occurred when connecting devices using USB 3.0.
Fastboot: On Windows, adds support for wiping devices that use F2FS (Flash-Friendly File System).

27.0.0 (December 2017)

Re-fixes the macOS 10.13 fastboot bug first fixed in 26.0.1, but re-introduced in 26.0.2.

26.0.2 (October 2017)

Add fastboot support for Pixel 2 devices.

26.0.1 (September 2017)

Fixed fastboot problems on macOS 10.13 High Sierra (bug 64292422).

26.0.0 (June 2017)

Updated with the release of Android O final SDK (API level 26).

25.0.5 (April 24, 2017)

Fixed adb sideload of large updates on Windows, manifesting as "std::bad_alloc" (bug 37139736).

Fixed adb problems with some Windows firewalls, manifesting as "cannot open transport registration socketpair" (bug 37139725).

Both adb --version and fastboot --version now include the install path.

Changed adb to not resolve localhost to work around misconfigured VPN.

Changed adb to no longer reset USB devices on Linux, which could affect other attached USB devices.

25.0.4 (March 16, 2017)

Added experimental libusb support to Linux and Mac adb

To use the libusb backend, set the environment variable ADB_LIBUSB=true before launching a new adb server. The new adb host-features command will tell you whether or not you"re using libusb.

To restart adb with libusb and check that it worked, use adb kill-server; ADB_LIBUSB=1 adb start-server; adb host-features. The output should include "libusb".

In this release, the old non-libusb implementation remains the default.

Fixed Systrace command line capture on Mac

25.0.3 (December 16, 2016)

Fixed fastboot bug causing Android Things devices to fail to flash

25.0.2 (December 12, 2016)

Updated with the Android N MR1 Stable release (API 25)

25.0.1 (November 22, 2016)

Updated with the release of Android N MR1 Developer Preview 2 release (API 25)

25.0.0 (October 19, 2016)

Updated with the release of Android N MR1 Developer Preview 1 release (API 25)

24.0.4 (October 14, 2016)

Updated to address issues in ADB and Mac OS Sierra

Terms and Conditions

1.Introduction

3. SDK License from Google

4. Use of the SDK by You

5. Your Developer Credentials

6.Privacy and Information

7. Third Party Applications

8. Using Android APIs

https://privacy.google.com/businesses/gdprprocessorterms/

10. DISCLAIMER OF WARRANTIES

11. LIMITATION OF LIABILITY

12. Indemnification

14. General Legal Terms

January 16, 2019

Download Android SDK Platform-Tools

Before downloading, you must agree to the following terms and conditions.

Terms and Conditions

This is the Android Software Development Kit License Agreement

1.Introduction

1.1 The Android Software Development Kit (referred to in the License Agreement as the "SDK" and specifically including the Android system files, packaged APIs, and Google APIs add-ons) is licensed to you subject to the terms of the License Agreement. The License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK. 1.2 "Android" means the Android software stack for devices, as made available under the Android Open Source Project, which is located at the following URL: http://source.android.com/, as updated from time to time. 1.3 A "compatible implementation" means any Android device that (i) complies with the Android Compatibility Definition document, which can be found at the Android compatibility website (http://source.android.com/compatibility) and which may be updated from time to time; and (ii) successfully passes the Android Compatibility Test Suite (CTS). 1.4 "Google" means Google LLC, a Delaware corporation with principal place of business at 1600 Amphitheater Parkway, Mountain View, CA 94043, United States.

2. Accepting this License Agreement

2.1 In order to use the SDK, you must first agree to the License Agreement. You may not use the SDK if you do not accept the License Agreement. 2.2 By clicking to accept, you hereby agree to the terms of the License Agreement. 2.3 You may not use the SDK and may not accept the License Agreement if you are a person barred from receiving the SDK under the laws of the United States or other countries, including the country in which you are resident or from which you use the SDK . 2.4 If you are agreeing to be bound by the License Agreement on behalf of your employer or other entity, you represent and warrant that you have full legal authority to bind your employer or such entity to the License Agreement. If you do not have the requisite authority, you may not accept the License Agreement or use the SDK on behalf of your employer or other entity.

3. SDK License from Google

3.1 Subject to the terms of the License Agreement, Google grants you a limited, worldwide, royalty-free, non-assignable, non-exclusive, and non-sublicensable license to use the SDK solely to develop applications for compatible implementations of Android. 3.2 You may not use this SDK to develop applications for other platforms (including non-compatible implementations of Android) or to develop another SDK. You are of course free to develop applications for other platforms, including non-compatible implementations of Android, provided that this SDK is not used for that purpose. 3.3 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you. 3.4 You may not use the SDK for any purpose not expressly permitted by the License Agreement. Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK. 3.5 Use, reproduction and distribution of components of the SDK licensed under an open source software license are governed solely by the terms of that open source software license and not the License Agreement. 3.6 You agree that the form and nature of the SDK that Google provides may change without prior notice to you and that future versions of the SDK may be incompatible with applications developed on previous versions of the SDK. You agree that Google may stop (permanently or temporarily) providing the SDK (or any features within the SDK) to you or to users generally at Google's sole discretion, without prior notice to you. 3.7 Nothing in the License Agreement gives you a right to use any of Google's trade names, trademarks, service marks, logos, domain names, or other distinctive brand features. 3.8 You agree that you will not remove, obscure, or alter any proprietary rights notices (including copyright and trademark notices) that may be affixed to or contained within the SDK.

4. Use of the SDK by You

4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under the License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights that subsist in those applications. 4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) the License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries). 4.3 You agree that if you use the SDK to develop applications for general public users, you will protect the privacy and legal rights of those users. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If the user provides your application with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, the user has given you permission to do so. 4.4 You agree that you will not engage in any activity with the SDK, including the development or distribution of an application, that interferes with, disrupts, damages, or accesses in an unauthorized manner the servers, networks, or other properties or services of any third party including, but not limited to, Google or any mobile communications carrier. 4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so. 4.6 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any breach of your obligations under the License Agreement, any applicable third party contract or Terms of Service, or any applicable law or regulation, and for the consequences (including any loss or damage which Google or any third party may suffer) of any such breach.

5. Your Developer Credentials

5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials.

6.Privacy and Information

6.1 In order to continually innovate and improve the SDK, Google may collect certain usage statistics from the software including but not limited to a unique identifier, associated IP address, version number of the software, and information on which tools and/or services in the SDKs are being used and how they are being used. Before any of this information is collected, the SDK will notify you and seek your consent. If you withhold consent, the information will not be collected. 6.2 The data collected is examined in the aggregate to improve the SDK and is maintained in accordance with Google's Privacy Policy.

7. Third Party Applications

7.1 If you use the SDK to run applications developed by a third party or that access data, content or resources provided by a third party, you agree that Google is not responsible for those applications, data, content, or resources. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources. 7.2 You should be aware of the data, content, and resources presented to you through such a third party application may be protected by intellectual property rights which are owned by the providers (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources (either in whole or in part) unless you have been specifically given permission to do so by the relevant owners. 7.3 You acknowledge that your use of such third party applications, data, content, or resources may be subject to separate terms between you and the relevant third party. In that case, the License Agreement does not affect your legal relationship with these third parties.

8. Using Android APIs

8.1 Google Data APIs 8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service. 8.1.2 If you use any API to retrieve a user"s data from Google, you acknowledge and agree that you shall retrieve data only with the user"s explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so. If you use the Android Recognition Service API, documented at the following URL: , as updated from time to time, you acknowledge that the use of the API is subject to the Data Processing Addendum for Products where Google is a Data Processor, which is located at the following URL: https://privacy.google.com/businesses/gdprprocessorterms/ , as updated from time to time. By clicking to accept, you hereby agree to the terms of the Data Processing Addendum for Products where Google is a Data Processor.

9. Terminating this License Agreement

9.1 The License Agreement will continue to apply until terminated by either you or Google as set out below. 9.2 If you want to terminate the License Agreement, you may do so by ceasing your use of the SDK and any relevant developer credentials. 9.3 Google may at any time, terminate the License Agreement with you if: (A) you have breached any provision of the License Agreement; or (B) Google is required to do so by law; or (C) the partner with whom Google offered certain parts of the SDK (such as APIs) to you has terminated its relationship with Google or ceased to offer certain parts of the SDK to you; or (D) Google decides to no longer provide the SDK or certain parts of the SDK to users in the country in which you are resident or from which you use the service, or the provision of the SDK or certain SDK services to you by Google is, in Google's sole discretion, no longer commercially viable. 9.4 When the License Agreement comes to an end, all of the legal rights, obligations and liabilities that you and Google have benefited from, been subject to (or which have accrued over while the License Agreement has been in force) or which are expressed to continue indefinitely, shall be unaffected by this cessation, and the provisions of paragraph 14.7 shall continue to apply to such rights, obligations and liabilities indefinitely.

10. DISCLAIMER OF WARRANTIES

10.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE SDK IS AT YOUR SOLE RISK AND THAT THE SDK IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND FROM GOOGLE. 10.2 YOUR USE OF THE SDK AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE SDK IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE . 10.3 GOOGLE FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

11. LIMITATION OF LIABILITY

11.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT GOOGLE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT GOOGLE OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.

12. Indemnification

12.1 To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless Google, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys fees) arising out of or accruing from (a) your use of the SDK, (b) any application you develop on the SDK that infringes any copyright, trademark, trade secret, trade dress, patent or other intellectual property right of any person or defames any person or violates their rights of publicity or privacy, and (c) any non-compliance by you with the License Agreement.

13. Changes to the License Agreement

13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available.

14. General Legal Terms

14.1 The License Agreement constitutes the whole legal agreement between you and Google and governs your use of the SDK (excluding any services which Google may provide to you under a separate written agreement), and completely replaces any prior agreements between you and Google in relation to the SDK. 14.2 You agree that if Google does not exercise or enforce any legal right or remedy which is contained in the License Agreement (or which Google has the benefit of under any applicable law), this will not be taken to be a formal waiver of Google" s rights and that those rights or remedies will still be available to Google. 14.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of the License Agreement is invalid, then that provision will be removed from the License Agreement without affecting the rest of the License Agreement. The remaining provisions of the License Agreement will continue to be valid and enforceable. 14.4 You acknowledge and agree that each member of the group of companies of which Google is the parent shall be third party to the License Agreement and that such other companies shall be entitled to directly enforce, and rely upon, any provision of the License Agreement that confers a benefit on (or rights in favor of) them. Other than this, no other person or company shall be third party benefit to the License Agreement. 14.5 EXPORT RESTRICTIONS. THE SDK IS SUBJECT TO UNITED STATES EXPORT LAWS AND REGULATIONS. YOU MUST COMPLY WITH ALL DOMESTIC AND INTERNATIONAL EXPORT LAWS AND REGULATIONS THAT APPLY TO THE SDK. THESE LAWS INCLUDE RESTRICTIONS ON DESTINATIONS, END USERS AND END USE. 14.6 The rights granted in the License Agreement may not be assigned or transferred by either you or Google without the prior written approval of the other party. Neither you nor Google shall be permitted to delegate their responsibilities or obligations under the License Agreement without the prior written approval of the other party. 14.7 The License Agreement, and your relationship with Google under the License Agreement, shall be governed by the laws of the State of California without regard to its conflict of laws provisions. You and Google agree to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from the License Agreement. Notwithstanding this, you agree that Google shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction. January 16, 2019

Download Android SDK Platform-Tools

Before downloading, you must agree to the following terms and conditions.

Terms and Conditions

This is the Android Software Development Kit License Agreement

1.Introduction

2. Accepting this License Agreement

3. SDK License from Google

4. Use of the SDK by You

5. Your Developer Credentials

6.Privacy and Information

7. Third Party Applications

8. Using Android APIs

9. Terminating this License Agreement

10. DISCLAIMER OF WARRANTIES

11. LIMITATION OF LIABILITY

12. Indemnification

13. Changes to the License Agreement

14. General Legal Terms

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. It should display the version of the installed Android Debug Bridge and a 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.