UPDATE.

Well the clusters are swapped, and I've tried to do the adaptation with VDCS but run into a problem. I can log into the ECU with the old cluster PIN (and the old cluster).  And I can log into the replacement one with its PIN so the PINs check out ok. But I'm getting to the end of the adaption when you enter the old PIN to adapt the Replacement cluster, it comes back with 'sysytem not ok' message. Also having trouble changing the soft coding, but I'm not that bothered by that.
Quetion is, can the eeprom be cloned to the new cluster from the above dumps? or change the eeprom to enable the IMMO code to be changed?

Regards

Alan

I am on the VDCS forums but they seem at a loss. All values seem to be correct for an adaptation to happen.
I'm currently slogging through the webs looking for a solution... not fun

Hi stuydub,  Lock timers show 0.0 in all fields. Cluster reads as IMMO3 on ID for VCDS and is an identical part number as the old, right down to the A. Same year of manufacturing.
I really want the IMMO on but the car is sitting and I would like to move it!
Old PIN extracted from cluster and logs into old cluster and ECU fine. New PIN logs into new cluster fine, but just won't adapt...
Also, may be of note, but the soft coding on the old cluster was 00444 (no options) and the new cluster was 05444 (4WD extended tank)
New cluster wont take the old soft code 00444.. It did take my mistake 04444.. and then took 05444 but not 00444. So it is codable?
I am getting an "unauthorised key intermitant" code, but I was expecting that, as the key would now not be chipped to the cluster...
I will look at ch21 and let you know.

Alan

Can I ask what tool you used to pull the bin from the cluster?

I am trying to do this same thing with my 2002 TT 180 AWP, but I am not able to get a full EEPROM read from either cluster.  I am trying to use VAG Commander 2.5 and am only getting partials from both clusters. 

Does that mean that both clusters have issues?

Did you ever get this to work?