My GPSMAP H1 is continuously rebooting.

I had to reset it to the intial settings (a very difficult process, as the device didn't stop rebooting).

I deleted the Topoactive map of Greenland, and the device was OK.

Can Garmin check this Topoactive map, must be corrupt, so it blocks the device. 

  •   how did you manage to reset the H1 while it was rebooting?  I have the same issue however not enough time when pressing the power + page + enter button before the H1 goes into it's next booth cycle 

  • I'm on firmware 5.09 ,
    Unfortunatly mine h1i got into reboting cycle eathier, 

     when pressing the power + page + enter,  then t press   erase on screen  , it rebot and keep reboting.  

    Di'd you find a way to fix it ??

  • After a few hours of use with firmware 6.04, I encountered the same bug: continuous rebooting. This is not a minor shortcoming but a very serious bug that makes the device unusable. It shows how unreliable it is to rely on it during a hike.

  • The power + page + enter combination, followed by erase, has no effect:-(

    With the USB cable connected to the computer, holding down the UP arrow during boot, after about 30 seconds the device enters USB mode. I tried loading a previous firmware version, but on the next boot the GUPDATE.GSP file is not read and the continuous rebooting starts again. I don’t know how to get out of this situation!

  • If you want to revert to a previous firmware version, create an empty file called FORCE.TMP and copy it (together with the GUPDATE.GSP) file to the Garmin folder on the H1’s internal storage. On next power up the unit should ask if you want to install the software update.

  • Do you have additional 3rd party maps on your device? I put a couple of 3rd party OSM-based maps on an SD card, and with the SD card inserted my device (on FW 6.04) continuously reboots on power on. But when I remove the SD card, the device boots and works normally.

    On the Internal Storage I have TopoActive Europe 2025.10, and a couple of Outdoor Maps+ layers for the region where I live.

  • Removing the SD card was the first thing I did when the problem occurred, but nothing changed. The internal memory contains only the original maps that were present when the device was new.

  • I added the force.tmp file in addition to GUPDATE.GSP, but nothing changed: the reboot continues endlessly without offering any possibility to install the software.

    I believe that in many years of using Garmin devices, I have never seen a bug of this magnitude.

  • That sucks! Could very well be a corrupted file that triggers the reboot and prevents the device from recognizing the firmware update. Best contact Garmin support for a replacement device.

  • My H1 kept rebooting and could not be reset by pressing the buttons “power + page + enter” simultaneously. I sent my H1 back to Garmin asking them to replace or refund but was refused as the device was already 2 months old!  Garmin reset and reinstalled the device and returned the same unit to me.

    Garmin could not provide a root-cause of the issue. Without knowing the cause, this can happen again. Neither will I be able to reset the H1 on the trail myself. I see this as a high risk in remote areas.

    Asking how to prevent this from happening again, support’s initial reply was:

    ”.. We therefore recommended using the Garmin Explore app to plan routes and sync them to the GPSMAP H1. You also shared your feedback that the Explore app does not meet your expectations. In this regard, we would like to clarify that if third-party applications continue to be used for route creation and transfer, we unfortunately cannot guarantee that the same issue will not reoccur in the future. To ensure optimal stability and compatibility, we strongly recommend using the Garmin Explore app for route planning and data transfer..”

    As this is a weird way to blame the customer for their bugs, I challenged this and received a different reply that GPX files can be imported but should aways be imported via the explore software.

    I have the H1 back for 2 weeks.  Also updated from 5.09 to 6.04.  This issue didn’t happen again.  I hope that all these issues are solved with the firmware update but still don’t feel confident taking it into unknown terrain.