Thread: DNX 7260BT no NAV, garmin module memory wiped, cannot access garmin module

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.

So , right now i should use windows explorer and remove everything beside the img_rscr.gir? and then flash the FW_all.bin?
or how would i go on about this ? should i go file by file and delete it -> upload fw-> check if working if not -> upload cure and start from the begininng ?
or should we just delete manually all files and then just move a gcd file into the memory and then upload FW_all ?
as im not sure where to start our search.
Manual file deletion to check if works and then at the end all files and put gcd file inside ?
Also i have a question , when im flashing into the memory the files how is it flashing it ? is it formating the memory with the boot.bin and FW_all and the pk files are moved inside the memory for the hardware to unzip it or is it unpacked and then moved into the memory and the hardware gets the file's? how does it exatcly work? how it affects the x:/Garmin/ folder?

Originally Posted by JacobsJ

So , right now i should use windows explorer and remove everything beside the img_rscr.gir? and then flash the FW_all.bin?

I've not got time to carefully review ORAK's procedures from the other thread at this time but i do think it's clearly different to what i'd instinctively do, which is to remove everything from the E:/ drive for a start. Then rather than re-use the GIR file from your backup I'd use a fresh copy of it. To do that use RGN_Tool to open the file 115501000431.rgn from the Update.zip i supplied in Post #2 > use the 'Save' button on the 2nd section to save pk_files66.zip somewhere > extract it to find a Garmin folder (containing sub-folder Langs and img_rscr.gir). Then write only that Garmin folder with contents to the root of E/:. The reason for using that Garmin folder and it's contents is we know them to be fresh and uncorrupted. Then safely remove it from your laptop and put the DNX back into preboot to flash a modification of the original fw i supplied (115501000431.rgn) with Updater.exe ... IMPORTANT: First remove the 2nd section (pk_filess66.zip) by ticking the check boxes for only 1st and 3rd sections (boot.bin & fw_all.bin) then save them as a new file but still named 115501000431.rgn. That's essential safety naming, don't use anything different and keep the new modded file separate from the original to save mixing them up. After flashing that modded RGN, without pk_filess66.zip in it, the DNX should start but maybe complain about other missing files, however MSM will again be available to replace more files using WebUpdater or GarminExpress (maybe not GE, i don't know if it works with KW devices). You may need to reset the device too, look to ORAK's guides for that.

or how would i go on about this ? should i go file by file and delete it -> upload fw-> check if working if not -> upload cure and start from the begininng ?
or should we just delete manually all files and then just move a gcd file into the memory and then upload FW_all ?
as im not sure where to start our search.
Manual file deletion to check if works and then at the end all files and put gcd file inside ?

As said above, i think ORAK's method may be different but i've written above how i'd do it and the reasons for that way are carefully explained in my previous post, i.e. about how the boot process works to discover files and how a GCD isn't (in other Garmin devices) looked for until after the boot cycle completes. That's why i'm suggesting using an RGN to load the original fw and the one in my Post #2 should work without the 2nd section as it's made from the original GUPDATE.GCD found in DNX7x60_9X60_431.exe which i'd previously got from the same link you later posted in your Post #5.

Also i have a question , when im flashing into the memory the files how is it flashing it ? is it formating the memory with the boot.bin and FW_all and the pk files are moved inside the memory for the hardware to unzip it or is it unpacked and then moved into the memory and the hardware gets the file's? how does it exatcly work? how it affects the x:/Garmin/ folder?

I think you may be conflating formatting with flashing and writing files. Go back and read everything again that i've written above and in my previous post #10. I do get that it's maybe hard to get your head around these things so in basic terms:

• A format of the file system in FAT32 is really no different to formatting a USB stick or media card in Windows, other than it's much safer to use RMPrepUSB for Garmin devices' internal flash memory.
• Manually placing folders and files or restoring them from a backup is exactly the same as what you'd do with a drive or other storage device on a PC. Drag and drop, copy and paste, restore from an image. Keep in mind if there's a corrupt file in your backup which is the cause of the bricking and you then simply write everything back that the same file will brick it again. So you must be careful in what you restore, best to use only minimal 'known-good' files for that.
• Flashing is an entirely different thing to simply writing folder and files. Flashing, whether done by RGN or GCD ultimately just writes the data in individual BIN files to various and appropriate 'regions' of the flash memory. Think of those regions as somewhat like small protected partitions on a Windows PC's drive. Except that in a Garmin device there are a possible 255 of those tiny invisible partitions, some of which we can copy and write to, via flashing, and some we can't access at all. But none of them can be directly seen nor accessed to be manipulated in-situ.

Finally, it's now up to you what you try from here. You can follow ORIK's method (which i'm yet to fully absorb) or follow what i've detailed being what i'd do for most any other Garmin device. What nobody can say at this point is which file has caused the problem. It might be that GIR file, or maybe a map IMG file or most any other file. It might even be that the basic format is wrong and ultimately it'll need to be re-done with RMPrepUSB but like i keep saying, re-formatting is last resort desperation for me. Adding back files progressively using 'known-good' fresh files is usually the best approach, then only add existing files from backups if you have no other choice but try to check them first. For instance, open IMG files in GMapTool and JCV files in ImgTool to see if they report errors.

I'm pretty patient, so you can keep asking questions if you don't understand still. I don't have time to look for links to the apps in bold above, but search the forum for them. I'm away from my home PC at present but if you can't find any you need just ask and i'll sort it for you later.

Thanks , I'll get right on it and illbe trying to remove manually everything and put the garmin folder only with flashing rgn file(no pk files in rgn)

We are in the home stretch now!!!!

Spoiler: image

[Only registered and activated users can see links. ]

Also could you explain what does what each file?
of course ignoring img_rsrc as i know that and garmindevice.xml
Edit I figured it out using Google gmapprom is the factory map that you get with the unit
Gmaptz is time zones
And the rest is additional files ,

Spoiler: image

[Only registered and activated users can see links. ]

EDIT , the problem was the gmapprom.img which was corrputed, as i added every file beside it and the nav still works
i will not be adding it as its just preinstalled maps from the factory and i dont relaly need them as i can download maps from other sites and put them on a SD card

WARNING
even though the gmapprom was bad rememeber to always flash the correct firmware
Images I took

Spoiler: image

[Only registered and activated users can see links. ]