Golf 6 24c32 Highle B/W cluster upgrade to Highline Color 24c64

**DjDvr** · 3rd June, 2020, 11:46 AM

Hello,

I am trying to do a swap from a black and white highline 24c32 cluster 5k0920870g to a highline color 5k0920882 cluster.

I read IMMO with original Carprog form old cluster, all is fine there I can see CS/MAC/Status keys.

I enter boot mode on the color cluster with FFF in color cluster on table. I can read IMMO , I write back original eeprom , read IMMO again still ok.

The problem is now when I try to write the OLD immo to the color cluster. It says it's written fine but the key ID's are wrong with Carprog.

I tried again using FVDI , put dash in boot mode , enter in read state and I can read the ID's, I write the new keys , exit boot mode via obd . I tried to read keys again with Carprog and they seem ok but when I put the dash in the car it still says key not found.

Any ideea ? Am I missing something ? I did other swaps 24c32 to 24c64 no problem on the table but this is the first color I do. Is there something special with these color clusters ?

Any ideea is appreciated.

Thank you in advance.

**H2Deetoo** · 3rd June, 2020, 12:59 PM

Nothing special. Please post the original immo file here.
Also read back the immo from the colour cluster which you wrote and post them as well.

**DjDvr** · 3rd June, 2020, 01:10 PM

Originally Posted by H2Deetoo

Nothing special. Please post the original immo file here.
Also read back the immo from the colour cluster which you wrote and post them as well.

Attached all 3 files.
All 3 read via obd on the table.

**levisdj** · 3rd June, 2020, 02:10 PM

that is not bin file... it's TXT

**DjDvr** · 3rd June, 2020, 02:46 PM

Originally Posted by levisdj

that is not bin file... it's TXT

it's .bin renambed to .txt so i can upload it

just rename to .bin

**immoneard** · 3rd June, 2020, 03:23 PM

Just write compete Immo block from original . Do not transfer manually. I suggest you use FVDI. Adopted file is not transfer 100%
Also when you enter service mode by modifying eeprom, you need to write back original eeprom before you do anything.

**H2Deetoo** · 5th June, 2020, 01:38 PM

I assume the AdaptedImmo file is the one read back after the Original immo file has been written?

The reason the transponders aren't recognized is because the CS is not the same.
Did you manually copy each value in some editor? That often won't work with those buggy tools (editors).

You need to write the Original immo file as it is, then it should be fine.
And if it still fails with your Carprog then do the whole procedure again with FVDI (read from orig, write to target).

Also there is a checksum error in both the OriginalColor and Adapted immo file, and key count is set to FF.
So not sure what you have done but there are several issues. Funny ...

**immoneard** · 5th June, 2020, 04:15 PM

Originally Posted by H2Deetoo

I assume the AdaptedImmo file is the one read back after the Original immo file has been written?

The reason the transponders aren't recognized is because the CS is not the same.
Did you manually copy each value in some editor? That often won't work with those buggy tools (editors).

You need to write the Original immo file as it is, then it should be fine.
And if it still fails with your Carprog then do the whole procedure again with FVDI (read from orig, write to target).

Also there is a checksum error in both the OriginalColor and Adapted immo file, and key count is set to FF.
So not sure what you have done but there are several issues. Funny ...

I think in Color cluster he never write original eeprom back after he did service mode.