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.
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.
BMW / MINI
Its the season of flat batteries and if you guys ever find a customer come in with the complaint similar to.
“Ever since I jump started my car the windows don’t work” or something electrical has stopped working.
What happens is the FRM (footwell) module corrupts the software after a low voltage scenario.
The eeprom jumps into the Dflash and we cannot communicate with the module afterwards leaving us facing the prospect of buying a new module plus programming.
There is another way to resolve the problem. We can connect to the board directly and Re-align the software which Re populates the eeprom side of the software restoring its ability to communicate and work again.
Xhorse Multi Prog detects the misaligned partitions. multiprog has a feature it will do it automatically. Vvdi prog will read and write but not fix it automatically.
You can also buy a clip for the board saves the soldering, saves loads of time.
Soldering is easy on these though.
Problem:
Tried to repair a BMW E series FRM3 Footwell module using Xhorse Multi Prog but it failed me.
Error:
Chip configuration failed. Error code 88030201 crystal frequency does not match.
Solution:
Double-check the wiring connection. The RESET point is not soldered well.
If the problem remains, send a diagnostic report to Xhorse technician.
Hey everyone, let’s walk through cutting a Fiat SIP22 blade using the Xhorse Key Cutting Machine – the Condor Mini Plus II. This key is used in most Fiats from around 2005 onward, so it’s something you’ll see often.
Step-by-Step Guide:
My Take on the Xhorse Condor II:
This machine is a game-changer. It’s fast, easy to use, and super reliable-perfect for automotive keys like the SIP22. If you’re a locksmith looking for a no-fuss, efficient cutter, I highly recommend it.