In the process of firmware Android devices using SP Flash Tool program periodically occur errors. Decision of which is often get out a large of time.
For your information and convenience, a compilation of the most common error codes with a detailed description and variants of their solution.
Errors
| Error code | Error name |
|---|---|
| 1002 or 0x3EA | S_INVALID_ARGUMENTS |
| Error description 1002 and solution Incorrect Scatter file. For example, in the scatter file, the PRELOADER and DSP_BL blocks are disabled | |
| 1003 or 0x3EB | S_COM_PORT_OPEN_FAIL |
| Error description 1003 and solution The problem with the port. For example, an error may occur if COM ports are disabled in the BIOS. Even if the COM port is virtual, and the physical USB. In this case, you will not see the equipment on which the PRELOADER drivers are placed. The problem can be in the USB cable, in this case, replace the cable. If the USB port of the computer is faulty, then it is necessary to puncture the cable to another port. Theoretically, it can occur in the USB UART mode. The port was visible, it was selected in the Flash Tool settings, the program recorded it in the INI file, after which the system was rebooted with the port disabled, and immediately launched the Flash Tool without selecting the port .. When after the red strip pass to 100% as a result of the firmware, Operation buttons are again available for clicking, but no error message, no green circle, this error appears, or similar to it, the code of which is 1013. In this state, the Flash Tool does not close the COM port, and trying to restart any operation by reconnecting the device will cause an error. If the program has moved into such an undefined state, then you need to close it and restart it | |
| 1011 or 0x3F3 | S_NOT_ENOUCH_STORAGE_SPACE |
| Error description 1011 and solution Occurs in the event that the size of one of the parts of the firmware exceeds the size of the space allocated to it. This is usually a kernel or recovery block. This error sometimes occurs on undeveloped versions of the Flash Tool. Replace the version of the driver used | |
| 1012 or 0x3F4 | S_NOT_ENOUGH_MEMORY |
| Error description 1012 and solution Use a more recent version of the driver | |
| 1013 or 0x3F5 | S_COM_PORT_OPEN_FAIL |
| Error description 1013 and solution Error similar to error 1003. Solutions should be sought on the same principle. Can help change the version of the flash driver, or flashing the device with the battery off | |
| 1018 or 0x3FA | S_UNKNOWN_TARGET_BBCHIP |
| Error description 1018 and solution Use a more recent version of the driver | |
| 1022 or 0x3FE | S_UNSUPPORTED_VER_OF_DA |
| Error description 1022 and solution Use a more recent version of the driver | |
| 1040 or 0x410 | S_UNSUPPORTED_OPERATION |
| Error description 1040 and solution Scatter file is not suitable for the device. For example, the file name contains the version number 6777, and the device version 6555 | |
| 1041 or 0x411 | CHS_ERR |
| Error description 1041 and solution You must go to the tab Help, click Open Logs Folder And delete all the logs. Go to the folder with the firmware and delete the file Checksum.ini | |
| 2004 or 0x7D4 | S_BROM_DOWNLOAD_DA_FAIL |
| Error description 2004 and solution The problem may be version of the SP FLASH TOOL. Download the version at the end of which there is the designation SEC. An error may occur if the operating system has a lot of USB drivers for different devices. Use the program USBDeview To remove installed USB drivers and perform firmware via Flash Tool. Can help connect the device with the volume key held down + or -. If the above methods do not help, after the error appears, you must immediately close the window with an error and immediately click the button download | |
| 2005 or 0x7D5 | S_BROM_CMD_STARTCMD_FAIL |
| Error description 2005 and solution An error can occur on MTD devices if the check box is not checked on the PRELOADER or DSP_BL blocks when selecting the Download mode. You must use a suitable version of the Flash Tool, for example v2.xxx for MT6573 phones, or disable DA Download All mode. If you select Download mode, a check mark is installed on the PRELOADER or DSP_BL units, you must remove it from these blocks. If you need to flash these blocks, connect the phone in BOOTROM mode. If you select ReadBack, Format or MemoryTest, you need to connect the device in BOOTROM mode. You can try flashing the device with the battery off | |
| 2020 or 0x7E4 | S_BROM_CHKSUM16_MEM_RESULT_DIFF |
| Error description 2020 and solution In the Flash Tool settings, forcibly check the box, indicating that the device is without a battery. After that, connect the device through the test point, but already with the battery | |
| 2035 or 0x7F3 | S_BROM_CMD_JUMP_DA_FAIL |
| Error description 2035 and solution After click Download connect to the computer an off device with pressed volume buttons | |
| 3001 or 0xBB9 | S_DA_EXT_RAM_ERROR |
| Error description 3001 and solution Perhaps the error is connected to the connection. Check the cable, reconnect the cable to another USB port | |
| 3012 or 0xBC4 | NAND_FLASH_NOT_FOUND |
| Error description 3012 and solution The problem is related to the definition of flash memory device. Use a different version of the program. As versions of different versions are updated, information about flash memory. If the above option does not help, try to flash the device on another computer, because There are problems that do not allow you to correctly determine the memory on a particular machine | |
| 3013 or 0xBC5 | S_DS_SOC_CHECK_FAIL |
| Error description 3013 and solution It's possible that the check mark for the Uboot checkbox is not checked in the flash tool's settings. Uboot - the boot loader of the operating system and drivers to initialize the main hardware, such as display, processor, GPIO. The error can occur if incorrect characters, hieroglyphs, are present in the path line on which the program or the firmware is located. It is acceptable to place the program and the firmware file only along the path that consists entirely of Latin characters. | |
| 3054 or 0xBEE | S_DA_NFB_BOOTLOADER_NOT_EXIST |
| Error description 3054 and solution Use a different version of the program. Try to replace the version of the driver with the fifth to the third version | |
| 3066 or 0xBFA | S_DA_HANDSET_FAT_INFO_NOT_FOUND |
| Error description 3066 and solution Occurs when automatic formatting occurs. It is necessary to set the address of the formatting manually | |
| 3144 or 0xC48 | S_DA_EMMC_FLASH_NOT_FOUND |
| Error description 3144 and solution An error occurs if there is a hardware problem with the device. It can also occur if the Scatter file does not fit the device. For example, in the name there is emmc, and the device is actually with MTD flash. There is a possibility that the problem will be solved if you use another computer and the operating system. It is preferable to use a computer running Windows XP with newly installed drivers | |
| 3149 or 0xC4D | S_DA_SDMMC_WRITE_FAILED |
| Error description 3149 and solution Use a different version of the flash driver. If you are stitching 3 version, try version 5, or vice versa. Select the Format all + download mode. It is necessary to reinstall the drivers for the device and ensure that the device in the Device Manager is correctly displayed as MTK USB PORT. Launch the Flash Tool, uncheck all items except PRELOADER and sew in Download mode. If the progress goes but at the end there is an error, then we are sure that we will only flash PRELOADER. At the top of the Flash Tool window, next to the Download button, click the Format button. A window of formatting settings with the formatting modes Auto and Manual opens. In the Auto mode, there are two settings, check the upper box and click OK. The formatting starts. After finishing the formatting, re-flash the PRELOADER. After successful firmware PRELOADER, flash the device completely | |
| 3168 or 0xC60 | S_CHIP_TYPE_NOT_MATCH |
| Error description 3168 and solution Incorrect scatter file. Use the Scatter file from your device | |
| 4001 or 0xFA1 | S_FT_DA_NO_RESPONSE |
| Error description 4001 and solution Change the USB port and transfer the Flash Tool to the root of the disk. Perhaps there is no information about the CPU/Flash in the Download Agent, so Use a more recent version of the driver. The error can be hardware, for example, if a failed flash memory | |
| 4008 or 0xFA8 | S_FT_DOWNLOAD_FAIL |
| Error description 4008 and solution Use a different SP FLASH TOOL version. There is a chance that the replacement version will help to the older one. The problem can be in the USB cable, in this case, replace the cable or USB port. Perhaps in the process of inserting a battery. Charge the device and try the firmware again. You can try to remove the battery from the device and try to flash without it. Try formatting the device | |
| 4009 or 0xFA9 | S_FT_READBACK_FAIL |
| Error description 4009 and solution In addition to reading errors in the device itself, an error can be observed in the event of errors in the file system of the computer. For example, there is not enough disk space, or the file can not be overwritten. It is blocked. In order to understand the reason, you need to look at the Flash Tool | |
| 4010 or 0xFAA | S_FT_FORMAT_FAIL |
| Error description 4010 and solution It is recommended to change the version of the program to version 5, it is highly advisable to start with version 5.1352.01 and try to flash the machine through the Firmware upgrade mode. The firmware must be original for the machine and contain all the blocks. Try changing the firmware cable to a better one | |
| 4032 or 0xFC0 | S_FT_ENABLE_DRAM_FAIL |
| Error description 4032 and solution An error may occur when flashing on a machine with an MT6589 processor. To fix this, format the device using the Format button. Do not format if you have an MT6575 or 6577 processor. After formatting, flash the device with all the checkmarks by clicking the Download button. You can try to reinstall the drivers and perform the formatting again. Run the firmware if the previous attempt was unsuccessful. If nothing has helped, then try changing the version of the flash driver. It is recommended to start with version 5.1352.01. The error is due to the incorrect PRELOADER block. It is necessary to find a native PRELOADER and flash it. If the firmware does not work with the standard method, then it may be necessary to flash the device through the testpoint. This error can be caused by a low battery charge. You can try to solve the problem by closing the 4th and 5th pin on the USB connector | |
| 4037 or 0xFC5 | S_FT_FS_READ_FAIL 0xFC5 |
| Error description 4037 and solution An error can occur if there are incorrect characters in the path line on which the program is located or the firmware, hieroglyphics. It is acceptable to place the program and the firmware file only along the path that consists entirely of Latin characters. | |
| 4050 or 0xFD2 | S_FT_NEED_DOWNLOAD_ALL_FAIL |
| Error description 4050 and solution Occurs when the block sizes in the PMT and in the Scatter file do not match. In general, this error is eliminated by loading all the blocks, then the size in the PMT should change to the correct one. You can try changing the version of the broacher | |
| 4058 or 0xFDA | S_FT_GET_MEMORY_FAIL |
| Error description 4058 and solution The error occurs when there are problems with the flash memory. It is not recommended to solve the problem yourself. Options for eliminating the error: warming up the flash memory chip with a blowtorch at a high temperature, about 400 degrees Celsius. Probably, it will be necessary to replace the chip with a donor fee, or to a new one | |
| 5002 or 0x138A | S_INVALID_DA_FILE |
| Error description 5002 and solution When configuring the Flash Tool Download Agent, you must select the driver that came with this version. Selecting other agents causes this error | |
| 5007 or 0x138F | S_FTHND_FILE_IS_NOT_LOADED_YET |
| Error description 5007 and solution The error usually occurs if the Flash Tool has a check mark on the block to which the path is incorrectly specified or absent. To fix this, you must specify the correct path to the desired firmware block. Also, if this error occurs, use a different SP FLASH TOOL version, for example v5.1352.01 | |
| 5054 or 0x13BE | S_DL_GET_DRAM_SETTINGS_FAIL |
| Error description 5054 and solution The error lies in the fact that the Flash Tool could not get the device's RAM settings. It can occur in the event that a full reset via the Flash Tool has been performed. Also, an error can occur when data is exchanged between the Download Agent and the device. If the driver does not work correctly, the transfer failure can occur only if you have Windows XP with a service pack lower than the third one. You need to install a third service pack. In older versions, the usbser.sys driver has not been updated and there will be no need to reinstall it | |
| 5066 or 0x13CA | S_DL_PC_BL_INVALID_GFH_FILE_INFOR |
| Error description 5066 and solution Incorrect Scatter file. It can occur if you selected Scatter from a folder with files that are not prepared for Flash Tool. You must select the Scatter file | |
| 5069 or 0x13CD | S_DL_PMT_ERR_NO_SPACE |
| Error description 5069 and solution The error most likely arises from the peculiarities of flash memory. It happens that formatting, even low-level, does not have any effect. Ie in flash memory, everything remains as it is. If you do Format, you may receive an error 1037 and a message is displayed, with the need to perform Download to create the partition tables. Firmware Upgrade can not be performed, due to an error 1037. You can make Download only PRELOADER. Loading any other partition will generate an error 5069. From the Scatter version, the FAT partition size does not depend. You can execute Manual Format, but within the UA Size. After formatting, the attempt to fill any section again is reduced to the error 5069 | |
| 6045 or 0x179D | S_SECURITY_SECURE_USB_DL_IMAGE_SIGN_HEADER_NOT_FOUND |
| Error description 6045 and solution It is recommended to change the version of the flasher to version 5, it is highly desirable to start with version 5.1352.01 | |
| 6104 or 0x17D8 | S_SECURITY_SECURE_USB_DL_DA_RETURN_INVALID_TYPE |
| Error description 6104 and solution It is recommended to change the version of the flasher to version 5, it is highly desirable to start with version 5.1352.01 | |
| 6124 or 0x17EC | S_SECURITY_INVALID_PROJECT (6124), MSP ERROE CODE: 0 x 00 |
| Error description 6124 and solution There is a possibility that the error will disappear after the firmware of the native PRELOADER via the Download button. After that, perform the modified version of the Recovery and the full firmware | |
| 6126 or 0x17EE | S_SECURITY_SECRO_HASH_INCORRECT |
| Error description 6126 and solution The error is often found on devices Huawei G610, Huawei G700, LG L60 Dual and currently not solvable at home. Consequences: periodic reboot, there are deleted files in the device, an error occurs when checking the memory for writing. The reason is that the device has a locked loader, which is why it is necessary to flash the unlocked SEC_RO for unlocking and further flashing. All is reduced to the fact that it is with the firmware SEC_RO that this error occurs. It is recommended to replace the memory in the service | |
| 8038 or 0x1F66 | SP FLASH TOOL ERROR/PMT changed for the ROM; it must be downloaded |
| Error description 8038 and solution To resolve this error, you must use the Firmware upgrade mode. Attention! The firmware must be specific to the firmware to be flashed and contain absolutely ALL blocks that are usually found in the stock firmware | |
| 8045 or 0x1F6D | SP FLASH TOOL ERROR |
| Error description 8045 and solution The error is similar to 8038, but in practice, editing the Scatter file does not help. To solve the problem, you can contact the service center to flash the device through the programmer. At home, sometimes the version of the firmware is activated via the Download button with all the checkmarks selected. You can also try changing the version of the firmware to version 5, it is highly advisable to start with version 5.1352.01. The problem can be hardware | |
| 8200 or 0x2008 | SP FLASH TOOL ERROR |
| Error description 8200 and solution The error occurs if you try to flash the machine on one platform, firmware from another. For example, you have MT6577, and you are trying to flash firmware from the device to MT6575. You can try changing the version of the firmware to version 5, it is highly desirable to start with version 5.1352.01 | |
| 8417 or 0x20E1 | SP FLASH TOOL ERROR: The load scatter file is invalid! |
| Error description 8417 and solution An error can occur if there are incorrect characters in the path line on which the program is located or the firmware, hieroglyphics. It is acceptable to place the program and the firmware file only along the path that consists entirely of Latin characters. | |
| Unrecognized ROM detected | |
| Error description and solution The error occurs if the markup does not match the Scatter file and the device. Most often it happens when the device performs actions on custom redrawing through changing partition parameters in the EBR. In this case, Scatter itself is usually not changed. To resolve the error, you must perform forced formatting with the parameters: Auto Format Flash and Format whole flash except Bootloader to initialize the device. Do not forget to backup NVRAM, IMEI beforehand. After formatting, you need to perform a full firmware via Download | |
| The application was not started because it was not properly configured. Reinstalling the application can solve this problem | |
| Error description and solution Install the package Microsoft Visual C ++ 2005-2008-2010-2012-2013-2017 redistributable Package. Also make sure that you unpack the firmware into the root of the disk on the computer, and do not try to start it from the archive | |
Attention
All actions you perform on your own risk. For damaged devices Flash-Tool.com site is not responsible