F255 Music stuck in 6-second bootloop (RTL Trap) & corrupted filesystem – Recovery advice needed

​Hi everyone,

​I'm looking for advice or advanced recovery options for my Forerunner 255 Music that is currently stuck in an endless bootloop (reboots exactly 6 seconds after powering on; the error log previously showed an RTL Trap crash).

​Current Behavior & Symptoms:

​Standalone boot: The blue Garmin triangle appears, stays on for ~6 seconds, then the device cuts off and restarts in a loop.

​Connected to PC via USB: The watch stays powered on reliably and mounts via MTP (Portable Device).

​Filesystem corruption: Deep inside the storage (Garmin/Apps_old/DATA/MEDIA/.../bb), there are 4 corrupted system nodes. In Windows Explorer, they show up with generic "This PC" icons, 0 bytes in size, with no filename or extensions.

​Any attempt to delete, rename, or move these files/folders fails with “The parameter is incorrect” or “The device has either stopped responding or has been disconnected” (the MTP connection momentarily drops).

​What Has Already Been Attempted:

​Directory Isolation: The original Apps folder was renamed to Apps_old (and a fresh empty Apps directory was created). Most subfolders could be renamed, but the corrupted DATA branch remains untouchable. The 6-second bootloop behavior persists after unplugging.

​Disk Check / Formatting: Since this is a Music model, it connects strictly via MTP (no drive letter assigned / not USB Mass Storage), making tools like chkdsk or FAT32 formatting via Windows Disk Management impossible.

​Hardware Master Reset (Non-prompted / unassisted): Attempted the standard button combo (holding Start/Stop + Back/Lap while powering on). The watch completely ignores it – no audio tones or vibration feedback occur, because the kernel crashes before the sound/haptic subsystem initializes.

​Garmin Express: Re-created the missing GarminDevice.xml with the matching Unit ID. Express detects and syncs with the device, but claims the software is up to date and does not offer a firmware re-install.

​Manual Firmware Flash (GUPDATE.GSP + force.tmp):

​Placed the official GUPDATE.GSP update file into Garmin/ and Garmin/RemoteSW/ along with an empty force.tmp file.

​Upon disconnecting the cable, the Garmin triangle appears, followed by the gear icon with a progress bar.

​However, after roughly 2 seconds (right at the start of the progress bar), the update process crashes and the watch falls straight back into the 6-second bootloop.

​Has anyone managed to recover a corrupted internal MTP filesystem on a 255 Music? Is there a known way to force this model into true USB Mass Storage (with a drive letter assigned), or bypass the boot check to let the firmware reflashing process finish?

​Thanks in advance for any insights!