Fastboot copy the file. Installing and using ADB and fastboot. Commands for working with ADB. What's new in the program ADB_RUN

Manage all aspects of Android mobile devices - memory, file system, installing and uninstalling programs, etc. — you can not only on the mobile device itself, but also from a personal computer by connecting a smartphone or tablet to it via a USB cable. For this purpose, special proprietary software is often included with the mobile device.

But such proprietary software is not always included, for example, for Linux/FreeBSD users. Therefore, it is advisable to at least have an idea of the universal interface for accessing Android devices from a personal computer, which is called (Android Debug Bridge) or briefly - ADB.

This universal interface is implemented in the form console utility under the same name adb, which is available for all popular operating systems and is launched from the command line. More details about what it is prepared with are described below. cut.

Introduction to ADB

The adb program establishes a connection between the device and the computer, allows you to send commands to the device via a USB connection and perform various manipulations with the Android system. Advanced users encountered it when obtaining root rights and installing.

The utility is a component intended for developers. Also, the smartphone manufacturer can supply this utility along with the drivers for a specific mobile device. But more details about installing the utility are below.

First, we list the main features of the ADB interface:

View Android devices connected to your PC;
viewing the Android system log;
copying files from/to an Android device;
installing and uninstalling applications on an Android device;
clear data partition on Android device;
run various Android device management scripts.

Users of Ubuntu 12.10+ can download the necessary utilities directly through the system package manager. The adb utility is already available in the official repository of this distribution. You need to install the android-tools-adb and android-tools-fastboot packages.

To fully work in Windows, you must also install specific device drivers to support the ADB interface via USB. Typically, Windows Vista and Windows 7 themselves find this driver on the Internet. After installing USB drivers for Windows in Device Manager you should observe: My Computer - Android Phone - Android ADB Interface. If you have instead Android ADB Interface After connecting the device, a yellow question mark lights up, which means the drivers were installed incorrectly.

For Linux/FreeBSD users, there is no need to install drivers, but you need to write a rule for udev. Below is the sequence of creating a rule using Ubuntu as an example.

To do this, you first need to find out the values of the idVendor and idProduct variables of your mobile device. This can be done using the lsusb command in the terminal, connecting the device via a USB cable, as a result of which information similar to this should be displayed:

Bus 002 Device 006: ID 12d1:1038 Huawei Technologies Co., Ltd.

Here idVendor is the hexadecimal digits after the ID and before the colon. IdProduct is the next four digits after the colon.

After this, create the file /etc/udev/rules.d/51-android.rules with chmod 644 rights and with the following content (substitute your ID and user values):

SUBSYSTEMS=="usb", ATTRS(idVendor)=="12d1", ATTRS(idProduct) =="1038", MODE="0666", OWNER="user"

$ sudo /etc/init.d/udev reload

In the first and second cases of receiving adb, it is very advisable to configure the environment variables so as not to enter the full path to the installed utility in the console when starting. Setting up your personal computer is now complete. USB debugging must be enabled on your mobile device: " Settings - Applications - Development - USB Debugging" Connect your phone via USB cable and DO NOT MOUNT as SD!

To get absolutely all adb features, the mobile device must already be root, and the package must also be installed Busybox(). But you should always remember that installing root rights in some cases may void the warranty on your device.

Now you can start working with adb.

Working with ADB

Let's look at some adb commands. Open the console and run the command:

$ adb devices

This command will display a list of devices connected to the PC. Something like this should appear:

List of devices attached
4CA94Dxxxxx device

If the adb utility responded to the adb devices request with something like “???????????? no permissions”, you need to .

$ adb reboot

$ adb reboot recovery

Installing the apk package from your computer:

$ adb install

Removing a package:

$ adb uninstall

View the device operation log:

$ adb logcat

After which you will see dynamic output of Android system messages. If you perform any manipulations with the device, this will be immediately displayed through the output of corresponding messages. Exit debugging mode using the Ctrl+C key combination.

And using ADB you can run a real Unix shell on your mobile device:

$ adb shell

By launching the shell, you can use all the UNIX commands available on the device - cat, ls, df and others, as well as run scripts.

If there is root and Busybox, then you can generally do whatever you want with your mobile device. So, you should be careful when using ADB.

A complete list of all ADB commands can be obtained by running adb without parameters. More details about debugging with its help are described. In some non-standard cases, the note may help. And here, even more detailed, but in English.

A set of other interesting specialized programs for connecting a desktop computer and your Anrdoid devices can be found in the article “” + I advise you to look at “”.

The proprietary utility of the Android +1 site is ADB Run. This program is a powerful “ADB combine” that allows you to fully unleash the potential of Android!

I will be grateful to everyone for donations, and it will also be a great incentive to develop the program further!

new things have appeared in it (Win 7 - 10)

What's new in the program ADB_RUN_v.4.14.16.23

New:
—
Deleted:
—
Corrected:
—
Updated:
Return to the main menu everywhere with the letter “B”

Download the Adb Run program and find out what
new things have appeared in it (Win XP - Vista)

An example of working with the program versions 3.X.

What can ADB RUN do?

and much more…

Review of ADB RUN instructions?

What is the essence of the ADB RUN program? What are the advantages, so to speak, of simply using adb on the command line?

The ADB RUN program has a pseudo-graphical interface, which contains many different commands, divided into categories that you use every day.

In this program it is much faster and easier to reboot Android, and then flash the phone in fastboot, take a screenshot, make a backup, reset the pattern.

Are you used to using the command line? One click and you switch from ADB RUN to the command line or adb shell, or you can even write your own script to automate actions and feed it to the program.

Examples of how to work with the ADB RUN program

Each item in the program menu is assigned a number. Press the required number on the keyboard and the ENTER button, get to the required menu, press the required number again to perform the action.

Now let’s briefly study all the menu items in the Adb Run program.

adb devices, fastboot decices - is the phone connected

Finding out whether ADB or Fastboot sees your phone is as easy as shelling pears. Everything is displayed in the main window at the top.

Reboot Android

The Reboot Android menu - ADB RUN quickly reboots Android into the selected mode - Download, EDL, Recovery, Bootloader.

Fastboot firmware in ADB RUN

ADB RUN allows flashing in fastboot

ADB Sideload

If you have over-the-air firmware, you can install it from the . In ADB RUN, everything is done so that the firmware is as easy as possible.

Download and send files on Android using ADB Run

Need to move files? Then you need to use the Move (Pull / Push) menu.

Unlock Gesture Key

The Unlock Gesture Key menu is a favorite section for many, all because it allows you to unlock the Android Gesture Key and it is now possible to unlock Pin codes and face codes.

Unlock Bootloader

If you need to unlock Bootloader on Android, but you don’t want to mess around with adb, then ADB Run will simplify this process, which everyone can figure out.

Memory and Partition

Memory and Partition allows you to find out everything about existing Android blocks and partitions.

Backup

Need to create a Backup? ADB RUN allows you to create a backup using adb and remove an img image from the required partition. Read more about creating a backup copy from an Android device.

Install / Uninstall Android App (APK)

The menu is responsible for installing applications, including, or here you can.

Screenshot/Record

Do you need to take a screenshot of the screen in the program or in Recovery mode? Maybe record a screencast? This is also possible!

Update ADB and Drivers

ADB Run works thanks to the adb utility, which needs to be updated periodically; this can be done directly from the program. You can also download new Google Drivers.

Android firmware, i.e. writing certain file images to the corresponding sections of the device’s memory using special Windows software that almost completely automates the process is today not the most difficult procedure from the user’s point of view. If using such tools is impossible or does not give the desired result, the situation can be saved.

In order to flash an Android device via Fastboot, you will need knowledge of the console commands of the same mode of operation of the device, as well as certain preparation of the smartphone or tablet and the PC used for operations.

Due to the fact that in fastboot mode, manipulations with the device’s memory sections are performed virtually directly, when using the firmware method described below, some caution and attentiveness are required. Additionally, the following steps should probably only be recommended if you are unable to flash the firmware using other methods.

The user carries out every action with his own Android devices at his own peril and risk. The site administration is not responsible for possible negative consequences of using the methods described on this resource!

Strict implementation of the preparatory procedures determines the success of the entire process of flashing the device, so the implementation of the steps described below can be considered a prerequisite before carrying out operations.

Installing drivers

You can learn how to install a special driver for fastboot mode from the article:

System backup

If there is the slightest possibility, before flashing the firmware, a full backup copy of the existing partitions of the device’s memory must be created. The steps required to create a backup are described in the article:

Downloading and preparing the necessary files

Fastboot and are complementary tools from the Android SDK. We download the entire toolkit or download a separate package containing only ADB and Fastboot. Then unpack the resulting archive into a separate folder on drive C.

Through Fastboot it is possible to record both individual sections of the memory of an Android device and firmware updates as a whole package. In the first case, you will need image files in the format *.img, in the second – package(s) *.zip. All files that are planned for use must be copied to the folder containing unpacked Fastboot and ADB.

Packages *.zip We do not unpack it, you just need to rename the downloaded file(s). In principle, the name can be anything, but should not contain spaces or Russian letters. For convenience, you should use short names, for example update.zip. Among other things, it is necessary to take into account the fact that Fastboot is case-sensitive in sent commands and file names. Those. “Update.zip” and “update.zip” for fastboot are different files.

Launching Fastboot

Since Fastboot is a console application, working with the tool is done by entering commands of a specific syntax into the Windows command line (cmd). To launch Fastboot, the easiest way is to use the following method.

This add-on allows you to perform all the operations from the examples described below in a semi-automatic mode and without having to resort to manually entering commands into the console.

Unlocking the bootloader

Manufacturers of a certain number of Android devices block the ability to manage device memory sections by locking the bootloader. If a device has a locked bootloader, in most cases flashing its firmware via fastboot is not possible.

To check the status of the bootloader, you can send the following command to the device, which is in fastboot mode and connected to the PC:

fastboot oem device-info

But again we have to admit that this method of determining the blocking status is not universal and differs for devices from different manufacturers. This statement also applies to unlocking the bootloader - the methodology for carrying out the procedure differs for different devices and even for different models of the same brand.

Writing files to device memory sections

Having completed the preparatory procedures, you can proceed to the procedure for writing data to the device’s memory sections. Once again, we double-check that the image files and/or zip packages are loaded correctly and that they correspond to the device being flashed.

Attention! Flashing incorrect and damaged file images, as well as images from another device into the device leads in most cases to the inability to load Android and/or other negative consequences for the device!

Installing zip packages

To write to the device, for example, OTA updates, or a complete set of software components distributed in the format *.zip, the fastboot update command is used.

Writing img images to memory partitions

In many cases, searching for firmware in the format *.zip may be difficult to download. Device manufacturers are reluctant to post their solutions on the Internet. In addition, zip files can be flashed through recovery, so the advisability of using the method of writing zip files through fastboot is questionable.

But the ability to flash individual images into the appropriate sections, in particular "boot", "system", "userdata", "recovery" etc. via Fastboot when restoring the device after serious software problems, can save the situation in many cases.

To flash a separate img image, use the command:

fastboot flash partition_name file_name.img

In this way, the firmware is flashed using commands sent via the console. As you can see, the preparatory procedures take more time and effort, but if they are performed correctly, writing sections of the device’s memory occurs very quickly and almost always without problems.

Need to flash Android using FastBoot, but don't know how? This article provides detailed instructions on using the FastBoot utility and how to use it to flash an Android device.

This manual will fully explain how to use FastBoot! If you don’t know how to install archived updates, then you need the article - Clockwordmod - what is it. Instructions for CWM recovery with pictures

Downloading and installing FastBoot

Before flashing Android using FastBoot, you need to download it and install it on the desired computer.

1. You can download the FastBoot utility with the official Android SDK program (heavy weight)

why ADB RUN is better

Launch

If you downloaded Separately Fastboot

After you have downloaded and installed FastBoot, open the " Command line »

and vve Enter the commands to go to the folder with the Fastboot utility (if you installed separately FastBoot)

cd/
cd adb

If you downloaded ADB RUN

If your choice fell on the ADB RUN program, then launch it and select Manual -> ADB from the menu

The files that need to be flashed must be located in the same folder as the Fastboot utility

Instructions for commands on how to flash Android using FastBoot

It is very important to write commands and firmware files as they are specified!

If your command is specified

fastboot flash cache NazvaniAFiLe.img

then you need to write exactly like that, but not any other way. In other words, the case of letters is important, otherwise you will get an error cannot load 'image' - there is no such file.

Reboot commands into firmware mode (bootloader)

fastboot reboot-bootloader

The command "sees" your Android PC

Get into the habit of checking before doing anything in Fastboot if the connection between your computer and Android is:

Checking whether your PC can see your Android

fastboot devices

Execute this command when the device is already in firmware mode (bootloader)

Nexus Bootloader Unlock and Lock Commands

Unlock bootloader for Nexus

fastboot oem unlock

Lock bootloader for Nexus

fastboot oem lock

Command to find out bootloader version

Shows the version number of the bootloader installed on Android

fastboot getvar version-bootloader

Partition formatting commands

Before flashing any partition in Android, you must first format it so that there are no problems with operation

fastboot erase Imya_razdela - erase partition: boot, radio, recovery, system, userdata and others

Erases the Cache partition

fastboot erase cache

Erases the Data section

fastboot erase userdata

Erases the System partition

fastboot erase system

Erases the Recovery partition

fastboot erase recovery

Commands for flashing a partition

After you have formatted the partition or partitions, you can start flashing the firmware

fastboot flash Imya_razdela imya_file.img - firmware of the selected partition: boot, radio, recovery, system, userdata and others

Flash the system partition (System)

fastboot flash system imya.img

Flash the cache partition

fastboot flash cache imya.img

Flash the data section

fastboot flash userdata imya.img

Flash the Recovery partition

fastboot flash recovery imya.img

Setting the power-on animation (firmware partition with animation)

fastboot flash splash1 splash.img

Flash all partitions (boot, recovery and system)

fastboot flashall

Instead of imya.img- you need to enter the name of the file you are going to flash

Command to install update.zip

Flashes an update archive on Android in update.zip format or a ZIP archive with IMG images of various sections

fastboot update filename.zip

For Sony devices

Checking the connection of the Sony device, if the answer is 0.3 device, then it is connected

fastboot.exe -i 0x0fce getvar version

Unlock bootloader

fastboot.exe -i 0x0fce oem unlock 0xReceived_Key

More detailed information on unlocking Bootloader Sony - How to unlock Bootloader Sony

Waiting for Device error

If you have the following message on in the command window for a long time: waiting for device- Means:

The driver is not installed or installed incorrectly - reinstall or install
Android device is not in Bootloader mode - translate
Incorrect connection to the USB port - use the rear USB 2.0 ports of the computer, do not use USB hubs

The user carries out every action with his own Android devices at his own peril and risk. The site administration is not responsible for possible negative consequences of using the methods described on this resource!