
Originally Posted by
Garman_Nuvi
.......
This shows 2.64 is Up to date but GE gives you 2.69 ?
Indeed! I hadn't noticed the fw version discrepancy in the two images showing 2.69 in the first and 2.64 in the second. That's a little weird anyway because according to the following post on the official Garmin forum, the changelog was 2.66 > 2.68 whereas your list from GE indicates that it was 2.64 > 2.69:
Code:
Please Login or Register to see the links
Even without researching too deep it's obvious from other forum posts that this model series, like some other sports watches from Garmin, are finicky and unreliable and very often difficult to recover when they brick.
Garmin has always tended to remove failed fw version histories from their changelogs, resulting in odd progressions in version numbering. It seems the GE history you posted ignores any 'minor' updates between 2.64 > 2.69. The very presence of minor versions, i.e., other than "x.x0" can indicate failed previous attempts and in the case of Version 2 major fw series it seems there may have been at most 9 'minor' attempts, going by V2.69 being latest. Some of the other minors may not have even been released at all and some released and quickly withdrawn.
Another difficulty is the structure of their watch firmwares, many don't have a ramloader (aka 'boot.bin') intended for region 12 (0x0C). Rather some have a bootloader only which is flashed directly to region 5. At lease the Venu Sq 2 is conventional in that sense and has a ramloader ... However, it's main system software (fw_all.bin for region 14) is not accepted by GarminCure3.exe so it cannot make cure fw, therefore should the watch be soft-bricked by a corrupt file it might be toast. The only hope of recovery lies in it having bad data in rgn14 which is successfully re-flashable as an RGN by Updater.exe in Garmin/preboot mode, because Cure3 fails and so likely QuickCure will also:
Bookmarks