Originally Posted by knc1
And yes, you have to either patch the checksum or do it the "lab126 way" and no-op the checksum tests.
Which is how they get away with bspatching the u-boot and uImage files and still be able to load them.
If you use the various mkimage tools, you will find that the patched images fail the checksum tests but load and run anyway.
JFYI, U-Boot was never changed by any KT firmware update. KT's OS hasn't access to U-Boot paritition (read access, at least; it looks like idme
tool can write to it).
Recent versions of kernel can access eMMC boot parition, but this functionality isn't present in KT's kernel/modules.