GPSrChive Discussion Forum

Had the same issue where the device would boot and then restart just before the checking maps part of the boot process.

On internal storage I have TopoActive Europe 2025.10 plus Outdoor Maps+ layers for the region where I live. On an SD card I have TrekMap Italia Abruzzo region (free map that I used to test official maps purchased from Garmin) plus several 3rd party OSM based maps for the Netherlands.

The device starts normally without the SD card, or when the SD card only contains the Abruzzo map plus a single 3rd party map for the Netherlands. But it gets in the boot/crash loop with more than one map for the Netherlands.

Interestingly enough when I insert the SD card with all maps on it when the device is already on, the maps get recognized properly and can be enabled and disabled via the Map Layers menu. But when power cycling after this, the unit ends up in a continuous boot and restart cycle.

NB the restart issue with the map dashboard and elevation data seems to be fixed in 6.04 so that seems to be a different issue than this one.

To add to my previous post: I did another test, this time installing the maps on the SD card via Garmin MapInstall (from GMAP sources, directly from a Windows computer to the SD card), instead of copying the img files downloaded from the map provider.

This seems to work, no more boot loop when powering on the H1 with the SD card inserted. Maps are recognized correctly and can be enabled/disabled from the Map Layers menu. Only difference is the name of the layer, it seems to be the name I renamed the img file to after MapInstall completed installation of the map on the SD card.

Only difference is the name of the layer, it seems to be the name I renamed the img file to after MapInstall completed installation of the map on the SD card.

So the filename of the mapset itself (ex. mapset.img) has no effect...at least after MapInstall has processed it and sent it to the unit. I've never heard of the requirement that a mapset needs to be (supposedly now according to Garmin) sent to the unit via MapInstall.

If this is indeed the case, pre-compiled (or compiled mapsets NOT using MapInstall or using the GMAP map source) which are common as dirt should be considered incompatible on the H1/H1i units when run from an SD Card.

This was never the case with past units. This sounds more like a quirk or bug that Garmin is hiding behind this "requirement" for the unit to operate normally.

Interesting

WallyGator wrote: Mon Dec 29, 2025 1:41 am I've never heard of the requirement that a mapset needs to be (supposedly now according to Garmin) sent to the unit via MapInstall.

No such requirement exists.

We are using multiple side loaded IMG maps on our H1i Plus's and eTrex Touch 2's without issue.

WallyGator wrote: Mon Dec 29, 2025 1:41 am

Only difference is the name of the layer, it seems to be the name I renamed the img file to after MapInstall completed installation of the map on the SD card.

So the filename of the mapset itself (ex. mapset.img) has no effect...at least after MapInstall has processed it and sent it to the unit. I've never heard of the requirement that a mapset needs to be (supposedly now according to Garmin) sent to the unit via MapInstall.

If this is indeed the case, pre-compiled (or compiled mapsets NOT using MapInstall or using the GMAP map source) which are common as dirt should be considered incompatible on the H1/H1i units when run from an SD Card.

This was never the case with past units. This sounds more like a quirk or bug that Garmin is hiding behind this "requirement" for the unit to operate normally.

Interesting

I guess it’s just a bug where multiple img files on the SD card (or possibly on the internal storage as well) with some specific condition that I don’t know trigger a crash when the device checks the map files.

Installing the same maps with MapInstall is apparently a workaround for me that doesn’t trigger the bug.

I’ve reported the issue to Garmin Support, let’s see if they can reproduce the issue.

What size card? Brand? Type? Formatted how?

What size are the maps?

GPSrChive wrote: Mon Dec 29, 2025 6:35 pm What size card? Brand? Type? Formatted how?

What size are the maps?

The SD card is a SanDisk 128GB High Endurance microSDXC card, formatted as exFAT using the SD Memory Card Formatter tool.

I had the following maps installed on the SD card:

• OpenFietsMap Benelux, 1,37GB
• Freizeitkarte NLD+, 1,13GB
• Speichenkarte NRWplus, 3,62GB
• OpenTopoMap Netherlands, 754,2MB
• Frikart Netherlands Roadmap, 562,2MB
• Frikart Netherlands Topo Summer, 598,2MB
• Reit- und Wanderkarte Nordsee, 3,32GB
• Garmin TrekMap Italia v6 PRO, Abruzzo region, purchased (for free) from Garmin.com and installed with Garmin Express

But as I mentioned I only got the device to boot normally with the SD card installed with only the Abruzzo map and a single Netherlands map on it (I believe the OpenFietsMap one, but it could also have been the Freizeitkarte).

This thread on the Garmin forums has reports of a couple of users also encountering a continuous rebooting issue possibly, but not conclusively, related to map files.

GPSrChive wrote: Mon Dec 29, 2025 2:58 pm

WallyGator wrote: Mon Dec 29, 2025 1:41 am I've never heard of the requirement that a mapset needs to be (supposedly now according to Garmin) sent to the unit via MapInstall.

No such requirement exists.

We are using multiple side loaded IMG maps on our H1i Plus's and eTrex Touch 2's without issue.

I know that and you know that but does Garmin know that?

As this bug has materialized and grown and with reports by JungleJim and possibly others that maps sent to the device using MapInstall alleviates the issue. Hopefully, Garmin won't be suggesting that users now load maps to the device via MapInstall to help cover their butts for this bug (if they actually deem it as a bug and not some sort of user error). Garmin seem to now be recommending that users not use third-party software but rather use Garmin Explore for "route planning and data transfer" as well as transferring GPX files to the unit after some have found issues when they are transferred in other ways (read the 13th post by user 7518644 at link provided by JungleJim above).

I don't recall ever having these issues with in the past with previous units by simply copying a pre-generated IMG mapset to any of my many previous Garmin units.

Two weeks ago I had this self same issue. The device would not boot and just cycled through the various splash screens.
I contacted tech support at Garmin Europe in the UK. I tried all the tests that they asked me to do. I sent them screenshots of the activity. The device would not do nothing asked of it
I had a replacement within three days having returned the faulty unit.
Fingers crossed on My fourth device
The first one had the same issue within days of receiving it immediately after the launch date.
The second one failed because the activity button did not work. It had become detached from the motherboard.
The third one has been described above so I am now on the fourth.
What can I say?
I’m going to South Africa in the coming days and I’m going to take my trusty 67 with me!

Glad you have a backup plan! Enjoy your trip!