What to do if SP Flashtool (flashtool) gives an error? (how to fix). Deciphering SP Flash Tool errors Sp flash tool error 8045 what to do

It often happens that during the flashing process through the SP Flashtool service utility an error is displayed. It's not just like that. Every error means some kind of problem. Usually, the program writes you a brief description of the problem in English and tells you the code of this problem.
It is difficult for a new product to understand what it is and why it is capricious. That’s why we’re on the RuleSmart forum, where we help everyone for free, and we ask, what’s the error code, huh? And only then, using this code, we can figure out what the problem is. Below we will provide the most comprehensive list of codes with decoding problems. In fact, we have already done this in a special topic on the Rulsmart forum, but in the article we will describe this in a little more detail, since the current material is designed for beginners.

Flashtool gives an error

Invalid Scatter file. For example, in the scatter file the PRELOADER and DSP_BL blocks are disabled

Problem with the port. For example, an error may appear if COM ports are disabled in the BIOS. Even if the COM port is virtual and the physical port is USB. In this case, you will not see the equipment on which PRELOADER drivers are installed. The problem may be with the USB cable, in which case replace the cable. If the computer's USB port is faulty, you need to plug the cable into another port. Theoretically, it can occur in UART USB port mode. The port was visible, it was selected in the Flash Tool settings, the program wrote it to the INI file, after which the system was rebooted with the port disabled, and the Flash Tool was immediately launched without selecting the port.. When, after passing the red bar to 100% as a result of the firmware, the operation buttons become available for clicking again, but neither the error message nor the window with a green circle appears; this error or a similar one will occur, the code of which is 1013. In this state, Flash Tool does not close the COM port, and attempting to restart any operation by reconnecting the device will cause an error. If the program has entered such an undefined state, then you need to close it and start it again

Occurs when the size of one of the parts of the firmware exceeds the size of the space allocated to it. Usually this is a kernel or recovery block. This error sometimes occurs on unfinished versions of Flash Tool. Change the version of the firmware you are using

The error is similar to error 1003. Solutions should be sought according to the same principle. Changing the firmware version or flashing the device firmware with the battery disconnected may help.

Use a more recent version of the firmware

Scatter file is not suitable for the device. For example, the file name contains version number 6777, and device version 6555

You need to go to the Help tab, click Open Logs Folder and delete all logs. Go to the folder with the firmware and delete the Checksum.ini file

The problem may be with the version of the flash drive. Download the version that has the SEC designation at the end. The error may occur if the operating system has many USB drivers installed for different devices. Use the USBDeview program to remove installed USB drivers and flash the firmware using the Flash Tool. Connecting the device while holding down the volume + or - key may help. If the above methods do not help, after the error appears, you must immediately close the window with the error and immediately click the download button again

The error may occur on MTD devices if the checkbox is not checked on the PRELOADER or DSP_BL blocks when selecting the Download mode. It is necessary to use the appropriate version of the Flash Tool, for example v2.xxx for MT6573 phones, or turn off the DA Download All mode. When selecting the Download mode, the checkbox is checked on the PRELOADER or DSP_BL blocks, you need to uncheck it from these blocks. If these blocks need to be flashed, then connect the phone in BOOTROM mode. When selecting ReadBack, Format or MemoryTest, you need to connect the device in BOOTROM mode. You can try flashing the device with the battery disconnected

In the Flash Tool settings, force the checkbox to indicate that the device does not have a battery. After this, connect the device via test point, but with a battery

After pressing the Download button, connect the switched off device to the computer with the volume buttons pre-pressed

The error may be related to the connection. Check the cable, reconnect the cable to another USB port

The problem is related to the detection of the device's flash memory. Use a different version of the flash driver, because... As different versions are released, information about flash memory is updated. If the above option does not help, try flashing the device on another computer, because... There are problems that do not allow you to correctly determine the memory on a specific machine

It is possible that the Uboot checkbox is not checked in the Flash Tool firmware settings. Uboot is an operating system and driver loader for initializing basic hardware such as display, processor, GPIO.

Use a different version of the flash driver. Try replacing the firmware version from version 5 to version 3

Occurs during automatic formatting. You must set formatting addresses manually

The error occurs if there are problems with the device's hardware. It can also occur if the Scatter file does not match the device. For example, emmc is present in the name, but the device actually has MTD flash. There is a possibility that the problem will be solved if you use a different computer and operating system. It is preferable to use a computer running Windows XP with newly installed drivers

Use a different version of the flash driver. If you are flashing version 3, try version 5, or vice versa. Select Format all + download mode. You need to reinstall the drivers for the device and ensure that the device is correctly displayed in Device Manager as MTK USB PORT. Launch Flash Tool, uncheck all items except PRELOADER and flash in Download mode. If progress is made but an error occurs at the end, then we make sure that we will only flash PRELOADER. At the top of the Flash Tool window, next to the Download button, click the Format button. The formatting settings window will open with Auto and Manual formatting modes. In Auto mode there are two settings, check the top box and press OK. Formatting will begin. After formatting is completed, flash PRELOADER again. After successfully flashing PRELOADER, flash the device completely

Incorrect scatter file. Use the Scatter file from your device

Change the USB port and move the Flash Tool to the root of the disk. The Download Agent may not have CPU/flash information, so use a more recent version of the firmware. The error may be hardware, for example due to a failed flash memory

Use a different version of the flash driver. There is a possibility that replacing the version with an older one will help. The problem may be with the USB cable, in which case replace the cable or USB port. Perhaps the battery ran out during the firmware process. Charge the device and try flashing the firmware again. You can try removing the battery from the device and try flashing it without it. Try formatting your device

In addition to reading errors in the device itself, the error can occur in the event of errors in the computer's file system. For example, there is not enough disk space, or the file cannot be overwritten because it is blocked. In order to understand the reason, you need to look at the Flash Tool log

It is recommended to change the firmware version to version 5; it is highly advisable to start with version 5.1352.01 and try to flash the device through the Firmware upgrade mode. The firmware must be original for the device and contain all the blocks. Try changing the firmware cable to a better one

An error may occur when flashing firmware on a device with an MT6589 processor. To fix it, format the device using the Format button. Do not format if you have a device with an MT6575 or 6577 processor. After formatting, flash the device with all the checkmarks by clicking the Download button. You can try reinstalling the drivers and formatting again. Run the firmware if the previous attempt was unsuccessful. If all else fails, try changing the firmware version. It is recommended to start with version 5.1352.01. The error is due to an invalid PRELOADER block. You need to find the native PRELOADER and flash it. If flashing the firmware using the standard method does not bring results, then you may have to flash the device through a testpoint. This error may be caused by a low battery charge. You can try to solve the problem by shorting pins 4 and 5 on the USB connector

An error may occur if the path line where the program or firmware is located contains Cyrillic or incorrect characters or hieroglyphs. It is permissible to place the program and firmware file only in a path that consists entirely of Latin characters. An example showing incorrect file placement: C:\Users\User\Desktop\Firmware\Tablet Firmware\

Occurs when the block sizes in the PMT and the Scatter file do not match. In general, this error can be resolved by loading all blocks, after which the size in PMT should change to the correct one. You can try changing the firmware version

The error occurs when there are problems with flash memory. It is not recommended to solve the problem yourself. Options for eliminating the error: warming up the flash memory chip with a soldering hair dryer at high temperature, approximately 400 degrees Celsius. You will probably have to replace the chip from the donor board or with a new one

When setting up the Flash Tool Download Agent, you must select the one included with this version of the firmware. Selecting other agents results in this error

The error usually occurs if the Flash Tool program has a checkmark on a block to which the path is incorrectly specified or is missing. To eliminate it, you must specify the correct path to the required firmware block. Also, if this error occurs, use a different version of the firmware, for example v5.1352.01

The error is that the Flash Tool was unable to obtain the device's RAM settings. This may occur if a full reset was performed via the Flash Tool. An error may also occur during data exchange between the Download Agent and the device. If the driver does not work correctly, a transmission failure can occur only if you have a Windows XP operating system with a service pack lower than third. It is necessary to install the third service pack. In older versions, the usbser.sys driver has not been updated and there is no point in reinstalling it

Invalid Scatter file. This may occur if you selected Scatter from a folder with files not prepared for the Flash Tool. You must select the correct Scatter file

The error most likely occurs due to a feature of flash memory. It happens that formatting, even low-level, does not have any effect. That is, in flash memory everything remains as is. If you do Format, error 1037 may appear and a message is displayed asking you to perform Download to create partition tables. Firmware Upgrade cannot be completed due to error 1037. You can only download PRELOADER. Loading any other partition will generate error 5069. The size of the FAT partition does not depend on the Scatter version. You can perform Manual Format, but within the UA Size. After formatting, trying to upload any partition again results in error 5069

There is a possibility that the error will disappear after updating the native PRELOADER firmware via the Download button. After that, flash the modified Recovery and full firmware

The error often occurs on Huawei G610, Huawei G700, LG L60 Dual devices and is currently not solvable at home. Consequences: periodic reboot, deleted files remain in the device, and an error occurs when checking the memory for writing. The reason is that the device has a locked bootloader, which is why it is necessary to flash the unlocked SEC_RO for unlocking and further flashing. It all comes down to the fact that it is during the SEC_RO firmware that this error occurs. It is recommended to replace the memory at a service center

To resolve the error, you must use the Firmware upgrade mode. Attention! The firmware must be specific to the device being flashed and contain absolutely ALL the blocks that are usually found in stock firmware

The error is similar to 8038, but in practice editing the Scatter file does not help. To solve the problem, you can contact a service center to flash the device using a programmer. At home, sometimes the firmware option works through the Download button with all the boxes checked. You can also try changing the firmware version to version 5; it is highly advisable to start with version 5.1352.01. The problem may be hardware

The error occurs if you try to flash a device on one platform with firmware from another. For example, you have MT6577, and you are trying to flash the firmware from the device on MT6575. You can try changing the firmware version to version 5, it is highly advisable to start with version 5.1352.01

The error occurs if the markup in the Scatter file and the device do not match. Most often it happens when the device has undergone custom repartitioning by changing the partition parameters in the EBR. At the same time, no one usually changes the Scatter itself. To eliminate the error, you must perform forced formatting with the parameters: Auto Format Flash and Format whole flash except Bootloader in order to initialize the device. Don't forget to backup NVRAM and IMEI in advance. After formatting, you need to perform a full firmware via Download

Install the Microsoft Visual C++ 2005-2008-2010-2012-2013-2017 Redistributable Package. Also make sure that you unpacked the firmware to the root of the disk on your computer, and are not trying to run it from the archive

Flashtool frozen

Yes, yes, this happens when the computer does not have enough resources or you screw up the settings. Of course, there may also be reasons in the computer itself, a normal freeze, which, as a consequence, led to a failure of the program. For the most part, this is a small problem, just wipe all data and reflash again.
In general, there is nothing to worry about here, really.

Understood nothing

If you don’t understand how to fix the error in the flash drive, then run for free help in the first aid section, on the RuleSmart forum, they will help you there. Just describe your problem in detail and show maximum respect, gourmets of highly intellectual communication will answer there.

Decoding common FlashTool errors. ™

You can share your experience or discuss instructions in the topic:

The instructions are supplemented and updated.

(1003) S_COM_PORT_OPEN_FAIL

Spoiler

Problem with the port.
This may occur if: - For example, you have com ports disabled in the BIOS (although in this case the com port is virtual and the physical port is USB, but when disabled, you simply will not see the equipment on which preloader drivers are installed).
- The problem is in the USB cable (changing the cable for the firmware helps).
- The problem is in the computer’s USB port (reconnecting the cable to another port helps).

(1011) S_NOT_ENOUCH_STORAGE_SPACE

Spoiler

Occurs when the size of any part of the firmware exceeds the size of the space allocated to it (Usually this is a kernel or recovery block).
Sometimes it occurs on “raw” versions of the flash drive, so maybe changing the firmware version will help. May occur when flashing with the wrong firmware version for a different amount of memory.

(1012) S_NOT_ENOUGH_MEMORY

Spoiler

Use a more recent version of the firmware.

(1013) S_COM_PORT_OPEN_FAIL

Spoiler

The error is similar in nature and direction to error 1003. Solutions must be sought according to the same principle (see 1003).
- Changing the firmware version to v5 may help. - The problem was solved as follows: Options -> DA Download All -> Speed -> Full Speed(when High Speed mode is selected, the above error appears on my computer)

(1022) S_UNSUPPORTED_VER_OF_DA

Spoiler

You need to use a newer version of SP FlashTool.

(1040) S_UNSUPPORTED_OPERATION

Spoiler

Scatter file does not match the phone. For example, the name contains 6577, but the phone number is actually 6573

(1041) S_CHKSUM_ERROR

Spoiler

Verification file error. Delete the checksum.ini file from the folder with the firmware and try to flash it again.

(2004) S_BROM_DOWNLOAD_DA_FAIL

Spoiler

Error writing DA bootloader to internal SRAM memory of the processor.
Causes:
1. The problem is in the connection between FlashTool and BootROM.
2. The device may turn off unexpectedly due to low battery power.
Actions:
1. Try again.
2. Check the cable and connector of the device for damage.
3. Check the battery voltage. Charge the battery on the charger. 4. Try flashing without a battery.

(2005) S_BROM_CMD_STARTCMD_FAIL

Spoiler

Error cases:
1. When selecting Download, the preloader or dsp_bl blocks are not checked. You must use the appropriate version of SPFT, for example v2.xxx for MT6573 phones, or turn off the DA Download All mode.
2. When you select Download, the preloader or dsp_bl blocks are checked. We need to uncheck these blocks! If these blocks need to be flashed, you need to connect the phone in BOOTROM mode.
3. When you select ReadBack, Format or MemoryTest. You need to connect the phone in BOOTROM mode.

(2020) S_BROM_CHKSUM16_MEM_RESULT_DIFF

Spoiler

The error occurs when trying to write the bootloader to the internal SRAM of the processor. The problem is in the internal memory, resulting in a 16-bit error. checksum.

(2035) S_BROM_CMD_JUMP_DA_FAIL

Spoiler

After clicking the Download button, try connecting a switched off device to the computer with the volume buttons held down.

(3001) S_DA_EXT_RAM_ERROR

Spoiler

There may be connection problems. Check the cable and/or reconnect the cable to a different port.

(3012) NAND_FLASH_NOT_FOUND

Spoiler

There is a problem with detecting the device's flash memory. Known methods to overcome this problem:

Try using different versions of the flash driver, because... As different versions are released, information about flash memory is updated.
Try flashing your smartphone on another computer, because... There are software problems that prevent you from correctly identifying memory on a specific machine.

(3013) S_DS_SOC_CHECK_FAIL

Spoiler

It is possible that there is no checkmark in the SP_Flash_Tool window for uboot. uboot - operating system loader + drivers for initializing the main hardware (display, processor, GPIO).
Or when there are Russian folder names in the path line, for example: C:\Users\Kolyan\Desktop\Hata\Firmware\Tablet Firmware\8.31\Surfer 8.31 3G_20130402_V1.03\Surfer 8.31 3G_20130402_V1.03

(3036) S_DA_INVALID_RANGE

Spoiler

The problem is that before flashing the firmware, the SP Flash Tool compares the address of the PMT block on the device’s flash with the scatter file and finds the difference, which is why it gives an error. The PMT block is created dynamically by the SP Flash Tool from a scatter file. To delete/overwrite a PMT block with a new one from a scatter file, you must first erase it in the device you want to flash. To do this, you need to click on the “Format” button in the SP Flash Tool program (in the window that opens, we don’t change anything, just click OK), then click “Download” and the SP Flash Tool will write new data about the PMT block and others to the flash again.

(3066) S_DA_HANDSET_FAT_INFO_NOT_FOUND

Spoiler

Occurs during automatic formatting; you should try setting formatting addresses manually.

(3144) S_DA_EMMC_FLASH_NOT_FOUND

Spoiler

In addition to a hardware problem, it may happen that the Scatter file does not fit the phone.
For example, emmc is in the name, but the phone actually has MTD flash.

(3148) S_DA_SDMMC_READ_FAILED

Spoiler

The error occurs when you try to write to a faulty flash drive.

(3149) S_DA_SDMMC_WRITE_FAILED

Spoiler

The problem may be hardware, for example, a failed flash memory.

(3168) S_CHIP_TYPE_NOT_MATCH

Spoiler

Invalid scatter file. Use the native scatter file from your device. The phone has a different processor.

(4001) S_FT_DA_NO_RESPONSE

Spoiler

Solution: change the USB port and move the SP Flash Tool to the root of the C:\ drive
There is also an option that the Download Agent file does not contain information about the CPU/flash. Solution: update the firmware version.
The problem may be hardware, for example, a failed flash memory.

(4008) S_FT_DOWNLOAD_FAIL

Spoiler

Methods from practice that solved this problem:

Changing the firmware version and the most interesting thing is that to an older version.
Changing the cable for firmware.
It is also possible that the battery is dead during the firmware process... Solution: charge the phone (battery) and try the firmware again.
Formatting the device can also sometimes help.

(4009) S_FT_READBACK_FAIL

Spoiler

In addition to reading errors in the phone itself, the same error occurs when there are errors in the PC file system. For example, there is not enough space for the file or the file cannot be overwritten because it's locked. To clarify, you need to look at the log.

(4010) S_FT_FORMAT_FAIL

Spoiler

Flash formatting error. Check your format settings.

(4032) S_FT_ENABLE_DRAM_FAIL

Spoiler

It appears if the preloader firmware file does not know the ROM memory installed in your smartphone. As a rule, this means that you bought a smartphone from a new batch, in which memory was installed that was not taken into account at the time of release of this firmware. You need to find a newer or Chinese firmware and use the preloader from it.

Try to format the phone.
- Sometimes you need to remove and reinstall drivers and format again, and then reflash if the previous attempt was unsuccessful.
- If flashing the firmware using the standard method does not bring results, then you may have to flash the device through a testpoint.

(4048) S_FT_MEMORY_TEST_FAIL

Spoiler

I encountered error 4048 when trying to test memory through the Memory test tab in the SP Flash Tool. Symptoms of the device's behavior are as follows: the phone does not boot, it constantly reboots on the screen saver.

(4050) S_FT_NEED_DOWNLOAD_ALL_FAIL

Spoiler

The block sizes in PMT and scatter do not match. You need to look for the line in the BROM_DLL log:

Spoiler

Size changed from 0x

It often happens:

Spoiler

Partition 13 (USRDATA) size changed from 0x00000000000000000 to 0x000000000B620000

This error can occur after editing the scatter incorrectly during the treatment of error 8038. It can be cured by loading all blocks through FT, or only one userdata block, after which the size in PMT should change to the correct one. Instead of a whole block, you can flash userdata_nvram_only.img from your backup or a dummy file. There is no size in scatter, so SPFT itself calculates the size of USRDATA based on the size of the flash and the space for BMTPOOL. And in the PMT tables inside the body, the size of the blocks is registered, and in this case, someone or something wrote zero there. To work around this case, you can rename the scatter USRDATA to __NODL_USRDATA ... but this may cause error 8038 due to the difference in names. In general, this error can be corrected by flashing all the blocks, after which the size in PMT should change to the correct one.

(5002) S_INVALID_DA_FILE

Spoiler

When setting up the SP Flash Tool - Download Agent, you need to select the one included with this version of the firmware. Selecting other agents gives the same error.

(5007) S_FTHND_FILE_IS_NOT_LOADED_YET

Spoiler

This error can be “cured” by choosing a different firmware method Firmware Update -> Download.

(5054) S_DL_GET_DRAM_SETTINGS_FAIL

Spoiler

Sometimes it can be solved by reinstalling the drivers.

(5066) S_DL_PC_BL_INVALID_GFH_FILE_INFOR

Spoiler

Incorrect files. For example, when you selected a scatter from a folder with files not yet prepared for FT. You need to select scatter from the folder of files prepared for FT.

(5069) S_DL_PMT_ERR_NO_SPACE

Spoiler

It can occur when the physical memory is faulty or the flash drive has gone into protection (read only).

(6124) S_SECURITY_INVALID_PROJECT

Spoiler

The problem was resolved as follows: Options -> DA Download All -> Speed -> Full Speed(when the High Speed mode is selected, the error described above appears on my computer) and by the way, the method also worked for error 1013 target item key (CUSTPACK), value (0x3444000)

in this example, you need to replace the name CUSTPACK2 with CUSTPACK in the scatter. If there are several differences, then this error will occur until the scatter, after the corrections made, becomes identical to the PMT. You can fix everything right away if you compare the tables that are in the log just above the NOT MATCH line. The first one is from scatter, the second one is from PMT phone. All block names in scatter must be the same as in the second table:

Scatter must be edited carefully! Change only the names and keep the original number of lines!
Some people manage to remove the line feed and the line with the block name ends up on the same line with the curly brace. FT does not see this block and writes PMT without it. Then you have to spend effort restoring this table! Another way:
- Download the latest mtkdroidtools
- Connect the phone and save the block map (2 files will be saved and one of them will be named PMP)
- We leave only PMP and rename it to the usual type of scatter
- Through it you can flash any firmware without error 8038 For phones with a new type of scatter (MT6572/82/92 and newer):
1. At the moment, an old type of scatter and/or an old version of FT is used, which does not work correctly with the new scatter.
2. Previously, an old scatter type or an inappropriate version of FT was used, which changed the PMT table inside the body to a table of the old type.
Use the SP FT version that understands the new scatter type and do not use older FT versions with the old scatter type!
3. The names or addresses of blocks in scatter are different from the table inside the phone (PMT)

(8045) SP FLASH TOOL ERROR

Spoiler

The error is similar in nature to 8038, but in practice editing the scatter file did not help. To solve the problem, many went to the service center and they resurrected the device through the programmer.
Very few people were helped by flashing the firmware via the DOWNLOAD button with all the boxes checked.

(8200) SP FLASH TOOL ERROR

Spoiler

Occurs if you are trying to flash a device on one platform with firmware from another (for example, you have MT6577, and you are trying to flash firmware from a device on MT6575, etc.)
Changing the firmware version may also help.

5 people liked the post

With the massive spread of the Android operating system as a software basis for various devices and gadgets, a huge number of different devices operating on the Mediatek hardware platform (abbreviated as MTK) have appeared on the market.

A large selection of devices and their enormous popularity have led to an increase in the number of usage models, the emergence of new programs and functions, but also introduced new problems into the world of ordinary users caused by instability and software failures in certain representatives of a large list of existing Android devices. Fortunately, many problems can be solved quite simply with the help of firmware for MTK devices. One of the most popular solutions for MTK devices in this area is the Sp Flashtool program. Errors made by software developers when using custom firmware and the described program can be easily eliminated, even if the user does not have a high level of competence. Let's look at the main points of using Flashtool and errors that may appear during its use. But more on that below; first, a little history and theory.

The enormous popularity of Android as an OS and MTC for smartphones and tablets has led to a wide variety of devices released using the above hardware and software components. The openness of Android and the relative versatility, and most importantly, the availability of MTK for smartphones, tablets and other solutions have made a variety of previously not widespread opportunities available to end users of devices. We are talking about the possibility of independent, without the involvement of specialists, management and control of the software and hardware of devices.

Why did SP Flashtool appear?

Few people know that each user can not only run functions defined by the device manufacturer, but also fully control and to some extent improve them, and sometimes even create new ones. This is the so-called “customization”, that is, changing certain parts of the Android system to suit your tasks. In addition to the customization process, users now have the opportunity to carry out independent software repairs of their devices, “reinstall” the OS and completely replace the software part of a smartphone or tablet with a version more suitable for the user. In general, all these concepts can be called the word “firmware”.

Of course, an ordinary user, or even a service engineer, is not able to work with the software part of such a complex device as any device running Android. In order to “flash” any gadget, you need tools (in our case, programs) capable of performing certain manipulations in an automatic or semi-automatic mode. One of the most famous programs of this kind is SP Flashtool. This is an application with which you can perform a wide range of procedures with MTK-based devices, collectively called "firmware".

How to work with SP Flashtool

The wide variety of models supported by the program does not allow writing universal instructions for its use.

For each model line or specific device, the process of flashing the firmware or backing up the system (backup) will be slightly different. But in general, to install the firmware on the device, almost all users will need to complete the following steps:

Download the required version of the program, unpack the resulting archive (the application does not require installation) and launch.
Indicating to the program the path to the location of a special scatter file.
Selecting partitions to flash into the device.
Translation of the program into device connections.
Connecting the device.
Waiting for the firmware process to complete.

While performing the above steps, various Flashtool errors may appear, in most cases the same for a wide range of devices and procedures. Let's look at them in more detail and try to apply methods to solve the situation when Flashtool throws an error.

Preparing to work with the program

Before moving on to considering common mistakes, let's figure out what needs to be done in preparation for working with the program. This will resolve most problems.

Install the correct device drivers. When the program is running, a virtual COM port is used to transfer data to the device. The driver for this component is different for each device. It is necessary to install only verified drivers obtained from reliable sources.
We use only fully functional and, most importantly, high-quality USB cables. This component is definitely not in last place in the list of factors accompanying successful firmware. It often happens that a user who receives a lot of errors when flashing a device via Flashtool already despairs of a successful outcome of the event. But it’s enough to take another USB cable, and everything will go without errors, smoothly and quickly.

"Correct" version of Flashtool

And again the wide variety of MTK devices makes itself felt. The firmware program is constantly updated; There are many versions of it, applicable to a certain range of models. It is important to find out which version of the application exactly works with a particular device and use only this version. In addition, if you use the wrong version of the Flashtool firmware, errors encountered during the process can even lead to damage to the hardware of your smartphone or tablet. You need to be extremely careful.

Corresponding "firmware"

In most cases, the manufacturer releases its own version of the software for each specific device. This also applies to custom firmware. And although there are cases when phones or tablets accept “not their own” firmware and even work after that, most often when you try to flash the device with a “foreign” set of files, an error will occur. To avoid such situations, you need to carefully and clearly determine the model and hardware revision of the device, and also download firmware only from trusted sources.

Device health

Even though Flashtool is a very powerful tool, it is not “magic”. No program can fix hardware failures. For example, if you try to flash a phone with a faulty USB connector or a faulty processor, it will not end well. The firmware will not even start, and the time spent trying to fix errors generated by Flashtool will be wasted.

The most common mistakes

In reality, the number of errors that can occur when working with the program is very large. When an error occurs during Flashtool firmware, the user becomes available information about the number of the event that occurred (error number), as well as a short transcript, which, however, does not provide any valuable data. For most users, this set of Latin letters is completely useless.

The most common errors described below occur. Under each item in this small list you can find recommendations for eliminating them.

Error 4001

If error 4001 appears when you try to write firmware to the device, Flashtool cannot continue to work. There can be several reasons for a problem, and finding the right solution can sometimes be difficult even for an experienced programmer. To easily resolve the error, we can recommend using a different USB port. You can also try moving the program files to the root of drive C.

In addition, when eliminating error 4001, changing the program version often helps. This may be due to the absence in the application files of information about the specific processor model or flash memory used in the device being flashed.

In some cases, the error may indicate a failure of the device's flash memory.

Error 4008

As in the previous case, error 4008 generated by Flashtool does not make it possible to draw an unambiguous conclusion about the cause of its occurrence.

Many users fixed it by changing the program version to an older one. Changing the USB cable used for firmware also often helps.

Among other things, error 4008 can occur when the device’s battery is discharged while working with the program. If you suspect that this has happened, you need to charge the battery and repeat the steps of the firmware procedure from the beginning.

Error 5054

Error 5054 is a very common problem that in most cases has a clear and unique solution. To avoid error 5054, Flashtool must accurately recognize the connected device. And it is well known that in order to correctly “understand” any device, software needs a driver. In other words, to solve the problem you need to reinstall the driver or find another suitable version. After performing this operation, error 5054 does not occur in most cases.

Error 8038

One of the few possible errors that has an unambiguous description and solutions. If error 8038 occurs when trying to load firmware into a device, Flashtool protects the device's memory from writing invalid blocks. This may be a discrepancy between the names and/or addresses of the blocks contained in the scatter file and the table of blocks recorded in the device.

The solution to the problem is to use a different version of the firmware containing a scatter file different from the one that caused the error. If this option is not possible, you will have to edit the scatter file manually. But using such a solution is highly not recommended due to the risk of damaging the device’s flash memory by writing blocks with inappropriate names and/or addresses.

As we can see, the appearance of errors in an application is not always a bad situation. If all the preparatory procedures described above were carried out correctly, but errors still occur, it is likely that SP Flashtool is simply protecting the user’s device from damage due to writing incorrect parameters or files.

When flashing a Lenovo phone using the Smart Phone FlashTool program, before starting the process or at a certain stage of the firmware, various errors may appear.
As a result, we cannot complete the process and receive a four-digit code from the SP FlashTool program

Explanation of common errors:

(1003) S_COM_PORT_OPEN_FAIL
Problem with the port.

(1011) S_NOT_ENOUCH_STORAGE_SPACE

(1013) S_COM_PORT_OPEN_FAIL

(1040) S_UNSUPPORTED_OPERATION
Scatter file does not match the phone. For example, the name contains 6592, but the phone number is actually 6589

Solved by replacing or changing the Scatter file

(2005) S_BROM_CMD_STARTCMD_FAIL
On phones with MTD flash the error occurs:

(3001) S_DA_EXT_RAM_ERROR
There may be connection problems.

Check the cable and/or reconnect the cable to a different port. Don't use a cable that is too long

(3013) S_DS_SOC_CHECK_FAIL
Perhaps there is no checkbox for uboot in the SP_Flash_Tool program window. uboot - operating system loader + drivers for initializing the main hardware (display, processor, GPIO).
Or there are Russian folder names in the path line, for example: D:\Firmware\Lenovo K930 Firmware\

(3144) S_DA_EMMC_FLASH_NOT_FOUND
There is a hardware problem or the Scatter file does not fit the phone. For example, emmc is in the name, but the phone actually has MTD flash.

(3066) S_DA_HANDSET_FAT_INFO_NOT_FOUND
Occurs during automatic formatting, you need to try setting formatting addresses manually.

(3036) S_DA_INVALID_RANGE
SP Flash Tool the address of the PMT block on the device’s flash does not match that in the scatter file.

The PMT block needs to be deleted through the "Format" tab, and a new one must be uploaded from the scatter file through the "Download" button and the SP Flash Tool will write new data about the PMT block and others too onto the flash.

(4001) S_FT_DA_NO_RESPONSE

The problem may be hardware, for example 4001 error occurs when Flash memory has failed.

(4008) S_FT_DOWNLOAD_FAIL

(4009) S_FT_READBACK_FAIL
In addition to reading errors in the phone itself, the same error occurs when there are errors in the PC file system. For example, there is not enough space for the file or the file cannot be overwritten because it is locked. Perhaps you are uploading firmware from 8 GB to a 4 GB device. To clarify, you need to look at the log file.

(4032) S_FT_ENABLE_DRAM_FAIL

(4050) S_FT_NEED_DOWNLOAD_ALL_FAIL
The block sizes in PMT and scatter.txt do not match. You need to look for the line in the BROM_DLL log.
size changed from 0x
Happens often
Partition 13 (USRDATA) size changed from 0x0000000000000000 to 0x000000000B620000
If the processor is MTK, there is no size in the scatter, and SPFT itself calculates the USRDATA size based on the size of the flash and the space for BMTPOOL. And in the PMT tables inside the body, the size of the blocks is registered, and in this case, someone or something wrote zero there:sh_ok: . To work around this case You can rename scatter.txt USRDATA to __NODL_USRDATA... but now 8038 may occur due to the difference in names. In general, this error can be corrected by loading all blocks (maybe one usrdata is enough), after which the size in PMT should change to the correct one.

(5054) S_DL_GET_DRAM_SETTINGS_FAIL
You need to reinstall the drivers.

(5066) S_DL_PC_BL_INVALID_GFH_FILE_INFOR
Incorrect files. There are no required files in the folder with the scatter file.

(6124) S_SECURITY_INVALID_PROJECT , MSP ERROE CODE: 0x00

Reduce recording speed in the program settings. Tab: Options -> DA Download All -> Speed -> Full Speed

(8038) SP FLASH TOOL ERROR
Occurs if the names or addresses of the blocks in the scatter differ from the table inside the phone (PMT). You need to look at SP_FLASH_TOOL.log and look for the NOT MATCH line in it
NandLayoutParameter::CompareIsNandLayoutMatched(): NOT MATCH: load item key(CUSTPACK2), value(0x3444000), target item key(CUSTPACK), value(0x3444000)
in this example, you need to replace the name CUSTPACK2 with CUSTPACK in the scatter file. If there are several differences, then this error will occur until the scatter, after the corrections made, becomes identical to the PMT. You can fix everything right away if you compare the tables that are in the log just above the NOT MATCH line. The first one is from scatter, the second one is from PMT phone. All block names in scatter must be the same as in the second table

(8045) SP FLASH TOOL ERROR
The error is similar in nature to 8038, but in practice editing scatter.txt does not help.

(8200) SP FLASH TOOL ERROR

Possible errors that the SP Flash Tool program produces when flashing devices based on MediaTek processors.

(1003) S_COM_PORT_OPEN_FAIL

Problem with the port.

This can occur if, for example, you have com ports disabled in the BIOS (although in this case the com port is virtual and the physical port is USB, but when disabled, you simply will not see the equipment on which preloader drivers are installed). This is either a problem in the USB cable (changing the cable for the firmware helps), or a problem in the USB port of the computer (plugging the cable into another port helps).

(1011) S_NOT_ENOUCH_STORAGE_SPACE

Occurs when the size of any part of the firmware exceeds the size of the space allocated to it (Usually this is a kernel or Recovery block). Perhaps changing the flasher version will help.

(1013) S_COM_PORT_OPEN_FAIL

The error is similar in nature and direction to error 1003.

(1022) S_UNSUPPORTED_VER_OF_DA

You must use a newer version of SP Flash Tool

(1040) S_UNSUPPORTED_OPERATION

Scatter file does not match the phone. For example, the name contains 6577, but the phone number is actually 6573.

(2005) S_BROM_CMD_STARTCMD_FAIL

On phones with MTD flash the error occurs:

1) When selecting Download, the preloader or dsp_bl blocks are not checked. You must use the appropriate version of SPFT, for example v2.xxx for MT6573 phones, or turn off the DA Download All mode.
2) When you select Download, the preloader or dsp_bl blocks are checked. We need to uncheck these blocks! If these blocks need to be flashed, you need to connect the phone in BOOTROM mode.
3) When selecting ReadBack, Format or MemoryTest. You need to connect the phone in BOOTROM mode.

(3001) S_DA_EXT_RAM_ERROR

There may be connection problems. Check the cable and/or reconnect the cable to a different port.

(3013) S_DS_SOC_CHECK_FAIL

It is possible that there is no uboot checkbox in the SP Flash Tool window. uboot - operating system loader + drivers for initializing the main hardware (display, processor, GPIO). Or when the path line contains Russian folder names, for example: C:\Users\Andrey\Desktop\Hata\Firmware\Tablet Firmware\8.31\Surfer 8.31 3G_20130402_V1.03\Surfer 8.31 3G_20130402_V1.03

(3144) S_DA_EMMC_FLASH_NOT_FOUND

In addition to a hardware problem, it may happen that the Scatter file does not fit the phone. For example, emmc is in the name, but the phone actually has MTD flash.

(3066) S_DA_HANDSET_FAT_INFO_NOT_FOUND

Occurs during automatic formatting; you should try setting formatting addresses manually.

(3036) S_DA_INVALID_RANGE

Solution to the problem:

To delete/rewrite a PMT block with a new one from a scatter file, you must first erase it in the device you want to flash. To do this, you need to click on the “Format” button in the SP Flash Tool program (in the window that opens, we don’t change anything, just click OK), then click “Download” and the SP Flash Tool will write new data about the PMT block and others too onto the flash.

(4001) S_FT_DA_NO_RESPONSE

The solution is to change the USB port and move the SP Flash Tool to the root of drive C:

There is also an option that the download agent file does not contain information about CPU/Flash. The solution is to update the flasher version.

The problem may be hardware, for example, a failed flash memory

(4008) S_FT_DOWNLOAD_FAIL

Solution to the problem:

changing the flasher version, possibly even to an older version;
changing the cable for firmware;
It is also possible that the battery ran out during the firmware process. Solution: charge the phone and try the firmware again;
It may also be worth flashing with the battery inserted.

(4009) S_FT_READBACK_FAIL

In addition to reading errors in the phone itself, the same error occurs when there are errors in the computer’s file system. For example, there is not enough space for the file or the file cannot be overwritten because it is blocked (see log).

(4032) S_FT_ENABLE_DRAM_FAIL

The error occurs when you try to change the firmware on a device with a processor using the SP Flash Tool program.

Solution to the problem:

After flashing the phone, format the phone using the Format button (do not do this if you have a device with an MT6575 or 6577 processor) in the SP Flash Tool program, then flash the official firmware or the one from your device and flash all the blocks (check all the boxes). Sometimes you need to remove and reinstall drivers and format again, and then reflash if the previous attempt was unsuccessful.

(4050) S_FT_NEED_DOWNLOAD_ALL_FAIL

The block sizes in PMT and in the scatter file do not match. You need to find the line in the BROM_DLL log:

size changed from 0x

It often happens:

Partition 13 (USRDATA) size changed from 0x0000000000000000 to 0x000000000B620000

There is no size in the scatter file, so SPFT itself calculates the USRDATA size based on the size of the flash and the space for BMTPOOL. And in the PMT tables inside the body, the size of the blocks is registered, and in this case, someone or something wrote zero there.

To solve this case, you can rename the scatter USRDATA to __NODL_USRDATA ... But here error 8038 may occur due to the difference in the names wink.gif. In general, this error can be corrected by loading all blocks (sometimes one usrdata is enough), after which the size in PMT should change to the correct one.

(5002) S_INVALID_DA_FILE

When setting up the SP Flash Tool download agent, you need to select the one included with this version of the firmware. Selecting other agents gives the same error.

(5054) S_DL_GET_DRAM_SETTINGS_FAIL

If, after complete assembly via the SP Flash Tool, it is not possible to install new firmware, and you cannot reset it again.

Solution to the problem:

Reinstall the drivers again.

(5066) S_DL_PC_BL_INVALID_GFH_FILE_INFOR

Incorrect files. For example, we selected a scatter file from a folder with files not yet prepared for FT. You need to select a scatter file from the folder of files prepared for FT.

(5069) S_DL_PMT_ERR_NO_SPACE

Hardware problem with flash memory

The error occurs:

If you do Format, the error S_PART_NO_VALID_TABLE (1037) will appear and it says that you need to do Download to create the partition table.
Firmware Upgrade does not allow me to do it -> again due to error 1037
You can download only PRELOADER. Loading any other partition produces error (5069) S_DL_PMT_ERR_NO_SPACE.
Does not depend on the version of the scatter file.
It also does not depend on the size of the FAT partition.
You can do Manual Format - it does, but within the UA Size. After this, an attempt to upload any partition again ends with error 5069.

Most likely this is a feature of flash memory - there are cases when neither formatting nor low-level formatting has any effect.

(6124) S_SECURITY_INVALID_PROJECT

Solution to the problem:

Select: Options -> DA Download All -> Speed -> Full Speed (when High Speed mode is selected, an error (6124) appears on some PCs).

(8038) SP FLASH TOOL ERROR

Occurs if the names or addresses of blocks in the scatter file differ from the table inside the phone (PMT). You need to look at SP_FLASH_TOOL.log and look for the NOT MATCH line in it.

NandLayoutParameter::CompareIsNandLayoutMatched(): NOT MATCH: load item key(CUSTPACK2), value(0x3444000), target item key(CUSTPACK), value(0x3444000)

It is necessary to replace the name CUSTPACK2 with CUSTPACK in the scatter. If there are several differences, then this error will occur until the scatter, after the corrections made, becomes identical to the PMT. You can fix everything right away if you compare the tables that are in the log just above the NOT MATCH line.

The first one is from the scatter file, the second one is from the phone’s PMT. All block names in scatter must be the same as in the second table.

(8045) SP FLASH TOOL ERROR

The error is similar to 8038, but editing the scatter file did not solve the problem.

Solution to the problem:

1) Firmware of the device via the programmer.
2) In rare cases, flashing the firmware via the DOWNLOAD button with all the boxes checked helped.

(8200) SP FLASH TOOL ERROR

It occurs if you try to flash a device on one platform with firmware from another.

Solution to the problem:

In other cases, changing the version of the flasher.

Invalid ROM or PMT address

If the hardware of the device is known to be in order, it is necessary to format the memory, and then flash the firmware in the standard manner.