English | 繁體中文

Tesla FSD Unlock for Flipper Zero

Unlock Tesla FSD on your Flipper Zero. No subscription, no computer, just plug into OBD-II and go.

Features

• Auto-detect HW3/HW4 from GTW_carConfig (0x398), or force manually
• FSD unlock via bit manipulation on UI_autopilotControl (0x3FD)
• Nag suppression (hands-on-wheel reminder)
• Speed profile defaults to fastest, syncs from follow-distance stalk
• Live status on Flipper screen

HW Support

HW4 vehicles on firmware before 2026.2.3 should use HW3 mode. See Compatibility.

Hardware Requirements

Wiring

Important: Cut or disable the 120-ohm termination resistor on the CAN Add-On. The vehicle's CAN bus already has its own termination — adding a second one causes communication errors.

Alternative connection point: X179 diagnostic connector in the rear center console (Pin 13 CAN-H, Pin 14 CAN-L on 20-pin; Pin 18/19 on 26-pin).

Installation

Option 1: Download Pre-built FAP

1. Go to Releases
2. Download tesla_fsd.fap
3. Copy to your Flipper's SD card: SD Card/apps/GPIO/tesla_fsd.fap

Option 2: Build from Source

# Clone the Flipper Zero firmware
git clone --recursive https://github.com/flipperdevices/flipperzero-firmware.git
cd flipperzero-firmware

# Clone this app into the applications_user directory
git clone https://github.com/hypery11/flipper-tesla-fsd.git applications_user/tesla_fsd

# Build
./fbt fap_tesla_fsd

# Flash to Flipper
./fbt launch app=tesla_fsd

Usage

1. Plug the CAN Add-On into your Flipper Zero
2. Connect CAN-H/CAN-L to the vehicle's OBD-II port
3. Open the app: Apps > GPIO > Tesla FSD
4. Select "Auto Detect & Start" (or force HW3/HW4)
5. Wait for detection (up to 8 seconds)
6. The app starts modifying frames automatically

Screen Display

  Tesla FSD Active
  HW: HW4    Profile: 4/4
  FSD: ON    Nag: OFF
  Frames modified: 12345
       [BACK] to stop

Activation Trigger

FSD activates when "Traffic Light and Stop Sign Control" is enabled in your vehicle's Autopilot settings. The app watches for this flag in the CAN frame and only modifies frames when it's set.

Compatibility

HW1/HW2 Legacy Support — Volunteers Needed

Older Model S/X vehicles (2016-2019) use a Mobileye-based architecture with different CAN IDs. The autopilot control frame is on 0x3EE (1006) instead of 0x3FD (1021), and the bit layout differs.

The logic is already documented (see CanFeather LegacyHandler), but we need someone with a HW1/HW2 car to validate it before we ship.

If you have a 2016-2019 Model S/X with FSD and want to help:

1. Hook up Flipper + CAN Add-On to OBD-II
2. Open the stock CAN sniffer app
3. Confirm CAN ID 0x3EE (1006) appears on the bus
4. Capture a few frames and post them in issue #1

Once verified, Legacy support is a quick add.

How It Works

Single-bus read-modify-retransmit on Party CAN (Bus 0). No MITM, no second bus tap.

1. ECU sends UI_autopilotControl (0x3FD) on Bus 0
2. Flipper catches it, flips the FSD enable bits
3. Flipper retransmits — receiver uses the latest frame

CAN IDs Used

FAQ

Does FSD stay unlocked after I unplug?
No. It's real-time frame modification. Unplug = back to stock.

Can this brick my car?
Only UI config frames are touched. No writes to brakes, steering, or powertrain. Still — your car, your risk.

Do I need the CAN Add-On?
Yes. Flipper has no built-in CAN. You need the Electronic Cats board or any MCP2515-based module on the GPIO header.

Credits

• commaai/opendbc — Tesla CAN signal database
• ElectronicCats/flipper-MCP2515-CANBUS — MCP2515 driver for Flipper
• Starmixcraft/tesla-fsd-can-mod — original CanFeather FSD research

License

GPL-3.0

Disclaimer

Educational and research use only. Modifying vehicle systems may void your warranty and may violate local laws. You are solely responsible for what you do with this. Use at your own risk.