TL;DR: Thought my Nextbase 622GW’s bluetooth module was dead. ChatGPT reverse engineered the firmware and found that the internal storage couldn’t save its Bluetooth configuration (probably caused by a firmware update). An SD card format, or camera hard reset doesn’t touch that area. Running the camera’s internal formatter permanently restored Bluetooth functionality.
_______
I’ve owned my Nextbase 622GW since 2022. After about a year bluetooth stopped working.
It’s annoyed me ever since. The camera still recorded, but whenever I wanted footage I had to take out the SD card and plug it into my Mac, find the files etc. I’d been thinking about buying a new dashcam because of this.
Today I decided to see whether ChatGPT could investigate it with reverse engineering tools. I didn’t expect much as I’d assumed the bluetooth module failed.
I installed Ghidra and Rizin and asked GPT-6.1 Sol to examine the firmware and work out what was going on. It took roughly an hour.
Even getting the camera to show the USB/firmware-update screen was a headache. A USB-A to USB-C adapter didn’t work for me, but worked with a cheap dongle.
I was amazed to find out that the Bluetooth radio still worked, the camera just couldn’t save the configuration it needed to start it properly.
The logs showed the camera bluetooth app trying to create a file called bt_config.xml on an internal storage area called Drive A. Creating that file failed, and bluetooth initialisation then aborted. The camera was also reporting zeros for the bluetooth address which is why a hardware failure seemed plausible.
The camera’s format/reset option clears the removable card used for recordings. Drive A is separate internal storage that holds configuration and pairing information, and formatting the SD card leaves it untouched, and a camera hard reset wouldn't fix it.
Before applying a permanent fix, GPT tested by giving the bluetooth software a writable directory in RAM.
It generated its own configuration, bluetooth started, I could connect through the new iOS Nextbase app and get at the camera and recordings.
The permanent fix used the camera’s own internal Drive A formatter via a diagnostic startup script.
Afterwards, the stock software recreated its configuration and I paired my phone. The pairing survived numerous restarts, including a final normal boot after the diagnostic scripts were removed, so it wasn’t relying on the temporary RAM setup.
I’ve added the findings and repair tools to the GitHub repo below. I had ChatGPT package it as a Windows EXE and MacOS apps for Intel and Apple Silicon.
Python is included, and the source code and script launchers.
Nextbase 622GW Bluetooth repair
Enjoy!