GarminCure3 tool - the new way to create cure firmwares for Garmin devices

**kunix** · 16th July 2012, 02:05 PM

As for me, I don't know any other solutions.
Can you tell me more about China GPS and JTAG?
Long time ago I was trying to play with debug registers of 37xx, in particular, I was trying to set a hardware breakpoint.
Unfortunately, I couldn't enable debug registers, though I was doing everything right. I think it's because debugging capabilities were disabled by manipulating specific output pins of the ARM core (I'm not sure if those pins really come out of the processor). And, in fact, there were a few flags in some status register (I don't remember its name) indicating that.
So, in conclusion, I think Garmin disables debugging support (including JTAG) for production processors.

**lolypop000** · 16th July 2012, 02:21 PM

Ok,thank you for answer,i will try to experiment with nuvi 250W.
For Jtag i mean this

Code:

Please Login or Register to see the links

and this:

Code:

Please Login or Register to see the links

**dasilvarsa** · 17th August 2012, 08:32 AM

Maybe your device is MTK Chipset.
You could try using the MTK Firmware from the link below.

[Only registered and activated users can see links. ]

Read the Next Post by Kunix The Author of GarminCure3 before you try MTK

**kunix** · 17th August 2012, 09:52 AM

Can you try doing the same things on a real PC, not a virtual machine? USB emulation is not always perfect.
If you are afraid of viruses in GarminCure3.exe then clear the GarminCure3-TEMP folder, make the CURE firmware, press "Updater.exe", and then use the only RGN file present in the only subfolder of the GarminCure3-TEMP.
You can easily download updater.exe somewhere else.
Then copy the RGN and the updater.exe to some folder on your real PC and flash the RGN by running updater.exe (you would probably need to run it "as Administartor").

**yeffocb** · 17th August 2012, 03:49 PM

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
Updating...
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
Erasing...
(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?

**yeffocb** · 17th August 2012, 04:16 PM

Thanks kunix, trying now. Will get back to you shortly.

**kunix** · 17th August 2012, 04:13 PM

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.

**yeffocb** · 17th August 2012, 04:14 PM

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.

**yeffocb** · 17th August 2012, 04:40 PM

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.

Very promising, next steps?