Seemed to have found a fix. First I wanted to know more about the GL version and found instructions to hold down power until an info screen displays. It did say "GPS Type: GL2 BCM4750". So, I could use the fix here: [Please Register or Login to download file]

As instructed I downloaded the glgps.rar. The instructions were to swap the archived glgps for the /bin/glgps. However there was a problem using linux unrar to unpack the glgps.rar file. So I unpacked that using 7zip on Windows and got a second glgps.rar and unzipping that gave me glgps.

After installing then letting the gps sit in the window a while the time did set on its own but was off by an hour. This might be as I sit not too many miles from the Georgia/Alabama border in Georgia in a tin mobile home and the gps is in a window facing west. I set the correct time and it's been all's well for maybe 20 minutes.

WTJ848 wrote:Seemed to have found a fix. First I wanted to know more about the GL version and found instructions to hold down power until an info screen displays. It did say "GPS Type: GL2 BCM4750". So, I could use the fix here: [Please Register or Login to download file]

None of this makes any sense...AFAIK, you are the only one to have this problem considering what device you have.

The reason is, TT specifically released NC 9.541 to address the WNRO problem:

TomTom wrote:Version 9.541

Released on 19 December 2018 This update applies to: XXL Classic, ONE IQ Routes, XL IQ Routes, XL IQR2 / XL Classic, GO 750, GO 750 LIVE, GO 950, GO 950 LIVE, GO 540 LIVE, GO 740 LIVE, GO 940 LIVE, GO 530, GO 630, GO 730, GO 930, GO 720, GO 520, GO 920, EASE, ONE 140, Start

• Maintenance release.
• This update prepares your navigation device for the week number rollover in April 2019 which has an impact on GPS.

There are many other users that have the devices listed by TT above...they have installed the new navcore > sometimes with a new map - sometimes not > reset it = job done

It's only users that don't have a device listed above that need the 'rima-lock fix' or users who have a SirfStar chipset that have had to go through a different route to fix it
If you don't believe me...compare the 'fixed' glps file to the glps file that is contained within NC 9.541...they are exactly the same file.

Perhaps because after getting the one time download of v9.541, I tried updating the XXL again. The download stopped at 80%, repeatedly. But, if the download stopping was the failure cause, why did changing the glgps (not glps) successfully fix the issue?

Oh, they are NOT exactly the same file as their byte count differs, the new slightly larger.

Am backing up now with xcopy and will then transfer mapsettings.cfg from the first backup for all my old destinations. Wonder if the 620 Go can use the same mapsettings.cfg from the earlier XXL.

Really would like to see a change that makes the current time available on map display of the 620 Go. I am so habituated to glancing at the GPS for the current time the 620 Go seems annoying. Putting an unnecessary destination is a crude undesirable fix. Garmin apparently shows the current time on it corresponding GPS.

You've already cluttered up that thread with enough of your machinations that it deserves it's own thread now.

WTJ848 wrote:1. Perhaps because after getting the one time download of v9.541, I tried updating the XXL again. The download stopped at 80%, repeatedly.
2. But, if the download stopping was the failure cause, why did changing the glgps (not glps) successfully fix the issue?
3. Oh, they are NOT exactly the same file as their byte count differs, the new slightly larger.
4. Wonder if the 620 Go can use the same mapsettings.cfg from the earlier XXL.
5. Really would like to see a change that makes the current time available on map display of the 620 Go. I am so habituated to glancing at the GPS for the current time the 620 Go seems annoying. Putting an unnecessary destination is a crude undesirable fix. Garmin apparently shows the current time on it corresponding GPS.

1. One time download? You can easily download the official navcore 9.541 for your XXL from here:
[Please Register or Login to download file]
2. You probably needed to do a hard reset after the initial update to clear the flash memory...instead of that you downloaded the same file from a different place and inadvertently did a hard reset when you held the power button down to go into the BIOS screen.
3. Yes, they ARE the same file...both of them are 1,176,168 bytes. Another member took the glgps file from the official TT navcore and posted it on his site to make it easier for people to download it...he didn't do it for pedants to rhapsodize over
4. If that's your indirect way of asking a question without actually asking it...I wonder if I should enlighten you
5. Actually it's a 'Go 620'...I've already told you above that TT released the new 9.541 navcores to specifically address the WNRO problem and luckily for you, your XXL can utilize the new navcore to fix the problem but the Go 620 might need the firmware flash to fix it.

I think that's enough, you've obviously got your own individual way of doing things & we've already wasted a fair bit of our festive holidays trying to decipher your inane drivel in order to try & help you. You have all the information you need now to complete the rest of the process by yourself.