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

No luck unfortunately. I get the same error not matter what I try. Strange that it died when it did but I guess there's not anything more I can do about it 😕

Don't know if you can help but:

1) Bricked device MODEL, Firmware version, HWID. Garmin Forerunner 920xt

2) Why and how the device got bricked. Nothing weird, just syncronizing with phone, then entered bootloop

3) Symptoms: what's wrong in your device?Constantly booting. Displays garmin logo for 7 seconds then boots again. Hard reset does not work. Garmin logo stays if I press the up arrow button

4) Does your pc sees your device ?Sees it if I connect it while pressing the up arrow button. However garmin applications do not see it.

5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.Soft and hard reset. Connecting to PC but not recognised

6) Do you have Garmin USB Drivers installed ? Garmin: USB Drivers Updates & DownloadsI think so

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

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 guideno

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

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

Thank you so much

@hiban
I'd guess that the watch is going into preboot mode when you press the up arrow. Please advice whether you mean it's seen in Windows Explorer (that's Mass Storage Mode) or if it only appears in Windows Device Manager (preboot) when you connect to PC with the up arrow held.

If it's seen in MSM then it may be very easy to recover. However it's only attaining preboot then we may be able to load cure fw to fix it so please then also post a link to the original firmware version currently loaded to it.

Originally Posted by Andy Waltson

.............
GarminExpress - does not see the watch, so it's not possible to update it in usual manner. WebUpdater fails as well, probably because watch memory is not visible at OS.

GE uses Mass Storage Mode to access devices. WU can use both preboot mode and MSM. In preboot mode the device will be visible in Windows Device Manager but not in Windows (File) Explorer.

GarminCure cannot convert it:

Processing D:\Fenix6SPro_6SProSolar_1660.gcd
This is a GCD file.
No patchable HWIDs detected
Processing FAILED

This is not a good sign. It may be more than just a non-typical firmware, see more below about this.

So I've tried open GCD using RGN_Tool_V094:
........
However there are no detected HWID and SW version (Question #1 - is it expected?).
When I've tried to convert it as is, I've received this warning: ........

Not showing a HWID in RGN_Tool is common with some modern Garmin device firmwares, however not showing the version is unexpected. Again, weird fw because also what is not typical is directly flashing region 5 with the bootloader. Usually in a more typical fw it's done indirectly by the (so-called) boot.bin (slight misnomer as really it's the ramloader and not the bootloader itself exclusively) being flashed to a virtual region 12 (hex 0C) and rgn12 then in turn flashes the bootloader to rgn5 and the x-loader to rgn43, both of which are actual physical regions of the flash. That's why RGN_Tool gives the message "..... I hope you know what you are doing!" because it's expecting the first section to contain "boot.bin" (Region 12/hex 0C, Section 0800) and not "fw_0505.bin" (Region 5, Section 0505). In typical devices rgn5 cannot even be flashed directly using any external method because it's protected against that and only can be written to by rgn12. If your fenix has rgn5 protected against external flashing then any attempt to flash an RGN will fail and that's potentially a huge problem.

After opening converted RGN, it looks the same: .........

Yes but they only look the same in RGN_Tool because all it shows on the GUI are the separate fw components. An RGN file and a GCD file of the same fw differ only in that there's a header added to the GCD file. Think of a GCD as a 'smart' file, kind of like a type of self-extracting EXE file. It's placed on the device and flashes the required regions from there quite independently but of course it requires the device to have fully booted for the GCD to be initiated. An RGN file can be considered as 'dumb', it doesn't do anything by itself and requires Updater.exe to flash its components directly to the appropriate regions of the device.

Question #2 - is it safe to try and upload it using Updater.exe into device?

Yes it is safe, that is it's safe provided the RGN file is not corrupt and it's named correctly and is suitable for the device. Correct 'safe' naming is XXXX01000xxx.RGN where XXXX is the firmware's HWID and xxx is the SW version without the decimal (e.g. 328801000160.RGN). Updater.exe on reading that format will first query the device and compare the fw's HWID with the device's reported HWID. If there is a mismatch it will stall without flashing, giving the message "No updates are available ...". Any other naming (e.g. OUT.RGN, Fenix6SPro_6SProSolar_1660.RGN or even altering the middle numerals 01000 such as 32880100160.RGN) will let Updater skip the HWID check and force the flash with potentially devastating results if the HWID of fw and device doesn't match.

Question #3 - is there any hope to resolve this headache introduced by Garmin?

Hope somebody will find time to answer...

I haven't checked in detail the forum link you posted however if this problem is both common and due to Garmin issuing a corrupt fw then they may be prepared to replace the watch regardless of it being out of warranty. I think it may be worth you contacting them before attempting a software repair yourself.

The problem for you is that to remove the (likely faulty) GUPDATE.GCD from the device's internal memory you will need to load cure firmware to re-enable Mass Storage Mode and Cure3 isn't cutting it by your experience (again, probably it doesn't like the unusual layout of it because of fw_0505.bin being where boot.bin should be). Flashing a good original fw as RGN via Updater may not be sufficient although that's worth a try for sure. If after flashing an RGN the corrupt GCD on-board continues to prevent it to boot then the only answer would be to manually make cure fw yourself (see this thread: [Only registered and activated users can see links. ]). As it's highly likely that it's the GUPDATE.GCD loaded by GarminExpress causing the problem, you could try only changing GCD to XCD in a hex editor initially.

I hope this at least helps you understand the likely problem and a possible solution to try if Garmin won't take responsibility for GE loading a bad GCD file. Post again if you think we can help further or you need some clarification. Sorry that this reply is not only wordy but a bit negative, however i'm happy to keep trying to help you even if Garmin won't. Good luck.

Hi Butters,

Thank you for comprehensive answer.
So, I've converted [Only registered and activated users can see links. ] into RGN using RGN Tool (by default - without any custom fields and without "Preserve current..." checkbox):

Spoiler: pic 1

[Only registered and activated users can see links. ]

and named accordingly - 328801000160.RGN.
Placed near Updater and flashed it, there were no errors and success message.

How it looked on initial stuck and during Updater flashing:

Spoiler: pic 2

[Only registered and activated users can see links. ]

After I've touched the Light button - "gear update" immediately has shown and progress was increasing. However it has stopped at the middle after few minutes and was not changing during ~5 hours:

Spoiler: pic 3

[Only registered and activated users can see links. ]

So, I've decided to switch it off... After enable there were no "gear update" anymore, but increasing progress bar only (stuck at the middle as well):

Spoiler: pic 4

[Only registered and activated users can see links. ]

Windows - does not see it as storage device, only Garmin USB GPS (same as before).
WebUpdater fails as well:

Spoiler: pic 5

[Only registered and activated users can see links. ]

however now it correctly shows firmware version (16.60, previously it was showing v03.00) and device ID (3312..., previously it was 0):

Spoiler: pic 6

[Only registered and activated users can see links. ]

Garmin Express - automatically detected device (previously it was not visible to it at all) but crashed...
So as summary - something has changed, watch is almost bricked but still alive. Not sure that I should wait more than 5 hours initially when it was flashing internally.

Regarding hex editing of custom cure - [Only registered and activated users can see links. ]
It is strange but I cannot find any enumerated file extensions at RGN (.img .GCD .gpx .gpi .zip .vpm). I've attached it.

Hope you will have some ideas what is happening.

@Andy Waltson

Originally Posted by Andy Waltson

....................
Windows - does not see it as storage device, only Garmin USB GPS (same as before).
WebUpdater fails as well.....

Question 1: What file type were you trying to flash with WU when it gave that message?

however now it correctly shows firmware version (16.60, previously it was showing v03.00) and device ID (3312..., previously it was 0)......

Well, it's maybe just still soft-bricked although not as badly as before with some functionality returned. At worst of course it may have a non-volatile memory corruption or even a hardware failure of some kind. See below for something more to try using WU.*

Garmin Express - automatically detected device (previously it was not visible to it at all) but crashed...

This is interesting because GE only detects devices in mass storage mode, not in Garmin mode or preboot mod like WU is capable. I wonder if the watch is somehow intermittently attaining MSM and GE crashed when MSM dropped out.

So as summary - something has changed, watch is almost bricked but still alive. Not sure that I should wait more than 5 hours initially when it was flashing internally.

No, taking that long to flash is not at all normal. Minutes is normal, not hours.

Regarding hex editing of custom cure - [Only registered and activated users can see links. ]
It is strange but I cannot find any enumerated file extensions at RGN (.img .GCD .gpx .gpi .zip .vpm). I've attached it.

You're correct, i couldn't find GCD or IMG in it using XVI32, didn't look for other names as that's conclusive enough for me. The extension names may in fact be there but in some encrypted fashion not able to clearly seen. Like i've said: "weird firmware".

Hope you will have some ideas what is happening.

Unfortunately i don't know, but i do still suspect that the problem is faulty/incomplete firmware loaded by GE. Usually a device bricked by a corrupt GCD file is straightforward to fix: Load cure RGN firmware to re-enable MSM, delete the GCD file from the device, load original RGN firmware and then the device will boot normally.

*When WU shows the screen in your pic 6, usually clicking next will prompt it to ask if you want to re-install the same firmware version.
Question 2: Have you tried that? If not try now and report what happens.


@hiban

Originally Posted by hiban

......
4.- PC recognizes it as "Garmin USB GPS" since I have the drivers installed.

Please also check that it's showing in Device Manager like it's showing in Devices and Printers. That will confirm for sure it's in Garmin mode/preboot mode.

However, I cannot access its content via mass storage and neither Garmin Express or Webupdater dectect it.

GE not seeing it is normal when it cannot access Mass Storage Mode. However WU should see it in preboot mode.

It seems by what the updater says that the current firmware the watch has is version 8.40 but I couldn't find it since garmin removed old firmwares from their web.

I can, however, "update" it with the updater. I dowloaded the 9.9 firmware of the watch, and I am able to do the update (while holding the Up button). The updater says everything went well, the watch stays for a little longer on the garmin logo but then bootloops again.........

I suspect your fenix has a faulty file onboard and the problem isn't to do with firmware given that result. If it cannot load an essential file during the boot process, e.g. an IMG file for the detail map, the boot process is either abandoned and started again (a "bootloop", as with your device) or it simply freezes and stalls on the logo/splash screen.

So, on the plus side for you is the fact that you can attain preboot meaning that a cure fw can be loaded to the watch, provided that your fenix's fw isn't like the other watch fw discussed above. Best try to make the cure fw and then if you can do so, load it with Updater to re-enable MSM. Good luck, please report back even if successful. (PS: Read here how to make Cure3 fw: [Only registered and activated users can see links. ]).

@Andy Waltson

All your manipulations with the .gcd file of the Fenix 6S Pro firmware don't make sense, because this file is securely encrypted.