Any chance to ask you to help me and combine these firmwares! I think, that i'm little bit stupid in firmwares creation!
Any chance to ask you to help me and combine these firmwares! I think, that i'm little bit stupid in firmwares creation!
It may not be you having difficulty combining the firmware. RGN_Tool is a little confused by the additional regions in the aera firmware. Leave it with me for a short while, I'll make it in another way for you. Be patient as I have some other more pressing matters to attend to at present.
I will be grateful if you do this for me. And i olso was confused when i have seen 3 unknown sectors in aera's gcd! Aera's firmware used by few models of Aera
devices : 500, 510, 550 and 560 ! One gcd for all these models and i dont know how the device choosing it ! Aera has 2 firmware : auto and avia, and device reloads each time when i change the mode, so aviation mode is more important for me!
All aera 5x0 are basically the same device and that's why there's only one firmware for all of them.
Let's just check some things before I go to the trouble of making a combined firmware for you. As you'd already seen, aera has 4 additional firmware regions used over zumo. I want to see if the additional regions populated by the aera firmware are also available on the zumo in it's current configuration. Both have unit software fw_all in the standard rgn 14 (hex 0x0E) of course, but due to their dual-purpose as aviation and automotive devices, aera devices have a second unit software fw_all2 in rgn 85 (hex 0x55) along with 3 other components, which RGN_Tool doesn't specifically identify naming all as 'unknown', in rgns 253, 254 and 250 (hex 0xFD; 0xFE; 0xFA). So first let's see if we can dump those additional regions 253, 254 and 250 from the zumo. There are usually 255 possible regions in Garmin devices so those additional components are right at the end. We may as well backup it's nonvol region 41 while we're at it, it's handy to have that anyway. Look behind the spoiler for a guide:
Spoiler:
Last edited by Butters; 15th August 2017 at 01:51 AM. Reason: replaced SD pack.
All those regions 55, 250, 253 and 254 are available on the zumo. Hopefully they are big enough to take the bin files from the aero's firmware. I've made a composite aera RGN with the boot.bin from zumo and the HWID retained as 924. This is still a time where you can back out and there'll be no hard feelings. From here on you're in uncharted territory and the risk is entirely yours. The devices have almost identical hardware but the slight difference in PCB P/Ns may be significant or not. So, on the strict understanding that although I feel we can at least recover it as a zumo if it gets bricked, the risk is still all yours. If you end up with a hard-bricked device you'll get my symphathy but that's all, so we proceed on that basis only. Look behind the spoiler:
Spoiler:
You can try the full aera firmware, but there is a far greater chance of bricking it. As that changes the HWID to 1063 and resets the region layout it makes it much harder to return to zumo if it goes wrong than it would be with zumo boot.bin and 0924 retained. Safer to stop now, it would be a quite courageous decision to go on. Fully at your discretion of course.
I've tried to load aera's firmware with HWID 0924 and result is the same like this!
Bookmarks