Plug in your existing cable (VCDS, VAS, VNCI 6154A, and many Passthru/USB tools). The app reads what the control unit asks for, grabs the unlock from sfdcode on the Internet, sends the answer back to the car — you stay inside one workflow.
Windows 10 · Windows 11 · 64-bit
~58 MB · auto-update enabled
Amounts exclude VAT unless stated at checkout.
The installer is locked and digitally signed — we're on the final test pass. Want a ping when downloads open? Write to support@sfdcode.com.
When your unlock reply is ready, the app pushes it straight into the chosen control unit over the cable you already use. Skip pasting hex into VCDS, QR codes, or another tool: one flow from “read question” to “car accepts answer”.
SFD (fast lane) — the reply is fetched in moments and delivered back inside the same car session (usually under one minute).
SFD2 (operator turn) — the app sends our team the request, waits for the manual reply when it arrives, then writes it to the vehicle in your next cable session.
Safety net — each attempt stores a rollback point beforehand; you can go back safely from History if anything looks wrong.
A preview of the interface we’re shipping. Looks and actions mirror the behaviour you saw above: faster SFD jobs and queued SFD2 jobs share the same pages.
Step 1
Choose the cable plugged into the PC. We read the chassis number from the gateway, list the control modules on the vehicle, and show what kind of unlock each one needs.
Modules found
0x01EngineSFD0x17DashboardSFD0x19GatewaySFD20x5FInfotainmentSFD2Step 2
Pick the relevant module (for example dash, gateway or infotainment). The tool reads its security prompt; we instantly buy an SFD reply or quietly queue an SFD2 reply — everything happens on one screen.
Request string from diagnostic tool
A1F4 9CB2 DD30 7E18 4A2C 5F90 11B6 CC42 …8C42 1E9B 7AD0 22F1 65E8 4A33 …Step 3
We forward the unlock answer into the chosen module in the same connection, verify the accepted status, and show a clear unlocked confirmation.
Captures what the ECU challenged, retrieves your authorised reply via sfdcode, and flashes it straight back via the ongoing cable conversation — rarely more than sixty seconds hands-off.
For jobs that still need manual approval behind the scenes, the app relays the paperwork, watches for the finished reply quietly, then injects it the moment our staff release it.
Supports common workshop interfaces: Passthru (often called “J2534”) mode for HEX-V2 and similar, plus VW’s modern D‑PDU/USB pattern for OEM VAS and VNCI 6154A hardware.
Pulls chassis number straight from data on the gateway, inventories every reachable module, labels which unlocking style each one prefers — reduces guess clicks.
Each attempt freezes a reversible snapshot first; rollback from History restores the stored copy if behaviour looks off.
If the broadband blips halfway through, unfinished steps queue politely and replay once you’re reachable again.
“Recommended” tools are exercised on every numbered release so we can stand behind predictable behaviour. “Also supported” entries share the same cabling rules but rely on cloned or generic adapters — quirks can appear, though many shops run them happily.
| Tool | How it attaches | Trust level | SFD auto-write | SFD2 auto-write |
|---|---|---|---|---|
| VCDS HEX-V2 (Ross-Tech) | USB / Passthru (J2534) | Recommended | ||
| OEM VAS5054A | USB / Passthru (J2534) | Recommended | ||
| OEM VAS6154A / VAS6154B | USB diagnostic (VW D‑PDU) | Recommended | ||
| VNCI 6154A | USB diagnostic (VW D‑PDU) | Recommended | ||
| VAS5054 clones | USB / Passthru clone | Also supported | ||
| Generic J2534 clones | USB / Passthru (generic) | Also supported |
VCDS HEX-V2 (Ross-Tech)
USB / Passthru (J2534)
OEM VAS5054A
USB / Passthru (J2534)
OEM VAS6154A / VAS6154B
USB diagnostic (VW D‑PDU)
VNCI 6154A
USB diagnostic (VW D‑PDU)
VAS5054 clones
USB / Passthru clone
Generic J2534 clones
USB / Passthru (generic)
Currently in development — will be released soon · support@sfdcode.com