Autel IM508 Read EDC16U34 ECU CS and PIN from Dump

Here we will show how to read CS and PIN code from EDC16 engine ECUs using Autel MaxiIM IM508 XP400 pro.

 

Model example: 2007 VW Touran

ECU type: Bosch EDC16U34

EEPROM chip: ST95320

The similar procedure goes to other EDC16 engine ECUs.

Procedure:

Go to EEPROM function, select ST95320.

Connect the chip with XP400 Pro using the eeprom clip adapter (from 3rd party).

Read and save 95320 chip data.

Then go to IMMO programming function, select VW brand.

Choose Expert Selection.

Select Dump tool function.

Choose Engine EDC16 [95320] option.

Upload and select 95320 eeprom data just saved.

Autel IM508 will extract CS and PIN code of this ECU.

Retrieve the code and program your keys in two minutes.

How to Clone VAG MQB RH850 Cluster by Autel IM608?

Question:  Is it possible to clone the VAG MQB instrument cluster with Autel MaxiIM IM608? It’s a 2015 VW Golf.
If yes, where can i find the pinout for it?

Yes, the Autel MaxiIM IM608 (especially IM608/II or Pro variants) can clone VAG MQB instrument clusters, but it typically requires the XP400 Pro programmer + specific adapters (like APB130 or APB131), bench work (removing the cluster), and the latest software updates. It is not a simple OBD plug-and-play process in most cases.

Need to read and write VAG RH850 cluster data using APB131 adapter.
IM608 will show you the wiring connection diagram.

 

Requirements and Process Overview

• Remove the cluster and work on the bench.
• Use XP400 Pro + APB130/APB131 adapter (APB131 for some V850/RH850 and newer MQB).
• Follow on-screen wiring diagrams for soldering/pin connections.
• Read the original cluster’s data – decode – write to the new/donor cluster.

Limitations and Notes
Not all clusters are equally easy — Success depends on the exact chipset (e.g., NEC35XX vs. others) and cluster version. Older MQB (e.g., 2014–2016) and some 2015 Golf examples are discussed in forums with mixed direct OBD results; bench work is more reliable.
Adapters are essential — Without XP400 Pro + APB130/131, full cluster read/write is limited.
Software updates matter — Ensure you have the latest VW/Audi/Skoda software (e.g., V1.90+ in older updates; newer ones add more MQB support).
Alternatives often mentioned: Tools like Xhorse VVDI2, Yanhua ACDP are used by some for easier cluster swaps/mileage in certain cases. Autel excels in the IMMO/key side.

 

User feedback:

Got it done with the IM608 and the APB131 adapter. Vehicle started no problem and transferred all the information.

Autel IM608 BMW EWS4 AKL Car No Crank Solution

Problem:

It’s a 2008 BMW X3 with EWS4.4 all keys lost. Read dump with Autel IM608 XP400 Pro and CG Pro. Both dumps are identical. Read the flash with Autel and the data is good.

In live data, it recognizes the key as the slot I wrote it to, but it says key password incorrect, rolling code incorrect. It won’t crank.

I tried a few different chips, including vvdi superchip, which were not recognizing, but this Ilco key is now recognizing as key 8. But still says key password incorrect, rolling code incorrect, in live data.

Solution:

The most common cause for no-crank (or crank but no start) after EEPROM-based key programming on BMW EWS4.4 (all keys lost) is a lost or mismatched synchronization between the EWS module and the DME (engine ECU). This often triggers an “anti-tampering” or EWS manipulation fault.

 

Quick Checks First

• Verify the EWS programming: Ensure you correctly read the original EEPROM dump, programmed the new key(s) into an available/used slot (often via tools like AK90, VVDI, etc.), and wrote the updated file back to the EWS chip. Some users forget this step or experience a write error/corruption — reload the original dump if needed and re-program.
• Battery voltage: Must be strong (fully charged, ideally on a charger at ~13.5V during procedures). Low voltage can desync the system.
• Connections: Confirm the EWS module is properly reinstalled, ring antenna (around ignition) is connected, and no wiring damage.
• Scan for codes: Use a BMW-compatible scanner (INPA, ISTA, Autel, Launch, etc.) to check for EWS/DME faults like anti-tampering, ISN mismatch, or communication errors.

 

Main Solution: Perform DME/EWS Alignment (Synchronization)

This re-matches the ISN (Individual Serial Number) and rolling codes between EWS and DME.

 

• Connect a diagnostic tool that supports EWS/DME alignment (INPA with K-DCAN is popular and cheap for E46/E39/X3 era cars; ISTA, PASoft, or Autel also work).
• Read the ISN from the DME (often under Coding or Identification).
• Go to the EWS or DME adaptation/sync function and perform the alignment (sometimes called “EWS Calibration,” “DME-EWS Start Alignment,” or “Sync”).
• Follow on-screen prompts (usually turn ignition on/off, wait, etc.).
• Clear fault codes and test start.

Alternative simple reset (if no tool immediately available): Disconnect the battery negative terminal for 10–30+ minutes, reconnect, and try starting. This can help minor desyncs but often requires proper alignment afterward.

 

Other Possible Fixes

• Key slot issues — With AK90-style tools, ensure keys are marked as “used” in the correct slots and unused ones unchecked when writing back.
• Transponder chip quality — Cheap blanks can program but fail to authenticate properly.
• EWS module damage — Rare, but bench testing or professional repair may be needed if alignment fails repeatedly.
• Transmission/P/N switch (automatics) — Can lock out cranking independently of immobilizer.

 

User report:

To fix the errors I wrote a key to slot one , then resync the EWS to the DME.
Then inserted the key and the car started, then manually added the remote locking.

Backed up the file just incase, then deleted all the keys, added key one use Xhorse XT15 chip, so only one key in the EWS, plugged everything back in
then turned the IGN on, and paired the EWS to the DME, the car then started and I added 2 more keys.

Autel IM508 Cannot Make Xhorse MQB Dealer Key Solution

Problem:

Skoda Octavia 2016 add key Full MQB ! I have the all the data pulled out. Autel IM508 can’t make the dealer key seems it is not accepting this Xhorse MQB key. It says keyless but i assume it is the right one. It is a bladed key. Anyone used this key or generated any other key for this car?

Solution:

You cannot generate an Xhorse key with Autel. Likewise, you cannot generate an Autel key with Xhorse.

Xhorse MQB keys can only be precoded with Xhorse tools.
Use Xhorse tools or change remote brand. Use Keydiy remote or OEM.

Don’t use xhorse remote with Autel. KD remote works fine, but try to do dealer key input cs manual.

Xhorse stopped accepting third-party companies to use their remotes.

You can make xhorse dealer key only with xhorse hardware.
Switched to KD, aftermarket or OEM key.
People use KD remotes without problem.

Check: KD ZB smart remote

Autel IM608 II Update Benz FBS4 VGS4 TCU Cloning

 

Autel MaxiIM IM508S and IM608 II released a big immo software update for Benz, BMW and VAG models- update lots of ECU and TCU cloning models.

Requires Gbox3.

Mercedes Benz (New Feature)
The following ECU cloning function covers models from 2000 to 2019

Supports cloning (Bench mode) for the following 27 ECMs from 4 suppliers for Mercedes Benz:

BOSCH:
CRR2, EDC16C2, EDC16C32, EDC16CP31, EDC16CP36, EDC17C43, EDC17C66, EDC17CP01, EDC17CP10, EDC17CP46(CR60), EDC17CP57_V1(CR43), EDC17CP57_V2(CR61), ME17.7, ME17.7.8, MED17.7.1, MED17.7.2, MED17.7.3, MED17.7.3.1, MED17.7.5, MED17.7.7,MRD1;

CONTINENTAL:
SID307(CRR1), SID310(CRR1 plus), SIM271DE;

DELPHI:
CRD11, CRD3x.x;

SIEMENS:
SIM271KE

Supports cloning for the following 8 TCUs for Benz:
FSB4 VGS4-0-NAG2 cloning via Bench mode;
FSB4 VGS4-500-NAG2 cloning via Boot mode;
VGS-NAG3, VGS2-FDCT, VGS-FCVT, VGS-FDCT, EGS52, VGS3-FDCT cloning via Bench mode

BMW
The following ECU cloning function covers E/F/G chassis-equipped models up to 2019
Supports cloning (Bench mode) for the following 42 ECMs from 2 suppliers for BMW:
BOSCH:
EDC16C1, EDC16C31, EDC16C35, EDC16CP35, EDC17C06, EDC17C41, EDC17C50, EDC17C56, EDC17C76, EDC17CP02, EDC17CP09, EDC17CP45, EDC17CP49, MD1CP002, MD1CP032, MD1CS001, ME17.2.1, ME17.2.42, MED17.2, MEV17.2, MEV17.2.1, MEVD17.2, MEVD17.2.3, MEVD17.2.4, MEVD17.2.5, MEVD17.2.6, MEVD17.2.8, MEVD17.2.9, MEVD17.2.G, MEVD17.2.H, MEVD17.2.K, MEVD17.2.P, MEVD17.8.4, MG1CS003, MG1CS024, MG1CS201;
SIEMENS/CONTINENTAL:
MSD80, MSD81, MSD85, MSD87, MSV80, MSV90

Supports cloning (Bench mode) for the following 6 TCUs from 2 suppliers for BMW:
GETRAG:
F-6HP,F-7DCT300,F-DKG 436 Gen2;
TCM ZF:
F-8HP,F-8HP Gen3,G-8HP

Volkswagen
The following ECU cloning function covers models from 2000 to 2024
Supports cloning (Bench mode) for the following 62 ECMs from 3 suppliers for VAG:
BOSCH:
EDC16C4, EDC16CP, EDC16CP34, EDC16CP34 CRAFTER, EDC16CP34 M&S, EDC16U1, EDC16U31, EDC16U34, EDC17C46, EDC17C54, EDC17C64, EDC17C74, EDC17CP04, EDC17CP14, EDC17CP20, EDC17CP20_CRAFTER, EDC17CP24, EDC17CP44, EDC17CP54, EDC17CP74, EDC17U01, EDC17U05, ME17.1.1, ME17.1.6, ME17.5.20, ME17.5.22, ME17.5.24, ME17.5.26, ME17.5.6, MED17.1, MED17.1.1, MED17.1.10, MED17.1.12, MED17.1.21, MED17.1.27, MED17.1.6, MED17.1.61, MED17.1.62, MED17.5, MED17.5.1, MED17.5.2, MED17.5.20, MED17.5.21, MED17.5.25, MED17.5.5, MED9.1, MED9.1.1, MED9.1.2, MED9.1.5, MED9.5, MED9.5.10;
CONTINENTAL:
Simos 12.1, Simos 12.2,Simos 8.3x, Simos 8.4x, Simos 8.5x, Simos 8.6x;
SIEMENS:
PCR2.1, Simos 6.2, Simos 6.3, Simos 7.1, Simos 7.1A

Supports cloning (Bench mode) for the following 6 TCUs from 3 suppliers for Volkswagen:
BOSCH:
DQ380;
CONTINENTAL:
DQ400, DQ500;
TEMIC:
DQ200_G2_PQ, DQ200D, DQ250_MQB

Autel IM608 Fix VAG IMMO4 ABS Coding Lost Problem

For VW IMMO4 All Keys Lost (AKL) procedures, backing up and restoring your ABS coding is a preventative step. Because AKL procedures via Service Mode disrupt communication, the ABS module frequently loses its coding, which requires a specific restoration workflow using your immobilizer tool.

 

When you are doing these all keys lost scenarios using Autel MaxiIM IM608 device, we recommend doing the Code loud backup procedure first.
Go to the Diagnostic Menu first and do a complete cloud backup.

It will back up every module in case some modules get messed up.
You can always restore it back.
The other option is if you just want to back up the ABS data. You can click Back up ABS code to recover it.

In Autel you have different paths. One path might not work but if you just take a different route that one will work.

 

If the ABS coding is lost, the Autel IM608/IM508 XP400 Pro can do repair abs/restore abs for free.

 

How to Fix ABS Coding with Autel IM608/IM508?

Go to the Diagnostic side- Programming/Customization and look under Online Coding and see if it’s there.

 

 

NOTE:

Recommend using this Godiag GT110 pogo pin adapter for IMMO4/IMMO4.5 cluster. It works with Autel as well as many other devices on bench and saves a whole lot of time.

As long as you pogo the right pin. It lets you in, save the data to use it to make a dealer key with the xp400. Can generate a VW chip with xhorse. And it will accept that. Once made then can learn the key to it. All on the bench.