No, KSM does not modify the boot sector at all. The most significant modification is of the rcS file (/mnt/etc/init.d/rcS). In the original version the script of the rcS file calls at a certain point nickel (the kobo reader GUI). The modified script branches to KSM instead. All that is needed to restore the original behaviour of the device (as far as KSM is concerned) is to replace the modified rcS by the rcS that came with the FW you are running now.
The only other system file that KSM modifies is /usr/local/Kobo/udev/usb. But this is of minor or no consequence in more recent FWs.
Future versions of KSM will also modify /usr/local/Kobo/udev/sd.
"Restoring factory defaults" will leave no trace of KSM. There is no need to uninstall KSM before doing the factory reset.
Quote:
Originally Posted by tigran
tshering,
Can you please explain the technical side of Kobo Start Menu, i.e. exactly how it works. For example, do you modify the boot sector or not? I am asking because fsck.vfat reports that the boot sector differs from all the backup copies and I am not sure if this is a corruption or expected behaviour as required by your program. Also, knowing what exactly is going on helps in situations with fs corruptions --- should I simply restore the backup partition to the first one and reformat the vfat partition (by using "restoring factory defaults" function in Nickel, or manually) or do I need to do some kind of "uninstall" of Kobo Start Menu first? I.e. if you modify the boot sector then I must do uninstall... Please clarify these things. Thank you very much in advance!
UPDATE: I looked at what's inside KoboRoot.tgz and got an idea of how it works. I don't see anywhere that you modify the boot sector, but still your confirmation (or otherwise) of this fact would be appreciated. Thank you.
|