How to use VVDI2 for Audi A6 4F all key lost

Post starts with this question: I have Audi A6 4F bought as dead car because it does not react to the inserted key. Immo shows NOK key inserted. I bought xprog recently and I need to advice what should I buy more to be able to create or adapt the key I got. Unfortunately it’s just my hobby so I have to purchase the clone versions. Is Tango clone solution for my problem or FVDI? I don’t want like to give it to dealer as I am glad to learn new tools and things.
Solution: VVDI2 commander
Vvdi2 can easily do it.done one of these in 20mins akl, without dismantling anything,using vvdi2.
If you don’t want to spend money for tools you can’t do the jobs so you loose money.
***If it’s just a hobby, no need to buy expensive tools… just pay a professional to do the job

Here comes the procedure of VVDI2 programs Audi A6 4F all key lost:
Remove engine from Audi a6l 2.4
vvdi2-for-audi-a6-4f-all-key-lost-01
Open Engine cover, find out the Engine position, disassemble engine.
vvdi2-for-audi-a6-4f-all-key-lost-02
Remove the engine ECU
vvdi2-for-audi-a6-4f-all-key-lost-03
Take apart engine ECU.
Next is to read this 95320 chip.
Remove 95320 chip and put it on the VVDI pro to read data.
vvdi2-for-audi-a6-4f-all-key-lost-04
vvdi2-for-audi-a6-4f-all-key-lost-05
Open VVDI pro
Select type, manufacture and model
Click “New”
Click “Read”
Successfully Read out data, click “Save”.
Take out chip from VVDI Pro and desoder the chip back to the engine ECU.
vvdi2-for-audi-a6-4f-all-key-lost-06
vvdi2-for-audi-a6-4f-all-key-lost-07
Reinstall engine ECU back to the Audi.
Open VVDI2 and click “Audi” option.
vvdi2-for-audi-a6-4f-all-key-lost-08
Select “Special function”
Select “EEPROM data processing tool”
vvdi2-for-audi-a6-4f-all-key-lost-09
Firstly calculate CS code
Select “ECU Simons PPDIX – Reset component protection data”
vvdi2-for-audi-a6-4f-all-key-lost-10
Click “Load” the load the data that read out just now, then click open.
This is CS code, take a picture to record it.
vvdi2-for-audi-a6-4f-all-key-lost-11
Next is to calculate it’s PIN code
Select “ECU Simons PPDIX – Security Access Code”
vvdi2-for-audi-a6-4f-all-key-lost-12
Click “Load” again to load the file.
vvdi2-for-audi-a6-4f-all-key-lost-13
The first step is prepared well.
Open VVDI2, click “Learning Key”- “Audi A6/Q7” Option.
Input the CS and PIN code that read out by VVDI pro, then you will see the button “Learning Key” and “Generate dealer key” are enabled.
Put OEM chip and 8E chip into VVDI2 key programmer.
Click “Generate dealer key”
Generate dealer key is done.
Next is to learning key
Disconnect the short insurance line.
vvdi2-for-audi-a6-4f-all-key-lost-14
Connect back
Take out the chip from VVDI2 and put it into ignition data coil.
vvdi2-for-audi-a6-4f-all-key-lost-15

Click “Learning Key”
Open and close car door, turn on ignition, press down brake.
Click “Learning Key”.
learning successfully.
Next is to read out EZS-KESSY(J518)EEPROM.
Click “ok”, select Chip type 9S1201128, the aim to read EZS-KESSY(J518)EEPROM is to generate OEM remote control.
Save EZS-KESSY(J518)EEPROM.
Generate OEM remote control.
Vertical put remote controller on the coil of VVDI2.
Click “Open”
Following the prompt the put the remote controller, click “Next”
Controller is generated successfully, assembled key and to test.
Test the key whether it can start the A6L.
The car can start.
Prepare to test Remote control.
Remote control is working.

Done.

VVDI Keytool remote cloning Fixed code cloning vs Special cloning

Look here: In remote cloning with Xhorse VVDI Key Tool what’s the difference between Fixed Code & Special Clone?

remote cloning

remote cloning includes hcs/fixed code cloning, non-hcs rolling code cloning and remote editing function

hcs/fixed code cloning:

support common fixed code cloning PT22XX, LX918, HT6P20, etc.

support hundreds of vehicle and garage hcs rolling code remote cloning and generating. generated remote should be re-programmed to received to receiver box

support all xhorse universal remote serials

non-hcs rolling code cloning:

support all fixed code remote cloning

support partial special vehicle models (such as Hornor) remote cloning without repeated code

support partial vehicle non-repeated code hcs type remote direct cloning

* this type only support cloning by xhorse universal wired remote series

remote editing:

support editing PT22XX, LX918, HT6P20, VD5029, AX5326, HT12X, etc.

common fixed code format data and use xhorse universal remote to emulate

support all xhorse universal remote series

vvdi-key-tool-remote-cloning-1 vvdi-key-tool-remote-cloning-2 vvdi-key-tool-remote-cloning-3

VVDI2 MQB Experience VW Tiguan and Audi A3 2015 – Success!

Xhorse VVDI2 experience :
Yesterday I added key successful on VW TIGUAN MQB (2015)
1)read & save eeprom
2)read &save immo data
3) make dealer key
4) reset…..
5) add key :
a) method 1
b) give ignition with each key
6) reset
WORK DONE on 15 minutes

VW-Tiguan-and-Audi-A3-2015

Another test: I also did a Audi A3 65 plate 2015, MQB add remote key same procedure. With needles not virtual dash.

VVDI2 and MQB question and answers:

How can i save the immo data ?
Where is the save immo data button ?
the same button when you save eeprom data
When you read immo data just click on save file … Like save eeprom data
Was the meter with needle or cetais electronic tablet style?
with needle
so you had to pull needles to read eeprom? and why eeprom was it?
no FREIND all was done via OBD and eeprom was 24xxx

24c64 or 24c32
NEC+ 24C64
Not mqb
correct, VW Tiguan is only MQB from 2016+ (second generation)