Thread: Garmin Nuvi 1200 that gets stuck on Garmin logo

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

[Only registered and activated users can see links. ]

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.