A black screen, lack of response to buttons and endless freezing on the logo indicate a critical software glitch that turned an Android smartphone into a “brick”, however, instead of an expensive replacement of the motherboard in the service, the device can often be revived independently by flashing it through a computer.
Process flashing via a computer is the most effective method of resuscitating the device when the standard settings menus are not available. To do this, you will need a stable connection to your PC, special drivers and the correct system image. It is important to understand that recovery Android is a procedure with certain risks that requires care and strict adherence to the algorithm of actions, since one wrong move can make recovery impossible.
In this article we will analyze in detail all the stages of preparation, selection of tools and the process of recording a new operating system to the phone's memory. You will learn how to transfer the device to special boot modes, what apps to use for different processors and how to avoid fatal errors when working with bootloader.
Diagnostics of the condition and preparation of the workplace
Before taking active steps, you need to clearly determine the current state of the gadget. There is a “soft” brick, when the phone vibrates or shows a logo, but does not boot completely, and a “hard” brick, when the device is completely dead. In the first case, the chances of success are close to 100%, in the second they depend on the safety of the boot memory sectors eMMC or UFS.
To carry out the procedure, you will need a computer with an operating system Windows, since most specialized utilities do not have versions for macOS or Linux. It is also critical to use a high-quality USB cable: cheap wires often only support charging and do not transmit data, which will lead to a connection error at the stage of the most important action.
⚠️ Attention: Before starting any manipulations, make sure that the device’s battery is charged at least 30-40%. If the phone does not turn on at all, leave it on charge for 20-30 minutes, even if the indicator is not lit. Attempting to flash firmware on a completely discharged battery may interrupt the writing process and irreversibly damage the partition table.
The next step is to install the necessary drivers. Without them, the computer simply will not see the phone in special boot modes. The set of drivers depends on the processor of your device: for Qualcomm you need some, for MediaTek - others, and for Samsung - still others. An incorrectly installed driver is the most common reason for connection failure.
It is recommended to disable your antivirus software and firewall during the procedure. Some flashing utilities operate at a low level of access to ports and can be falsely identified by system protection as malicious objects, which will block the data writing process.
Selecting a flashing tool depending on the processor
There is no universal “restore everything” button, since the architecture of Android devices varies greatly. The choice of software directly depends on the brand of processor installed on your board. The wrong choice of app will not only not help, but can also lead to a conflict of hardware identifiers.
For chip-based devices MediaTek the de facto standard is the SP Flash Tool utility. It allows you to work with images in scatter.txt format and gives deep access to memory. For processors Qualcomm QFIL (Qualcomm Flash Image Loader) or the more advanced QPST is used. Owners of smartphones Samsung are the luckiest - they have branded Odin, which is highly reliable and has a simple interface.
Below is a table of correspondence between processors and recommended software:
| Processor manufacturer | Recommended utility | Firmware file type | Connection mode |
|---|---|---|---|
| MediaTek (MTK) | SP Flash Tool | Scatter-loading file | BROM / Preloader |
| Qualcomm (Snapdragon) | QFIL / QPST | RawProgram / Patch | EDL (Emergency Download) |
| Samsung (Exynos) | Odin (v3.13+) | .tar or .tar.md5 | Download Mode |
| Xiaomi (various) | Mi Flash Tool | Fastboot images | Fastboot |
It is important to download the firmware specifically for your model and region. Using an image from another modification of the phone, even if they are externally identical, can lead to the inoperability of the communication modules, camera or touch screen. Always check the model codes in the settings or on the sticker under the battery if it is removable.
Boot modes: Recovery, Fastboot and EDL
So that the computer can communicate with the phone at a low level, the device must be switched to a special service mode. In this case, normal system booting is either impossible or unnecessary. Understanding the differences between these modes is the key to successful recovery.
Mode Recovery (recovery) is a minimalistic operating system recorded in a separate memory section. It allows you to reset settings, install updates from a memory card and create backups. However, if system files are critically damaged, standard Recovery may not start or may not be visible to the computer.
Mode Fastboot (or Bootloader Mode) provides deeper access. Through it you can reflash individual sections of the system: bootloader, kernel, recovery, system and user data. This is the main tool for custom firmware and recovery after unsuccessful experiments. To enter, a combination of the volume and power buttons is usually used when the cable is connected.
What is EDL mode (Emergency Download Mode)?
EDL mode is an emergency boot mode for Qualcomm processors that works even with a completely removed bootloader. Entering it often requires disassembling the phone and closing special contacts (test points) on the board, since the software input can be blocked by the manufacturer.
The deepest access level for Qualcomm chips is the mode EDL. In this state, the phone is detected by the computer as a Qualcomm HS-USB QDLoader 9008 device. It allows you to write a system image from scratch, ignoring the bootloader state. This is the last chance to revive a device that has been turned into a “brick” by unsuccessful firmware.
Samsung devices have their own analogue - Download Mode. It is entered using a unique key combination (often volume down + home button + power). In this mode, the Odin app works, which sees the phone even if there is no Android bootloader installed.
Step-by-step guide: firmware via SP Flash Tool and QFIL
Let's consider a detailed algorithm of actions for the most common cases. Let's start with devices on the platform MediaTek. After launching the SP Flash Tool, you must specify the path to the file scatter.txt, which is located in the folder with the unpacked firmware. This file contains the memory map and partition addresses.
In the app settings, select the “Download Only” or “Firmware Upgrade” mode. The “Format All + Download” mode is dangerous to use, as it erases the unique IMEI identifiers, which will lead to the loss of the ability to make calls. Press the Download button, then connect the switched off phone to the computer by holding down the volume button (sometimes both buttons).
☑️ Preparing for MTK/QCOM firmware
For processors Qualcomm procedure looks different in the QFIL app. Under Select Build Type, select Flat Build. Specify the path to the file prog_emmc_firehose_*.mbn (or ufs) in the “Programmer Path” field. Then add files rawprogram0.xml and patch0.xml via the “Load XML” button.
After setting the parameters, switch the phone to EDL mode. If the software input is blocked, you will have to open the back cover and close the Test Point contacts on the motherboard when connecting the USB cable. Once the Qualcomm port appears in Device Manager, the “Download” button in QFIL will become active. It will take 3 to 10 minutes to start the process.
⚠️ Attention: Never disconnect the USB cable or interrupt the recording process until the “Download OK” message or green ring appears. Interrupting recording at the system partition stage will result in the phone no longer being detected by the computer at all, and a programmer will be required to restore the bootloader.
When the process is complete, disconnect the cable and try to turn on the device. The first boot after flashing (“boot”) can last up to 10-15 minutes, as the system optimizes applications and creates new configuration files. Don't panic if the phone hangs on the logo longer than usual.
Recovering Samsung devices via Odin
Smartphones of the Korean giant have their own specifics. To work, you will need the Odin app (version 3.13.1 or later) and official firmware downloaded from resources like SamMobile or SamFw. The firmware usually comes in the form of one archive that needs to be unpacked.
Run Odin as administrator. Switch your phone to Download Mode: turn off the device, then press the Volume Down and Home buttons (if available) at the same time and connect the USB cable. When the blue warning screen appears, press the Volume Up button to confirm input.
In the Odin interface, you will see a field with a port number (for example 0:[COM5]), colored yellow or blue. This is a successful connection signal. Distribute the firmware files into the appropriate slots: file with prefix BL in the BL field, AP in the AP field, CP in the CP field and CSC in the CSC field.
Use the file HOME_CSC instead of regular CSC if you want to save user data (photos, contacts). A regular CSC file will perform a full reset (Wipe Data), which is necessary in case of critical system errors, but will delete all personal information.
Make sure that in the settings (Options) only the “Auto Reboot” and “F. Reset Time". The “Re-Partition” option should be unchecked if you are not using a special PIT file, since turning it on unnecessarily can repartition the memory and destroy the data permanently.
Press the button Start to begin the process. The progress bar in the app and on the phone screen will show the progress status. Once completed, the phone will automatically reboot. If the green PASS status appears in Odin and the phone boots into the system, the operation was successful.
Possible errors and methods for eliminating them
Even if you strictly follow the instructions, unforeseen situations may arise. The most common error is "S_BROM_CMD_STARTCMD_FAIL" in SP Flash Tool or "Firehose Error" in QFIL. This most often indicates a problem with the drivers or an incorrect choice of connection mode.
If the computer does not see the phone at all in special modes, try changing the USB port (it is better to use USB 2.0 ports on the rear panel of the system unit), replace the cable, or install a different version of drivers. Sometimes disabling driver signature in Windows before installation helps.
The “PMT changed for the ROM” error means that the partition structure in the firmware is different from what is currently on the phone. In this case, in SP Flash Tool you need to select the “Firmware Upgrade” mode instead of “Download Only” in order to force the memory to be repartitioned according to the new markup file.
⚠️ Attention: app interfaces and mode names may differ slightly in different software versions. Always check the documentation (ReadMe) for the specific version of the firmware or utility that you downloaded, since developers often make changes to the logic of the tools.
If you receive status FAIL in Odin, try reconnecting the cable, restarting the computer and running the app again. It is also worth checking whether the antivirus is blocking the operation of Samsung USB Drivers. Sometimes clearing the folder C:\Odin\Logs of old log files helps.
90% of firmware errors are not due to a phone malfunction, but to a bad USB cable, lack of drivers, or an incorrectly selected app operating mode. Careful preparation eliminates most risks.
Will all information from the phone be erased after flashing the firmware?
In most cases, yes, especially if you use full wipe modes (Format All, CSC in Odin). When updating via Recovery without resetting, the data may be saved, but when restoring a broken phone, it is recommended to count on complete data loss. Always make a backup if the phone reacts in any way.
Is it possible to flash a phone if it is not detected by the computer at all?
If the device manager does not show any new connections when you try to enter Fastboot/EDL/Download modes, the problem may be hardware: the power controller, USB port, or the board itself has burned out. In this case, firmware update is impossible without first repairing it with a soldering iron.
What to do if, after flashing the firmware, the phone hangs on the logo?
Try to enter Recovery mode (volume + power buttons) and perform the “Wipe Data/Factory Reset” item. If this does not help, the firmware may not be suitable for your board revision or the cache partition is damaged. Try to reflash again, clearing the partitions before writing.
Is it dangerous to use custom firmware for recovery?
Using unofficial builds (LineageOS, Pixel Experience) to restore a brick is risky, since they may not contain the necessary proprietary drivers for your hardware. For resuscitation, always use only stock (official) firmware from the manufacturer.
Do you need to unlock the bootloader before flashing the firmware?
To install official firmware via Odin or SP Flash Tool, unlocking the bootloader is usually not required and is not even desirable. Unlocking is only needed to install custom Recovery (TWRP) and modified systems. Moreover, on some phones, unlocking resets the warranty and degrades the quality of the photo.