Thread: Nuvi 1490 help

Unless you have inquisitive children or novices using your PC I would not have protected operating system files or extensions for known file types hidden in Windows. Nor would i select the radio button for 'Don't show hidden files folders or drives' in Folder Options>View. What possible rationale there is for wanting .System hidden other than the ineptitude of other users of your PC escapes me.

You can safely copy all the other minor [nonessential] files from another working 1490. Take them from your last backup if you wish, they are unlikely to have been the cause of your problems. If your backup was made after the unit bricked [when file system was made visible by Cure3 fw], be very cautious about copying anything from the folders mentioned by Loly and I previously such as Text, Keyboards, Voice, GPX, POI or detail map images.

Spoiler: fs_image.ver

[Only registered and activated users can see links. ]

Thank you so much.

I think my old fs_image.ver was no good.
Opened it with notepad and here it is: 〰ⴶㅄ㜲ⴵ㈰툀

The new one I just got from you: 006-D0564-02 d

Could this be the reason, for all the trouble ?

Anyway, I think all the files and folders, are now present in the device.
And the "new" 1490lmt still running great, I just cant thank you all enough for helping me
So right now, I make a new backup.
After that I must say mission complete.

If any of you are in to Toyota navi, could you please pm me. Thanks

@Caty

From what unit do you take fs_image.ver ?

1490 have number D1275-02 writen inside

Spoiler: fs_image.ver from 1490

[Only registered and activated users can see links. ]

lolypop000

Originally Posted by Alfiogigio

I think my old fs_image.ver was no good.
Opened it with notepad and here it is: 〰ⴶㅄ㜲ⴵ㈰툀

The new one I just got from you: 006-D0564-02 d

It is from very old Nuvi 200...
In any case I think what this file only factory test service info likes manifest.txt in modern devices.

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 Alfiogigio

I have just opened fs_image.ver from another Nuvi 1490,
it was also: 〰ⴶㅄ㜲ⴵ㈰툀

So maybe thats ok....

You replenished the numerous numbers of victims of Windows. Notepad try read .ver files according to Windows proprietary format for such files. You see only ⴶ in this program window or empty screen, then you tried to change font or program perform suitable for Unicode font without your permission and you received this result. Sometime you can see even broken picture icon instead content of file in WoprdPad or Word.
For correct opening you must see this file with menu of Notepad only - Open... -> Choose below File of type: - All and Encoding: - ANSI -> Go to file and press Open! Or you can use programm what not so much clever