[Oski]

Hi. I have an A6 cluster, and it can't be done with Odis online as apparently eeprom is damaged - someone tampered with it with VVDI. I also have a good eeprom from a cluster adapted to car with geko, and just thought if I put the good one in to the damaged cluster, would Odis let me remove CP? Has anyone tried that? I know about fisrt 48 bytes - won't copy them over.

[Supertramp78]

Hi. I have an A6 cluster, and it can't be done with Odis online as apparently eeprom is damaged - someone tampered with it with VVDI. I also have a good eeprom from a cluster adapted to car with geko, and just thought if I put the good one in to the damaged cluster, would Odis let me remove CP? Has anyone tried that? I know about fisrt 48 bytes - won't copy them over.

Hi. Did you have success with copying the eprom data from the other cluster to your cluster?
what about the first 48 bytes? that should be the odometer reading, right?
Could you send me the dump from the working cluster? I have the same problem with another cluster that I purchased. They set it to virgin and ODIS cand unlock it.
My idea is to read out the eprom data from the same model cluster in my car and clone it to my spare cluster and then try to remove CP with ODIS

[eFighter]

Which partnumber has your cluster?
Maybe I have dump for you

[Oski]

Hi. I have an A6 cluster, and it can't be done with Odis online as apparently eeprom is damaged - someone tampered with it with VVDI. I also have a good eeprom from a cluster adapted to car with geko, and just thought if I put the good one in to the damaged cluster, would Odis let me remove CP? Has anyone tried that? I know about fisrt 48 bytes - won't copy them over.

Hi. Did you have success with copying the eprom data from the other cluster to your cluster?
what about the first 48 bytes? that should be the odometer reading, right?
Could you send me the dump from the working cluster? I have the same problem with another cluster that I purchased. They set it to virgin and ODIS cand unlock it.
My idea is to read out the eprom data from the same model cluster in my car and clone it to my spare cluster and then try to remove CP with ODIS

Hi. I've tried that, but odis rejected cluster with a fault code, can't recall the number, but said something like the serial number could not be revealed. I had to use abritus to pair the cluster. And yes, first 48 bytes contain odometer reading.

[Supertramp78]

Same here. ODIS says that if the serial number is not on the exception list the unit cannot be unlocked.
A buddy of mine will try to restore the eeprom with his tools.
It looks like there is not just the odometer info in the first 48 bytes but also the ID of the cluster (serial)
and since this block is crypted, it cannot simply be copied.
I hope he can solve this issue for me.

---

Which partnumber has your cluster?
Maybe I have dump for you

Hi there,
its 4F0920934a
I have another cluster with the same number. I took it out of my car, read the eeprom with an external programmer and copied it to the spare cluster.
That didnt work. The spare cluster now shows DEF and 999999
When I keep the first 48 bytes of the old eeprom data, the DEF dissapears and odometer shows 255.
So its a mixed dataset of original first 48 bytes and the rest from my working cluster.

However I noticed that the eproms are not the same type.
The one on my working cluster is a 25320AN
The one on my spare 95320W