Looking for working EEPROM 95320 dump - Mercedes EDC16C2 0 281 012 225 / A6461500391

• OtoCheck — this is a tool for immo data in the EEPROM of the ECU (the 95xxx/24Cxx family). In other words, it works on the 95320 itself. In your case, that is not enough — the previous person already accessed just the chip using a clip, hence the inconsistency. OtoCheck will repeat exactly the same mistake because it will not touch the DAS authorization in the MPC flash.
• Immo Universal Decoding / Immo Killer — these tend to be broader, and some builds have entries for Bosch EDC16, but I cannot confirm from here that your particular build has a profile for CR30-646-12E2 / DAS CR3 OM646 and that it operates on the flash rather than just the EEPROM. That is the whole difference in your case.

• whether there is an entry marek/ECU in the list for Mercedes → Bosch EDC16C2 (or CR3 / OM646 / DAS),
• whether, when loading, it asks for a flash file (FLS) or only for EEPROM — if it only takes EEPROM, it is ruled out for the same reason as OtoCheck,
• what exact wersja/build each one is.

• Wrong file size — the “parziale” profile (Italian for “partial”) often expects a specific flash segment, not a full read. Your FLS is a full 1.00 MB. Some tools only want the data section (e.g. 512 KB / 0x80000) or exactly the block where the authorization is stored, not the entire 1 MB with the boot.
• Wrong file altogether — the profile takes EEPROM, and you're providing flash (or vice versa).

• what exact size in bytes file this profile expects (it is often written in oknie/opisie),
• whether “parziale” requires flash or EEPROM,
• the full name and version of this tool.

• VIN in the EEPROM header: WD0PD6447557892526471 → this is a Sprinter (W901–905 / T1N generation), matches your "Sprinter 2005".
• Dataset 1037371847 is consistent across EEPROM (0x20), EXT FLASH (0x10) and INT FLASH string → all three files are the same ECU, same read session. Good.
• INT FLASH carries CR30-647-C3N3-N4 / 2.7l → this is the OM647 2.7 CDI, EDC16C2. That fits 0281012198.

• Which target is this going into — is the Sprinter ECU staying in the Sprinter with its original EIS/immo module and keys, or is this a swap into another vehicle without the Mercedes EIS? That decides whether you even want immo off, or whether a normal EIS/key sync would be cleaner.
• What software/tools do you have on the bench (KESS/KTAG/BDM, and any immo-off tool with an EDC16C2 profile)? Same question as before — some profiles only touch EEPROM and will repeat the half-patch.
• Confirm the INT FLASH is a full read — it shows 448.5 KB, which is the internal-only section, so a tool asking for a 1 MB or 512 KB file may reject it as "incorrect file size."

Gemini said:

Hi Alex, this is a different truck/ECU from the thread starter, but you actually uploaded a solid set of files, so here's what I can see.

Identification from your dumps:

• VIN in the EEPROM header: WD0PD6447557892526471 → this is a Sprinter (W901–905 / T1N generation), matches your "Sprinter 2005".
• Dataset 1037371847 is consistent across EEPROM (0x20), EXT FLASH (0x10) and INT FLASH string → all three files are the same ECU, same read session. Good.
• INT FLASH carries CR30-647-C3N3-N4 / 2.7l → this is the OM647 2.7 CDI, EDC16C2. That fits 0281012198.

The important part for immo off:
On this generation the engine ECU immo authorization lives on both the flash and the EEPROM. If you only раtсh the 95320 EEPROM with a clip tool, the flash still expects the handshake and you get a mismatch fault that won't clear — exactly the trap the guy earlier in this thread fell into. So immo off has to be calculated on the flash + EEPROM pair together, not EEPROM alone.

What I need from you to point you at the right way in:

• Which target is this going into — is the Sprinter ECU staying in the Sprinter with its original EIS/immo module and keys, or is this a swap into another vehicle without the Mercedes EIS? That decides whether you even want immo off, or whether a normal EIS/key sync would be cleaner.
• What software/tools do you have on the bench (KESS/KTAG/BDM, and any immo-off tool with an EDC16C2 profile)? Same question as before —custome disconect battery some profiles only touch EEPROM and will repeat the half-раtсh.
• Confirm the INT FLASH is a full read — it shows 448.5 KB, which is the internal-only section, so a tool asking for a 1 MB or 512 KB file may reject it as "incorrect file size."

One rule before anything: keep the untouched backup of all three files (EXT FLASH + INT FLASH + EEPROM) exactly as you read them, before you write anything back.target srinter inmobilazer is original wps original key remote wont sent signal to the doors no backrground of the sprinter no idea if is the original car turn on swaping ecu wps and key customer diconect the barteery and car wont start again i using multprog to read it i have a donated ecu touched for a locksmith with no luck to virginize it thats the other way i can fix that what you recomend

Click to expand...

• Your two attachments here are two different ECUs. The first EEPROM/FLASH pair (…155034 / …154829) has VIN WD0PD644…, dataset 1037371847P322/C33. The second pair (…160925 / …161103 / INT FLASH …161232) has a different VIN WD2YD742…, and the EXT FLASH there carries 1037543368P322/C33, while the EEPROM still shows 1037371847. So on the second set the flash and EEPROM datasets don't match each other — make sure you're not mixing reads from two ECUs on the bench.
• All of them are CR30-647-C3N3-N4 / 2.7l = OM647, EDC16C2, so 0281012198 fits.

• Did that immo-off run actually write back, or did it just open/close the window with no data changed? The log lines don't show a write result — did it report success?
• Multi-PROG immo-off on this profile — does it operate on the INT FLASH + EEPROM, or only EEPROM? That's the whole point on OM647; EEPROM-only will leave the same mismatch the earlier guy hit.
• Which exact ECU are you actually fitting — the WD0PD644 one or the WD2YD742 one? Pick one and keep its own matching flash + EEPROM + int flash together.

• "Original ECU and donated ECU files" — this is important. Are you trying to clone the donor ECU to replace the original, or do immo off on one of them? Those are different jobs:
  • Clone: you copy the donor's full flash + EEPROM into the target ECU so it behaves as that unit. But a donor from another car still has its own immo/VIN data — it won't just start in your vehicle unless the donor was already immo-off, or you also handle the EIS/immo side.
  • Immo off: you patch the authorization out of flash + EEPROM so the ECU runs with no immo handshake at all. This is the right path for a swap with no Mercedes EIS.
• Multi-PROG doesn't calculate immo off, so you need a separate tool that has an EDC16C2 / OM647 profile and operates on the INT FLASH + EEPROM pair, not EEPROM alone. Same trap as earlier in this thread — EEPROM-only leaves the flash still expecting the handshake.

• Which ECU is actually going in the vehicle — the original or the donor? Keep that one ECU's own matching flash + EEPROM + int flash together and don't mix the two reads (your two file sets have different VINs/datasets).
• Is this a swap with no Mercedes EIS/keys in the target vehicle? If yes → full immo off is the way. If the original EIS + keys are still there → a normal EIS/key sync is cleaner and you may not need immo off at all.
• What immo-off software do you actually have access to besides Multi-PROG? That's the tool that has to do the flash+EEPROM calculation.

• There is no ready-made universal .bin that will just start your engine. Immo off has to be calculated on your own matching flash + EEPROM pair — someone else's dump has their VIN/immo data and won't work in your ECU.
• You must confirm the tool's profile actually lists EDC16C2 / CR3 / OM647 specifically and takes the INT FLASH file, not EEPROM only. EEPROM-only will repeat the mismatch trap.

• Which ECU is actually going in the truck — the original (WD0PD644…) or the donor (WD2YD742…)? Keep that one ECU's own flash + EEPROM + int flash together and don't mix the two reads.
• Is this a swap with no Mercedes EIS/keys in the target vehicle? If yes → full immo off is correct. If the EIS is staying, a normal EIS/key sync is cleaner.

• WSP = Wegfahrsperre, the Mercedes immobilizer system. If your truck still has the original WSP/EIS immo module and keys, and the ECU is staying in that truck, you very likely don't need immo off at all — you need the ECU and the WSP module to be in sync (correct handshake), which is a cleaner and more reversible job than patching the flash.
• You only want a full flash+EEPROM immo off when there is no working WSP/EIS module in the target vehicle — e.g. an engine/ECU swap into something without the Mercedes immo, or the WSP module is dead/missing.

• Which ECU is actually going in the truck — original (WD0PD644…) or donor (WD2YD742…)? Keep that one's own flash + EEPROM + int flash together.
• Is the original WSP module + working key staying in the vehicle, or not? If WSP stays → sync/adapt the ECU to the WSP, don't immo off. If WSP is gone → then full immo off on flash + EEPROM is the correct path.