I'm really getting tired or your f'ing use of those belittling emoji's that indicate you're calling me stupid
Sorry!
I appreciate your comments!
My objective is explain a different way to use the Xposed Framework when using it with Magisk.
Please, you use Xposed SYSTEM or SYSTEMLESS?
The reason why you can't even disable xposed modules is because you're disabling xposed when xposed isn't even the problem, faulty xposed modules have nothing to do with xposed. Instead of disabling xposed through magisk use the xposed manager to do that, there's a disable switch in there for a reason, turning off the magisk module turns off the module and that's it, nothing more.
This is not possible with a bootloop!
And when you can't boot, then you boot to the TWRP and
disable the MAGISK not the XPOSED! This is the different between you and me!
Turning off xposed through the xposed manager app, that's different, but then again none of this matters because if you have a faulty xposed module and can't boot then there's NO other way but simply deleting the one file that tells xposed "hey, these are activated, boot them up ok" vs disabling xposed
Then explain why the Xposed Installer let the user enable/disable modules with the Framework disabled and not when it doesn't detects the Framework.
The Installer is now checking the file "disabled". But it only does for SYSTEM installation, and not for Magisk Installation. This the different and the point that I want to point.
You do realize you can't do that if you CAN'T boot at all. Did you even read anything i said? (If an xposed module bootloops your device, the only way to make it boot with all modules disabled is to delete the file of enabled xposed modules, then boot, tick back those that work and reboot)
I repeat. This assumption is false... In my way I boot to TWRP and I disable MAGISK. After that you can boot. And then my objective is use the Xposed Installer to disable the faulty module. At time, I can only do it with a very tricky hack: create the "disabled" file and open the Installer... only with this the UI leaves the option for enable/disable modules.[/QUOTE]
I explain it: The reason is because I like to use STOCK Roms and upgrade using OTAs. So for this the only way (at time) is a SYSTEMLESS rooting & Xposed. This can be done using Magisk. So in my opinion the Magisk way is the future. And for this I recommend to fully support it in the Xposed Installer. It needs to support the two variants: SYSTEM and SYSTEMLESS. At time, it only support the SYSTEM version.
I don't understand why you want some overly complicated magical way of flipping a switch to disable a xposed module or magisk or xposed itself when your device just won't boot, when xposed is disabled (be it through the app or via magisk) you can't disable it's xposed modules, someone already pointed that out, disabling magisk won't help you either[/SIZE]
When you will use Xposed with Magisk you will understand it. This is not complicated. It's the way when using Magisk.
Only other way that you can disable xposed is by doing vol + vol - as your device turns on but like some guy said you can't disable xposed modules when xposed is turned off.
Just do what everyone has always done ok? Delete the enabled modules file from the xposed data folder and reboot to android and go on from there...
Remember that when you remove the file of running modules you lose the list. For this reason the "disabled" file is created.
Regards
Wanna trade phones?? No?? So you DO see my point!
