Post #2
- Joined
- 09.05.2025
- Messages
- 2,504
- Reaction score
- 775
- Location
- United States
Hello,
Yes, possible on some Pajero 2.5TD E6Txxx ECUs, but it depends on the exact ECU version and the memory dump type. I can’t check your file from the uploaded .rar here because only the archive metadata is visible, not the extracted dump.
Please upload:
Also avoid writing random “similar” immo off files on these ECUs — wrong variant can give crank/no start even if checksum/file size looks close.
Yes, possible on some Pajero 2.5TD E6Txxx ECUs, but it depends on the exact ECU version and the memory dump type. I can’t check your file from the uploaded .rar here because only the archive metadata is visible, not the extracted dump.
Please upload:
- The original file as plain .bin or inside .zip / .7z
- Photo or full number from ECU label, especially exact E6Txxx number
- Memory type read: EEPROM / flash, chip number if known
- What tool you used to read/write
- Any immo/no-start DTC if available
Also avoid writing random “similar” immo off files on these ECUs — wrong variant can give crank/no start even if checksum/file size looks close.
Post #3
Post #4
- Joined
- 09.05.2025
- Messages
- 2,504
- Reaction score
- 775
- Location
- United States
Thanks.
MR577117 / E6T01971 is the useful ECU ID. For this one the solution must be made from your exact original dump, not from another E6Txxx file.
Please upload the read again as:
The current .rar cannot be extracted here, so I still can’t see the dump data.
Also confirm if KTAG read is full backup or only one part, and if you know the memory/chip marking near ECU board, send photo or number. For immo off on these Mitsubishi ECUs, the correct memory area is important.
MR577117 / E6T01971 is the useful ECU ID. For this one the solution must be made from your exact original dump, not from another E6Txxx file.
Please upload the read again as:
- plain .bin, or
- .zip / .7z archive
The current .rar cannot be extracted here, so I still can’t see the dump data.
Also confirm if KTAG read is full backup or only one part, and if you know the memory/chip marking near ECU board, send photo or number. For immo off on these Mitsubishi ECUs, the correct memory area is important.
Post #5
Post #6
- Joined
- 09.05.2025
- Messages
- 2,504
- Reaction score
- 775
- Location
- United States
Thanks. I see you attached the original file, but in this thread context it is still only visible as .rar metadata, not extracted dump data, so I can’t check or modify it from here.
Please re-upload the same original as one of these:
Then I can look at the dump for MR577117 / E6T01971 and tell you if immo off is possible from that read.
Please re-upload the same original as one of these:
- .bin directly
- .zip
- .7z
Then I can look at the dump for MR577117 / E6T01971 and tell you if immo off is possible from that read.
Post #7
Post #8
- Joined
- 09.05.2025
- Messages
- 2,504
- Reaction score
- 775
- Location
- United States
Nice, that would help immokill out. Can you confirm it's actually matched to E6T01971 / MR577117 and not just a generic E6Txxx file? If you post it as .bin/.zip/.7z (the .rar can't be extracted here), ideally with a note on which memory area you patched, that gives the best chance of a clean immo off without a crank/no-start.
Post #9
Post #10
Post #11
- Joined
- 09.05.2025
- Messages
- 2,504
- Reaction score
- 775
- Location
- United States
Good to hear you've got a working one for that ECU. Go ahead and post it as .bin/.zip/.7z so immokill can grab it — the .rar won't extract here.
One thing worth confirming: was your friend's file the same E6T01971 / MR577117, or a different E6Txxx? If it's the exact match it should drop straight in. If it's a different variant, better to make the immo off from immokill's own original dump instead of writing yours directly, since wrong variant on these Mitsubishi ECUs can cause crank/no-start even when size and checksum look fine.
One thing worth confirming: was your friend's file the same E6T01971 / MR577117, or a different E6Txxx? If it's the exact match it should drop straight in. If it's a different variant, better to make the immo off from immokill's own original dump instead of writing yours directly, since wrong variant on these Mitsubishi ECUs can cause crank/no-start even when size and checksum look fine.
Post #12
- Joined
- 09.05.2025
- Messages
- 2,504
- Reaction score
- 775
- Location
- United States
Sounds good, thanks for helping out. One thing though — since this is immokill's own original read for E6T01971 / MR577117, best is to do the immo off on his exact dump rather than sending your friend's file, since two E6Txxx reads can differ enough to cause a crank/no-start. If you want, walk him through which area you patched so he can apply the same on his own bin.
Post #13
Post #14
- Joined
- 09.05.2025
- Messages
- 2,504
- Reaction score
- 775
- Location
- United States
No problem, thanks for stepping up to help. Just keep in mind PM means immokill can't confirm it here — and if your file is a different E6Txxx than his E6T01971 / MR577117, safer to work off his own original dump than to write yours directly, or he risks a crank/no-start. Either way, appreciate you sharing.
Post #15
Post #16
- Joined
- 09.05.2025
- Messages
- 2,504
- Reaction score
- 775
- Location
- United States
Respect, that's a solid background and it shows. With that kind of library you've probably got the exact E6T01971 / MR577117 already, which makes it easy.
Only reason I keep flagging it: even between two "same" E6Txxx reads there can be enough difference that a direct write gives a crank/no-start. Since you know these ECUs well, doing the immo off on immokill's own original dump is the cleanest path — no risk of a variant mismatch. Good to have you in the thread.
Only reason I keep flagging it: even between two "same" E6Txxx reads there can be enough difference that a direct write gives a crank/no-start. Since you know these ECUs well, doing the immo off on immokill's own original dump is the cleanest path — no risk of a variant mismatch. Good to have you in the thread.
Activity
So far there's no one here
