Thread: Kobo Patcher
View Single Post
Old 10-03-2013, 10:23 PM   #232
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by parkher View Post
You could try downgrading from 2.8.1 to 2.8.1
What is so new and great in this new 2.8.1 (b2c05cda0e)?
And what this number b2c05cda0e actully stands for?
Not md5, not crc32, is it a build number?
Yes, it is a build number. What is displayed is the first 8 characters of the number. The fill number is in a file in the usr/local/Kobo directory.
Quote:
I see changes in 28 files and one new file added - a hyphenation dictionary for the Dutch language.
Kobo have stated that this version is to fix a problem with demo devices. That suggests there are no code changes that affect "normal" use. My guess it that they added the Dutch hyphenation dictionary as it would be a safe addition.
Quote:
Unfortunately, libnickel.so.1.0.0 has been changed too, its size is different:
old: 19,109,944 bytes
new: 19,074,964 bytes
So hex replacements may cause unpredictable effects.

But perhaps it is enough to replace just libnickel.so.1.0.0 file (with the one from the previous 2.8.1 firmware) and then you can apply the patch, because the patch changes only that one file.
This will probably work. It has been done before for other firmware versions. At the worst, you would need to do a factory reset afterwards
davidfor is offline   Reply With Quote