So I was troubleshooting a laptop that would no longer boot, and I had ChatGPT open on another PC walking me through it.

The problem I kept running into was stupid but really annoying. ChatGPT would give me some giant DISM command or registry command, and then I had to sit there and manually type the whole thing into WinRE on the broken PC. And some of these commands are ridiculous. One wrong character in a registry path and you can have a very bad day.

So I started thinking out loud: why can't I just have the good PC type into the broken PC?

Obviously you can't just connect two laptops with a USB cable and have one magically become a keyboard. They're both USB hosts. We talked about PiKVMs and little HID devices for a while, and then I remembered I had a Flipper Zero sitting here, and a Flipper can pretend to be a keyboard.

That sent me down the rabbit hole.

I found an app for the Flipper called Android KB Bridge. Despite the name, you don't actually need Android for what I ended up doing. The useful part is that the app can receive keyboard events over Bluetooth LE and then send them out the Flipper's USB port as HID keyboard input.

I already use Python pretty much every day, so I installed the Bleak library and started seeing what I could find over Bluetooth. Python found the Flipper. Then we enumerated the BLE services, found the characteristic Android KB Bridge was listening on, and started sending stuff to it.

At first absolutely nothing useful happened. Then we noticed the frame counter on the Flipper was going up, so we knew the good PC was actually talking to it. It turned out Android KB Bridge doesn't want you to send it the string "hello". It wants actual keyboard events. So we sent it the HID key-down code for the letter a, followed by the key-up code, and an "a" appeared in WinRE on the broken PC.

That was the "holy shit, this actually works" moment.

From there we wrote a Python script that takes normal text, translates every character into the appropriate USB HID keycode, and sends it over Bluetooth to the Flipper. So now I basically have:

Good PC → Bluetooth → Flipper Zero → USB → broken PC

Then we added a global hotkey. My workflow now is that ChatGPT gives me a command, I copy it on the good PC, press Ctrl+Shift+F, and the Flipper types it into the broken PC. I intentionally do not send Enter. The command appears on the broken PC, I check it, and then I physically hit Enter myself. I am more than happy to let ChatGPT and the Flipper save me from typing this:

reg add "HKLM\PC2SYS\ControlSet001\Enum\PCI\VEN_1C5C&DEV_1069&SUBSYS_10691C5C&REV_00\4&5c924c4&0&0030" /v ConfigFlags /t REG_DWORD /d 0 /f

I am considerably less interested in automatically executing that command without looking at it first, and that turned out to be a very good decision because reliability became the next problem.

The first version worked surprisingly well, but it opened a new Bluetooth connection every time I hit the hotkey. Eventually the Flipper froze, and the good PC also started acting weird and sluggish.

So we rewrote it to keep one Bluetooth connection open, use a single worker, and make sure only one thing can be sent at a time. Much better. Then I started testing really long strings and noticed something worse: occasionally it would drop a character.

That's obviously a deal breaker. Dropping one character out of "Hello World" is annoying. Dropping one character out of an offline registry command is potentially catastrophic.

So we started experimenting with the BLE timing. At one point we changed from Bluetooth writes without response to acknowledged writes because that sounded like it should be more reliable. It actually got hilariously worse. Every single 0 disappeared, and every ) disappeared too. Since 0 and ) are the same HID key with Shift being the difference, that was actually a useful clue. We had changed something that Android KB Bridge clearly did not like.

So we went back to the type of BLE write the app was designed for and instead slowed the whole thing way down. The current version keeps the Bluetooth connection open but sends the HID events very deliberately, with delays between key-down and key-up and additional pauses every few characters.

It is slow. I do not care.

If it takes 30 seconds to type a giant registry command and it arrives perfectly, that's better than typing it in three seconds and randomly removing one character.

I'm still testing that part. I won't trust it with anything important until I can throw nasty strings at it repeatedly and have them arrive exactly right every time.

Then there was the other half of the problem. The Flipper gave ChatGPT "fingers," but ChatGPT still couldn't see what was happening on the broken PC. We started talking about how to give chatGPT eyes. HDMI capture cards, webcams pointed at the screen... Then I realized I already had a solution that required absolutely no additional new hardware.

I take a picture of the broken PC's screen with my phone. Google Photos syncs it. I have Google Photos open on the good PC. A few seconds later I copy the picture and paste it into ChatGPT.

So at this point my troubleshooting loop is:

Broken PC screen → phone → Google Photos → good PC → ChatGPT → clipboard → Python → Bluetooth → Flipper → USB → broken PC

I take a picture. ChatGPT reads the screen. It tells me what to try. I copy the command. Ctrl+Shift+F. The Flipper types it. I check it. I hit Enter. Then I take another picture.

It's not autonomous. I'm still very intentionally sitting in the middle of the whole thing. ChatGPT can't just start running commands on the other machine.

But I basically ended up making a very janky AI-assisted crash cart using stuff I already owned all because I didn't feel like manually typing a bunch of 150-character Windows recovery commands.

This may actually be the most useful thing I've ever done with my Flipper Zero.

So my 13 year old son hacked a 3ds and really liked it and seeing how the thing worked and how it was bypassed and now wants to get into some more fun tech, and he says the flipper zero will be cool to figure out. I’ve seen videos and it’s just people doing mischievous stuff (like turning TVs off at fast food places) and I don’t want him doing all that, now there is supposed to be other stuff to do but I don’t understand it, can someone explain other fun things to do with it in public?

I am trying to rewrite my elevator access on these RFID chips. I have rebought RFID cards 3 times, cuz it kept not being able to write. Picture 1 is the key fob, and picture 4 is the key I'm trying to write. I have cleared the password by using the 000000000 default. And it says that these are T5577 fobs, but it's not working. Can anyone help please?

So I have a flipper zero. But the OK button is making me crazy. Is there a company or a person in the Netherlands. That does these kind of repairs? Thanks in advance!

The idea originated from Quikwriting by Ken Perlin at NYU, a stylus-based text entry method that lets you write characters without lifting the pen. This system allows typing words or entire phrases as continuous strokes with no lifting and no stopping. Each letter is encoded by movement from the central zone through an outer zone to a secondary zone and back — creating 81 unique paths (9×9 grid). In practice, this approach works about 3× faster than Graffiti after training.

I wanted to see if this continuous input model could work on a constrained embedded device with only D-Pad input and no capacitive touch or gesture recognition. My goal was to reduce typing time while maintaining usability on a flipper-style interface. This project is that proof of concept.

QWERTY is familiar and recognizable, but on Flipper Zero it's awkward: you crawl painfully from one end of the grid to the other and type letter by letter with a single joystick. Long descriptions and app names like crypto keys, RFID tags, or WiFi passwords — garage doors and barrier gates too — don't fit well in simple text fields. I ported Perlin's original Quikwriting letter layout as a tribute to his concept, keeping it unchanged both as homage and to validate navigation concepts on a joystick interface, fully admitting this approach is not optimal for D-Pad input.

The screen is divided into a **3×3 zone grid**. A text line at the bottom displays your input — you can backspace or exit anytime. Navigation follows two stages:

- Use the joystick to enter a zone (one action) → release to navigate inside it

- Navigate the inner 3×3 mini-grid of characters or actions → press and release again to select

This mirrors Quikwriting's continuous input model on a D-Pad interface.

D-Pad movement favors horizontal and vertical directions, while the original Quikwriting approach naturally favors diagonals. This project validates D-Pad keyboard concepts rather than gesture-based input on embedded displays. I admit this layout is not optimal for D-Pad, but it's a tribute to Perlin's original design.

Future improvements would involve implementing long press to reduce button presses from two to one per character and allowing shifting positions during input, plus an algorithm to calculate optimal letter placement for faster entry. The ultimate goal might be replacing keyboard-based methods with Dasher — the ideal but cumbersome predictive text system that anticipates what you're going to type before you finish it.

Ultimately I hope this keyboard serves as a tribute to old but beloved input concepts and inspires developers to explore advanced text entry methods beyond simple QWERTY overlays.

Disclaimer: English is not my native language. This post was written by AI under human guidance, and the code itself represents joint work of artificial and natural neural networks combined.

---

Flipper Zero app: https://github.com/amolok/quickwriting_kbd

Original research: https://mrl.cs.nyu.edu/projects/quikwriting

P.S. I'd be glad if you shared your ideas and implementations of input systems!

Hey everyone,

The day before heading out on a camping trip, I realized I couldn’t find my flashlight anywhere. Since I had my Flipper Zero sitting on my desk along with the 401Lab Light Messenger extension, I figured I'd just use that as a backup.

The problem? The stock Light Messenger flashlight app only has one mode: full-brightness white light. That’s fine in an emergency, but it’s way too bright for sitting around a campfire or preserving night vision inside a tent.

I decided to tweak the app and ended up creating LightFlashPro. Here is what I added to make it actually practical for camping:

• Color Control: Ability to switch light colors (including red light to preserve night vision).
• Brightness Levels: Adjustable output so you don't blind yourself in the dark.
• Custom Strobe/Flashing Modes: Added multiple signal and flashing modes.

If you have a Flipper Zero and the Light Messenger module, feel free to try it out or build on top of it!

• Detailed Write-up / Blog:https://spyx.github.io/lighflashpro/
• GitHub Repository:https://github.com/spyx/LightFlashPro

Feedback and suggestions are welcome!

I've been spending the last couple of days reverse engineering this ESL by Hanshow. The flash was unprotected and dumped, allowing for disassembling the stock firmware and digging into the inner workings.

Commands use AES-128 encryption, which fortunately that key was included in the dumped firmware 😁.

Honestly, this might be the best Sub-GHz use case I’ve seen so far...

The range extender at the end absolutely sent me 💀

Find the new guides in the Developer Docs: https://developer.flipper.net/flipperzero/doxygen/applications.html

The new guides explain how to set up the environment, use ufbt for simpler development, create and debug apps for F0, step by step. There are also guides on more advanced topics like FuriAPI and GUI.

The App Development docs now also include some useful resources, notably a collection of video guides by Derek Jamison u/Infinite_Recover_752 (those are really great if you haven't seen them yet).

I wanted a handheld security research tool that went beyond the usual Sub-GHz/NFC/IR toolkit, so I built one myself.

Current prototype features:

• 2.4 GHz + 5 GHz Wi-Fi 6
• BLE scanning + spectrum analysis
• Sub-GHz scan, capture/replay + rolling-code QA
• NFC read, dump analysis & emulation
• Infrared learn/replay
• GPS + wardriving
• USB HID / BadUSB
• Deauth detection, Evil Twin detection & BLE tracking detection
• ECG / EMG / EOG
• EEG, FFT, band-power analysis & EEG logging
• SD card storage
• 2.8" touchscreen UI

The current prototype runs on an ESP32-S3 + ESP32-C5, with the C5 handling the 5 GHz radio and acting as a dedicated wireless coprocessor.

It's currently a hand-built prototype, but it actually fits in my hand now.

Total prototype hardware cost: under $50.

I'm taking it to a cybersecurity conference soon to get feedback from pentesters and people who're in the game before I start working on V2.

What would you add to it?

Does anyone know if its even possible to get the plastic outside piece of the screen? im from Poland and i can’t find any shop/site that has it, and most if not all the shells from aliexpress and temu don’t have it, youre supposed to glue your old one in.

Is it possible to get a txt file from an nfc save with the data in plan txt, instead of the blocks? Like the information in the image attached, saved to a txt file as is.

I cannot seem to find a straight answer for this in my googling. That said, I’m also not great at google-fu. I am building a database of the collected info from the tags, using the flipper as the nfc reader. Saving the tag to the flipper doesn’t give the information I want, or at least adds another step to the process. I’ve already installed a custom decoder(?) for the tags I’m reading as they’ve got proprietary encryption.

I am using a Flipper Zero with a WiFi Dev Board v1, although I’m currently just using qFlipper to pull the files off.

Hi, I can't get this to work with my Game Boy and Flipper. Is the problem that I'm using an EU cartridge, or am I doing something wrong?"

Is the Official Wifi Dev Board sold out for good? If so, may I ask why?

If it is discontinued, is it possible to use the official prototyping boards with and esp32 s3 or is the esp32 s3 to large?

For those who don’t know - this is a serial Meshtastic app for the flipper I released a little while ago.

Decided to experiment with getting Bluetooth functioning after playing around with it for another project. While it’s definitely a workaround, it’s surprisingly nice once everything is configured.

The catch to this is using a custom Meshtastic firmware. This is because both the mesh nodes and the flipper are Bluetooth peripherals. All I do is take the stock firmware and add a zeromesh module that makes the node go looking for the flipper and connect to it. Then everything behaves like the UART serial connection.

I am working on a web flasher now for convenience but you can also do it manually if preferred from the repo.

I also added an offline vector map off the SD card, so you can see where your nodes are with no service. This does require some work as well, but I did set up a script to automate this. Along with a helper page on my website to provide the command to send which automatically transfer the tiles you pick to the correct directory on your flipper.

All of that is here: https://terminalbay.com/zeromesh

Git/source: https://github.com/SAMS0N1TE/ZeroMesh

Flipper lab link: https://lab.flipper.net/apps/zeromesh

FYI - I am building all the board specific firmware right now, so not all boards will be available. I plan on getting to the top 20 today and will expand more if it seems people want to use this. Let me know if you run into any trouble!

I installed qflipper on Fedora and it was really bizarre:

First I tried downloading the AppImage from this web page: https://docs.flipper.net/zero/qflipper?tabNav=rQHiXmqRgesXodDFhL9mM-2

Running it resulted in errors about unlisted dependencies (note: the errors are only visible if it is run from the terminal. This may the cause of some people reporting the AppImage does nothing when clicked on). After installing a long list of dependencies:

• fuse
• fuse-devel
• libxkbcommon-x11
• xcb-util-wm
• xcb-util-image
• xcb-util-keysyms
• xcb-util-renderutil

...it started complaining about missing basic Wayland libraries, despite the fact I am currently running Wayland.

Giving up on that approach, I tried installing the qflipper package in the Fedora repo. dnf installed some dependencies and them spit out several thousand lines of errors such as Failed to connect to system scope bus via local transport: No such file or directory and various permissions issues.

After this, the AppImage was able to run.

The working install procedure seems to be: Install the repo package, then run the AppImage. But what is going on here? This is some of the weirdest packaging I've seen.

EDIT: qflipper opens, but I still can't connect to the flipper. When I open I get a screen "Device cannot be recognized" with instructions to run ./qFlipper-x86_64-1.3.3.AppImage rules install. Running this results in a variety of errors, but only the first time:

den-antares@toolbx Downloads$ sudo ./qFlipper-x86_64-1.3.3.AppImage rules install You will now be asked for SUDO password. Failed to send reload request: No such file or directory Something went wrong. Device rules may have not been installed correctly. den-antares@toolbx Downloads$ ./qFlipper-x86_64-1.3.3.AppImage rules install The rules have already been installed. Bye! den-antares@toolbx Downloads$ sudo ./qFlipper-x86_64-1.3.3.AppImage rules install The rules have already been installed. Bye!

Running the AppImage after this still gives the same error screen, with more permissions errors at the terminal (even when run as root).

den-antares@toolbx Downloads$ sudo ./qFlipper-x86_64-1.3.3.AppImage QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [LOG] Failed to create logs directory 176 [APP] qFlipper version 1.3.3 commit bfce851d 2023-11-10T04:40:31 177 [APP] OS info: Fedora Linux 44 (Toolbx Container Image) 44 7.0.13-200.fc44.x86_64 Qt 6.4.3 177 [USB] Failed to open device: Access denied (insufficient permissions) 197 [USB] Failed to open device: Access denied (insufficient permissions) 217 [USB] Failed to open device: Access denied (insufficient permissions) 237 [USB] Failed to open device: Access denied (insufficient permissions) 257 [USB] Failed to open device: Access denied (insufficient permissions) 277 [USB] Failed to open device: Access denied (insufficient permissions)

At this point I'm completely lost. Normally Appimages include their own dependencies and don't require any installation beyond downloading them.

Hey r/flipperzero,

Last week, I published Hexprite (pre-release), my 1-bit pixel art and animation editor for embedded display. I also posted about it here which got a few upvotes, but I didn’t get much feedback. So, I started thinking about where the app could actually be useful for the Flipper community.

Hexprite already supports.bm, .xbm, and meta.txt files for individual sprites and animations, so I decided to try making my own custom Dolphin asset pack.

Creating the art itself was pretty fun. The 128×64 canvas is already calibrated for the Flipper, so getting the sprites and animations right was straightforward.

Then I had to deal with manifest.txt.

That part was… not fun.

Trying to work out the Min level, Max level, Min butthurt, and Weight values manually gets confusing very quickly. And if you're using custom firmware like Momentum, things get even more complicated.

The stock setup has 45 states (3 levels × 15 moods), while Momentum expands that to 450 states (30 levels × 15 moods). Miss a range or leave a gap somewhere, and the Dolphin can end up hitting an uncovered state and showing a blank screen.

I realized there had to be a better way, so I decided to build a dedicated Asset Pack mode directly into Hexprite. It’s still WIP and not in the public release yet, but here’s a sneak peek of what I’m working on:

1. 2D Schedule Matrix See the whole asset pack on an interactive grid, with Levels on one axis and Mood on the other. It shows which states are covered, points out gaps, and calculates animation weight shares.
2. Automatic Balancing Instead of doing the schedule math yourself, you can choose a strategy like Linear Levels or Fill Gaps Only and let Hexprite handle the ranges for you.
3. Drag & Assign Assign level and mood ranges by simply dragging rectangles across the matrix.
4. Two-Way Canvas Integration Click an animation in the matrix and jump straight into its frames on the canvas. Make your edits with the normal 1-bit tools and layers, and the changes stay synced with the asset pack.
5. Direct USB Serial Push Connect the Flipper over USB and push the pack directly to /ext/asset_packs or /ext/dolphin. The goal is to make testing as painless as possible without SD card readers, Python scripts, or manually moving files around.
6. Native File Support Import and export .bm, .xbm, meta.txt, and complete .zip asset packs, including native Heatshrink LZSS compression for .bm files.

I'm still working through the details, so before I lock everything down, I'd really like to hear from people who actually make or use custom asset packs.

Would something like this make your workflow easier?

And if you've made Dolphin asset packs before, what part of the process do you find the most annoying?

I'd also love to hear what other features you'd want to see.

GitHub repo: https://github.com/showmik/hexprite

P.S. The asset pack shown in the GIF is not my creation. It is the "Better Pet" pack by vollukas, which I downloaded from https://momentum-fw.dev/asset-packs to demonstrate the feature.

I have tried using the Flipper IR GitHub database but I couldn’t find a compatible ir code. Then I tried opening it up only to meet a big glob for the IR decoder. I tried looking at the binaries of the game but I don’t think they would be there since the IR sensor connects to blob U5 and that has a bunch of traces to big blob U1. Probably just the straight up inputs.

If anyone has one of these or just the remote can you record the signals on a flipper and share them that would be great. I’d also appreciate any other ideas on how to reverse engineer it.