VVDI Key Tool Plus VAG vs VVDI2 Full VAG


I’m stuck between vvdi2 full VAG version SV86-C+XNR-SS290 and VVDi2 Keytool plus VAG version xDKP02GL, I am already purchasing VVDI multi prog so I need a tool that will greatly help in vag immobilizer & instrument cluster cloning,key learning etc and not for diagnostics.


First of all, check a table comparison below:

Item Xhorse VVDI2 Full VAG Xhorse VVDI Key Tool Plus VAG
Basic VAG IMMO/KM correction Yes Yes
IMMO4 Yes Yes
IMMO5 Yes Yes
Porsche IMMO Yes Yes
OBD48 Clone (obdii copy 48) Yes Yes
96 bit copy 48 Yes Yes
MQB/49 (5C) IMMO System Yes Yes
IMMO Data Tool Yes Yes
MQB48 License Need to buy MQB48 License Need to buy MQB48 license
MQB48 RH850 No Yes, with RH850/V850 cable
IMMO for other brands No Also work on other ordinary brands such as Toyota, Honda, Ford, Buick, Chevrolet, etc.
Toyota 8A All keys lost No Yes
Key Tool Functions (remote clone, transponder clone, generate remote/transponder, Remote cloud recognition) No Yes
Remote renew No Yes
Maintenance feature No Yes
Control xhorse key cutting machine No Yes


In sum:

VAG function is almost the same expert key tool plus supports RH850 MQB48 immo key programming, vvdi2 does not.

Key tool plus has PROG function to read eeprom, ecu and mcu. Vvdi2 does not.

Key tool plus has key tool functions, it can generate remote/transponder, clone remote, renew remote etc. VVDI2 does not.

Key tool plus have extra immo coverage for some common brands, Toyota, Nissan, Ford, GM etc, it also does Toyota 8A (smart and non-smart) all keys lost. Vvdi2 does not.

Key tool plus also controls key cutting machines. Vvdi2 does not.

Vvdi2 full vag version price is the same as full version. Vvdi2 full is recommended.


Xhorse VVDI2 Program 2004 VW Tourage all keys lost

I was working a 2004 vw tourage, none original key could not program it, i had the pin and cs and no luck. we purchased the new original key from dealer and still no luck. is this a 4th generation immo? i am kind of new to vw key programming. I have tried that, and just regular key programming it opens the cluster, dash, and starts and dies. after turning the key in to off position, it won’t turn the cluster on, the steering is locked also. when I leave the ignition key in the on position, i can access engine control module, kessy also. I don’t know what else to do. any ideas how to get this keys programmed????? i have 2, original and aftermarket. this is a all keys lost situation.


From one User:
Your transponder PRECODING not correct. Must show DEALER key as “YES” then it will work.
From Xhorse engineer:
When using Xhorse VVDI2 to program 2004 vw tourage with 4th generation immo, Phaeton and A8 with K-line immo. In the first step, it prompts to pull out the key and insert it again, please do not pull out the key, just close and open is okay. When learning the key, please follow the prompts to operate, when you hear the ELS/ELV unlocking sound, please insert the dealer key that is generated. It won’t have prompts like 1-2, if the dashboard is not lit, turn the key continuously. After learning complete, to try to start the car, if failed, wait the key lit the dashboard for 5 minutes and start again.

VW Audi VDO NEC 2009+ -UDS 4th IMMO Learn Key with VVDI2

Vehicle: VW Audi Seat Skoda with VDO NEC 2009+ -UDS
Purpose: All keys successfully Learned.
Tools to use:
FIGO Simulator (flamingosimulador.com)
There’s special procedure for prepare dealer key: Menu -> Key Learn. Choose specific type for 4th immobilizer system.
Lost all key-OBD prepare key:
This function will read PIN/CS from ECU (or input PIN/CS) and prepare dealer key. The dealer key can learn to car .
After run this function, it changed 6 bytes of all 12 bytes CS in immobilizer system, so the old key can’t be used anymore, and don’t accept any key come from dealer.
Support make OEM dealer key. The OEM key can do online operation. Need special transponder.





Which tool to Program VW Golf 7 All Keys Lost?

Confirmed: There is no tool on the market that can do MQB platform all key lost …..yet
only dealer + dealer key order
Works with working key only.
  1. Since VVDI2 V6.1.0 Update:
Improvement for MQB prepare dealer key.
Support change MQB key ID (support GEKO online), require use VVDI proximity remote.
VW MQB add new type: Dashboard version 0555, 0556.
Support generate MQB proximity remote: require use VVDI proximity remote and download latest remote database.
How-to’s of
  1. How to program Skoda Octavia 2015 MQB keyless go with VVDI2
  1. How to program Seat Leon MQB remote key with VVDI2 VAG?
  1. How to use VVDI2 to program new keys to VW MQB NEC35XX?
  1. Abrites diagnostics for VAG: Works with working key only.
Key programming for vehicles based on the MQB platform from 2012 onwards. The VN009 special function will allow you to program keys to those vehicles if you have a working key. You can use new keys and keys previously programmed to the particular vehicle.
Supported models:
Audi A3/S3 2014+
Audi A3 8V (2012-2014)
Audi Q2
Seat LEON 07.2014+
Seat LEON 3 5F (2012-2014)
Skoda RAPID 06.2015+
Skoda OCTAVIA 3 5E (2012-2014)
Skoda FABIA/OCTAVIA III 07.2014+
Volkswagen Crafter 2017+
Volkswagen Golf VII (2012-2014)
Volkswagen Golf 7/Polo/Tiguan II/Touran II 07.2014+
Volkswagen Passat B8
Please note: Vehicles with JCI clusters and virtual cockpits are not supported at the moment.
This special function requires an Abrites PROTAG Programmer, internet connection and an active AMS.
A new AVDI Interface or active AMS is required to purchase this special function.
Source: abrites.com

Xhorse VVDI2 V6.1.0 can change VW MQB ID

Xhorse VVDI2 new software updateV6.1.0  adding new VW MQB and FEM/BDC versions on Jan. 7th, 2018.
VVDI2 latest software version V6.1.0 update
************************************************* *********************
*** 2018-01-07
*** Require firmware V6.1.0
************************************************* *********************
===== VAG V6.1.0 =====
1. Immoprovement for MQB prepare dealer key
a). Support change MQB key ID(support GEKO online),require use VVDI proximity remote
b). Support save synchronize data when make key with working key
c). Support make dealer key with immo data and synchronize data while all key lost
2. VW MQB add new type: Dashboard version 0555, 0556
3. Immoprovement for autodetect VAG immobilizer system
4. Support some NEC24C32 TFT dashboard
5. Bugfix
===== BMW V6.1.0 =====
1. ECU /CAS ISN: Bugfix for change ISN for F series
2. FEM/BDC make key: Add new version, support car until 2018.11
3. FEM/BDC backup coding: Add new version, support car until 2018.11
4. Bugfix for MSV70 read ECU synchronize code(2 Bytes)
5. Bugfix
===== Porsche V6.1.0 =====
1. Bugfix
===== PSA V6.1.0 =====
1. Bugfix
===== Transponder Programmer V6.1.0 =====
1. Support generate MQB proximity remote: require use vvdi proximity remote and download latest remote database
2. Improvement for vvdi special transponder
3. Immobilizer data tool: Euro->BMW->motorcycle add new type
4. Immobilizer data tool: Euro->Iveco->Daily 93C56 bugfix
5. Immobilizer data tool: Asia->Isuzu->SX4 TC1762 bugfix
6. Immobilizer data tool: Asia->SAIC->Roewe750 add new type
7. Bugfix
===== Copy 48 (96 bits) V6.1.0 =====
1. Bugfix
===== J2534 V6.1.0 =====
1. Bugfix
===== Online Upate Tool V6.1.0 =====
1. Bugfix
===== Quick Start V6.1.0 =====
1. Bugfix

Program Audi S5 2010 BCM2 Smart Remote Key with VVDI2

How to: Program Smart Remote to a Audi S5 year 2010 5th generation immobilizer BCM2 with Xhorse VVDI2 key programmer.


Step 1:Read BCM2 data


Open VVDI2 software->Audi->Key Learn->5th Immobilizer system

Precedure to read BCM: choose Read by OBDII
Press Read BCM2 data (OBDII)

Insert working key into ignition and switch on before continue
If working key is already in car, take out and insret it again (also switch START/STOP button)
If lost all working keys, open the headlight, and step on the brake before continue
Disable security access level1 Success

VVDI2 read VAG number and key number


Save BCM2 data


Step 2: Check key status

Step 3: Make dealer key by BCM2 dump


Choose A4L A5 Q5 add key or lost all keys- Don’t need working key
Press Next

Press OK to load BCM2 data read from step 1

Put new key into VVDI2 VAG programmer,then continue
Start read key information, please wait

Now reprogramming key info, please wait

Start make key


Dealer key make successful


Step 4: Key Learning 

Connect with our VVDI2 device to vehicle, prepare all the key for this car. Insert one key into switch ignition,
input key number you want to learn.

Here 2 keys need to learn. Press Key Learning to continue.

Press OK to load BCM2 data read from step 1
Insert working key into igniton (or nearby ignition coil) and switch on beofre contonue.
If lost all working key, insert dealer key into ignition (or nearby ignition coil), open the headlight, and
step on the brake before continue.
Start learning key

Insert every key into ignition in turn
Once a key is learned successful, X/Y in the dashboard, X will be added 1.
If only have ignition coil, please stop and start the START/STOP button after X added 1.

1st key learned successful
Insert 2nd key to ignition switch and turn on

2nd key learned successful

All keys have been learned success

Test start ok


Test remote control ok



Xhorse VVDI2 Program Audi S5 2010 BCM2 Smart Remote Key

How to use VVDI2 VAG to Re-adapt Key Audi A7 keyless Go

As titled, here’s the test on re-adapting key on Audi A7 Keyless Go using  Xhorse VVDI2 VAG key programmer.
Insert working key into VVDI2
Open VVDI2 VAG software
Select Key Learn->5th Immobilizer system->Check key status
The current key has keyless. The key is locked.
Insert another key into VVDI2 key programmer, check key status again
The current key does not have keyless. The key is not locked.
Turn ignition switch to ON position
Read BCM2 Data (OBDII)
Insert working key into ignition and switch on before continue.
If working key is already in car, take out and insert in again (switch START/STOP button as well)
If lost all working key, open the headlight, and step on the brake before continue.
Transfer data
Save data
Connect VVDI2 with car,prepare all the key for this car.  Insert one key into switch ignition, input the key number you want to learn, Then press “Key Learning”, it requests load the BCM2 data read in step 1.
Insert every key into ignition in turn. Once a key is learned successful, X/Y in the dashboard, X will be added 1.
If only have ignition coil, please stop and start the START/STOP button after X added 1.
Insert working key into ignition or nearby ignition coil and switch on before continue.
If lost all working key, insert dealer key into ignition. Open the headlight, and step on the brake before continue
Start learning key
VVDI2 re-adapt Audi A7 keyless go success.

VVDI2 2015 Skoda Octavia MQB Mileage Correction Guide

Here’s an example of odometer (mileage) correction in the car Skoda Octavia 2015 (VAG MQB platform). The procedure is carried out with the Xhorse VVDI2 VAG key programmer.
Original mileage: 66,612KM
Open VVDI2 software
Select Key Learn->MQB platform instrument immobilizer->Instrument with NEC35xx (Continental/VDO)
Click on Diag to load vehicle information
Instrument version 2210
Instrument type: MQB NEC35xx Continental VDO
You can read eeprom and save it first.
Click on read KM
Read odometer success.
Manually enter odometer you desired
Click on Write KM
Switch ignition on with working key before press OK. If car has Keyless Go, put the working key nearly car coil and switch on.
Choose security login:  Login Method 2 (because software version of the dashboard belong to 2210)
Write data success.
Use “Reset instrument” to active instrument after all the operation is finished.
Reset success.
Check mileage on dashboard
Clear ABS fault codes with VVDI2 software

Program Skoda Octavia 2015 MQB Keyless Go with VVDI2 VAG

Here’s an example of programming a smart key in the car Skoda Octavia 2015 (MQB platform VAG) using Xhorse VVDI2 VAG key programmer.
Open VVDI2 VAG software
Select Key Learn->MQB platform instrument immobilizer->Instrument with NEC35xx (Continental/VDO)
Click on Diag to load vehicle information
Instrument version 2210
Instrument type: MQB NEC35xx Continental VDO
Read EEPROM data and save
Switch on with working key before press ok
If car has keyless Go, put the working key nearby car coil and switch on
Choose Login Method 2, the car software for dashboard belong to 2210
Press Next to continue
1. The dashboard is dark when you see this tips. You need finish all operation before reset instrument.
2.Read EEPROM and save it.
3.Read IMMO data and save it.
4. Prepare a dealer key (You can go to step 7 if have working key aslo
don’t want to add key)
5. Reset instrument
6. Add key use immo data to learn the new dealer key to car
7. Finish other customer requests.
Save eeprom
Click on Read Immo data and then save it
Select Maker Dealer Key->Skoda
If prepare normal dealer key, follow instructions below:
Here we select Prepare OEM key
Prepare OEM key: need special key or OEM key. You must provide an original key ID to prepare OEM key. The OEM key can do online operation. OEM key can start engine directly for 4th immo system.
For 5th immo system need learn again.
Select key position 3
Press Next to continue
Input original working key to VVDI2 and press OK
Input OEM key to VVDI2 key programmer and continue.
Use “Reset instrument” to active instrument after all the operation is finished.
Click on Add key
Select Learn key, login with security code from immo data. Put the key into ignition switch on accord flowing tips. You must prepare all the working key.
Select key number to learn: 2
Press Next
Confirm car has keyless.
Put the dealer key nearby car ignition switch and switch ON dashboard before continue
First key learn succeed
Learn second key with VVDI2
Test the remote control and start car.

VVDI2 Golf 5 EDC16U1 K-line Data Upload Failed Solution

Hi, I have with Xhorse vvdi2 vag v5.5.0 problems with edc16u1 ecu and dashboard.
It can’t read golf 5 2005 year. Something not ok with it
It looks like K line not working.
picture attached:
Error “Can’t connect to device. Switch ignition OFF/ON and retry”
Error “Non-standard upload data failed”
Here’s the customer solution:
I test it this morning and all works fine now.
I removed soldering ball and i reinstall drivers and all working fine.
It reads now over kline it detects edc16 ecus and it read immo data eeprom and also dashboard it can read now.
I check k line from vvdi2 db25 connector on PCB to the optocupler (relay) omron, and from it to the ADG1606B multiplexer then from multiplexer to the L9637 interface. Then from it to the mcu Rx and TX line. All is ok. Even replace from vvdi 1 L9637 ISO 9141 interface. Didn’t work. Then I measured supply to the omron optocoupler relay it has 1.2 v when activate Kline communication. Check also 120ohm pull down resistors, check supply to the multiplexer ADG1606B it is ok 3.3v ako also on iso 9141(L9637) interface, and also I have on oscilloscope TX and TX signals from mcu to the L9637 it send data when It activate Kline. And in the end I found one solder ball between legs of multiplexer. You can see it on picture that I send you before. First time i open it. That was the main problem and USB drivers.
this is all i tested on this interface. Now all is fine and i can work now 😉
Interface is very high quality production, but this is something that happens from time to time.
Hope this helps.