[corpus]

requesting Zb #7842483 for flashing 2008 e92 m3 Dme.

[willisodhiambo]

Why not use the latest version?

[corpus]

Why not use the latest version?

I tried flashing it with Sp Daten v66. Came up with a flash failed error.
Now whenever I try flashing the Dme I get an ZB# not found error.

---

What are the other possible Zb# for E9x M3 DME ?

[Enabled]

Did you use a cheap K+DCAN?
There is a firmware issue with the K+DCAN that will brick certain dmes, smg modules, etc. by writing in corrupt data.
This is why China K+DCAN should generally be avoided for flashing, unless on the newer ediabaslib fixed firmware.

---

MSS60 and MSS65 are easily bricked by K+DCAN.

[Impac]

Yup for M3 dme you will need an Icom or get the kdcan from Bimmergeeks

[Enabled]

If you need help unbricking/recovering the dme, I see you may be USA based... Send PM.

[corpus]

i'm finally able to start the flash procedure once again. 
here are a few screen shot of the error after the completion of flash

what does these error mean?

[Enabled]

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

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

[____ANGEL___]

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.

[corpus]

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.

ill order a icom .Thank you i appreciate you taking the time to explain the meaning of the error codes.