[matcas7792]

Greetings to all the members of this fantastic forum, let me introduce myself, my name is Matteo and my car is an old golf 5 2.0 TDI.
I am an OB expert and currently have the following automotive diagnostic tools:
Xprog box various versions, SVCI 2020, FVDI 2015, UPA, VCDS, KESS V2, MPPS V.18 and more.
I recently purchased an odometer with part number:
1K0920873 B and I am carrying out bench tests, not connected to the car.
This being an odometer produced after June 2006, from that and I understood, to access the Immo data you have to do the procedure on the 24c32 eeprom (service mode), i.e. from offset 0x812 to offset 0x9BF, write everything 0xFF.
Then turn on the odometer, read the Immo data, load the original eeprom, and read the Immo data again so you can edit the Immo data....
Ok, this is my problem, why does SVCI 2020 read my immo data bypassing the protection without a valid key?
I can't figure out if eeprom or flash are corrupt.
I attach eeprom, decrypted, flash and unmodified eeprom.
I count on your help, thank you.

[mikajna]

Greetings to all the members of this fantastic forum, let me introduce myself, my name is Matteo and my car is an old golf 5 2.0 TDI.
I am an OB expert and currently have the following automotive diagnostic tools:
Xprog box various versions, SVCI 2020, FVDI 2015, UPA, VCDS, KESS V2, MPPS V.18 and more.
I recently purchased an odometer with part number:
1K0920873 B and I am carrying out bench tests, not connected to the car.
This being an odometer produced after June 2006, from that and I understood, to access the Immo data you have to do the procedure on the 24c32 eeprom (service mode), i.e. from offset 0x812 to offset 0x9BF, write everything 0xFF.
Then turn on the odometer, read the Immo data, load the original eeprom, and read the Immo data again so you can edit the Immo data....
Ok, this is my problem, why does SVCI 2020 read my immo data bypassing the protection without a valid key?
I can't figure out if eeprom or flash are corrupt.
I attach eeprom, decrypted, flash and unmodified eeprom.
I count on your help, thank you.

Because your dash dont have protecton, its like before 2006 year, its not mandatory rule that all golf's made after 06.2006 are protected with security access. That mean if your dash can be read without working key, and you need donor dash which also can be read without working key.
Those dash can be learned on Chanel 050 like dash for Golf 4, there is no neead for transfering immo data, specialy if part number not same, or manufacture (Visteon to VDO or vice versa).

Best regards

[matcas7792]

Greetings to all the members of this fantastic forum, let me introduce myself, my name is Matteo and my car is an old golf 5 2.0 TDI.
I am an OB expert and currently have the following automotive diagnostic tools:
Xprog box various versions, SVCI 2020, FVDI 2015, UPA, VCDS, KESS V2, MPPS V.18 and more.
I recently purchased an odometer with part number:
1K0920873 B and I am carrying out bench tests, not connected to the car.
This being an odometer produced after June 2006, from that and I understood, to access the Immo data you have to do the procedure on the 24c32 eeprom (service mode), i.e. from offset 0x812 to offset 0x9BF, write everything 0xFF.
Then turn on the odometer, read the Immo data, load the original eeprom, and read the Immo data again so you can edit the Immo data....
Ok, this is my problem, why does SVCI 2020 read my immo data bypassing the protection without a valid key?
I can't figure out if eeprom or flash are corrupt.
I attach eeprom, decrypted, flash and unmodified eeprom.
I count on your help, thank you.

Because your dash dont have protecton, its like before 2006 year, its not mandatory rule that all golf's made after 06.2006 are protected with security access. That mean if your dash can be read without working key, and you need donor dash which also can be read without working key.
Those dash can be learned on Chanel 050 like dash for Golf 4, there is no neead for transfering immo data, specialy if part number not same, or manufacture (Visteon to VDO or vice versa).

Best regards

Thank you for answering me, when I purchased this cluster it had protection, now after having changed immo data with FVDI 2020 for my car and adapted it to my car with SVCI 2020 everything is ok.
Then after removed it from my car and rewrote the original eeprom backup with Revelprog is
but now clusters no longer have protection even with eeprom original backup, why???

[cristo_844]

That is normal!
After deliting immo data from offset 0x812 to offset 0x9BF and reapload eeprom file by obd you lose protection...No longer need key to read immo data!

[matcas7792]

That is normal!
After deliting immo data from offset 0x812 to offset 0x9BF and reapload eeprom file by obd you lose protection...No longer need key to read immo data!

Ok, I'm using google translate, maybe translation not ok, I'll try to explain my problem better.
This is just an example to better understand.
I purchase cluster from internet 1K0920873 B.
Step 1 = connect external programmer to read 24c32 eeprom for backup.
step 2 = I connect xprog box to read Micronas CDC 3217 to have original flash backup.
NOW I connect the cluster on the bench and via SVCI 2020 OBD I read the immo data from the original cluster of my car, 1K0920860 L.
I travel with my car for 6 months, with cluster 1K0920873 B, then I decide to replace my old cluster 1K0920860 L.
Now the cluster 1K0920873 B has immo of my car, then I rewrite with an external programmer its original EPROM, from when I purchased the cluster.
Now I connect cluster with SVCI 2020 and reading immo data I have no protection, I hope I explained myself better.
I can't figure out if there are bytes to change in Eeprom or Micronas.
Compared with other Micronas they are identical, apart from the 9 decryption keys at the offset 0x00077F00, and 0X00077F80 which I still haven't understood what they were for..