Congratulations. That's a great result for "the blind leading the blind" isn't it? But we ain't outta da woods yet mate.

A bit more explanation of what's happened with QuickCure so you'll understand my note of caution above. As i said, there's no firmware involvement at all in QC's process using a modified ramloader (boot.bin) to partially boot the device only to a point before before essential files are even looked for, unlike with Cure3's which uses an unmodified ramloader with modified main firmware (fw_all.bin data in rgn 14) to prevent essential files such as map IMGs, voice VPMs, etc. from being loaded. Regardless, for us observing it, the process outcome appears the same during the partial boot process. i.e. if the splash screen can be displayed, the device freezes on the Garmin logo (and in your case it may still be a black screen). That's the point at which it's stuck in the boot cycle whether QC or Cure was used, but very importantly, with MSM re-enabled which is the sole aim of using any type of soft-cure[/]: i.e. [i]To get into the file system via MSM.

So.... No firmware has been involved in partially-booting the DNX enough to get back MSM. Now we can get on with looking for and removing/replacing faulty files, maybe removing everything and putting back only minimal folders/files - or as a last resort re-formatting the visible file system. Then we load original firmware which allows normal booting. What do you think will happen if we do indeed have some partial flash damage and region 14 is affected? Remember, 14's fw_all data is essential to a normal boot process along with other regions. Answer is, it still won't start and you're back to square one. So cross your fingers.

Now you have a good backup i would probably initially go with just removing everything from the file system and copying bacj only the minimum and known-good files required, for the time being (without formatting the internal memory). We know QC works so it can always be used again if needed. My suggestion therefore is to follow ORAk's procedures from the old thread from this point. Keep in mind that while cure is loaded the device may not *read a GCD fw file (see below) so original fw is best flashed back directly to regions using an RGN file. The only difference between a GCD and an RGN file is the header, the rest is identical.

*GCD files are somewhat like a self-extracting EXE file. The device looks for a new version GCD at the end of each successful boot and examines it to determine its version. If it finds a later one, it will initiate it, and it then writes its component/s to the appropriate region/s. So, can you see the problem if cure fw is still loaded? It doesn't even get far enough to load any files at all, that includes even looking for an updated GCD. Therefore, after sorting out the files, you'll likely have to load an original fw RGN file using Updater in preboot. That's certainly the way it works with other Garmin devices anyway.

Ask questions before proceeding if you need. I can't guarantee specific answers though, i'm still learning about these devices just like you. Generic information i can impart, however. Good luck.