koanga
  •  koanga
  • 76.6% (Friendly)
  • Member Topic Starter
2020-12-02T11:45:28Z
Getting the error P160A checksum error after cloning the DME. I tied with all the checksum options enable and disable also, same error.

I notice that after I`ll write the d-flash (with or without checksum corrections) and readback the data out after and compare those files, there are several blocks that don`t match. So HexProg is not writing all the data. This is done via factory mode.

Reading on some forums that P0606 needs to be deleted in order to fix/start the car, also that only the Magic Pro 2 tool can clone this DME ....
Sponsor

Start ECU Repairing, ECU Cloning, and Chip Tuning today, all from an incredible price of just USD 385.00.

No annual fees, no extra charges: You pay only when you have a job.

Visit Hexprog II page

abc123
  •  abc123
  • 100% (Exalted)
  • Advanced Member
2020-12-02T20:40:25Z
You say you cloned this DDE. Did you check if the original DDE has the same code? Also what car / ECM is it ???
koanga
  •  koanga
  • 76.6% (Friendly)
  • Member Topic Starter
2020-12-03T00:22:57Z
Originally Posted by: abc123 

You say you cloned this DDE. Did you check if the original DDE has the same code? Also what car / ECM is it ???


The original DME doesn`t show P160A. It`s acting up and the only code that the original one has is P06060. The car is Audi 2010 2.0, ecm is MED17.1.

Every time after I`m cloning a DME I do a readout after and compare the D-flash that had been written in with the file that I`m sending, on this particular DME I notice that the D-flash has some address changed. I`ve tried several times to write the D-flash and everytime when I`m reading back, the file is not 100% matching.
abc123
  •  abc123
  • 100% (Exalted)
  • Advanced Member
2020-12-03T06:22:54Z
Audi cannot be cloned like that. The have OTP sector that cannot be written over and it is used for encrypting the immo data. You have to read original, decrypt it and transfer immo (and other) data to the replacement DME
koanga
  •  koanga
  • 76.6% (Friendly)
  • Member Topic Starter
2020-12-03T11:03:26Z
That explains why some blocks remains the same when writing the D-flash, do you know how can I decrypt the data?
abc123
  •  abc123
  • 100% (Exalted)
  • Advanced Member
2020-12-03T15:35:33Z
Originally Posted by: koanga 

That explains why some blocks remains the same when writing the D-flash, do you know how can I decrypt the data?



It is done by other tools. We cannot post the names here. You still should be able to use HexProg to read / write.

sixcode
2020-12-03T20:09:12Z
Post all files so ori and donor, bdm files
Autohex_II_BMW
2020-12-05T10:59:38Z
In VAG models IMMO data is stored in OTP portion which will not be transferred even if you read and write. So this car models either you need to do immo off or need to sync immo once you transfer data.
sixcode
2020-12-11T10:48:52Z
i will sync immo if needed, pm me