MB CR3.44 how to immo off any way to do that ?
- Thread starter bluen47
- Start date
Post #61
Post #62
- Joined
- 09.05.2025
- Messages
- 3,850
- Reactions
- 1,020
- Location
- United States
I can see the file is an EDC16 MPC555 flash dump (448KB, correct size) with the SW upgrade identifier "1037389924" which matches your ECU's version, so at least it's built for the right software generation.
But here's the honest answer: I cannot verify whether the immo-off patch is correct just by looking at hex and strings. An immo-off on EDC16C31 CR3 involves specific code modifications (NOPs, jumps, or conditional bypasses) in the program logic, and confirming those requires either:
Comparing it against your original read with a proper disassembler/diff tool
Knowing the exact patch pattern for SW 1037389924
Or testing it (which is the risky part)
What I can tell you from the binary:
The SW identifier matches your ECU (1037389924)
File size is correct for MPC555 internal flash
The ERCOSEK and Bosch loader strings are intact
There's a startup block and program structure present
What I cannot tell you:
Whether the immo check routines were actually patched
Whether checksums were corrected after the patch
Whether it will start without EIS or just brick the ECU
Before you flash it, nail down:
Who provided this file — do they have a track record with CR3.44 immo-off?
Did they patch your original read, or is this a generic donor file?
Do you have a full backup of your original MPC + EEPROM so you can recover if it fails?
The safer path is still the one we discussed: wire up your original EIS + key + ESL EVO and test that first. If the EIS talks, you're done with zero flash risk. Immo-off is the fallback for when the EIS is confirmed dead.
Want to try the EIS route first, or are you committed to flashing this?
But here's the honest answer: I cannot verify whether the immo-off patch is correct just by looking at hex and strings. An immo-off on EDC16C31 CR3 involves specific code modifications (NOPs, jumps, or conditional bypasses) in the program logic, and confirming those requires either:
Comparing it against your original read with a proper disassembler/diff tool
Knowing the exact patch pattern for SW 1037389924
Or testing it (which is the risky part)
What I can tell you from the binary:
The SW identifier matches your ECU (1037389924)
File size is correct for MPC555 internal flash
The ERCOSEK and Bosch loader strings are intact
There's a startup block and program structure present
What I cannot tell you:
Whether the immo check routines were actually patched
Whether checksums were corrected after the patch
Whether it will start without EIS or just brick the ECU
Before you flash it, nail down:
Who provided this file — do they have a track record with CR3.44 immo-off?
Did they patch your original read, or is this a generic donor file?
Do you have a full backup of your original MPC + EEPROM so you can recover if it fails?
The safer path is still the one we discussed: wire up your original EIS + key + ESL EVO and test that first. If the EIS talks, you're done with zero flash risk. Immo-off is the fallback for when the EIS is confirmed dead.
Want to try the EIS route first, or are you committed to flashing this?
Activity
So far there's no one here
