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

Thanks for that, it's totally clear now what's happening with preboot in your DNX. Whether that's typical Kenwood behaviour or not where the device is listed in Device Manager regardless of being powered on i don't know. It would certainly be considered quirky for a normal Garmin device. They're neither seen in Updater nor device manager unless powered on while manually placed in preboot. The only exception to that is if region 14 is empty or corrupt where the device will default (i.e. fail-over automatically) to preboot mode without user input. That's why i suspected your device may already be in preboot and may be indicating that it had incomplete or damaged fw_all data in rgn 14.

The two RGN files do appear to have the same boot.bin and fw_all.bin, in size at least, however your RGN doesn't have pk_files_6605.zip included like mine does. My next suggestions were to be (i) to remove the zip from section 2 of RGN_Tool and save just boot.bin and fw.all.bin as an RGN - but you've already tried that; then (ii) try kunix's QuickCure3 to re-enable MSM, then if that fails (iii) make proper specific Cure3 fw, also without the zip - but it seems that didn't work for you to restore MSM either. It's of mild concern that my file with PK zip included didn't fail with an Updater error message about not being able to program the region. Despite any message indicating it's finished successfully there may in fact be some damage to the module's flash memory where some or all memory regions in reality cannot properly be flashed or accessed. Because on careful reading of the other thread, Updater should fail with that error if the PK zip is kept in the RGN file flashed to a soft-bricked device.

I'd try the Quickcure now, on the off-chance it works: [Only registered and activated users can see links. ]. The Quickcure RGN contains only a modified universal boot.bin, nothing else. It's not firmware or HWID dependent at all, and it doesn't work for all Garmin devices but it's worth a shot and can't damage anything because nothing is really permanently flashed to the unit, it just attempts to interrupt and stall the normal boot process before any corrupt files can be loaded, in exactly the same way a tailored Cure3 "device-specific" fw intends doing, but by using an entirely different approach.

Same procedure: Extract the ZIP above and drag the RGN onto Updater.exe, etc.... you know the drill for that DNX's preboot better than me i think .

If QC doesn't work then try Cure3 fw again without the PK zip file. I've made one made freshly from my RGN in Post #2, without the second section PK zip and with only boot.bin and fw_all.bin saved into the RGN then loaded that into kunix's Cure3 application to make the RGN below. Of course it may be that it's the same as the cure file you made yourself but it's worth trying this one if QC didn't work: [Only registered and activated users can see links. ]

Good luck.

Its pretty late for me to try it. I will try it tomorow and i will post the results in this comment . If the anwer will be corrupted NAND chip then i will go to a service to get them switched for working ones and then i will resume the attempts.
Here are the files i have so far for other people stumbling on this post

Spoiler: image

[Only registered and activated users can see links. ]