skodapilot Forum

Hi everyone,

When you use the fonction "Export IMMO area", what VDOeditor export?

Is include the odometer/milage?

Is include the keys?

Thanks in advance!

Bob

VDOeditor copy segment of EEPROM contained crypted IMMO data "as is" from loaded dump to selected dump.
Import is mirror function and copy segment from some dump on disk to loaded dump.
This option was designed to simplify firmware update routines, because this option is working with the same cluster only and could no be used to transfer data between different dashboards.

Thanks Anton,

But this section include immo data (MAC, CS, PIN, etc...), and keys?

Yes, sure, due to data is encrypted we can transfer all or nothing.

Tapatalk

Thanks for your reply.

And you said, that is not possible to transfert the IMMO Data section in another cluster (26C64 --> 24c64)?

If not, who maid the encryption? the ECU?

Thanks in advance!

00Bob wrote: ↑28 Jan 2021 19:19 And you said, that is not possible to transfert the IMMO Data section in another cluster (26C64 --> 24c64)?
If not, who maid the encryption? the ECU?

Yes, keys are stored in MCU flash and unique

Thanks Anton!

I'd like to know if the "component protection" data that is used on Euro6 vehicles such as 2016+ Caddy and T6+ Transporter is held in the EEPROM and if it will be possible to export/transfer that to other clusters for upgrades/swaps.

droid wrote: ↑12 Feb 2022 01:54 I'd like to know if the "component security" data that is used on Euro6 vehicles such as 2016+ Caddy and T6+ Transporter is held in the EEPROM and if it will be possible to export/transfer that to other clusters for upgrades/swaps.

At least CP is part of IMMO data field. I don't know is there any additional info are stored outside of immo area

CP info is more or less only the VIN number of the car. In adaptations of the cluster there is a possibility to activate CP for Radio and for Navigation.
CP is only checking if VIN number matches with VIN in radio and in a third component, like CMM