I attached the file I pulled from it with vagtacho, I dont know if it is pulled correctly. Car runs, immo and vin are correct and keys are matched just fine, but I have a steady ON immobilizer light. When I reset the cluster it jumps back to the mileage it was when I first pulled the skc (pin 2116). When I log into instruments with the code in vcds and then go put the same pin in adaptation block 50 (this is not a cluster swap, its the original cluster, and the ecu is NOT immo defeated), it just says "Wait" rather than grabbing the vin/immo id again and adapting.

Also, vagtacho tells me the pin is 0324, but that pin fails lol, 2116 is what has worked for both ecu and cluster.

I dont know if someone can provide a zeroed out eeprom or what, maybe its just a bad checksum? Bad mileage change? IDK, but this is really frustrating me, I dont even know if I pulled the bin right...

Vin and immo if it matters: 3VWFE31C64M405673     VWZ5Z0C7161043

Who says its a clone? Anyways, how SHOULD I read it via odb2 port? I can't get the eeprom flasher to communicate

eh, vagtacho sucks on any MM cluster. genuine or not.

i use carprog for audi/beetle mm cluster. 100% success.

attached.

I noticed thats a format match to the last 2048 bytes of my eep dump with tacho, ill see how it works out tomorrow if I cant get a proper 2048 only Ill add the garbage data to the top 2048 and try flashing that: