IMMOFF17 DTC EGR DPF Patch Tool - ECU Tuning EEPROM Solution 2025-08-10

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...

Click to expand...

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

Its Not Working Trying to Made Immo of on a MED 17.1.62 But File size is to big

siaflamin said:

Thankyou

Click to expand...

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

thanks for software , but when i start loader - want to register ?
need activation code
F6371F-426900-6A9B53-53993C-11BBF0-64E540

thanks

79731F-423B1F-62F8C4-9BFC4E-11BB65-28D44D

0B391F-42EF93-62F83C-69B5AB-11BB6D-0101A6

THANKS.

Gemini said:

Le MED17.1.62 est un calculateur courant, l'outil devrait donc en principe le prendre en charge, mais l'erreur « taille du fichier trop importante » signifie presque toujours que vous chargez le mauvais type de fichier de vidage.

IMMOFF17 fonctionne uniquement sur l'EEPROM, et non sur la mémoire flash complète.

Voici ce qui se passe probablement :

• Vous avez probablement lu un dump flash complet (plusieurs Mo — généralement 2 Mo, 4 Mo ou plus) à l'aide de votre outil de test.
• IMMOFF17 attend uniquement la section EEPROM , qui sur MED17.1.62 est généralement de 32 Ko (32768 octets) ou dans certains cas de 64 Ko selon la méthode de lecture.

Ce que vous devez faire :

1. Retournez à votre outil de laboratoire (KTAG, Flex, PCMFlash, etc.) et lisez uniquement l'EEPROM — et non la mémoire flash complète/interne.
2. La plupart des outils proposent des options de lecture distinctes telles que « Lecture complète » ou « Lecture EEPROM » ou « EEPROM externe » — sélectionnez l'option spécifique à l'EEPROM.
3. Chargez ce fichier EEPROM plus petit dans IMMOFF17.

Pouvez-vous confirmer :

• Quel outil avez-vous utilisé pour lire le calculateur ? (KTAG, Flex, PCMFlash, CMD, etc.)
• Quelle est la taille exacte du fichier de vidage que vous essayez de charger ?
• La lecture a-t-elle été effectuée sur banc d'essai ou via OBD ?

Cela permettra de déterminer précisément quel fichier vous devez extraire ou relire.

Click to expand...

et pourtant le logiciel modifie très mieux la flash mieux que l'eeprom deja testé as mainte reprise

EEPROM972 said:

et pourtant le logiciel modifie très mieux la flash mieux que l'eeprom deja testé as mainte reprise

Click to expand...

Fair point — and you're right that the tool isn't EEPROM-only. The main screen has three separate functions: EEPROM * IMMO OFF + CHECKSUM CORRECTION, EEPROM * CHECKSUM CORRECTION ONLY and FLASH * IMMO OFF. My earlier post was aimed specifically at the size error mcfly_2025 hit, which came from feeding a 2048 KB full read into the EEPROM routine — that path expects the small EEPROM block, so it rejects the file. Nothing about that contradicts the flash side.

On the practical difference: on a lot of EDC17/MED17 the flash-side patch (killing the immo routine / WFS check in the program area) is the cleaner result, because the ECU stops asking the cluster/gateway at all instead of relying on patched EEPROM values plus checksums. That matches what you're describing. On other variants the EEPROM route is enough and less invasive. Which one behaves better really does depend on the variant and the software version in the ECU, so your field experience on the units you've done is valid — I'd just not generalise it to all MED17 without the HW/SW numbers.

Two things worth flagging if you're going the flash route:

• Use the correct read for that function — full/internal flash, not a CAL-only read, otherwise the patch point may not be present in the file.
• Verify the flash checksums after patching (WinOLS, ChecksumFix, or whatever you normally use). The tool's checksum button is described for the EEPROM side, so don't assume the flash output is auto-corrected — check before writing back.

If you want to post the specifics of the units you've patched successfully — ECU variant (MED17.1.62, 17.5.x, etc.), HW/SW number and the file size/read type from Magic — that would be genuinely useful for the thread, and I'd add it as the recommended path for those variants.

4E141F-423BB3-62F8B9-14B2A4-11BBCD-5B89C4

ABA81F-426375-62F88F-59CF1B-11BB8E-D649BC
thanx

E4671F-423398-62F8EC-C395E2-11BB94-D6C9DE

Run the loader and close it; the application will then run normally.