VVDI 2 new tool arrived

[balakovo]

he is not declared there. I'm talking about autel

[ASCM]

Hello does anyone tried to program transponder for kavasaki Moto with vvdi 2

Sent from my 5033F using Tapatalk

[daxxer]

Hello does anyone tried to program transponder for kavasaki Moto with vvdi 2

Sent from my 5033F using Tapatalk

test copy/clone 4D chip of kawa, work ok with superchip

[autoTkey]

I couldn't complete a Caddy 2017 PQ add key job with AES transponder.
VVDI2 acts as it has some bug. It is also very possible that I didn't use VVDI2 correctly but X300 OBDSTAR also could finish it.

Car has one working key MQB 48 and VVDI2 detects as "NEC+24C64 2014.06-". I read and backup EEPROM and IMMO and move on to make the OEM Dealer key. When I check working key position it detects it as "FFFFFFFC" and says it's not from this car. I read it in other device and compare the ID and select the other one but then VVDI2 returns another odd message - "Failed to set OEM key ID! Make sure the input key is not locked!". I used XSMQB1EN and generated it with few different MQB options from Key Tool software but never got to pass these messages. I also tried to make normal Dealer key but got the same message when tried to do it.
What did I do wrong?

[comizelu]

I couldn't complete a Caddy 2017 PQ add key job with AES transponder.
VVDI2 acts as it has some bug. It is also very possible that I didn't use VVDI2 correctly but X300 OBDSTAR also could finish it.

Car has one working key MQB 48 and VVDI2 detects as "NEC+24C64 2014.06-". I read and backup EEPROM and IMMO and move on to make the OEM Dealer key. When I check working key position it detects it as "FFFFFFFC" and says it's not from this car. I read it in other device and compare the ID and select the other one but then VVDI2 returns another odd message - "Failed to set OEM key ID! Make sure the input key is not locked!". I used XSMQB1EN and generated it with few different MQB options from Key Tool software but never got to pass these messages. I also tried to make normal Dealer key but got the same message when tried to do it.
What did I do wrong?

User fault!

Sent from my MI CC9 Pro Premium Edition using Tapatalk

[autoTkey]

Got it, I'm an idiot ...

Edit: Yep - client just returned to finish the job. I actually used the IMMO dump from the other day to generate the OEM dealer key before he arrived. Car started straight on with it. No any additional programming was required (except for adding of the remote).

I'm curious - what other cars have this modification? I know already about Caddy, Transporter, Jetta, Sharan, Alhambra ... any other?

[ASCM]

test copy/clone 4D chip of kawa, work ok with superchip

It's all key lost situation

Sent from my 5033F using Tapatalk

[dimet]

New update

[nemena]

But how do you update? Using the update tool, seems to be updating, but all versions stay the same.

[dimet]

But how do you update? Using the update tool, seems to be updating, but all versions stay the same.

https://www.xhorsevvdi.com/info/free...are-12141.html

[ASCM]

Hello does anyone tried to program transponder for kavasaki Moto with vvdi 2

Sent from my 5033F using Tapatalk

tested not work

[qwojtus]

Land rover, generate a key without write the dump to the KVM.
First key: Remote ok, but " no key detected" - most of the time.
Second key: Start ok, but no remote at all. Actually give up.

[ASCM]

Land rover, generate a key without write the dump to the KVM.
First key: Remote ok, but " no key detected" - most of the time.
Second key: Start ok, but no remote at all. Actually give up.

Which version of Landrover it is?

Sent from my 5033F using Tapatalk

[lion0304]

Which version of Landrover it is?

Sent from my 5033F using Tapatalk

From 2015 - 2018

[ASCM]

From 2015 - 2018

You need to write generated data to KVM after that need to add by obd second remote

Sent from my 5033F using Tapatalk