04-20-2020
11:14
- last edited on
08-20-2020
17:08
by
MatthewFitbit
04-20-2020
11:14
- last edited on
08-20-2020
17:08
by
MatthewFitbit
Hello!
all 5 lights on my my Fitbit are quickly flashing continuously whilst on charge, it won’t sync to my app, nor will it charge at all, as soon as I take it out of the charging cable all lights go off as if it’s dead !! Anyone got any advice, I’ve tried resetting it but it won’t even vibrate
04-20-2020 13:10
04-20-2020 13:10
Any idea what is going on with it?
04-20-2020 13:27
04-20-2020 13:27
the same thing happened to mine at about the same time you're reporting. I followed the reset instructions but it doesn't even vibrate.
04-20-2020 14:10
04-20-2020 14:10
How did you reset it? Mine has no buttons to do that. It’s a Flex2
04-20-2020 16:48
04-20-2020 16:48
The reset button is on the bottom of the charger. Instructions are to press the reset button 3x in a row while the Fitbit is in the charger. It says it should vibrate each time you press it.
04-20-2020 16:50
04-20-2020 16:50
I called the help line and after walking through the troubleshooting, they said it can't be fixed and sent me a 25% off coupon for a new Fitbit.
04-23-2020 03:40
04-23-2020 03:40
I bought new one, it's been never rechargeable, have the customer service has solved the problem
04-23-2020 04:20
04-23-2020 04:20
04-27-2020 12:46
04-27-2020 12:46
mine started last night when charging. It continues to flash after I take it out of the charger?!? Also can't reset. Is it bricked? Stupid Fitbit
04-27-2020 14:56
04-27-2020 14:56
According to tech support, yes. If you’re outside of the 1 year warranty period and you call them they’ll send you 25% off of a new one. I really think they’ve done this in their system to force those of us with older models to replace them.
05-03-2020 11:11 - edited 05-03-2020 20:17
05-03-2020 11:11 - edited 05-03-2020 20:17
I recently ran into this problem, and was able to get my Flex 2 running again by putting the device into the charging port and pressing on the reset button continuously until it responded (took at least 5 minutes). See if this solution may work for you.
Things I've noticed while fixing this issue were: