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

**Arva** · 9th May 2022, 01:34 PM

"* Be persistent in trying to get it to flash, it may take numerous attempts to flash a flaky device which moves in an out of preboot." if I am constantly in preboot mode even without button pressing how can the device move out of it.

Also it is unclear should I rename the firmware that is placed in the same folder as the updater.exe only 205001000960.rgn or 205001000960_cure.rgn? Using quickcure3.rgn do I need to rename it the same?

I tried a couple of times and I managed to get somewhere like 4-5 times. Once using an older version v2.7 (because I saw it was modified in 2012) but I got an error message "There is a problem with this GARMIN application...." than a couple of times with the v2.8 updater.exe and it asked me if I want to reinstall the same firmware version but when I clicked YES it went to a screen
"FENIX3 V9.60
Erasing...
(this may take a few minutes)" I left it there for more than an hour but nothing happened, progress bar did not move at all.

I was able to get to this point a few times but no progress after that and I have no idea why other times did not even manage to get here... it does not seem to be consistent.

In the meantime I read this post "How to unbrick a nüvi - step by step guide", and a couple of people had the same problem where they got the gps not responding error, in comment #70 you said "Connect a suitable USB cable directly to a REAR USB2 port of PC without a hub, don't use a front port or USB3 port" as I found out my laptop has only USB3 could this be why it can't get a connection?

When retrying the whole process should I turn off my device every time or is it not necessary because it is always in preboot mode?

Thanks for the quick reply (hope I can write thanks like this)

**Butters** · 9th May 2022, 11:37 PM

I didn't mean that your specific device is necessarily doing that (dropping the preboot connection) but it can happen with some misbehaving soft-bricked devices and if it does happen then persistence (and both timing and luck) are required to complete a flash. You can observe the Device Manager list to see if it's dropping out of there then reappearing.

ALWAYS safe-name the RGN file using protocol XXXX01000xxx.rgn regardless of whether it's original, cure or quickcure where XXXX is the HWID, in your case 2050. Using 960 (xxx) for the applicable software version 9.60 being used is preferable but the numerals don't have to match, that's more about identification.

Unfortunately the inconsistency in flash results you are seeing might indicate internal flash memory damage rather than it's dropping connection for another reason.

Ditch the laptop and find a Windows PC with rear USB2 ports, even an old XP one will do as you don't need an internet connection anyway. It might solve your connection problems but you'll probably need to load Garmin Drivers to it. USB3 wasn't around when Garmin designed Updater.exe so it doesn't always play nice with Updater even though USB3 is supposedly backwardly compatible with USB2 cables and devices.

Best practice is to force the device fully off before trying again however if it's dropping the connection due to physical damage to flash regions rather than attempting to re-start (boot-looping) then nothing can be done to complete the flashing.

**Arva** · 10th May 2022, 07:56 PM

Today I managed to use an old PC with USB 2.0 ports.

I'll try to describe what I realised: when pressing the START / STOP button while the device is OFF keep pressing while plugging in the USB cable, UPDATER.exe instantly recognizes it as FENIX3 V4.50 (which is weird because if I do not press that button it is always V9.60) and I was able to re flash it successfully I filmed it with my phone.

However after releasing the START / STOP button it just restarts and nothing else happens, no Mass Storage Media or anything... I tried to fiddle around with hex editor with this .rgn to change .RGN to .XGN, or .IMG to .XMG .... the only thing that this resulted was that the Diagnostic startup screen where the watch gets stuck now says ROM (2mb) check ....FAIL and watch light flashes.... also trying to re flash with the quickcure3 file it gives me an error message that says something like this: The garmin device is unable to program the requested memory region.

I was able to re flash it a lot of times trying with different .rgn files, and I could also get back where the diagnostic screen ROM check returned to PASS.... so I guess I was doing something. But this procedure was done only with the START / STOP button press procedure. Without pressing that button I could not re flash. I have no idea what that button does while the watch is OFF and get's connected to the PC. And why does it show like it is V4.50 instead of V9.60... I never read anything like this behaviour. When releasing that button USB connection gets lost and the watch restarts. Do you know of anyone that had any success of repairing a Fenix 3?

**Kris Poland** · 18th May 2022, 07:50 PM

Dear gpspower Community,

I request the help for bringing back to life the GPSMAP 276cx unit. Here is the history:

1) Bricked device MODEL, Firmware version, HWID.
GPSMAP 276cx, Firmware 3.70 (at the moment when problem occured), 2479

2) Why and how the device got bricked.
During normal shutdown the power logo which is usually briefly displayed stayed for long time. I noticed after several minutes, so took the battery off the device. When reinstalled battery, device was stuck on Garmin logo (checked for 5-10 min). The only way to switch off the display is to remove the battery. Not possible to switch off during very long power button hold.
The device was never updated by me. Several days before I uploaded new track before my trip on SD card. At the same time I enabled bluetooth and WiFi for the first time trying to connect to Garmin CONNECT. After that I booted the device maybe 3 times. Just before my ride I started device at home to check if I finally uploaded the truck several days ago, once I confirmed it is visible, I switched off the device and power logo stayed, then battery removed as mentioned. Since this moment never booted again.
I want to confirm that I haven't attempted any updates, files removal/adding to main storage just before the problem happened. Files were always updated using USB cable directly to MSM storage in GPX folder on SD card.
I had 3 years warranty and the unit is 3 years and 5 months old. Bad luck. Very rarely used during last 2 years (5 -10 times a year for 3 hours every ride).

3) Symptoms: what's wrong in your device?
It never booted again, no matter what I do (normally). Always stuck in Garmin logo.

4) Does your pc sees your device ?
Normally no, but after preboot mode (very long up arrow hold) will switch off the pre-boot mode and enter MSM mode. All files are accessible. It works every time.

5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
I first tried to update software using webupdater in MSM mode. It took a blink of the eye when reported that update is complete which was not true. Then I tried full cure with Cure3 using the only accessible firmware 5.80. Cure3 properly detected that 3.70 firmware is installed. Cure3 detected my HWID as 2479. The process always worked successfully, CURE firmware allowed to boot in MSM mode. It was identical to the forced one using up arrow key for long time. I did not notice any corrupted files, however I flashed the garmin main drive (SD card removed from the very beginning) using RMPrepUSB as in manual. With cleared drive I flashed the original firmware (5.80) and device behaved exactly like old one. Stuck at Garmin logo.

6) Do you have Garmin USB Drivers installed ? Garmin: USB Drivers Updates & Downloads
Yes, installed Garmin USB drivers just before dealing with Cure3. Never had any issue with connecting as USB.

7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID
HWID was taken from GarminDevice.xml which was accessible in MSM mode. It matched firmware I downloaded directly from Garmin website.

8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
How to unbrick a nüvi - step by step guide
Yes, by the book, did it twice (Cure->Original, again Cure->Original), always successful, no errors during the whole procedure.

9) Can you reach preboot mode? If no ,have you followed this? Garmin devices preboot mode
Yes, it was required to flash with Cure3. Holding UP key during plugging USB cable, Windows sound, immediately detected by Cure3 then. No issues, works like charm.

10) Probably no , but do you have NV backup?
Sorry, I am not sure what is NV backup. If this is just the software from internal flash drive, then before using Cure3 I backed up everything, as MSM can be accessed by very long holding UP arrow.

11) Once you get a reply and a procedure to follow from our experts, please give an accurate reply about what you did and obtained results.
Ready to reply

**Butters** · 19th May 2022, 02:55 AM

@Kris Poland
From the extensive information you've given and the detailed steps you've correctly taken to fix a 'soft-bricking' it seems that the device has a hardware problem, probably it's not repairable using any 'cure' firmware unfortunately.

**duvbdub** · 1st June 2022, 12:41 PM

Write please in your HELP request:

1) Bricked device MODEL, Firmware version, HWID.
Garmin Edge 1030, 2713

2) Why and how the device got bricked.
Someone decided to bitlocker their device by accident and I am trying to help them out.,

3) Symptoms: what's wrong in your device?
Loading course if you just turn it on, in mass storage its blank.

4) Does your pc sees your device ?
Yes

5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
GarminCure3, 01.0.0 Updater 2.8.0.0, Creating the Garmin Folder and GUPDATE file, reformatting FAT32 in Windows and using RMPrep tool,

6) Do you have Garmin USB Drivers installed ? Garmin: USB Drivers Updates & Downloads
Yes Garmin Drivers 2.3.1.2.exe

7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID
2713

8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
How to unbrick a nüvi - step by step guide
Yes GamrinCure3, issue is that I cannot get it to stay in preboot using Cure3 tool to copy firmware over, I have to drag and drop the rgn on the updater tool.

9) Can you reach preboot mode? If no ,have you followed this? Garmin devices preboot mode.
Yes

10) Probably no , but do you have NV backup?
NO

I have the rgn current file. 271301001329 beta created from GamrinCure2 and manually via RGN_Tool

***********
Updated.... managed to get into pre boot finally, after much trying.

I updated to 271301001329 Beta and seemed to flash the device.
[Only registered and activated users can see links. ]
I also downgraded to 271301001320 from the same folder above from Garmin and Flashed that.

I copied a GUPDATE.GCD from a friends Garmin Edge 1320 "Garmin" Folder and converted to rgn 271301001340 If I use that then get, The Garmin device is unable to program the requested memory region. (Maybe you cannot do this??)

The 271301001320.rgn Seemed to load /flash onto the device fine. It powers on but sits at loading profiles, cannot see in device manager.

Update again,
Rebooted Laptop and could see the Drives in Windows.
formateed again using RMPREP
Created Garmin Folder and copied GUPDATE_1320 renamed to GUPDATE, rebooted.

All working! thanks for the help

)

**~~peshoa~~** · 25th August 2022, 10:32 AM

Hello, hope you can help or at least to understand the problem of my unit.

1) Bricked device MODEL, Firmware version, HWID. - Garmin Drive Smart 60, HWID - 2268 (CHECKED WITH G7ToWin)

2) Why and how the device got bricked. - Received with BLINKING SOFTWARE MISSING

3) Symptoms: what's wrong in your device? - NOT STARTING (STUCK AT LOGO SCREEN)

4) Does your pc sees your device ? NO, WINDOWS CAN NOT SEE THE DEVICE

5) List all the procedures you already tried to unbrick it and their results and errors messages obtained. i TRIED THE CURE TOOL AND CREATED CURE FIRMWARE. MADE IT SUCCESSFULLY, THE MASS STORAGE MODE WORKS. I AM NOT ABLE TO SEE WHAT IS IN THE INTERNAL DRIVE. PROPERTIES SHOWS THAT THE USED INTERNAL MEMORY IS MORE THAN HALF OF FULL CAPACITY. I AM NOT ABLE TO PASTE ANYTHING IN THE INTERNAL MEMORY OR CREATE NEW FOLDER. I AM NOT ABLE TO FORMAT IT. TRIED TO INSTALL PATCHED FIRMWARE - SUCCESSFULLY, BUT STILL STUCK AT LOGO SCREEN. THE SYSTEM FILE IS "generic hierarchical"

6) Do you have Garmin USB Drivers installed ? Garmin: USB Drivers Updates & Downloads YES, I HAVE USB DRIVER INSTALLED AND WHEN I USE GarminCure3, THE DEVICE IS VISIBLE AND PUT IT IN BOOT MODE

7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID

8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
How to unbrick a nüvi - step by step guide

9) Can you reach preboot mode? If no ,have you followed this? Garmin devices preboot mode YES, I CAN REACH PREBOOT MODE

10) Probably no , but do you have NV backup? NO, I DO NOT HAVE NV BACKUP

11) Once you get a reply and a procedure to follow from our experts, please give an accurate reply about what you did and obtained results. DULY NOTED

I'm writing this because sometimes it needs a lot of posts before understanding what has been already tried and what is needed. Being precise will help you and us in saving a lot of time and curing it
Thanks

**Butters** · 26th August 2022, 06:14 AM

@peshoa
"System Software Missing" can mean a couple of things - the first, and most innocuous, is that the main firmware (Garmin correctly calls it 'software') contained in region 14 is either unreadable or missing. That's easily fixed by flashing the firmware again as an RGN file using Updater.exe in preboot. Additionally, if this is a software problem, the device would have automatically defaulted to preboot mode and without having to hold the device screen when connected to PC it will appear in both Updater's GUI and in Windows Control Panel's Device Manager (it will not be visible in Windows File Explorer however, for that a Garmin device needs Mass Storage Mode/Media Transfer Protocol available).
[Only registered and activated users can see links. ]

If it hasn't defaulted to preboot there may be a hardware problem, most likely in that case the flash chip is damaged and some of its memory is not accessible, in particular region 14.

So do you first have to hold the screen to place it in preboot or is it detected by Device Manager/Updater just by connecting to PC?

**~~peshoa~~** · 26th August 2022, 07:32 AM

Hello,
thank you for the prompt answer.
If I connect the device to PC, nothing happens. There is no reaction from PC. The updater is able to see the device ONLY if I hold finger on first letter "A" of the logo after restart...

**Butters** · 27th August 2022, 02:09 AM

Although 'System Software Missing' is a type of 'bricking', it's quite different from a device which cannot start because of a corrupt file unable to load during the boot-cycle. As i explained in Post #320 (if we discount a hardware problem) the message usually means the data is region 14 is lacking.

So to summarize the problem: You were able to flash cure fw and can then access MSM but are unable to read or format the internal memory. My conclusion: Region 14 is able to be written with new data - usually the 'System Software Missing' message would then not appear and the device would operate normally once original firmware was flashed, or it'd simply stall on the Garmin logo screen with no message at all if cure fw was flashed. Perhaps this device has had its memory corrupted, maybe even by a virus. Because you don't know its history we just need to make some assumptions ongoing.

My suggestion is to try a low-level format with cure firmware loaded. I doubt you can damage the device more but hereon it's all at your own risk. Download the tool from the link behind the spoiler below and see if it can re-format the internal memory to FAT32. If it ends up showing in Disk Management as 'RAW' after a LLF then use [Only registered and activated users can see links. ] to properly format it to FAT32.

Spoiler:

If LLF Tool cannot wipe the drive and at least revert it to RAW then the only other possibility is that physical damage has been suffered which cannot be fixed using software solutions.

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

Thread Tools

Display

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions