GPEC2 / 2A / 3 / 3B ECU Unlock

Fast in-browser tool to unlock the readout protection on Bosch / Continental GPEC2, GPEC2A, GPEC3 and GPEC3B ECUs — used in FCA / Jeep / Chrysler / Dodge / RAM vehicles from 2015 onwards — using the documented E6→E8 (2015-2018) and 07/08→96 (2018+) method, so that after unlocking you can read & write with HP Tuners. Everything runs locally — your file never leaves your device.

Local-only processing Instant results Documented E6→E8 / 07→96 method Jeep / Chrysler / Dodge / RAM 2015+ Auto-download of modified file

GPEC families supported (2 / 2A / 3 / 3B)

2015+

Jeep / Chrysler / Dodge / RAM

Uploads to any server

100 %

Runs in your browser

1) Upload your ECU file

Drop your ECU file here or click to browse

.bin / .hex / .ecu supported (up to 50 MB)

2) Pick the unlock operations

Readout Protection Unlock ⭐

Documented method: E6→E8 (2015-2018) or 07/08→96 (2018+) — enables HP Tuners read & write

IMMO Removal (Immobilizer)

Disable the immobiliser without touching the VIN (best-effort pattern)

Clear DTC (Diagnostic Trouble Codes)

Erase stored fault codes (P0xxx) from memory (best-effort pattern)

Everything runs in your browser — files are never uploaded to our servers. Press Run Unlock and the modified _unlocked file will download automatically.

Frequently Asked Questions

Does the file stay on my device?

Yes. All processing happens locally in your browser using FileReader and Uint8Array. No data is sent to any server. You can go offline and the tool still works.

What is the documented readout unlock method?

According to the publicly documented method (pcmtuner.seesaa.net and the "Easy Unlock GPEC2/GPEC2A with Hex Editor" video):

2015–2018: search the file for E6 06 65 DD and change the E6 byte to E8 (E6 = locked, E8 = unlocked).
2018+: search the file for 00 68 29 68 and change the following 07 or 08 byte to 96.

The address varies by year / model / software version — the pattern search locates it. It is a single-byte change to the bootloader readout-protection flag. After unlocking, the ECU can be read and written with HP Tuners.

Why isn't the checksum modified?

The GPEC2A checksum is auto-corrected by the flashing tool (DC706 / Foxflash / KESS3) when the file is written, so the tool deliberately does not rewrite it — modifying it here would corrupt the file. Write the unlocked file with your usual tool and the checksum is corrected automatically.

Must the file be read in boot mode first?

Yes — this is a hard requirement. The file must be a full boot-mode read taken with a programming tool (DC706 / FoxFlash / KESS3 / AutoTuner / Flex / BitBox / Ktag), not a partial OBD read — otherwise the unlock pattern (E6 06 65 DD or 00 68 29 68) may not be present in the file. After unlocking, write the unlocked file back with the same tool, and the ECU can then be read and written with HP Tuners.

Does the method work on GPEC2?

The documented method (E6→E8 / 07→96) is verified for the GPEC2A family. Per technician reports (diag.net), the GPEC2 is completely different and this method does NOT work on it — use a dedicated tool (DC706 / FoxFlash / KESS3) for GPEC2 (3MB) files. The tool warns you automatically if it detects a GPEC2 file.

Which vehicles are supported?

The GPEC2 (MPC5566 3MB, FID 20/21), GPEC2A (MPC5674 4MB, FID 19/131) and GPEC3 / GPEC3B (MPC5674 4MB, FID 18) families — used in FCA / Chrysler / Dodge / Jeep / RAM vehicles from 2015 onwards. The tool auto-detects the family from the file size (3MB or 4MB). GPEC2A is the HP Tuners-compatible one.

What about the IMMO and DTC operations?

The IMMO and DTC operations use generic best-effort patterns that are not part of the documented GPEC unlock method and may not exist in every file. The only documented operation is the Readout Protection Unlock. Keep that option checked and use IMMO/DTC with care.

Is this legal?

The tool is intended for ECUs that you own or have explicit permission to modify — typically for diagnosis and repair. Using it to hide defects when selling a vehicle may put you in legal jeopardy.