Thread: IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this

Hi Butters,

I responded from my smatphone..but apparently it wasn't posted.
First of all, thanks for your support and your..promptness, i wasn't expecting that!

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.

Does using the old "RGN_tool" could help ?(just a tought)

I feel.. at loss ..
Is there a way to read the chip directly from the PCB? Perhaps?... Since i've a working unit

Thanks foryour support!

Originally Posted by Nerox

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

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 !

Originally Posted by Butters

As i said, bricked devices can be tricky with connection but the fact that it's seen in device manager when in preboot but not in MSM with cure fw loaded is a little troubling. Flash damage is indicated especially if you get the same behavior using a desktop with rear USB2 which is why i'd like you to try that if possible. Keep in mind that 'bricked' devices are sometimes VERY flaky.

I remembered i had my oooolld laptop. X86 based, win7 32Bits , USB 2.0 (Powered by a massive intel centurion M 1.86GHZ ). Joke aside, before following your new directions, I've tried to flash cureFW via the laptop, and the same symptoms appear : Successfull flash, but no detection after it except in pre-boot

Holding the power button for between 10 and 30 seconds should force it off with the battery in it anyway. It should also work without the battery in provided there's enough power from the USB source, because in most Garmin devices the battery isn't an essential part of the power circuitry. Anyway, it doesn't seem that your problem is it's not fully off for your attempts (it can't enter preboot unless it's fully off and you've got preboot).

Thanks for the clarification

Please follow this:
REMOVE the file named "Ldr.bin" from the 1541 folder on your microSD card. There should only be one file named "update.txt" remaining in 1541 folder.
Place the card into the device and ensure it's fully OFF.
Open this extracted RGN file Attachment 123548 in Updater.exe and leave it's GUI open and visible for quick initiation.
Have the PC with USB cable connected, hold Nav screen, plug in USB cable to it then quickly start Updater.exe to flash.

In explanation, the only content in this RGN file is boot.bin (Ldr.bin) which has been modified to bypass the requirement of the firmware initiation's for using the TXT commands in update.txt. This is definitive, if this doesn't work to dump region 41 and the internal folders and files then it's flash damage and irrecoverable using software means. If it works, then we'll keep going. Good luck this time.

Done, the NAV hangs on the logo screen with "loader" on top but nothing happens after. No dump produced on the sdcard... (It's still..empty in the backup folder)

EDIT: IMPORTANT! I've just realized i've made a typo in the HWID folder name on the SD card kit. It's "1451" when it should be "1541" so please change that before proceeding.

Done

Thanks for your help... I think i've to deal with it .Amazing help though !

I'll try (again) in a day or two, out of "boredom" to see if it suprisingly works.

General question Though, I've another (another other) NAV V that i bought for spares a while ago. But it has a power off issue while charging -apart from that it's okay.... Whatever, not my point :D
So, theorically, if i ask a skilled tech to swap the eMMC (memory module) between the two units, would it work? I mean, do you know what actually gives the Serial number etc to the NAV V?

Would a "simple" memory swap could solve the issue, according to your knowledge of garmin devices?

I can ask garmin for a replacement, but I think they're gonna charge stealer price aka BMW price aka 450 euros ... Almost twice tue value of a used one . I'd rather make a working device out of two non usable one...

Originally Posted by Nerox

Done, the NAV hangs on the logo screen with "loader" on top but nothing happens after. No dump produced on the sdcard... (It's still..empty in the backup folder)

Did it eventually stop showing 'Loader' and try to boot itself to the logo screen, or, how long did you leave it with 'Loader' showing before giving up? Also check in the card's 1541 folder to see if there's any new files named last_id.bin and/or update.log because if those files have been created we're maybe not totally done yet.

General question Though, I've another (another other) NAV V that i bought for spares a while ago. But it has a power off issue while charging -apart from that it's okay.... Whatever, not my point :D
So, theorically, if i ask a skilled tech to swap the eMMC (memory module) between the two units, would it work? I mean, do you know what actually gives the Serial number etc to the NAV V?

No it won't work without also reprogramming the replacement chip. It's quite above my 'pay-grade' but that because i'm not a programmer or coder. The ID codes are stored on the chip somehow and it would recognize that the hardware has changed without reprogramming, i guess that'd need to be done by a true expert with special JTAG equipment - certainly the factory can do it as that's often what's done with replacement 'refurb' units which were returned with failed chips. *See below for the other unit's charging issue.

Would a "simple" memory swap could solve the issue, according to your knowledge of garmin devices?

No, even if you flashed all the information in the dedicated regions from the old chip to the new one with conventional means, i.e. simple memory swap, (flashing BINs as an RGN file with Updater.exe in preboot, or BIN files via SD card TXT commands) it wouldn't be enough (see previous answer about JTAG). Regardless, in your case you don't have a previous dump of all individual relevant regions anyway and seemingly read/write of/to the card fails so there's no way to get them now.

I can ask garmin for a replacement, but I think they're gonna charge stealer price aka BMW price aka 450 euros ... Almost twice tue value of a used one . I'd rather make a working device out of two non usable one...

*Personally, i'd be looking at trying to repair the other device. It maybe as simple as one or two cracked solder connections on the USB socket causing it not to charge properly and power off. Re-flowing the solder connections to the board is fairly simple and a common Garmin failure point (see post #157 in this thread). Of course it may be due to a component failure on the board itself, not so easy to find and fix however i'd be re-flowing the usb socket connections or you can even swap sockets between the units if you suspect the socket's internal pins are damaged.