Problem:
Tried to program 2022 Nissan Sentra B18 smart key with xhorse vvdi key tool plus. It asks for a 32-digit rolling code.
Where can I get the pin code?
Solution:
Key tool plus cannot pull pin code for Sentra B18.
Need to remove HFM hands free module and read pin from dump.
Xhorse multi prog will read HFM data, but key tool plus cannot decode pin code automatically.
Need to send data to xhorse engineer to decode pin code manually.
Immobilizer deactivation (Immo Off) is a common procedure for Hyundai and Kia vehicles with the ME 17.9.1 ECU, often required after ECU repairs, key loss, or engine swaps. This guide outlines key steps and considerations.
Here we will show how to do Hyundai ME17.9.1 ECU immo off with xhorse multi prog programmer.
Select Kia Bosch ME17.9.1 ECU.
Check wiring diagram.
Connect ECU with multi prog.
Read and save int eeprom.
Read and save flash data.
Go to Tool tab- Turn off immo.
Select Hyundai-Elantra-ME17.9.11. Load original flash data.
Hit Turn off the immo.
Generate immo off file and save.
Load immo off file and write data to ECU with multiprog.
Verify checksum correction.
Write immo off data successfully.
IMMO OFF is done.
Cloning an ignition switch (EIS) for Mercedes-Benz vehicles like the W215/W220/W230 model can be a cost-effective solution for replacements. In this guide, we’ll walk you through the process of cloning data from the original EIS to a replacement unit using an Xhorse VVDI Prog programmer.
Tools Required
Original and replacement EIS (Part number: 2305450708)
Mercedes key (from the original ignition switch)
Pinout adapter (for testing)
Step-by-Step Process
1. Reading the Original EPROM Data
In VVDI Prog software, select Benz-Immobilizer- Benz- WIS-W230(W215) 4J74Y
Check wiring diagram.
Connect the original EIS to the VVDI programmer.
Use the software to read the EPROM data from the original EIS. This data contains critical information needed for the replacement unit.
2. Transferring Data to the Replacement EIS
Connect the replacement ignition switch EIS to the VVDI programmer.
Write the original EPROM data onto the replacement unit. This ensures the new EIS will recognize the vehicle’s keys and function correctly.
3. Testing the Replacement Ignition Switch
Use the pinout adapter from VVDI Prog to simulate the EIS connection.
Insert the original key into the replacement EIS.
If the cloning was successful, you should hear a click, indicating the key has been detected.
Turn the key to verify the ignition switch operates properly.
Conclusion
By following these steps, you can successfully clone a Mercedes W230 ignition switch using a VVDI Prog programmer. This method saves time and money compared to dealership replacements.
Choosing the right key cutting machine is crucial for locksmiths, whether you’re a mobile professional or shop-based. Two top-tier options are the Xhorse Dolphin XP005L (Dolphin II) and the CGDI Godzilla. Here’s a detailed comparison to help you decide which one suits your needs.
Dolphin II vs. CGDI Godzilla Comparison
The Dolphin II is designed for locksmiths on the move. Its compact, lightweight build and built-in rechargeable battery allow you to take it anywhere – whether you’re servicing cars, homes, or businesses on-site. No need for a constant power source like the Godzilla, which ties you to a shop.
The Godzilla lacks wireless capabilities, meaning manual updates and fewer tech-forward advantages.
The M5 Clamp on the Dolphin II handles a wider variety of keys with precision, including high-security and automotive keys. While the Godzilla can cut standard keys well, it doesn’t match the Dolphin’s adaptability for modern locksmithing needs.
With regular software upgrades, the Dolphin II evolves with industry trends, ensuring long-term usability. The Godzilla, while cheaper upfront, may require costly replacements or upgrades sooner.
Godzilla: A Good Machine, But Not the Best
The CGDI Godzilla is a budget-friendly, durable option for shop-based locksmiths, but it lacks:
– Portability (no battery, requires constant power)
– Wireless features (no Bluetooth or Wi-Fi)
– Latest tech advancements (manual updates, no touchscreen.
Conclusion: The Dolphin II Wins
CGDI Godzilla is ideal forLocksmiths who prioritize durability and affordability for a fixed workstation.
If you want a high-performance, portable, and future-proof key cutting machine, the Xhorse Dolphin XP005L is the clear winner. It’s the best choice for locksmiths who value mobility, efficiency, and staying ahead of the competition.
In this tutorial, we’ll walk through the process of cloning a Ford Focus MK2 instrument cluster (Part No.: 8V4T-10849-HH) by reading and writing its EEPROM and Flash data using the Xhorse VVDI Prog tool. This procedure is useful for replacing a faulty cluster or performing repairs while retaining the original vehicle data.
Tools Required
MC9S12 Cable
Screwdriver/Pry Tool (to open the cluster housing)
Replacement Cluster (same part number as the original)
Step-by-Step Procedure
Remove the instrument cluster from the dashboard by gently prying it out. Releasing the clips on both sides allows the cluster to slide out easily.
Once removed, locate the EEPROM and Flash memory chips on the circuit board.
Use the MC9S12 cable to connect the cluster to the VVDI Prog tool.
Follow the pinout diagram in the software to ensure correct wiring:
Power (VCC)
Ground (GND)
Reset (RST)
Communication lines (PCC, etc.)

Open VVDI Prog software and select the Ford Focus 09-10 dashboard option.
Click “Read” to extract:
EEPROM data and save.
Flash data (saved separately)
Verify that the readings are successful before proceeding.

Once the replacement cluster arrives, connect it to VVDI Prog.
Load the previously saved EEPROM and Flash files and click “Write” to transfer the data.
Ensure all mileage, immobilizer, and settings match the original cluster.
Carefully reinstall the cloned cluster into the dashboard, securing all clips.
Test the cluster by turning on the ignition to confirm functionality.
Important Notes
Compatibility is critical—the replacement cluster must have the exact same part number.
Improper wiring or data transfer may corrupt the cluster, so double-check connections.
This process may require additional coding for full vehicle integration (e.g., immobilizer sync).