The ORI (Original) file is the ECU firmware read directly by the control unit, identical to the one loaded in the factory by the manufacturer. Typical extension: .ori, .bin, .frf, .fpf.
Importance of the ORI
- Backup: before any modification, saving the ORI is MANDATORY
- Starting point: the MOD file is created by modifying the ORI
- Recovery: if the MOD has problems, reflashing the ORI restores the factory state
- Car warranty: in case of assistance, reflashing the ORI "erases the traces"
Obtaining an ORI
Three ways: (1) read directly from the customer's ECU (always preferred), (2) download an ORI sample from the file service database for that specific ECU code, (3) official manufacturer files (VAG ODX, Mercedes For this reason it must be saved before any writing and kept associated with the vehicle, together with the reading information (method, tool, checksum).
Original from the customer or database
The best source is always the ORI read from the customer's ECU, because it contains the calibration and real adaptations of that example. The database ORIs, which can be downloaded from the service files for a specific control unit code, are useful when reading is not possible, but must be used carefully because they may differ due to software revision or variants. The manufacturers' official files (ODX/FRF formats) constitute a further source of reference.
Operational rule
The first operation on any vehicle is to read and save the ORI: it is the point of no return that protects all subsequent work. It must be stored with the reading data (tool, method, checksum) and associated with the vehicle. Always prefer the customer's original to the database ORI: only the file read by the car reflects real calibration and adaptations of that specimen, avoiding inconsistencies that could emerge after writing.