[LeEco Le Max 2 ROMs, Kernels, Recoveries, & Other ] voland:
So folks who need Xposed and SafetyNet working with Magisk, please read carefully.

Go to the built-in Material Design Xposed Installer. You will see prompt to update to newer version. Download it. It will be in ~/XposedInstaller dir. In case of you will not be prompted, DL it from there: https://xdaforums.com/devdb/project/dl/?id=26586&task=get

Install just downloaded XposedInstaller_by_dvdandroid_09_09_17.apk

Run Xposed Installer, go to the OFFICIAL section, choose "Uninstall", reboot.

If something goes wrong, DL classic Xposed Uninstaller from http://dl-xda.xposed.info/framework/uninstaller/xposed-uninstaller-20160829-arm64.zip

Reboot to TWRP and install just downloaded xposed-uninstaller-20160829-arm64.zip. Reboot to system.

Run Magisk Manager. You will be prompted to install new Magisk Manager version. Install it and run it again. You then will be prompted to install new MagiskSU. Install it and reboot.

If something goes wrong, download latest Magisk Manager from here: https://github.com/topjohnwu/MagiskManager/releases/download/v5.3.0/MagiskManager-v5.3.0.apk. Install it. Do not run it.

Download latest MagiskSU from here: tiny.cc/latestmagisk

Reboot to TWRP and install just downloaded Magisk-v14.0.zip. Reboot to system.

(Essential) In case you has systemless Xposed Framework installed before, do not update that module! Go to the Magisk Manager => Modules instead and press "Trash" icon near Xposed Framework SDK 23 module. Reboot.

DO NOT install old 87.0 framework from "Systemless" section of updated Xposed Installer! Run Magisk Manager instead and go to Downloads section. List down and install Xposed Framework 87.3 SDK 23 module from there. Reboot.

Go to the Xposed Installer and check you finally have systemless Xposed Framework installed and active. You can now install your classic Xposed modules and activate them in Modules section. Sun is shining brightly... :p

Go to Magisk Manager, press "Tap to start SafetyNet check" and notice inconsistency between inconspicuous "SafetyNet check was successfull" (!!) message and bright red "ctsProfile: false" and "basicIntegrity:false" messages. Check real situation in Google Play => Settings => Device Certification. You should see "Certified" status. So Safetynet is really passed and you can play PokemonGo... :silly:

If you want, you can turn ctsProfile to "true" state by installing NoDeviceCheck classic Xposed module from here: http://dl-xda.xposed.info/modules/com.pyler.nodevicecheck_v11_77cce6.apk.

Unfortunately, even with all my effort, I do not found the way to turn basicIntegrity to green, even by installing newest beta Universal SafetyNet Fix systemless module for Magisk v14 from here: https://xdaforums.com/attachment.php?attachmentid=4265013&d=1504747397. It's up to you though, @CrisBalGreece :victory: Could you update your SafetyNetPass for X82x systemless module to formally "clean pass" everything, please, and publish it apart of your next V10 also?

---------- Post added at 03:05 ---------- Previous post was at 02:40 ----------

Well, there probably needed to some explanation about Magisk, Xposed, privileged apps and SafetyNet functionality.

I will try to be reasonably laconic.

There are usual apps, system apps and even privileged apps in Android. Of course, those privileged ones have more possibilities to influence system processes than usual ones.

Such a privileged apps are situated in /system partition of SELinux, Android is based on. This partition is in R/O mode by default BTW, so you need root rights to change this state, even temporarily. More than that, this is quite dangerous. You just cannot give root permission literally "to do everything he want to do" to every developer without any rules and restrictions. At least because not every person are capable enough for understanding all of delicate causalities. At least for reason of hardworking and so time- and effort-consuming workstyle of such low-level programming.

So, an systematic hierarchical architecture of connection between system/kernel, framework and modules was invented. It is consists from:

the common Framework, tightly connected to system/kernel and installed usually in /system, which communicate directly with system/kernel on low level, and simultaneously expose standard high-level functions and interfaces to its Modules

a (user/programmer-written) Modules, exploiting (in standardized way) such a high-level functions and interfaces, exposed to them by Framework

One of such (widely used today) Framework/Modules system is named "Xposed". Many different modules was written for Xposed by advanced users/programmers.

Well as you see, you need serious system privileges for typical user tasks demanded, e.g. filtering off all damned annoying commercials on YouTube. This job could be done for example with appropriate Xposed module, which must be connected to Xposed framework, which (along with filtering module itself) must be installed to system (really into /system partition in case of classic Xposed) by Xposed Installer.

You although have to understand, that by denying commercials you will cut (actually very small amount of) money from YouTube (Google) and respective buyers of its services! You therefore could not be surprised that Google checked integrity of /system (through Google Services) and rise red flag "Tampered!" for those who are interested/involved. Google calls such a checking mechanism "SafetyNet passing".

So... who are interested? Well there are some apps and processes, which want (or must) to check system security more thoroughly, or want to defense itself from hacking. For example AndroidPay, some Wallet apps, Netflix, PokemonGo and other spying/payed/paying apps. Such apps can ask directly GooglePlay about system status (you can see your status in Settings => Device Certification), and then can reject to install itself when your device reported as "Not certified" or reject to run/work after installation until you pass SafetyNet.

However, in real world not such a wide percent of people really need to pass SafetyNet.

Do you really need it?

Do any app (you unconditionally need) reject to install/run/fully work with reason "Your device is not SafetyNet certified"?

If not - do not bother yourself with SafetyNet. You are not endangered with "ctsProfile mismatch" in any way.

Well you can break SafetyNet passing in many ways - unlocking OEM bootloader, turning on USB debugging, remounting /system as R/W, and of course rooting your device in standard way - for example with SuperSU. Installing of classic Xposed Framework or classic Xposed Installed will break your SafetyNet pass for sure!

Nevertheless, if you are already break down SafetyNet by installing classic Xposed, you can just uninstall it from within Xposed Installer app.

Although Magisk author (respectful @topjohnwu) invents another method to root an Android device - without modifying /system partition. He call it "MagiskSU systemless root" (I will not explain all the magic there, if you really interested - lift your ass and find it).

He wrote Magisk Manager app also - standard APK. He also add possibility to hide MagiskSU (i.e. root) from Google and even from particular apps. He also included in Magisk Manager whole system of add-in systemless modules, creating in that way a full-size root + framework + modules bunch -- all without modifying /system. Respect, Master @topjohnwu.

He write many systemless Magisk modules by himself and also ported to Magisk many other modules, written before (by other people) for other root tools and frameworks - for example, for classic Xposed.

However... "Xposed modules, even ported to Magisk, still needs the Xposed Framework to work!" you could say! Of course yes :) That's why [MENTION=4470081]topjohnwu[/MENTION] ported even classic Xposed Framework to systemless Xposed Framework for Magisk - opening in that way doors to successful working of classic Xposed modules under Magisk.

Finally now you are prepared to fully understand why by installing to your phone classic Xposed framework and classic Xposed modules through classic Xposed Installer you will unconditionally break SafetyNet pass - in two words because of unavoidable tampering of /system partition (and other processes/checks also).

For example, if you install (as standard APK file) classic AdAway Xposed module, Xposed Installer (usual user app) tells you "Module is not active: Xposed Framework is not installed!". Okay, you obediently install (classic) Xposed Framework... - and voila, SafetyNet pass is surely gone.

Therefore, you cannot install YouTube AdAway classic Xposed module in classic way. Although you may install iYTBP systemless Magisk module instead. Its work perfectly, believe me and test me.

Well. Using systemless Magisk Manager (working like Xposed Installer in case of classic Xposed) you can systemlessly (I mean in invisible for Google way) install specific Magisk systemless modules (written directly and intentionally for Magisk only, without needs of any additional framework).

But... it would be great if you also could install an special Magisk port of Xposed framework... And then you would be able to use classic Xposed modules in way as they became ported to Magisk (so became systemless)!

Is this possible? Yes! :)

But "Stop!" you can tell. "All you told there means that (when we are using Magisk and we want to pass SafetyNet) we cannot install classic Xposed framework anymore, and we cannot install classic Xposed Installer anymore. So where is interface between classic Xposed modules and systemless Xposed Framework port?..." you can tell. And yes, you will be right again :)

Fortunately, respectful @DVDandroid write for us Material Design Xposed Installer, which are able to cooperate with systemless Xposed Framework (as good as with classic one), and respectful @CrisBalGreece built-in such Installer in his great ROM v9.

BTW, you are really do not need some of Xposed modules anymore. For example, you do not need Greenify - you have great Spectrum standalone system tool in this ROM. You do not need YouTube AdAway and YouTube Background Play Xposed modules - direct (needless any middle frameworks) native Magisk systemless iYTBP module cover all that. And so on.

There, on XDA, many native Magisk modules exists and many Magisk modules are ported from Xposed too. Just search your ex-favorite Xposed module name with "systemless" keyword, read comments and suggestion from other users, believe you are not only one who wants such a change - and luck will be with you. Of course, not completely all Xposed modules are ported to Magisk for now.

Good luck, my friends. Press "Thanks" button at least, if you feel your knowledge and understanding has been extended or deepened. And please forgive me my ignorance if I tell something wrong :)