07-19-2022 11:26 - edited 07-20-2022 13:42
07-19-2022 11:26 - edited 07-20-2022 13:42
We’re excited to announce that a firmware update for Charge 5. Some of you might already have this update available. If you installed it, let us know what you think!
We release updates to customers in phases. If you don’t see it, check the Fitbit app in a few days, and you’ll see a message when you can install the update. We appreciate your patience while we get this update to all of our customers.
WHAT’S NEW AND FIXED
See What's changed in the latest Fitbit device update? for release notes.
HOW DO I UPDATE?
See How do I update my Fitbit device? for step-by-step instructions for updating your Charge 5. If you run into difficulty updating, see Why can't I update my Fitbit device?.
We’re interested in hearing your feedback on this update! Let us know what you like! If you encounter unexpected behavior during or after your update, please post the details below.
Answered! Go to the Best Answer.
09-15-2022 10:29
09-15-2022 10:29
@SunsetRunnerThey have no fix as far as anyone knows. Only replacement. They have been bricking these the Charge4/Charge5/Versa2/Versa3 models with this latest update since about the end of July.
The FitBit support folks will never respond here, only the moderators who cannot help but only offer advice.
Contacting the support as you have done is your only option.
09-15-2022 11:48
09-15-2022 11:48
My overall Fitbit Charge 5 experience is dismal at best. Charged, reset, updated Firmware, changed clock faces, adjusted GPS, etc. Will not last one day with normal use. Given the number of threads out there on "Fitbit Charge 5 losing charge.....", there is clearly an ongoing issue.
09-15-2022 11:54
09-15-2022 11:54
09-15-2022 12:35
09-15-2022 23:23
09-15-2022 23:23
So, as already announced by many people, my Charge 5 is replaced.
And since I go on vacation today, she will definitely not reach me before.....
09-16-2022 12:38
09-16-2022 12:38
I just got my Fitbit replacement charge five since the firmware upgrade ruined it now this one is asking for a firmware update. Has the problem been fixed should I update My new charge 5 or am I going to have the same issue I had before I’m leery of doing an update- I would like to hear from Fitbit before I do the firmware update on my brand new replacement Fitbit
09-16-2022 13:08 - edited 09-16-2022 13:15
09-16-2022 13:08 - edited 09-16-2022 13:15
@SunsetRunnerIt will be good to hear from FitBit officially if they will but they do not do so here if the past is any indication..
So far the Fitbit Support folks have just said keep updating until you end up with one that doesn't brick, but I have seen nothing at all that says they are working on a fix. I have to think they are, but I have seen nothing official ever about it. They seem to only mention it to a few people over the phone, but never an official acknowledgement.
Just more paddling down the river of denial, officially.
Notice how the Twitter support Fitbit folks will never discuss anything in public, only through DM... It of course obviously appears that the plan is to hide the reality so no one notices.
This is damaging so many devices and costing so many customers their $100+ working FitBits, I do not see how that is rational...
Like many cloud companies that control so much of your devices and services, if they refuse to officially acknowledge it, it doesn't really exist and never happened. They seem unwilling to accept the responsibility.
If you think about it, everyone is effectively being forced to play a firmware bricking lottery and when they lose, they are sent a $100-$175 bill as punishment for daring to be out of warranty.
Regardless of the actual intent, that is the effect.
09-16-2022 13:28
09-16-2022 13:28
I kept getting the notification to update it so I finally called them up and told them point blank I was terrified of updating it because of the last time I updated it I lost the Fitbit for almost 3 weeks. They assured me that it was fixed and it was basically a software in compatibility issue with the phones and Fitbit but everything was fixed now so I did update it and hopefully it will be OK so far it’s fine
09-16-2022 13:40
09-16-2022 13:40
09-16-2022 15:01
09-16-2022 15:01
09-16-2022 15:14
09-16-2022 15:14
@SunsetRunner
Please let us know if you start having any problems with your updated replacement.
Bill
09-16-2022 15:55
09-16-2022 15:55
09-16-2022 16:01
09-16-2022 16:01
09-16-2022 20:52
09-16-2022 20:52
I called them and updated it while on the phone with them and it seems to be fine they assured me that the glitch is gone and that the clash between the software’s on the phone and on the Fitbit is fixed
09-16-2022
20:54
- last edited on
09-27-2022
12:44
by
DavideFitbit
09-16-2022
20:54
- last edited on
09-27-2022
12:44
by
DavideFitbit
That’s how I was feeling. I called them yesterday prior to updating and they assured me that the problem that we were all having with the charge five and the firmware update has been eradicated. I did update it last night and so far no problem I am keeping my fingers crossed they are aware that a lot of people are very hesitant to update the Fitbit. She actually stayed on the phone with me while mine was updating.
I will definitely do so so far so good
09-19-2022 11:41
09-19-2022 11:41
Unable to download the update. Been trying since it came out. Have an Android phone.
09-19-2022 16:20
09-19-2022 16:20
My charge-5 purchased in April 2022 became non-functional in July following this update. After multiple chats with customer service, I received a replacement in early September 2022 which came loaded with 1.171.50 update and has been working fine (i.e., just like my first Charge-5 prior to the update).
I had also deleted the FitBit app from my iphone, and then re-installed it prior to attempting to pair my "new" Charge-5. Maybe that helped?
From the huge number of posts on these forums (and from my own experience), there DOES seem to be some destructive interaction between some vintages of Charge-5 hardware, Firmware, and FitBit app.
09-19-2022 17:01
09-19-2022 17:01
09-19-2022 17:17
09-19-2022 17:17
09-19-2022 17:31
09-19-2022 17:31
If mine didn't already have the newer software, I'd skip the update too. There is some combination of hardware + 1.171.50 software + app that is deadly, and it's unclear what's "safe".