Firmware 4.45.23684

[rantanplan]

Originally Posted by Sirtel

You can only downgrade to the version your device originally shipped with. If it was 5.15, then you can't downgrade any lower than that.

That’s not true and you can downgrade to a 4.45 version with no problem.

Here’s everything you need:

https://github.com/notmarek/KoboTolinoFindings

[JSWolf]

the patches will be available later today.

[jlinear]

Originally Posted by svetlyo

Kobo Clara Color - upgraded firmware yesterday and now Calibre sideloads get stuck at 6% even after Factory reset. Can I use old manual backup, or downgrade firmware, or any way to fix this?[/URL]

I wonder what it is about 6%? My Aura One would constantly get stuck on exactly 6% when sideloading a few years ago. I successfully installed a previous firmware version to rectify the problem until a newer firmware version fixed it.

[Falafelteller]

Line Spacing patch produces cut off lines on some settings, is this normal?

[DNSB]

Originally Posted by jlinear

I wonder what it is about 6%? My Aura One would constantly get stuck on exactly 6% when sideloading a few years ago. I successfully installed a previous firmware version to rectify the problem until a newer firmware version fixed it.

The actual book import progress starts at 6% and ends at 94%. Other housekeeping tasks take up the first and last bits.

[jlinear]

Originally Posted by DNSB

The actual book import progress starts at 6% and ends at 94%. Other housekeeping tasks take up the first and last bits.

Thanks. I didn’t know that.

[JSWolf]

The patches are now available at https://www.mobileread.com/forums/sh....php?p=4580999.

[McGlear]

Originally Posted by rantanplan

That’s not true and you can downgrade to a 4.45 version with no problem.

Here’s everything you need:

https://github.com/notmarek/KoboTolinoFindings

At least for me, the downgrade isn't working on a Tolino Vision Color (the modified tar for activating devmode works fine, but using the downgrade one does not take me back beyond 5.10 - the same version I get to when doing a manual reset). I can get all the way down to 5.1.xx by using the other firmware tarballs provided in the repo. But nothing I tried got me to a 4.xx firmware. And while on a 5.xx, the Kobo / converted Tolino obviously doesn't want to use any provided KoboRoot.tgz packages, so having access to 4.xx firmware files in that old update format doesn't help...

So Sirtel might have a point, at least for some users/devices?

[rantanplan]

You don’t need a tar file to downgrade. After enabling dev mode and switching to Kobo, you’ll find an option to disable barrier free reading, which will then automatically download the 4.45… firmware.

[McGlear]

Originally Posted by rantanplan

You don’t need a tar file to downgrade. After enabling dev mode and switching to Kobo, you’ll find an option to disable barrier free reading, which will then automatically download the 4.45… firmware.

While it doesn't really belong in this thread (maybe the conversation can be split off into an individual thread by a mod?), I thought I'd share my experience and what worked for me in the end:

Following the steps in the KoboTolinoFindings repo, I was not able to downgrade to a 4.x firmware. Hitting "Revert" led to either:

1. Appearance of the update screen, a reset of the device and then a boot into 5.10 firmware (!) or ...
2. ... nothing. (The device would display the home screen and the syncing window in the top right, but not download or apply an "Update" or change in any other visible way)

The ´´´DowngradePackages/update.tar´´´ provided in the repo would start an update process, but the device would eventually boot into the same firmware version that it had before.

In the end, I decided to apply the recovery version of the 5.10.225420 firmware, provided in the repo as a tarball as well. After doing that, the "Revert" function did what I expected; a 4.38 (?) FW was downloaded and installed, on the next boot I was asked whether I wanted to install "Accessibility features" (which I declined, of course) and after the following initial setup I was able to do an OTA update using the built-in Update check, so that I'm now on 4.45.23684.

[JSWolf]

Originally Posted by Irrevanent

I have no idea what I'm doing but I reverse-engineered a fix for the "Both page turn buttons go next" patch that seems to be working on my Libra Colour-

Both page turn buttons go next:
  - Enabled: no
  - Description: Make both page turn buttons on the Libra Colour go next in the reader.
  - ReplaceBytes:
      Base:          "ReadingView::keyPressEvent(QKeyEvent*)"
      Offset: 60
      Find:    [0x68, 0xB9]
      Replace: [0x0D, 0xE0]

The above is from a post in the 4.45.23684 thread. I tried it and it applies on 4.38.23684. However, I'm not currently running this firmware. Can someone with a Kobo with page turn buttons please est this patch? I can supply the pages if need be.

[slycat]

Originally Posted by JSWolf

Can someone with a Kobo with page turn buttons please est this patch? I can supply the pages if need be.

Patched 4.38.23684 successfully with changes
Testing on a Libra 2, works as intended! HUZZAH!
Will continue using device to see if it I find any negative affects but it does what it says it does


Sidenote: the Key Tester ("Physical Keys" option in developer mode) still lists each button press as down and up, not both one or the other. Using the keys in any other scenario, such as scrolling the menu, still operate in up and down. So only the reader function is effected with this revised patch.

[JSWolf]

Originally Posted by slycat

Patched 4.38.23684 successfully with changes
Testing on a Libra 2, works as intended! HUZZAH!
Will continue using device to see if it I find any negative affects but it does what it says it does


Sidenote: the Key Tester ("Physical Keys" option in developer mode) still lists each button press as down and up, not both one or the other. Using the keys in any other scenario, such as scrolling the menu, still operate in up and down. So only the reader function is effected with this revised patch.

Thanks for testing this patch. Does the patch work for both ePub and KePub? Once I know this, I can release an updated set of patches.