Mercedes 7G-DCT · 724.0 · Getrag VGS2 FDCT

FDCT EEPROM Repair

Rebuilds a stuck transmission control unit EEPROM from the unit's own data. The diagnosis is free, so you can check your file before you buy.

Check is free · no account needed Sign in

1. Upload the EEPROM read

Drop the .bin file here or click to choose it. FLEX: …int_eeprom.bin · FC200: …DFLASH.bin · 128 KB

  1. Read the TCU's internal EEPROM on the bench and keep the original.
  2. Upload it here for a free diagnosis.
  3. Rebuild for one credit if the EEPROM is stuck, and download the file.
  4. Write it back, clear fault codes and run the teach-in with your diagnostic tool.

Files you upload are kept for 90 days for support, then deleted.

2. Diagnosis

Upload a file to see the bank state, VIN and any interrupted writes.

For the 7-speed 724.0 dual-clutch transmission with the Getrag VGS2 FDCT control unit (A, B, CLA and GLA-class). 8-speed units are not supported.

The rebuild fixes a stuck EEPROM, where the active bank filled before the TCU finished moving its data across. It does not fix hardware faults, mismatched software or a file from another unit. Always keep your original read and bench-test before installing.

What a stuck FDCT EEPROM is

The Getrag VGS2 FDCT control unit on the Mercedes 7G-DCT (724.0) dual-clutch transmission keeps its adaptations, counters, coding and VIN in an emulated EEPROM: two 64 KB banks of data flash that are written as a running log. When the active bank fills up, the TCU copies every block that only exists in the old bank across to the new one, then erases the old bank and carries on.

If that copy doesn’t finish, for example because the bank runs out of room part-way, the TCU is left with a full bank it can’t write to and an old bank it can’t erase. From then on it can’t save anything new, so adaptations and learned values stop updating. A read of the internal EEPROM shows it clearly: a full active bank, a previous bank that was never erased, and interrupted writes at the end of the full bank. The free check above shows exactly that.

How the FDCT EEPROM repair works

The rebuild does the step the TCU failed to finish. The newest valid copy of every block is carried into a clean bank, unchanged, with its write counter one higher, and the other bank is left erased and ready. Nothing comes from a donor file: the VIN, software number, serial, coding and the unit’s own adaptations stay as they were. Interrupted writes are dropped, because the TCU never completed them.

  1. Read the TCU’s internal EEPROM on the bench (128 KB) and keep the original.
  2. Upload it above. The check is free and doesn’t need an account.
  3. If it’s stuck, rebuild it for one repair credit and download the file.
  4. Write the file back, clear fault codes and run the teach-in with your diagnostic tool.

Supported units and files

  • Transmission: Mercedes-Benz 7G-DCT 724.0 dual-clutch with the Getrag VGS2 FDCT control unit (A-Class W176, B-Class W246, CLA C117, GLA X156).
  • File: the 128 KB internal EEPROM read. From FLEX it ends in int_eeprom.bin; from FC200 it ends in DFLASH.bin.
  • Not supported: 8-speed 8G-DCT units, program flash reads, and files from a different unit.

Questions

Do I need an account to check my file?

No. Anyone can upload an EEPROM read and see the full diagnosis. You only need an account to buy a credit and download a rebuilt file.

Will I lose the adaptations?

No. The rebuild keeps the unit’s own data, including its adaptations. It’s still good practice to clear codes and run the teach-in after writing the file.

What if my file isn’t stuck?

Then there’s nothing to rebuild and no credit is used. If the TCU still has problems, the cause is somewhere other than the EEPROM.

Is my file stored?

Uploaded files are kept for 90 days for support, then deleted.

Scroll to Top