For older Android 9-10 devices, you can trick the verification.
If disabling the checksum results in a bootloop or another error, your firmware files are legitimately corrupted or intended for a different device variant.
Note: If you have tried multiple versions of the tool and verified the ROM is correct for your specific model, but still get 1042, it is possible your device has a hardware failure (dead EMMC chip). sp+flash+tool+error+1042+verified
In the SP Flash Tool, typically indicates that the flashing process timed out because the tool was unable to communicate with the device or the operation took longer than the allocated timeframe. When this occurs alongside a "Verified Boot" message, it usually means the device's security measures are preventing unauthorized firmware from being written. Quick Fixes for Error 1042
(often accompanied by the message S_TIMEOUT or compatibility blocks) is a common flashing error that occurs when the software fails to maintain or establish proper communication with a MediaTek (MTK) device during a firmware update. For older Android 9-10 devices, you can trick
When Error 1042 occurs, the following sequence is consistently observed:
Error (1042): Verified boot is enabled. Please download verified image (auth file) or disable verified boot. [HINT]: Please use an authenticated DA file (MTK_AllInOne_DA.bin with auth). In the SP Flash Tool, typically indicates that
If editing the file doesn't work, completely delete the checksum.ini file from the ROM folder.
The default Download Agent cannot initialize the device hardware. Change DA to MTK_AllInOne_DA.bin .
Error 1042 in SP Flash Tool is a communication protocol error that typically occurs during the "Download" or "Firmware Upgrade" process. It generally indicates that the tool is attempting to write a file to a NAND/Flash address that does not exist or is not recognized by the target device's scatter file configuration.