Usually Garmin had stroke out FID from certain value...
Printable View
Usually Garmin had stroke out FID from certain value...
G, are you saying that the Oregon/Montana fw has a fault and cannot read some FIDs? e.g. 3220 > ?
@Neil
CNEU NT 2013.40 has FID 2840 and doesn't work, Slovakia Topo v.4 has FID 5015 and doesn't work, free map Eu winter activity doesn't work
Coded link to the topic please?Quote:
Originally Posted by bommelb [Only registered and activated users can see links. Click Here To Register...]
Edit:
I assume this is the thread concerned (see post #14):
Also see post #18 en #22: these posters eventually reinstalled the 3.70 firmware and then the CNE 2014.40 and everything worked fine thereafter...Code:http://forum.gps.nl/viewtopic.php?f=113&t=42456
On other forums, people report that legal and other types of maps, like OpenStreetMap, also suffer form this problem. If all these people speak the truth about the legality of their maps, this points more to a firmware issue. One person said he heard from a reliable source that there is no validity checkQuote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
(user SmickF).Code:http://garminmontanagpsr.wikispaces.com/share/view/65927798
Hi,
On my opinion, Garmin new map authentication process is a reality, but is not perfect yet and disable both pirated and some legitimate maps.
Quote:
Originally Posted by lolypop000 [Only registered and activated users can see links. Click Here To Register...]
I agree...Garmin does not intentionally block the free maps from working
but still to fear that they will get new idea to stop UnLocked map working
in the German forum describes someone that has helped it to change the file extension img - then reboot
then turn off and change the file extension back to img
Code:https://forum.garmin.de/showthread.php?23769-Montana-(WebUpdater)-software-version-5-60-as-of-January-30-2014&p=160388#post160388
Btw as I trust Oregon 6xx wiki and I've read this:
I decided to stop testing and went back to previous firmware ;)Quote:
babj615 about 17 hours ago
I see others have already reported it, and now I also am suffering from a bricked Oregon 650t after updating to v3.70.
Spoiler: wiki post link
NOTE: I moved posts regarding new Oregon firmware from [Only registered and activated users can see links. Click Here To Register...] here.
from wikispaceQuote:
Warning
3.70
Multiple reports of new map authentication process disabling legitimately purchased maps. (Bug 72)
Multiple reports of 'bricked' units hanging during boot process.
Multiple reports of frequent lock-ups and crashes. (Crash 20)
Another shity FW from Garmin.