Thread: aera 795 stuck on 'Loader' after fw update (could getting Unit ID from GMA or UNL files help?)

Originally Posted by MY58002

........
2) I read somewhere the RGN file must be in the same folder as Updater.exe. So I also tried moving this generated RGN file to the same level where Updater.exe is and then launche the updater by dragging the RGN file onto it

They only need to both be in the same folder (directory) if you intend to load the RGN by starting Updater.exe, otherwise drag and drop should work fine if they are in different locations. Drag and drop doesn't work in GarminCure3.exe if set to run as Admin though.

3) I have all executables set to start as Administrator

Try again without "Run as Adminstrator" checked for Updater.exe and/or also change compatibility to an earlier version of Windows, even try XP. However both V2.7 & 2.8 of Updater work fine for me in Win10_64.

5) When I load the GCD file into the RGN tool it shows boot.bin and fw_all.bin with correct HWID (1364) and SW Version (560) but it also shows 4 more "Unknown.bin" files where HWID and SW Version is just NA. Is this correct?

RGN_Tool is older than much of the fw existing today. Sometimes it isn't sure 'what is what' in regard to regions and sections so i'd suggest if you want to check the RGN file's BIN components you use this instead: [Only registered and activated users can see links. ]. It's much better at correctly identifying the contents accurately and the author of both Cure 3 and gfw is kunix so there'd be no cock-ups in either i'd think .

6) There are two official Garmin master reset procedures. The one that also wipes nonvol requires the unit to be in the stand. I also tried numerous times to flash while in the stand.

As you've found this problem cannot be rectified by a reset/clear nonvol. I don't think you need to have it in the cradle for flashing either.

7) From the "How to unbrick a nüvi" document I understand I should be holding the power button during the entire updating process. This means that after the first phase of updating the unit restarts and then enters preboot mode again. The second phase begins but the Updater only goes to 2 % and then disappears. No message or anything.

8) No matter what happens, if I do not enter preboot it still shows the old SW version (550) and then shows LOADER which is a dead end and battery needs to be removed.

Worst case scenario is physical flash damage exists. Let's assume otherwise for the present and press on.

I can make a video of the process if it would be helpful.

If you want to go to the trouble, sure do that. However it's not necessary ATM.

Also I want to apologise for creating this thread. I believe this should be a part of the GarminCure3 thread.

A mod has been approving some of your posts which must have been sent to the moderation queue for approval, perhaps your IP is causing that. Regardless if Boki_Srb thought it belonged elsewhere, he'd have likely moved it already. Personally, i think your problem is more than a little different from the 'run of the mill' everyday brickings of common devices and additionally it's an aviation unit so as such deserves it's own thread for both reasons.

Good luck. Persistence sometimes pays off with stubbornly bricked devices.

EDIT: Gah! Your next post made 17 mins before mine was also moderated and i didn't see it before i posted as above.

Originally Posted by MY58002

Hello,

I have a little update. If I use GarminCure3 to generate the RGN file, the first update phase takes about 5 seconds to complete, then the unit restarts and then the Updater just disappears.
If I use RGN tool to generate the RGN file, it only takes about a second to complete the first phase. It is much quicker. The same GCD file is used in each case. I was just wondering if this could indicate something...

Well, the two RGNs are different files in that one is a 'standard' firmware and the other a 'cure' firmware. There's no point you trying to flash an original (unmodded) RGN anyway whether it's the same version as already on-board or later because the reason the device isn't starting is that it cannot load a file that's already on the device. The way GCD and some other update files and RGN files are treated differ immensely. An RGN is flashed by Updater.exe directly to the relevant regions whereas in modern Garmin devices other files like gupdate.gcd for example are first loaded to a directory in the device's visible file system (also a 'region' but a special one, in your aera probably region 83). In the latter case, the flashing is delayed until the next boot when as part of the start-up sequence the device will attempt to load those files appropriately, e.g. the components of a new (later fw version) gupdate.gcd in the root of .System are loaded (flashed) to the respective regions and other lesser updates in .System\RemoteSW folder are also activated. I believe it's one of those minor files causing the problem provided the device is otherwise healthy.

I also tried to use another cable and another PC. My PC has Win 10, I tried on Win 7 too. The same behavior was observed.

Not an operator error it would seem going by that.

Once the updater disappears (after restart) the unit remains in the boot mode even without holding the power button. It remains connected and when I launch Updater again it still recognizes the unit.

Yes however you'll not be successful in getting a flash initiated in that situation in my experience. Best to power off and start again.