The process of restoring a smartphone or installing custom firmware often seems complicated and scary for the average user. However, using the mode Fastboot remains one of the most reliable ways to interact with the system partition of the device at a low level. Unlike the standard Recovery mode, this protocol allows you to send commands directly from the computer, bypassing the phone’s operating system.
This technique is indispensable in situations where the device has turned into a “brick”, hangs endlessly on the manufacturer’s logo, or requires complete data clearing before sale. We will analyze in detail the preparation of the workplace, installation of the necessary drivers and the sequence of actions that will bring your gadget back to life or open up new customization opportunities.
Preparation of tools and drivers
Before you begin any manipulations with system partitions, you must ensure a stable connection between the computer and the mobile device. You will need a high-quality USB cable, preferably an original one, since cheap analogues often provide only charging without data transfer. It is also critical to install ADB and Fastboot drivers on your PC.
For Windows users, the installation process may require manual intervention through Device Manager if automatic installation does not work. Owners of macOS and Linux usually just need to unpack the platform tools into a convenient directory. Make sure that there is enough space on your hard drive to store the firmware image, which can occupy several gigabytes.
⚠️ Attention: Using non-original cables or damaged USB ports may lead to a loss of connection at the critical moment of data recording, which will make the device unrecoverable using software methods.
Download the current version of platform tools from the official developer resource. Unpack the archive to the root of the disk or any folder without spaces in the path name to avoid errors when calling the command line. This is a basic requirement, ignoring which often becomes the reason for unsuccessful firmware attempts.
Use USB ports located directly on the motherboard (rear of the system unit), and not on the front panel of the case, to ensure maximum stability of voltage and data transfer.
Activating developer mode and unlocking the bootloader
To gain access to low-level functions of the device, you must activate the hidden menu for developers. Go to the settings of your smartphone, find the “About phone” item and click on the build number seven times in a row. After this, a new section will appear in the menu where you need to enable USB debugging.
The next critical step is unlocking the bootloader (Bootloader). Manufacturers often block this feature to protect user data and system integrity. The unlocking procedure varies depending on the brand: some require obtaining a special code from the manufacturer's website, others allow you to do this with a simple command.
- 📱 Enable USB debugging in the developer menu.
- 🔌 Connect the phone to the PC and confirm the RSA key fingerprint on the smartphone screen.
- 🔓 Enter the unlock command after backing up your data.
- 💾 Save important files, as unlocking will completely delete all information from the device.
Remember that unlocking the bootloader will often void the manufacturer's warranty. Before executing a command fastboot flashing unlock or its equivalent, weigh all the risks. Some brands, such as Huawei or older models Sonymay require unique unlock codes, which are currently difficult or impossible to obtain.
Entering mode Fastboot and connection check
To put the device into the desired mode, you usually need to turn off the smartphone and hold down a certain key combination when turning it on. Most often this is the volume down button along with the power button. On some models, for example Google Pixel, you must first enter Recovery mode and then select “Enter Fastboot.”
After connecting the cable to the computer, open a command line or terminal in the folder with installed tools. Enter the command fastboot devices. If the drivers are installed correctly, you will see the serial number of your device. No output indicates a problem with the drivers, cable, or connection mode.
fastboot devices
0123456789ABCDEF fastboot
If you see a “waiting for device” message instead of the serial number, check your task manager for unknown devices. You may need to manually update the driver to the INF file path from the platform tools folder. Successful display of the serial number is the green light to begin the firmware procedure.
☑️ Checking readiness for firmware
Firmware process and basic commands
The process of writing an image to flash memory depends on the type of firmware. For devices with a project Treble or pure Android, the command to flash all partitions at once is often used. In other cases, you may need to alternately write the bootloader, system, recovery and modem.
The main command for writing an image looks like fastboot flash partition_name image_file.img. Here partition_name is replaced by the partition name (for example, boot, system, recovery), and image_file.img by the name of your firmware file. An error in the name of the section may cause the phone to stop booting.
| Section | Description | Risk in case of error |
|---|---|---|
boot |
System kernel and boot image | High (the phone does not turns on) |
system |
Main operating system Android | Critical (the system will not boot) |
recovery |
Recovery mode | Medium (cannot reset) |
userdata |
User data and settings | Loss of all personal files |
To completely clean the device before installing a new system, the command fastboot -wis often used. It formats the data and cache partitions. This is a mandatory step when switching between different versions of Android or changing the firmware type from official to custom.
What are A/B partitions?
Some modern smartphones use an A/B update scheme, where the system is duplicated in two slots. When flashing such devices, commands may require specifying the active slot, for example, --slot=all.
Completing the procedure and first boot
After successful execution of all image recording commands, you must reboot the device. To do this, use the command fastboot reboot. Do not disconnect the cable until the manufacturer's logo appears on the screen to ensure that the initialization process was successful.
The first boot after flashing may take significantly longer than usual - from 5 to 15 minutes. This is due to the optimization of applications and the creation of new system files. If the phone is stuck on the logo for more than 20 minutes, you may need to repeat the procedure to clear the data or check the compatibility of the firmware image.
⚠️ Attention: If after flashing the device asks for a Google account that was previously synchronized with the phone (FRP Lock), you will need to enter data from this account to confirm ownership.
Make sure basic functions such as connectivity, Wi-Fi and touchscreen are working correctly. Sometimes, after installing custom images, minor software glitches may occur, which can be resolved by resetting the settings to factory settings again from the Android menu itself.
Successful reboot and login without errors means that the firmware was installed correctly, but it is recommended to conduct a full test of all communication modules and sensors on the first day of use.
Possible errors and methods for them elimination
During the process, you may encounter an error FAILED (remote: device is locked). This means that the bootloader is still locked and writing to system partitions is prohibited. Return to the unlocking step and make sure that the command was completed successfully and the status changed to unlocked.
Another common problem is error FAILED (data too large). It occurs when you try to write an image whose size exceeds the capacity of the partition. This often happens when installing firmware designed for devices with a large amount of memory on a model with a smaller one.
- 🚫 Communication error: replace the USB cable or connection port.
- 🔋 Low battery: connect the device to a charger before starting.
- 📂 Incorrect path: make sure that the command line is open in the folder with the firmware files.
- 💾 Broken file: check the checksum of the downloaded firmware image.
In some cases, using the flag --disable-verity or --disable-verification when unlocking, especially on devices with strict integrity checks of boot partitions. However, this reduces the security level of the device.
What to do if the phone is not detected in Fastboot?
Try reinstalling the drivers, disabling the antivirus that may block access to ports, or using another computer. Also check if charge only mode is enabled in the USB settings on the phone itself.
Is it possible to flash the phone if the screen is black?
Yes, if the tactile feedback or the sound of the USB connection works, you can try to blindly enter the button combination to enter Fastboot and send commands based on the time or sound signals.
Will the firmware erase my photos and contacts?
Yes, almost any operation via Fastboot, especially related to unlocking the bootloader or the -w command, completely deletes all user data. Be sure to make a backup copy in advance.