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

Can't update Blaze FW to 17.8.301.7

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

Hi,

 

My Blaze currently runs FW 17.8.200.3 and I'd like to get latest clock faces so I want to update to latest FW 17.8.301.7.

 

So I open FitBit app on my Android (Samsung Galaxy S5) and in Dashboard under Blaze I end up at a horizontal red bar that says "Update Tracker Software" so I hit that to begin FW update procedure.

 

However I am consistently stopped in a never-ending loop

1) Keep your Blaze nearby ( mine is )

2) Enable Bluetooth (Blaze Classic is paired properly but Blaze is rejected when trying to pair it

3) Make sure you have an active internet connection ( I do )

4) Make sure your battery is fully charged (mine is pretty close to 100% at 95%)

Try Again

 

After 6x of "Try Again" a dialog pops up citing Bluetooth issues and gives me option of either "Restart Bluetooth" or "Cancel" - I hit cancel 1 time and then tried restart bluetooth and i never get past here.

 

If I leave phone alone after it locks I get a "FitBit - update failed" notification..

 

Any ideas

Thanks

BigDaddy68

 

 

 

Moderator edit: format

 

Best Answer
3 REPLIES 3

Have you tried updating the app itslef from the play store?

If it doesnt work, please contact support here.

Thank you

 

Please Consider To Like This Post
Best Answer
0 Votes

This seems to help and now after restarting my phone and Blaze - now my FitBit Blaze is properly taking its new FirmWare (FW) 17.8.301.7 - I am guessing it will take around 5-7 mins.

 

https://help.fitbit.com/articles/en_US/Help_article/2047

 

I guess it pays to read the sticky topics posted by the moderator..

 

For feedback - its pretty poor quality that to update your watch FW that you need to restart your phone.  Your FitBit Connect SW should not require this so its got bugs in it you should fix

 

thx

BigDaddy68

 

 

Best Answer
0 Votes
It might not have been Fitbit that required restarting the phone, it could have been stuck hardware and your operating system was unable to gain control of the BT hardware.. This might not be common but hardly unheard off.. Usually a restart if the BT is enough.
Best Answer
0 Votes