[Android General] Tzul:
I've never gotten those errors, and I've been using the SPFT for years, first with three different phones (based on the MT6589 and MT6582) and now with this tablet.

You'll definitely lose NVRAM when you use the "Format All + Download" mode. Because it really formats everything, including NVRAM.

You might also damage something if you use an incorrect scatter file or obsolete SPFT version.

Why? That only forces people to manually rename one of those files, or to install SuperSU. Not very user-friendly.

If it's about preserving the stock recovery - well, you should have saved that before with SPFT. But if you didn't, you can still get it - just use the applypatch command manually, with a terminal or ADB.

# get root
su
# review the relevant line from the original install-recovery.sh script, most importantly the SHA1 checksums
grep "applypatch -b" /system/bin/install-recovery_original.sh
# copy the output of this grep command and adjust it where necessary...

# Example 1: flash the stock recovery after TWRP has renamed recovery-from-boot.p to .bak
# The size and SHA1 values can differ from version to version, that's why we needed to review install-recovery.sh
applypatch -b /system/etc/recovery-resource.dat EMMC:boot:7100416:e3aae3861a79470d5bdac7a8982d527f07548dcf EMMC:recovery 11a0f3ef36035a906dcea1944e970ff649acfff6 8173568 e3aae3861a79470d5bdac7a8982d527f07548dcf:/system/recovery-from-boot.bak

# Example 2: create a stock recovery image at /sdcard/recovery.img, but don't flash it...
# also use /sdcard/boot.img instead of the current EMMC boot partition
bootsha1=$(sha1sum /sdcard/boot.img | cut -d' ' -f1)
recoverysha1=11a0f3ef36035a906dcea1944e970ff649acfff6
applypatch -b /system/etc/recovery-resource.dat /sdcard/boot.img /sdcard/recovery.img $recoverysha1 0 $bootsha1:/system/recovery-from-boot.bak

The command format is "applypatch -b {bonusfile} {sourcefile} {targetfile} {targetSHA1} {targetsize} {sourceSHA1:Patchfile}".

The sourcefile and targetfile can be EMMC partitions (as in Example 1) or regular files (as in Example 2). For partitions, the format is "EMMC:{partitionName}:{size}:{SHA1}"; for the partition target, "EMMC:recovery" is enough, because SHA1 and size follow as separate arguments (targetSHA1 and targetsize). The targetsize isn't really important, it can be specified as 0, like I did in Example 2.

This is undoubtedly a bit complicated for people not experienced with a command shell, but I think a few people here will appreciate the info.

Yeah, we've talked about it before, all those different MT numbers are confusing. The A10-70F has [ro.hardware]: [mt6752], by the way.

Please let me know if the patched lk.bin works, if you try it. It's quite an easy patch - there's a sort of partition table in lk.bin with 80 bytes per entry, and each entry stores the partition name, a few other things, and whether or not fastboot is allowed to erase and to flash that partition. I simply set the "erase" and "flash" flags to 1 for a few more partitions.

PS: I just compared your lk_S114.img with the new lk.bin of the A10-70F, and they are almost identical. Only 14 bytes differ, probably some initialisation values for the SIM card / LTE stuff.