Thread: Table of nuvis PCB P/N written in FW and possible conversions

On other thread someone asked about conversion 1390->1690. 1690 is nulink, but maybe hardware is enough compatible to make conversion and get routes? PCB number is not the same but similar. Any thoughts about it?

Edit:
nuvi 5xx - 105-01364-00
zumo 2x0 - 105-01364-00
zumo 350 - 105-01973-00
zumo 4xx/5xx - 105-01074-00
zumo 660 - 105-01452-00, 105-01452-01, 105-01452-02
zumo 665 - 105-01452-01, 105-01452-02
nulink 1695 - 105-01756-00
nulink 23xx - 105-01774-10, 105-01774-00

Originally Posted by Kanopus

On other thread someone asked about conversion 1390->1690. 1690 is nulink, but maybe hardware is enough compatible to make conversion and get routes? PCB number is not the same but similar. Any thoughts about it? .......

I tried that conversion some time ago using hybrid fw with original 13xx boot.bin, and also the other way 1690>1390. Converting 1390>1690 gets you routes, but of course you won't have Traffic either TMC or nulink or anyother connected services, and you lose the Lexicon too. More importantly, the unit was mute and wouldn't connect properly in MSM to PC. It identifies as 13xx on boot. The conversion just makes a perfectly good 1390 into a really sucky 1690 without sounds. Pre-boot was accessible so i just flashed it straight back to 1390. Needs for you NSE guys to do some serious fw manipulation i think and i doubt it's worth the trouble. But if you can get the sound and TMC traffic working and sort out the other bugs it would be ok i suppose. Probably easier to try to awaken routes in 13xx by playing with its own fw i'd reckon [but i wouldn't know].

1690>1390 works ok, but loses traffic. Identifies as 1390 on boot. Also won't turn off normally, has to be forced off by holding the on button down. There were some other little quirks too, but i can't remember them now.

Added your additional PCB P/N info into Post #1, thanks.

Originally Posted by Kanopus

On other thread someone asked about conversion 1390->1690.

recently completely repairing in 1690 a non-working. Corrupted all bootloaders and memory.
The boot region(0x0-0x13ffff0) from 1314xx fully reached. Navigator booted up to the logo and connected preboot, after re-flash the original firmware.