How to reflash a smartphone to Android 6.0 via a computer

The procedure for flashing a device based on an operating system Android 6.0 Marshmallow via a personal computer remains relevant for owners of old smartphones who want to restore the functionality of the gadget or install a custom assembly. Despite the fact that this version of the OS is outdated, many budget models or specialized devices still operate on it. Using a PC as a source of firmware gives much more control over the process than updating over the air, and is often the only way to revive the “brick.”

Before taking active steps, you must clearly understand the risks. Any interference with the system memory partition carries the potential threat of complete data loss or bootloader blocking. You will need not only the firmware file, but also a specific set of drivers, as well as an understanding of the architecture of your processor. In this material, we will analyze a step-by-step algorithm of actions that will help minimize errors and successfully complete the installation of a new system.

Preparation of the workplace and equipment is the foundation for success. Make sure that your smartphone battery is charged at least 60-70%, as a sudden power outage while writing memory sectors can lead to irreversible consequences. You will need a high-quality USB cable, preferably an original one, and a computer with an operating system Windows, since most specialized utilities are optimized specifically for this platform.

Preparing drivers and software

The first critical step is to install the correct ones USB drivers for your device. Without them, the computer simply will not see the smartphone in download or debugging mode. Processors Qualcomm usually require QDLoader drivers, MediaTek - VCOM, and devices Samsung require a package Samsung USB Driver for Mobile Phones. Universal drivers from Google often work unstable with older models, so it is better to look for specific versions from the chipset manufacturer.

In addition to drivers, you will need command line tools. The platform ADB (Android Debug Bridge) and utility Fastboot are the industry standard for interacting with the system at a low level. They can be downloaded as part of the package SDK Platform Tools from the official website of the developers. After unpacking the archive, it is recommended to add the path to the folder with executable files to the system environment variables in order to call commands from any directory.

⚠️ Attention: Never install drivers from unknown sources or dubious all-in-one collections. An unsigned driver may intercept data or contain malicious code that will block USB ports at the system level.

You also need to determine the type of firmware. If you are planning to install a stock system, look for images with an extension .img or archives for specific utilities (for example .tar.md5 for Samsung). For custom firmware, zip archives are often used, which are installed through recovery, but for the initial installation “from scratch” via a PC, you need raw images of partitions. Check the integrity of the downloaded files using checksums MD5 or SHA-1to prevent data corruption during downloading.

Enabling debugging mode and unlocking the bootloader

In order for the computer to issue commands to the smartphone, the mode must be activated on the device itself. USB debugging. This feature is hidden in the "For Developers" menu. To activate this menu, go to Settings → About phone and quickly click 7 times on the “Build number” item. After the message “You have become a developer” appears, return to the main settings menu, where a new section will appear.

Inside the developer menu, find the switch USB debugging and activate it. When you connect to your computer for the first time, you will be asked to confirm your RSA key on your smartphone screen. Be sure to click “Allow”, otherwise the command adb devices will show the status unauthorizedand further actions will become impossible. This is a security measure that prevents access to data from other people's computers.

The next step is often unlocking Bootloader (bootloader). On many Android 6.0 devices this is done through the Fastboot command. Put your smartphone into fastboot mode (usually by holding the volume down button and the power button) and connect it to the PC. At the command line, enter:

fastboot oem unlock

Or, for some manufacturers:

fastboot flashing unlock

A warning message appears on the device screen indicating that all data will be deleted. Confirm the action with the volume buttons. Please note that this procedure is irreversible on some models and may void your warranty if it was still in effect. After unlocking, the device will automatically reboot and perform a factory reset.

Selecting a firmware method depending on the processor

The firmware algorithm directly depends on the processor architecture of your smartphone. There is no universal “Flash everything” button, so it is important to correctly identify the hardware. The wrong choice of utility can lead to the app simply not seeing the device or, worse, writing incompatible code into memory.

For devices based on MediaTek the de facto standard is the utility SP Flash Tool. It works with phones even when turned off (BROM mode), which makes it indispensable for restoring bricks. You will need a file scatter.txt, which is contained in the archive with the firmware and describes the device’s memory card. In the app interface you need to select mode Download Only or Firmware Upgrade, specify the path to the scatter file and click the Download button.

Smartphones based on Qualcomm are most often flashed through the utility QFIL (Qualcomm Flash Image Loader) or MiFlash (for Xiaomi devices). The connection mode is important here Emergency Download Mode (EDL). Entering it sometimes requires closing special contacts on the board (Test Point) if the software input is blocked. In QFIL you need to select the build type Flat Build, specify files prog_emmc_firehose.mbn and partition images.

Devices Samsung use their own protocol and are flashed through the app Odin. For Android 6.0, Odin versions 3.10 or 3.12 are relevant. The app interface is intuitive: firmware files with certain prefixes in the name are loaded into the appropriate fields (BL, AP, CP, CSC). It is important to choose the correct CSC file: using a regular CSC_... will lead to a complete data reset, and HOME_CSC_... will try to save user information (although this is not recommended when changing the Android version).

Chip manufacturer	Main utility	Connection mode	Key configuration file
MediaTek	SP Flash Tool	Disabled (BROM) / Fastboot	scatter.txt
Qualcomm	QFIL / MiFlash	EDL (Emergency Download)	prog_emmc_firehose.mbn
Samsung	Odin	Download Mode	.tar.md5 archives
Universal	Fastboot	Fastboot / Bootloader	flash_all.bat / .sh

What to do if the SP Flash Tool gives the error STATUS_BROM_CMD_STARTCMD_FAIL?

This error often occurs on new versions of Android or protected bootloaders. Try holding down the volume buttons before connecting the cable or using an authorized account in MCT Bypass tools to bypass DA protection.

The process of installing firmware via Fastboot

If you have access to the mode Fastboot and a set of images .img, you can flash the device manually, writing each partition one by one. This method gives maximum control, but requires care. First, make sure that the device is detected by the fastboot devicescommand. If the list is empty, check the drivers.

Firmware is installed sequentially. Typically the order is: bootloader, radio (modem), boot image, system, recovery, cache and userdata. The commands look like this:

fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img

Some users prefer to use ready-made scripts flash_all.bat (for Windows) or flash_all.sh (for Linux/Mac), which come as part of the factory images of Google Pixel or Xiaomi. Running such a script automatically flashes all partitions and clears memory. However, before starting, carefully open the script file in Notepad and check if there is a command there fastboot erase userdataif you want to try to save the data (although this is unlikely when flashing Android 6).

⚠️ Attention: When manually flashing via Fastboot, it is critical not to mix up the partitions. Writing an image system.img to a partition boot is guaranteed to turn the device into a “brick” that can only be restored by a qualified specialist with a programmer.

After completing all commands, you need to lock the bootloader back (if required for DRM functions, for example, Widevine L1 to watch HD video on Netflix) and reboot the device. The first boot after the firmware can take from 5 to 15 minutes, as the system optimizes applications. Do not interrupt this process, even if the screen goes dark or the logo appears.

Installing custom recovery and firmware

Often a goal Flashing Android 6 is not just a restoration, but the installation of a newer version of the system or a custom build, for example LineageOS. This requires replacing the stock recovery mode with a custom one, the most popular of which is TWRP (Team Win Recovery Project). The TWRP image is specific to each device model, so download it strictly using your codename.

TWRP is also installed via Fastboot. The command looks like this:

fastboot flash recovery twrp-3.x.x-x-device.img

An important nuance: on many devices, after a reboot, the stock recovery automatically replaces the custom one. To prevent this, immediately after entering the command, disconnect the cable and hold down the combination of buttons to enter Recovery (usually Volume Up + Power), without releasing them until the TWRP logo appears. If you simply reboot the system, the changes may be undone.

While in the TWRP environment, you can install the firmware from a ZIP archive previously copied to the internal memory or SD card. Before installation, be sure to Wipe (clean) the Dalvik, Cache, System and Data partitions. This is called a “clean install” (Clean Flash) and helps avoid conflicts between old and new system files. After installing the firmware and, if necessary, packages Google Apps (GApps), reboot the system.

Possible errors and ways to eliminate them

Various failures may occur during the firmware process. One of the most common mistakes is FAILED (remote: device is locked). This means that the bootloader is locked and does not allow new images to be written. The solution is described above: you need to execute the unlock command, keeping in mind the loss of data.

Another common problem is getting stuck on the manufacturer's logo (bootloop). If this happened after the firmware, try entering Recovery mode and executing Wipe Data/Factory Reset. If this does not help, perhaps the firmware version is incompatible with your hardware revision or the partition has been damaged boot. In this case, you will need to re-flash the stock image via Fastboot or a specialized utility.

Error waiting for device on the command line indicates problems with communication. Check the cable, try another USB port (preferably USB 2.0 on the back of the motherboard), reinstall the drivers. Sometimes disabling driver signature verification in Windows at boot helps. Also make sure that the “Charge Only” mode is not enabled on your smartphone in the USB connection settings.

⚠️ Attention: If the device is no longer detected by the computer at all (no connection sound, no response in the Device Manager), the BROM bootloader may be damaged or the power controller may be burned out. In this case, software methods are powerless, and hardware repair is required at a service center.

Frequently asked questions (FAQ)

Is it possible to flash Android 6 on a phone that originally ran Android 4 or 5?

Technically, this is only possible if the developers have released an official update or there is a stable custom firmware (for example, LineageOS) for your specific model. You can’t just “roll” a new version because of differences in drivers and the system kernel.

What to do if Odin freezes at the SETUP-CONNECTION stage?

This means that the app does not see the phone in Download mode. Try reinstalling Samsung drivers, using a different USB cable, or connecting the device to a different port. Also make sure that you have entered the Download mode correctly (usually Volume Down + Home + Power).

Is it safe to unlock the bootloader on banking applications?

No, after unlocking the bootloader, applications that require high security stop working (Google Pay, banking clients), since the integrity of the system is compromised (SafetyNet/Play Integrity). You can get it back working only by re-locking the bootloader and flashing the stock system.

Will the firmware erase my photos and contacts?

In 99% of cases, flashing, especially with unlocking the bootloader or through the command fastboot erase userdata, completely deletes all data from the internal memory. Be sure to back up your important files to your computer or to the cloud before starting the procedure.

Is it possible to roll back from Android 7 to Android 6?

Yes, it is possible, but it requires a complete data wipe. You need to find the official Android 6 firmware dump specifically for your model and flash it via Fastboot or the manufacturer’s specialized utility. You cannot simply install the old version via an OTA update.