@motoltd
You could try a different USB cable if you haven't already tried a few. The chances are that the USB socket connections to the board are the problem though. That can happen with any device however 5" devices like nuvi 5x series and 14xx are particularly prone to the soldered connections failing. You can fix that by carefully reflowing the solder with a very fine tipped iron using plenty of paste and importantly also reinforcing the two attachment points that hold the socket in place as their weakness is the usual reason that the electrical connections fail. If the socket isn't physically loose then inspect its external pins using a magnifying glass to ensure none are bent or broken. There are plenty of videos on the internet how to repair or replace a mechanically-failed usb socket. The other reason for having no data connection to the PC might be due a failure of a component on the PCB itself, that's not at all easily user-fixable.
It's easy to delete any file from the onboard memory and replace it with another using txt commands. In the case of a device with USB connection problems that cannot be fixed by repair of the socket, it's unsafe to do so except as an absolute last resort because if you mess up and brick the device because of an unreadable file the device will likely also lose SD reading function. Then there's no way to fix it using cure firmware because preboot mode relies on having PC connection too.
The two commands to delete and then replace a primary detail map would be as follows:
Code:
Please Login or Register to see the links
The copy command above is for when the source IMG file is contained in the root of the card (along with, not in, the Garmin folder). Remember to write "reboot" as the final command or the device will hang.
Quite frankly it's better to use the card for new detail mapping and just either delete (or disable in settings) the on-board map. If you have both an internal and external map of different versions covering the same area with both maps enabled it will cause problems with route calculations and freezing/restarting, just as you described. Creating exceptionally long routes can cause that in leader-line devices with lower performance regardless of there being only one detail map anyway. The nuvi 52 is not a particularly high spec'ed device.
Bookmarks