hypery11/flipper-tesla-fsd

This is a Tesla CAN-bus toolkit for Flipper Zero and ESP32 boards: it reads traffic from the car, rewrites selected frames and retransmits them. It targets owners who are comfortable tapping a vehicle bus and want FSD-related bit tweaks, nag suppression, or read-only diagnostics instead of buying a commercial dongle — at the cost of wiring work, firmware-version caveats and warranty/legal risk the author flags.

What it changes

It works as single-bus read-modify-retransmit on Party CAN: an ECU transmits a frame, the device catches it, alters specific bits and sends it back so the receiver takes the latest version. No second bus tap or man-in-the-middle setup is needed. FSD unlock alters bits on 0x3FD (HW3/HW4) or 0x3EE (Legacy HW1/HW2); the nag killer echoes 0x370 with a randomised torque walk capped at ±1.8 Nm; TLSSC Restore rewrites 0x331 to recover traffic-light/stop-sign control on cars whose VIN has been banned. The ESP32 build adds extra opt-in toggles such as Summon EU unlock and Track Mode settings that the Flipper menu does not expose.

Hardware and setup paths

Two paths with different prerequisites. The Flipper Zero route needs a Flipper plus an MCP2515-based CAN add-on (roughly $30) and an OBD-II or X179 cable; the .fap can be installed from the Flipper Apps catalog or copied to the SD card. The ESP32 route is cheaper — from about $14 for an M5Stack ATOM Lite plus ATOMIC CAN — and supports browser flashing from Chrome, Edge or Opera, then a Wi-Fi dashboard at the board's access point. Wiring differs by Tesla model and year; the author recommends X179 behind the rear console over OBD-II because pin-to-bus mapping varies and post-2024 Highland/Juniper cars use Ethernet at the OBD port. The device boots in Listen-Only mode and cannot transmit until Active is enabled.

Limits that matter before buying

Full FSD still requires a valid Tesla FSD entitlement; the tool changes CAN frames, not server-side records. Firmware 2026.14.x added a preflight check that blocks engagement while injection is active, so an AP-First mode delays injection until autopilot is engaged — but the author states outright that FSD unlock does not work on 2026.14.x/2026.20/2026.26.x. Tesla's April 2026 VIN bans remove the TLSSC toggle, and TLSSC Restore only recovers traffic-light/stop-sign control, not full FSD visualisation. GTW Config Replay masks frames at the broadcast layer only: the author explicitly says it does not undo NVRAM or server-side state, and no ban prevention was confirmed across six weeks of v2.9–v2.14 deployment.

FSD persistence ends when the device is unplugged. The author warns modifications may void the warranty and violate local laws, and frames the project as educational/research use only. The code is GPL-3.0 (the repository's licence metadata reports NOASSERTION).

Project source and documentation