VOLVO V50 2010 CEM IMMO KEY From CEM-TYPE3-MC9S12XDT256 EEPROM/FLASH.bin

Gemini said:

Then I would not add the VIN manually to that EEPROM either. If VDASH gives the same “cannot read VIN / cannot save to account” type error, it is probably not recognizing the file format/layout it expects, not simply missing a visible VIN string.

What is visible so far:

• The uploaded ECU flash is a SID803 2 MB file with ID 5WS40562A-T.
• The VIN is not clearly readable in the flash scan; it was only visible reversed in the file name.
• The immo/sync data can be in EEPROM/secure area, but it is not something to patch by typing VIN text into the file.

For the CEM↔ECM sync repair, the important set is usually:

• CEM flash
• CEM EEPROM / secure data
• ECM/SID803 flash
• ECM/SID803 EEPROM if available

If VDASH will not import them, Mechanior or another SID803/P1 sync tool can still work from the raw dumps, but the files need to be the correct raw reads.

Please post the exact VDASH error screenshot and confirm which EEPROM file you mean:

• CEM chip 10 EEPROM / secure data?
• ECU/SID803 EEPROM?
• File size in bytes?
• Read by Autel IM608 Pro 2 from which menu?

Do not write any “VIN-added” EEPROM back until the checksum/layout is confirmed.

Click to expand...

Franks_int said:

Ok,
''Your file 'CEM-TYPE3-MC9S12XDT256-EEPROM-chip10.bin' was decoded.
VIN: UNKNOWN_VIN''
And this...

Click to expand...

CEM-TYPE3-MC9S12XDT256-EEPROM-chip10.bin decoded
VIN: UNKNOWN_VIN

CEM-TYPE3-MC9S12XDT256-FLASH-chip-10.bin decoded
VIN: YV1MW7551A2560339

• CEM FLASH = VIN / CEM identity
• CEM EEPROM chip10 / secure data = immobilizer/security data
• SID803 ECU flash = ECM side for sync

Gemini said:

Ok, good — that result is actually normal enough.

If VDASH says:

Code:

CEM-TYPE3-MC9S12XDT256-EEPROM-chip10.bin decoded
VIN: UNKNOWN_VIN

but on the flash says:

Code:

CEM-TYPE3-MC9S12XDT256-FLASH-chip-10.bin decoded
VIN: YV1MW7551A2560339

then the VIN is not missing from the CEM set. It is being read from the CEM flash. The EEPROM/secure data file simply does not expose the VIN in the way VDASH displays it.

So I would still not modify/add VIN manually to the EEPROM.

For the sync job, try to use the files as a matched set:

• CEM FLASH = VIN / CEM identity
• CEM EEPROM chip10 / secure data = immobilizer/security data
• SID803 ECU flash = ECM side for sync

If VDASH refuses to save only because the EEPROM says UNKNOWN_VIN, then the problem is likely the VDASH import workflow — it wants the CEM flash loaded together/first, not EEPROM alone.

Next thing to check: when VDASH decodes the EEPROM, does it show any CEM PIN / IMMO PIN / fixed key / security key value, or only VIN: UNKNOWN_VIN? If you can post that VDASH decode screenshot/output, we can see whether it actually extracted the useful immo data.

Click to expand...

Franks_int said:

nope
Your file 'YV1MW7551A2560339-SID803-5WS40562A-T.bin' was decoded.
VIN: UNKNOWN_VIN

well any i...

Click to expand...

28 20 71 01 50 20

• Search text/ANSI:
  Code:

  YV1MW7551A2560339

• Search text/ANSI reversed:
  Code:

  9330652A1557WM1VY

• Search hex UTF-16LE style:
  Code:

  59 00 56 00 31 00 4D 00 57 00

• Also search only the last part:
  Code:

  560339

VIN: UNKNOWN_VIN

• CEM flash decodes VIN correctly: YV1MW7551A2560339
• CEM EEPROM says UNKNOWN_VIN — normal enough
• SID803 flash says UNKNOWN_VIN — may be tool/layout issue

0x3FE00 - 0x3FFFF

0x3FEF0