CAR DON'T START AFTER WRITE KESS 5.017 EDC17CP14

[0soinsa]

Yesterday i write GOLF 6 2.0 TDI 170HP 2011 with ecu EDC17CP14
0281015988 - 1037507614 - 03L906022LC
Writing with Kess 5.017 Red Board blocked at 70% at car dont' start
Function Recovery with KESS also blocked at 70%
I post read file with K-TAG 7.020 after blocked
SOMEONE COULD HELP ME TO UNDERSTAND THE PROBLEM, THANK IN ADVANCE!!!
KTAG READ.rar

[dtip]

you write it over obd? and if yes , why?

[0soinsa]

i always write EDC17CP14 in OBD and never problem

[dtip]

i always write EDC17CP14 in OBD and never problem

i don't know what edc17 you wrote before but this year and this SW ecu must have tprot for sure and can't be wrote over obd....at least not with kess clone , not sure about ori kess

[0soinsa]

I was wrong, but I still have to solve the problem

[kire106ka]

Here is test file
let me know result

[0soinsa]

please resent me password, i clear inbox

[gad3n]

TPROT_V07.00.00/1796 ... 100% protected

[smirnoff_rules]

l have always worked off this list ?
-03L906022NH 3397 1037399332 tc1796 NO TP
-03L906022NH 4388 1037500120 tc1796 NO TP
-03L906022NH 5509 1037506174 tc1796 NO TP ,
no tp 1037563984 no tp .
1037563980 no tp

and normally write fails at 99%

if cars had an update might be a problem ?

this info from magpro

================================================== ===============
I problem: ECU VAG EDC17CP04/14 blocked writing MOD by OBD (so called EEPROM crash)
caused by: ECU remain in programming mode.
1. Read IROM / XROM and EEPROM in bootloader mode.
2. Fix IROM/XROM using bootloader readout and OBD ORI readout (you will probably need to paste part of map zone and chk/RSA zone)
3. Write fixed IROM/XROM by bootloader (do not touch EEPROM!)
4. connect ECU to the car and write repaired IROM/XROM (same used for bootloader) by OBD.
It will automaticaly fix eeprom problem.
Resolved

================================================== =====================
II problem: ECU VAG EDC17 blocked writing IROM /XROM by bootloader. Cannot read anymore IROM/EEPROM
Caused by: damaged sector 0 by interrupted writing
1. find someone with MAGpro2 X17 or T-BOOT tool
2. Write IROM / XROM by X17/T-BOOT using OPTIONS= ALL
resolved

Regards
MAGICMOTORSPORT Team
magicmotorsport

[teerak2uk]

l have always worked off this list ?
-03L906022NH 3397 1037399332 tc1796 NO TP
-03L906022NH 4388 1037500120 tc1796 NO TP
-03L906022NH 5509 1037506174 tc1796 NO TP ,
no tp 1037563984 no tp .
1037563980 no tp

and normally write fails at 99%

if cars had an update might be a problem ?

this info from magpro

================================================== ===============
I problem: ECU VAG EDC17CP04/14 blocked writing MOD by OBD (so called EEPROM crash)
caused by: ECU remain in programming mode.
1. Read IROM / XROM and EEPROM in bootloader mode.
2. Fix IROM/XROM using bootloader readout and OBD ORI readout (you will probably need to paste part of map zone and chk/RSA zone)
3. Write fixed IROM/XROM by bootloader (do not touch EEPROM!)
4. connect ECU to the car and write repaired IROM/XROM (same used for bootloader) by OBD.
It will automaticaly fix eeprom problem.
Resolved

================================================== =====================
II problem: ECU VAG EDC17 blocked writing IROM /XROM by bootloader. Cannot read anymore IROM/EEPROM
Caused by: damaged sector 0 by interrupted writing
1. find someone with MAGpro2 X17 or T-BOOT tool
2. Write IROM / XROM by X17/T-BOOT using OPTIONS= ALL
resolved

Regards
MAGICMOTORSPORT Team
magicmotorsport

I work on the principle its safer to do via boot may take a bit longer but not an issue when charging a reasonable rate

[smirnoff_rules]

should be able to send read to alientech or mms and they can tell you straight away if its tp file

[0soinsa]

anyone could repair my EEPROM and make chechksum?

[icezero2010]

anyone could repair my EEPROM and make chechksum?

use ktag make full backup unlock obd write and write again over obd after that the eeprom is ok

[lsdlsd88]

I found this ori read with ktag (flash only)
it has some difference only in checksum area so I think your problem is in eeprom. follow those instructions from MMS

[0soinsa]

with his eeprom he does not go into the diagnosis and does not ID in OBD