VW AMAROK EDC17c54 CLONING

**checho83** · 16th August, 2016, 03:46 PM

hi everyone... i have to clone a edc17c54 ecu from amarok... I bought a used edc17c54 ecu, same bosch and vw number... I read orginal and also back up bought one..
The tool i use is chinese KTAG, but seems to read all OK. Reading options are internal flash memory from TC1797 and eeprom.. I make full backup of both and i program the replacement one with data of the original one, but during reading testing, one thing i was worried about that eeprom reading from one had diferent data structure that the other, althought was the same ECU.
After that, owner test both ecu on the vehicle, and with original, all ok, but used one IMMO FAULT...
With tester was checked and both had the same vin number, so programming was ok!, no faults despite immo... all ok, but bought one, the reprogrammed one, starts and stops..
Any idea? All inmo information is on eeprom only? I dont want to make immo off... If there is any procedure i am missing, tell me. Thanks!!!!
edc17_eeprom.rar

**vasa** · 16th August, 2016, 03:53 PM

maybe you need small learning can you past in Google OTP area you cant clone edc17 you need immo off flash end epromm mate

**checho83** · 17th August, 2016, 12:48 PM

Hi Sr, thanks for answering.. i have read the post.. and as soon i could undersand, people that have problems with that area, there are not able to write in micro normally..but i am able to do that... not writing errors and verification on both, eeprom and flash seems ok... What someone tolds is the posibility to clone and inmo writing pin, VIN and CS on the bought unit eeprom and that should be to OK to car start. I am correct? Thanks

**yugo45** · 17th August, 2016, 06:11 PM

Originally Posted by checho83

Hi Sr, thanks for answering.. i have read the post.. and as soon i could undersand, people that have problems with that area, there are not able to write in micro normally..but i am able to do that... not writing errors and verification on both, eeprom and flash seems ok... What someone tolds is the posibility to clone and inmo writing pin, VIN and CS on the bought unit eeprom and that should be to OK to car start. I am correct? Thanks

No , you are not writing OTP area, After you write original file in New ECU , read ecu again then check in Hex editor and you will see that OTP area is not written in new ECU.
EDC 17 , MED 17 is not possible to clone 1 to 1.
Only immo data can be transfer , but not with tool you have.

**checho83** · 17th August, 2016, 09:58 PM

Thanks for answering... i will check that, but i think i did that to recheck data transfer..., but i could had make a mistake...; Now, my question is, inmo data could not be trasnfered manually to one file to another?. I was thinking in putting back original data and transfer eeprom only from the one with immo working... Thanks!

**banabana** · 18th August, 2016, 08:58 AM

Originally Posted by checho83

hi everyone... i have to clone a edc17c54 ecu from amarok... I bought a used edc17c54 ecu, same bosch and vw number... I read orginal and also back up bought one..
The tool i use is chinese KTAG, but seems to read all OK. Reading options are internal flash memory from TC1797 and eeprom.. I make full backup of both and i program the replacement one with data of the original one, but during reading testing, one thing i was worried about that eeprom reading from one had diferent data structure that the other, althought was the same ECU.
After that, owner test both ecu on the vehicle, and with original, all ok, but used one IMMO FAULT...
With tester was checked and both had the same vin number, so programming was ok!, no faults despite immo... all ok, but bought one, the reprogrammed one, starts and stops..
Any idea? All inmo information is on eeprom only? I dont want to make immo off... If there is any procedure i am missing, tell me. Thanks!!!!
edc17_eeprom.rar

if you post flash ican do off for you from flash

**yugo45** · 18th August, 2016, 03:59 PM

Originally Posted by checho83

Thanks for answering... i will check that, but i think i did that to recheck data transfer..., but i could had make a mistake...; Now, my question is, inmo data could not be trasnfered manually to one file to another?. I was thinking in putting back original data and transfer eeprom only from the one with immo working... Thanks!

No , it is not possible because it is encrypted in eeprom.

**yugo45** · 18th August, 2016, 04:03 PM

Originally Posted by banabana

if you post flash ican do off for you from flash

17c54 should be is UDS protocol ECu and immo off can not be done to UDS protocol ECu, only immo data transfer.

**offsystem** · 18th August, 2016, 08:43 PM

Originally Posted by yugo45

17c54 should be is UDS protocol ECu and immo off can not be done to UDS protocol ECu, only immo data transfer.

What about immo off in flash? Also not working

**yugo45** · 19th August, 2016, 03:24 AM

Originally Posted by offsystem

What about immo off in flash? Also not working

For me that is not solution at all,ending up with immo error in cluster .

**steveleo** · 19th August, 2016, 11:42 AM

Question for the experts:
X old ecu
Y new ecu
copying only immodata from eeprom X to eeprom Y (decrypted with key from X and encrypted with key from Y)
copying VIN from eeprom X to eeprom Y
Then checksum correction
Would this work?

**yugo45** · 19th August, 2016, 06:08 PM

Originally Posted by steveleo

Question for the experts:
X old ecu
Y new ecu
copying only immodata from eeprom X to eeprom Y (decrypted with key from X and encrypted with key from Y)
copying VIN from eeprom X to eeprom Y
Then checksum correction
Would this work?

Yes it will. But the key is decryption.
Not many tools on market can decrypt EDC 17/ MED 17.Plus checksum need to be calculate . All immo data has checksum.
Once you have decypt data , you can do what ever you want.

**checho83** · 25th August, 2016, 04:10 AM

Thanks for all reply...I will now try immo off options... Here is flash from bought ECU... if someone can do the try... i wonder if there is options to make dash inmo message disapear. Thanks!!!