Firmwares 4.39.23027 and 4.38.23038

[lumping-sugar66]

Is it just me or is it that they introduced a password to the telnet? I enable it with nm, yet I am prompted for password.

[DNSB]

Originally Posted by lumping-sugar66

Is it just me or is it that they introduced a password to the telnet? I enable it with nm, yet I am prompted for password.

As has been mentioned several times, root now has a password. However you can use admin/admin as the user/password.

[Cactus Chef]

Adding a password to root is not a bad thing. It used to be a pretty big security hole that you had the telnet daemon running with a passwordless root login any time you had Developer Mode enabled.

I'd personally prefer that they added a proper SSH binary, but c'est la vie.

[DNSB]

Originally Posted by Cactus Chef

Adding a password to root is not a bad thing. It used to be a pretty big security hole that you had the telnet daemon running with a passwordless root login any time you had Developer Mode enabled.

The current firmware does not enable telnet with Developer Mode. You can still use telnet by enabling it from NickelMenu.

[lumping-sugar66]

Originally Posted by DNSB

As has been mentioned several times, root now has a password. However you can use admin/admin as the user/password.

Thanks, although I have read the thread I must have somehow I missed it.

[JSWolf]

I want to thank @Semwize for updating some of the offsets. It really fixes the patches.

[retro]

I upgraded my Libra2 and Claras about 3 weeks ago, then applied a few patches, 'Remove recommendations (row1col2) from home screen' was one of them. All worked as expected.

I never turn on wifi and connect, all the upgrades were done offline. Two days ago, I rebooted my Libra2 which I do once a week or so and it wasn't the first time since the upgrade. 'Recommendations' were back where I was used to seeing one of my collections on the home page.

Only on the Libra2, the Claras are still fine. I double checked the yaml files and installed the patches again. 'Recommendations' are still there.

Not earth shattering or anything, just weirdness. But I was wondering if changing the offset might fix it? I don't mind experimenting, but not sure which way to change the offset.

[JSWolf]

Originally Posted by retro

I upgraded my Libra2 and Claras about 3 weeks ago, then applied a few patches, 'Remove recommendations (row1col2) from home screen' was one of them. All worked as expected.

I never turn on wifi and connect, all the upgrades were done offline. Two days ago, I rebooted my Libra2 which I do once a week or so and it wasn't the first time since the upgrade. 'Recommendations' were back where I was used to seeing one of my collections on the home page.

Only on the Libra2, the Claras are still fine. I double checked the yaml files and installed the patches again. 'Recommendations' are still there.

Not earth shattering or anything, just weirdness. But I was wondering if changing the offset might fix it? I don't mind experimenting, but not sure which way to change the offset.

You could try applying the patches again and see how you get on.

The other thing, you don't need to reboot once a week. I don't and my Libra 2 is good to go. The last reboot was when I installed the patches for 4.38.23038.

[ghira]

I reboot when it says all my epubs are adobe protected etc. So a few times a year?

[retro]

I double checked the yaml files and installed the patches again. 'Recommendations' are still there.

Rebooting doesn't hurt anything and often helps.

[bohn]

how am I meant to patch a kobo libra 2 with 4.38.23038 ?

am I able to roll back to a previous to patch?

[bluepeter]

Originally Posted by bohn

how am I meant to patch a kobo libra 2 with 4.38.23038 ?

am I able to roll back to a previous to patch?

AIUI, you have two options.

1. Create patches for build 23038 firmware using the build 21908 patch software. Downside: not all patches will work, so you'll need to check the log file if it fails on your first attempt. This'll tell you which of the patches you want haven't worked, and you can try again without them. Or give up and try the other option.

2. Yes, you can roll back the firmware and apply patches appropriate to it. I've just taken my Libra H2O back to 4.38.21908, so I can't see why it won't work for a Libra 2. Downsides: (a) you won't benefit from the improvements in build 23038 (I forget what they are, but IIRC they were discussed upthread); (b) next time you sync your e-reader, it'll reinstall build 23038 firmware and you'll lose your patches.

In case you don't already know where to obtain earlier firmware and install it, head to https://pgaskin.net/KoboStuff/kobofirmware.html.

[EnterNameHere]

I assume that the other option (which is the one I've been taking so far) is not to upgrade until Patrick Gaskin releases the patches for 4.38.23038.

Does anybody know when/if this is likely to happen?

[Sirtel]

Originally Posted by EnterNameHere

I assume that the other option (which is the one I've been taking so far) is not to upgrade until Patrick Gaskin releases the patches for 4.38.23038.

Does anybody know when/if this is likely to happen?

No. He has said he is a bit busy at the moment, and some patches need extensive reworking, so it might take a while.

I'm also waiting for the patches before I update.

[icerom]

Originally Posted by JSWolf

It is nice to know that the database issue has been fixed. We can look forward to no more posts about a corrupted database from anyone with this firmware or later.

OTH After I updated to 4.38.23038 I have been unable to connect to Calibre. I get a "database disk image is malformed". I am currently restoring the db, we'll see if it fixes it.

Also, it appears my device has been deauthorized for ADE. Might be the two issues are interconnected, I dunno. But I wish I'd never updated.