KoboPatch WebUI: customization (NickelMenu, KOReader) and patching via your browser

[PeterT]

I'm a tad confused. I'm trying the Beta site https://kp-dev.nicoverbruggen.be/ intending to install the Unify Font size patch on my Libra Colour running 4.45.23697. The site correctly identifies my device, displays the serial number etc, lets me select the desired patch. However when I get to the penultimate page the verification page indicates the download URL is https://ereaderfiles.kobo.com/firmwares/kobo12/May2026/kobo-update-4.45.23697.zip and then the verification text reads

You can verify if this URL matches your Kobo's model on Kobo's support page. The most important bit is that "koboXX" matches, for example "kobo13" for Kobo Libra Color.

Note the fact that the download location is kobo12, but the model should be kobo13.

Checking via PGaskin's list the download location there shows up as https://ereaderfiles.kobo.com/firmwares/kobo13/May2026/kobo-update-4.45.23697.zip

[MrSilverstrike]

Originally Posted by PeterT

I'm a tad confused. I'm trying the Beta site https://kp-dev.nicoverbruggen.be/ intending to install the Unify Font size patch on my Libra Colour running 4.45.23697. The site correctly identifies my device, displays the serial number etc, lets me select the desired patch. However when I get to the penultimate page the verification page indicates the download URL is https://ereaderfiles.kobo.com/firmwares/kobo12/May2026/kobo-update-4.45.23697.zip and then the verification text reads

Note the fact that the download location is kobo12, but the model should be kobo13.

Checking via PGaskin's list the download location there shows up as https://ereaderfiles.kobo.com/firmwares/kobo13/May2026/kobo-update-4.45.23697.zip

Let me start by saying that the mapping as kobo12 = Libra Colour I've used is based on this support article on Kobo's documentation page here: https://help.kobo.com/hc/en-us/artic...evice-Firmware

It also lists the P365 revision Clara BW as kobo14, which is missing from the website you've linked, so I've used it as the authoritative source for the list of downloads here: https://github.com/nicoverbruggen/ko...downloads.json

I've always used pgaskin's downloads page myself before building this tool, and I don't recall the list there ever being wrong (just missing the kobo14 entry), so I'm a bit confused myself, too. Either way, as it stands, either the official documentation or Patrick's site is displaying the wrong URL mapping?

EDIT: I did a quick diff of both firmware zips and it seems to me that the only difference in KoboRoot.tgz itself is that in kobo12 the note taking libs and the PDF stack is missing. So Patrick's site is correct and the documentation is wrong. So I'll need to fix the URLs! Thanks for pointing this out.

[cellaris]

Great work! Thank you very much. I find it really handy to be able to install the patches on my Kobo e-readers without needing a computer to hand.

[PeterT]

Originally Posted by cellaris

Great work! Thank you very much. I find it really handy to be able to install the patches on my Kobo e-readers without needing a computer to hand.

Maybe I'm missing something here. Thus tool is a website designed for use from a desktop or laptop; not from the device itself or phone or tablet

[cellaris]

Originally Posted by PeterT

Maybe I'm missing something here. Thus tool is a website designed for use from a desktop or laptop; not from the device itself or phone or tablet

I’m sure it’s as you say, but I’ve tried it several times using my smartphone’s browser and it’s worked fine for me (admittedly with an initial warning message). In any case, I’m not recommending anyone else do it this way; it’s simply how I’ve used it myself.

[MrSilverstrike]

It's true that mobile is indeed supported, but the happy path with the "Connect to Kobo" flow where you don't even have to copy the file(s) yourself sadly isn't functional on mobile.

Cool to see the various ways in which people are using the site!

[cellaris]

Originally Posted by MrSilverstrike

It's true that mobile is indeed supported, but the happy path with the "Connect to Kobo" flow where you don't even have to copy the file(s) yourself sadly isn't functional on mobile.

Cool to see the various ways in which people are using the site!

That’s right. You can then transfer the KoboRoot.tgz file wirelessly (which is what I did) or via a USB cable from your smartphone to the e-reader. For me, the important thing is that I can do without a computer – to which I have very limited access for reasons that are beside the point – whilst I always have my smartphone with me.

[Phil_C]

This looks awesome and easy to use.

The aforementioned ability to save previous patch choices and customizations would be welcome.

One more thing would be useful: I use the "Additional Files" section of kobopatch.yaml to add certain Kobo encrypted fonts from earlier devices that were removed on newer devices. The fonts reside on my laptop SSD. Is there some way to incorporate this into your patching system?

[MrSilverstrike]

Originally Posted by Phil_C

This looks awesome and easy to use.

The aforementioned ability to save previous patch choices and customizations would be welcome.

One more thing would be useful: I use the "Additional Files" section of kobopatch.yaml to add certain Kobo encrypted fonts from earlier devices that were removed on newer devices. The fonts reside on my laptop SSD. Is there some way to incorporate this into your patching system?

So, the saving and re-loading of previous patch choices should already work!

When it comes to adding additional files... it sounds like it'd be possible. I'll take a look at it.

I totally understand why you'd want to do this, as I'm quite fond of e.g. Amasis and Caecilia myself. They are sadly no longer present on the new devices. As an aside, the font selection getting worse is actually why I began curating this collection.

[Phil_C]

Originally Posted by MrSilverstrike

So, the saving and re-loading of previous patch choices should already work!

When it comes to adding additional files... it sounds like it'd be possible. I'll take a look at it.

I totally understand why you'd want to do this, as I'm quite fond of e.g. Amasis and Caecilia myself. They are sadly no longer present on the new devices. As an aside, the font selection getting worse is actually why I began curating this collection.

Thanks for looking at this. And I'll take a look at your font collection.

I really missed Avenir and Gill Sans when Kobo failed to include them on newer models, so I added them to my Kobos via Kobopatch.yaml where needed.

[MrSilverstrike]

@Phil_C: I got this working. You can try out the feature on the preview at:
https://kp-dev.nicoverbruggen.be

It's accessible via the "Advanced" section below the patch selector.

You normally need to put in the destination path for the files manually, but fonts are automatically detected and the path is prefilled for an easy "sideload fonts to the system partition" experience.

(I've successfully used it to patch in some of my own fonts, which seems to work fine. If you want to undo it, removing these patched files still needs to happen via telnet or SSH, as you can only zero out patched files to "disable" them.)

[PeterT]

I was thinking last night that it might be interesting if when you build the tgz file it could include a configuration file listing which patches/options had been selected, and store this config file in the devices .kobo directory or .adds/patches

[MrSilverstrike]

Originally Posted by PeterT

I was thinking last night that it might be interesting if when you build the tgz file it could include a configuration file listing which patches/options had been selected, and store this config file in the devices .kobo directory or .adds/patches

This already happens!

Currently, a manifest is stored in the (hidden) .kobopatch-webui folder at the root of the drive if you use "Connect to my Kobo" via USB and patch your device.

The manifest contains information about the patches you last chose, and you can "re-apply" the patches that you chose before if you attempt to go through the flow again.

The NickelMenu flow works the same way (it also generates a manifest) and there's a logs folder in there too for everyone who wants to see exactly what the webapp did to their device.