Alpha100 flashing firmware version 7.90 problems

**Fa_Piter** · 8th August 2021, 07:09 PM

The actual problem is that newer versions of Alpha100 come with version 7.80. But the latest version available via Webupdater or Express is 7.80.
If you flash 7.80 into a new Alpha (for example, patched), then the compass stops calibtation. And you cannot return Alpha back to 7.90, since it is not freely available.
Help me!

See Posts 4 to 8 for compass fix solution and Post 17 for hybrid V7.80/V7.90 firmware RGN file. Note Warnings!

**Garman_Nuvi** · 9th August 2021, 06:02 AM

Fa_Piter has exceeded their stored private messages quota and cannot accept further messages until they clear some space.

Garmin has started putting the next Firmware version number in the garmindevive.xml ready for the next update but I'm sure your device only had 7.80 installed before you (for example, patched).
Check your own garmindevice.xml

<PartNumber>006-B1562-00</PartNumber><Version><Major>7</Major><Minor>80</Minor></Version><Path>Garmin</Path><FileName>GUPDATE.GCD<

Spoiler: large image

**Fa_Piter** · 9th August 2021, 10:19 AM

Sorry. Freed up space.

I checked garmindevice.xml.
- <UpdateFile>
<PartNumber>006-B1562-00</PartNumber>
- <Version>
<Major>7</Major>
<Minor>90</Minor>
</Version>
<Path>Garmin</Path>
<FileName>GUPDATE.GCD</FileName>
</UpdateFile>

I tried to upload 5 and 14 regions from Alpha100 version 7.90. Cut off the last FF bytes.
I packed wirmare with rgntool and gfw, result is the same. But then I try to update Alpha with this firmware it goes into a loop ("Loader loading.." - reboot).

**Butters** · 9th August 2021, 11:25 AM

Originally Posted by Fa_Piter

.........
I tried to upload 5 and 14 regions from Alpha100 version 7.90. .......

Flashing region 5 (the bootloader) directly may be problematic. Perhaps you should try SD method to flash just region 14 seeing the Alpha fw supports txt command xrgn. The boot.bin/ldr.bin (ramloader) from V7.80 will likely handle flashing V5.90 fw_all.bin i think.

**Fa_Piter** · 9th August 2021, 11:52 AM

As I understand it, you propose to build the firmware with 7.80 loader and 7.90 body, and if it does not work out, flash 14 region directly from SD.
Ok. I will try it.

**Butters** · 9th August 2021, 12:00 PM

Yes that's exactly what i mean. As you already have V5.80 bootloader and x-loader on-board there should be no risk in using its ramloader and it should work provided it's capable of loading the V5.90's main firmware.

**Fa_Piter** · 9th August 2021, 03:40 PM

Yes. I am understand. I made this "hybrid" and 7.90 was flashed. I still to to check compass.... Ok, working!
Thank you for your helping!

**forla** · 31st August 2021, 08:35 PM

Originally Posted by Fa_Piter

Yes. I am understand. I made this "hybrid" and 7.90 was flashed. I still to to check compass.... Ok, working

can you share the "hybrid" firmware

**Butters** · 10th August 2021, 02:31 AM

I know you have good Garmin knowledge Fa_Piter so likely now understand why your previous attempt to flash the V7.9's dumped 5 & 14 regions failed, however to explain more for others, region 5 is a sensitive region as it's the bootloader and if it becomes corrupted the device might never boot again and be 'dead'. To some extent rgn5 might be protected against direct flashing, depending on device. Also it may be impossible to directly flash it anyway as when boot.bin/Ldr.bin (note: despite the 'boot' reference, boot.bin is the ramloader) is being executed it's being flashed to a virtual region, region 12 (0x0C), which in turn flashes the bootloader to region 5 along with the x-loader to region 43. That's done entirely on the device. So you can see it may be problematic to try directly flashing rgn5 when rgn12 is also flashing it. If it's unprotected, a direct flash using a copied 5.bin alone as an RGN might succeed but may also hard-brick the device. Short story: Don't mess with region 5.