Quote:
..............
1) Bricked device MODEL, Firmware version, HWID.
GPSMAP 62st, 4.80 (although self test shows 7.20 after trying flash, Updater still shows 4.80), 1113
It's possible that inconsistency of version # is due to a partially completed flash using V7.20 while the device had V4.80 onboard.
Quote:
2) Why and how the device got bricked.
It started when someone downloaded maps from somewhere. After this point the device started to have trouble starting. Sometimes it worked for a while and then crashed. Now it seems to never pass 'loading waypoints, tracks and routes..'
That boot-freeze is usually indicative of a device that cannot load some file/s needed for normal operation due to those file/s being corrupt or incomplete. Certainly *.img and *.gpi files are commonly the cause of such a 'soft-bricking', if indeed it is bricked whether with or without a coincidental hardware problem.
Quote:
Since this is a second hand unit it might be a previously existing hardware problem that happened to coincide with the uploading of new maps.
Maybe that's correct. In fact likely it has an intermittent hardware fault rather than solely a consistent soft bricking, and it could well be both as you mused. Perhaps it has a failing flash chip or a dodgy USB connection which is "making and breaking" and so it sometimes works long enough to only partially complete flashing or boot-loading tasks. But if it ALWAYS sticks on the same point in the boot cycle that's likely caused by at least one problem file. As said, there's always the chance it has both problems where the hardware fault manifested itself while it was being updated with maps or when the device was attempting to self-create a route or similar file in the memory and therefore the hardware fault was there before the bricking and in fact caused the latter.
Quote:
3) Symptoms: what's wrong in your device?
It never passes loading waypoints during startup.
It is recognized but any communication with the device fails.
for example. Flashing can start but fails.
Calling for the HWID I can see the firmware version, HWID, but device ID shows 0. I also get an error "USB Error: WaitComplete: Error waiting for overlapped I/O"
Opening device properties in windows, opening device manager etc is all very very slow or never responding.
Such communication faults and connection inconsistencies and some of the others mentioned later in your post are unfortunately symptomatic of an intermittent hardware problem.
Quote:
4) Does your pc sees your device ?
Not when normally connecting and starting.
The device is recognized in preboot and Mass storage mode
Garmin express never recognizes it.
WebUpdater only in preboot mode.
RMPrep only in Mass Storage
Basecamp never (not sure)
g7towin only in preboot
GarminExpress only connects in Mass Storage Mode and reads the device's Unit ID to determine if it can be updated. If the device has lost it's UID (yours shows "0" you said) then it won't even recognise it. It doesn't connect to devices which are in preboot or 'Garmin mode', only in MSM.
WebUpdater can see devices in both MSM and Garmin mode/preboot mode. Updater.exe of course only works for devices in Garmin mode/preboot.
PMPrepUSB is useful only in MSM, it can't see devices in preboot just like Windows Explorer, however G7ToWin is the reverse and only works for preboot.
Quote:
5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
-I've tried webupdater in preboot mode. Error message: 'update is damaged' (sorry not sure on the exacte message, this is translated), when trying again it shows device is not responding.
-I've tried GarminCure, both Cure and Original > Updater. it instantly goes to 100%. After a while it shows a generic error: 'There is a problem with this Garmin Application'. The error messages doesn't look important. The device stays recognizable. Upon trying flash again it says the version is the same, yes, utility disappears after a few seconds.
-I've tried formatting it, but as soon as the device enters mass storage mode the utility is 'not responding', same goes for explorer in general if I try to open the garmin's storage.
-Master reset, freezes after pressing 'yes', shuts off after 10s or so.
-Self test freezes and shuts off after 25s or so. RAM passes but ROM is still at WAIT.
I suspect there is either something with ROM or I/O. In that case, should I blast it with a Hot air rework station?
Yes i also strongly suspect that's the case and it's also the root-cause of any software bricking. You can try re-flowing the connections of the USB socket to the MO. I use lots of flux, a fine tip iron and leaded-solder (if you can get it it's better than the EU mandated stuff), also you must reinforce the socket's mounts because it's weak mounts from the factory that cause the soldered connections to fail. I prefer to recommend solder re-flowing over hot air but you can try that if you're experienced. Of course you still need to beef-up the mounts. If it is actually a failing flash chip it's not so easy. You'd need to source a compatible BGA chip and re-program it after installation (reballing will be required for that). The process of unsweating and reballing isn't physically difficult but needs some skills and is harder than repairing the USB so do the socket reflow first anyway. In particular reprogramming the chip is a huge problem for casual users even with some background knowledge, and the equipment to do it isn't common anyway. Generally not worth it even if you can get a suitable chip replacement.
Quote:
...............
8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
How to unbrick a nüvi - step by step guide
Tried
Was MSM only available when you tried with Cure firmware loaded, or does Updater stall every time and you've not been able to load any firmware, cure or original? If it does fail to flash Cure fw then you must have MSM available at least sometimes or you wouldn't have been able to try RMPrepUSB. It's very important you clarify this before we try anything else of a software nature.
