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

Device stuck, did soft restart, now stuck on green triangle. What to do?

Former Member
Former Member

My Garmin Fenix 6 Pro was stuck on 16:08 yesterday. It was unresponsive to button presses. Northing out of the ordinary has happened with the watch recently, was just chilling in the lounge when I noticed it wasn't responding.

I searched to find that holding the top left "light" button would perform a soft reset. This worked, the screen when off. I restarted it with the same button. It showed a green triangle on screen. I left the watch on charge.

The watch _still_ has the green triangle this morning. I've performed another soft restart to no avail. I've also tried Garmin Express to see if it can recognise the watch but that doesn't even detect the watch.

I'm unsure of what to do now. I'm also unsure of how I actually contact a Garmin representive to respolve this.

The watch is 6 months old.

  • Unfortunately I still have an issue. I tired the method above but I still have a screen the alternates between the Garmin start page and the green triangle - any other thoughts on a fix?

  • 显示佳明 USB GPS 但是打不开 还必须一直开始键

  • Thanks for this 

    Years later and my 965 got stuck on the green triangle. (Happens is after the blue one, and changes colour).

    This fixed it and was able to get back into it.

  • That is crazy, why is a forum the only place to find this info? This is the only thing that worked for me

  • Bumping this as well (and putting it in my posting history so I can find it again).  I have a Fenix 6 pro that out of the blue disconnected from my phone and would not connect no matter what I did.  I tried plugging into the computer, re-syncing, power cycling watch and phone, re-loading Connect on phone etc... nothing worked.  Genuinely thought I had a Bluetooth hardware failure on the watch.  I've never seen any instructions to do this factory reset before... but it was the answer.  Thanks for posting, and to anyone else with weird problems... it's worth a try.