Firmwares 4.39.23027 and 4.38.23038

[BionicGecko]

Originally Posted by jkrzok

I have a Clara BW coming today and would like to patch it as i always do. While there are no new patches for the latest firmware I see that some people are patching their devices.

Is it as simple as following the instructions in the latest patch thread while ignoring version numbers? Do I need to rename or otherwise modify the update or patch zips? And lastly, is there any chance of bricking my new device?

I went through that rabbit hole recently and perhaps the following posts can help; these are unofficial releases of working patches for firmware versions 4.39.22861 and 4.39.22801 respectively. If your Clara comes with, or updates to, 4.39.23027 when you set it up, you will have to manually update the version numbers here and there in the yaml files.

[DNSB]

Originally Posted by ghira

Does that happen? I think I waited for that once, gave up, and have never given it serious thought since.

That has worked for me on Windows, Linux and MacOS. As near as I can tell, the eject process momentarily removes power from the USB device which most intelligent devices seem to treat as "I've been disconnected".

For Kobo device owners, this is why the USB connect option from NickelMenu is handy since you can reconnect without having to remove the USB cable.

[ghira]

I just ejected my Kobo, forgot I had done it and went and did other things for at least half an hour, I would say. Came back and screen still not back to "normal". So it does seem as though waiting is pointless for some reason at least in my case.

[rantanplan]

Originally Posted by ghira

I just ejected my Kobo, forgot I had done it and went and did other things for at least half an hour, I would say. Came back and screen still not back to "normal". So it does seem as though waiting is pointless for some reason at least in my case.

That's weird because for me the Kobo deviced go to the home screen after ejecting it. It takes about 10 seconds or so. I'm on macOS Sonoma.

[Aleron Ives]

On Windows, ejecting from the tray will not release the device from the charging screen; you must unplug it first. Ejecting from Windows Explorer will release the device from the charging screen, though. Different ejection methods yield different results.

[mbovenka]

Originally Posted by Aleron Ives

Ejecting from Windows Explorer will release the device from the charging screen, though.

Ejecting from within Calibre will as well.

[jkrzok]

Originally Posted by BionicGecko

I went through that rabbit hole recently and perhaps the following posts can help; these are unofficial releases of working patches for firmware versions 4.39.22861 and 4.39.22801 respectively. If your Clara comes with, or updates to, 4.39.23027 when you set it up, you will have to manually update the version numbers here and there in the yaml files.

Many thanks. This worked a treat once I saw that the kobopatch.yaml mention the firmware version twice.

I was unsuccessful in applying the increase size kepub chapter progress chart. I got this in the log

could not apply patch "Increase size of kepub chapter progress chart": line 672: inst 4: ReplaceZlib: not a zlib stream

I got a similar error for the don't capitalize the header/footer text as well.

I'm running 4.39.23027.

[JSWolf]

Originally Posted by DNSB

Probably never. You did notice that the 4.38 firmware is 11 builds ahead of the 4.39 firmware? I tend to the belief that the next unified firmware for Kobo ereaders will be a v5 firmware for Kobo and tolino ereaders.

Does that matter as it's the main number 4.38 vs 4.39 that should matter most?

[JSWolf]

Does anyone think that that 4.38.23038 fixes the file open issue?

[DNSB]

Originally Posted by JSWolf

Does that matter as it's the main number 4.38 vs 4.39 that should matter most?

For our purposes the build number is likely the one that matters more.

[DNSB]

Originally Posted by JSWolf

Does anyone think that that 4.38.23038 fixes the file open issue?

If you are referring to the database not being properly closed before the USB connection is made? If so, I did ~100 cycles of connect, eject/disconnect, read and back to connect without seeing any database corruption being detected. I take that as meaning that we may see an occasional database corruption but the consistent bug that we have seen for the last few firmware releases has been swatted.