How to Flash an FRF File with ODIS or VCP: VAG Software Update Guide

FRF containers are the way Volkswagen, Audi, Skoda and Seat dealers update control unit software. With the right tool you can do the same in your workshop: install a newer software version, downgrade after a problematic update, or recover a module that still communicates. This guide walks through the procedure with ODIS Engineering and VCP, the two tools most workshops use.

What you need

• The FRF file for your control unit part number and target software version.
• ODIS-E (Engineering) with a VAS 6154 or compatible pass-thru interface, or VCP (VAG CAN Professional) with its own interface.
• A battery charger able to hold 13 to 14 V under load, not a jump starter.
• A laptop with power connected, Wi-Fi and sleep mode disabled.

Choosing the correct container

An FRF is tied to the control unit’s part number (for example 04L906021N for a 2.0 TDI engine ECU, 0AM927769G for a DQ200 gearbox). Read the part number and current software version with the diagnostic tool from the control unit identification, then choose the container with the same part number and the version you want. On engine and gearbox modules the software version is the four-digit number after the part number in our product titles. A container for a different part number will be rejected by the tool or, worse, accepted and brick the module.

Flashing with ODIS-E

1. Connect the charger and the interface, switch on the ignition, engine off.
2. Start ODIS-E, select the vehicle and open the control unit.
3. Choose “Flash” (or “Programming”), point to the FRF file and confirm the identification data match.
4. Start the flash. Do not touch the car, doors or lights until the tool reports completion.
5. Perform the follow-up steps the tool lists: basic settings, adaptations, clearing codes.

Flashing with VCP

1. Open VCP, select the control unit and go to Flash.
2. Load the FRF; VCP shows the container’s part number and version next to the module’s own.
3. Start the flash. VCP handles security access and checksums itself.
4. After completion, run the recommended coding and adaptation checks.

Common errors

• “Container does not match control unit.” Wrong part number or a container for another hardware index. Check the numbers again.
• Flash stops at a few percent. Voltage drop or an interface driver problem. Fix the power supply first.
• Module answers but the car will not start after flashing. Adaptations and component protection need to be redone; on engine ECUs check the immobilizer adaptation.
• No communication after an interrupted flash. The bootloader is usually intact. Repeat the flash; if the module stays silent, recover with the raw original dump on the bench. See our recovery guide.

FRF versus SGO

Both are VAG flash containers. FRF is the encrypted dealer format; SGO is the older, unencrypted engineering format that some tools prefer. Our guide FRF vs SGO explains the difference and which tools accept which.

Finding your file

Search our FRF/SGO category by part number. Popular families include engine ECUs EDC17CP14, EDC17C46, MED17.5.5, MED17.1 and gearbox units DQ200 and DQ250. If a version is missing, request it through the file request form.