Thread: nuvi 1490 identifies as "nuvi 14xx"

The unit still works... kind of.
It's not keeping some settings since the shutdown. I connected my phone to it, but after a reboot, the phone was erased from the list.

Sent from my LM-G900 using Tapatalk

@Cuber
(i) Loss of model number is usually caused by erasure or corruption of data in non-volatile (aka nonvol or NV) memory region (rgn41). The device has some permanent data written to it at the factory which is specific to the individual unit. The nonvol region is rewritten/updated to a limited degree on each successful boot cycle however if its identifying as "14xx" is due to a nonvol problem that cannot be rectified unless you have a backup of the actual device's rgn41 (flashing another 1490's nonvol data will cause even bigger problems). Even a very old backup will restore it provided it's from your actual device: [Only registered and activated users can see links. ].
(ii) The other possible cause, although less likely, is a problem with the device's logo region (rgn16) - that's the data which shows the splash screen on startup and in the 1xxx devices it also controls which features are activated or de-activated in the device (i.e. JCV, Lane Assist, etc.). You should reflash the logo, it's quite safe and easy to do, look here: [Only registered and activated users can see links. ]. The logo.bin linked there is the 'senior' version taken from a US/EU version 1490 like yours. Unlike 41, the device's rgn16 is not individual device-specific.

If re-flashing rgn16 doesn't fix it and you don't have a backup of its rgn41 then the model change is permanent.

Re-flashing the logo was always the less likely solution unfortunately.

Region 41 is encrypted in simple terms however that's not the problem, decrypting and re-encrypting is done with relatively trivial XOR.

Unfortunately AFAIK it's not possible to write to and save such info into a rgn41 BIN file and then properly flash the amended re-encrypted BIN to the device. In fact, i don't even know what and where the necessary changes and/or additions are needed to be made in the file. If someone outside of Garmin knows how to do that without proprietary programming kit they're keeping it to themselves, because if it was made public it'd be posted on a forum like this one and others like it very quickly.