Thread: nuvi 58LM is working but not recognized by Computer

Yes it's still capable of reading from SD as i fully expected and that's why i referred you to that thread. Certainly it can update firmware from a card. The fw must be named gupdate.gcd only. Place the file in the root of the card (along with the Garmin folder, not in it) and use the following command as Update.txt in the 2087 folder:

Code:

Please Login or Register to see the links

If there's an existing GCD for V3.50 contained in .System folder the command will overwrite it and if there's none existing the new GCD will be written there. It'll be activated on re-boot when you'll again see the usual loading message on the screen confirming it's being updated.

You wrote: "....create a folder Garmin and in it a folder 2087 and in it create a file update.txt ....". That won't work as it's missing the folder named "Updater" - you need this arrangement:
SD:\Garmin\Updater\2087
In the 2087 folder place the boot.bin extracted from the firmware GCD by RGN_Tool then renamed to Ldr.bin, along with the update.txt file. Read this again: [Only registered and activated users can see links. ]. You must take great care making SD flash kits, some mistakes can kill a device, like flashing with the wrong Ldr.bin for example.

It's a different method than using individual BIN files, like for patching, but similar. The point is that you could do this fw upgrade with individual .bin files too, but you need to delete any existing GCD from the device first with command "del,0:/.System/gupdate.gcd", and so if it's your intent to patch the device's fw to use unlocked maps then you may as well just use the patched BIN method with the delete command and forget about flashing gupdate.gcd. We can't give you any specific help in this forum with patching of course due to the rules here.

I note that you don't have "reboot" as the final command in that Notepad screenshot of update.txt. If you don't include it the device won't boot after flashing and it'll just stick on loader message until forced off. Also if you copy/pasted the command from my post ensure you don't have any extraneous end space or carriage return in the command.

The SD card kit is already compiled with the update.txt that has the commands to install the Firmware, Patched or Not
This is a simple extraction to a FAT 32 formatted SD card with plug & play situation.

This will be my last Post in this thread.

Originally Posted by diversola

I don't understand, I'm not asking for patching to be explained to me, but how to install fw on nuvi via SD card.I don't understand, I'm not asking for patching to be explained to me, but how to install fw on nuvi via SD card. I put this picture as an example of whether it should look like this and to be explained how to extract it boot bin.

We're not trying to explain patching to you although it's clear now it was your intention to patch firmware to enable the device to read unlocked maps from SD card.

Leaving any GUPDATE.GCD in the .System folder can cause problems unless it's the same version you are wanting to flash from an SD card (which would be pointless anyway). You're unable to access Mass Storage Mode to delete an existing GCD manually or to even see if it is even there so running a 'del' command from SD is the only way to ensure its removal before flashing another version of fw from SD (whether that's flashed contemporaneously by following commands in Update.txt using individual BINs, or by copying a later version GCD to overwrite or place using 'copy' cmd as i suggested to you, or even flashed later by a GCD from SD in a completely separate action). Additionally, using individual BINs where the fw_all component (aka 14.bin or 0E.bin in Update.txt file) has been PATCHED or is ORIGINAL ultimately has the same effect as loading a GUPDATE.GCD file in that the firmware is updated to a later desired version. Whatever way a GCD is loaded makes no difference, if it's a later version it'll be initiated by the device on next boot cycle and loaded appropriately. If there's an earlier version GCD left on the device it can interfere so it's best removed or overwritten.

Individual BIN files can be extracted from a GCD or RGN firmware file using RGN_Tool.exe or gfw.exe, they are commonly available for download on the internet and are basic tools used for Garmin firmware manipulation and modification. As extracting BINs is "Garmin firmware 1.01 for Dummies" it's not in your own best interests to be doing more advanced manipulations without understanding the very basics. I guess if you don't understand that then you might not understand what i wrote above about various means of fw flashing either.

But regardless of all the above, it seems that the ever-patient Garmin_Nuvi has assisted you in another forum where the Rules don't prohibit us from talking openly about fw manipulations which clearly defy Garmin's EULA. Indeed we're expressly prohibited assisting hands-on with making patched firmware in here. Because of that not done in here you might now understand why we aren't so direct about things and appear to be talking in riddles at times. We won't banned or infracted for talking generally though.

Good luck with flashing the later version fw, please let us know if it re-enables Mass Storage Mode although i suspect your device actually has a hardware failure.