[Turbotime]

Had my friends f10 m5 not write successfully when trying to return to stock today, automatic recovery kept failing so then i exited and could not communicate with ecu after, i did not know the recovery setting in the kess is different from the one that comes up automatically so i tried using esys to completely flash the ecu. It flashed but would not detect or write the cafd on one of the ecus. Apart from cafd all was updated. I then used recovery function on kess and it managed to get the ecu working again but the files i had were for the oroginal 2014 software, on top of this kess would not find a vr of the current data so i tried flashing with esys now ecus were showing cafd and healthy but it failed on both ecus (when no cafd other ecu was writable with esys) so i used autotune to get a vr and wrote that back in successfully. My question is what do i do next, can i use ista or esys to force full write in and make sure data is not a mismatch of original and new versions.

[Thorsten]

Hm,

with E Sys, create a new working TAL, flash both DME and code them.
Then use Autotuner to get a virtual read...


Thorsten

[Turbotime]

Would i be right in thinking of this as the process
Fa
Svt
Select correct shipment
Svt sol
Tal
Then load tal and fa (select svt sol as well?)
Blflash, swdeploy and cddeploy
Code dme's

After can vr read and work from there as normal. If it still fails to write in esys is there a way to force the write?

[jaramillo]

I could help you remote

[Turbotime]

Thank you would like to try and do myself if possible

---

Take it i am not correct in my process?

[jaramillo]

You can proceed as intended.
Dot forget to press "HW-ID from SVTactual" and then save svt soll

[Turbotime]

Ok will do, i did not know to do that as well. Thank you