Hi, forum.
l need help for understand which is the problem, recover my ECU and learning for not do it again.
VW tiguan Bosch 0281015192 DIESEL EDC17CP14
Read by boot tricore with MPPS, all ok full backup, Delete DTC code and write in bench again all ok.
When l put the ECU into the car, the car not start ,no comunication with diagnostic, Vagcom ,Odis, nothing no comunication with engine.
Open the ECU recover in bench with MPPS in boot mode write OK,
Put again into the car, but the car not start and no comunication , the fan run always :thumbdown:
I read in bench with ktag and read new backup folder all ok.
what can l do?

Hy, nobody. l can pay for this :wave: :wave:

did you fix this

Some EDC17, MED17 will recognize if you only delete dtc ;) and than dont work.
Post backup file so can be check if ok.

Why dont you work with ktag on them if you got, mostly more stable than Mpps (99% got fake tool of em).
Clones on EDC, MED17 allways risky.

Hello everyone and i'm sorry if i'm posting in the wrong section (IDK how to create a new post).
I'm in dire need. :cry:

I have encountered an error while writing via obd after i used EcuSafe 2.0 DPFOFF for my map.
After it finishes flashing the ECU, "Block data checksum error" in User Information area is displayed.
First 4 tries were successful with different versions of my ecu file, the last four were not successful with any file but
still completed with 100%. Ecu identification via obd still works but engine won't start and i'm seeing
a lot of instrument cluster lights + engine fans are 100% which are not helping with battery life. 
Writing original or any version of modified file now fails with the same error no matter the mode i'm writing in. 
While writing there is something displayed to "User Information" area when the progress bar reaches 75% (adress: 5FF3A)
then it continues with "Programming ECU now".
It is too fast to read but managed to catch most of the lines (at 5FF3A):
"Controlling checksum now.. "
"Wait..Routine not complete"
"Req(uired) *something* (down)load"
"Erasing flash now.. "
"Controlling flash" 
I would like to know if this is a software problem with MPPS, a hardware (interface/ ECU) problem or the fact that i've written a bad mod file in the ecu. Anyone knows if my ecu is toasted or if it's recoverable somehow? Original file was read via OBD with the same MPPS (2048KB file size) and i've never had problems with any of my versions until i used EcuSafe 2.0

VW Hardware Number: 03L906022BQ
VW Software Number: 9978
ECU : EDC17CP14
Car: Audi A3 2.0 TDI CBBB
MPPS v16.0.1.8 Amt Flash 16.13 clone

Hello, now I have the same problem with a 2,0tdi Passat. Is this tuning protection for the 17CPxx?

I have now tried several times to overwrite the ECU with original files,
but the ventilation is still being serviced to discharge the battery.

does anyone have experience with such protected control units?

can the ECU still be repaired?

Using VCP with EDC17 subscription and boot mode or ktag...