Upgrading Kobo OS, what impact does it have on KOReader?

twowheels · 11-11-2020, 06:53 PM

I installed KOReader w/ the simple installer that installs KOReader and launcher all at once, and haven't used the built-in reader since. I see that there's a new Kobo OS update, which I probably don't care about, but it might update itself soon, so before that happens I thought that I should check to see if there's anything that I need to do to ensure that I don't lose my reading statistics, progress, etc. I assume that these are stored in the normal user-space that isn't overwritten by the Kobo OS installer, but would like to confirm.

Once the Kobo OS updates, I'm guessing that I need to re-install KOReader. I assume that I can just use the same install script. Anything else that I need to be aware of?

NiLuJe · 11-11-2020, 07:01 PM

The only thing that'll be disabled by the FW update is KFMon, which means that you won't be able to *launch* KOReader without reinstalling that (either standalone, or via the OCP. Note that the OCP install script can handle KFMon's standalone package just fine, if you want to save a bit of time).

Everything else is completely orthogonal to the official FW, and is perfectly safe as long as you don't factory reset.

(NickelMenu will survive the update, so, another approach is to tweak the NM configs installed by the OCP to bypass KFMon and go directly through NM. That's already in there almost ready to use, everything's just commented out).

twowheels · 11-12-2020, 03:23 AM

Thanks, that's what I suspected, but it's nice to have it confirmed.

Jellby · 11-12-2020, 04:22 AM

Just in case, make sure to have a backup of your koreader folder (or the whole kobo drive)

NiLuJe · 11-12-2020, 10:34 AM

I've got a quick'n dirty backup script here. Which, granted, only helps you if you have shell access

.

twowheels · 11-12-2020, 04:43 PM

Shell access? I wouldn't have it any other way!

(I spend the vast majority of my day at a bash prompt, vim, gdb, etc...)

Thanks for the pointer, I'll check it out.

steveparry · 11-20-2020, 05:02 PM

I have just powered up my Kobo Libra for the first time in a few weeks. It hasNickel menu/Koreader/plato installed. When the Libra started up it updated the Kobo OS... There was a quick flash of dialogue box saying something about something then it started up properly. Now when I touch the Nickel Menu icon a box comes up saying "Generator error". What should I do? I'm not a programmer like most others in this forum seem to be. And I remember it was a royal pain for me to install it via my Mac - we're used to a graphical user interface. Should I try to install it all over again?

NiLuJe · 11-20-2020, 05:25 PM

@steveparry: Yep, the "Generator error" menu entry is simply the visual effect on NickelMenu of KFMon having gone MIA after the update

.

twowheels · 11-20-2020, 05:25 PM

I had the same exact error, and just followed the install instructions and unzipped the package on my Kobo again and it re-installed itself and worked perfectly, without any data loss.

The one-click installer should also do the same, but easier.

steveparry · 11-20-2020, 05:30 PM

Yes! I re-downloaded the install script and the new package and installed it. The Libra has now rebooted and Plato and Koreader appear working OK. Thank you.

sladflob · 11-22-2020, 08:56 PM

So the last couple of Kobo firmware updates have installed themselves and overwritten the ExcludeSyncFolders setting in eReader.conf. Has this always been the case or that something new? I think in the past I've either flashed the firmware myself or used the script which restores that setting, but recently I've left the wifi on after using Nickel to read Pocket articles and it's caught me out by updating itself.

NiLuJe · 11-22-2020, 09:26 PM

@sladflob: Never seen it happen myself.

sladflob · 11-22-2020, 10:55 PM

Quote:

Originally Posted by NiLuJe

@sladflob: Never seen it happen myself.

That's odd. What's worse is that when I add the line back in and unplug it it proceeds to delete all the icons from the KOReader install, so I have to copy them in again.

NiLuJe · 11-23-2020, 09:30 AM

@sladflob: That, on the other hand, is the expected behavior when the config entry has been added too late

.

sladflob · 11-23-2020, 05:26 PM

Quote:

Originally Posted by NiLuJe

@sladflob: That, on the other hand, is the expected behavior when the config entry has been added too late

.

Yes, but I don't have much choice once it's automatically updated. It's really annoying, especially with kobo updates happening every week or so these days. I'll try installing the next one manually and see what happens.

Sent from my SM-T720 using Tapatalk

11-11-2020, 06:53 PM	#1
twowheels Wizard Posts: 1,853 Karma: 13432974 Join Date: Nov 2010 Device: Kobo Clara HD, iPad Pro 10", iPhone 15 Pro, Boox Note Max	Upgrading Kobo OS, what impact does it have on KOReader? I installed KOReader w/ the simple installer that installs KOReader and launcher all at once, and haven't used the built-in reader since. I see that there's a new Kobo OS update, which I probably don't care about, but it might update itself soon, so before that happens I thought that I should check to see if there's anything that I need to do to ensure that I don't lose my reading statistics, progress, etc. I assume that these are stored in the normal user-space that isn't overwritten by the Kobo OS installer, but would like to confirm. Once the Kobo OS updates, I'm guessing that I need to re-install KOReader. I assume that I can just use the same install script. Anything else that I need to be aware of?

11-11-2020, 07:01 PM	#2
NiLuJe BLAM! Posts: 13,506 Karma: 26047190 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	The only thing that'll be disabled by the FW update is KFMon, which means that you won't be able to launch KOReader without reinstalling that (either standalone, or via the OCP. Note that the OCP install script can handle KFMon's standalone package just fine, if you want to save a bit of time). Everything else is completely orthogonal to the official FW, and is perfectly safe as long as you don't factory reset. (NickelMenu will survive the update, so, another approach is to tweak the NM configs installed by the OCP to bypass KFMon and go directly through NM. That's already in there almost ready to use, everything's just commented out). Last edited by NiLuJe; 11-11-2020 at 07:04 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Upgrading from Kobo Touch	Katel	Kobo Reader	13	10-23-2017 05:13 AM
Upgrading KOReader	chromeuser	KOReader	6	06-01-2017 12:56 PM
Upgrading from nook to kobo. Please help.	tomtin	Kobo Reader	33	12-09-2014 04:47 AM
upgrading from a kobo glo.	mystika1	Which one should I buy?	2	02-17-2014 06:16 AM
upgrading kobo wifi	leaperk	Kobo Reader	4	06-09-2011 03:46 PM

11-12-2020, 03:23 AM	#3
twowheels Wizard Posts: 1,853 Karma: 13432974 Join Date: Nov 2010 Device: Kobo Clara HD, iPad Pro 10", iPhone 15 Pro, Boox Note Max	Thanks, that's what I suspected, but it's nice to have it confirmed.

11-12-2020, 04:22 AM	#4
Jellby frumious Bandersnatch Posts: 7,543 Karma: 19001583 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	Just in case, make sure to have a backup of your koreader folder (or the whole kobo drive)

11-12-2020, 10:34 AM	#5
NiLuJe BLAM! Posts: 13,506 Karma: 26047190 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	I've got a quick'n dirty backup script here. Which, granted, only helps you if you have shell access .

11-12-2020, 04:43 PM	#6
twowheels Wizard Posts: 1,853 Karma: 13432974 Join Date: Nov 2010 Device: Kobo Clara HD, iPad Pro 10", iPhone 15 Pro, Boox Note Max	Shell access? I wouldn't have it any other way! (I spend the vast majority of my day at a bash prompt, vim, gdb, etc...) Thanks for the pointer, I'll check it out.

11-20-2020, 05:02 PM	#7
steveparry Connoisseur Posts: 81 Karma: 513524 Join Date: Dec 2019 Device: none	I have just powered up my Kobo Libra for the first time in a few weeks. It hasNickel menu/Koreader/plato installed. When the Libra started up it updated the Kobo OS... There was a quick flash of dialogue box saying something about something then it started up properly. Now when I touch the Nickel Menu icon a box comes up saying "Generator error". What should I do? I'm not a programmer like most others in this forum seem to be. And I remember it was a royal pain for me to install it via my Mac - we're used to a graphical user interface. Should I try to install it all over again?

11-20-2020, 05:25 PM	#8
NiLuJe BLAM! Posts: 13,506 Karma: 26047190 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@steveparry: Yep, the "Generator error" menu entry is simply the visual effect on NickelMenu of KFMon having gone MIA after the update .

11-20-2020, 05:30 PM	#10
steveparry Connoisseur Posts: 81 Karma: 513524 Join Date: Dec 2019 Device: none	Yes! I re-downloaded the install script and the new package and installed it. The Libra has now rebooted and Plato and Koreader appear working OK. Thank you.

11-22-2020, 08:56 PM	#11
sladflob Connoisseur Posts: 63 Karma: 10 Join Date: Feb 2013 Device: Kobo Touch, Aura One	So the last couple of Kobo firmware updates have installed themselves and overwritten the ExcludeSyncFolders setting in eReader.conf. Has this always been the case or that something new? I think in the past I've either flashed the firmware myself or used the script which restores that setting, but recently I've left the wifi on after using Nickel to read Pocket articles and it's caught me out by updating itself.

11-22-2020, 09:26 PM	#12
NiLuJe BLAM! Posts: 13,506 Karma: 26047190 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@sladflob: Never seen it happen myself.

11-23-2020, 09:30 AM	#14
NiLuJe BLAM! Posts: 13,506 Karma: 26047190 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@sladflob: That, on the other hand, is the expected behavior when the config entry has been added too late .

Advert

Advert