mysqldump dumps different data with and without --no-create-info
Try dumping using --hex-blob
mysqldump --hex-blob test_db test &gt; dump_test.sql
mysqldump --hex-blob --no-create-info test_db test &gt; dump_test2.sql

Please let us know if the hex value remains the same between the two dumps.
UPDATE 2021-01-08 14:15 EST
Try changing character set
The MySQL Docs say that mysqldump will use utf8 if not specified

Internationalization Options The following options change how the
mysqldump command represents character data with national language
settings.
--character-sets-dir=dir_name
The directory where character sets are installed. See Section 10.15,
“Character Set Configuration”.
--default-character-set=charset_name
Use charset_name as the default character set. See Section 10.15,
“Character Set Configuration”. If no character set is specified,
mysqldump uses utf8.
--no-set-names, -N
Turns off the --set-charset setting, the same as specifying
--skip-set-charset.
--set-charset
Write SET NAMES default_character_set to the output. This option is
enabled by default. To suppress the SET NAMES statement, use
--skip-set-charset.

Just add -N to ignore character sets or use --set-charset to explicitly name the character set you want to use when loading the dump in.