How to Program Grand Cherokee 2000 Key with VVDI2

How-to: Program Jeep Grand Cherokee 2000 immo key when all keys lost using Xhorse VVDI Prog and VVDI2 key programmer.

Step 1: Read mcu data 

Disassemble IMMO Box and desolder IC chip MC68HC908 with a hot gun

Solder MC68HC chip to VVDIProg HC058x programming adapter following wiring diagram

In VVDI Prog software

select Type 2 MCU->Motorola-MC68HC(9)08->HC08A232_EEP_SECURED

Read and save dump data, i.e jeep 2000.bin

Step 2: Make dealer key

Open VVDI2 software, select Transponder Programmer->Immobilizer Data Tool

Select vehicle information and load eeprom dump just saved

USA-Jeep->Grand Cherokee->1999-hc68hc08

Select an unused key position and press Make Dealer Key

Insert new transponder into VVDI2 key programmer

Prepare dealer key success. It can start engine after write back new dump file or learn it to car.

Save new key dump file

Step 3: Write back new dump

Open VVDI Prog software

Open new key dump file

Press Write

Write data success

Reinstall the immo box back to vehicle.

Now the new key can start vehicle.

www.vvdishop.com

http://www.vvdishop.com/service/program-grand-cherokee-2000-all-keys-lost-with-vvdi-prog-vvdi2-9086.html

LKP-02 Clonable Transponders & VVDI Key-Tool Compatibility

Here we test and look at LKP-02 clonable/programmable transponders and Xhorse VVDI Key Toolcompatibility.

Note:

LKP-02 supports 4D-60/61/62/63(40bit/80bit)/64(4E), Chrysler/65/66/67/68/69/70/70E, 4C,Toyota G chip

This chip can be used to either generate new transponders with the Tango or to clone original keys.

Transponder Clone 4D

Generate Transponder (Toyota G chip), success

Generate transponder Toyota ID67 All using TIRIS 4D-67

no problem

Special Functions (Special 4D to 4C)

Transform the Xhorse 4D transponder to ID-4C, without issue

Will test and report more

www.vvdishop.com

http://blog.vvdishop.com/lkp-02-clonable-transponder-chip-vvdi-key-tool/

Xhorse Condor Mini Series Number KM03 vs. KM02

This is for your information. It’s different between Xhorse Condor XC-Mini key cutting machine KM02xx and KM03xx series

What is the difference between KM02xx and KM03xx series ?

The difference is:
motherboard, driver board, touch screen and add a fan near power.
KM03xx supports Bluetooth function.

Btw, you can activate Bluetooth on Laptop/Tablet or Smartphone and press the “search for machine” button in Instacode and it will pair with Condor Mini.

How do you know your machine is KM02 or KM03?

Mate,turn on the machine you will find machine SN and software version in main-interface.

Where to get KM03 with Bluetooth?

Here you go. http://www.vvdishop.com/wholesale/xhorse-condor-xc-mini-plus-key-cutting-machine.html

Condor Mini KM03 test report:

Today tried to cut HU55P, cutter started to the other direction and cut into the jaw

I cut some HU64 and never had a problem with it.

100% hu64 is ok with condor xc007 and condor mini km03 tested by me many times…

I used it to cut HU100. Worked like a charm!!!

HU66, HU49, HU83 cutting OK.

Recently got the Condor Mini.

Seems good. However if the dust cover could have been designed a bit away from key it would’ve been nice.

I haven’t no any problems with Condor XC-Mini

cut keys blade HU64-3 without any problems

Just got a new km03 from vvdishop.com. So very new to this. Been very successful up till now. Tried to decode a Renault megane emergency key Card type. Renault-megane-2003- Condor checks the clamp position ok then goes looking for the tip of the key but misses the tip with the prob going down the middle of the cut for 5mm then backs off as it thinks no key is in the clamp. Is it operator error or a bug. Look like the probe is not low enough to bump into the key tip. Other than this I’m very happy.

Condor KM02 feedback:

I have machine with SN starting with KM02.

To cut keys HU92 BMW need to be in 1.00MM, when you select HU92 the device will ask you to chose between Land ravor and BMW, Land Rover came with 1.00mm and BMW with 1.25mm, if you try to cut with 1.25mm the key will not turn.

I have proved with 4 different machines and 3 different cars.

http://www.vvdishop.com/service/xhorse-condor-xc-mini-series-km03-vs-km02-9085.html

Xhorse VVDI2 V6.1.0 adds MQB and FEM versions

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

Free Download VVDI2 Software V6.1.0
https://mega.nz/#!2sxmDYCT!VXl3Dj4lgCsYr4vTLrJOfbOiGZ5DGyjTtr-ve8WdlZ8

VAG OBD Helper Read Audi A1 2013 4th IMMO Data

Test report from Argentine locksmith Mr.Korenfeld: read/backup IMMO4 BCM NEC24C64 data of Audi A1 2013 using VAG OBD helper and add new key with other programmer, all done via OBD.

Step 1: Read IMMO data with vag helper

Connect vag helper cable with laptop and vehicle

Token is required to calculate data

Read Car information

Calculate success

IMMO4 NEC24C64 data auto saved in vag obd software folder

Step 2: You can prepare new dealer key and learn key with this immo data in other IMMO device. i.e VVDI2, Lonsdor K518, SMOK etc.

Here’s add key/all keys lost example:

How to use VAG OBD Helper and VVDI2 to make VAG IMMO4 key via OBD

http://blog.vvdishop.com/vag-obd-helper-read-audi-a1-2013-immo4-data-success/