Versa's touch screen not responding

[caspian]

My versa started going into a bootloop earlier today. After restarting several times it finally booted but now it is not responding when i press the screen. The buttons on the side still work. I have only had it for 3 months. Is there a way to fix this or can i send it somewhere for repair?

Moderator edit: updated subject for clarity

[SunsetRunner · Accepted solution]

Hi @caspian , since your buttons are still working, you can try to do a Factory Reset by pressing and holding all buttons together untill you feel a strong vibration (might take a while) and release the buttons. If that also does not solve your problem, call Customer Support. Regards kuzibri

[JuanJoFitbit]

@caspian welcome to our Fitbit Community! Regarding the display issues that your Versa is experiencing, I appreciate the time spent trying the restart process before contacting our forums.

If you haven't contacted our Support team as @SunsetRunner advised, please try changing the clock face to one developed by Fitbit, not a third party clock face. After this, restart your watch one more time as @SunsetRunner mentioned and see if the issue gets fixed.

Keep me posted on the outcome! 😀

[nacioss]

I have the same problem. Several days ago the screen started scrolling by itself. Then the screen stopped responding to the touch. It was counting steps, calories etc but I couldn’t go to menu or check notifications. I’ve done soft and hard restart several times, I’ve changed the clock face several times and nothing seems to work. Today the screen went black and nothing seems to work to turn it on. I purchased it 29.11.2018 in Europe and I just found out that there is 2 year warranty. Is it possible to replace it? 

[Naheed]

My Versa touch screen has stoped working. I have reset it several times, but screen is not responding to touch. Can anyone help?

[DBHope]

This doesn’t work!!!   I’m very frustrated.  Just bought an Apple Watch.  

[DBHope]

Rebooted, changed screen, and washed touch screen.  Why isn’t there a better answer or a known bug report on this??!