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

**Neil** · 18th March 2014, 07:25 AM

Structure seems ok but best to uncheck 'Hide extensions for known file types' under Windows Folder Options>View so that you can be sure they are correctly named.

If it cannot read from/write to the card or enter pre-boot then there's no way to run commands or re-flash of course. But we'll not give up just yet.

Your folder naming of '1327' is assuming that the unit's HWID has remained as the original Indonesian. But that depends on how you flashed the US fw to it i.e. did you flash complete US fw or hybrid of ID boot.bin with US fw_all.bin. So some questions:

1. What did you flash, hybrid or complete?
2. What version/s?
3. How did you name the flash, ie: conventionally as 132701000xxx.rgn [where xxx is fw version e.g. 490], or did you use some other name?

I'd be somewhat concerned if you've managed to flash US fw because your device has a different PCB P/N to the US 24x5 series which has HWID 1371. The different HWID is not concerning, but the mismatching PCB P/Ns usually means a complete lack of compatibility between the hardware and firmware. Looking at the comparison:

ID 2465 PCB PNs

PS: Speak a little 'strine' do you neighbour? G'day back....

**abunadian** · 25th March 2014, 08:46 AM

Sorry for taking long time to reply, my computer hard drive has died...this gives me double burden to jog my memory down to which firmware I flashed, and not all files can be revived.

Following your suggestion I've made sure that the directory structure and file naming is correct, so yes it's very likely the unit has lost capability to read/write the sd card.
1. Honestly I cannot remember which firmware I injected, but likely I played with both 2 bin files
2. on the top of my head, it begins with 2, could be 2.6 or 2.8
3. I didn't use conventional name for .rgn, instead just words which mean something, definitely not related to s/w verssion.

Yeah, that's the story...
nb: I stayed for a while in WA some time a go

**Neil** · 25th March 2014, 10:13 AM

The problem with deviating from the 'conventional' naming of the rgn file of yyyy01000xxx.rgn [where yyyy is the unit's native HWID and xxx is the fw version] is that any other naming will force the flash. The conventional naming prevents flashing an incorrect fw boot.bin. There are times when we want to force the flash such as when doing a full conversion of totally compatible hardware when the PCB P/Ns match.

Unfortunately, US/EU 24x5 and ID 2465 are not the same hardware in the sense that you can simply cross-flash as you've found out. Such cross-flashing might be possible with some serious manipulation of the US fw beforehand, but it's certainly not successful unmodified.

Maybe our resident navigation software experts can suggest some other CPR for your now comatose unit. There is nothing further i can suggest. Without flashing in preboot or from the card, i'm all out.
PS: I think i'm closer to Bali than Perth [geographically and spiritually]. BTW, not a fisherman by profession are you?

**kunix** · 25th March 2014, 10:52 AM

I can only suggest trying harder to enter the pre-boot mode.
Loading ldr.bin would help only if the fw_all.bin boots far enough to load it. But it seems that the device crashes while running the bootloader (which provides the pre-boot mode).
If running ldr.bin or entering the pre-boot mode is impossible then I don't know how to cure the unit using purely software methods.
Then in most probably can be cured by unsoldering the flash chip and flashing it with a healthy dump.

**Neil** · 25th March 2014, 10:28 PM

Originally Posted by Neil

....................
Your folder naming of '1327' is assuming that the unit's HWID has remained as the original Indonesian. But that depends on how you flashed the US fw to it i.e. did you flash complete US fw .........

@abundadian
Another thought, did you remember to try again with SD renaming the folder from 1327 to 1371 and replacing the ID ldr.bin with the US? I've remade the 'backup region 41 kit' for you to try in case you've overlooked doing that: [Only registered and activated users can see links. ]

**peelos** · 31st March 2014, 07:13 PM

HI All,

I registered today to search the forum and potentially to post my issue that I have been having with my BMW Navigator IV (Zumo 660) since yesterday afternoon, when in a moment of sheer stupidity I thought it would be a good idea to format the device memory to start with a clean slate. I'd backed up all of the memory to my local Mac, so I thought I'd be safe, how wrong I was.

Anyway, to cut a very long story very short, I carefully read through this post and followed precisely the steps laid out in this post.

I had to use QuickCure3-with-flasher.rar functionality as the normal updater.exe started but then failed. Once the device was recognised I successfully managed to format under windows 8 (via VMWare) using the RMPRepUSB settings specified. Then I was able to reflash the latest firmware using Garmin WebUpdater and eventually reinstall my maps via Garmin Express.

All that I have remaining is a small issue of trying to salvage my NuMaps Lifetime Europe maps from my backup, but this is a minor issue as I finally have a functioning device.

I cannot thank all of you that helped with this, especially kunix enough for your fantastic posts and continued support - if only Garmin would offer such a service!

**Neil** · 1st April 2014, 01:07 AM

Hard lesson. Moral: Never format any flash drive to FAT16/32 using a Mac directly. Never even format a Garmin internal drive using Windows built-in tool for that matter, use PMPrepUSB only. I don't even like using the Windows tool for general media card formatting.

Thanks for your feedback on your experience peelos. It may save some other innocent mac-using soul some torture.

**mrwwwhite** · 1st April 2014, 12:14 PM

Just used it to solve some issues with my Montana 650 stuck in Garmin logo screen after an unsuccessful patched firmware upload.
Great work!
Thanks,

**atirws** · 20th May 2014, 08:16 AM

I have the nuvi 265W yesterday I accidentally deleted partition and formatted the unit fat32, now when I turn the unit on it shows the garmin boot screen then goes into a reboot loop, if I put a sd card in the slot it will boot into the unit and I can get to the menus. When I plug the unit into the pc the unit beeps like it charging but the pc does not see the unit, if I hold my finger in the top left when powering on and plug it in when I see garmin on the screen windows will do the ding dong sound like it found the unit but if I leave my finger on the screen to long the pc will ding dong again like the unit disconnects from the pcand the calibration screen will come on. I cant get to preboot at all. PLEASE HELP....

**Neil** · 20th May 2014, 08:39 AM

The unit waits in pre-boot mode for ~30 seconds. If nothing is flashed to it in that time it will go the the calibration screen and then boot [if it's able].

Read carefully post #1. Make the cure firmware and load it to updater.exe and have that visible on your desktop with the radio button beside 'USB Device' selected. Hold the top LH corner of the screen while plugging the USB lead into the nuvi [have the lead ready, plugged into a rear port of your PC]. As soon as you see the nuvi's details appear in the window to the right of 'USB Device', press OK on updater.exe and keep holding the screen at least until you see 'Loader' appear on the screen.

It will go to the Logo again on boot and stay there, but you should then be able to access Mass Storage Mode. Reformat using RMPrepUSB only [see link, post #1]. Create a root folder named Garmin on the unit. Finally load the original firmware, then connect to WebUpdater to replace voice files etc and MapUpdater to replace your purchased maps, or if you have a backup restore from there.

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

Thread Tools

Display

Hybrid View

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions