Sp flash tool error 1041 solution. Deciphering SP Flash Tool errors

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 error described above appears on my computer)

(1022) S_UNSUPPORTED_VER_OF_DA

Spoiler

Need to use more new version 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 internal memory, as a result, 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 released different versions Information about flash memory is also 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 for uboot in the SP_Flash_Tool window. uboot - bootloader operating system+ drivers for initializing the main equipment (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, there may be a Scatter file that 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 it is more old 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)

V 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 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

SP Flash Tool errors and solutions:

S_COM_PORT_OPEN_FAIL (1003)
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).
or the problem is in the USB cable (changing the cable for the firmware helps).
or the problem is in the computer’s USB port (reconnecting the cable to another port helps).
S_NOT_ENOUCH_STORAGE_SPACE (1011)
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).
It also became known that this error sometimes occurs on “raw” versions of the flash drive, so maybe changing the firmware version will help. It may also arise when the firmware is installed with the wrong version for a different amount of memory.
S_COM_PORT_OPEN_FAIL (1013)
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 also help.
S_UNSUPPORTED_VER_OF_DA (1022)
You need to use a newer version of SP FlashTool.
S_UNSUPPORTED_OPERATION (1040)
Scatter file does not match the phone. For example, the name contains 6577, but the phone number is actually 6573
S_CHKSUM_ERROR (1041)
One solution to error 1041 (CHS_ERR):
Go to the "Help" tab, click "Open Logs Folder" and delete all logs. Next, go to the folder with the firmware and delete the “Checksum.ini” file. We flash Format+Dowloand again.
Not a panacea, but it really works, of course, if the firmware has this file. (thanks to Valdemar (http://www..php?u=28487))

S_BROM_DOWNLOAD_DA_FAIL (2004)
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 device's supply voltage.
S_BROM_CMD_STARTCMD_FAIL (2005)
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 you select ReadBack, Format or MemoryTest. You need to connect the phone in BOOTROM mode.
S_BROM_CHKSUM16_MEM_RESULT_DIFF (2020)
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.
S_BROM_CMD_JUMP_DA_FAIL (2035)
S_DA_EXT_RAM_ERROR (3001)
There may be connection problems. Check the cable and/or reconnect the cable to a different port.
S_DS_SOC_CHECK_FAIL (3013)
It is possible that there is no checkmark for uboot in the SP_Flash_Tool window. 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
S_DA_HANDSET_FAT_INFO_NOT_FOUND (3066)
Occurs during automatic formatting; you should try setting formatting addresses manually.
S_DA_INVALID_RANGE (3036)
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.
S_DA_MT_DEDICATED_PATTERN_ERROR (3094)
May appear if the flash drive is faulty.
S_DA_EMMC_FLASH_NOT_FOUND (3144)
In addition to a hardware problem, there may be a Scatter file that does not fit the phone. For example, emmc is in the name, but the phone actually has MTD flash.
S_DA_SDMMC_READ_FAILED (3148)
The error occurs when you try to write to a faulty flash drive.
S_DA_SDMMC_WRITE_FAILED (3149)

S_STORAGE_NOT_MATCH (3167)
The problem may be hardware, for example, a failed flash memory.
S_STORAGE_NOT_MATCH (3173)
The problem may be hardware, for example, a failed flash memory.
S_FT_DA_NO_RESPONSE (4001)
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 the CPU/flash. The solution is to update the firmware version.
The problem may be hardware, for example, a failed flash memory.
S_FT_DOWNLOAD_FAIL (4008)
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 and try the firmware again.
S_FT_READBACK_FAIL (4009)
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.
S_FT_FORMAT_FAIL (4010)
Format flash error! Possibly given a wrong format range, please check you format settings.
S_FT_ENABLE_DRAM_FAIL (4032)
S_FT_ENABLE_DRAM_FAIL (0xFC0)
I encountered error 4032 (0xFC0) when trying to change the firmware on a device with an MT6589 processor using the Sp_Flash_tool program.
The device was revived by formatting the phone through 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 downloaded official firmware and flashed it with all the checkboxes through the download button. Sometimes you need to remove and reinstall drivers and format again, and then reflash if the previous attempt was unsuccessful.
S_FT_MEMORY_TEST_FAIL (4048)
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.
S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
The block sizes in PMT and scatter 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
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 loading all blocks (maybe one usrdata is enough), after which the size in PMT should change to the correct one.
S_INVALID_DA_FILE (5002)
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.
S_FTHND_FILE_IS_NOT_LOADED_YET (5007)
This error can be “cured” by choosing a different firmware method: Firmvare Update -> Download or using the SP Flash Tool of a different version v.3.x.x.x<->v.5.x.x.x
S_DL_GET_DRAM_SETTINGS_FAIL (5054)
I did a full reset via USB flash drive, and now I can’t install new firmware. It is also not possible to reset again, the same error occurs. I solved the problem by reinstalling the drivers.
S_DL_PC_BL_INVALID_GFH_FILE_INFOR (5066)
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.
S_DL_PMT_ERR_NO_SPACE (5069)
It can occur when the physical memory is faulty or the flash drive has gone into protection (read only).
S_SECURITY_INVALID_PROJECT (6124)
The problem was solved as follows: Options -> DA Download All -> Speed -> Full Speed (with the High Speed mode selected, the error described above appears on my computer) and by the way, the method still worked for error 1013
SP FLASH TOOL ERROR (8038)
Occurs if the names or addresses of the blocks in the scatter differ from the table inside the phone (PMT). You need to correct the scatter file in the folder with the firmware, i.e. bring it to the same view as your current scatter file, from the firmware that you currently have on your device.
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. 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
2188
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 need 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 the new scatter type (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)
SP FLASH TOOL ERROR (8045)
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.
SP FLASH TOOL ERROR (8200)
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.

Sources:
1. http://lenovo-forums.ru/topic/1345-decoding-common-errors-flashtool

Manually editing the Windows registry to remove Error 1041 keys that contain errors is not recommended unless you are a PC service professional. Mistakes made when editing the registry can render your PC inoperable and cause irreparable damage to your operating system. In fact, even one comma placed in the wrong place can prevent your computer from booting!

Because of this risk, we highly recommend using a trusted registry cleaner such as WinThruster [Download] (developed by Microsoft Gold Certified Partner) to scan and repair any Error 1041-related issues. Using Registry Cleaner [Download] you can automate the process of finding corrupted registry entries, missing file references (such as those causing the %%error_name% error), and broken links within the registry. Before each scan, a backup copy, which allows you to undo any changes with one click and protects you from possible damage to your computer. The best part is that fixing registry errors [Download] can dramatically improve system speed and performance.

Warning: Unless you are an experienced PC user, we DO NOT recommend manually editing the Windows Registry. Using Registry Editor incorrectly can cause serious problems and require Windows reinstallation. We do not guarantee that problems resulting from incorrect use of Registry Editor can be corrected. You use Registry Editor at your own risk.

Before you manually repair the Windows registry, you must create a backup by exporting the portion of the registry associated with Error 1041 (for example, Adobe Flash Player):

Click on the button Begin.
Enter " command" V search bar... DON'T CLICK YET ENTER!
While holding down the keys CTRL-Shift on your keyboard, press ENTER.
A dialog box for access will be displayed.
Click Yes.
The black box opens with a blinking cursor.
Enter " regedit" and press ENTER.
In the Registry Editor, select the Error 1041-related key (for example, Adobe Flash Player) that you want to back up.
On the menu File select Export.
On the list Save to select the folder where you want to save the backup copy of the Adobe Flash Player key.
In field File name Enter a name for the backup file, for example "Adobe Flash Player backup".
Make sure the field Export range value selected Selected branch.
Click Save.
The file will be saved with extension .reg.
You now have a backup of your Adobe Flash Player-related registry entry.

The following steps for manually editing the registry will not be described in this article, as they are likely to damage your system. If you would like more information about editing the registry manually, please check out the links below.

When flashing Lenovo phone, 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 too long a cable

(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

H. Douglas Brown has defined linguistic errors as "a noticeable deviation from the adult grammar of a native speaker, reflecting the interlanguage competence of the learner." He cites an example Does John can sing? where a preceding do auxiliary verb has been used as an error.

Difference between error and mistake

In linguistics, it is considered important to distinguish errors from mistakes. A distinction is always made between errors and mistakes where the former is defined as resulting from a learner's lack of proper grammatical knowledge, while the latter as a failure to utilize a known system correctly. Brown terms these mistakes as performance errors. Mistakes of this kind are frequently made by both native speakers and second language learners. However, native speakers are generally able to correct themselves quickly. Such mistakes include slips of the tongue and random ungrammatical formations. repeatedly and are not recognizable by the learner. They are a part of the learner's interlanguage, and the learner does not generally consider them as errors. They are errors only from the perspective of teachers and others who are aware that the learner has deviated from a grammatical norm. That is, mistakes can be self-corrected with or without being pointed out to the speaker but errors cannot be self-corrected.