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. 

  • What map are you using? The default TopoActive, Outdoor Maps+ or a different map? When you select Current Activity the map display becomes garbled.

    And does the device also crash if you do a TracBack when you have a valid position fix?

    It could also be a defective device, maybe you can get Garmin to exchange your unit?

    Only the original maps are in the internal memory. Custom maps are on the SD card. However, the problem also occurs when the SD card is removed.
    TrackBack is performed after acquiring a GPS fix and, in any case, it should not crash regardless of the fix status.
    The issue was reported to Garmin; they responded and opened the warranty replacement procedure. I would have liked to wait for one last firmware update to see if anything changed, but I think I will proceed with the replacement.

  • I never had any luck getting my GPSMAP 67 (for the very short time I had it) to connect to my M2 MacBook Air using OpenMTP. Hunting around, one can find the older AndroidFileTransfer which worked flawlessly on the same Mac with the GPSMAP 67. My newer eTrex Touch 2 also works flawlessly with it as well (it also did not work using OpenMTP). Hunting down AndroidFileTransfer may be worth a shot if OpenMTP doesn't work (for whatever reason).

  • TrackBack is performed after acquiring a GPS fix and, in any case, it should not crash regardless of the fix status.

    Just asking because in the video you don't have a GPS fix. And indeed it should not crash regardless of the fix status, but it could very well be that the crash is caused by bug when doing a TracBack without a GPX fix...

    The map display becoming garbled makes me think it could be a hardware issue, so interesting to see whether the replacement has the same behavior.

    With the pace of software updates for the H1 so far I wouldn't expect a new update before beginning of February...