No issues reportedQuote:
Fixed default voice language setting for Czech locale.
Printable View
No issues reportedQuote:
Fixed default voice language setting for Czech locale.
New Locales.xml was publish a few days ago and maybe it is not so long for reports. I do not think that many users do reset for this time.Quote:
Originally Posted by catymag [Only registered and activated users can see links. Click Here To Register...]
Software version 4.00 and 2.10, please
@miroslavbl
V4.00 is current and can be obtained easily via WebUpdater/GarminExpress. Additionally Perry link and direct link from Garmin server are also both in initial post anyway.
V2.10 might be elusive as it was initial factory load fw, maybe someone has it as a UAT version though.
I cannot connect my nuvi 40 on computer, because there is problem with USB port. :(
I need 2.10 version for creating ldr.bin file and updating fw to version 4.00 with SD card.
Thank you.
Just put v4.00 in Garmin folder on microSD [x:/Garmin/gupdate.gcd], turn nuvi off, insert card and turn on. It will update without having to use ldr.bin of existing version.
Warning! Think twice (or four times) before trying this!
I also have a Nuvi 40 with broken USB connector and tried to update my nuvi 40's fimrware to 4.00 via SD card as suggested above. On reboot I had lost everything stored on the internal drive (original maps, all voices, all languages other than American English, help information, ...). Without speech output it's essentially useless. Very sad.
I'm not sure what happened, but it looks like the internal drive is scrambled and without USB connectivity I fear it will be impossible to recover.
Carefully consider whether the risk of losing everything is worth any improvements from a firmware update.
Probably you made something wrong because it's a normal and safe method to update software in nuvi
@EdC
I'm sorry to hear you've had a problem but i agree with catymag that updating software from the card is usually very safe. I'm guessing that your unit lost power while updating or the problem is coincidental and unrelated to the update. The USB connections in most units can be repaired by reflowing the solder connections. Sometimes that doesn't help because the problem is on the board itself. Failed USB connections are a very common problem on xx and 1xxx nuvis, particularly the 5" models 50 and 14x0, but 30/40 and 12x0/13x0 and even 2xx/W can also suffer. I have a couple of units with re-flowed USB sockets which still charge but have no data transmission because of some other fault, probably failed component on PCB. I can backup and update everything including voices, maps etc by using text commands from the card, it's a little cumbersome but the units are usable.
Reflow first, and then if you still don't have data open a topic in Garmin Discussions and we'll talk you through updating from the card.
Thanks for the kind words.
I had opened up the unit and found I could not re-attach the USB connector because some of the traces had been lifted off the board. However, I cut off the B side of a USB cable and soldered this cable's black and red wires to a ground trace and the trace that used to be the USB connector's +5V pin. I also connected the ID pin to +5 (otherwise it seemed to hang waiting for a USB connection on boot-up). This gave me a fully functional unit. I was able load maps and even custom PoIs via the SD card. So I'm very annoyed at myself for not quitting while I was ahead.
My problem may be related to the fact that when the Nuvi is configured like this it seems to go through a different boot process than when the USB port is functional. I don't doubt that in normal situations this method works. That's why I thought it worth warning others who may be trying to do firmware upgrades with non-functional USB ports.
Setting/System/About shows the Software Version is still at 2.30 while the Keyboard version is "Unknown" and the Audio version is "Missing" so perhaps the problem is that the update to 4.00 did not complete or somehow went haywire. I'll try disconnecting the ID pin and to see if the different boot sequence causes the gupdate.gcd to get loaded (no amount of power cycling or erasing user data seems to do it).
Otherwise I may have to resort to using ldr.bin and update.txt as I think you are suggesting.
Thanks again.