06-27-2022 13:47
06-27-2022 13:47
Unit is less than 6 months old. Battery started draining super fast. Some tips here helped but not back to normal. Last night it went into a reboot loop, showing the Fitbit logo over and over again. I tried the hard reset (press and wait 3x on the charger) numerous times to no avail. I removed it from the Fitbit app on my phone and deleted from bluetooth devices. More hard resets, same results. Now it shows the red circle with white X inside. How do I get in line for a replacement unit?
06-28-2022
10:11
- last edited on
03-13-2024
08:42
by
MarreFitbit
06-28-2022
10:11
- last edited on
03-13-2024
08:42
by
MarreFitbit
Hello, welcome to the Fitbit Community forums, @GaryTheDad.
Thank you for sharing all your feedback and that you've been experiencing this inconvenience with your Charge 5 and that you already tried a few troubleshooting steps.
In this case, since you already tried the restart procedure with the charging cable and you continue to experience the same problem with the display and the red X, I recommend that you get in touch with the Customer Support team for further assistance with this. They will let you know how to proceed.
The best way to get help for this problem is to chat with us online or give us a call. You can click here to get connected.
06-28-2022 10:46
06-28-2022 10:46
I have the same problem. They told me the engineers are working on a solution and I have to wait until they resolve the issue. Not what I wanted to hear! I need a working device.
07-08-2022
10:53
- last edited on
03-13-2024
08:28
by
MarreFitbit
07-08-2022
10:53
- last edited on
03-13-2024
08:28
by
MarreFitbit
@gramstarr Thank you for sharing the information provided to you by Customer Support.
The team continues to work to improve the Fitbit experience and your feedback is a big part of that process.
If you're referring to the battery draining too fast, there's an ongoing issue with the GPS chip causing rapid battery drain in some devices and the team of developers will released a new firmware update to address this problem.