Thread: Garmin Updater Program

The link

Code:

Please Login or Register to see the links

is for 2.7.0.0 version!
I've removed your direct link and coded it. Please CODE all outside links other than to 3rd party download sites. Read: [Only registered and activated users can see links. ]

Originally Posted by dafjkhsd

The link [<uncoded Garmin link removed>] is for 2.7.0.0 version!

So just use the later file attached on our server. Either will work fine with most devices anyway, also there doesn't seem to be an easily found official link for V2.8 so if you have one please post it. BTW, direct links are not allowed as per [Only registered and activated users can see links. ] so you should either remove that from the quote in your post or code it otherwise a mod might do it anyway.

OP edited to note the earlier version on Garmin's server.

Originally Posted by Butters

also there doesn't seem to be an easily found official link for V2.8 so if you have one please post it.

There are several versions of UPDATER.EXE.
I only managed to find 7 versions on Garmin and Perry sites.

Code:

Please Login or Register to see the links

*Strange, but there are 2 options for version 2.5.

In the attachment, I put an archive with all 7 versions:

I wanted to ask a question in [Only registered and activated users can see links. ], but today it was closed.
Therefore, I will ask my questions here.

Thus, the Updater works correctly with all modern devices that can switch to pre-boot mode. Correctly ?

It's not entirely clear why WebUpdater is not used for these purposes?
It is more modern, it can work not only with the RGN, but also with the GCD.

@Vadimk
A "bricked" device which boots only as far as the logo splash screen due to an unloadable file (or files) needed to boot, may not be detected by WebUdater but should always be detected by Updater (that's in preboot only for modern devices, as the very old 'region-only' devices are in a perpetual state where Updater.exe can be used regardless to re-flash its regions as required).

Modern devices normally have a visible file system accessible in Mass Storage Mode which isn't available if the device is soft-bricked, however usually in such cases preboot is still available. To remove corrupt files or re-format the file system, it's necessary to load a modified "cure" firmware so that MSM is re-enabled. After removal of corrupt files or formatting, original firmware is then loaded back to the device.

So you can now understand that if the boot process doesn't complete far enough for WebUpdater to be used, Updater.exe can be be essential to repair a device by software means.

I think you need to read my previous post again carefully. Note the use of "may not", you seem to have read that as "can't" (can not). Also i was referring to preboot mode not MSM for bricked devices. Incidentally, txt commands via media card are usually also not initiated by a bricked device because the card is read after "Loading Maps" appears on the device screen. Most bricked devices therefore don't get far enough into the boot process to read the card.

Brick a device intentionally and test for yourself if it's detected by WU in preboot.

Certainly nuLink 23xx does use Updater.exe in preboot. If the screen of the device isn't held for long enough then the preboot connection might be dropped but that's not what seems is happening in your case. Usually holding until "Updater"/"Software Updating" appears on the device screen is sufficient however holding for the entire process is best to be sure. Once a flash is initiated it should complete in the case of a 'soft-bricking'.

A faulty region in the device memory or a physically failed chip can be a cause of the flash not completing.

So, provided you're sure the RGN file has been properly prepared and your flashing procedure is correct, there may indeed be a hardware fail. Do you get a "success" message or any any other message on screen after the 100% green bar?