topblog Ivoire blogs


Guide to program Hyundai vvdi remote key with Xhorse VVDI2

Hyundai remote key programming successfully! With Xhorse VVDI2 key programmer.


Tools preparation:

Vvdi tools (Xhorse VVDI2)


A new vvdi remote key and the original Hyundai key


Here are the remote generation steps...


Step 1 - chip information collection via VVDI2 xhorse

Install the battery for the new wirless remote key

- take out the pcb on the remote controller

- install the battery


vvdi2-vvdi-key-tool-program-hyundai-remote-1 vvdi2-vvdi-key-tool-program-hyundai-remote-2

Generate wireless universal remote into chip signal collector via VVDI2 v1.2.2 software; VVDI2 automatically detect the chip





Press the remote control buttons and the LED will keep flashing (it means that: it’s coming into the collection status)


Signal acquisition is successful when the LED flashes rapidly





Information collection is complete. Now, ready for decoding and chip copy.




Step 2 - chip decoding and copy by vvdi2 v1.2.2

Put the chip with a battery installed into the remote control


Put the original car key into VVDI2 device for identification


Click on Start copy in VVDI2 interface


To collect information in the car and put the collector into VVDI2 (because we have been collecting data, it’s ok to put the collector into vvdi2)



Put the original key into vvdi2 key programmer again

Connect to the network, to begin decoding online


Chip decoding success!


Put the the the collector (vvdi remote key) into vvdi2

Chip copy success



Step 3 - remote control generation 

Try to start the car with the new copied key, after chip copy success

It can start the car but the remote cannot work properly




Ready to generate remote control

Use vvdi2 control generating function to generate the remote control

Put the new key into vvdi2 programmer

Finish vehicle info selection and click on Generate Remote Control




Use special equipment to program the remote


Xhorse wireless universal remote can copy a chip after regeneration as remote control, in the new equipment is the vvdi key tool (will add this function)


This article is from :



How to update kess v2 2..8 software

This software update program can use in :SE87:KESS V2 OBD2 manager tuning kitSE87-C: Kess v2 4.036 firmwareSE87-E: Kess v2 3.099 firmwareSE87-K: KESS V2 Truck versionSE87-CK: V4.036 Truck KESS V2
Kess v2 2.25/2.28 installation steps:

Step 1 – install K-Suite v2.25

Run K suite software and install K-Suite 2.25


Accept the license agreement

Select installation language to go on


Install usb driver


always click on Next until installation completes


Ksuite installation success.

Ksuite language: English, German, Spanish, Italian, Portuguese, French


Step 2 – disable network

Disable all network connection


Step 3 – setup Ksuite properties

Go to Ksuite properties

Click on Find targets, then delete the “help” folder in C:Ksuite

Copy another “help” folder in disk E: to C:Ksuite

Close all windows


Step 4 – install & setup software for USB device

Select install USB device software automatically

After finishing the installation, go to Computer management

Select USB device


Step 5 – Ksuite v2.25 read BMW E90 ecu

Run KSUITE on desktop

It’s Kess v2 ksuite v2.25


Here we test Kess v2 on BMW E90 MED17/MEV17 ECU reading


software-and-install-k-suite-2-259 software-and-install-k-suite-2-2510 software-and-install-k-suite-2-2511 software-and-install-k-suite-2-2512 software-and-install-k-suite-2-2513 software-and-install-k-suite-2-2514 software-and-install-k-suite-2-2515 software-and-install-k-suite-2-2516 software-and-install-k-suite-2-2518 software-and-install-k-suite-2-2519 software-and-install-k-suite-2-2520 software-and-install-k-suite-2-2521

BMW e90 reading ecu OK. Save data.


Step 6 – setup Ksuite v2.28

Delete “Setup 2.25” on Desktop

Again, open Ksuite properties

Click on Find targets,then delete all files in C:Ksuite except the “help” folder

Copy all files in the Ksuite 2.28 zip file to C:Ksuite

Delete the Ksuite 2.28 zip file

Then open K-suite app on Desktop

It’s ksuite 2.28 version now


Ksuite 2.28 can read BMW e90 ecu id like Ksuite 2.25 above




Lexia 3 DiagBox v7.76 v7.77 Language Change

It’s a customer share of changing language in DiagBox, Lexia and PP2000. The user has tested on v7.76 and v7.77, and this is how to do it:


This is for educational and experimental use, and I hold no responsibility for any improper usage or damage to your system..

For DiagBox 7.76 / 7.77:
1- Open the File Explorer and navigate to “C:AWRootdtrdtrans”, find the file “Language.ini” and create a copy “”.
Open the file Language.ini and under [LANGUAGE], change “Current=en_GB” to “Current=fr_FR” and save (I commented the original and added the new line to change from English to French).


For Lexia 3:
2a- Navigate to “C:APPLEXIAEXE” find the file “langue.ini” and create a copy “”.
Open the file “langue.ini” and under [DicoMap], change all “%LG%” to FR (I commented the original 4 lines and added changed 4 lines to activate French language).


2b- Navigate to “C:APPLICLCTLEX3”, find the file “Dico.txt” and create a copy named “”.
Open the file “Dico.txt” and change the line “Dico=THELEXGB.DBZ” to “Dico=THELEXFR.DBZ” to change Lexia language to French.

For PP2000:
3- If you wish to change PP2000, Navigate to “C:APPOutilRepexe”, find the file “Dico.txt” and create a copy named “”. Open the file “Dico.txt” and change the line “Dico=THESAUFR.DBZ” to “Dico=THESAUGB.DBZ” to change to English,

The language change is achieved by replacing the “**” in “Dico=THESAU**.DBZ” with 2 letters representing the language you want, you can choose any of the 20 available languages.

Please notice that English=GB, French=FR and German=AL (French naming not unicode).

There are other incidents of “en_GB” that I changed to “fr_FR” in my installation. But I think the above is enough to get you working, you can find them in the INI and few java files….

Language table added
You can also use the attached Country Codes table to change the codes in your system, example for English:
Codes for DiagBox (DBX) go into C:AWroot…. in (2 Chrs.) statements such as “LauncherEN.DBZ” or (5 Chrs.) statements such as “Current=en_GB”
Codes for Lexia / PP200 go into C:APP… in statements such as “Dico=thesauGB.dbz” (in file Dico.txt)…

Please notice that you can have DiagBoX, Lexia and PP2000 eaxh working in a different language…

PP2000 Language fall back and font sizing
Also, for PP2000, the statement in C:APPOUTILREPEXELANGUE.INI:
will determine the language used in case you choose an unsupported language (or missing language files). In this case you may also add the statement Arial=10 (or any font size that you may prefer) like below.

p.s. Simple trick, if you wish to play with the font size, change the statement in Dico.TXT “Dico=thesauGB.dbz” to “Dico=thesau.dbz”, this will force the system to use the backup language of your choice with the Arial fonts you decided… I tried it for PP2000, and it works.

Lexia resizing and screen positioning
And since I am at it, you can also position and resize Lexia on the screen to your liking by navigation to:
C:APPLEXIAEXE and finding the file: “ecran.ini”.. open it using notepad and under:
position_X =0
position_Y =0
largeur_ecran = 1024
hauteur_ecran = 748

I think it is self explanatory, the X and Y affect positioning on the screen (from top left), and the ones I cant read are the Width and Height in pixels…; Try position_X =200 and position_Y=100, largeur_ecran = 800 and hauteur_ecran = 600.

Enjoy the Multilingual version of DiagBox 7.xx and feel free to share this information with reference..

The issue with Language button in DiagBox v7.74+ is sorted (Photo below).


1-8lexia-diagbox-language-setup-1 lexia-diagbox-language-setup-2 lexia-diagbox-language-setup-3 lexia-diagbox-language-setup-4 lexia-diagbox-language-setup-5 lexia-diagbox-language-setup-6 lexia-diagbox-language-setup-7 lexia-diagbox-language-setup-8



Exaggerated examples for demonstration purposes:

1: Lexia, editing ecran.ini values to:
position_X =256 for the first photo and 96 for the 2nd
position_Y =96 for the first photo and 32 for the 2nd
largeur_ecran = 800 for the first photo and 1200 for the 2nd
hauteur_ecran = 600 for the first photo and 700 for the 2nd

2: Lexia PP2000, editing the values:
Dico.txt –> Dico=THESAU**.DBZ
Langue.ini –> Arial=24

I have also attached a snapshot for PP2000 in Arabic and Hebrew… Both languages are RTL (Right To Left) scripting. Regrettably I don’t have the DBZ and DU8 files for them

diagbox-language-1 diagbox-language-2 diagbox-language-3 diagbox-language-4 diagbox-language-5