01-05-2019
06:15
- last edited on
11-17-2020
13:05
by
MatthewFitbit
01-05-2019
06:15
- last edited on
11-17-2020
13:05
by
MatthewFitbit
So my dad was complaining that the heart rate monitor wasn’t working and then all of a sudden the Fitbit logo popped up with a 001. This is a Fitbit Charge 3. I tried charging it and the screen does not Change.
Moderator edit: subject for clarity
02-03-2019 06:14
02-03-2019 06:14
Thank you this worked.
02-04-2019 03:51
02-04-2019 03:51
Great to see you around @Workfmhomdiva.
I am glad to hear that the instructions provided here worked and that your tracker is now working properly. If there is anything else we can help you with, do not hesitate to post it.
Keep the stepping up!
02-08-2019 13:23
02-08-2019 13:23
Thank you, this worked first time. 😊
02-08-2019 18:13 - edited 02-08-2019 18:15
02-08-2019 18:13 - edited 02-08-2019 18:15
I'm having this same issue. I attempted to reset when it was plugged in by pressing the side button but the Fitbit Charge 3 never turned off. The "001" remains displayed.
02-10-2019 03:11
02-10-2019 03:11
Hey all, hope you are doing fine.
@Shelley2310, it's great to hear that your Charge 3 is now working properly. If there is anything else we can help you with, do not hesitate to post it.
@ghostRansom, I appreciate all the efforts in trying to fix this 001 error by yourself. Since the restart process didn't work, I recommend performing a long restart by doing the following:
Let me know the outcome.
02-12-2019 05:48
02-12-2019 05:48
02-13-2019 16:13
02-13-2019 16:13
I got 001 error screen. Tried the restart steps and it worked for me. I had to try pressing the button, couple of times as it is hard to press it with charge plugged in. Thanks
02-14-2019 03:14
02-14-2019 03:14
Thanks for the update @ghostRansom and @Ps19.
I am glad to hear that your trackers are working properly now. If there is anything else we can help you with, do not hesitate to post it.
Keep the stepping up!
02-15-2019 07:20 - edited 02-15-2019 07:33
02-15-2019 07:20 - edited 02-15-2019 07:33
deleted.
02-19-2019 14:16
02-19-2019 14:16
Hello! I just had this 001 error code and Fitbit logo show up on my Charge 3 about an hour ago. I have done all the required steps in your instructions and still nothing. Please help!
02-19-2019 15:34
02-19-2019 15:34
@Justisse - the steps didn't work for me either. I left it uncharged overnight which allowed the device to run out of battery. The next day, I plugged it back in and it reset and then worked. The restart steps didn't work for me...it would just vibrate twice.
02-22-2019 10:02
02-22-2019 10:02
Mine is doing the same thing! Very frustrating! I’ve only had it 2 months and have had to rest it twice. Not with this 001 error showing and my charger is at home I have no way to fix it at the moment. I wish I could have my money back!!
02-22-2019 10:04
02-22-2019 10:04
Please add me to this list. Very frustrated!!!
02-22-2019 10:06
02-22-2019 10:06
So do I! I’m tired of it not working properly!
02-25-2019 04:55
02-25-2019 04:55
have tried the restart process by my fitbit has the same error!! how do I fix this?
02-25-2019 15:46
02-25-2019 15:46
I am having the same problem -error 001.
I am trying to hold down the button but nothing happening.
I am am so disappointed
None the wiser from the advice in the posts. What am I supposed to do???
Also tried fitbit verse that. malfunctioned so returned it. Now this is happening on my new Charge 3. Really this is very poor. Help me out r. Will return this one too for a refund from John Lewis.
02-25-2019 20:58
02-25-2019 20:58
I just received the same 001 error on my Charge 3. I put the Fitbit into the charger and pressed the button - got the smiley face. Put it in the charger again - the screen went black. After about 30 seconds, a box (battery icon?) with 4% in it appeared. I'm like, what??? I charged it to 100% yesterday - the battery charge icon on the Fitbit was green. Checked the app on my phone - the battery charge icon in the upper left was green - then suddenly, as I watched, it turned red. It's now orange as the Fitbit continues to charge. It's now at 43%.
I hope this fixes the problem - I'm reporting this just in case the info is useful to you. But why would the battery suddenly drain??? I charge it every Monday when the battery still has 15-20% charge left. So this seems weird and troubling.
02-26-2019 04:13
02-26-2019 04:13
@LottieD- the same thing happened with mine - I wasn't able to restart it once it was plugged in (like was suggested from the Fitbit team). However, I let the device sit (off the charger) overnight and then it ran out of battery. I then plugged it back in and was able to boot up the device without the error.
Try letting it run out of battery and see if that works -
02-26-2019 07:57 - edited 02-26-2019 08:01
02-26-2019 07:57 - edited 02-26-2019 08:01
Welcome to the Fitbit Community @LottieD- and @Kellyyyyy! Sorry to hear your Charge 3 trackers are displaying error 001. I really appreciate your efforts while troubleshooting this, nice way to go!
Can you please try what my friends @ghostRansom and @SVFB are sharing with you and see if those steps work for you too?
Keep us posted!
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
02-26-2019 08:54
02-26-2019 08:54
Alas, I am now a member of the 001 club, too. I don't have a charger at work, so I can't try the restart right now. But for reference (based on information I've seen in this and other threads), it's running on the default clock face, connected to an iPhone Xs, and was purchased in November-ish. The error's been up for about an hour. Earlier this morning, the charge was at 22% so I plugged it in while I was getting ready to leave (about 20 minutes) and it charged to about 52%. It's last sync was at 10:37am and I noticed the error around 11:20am.
I'll check back in once I get a chance to try the restart. But is this a problem I'm going to have to monitor for all the time now? I've seen people have their units replaced over it; is this something I might also have to consider?