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

Originally Posted by nickus

Can you tell me how can I delete the files from System volume information? (I mistakenly copied them here and it takes up a lot of space, more precisely I downloaded maps and it occupies about 4 GB).

If you can see .System (see previous Post #149, last point) you can easily delete any unwanted .img files.

Another question: where can I download another language for the device?
Question: I can change the language at the menu interface (in settings I only have English)

That's because you haven't accepted the required Voices offered by GarminExpress. Without the relevant .vpm files you will only have the default EN voice. Connect to GE again after re-reading my post #151. i.e., this: "Also accept all other files offered by GE which you want to use (Voices, Vehicles etc.)". Once you have the required Voice file you can select it in settings.

I guess you're missing Text and/or Keyboard files. I've bundled up Help, Keyboards, Text, Voice and Vehicle folders into a RAR file (Extra_Folders.rar) and uploaded it for you:

Spoiler:

[Only registered and activated users can see links. ]

Extract it and you can take what you need to complete your restoration of the device. All those folders go in the root, i.e. with the .System and Garmin folders, not in them. That should then complete the restoration of your nuvi 44 provided you've followed all my other suggestions, however if there's anything else just post again.

1) Nuvi 50, ???, HWID.

2) I turned off the device, and when I turn on, it’s already a brick

3) The device weighs on the logo

4) The PC does not see the device (does not have time to install the driver)

5) I tried to flash through updater but the device does not connect to the PC.

6) Garmin USB Drivers installed, last version

7) I can not use G7ToWin for HWID because device does not connect to PC

8) no backup

really hope for help

@Rus_Fan
Most devices which stick on the logo (splash) screen can be cured, i.e. if they are 'soft-bricked'. Some, quite rarer, can't benefit from a software cure because they have a damaged flash, so they're 'hard-bricked'. A soft-bricked device will ALWAYS be able to access pre-boot although it might be difficult to do so. Perseverance and technique is the key. To test it, try this:

• Open Windows Device Manage and leave it visible on your desktop
• Ensure your device is fully OFF. Force it off if necessary by holding the power button down until you're certain it's really off.
• Connect a 'known-good' USB directly cable to a REAR USB2 port of your PC, don't use a USB3 port or a front port or a hub.
• Hold the upper LH corner of the device screen then plug in the miniUSB end to the device.
• Immediately turn your attention to the Device Manager window and watch to see if 'GARMIN Device' appears there, if you have systems sounds enabled you should also hear the Windows sound for device connection.

Provided you do have Garmin USB Drivers load it should show in Device Manager, if so it can attain preboot. If it doesn't it may be hard-bricked, albeit that is less likely.

Thanks! Butters and Giomen. I found a problem, problem in the power / data connector. I will try your solutions after repair.

Not so unusual to have both a hardware failure and a software bricking co-incidentally because the latter can happen if the connection is flaky during a software or map update. Many ppl get away with a dodgy usb for a while, holding a cable in a certain way so it'll charge and/or connect to computer. Unfortunately nuvi 50 and nuvi 14xx seem very prone to USB socket failure, even more-so than other series. Usually it's an easy fix to re-flow the solder connects to the board however it's best to further strengthening the repair if possible. These things are not hand-soldered in the factory, all common SMD components are cooked-on in mass production.

Originally Posted by hodgo

newbie, here with a failed firmware upload.
1) Bricked device: Montana 610 , Firmware version:failed to update 3.50, HWID - 39xxxxxxxx.

That's your device's unique 10 numeral Unit Identification (UID), not it's HWID which consists of only four numerals. Being as you're in Oz if you purchased it new locally it'll be HWID 2299. Seems you can access preboot so you can check it's HWID with G7ToWin. You should remove your UID from your post for privacy as it's possible to use it for cloning.

2) used basecamp to update firmware. After restarting garmin did the "validating update" screen, gets to somewhere between 22% and 31% and screen fades off

It appears to be soft-bricked because of a corrupt GCD file.

4) Does your pc sees your device: very briefly with basecamp not GE, and only if i hold power button depressed

It's going into preboot when you hold the power button down but it doesn't stay in preboot for long unless a flash is initiated by Updater.exe in which case it holds preboot.

7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID - trying that now

It's essential you confirm your HWID is 2299 before proceeding.

8) Write down if you already read or tried GarminCure3 tool - giving this a go once i figure out HWID

Post again if you need more help after trying with cure firmware to reach Mass Storage Mode. You'll likely only need to delete the corrupt GUPDATE.GCD file from the device then load original fw to restore it. You probably won't need to re-format the internal drive.

9) Can you reach preboot mode? sounds like i did accidentally.

Yup.

Originally Posted by fgafga

4- yes, but after holing switch for a while

Please detail how it was seen by PC. For example: By File Explorer (Mass Storage Mode), or in Device Manager (preboot mode), or by one of Garmin's programs like MapSource/BaseCamp, or ?

8- garmin cure, updater.exe doesn't recognize the device usb port.

Both pro-boot mode and Garmin USB Drivers loaded are required for that.

9-no

Are you sure pre-boot isn't available? Most devices which boot only to the logo still have preboot. If it was stuck on logo screen then it's easier to find and maintain preboot but devices which reach the logo then either turn off or attempt to re-boot are more difficult.

The vast majority of devices which will turn on and show the logo even briefly can be recovered with persistence.