One-Click Install Packages for KOReader & Plato

[PeterT]

It's similar for me on a chromebook.

Yes, I "eject" any Kobo via the FileManager.

No, the Kobo does not recognise that it's been dismounted until I physically remove the cable.

It's been this way for as long as I've had a chromebook (many, MANY years).

[Jwing]

@Frenzie, thank you for replying.

There is a koreader crash log and it is big, I think it is because of the quantity of attempts.

The whole crash log is attached to this message, and I'll put here a chunk that, I think, is related to the last attempt.

Any thoughts?

               launching...
  _  _____  ____                _
 | |/ / _ \|  _ \ ___  __ _  __| | ___ _ __
 | ' / | | | |_) / _ \/ _` |/ _` |/ _ \ '__|
 | . \ |_| |  _ <  __/ (_| | (_| |  __/ |
 |_|\_\___/|_| \_\___|\__,_|\__,_|\___|_|

 It's a scroll... It's a codex... It's KOReader!
[*] Current time: 04/20/25-09:14:41
has monolibtic? no (libs/libkoreader-monolibtic.so: cannot open shared object file: No such file or directory)
lib_search_path: libs/?
lib_basic_format: lib%s.so
lib_version_format: lib%s.so.%s[*] Version: v2025.04

ffi.load: rt.so.1 (RTLD_GLOBAL)
ffi.findlib: utf8proc [3]
ffi.load: libs/libutf8proc.so.3
ffi.findlib: blitbuffer
ffi.load: libs/libblitbuffer.so
./luajit: frontend/device/kobo/device.lua:1791: unrecognized Kobo model spaBWTPV with device id 395
stack traceback:
	[C]: in function 'error'
	frontend/device/kobo/device.lua:1791: in main chunk
	[C]: in function 'probeDevice'
	frontend/device.lua:53: in main chunk
	[C]: in function 'require'
	./reader.lua:151: in main chunk
	[C]: at 0x00013e71
!!!!
Uh oh, something went awry... (Crash n°5: 04/20/25 @ 09:14:41)
Running FW 4.41.23181 on Linux 4.9.77 (#1 SMP PREEMPT 5e7b87d-20250116T185838-B0116213937)
Too many consecutive crashes, aborting . . .
!!!! ! !!!!
Restoring original fb bitdepth @ 32bpp & rotation @ 3
[FBInk] Unidentified Kobo device code (395)!
[FBInk] Detected a Kobo Unknown! (395 => ?? @ Mark ?)
[FBInk] Explicit EPDC wakeup isn't supported on this device
[FBInk] Clock tick frequency appears to be 100 Hz
[FBInk] Screen density set to 167 dpi
[FBInk] Variable fb info: 1072x1448, 32bpp @ rotation: 3 (Counter Clockwise, 270°)
[FBInk] Fixed fb info: ID is "hwtcon", length of fb mem: 6243328 bytes & line length: 4288 bytes
[FBInk] Canonical rotation: 0 (Upright, 0°)
[FBInk] Fontsize set to 16x16 (IBM (Default) base glyph size: 8x8)
[FBInk] Line length: 67 cols, Page size: 90 rows
[FBInk] Horizontal fit is perfect!
[FBInk] Vertical fit isn't perfect, shifting rows down by 4 pixels
[FBInk] Framebuffer pixel format: RGBA
[FBDepth] Screen is 1072x1448 (1072x1456 addressable, fb says 1072x1448)
[FBDepth] Buffer is mapped for 6243328 bytes with a scanline stride of 4288 bytes
[FBDepth] Current bitdepth is already 32bpp!
[FBDepth] Current rotation is already 3!

[petersz]

It's the same for me. Unfortunately, this update does not work with Clara BW.

[Frenzie]

Originally Posted by Jwing

@Frenzie, thank you for replying.

There is a koreader crash log and it is big, I think it is because of the quantity of attempts.

The whole crash log is attached to this message, and I'll put here a chunk that, I think, is related to the last attempt.

Any thoughts?

In that case the thing to try is to see if it works if you add or codename == "spaBWTPV" to this line: https://github.com/koreader/koreader...ua#L1786-L1787

[Jwing]

@Frenzie, it worked!

Do I have to open a pr for koreader to add that line to the next versions?

[Frenzie]

Please do.

[Jwing]

I was unable to open a PR, too advanced for me

Instead, I opened an issue.

[RICC8245]

This is a very long story. I hope maybe one of you can give me a hint to get back on track, but I also understand if you'd rather read a different novel ;-) With this post, I'm trying to show what I've done so far and that I've tried a lot before starting to ask things immediately.

So, my question is: I can't get KFMon and/or NickelMenu to work. Does anyone have an idea how I can get this working? I've read and tried so much, but I just can't figure it out.

My situation:

I have a Kobo Libra 2. I flashed a new microSD card (the old one was corrupt) with the Kobo Libra 2 revision E image (thanks to DNSB!)

After flashing, the e-reader immediately tried to update but failed. It then started a loop where it appeared to update, but after rebooting I had to set the language and WiFi again. After the third cycle, I decided to set up the Kobo via Kobo Desktop for Mac. That did get me to the Nickel homescreen.

Through pgaskin.net, I downloaded the latest firmware for the Libra 2. The installation of that update seemed unsuccessful at first, because the version number didn't change > 4.32.19501 (oe55e3f620, 14-04-22). However, when I checked the release notes through the settings, I did see the notes that belong to the October 2024 update > version 4.38.23171. The same menu also shows the serial number as "Noooooooooooooooo." I tell this just for troubleshooting reasons. This behavior is normal because from the filename of the Revision E image that I flashed, it already says that no serial number is attached to it.

Previous experience with custom software:

I jailbroke a Kindle using Winterbreak and installed KOReader on it without any trouble.

What I've already tried:

- Downloaded the one-click install: OCP-KOReader-v2025.04.zip
- I placed it in a folder on my Mac, along with install.command (from kfm_mac_install.zip, which I unzipped manually).
- Connected the Kobo Libra 2 via USB to my MacBook Air M1.
- Ran install.command (granted Gatekeeper permission) and selected option 0.
- The process took about a minute with no errors according to the script.
- Unmounted the device as instructed.
- It looked like Kobo processed the files and it appeared to detect the .tgz, as it triggered an 'update'.
- Back in the Nickel homescreen, I saw the KFMon log and KOReader books, but tapping them just opens an image, nothing else.

I repeated this process several times, after doing a factory reset via the dev menu in between. Each time, I changed one small thing:

- After one "successful" install, I also unplugged the USB cable right after unmounting.
- Another time, I fully powered off the e-reader before starting the process > no menu interaction at all, except one tap to connect the Kobo to my Mac. I tried this both with and without removing the cable after unmounting.
- and one time I tried launching KOReader right after installation.
- Another time, I restarted the e-reader after installation, but even then, tapping the KOReader book just opens an image. It doesn't launch KOReader.

By the way, I keep mentioning opening a book via KFMon, but NickelMenu doesn't show up either.

Other things I've tried:

- Installing the package with KOReader and Plato combined (both via the script and manually)
- Installing NickelMenu separately
- Installing KFMon separately
- Added a trigger to the nm folder (although there was no sign of the menu in the Nickel UI)

I hope someone recognizes some kind of pattern here. I love to use KOReader on my kindle, but I miss the page turning buttons on that one

[DNSB]

That sounds almost as if KFMon is not installing or the # commenting out it's launching of KOReader or Plato is not being removed. I take it NickelMenu is installing which suggests the KoboRoot.tgz file is being copied to the .kobo directory on your ereader correctly.

Have you tried launching KOReader or Plato directly from NickelMenu?

I've attached a sample NM.txt file with the lines needed to launch KOReader and Plato from NickelMenu without need for KFMon or the icons.

menu_item : main    : KOReader           : cmd_spawn : quiet : exec /mnt/onboard/.adds/koreader/koreader.sh
menu_item : main    : Plato              : cmd_spawn : quiet : exec /mnt/onboard/.adds/plato/plato.sh

Simply copy that file into the .adds/nm directory and delete the koreader and/or plato files in that directory.

Since you are using a Mac, I'm assuming that you are showing hidden files/directories with names starting with a . by hitting command+shift+. or have configured that option using Terminal.

[Frenzie]

^ I switched to doing it that way a while ago because it's unaffected by updates most of the time.

[snafus]

Hello,

I've unsuccessfully tried installing Koreader Cervantes as well as other versions of koreader on my Kobo Aura H2O second edition using the instructions found here:

https://www.mobileread.com/forums/sh...d.php?t=314220.

I would appreciate if someone could tell me what's wrong.

Thank you for any help you can offer.

[DNSB]

Originally Posted by snafus

Hello,

I've unsuccessfully tried installing Koreader Cervantes as well as other versions of koreader on my Kobo Aura H2O second edition using the instructions found here:

https://www.mobileread.com/forums/sh...d.php?t=314220.

I would appreciate if someone could tell me what's wrong.

Thank you for any help you can offer.

I take it you did not download and install the version in the first message in this thread? Nor did you try to use the One Click installer referenced in the second message in this thread?

Why would you have downloaded and attempted to install a version intended for a Cervantes ereader instead of one intended for a Kobo ereader? When you visited the KOReader download page, did you click on the Show all 20 assets button?

[snafus]

Hello, David,

I tried installing the version you are referring to as well as the Cervantes version by extracting the files to the root section of the reader and waiting for it to process the files. I've also tried the One click installer option which also doesn't seem to work.

[DNSB]

So you copied the contents of the .zip archive to the root of your Kobo. Does that mean you copied the .adds and .kobo directories from the archive to the root of your Kobo's exposed storage?
The One Click Install script for Windows PowerScript does show a series of steps that you must follow. So to basically recap the Windows method shown in message #2 in this thread
[list=1][*]You downloaded the OCP-KOReader-v2025.04.zip file and placed it in a directory on your Windows computer.[*]You downloaded the installer script (install.ps1) and copied install.ps1 into the same directory as the .zip file(s) you downloaded.[*]You unblocked the installer script as per step 3 in the instructions with pretty pictures.[*]You ran the installer script either by right clicking and run with Powershell or by opening a Powershell command window, CDing to the directory where you placed the files and running .\install.ps1 (the .\ or ./ is required since by default, Powershell does not look in the current directory). This is my recommended method since it allows you to see any error messages.[*]Once the install was finished, you safely ejected your Kobo, watched the install screen run and your Kobo rebooting and coming back to the GUI.

Image of running ./install.ps1 in the same directory as two OCP packages is attached.

Manually installing the package is a lot more pain since you need to modify the ExcludeSyncFolders line under the [FeatureSettings] header.

[FeatureSettings]
ExcludeSyncFolders=(\\.(?!kobo|adobe).+|([^.][^/]*/)+\\..+)|(screensaver_old)
IgnoreCaptivePortal=true
InvertScreen=false
Screenshots=false

[alaskazimm]

This afternoon I tried to use the install scripts from the second post on both Linux and Windows. This was on a Clara Colour and a fresh reboot. The Clara is registered. The scripts wouldn't run on either OS - Linux wouldn't even open the command line window and Windows flashed the PowerShell window briefly. I did follow the instructions with both the script and zip files in the same folder.
In the end, I wound up doing it manually by unzipping the files to the root of the device and manually updating the .conf file. All's well that ends well, but I have no idea why the scripts wouldn't run.