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

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. ]).