Thread: Enable features in your nuvi 12xx, 13xx and 14xx - JCV, LA, TTS

I think got it to work. This is what i see. in it own screen then it switch back to normal driving screen. Is this how it is?

Originally Posted by lolypop000

p.s.

On win 7 you can also try to install garmin usb drivers as administrator. (right click on garmin usb drivers.exe and run as administrator)

I never had problem in using updater.exe in 7 x64 recently, now it works fine- Tested with 1200 and 3490

Removing the card from the Garmin before flashing was actually a smart move. However, it looks as if your directory structure is a bit messed up. Maps cannot be stored in subdirectories beneath X:/Map/ but must reside in the X:/Map/ directory itself. Thus, X:/Map/North America.img is acceptable. X:/Map/2013.10/North America.img is not.

I understood what you meant by "SD Card root". I simply call it "X" as it's quicker to type out than "SD Card root".

In any event, 2013.10.img may not work because the firmware may treat it as a double extension. Rename it to 2013_10.img and you should be fine. Personally, since the name of the file can be anything, it won't hurt to be more descriptive, e.g. North America 2013-10.img.

@lolypop000: since I got lucky flashing the wrong boot, but it work. Should I reflash with the correct boot Or just leave as is since it works. Thx

Thinking about it, i don't think the flash ever go through nuvi 1450 when i flash the wrong boot. Y? Because when I click OK and pop up msg said no available update then I click OK again, and the flash just cancel itself. But Y I have Full JCV? Maybe nuvi 1450 already had full JCV since Garmin site stated.

Then question arise. y my nuvi 1450 never had full jcv b4 coming to this forum. I think maybe the original jcv was only 49kb and new jcv is now 755mb.
====

My other friend had nuvi 1300 and based on garmin site, no full jcv. I will see what's his chipset is, 0972 or 1104. If none of those then i guess he's just unlucky to have jcv.

People, you can't run 1104 boot.bin on a device with 972 bootloader and vice versa. It's because of the totally different loading addresses of boot.bins (0x60000 for 972 vs 0x10040000 for 1104). boot.bin is not a position independent piece of code. It crashes very early if loaded at a wrong address.

As it is boot.bin who is responsible for flashing bootloader, you can't accidentally replace 972 bootloader with 1104 one and vice versa. Doing so would require running update.txt script rather than just flashing an RGN file.

Exactly the same thing is true for firmwares. You can't run 1104 firmware on a device with 972 bootloader and vice versa. You'll see the "system software missing" message in this case.

So, cat2115, it's impossible that you've flashed wrong boot or wrong firmware. Even if you renamed the RGN file, it would still be impossible. The explanation must be somewhere else.

UPD
By the way, I'm by no means saying that you can safely rename RGN files. It could be deadly dangerous!
But in this particular case it's safe because of the different loading addresses.