Troubleshooting & FAQ
Home > Getting Started > Troubleshooting & FAQ
Troubleshooting & FAQ
This page covers LED indicators, common issues, and frequently asked questions.
LED Reference
Biscuit uses LED color and pattern to communicate device status at a glance. The meanings differ depending on which module or device you’re looking at.
WROOM LED (Pro and Ultra)
| Color | Pattern | Meaning |
|---|---|---|
| Yellow | Solid | Booting up |
| Green | Breathing | Ready, not connected |
| Blue | Breathing | App connected |
| Orange | Fast blink | Downloading firmware update |
| Orange | Solid | Installing firmware update |
| Yellow | Slow blink | C5 module warning |
| Red | Fast blink | C5 module disconnected |
| Red | Double blink | Low battery (below 20%) |
C5 LED (Pro and Ultra)
| Color | Pattern | Meaning |
|---|---|---|
| Yellow | Solid | Booting up |
| Blue | Breathing | Scanning or sniffing active |
| Red | Breathing | Attack in progress |
| Orange | Fast blink | Downloading firmware |
| Orange | Solid | Installing firmware |
DIY / Node LED
| Color | Pattern | Meaning |
|---|---|---|
| Yellow | Fast blink | Searching (Node only) |
| Green | Slow blink | Paired, waiting |
| Green | Solid | Scanning active |
| White | Flash | Sending data |
| Orange | Pulse | Firmware update |
| Red | Solid | Error |
Common Issues
Device not showing up in BLE scan
- Make sure Bluetooth is enabled on your phone.
- Make sure Location permissions are granted to the Biscuit Manager app. Both iOS and Android require location access for BLE scanning.
- Confirm the device is powered on – you should see a breathing green LED (Pro/Ultra) or an active LED (DIY).
- Move closer. Stay within about 10 meters of the device.
- Try closing and reopening the Biscuit Manager app.
Pairing fails or Connect never finishes
- Cancel the current connection attempt.
- Open Settings > Connection.
- Turn off Request Encrypted Connections.
- Return to the Dashboard and connect explicitly from the device panel.
The option is enabled by default and applies to every Biscuit used by the app. Turning it off does not erase existing Bluetooth bonds; it only stops the app from requesting encryption on the next connection. The phone may still encrypt an already-bonded link. A dashboard lock means the current link was verified as encrypted.
iPhone or iPad cannot reconnect after saved phones were reset
After Settings > Device Settings > Bluetooth Security > Reset all saved phones on this Biscuit succeeds, wait for the app to disconnect. Then:
- Open iPhone or iPad Settings > Bluetooth.
- Tap the info button beside the Biscuit and choose Forget This Device, if it is still listed.
- Return to Biscuit Manager, open the device panel, tap + Add new device, and select the Biscuit again.
- Accept the new system pairing request.
The app cannot remove the phone-side Bluetooth bond. The reset clears every phone saved on the Biscuit. If the Biscuit’s NVS was erased with a flashing or maintenance tool instead, Forget This Device in iPhone or iPad Bluetooth Settings too. Separately swipe the old Biscuit from the app’s Known Devices list before using + Add new device; removing that app row does not remove the system Bluetooth bond.
Connected but no scan results
- Check the C5 LED – it should show a breathing blue pattern while a scan is running.
- If the WROOM LED is showing red fast blink, the C5 module may have lost connection. Try power-cycling the device.
- If the issue persists after a restart, the C5 module may need a firmware update. Check the Dashboard for available updates.
Device gets warm during long scans
Firmware 1.6.0 adds automatic processor throttling to Pro, Ultra, and DIY devices. Normal speed is 240 MHz. At an internal chip temperature of 70°C, it drops to 160 MHz; at 80°C, it drops to 80 MHz. These readings describe the chip, not the temperature of the case or battery.
Scans and wardrives continue at the lower speed, though some processing may take longer. Speed returns one step at a time: 80 to 160 MHz after at least 30 continuous seconds at or below 75°C, then 160 to 240 MHz after at least 30 continuous seconds at or below 65°C.
If a valid temperature reading is unavailable for five seconds, the device uses 80 MHz until fresh readings allow the same gradual recovery.
Firmware update failed
- C5 is updated and WROOM switches to fallback: The WROOM radio is 2.4GHz-only, but current Pro/Ultra firmware can automatically recover through the dual-band C5. This recovery route takes longer; keep the device powered and the app nearby.
- Make sure you have entered the correct WiFi credentials in the app. The device downloads firmware updates over WiFi.
- Captive portals, enterprise WiFi, WEP, OWE, and 6GHz-only networks are not supported for firmware updates. Use an open or WPA/WPA2/WPA3 Personal network instead.
- Ensure the device has more than 30% battery (Pro/Ultra). Low battery can interrupt the update process.
- Stay connected to the device in the app for the entire duration of the update. Do not close the app or walk out of range.
- Read the detailed error shown by the app before retrying. Authentication, DHCP, download, image-validation, and boot-rollback errors require different fixes.
- Open the Dashboard device-details sheet after reconnecting to confirm the expected version and running partition.
Common classified network errors:
| Error | What to check |
|---|---|
| Network not found | Confirm the SSID exactly, move closer, and verify the network is not 6 GHz-only. Hidden networks are supported when the SSID is entered exactly. |
| Authentication mode unsupported | Use open or WPA/WPA2/WPA3 Personal. WEP, OWE, and Enterprise/EAP are unsupported. |
| Authentication failed | Re-enter the password exactly, including leading or trailing spaces. |
| Association failed or disconnected | Move closer, temporarily disable aggressive band steering, or retry another matching mesh access point. |
| DHCP timeout | Check that the router has free DHCP leases and is not filtering the device. |
| Captive portal | Use a network that does not require browser sign-in. |
| Cancellation rejected / committed | Keep the device powered. The update has crossed its commit gate, or the previous boot slot could not be safely restored. Let verification finish before taking another action. |
If the app reaches Verifying, do not start another update just because the
BLE link briefly disappears. The device is expected to reboot. Success requires
the target firmware version, running partition, and completed first-boot health
check after reconnection. That health check takes at least 30 seconds. If it
cannot pass, the Biscuit automatically returns to the previous firmware. Not
reported means the older firmware did not expose the partition field.
SD card not detected (DIY / Ultra)
- The SD card must be formatted as FAT32. Other file systems (exFAT, NTFS) are not supported.
- Check that the card is properly seated in the slot.
- Try a different SD card – some cards may not be compatible.
Evil portal not working
- Portal templates must be downloaded first through the app before they can be used.
- An SD card is required on DIY builds for storing portal templates.
- Make sure the SD card is detected (see above).
Wardriving shows no GPS
- Make sure Location permissions are granted to the Biscuit Manager app.
- Confirm that GPS is enabled on your phone.
- GPS needs a clear view of the sky. If you’re indoors, move outside and allow a minute or two for a GPS fix.
Frequently Asked Questions
What’s the range of the BLE connection?
About 10-15 meters in open air. Walls and obstacles will reduce this range. For best results, keep your phone in the same room or pocket as the device.
Can I use Biscuit without the app?
No. Biscuit is a headless device with no screen or buttons for navigation. All control, configuration, and data viewing is done through the Biscuit Manager companion app.
Does Biscuit work on 5GHz WiFi?
Yes. The ESP32-C5 supports both 2.4GHz and 5GHz bands. Biscuit can scan, capture, and attack on both frequencies.
Can I use multiple Biscuit devices at once?
The app connects to one Biscuit device at a time. However, if you have BiscuitNode satellites, you can pair them with your main device for mesh wardriving – the nodes operate independently and relay data back through the mesh network.
Is Biscuit legal?
Biscuit is a security research tool. The legality of its use depends entirely on how and where you use it. You must have proper authorization before testing any network or device you do not own. Unauthorized wireless testing may violate local laws. Always obtain written permission before conducting security assessments.