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

The file on the broken PDA doesn't work, but I tried it on another Atemos 100 and it's okay, I think it's a hardware problem with the PDA.
How to prepare the RGN firmware for alpha 100? did you use any new version of RGN Tool?

Thanks for your help and your concern

I can send you the rgn for ALPFA 100. The last version for the RGN Tool is 0.94.

Hi to y'all, got one problem with nuvi 2475, the device turn on and work but no voice navigation and I think few maps missing too. This happened when my friend try to put few new maps on the device, and in one moment he format one of the partitions but he forget make new partition.

Spoiler: image

[Only registered and activated users can see links. Click Here To Register...]

So now pc not detect the device at all.

second problem is, we can't find the .gcd file for nuvi 2475, and the firmware either, is mission impossible.

Any advice or suggestions links etc ?

Thank you and regards. Georg

nuvi 24x5 and 25x5 (GCD File) 006-B1371-00 Release 8.30
[Only registered and activated users can see links. Click Here To Register...]
[Only registered and activated users can see links. Click Here To Register...] (49024 Kb)

Spoiler: Image

[Only registered and activated users can see links. Click Here To Register...]

thank you Garman_Nuvi , we will try tomorow, and report back what and how it go :)

gdnight and thanks again

Edit:

I got new problem, my friend cant got in pre boot on that device nuvi 2475 ?

thx for any advice

@georg001
Some modern devices have a very short preboot period before it's dropped whereas older series had much more. It may be only a matter of seconds it's in preboot where it's possible to start a flash with Updater.exe however once the flash is initiated preboot should be held until the flash finishes. A technique that usually works is detailed [Only registered and activated users can see links. Click Here To Register...].

Tried to download the *GCD file for my Etrex 10, but Garmin said I am lost and should go to Garmin Express.
But Garmin Express does not connect my registered Etrex any more.
GPS says System Software Missing.

@seidenherb
That message at it's most benign and common occurrence means that the main 'system software' (firmware) contained in the device's region 14 is either missing, incomplete or corrupt. At it's worst it means the device has physical damage to the flash chip which cannot be remedied by software means. Let's proceed on the basis of it being the former, which is easily fixed by re-flashing the firmware in preboot mode. The device is not 'bricked' in the sense that it's unable to load necessary files on the boot sequence, as it's not able to use the firmware therefore no cure firmware needs to be loaded, just needs the original fw loaded in preboot. The device should have defaulted to preboot mode anyway if there is no flash chip fault and so you can proceed as follows behind the spoiler:

Spoiler: Click to Show

• Open the attached ZIP file into a convenient directory (folder) on a Windows PC;
• Drag the RGN file onto Updater.exe to open it;
• Click the radio button next to "USB Device" on it's GUI;
• Connect the eTrex to your PC, preferably using a desktop and a REAR USB2 port;
• Watch the window adjacent to "USB Device" and when the device's detail appear in it click "OK";
• Wait until Updater reports the flash has been succfessful before disconnecting from PC;
• When the device is started it should boot normally.

NOTE: All flashing carries risk and it's all yours although it's minimal risk in this case. I'm assuming that you have a US/EU eTrex 10 with HWID 1304 and the flash kit uses that fw for the RGN file. If the device is An Asian or APEC model the flash won't be started because they have a different HWID.

[Only registered and activated users can see links. Click Here To Register...]

Worked great. Thanks.
Was probably caused by incorrect update procedure in Garmin Express.
Extremely lucky to have found you.

My pleasure to help. You're almost certainly correct that GarminExpress was the cause if you were indeed using it to update immediately before the problem happened. Previously,especially when it was first introduced and probably frankly only in Beta form, there were countless reports of (so-called) "brickings" after using GE where the devices were either stuck on the Logo screen unable to load a faulty IMG, VPM, etc. file, or as in your case a faulty fw_all.bin file in the new GUPDATE.GCD had messed up region 14. Garmin, being Garmin, blamed the victims by claiming that users were disconnecting their devices before the update files were complete .... in some cases that may have been so. However that flood of problems has now reduced to a trickle as GE's matured into a more reliable program.