Thread: GarminCure3 tool - the new way to create cure firmwares for Garmin devices

I turn it off by taking battery out.

Before these days it can go to preboot, but after I downgrade to 4.52beta, It can not access to preboot anymore. (Pressing UP+Connecting for more than 30-60sec.)

I try several versions, 7.2/7.1/..down to 5.90 to find the one that doesn't has error during flashing.

I feel that I still have some hope because I can flash FW by updater.



Sent from my EVR-L29 using Tapatalk

You must give the full history of what happened so we can assist properly. Please read this and then supply all information asked in post #1: [Only registered and activated users can see links. ]. Additionally, please state clearly why you've downgraded to such an old beta version. Beta firmwares are often incomplete or buggy. Also, did you try entering preboot by holding 'Enter' button instead of 'Up' and also by powering on manually as i suggested, if it doesn't liven up after connecting USB? Also what do you mean 'flash fw by updater'? Updater.exe is only usable in preboot.

Thank you

1. Bricked Device Gpsmap 62s FW 6.90 HWID 1113 - Stuck at Garmin Logo after pressing Power on.

2. I updated regularly till 6.90 before it has the problem. As I remember it occurs during removing the weak battery and inserting the new ones.

3. Then it was stucked at Garmin Logo after pressing Power on. The only method to turn it off is to remove battery.

4. It isn't seen by any PC or Mac. I already updated Garmin USB driver to the latest version. I perform all procedure in PC as I see somewhere that Mac is not working for those procedure.

5. I run GarminCur3 from the first page step by step by using GUPDATE.GCD version 7.20 with Cure radio button.
I flash the cure 11301000720.RGN by running UPDATER. EXE in Dos command.
I activated pre-boot mode at the initial moment immediately. It needs to quickly press OK and OK 3-4 times until it transfers FW to the device.
It shows "Loading Software" on device screen.
After around 30 sec, the Error message pop-up on PC showing some code. The unit is stucked at Garmin Logo.
I need to remove power from the unit to turn it off.

6. I have the latest Garmin USB driver from Garmin website installed in my PC.

7. HWID is 1113

8. I read and try it from Docs.

9. I can reach Pre-boot mode intermittently only at the initial moment after pressing (UP+Connect Cable). Pre-boot is held for a time long enough to receive FW transferring.
After 15-25 sec, Pre-boot mode is disconnected.
I haven't try (Enter+Connect Cable)

10. I have all waypoints backup in Basecamp.
-------------
The reason I downgrade to lower version because when I UPDATER with the latest 7.20 version, it return with Error. So I tried with 7.10/7.00/6.90....until 4.52beta which I found it has no error.

I then flash up with UPDATER from 4.52/4.60/4.70/..going up until I found that 5.90 won't return any Error.

UPDATER shows OK on PC screen.

So I keep the device at 5.90
--------
I try many versions and my Gpsmap 62s is still stucked with Garmin Logo.



Sent from my EVR-L29 using Tapatalk

I also have a good help from one of the gentleman here to create a cure 5.90 sending to me. I will test it tomorrow.

Thank you to all for the help.

Sent from my EVR-L29 using Tapatalk

I flash the cure FW successfully with the quick pre-boot mode. but the device is still not seen by PC.

The pre-boot mode is held shortly during flashing FW and it disconnect.

It seems to be hardware failure.

Thank you everyone for helping.

Check if the firmware version changes after the firmware upgrade. Just run the updater.exe again and see the number. If it does not change, most likely your flash memory chip has failed.

FW version is changed every time. I use g7towin to check it.

Sent from my EVR-L29 using Tapatalk

Hello everyone,
I have a problem with a Garmin Atemos 100 when starting "SYSTEM SOFWARE MISSING", I tried to use Garmin WebUpdater without solving, the software detects the device but writes damaged file. I tried to use GarminCure by creating the RGN file with the correct name HWID01000FIRMVER but I still can't complete the procedure. I noticed that UPDATER.EXE fails to write recent firmware versions even of alpha 100. Maybe it is an RGN file problem?

Regards

@GK3000
"System Software Missing" message means at it's most benign that the main firmware data is corrupt and that's the most common reason. In such a case the device defaults to preboot mode and is can be flashed with a healthy RGN file using Updater.exe. Ensure you're using its latest version V2.80: [Only registered and activated users can see links. ].

At its most serious and rarer, the message indicates the flash chip has physical damage whic isn't able to be repaired by software means. Often in that case the device isn't defaulted to preboot and neither MSM nor preboot can be used successfully.

Generally, the use of Cure firmware is not indicated when "System Software Missing" message is displayed. The purpose of Cure fw is to restore Mass Storage Mode in a device 'bricked' by corrupt files which cannot be loaded on boot. That then allow files to be deleted or a reformat done which isn't helpful if the device's main firmware region (RGN14) is empty or corrupt, nor is it helpful or even possible if the chip's damaged. Please read the initial post of [Only registered and activated users can see links. ] and post any relevant information if you cannot successfully flash in preboot. If you have preboot available, use [Only registered and activated users can see links. ] to confirm the HWID and ensure you have the correct fw for your device. Flashing a correct and healthy ORIGINAL firmware RGN file when preboot's available nearly always fixes system software missing problem.