Thread: how to upgrade firmware on nuvi 40 using sd card

You said in Post #4 that it showed the calibration screen. The way that screen is reached is by putting the nuvi into preboot by holding the screen and powering it on, a healthy nuvi x0 device will go into preboot for 30 seconds them move to the white screen. It you connect it to a PC by USB holding the screen, it will won't move into Mass Storage Mode, after 30 seconds going to calibration and staying there if you don't calibrate the screen manually. If you do it will boot normally even though it's connected to the PC (a handy trick to charge it and operate it normally).

You can see easily if in fact it is or isn't in preboot by holding the screen and connecting to PC. Have Windows Device Manager open and visible on your desktop first and watch it's GI, when you hold the screen with the device fully OFF and plug in the USB you should see it show in Device Manager for ~30 seconds then it will try to go to MSM as the green line appears on it's screen if you stop holding the screen before it moves to calibration.

[Only registered and activated users can see links. ]

When in MSM a healthy device will show as 'Garmin nuvi Flash USB Device' in Disk Drives and 'Garmin Devices' will have disappeared from the principal list. As your nuvi cannot reach MSM it defaults to boot normally instead.

Better to make absolutely sure that it cannot enter preboot using either the hidden menu or holding the screen by experimenting as I've detailed above before trying to do anything with sd card text commands.

Originally Posted by Butters

You said in Post #4 that it showed the calibration screen. The way that screen is reached is by putting the nuvi into preboot by holding the screen and powering it on, a healthy nuvi x0 device will go into preboot for 30 seconds them move to the white screen. It you connect it to a PC by USB holding the screen, it will won't move into Mass Storage Mode, after 30 seconds going to calibration and staying there if you don't calibrate the screen manually. If you do it will boot normally even though it's connected to the PC (a handy trick to charge it and operate it normally).

You can see easily if in fact it is or isn't in preboot by holding the screen and connecting to PC. Have Windows Device Manager open and visible on your desktop first and watch it's GI, when you hold the screen with the device fully OFF and plug in the USB you should see it show in Device Manager for ~30 seconds then it will try to go to MSM as the green line appears on it's screen if you stop holding the screen before it moves to calibration.

[Only registered and activated users can see links. ]

When in MSM a healthy device will show as 'Garmin nuvi Flash USB Device' in Disk Drives and 'Garmin Devices' will have disappeared from the principal list. As your nuvi cannot reach MSM it defaults to boot normally instead.

Better to make absolutely sure that it cannot enter preboot using either the hidden menu or holding the screen by experimenting as I've detailed above before trying to do anything with sd card text commands.

I TRY to do like you show many times, but my computer cannot recognize nuvi, Windows Device Manager don't have any change
,

If you tried using several different microUSB cables, different REAR USB ports directly [no hub] and even tried with another PC without being able to hold either preboot or mass storage mode, then it's probably got some hardware damage or failure, either the USB socket itself or the socket's connection to the board. I can certainly help you to load new firmware using SD txt commands. However, you did say this in Post #5:

Originally Posted by sangphung

i use kaspersky internet security on pc, when i connected nuvi whit pc, kaspersky deleted some file on my nuvi, and then i connect nuvi into pc again, it not recoginize my nuvi

• So you had PC recognition before that. It might be co-incidental that it's got a damaged USB socket connection about then (but I really don't believe in "co-incidences" much).
• If the above circumstance with Kaspersky is the cause why do you think re-loading firmware will fix it?
• What fw version is it running now?
• Have you hard reset it and cleared NV?

Please clarify those items before we look at using SD txt commands.