Chip-Tools

ITDEENBGES

MQB Immo 5C/5D: extracting immo data from the key's NCF processor for spare keys and module replacement

This solution reads the complete immobiliser data straight from a working MQB Immo 5C and 5D key: Key ID, immobiliser Secret Key (CS), synchronisation data (Immo Data) and immo platform information. It's what you need to add a spare key without reading the cluster or CEM, and to extract the slave modules' immo data when replacing an ECU, TCU or ELV.

Procedure

1. Strip the shell off the working key and get to the PCB.
2. Open the ZN085 software, go into the NCF menu and bring up the wiring diagram for the key you're working on.
3. Solder the CB503 cable to the PCB connection points following the diagram shown in the NCF menu of the ZN085 software.
4. Read the NCF MCU to extract Key ID, Secret Key (CS), synchronisation data (Immo Data) and immo platform information. No third-party information is needed.
5. Save the file with the extracted data: it is the basis both for the new key and for any module replacement.
6. For a new or used OEM key: prepare it as a dealer key with "Make Key with ZN085", then program it to the vehicle with "Key Learning by CS".
7. For a virgin aftermarket key: prepare it with "Make Key with Protag" using the PROTAG, then run "Key Learning by CS".
8. For a module replacement: with a working key from the donor vehicle available, use the extracted immo data to replace the ECU, TCU or ELV, without having to read the donor's module directly or buy the synchronisation data from third-party sources.

Reference screenshots