PDA

View Full Version : CAR DON'T START AFTER WRITE KESS 5.017 EDC17CP14



0soinsa
16th December, 2017, 02:12 PM
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!!!
493166

dtip
16th December, 2017, 02:22 PM
you write it over obd? and if yes , why?

0soinsa
16th December, 2017, 02:26 PM
i always write EDC17CP14 in OBD and never problem

dtip
16th December, 2017, 02:29 PM
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
16th December, 2017, 02:38 PM
I was wrong, but I still have to solve the problem

kire106ka
17th December, 2017, 12:50 AM
Here is test file
let me know result

0soinsa
17th December, 2017, 01:35 AM
please resent me password, i clear inbox

gad3n
17th December, 2017, 11:58 AM
TPROT_V07.00.00/1796 ... 100% protected

smirnoff_rules
17th December, 2017, 12:04 PM
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
17th December, 2017, 12:14 PM
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
magicmotorsportI work on the principle its safer to do via boot [emoji16] may take a bit longer but not an issue when charging a reasonable rate

smirnoff_rules
17th December, 2017, 12:16 PM
should be able to send read to alientech or mms and they can tell you straight away if its tp file

0soinsa
17th December, 2017, 01:49 PM
anyone could repair my EEPROM and make chechksum?

icezero2010
17th December, 2017, 04:02 PM
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
17th December, 2017, 05:52 PM
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
17th December, 2017, 09:20 PM
with his eeprom he does not go into the diagnosis and does not ID in OBD

0soinsa
17th December, 2017, 09:20 PM
already tried, only solution and repair eeprom

icezero2010
17th December, 2017, 11:41 PM
already tried, only solution and repair eeprom

my solution work ! test many times

voltechcar
17th December, 2017, 11:46 PM
writing ori be obd or use flasher to flashing this ecu frf orginal file and car start. When start use k-tag to read in boot mode or Kess vread and writng by obd.

0soinsa
18th December, 2017, 11:40 AM
I repeat in OBD not make ID with KESS and non function DIAGNOTIC!!!!! OBD NOT WORK!!!! EEPROM IS DAMAGED!!! SOLUTION IS REPAIR EEPROM!!!

bobolin4o
18th December, 2017, 12:31 PM
I repeat in OBD not make ID with KESS and non function DIAGNOTIC!!!!! OBD NOT WORK!!!! EEPROM IS DAMAGED!!! SOLUTION IS REPAIR EEPROM!!!

No need to shooting here, mate.
You are the one, who is in deep shit here...
So keep your nerves and wait until someone fix your eeprom!
BR!

0soinsa
18th December, 2017, 12:48 PM
You are right! I had written from the beginning of the problem is in eeprom, but all insist on writing obd and write obd ...

lsdlsd88
18th December, 2017, 12:51 PM
why do you think you can't flash FRF with appropriate tool if eeprom is damaged?

0soinsa
18th December, 2017, 03:30 PM
problem solved! one user repair eeprom and flash and car start! thank you all at partecipation!

ikara
21st September, 2018, 08:40 PM
have same problem,who can help me,

icezero2010
25th September, 2018, 05:37 PM
have same problem,who can help me,

the solution is in this topic

Use ktag make boot backup

Unlook Seriel programming write file again obd

than the ecu fix the eeprom byself its write the eeprom complete new in second eeprom

ikara
30th September, 2018, 09:08 AM
the solution is in this topic

Use ktag make boot backup

Unlook Seriel programming write file again obd

than the ecu fix the eeprom byself its write the eeprom complete new in second eeprom

thx.,but already solved, a friend make some file wich i write in boot mode and get diag alive again,than reflash with Odis

gfck1
14th June, 2019, 11:57 PM
Hi Guys!
I need your help - i tried to remap my girlfriends Audi A5 2.0tdi (143hp) (2009)....
I'm owning PCM Flash + EDC17.x module and a Kess eu version.

I wanted to read/write the car via obd - took pcm flash -> ecu id -> grabbed the correct virtual read file -> and tried before any remaps flash the stock file via obd...

Unfortunately the write process stopped during (write block1 - that was erased before) so i fear that was tprot that caused that...

Then i took out the ecu and tried it via kess bootloader - ecu id not possible, write process not possible, only a backup read for eeprom and micro was possible (saved together in one file)

What can i do? Is the ecu bricked?

Thx & BR
Chris

Happy786786
15th June, 2019, 12:50 AM
Hi Guys!
I need your help - i tried to remap my girlfriends Audi A5 2.0tdi (143hp) (2009)....
I'm owning PCM Flash + EDC17.x module and a Kess eu version.

I wanted to read/write the car via obd - took pcm flash -> ecu id -> grabbed the correct virtual read file -> and tried before any remaps flash the stock file via obd...

Unfortunately the write process stopped during (write block1 - that was erased before) so i fear that was tprot that caused that...

Then i took out the ecu and tried it via kess bootloader - ecu id not possible, write process not possible, only a backup read for eeprom and micro was possible (saved together in one file)

What can i do? Is the ecu bricked?

Thx & BR
Chris

X17 frf File obd should be fine


Sent from my iPhone using Tapatalk

zxc11
25th July, 2019, 08:46 PM
Hello gfck1,
You can write in PCM suport forum . For module 65 "VAG MED17/EDC17 CAN TP2.0/K-Line":
http://pcmflash.ru/forum/viewtopic.php?f=16&t=1098
for module 48, 50 - VAG MED17/EDC17 UDS:
http://pcmflash.ru/forum/viewtopic.php?f=16&t=212
Try write in english, if no answer- use google translator.
I think You will get help. You can recower that car with pcm flash.


Best regards,
Jordan

Noergaard4822
1st August, 2019, 10:12 PM
Here is test file
let me know result
Thx for the file :) i got to use it

teerak2uk
1st August, 2019, 11:41 PM
Hello gfck1,
You can write in PCM suport forum . For module 65 "VAG MED17/EDC17 CAN TP2.0/K-Line":
http://pcmflash.ru/forum/viewtopic.php?f=16&t=1098
for module 48, 50 - VAG MED17/EDC17 UDS:
http://pcmflash.ru/forum/viewtopic.php?f=16&t=212
Try write in english, if no answer- use google translator.
I think You will get help. You can recower that car with pcm flash.


Best regards,
JordanYou can write in English they understand

Fabiomg89
10th October, 2019, 11:01 PM
problem solved! one user repair eeprom and flash and car start! thank you all at partecipation!
same problem. could you help me? eprom and flash attached
thanks

tothzsolt
11th October, 2019, 08:31 AM
Hello I corrected you my org flash CHK they were not good because you could not start the car, write back fixed ori flash so let's know what's going on

Fabiomg89
11th October, 2019, 06:51 PM
sorry but its not a golf. it is a 2010 audi a6 2.7 tdi engine code CANC 4F7910401L

quiquen
17th October, 2019, 10:12 AM
hello from Spain. its possible help me i have the same problem with EDC17CP04 wont start. greethings Sito

tothzsolt
17th October, 2019, 11:42 AM
this is not from golf flsh this is the original you posted on the forum jasam wrong wrote golf again I say not golf jasam just chk repair, writen to car and start ok

deadmaroz
5th May, 2021, 03:30 PM
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

Can anyone fix the file or tell me where the maps and chk / RSA addresses are (from - to)?

In archive ori.bin is tuned from ecu, readed with kess, 1326_b18bbf42e5.bin ir orginal BDM file!

I read with kess ori.bin, edit and write back, after flesh ecu bricked. I recover ecu with kess an writ 1326_b18bbf42e5.bin, car alive but I need write back tuned file! My Ktag, Kess, MPPS dot read this ecu in boot mode ;-(

THX!

dkmutlu
11th September, 2021, 01:53 PM
HELLO I HAVE THE SAME PROBLEM CAN YOU HELP ME?

dkmutlu
11th September, 2021, 01:59 PM
MERHABA BENDE AYNI SORUN VAR YARDIMCI OLABİLİR MİSİNİZ?