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

You can remove the pressure from the LH top corner at any time after a loading/loader message appears on the device or just keep holding until Updater reports the flash results. Once an exchange of data starts between Updater and the device, preboot is locked and remains so while Updater is still communicating with the device.

A damaged flash memory is almost certainly now confirmed. It may fail completely at any time and in fact it's more likely to do that while being stressed during flashing attempts. You can of course continue in trying to recover it using the modified boot RGN but i'd just give up now as i really think there's very little chance of success now given those latest symptoms and you're clearly aware that a looping shift between the logo and white screen is not the required behaviour. Following the very first flashing attempt it should have fully re-booted after showing the logo splash screen where the copyright info usually appears. Sorry man, seems like "He's dead Jim". You can strip all usable parts like screen, battery, bezel/case and even un-sweat the USB socket and power switch from the board. They'll bring some $$ on ebay probably. The rest of the PCB has only junk recycle value. It's not feasible to replace the flash memory even if you had free access to the re-programming equipment required.

Interesting that it got so far as to create a 41.bin at least once. Did you keep a copy of it or note the size of the file? (It should be 4096 KiB in a healthy 1xxx but may copy as 0 in a malfunction device).

Out of further interest, did you notice if a file named "update.log" and/or "last_id.bin" was created in the 0972 folder at any time? (Between flashing attempts it's only necessary to remove last_id.bin, if present, so that the card's again recognised... but re-formatting does that of course).

EDIT: Just saw your 2nd update made several minutes back. The 'double-up' of HWID with UID is normal. I can't explain why that happens and what you said about expecting HWID to show 0972 is sensible. The fact that it creates the LOG file is telling me that the modified boot RGN works properly in Updater. Please post the contents of update.log file.