Gee, i guess i shouldn't be surprised. Old saying by anyone who's had much to do with them: "Garmin is so Garmin". The inability to dump all regions at once is a throwback to a characteristic of automotive devices even older than those which read/write the card as "1". Nonvol is in rgn41, rather than the later trend of using rgn154. I'm also a little amazed at the small flash size on such a complex device, it seems it's no bigger than 2GB. The encouraging news is that viewing the dumped regions this device seems physically healthy as far as i can tell. So, a software solution is likely but i still have a lingering suspicion of some flash damage but if is there but minor and confined to the visible parts of the flash we can easily work around that if the next steps fail. The File System is indeed in rgn48, another 'older' characteristic. When 48.bin is extracted and examined i see that there were 4 new files added at 15.32 on May 4, that's when you used WebUpdater and it bricked i guess? Two of those files are gupdate.gcd [update fw v5.60] and gmaptz.img [time zone map V22] which i've been able to compare to known-good files and their hashes match so we can rule them out for the present. The other two are in RemoteSW folder, 006B134300.gcd & 006B251300.gcd and they're my main suspects.

Spoiler: pics
[Only registered and activated users can see links. ]


There is another file in the GPX folder named Current.gpx added at 13.36 but not such a likely suspect and i guess that was the last time the aera was used before the update with WebUpdater at ~15.30 that day. Let's delete those 2 main suspect files from RemoteSW and see if that frees it up to properly load the V5.60 fw from gupdate.gcd on reboot. If this works, "Loader"/"Software Loading" or similar should show briefly on reboot and then it'll start normally, updated to V5.60.

You know the drill by now, look behind the spoiler. Open your card's 1364 folder and remove both last_id.bin and update.txt and replace with the new update.txt below. Load the modded RGN into Updater.exe then connect in preboot, etc.. Good luck.
Spoiler: txt file
[Only registered and activated users can see links. ]