VAG IMMO Tool — BCM2/ELV/EZS/TCU, PCR2.1 & ECU Decode • EEPROM 95320

Post #22

Mrkyawhtoo

Suspended
Joined
28.01.2026
Messages
55
Reaction score
4
All-in-one VAG IMMO workspace
Decode / view / edit immobilizer datasets across BCM2 / BCM2 Locked / ELV / EZS / CCM / TCU plus PCR2.1 and ECU Decode pages (EEPROM / D-Flash / P-Flash / Flash) — with clear UI fields like VIN, CS, MAC, Power Class, key slots, status and export/save actions.

Built for fast, structured IMMO data work: upload the required dump (EEPROM / Flash / D-Flash / P-Flash), press Decode, and get a clean “service view” of the immobilizer dataset.
You’ll see the same core pairing fields across modules (VIN, IMMO ID, CS, MAC, Power Class, key slots, status/CP fields where applicable), plus one-click export buttons like Save Data, Save EEPROM and Save Flash depending on the module.



What you can do with it (in practice)
  • Decode immobilizer datasets from different VAG control units and see the important fields in a clean editor (no hex scrolling).
  • Compare / verify data — quickly check whether dumps match each other (typical when diagnosing “component protection / mismatch” style problems).
  • Prepare data for module replacement — when you have an original unit + donor unit and need the donor to match the vehicle’s stored identity/alignment data.
  • Recover from corrupted dumps — the UI is designed around “decode → identify → edit → export” flows and has dedicated repair-style actions in some modules.
  • Work module-by-module — ELV, BCM2, EZS, CCM, TCU are treated differently because the stored IMMO structure differs per unit.
  • Export results — save decoded data views and save processed EEPROM/Flash outputs (buttons are built into every Execute page).

Why there are so many modules (what each one targets)
Think of each module as a “profile” for a specific unit/family and its memory layout:
  • BCM2 — main body/immobilizer storage workflow for BCM2 (EEPROM/P-Flash pairing in the Execute). Shows the richest dataset view (CS/MAC, CP-related fields, key slots, etc.).
  • BCM2 Locked — BCM2 locked variant flow (D-Flash + P-Flash + optional key file). Same idea as BCM2, different source files and structure.
  • AUDI ELV — ELV (steering column lock) focused workflow. Flash input → decoded IMMO fields + console for status/logs.
  • EZS — EZS (central locking / immobilizer-related dataset) workflow. EEPROM input → CS/MAC/PIN/status + key slots.
  • EZS Crafter — EZS flow tailored for VW Crafter modules (same UI style, but Crafter-specific dataset layout).
  • SYNC AKL — “All Keys Lost” synchronization suite shown in the module overview (reset/synchronization style actions).
  • CCM — comfort module dataset view (VIN/IMMO ID/CS/MAC + brand/status dropdowns + key slots).
  • TCU — DSG/TCU workflow (Flash + EEPROM inputs) with its own decoded fields and drop-down selectors for IMMO areas.
  • PCR2.1 — EEPROM-only operations for PCR2.1 family (the UI explicitly highlights EEPROM-only support).
  • ECU DECODE — engine ECU focused decode/edit for IMMO4/IMMO5/IMMO6 generations (as stated in the module description).
  • ECU Cloning — “Original vs Donor” full automatic built for moving the full dataset between ECUs and keeping alignment consistent.

Access
https://www.immo-master.net/vag/login.php
Code:
👤 Login: mhh
🔑 Password: full

Quick module map
ModuleCore purpose (as shown)Available actionsRequired files
BCM2Decrypt IMMO data from BCM2 95320 EEPROM or D-Flash; identify/repair data issues; ELV-related option shownDecode/Edit IMMO data • Repair EEPROM Errors • Disable ELVEEPROM 95320 or D-Flash • P-Flash
BCM2 LockedDecrypt IMMO data from BCM2 Locked D-Flash; data error repair; ELV-related option shownDecode/Edit IMMO data • Repair EEPROM Errors • Disable ELVD-Flash dump • P-Flash • Key EEPROM file (full decode only)
AUDI ELVElectronic Steering Column Lock: clone/decrypt IMMO-related data from ELV moduleDecrypt IMMO data • Edit IMMO dataDFlash file
EZSElectronic Central Locking: clone/decrypt/edit IMMO data (Audi EZS), MCU-type targetedDecrypt IMMO data • Edit IMMO dataEEPROM or D-Flash
EZS CrafterVW Crafter EZS: full IMMO decryption + complete cloning support (as stated in UI)Decrypt IMMO data • Edit IMMO dataEEPROM or D-Flash
SYNC AKLAll Keys Lost synchronization suite: reset + synchronization workflowsImmo Reset • ECU Synchronization • Transponder Generation • Adaptation ResetEEPROM file • Abrites • Advanced Diagnostics
CCMComfort Control Module: cloning + full decryption of immobilizer data in VAG CCM unitsDecrypt IMMO data • Edit IMMO dataEEPROM file
TCUTransmission Control Unit: cloning-style data handling on DQ200/DQ250/DQ400 MQB familiesDecrypt IMMO data • Edit IMMO data • IMMO OFF (button shown)EEPROM file • Flash file
PCR2.1PCR 2.1 — EEPROM Only Operations: decrypt all immobilizer data using EEPROM only (no flash / no MCU ID required)Decrypt all immo data • Edit all immo dataEEPROM 95640 (accepted size: 8 KB or 136 KB)
ECU DECODEEngine Control Unit IMMO workspace: calculates/edits IMMO data for IMMO4 / IMMO5 / IMMO6 generationsDecrypt all immo data • Edit all immo dataEeprom File • Flash File OR MCU ID
ECU CloningFull Automatic ECU cloning for engine ECUs incl. immobilizer synchronization (as stated in UI)Full ECU Clone • Immo Data TransferOriginal ECU EEPROM/Flash • Donor ECU EEPROM/Flash • MCU ID (optional)

“Execute” pages — common layout
After clicking Execute, modules open a dedicated “Programming Interface” with a familiar structure:
  • Upload Files — only the file types needed for that module (EEPROM / D-Flash / P-Flash / Flash)
  • File Operations — buttons like Decode, Save Data, Save EEPROM, Save Flash, etc.
  • Identification (where available) — detected HW/SW/Version/ECU type/IMMO type after decoding
  • Config (where available) — Master/Slave ECU + TCU/ELV toggles (checkboxes)
  • Immo Data — decoded fields + Enable Edition toggle for editing mode
  • Console (some modules) — log output + Clear button

Modules (expanded: Dashboard details + Execute interface)

Dashboard (“Module Details”) highlights
  • Decrypts IMMO data stored in BCM2 95320 EEPROM or D-Flash; aimed at identifying/repairing data issues; ELV option is shown.
  • Compatibility shown: Audi A4 / Audi A5 / Audi Q5
  • Required files shown: EEPROM 95320 or D-Flash + P-Flash

Execute page (“BCM2 — Programming Interface”)
  • Upload Files: P-Flash + Eeprom
  • File Operations: Decode • Virgin • Save EEPROM • Save Data • Repair ELV
  • Identification fields shown: HW • Version • SW • ECU Type • Immo Type
  • Config checkboxes shown: Master ECU • Slave ECU • TCU • ELV
  • Immo Datafields shown:
    • FAZIT • VIN • Key CS • ECU CS • TCU CS • ELV CS
    • BCM CP • CP Status
    • ECU MAC • TCU MAC • ELV MAC • BCM MAC
    • Power-Class • Key Count • Pin Code
  • Keys slots shown: Key1 … Key8

Dashboard (“Module Details”) highlights
  • Decrypts IMMO data stored in BCM2 Locked D-Flash; supports data issue repair; ELV option is shown.
  • Compatibility shown: Audi A6 / Audi A7 / Audi A8 / VW Touareg
  • Required files shown: D-Flash dump + P-Flash + Key EEPROM file (full decode only)

Execute page (“BCM2 Locked — Programming Interface”)
  • Upload Files: P-Flash + D-Flash + Key File (Optional)
  • File Operations: Decode • Virgin • Save EEPROM • Save Data • Repair ELV
  • Identification fields shown: HW • Version • SW • ECU Type • Immo Type
  • Config checkboxes shown: Master ECU • Slave ECU • TCU • ELV
  • Immo Datafields shown:
    • FAZIT • VIN • Key CS
    • ECU1 CS • ECU2 CS • TCU CS • ELV CS
    • BCM CP • CP Status
    • ECU1 MAC • ECU2 MAC • TCU MAC • ELV MAC • BCM MAC
    • Power-Class • Key Count
  • Keys slots shown: Key1 … Key8

Dashboard (“Module Details”) highlights
  • ELV (Electronic Steering Column Lock) module view for cloning/decrypting IMMO-related data (as stated in UI).
  • Required files shown: DFlash file

Execute page (“AUDI ELV — Electronic Steering Column Lock”)
  • Upload Files: Flash File
  • File Operations: Decode • Save Data • Save File
  • Immo Data fields shown: VIN • Status • Immo Type • CS • Power Class • MAC • ECU Type
  • Console present + Clear button

Dashboard (“Module Details”) highlights
  • Clone/decrypt/edit IMMO data from EZS module for Audi vehicles (as stated in UI).
  • Compatibility note shown: MCU types 1L59W, 3L40K, 0L01Y
  • Required files shown: EEPROM or D-Flash

Execute page (“EZS — Electronic Central Locking”)
  • Upload Files: Eeprom File
  • File Operations: Decode • Save Data • Save File
  • Immo Datafields shown:
    • Fazit • VIN • ECU CS • CS2
    • MAC ECU • MAC ECU 2 • MAC EZS • MAC TCU
    • PIN • Status (dropdown)
    • Power Class • ECU Type • Immo Type • Key Count
  • Keys slots shown: Key1 … Key4

Dashboard (“Module Details”) highlights
  • Crafter EZS module: full IMMO decryption + complete cloning support (as stated in UI).
  • Compatibility shown: VW Crafter
  • Required files shown: EEPROM or D-Flash

Execute page (“EZS Crafter”)
  • Upload Files: Eeprom File
  • File Operations: Decode • Save Data • Save File
  • Immo Data fields shown: Immo ID • VIN • CS • MAC • PIN • Power Class • Immo Type • Key Count
  • Keys slots shown: Key1 … Key8

Dashboard (“Module Details”) highlights
  • CCM enables cloning + full decryption of immobilizer data in VAG CCM units (as stated in UI).
  • Compatibility shown: VW Passat B6 / Passat B7 / Passat CC
  • Required files shown: EEPROM file

Execute page (“CCM — Comfort Control Module”)
  • Upload Files: Eeprom File
  • File Operations: Decode • Save Data • Save File
  • Immo Datafields shown:
    • Part Number • HW • SW • VIN
    • IMMO ID • CS • PIN • Power Class
    • MAC CCM • MAC ECU • MAC ELV
    • Brand (dropdown) • Immo Status (dropdown) • Key Count
  • Keys slots shown: Key1 … Key8

Dashboard (“Module Details”) highlights
  • Supports cloning-style operations for DQ200 / DQ200 G2 MQB / DQ250 MQB / DQ400 MQB (as shown).
  • UI note shown: for DQ400 correct Power Class configuration aligned with the vehicle module is required.
  • Required files shown: EEPROM file + Flash file

Execute page (“TCU — Transmission Control Unit”)
  • Upload Files: Flash File + Eeprom File
  • File Operations: Decode • Save Data • Save EEPROM • Save Flash • Immo Off (button shown)
  • Immo Data fields shown: Part Number • HW • SW • VIN • CS • MAC • Power Class • Immo Flash (dropdown) • TCU Type • Immo Eeprom (dropdown)

Dashboard (“Module Details”) highlights
  • Description shown: Decrypt all immobilizer data for PCR2.1 using EEPROM only — no flash or MCU ID required.
  • Compatibility shown:
    • All 1.6 TDI models equipped with PCR2.1
    • Ibiza
    • Polo
    • Caddy
    • Golf
    • Jeta
    • Others
  • Available actions shown: Decrypt all immo data • Edit all immo data
  • Required files shown:
    • EEPROM 95640
    • Accepted size: 8 KB or 136 KB

Execute page (“PCR 2.1 — EEPROM Only Operations”)
  • Upload Files: Eeprom File (Browse)
  • File Operations: Decode • Save Data • Save EEPROM
  • Immo Data panel with Enable Edition
  • Visible IMMO fields:
    • Part Number • CS • Status (dropdown)
    • MCU ID • MAC • Coding
    • VIN • Power Class
    • IMMO ID • PIN

Dashboard (“Module Details”) highlights
  • Description shown: This module calculates/edits IMMO data for IMMO4, IMMO5, and IMMO6 generations.
  • Compatibility list shown(as displayed):
    • SIMOS PCR2.1 • SIMOS 10.xx • SIMOS 12.xx • SIMOS 18.xx
    • EDC17C46 • EDC17C54 • EDC17CP04 • EDC17CP14 • EDC17CP20
    • EDC17CP44 • EDC17CP54 • EDC17U01 • EDC17U05
    • ME17.1.1 • ME17.1.6 • ME17.5.2 • ME17.5.6
    • MED17.1 • MED17.1.6 • MED17.5 • MED17.5.1 (MPC & ExtFlash)
    • MED17.5.20 • MED17.5.2 • MED17.5.5
    • EDC17C64 • MED17.1.1 • MED17.1.21
    • ME17.5.20 • ME17.5.24 • ME17.5.26
    • MED17.1.21 • MED17.5.25
  • Available actions shown: Decrypt all immo data • Edit all immo data
  • Required files shown: Eeprom File • Flash File OR MCU ID

Execute page (“ECU DECODE — Engine Control Unit”)
  • Upload Files: Eeprom File + Flash File
  • Option: Enter MCU ID Manually (checkbox)
  • File Operations: Decode • Save Data • Save EEPROM
  • Immo Data panel with Enable Edition
  • Visible fields:
    • IMMO Type • VIN • IMMO ID
    • CS • MAC • MAC 1 • MAC 2
    • Power Class • PIN
    • Status (dropdown)

Dashboard (“Module Details”) highlights
  • Title shown: ECU Cloning — Full Automatic
  • What it is (UI description):

    Complete ECU cloning for engine control units including all data, and immobilizer synchronization. Perfect for ECU replacement without dealership.​
  • Available actions shown:
    • Full ECU Clone
    • Immo Data Transfer
  • Required files shown:
    • Original ECU EEPROM/Flash
    • Donor ECU EEPROM/Flash
    • MCU ID (optional)
  • Compatibility shown (as displayed in the UI):
    • SIMOS PCR2.1 • SIMOS 10.xx • SIMOS 12.xx • SIMOS 18.xx
    • EDC17C46 • EDC17C54 • EDC17CP04 • EDC17CP14 • EDC17CP20
    • EDC17CP44 • EDC17CP54 • EDC17U01 • EDC17U05
    • ME17.1.1 • ME17.1.6 • ME17.5.2 • ME17.5.6
    • MED17.1 • MED17.1.6 • MED17.5 • MED17.5.1 (MPC & ExtFlash)
    • MED17.5.20 • MED17.5.2 • MED17.5.5
    • EDC17C64 • MED17.1.1 • MED17.1.21
    • ME17.5.20 • ME17.5.24 • ME17.5.26
    • MED17.1.21 • MED17.5.25



Execute page (“ECU Cloning — Full Automatic”) — what you actually do
  • Two mirrored upload blocks(Original vs Donor) so the tool can move data cleanly between ECUs:
    • Upload Original Files
      • Eeprom File (Original)
      • Flash File (Original)
      • Enter MCU ID Manually (Original) — checkbox (use when MCU ID can’t be auto-detected from files)
    • Upload Donor Files
      • Eeprom File (Donor)
      • Flash File (Donor)
      • Enter MCU ID Manually (Donor) — checkbox (same logic as above)
  • Main action: one large button — “Cloning ECU”

    This is the “one click” workflow trigger for the full automatic operation shown in the UI.​
  • Console: live log panel + Clear button

    Use it to confirm the page is ready, track the workflow steps, and spot missing inputs fast.​

Why this module is special (based on UI design)
  • Unlike single-module decoders, pairing two ECUs (source + donor).
  • The UI clearly separates Original and Donor files, which is exactly what you want for a clean clone workflow.
  • “Immo Data Transfer” being listed as an action suggests the module is not only cloning raw memory, but also targeting immobilizer synchronization as part of the process.

BCM2 + EEPROM 95320 checksum note

View attachment 2614View attachment 2615View attachment 2616View attachment 2617View attachment 2618View attachment 2619View attachment 2620View attachment 2621View attachment 2622
how to login account
 

Post #24

yazıcı

Watchlisted
Türkiye
Joined
08.02.2026
Messages
4
Reaction score
0
Location
Türkiye
Hello, I can't log in, please help.
 

Post #25

tango

Stock Member
Spain
Joined
23.02.2026
Messages
7
Reaction score
15
Location
Spain
not work? i have a problem with elv audi a4 with bcm 95320
 

Post #26

stopmen46

Watchlisted
Germany
Joined
18.03.2026
Messages
1
Reaction score
0
Location
Germany
with password is wright one?
 

Post #27

zrr_immo

Stock Member
Romania
Joined
11.03.2026
Messages
17
Reaction score
4
Location
Romania
Doesnt work login !!!

Invalid credentials
 
Activity
So far there's no one here