MobileRead Forums - View Single Post

thatworkshop · 08-15-2015, 03:34 PM

JBPatch in nature is something like Xposed for Android OS. In Xposed, we have a fail-proof way to disable Xposed patches (called modules) if things go bad and system fails to boot. At boot time, user would press certain buttons a few times as a signal to disable Xposed. The reason I'm mentioning this is that, if there was such a mechanism in JBPatch, someone like me who has a hard-earned Kindle DXG, would dare to play with it and as it modifies running process at boot time (/opt/amazon/ebook/bin/init.xargs) and on these very subtle devices, things go wrong very easily resulting in a brick.

Is there such an option possible? or done by someone?

08-15-2015, 03:34 PM	#1777
thatworkshop hub Posts: 715 Karma: 2151032 Join Date: Jan 2012 Location: Iranian in Canada Device: K3G, DXG, Kobo mini	JBPatch in nature is something like Xposed for Android OS. In Xposed, we have a fail-proof way to disable Xposed patches (called modules) if things go bad and system fails to boot. At boot time, user would press certain buttons a few times as a signal to disable Xposed. The reason I'm mentioning this is that, if there was such a mechanism in JBPatch, someone like me who has a hard-earned Kindle DXG, would dare to play with it and as it modifies running process at boot time (/opt/amazon/ebook/bin/init.xargs) and on these very subtle devices, things go wrong very easily resulting in a brick. Is there such an option possible? or done by someone? Last edited by thatworkshop; 08-24-2015 at 12:05 PM.