Hi Butters, Thanks again Butters - I'm glad i can be a "distraction" in your eternalnsupport to the gps community

  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?
    ..Yes, i've checked, but... IT DOES NOT get an allocated drive letter...since it's only detected in pre-boot
  2. Does the other Nav V you have connect and get recognized by the same PC?
    Yes, with the same cable, same port
  3. Are you using only a REAR USB2 port directly (not front port or USB3 port or via a hub)?
    ..Is usb 2.0 still a thing ? I've only usb 3.0 - But i did "RTFM-Cure3" and used a port on the motherboard itself as precognized.
  4. Does Windows play a 'ding/dong' sound when you connect or disconnect either of the Nav devices?
    For the defective one, only during pre-boot. As soon as it leave pre-boot and tries to boot "normally" it does'nt get detected .
    And it only gets detected in the Device manager under "Garmin Devices"
    For the Working one - Yes, and it's getting detected by garmin express and is able to be put in MTP via the menus of the unit.
  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)

I've tried two USB ports, but only one computer. I'll try with one friend's laptop. But it's still usb 3 ,and windows 10.
and... the annoying thing here, is that i get the "successfull patch" every f*** time . So it doesn't seem's like a transfer issue. And if eMMC (internal memory) was defective, i wouldn't be able to flash... it's still a 70mb file to send, i doubt that the rom is that big



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. It was indeed my question. But i've googled it..and, well, the device itself cost like 150 euros to read the Emmc.. + the fact that i sould know how to desolder , reballing etc... soo , yes. A bit too high level repair for me

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.
...It never went that far, sadly



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);
    -Done
  • Insert the card into the device and replace the battery and cover but don't turn it on manually or hold the screen;
    ...So, my issue is that it's turning itself on as soon as battery is connected.
    I've tried to connect the usb cable then the battery,
    i've also tried to 1) Disconnect battery 2) put back cover so i don't get the warnin msg, 3) put usb charging cable
  • 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.
It Didn't ..

What about doing a backup of my other nav via micro sd and then try to use it in the defective one - aka "clone" it..?
Thanks for your help !