IMMOFF17 v2.1 - The EDC17/MED17 Immo Disabler

IMMOFF17 DTC EGR DPF раtсh Tool - ECU Tuning EEPROM Solution 2025-08-10

Sign in to download for free
IMMOFF17 v2.1 - The EDC17/MED17 Immo Disabler
IMMOFF17 DTC EGR DPF раtсh Tool - ECU Tuning EEPROM Solution 2025-08-10
Sign in to download for free

Bin

Thread Owner
Administrator
Joined
03.05.2025
Messages
1,813
Reaction score
30,861
New release thread for IMMOFF17 v2.1 - The EDC17/MED17 Immo Disabler: discuss, share feedback, and get help.


IMMOFF17 v2.1 - The EDC17/MED17 Immo Disabler​

Your "Immo Off" Solution for Engine Swaps and ECU Repairs.

The Professional's Tool for Disabling the Immobilizer on EDC17 & MED17 ECUs.

View attachment 428

IMMOFF17 is a specialized software utility designed for one critical task: correctly disabling the factory immobilizer system within the EEPROM of...

Frequently Asked Questions​

Which Windows version is recommended?
For maximum stability during ECU flashing and diagnostics, a clean installation of Windows 10 (64-bit) is recommended.
Is it compatible with J2534 PassThru?
Most modern software versions support standard J2534 interfaces like Scanmatik 2 Pro, OpenPort 2.0, and specific VCI adapters.

What's inside:
  • Overview & screenshots
  • Version history and compatibility
  • Download link and setup notes

👉 View full details and download — IMMOFF17 v2.1 - The EDC17/MED17 Immo Disabler
 

The MED17.1.62 is a common ECU, so the tool should support it in principle — but the "file size is too big" error almost always means you're loading the wrong type of dump.

IMMOFF17 works on the EEPROM only, not the full flash.

Here's what's likely happening:

  • You probably read a full flash dump (several MB — typically 2 MB, 4 MB, or larger) using your bench tool.
  • IMMOFF17 expects only the EEPROM section, which on MED17.1.62 is typically 32 KB (32768 bytes) or in some cases 64 KB depending on the read method.

What you need to do:

  1. Go back to your bench tool (KTAG, Flex, PCMFlash, etc.) and read only the EEPROM — not the full flash/internal flash.
  2. Most tools have separate read options like "Full Read" vs "EEPROM Read" or "External EEPROM" — select the EEPROM-specific option.
  3. Load that smaller EEPROM file into IMMOFF17.

Can you confirm:
  • What tool did you use to read the ECU? (KTAG, Flex, PCMFlash, CMD, etc.)
  • What is the exact file size of the dump you're trying to load?
  • Was it read on bench or via OBD?

That will help narrow down exactly which file you need to extract or re-read.
 
file size 2048kb and i read with magic motorsport in bench

That confirms the issue — your 2048 KB (2 MB) file is the full internal flash, not the EEPROM.

What you need to do

In MAGPro2 / Flex, when you set up the bench read for MED17.1.62, the software gives you separate read options:

  • Internal Flash — this is your 2 MB file (full calibration + program area)
  • External EEPROM — this is the small file IMMOFF17 needs (typically 32 KB)

You need to go back to bench and read the External EEPROM separately. In Flex/MAGPro2:

  1. Keep the ECU on the bench with the same wiring/pinout
  2. In the software, select the same ECU family (MED17.1.62)
  3. Look for the EEPROM read option — it's usually listed as a separate memory area (e.g., "EEPROM 93C86" or similar depending on the variant)
  4. Read it — the resulting file should be around 32 KB
  5. Load that file into IMMOFF17, apply the IMMO OFF + Checksum раtсh
  6. Write the patched EEPROM back via the same EEPROM write function

Important

  • Do NOT write the patched EEPROM data into the full flash area — they are completely different memory regions.
  • Always keep a backup of both the original full flash and the original EEPROM before writing anything back.
  • After writing the patched EEPROM, the full flash stays untouched — you only modify the EEPROM.

Go ahead and re-read the EEPROM on bench with Flex and try again. If you run into any issues with the read or the tool still rejects the file, post the exact file size of the new EEPROM dump and any error message you get.
 
Activity
So far there's no one here
Back