7-Point Safety Checklist Before DIY Coding
Before you code your own car, run this 7-point check — the only way to avoid a bricked ECU.
— Tekin Code
Coding is safe in theory — but every year a handful of people brick ECUs through wrong FA files or mid-write disconnections. This 7-point check prevents 99% of failures.
1. Battery Voltage ≥ 12.6V
If voltage drops below 12.0V mid-write, the ECU flash halts and the module bricks. For long sessions, keep a trickle charger connected.
2. Make a Full Backup
OBDThink auto-backs up, but also manually 'Export FA' and save it outside your phone (cloud, computer).
3. Verify the Template
The template must match your car's chassis code (F30 vs G20) and production year. Applying a wrong-generation template produces unpredictable results.
4. One Module, One Change
If it's your first time, don't touch multiple modules at once. Make one change, test it, then continue.
5. Airplane Mode
A notification, call, or app update can sever the connection mid-code.
6. Engine Off, Ignition On
Coding requires engine off but ignition ON. Exact position: press start once without touching the brake (wakes all systems without cranking the engine).
7. Rehearsed Recovery Plan
If something goes sideways: you should already know Restore Backup by heart. Before your first coding session, run the restore flow once as a dress rehearsal.
Skipping these 7 steps turns 'free coding' into a €2,500 ECU replacement bill. Not worth it.