|
hex editor was mentioned less with need to use it, more with 'double-check what actual calids in binary blob are, not just first from those (possibly changed) that flashing software might misreport'. Hex editor just as one of means to check for those calids in binary firmware file.
But also definitely, as tune definitions tell at which address which value tables reside and as that is specific to tune version, it's of utter importance to have definition table to match tune editted/flashed, to not have wonders that changing some table alters some random code in firmware image, instead of altering table that wished.
|