Quote:
Originally Posted by frostschutz
It uses checksums to keep track of things. It will try to (re)apply patches whenever the checksum (of either files or patches) changes. If someone uses KoboRoot.tgz to replace only one file, then it would be patched again.
|
So if the firmware updated automatically but librmsdk.so.1.0.0 didn't change, then the device would reboot again after the new firmware installed just to patch librmsdk.so.1.0.0? (the other patches would fail). Maybe an all-or-nothing option would be useful, so no patched files are installed unless all the patches succeed.
Quote:
|
I still want to add support for patches that work for any firmware version as long as its unique signature can be found; so while a string may be at a different address in each firmware version, as long as it's the same string and unique the patch should still work.
|
I've added this sort of capability in patch32lsb v0.9, a version for testing posted
here. (One of the fuctions needs to be made more efficient, but it should still produce correct results.) The idea should be workable for some patches that only modify data, but not for many of the ones that modify code, as often the code changes depending on its position relative to other code or data.