[General Questions and Answers] tapa_t:
OK, don't know why or exactly how but I got xposed working.

Current configurations:

Jelly Pro, OS 7.0, 2017.11.28 update.

Root with TWRP and the official SuperSU v2.82, pretty much following this.

Xposed framework: 26-07-17-xposed-v87-sdk24-Xposed-by-PurifyOS.zip by ErnyTech from this link.

Xposed installer: XposedInstaller_by_dvdandroid_04_08_17.apk posted by petrevirgil here.

How:

So, I went to Magisk systemless xposed thread to complain that I get bootloop with the latest Magisk and systemless xposed. No help whatsoever, but quite a few people followed me and reported bootloop in similar situations. Interestingly, all of them were Galaxy users on Nougat. So, I got curious and did some digging, found out that Galaxy always has some problem with xposed and people are doing various workaround, one of which is this comment by rifek4.

Out of curiosity, I followed his comment and installed the latest material xposed installer by dvdandroid, and flashed the unofficial framework from the link above in TWRP. Reboot.

Now, I get xposed framework "active" in the installer app, which I never got with the the latest official framework regardless of which installer I use.

You can check modules to activate in the installer but none of the modules were actually activated after reboot. There are module_list and enabled_module_list in /data/data, but they never get activated. don't know why.

So, I said "The hell. This guy says he's got it working with an older version of the material installer. Why don't I give it a try?" I uninstalled the latest installer and installed the one petrevirgil posted. May have flashed the same framework again. Reboot, and I got myself a nice bootloop again. Nice, just nice.

To get out of the bootloop, I forced shutdown and boot into TWRP, adb installed the latest official XposedInstaller_3.1.5.apk. An old installer gives you bootloop, just replace it with the latest. However, installation fails with:

>	3882 KB/s (3105672 bytes in 0.781s)

>	/sbin/sh: pm: not found

Edit: Come to think of it now, it's obvious that installing apk in recovery fails since it's not running Android, and of course, there is no pm running either.

To see if adb installation really failed, I booted into system and found:

- I no longer have bootloop.

- Yes, installation indeed failed as I still have the old material installer installed.

- All installed modules are working now. I can also install new modules and all of them are activated with the installer now.

So, there you have it. Working xposed with the files linked above, but I have not a slightest idea why.

How does installing a newer installer and failing get you out of bootloop? And how does it get the installed modules activated?

Or has it nothing to do with anything, and as long as you get out of bootloop in any way, xposed starts working? I do not know.

Edit: Now that we can confidently say it wasn't the installation of the latest installer nor the failure to do so that fixed the bootloop, I really don't know what got me out of bootloop. Maybe I just had all the right files installed, and it would have eventually booted successfully if I just waited longer than 10 minutes.

I just got notification for system update, but I am going to hold off on that for a while. Will eventually update and see if xposed still works with the latest firmware.