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

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. ]

Great result, congratulations. I see you've been busy while i was catching some ZZZZZ's downunder huh!

Yep, if a 'bricking' is due to a corrupt IMG file it is most often one of the detail maps (gmapprom.img; gmapsupp.img; gmapoem.img) in the Garmin folder which has caused the problem. Very rarely is it the basemap (gmapbmap.img) as it was for mylona79 in the old thread, or any other ancillary map such as the time-map (gmaptz.img).

Is that a complete list of all files/folders within your DNX's Garmin folder?

I'm asking that because on checking specs it's clear that, unlike the senior model 9260BT, the 7260BT doesn't have ASR (automatic speech recognition) capability, nor can it use gmap3d.img for 3D buildings view in cities, however it can show JunctionView images so along with other usual folders there should have been a JCV folder within the Garmin directory with *.jcv files specific to that gmapprom detail map. A JCV folder should also work from a Garmin folder of the SD card however, so if you want to use that feature with the replacement map you can put that folder in SD:/Garmin too. That will very much depend on Garmin having issued device-appropriate JCV files matching their EU NTU mapping because your device uses the JCV file-type for the very old nuvi 7x5W devices dating from ~2008 ....so you may not even be able to get JunctionView to work anyway.

About using files on a media card generally: Note that perhaps only gmapsupp.img naming may work for a detail map in SD:/Garmin. Perhaps other naming limited to 11 letters (e.g. "anyname.img") might working in SD:/Map folder but i doubt it seeing the unit's internal file structure is of the older type (there isn't a ".System" folder present and maps are in the Garmin directory). Also that style of Garmin device exclusively used NT format detail mapping and Garmin has now discontinued NT for European maps, issuing only NTU format (capable of displaying Unicode characters) so if you have a problem getting an NTU detail map img to display properly there is a workaround by changing the CP number which may work if the most recent firmware from January 2014 (V4.31) doesn't support unicode and causes navigation guidance problems.

N.B. The *.sum files are only checksums and can safely be removed.

This thread can now serve as a guide to others with soft-bricked black display DNXxx60BT units. To me the method i suggested and which you've proved is easier to follow than the one in the earlier thread. That might be just as effective, however what's been used here is the more traditional way of restoring soft-bricked Garmin devices. I've put a link in the initial post of that thread linking to your post there to save others wading thru to find it.

Right. I would remove the JCV folder from the internal memory in case it interferes with the new detail map's jcv file in the SD card. It won't be a problem if you don't put any new files in there though.

Hello , after using it for some months I had the opportunity to finally use the navigation feature on highways and the jcv junctions work

Spoiler: image

[Only registered and activated users can see links. ]