SP Flash Tool Error With Solution [Part 1]

SP Flash Tool Error With Solution All Here 2017 

Lots Of time we face a problem when working with sptool when we flash mtk android Phone

here we will discuss and share sptool problems/errors. why it happens and what is its solution.

There is some mode in mtk for connect phone to pc, read below to know more

BOOTROM:

(in Device Manager is usually seen as MTK USB Port with pid = 003).

In order to connect your phone in this mode, we need some key combinations, like vol up + cable, connector, home button + cable connect, we have to keep try until we found correct key for this
Sometimes we need special cables or test points to get this mode.

Preloader :

(Port MediaTek USB VCOM with pid = 2000).
Its most common mode in mtk android phones, when we trying to flash phone using sptool and connect phone in power on phone condition to USB, phone connect as preloader

Is it sometime hard to install drivers in this mode, as it quickly disappear, but its not much hard if you faster then your pc
Just kidding you should install driver from exe base-installer

DA_HIGHSPEED:

(Port MediaTek DA USB VCOM with pid = 2001).
Ok when you flash your phone,you connect first in bootrom mode or in preloader,as sptool detect your phone, its give command to phone for DA_Highspeed download,to load the firmware in phone.
So it will always good to check drivers when flashing phone with sptool, if sptool giving error after the first red line, you should check for Da drivers.

..................

Guide How To Disable DA Download All :

Sometimes off mode DA Download, All helps to avoid errors on phones with MTD (nand) flash. The latest versions of FT this cannot be done from the menu, you must change the file platform.XML (Inside sptool flasher). You need to change the platform of your phone keys usb_download_support and da_dl_all_support to "true" to "false" Warning! This only works if not marked daw blocks preloader and dsp_bl! If you need to sew the blocks, it is necessary to put true!



After these changes, you must connect the cable to the PC immediately after clicking on Download , and wait for the end of the frame.

SP Flash Tool Errors and why It Occurs

• S_UNSUPPORTED_OPERATION (1040)

Scatter file does not fit the phone. For example, in 6577 the title is present, and the phone is actually 6573.

• S_DA_EMMC_FLASH_NOT_FOUND (3144)

Besides problems with iron can be Scatter when the file is not the phone. For example in the title is present emmc, and the phone is actually an MTD flash.

• S_BROM_CMD_STARTCMD_FAIL (2005)

On phones with MTD flash if an error occurs:

1. When you select Download to block preloader or dsp_bl not set daw. You should use the appropriate version SPFT, such v2.xxx for phones MT6573, or off DA Download All.
2. When you select Download to block preloader or dsp_bl set daw. It is necessary to uncheck these blocks! If these blocks need to flash, it is necessary to connect the phone to BOOTROM.
3. When selecting Readback, Format, or MemoryTest. It is necessary to connect the phone to BOOTROM.

• S_FT_READBACK_FAIL (4009)

In addition to reading errors in the phone the same error for errors in the file system PC. Eg not enough space for a file or file cannot be overwritten because it is locked. To clarify the log should look.

• S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)

Do not match the size of the blocks in the PMT and scatter. We must look at the logline BROM_DLL

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

This error may occur after the curve editing scatter during treatment error 8038. Treated loading FT through all blocks, or only one block user data, then the size of the PMT should switch to the right. Instead, the entire block can be sewn userdata_nvram_only.img from its backup file or a pacifier.

• S_DL_PC_BL_INVALID_GFH_FILE_INFOR (5066)

Wrong files. For example when the scatter of the chosen folder is not yet prepared for the FT files. It is necessary to choose the scatter in the folder prepared for FT files.

• SP FLASH TOOL ERROR (8038)

This error Occurs If:=For phones with the old type scatter (MT6515 / 16/17/73/75/77/89):
Names and location of the blocks in the scatter differ from the table inside the phone (PMT). We must look SP_FLASH_TOOL.log and look at it line NOT MATCH


Example:

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

in this example, it is necessary to replace the name scatter CUSTPACK2 on CUSTPACK. If a few differences, this error will occur until the scatter after amendment does not become identical to the PMT. You can just fix it if we compare the tables are a little higher in the log line NOT MATCH. The first of scatter, the second of the PMT phone. It is necessary that all blocks in the names scatter were the same as in the second table

Edit scatter must be carefully! Change the names and the number of lines to save the original! Some manage to remove the newline and string imam unit is on one line with a brace. FT sees this block without PMT and writes it. Then we need to spend efforts to restore this table.