Instructions for patching firmware 3.19.5761

[oren64]

Originally Posted by boriar

Edit: @oren64

Apart from uncomment line in the version I posted before, it seems not to have any difference and produced the same error . Is it supposed that I can not uncomment it?

I test it and it works okay, are sure you used the Multi-version patch: 3.17.0-3.19.5761, and copy the patch to libnickel.so.1.0.0.patch.

Can you please add the run erorr.

[boriar]

Originally Posted by oren64

I test it and it works okay, are sure you used the Multi-version patch: 3.17.0-3.19.5761, and copy the patch to libnickel.so.1.0.0.patch.

Can you please add the run erorr.

Yes. Here is my only change. I delete the red #:

#<<Bottom margin top container >>
# Touch
#replace_string = 0050, `qproperty-bottomMargin: 10;`, `qproperty-bottomMargin: 05;`
# Glo\Aura
#replace_string = 00ED, `qproperty-bottomMargin:15;`, `qproperty-bottomMargin:10;`
# Aura HD\H2O & Glo HD 
#replace_string = 0188, `qproperty-bottomMargin: 20;`, `qproperty-bottomMargin: 15;`

If I left the #, all go well.

EDIT: Hi! Problem solve with your patch. The error come from the original libnickel.so.1.0.0 that was corrupted. Althought I still have problem with the other patch
Thanks for your help!

[jackie_w]

Originally Posted by boriar

oren64 said here that for that FW is in libnickel.so.1.0.0.patch. But thanks for your answer.

What exactly is your point?

oren64's reply about the patch 'Increasing The View Details Container' is irrelevant to the patch 'Custom Header menubar - reduce height by 33%'.

In fw 3.19.5761 the 'View Details' patch belongs in libnickel.so.1.0.0.patch but 'Custom Header menubar' belongs in nickel.patch. If you are trying to run either of them from the wrong place it's not surprising you're having trouble.

Due to underlying Kobo changes, from fw 4.x.x onwards both patches belong in nickel.patch. Both of my 'Custom Header menubar' patches (33% and 50%) have been rewritten to accommodate fw 4.x.x and are now included in GeoffR's standard patch package.

[JSWolf]

One advantage to the new firmware is that these patches that you are trying to get working are already in the correct place in the proper patch file.

[boriar]

Originally Posted by jackie_w

What exactly is your point?

oren64's reply about the patch 'Increasing The View Details Container' is irrelevant to the patch 'Custom Header menubar - reduce height by 33%'.

In fw 3.19.5761 the 'View Details' patch belongs in libnickel.so.1.0.0.patch but 'Custom Header menubar' belongs in nickel.patch. If you are trying to run either of them from the wrong place it's not surprising you're having trouble.

Due to underlying Kobo changes, from fw 4.x.x onwards both patches belong in nickel.patch. Both of my 'Custom Header menubar' patches (33% and 50%) have been rewritten to accommodate fw 4.x.x and are now included in GeoffR's standard patch package.

Sorry! My mistake. I missreading your post. Trying it in nickel and all perfect.

[mobama]

I'm on Linux. I have been following these instructions all day a bunch of times now. It seems to run smooth all the way to the end, but the problem is that a KoboRoot.tgz and a 3.19.5761_target/ directory are not happening. Either no KoboRoot.tgz is generated or it gets lost somewhere where I don't know to look.

The last lines in the terminal are
Ignoring disabled patch `KePub text-rendering options`

Wrote 14928256 bytes to output file '/tmp/patch32lsb_QGDIvGqS/patched/./usr/local/Kobo/libnickel.so.1.0.0'
Read 7437684 bytes from input file '/tmp/patch32lsb_QGDIvGqS/original/./usr/local/Kobo/librmsdk.so.1.0.0'
Applied patch `Fix page breaks bug`
tools/patch32lsb-x86_64-Linux: line 42 in '3.19.5761_source/librmsdk.so.1.0.0.patch': find_base_address string not found.
Cleaning up /tmp/patch32lsb_QGDIvGqS

Can somebody help out or is this thread too outdated now?

[jackie_w]

Originally Posted by mobama

I'm on Linux. I have been following these instructions all day a bunch of times now. It seems to run smooth all the way to the end, but the problem is that a KoboRoot.tgz and a 3.19.5761_target/ directory are not happening. Either no KoboRoot.tgz is generated or it gets lost somewhere where I don't know to look.

The last lines in the terminal are
Ignoring disabled patch `KePub text-rendering options`

Can somebody help out or is this thread too outdated now?

The patcher is failing on one of your enabled patches in file librmsdk.so.1.0.0.patch. That's why you're not getting any output.

line 42 in '3.19.5761_source/librmsdk.so.1.0.0.patch': find_base_address string not found

It looks like `Fix page breaks bug` ran OK but the next enabled patch didn't.
Was it `Default ePub monospace font (Courier)` by any chance.

[mobama]

Originally Posted by jackie_w

It looks like `Fix page breaks bug` ran OK but the next enabled patch didn't.
Was it `Default ePub monospace font (Courier)` by any chance.

Yes, you are right. I think I made some changes to it that were unpalatable (instead of CourierStd I tried to point to Courier Prime).

I got a KoboRoot.tgz by enabling that patch without other modifications in the patch.

[mortimer7]

hi, i have last firmware on my Aura 6", can i downgrade to this version without lost my book/underlining/annotations/collections? i have a KoboReader.sqlite of 1 month ago, can i use it?

[davidfor]

Originally Posted by mortimer7

hi, i have last firmware on my Aura 6", can i downgrade to this version without lost my book/underlining/annotations/collections? i have a KoboReader.sqlite of 1 month ago, can i use it?

Why don't you try it and see? It won't damage the device. If it fails, you will probably just be forced to sign in to you Kobo account again. At the worst, it will be a factory reset. The database structure is backwardly compatible, but there have been some changes in how some data is stored. These are mainly in the way the stats are stored. I'd expect you will loose all the reading stats, but you should keep the reading status for books.

If your database backup is from 3.19.5761, you can try restoring that after doing the firmware downgrade. If you do it before, it will be updated to the latest database version. After restoring the database, shutdown the device as quickly as possible. Then it will be reread during the start-up.

What I suggest doing is taking a copy of all the files on the books partition before trying. If things go wrong, you can restore this and try again. If your database is from

[mortimer7]

I did it and it worked!
I have simply copied the firmware 3.19 on ./kobo directory without factory reset and i haven't lost reading stats/annotations/collections :-)