Question: I am ready to order the xhorse MQB nec35xx license for vvdi2. Is this option Ok for Odometer correction. Sync data also needed for odometer? or just for the Immo part.
Answer:
MQB license works for odometer as well.
Sync data is just for IMMO of course. Sync data is for dealer key generation.
The whole dump is encrypted and the processors are locked. But for odometer you don’t need sync data. The servers of VVDI/AVDI and the other tools decrypt the dash/immo data but they cannot get the sync data which is only stored in the working key.
So currently you have one option to get the SYNC data (when key is missing) – use paid service to get it from VAG server. Soon there may be a second option – to generate the SYNC yourself by reading all the computer modules in the car (ECU, DASH, ELV, Transmission…) but for the moment there’s no tool which can read the ELV if fitted.
Xhorse MQB mileage correction review:
1). Today did Skoda Octavia 2016 with MQB Visteon 5E0920781B dash D70F3529 MCU. Read, Write, ZERO issues.
Where can i find pinouts to read bsi valeo psa with xhorse vvdi prog and which eeprom?
EEPROM:
912dg128A Motorola
Pinout to vvdi prog
Xhorse VVDI PROG + VVDI2 is able to read & decrypt 2016 Volkswagen Polo MQB locked D70F35xx immo data on bench. Need to activate VAG MQB48 License and disassemble MQB module from vehicle for pin lifting.
Following are the quick steps.
Step1. Read Data via VVDI PROG
Lift FVDD PIN from PCB according wiring diagram
Connect MQB board to VVDI PROG for reading.
Save the immo data file.
Step2. Decrypt Locked Data via VVDI2
Connect MQB board to VVDI2.
VW >> Key Learn >> MQB platform instrument immobilizer >> instrument with locked NEC35xx(MQB48, VDO/JCI) >> Load file >> Decode immodata >> Yes >> Selected immo data file read by VVDI PROG
Server calculating, please wait…
Press “OK” to save immo data file.
As we can see, immo data like VIN, CS, PIN, MAC & keys have been read out. It’s unlocked now and can be used for key adding or all keys lost.
Problem:
Did a 2008 VW Passat all keys lost using xhorse vvdi2 and vvdi prog.
Read EEPROM out of circuit, found 7th Byte, Generated Dealer Key.
Follow the instruction here
http://blog.vvdishop.com/program-vw-passat-2011-all-keys-lost-with-vvdi-prog-and-vvdi2/
My question is do I need to write back file?
When I finished making dealer key it says “Key Make Okay and Locked”
but doesn’t give option to save new file.
Not sure of The process I did to make dealer key is taking up a slot or just made a copy of existing key?
Any help?
Solution:
Can do either
No writing file back reinstall to car and learn by obd. With vvdi you could even clone from existing dump reinstall and will just start.
Load dump into transponder programming on first screen before selecting VW.
Choose an existing slot and make dealer key. (just copy working key from existing slot.), then no need to write back if use existing slot need vvdi super chip.
Megamos chips do not write back. Such as 48 and 13.
You just read file and match with the chips. Same procedure for Volvo, Honda with 13 chips, Volkswagen,audi and all others.
An Opel Movano 2016 body control unit BCM N3 had water damage earlier. We need to clone BCM to this unit with xhorse vvdi prog.
Found the connection diagram on google for this BCM.
Connect BCM with vvdi prog follow the wiring diagram
In VVDI Prog software, select MCU->Renesas-V850->D70F3376A
Read Dflash
Make sure you have backup config, d-flash and p-flash files.
Everything is in the flash. Write p-flash.
Open original p-flash
Write flash.
If failed to read D70F3376A processor, try solution here
Xhorse VVDI Prog Opel Movano BCM2 D70F3376A Try Frequency Failed Solution