Thread: Need Help with Bricked nuvi 1490

Originally Posted by cbstealth

I also have a bricked Nuvi 1490 I would like to try and fix but all the files from zippyshare are not available anymore. Can the mods re-upload them? Thank you

If you have simply 'soft-bricked' your device then that described fix isn't for you. The OP had accidentally flashed his 1490 using the Ldr.bin [boot.bin] from a different device. Most 'brickings' are the result of a corrupt file loaded, such as a map (*.img), a POI (*.gpi), a Voice (*.vpm), etc.. The usual way to fix that problem is to load Cure firmware which re-enables Mass Storage Mode, then remove the offending file if you know which one it is or re-format if removing likely files doesn't fix it. Read this guide: [Only registered and activated users can see links. ] and go to this thread for the tools: [Only registered and activated users can see links. ]. Post again if you need more help saying exactly what you have attempted, as per here: [Only registered and activated users can see links. ]

Here is what I get:

Spoiler: image

[Only registered and activated users can see links. ]

Gramin Nuvi 1490 bricked by Garmin Express.
Goes to Garmin logo and restarts.
It is not recognised by computer.
Also I am unable to download anything in the forum. I just goes to a login screen even tho I am logged in.

@cbstealth
Unfortunately there's a temporary systemic problem downloading some attachments presently. Admin is working to fix it. Meanwhile i can supply any files you need to attempt to fix your 1490.

First please check for certain the HWID of your 1490 because there are two, read here how to check for sure: [Only registered and activated users can see links. ]. When you've confirmed that it is definitely 0972 as shown in your post above, or that it's the MTK chip HWID 1104, we can proceed.

Your error "ERROR: can't run D:\Garmin\cure\updater.exe" is probably only due to user account restrictions on your PC or Updater.exe not being in it's proper place. The cure firmware was made, indicated by the line above that, i.e. "Processing OK :)" and so the cure RGN file would be in the same directory as GarminCure3.exe but in a folder "GarminCure3-TEMP" and in there will be another named, for example, "GarminCure3-B52E1C07" but with different last 8 characters which are a hexadecimal identifier, and inside you'll find "097201000630.rgn".

I can make a kit for you to flash the cure in preboot (just ask) but really all you need do is locate that RGN file as advised above and drag it manually onto Updater.exe. You can also put Updater.exe in the same folder as the cure RGN and run the EXE. Once the cure fw is loaded you should have Mass Storage Mode available to delete the faulty file/s loaded by GarminExpress (likely the new detail map *.img file if you were updating the map), then re-load your original RGN firmware to complete the process.

Keep trying to flash over and over. Bootlooping devices can be tricky to flash and perseverance is key. By the way, telling us all the circumstances how it became bricked using GarminExpress is not just important it's crucial which is why i suggested in Post #2 you read this: [Only registered and activated users can see links. ] and then report.

If you're still unable to flash any firmware in preboot after numerous repeated attempts then it could be that the flash chip is damaged, sorry. If the problem is indeed hardware damage then there is no software solution.

There is also a way to attempt the flash using a modified boot.bin as an RGN to execute text commands from a microSD card so don't give up but keep trying to get the Updater.exe flash to complete before we try that. I once got an Updater.exe flash to complete on an old StreetPilot after trying 10 times every morning for over a week. Persistence pays off sometimes with stubbornly bricked devices.

EDIT: I guess you mean "created the RGN" not GCD in above post.

I will. There is a file called quickcure I would like to try but I can't download it. Can you help?

It's working now because Admin fixed the attachment problem. [Only registered and activated users can see links. ] anyway. QuickCure doesn't use the actual device firmware so it might flash more easily but likely it'll also require perseverance unless you strike it lucky. Don't forget to name it safely (097201000630.rgn).