Xhorse VVDI Prog Read and Write Renault SIRIUS 32

 Renault Siemens SIRIUS 32 read and write, immo off with Xhorse VVDI Prog.

Disassemble the Siemens SIRIUS 32 ECU.

Locate and desolder the AM29F400BB chip.

Solder the AM29F400BB chip to the eeprom adapter.

In VVDIProg software, select EEPROM-AMD-AM29F400BB-xxS option.

Read and save immo data.

Modify immo data with IMMO Bypass program or a tuner.

Write the modified immo data with vvdi prog.

Solder the AM29F400BB chip back to the ECU. Reinstall the ECU and install it on vehicle.

www.vvdishop.com

Xhorse VVDI Prog 5.3.8 adds BMW G Series BDC3 Option

 Xhorse VVDI Prog released new software version V5.3.8 on October, 10th, 2025.

VVDIProg v5.3.8 (2025-10-09)
* This version DON’t need update firmware
+ Add BDC03 option in <4-IMMOBILIZER>-><BMW>
* Modify MB91F467D option in <2-MCU>-><FUJITSU-MB9XF>: Erasing failure repair
* Modify CAMRY AC COMPUTER option in <8-OTHER>-><TOYOTA>: Erasing failure repair
* Modify Rover 2017- BCM(MPC5748G)option in <4-IMMOBILIZER>-><LandRover>: Wiring diagram update
* Modify S350-CONTROL-UNIT-PKE option in <4-IMMOBILIZER>-><JMC>: Wiring diagram update
* Modify ZAFIRA-DG128, ASTRA-DG128 options in <4-IMMOBILIZER>-><Opel>: Wiring diagram update
* Fix of other known issues

Free download VVDI Prog V5.3.8 software

VVDI Prog BMW BDC3 wiring diagram

BMW BDC03 NCF29A1-B

BMW BDC03 NCF29A1

Xhorse multi prog also update BMW BDC3 option on October 9th, 2025.

Collect original BMW BDC3 key data with vvdi prog, then load data to vvdi2/key tool plus/key tool midi to add (copy) key.

How to Cut PS AHU83 Key with Xhorse Dolphin XP005

 Problem:

When I tried to cut a Citroen Jumpy key with a HU83 blade in my Xhorse Dolphin XP005, I had this problem. It fit properly in the door lock, but not in the ignition cylinder. Afterwards, I looked at the detail in the attached photo. Could this be the reason why the key didn’t fit properly?

Solution:

The end of the key likely isn’t actually cut properly. If you held the original and new key up together they would be slightly different at the tips/last bitting. Use universal duplication to cut HU83 with extra bitting.
Other people with the same issue. So as long as the machine is calibrated right, it decoded it properly, and the key actually was HU83 and not VA2, then it will just be that same bug, it’s nothing you’ve done wrong apart from maybe not comparing the keys after you cut them.

We’ve experienced the same problem, and the issue lies not with the cut, but with the key not passing dust lid you need to file tip of the key narrow to pass it. Just done the same hu83 for 308 today, file tip a bit and it will work.

Tips to Read GM BCM D70F3469 with Xhorse Multi Prog

 Problem:

I want to clone this Chevrolet Cruze BCM D70F3469 using Xhorse multi prog, but I’m getting this error.

Error: Chip configuration failed. Error code 08030201. Crystal frequency does not match.

Solution:

Check your connections.  Need a 120 ohm resistor between the two CAN H and L wires. Between CAN H and L, just jumper those wires with the resistor.

A 120 ohm resistor is required on the CAN L and H wires, since their communication uses the resistance security system, implemented in the communication network of these units. This is intended to provide additional protection against diagnostics from the OBD2 port. If the circuit is opened by resistance, communication with the corresponding modules is lost. If you want to scan the vehicle and certain modules don’t communicate, by sheer logic, everything is derived thanks to the diagnostic protocol.

Program W220 Kline 4J74Y All Keys Lost with VVDI Key Tool Plus

Tips to program Mercedes Benz W220 all keys lost with xhorse tools.

2002 Mercedes S500 (W220)
-All Keys Lost-
VVDI Key Tool Plus Failed Via IR.
Autel IM608 Failed Via IR.
CGDI MB Failed Via IR.
Xhorse Multi-Prog + VVDI Key Tool Plus
Success.
EIS/EZS: W215/W220 (K-Line)
Chipset: Motorola (4J74Y)
•Read EEPROM1 with Xhorse Multi-Prog
•Transfer File to VVDI Key Tool Plus (Xhorse Cloud)
•Load & Decode File
•Prepare Key File
•Write Key file