Thanks for responding, kunix. Unfortunately, the same thing happened. Here's what I did on my native Windows 7 Ultimate machine:
1. I generated the 097201000610.rgn file from GarminCure3.exe using CURE and using nuvi13xxand14xxseries_GCDFile__610.gcd
2. I manually ran Updater.exe 097201000610.rgn (Updater.exe is v2.8.0)
3. Clicked on button for USB Device
4. Clicked and held upper left hand corner of Nuvi 1390
5. Plugged in USB cable to Nuvi
6. As soon as my Nuvi device appeared in USB Device box on computer, I immediately clicked on OK
7. Then the Updating Software window appeared which said this:
nuvi 13xx Series Software Version 4.20
100% complete, 0:00 remaining
Note: The USB connection audibly dropped and re-connected once or twice during the Update process
Then the window changed to this:
nuvi 13xx Series Software Version 4.20
(this may take a few minutes)
Then this window popped up:
The GARMIN device is unable to program the requested memory region.
This could be due to an incompatibility between this application and the GARMIN device.
If this error continues to occur, please contact GARMIN Technical Support.
What is odd is that if I do the hold upper left hand corner process and plug in cable, the machine recognizes the Garmin device for about 30 seconds, but the machine is unable to access this like a drive during this period (I tried finding it with Windows Disk Management as well). If I run the updater, the updater seems to knock out the connection within in the first couple of seconds. The USB connection continues to open and close during this period. My thought is that my machine is working fine trying to establish a connection with the nuvi connected to USB. Is there anything else I can try? Or is there another way to wipe this device to get it out of boot loop and then flash the rgn file?
Last edited by yeffocb; 17th August 2012 at 15:52.
Ok, thanks for a very detailed description.
Can you try flashing those RGNs and tell me what happens? This is not dangerous at all. [Only registered and activated users can see links. ]
I think that the one from boot.bin folder will flash normally, device will reconnect, and then updater.exe will see the device.
I expect that the one form fw_all.bin folder will cause "unable to program the requested memory region" popup immediately.
Sorry dasilvarsa, I missed your post and just saw it now. I didn't see where any good description on the MTK version of this device in the first post, but I still gave it a shot. I downloaded the nuvi13xxand14xxseries_GCDFile-MTK__610.gc, built a cure rgn file called 110401000610.rgn from GarminCure3.exe. Oddly clicking on the updater button from garmincure3 did not work so I ran updater 110401000610.rgn. This returned that no updates were available for the device. I'm not sure exactly what this means, but it sounds like either it doesn't think that my device is MTK or that it doesn't need any updates. So this attempt did not work either.
kunix: Like you expected, the rgn in boot.bin reported that it was successful.
Now's here is where it gets interesting...
The rgn in fw_all.bin folder actually started updating the device
(it finally looked like it was actually doing something as percentages actually were incrementing in smaller increments).
It completed and it said it was successful.
Currently the Nuvi 1390 screen shows: Loader Loading...
I have not powered off and powered device back on yet.
Nothing, yet I was going to make sure that your device doesn't flash firmwares anymore, which is not recoverable as far as I know, but it seems that it still can.
Let's try clearing non-volatile memory, it helps frequently. [Only registered and activated users can see links. ]
Put Garmin folder on an SD card and insert it into the device. Then flash the RGN. And after, say 5 minutes, remove the SD card and upload its contents. A few new files should appear on the SD card. If there are no new files then don't upload
Also let's see how it behaves with the following tool:
[Only registered and activated users can see links. ]
Is the order of the command important? I'm trying to think through your first step. Sorry, can you clarify that better? I don't have one of those dongles that allow you to plug in an SD card and then connect to the garmin. I do have and external hard drive that I could directly connect to it, but I'm not sure how I'd run commands from the garmin using the newly created garmin folder. I do have the ability to plug an SD card into my computer though.