I respect your decision and appreciate your sentiments and stating that the effort was "beyond the call of duty". I of course want to help you however there's a slightly selfish motivation as well because i can often learn something out of these 'unusual' brickings. On probability, it's likely a hardware problem anyway.

If you want to try erasing the nonvol without examining the firmware BINs you can simply change the update.txt file to read:

ergn,41
reboot

That'll completely vacate region 41 if successful and it'll stay that way until the device reboots, if ever, when the device itself will re-write fresh data but only partially restore it. If the source of the problem is poisoned nonvol data it will in fact boot successfully or at least boot far enough that Cure fw can be properly used.

BTW, your concern about the 14 & 127 bin files is understandable but entirely wrong. There's absolutely nothing personal or individual in those files which can be used by anyone else - nothing more that can be found in general info by examining the BIN components from a firmware GCD or RGN file for sure. I hate to tell you, but it's data in 41.bin that can disclose personal and device info, if a malintent had the ability to decrypt it and know what and where to look for in the jungle of the clear data. Very few ppl do know, outside Garmin itself, i can assure you. Have a look back at your [Only registered and activated users can see links. ], you'll see i removed the attachment immediately after i downloaded it to negate any chance of someone else getting their hands on it. As a Mod, i could see that i was the first and only downloader. I'll also remove the copy of it from my PC as well, not that i'd ever try to misuse it. Good luck and thanks for hanging in there thus far.