• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 3012 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

OVERNIGHT BRICKED

John John
over 5 years ago

I charged my fenix 5x to 100% before sleeping.  I woke 6 hours later to a black screen and a bricked watch.  I have tried all reset methods i.e. 25 seconds on the Light button and the Light, Down and Back buttons to no avail.   All I got was a beep and a flickering blue triangle followed by blackness!

I have tried four different cables all with no result.  When I repeat the resets `i don't even get the flickering blue triangle now.

Please give me a clue.  I don't want to fork out $100+ dollars for a Service department inspection.

John

  • Former Member
    0 Former Member over 5 years ago

    Try this- with the watch powered off, simultaneously depress the light button, back lap button, and power (button with red ring and triangle on the head) button. Release the power button after the 1st beep, release the other two after the second beep. Restart and hopefully this will give you a good restart.

  • 0 over 4 years ago in reply to Former Member

    This worked for me, many thanks.

    Completely unresponsive 5X. It took a while holding the three buttons for the first beep, and I messed it up the first time I tried it by releasing all the buttons. It looked like it was going to power up but it still wasn't enough. It took a second attempt and following the instructions precisely for the watch to fully recover. It really felt like the watch was fully bricked but this button and beep combination did the trick to get it back up and running again.

  • 0 over 4 years ago

    Just to let you know - I took the watch back to Garmin and they replaced it without question.

  • +1 over 4 years ago in reply to John John

    Please refer to this main thread to track this issue and to use the workaround that resolves the issue:

    - Software Version 22.20 Crash