Problem 1:
Halle, I need help, I tried to read the tacho with godiag via vvdi keytool plus, during the process, the part completely went off, now it doesn’t work anymore, also not on the vehicle, what could be broken, you can see, it’s not burned or something else strange, if anyone can help me
it is a Transporter T6, 7E0920870S or 7E0920880L
Problem 2:
Working on Transporter 2019 key lost
I use VVDI2 + Pogo cable but cannot recognise dash with 24C64
I use every type with 24C64 all failed identifie this dash
Working on the Transporter T5 2020 follow owner said, I use VVDi2 + Pogo cable but VVDI cannot identified this dash 7E0920861A.
Inside has 24C64, so i use every option of NEC + 24C64 still not recognised.
Does someone have this problem? Or VVdi still not support?
The very last software of the PQ/UDS immo4 platform are not supported by anyone yet. Those clusters are much like MQB where you need the key from the NEC to decrypt the immo data but because they’re not a common passenger vehicle the aftermarket tool suppliers haven’t shown interest in working on this oddball combination.
this car use Megamos AES not standard ID48
for SW2030 , the Best and safe way is to buy immo-data for this model ( not expensive).
The very last software of the PQ/UDS immo4 platform are not supported by anyone yet. Those clusters are much like MQB where you need the key from the NEC to decrypt the immo data but because they’re not a common passenger vehicle the aftermarket tool suppliers haven’t shown interest in working on this oddball combination.
Xhorse can do that easy
read cpu over Multiprog
load to vvdi2 to decode that and get Skey
and then login to cluster over Skey
already did SW 2050 and 3030
I see this T6 with AES key did by VVDI2
His T6 dash is ealier than mine. VVDI recognise dash version and also did remote by Xhorse key.
