Thread: Garmin Fenix 6X PRO Bricked :(

Thanks for the detailed reply —
Here is the exact sequence of what I did, as accurately as I can reconstruct it:

*With all of my attempts GarminCure3 could never produce a RGN file, always got this warning:
"Processing F:\GarminCure3\329101000280.rgn
This is a RGN file.
got an exception:
XRgn::DetectHWIDandSWVER(): ramloader has invalid format

Processing FAILED "
So all of the firmware I flashed were always straight from RGN_Tool.

Spoiler: Click for images etc.

First (incorrect) flash

I downloaded firmware from this link (believe to be fenix 6X Pro):
[Only registered and activated users can see links. ]

From that drive I used GUPDATE.GCD (v28.00).
I ran the GCD through RGN_Tool without manually overriding the HWID.
RGN_Tool did not recognize the HWID and produced a warning (screenshot attached).

I then flashed the generated RGN using Updater.exe in pre-boot mode, without renaming the RGN manually.
After this flash, the device entered the update screen and became stuck in the state previously described.

Second flash attempt (still wrong HWID)

Believing the HWID to be 3368, I repeated the process:

Same firmware version (v28.00)
RGN_Tool with HWID override set to 3368
Resulting file named 336801000280.rgn
Flashed again using Updater.exe in pre-boot

Discovery of correct HWID and later attempts

Afterwards, using G7ToWin, I confirmed the device’s actual HWID is 3291 (screenshot attached).


I then attempted to reflash:
Firmware v28.00
Firmware v9.xx

Both override in RGN_Tool for HWID 3291
All were flashed via Updater.exe in pre-boot, but the device behavior did not change.


Current state:

Pre-boot mode is reachable
Device enters update screen
Update freezes part-way
No Garmin logo
MSM still unavailable
In Pre-boot the watch can be seen by WebUpdater, and GarminExpress.

Regarding Region 5
Because all flashes were done using Updater.exe with RGN files in pre-boot, I understand that Region 5 (fw_0505.bin) may have been overwritten during the initial incorrect flashes.

I do not have a way to confirm whether: an incorrect fw_0505.bin was written, or Region 5 is partially intact.

If there is any way to infer the state of Region 5 from these symptoms , I would greatly appreciate guidance.
Thanks again for taking the time to look into this.
*A link to my google drive with all of the screenshots firmware and tools i used: [Only registered and activated users can see links. ]