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

@GEOMAPIX
If your 1390 is a US/EU firmware device then it has either HWID 0972 or 1104, not 0951, be sure to use the correct firmware for it. You cannot access any of the devices folders or files in preboot, only in Mass Storage Mode. Using Cure3 modified fw restores MSM. Most likely the map you were using when it bricked was corrupt, if that's been overwritten when you used GarminExpress to update it then there should be no further problem AFTER you now load original firmware (Cure fw cannot boot the device, that's the whole point of it .... it stalls the boot so corrupt files aren't loaded, allowing MSM access to remove them). Read this to fully understand the process: [Only registered and activated users can see links. Click Here To Register...].

yes you are right made a typo, the HWID is 972
wil try cure document tomorrow

Hi all,
i have an garmin drive 40 lmt, and accidentaly i formatting the internal memory as NTFS. After that, the device remain in garmin the logo screen.
I used cure3 to flash it and i reformatted in the fat32 the internal memory, and then i coppied the files from another device to internal memory, but still dont work.
In preboot mode, the garmin express communicate with the device, recognise him and make the update, but afther that, nothing change :(
HWID 2262
The firmware is 5.60
Can You help, please!

follow the[Only registered and activated users can see links. Click Here To Register...]
find your firmware [Only registered and activated users can see links. Click Here To Register...]

Quote:

---

Originally Posted by sorinnitoiu [Only registered and activated users can see links. Click Here To Register...]

Hi all,
i have an garmin drive 40 lmt, and accidentaly i formatting the internal memory as NTFS. After that, the device remain in garmin the logo screen.
I used cure3 to flash it and i reformatted in the fat32 the internal memory, and then i coppied the files from another device to internal memory, but still dont work.
In preboot mode, the garmin express communicate with the device, recognise him and make the update, but afther that, nothing change :(
HWID 2262
The firmware is 5.60
Can You help, please!

---

It would seem from that info that you still have the cure firmware loaded. Cure fw CANNOT boot the device, it will only allow Mass Storage Mode so corrupt files can be removed/replaced, or, in your case, a proper FAT32 reformat done using RMPrepUSB. You probably only need to load now the original fw back to the device in preboot.

Quote:

---

Originally Posted by skurtu [Only registered and activated users can see links. Click Here To Register...]

follow the[Only registered and activated users can see links. Click Here To Register...]
find your firmware [Only registered and activated users can see links. Click Here To Register...]

---

Solved, thanks you!!!

Yes, i solved with RMPrepUSB, thanks you!

Hi all, I have bricked Nuvi 5000

1. As mentioned it's a Nuvi 5000, G7ToWin don't show which FW but HWID is 1830
2. Suddenly device can't startup properly.
3. It seems to boot ok, but when finished loading map, it's stuck at screen reminding that maps are more than one year old and needs update.
4. PC can't see the device (only in preboot mode device are shown in device manager as "Garmin USB GPS")
5. Tried hard reset, and loading new map from SD.
6. I have all Garmin drivers installed.
8. I haven't tried Garmincure3 Tool etc, as I can't find any GCD files for this device,
so only have "Nuvi5000_410.exe" and "Nuvi5000_regionfileonly__410.rgn"
9. I can easy enter preboot mode.
10. Don't have NV backup.

Any help would be very much appreciated.

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. Click Here To Register...] 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. Click Here To Register...]
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.