Possible to roll back to 6.00?

Former Member
Former Member
I am on 6.75 beta and wondering if it's possible to roll back to public release 6.00? If so, how? Thank you.
  • From the beta installation instruction:

    If you would like to revert to the last public release software, drop the gupdate.gcd file, found in the System_Backdate_v600 folder, into the \GARMIN folder of the device.
    NOTE: If you revert to an older version of software, all of your settings will be reset to defaults.
  • Former Member
    0 Former Member over 7 years ago
    Thanks for responding!
    I must have overlooked the "last public release" detail. I thought it would only roll me back to what was on the device prior to the update. In my case, that would be Beta 6.71.
    Thanks very much!
  • Former Member
    0 Former Member over 7 years ago
    As a follow up - I did the roll back to public release 6.00 and that seemed to fix my problem.
    I was having issues with settings, alarms and watch faces resetting to default values on Beta 6.75. It occurred to me that it might be similar to my Pixel XL phone in that after a series of incremental updates, the phone begins behaving strangely and I need to do a clean flash and reinstall everything. My 5X which I bought when they first came out, has been getting all the public and beta updates every time one came out and I've never done a full wipe and reset.
    Last night after flashing back to public 6.00 it was so stable that I thought maybe then I could update to the 6.75 beta and have no issues.
    I flashed the 6.75 beta and almost right away had the issues with the MyWatch watch face resetting "IQ" errors, etc. So I reflashed again back to 6.00 Public and everything is fine again. It was a pain to have to manually reinstall all my settings, but it was worth it as an experiment. It seems 6.75 beta does have some stability issues.
    For those in other posts having instability, a flash back to 6.00 might help.
  • I am currently working with Garmin engineers to investigate the problems with the watch faces on 6.75. But it's reassuring that I am not alone in seeing this issue and that it only seems to happen with 6.75. Let's hope they find and fix the fault before rolling this version into production.
  • Former Member
    0 Former Member over 7 years ago
    Thanks for working with them to find and fix it! The 6.75 beta did also include an update to the CIQ version right? Maybe it's related to that.
  • Possibly. The issue is related to watch faces which save data to the object store, such as location, weather or other information. The new CIQ version has a new method of saving data so I ported my watch to this to see if it made a difference, and they still crash, but the symptoms are subtly different. Anyway, I have provided details to Garmin and they are investigating.
  • Former Member
    0 Former Member over 7 years ago
    That's interesting. Well the watch face I use is MyWatch, which displays barometer, moon phase, daylight, etc. but hasn't been updated since July. I hope whatever fix now works with the new storage configuration doesn't mean MyWatch won't work anymore because there's no other watch face that displays the same information and it's invaluable to me in my outdoor activities!
  • Something odd is going on here. Maybe the FW problem where apps setting and the object store get zapped came back. (that was fixed long ago :( )

    The new CIQ storage thing isn't involved, as it's something that won't be commonly used for some time yet. Something is stepping on the files where things are stored it seems
  • Former Member
    0 Former Member over 7 years ago
    You are correct Jim! I was using MyWatch months ago and with others using this and other watch faces experienced the same symptoms we seem to have with Beta 6.75. I agree that original issue was resolved some months ago and I have enjoyed good stability with the MyWatch watch face, even though it hasn't been updated since July. I don't remember which FW update first solved the issue we seem to have again now, but perhaps the historical engineering notes will show what changes were made back then which originally worked. Perhaps in the time since, the code written has used a similar method to enable some new feature which in the update, rekindled the old problem.