My pleasure, i like mucking around with this stuff. When you open it up, please do consider my suggestion of leaving the battery disconnected for a while, an hour or even overnight to be sure. It may then power on again and we can try something else i've thought of. A very clever guy, user name kunix who made Cure3 and QuickCure3 also made a little known program he called 'gfwpack'. I guess that means Garmin Firmware Packer 'cos that's what it does. Reduces the size of a firmware. I think he did that primarily so as to enable a fw_all.bin which was too large to use in cross-flashing to modify another device's region14, because of the intended region's limited space.
Now, looking at what was successfully dumped from your device, even though it seems that there is ~10MiB before the damaged area starts, clearly the flash of fw_all.bin was fritzed. The entire (healthy) region has 16MiB available as i also mentioned earlier, however current and recent fw_all.bin component is only ~9MiB but it isn't loaded to your undamaged area of region14 (maybe doesn't miss by much, but still ...). However, a compressed (packed) BIN file might load properly. I've been able to pack V5.90 fw_all.bin down to under 5.5MiB so ... it..might..work.
Let me know if you can get it to liven up and if so if you want to try a last gasp attempt.



Likes:
Reply With Quote



Link to other forum removed as contrary to this forum's rules. In any case the file is attached and has been downloaded thousands of time from the initial post of our thread [Only registered and activated users can see links. 

Bookmarks