Quote:
.................
1) Bricked device MODEL: etrex 10
Firmware version: 2.80
HWID: G7ToWin Error was "USB Error. open_GArmin_USB: Failed getting USB Handle"
I think that means the device has already exited preboot. Many devices give very little time in preboot however once a query has been received by the device in the form of a data packet it will then hold preboot, awaiting further communication. Read the detailed information in [Only registered and activated users can see links. Click Here To Register...] of the G7ToWin thread. You may not even need the HWID in any case, read more below(*).
Quote:
2) Why and how the device got bricked: I tried to upload a new GPX Track to the etrex using my android-phone. When I connected the etrex to phone via usb otg, I was asked, if the device should be formatted to make it readably. I was a desperate idiot and I did give it a try. Since then the device can't read any gpx-track from the internal memory anymore. Also, all the data from the internal memory is gone. I don't have a backup of it ...
So the format was maybe done in a way that's not completely acceptable to the eTrex's OS. Garmin devices are often very particular how their internal memory must be formatted as you're probably aware. A correct format may be all that's needed.
Quote:
3) Symptoms: what's wrong in your device? Can't read gpx-files in folder Garmin/GPX anymore.
Do you mean the files that were there previously or some files you've added since? Of course all your previous on-board files are gone due to the re-format. Or do you mean files in a media card's Garmin folder?
Quote:
4) Does your pc sees your device ? Yes, my PC sees it and declares it as a normal drive.
Cure firmware is only used to fully re-enable Mass Storage Mode (MSM) so that faulty files may be removed or a correct format done.
Quote:
5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
I tried to connect it with garmin express. But it is not recognized.
Maybe because the format isn't quite right. GarminExpress uses MSM to access devices and an unacceptable format may not allow complete recognition.
Quote:
In preboot mode I tried the HW test, RAM and ROM get a "Pass", when BMap Chk gets a "Wait".
Is there still a basemap present though? It won't be unless you've since added one because the original gmapbmap.img would have been removed by the format along with all other internal files.
Quote:
I tried to format it using RMPrepUSB. When I use the GUI-Part, the Garmin Device is shown. But when I try to format the device the Error "Cannot find drive 3". I tried to use the CLI Version on an admin shell but RMPARTUSB.exe list does not list any devices.
This again may be due to the format previously done via the phone. Try to format it using the built-in tool in Windows Disk Management and then if that format doesn't allow normal working of the device try again using RMPrepUSB(#).
Quote:
6) Do you have Garmin USB Drivers installed ? Garmin: USB Drivers Updates & Downloads
No, I always used the device like a regular usb drive and I just copied gpx-files to the device.
Garmin USB Drivers are only needed to access the device in preboot mode. Load them to the PC again anyway to ensure they're up to date: [Only registered and activated users can see links. Click Here To Register...].
Quote:
7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID
G7ToWin Error was "USB Error. open_GArmin_USB: Failed getting USB Handle" If it is really needed, I will try again to find it.
(*)The HWID is only crucial if we need to load cure fw. As the device is partially working you may be able to confirm it's HWID other ways: [Only registered and activated users can see links. Click Here To Register...]. As you're in EU it's likely an EU localized device and if so will have US/EU etrex 10 HWID of 1304.
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
No I did not try to use the GarminCure3 tool. I don't think the firmware is the problem. The problem should be the malformated storage. So I don't want to mess with the firmware.
You may be correct about firmware, however Cure fw can also help to reliably re-enable MSM in the case of an incorrect format ... that's always needed if the format is the wrong type, e.g. NTFS instead of FAT32. Strange things can happen with only partial functionality if the format type is 'technically' correct but done to Garmin devices with the wrong tool.
Quote:
9) Can you reach preboot mode? If no ,have you followed this? Garmin devices preboot mode
Yes I can reach the preboot mode. In preboot mode I tried the HW test, RAM and ROM get a "Pass", when BMap Chk gets a "Wait".
We'll only need preboot as a last resort to load cure fw if further efforts to re-format don't work as suggested above(#).