Error 1041 sp flash tool solution. Decoding errors SP Flash Tool

Manually editing the Windows registry to remove invalid Error 1041 keys is not recommended unless you are PC service professional. Errors made while editing the registry can cause your PC to malfunction and cause irreparable damage to your operating system. In fact, even a single comma 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 registry problems. Using a [Download] registry cleaner can automate The process of finding invalid registry entries, missing file references (like the one causing your %% error_name %% error), and broken links within the registry. Before each scan, a backup is automatically created, allowing you to undo any changes with one click and protecting you from possible damage to your computer. The best part is that fixing registry errors [Download] can dramatically improve system speed and performance.

A warning: Unless you are an experienced PC user, we do NOT recommend manually editing the Windows Registry. Incorrect use of Registry Editor can lead to serious problems and require you to reinstall Windows. We do not guarantee that problems resulting from improper use of Registry Editor can be fixed. Your use of the Registry Editor is at your own risk.

To manually repair your Windows registry, first you need to create a backup by exporting a portion of the registry related to Error 1041 (eg.Adobe Flash Player):

Click on the button Begin.
Enter " command" v search bar ... DO NOT PRESS YET ENTER!
Holding the keys CTRL-Shift on the keyboard, press ENTER.
A dialog box for access will be displayed.
Click on Yes.
The black box opens with a blinking cursor.
Enter " regedit" and press ENTER.
In the Registry Editor, select the Error 1041-related key (eg.Adobe Flash Player) you want to back up.
On the menu File choose Export.
In the list Save to select the folder where you want to save the Adobe Flash Player backup key.
In field File name enter a name for your backup file, such as "Adobe Flash Player Backup".
Make sure in the box Export range value selected Selected branch.
Click on Save.
The file will be saved with the extension .reg.
You now have a backup of your Adobe Flash Player-related registry entry.

The next steps for manually editing the registry will not be described in this article, as they can most likely damage your system. If you would like more information on manually editing the registry, please see the links below.

When flashing a Lenovo phone with 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 get a four-digit code for the SP FlashTool program

Decoding of common errors:

(1003) S_COM_PORT_OPEN_FAIL
Port problem.

(1011) S_NOT_ENOUCH_STORAGE_SPACE

(1013) S_COM_PORT_OPEN_FAIL

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

Solved by replacing or changing the Scatter file

(2005) S_BROM_CMD_STARTCMD_FAIL
On phones with MTD flash, error cases:

(3001) S_DA_EXT_RAM_ERROR
Possible connection problems.

Check the cable and / or reconnect the cable to a different port. Do not 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 equipment (display, processor, GPIO).
Or in the path line there are Russian folder names for example: D: \ Firmware \ Firmware Lenovo K930 \

(3144) S_DA_EMMC_FLASH_NOT_FOUND
The problem with the hardware or the Scatter file does not fit the phone. For example, the name contains emmc, but the phone is actually with MTD flash.

(3066) S_DA_HANDSET_FAT_INFO_NOT_FOUND
It occurs during automatic formatting, you need to try to set formatting addresses manually.

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

The PMT block must be removed through the "Format" tab, and a new one from the scatter file must be filled in through the "Download" button and the SP Flash Tool will rewrite new data on the PMT block and others to the flash.

(4001) S_FT_DA_NO_RESPONSE

The problem can be hardware, for example 4001 error occurs when the Flash memory is out of order.

(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 the firmware from 8 GB to 4 GB device. For clarification, you need to look at the log file.

(4032) S_FT_ENABLE_DRAM_FAIL

(4050) S_FT_NEED_DOWNLOAD_ALL_FAIL
Block sizes in PMT and scatter.txt do not match. You need to look for a line in the BROM_DLL log.
size changed from 0x
It often happens
Partition 13 (USRDATA) size changed from 0x0000000000000000 to 0x000000000B620000
If there is no size in the scatter on the MTK processor, 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 spelled out and in this case someone or something wrote zero there: sh_ok:. To cure this case It is possible to rename the scatter.txt USRDATA to __NODL_USRDATA ... but now 8038 may appear due to the difference in names. In the general case, this error is treated by loading all blocks (maybe one usrdata will be enough), after that the size in the 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
Invalid files. There are no required files in the folder with the scatter file.

(6124) S_SECURITY_INVALID_PROJECT, MSP ERROE CODE: 0x00

Reduce the write 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 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, 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 from the scatter, the second from the PMT of the phone. It is necessary that all block names in the scatter are 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, whilst 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. On the other hand, errors are systematic in that they occur 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.

Possible errors generated by the SP Flash Tool when flashing devices based on MediaTek processors.

(1003) S_COM_PORT_OPEN_FAIL

Port problem.

It may occur if, for example, com-ports are disabled in your BIOS (although in this case the com-port is virtual, and the physical USB, but when disabled, you simply will not see the equipment on which the preloader drivers are installed). This is either a problem in the USB cable (changing the cable for firmware helps), or a problem in the USB port of the computer (poking 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 (This is usually a kernel block or Recovery). Perhaps changing the version of the flasher 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 the SP Flash Tool

(1040) S_UNSUPPORTED_OPERATION

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

(2005) S_BROM_CMD_STARTCMD_FAIL

On phones with MTD flash, error cases:

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

(3001) S_DA_EXT_RAM_ERROR

Possible connection problems. Check the cable and / or reconnect the cable to a different port.

(3013) S_DS_SOC_CHECK_FAIL

It is possible that the uboot bird is not in the SP Flash Tool window. uboot - operating system loader + drivers for initializing the main equipment (display, processor, GPIO). Or when there are Russian folder names in the path line 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 the problem with the hardware, it can be when the Scatter file does not fit the phone. For example, the name contains emmc, but the phone is actually with MTD flash.

(3066) S_DA_HANDSET_FAT_INFO_NOT_FOUND

Occurs during automatic formatting, you should try to set formatting addresses manually.

(3036) S_DA_INVALID_RANGE

The problem is that the SP Flash Tool, before flashing, compares the PMT block address on the flash drive of the device 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.

Solution:

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, click on the "Format" button in the SP Flash Tool (do not change anything in the window that opens, just click OK), then click "Download" and the SP Flash Tool will rewrite new data on the PMT block and others on 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 the C drive:

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

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

(4008) S_FT_DOWNLOAD_FAIL

Solution:

flasher version change, possibly even to an older version;
changing the firmware cable;
it is also possible that the battery is dead during the firmware. Solution: charge your 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 a file, or the file cannot be overwritten. it is blocked (see the log).

(4032) S_FT_ENABLE_DRAM_FAIL

The error occurs when trying to change the firmware on a device with a processor through the SP Flash Tool.

Solution:

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, then flash the official or from your device firmware and flash all the blocks (check all the boxes). Sometimes you need to uninstall and reinstall the drivers and do the formatting again, and then reflash if the previous attempt was unsuccessful.

(4050) S_FT_NEED_DOWNLOAD_ALL_FAIL

Block sizes in PMT and scatter file do not match. It is necessary 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 spelled out and in this case someone or something has written 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 the general case, this error is treated by loading all blocks (sometimes one usrdata is enough), after that the size in the PMT should be changed to the correct one.

(5002) S_INVALID_DA_FILE

When setting up the SP Flash Tool download agent, you need to select the flasher that comes with this version. Choosing other agents gives this error.

(5054) S_DL_GET_DRAM_SETTINGS_FAIL

If, when fully assembled through the SP Flash Tool, there is no way to install a new firmware, and you also cannot reset it again.

Solution:

Reinstall the driver again.

(5066) S_DL_PC_BL_INVALID_GFH_FILE_INFOR

Invalid files. For example, we chose a scatter file from a folder with files not yet prepared for FT. It is necessary to select the scatter file from the folder prepared for FT files.

(5069) S_DL_PMT_ERR_NO_SPACE

Appatana problem with flash memory

The error occurs:

If you do Format, then the error S_PART_NO_VALID_TABLE (1037) will come out and it says that you need to do Download to create the partition table.
Firmware Upgrade does not allow to do -> again due to error 1037
You can download PRELOADER alone. Loading any other section throws error (5069) S_DL_PMT_ERR_NO_SPACE.
Does not depend on the version of the scatter file.
The FAT does not depend on the size of the partition either.
You can make Manual Format - it gives, but within the UA Size. After that, an attempt to fill any section 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:

We select: Options -> DA Download All -> Speed -> Full Speed (when the 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 string 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 from the scatter file, the second from the phone's PMT. It is necessary that all block names in the scatter are 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:

1) Firmware of the device through the programmer.
2) In rare cases, the firmware helped through the DOWNLOAD button with all the checkmarks installed.

(8200) SP FLASH TOOL ERROR

It occurs when you try to flash the device on one platform with the firmware from another.

Solution:

In other cases - changing the version of the flasher.

Invalid ROM or PMT address

If the hardware part of the device is known to be in order, the memory must be formatted, and then the firmware is in a standard order.