Updates for newer firmware versions

[johnlago]

There have been a number of official Kobo firmware updates since the last modified build in this project. What's involved in generating an updated KoboRoot.tg.gz? The guide has a "TBD" for this portion of the setup, and I suspect there's something more than just telnet to change - this doesn't seem to work properly with a rooted Kobo on 4.38.21908.

Thanks for building this - I'm excited to use Omnivore on my Kobo!

[Podginator]

Hey! I will make some effort to update this section today. It is not a lengthy process, I just wanted to make sure it was automated.

[johnlago]

Hi! Anything we can do to help with this? If you point me in the right direction, I'd be happy to take a stab at documenting the process or generating new files.

[Podginator]

Sorry, I have been very bad at responding to this.

For updated versions you can do this

Download the update tar.gz
extract it

perl -pi -e 's/https:\/\/getpocket.com/http:\/\/fckpocket.com/' ./KoboRoot/usr/local/Kobo/libnickel.so.1.0.0 && perl -pi -e 's/https:\/\/text.getpocket.com/http:\/\/text.fckpocket.com/' ./KoboRoot/usr/local/Kobo/libnickel.so.1.0.0

Extract the tar.gz that is in this repo, and replace the usr/local/Kobo/libnickel.so.1.0.0 with the one you've just edited.
Repackage the tar.gz file.
Update it using the SD Card by doing the following: Place the new tar.gz inside the .kobo directory on the Kobo

Sorry this is not more elegant a solution, I've been swamped recently.

[Podginator]

Note, whilst I haven't tried this, it is probably possible to achieve the same using SSH/Telnet and running those commands. Or doing a scp of the libnickel.so.1.0.0, patching it on your machine, and then scping it back. Which is probably a less tedious process when an update happens.

[johnlago]

Thanks for writing that out! No dice, unfortunately. I wonder if something more major changed in the most recent firmware update, since Pocket now uses Mozilla's oAuth to sign into the real Pocket. I may try downgrading to see if that does the trick.

[Podginator]

I hope to get some time in the near future to be able to look at this more closely.

One approach I wanted to do was to intercept the URL by using a hook on the OS level. Rather than having to patch the lib - which ultimately gets overridden each time. I had a look at this a while ago but I never got it off the ground.

[Podginator]

But with that approach you'd be able to actually host this instead of just using it locally.

[Podginator]

Hey!

I have changed the method in which this works. It no longer patches libnickel (which would get updated every single firmware update) but instead hooks into the webrequest method.

This has two benefits:

1. You can now run it on any firmware version, without having to worry about updates. The steps for setting this up largely stay the same. Change /etc/hosts etc
2. You can actually HOST a version of this now, on either Vercel, or Lambda, or any platform of your choice. You can them modify the .cc file and follow the instructions in the guide to pull from your hosted version.

I spent hours getting stuck because I got one little thing wrong and kept causing a Segfault. I love C.