Instructions for patching firmware 3.19.5761

[PeterT]

If you upgrade f/w you will have to repatch, and that can only happen when the patch gurus have created the patches for the new f/w. Then there is the possibility that a patch you love might not be possible in the new f/w.

[GeoffR]

Originally Posted by superjoefly

I only have one more question at the moment, and that is...do updates to the Kobo firmware interrupt the patches?

Just to expand a bit on what PeterT said: when you upgrade to a new firmware the patches will disappear, but some of the settings you changed using the patches might persist until you change them again.

For example, if you set the number of page turns per refresh to 10 using the `Custom page refresh options...` patch then the device will store that value in its configuration file and keep using it after the patch has gone, but if you try to change it again before you have patched the new firmware then the settings menu will only give you the options 1-6.

[rudgas]

Is it possible to add "sort by Series" inside a collection? I'm not entirely sure how calibre generates the little series label.
To clarify I'm talking about the subtitle thats added when in calibre a series is set. For example: Harry Potter and the Chamber of Secrets | Harry Potter - 2 | J.K. Rowling

[GeoffR]

Originally Posted by rudgas

Is it possible to add "sort by Series" inside a collection? I'm not entirely sure how calibre generates the little series label.
To clarify I'm talking about the subtitle thats added when in calibre a series is set. For example: Harry Potter and the Chamber of Secrets | Harry Potter - 2 | J.K. Rowling

No, I'd like to be able to sort on the series/index fields myself and was very disappointed when Kobo removed this feature, but no patch has been found to replace it so far.

I think the only work-around is to add the series information to the title or author fields and sort on those. Personally though I think that is worse than just leaving them unsorted. so I use search to get a list of all books in a series (which is faster than using collections anyway) and just live with them being out of order.

[rudgas]

Thanks for the quick reply! Then I'll hope that maybe a future firmware update will include this at some point.

Sent from my GT-I9195 using Tapatalk

[superjoefly]

Hi there!

I'm currently running GalliumOS 2.0 (linux) and patching for Kobo Glo HD.

In # 4 of instructions for patching it says "For Linux/Mac open a terminal, change to the patch_kobo_3195761/ subdirectory, and run ./3.19.5761.sh from the command line."

I'm rather new to linux so I could use some help with this.

How do I "change to the patch_kobo_3195761/ subdirectory" in terminal? Can I just drag and drop the .sh file into the terminal?

Also, how do I run the .sh file in the command line? Once I drag and drop it into the terminal, do I just hit enter, or do I have to add something to the command?

(UPDATE): I drag and dropped the .sh file into Xfce, and hit enter, which resulted in several lines of text in mousepad that ended with:

echo "Creating KoboRoot.tgz ..."
rm -rf $TARGET_DIR
mkdir -p $TARGET_DIR
tar cvzf $TARGET_DIR/KoboRoot.tgz --directory=$NEW $FILES_TO_PATCH

It seems the KoboRoot.tgz was created, however, I cannot find the 3.19.5761_target/ subdirectory that contains the new .tgz file.

Do I have to save this in mousepad in order to create the tgz file? If it was already created, where was it created...how do I locate it?

Thanks :-)

[GeoffR]

Originally Posted by superjoefly

I'm currently running GalliumOS 2.0 (linux) and patching for Kobo Glo HD.

In # 4 of instructions for patching it says "For Linux/Mac open a terminal, change to the patch_kobo_3195761/ subdirectory, and run ./3.19.5761.sh from the command line."

I'm rather new to linux so I could use some help with this.

It might work just to double-click on the 3.19.5761.sh script from the desktop, that works on my desktop (Gnome running on Debian Wheezy), but it might not work on all desktops and the problem is that if there is an error you won't see the error messages. The instructions for running from the command line should work on all Linux setups.

Somewhere there will be an application called Terminal or Term or Shell or something like that, probably with a picture of a box with a command prompt inside. Run that to open the command-line terminal.

In the command-line terminal, to change directory use the cd command. You need to enter the path to the place you unzipped the patch_kobo_3.19.5761.zip, if that was in your home directory then just type:

cd ~/patch_kobo_3195761

(Edit: ~ is a way to refer to your home directory. E.g. my home directory is /home/geoff so instead of typing cd /home/geoff/patch_kobo_3196761 I just type ~/patch_kobo_3195761)

Then to run the 3.19.5761.sh from the command line, just type:

./3.19.5761.sh

(Edit: . refers to the current directory. In Linux for the command-line shell does not normally look in the current directory for programs, so you have to specify it explicitly as ./3.19.5761.sh instead of just typing 3.19.5761.sh)

[ICDeadPpl]

A suggestion: Would it be possible to list the patch names in the beginning of each patch file. with the option of enabling/disabling them there?
These patch files are quite long, so it would save a lot of scrolling when finding the patches to enable.
Something like this:
Disable_reading_footer = yes
Custom_reading_footer_style = yes

[GeoffR]

Originally Posted by ICDeadPpl

A suggestion: Would it be possible to list the patch names in the beginning of each patch file. with the option of enabling/disabling them there?
These patch files are quite long, so it would save a lot of scrolling when finding the patches to enable.
Something like this:
Disable_reading_footer = yes
Custom_reading_footer_style = yes

What I do is use the text editor's search next function, and search for patch_enable. That quickly takes me to the beginning of each patch in turn.

Since some of the patches have warnings that should be read and customisation options to set, I am a bit wary about making it easy to enable patches without seeing those.

[superjoefly]

GeoffR, I did what you said and it opened in Mousepad with the following text:

#!/bin/sh

FIRMWARE_VERSION=3.19.5761

SOURCE_DIR=${FIRMWARE_VERSION}_source
TARGET_DIR=${FIRMWARE_VERSION}_target

KOBO_FIRMWARE=$SOURCE_DIR/kobo-update-$FIRMWARE_VERSION.zip

PATCH32LSB_SRC=tools/patch32lsb.c
PATCH32LSB_BIN=tools/patch32lsb
STAT="stat -c %a"

set -e

FILES_TO_PATCH=""
for F in $SOURCE_DIR/*.patch; do
FILES_TO_PATCH="$FILES_TO_PATCH ./usr/local/Kobo/`basename $F .patch`";
done

case `uname -s` in
Darwin)
PATCH32LSB_BIN=tools/patch32lsb-Darwin
STAT="stat -f %Lp"
;;
Linux)
case `uname -m` in
i?86)
PATCH32LSB_BIN=tools/patch32lsb-i386-Linux
;;
x86_64)
PATCH32LSB_BIN=tools/patch32lsb-x86_64-Linux
;;
esac
STAT="stat -c %a"
;;
esac

SCRATCH=`mktemp -d -t patch32lsb_XXXXXXXX`
trap 'echo "Cleaning up $SCRATCH"; rm -r $SCRATCH' EXIT

OLD=$SCRATCH/original; mkdir $OLD
NEW=$SCRATCH/patched; mkdir $NEW

echo "Extracting files to patch from $KOBO_FIRMWARE ..."
unzip -p $KOBO_FIRMWARE KoboRoot.tgz | tar xvz --directory=$OLD $FILES_TO_PATCH

for F in $FILES_TO_PATCH; do
mkdir -p `dirname $NEW/$F`;
$PATCH32LSB_BIN -p $SOURCE_DIR/`basename $F`.patch -i $OLD/$F -o $NEW/$F;
chmod `$STAT $OLD/$F` $NEW/$F;
done

echo "Creating KoboRoot.tgz ..."
rm -rf $TARGET_DIR
mkdir -p $TARGET_DIR
tar cvzf $TARGET_DIR/KoboRoot.tgz --directory=$NEW $FILES_TO_PATCH



Is it supposed to open in Mousepad like this?


"5. If there were no errors, copy the resulting KoboRoot.tgz from the 3.19.5761_target/ subdirectory to the .kobo directory on your ereader."


I can't find the KoboRoot.tgz or the 3.19.5761_target/subdirectory...where is it located?


Thanks again for your help :-)

[GeoffR]

Originally Posted by superjoefly

[B]
Is it supposed to open in Mousepad like this?

No. I guess mousepad is a text editor? You shouldn't open 3.19.5761.sh in a text editor. If it opened in mousepad when you double-clicked on 3.19.5761.sh then something is wrong with the your file associations, so you'll have to follow the instructions and run it from the command line.

I can't find the KoboRoot.tgz or the 3.19.5761_target/subdirectory...where is it located?

You haven't run 3.19.5761.sh yet, you just opened it in something called mousepad.

You might want to consider spending a bit more time getting familiar with your Linux system before you attempt patching though, it is hard to know where to begin explaining things if you don't know how to run a program.


Edit: As an example, here is the detailed sequence of commands I would use, after downloading patch_kobo_3195761.zip and kobo-update-3.19.5761.zip using the web browser, and opening a command-line terminal. The numbers in [brackets] are the corresponding steps in the instructions in this thread. The pathnames might be different on your system, you will probably use a different text editor (mousepad instead of emacs maybe?), and you might do some of the steps from the desktop instead of from the command line. All Linux systems are different, but from the command line they are usually quite similar while from the desktop they can be totally unrecognisable.

[1] unzip ~/Downloads/patch_kobo_3195761.zip
[4] cd patch_kobo_3195761/
[2] cp ~/Downloads/kobo-update-3.19.5761.zip 3.19.5761_source/
[3] emacs 3.19.5761_source/*.patch
[4] ./3.19.5761.sh
[5] cp 3.19.5761_target/KoboRoot.tgz /media/KOBOeReader/.kobo/
[6] eject /media/KOBOeReader

[JSWolf]

Mousepad is a text editor for Linux.

https://community.linuxmint.com/software/view/mousepad

[superjoefly]

I tried changing the file association and also running the .sh file using different terminals to no avail. Sometimes I get the error "unexpected end of file" and sometimes nothing happens at all, depending on which terminal I'm using. Prior to this, I've had no problems using linux...so this has been frustrating...I'll probably just do the patch using windows...lol...thanks for your help :-)

EDIT: I finally got it to work in the linux terminal!

I don't know what I did differently, but the KoboRoot.tgz file was created and as far as I can tell, there were no errors.

EDIT 2: I completed the patch and it was successful.

Thanks for your help :-)

[PeterT]

@geoffr in your step by step instructions are you missing a chmod +x on the shell script?

[GeoffR]

Originally Posted by PeterT

@geoffr in your step by step instructions are you missing a chmod +x on the shell script?

No, 3.19.5761.sh is already executable.