Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Sense 2 stuck on Fitbit logo

Replies are disabled for this topic. Start a new one or visit our Help Center.

Been using Versa 3 for a couple years. Decided to upgrade to Sense 2. Unpacked, charged,  and setup my Sense 2 yesterday. No problems. Today the unit shut off. Holding reset button for 10 seconds till logo appears. Logo blinks for about 10 seconds then a red X appears on screen. It attempts to boot again with same results, then shuts down.

 

 

Moderator Edit: Clarified subject

Best Answer
5 REPLIES 5

Hi there, @Ronhoch. Welcome to the Community Forums. Thanks for trying to troubleshoot the issue with your Sense 2 before reaching out. 

Please note the issue you're having comes from performing a factory reset without first unpairing your Fitbit device from your Fitbit account and phone's Bluetooth settings. With that being said, I suggest following the steps below in the order listed:

  • Unpair your Sense 2 from your phone's Bluetooth and also make sure it's no longer connect to your Fitbit app. 
  • Force quit the Fitbit app.
  • Turn off the Bluetooth.
  • Shut off your phone and turn it on after 1-2 minutes.
  • Turn on the Bluetooth.
  • Set up your Sense 2 again.
  • If there is no connection, restart your Sense 2.

If you can't get started with your Sense 2, usually a missing requirement is the cause. Carefully review the requirements provided in the help article Why can't I set up my Fitbit device? 

If you continue having difficulties to update your Fitbit device, see Why can't I update my Fitbit device?

Hope that helps. 

Maria | Community Moderator, Fitbit


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...

Best Answer
0 Votes

Not having much luck but not giving up on Fitbit! I've been a FB user for some years starting with Charge 3, then Charge 4, then Versa 3 which I still have. Unpacked and successfully setup Sense 2 yesterday. Today is when the display refused to come on.

Here's what I've done so far:

Validated charger and cable using my Versa 3.

FB app on phone: removed Versa 3 and Sense 2 devices

Completly unistalled FB app.

Unpaired Vesra 3 and Senase 2 on phone bluetooth, then shut phone off for an hour.

Reinstalled FB app on phone

Power up Sense 2. Logo appears but never gets further

App "sees" Sense 2 and prompts to setup device

App asks for Pairing Code displayed on Sense 2 but the display is black. 

 

I'm not sure where to go from here??

Best Answer

@Ronhoch   It certainly sounds like you have a defective device.  Contact Support for more help. 

Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS

Take a look at the Fitbit help site for further assistance and information.

Best Answer
0 Votes

I just established a new FB account using wife's email. Also attempted setup using wife's Android tablet. 

Same results so the issue appears to be something with my Sense 2.

 

So disapppointed. 

Best Answer
0 Votes

I have been having a similar problem, although I had been using the device for a couple of months before it started.  I was having a lot of syncing problems, so I was getting in the habit of going right to the force stop fitbit, turn Bluetooth off and back on, and rebooting the device.  I also tried rebooting my phone some of those times.  The problem kept getting worse, with the reboot getting stuck on the Fitbit icon.  It would take several attempts to get a reboot.  Finally, it stopped rebooting entirely.  Twice now, I have tried to reboot, and it has done the blinking, the big red X, followed by a permanent freeze on the Fitbit logo.  It stays there until the battery runs out, then I am able to recharge it again and it will work for a while.  It cannot be rebooted, or this will happen again.  I have tried engaging customer support, without much luck.  At this point, I am pretty sure it is a defective device.  Nobody wants to admit that.  Oh, and I have never done a factory reset, so that is definitely not the problem!

Best Answer
0 Votes