Stage 1 file — what to check before flashing

A stage 1 file is a calibration-only tune for a completely stock vehicle: boost pressure, injection quantity and timing, torque limiters and throttle maps are raised within the margins the hardware already tolerates. No different turbo, no mechanical changes, no emissions removal.

That distinction matters in the file: a proper stage 1 leaves every monitor and safety routine active. DPF, EGR or AdBlue deletes are separate modifications with their own logic — don't confuse a “stage 1” that quietly removes hardware monitoring with a real calibration tune.

On many ECUs an OBD read returns the whole calibration area — enough for a stage 1 on most Bosch EDC16/EDC17, ME7/MED9 and similar units. But some protocols only return a “virtual read” (reconstructed by the tool) or the map area alone.

• Full bench/boot flash — required on locked ECUs (Bosch MD1/MG1, several Delphi and Continental units); contains everything, including zones OBD can't reach.
• Virtual read — usable for map work, but checksum zones and DTC tables may be reconstructed rather than dumped; tell the file service what it is.
• Map-area-only OBD read — enough for a stage 1 in many cases, but a service can't safely touch what it can't see; partial is not corrupt, just incomplete.

Save the untouched read before anything else — under a name that records the vehicle, ECU ID, tool, method and date. That ORI is your rollback if the car misbehaves, and the baseline for every future modification.

If the original is ever lost, a back-to-stock service can rebuild a stock file for most ECUs — but it costs time and credits a saved ORI makes unnecessary.

• An OBD write takes roughly 2–20 minutes depending on the protocol; voltage below ~12.5 V during the write is the classic cause of a truncated flash.
• Use a stabilised battery support unit — not a trickle charger; you need 20 A+ available on demand.
• Ignition on, consumers off: blower, headlights, heated rear window, wipers.
• Laptop on mains power, sleep and updates disabled for the session.
• Bench or boot work: use a lab PSU — a car battery on the bench is a brown-out mid-write.

A slave tool produces files only your master can modify — often delivered encrypted. A file service can't open them; the file must come from your master, or the service must explicitly support your tool's ecosystem.

Checksum: master tools recalculate it during the write, and the log says so — “checksum corrected” is the line you're looking for. If your workflow flashes a raw file through another path (BDM, boot restore), the file itself must be pre-corrected — see the checksum correction guide.

An EDC17C64 is not an EDC17C79, and the same ECU model ships in several software versions. Match ECU ID, software version and hardware number between the read and the file you're about to write — “close enough” is how recoveries start.

A professional file is built on the file you sent, not on a generic family match — which is why the original read matters more than the tool that made it.

A stage 1 keeps emissions hardware and monitors functional, but any tune can affect emissions, type approval and warranty — and insurers and inspectors may treat an undeclared tune as a modification. Regulations differ by country: check what applies to a road-going vehicle locally. Modifications destined for competition or off-road use are flagged as such on our service pages.