Xhorse VVDI Tools, VVDI2, VVDI MB, VVDI Prog, VVDI key tool, VVDI BMW etc software & firmware download, update and technical support from vvdishop.com.
Xhorse VVDI Prog read and write JAC vehicles Delphi MT62.1 engine control module ECU successfully. BITBOX can only recognize ID, PCM (genuine) can read but it is costy. VVDI-Prog can read this ecu if using the correct pinout.
Check the wiring diagram pinout here:
If it fails to read MT62.1 ECU by this pinout, try this:
FYI:
VVDI Prog Pinout to Dephi MT62.1G ECU
Xhorse VVDI Key Tool Max Pro released new functions on June 3rd, 2026.
New Functions, More Possibilities.
What’s New on KEY TOOL MAX PRO:
Update BMW BDC2 / BDC3 / BCP / U Key Cloning function.
Adds OBD Key Programming for New EV models
Adds OBD key programming for Honda and Yamaha motorcycles (some require XDKP92GL adapter).
Xhorse Multi Prog new user report:
Cloning Renault Sagem S3000 with success!
The user copied the flash memory from the original one of the car and wrote the eeropm separately but yes there are many options if you mean disabling the immobilizer (IMMO OFF)!
Speaking of multiprog xhorse for this type of sagem s3000 motor computer flash and eeprom reading is feasible but writing is only for flash the eeprom needs to be stripped off the board and written separately repeatedly with multiprog!
Images attached:
Problem:
Xhorse Multi Prog will not read Immobiliser Data on a 2022 Skodia Kodiaq MQB49 5C smart key. It said chip connection failed.
Any solution?
Solution:
He did not modify the MCU cable as shown in the diagram.
To read MQB49 5C/5D original key data with multi-prog, need to modify mcu cable first.
Fix the ground cable at plug.
Optional solution
1. Read 5C 5D key data with multi prog + 5C 5D solder free adapters.
2. Read key data with Xhorse VVDI Key Tool Plus.
Problem:
It’s a VW Polo MQB 49 5c from the end of 2018, only starting it works, but the remote does not work. The customer has already tried all of these, what could it be? He can no longer program the original key, but the remote does work, how is it possible that it no longer starts, only the Xhorse MQB and KD keys start without the remote?
Reason and Solution:
Key ID issue.
Because when you program a gecko online key MQB, it uses the key ID that is stored in the immo data, so you need to change the key ID with the original system and then it should work.
The clue is the two universal keys starting the vehicle. When adding keys you make the normal dealer key and save the key sync data as well, normally you have complete immo data from the cluster but mqb49 5c it’s from the original key so you have to make a normal dealer key as gecko online dealer key uses the original key ID.
Xhorse vvdi key tool plus has the function to modify original key ID.
Now when making normal dealer key on vag if the car is connected to Odis it will knock out the keys as it’s not a gecko online key.
In the past, only Xhorse VVDI Key Tool Plus supports BMW BDC2 all keys lost programming function, and it was a test version with a Chinese menu.
Good news — XHORSE has officially released the BDC2 all keys lost software, and both the MIDI and VVDI2 devices have been upgraded with this feature.
The menu is in English, not a test menu.
BMW BDC2 All Key Lost is now supported!
Available on:
VVDI KEY TOOL PLUS
VVDI KEY TOOL MIDI
VVDI2
It is done on bench +obd +ecu eeprom. Need ECU D flash, on bench unlock bdc, +obd sync ecu.
Does it modify the data?
That’s the only way that it works for all keys lost.
The G-series bimmers use “synchro” just like MQB/MLB/FBS4. Master immo password derived from multiple individual module passwords. Without a working key, data needs to change.
Problem:
Trying to generate Xhorse SW-007 smart watch for my car and this keeps coming up?
Car is 2013 range rover vogue.
Error: Use Smart Key or XM Remote.
SW-007 is the smart key why it still ask for a smart key.
Solution:
Change the battery. The battery must be full.
Feedback:
Yes, tried a battery. I’ve sorted it now.
I took the watch apart and removed the board then held the battery on it and held into the reader on the vvdi tool and it generated it. Its working now
How to clone a VW Golf MK5 new key using Xhorse vvdi mini key tool?
Original key: 1K0959753G
The new key was purchased from Xhorse, an XEB510EN Gen2 wire remote, and customized to the car’s make and model using the part number on the key.
The immobilizer chip of the original key was also cloned into this key (the XT27B chip is built-in).
Preparation and cloning were done using the VVDI MINI KEY TOOL. To clone the ORIGINAL immobilizer chip, I had to walk to the car, as the VVDI MINI KEY TOOL sniffs the data exchange between the coil and the chip, then sends it to the server for calculation. To sniff, you need to hold the antenna close to the immobilizer ring and turn the ignition on and off ten times with the key removed. Each successful sniffing attempt will be displayed on the screen. It took no more than five minutes. Of course, it could have been done a little easier, by changing the ID in the new chip to match the original and adding data from the dashboard using a heavier tool like the VVDI2 . But I was interested in trying out the original chip cloning feature.
Then program remote with VDCS. I followed the standard procedure for linking the radio channel and the door cylinder and checking the functionality.
Go to Module 46 – Adaptations – Channel 01 – enter the number of keys – Test – Save. However, this didn’t work for me; the app didn’t accept the number “2.” Finally, I set the number of keys to “1” – Test – Save. I turned off the ignition, exited the car, and paired the key through the door cylinder: turn it clockwise while pressing the “Close” button, then counterclockwise while pressing the “Open” button. The key was successfully paired to the car via radio. Then I checked the functionality of the second original key and paired the second key the same way without leaving the door.
The car starts, the central locking system responds to the new key fob. Mission accomplished!
Here comes the user’s working experience on Porsche Panamera BCM cloning with Xhorse Multi Prog programmer.
Have successfully read this Porsche BCM – MC9S12XE – 2M25J.
Backed up both PFLASH and DFLASH with Xhorse multi prog.
Now need to clone it to a good donor module.
Both the original module and the donor module were backed up with DFlash / PFlash.
After that, the donor MCU was unlocked. The procedure completed successfully with Multiprog, but all information from the donor gets erased during the unlock process (full backup before unlocking the chip is mandatory).
Then the donor was written with:
– DFlash from the original module
– PFlash from the donor module
With the module configuration, this procedure worked without any issues and the vehicle (Panamera) is operating normally.
The two BCM modules have differences in part numbers. With more significant differences in another case, it will probably also be necessary to transfer the PFlash from the original module.
