// the find
hypery11/flipper-tesla-fsd
Tesla Mod — Flipper Zero & ESP32. Nag killer, FSD region unlock, track mode, BMS dashboard, blind spot alert, high beam strobe, speed display, steering mode + more. Works via OBD-II or X179 connector.
A Flipper Zero (and ESP32) app that does real-time CAN bus frame modification on Tesla vehicles — intercepts frames from the gateway ECU, flips specific bits, and retransmits to enable FSD features, suppress hands-on nags, and recover controls on VIN-banned cars. Aimed at Tesla owners who want to avoid paying $200+ for the S3XY Commander dongle. Requires an active FSD subscription for FSD features; non-FSD diagnostics work on any AP-capable car.
The nag killer is technically careful — DAS-aware gating so it only echoes when the car is actually demanding hands, plus xorshift32 PRNG torque variation to avoid the fixed-value pattern that earlier tools tripped over. The GTW Config Replay feature was honestly renamed from 'Ban Shield' in v2.15 after community testing showed it doesn't prevent bans, and the README says so explicitly with issue links — that kind of honest documentation is rare in this space. The ESP32 port brings the same CAN logic to $14 hardware with a WiFi dashboard and NVS persistence, which is a significant cost reduction over the Flipper path. The compatibility table with specific firmware versions, hardware revisions, and named testers is genuinely useful for evaluating whether your car is covered.
The default Listen-Only boot mode is safe but the jump to Active mode for someone who doesn't understand CAN bus is a real risk — one wrong toggle and you're injecting frames into a moving vehicle's control bus. The OBD-II connection point warning ('may go silent in Drive on some Model 3/Y builds') is buried in the hardware section and should be front-and-center since silent failure mid-drive is the worst outcome. The beta settings table includes 'Telemetry Off' with the note 'may itself be a ban signal, use only with SIM pulled' — shipping that in the UI at all without a hard warning is irresponsible. No automated hardware-in-loop testing exists; the test/ directory has a single Makefile and one C file, so firmware regressions depend entirely on community volunteers reporting broken cars.