Yeah I meant technical limitation
Thanks for this. I fail to see though why a clean relaunch would be needed. In most cases, users will either relaunch system menu for sigpatches, or would go to hbl (or a hotkey'd app) that would need hacked functions such as wupinstaller for fakesigned installations, or ftpiiu_everywhere.
If a user wants to use any of these apps anyway, he would have to relaunch to system menu then launch these apps, where after he's done, he's not left with a clean relaunch anyway.
Also, couldn't implementation be versatile? In the sense of having the option in config.txt to either keep it the way it is, or the way I'm proposing. So that users get to pick the way they would like to see haxchi working.
Though I do see the limitation of it being not too friendly in the sense that you'll have to reinstall haxchi every time you change that option (or anything) in config.txt .. which leads me to my next point: wouldn't it be possible to implement reading the config.txt from SD, and revert to nand only if SD doesn't exist/file on SD doesn't exist?
Thanks again