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.

Will CGDI MB or VVDI MB Program Mercedes FBS4 keys

What users think of CGDI Prog programmer and VVDI MB tool regarding Mercedes FBS4 key programming.

Real opinions from users:

User 1:
the difference between CGDI and VVDI in FBS4 is as follows:
On one hand,
CGDI MB can read FBS4 keys and knows if its in a working status or key is damaged;
CGDI can read EIS FBS4 and knows if it working or not working; however, VVDI can not Detect FBS4 .

On the other hand,
CGDI never claimed that it can make calculation for FBS4 . Only Read to know the status. Out of the subject No one was Born knowing everything at one point we all asked for questions to know.

User 2:
Both CGDI and Vvdi MB are a great comprehensive solution comparing to what else is available out there.
In my opinion they’re the two best for keys maybe along with Diagspeed but much far ahead than AVDI (for keys).

User 3:
with 655$ i earned 11000€ with cgdi !!! Well with vvdi always must to pay extra to make akl and one more thing ,, the server is very old on vvdi and sometimes have problems like cgdi !!!
So conclusion is only one !!! 655$ comparing with 2000$ its very big difference !!!

User 4:
Both tools are good ,but people don’t know how to use it at full capacity!

User 5:
i read somewhere that cgdi mb tool can make it and it is much cheaper tool from xhorse vvdi mb tool !!

Fbs4 it can read eis ID via obd and read key via IR but that’s it, can’t make a new key or calculate anything.

User 6:
The main difference between cgdi mb and vvdi mb is that, on old Mercedes, cgdi mb is able to OBD program a new key while you have to disassemble EIS to add a new key with vvdi mb tool. That is why you should have a cgdi programmer for mb.

With VVDI MB Tool, you should buy Vvdi prog too, because the are some eis and ecu’s that you cant do with MB Tool independently. For example some w210 eis or Sprinter 906. You should have both, VVDI MB Tool and VVDI prog. Or, if you have to buy some tool again, Simon Touch is the best, but its more expensive.

But if you have a CGDI MB, you have a chance to program a new key through OBD. All done with a tool. That’s the reason why I bought it.

Look here: CGDI MB key programmer read FBS4 key data successfully!

cgdi-mb-fbs4-key-1 cgdi-mb-fbs4-key-2

So there is no tool can do FBS4 key?

No.  With genuine xentry and daimler fbs server.  Makes FBS4 every day via OBD very fast and easy.

Diagspeed announced the dates of FBS4 solution. But not confirmed yet. The Diagspeed has the reputation of being the best in the Mercedes world to make keys, Reset ECU’s and trouble shoot problems that a normal scan tool can not.  It is worth to take a gamble.

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)