Musing on preventing Upgrades

PeterT · 12-21-2013, 10:26 PM

A thought just popped into my head....

Using the approach introduced by the fmon tool, it should be possible to prevent upgrades being installed to Kobo's. All that would be needed would be either a new customized version of fmon that watched for the creation / closing of the update files and then dropped them, or the use of the standard fmon with a script that gets invoked to drop the file.

Yes, updates would be still downloaded to the device, but, when the file(s) were closed, they would be deleted.

Thoughts?

tshering · 12-22-2013, 06:06 AM

Since fmon is usually started by on-animator.sh, and on-animator.sh started from rcS only after the update block is passed, one would have to start fmon another way.
It is easier, I think, to edit rcS to the effect, that it deletes the update files if it finds a KoboRoot.tgz, and runs the update script block, if it finds a xKoboRoot.tgz (in order to allow to install updates and applications using the update mechanism if one wishes).

Somehow related: I did a new version of my kobomenu and also of the sample application "start menu". It gives you the choice to select on start up, whether to install an update or to delete the update files. I will upload the new version after some more testing after the holidays.

PeterT · 12-22-2013, 07:22 AM

You're missing the point. Once the program IS running then the idea is that when ever upgrade.tgz is written too, created, closed (any file operation), the api in use by fmon is invoked,, so as long as this program has been launched, it would be monitoring for the upgrade files.

tshering · 12-22-2013, 07:55 AM

I am not sure whether my guess is correct, but here it goes:
While the reader is connected via usb, fmon does not see file opeations. So it cannot know that KoboRoot.tgz is beeing written to .kobo. The next file operation on KoboRoot.tgz. will happen after the next reboot, ...

PeterT · 12-22-2013, 09:56 AM

You're right. I had forgotten the dismount that had happened on USB connection. But still this should prevent over the air upgrades happening.

12-21-2013, 10:26 PM	#1
PeterT Grand Sorcerer Posts: 12,236 Karma: 74000000 Join Date: Nov 2007 Location: Toronto Device: Nexus 7, Clara, Touch, Tolino EPOS	Musing on preventing Upgrades A thought just popped into my head.... Using the approach introduced by the fmon tool, it should be possible to prevent upgrades being installed to Kobo's. All that would be needed would be either a new customized version of fmon that watched for the creation / closing of the update files and then dropped them, or the use of the standard fmon with a script that gets invoked to drop the file. Yes, updates would be still downloaded to the device, but, when the file(s) were closed, they would be deleted. Thoughts?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Musing on Apple 2013	frahse	Apple Devices	108	10-31-2013 06:37 PM
Musing on Apple September 2013	frahse	Apple Devices	144	10-04-2013 04:15 PM
Something is preventing custom upgrades on my jailbroken KPW 5.3.1	pirl8	Kindle Developer's Corner	6	02-26-2013 05:55 PM
I've been musing about tablets, the Fire and computers	KlondikeGeoff	Kindle Fire	35	09-15-2012 09:40 PM
Seriously thoughtful The Darkness of the Dreams - Musing on the music of Warren Zevon	Greg Anos	Lounge	1	05-15-2010 09:14 PM

12-22-2013, 06:06 AM	#2
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	Since fmon is usually started by on-animator.sh, and on-animator.sh started from rcS only after the update block is passed, one would have to start fmon another way. It is easier, I think, to edit rcS to the effect, that it deletes the update files if it finds a KoboRoot.tgz, and runs the update script block, if it finds a xKoboRoot.tgz (in order to allow to install updates and applications using the update mechanism if one wishes). Somehow related: I did a new version of my kobomenu and also of the sample application "start menu". It gives you the choice to select on start up, whether to install an update or to delete the update files. I will upload the new version after some more testing after the holidays.

12-22-2013, 07:22 AM	#3
PeterT Grand Sorcerer Posts: 12,236 Karma: 74000000 Join Date: Nov 2007 Location: Toronto Device: Nexus 7, Clara, Touch, Tolino EPOS	You're missing the point. Once the program IS running then the idea is that when ever upgrade.tgz is written too, created, closed (any file operation), the api in use by fmon is invoked,, so as long as this program has been launched, it would be monitoring for the upgrade files.

12-22-2013, 07:55 AM	#4
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	I am not sure whether my guess is correct, but here it goes: While the reader is connected via usb, fmon does not see file opeations. So it cannot know that KoboRoot.tgz is beeing written to .kobo. The next file operation on KoboRoot.tgz. will happen after the next reboot, ...

12-22-2013, 09:56 AM	#5
PeterT Grand Sorcerer Posts: 12,236 Karma: 74000000 Join Date: Nov 2007 Location: Toronto Device: Nexus 7, Clara, Touch, Tolino EPOS	You're right. I had forgotten the dismount that had happened on USB connection. But still this should prevent over the air upgrades happening.

Advert

Advert