kobopatch - An improved patching system

[Mrs_Often]

Originally Posted by Dirk-71

I have created an overview of all patches with description of dependencies:



https://docs.google.com/spreadsheets...it?usp=sharing

Very nice!
Why am I not allowed to enable `Block WiFi firmware upgrade’?

[anacreon]

Originally Posted by geek1011

• Optional new format which is more powerful and consistent (demo)

The link to demo doesn't work for me (404 error).
Thanks, best, anacreon

[Dirk-71]

Originally Posted by Mrs_Often

Very nice!
Why am I not allowed to enable `Block WiFi firmware upgrade’?

You are allowed, but one say it is risky. I don't know more about the details!

[geek1011]

Originally Posted by anacreon

[/LIST]The link to demo doesn't work for me (404 error).
Thanks, best, anacreon

I removed it, as it got really out of date. The actual patches are better examples now.

[mbovenka]

Originally Posted by Dirk-71

You are allowed, but one say it is risky. I don't know more about the details!

I've had it enabled since pretty much forever. I don't know why it should be dangerous either; AFAIK it only sets the 'current version' in the code that checks whether the offered OTA version is newer to something off the scale, so that the OTA version is never newer.

It never gave me any trouble.

[Dirk-71]

I have extended the overview of patches.

Overview of Patches - Table

The question arises "Do I have to configure a patch?" if one wants to make use of kobopatch.yaml to overwrite the settings. In koboptach.yaml you only can choose YES or NO. But for some patches you HAVE TO do some configuration in the patch itself. That's why I have added a column "Settings?" in the overview where you can see, which patches require individual configuration.

[anacreon]

Originally Posted by Dirk-71

I have extended the overview of patches.

Overview of Patches - Table

The question arises "Do I have to configure a patch?" if one wants to make use of kobopatch.yaml to overwrite the settings. In koboptach.yaml you only can choose YES or NO. But for some patches you HAVE TO do some configuration in the patch itself. That's why I have added a column "Settings?" in the overview where you can see, which patches require individual configuration.

Thank you, very interesting. Is there a way to subscribe for modifications?

EDIT: I see the brightness fine control has no effect. Is it linked to the new patch system or to the F/W?

[Dirk-71]

Originally Posted by anacreon

Thank you, very interesting. Is there a way to subscribe for modifications?

EDIT: I see the brightness fine control has no effect. Is it linked to the new patch system or to the F/W?

I don't know if subscription is possible. Will get back to you later.....EDIT: Subscriptions are not possible. Sorry.

Brightness Control: I don't know whether it's the firmware or the patch. But it does not work as it should.

[Dirk-71]

Attached you'll find a complete kobopatch.yaml you can use as a starting point. You simply have to choose which patches you want to enable. There are remarks with information about dependencies etc.

It comprises all patches of firmware 4.10.11591. If you want to use it for earlier firmwareversions, you have to comment out all patches which are new in firmware 4.10.11591, e.g. "My 24 line spacing value". Otherwise you'll get an error.

[Terisa de morgan]

Hi geek1011,

I've already patched my Aura One and my Clara, adapting the new names, and it's have been quite easy. I've got a doubt, or a curiosity. There is an "out" directory that, in my mind, it's the point where koboroot.tgz will go. It is always empty, and this file is generated inside the "root" directory, where kobopatch.yaml is. I'm using the windows version of the tool.

PD: I keep the message but I've found the answer in a previous version I hadn't seen. You can define rules inside the yaml configuration file for out and log directories, and I hadn't defined in this configuration file, so it goes to the default place: root.

[DNSB]

A couple of items on the Windows patch setup.

1. Change the 'cd "%~dp0"' to 'cd /D "%~dp0"' to allow running from a different drive when using run as administrator or running from a different drive.

2. Possibly add a "timeout /t 60" statement at the end of the batch file rather than the fixed 60 seconds wait time from the executable. At least that way, I can hit a key rather than waiting 60 seconds or closing the window.

[geek1011]

I'll have updated patches for 4.10.11655 by later today.

Originally Posted by DNSB

A couple of items on the Windows patch setup.

1. Change the 'cd "%~dp0"' to 'cd /D "%~dp0"' to allow running from a different drive when using run as administrator or running from a different drive.

2. Possibly add a "timeout /t 60" statement at the end of the batch file rather than the fixed 60 seconds wait time from the executable. At least that way, I can hit a key rather than waiting 60 seconds or closing the window.

Thanks for the pointers. They're just in time for the new version today.

[geek1011]

Patches for 4.10.11655: https://www.mobileread.com/forums/sh...d.php?t=310315

[jcn363]

Maybe a ReplaceAllHex or ReplaceAllBytes instruction could be useful. Or change the actual one: when not offset then change all.
Good luck.

[geek1011]

Originally Posted by jcn363

Maybe a ReplaceAllHex or ReplaceAllBytes instruction could be useful. Or change the actual one: when not offset then change all.
Good luck.

I have considered doing that, but I decided against it, as there is too much possibility of replacing more than you meant or having a patch break silently between versions.