IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this

**sogvortex** · 26th October 2022, 08:44 AM

On my etrex10 problem "There is not enough memory to complete this operation" resolved with formatting in Rufus. Maybe this help to other devices:

Spoiler: images

**alphastigma** · 30th November 2022, 12:52 PM

Hello I need help with my Garmin dezlcam LM. It has boot loop, with only GARMIN logo showing. I recenetly learned about pre-boot mode and Garmin Cure. I managed to turn on pre-boot mode and now i have Garmin logo with the LOADING... info but when i connect it to PC nothing happens, in device manager it shows no change. Is there anything I can do?

OK. I managed to make a step further. Turns out preboot mode only lasts a couple of seconds in which i had to click update in garmin cure. It showed loading bar for a second and my unit now shows garmin logo with "software missing" text. It's visible in device manager as GARMIN USB GPS under gramin devices. but now what? It doesn't show in my computer.

I also didn't know what to pick in garmin cure whether original or cure. I downloaded ~55MB software from

Code:

Please Login or Register to see the links

named "dezlCam_380.gcd" I hope it's the proper one. Using cure option with this file got me to when I am now. If i click the original It warns me that the current software is of the same version as I'm trying to load. If i continue it shows erasing for a seconds, my unit restarts and shows garmin logo as in the beginning.

sometimes after using cure after software missing text, it shows software loading... and it shows me this error

Spoiler: image

and just stays like that (it's visible in device manager but nothing apart from it)

I think the main problem is that I have like 2-3 seconds when i touch the space between G and A letters when it shows moving up and down "system" text. After that time the system text disappears and it shows Loading, but when loading is displayed the unit disappears from device manager - it's only visible for updater.exe during those 3 seconds. And when i click OK in updater.exe during this time it just shows "Erasing" bar for like one second and the unit reboots with "software missing info" I think installing software should take longer than just erasing... Could it be a hardware fault?

**Butters** · 1st December 2022, 01:04 AM

@alphastigma
It's important to understand some basics: Cure firmware intentionally cannot boot the device, it's sole intended purpose when loaded to an otherwise-healthy device is to stall the boot process before loading essential files thereby re-enabling Mass Storage Mode. That's to allow any potentially corrupt files to be removed or as a last resort for a re-format to be done. However, a heathy device shouldn't show 'software missing' message when stalled on the logo screen with cure fw loaded. That's because the only way a device with bad firmware shows that message is if it's gone far enough into the boot process to find that the main system software (as Garmin correctly calls the firmware in region 14, i.e. the data flashed from fw_all.bin) is either incomplete, unsuitable/foreign, corrupted or missing completely. Perhaps if you used a faulty cure fw file, it might show that message which is an indication of a region 14 problem. BTW, there is only one dezlcam afaik, HWID 2141 and it indeed has latest fw version of 3.80. You've used the correct firmware if your device matches the fw's HWID: [Only registered and activated users can see links. ].

As you've mused, i too suspect there's a hardware fault in this case. The only other reason a device shows 'system software missing' is if there is physical flash damage involving region 14 and that of course is not repairable using software methods such as cure fw. The Updater.exe pop-up message in your pic also supports the flash fault theory as it's indicating it cannot properly write data to some region.

To be certain you should download the GCD again and carefully remake the cure firmware then reflash it. When 'system software missing' is showing the device should be automatically defaulted to preboot mode thus making flashing with updater more leisurely than before when you only had a few moments to initiate the flash after manually starting preboot. Because it's in preboot (showing in Device Manager) it cannot also show in Windows File Explorer which requires Mass Storage Mode or Media Transfer Protocol enable. Preboot/Garmin Mode and MSM/MTP are mutually exclusive as you probably realize.

**alphastigma** · 1st December 2022, 12:06 PM

Thank you for such a detailed anwer. I wonder why the device shows "software missing" of "system software missing" but it's probably not that important. The device indeed stays in preboot mode during this text but when i click OK in updater.exe i get:

Spoiler: Click for Image

after clicking OK the unit turns off. I can turn it on again but i see no change.

Anyway, thanks again. It really looks like the hardware fault. I think i'll just look for motherboard or something if I want to revive it

**Butters** · 1st December 2022, 12:31 PM

Updater.exe shows that message about same version only because the same Version number is written into the cure fw as that currently loaded on the device. Updater queries the device in much the same way G7ToWin queries it to verify HWID and SWV. If you advance the Version in the cure fw to 3.81 or higher that message wouldn't show up. In other words that particular message isn't concerning at all, unlike the other error about data packets not being received which is concerning. It seems irrecoverable by usual software methods for sure. You could try to flash it using a modified boot.bin as an RGN. That's detailed in this post [Only registered and activated users can see links. ] but read the first part of the thread as well to help understand flashing from media card. Post again in here if you want specific help with the card method.

**ThatRinoGuy** · 6th February 2023, 05:05 AM

Hello--

I have a Rino 650 and 655t that I acquired second hand. They would freeze as they powered up displaying "updating waypoints and trackways". I used GarminCure3 to get access to USB mass storage. I installed FW 1247 and SW 5.10. Garmin Express crashes on my PC when I try to start it, but Garmin's other applications (BaseCamp, MapInstaller, etc) work to update software, and I can navigate the devices' memories via USB.

Now I can't get the devices out of USB. When I disconnect them and power them up, I get the Garmin logo and the USB symbol. The devices shut off shortly thereafter. I have deleted GUPDATE.GDC, but it looks like there's something else interfering with startup. I have other, functional devices to serve as templates, and don't see anything obviously interfering.

Thanks much for your thoughts.

Joe

**asprin624** · 6th February 2023, 12:12 PM

Have you remove the removable, rechargeable lithium-ion battery pack from the unit and wait a couple of minutes to make sure it is fully off.

Then add new rechargeable lithium-ion battery pack??

Do you have the maps on an SD card and how big is it.?
What type of maps are you using?

**ThatRinoGuy** · 10th February 2023, 01:33 AM

Hello, asprin624. These devices did not come with batteries. I used my own, which were fully charged to 100%. Also, they did not come with SD cards.

**asprin624** · 10th February 2023, 08:41 AM

It was about removing the batteries and SD card.
It did not matter if it came with batteries or SD card.

The point I was making was to let the unit rest before you put the batteries back in and then turn it on.
In hope that the unit will boot normally.
If it then worked add the SD card and start over with the maps on it.

It was just a trouble shooting guide.....

**ThatRinoGuy** · 13th February 2023, 08:38 PM

Following up on my last:

I was able to get both the Rino 650 and 655t back in operation by doing the following:

1) Installing GarminCure3 on my computer.

2) Connecting the devices in preboot mode.

3) Noting the software version installed in each device as detected by GarminCure3 in a firmware cure install.

4) Tracking down a previous version of the firmware here: [Only registered and activated users can see links. ]

5) Using GarminCure3 to install on the devices a previous version of software than what was already on the device. This overwrites the corrupted update causing the problem.

6) With each device now recovered and recognized via USB, updating the software to the current version (as of this writing, 5.10).

Voila. Best of luck to you folks, and a hearty thank you to Kunix.

Thread: IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this

Thread Tools

Display

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions