Definitions
SFD blocks sensitive adaptations until an unlock token is applied.
Almost every workflow begins with reading an offline challenge — a long hexadecimal string — from the ECU through UDS security routines.
That challenge is what we transform into the unlock token you paste back into the tool.
Generic workflow
Identify module hex address (e.g. 17 instrument cluster, 01 engine).
Use your scan tool's vendor-specific menu to request an offline SFD challenge.
Copy the challenge verbatim — whitespace does not matter; we normalise it.
Purchase an unlock token from sfdcode for the correct SFD generation.
Apply the returned token using the same tool path your OEM software expects.
Why we publish tool guides
Menus differ: OBDeleven speaks mobile-first copy, VCDS uses German engineering terminology, Autel hides routines inside brand-specific tiles.
Search engines reward specificity, so our OBDeleven / VCDS / VCPC / Autel guides mirror the UI language technicians actually type into Google.
SFD vs SFD2 in one paragraph
SFD uses an older challenge-response scheme we can compute instantly after payment.
SFD2 is newer and heavily guarded — we broker tokens manually via trusted suppliers, which is why delivery is measured in hours, not seconds.
Pick the wrong generation and the token will never take — when unsure, compare what your tool displays against our selector or email support with a screenshot.
Legitimate use only
sfdcode is built for workshops servicing vehicles they are authorised to work on.
We do not assist theft, immobiliser bypass, mileage rollback or any tampering scenario.
Choose your path
One-off token? Guest checkout.
Volume workshop? Prepaid packs and the member panel.
Want truck-side automation? Watch the desktop roadmap — J2534/D-PDU writers ship after the public beta.