Thread: Nuvi 1490 help

My guess is that Caty's file is from an EU 2x0/W series. US 260 & 260W have 006-D0564-10 NULn [3 examples].

@Alfiogigio
The reason you couldn't read your US1490 fs_image.ver is because you're opening it in Notepad. All US 1xxx series files will show 〰ⴶㅄ㜲ⴵ㈰툀 in Notepad. Use Notepad++ (it's free, Google it) and you will see for your original file 006-D1275-01 NULÒ. Loly's EU 1490 file is 006-D1275-02 NULÒ in Notepad++ and 〰ⴶㅄ㜲ⴵ㈰툀 in Notepad. Caty's file will show 006-D0564-02 d in either program.

Almost certainly your unit's original minor files did not cause it to brick as i said. You don't need the EULA but if you want it for original completeness this one's from a US 1490T:

Spoiler: EULA.rar

[Only registered and activated users can see links. ]

And here's an original US1490T fs_image.ver file which is also of no real importance to your unit imo:

Spoiler: fs_image.rar

[Only registered and activated users can see links. ]

I have some knowledge of Toyota VDO Dayton/Denso-type Car Navigation units [with map data on DVD]. Is that the one you're asking about?

Originally Posted by Neil

Almost certainly your unit's original minor files did not cause it to brick as i said. You don't need the EULA but if you want it for original completeness this one's from a US 1490T:

Spoiler: EULA.rar

[Only registered and activated users can see links. ]

You are ball of fire as "живчик" as usually and leave me without "likes"

But I do not recommend to put any EULA if it is not from factory loading. Even if I updated this file from same device nothing to crash but I received "false" record in end of garmindevice.xml after EULA partnubers in most case. I think it is not critical but "false" is not good word and I feel guilty what I really violate this agreement

LOL! What to do with you G? живчик translates as 'twig' in Bing and 'Zinger' in Google. I will accept the later, thank you. Fret not, I shall replenish your 'Likes Score' on account of you having two excellent if unfortunately consecutive posts [but that gets another 2 likes on your total, so 'every cloud has a silver lining']

I agree about the EULA, but as he seemed to want one it's best to at least supply one from another 1490T. It won't cause any real problems.

You could probably put back "all the factory files" without bricking the device.
Most of the factory loaded files never get written again.
I would first make a backup of its current state.

Loly is right Giomen. I'd hadn't tried to open ver files with anything other than Notepad++ or a hex editor, but when Loly posted about WordPad i tried it and it works. Using his EU file, I get 006-D1275-02 Ò in WordPad. Also, Microsoft Word with encoding set to Unicode shows only 〰ⴶㅄ㜲ⴵ㈰툀 but as Unicode UTF 7 or 8 shows 006-D1275-02, and ASCII shows a trailing R instead of Ò.

Even swriter.exe [OpenOffice] will open it but shows 006-D1275-02#Ò. It seems there may be any number of basic text readers which will at least show the first part in readable form.

Originally Posted by Alfiogigio

Think that the only way, is to copy back each file from the backup
one by one, and when/if I find it, im back where I startet......

We know the main Garmin hanger (extensions of files) ! It is wrong POI (gpi), voice (vpm), maps (img) and no doubt SW (gcd)...

Maybe it wasn't a corrupt file at all !
It could have been the Filesystem that had errors and needed a format.
Examples:
If someone formats the Nuvi to NTFS or in a MAC then the Nuvi won't work until it is formatted back to FAT32 using RMPREPUSB (not in your case)
Also if the Drive has lost clusters or another filesystem error it can cause the Nuvi not to work until the filesystem error is properly corrected.
A nearly flat battery can cause filesystem errors if the Nuvi dies due to lack of power while it is booting up. We've had such a case in the forum on a 3790 with a bad battery.
Please Charge your Nuvi at least once a month if it is not in use.

I think that you could safely put back all the pre-loaded original files such as help etc etc. (check date stamp to find preloaded files)
Try to avoid putting back files that get updated regularly such as voices text etc etc.