Garmin Nuvi 1200 that gets stuck on Garmin logo

**julianof** · 13th December 2023, 09:00 PM

Hi guys.

I have a Garmin Nuvi 1200 that gets stuck on Garmin

HWID: 1106
Firmware: nuvi12xx_GCDFile-MTK__630.gcd
Latest drivers
Operating System: Windows 11 and Windows 7

Tools used

Updater
RGN Tool
GarminCure by Kunix
G7towin
RMPrepUSB

Tests I did.

1- I converted GCD to RGN with RGN Tool with the name 110601000630.rgn and uploaded it to Updater. I did the preboot and when I wanted to load the firmware, after a while it gave the error "IOU_UTILITIES.CPP-203-2.8. Same error with Cure

2- I converted GCD to RGN with RGN Tool, just boot.bin, with the name 110601000630.rgn and uploaded it to Updater. I did the preboot and it ends successfully. Windows recognizes it but does not assign a letter to the drive. It is detected by Updater, but not RMPrepUSB. With Cure (only boot.bin) it gives the same error as in 1.
Once annealed and trying to update the complete firmware with Updater it gives the same error as in 1

3- I wanted to convert GCD to RGN with RGN Tool, only fw_all.bin and I get the error "Section 1 must be enabled. Normally it should contain section 0800 boot.bin" and it does not allow the RGN to be created

4- I tried with a microsd with a Garmin and Gupdate folder inside and it does nothing.

Any suggestions?

**Butters** · 14th December 2023, 02:37 AM

@julianof
I initially mis-read your post. In (2) i do see that you flashed cure fw but Disk Management hasn't automatically assigned a drive letter. To fix that simply right-click the drive information and select "Change Drive Letters and Paths" to assign a drive letter manually. If still having problems proceed as below:
I'm unsure why you attempted the tests described, other than (1) if it was cure fw. The complete guide for both making and flashing cure fw is detailed in the initial post here: [Only registered and activated users can see links. ]. Incidentally, the only part of fw which is modified by Cure3.exe is fw_all.bin. The boot.bin and resources.bin are unchanged.

Regarding your attempt to load cure fw via the SD method (4), that is usually impossible because a soft-bricked device likely cannot move far enough into the boot process to see a media card. In a healthy device you will note that "Loading Maps" appears on the device screen prior to a flash being initiated from the card. Consequently, any corrupt file which must be loaded (even if that is one of the map IMG files, loaded last) will have 'bricked' the device before the point of recognizing the card. Regardless if you still have an SD card inserted you should take it out because it might contain a bad file.

Behind the spoiler is a cure kit which should work for you:

Spoiler: Click

Instructions:

Extract the ZIP file somewhere convenient to find the folder "Flash_Kit"
Open the folder to find "110601000630.rgn" and "Updater.exe"
Drag the RGN onto Updater which will open it's GUI
Enable the Radio Button next to "USB Device" on Updater's GUI and leave it open and visible on your desktop with your mouse cursor positioned over the OK button
Ensure your nuvi's battery has at least some reasonable charge in it, don't ever try flashing when it's flat
Ensure the device is completely OFF - press and hold the power button down between 10 and 30 seconds if necessary
Connect a 'known-good' USB cable directly (no hub) to your Windows computer, use only a rear USB2 port of a desktop. Avoid a front port or USB3 port if possible
Holding the nuvi in your left hand with fingers behind it, use your THUMB to hold the upper LH corner of the screen firmly, maintaining a firm and steady pressure
Use your right hand to plug the cable into the nuvi's USB port while watching the window next to 'USB Device' on Updater's GUI
IMMEDIATELY you see the device details populated in the window adjacent to "USB Device", click OK or just hit the Enter key of your PC's keyboard
Keep firm steady pressure on the screen until Updater shows a success message or at least hold it until "Software Loading" or similar message appears on the nuvi's screen.

Once you have cure fw loaded and Mass Storage Mode is re-enabled you can proceed as detailed in the Cure3 thread to remove corrupt files. If you need to re-format the file system do so only using [Only registered and activated users can see links. ] with the recommended settings. Note that re-formatting should be a method of last resort if you're absolutely unable to determine which file is bricking it (do a backup anyway beforehand), or if it has severe file system corruption, or it's been mistakenly previously formatted as NTFS rather than FAT32.

**julianof** · 14th December 2023, 02:23 PM

Thanks Butters for answering. Below I attach a video of the procedure and the error it gives.

Video showing the procedure and error

Spoiler: YT video

Spoiler: pic

Does not show drive in Disk Manager

Spoiler: pic 1

Does not detect drive in RMPrepUSB

Spoiler: pic 2

Thanks

P.S:

Originally Posted by julianof

2- I converted GCD to RGN with RGN Tool, just boot.bin, with the name 110601000630.rgn and uploaded it to Updater. I did the preboot and it ends successfully. Windows recognizes it but does not assign a letter to the drive. It is detected by Updater, but not RMPrepUSB. With Cure (only boot.bin) it gives the same error as in 1.
Once annealed and trying to update the complete firmware with Updater it gives the same error as in 1

3- I wanted to convert GCD to RGN with RGN Tool, only fw_all.bin and I get the error "Section 1 must be enabled. Normally it should contain section 0800 boot.bin" and it does not allow the RGN to be created

I did the test guided by the following posts

Comment #18 and #21
[Only registered and activated users can see links. ]

Also comment #22
[Only registered and activated users can see links. ]

**Butters** · 15th December 2023, 02:09 AM

I'm on a phone just now so I'll look into your links fully when on a PC. Meanwhile please say what that first popup message from Updater early in your video states, this one:

Spoiler: Screen grab

EDITED TO ADD:
Both the threads you linked were about devices which displayed "System Software Missing" messages. That's usually a different type of bricking. That message is due to either (i) a corrupt/incomplete firmware in region 14, i.e. fw_all.bin's data (which problem is usually easily fixed), (ii) an incompatible bootloader in region 5 which is still a software failure but much harder to remedy than region 14 corruption, OR (iii) even more concerningly, a partially physically damaged or failing flash chip. In the case of the nuvi 265T although the problem was in fact (iii) it was able to be restored to somewhat working condition but probably not permanently. Flash damage was almost certainly the case with the nuvi 1690 too, but more severe and therefore fatal.

The symptom you have is different and probably also indicates a different problem, that is if it is in fact a 'soft' bricking rather than a hardware failure. Because your device is stuck on the Garmin Logo/Splash screen with no access to Mass Storage Mode it's unable to be seen by Disk Management, Windows File Explorer or RMPrepUSB. All of those programs require that MSM is functional in the device. Although such a stalled boot can occasionally be indicative of some flash damage it's far more often due simply to the presence of a corrupt file which is required to be loaded during the boot process. If an essential file cannot be loaded, the device freezes like yours does or sometimes a device might boot-loop. The fix for that type of soft-bricking is to load cure fw which prevents loading of any files on the next boot and although the device will still stick on the logo it will have MSM available again so that corrupt files can be removed or as a last resort a reformat done. After then loading original fw and replacing any needed files the device functions normally.

Fortunately you do have preboot mode active and in that protocol a Garmin device is seen by Windows Device Manager (under GARMIN Devices), recognized by G7ToWin and very importantly it's seen and can be flashed by Updater.exe. Conversely Updater.exe etc. cannot see devices in MSM. Also Disk Management, Explorer etc. cannot see a Garmin Device which is in preboot mode.

Hopefully you now have a more thorough understanding of what your 1200's likely problem is, also how the manoeuvrings done in those other two threads might be be inappropriate in your case. Sometimes simple soft-brickings due to a bad file do have other problems arise and quite frankly such complications can even be caused or exacerbated by inappropriate flashing attempts which are done trying to 'correct' a problem that wasn't there in the first place. I'm not stating that's what's happened here, i think only that some of your previous efforts as described in the initial post have been pointless and resulted in some side-tracking and time wasting at worst.

In addition to advising about Updater's first popup message, here's what i'd like you to do now:

Post to confirm that you used G7ToWin to obtain HWID of 1106 before you attempted any flashing with Updater.exe;
Confirm that all your recent subsequent flash attempts have been solely made using the files i supplied in Post #2;
Confirm that you have the latest [Only registered and activated users can see links. ] loaded to any computer you've used for flashing;
Advise whether you've tried loading [Only registered and activated users can see links. ];
Advise whether you are using a laptop or desktop PC; and which ports;
Advise whether you've tried different USB cables and/or different computers.

Note: The final message "IOU_UTILITIES.CPP-203-2.8" as reported by Updater in your video and shown also in your first SS means there was a communication error of some kind and it can have various causes. More details here:

Code:

Please Login or Register to see the links

That may clarify why i'm asking you for more info above.

**julianof** · 15th December 2023, 01:53 PM

Thanks for answering

Originally Posted by Butters

I'm on a phone just now so I'll look into your links fully when on a PC. Meanwhile please say what that first popup message from Updater early in your video states, this one:

Spoiler: pic

That's what the window reports

Spoiler: Screen gps

Originally Posted by Butters

[*]Post to confirm that you used G7ToWin to obtain HWID of 1106 before you attempted any flashing with Updater.exe;

Spoiler: G7toWin

Originally Posted by Butters

[*]Confirm that all your recent subsequent flash attempts have been solely made using the files i supplied in Post #2;

Yes, I used the one you provided.

Originally Posted by Butters

[*]Confirm that you have the latest [Only registered and activated users can see links. ] loaded to any computer you've used for flashing;

Drivers version: 2.3.1.2

Originally Posted by Butters

[*]Advise whether you've tried loading [Only registered and activated users can see links. ];

Updates correctly but does not recognize it as a drive

Originally Posted by Butters

[*]Advise whether you are using a laptop or desktop PC; and which ports;

PC(W11 y XP(VM)) and notebook(W7). On PC rear USB ports

Originally Posted by Butters

[*]Advise whether you've tried different USB cables and/or different computers.

Two different cables, one longer and one shorter.

Thanks

**Butters** · 15th December 2023, 10:35 PM

Originally Posted by julianof

That's what the window reports

Spoiler: Screen gps

Good, that's what i was hoping it was. Not an error message.

Spoiler: G7toWin

I know the HWID would be reported by G7ToWin as 1106 now, but what i asked was this: "Post to confirm that you used G7ToWin to obtain HWID of 1106 before you attempted any flashing with Updater.exe".
Are you able to state 'yes' definitely to that or not?

The reason for asking is that there are 2 different hardware versions of 12xx with HWIDs of 1106 and 0971 running different firmwares. Flashing the other's fw, original or cure, will change the HWID but the device won't ever function as it should with wrong fw. I'm wanting to eliminate any chance at all that's happened. If you're not sure 100% that your device was always HWID 1106 please say so and then we can look further. I'd prefer know with certainty if the HWID was or wasn't changed inadvertently of course.

Drivers version: 2.3.1.2

Latest version so that's not the problem.

Updates correctly but does not recognize it as a drive

I'm assuming you mean after using QuickCure3 the device still isn't recognised in Windows Disk Management or File Explorer.

So flashing QC3 doesn't also result in the IOU message you saw from Updater when using Cure3?

PC(W11) and notebook(W7). On PC rear USB ports
.............
Two different cables, one longer and one shorter.

Ok, very unlikely the comms issue is due to any of those then.

In "2-" of your initial post you mentioned that you tried flashing boot.bin only as an RGN and "Windows recognizes it but does not assign a letter to the drive". Please clarify which you mean: (i) it was seen only in Device Manager; or, (ii) it was seen in Disk Management but without a drive letter allocated?

Please answer all the 3 questions underlined. Be as accurate and informative as you can. If unsure just say that but don't guess.

**julianof** · 15th December 2023, 11:39 PM

Originally Posted by Butters

Are you able to state 'yes' definitely to that or not?

Yes, I definitely knew the HWID before flashing the first time.

Originally Posted by Butters

So flashing QC3 doesn't also result in the IOU message you saw from Updater when using Cure3?

Flashes correctly, without IOU error, but is not recognized in Disk Manager.
Reference: pic 1 in comment 3

Spoiler: pic 1

Spoiler: flash ok

Spoiler: Device Manager

Originally Posted by Butters

Please clarify which you mean: (i) it was seen only in Device Manager; or, (ii) it was seen in Disk Management but without a drive letter allocated?

It is visible in Device Manager, but not in Disk Manager.

Thanks again for your help

**Butters** · 16th December 2023, 12:01 AM

Thanks for clarifying.

A further follow up question about after you flashed QC3: Did you try disconnecting from the PC and re-connecting normally to see if MSM was then re-enabled?

It should have promptly exited preboot and entered MSM itself without a disconnect/reconnect if QC was genuinely successfully flashed, but sometimes that doesn't happen. If you didn't do a manual disconnect/reconnect or can't recall if you did, please flash QC again then report back.

QC works quite differently than tailored device-specific Cure fw so the final 'success' message rather than an error message is not remarkable even if it didn't actually work.

**julianof** · 16th December 2023, 12:22 AM

Originally Posted by Butters

A further follow up question about after you flashed QC3: Did you try disconnecting from the PC and re-connecting normally to see if MSM was then re-enabled?

After running QC3, when you disconnect and reconnect the GPS, it is still recognized by Device Manager, but not by Disk Manager, unfortunately.
I have recovered other GPS before, but this one looks complicated.

**Butters** · 16th December 2023, 02:19 AM

Unfortunately as we eliminate each possible soft problem the more likely a hard-bricking due to physical flash damage becomes.

Not done yet however, there's still some tricks to try.

I doubt it can read directly from a microSD card because it's stuck on the logo, but because preboot is working we should be able to get it reading from and writing to a card using a modified boot.bin as RGN. I'm sure you you know how to use a Hex Editor so follow the guide in [Only registered and activated users can see links. ] to make 110601000630.rgn and then try a backup of its nonvol region 41. Make the SD flash kit normally following [Only registered and activated users can see links. ] but don't have Ldr.bin in the 1106 folder with Update.txt file. This is the command:

Code:

Please Login or Register to see the links

With the card inserted, load the RGN to Updater.exe then connect the nuvi in preboot. Run Updater normally. Report result.

If unsure of how to do it, ask and i'll make the kit for you when i have time.

If it dumps region 41 ok then we can also erase 41 just in case it's got poisoned data in it preventing the boot or the completion of a successful flash. Depending on results we can maybe also do flashing of cure fw using the same method after also dumping the main firmware region 14 to check for problems there. But let's take it slow and step-by-step.

Thread: Garmin Nuvi 1200 that gets stuck on Garmin logo

Thread Tools

Display

Garmin Nuvi 1200 that gets stuck on Garmin logo

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions