Troubleshooting¶

For guides to troubleshoot some of the more obscure Flipper Zero issues, see the items below.

Flipper Zero¶

Forgotten/unknown Flipper Zero PIN¶

See the official docs page for PIN reset instructions.

If you are still having problems, browse your MicroSD card and delete the hidden .int folder and try the above steps in the docs again.

Flipper Zero is experiencing lag or behaving slow¶

This is an issue that is most commonly caused by certain development features being enabled and putting strain on the CPU of the flipper. To fix this, run through the following steps:

Press the center button on your flipper
navigate to Settings
Scroll down and select System
Scroll down again and check that the following options are set:
- Log Level: Default
- Debug: OFF
- Heap Trace: None

After these are set, press back and leave the menu. Reboot your flipper. The issue should not be gone.

Infrared or SubGHz does not appear to be working¶

This is an issue that can occur from switching between firmwares. To fix this, try the following:

Connect your flipper to your PC
Open Up qFlipper
go to your SD card files
make sure Show Hidden Files is enabled
on your SD card, locate and delete the /.int folder
- This will delete out the old misconfigured settings from past firmwares.
Go back to qFlipper, and reinstall the latest firmware
Unplug and try using your Flipper Zero again to verify the device works as expected.

Windows¶

Note

Try the Official qFlipper Troubleshooting Guide FIRST!

If those steps did not help, you may continue below.

Flipper Zero not appearing under Bluetooth in Windows 11¶

If you are attempting to use either badusb in bluetooth mode or the remote function of the flipper, Windows 11 now requires a new setting to see the flipper.

Open Settings from your start menu
Go to Bluetooth & Devices
change Bluetooth Device Discovery to Advanced

Your Flipper Zero should now be discoverable.

DFU mode is not being recognized by qFlipper¶

This commonly occurs when a driver is conflicting with the DFU driver. To remedy this, follow the steps below:

Download the Zadig driver tool
With you Flipper Zero unplugged, do the steps necessary to put your Flipper Zero into DFU mode
Open the Zadig tool
In the Zadig tool, choose Options, then List all devices
Choose the DFU in FS mode item
Make sure the winusb driver is selected, then press Reinstall driver

Close the tool out, unplug your Flipper Zero and plug it back in. qFlipper should now recognize your flipper.

Linux¶

Error while loading shared libraries: libOpenGL.so.0¶

This error most commonly occurs on Debian, but can occur on some other distros as well. To fix this, you will need to install the libopengl0 package.

On Debian, this can be done via sudo apt install libopengl0.

Flipper Zero not recognized by qFlipper¶

Typically this issues is the result of not installing the udev rules. To fix this, follow the steps below:

open a terminal and cd to the directory of your qFlipper appimage
run ./qFlipper-x86_64.AppImage rules install
once this reports it installed successfully, reboot your pc

Alternatively, you may try running qFlipper with sudo, however this is not ideal and has security implications.

Fedora qFlipper not detecting Flipper Zero¶

First, verify you installed the udev rules from the steps detailed in this page. If it still is not detected, you may be experiencing a known conflict between the udev rules of Flipper Zero and the udev rules of the sysdemd-udevpackage. This will require you to manually apply a fix related to one of the udev rules.

See this Github issue for further details.

Ubuntu cannot run the appimage¶

This is likely due to a missing library.

Verify you have enabled the Universe repo, and updated your local apt database using apt update
run sudo apt install libfuse2 to install the missing libfuse2 library.
make sure your appimage is set as executable

The appimage should now run.