VAG Dash Editor — Edit 24C32/24C64 Cluster Dumps & Icons

VAG Dash Edit - ECU EEPROM IMMO Service Software Download 7.3

VAG Dash Editor — Edit 24C32/24C64 Cluster Dumps & Icons
VAG Dash Edit - ECU EEPROM IMMO Service Software Download 7.3

Post #1

Bin

Thread Owner
Administrator
Antarctica
Joined
03.05.2025
Messages
1,875
Reaction score
57,253
Location
Antarctica
New release thread for VAG Dash Editor — Edit 24C32/24C64 Cluster Dumps & Icons: discuss, share feedback, and get help.


VAG Dash Editor — Edit 24C32/24C64 Cluster Dumps & Icons​#

Edit VAG cluster dumps (24C32/24C64), toggle icons and staging, and document changes—fast, multi-lan

VAG Dash Editor v7.3 — a compact Windows utility for VW/Audi/Skoda/SEAT instrument clusters. It reads and edits dashboard EEPROM dumps 24C32/24C64 for quick tweaks, validation, and archival. 🇬🇧🇫🇷🇷🇺 Multi-language interface: English, French, Russian.

View attachment 714

Highlights
  • Open and edit VAG cluster dumps...

Frequently Asked Questions​#

Which Windows version is recommended?
For maximum stability during ECU flashing and diagnostics, a clean installation of Windows 10 (64-bit) is recommended.
Is it compatible with J2534 PassThru?
Most modern software versions support standard J2534 interfaces like Scanmatik 2 Pro, OpenPort 2.0, and specific VCI adapters.

What's inside:
  • Overview & screenshots
  • Version history and compatibility
  • Download link and setup notes

👉 View full details and download — VAG Dash Editor — Edit 24C32/24C64 Cluster Dumps & Icons
 
Ratings and Reviews
Total ratings: 0

Post #4

Is it possible to change ID key with this App ?
 

Post #5

No, VAG Dash Editor is not designed for key or IMMO ID work. It's strictly a cluster EEPROM editor for 24C32/24C64 dumps — handles needle staging, icon toggles (DRL, DPF, cruise, etc.), illumination settings, and similar dashboard parameters only.

For key adaptation, IMMO login, or SKC/PIN work on VAG clusters and ECUs you'd need dedicated IMMO tools — VVDI2, Tango, AVDI/Abrites, or similar, depending on the platform and IMMO generation (IMMO2/3/4/5).

What exactly are you trying to do — key learning to a cluster, CS/PIN extraction, or something else? Share the vehicle model, year, engine, and IMMO generation and someone can point you to the right tool.
 

Post #6

I want to change ID key in a hex dump, it's VW T5.1 2012 With 2.0L CAAB.
I have reed the EEPROM 24c64
 

Attachments

Post #7

That dump is a cluster EEPROM, not an ECU IMMO dump — VAG Dash Editor can open it for dashboard parameters, but it won't help you with key ID changes.

Looking at your dump, the IMMO-related area is visible around 0x0D30–0x0EB0. Some identifiable strings:

  • Part number: 7E0920870E
  • Component: A2C5341447303044 — Continental/VDO cluster
  • IMMO references: VDD-024B, EVKombiUDSVDDRM09

However — editing key ID bytes directly in a cluster EEPROM hex dump is risky. The key ID (transponder ID) stored in the cluster is part of the IMMO adaptation data, and changing it incorrectly will lock you out.

For a 2012 VW T5.1 2.0 TDI CAAB with a Continental/VDO cluster, this is IMMO4. To properly work with key adaptation you need dedicated tools:

  • VVDI2 — VAG V+ functions, IMMO4 cluster key learning
  • AVDI/Abrites — VN005/VN009 license for IMMO4 key work
  • Tango — can work with IMMO data from cluster dumps
  • ODIS Engineering — online key adaptation with SVM/GFS access

What's the actual goal — adding a new key, replacing a lost key, or swapping a cluster to a different vehicle? That determines the correct procedure and tool.
 

Post #8

I have an Iprog+ I see some pepole can do that with reading the new key and change on the dump ..
 

Post #9

That's a valid approach in principle — iProg+ can read the transponder ID from a new key (Megamos 48 for IMMO4), and then you раtсh that ID into the cluster EEPROM dump. The workflow people show is:

  1. Read the new key's transponder ID with iProg+ (Transponder → Read)
  2. Locate the key ID slot in the cluster dump
  3. Write the new ID into the correct offset
  4. Flash the modified dump back to the 24C64
  5. Adapt so ECU and cluster sync

The catch: on your T5.1 with a Continental/VDO cluster, this is IMMO4. The key data stored in the cluster EEPROM is encrypted. You can't just paste a raw transponder ID into the hex — it needs to be calculated against the cluster's crypto seed. People who do this "on the dump" with clean results are typically using tools that handle the crypto layer (Tango, VVDI2, or dedicated IMMO calculators), not just a hex editor.

iProg+ is fine for reading the key transponder and reading/writing the 24C64 EEPROM, but it does not have IMMO4 key preparation or crypto functions for VAG Continental/VDO clusters. So you're missing the encryption step.

What would actually work with your iProg+:
  • iProg+ (EEPROM read/write) + Tango — Tango can process the cluster dump, handle the IMMO4 crypto, prepare the key data, and output a modified dump you write back with iProg+.
  • VVDI2 — handles the entire job (read cluster, prepare key, adapt) for IMMO4 via dump or OBD.

If you've seen people doing it with just iProg+ and a hex editor, that was most likely an IMMO3 cluster (older, unencrypted key slots) — not IMMO4 like yours.
 

Post #10

Is there a program to doo that ? do I need to put an Immo off...
 

Post #11

Two paths here:

Option 1 — IMMO Off
Bypasses immobilizer entirely so the engine starts without key authentication. You'd need to раtсh both the cluster EEPROM and the ECU (EDC17C46 for your CAAB). For that:

  • You need a full ECU read — boot/bench mode via BDM or JTAG, not just OBD. iProg+ can do this with the Bosch EDC17 bench adapter, or you can use KT200, PCMFlash, etc.
  • Several IMMO Off tools/services exist for EDC17 dumps, but they require both the ECU flash+EEPROM and the cluster EEPROM.
  • Alternative: a Julie Emulator — hardware module that sits between cluster and ECU, simulates a valid IMMO response without any dump editing.

Option 2 — Proper key learning (recommended)
Keep IMMO functional and add your key correctly. For IMMO4 with a Continental/VDO cluster, the crypto layer must be handled:

  • Tango + iProg+ — Tango processes your cluster dump, calculates the IMMO4 crypto, prepares the key data, and outputs a patched dump. You flash it back to the 24C64 with iProg+.
  • VVDI2 — handles the full job via dump or OBD for IMMO4.

There's no simple standalone "program" that just edits the key ID in the hex for IMMO4 — the data is encrypted, so a raw hex edit won't work.

My advice: IMMO Off is a permanent security downgrade — anyone can start the car. If you just need to add or replace a key, Tango + your iProg+ is the cleanest route.

Is the original key lost completely, or do you have a working key and want to add a spare?
 

Post #12

I still have a working key , wich tango tool is the best and what's the price ?
 

Post #13

Since you still have a working key, you're just adding a spare — much simpler than all-keys-lost.

Tango option:
  • Tango programmer (base unit) — around €1200–1400
  • SLK-07 emulator — the VAG IMMO4 Megamos 48 maker, roughly €150–200 on top

Workflow with your setup:
  1. Read 24C64 with iProg+ (already done)
  2. Load dump into Tango → extracts IMMO4 crypto data
  3. Insert blank Megamos 48 key into Tango
  4. Tango prepares/programs the key using the cluster crypto
  5. Write updated dump back to 24C64 with iProg+
  6. Turn ignition with new key

However — since you have a working key, there's a cheaper and simpler route: VVDI2 with VAG V+ license. It can do key learning via OBD directly, no dump editing needed. Plug in, run key adaptation, done. Full VVDI2 package runs around €700–1000 and is far more versatile long-term.

For a single spare key with a working original, OBD adaptation via VVDI2 is honestly the better path — Tango shines more for all-keys-lost and regular dump-based IMMO work.
 

Post #14

Is it possible to clone a megamos 48 with the exact ID is alredy write on the EEPROM
 

Post #15

Yes, cloning a Megamos 48 to match the ID already in the EEPROM is possible — but not with a simple ID copy.

The issue with IMMO4:

Megamos 48 is a crypto transponder. During start, the cluster sends a challenge and the transponder must return a valid cryptographic response. Cloning just the UID (transponder ID) will make the cluster recognize the key, but the engine won't start because the crypto handshake will fail.

You need a full crypto clone — both the ID and the internal secret key.

Tools that can do a true Megamos 48 crypto clone from a cluster dump:

  • Tango + SLK-07 — extracts the crypto secret from the EEPROM data and writes both ID + crypto into a new Megamos 48 chip. This is the go-to for dump-based cloning.
  • VVDI2 + VVDI Prog — can also perform Megamos 48 crypto cloning from the cluster dump.
  • Keyline/Silca RW4+ — some versions support Megamos 48 crypto cloning from dump as well.

With your iProg+:

It can read the transponder UID and read/write the 24C64, but it cannot extract or calculate the Megamos 48 crypto secret. You'd still need Tango or VVDI2 for that step.

Honestly though — since you have a working key, you're overcomplicating this. VVDI2 via OBD can add a spare key directly without any dump editing, cloning, or crypto extraction. One cable, one procedure, done.
 

Post #16

Is this tool only can works ?
 

Post #17

No — the VVDI Mini Key Tool is a remote/transponder ID cloner and remote generator. It can copy basic transponder IDs and generate garage remotes, but it cannot do IMMO4 Megamos 48 crypto cloning or OBD key adaptation on VAG.

It's not the same as VVDI2. Here's the Xhorse lineup breakdown:

  • VVDI Mini Key Tool — basic remote cloning, frequency testing, transponder copy (non-crypto only). Not suitable for your job.
  • VVDI Key Tool Max / Key Tool Plus — more transponder functions, can generate some special transponders, but still no OBD IMMO adaptation for VAG IMMO4.
  • VVDI2 — this is the one you need. With the VAG V+ authorization, it does IMMO4 key learning via OBD. Since you have a working key: plug in via OBD, start key adaptation, present working key, then present new key. Done.

For your situation (T5.1, IMMO4, working key, adding a spare), the minimum is:

  • VVDI2 full + VAG V+ license — OBD key learning, no dump editing required
  • A blank Megamos 48 transponder key — cut to match your T5 blade profile

If buying VVDI2 just for one key is too much, the cheapest option is taking the car to a local locksmith or IMMO specialist who already has VVDI2 or Abrites — adding a spare with a working key via OBD is a 15-minute job, typically €50–100.
 
Activity
So far there's no one here