05-15-2026
14:57
- last edited on
05-15-2026
19:24
by
ManuFitbit
05-15-2026
14:57
- last edited on
05-15-2026
19:24
by
ManuFitbit
Today, after working generally fine for many years, my Fitbit Charge 5 screen is continuously flashing the Fitbit logo, like it is stuck on a firmware update. The app doesn’t see the device. Have tried all conventional fixes (leave plugged in, turn phone Bluetooth off and on, the 5 presses on the flat side of the charger cord, etc.), but to no avail. Can’t help but think this has to do with the migration of Fitbit to Google (which I did a week ago). Any ideas?
Moderator edit: clarified subject.
Answered! Go to the Best Answer.
Best Answer05-15-2026 19:22
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
05-15-2026 19:22
A warm welcome to the community forums @MMCAMPBELL1.
Thank you for sharing these details about your Charge 5. We truly appreciate the time and effort you put into troubleshooting this on your own.
1. Sync the device in the Fitbit app.
2. Check for available Firmware updates.
Follow the on-screen instructions: Keep the Fitbit device close to your phone during the update. When the update starts, a progress bar appears on the device and in the Fitbit app until the update is complete.
3. Charge the device:
Double-check the connection: Ensure secure connection to the charging cable and that the cable is plugged into a working USB port (computer or UL-certified wall charger).
If these steps don't work:
4. Restart the device: Keep in mind that your data won't be deleted: How do I restart my Fitbit device?
5. Changing the clock face via the Fitbit app can sometimes resolve a black screen issue:
Best Answer05-15-2026 19:22
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
05-15-2026 19:22
A warm welcome to the community forums @MMCAMPBELL1.
Thank you for sharing these details about your Charge 5. We truly appreciate the time and effort you put into troubleshooting this on your own.
1. Sync the device in the Fitbit app.
2. Check for available Firmware updates.
Follow the on-screen instructions: Keep the Fitbit device close to your phone during the update. When the update starts, a progress bar appears on the device and in the Fitbit app until the update is complete.
3. Charge the device:
Double-check the connection: Ensure secure connection to the charging cable and that the cable is plugged into a working USB port (computer or UL-certified wall charger).
If these steps don't work:
4. Restart the device: Keep in mind that your data won't be deleted: How do I restart my Fitbit device?
5. Changing the clock face via the Fitbit app can sometimes resolve a black screen issue:
Best Answer05-15-2026 20:35
05-15-2026 20:35
Thank you for the follow up, @ManuFitbit.
Unfortunately, none of these recommendations work.
Syncing no longer is possible as the Fitbit Charge is no longer visible by Bluetooth. I’ve done everything to try to get it to reappear after unlinking it, including rebooting the phone, as well as attempting to find it with an iPad with which it had worked previously. It’s simply not seen as a Bluetooth-linkable object. This despite being charged for six hours and still continuously flashing the Fitbit logo.
So, options 1, 2 and 5 are ruled out, and option 3 is done.
I’ve attempted a restart (option 4) many, many times to no avail. I had to do a restart about 6 months ago, and did so successfully, so I believe I know what I’m doing. For whatever reason, it won’t restart this time. Just the logo going on and off continuously.
Recommendations now?
Best Answeryesterday
yesterday
I had the same problem a year ago, I left the band in the drawer for about a year in which I tried many times to make it work again with every new suggestion I get but it didn't work until last weak I tied charging it again it did start successfully for only two days and the problem returned again so I guess it's a dead band.