Was the battery heathy and holding a charge? If so, was it at least partly-charged before you used GarminExpress?
Was the battery heathy and holding a charge? If so, was it at least partly-charged before you used GarminExpress?
the battery was charged before abdejt on garmin express, although it is quite bad
Put the device on charge for a couple of hours and then check it again for a faintly lit screen in perfect darkness.
Ok.I put it on the charger. See you later.
is it possible that the 5.20 software was patched in it and that's why it bricked because it was updated to the original 5.60.
Last edited by Boki; 21st November 2022 at 12:38 PM. Reason: merged two posts
No. It's of no consequence if the V5.20 fw was patched or original. If it's soft-bricked it's because the fw loading was interrupted - likely because the battery failed as the GCD was executed. If the battery is no longer capable of holding a charge there would be a sudden shutoff when you disconnected from PC which was supplying 5V power via USB cable. That's conjecture however if the battery has completely failed electrically it explains why the device seems 'dead'. Because the battery doesn't actually form an essential part of the device's power circuit, it still should power-on even with a dead or missing battery when connected to a suitable 5V power source.
I have been charging the nuvi 55 on the power bank until now, and nothing happens. It can NOT turn on as before. Is there a solution.
Have you checked the screen in complete darkness?
It's charging all the time, but it doesn't seem to be charging. It's not warm at all. And I examined it in total darkness, holding the ignition button, and I can't see anything.
Ok it might be dead due to a physically failed flash chip but there's a small hope remaining. One last chance before you give up is to open it and disconnect the battery from the main board for about 30 minute to completely drain any possible residual current from the circuitry. Then put it back on charge. If it doesn't liven up after that it's toast sorry.
@diversola
It's likely a corrupt map .IMG file is causing that problem. Because the device is still recognized by Windows Explorer you don't need to load Cure3 fw and may simply remove any (unofficial) detail map/s you've added after patching V5.20 firmware. Because that device has already had patched fw loaded you may load a patched later version GCD file rather than use an RGN file or SD method to load BIN files which is required only initially. This means you can simply manually place the patched GCD (named only as gupdate.gcd) in the .System folder or drag nuvi55_56_560.gcd onto WebUpdater.exe or it's desktop icon with the device connected to your PC. Here's the link to V5.80:
Code:Please Login or Register to see the links
Bookmarks