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

Downgrade to stable 16.22 - instructions

.anjo 11 months ago

Following the very annoying problems with the Power Mode during activities and the daily suggestions dissapearance, I've decided to downgrade to the stable 16.22 version.

For those willing to do the same, here the basic instructions.

Note: it will be quite some work, as it resets the watch and you need to re-pair with the phone and then restore the settings.

DOWNGRADE INSTRUCTIONS

0. Make sure you have a Backup of the your settings before continuing - check step 5 on how to find the backup (and "Back Up Now", if needed).

1. Download latest stable version 16.22 for your model from the table below and unzip the file (thanks for the table @socorsu)

2. Connect your watch to the computer, open the explorer and copy both the gupdate.gsp and force.tmp files to the GARMIN folder of your watch.

3. Disconnect the watch from the computer. After some seconds it will detect the files and propose to perform the "update" to 16.22

4. On my case, during the restart it took several minutes on "Loading FIT files" and then "Loading Map xx".

5. Re-pair the watch with the Garmin connect App, pass the basic setup questions, go to the devices (top right), select the watch, System -> Backup Up & Restore -> Device Backups -> select the backup and click "Restore from Backup"

6. Watch will restart. In my case it tried to re-pair automatically, took a while in "Applying profile", then gave an error, restarted again and during the second restart finally appeared "applying backup" and after a while the watch was like few days ago, with 16.22 and all my settings and personalisations..

7. Disable Autoupdate on the watch, System -> Software Update -> Auto Update

The whole operation took me 30-60 minutes.

Firmware 16.22 links
Generation	Version	Model	Remark
Standard	16.22	fenix 7s
Standard	16.22	fenix 7	Quatix 7 Standard (MIP) -- use Fenix 7 standard
Standard	16.22	fenix 7x/Enduro 2
Standard	16.22	Epix_(Gen 2)	Quatix 7 Pro (amoled) -- use Epix 2 standard
Standard	16.22	Marq_(Gen 2)
Pro	16.22	Epix_Pro_42
Pro	16.22	Epix_Pro_47
Pro	16.22	Epix_Pro_51
Pro	16.22	Fenix_7s_Pro
Pro	16.22	Fenix_7 Pro
Pro	16.22	Fenix_7x_Pro

Hope it helps.

Top Replies

Garmin-Laurie 11 months ago in reply to thunder0187 +1 verified

thunder0187 said:
Can you somehow please make this thread sticky so everyone can find this one quickly...not only you totally messed up 17.xx,

Garmin is aware of a number of concerns that have been reported…
1706139 11 months ago +3

What's going on with this firmware ? First, version 16, many people complain that their watches are bricked, and have to go back to 15. Now the new version 17, the previous bugs are probably fixed, but…
9626287 11 months ago in reply to JosefK +2

15.76 or 15.77 is the best and most stable version. Both my epix gen 2 and epix pro 51mm are on it(15.76)

I could careless on the newer stuff, just don't want any interruption to marathon training block…
socorsu 11 months ago +2

Garmin official link .anjo is it possible to add it to your post ?

Generation Version Model Remark

Standard 16.22 fenix 7s

Standard 16.22 fenix 7 Quatix 7 Standard (MIP) -- use Fenix 7 standar…

All Replies

0 socorsu 11 months ago

Garmin official link .anjo is it possible to add it to your post ?

Generation	Version	Model	Remark
Standard	16.22	fenix 7s
Standard	16.22	fenix 7	Quatix 7 Standard (MIP) -- use Fenix 7 standard
Standard	16.22	fenix 7x/Enduro 2
Standard	16.22	Epix_(Gen 2)	Quatix 7 Pro (amoled) -- use Epix 2 standard
Standard	16.22	Marq_(Gen 2)
Pro	16.22	Epix_Pro_42
Pro	16.22	Epix_Pro_47
Pro	16.22	Epix_Pro_51
Pro	16.22	Fenix_7s_Pro
Pro	16.22	Fenix_7 Pro
Pro	16.22	Fenix_7x_Pro

#Matthias# tks for the Quatix 7 info ;-)

0 .anjo 11 months ago in reply to socorsu

Hi socorsu,

It is a great table. I would like to put on the original post, but I don't find a way to copy/paste as a table. Do you have an idea how?

0 8253847 11 months ago

Great information. Will I lose any data on my watch like heart rate variability, race predictions, heart rate zones and so on? I got pushed this 17.23 version and it's full of bugs: unable to set recommended training sessions by heart rate, voice prompts all the time that can't be disabled, worse battery life. Tomorrow I will call Garmin as well to report al this issues.

0 .anjo 11 months ago in reply to 8253847

I did not loose anything. The race predictions graph will start a new line, but in my case it was in the same position as before. The old information is in Connect App. Hrv and heart rate zones are not lost. My courses (for navigation) were lost, but was rather good as it is cumbersome to delete them, and I have them in Connect App.

I'm still happy with the rollback to 16.22

0 8253847 11 months ago in reply to .anjo

Thanks, I'll wait a couple of weeks, if I can live with the bugs, and see if Garmin releases a firmware with the fixes. If not then I will have to downgrade. I don't understand how such a buggy firmware was released.

0 8fb23e9f34b9459da4b42ea20be9af4e 11 months ago

Do you have experiences with rolling back on MacOS? I can't find the GARMIN folder.

0 .anjo 11 months ago in reply to 8fb23e9f34b9459da4b42ea20be9af4e

Hi,

Google is your friend. Check here:

whodeenie.medium.com/browsing-a-garmin-device-on-a-mac-6657cdd0b7d2

0 jcldl 11 months ago

Thanks, I downgraded and my watch is OK, since installation of the new software most of my watch faces indicated: IQ!. Now they are here!

0 thunder0187 11 months ago

Garmin-Laurie

Kelly_ODQA

Can you somehow please make this thread sticky so everyone can find this one quickly...not only you totally messed up 17.xx, WE are doing your work in the end helping others so it would be at least helpful if you could make this thread sticky as there is nothing more coming from your side. Hope this task isn't too hard. Thanks.

0 #Matthias# 11 months ago in reply to thunder0187

If you keep luring Garmin officials to this thread, they will lock it. They do not want us to backdate software. It is not officially supported to backdate from final release to another one and other threads offering backdate files to do so were already locked.