Anybody can help?

Maybe somebody knows about level of compatibility between different versions? What is more important: last 4 signs of VAG part number (mine: 933 P), or rvision number (mine: D07)?

Regards

Hi. And how do You think? Which one gives better chance of compatibility? For me it;s not a problem to check out both versions, I'm equipped with good programming device, resoldering station etc. Would You like to share that files?

Ooops, it looks like I'm really poor in that things :-/
I didn't know, that binary read via programmer (directly from eeprom) differs from a version read via diagnostic socket.
My problem is, that after burglar's intervention, car does not responding (immo light starts to blink immediately after ignition turned on) What is characteristic - when keys erased, immo light starts for a continous lighting for abou 1,5 seconds, and after it starts blinking. Here blinks form start.

I tried to read eeprom with Vag Tacho and Vag K+Can Commander - vag tacho reports "access denied", Vag K+Can reads a file which contains a few sequences from beginning to end and doesn't look like typical structure of such dump (no immo number, no VIN, PIN code not readable, tacho not readable etc.) So - I concluded, that there's no possibility to fix my problem through OBD socket and the only way is to load a good dump into eeprom directly.

Or maybe something else is damaged?? I can communicate with cluster (17) and immo (25), but I'm not able to get PIN to program a keys. What now?

After burglary, no any signs You described above were appear. Cluster seemed to work normally, original mileage worked, no any strange signals. Only no possibility to read eeprom with any device I own, immo light blinking at once, a trouble code in immo - "keys improperly programmed". Ignition was broken, as well as immo coil. Key's pilot worked properly - no problems to open and close a car. I've reworked another ignition to work with my original key, replaced damaged coil with new one. And no possibility to start engine for more than second - same as before.

But I've desoldered eeprom (made backup of course), and I tried to upload a dump from A6 of my father (same 2001 year, 2.8 V6). Of course, i read it with no problems from father's cluster with K+Can, and loaded into eeprom with programmer after desoldering.
And after that operation there's a complete set of cluster's behaviours, like described above: BONG signal, "FUSE" message in place of mileage, no lights in cluster panel, FIS totally blind.

Before I'll ask You for any further help (really great thanks for it!), I guess, I should rather go back to previous cluster's state (with original dump file readed in programmer)? I want to prepare it best to make Your help easier and more effective.

Thank You!

I can take a look this evening. My email is in my sig.