I was thinking of buying a device that emulates Amiibos for particular Nintendo games. Instead of spending $30-50, I decided to use my under-utilized Flipper Zero.
I used an AI app development tool (Cursor) to create exactly what I wanted, and it works extremely well! The next step is to see if anyone else is interested in using it, purely as a gaming assistant tool. I used to program like 30 years ago, but after a brain injury in the military, I just can't teach myself the newer programming languages.
Anyway.. I have it posted on GitHub if anyone would like to try it out. It got rejected from the Flipper Application Catalog for direct installation, due to copyrighted names like Amiibo, and Nintendo.
If you have Amiibos, it will backup their information in its database. If you download an existing library it will use those as well. The key here is that it will create new UIDs, so it will bypass the single daily use on games like Legend of Zelda Ocarina of Time. The "Blast" feature will create a new UID, transmit it, and then repeat.. So in the game you can just activate the Amiibo feature over and over, and watch the loot drop all around you, endlessly.
It's just been a neat thing to play around with, as a fun little toy to use with Switch / Switch 2, 3DS, etc.
EDIT: I am adding a couple links. Here is a link to the page with the pre-compiled Flipper app (flipper_amiibo.fap) that can be dropped right into your SD card's NFC folder:
And here is a complete Amiibo repository with every known Amiibo, including the two new Ocarina of Time remake Amiibos. Unzip it and drop this in \apps_data\flipper_amiibo\db. This contains the necessary key files as well:
This might sound strange but I can't get any parts for my flipper at all in the UK. I tried other sites and still nothing. Anyone has an alternative or a site I can use to order repair parts for my flipper?
The part I am looking for is a glass panel for the case (not the screen for the case)
If anyone's interested, I built a Flipper Zero app that plays the predefined ocarina tunes from OOT/MM on the Nintendo Switch via usb (and also via the speaker, albeit very quietly). There's also some MIDI support (within the ingame ocarina's range).
It supports both OOT and MM from NSO and the new OOT remake as well.
Feel free to leave some feedback in the repo or any issues you might find. If you want to contribute, PRs are also welcomed.
I built a web app that lets an AI operate my Flipper Zero over Bluetooth, straight from the phone. No PC, nothing to install from an app store, no account. You open a page, connect the Flipper, and ask things like:
"Open Infrared and tell me which remotes I have saved"
"What's on the SD card?"
"Open NFC so I can read a card"
The agent looks at the screen, presses keys, opens apps and reads/writes files until it's done. You watch the live screen the whole time and can take over with the on-screen remote.
Why another one? I wanted something free that runs on any phone — iPhone included — with nothing to install and no server of my own, and that works with whatever AI I already have.
What it does
Live Flipper screen + a small remote (short/long press, hold to repeat)
Tools for the AI: screen, keys, open/exit apps, list/read/write/rename/delete files, device and battery info
Bring your own model: Gemini (free tier), OpenRouter :free models, or any OpenAI-compatible API (OpenAI, DeepSeek, Groq, Ollama on your PC)
Claude mode: use Claude with your normal subscription, no API key. A small relay (Cloudflare Worker) exposes the Flipper as an MCP connector; you approve the login on the phone
Hand-off for Bluetooth apps: Bad KB and Bluetooth Remote switch the Flipper's radio to keyboard mode and drop the connection. The agent gets everything ready, tells you what to do, waits, and continues when the link comes back
USB cable on Android (OTG) and desktop Chrome/Edge, which keeps the Flipper's Bluetooth free
Auto-reconnect, conversation saved on the device, English/Portuguese UI
How it works (for the curious)
It's a static web page: Web Bluetooth → the Flipper's BLE serial service → protobuf RPC (the same protocol the official app uses). Codec written by hand, no dependencies
The Flipper hands out a 1024-byte credit window over BLE and only refills it when it runs out, so writes are chunked to fit — writing past it silently drops data
Key presses go as PRESS → SHORT/LONG → RELEASE in one batch; after each press it waits for the screen to settle before showing the model the result
The screen goes to the model as a 128×64 image (or as text art for text-only models)
Safety
Everything that comes from the Flipper (screen, file names, file contents) reaches the model marked as untrusted data, so a .txt on the SD card can't give the agent orders. The agent is told to only transmit (Sub-GHz, IR, NFC/RFID emulation, Bad USB) when you explicitly ask, and to confirm before deleting or overwriting files. Your API key stays on your device. Please only use it on your own stuff.
Limitations (being honest)
iPhone: Safari has no Web Bluetooth, so you need the free Bluefy browser. No USB on iPhone
It's slower than doing it by hand: each key press is a BLE round trip
Tested on my Flipper with Momentum. Other firmwares should work (it's the standard RPC), but I'd love reports
Is it possible to write a saved NFC tag onto a sticker? I’m a bit rusty and recently dusted off my Flipper, but I can’t seem to figure out how to do it. Any guidance would be appreciated!
I got my Flipper recently and wanted it to do something useful while it sits on my desk, so I built FlipTunes with AI assistance, tested on a Galaxy S25 Edge with firmware 1.5.1. It shows whatever's playing on my Android phone right on the Flipper, and lets me control it.
What it does:
- Album art (dithered to 48x48 for the 1-bit screen), title, artist, player app and a live progress bar
- Play/pause, next/previous, volume, hold Left/Right to seek
- The LED pulses orange in time with the music. The phone works out the song's tempo and the Flipper runs its own metronome, so Bluetooth lag doesn't throw it off
- Gentle buzz when a new track starts, lock mode for your pocket, settings menu (hold OK)
- Works with Spotify, YouTube Music, Samsung Music, anything with media controls
- No internet or accounts, just Bluetooth between the phone and Flipper
It's two parts: a Flipper app (.fap) and a small Android companion app. Both are open source (GPL-3.0), and the repo has a write-up of how everything works if you want to learn from it or fork it.
my flipper keeps disconnecting and connecting itself with my pc,the original cable is lost,if i try to connect it to qflipepr,before it reaches it,file explorer pops out and say this usb is broken and needs a repair
Totally functional but looks ugly. It has a silicone case but I'm just wondering if replacing the shell is worth it. Do you have any store recommendations? Black looks nice, transparent is ok if matte.
I made a cube timer app for the flipper zero, for now only 3x3 scrambles, I’ll eventually add other cubes. If you guys wanna try it out it’s available on the flipper app! Let me know what you guys think :)
I've been working on flipper-companion, an independent desktop + CLI companion for the Flipper Zero, written in Rust with a Slint UI. It started as a from-scratch rewrite of the ideas behind qFlipper and has grown into a full app I use daily.
What it does
USB discovery of Flipper devices in VCP and DFU mode
Firmware: browse the release channels, download, validate and install updates on the SD card; flash .dfu images over DFU with progress
File manager: browse /ext, single-click select / double-click open, properties, MD5 on demand, upload, download, rename, delete, new folder
Live screen mirroring with a remote keypad styled after the device
Backup / restore of the internal storage, factory reset, region provisioning
App catalog: browse the official catalog and custom JSON repositories, then install, update, uninstall or reinstall Flipper apps directly from the list. Multi-select + "Update selected" for batch updates, per-app SHA-256 verification, context menu on right-click.
Application log tab and a status bar that narrates every operation
Install
Linux packages are attached to the release (.deb, .rpm, .tar.gz, amd64 and arm64):
crates.io: flipper-companion (app) and flipper-companion-cli; the libraries are flipper-companion-core, -dfu, -protocol, -update, -app, -project
Status / limitations
Tested on a Flipper Zero (f7, firmware API 87.1), including app installs and checksum verification
The GUI only flashes devices already in DFU mode (the CLI can reboot into DFU)
STM32WB55 recovery helpers exist but are not hardware-validated yet
No self-update, no Windows/macOS builds yet
Licence: AGPL-3.0-or-later (source available). The project is independent and not affiliated with Flipper Devices; "Flipper Zero" is a trademark of Flipper Devices.
I purchased my Flipper One pre-order coupon last night and inside of the confirmation email, it included an image of a "Flipper One Pre-Order Coupon" that was designed to look like your stereotypical old school physical coupon/ticket with a perforated ticket stub on the right side which contained a barcode.
Upon scanning the barcode, it returned the string "OE2NPmqZ9nM" so I immediately pulled open a base64 decoder but after racking my brain as to what I was supposed to do with "8M>js" I realized that maybe I got ahead of myself and decided to go back to the basics and just start with a simple Google search of the original string which wasted no time informing me that it was the ID for the viral Youtube video known as "dolphin bonk" 🐬
SFTV: ridiculously slow and surprisingly unreliable one-way image transfer via sound.
I got both Flipper Zero and Playdate, I was staring at them once and thought, "Wouldn't it be great to be able to send a pic from one to another". It came out they have almost no shared interfaces except for BT which is not available on PD anyways. I also wanted to make it a bit weird. And also I'm kinda missing some old good ways of transferring data like IR and FAX (RIP). And also I like a SSTV thing.
So I spend a few weeks and clauded a SFTV - Slow flipper TV. It allows to send images, text notes and flipper animations from flipper to playdate console using sound. The first attempt was using just regular sound bands which worked but was really annoying. Then I tried to switch to higher freqs and surprisingly it kinda worked. Now whether you hear a sound or not depends on your own hearing config and luck. In my household only 25% of people hears actual high-pitch flipper makes
It works best when both TX and RX are nearby, like 3-10cm
Honestly I have no idea who and why might actually need it, but I had a great time building this.
I’ve been working on NFC Checker, a vibe-coded external app for the Flipper Zero. It lets you capture or load a reference tag, then capture or load the emulated copy you want to test. It compares the data it can read and shows an Emulation Success Score with a per-check breakdown.
It checks UID, protocol, and ATQA/SAK where applicable. When you use saved `.nfc` dumps containing the relevant data, it can also compare MIFARE Classic blocks and known keys, as well as MIFARE Ultralight/NTAG pages. Live reads capture identification data, not a complete memory image.
The score only uses checks that apply to the selected tags. It’s a rough compatibility estimate, not a guarantee: real reader behavior may depend on factors the app doesn’t measure.
I have just published the first realese build, and I’d love feedback from the Flipper community.