If this is correct I must reflash my device with your new reflash tool (TL866.exe v2.4) keeping my original serial number.
This should fix the checksum and I should be safe to use the new 6.8x software.
At this point the 6.8x will detect a legit TL866A and will upgrade the firmware without any issue.
Yes this is correct. If you have the original serial number just do what i said above to fix the checksum and you can upgrade to last version.
As a matter of fact the correct checksum is more important than an random generated serial. So from what i tested so far we can have the following situations:
1. Original serial and good checksum. This case is for genuine unmodified devices or converted devices with good checksum. These are not detected.
2. Original serial code and bad checksum. This will detect as "converted from CS" for A devices and "maybe clone" for CS devices. A simple checksum fix is needed here.
3. Random generated serial code and bad checksum. These devices are detected as pirated, "the infringement of copyright and piracy!" message.
4. Random generated serial code and good checksum. These devices are not detected by the minipro software and you don't get any warning! These bad serials are still detected by the firmware, but so far there's no limitations or warnings, so this is-yet-a good case. The new
TL866 firmware updater V2.4 will generate compliant serial numbers so please generate another one to correct this issue.
Regarding to the serial code there's no CS or A serial code but only valid serials. I have tested this. The 8 chars. Device code and 24 chars. serial number are somewhat connected as an unique ID.
A special case is for devices who have the copy protect bit unset in the config bytes. These devices have the bootmode dissabled in the firmware and you can't do any upgrade/downgrade/reflash or else because he can't enter in boot mode; so this is a semi-brick and my updater will report 'Reset error!' when you try to reflash something.
For these devices the bootmode must be forced as i stated above with the help of one resistor.
These devices are those which were reflashed by an external programmer with a hex file generated by my tool. This generated hex file had the CP bit unset.
So, for these kind of devices you must set the CP bit and correct the bad checksum.
A very special case is for genuine unmodified devices who are detected as pirated durring the firmware update and are deliberately bricked by deleting(overwriting) the bootloader.
These devices can be restored only by an external programmer(pickit) with a new generated firmware.
The
bad checksum is actually missing checksum. At that time i was not aware of it. This is a single byte 8 bit checksum of the serial code inserted somewhere in the 80bytes encrypted serial block.
At the development time (five years ago) i was expected to such actions fom the manufacturer. This is why the advanced window in my firmware updater have all those settings.
I don't know what manufacturer want. After five years and a programmer no longer in production to have these anti-user actions is...