radiomanV
commented
5 years ago Hi, Technically the 'randomly generated serials' and CS to A converted devices has nothing to do with what 6.80 software is detecting as 'piracy'. In fact you can put whatever strings you want in the serial and devcode fields. The problem is a flaw in the encrypted serial block in my firmware updater which can be detected by the firmware/software, not the serial code itself. In this 80 bytes encrypted block there's a field which is a simple checksum of concatenated serial and devcode. Well this field is missing in my generated block. So please wait patiently until I'll release a fix. Regarding to so called brick caused by minipro 6.80 this.is not a brick. They have dissabled the bootmode in the firmware and this prevents further updates from being made. Fortunately you can force the boot mode and downgrade to whatever firmware version you want. Details of how to force boot mode is given here in the docs section(a simple 100 ohm resistor soldered or if you have a steady hand keep the resistor connected in the indicated points with one hand while inserting the usb cable with the other hand)
firew4lker
okurka
MiniPro v6.80 detects a wrong Dev Code and Serial Number when they were randomly generated. It also detect CS to A converted devices. Upon detection the software then bricks the TL866 when its firmware gets updated by MiniPro v6.80.
MiniPro v6.81 still detects converted devices and the wrong Dev code and Serial Number, but doesn't brick the TL866. Instead it shows that the device is a 'clone' even on genuine devices that have the wrong serial number.
Best is not to generate random numbers, but numbers that'll get accepted by MiniPro. There has to be an algorithm check in MiniPro to detect genuine Dev code/serial number combinations, both for CS and A devices.