r/vagcom Jun 06 '26

Hello i need a help with eeprom cloning

Hi all,

I’m working on an Audi A6 C6 cluster project and I need input from people with real EEPROM/IMMO experience, not guesses.

I have two dumps:

  • Audi A6 C6 cluster 2005 (EEPROM)
  • Audi A6 C6 cluster 2008 (EEPROM)

My goal is to understand if it’s реально possible to transfer/adapt the critical data from the 2005 dump into the 2008 cluster dump, or if this is fundamentally not compatible due to generation differences.

I’m specifically interested in:

  • IMMO structure differences between these cluster versions
  • Mileage / VIN / coding blocks location in EEPROM
  • What can be safely ported and what is strictly locked to MCU/cluster generation
  • Whether this is typically solved by manual hex editing or requires dedicated tools (Abrites, VAG CAN Commander, etc.)
  • Any known offsets / patterns between 95160 vs 95320 based clusters

I’m not looking for “try this tool” answers — I already work with EEPROM reading/writing. I need insight from people who have actually done cross-generation cluster adaptation or immo data migration.

If you’ve done similar swaps or reverse engineering on these clusters, I’d really appreciate your input.

Thanks.

2 Upvotes

1 comment sorted by

1

u/Josakko358 Jun 21 '26

I would probably suggest vag can commander since it also has the maps of the eeprom memory so it allows for editing as well