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

**Neil** · 24th July 2013,Â 04:15 AM

@nanochip
So if seems that you've tried the cure by PouchX, but have you used this cure3 by Kunix also? Have you reloaded the original fw afterwards? What are the symptoms, i.e. Will the unit not boot but you can see the internal FS in Windows Explorer, even if it's empty?; or do you mean [rather than deleting the folders & files on it] that you actually removed the partition and under Windows Disk Management it's showing as 'Unallocated' space?

If the former, and it's not booting because of the cure fw's presence, load the full original fw and then create a folder named Garmin in the device root, boot it and then check if it's created a file GarminDevice.xml inside [if it's named GarminDevice.tmp rename the extension to .xml]. If you have the .xml there, connect to WebUpdater to load necessary files and then replace your maps. If the latter, create a new simple volume then format it first using RMPrepUSM [link in first post].

If it's none of those scenarios, post again with full details.

nanochip · 24th July 2013,Â 02:37 PM

Originally Posted by Neil

@nanochip
So if seems that you've tried the cure by PouchX, but have you used this cure3 by Kunix also? Have you reloaded the original fw afterwards? What are the symptoms, i.e. Will the unit not boot but you can see the internal FS in Windows Explorer, even if it's empty?; or do you mean [rather than deleting the folders & files on it] that you actually removed the partition and under Windows Disk Management it's showing as 'Unallocated' space?

If the former, and it's not booting because of the cure fw's presence, load the full original fw and then create a folder named Garmin in the device root, boot it and then check if it's created a file GarminDevice.xml inside [if it's named GarminDevice.tmp rename the extension to .xml]. If you have the .xml there, connect to WebUpdater to load necessary files and then replace your maps. If the latter, create a new simple volume then format it first using RMPrepUSM [link in first post].

If it's none of those scenarios, post again with full details.

Unfortunately I deleted the whole partition so connecting too the Nuvi via a PC/MAC aint possible (diskmanger is not showing the device). I also got hard times finding the right .gcd file for the Nuvi 265 hwid: 851. I need this too try Kunix cure method.

**lolypop000** · 24th July 2013,Â 03:13 PM

Here you have all that you need with tutorial inside:

[Only registered and activated users can see links. ]

nanochip · 24th July 2013,Â 04:45 PM

Originally Posted by lolypop000

Here you have all that you need with tutorial inside:

***Hidden content cannot be quoted.***

Thanks! My Nuvi is back

!!!

**franco663** · 23rd August 2013,Â 01:27 PM

Sorry for mi English. I have a problem whith the firmware for nuvi 750.

ID is 754 but dont work whit nuvi 760 firmware!

updater problem is this :

Nuvi 750 Software version 5.4 ID 754 using firmaware from nuvi 760 whit cure3 and original firmware!

updater problem: ( first say updating to 100%)
then.-

the GARMIN device is unable to program the requested memory region.
this could be due to an incompatibility betweenthis aplication and the GARMIN device!

Can you help me ?

**lolypop000** · 23rd August 2013,Â 01:50 PM

This look like your chip is Game over.

Try to restart your Pc and flash again.

**franco663** · 23rd August 2013,Â 07:12 PM

Are you sure ? Is the garmin of a friend !

**Neil** · 24th August 2013,Â 03:48 AM

I agree with Loly, the flash chip may well be damaged. But perhaps it is just flaky and will respond eventually so try again and again repeatedly to flash. What are the symptoms with this nuvi when turned on? Does it boot to the logo screen, show a bright white screen, faint light, etc. You can obviously reach pre-boot but what else can you tell us about it's history and what it's doing now? Did it brick after adding a map or other files or a fw upgrade, or for no apparent reason? Are you absolutely certain this unit is HWID is 0754 and not 0785 if it came to you bricked? In pre-boot, you can check the HWID with [Only registered and activated users can see links. ] if you haven't already confirmed it.

**franco663** · 24th August 2013,Â 04:57 PM

boot on garmin and restar, boot on garmin and restart! I update a photo.

[Only registered and activated users can see links. ][Only registered and activated users can see links. ]