Thread: New garmin gcd

Originally Posted by VadimK

...As for the title of this topic.
The problem is not with the new GCD format. The format is old.
The problem is that the executable binaries are encrypted now.

I think it's compressed in a different way, not encrypted
for example fenix6 uses a very different hardware chip for example, but gcd is the same
I think if you will work with hex, find meaning with different gcd versions of different devices helps us more
common point for all new gcds hex (01 B4 44) Rzip
thanks on behalf of everyone for your help

Originally Posted by Butters

The 'extra' size of the contents in a saved region is accounted for by the fact that the entire region is saved as a BIN file, not just the usable data in it. The extra space is indicated by empty FFs at the end of the BIN viewed in a hex reader. If the FFs are removed the hash files of the original bin file and the shortened dumped bin file should match.
....

dear butters, nice to see you interested, I hope you help us with your experience

but rgn14 is filled with 00 not with ff, Writes to the entire 30,720 kb memory
idem rgn144 (compressed fw_all.bin) but not visible on some devices