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

**Butters** · 1st January 2024, 10:51 PM

Originally Posted by askelly

.......
I have not attempted RMPrep because the device does not show in disk management - a requirement for RMPrep to work, yes?

Yes. However we may be able to format using SD card depending on the exact outcome of that failed last attempt.

Originally Posted by asprin624

askelly,

I think it is time to take your wife's advice here and take it to the dump to be recycled.

What's the fun in that. I've still got some things to try depending on what's in Update.log! That was a test as much as an attempted fix which i had him do with the SD text commands.

You can get Second Hand working Garmin Nuvi 1490 LMT Touchscreen GPS -Tested (Pre-Owned) from ebay.

Yes i'm sure he knows that. Plus if he could be bothered stripping it he might get the money back selling the parts.

Originally Posted by askelly

It's dead, Jim.

Probably it is mate, but i'd still like to know what's in update.log and also whether it was able to dump a ~4MB copy of region 41 as 41.bin in the card's root?.

........... All this learning should prepare me for any future mishaps

Yes that's the point, and that's the same whether we succeed or fail. The learning! Not just you but me also .... and the many unknown readers who don't comment but DO learn from this too. That's the essence of a public forum such as this .... co-operation and shared learning.

Have a great day (appreciate your efforts!)

You have a great day too. Please at least let me know what i've underlined above, even if you don't wish to try any further fixes. That way i can add to my experience otherwise i'll get nothing out of this because so far i haven't actually increased my knowledge. You see your 1490's problem is not typical of a soft-bricked device but neither is it clearly hard-bricked for sure.

**iwriteall** · 10th July 2024, 01:02 PM

hello

my device is zumo 396
ı accidentally format internal drive
i find the original firmware
i install garmin cure
than i flash it to prebooth mode.
i can see device as a usb disk, it is ok
but when i flash the original software, it restarts and it freezes at the "loading map" screen
also i recover alot of files after i formatted the internal drive, and i tried to copy all to internal drive include .system folder. but it didnt worked.

any suggestion?

**Neil** · 10th July 2024, 01:05 PM

Freezing on "Loading Maps" most likely means one of the .IMG files is corrupt. Try removing the detail map first, it's usually the culprit.

**Bellmac** · 17th October 2024, 11:47 PM

This involves a semi-bricked Nuvi 1350 (US/ North America I believe). It's old, but worked up to about a week ago. It froze while being used in a car and since then it stays stuck on the logo and keeps going off and on without booting or properly getting into pre-boot mode by plugging in the USB cable. I have tried both GarminCure3 and QuickCure3. Here are some details:

1. My 8GB flashdrive has been FAT32 reformatted as a properly as a FDD bootable device using latest version of RMPrepUSB.
2. The PC does not recognize it, unless I press upper left screen and plugging in USB cord.
3. I was able to get ID information using G7towin64: software version 6.30, HWID 0972, Unit ID 3827336719
4. Garmin Express does not recognize unit regardless of whether upper left is pressed before making USB connection.
5. Webupdater sees unit, but when attempting to reinstall, it says file is corrupt.
6. I have used GarminCure to make 2 firmware files (one cure and one original), but I am unable to install either one.
7. I am able to flash the Quickcure3 firmware (after renaming it to 097201000630), but I am not able to do anything more.
8. I am not 100% certain that I have the correct gcd file for this unit. I found links on this and another forum for nuvi13xxseries_GCDFile_630 and nuvi13xxseries_GCDFile-MTK_630. I believe that my 9720 does not use an MTK file. Garmin seems to have taken all firmware files off of its website. If I had an older version, I might have tried that as well.
9. I have tried renaming my GCD file to gupdate.gcd and putting it into both the root directory and a Garmin subdirectory of the flash drive.
10. I have tried to follow both the instructions at the start of this thread as well as the "How to unbrick a nuvi" doc file, but still no luck.
11. Maybe I am doing something obviously wrong.

Any advice would be appreciated. (Not sure this old unit is worth the effort, but I did like it.)

**Neil** · 18th October 2024, 02:16 AM

@Bellmac

Welcome to GPS Power and congratulations on making your first post here. Please make your next post as an intro thread in [Only registered and activated users can see links. ].

Worst case is that it's suffered some kind of hardware failure and if so, no software solution will help. Best case is that it's accessed some corrupt data while in use and that's temporarily 'soft-bricked' it. Let's assume the latter until proven otherwise.

Seems some of your info is contradictory. You say it's not "properly getting into pre-boot mode by plugging in the USB cable". However, preboot mode is required both to use G7ToWin and flash an RGN file with Updater.exe and you've been able to do so. BTW, GarminExpress uses only Mass Storage Mode or Media Transfer Proticol, neither of which are available unless a device can fully boot. Preboot is invisible to it. WebUpdater on the other hand can use preboot mode (aka "Garmin Mode") as well as MSM/MTP. Lack of MSM/MTP is also why Windows doesn't recognise it ... however when you press the upper LH screen corner Device Manager will see it under "GARMIN Devices" in preboot but only for about 30 seconds unless a flash is initiated.

It's unclear what you used to make Cure firmware. If you used the MTK version (for HWID 1104) and named 11041000630.rgn, then Updater would refuse to flash it because the file name and actual device's HWID don't match (Updater queries the device to check). Using the QuickCure RGN would flash however, if named 097201000630.rgn even though it's actually universal and HWID independent. QC3 doesn't always work to reenable MSM in all device-types and series, but in my experience, it has worked with all soft-bricked nuvi 1xxx devices to restore MSM. Keep in mind that a device with correct Cure3 or QC3 fw loaded will still appear to be 'bricked' because it sticks on the logo screen as it's designed to do, but importantly with MSM reenabled. The sole purpose of any cure fw is to stall the boot process BEFORE any essential files can be loaded. No corrupt files are used in the partial-boot even though they're still onboard.

So here's the link below to HWID 0972 V6.30 firmware. Re-make Cure3 from it named only "097201000630.rgn" and try to flash it.

Code:

Please Login or Register to see the links

If it does successfully restore MSM, follow the steps in "How to Unbrick ...." thread but keep in mind you might not need to re-format but only remove some files (see the initial post in the Cure3 thread). It you do have to re-format, use only RMprepUSB with correct settings and make a full file system backup beforehand too. If unsure, don't worry. There are no silly questions as far as i'm concerned so ask first - i won't bite ..... unless you don't make an Introduction thread in Members Presentation!

.

**Bellmac** · 18th October 2024, 09:13 PM

Thank you for getting me straight on the differences between pre-boot and MSM terminology.

So, I used GarminCure3 to generate both cure and original rgn files from the gcd file link you provided (I think that is what I used before).

Although I can initiate flashing of both files using Updater with it showing 100% upload, when it goes to erasing, I always get the attached error message
[Only registered and activated users can see links. ]

I have tried used Webupdater. It finds the Nuvi1350, but stays stuck on updating. I am not sure where the update file should be in order for Webupdater to access it. I assume Webupdater is looking for the RGN and not the gcd file. But again, where is it looking?

When I remove the flash drive, there is nothing in the drive except for the hidden System Volume Information folder that was created when the drive was formatted using RMPrepUSB.

**Neil** · 18th October 2024, 10:42 PM

Did you make a copy of the file system at anytime prior to doing the re-format? If so, look at the Garmin folder to find the file named GarminDevice.xml and open it in a web browser or text reader to look for this: <Model><PartNumber> near the start of the file. Behind it will be either 006-B1104-00 or 006-B0972-00 (my emphasis).

Can you say which 4 numerals written there please.

**Bellmac** · 18th October 2024, 11:17 PM

No, I have no copies. However, g7towin64 indicates HWID 0972.

**Neil** · 19th October 2024, 02:29 AM

Yes i understood that's what is shown by G7ToWin now. However, if you'd checked it with G7ToWin only after you attempted any flashing but had inadvertently used the wrong firmware, then the HWID may have been changed because the region layout could have been fully or partially re-mapped in an attempt to conform with the 'foreign' HWID. My query was made solely to determine whether it's original HWID was in fact 1104 but now changed to 0972.

Let's try another way. Have you ever used GarminExpress on your PC to update firmware on your nuvi 1350?

**Bellmac** · 19th October 2024, 05:12 AM

Yes, I updated numerous times with Express, including in 2024. Express currently shows a version 2025.20 City Navigator North America and Version 37.00 Time Zone Map available for installation.