I updated Magisk to 19.2/7.2.0 and found that after the update it had rendered the systemless exposed module inactive. Though it shows up in the modules list as active within Magisk Manager the Xposed Installer app states that it is not installed.
So in turn I updated the systemless xposed module (2019.05.01) and after the restart found myself stuck in a bootloop. It would appear that the all-in-one installer installed the standard version of xposed for my API-level (sdk 23, MM6.0) and not the wanam/samsung modified version I had been using prior, which does not cause bootloops.
(As an aside I did have a similar problem with Magisk 18, and could not use the systemless-xposed-wanam-zip because it had been keyed to accept Magisk versions lower than 18, and the zip was not updated to accept installation with newer versions...I incorrectly assumed that the all-in-one update perhaps fixed this issue.)
Considering systemless xposed requires Magisk to run as a prerequisite I uninstalled magisk using the TWRP-compatible zip file believing it would prevent it from running...but the bootloop still occurs.
I have a Samsung J7 (2015), SM-J700T running Android 6.0 Marshmallow. The data partition is Samsung encrypted and TWRP is unable to access it.
Is there any way to disable the module without having access to the system being loaded to disable/delete it via Magisk Manager? And if so, can a solution be performed without having access to the /data partition?
(I suppose the other question is whether anyone knows of a TWRP-mod/similar recovery that can access Samsung encryption to read the /data partition, but that's for a different thread.)
Although nothing on my device is critical I would appreciate not having to lose the existing data and having to start from scratch. Should I have transferred/backed-up/made a copy? Probably. But updating Magisk has been straightforward and without difficulties for quite some time that I evidently developed a false sense of security.
Any assistance on this would really be appreciated
Thanks in advance
All is running OK)))
PS rovo89 inform that 'most likely module will never get any updates in the future' (((