View Single Post
Old 01-03-2015, 05:48 PM   #4
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
Sorry I haven't go to testing this yet. I don't have any experience with cross-compiling to run on Kobo devices, do you have a patch32lsb executable available? Edit: I was looking at the github ink and missed the attachment.

What happens when the firmware is updated, does the autopatcher need to be re-installed?

Does it handle the situation where a firmware update only changes some files and not others? For example the librmsdk.so.1.0.0 is sometimes identical from one firmware version to the next.

From what I understand the device needs to reboot twice after changing a patch to install the new patch?

There are some definate advantages to doing it this way: you don't need to run the patching program (kpg.exe or patch32lsb) on an external computer, and the files to be patched are taken directly from the device instead of extracted from a downloaded firmware archive.

For those already used to patching from an external computer there probably isn't any incentive to switch to this method, but perhaps those who haven't patched before will find this method easier.

Last edited by GeoffR; 01-03-2015 at 06:33 PM. Reason: Now I see the attachment ...
GeoffR is offline   Reply With Quote