Xhorse VVDI2 BMW BDC2 Coding Unknown Version Solution

Problem:

Want to add a new key to BMW G31 BDC2 system with xhorse vvdi2 and BMW BDC2 adapter. but I can’t get past reading the code.
VVDI2 gave an error coding unknown version.

Solution:

Coding file is corrupt. Put it into the car and add coding file with your tool.

The car has a software version from 2021, but the coding data is missing, you can do your work normally, it has to be imported cafd manuel later, but that only works with a coding program, car missin cafd from S15A-21-11-560.

User report:

The problem has been solved and VVDI2 handled it very well. The problem was that the client arrived with corrupted CAFD data. Didn’t notice it at first. I put the BDC back in the car and fixed it via obd2 using the X-Diag program and Launch adapter. Then I went back to the previous steps and everything went smoothly.

I changed the BDC coding via OBD and the vvdi2 program accepted the new coding allowing me to program the new key.

VVDI2 VW Polo MQB R7F701401 Decode 5000 Error Solution

 Problem:

It’s a 2018 VW Polo MQB48 model with processor R7F701401.
I have the PCJ7991WT chip on the PCB, which finally confirms that it is the mqb49 5c.

Xhorse VVDI2 cannot decode data (read by multi prog) or change the mileage.

Solution:

It’s MQB49 cluster. Requires new MQB49 5C adapter set.
Only use the new MQB49 adapter, vvdi2 will decode data to change 5C/5D cluster mileage.

Use new MQB49 adapter and use this option to read cluster, than decode data with vvdi2.

Xhorse VVDI2 No BMW BDC3 Menu Solution

Is there any news about Xhorse VVDI2 where to upload BMW BDC3 key data for copy. No new software of VVDI2 to load file.

VVDI2 upload BDC3 key data menu is ready.

If there is no BMW BDC3 menu, download and replace VVDI2-BMW.exe file. It will be there.

Free download VVDI2-BMW.exe

The function requires BMW G function license activation.

Need to read BDC3 key data by vvdi prog or multi prog first.

VVDI2 Program BMW X6 F16 BDC All Keys Lost

 Introduction & Initial Challenge:

The vehicle in question, a BMW X6 F16 BDC system, arrived with a complete key loss (AKL). In such modern BMWs, simply programming a new key via the OBD-II port is not possible without first obtaining critical security data and preparing the vehicle’s central computer. The primary challenge involves two main steps:

Reading the Immobilizer Security Number (ISN) from the Engine Control Unit (DME).

Unlocking and preparing the Body Domain Controller (BDC) to accept new keys.

Step 1: Reading the ISN from the DME

Since no keys were present, the first step was to physically access the vehicle’s engine control units.

Remove DME from the vehicle. The specific model was identified as Bosch 0261 S15 497 (MEVD 17.2.h).

You can read ISN code with CG FC200 programmer on bench.

Step 2: Unlock and Prepare the BDC

With the ISN acquired, the next step was to prepare the BDC, the vehicle’s main security and access module.

Physical Access: The BDC was carefully removed from the vehicle. Its cover was opened to reveal the internal circuit board and the essential M95xxx EPROM chip.

Read and save BDC 95256 eeprom data with vvdi prog and clip adapter.

Bench Setup: The BDC was placed on a dedicated test bench, where power and necessary connectors were attached to simulate being in the vehicle.

Unlocking via VVDI2: Instead of directly reading and writing the EEPROM, we used the VVDI2. By selecting the “BDC Key Learn” function and choosing to program/unlock the BDC directly via OBD (simulated on the bench), the tool connected to an online server.

Server-Side Unlocking: This process involved the server generating a modified “flash file.” The VVDI2 tool then wrote this file to the BDC, a process that took several minutes. Upon completion, a message confirmed the “FEM BDC update success.”

Step: Programming Key

After the BDC was successfully unlocked, we proceeded to program the first new key.

Key Learning: Back in the VVDI2’s “BDC Key Learn” menu, the “Add Key” function was used. The previously saved ISN was pasted into the tool.

Success with Anomalies: The key was successfully learned, and the car started successfully. The remote functions also worked after a battery was installed in the key fob.

Persistent Fault Code: A diagnostic scan revealed a persistent “SWFL Lost” (Steering Wheel Lock) fault code. Clearing this fault permanently would require a full update of the BDC using BMW’s official ESys software, a step deferred based on the customer’s potential need for only one key.

www.vvdishop.com

Tips to Clone Audi A3 MQB Cluster with Xhorse

 Is it possible to clone original read from audi A3 2013 MQB cluster to another cluster with exact same MCI D70F3537. Original cluster dead after full read. I have already calculated sync data for dealer key preparation. All keys lost originally.

But after cluster read. And attempt to reset cluster didn’t work. I just need to confirm if it is possible to take original read over to donor cluster.

Original cluster part number is 8V0920870. 0570. H24
Donor cluster part number is 8v0920870G. 2220. H03.

Both cluster is 2013 year model. And both for audi car.

Will it be possible to clone D70F3537 from one to another directly on bench using Xhorse multi prog with MQB adapter?

Feedback:

If the sw and hw are the same then it is possible.

I used sync data to prepare dealer key successfully.
Select dashboard replace. Xhorse Vvdi2 asked for old dash encrypted data and new dash encrypted data. Calculated another file to be written with multi prog or vvdi prog. File written successfully. All info from old dash into new dash. Prepared dealer key with sync data. Used immo data selection to learn key successfully.
Car started and removed coded automatically when key learned.