Quote Originally Posted by Nerox View Post
..........
I've tried at least 10 time to make the cur3fw...
I've tried to flash with yours..
Still the same, sadly, it gets recognized while in pre boot then disconnect after a sucessfull flash.
It's an unusual problem to have a device when in preboot to be recognized in Device Manager but then not being seen in Mass Storage Mode when Cure fw is properly loaded. There is possibility of actual flash chip damage but we'll proceed assuming it's only a 'soft' problem, not physical damage.

Some questions:
  1. Have you checked in Disk Management that it's being allocated a drive letter by the system when you attempt to connect in MSM?
  2. Does the other Nav V you have connect and get recognized by the same PC?
  3. Are you using only a REAR USB2 port directly (not front port or USB3 port or via a hub)?
  4. Does Windows play a 'ding/dong' sound when you connect or disconnect either of the Nav devices?
  5. Have you tried a different rear USB2 port, various USB cables and/or different PC? (even tho' a certain cable, port or PC might work for the healthy Nav V)


Does using the old "RGN_tool" could help ?(just a tought)
No, not specifically in this case. RGN_Tool is useful to split or combine the BIN files from or into a firmware file and to convert an RGN file into a GCD file and vice versa.

I feel.. at loss ..
Is there a way to read the chip directly from the PCB? Perhaps?... Since i've a working unit
No sure what you're asking there .... other than you might mean can the chip be reprogramed perhaps? If so, yes but you need special kit and skills to do so and regardless it's beyond what's needed here. If the flash chip has actual physical damage it cannot be reprogrammed and chip replacement is not economically viable anyway.

If you're asking if the flash memory can be dumped, the answer is "maybe" but it depends on whether it's getting far enough into the boot process before sticking on the splash screen. To be able to read from and write to a microSD it needs to progress at least as far as 'Loading Maps', it's after that that fw_all.bin in region 14 [hex 0E] executes Ldr.bin on a media card to enable initiation of TXT commands and thereby access the internal flash memory/regions to write to them or copy [dump] them back to the card. We may have to try that, see below.

Thanks foryour support!
My pleasure, i don't mind a challenge.

If you've checked all the points asked above but still can't access MSM then re-flash ORIGINAL fw as an RGN file in preboot (you can make an RGN using GarminCure3.exe or RGN_Tool, name it ONLY as 145101000350.rgn for safety). Then remove the battery to access the microSD slot and follow this:
  • Download this ZIP file [Only registered and activated users can see links. ] and extract it directly to a CLEAN microSD of at least 8GB formatted FAT32 (you can use a large card 64GB> but you may have to reformat it from exFAT to FAT32, Nav V can't read exFAT);
  • Insert the card into the device and replace the battery and cover but don't turn it on manually or hold the screen;
  • Plug it into a suitable power supply which will power it on (don't use a PC usb port for this);
  • Observe the screen to see if 'Loader' appears in some seconds. If it does, leave it undisturbed until it finishes which will take quite a while.

It'll try to boot and stick on the logo screen when finished but if Loader doesn't show and it goes straight to the logo screen then the dump hasn't worked. If it does work then in the SD's Garmin folder there'll be a copy of it's nonvol memory as 41_backup.bin and the folder named 'BackUpFileSystem' will be populated). Good luck, please report back the result.