[Enabled]

Failing to sign the file into the DME. This only occurs with k+dcan cable or other cheap interfaces. This occurs because k+dcan cable when flashing locks its internal speed to a certain value and it can't change when required by ediabas, so when flash is ended it can't change internal speed required for signing the file and the car won't start. (sign a file require diagnostic speed, flash require flashing speed, with speed i mean "can line baudrate"). In fact flash goes to 100% and then stuck and error, it can't sign the file.

---

It's bricked. You absolutely CANNOT flash it, nor recover it with K+DCAN.

The cable writes a wrong byte every 200 or so bytes. It corrupted everything.

Absolutely not bricked, sign the file with tool32 if you can with signature_pruefen job or flash it again but with icom and the file will be signed.

If you need i can help you with teamviewer obviously for free but you'll need an icom and better a power supply.

Technically that is the meaning of bricked . The problem is not only the signature bytes, a lot of data is corrupted. But of course it can be recovered.
4 years ago I did the same thing with an M5 SMG module. ICOM or quality cable can recover it because bootloader is untouched.

[mrproper]

Not completely true.

First of all winkpf does not sign a file after write... It literally checks the signature after flashing. If flash is corrupted, rsa md5 hash is not correct when signature is checked and thus ecu stays in programming state.

Second, if program and cali is bricked, you still can recover, but not over CAN.

If you have  an ecu with :blocked debugger port: (what's also not correct btw) it is still accessible if you have proper tools for that. (and i do not mean generic BDM interface

[rs@chip]

I would try ista-p in your case while you waiting for Icom to arive..It worx litle diferent than kfp which can maybe help in your case..

[dpaul]

Not completely true.

First of all winkpf does not sign a file after write... It literally checks the signature after flashing. If flash is corrupted, rsa md5 hash is not correct when signature is checked and thus ecu stays in programming state.

Second, if program and cali  is bricked, you still can recover, but not over CAN.

If you have  an ecu with :blocked debugger port: (what's also not correct btw) it is still accessible if you have proper tools for that. (and i do not mean generic BDM interface

What tools will read the ecu with disabled BDM?