Thread: IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this

This cure method is only for devices with proprietary Garmin operating system and doesn't work for devices with Linux-based OS. Garmin made some in the past and nuvi 5000 was one such. [Only registered and activated users can see links. ] which will give you a basic understanding of the problems 'curing' such devices as nuvi 5000 and 8xx models.

The most likely problem is that either the detail map as become corrupted or a faulty script generating the 'map needs update' message is causing it to stick in the boot cycle. If the problem was indeed faulty firmware the device would likely be defaulted to a permanent state of pre-boot. I'm inferring from your info that you need to manually enter preboot by holding the screen and powering on, correct?

Regarding the firmware, the Linux devices don't use gupdate.gcd, they use a file named something like "B07xxxx.update" in a similar way. They can also update from an *.exe file for older fw versions and can of course use an .rgn file in pre-boot. Regardless, I doubt your problem is firmware anyway and you likely need to find a way to remove the map or script causing the problem.

I own a nuvi 5000 so I'm happy to use it to investigate further on ways to solve your problem however I do think we need someone with Linux device software experience to make a 'cure firmware' so you can enter Mass Storage Mode.

@ Alfiogigio
How big was the image you load on sd?
The nuvi 5000 can't read an image which is 2Gb or bigger.

@ Butters.
Thanks you reply, I didn't know about the Linux issue.
Now I tried PM Alexander2010 from this thread: [Only registered and activated users can see links. ]
He might be able to help unbrick Linux devices, but haven't been active on this forum since 22nd of January 2016,
so I don't have too high expectations that he will reply.
And yes, I manually enter preboot by holding the screen when powering on.

Now I also tried connect Nuvi 5000 to Linux computer, but still not possible connect as mass storage device.
Maybe there is some way I can delete map file from device via SD Card ?

@Jeanet
I tried loading full Europe NT, and Nordics (365 MB) on a 4GB SDHC Card.

I'm not at my usual PC so cannon check the firmware myself. If you can use a hex editor then open the firmware and search for the commands rrgn (copy), xrgn (overwrite) and ergn (erase). Search also as (for example) r.r.g.n where "." is a wildcard character. If the commands are in the firmware then it's maybe possible to use ergn to erase the detail map. The problem I foresee is that SD text commands need to be initiated by Ldr.bin [boot.bin] in 'normal' Garmin-OS devices and I have no idea how to extract the appropriate BIN file from an *.update or *rgn Linux firmware file.

I know how to use Hex Editor, unfortunately ergn is found only once,
in a position where it makes no sense to me (at 00886a7e0e).

Originally Posted by Alfiogigio

I know how to use Hex Editor, unfortunately ergn is found only once,
in a position where it makes no sense to me (at 00886a7e0e).

That doesn't sound promising. You could also try to edit the firmware yourself if you can find map file extensions mentioned in it. Changing any instance of ".IMG" to say ".XMG" does work with Garmin proprietary-OS firmware as a 'cure' to prevent loading maps. I can't say such a thing will work with Linux based-OS firmware and it may even 'brick' the device more seriously so all at your risk. Of course if that does work in the same way as 'normal' firmware, once the edited RGN is flashed in preboot no maps will be loaded on attempted boot and Mass Storage Mode might then be available to the device. Someone with Linux software experience might read this and comment hopefully, as that's only a stab in the dark guess.

.IMG and .XMG are nowhere to be found in firmware.

But problem are solved, by keep hard reset many many times, until device finally start up properly.
Now I found, that there was a bad (locked) IMG file on the device

Nice find! Every now and then, especially with older devices, a healthy one will fail to load maps on start up and present you wilh a screen without roads and showing only the vehicle icon. It might be only one in a hundred or many more boots when it happens and of course in an otherwise healthy device the next boot, whether done as a reset or normal boot, usually succeeds fully. I have a nuvi 765 US that's particularly prone to it. Now that little curious quirk can be used to advantage with a boot-looping device which will boot to 'Loading Maps' and then restart over and over, indicating a corrupt IMG file. By leaving it charging turned on for an extended period, maybe overnight or a day or even more, eventually it will fluke a boot without loading any .img files and you find the device fully booted but the Map screen showing no roads, only a lonely-looking vehicle icon. Then provided you don't let it reboot it will have MSM access and the offending map, which is nearly always a detail map, can be removed.

BTW, I didn't mean to look for .xmg too. I meant look for any instance of .img and change it to .xmg or it could be anything, .zzz or whatever provided it's not a used extension. It's just easier to substitute 'x' for the first letter that's all. It's really not surprising that the file extensions aren't in the Linux firmware but I've also checked multiple ways and you're right of course. If they were there us common folk would have been making cure fw for Linux devices years ago. Searching either as Unicode Latin or with a wildcard "." (i.e. ".I.M.G.") works with Garmin proprietary-OS firmwares and finds multiple references of ". I M G" and other common extensions which can cause 'bricking', such as gpi, gpx, vpm etc. Nobody bothers with that tedious method since the brilliant kunix came up with his Cure3 and QuickCure apps to simplify/automate making cures. Some more info here: [Only registered and activated users can see links. ]. I know for sure it can be done to make Linux cure fw but the guys who can do it just don't seem to post here anymore.

Originally Posted by sbihue

Pl. Help

1. Bricked Nuvi 2597 HWID 1582 S/W ver 440
2. Accidentally formated the internal memory while intending to format the SD card
3. Device now just boots into the Garmin screen, no filesyetem access to internl devide memory
4. No, PC does not see the device anymore
5. Downloaded GCD files, ver 440 through 550 from [Only registered and activated users can see links. ]
Ran GarminCure3 and created cure file with ver 440
Applied using updater and got message "updating successful"
The device is NOT detected by the PC. Garmin Express also doesn't see the device either
6. Yes, Garmin driver's are installed (as part of Garmin express)
7. HWID is 1582 (from original GarminDevice.xml)
8. Yes, tried that (Pl. see #5 above)
9. Yes, In preboot mode I can see System (and loading when applying the update using Updater). The screen is stuck at the GARMIN Logo
10. Sorry No, my bad, No NV backup
11. Waiting for your response

Thank you


Update
After reapplying the GarminCyre3 on the manually modified RGN (converted from 440_GCD with hexedits), the PC can now see the Garmin volume (Win 10). The drive is mounted as:
GARMIN (E)
System Volume Information

Garmin Express however can't see the device. Looks like one or more files/folders need to b erestored. Unfortunately, I have none backed up

Firstly you must understand that cure firmware cannot boot. It is designed that way so that Mass Storage Mode can be attained [you've now got that], once you have MSM it's possible to either (i) remove any corrupt files from the internal memory [you have nothing loaded], or (ii) allow a correct re-formatting to be done using [Only registered and activated users can see links. ]. Formatting with Windows built-in tool or even worse in FAT32 using Mac OS/Linux often isn't successful for Garmin devices. It seems you have an old file system backup so you can load that after you format with RMPrepUSB and then restore your backup and finally load original firmware after which it should boot fully. Remove any gupdate.gcd file from your backup before you restore. If it boots correctly GarminExpress will detect it properly and you can update old files and maps as necessary.

Post again if you have furthers difficulty after following the above steps.