Yes I'm very happy with the outcome, thanks GN for resolving it.
I initially suspected something like a corrupted file or a problem with the flash memory.
I tried a few things before asking such as reinstalling maps several times and changing the map region to somewhere else and back again in case that fixed it. Then when I found out to how to turn mass storage mode on I twiddled with a few files to see if the error messages changed.
After being burnt a few times I'm very careful trying to work out what I can mess around with without breaking things. Then if I do break things how hard it is to unbreak them. Copying files back easy, reflashing in boot modes slightly harder, soldering to test points on the PCB and using custom hardware to reflash trickier. Removing a chip, reflashing then replacing it is something I try to avoid thanks to my eyesight not being what it once was.
Within the limitations of the forum rules I'm curious as to what precisely went wrong and how it was fixed.
I gather the Garmin server is sending back a bad unl file for certain models. Is that a recent thing and if not why did it work fine until a few days ago?
I can fill in some of the blanks as to one way GN might have diagnosed the problem using the GarminDevice.xml file.
The one question I'd really like to know the answer to (and which may not be answerable here) is what the fix was and how it worked. It certainly did something interesting.
Bookmarks