ISTA+ DME Blue Block - MEV1746 MV1746 Bmw E Series LCI

The blue block in ISTA+ is expected here — you've got a mismatch between what's physically in the flash and the ECU's internal identity/security state, so ISTA+ refuses to touch it and WINKFP fails at security access. That's the core of it.

The key problem: you wrote the donor's full flash into the original DME, but the EEPROM stayed original (your read shows the 128 KB eeprom each time). So now the ECU has donor calibration/program data but original EEPROM identity data. The security access is derived from data that no longer matches, which is exactly why you get:


and then IFH-0009 (no response) once it tries to enter programming mode.

A few things to sort out before going further:

• On MEV17.4.6 the ISN and security data live in the EEPROM/internal area, not the external flash. Copying only the flash region leaves the ECU internally inconsistent.
• Since your original EEPROM survived (you read a valid 128 KB), the cleaner path is usually: keep the original EEPROM (original ISN/identity) and write only matching flash+cal to it, then let ISTA-P do a full recover/programm. Mixing donor flash + original EEPROM is what's producing the blue state.
• WINKFP won't recover a DME that ISTA+ marks blue — you need ISTA-P (which you have, 3.72) to do a full "encode/programme" recovery once identity is consistent.

To tell you exactly what to correct, I need a couple of specifics from your dumps:

• Confirm the exact ECU family from the label — is it MEV17.4.6 or MEVD17.4.6? (your title says MEV1746)
• Which EEPROM are you currently running in the original DME right now — original or donor?
• Are the ISN in original DME EEPROM and the CAS ISN the same? On a donor CAS+DME+key set the ISN should match the donor, so if you kept original DME EEPROM the ISN will conflict with the donor CAS.

That last point matters a lot: you said the donor CAS + DME + key made the car start, but now you're trying to run the original DME against the donor CAS. If the ISN in the DME doesn't match the ISN the donor CAS expects, EWS/DME alignment will fail regardless of flash. Post the ISN from original DME EEPROM vs the CAS ISN and we can confirm whether it's a security-access mismatch or an EWS sync issue.

Hello
MEV17.4.6
The original DME uses the original EEPROM.
I used a donor FLASH in the original DME
I'm currently using the original CAS + original DME + key (ISN original).

I currently have two sets:
1) Original CAS + original DME + key (previously fully functional)
(DME stopped working after the update)
2) Donor CAS + donor DME + key (previously fully functional)
(Water got into the DME - it's not working properly)

I decided to upload the donor's flash to the ORIGINAL DME
The car now recognizes the original DME.
The DME is now blue in ISTA+, previously, it wasn't detected at all.

Good, that clears up the identity picture: original EEPROM (original ISN) + donor flash in the original DME, running on the original CAS. So the ISN/CAS pairing is consistent — that's not your problem. The blue block now is a software/programming-state mismatch, not an immo mismatch.

Here's what's happening: the donor flash you wrote carries the donor's I-level / program+cal version and internal progman counters, but the ECU is being addressed as your original VIN/order. ISTA+ sees an ECU whose actual flash content doesn't match the expected SW status for that vehicle, so it marks it blue and refuses OBD programming until it's brought back to a known state. WINKFP then dies at security access / IFH-0009 because it can't negotiate programming mode on an ECU in that inconsistent state.

The realistic fix is to let ISTA-P 3.72 do a full recovery/programme of that DME to your car's target I-level. That's exactly the case ISTA-P is built for (blue/unrecognized SW state), and it's why ISTA+ told you to go to P. WINKFP alone won't dig it out of blue.

Before you run it, a few things worth checking so it doesn't fail mid-flash:

• Same MEV17.4.6, same part number both units? You said both are marked 7 585 247 / 0 261 S04 289 — good, so the target SW ISTA-P wants should be flashable.
• Was the donor flash a full read (internal MPC + external flash) or partial? If the external 4 MB flash went in but the internal MPC/pflash region is still original/garbage, WINKFP/ISTA-P can't complete programming mode — that alone produces IFH-0009.
• Stable bench or in-car supply — 13.5V constant during ISTA-P recovery, no battery charger noise.

To tell you the exact next click, confirm:

• Did you write both the 4 MB external flash and the 2 MB MPC (internal) from the donor into the original DME, or only the external flash?
• What's the target I-level of the car (from ISTA-P vehicle info) vs the donor's SW status?
• When ISTA-P sees the DME now, does it list it for a "Programmieren/Nachprogrammieren" action, or does it also refuse it?

My suspicion is you copied only the external flash and left the internal MPC original — that's the usual cause of a DME that goes blue and then blocks security access. Confirm the MPC question and we'll know which way to go.