[Len_Beach]

I want to mod a cluster with M3 style illumination, needles etc however I don't want to use my stock cluster in case there are any issues.

My car is on 48k and I've found a cluster on eBay which is on 42k. From what I've read; plugging this in will update the mileasge to the car; as the car is higher, the cluster will work but won't communicate with the IDrive. Is this correct?

From what I have read; the VIN needs to be updated to match the car to work correctly. Having read various forums; some people say you just write with WinKFP/Tool32 other say you have to use an R270 programmer to reset the VIN to virgin (replace the VIN with FF) then write with NCSExpert as you can't overwrite a non-virgin VIN?

Which method is correct?

[Sensible_]

Originally Posted by Len_Beach

I want to mod a cluster with M3 style illumination, needles etc however I don't want to use my stock cluster in case there are any issues.

My car is on 48k and I've found a cluster on eBay which is on 42k. From what I've read; plugging this in will update the mileasge to the car; as the car is higher, the cluster will work but won't communicate with the IDrive. Is this correct?

From what I have read; the VIN needs to be updated to match the car to work correctly. Having read various forums; some people say you just write with WinKFP/Tool32 other say you have to use an R270 programmer to reset the VIN to virgin (replace the VIN with FF) then write with NCSExpert as you can't overwrite a non-virgin VIN?

Which method is correct?

If you replace it as it is CAS and KOMBI vin / mileage will be mismatched.

Obviously this is protected, you cannot just change vin / mileage without getting a tamper dot.

There are several ways round this, however you should be able to use a simple on board chip programmer to read EEPROM, change VIN to all FF bytes in hex editor, write EEPROM back then program vin with winkfp or I think tool32. Better to flash new firmware to the KOMBI to match the rest of the cars I-level and write new vin in this way.

[Len_Beach]

Originally Posted by Sensible_

If you replace it as it is CAS and KOMBI vin / mileage will be mismatched.

Obviously this is protected, you cannot just change vin / mileage without getting a tamper dot.

There are several ways round this, however you should be able to use a simple on board chip programmer to read EEPROM, change VIN to all FF bytes in hex editor, write EEPROM back then program vin with winkfp or I think tool32. Better to flash new firmware to the KOMBI to match the rest of the cars I-level and write new vin in this way.

So I can just write a newer software version to the Kombi WinKFP and in doing so update the VIN?

This will then match the mileage to the car?

[Sensible_]

No you have to do mileage separately of course. But this is no problem. I think just correct mileage in EEPROM.

As long as you patch EEPROM vin bytes with FF bytes then you should be able to write any vin you want to it via winkfp or tool32.

[orca4wd]

Originally Posted by Sensible_

No you have to do mileage separately of course. But this is no problem. I think just correct mileage in EEPROM.

As long as you patch EEPROM vin bytes with FF bytes then you should be able to write any vin you want to it via winkfp or tool32.

************************
Hello, Anyone have instruction on how-to patch EEPROM VIN to FF bytes. Assumed the R270+ programmer can write to the chip. Thank you so much in advance.