The story behind this:
a) the normal way of flashing
You use an original flasher (.exe) to update your drive. If the flasher
detects an unsupported drive (e.g. when trying to flash an 832’s
firmware into an 812s), it will refuse flashing.
b) the cheaters’ way of flashing
You grab the official fw, run it through OmniPatcher and either
get a .bin file or a “more-user-friendly” .exe. Both can be used
to flash 812S@832S, for instance (EEPROM check has to be
As the newer firmwares are packed/scrambled, OP doesn’t help here
and that way cross-flashing (“overclocking”) is prevented.
There are at least three methods how overclocking-capabilities can
I) You manually unpack/unscramble the exe-flasher incl. the .bin.
This can be really hard work.
II) You know someone who owns a real 832S (NOT …S@832S!).
He can use the original flasher (as it’s intended for his drive…),
extract the fw and send you the .bin afterwards. This .bin can
be “injected” in a flasher (.exe), which then can be run through
(That’s perhaps the way the CodeGods aka CodeGuys took.)
III) You know someone living in .au who’s capable of checksumming
your EEPROM so that the (packed/scrambled) flasher-tool thinks
you’re having an 832S (instead of the old-fashioned 812S).
You then can continue with the 2nd part of II) and let your
imaginations flow freely…