yashsingh1/xdaforums huggingface dataset:
[Xposed General] Artim_96:
Most useless comment of the century...

The original thought behind systemless XPosed (what this thread was from the beginning) was to be able to have root and XPosed in a way that doesn't tamper with /system to be able to use OTA updates, AP was just a side effect.

That's why SuperSU is needed and will come back when Chainfire is back. Because when you want to flash a zip, there are only two ways: use FlashFire, which only works with SuperSU or use a Custom Recovery, which would break OTAs on non-Nexus devices (where you can't just boot it)

The Magisk does not work for you? Help with logs and information necessary to make it compatible. Wrong thread, bug reports regarding only Magisk belong to the Magisk thread.

You do not want to install Magisk? Lie on the floor and cry in fetal position unneccessary, childish and dumb.
[Xposed General] KaMyKaSii:
Then I won the gold medal? Nice. No matter if it's useless or not, is what will happen. But if you prefer to continue seeing people here crying the same thing, okay.
[Xposed General] Artim_96:
No, only the biggest facepalm you can imagine.

Learn to read. SuperUser is only a temporary solution. When Chainfire is back from vacation, he will contact him to fix the bug causing SuperSU not working properly since it's the only method that has a future. Without, neither LiveBoot nor FlashFire nor most other stuff will work. It would be the complete opposite of what this project is intended to be. Live with that, this is what actually will happen.
[Xposed General] sansnil:
Let's keep it civil guys. You both come off as posers and aren't contributing value here.
[Xposed General] KaMyKaSii:
He will contact Chainfire to correct the problem SuperSU installed with systemless Xposed for Magisk, not independent SuperSU (unless Chainfire want it). And I think you did not understand that I also love SuperSU, but the purpose of Magisk is to be a new center for new and existing systemless mods, not just mask SuperSU to pass verification of SafetyNet and remain current and unique system mods manager
[Xposed General] Artim_96:
There seems to be only a problem with the compination SuperSU+XPosed+AP passing.

And no, Magisk is a method to hide changes from SafetyNet, no matter if root, XPosed or different. But the main reason why systemless root and XPosed even exist is to be able to make OTAs. It was just an unforeseen side effect that SN wasn't able to detect it at first. Magisk is all in all only the same method like in systemless XPosed, the difference is that it works without a reboot. So sooner or later SuperSU WILL come back, I don't see any reason Chainfire wouldn't want his SuperSU to work with it. He makes the manuals about how to achieve root in new systems and how to write a root app to be compatible with all Android versions and ideally with all future versions. All his additions rely on his system because only there he can guarantee that everything is made in a working way.

And SuperSU is already available in a Magisk-compatible version, it only won't pass SN.
[Xposed General] knpk13:
Magisk works for me, both phh superuser and SuperSU. I'm not concerned with Android pay at the moment though it'll be nice if it works. The fact that there is a universal platform for systemless mods is what excites me right now, because of the potential.

Do you know whether the magisk compatible versions of both of these SU solutions were made by [MENTION=4470081]topjohnwu[/MENTION] or [MENTION=631273]Chainfire[/MENTION] and [MENTION=1915408]phhusson[/MENTION]?

I ask because the phh and SuperSU threads have no mention of magisk in them. No news there. So I'm curious as to whether those people think magisk is a good platform and move onto it eventually or maintain their projects independently. Also, magisk will soon be open source right?
[Xposed General] Darke5tShad0w:
As stated in the diagram in the 2nd post of the magisk thread AP does not work with supersu.
[Xposed General] datafoo:
Tested this as instructed and Android Pay does not work. I'm able to add cards but fails at the transaction.

I not using supersu and followed all instructions.
[Xposed General] greenawayj:
Unfortunately AP isn't working for me either for actual payment. (yet - but I am appreciative and hopeful! I've been hoping for a solution for a year or so and this method definitely seems most promising)

Toggling Magisk root off allows me to pass SafetyNet (green) but AP rejects at the pay terminal because Google 'is unable to verify...' something or other

Nexus 5. Just flashed yesterday to stock 6.0.1 MOB30Y (Aug 5 security patch)

SuperSU Uninstalled. Phh superuser zip flashed and app installed.

Xposed systemless 86.3 flashed.

Xposed material designinstaller by DVD Android.

Only non-standard aspect of my phone is TWRP instead of stock recovery. I do have a recovery switcher so in theory, I could swap stock recovery in.

Beyond that, I'm happy to help test anything else....

Thanks much for all the work on this.
[Xposed General] Artim_96:
At least it sounds like he made them himself (topjohnwu). And yes, I bet he will make it open source, at least one it's working good enough. Or was the same with the vet first version of systemless XPosed, at first he only opened a few things he changed, later he released the fur source code...I think.
[Xposed General] tohtorin:
Can someone share 86.2 uninstaller?

EDIT: No need anymore, found it.
[Xposed General] grep_i:
If I can remember correctly you didn't have bootloops or other booting issues so why create logcat of boot instead of logcat of device in working state on the moment the issue starts can it be you do not know how to do this or what to do when ?

Hope you understand enough to do what is needed this time[emoji4] . Maybe Google can help you out.

Happily for you the old method is still working so you are not totally unhanded here.
[Xposed General] Artim_96:
I don't have any bootloops, right. But there have to be problems that should be visible in bootlog. There should be visible if everything with Magisk is working right and why XPosed just won't activate. I mean I even had deleted cache and dalvik/art cache as I installed it but it recompiles for maybe 2 minutes or even less when it should take at least about 5 minutes to recompile everything. And normally when XPosed is active, the "optimization screen" shows up with something like 35 of 390 apps optimizing...here it started with 179 of 270 or something like that so I would say that there went something wrong.

I don't know if it's possible for me to take logs in the running system when something goes wrong because it looks like there is already going a lot wrong in bootup. And no root app is working which makes everything more tricky.

Anyway, it seems to be a general problem that Magsik isn't running on Samsung MM devices and it looks like I already have more luck than anyone else since I only read from others that their devices aren't booting at all. I already contacted topjohnwu since he is searching for testers with Samsung MM devices (his own are stuck on 5.1) and explained what is working and what not.
[Xposed General] abaddon37:
Can you post it please? I am unable to find it ????
[Xposed General] mklmkl:
Have the the problem that systemless XPosed sometimes isn't working & could narrow the problem down to "soft reboot".

It is deterministically not working after a "soft reboot" and functional again after a full reboot.

I'm using a Nexus 6p with AICP MM.

Anyone else?
[Xposed General] jmichaels1982:
Hello. 5/10 times xposed will not load. Attached are logs. Thanks http://cloud.tapatalk.com/s/57a76ea7c2c84/xposed systemless log.zip
[Xposed General] ianmacd:
I have to concur with this.

What [MENTION=4470081]topjohnwu[/MENTION] is doing with Magisk is very cool and I have a huge amount of respect for him, but it's a huge hack and riddled with bugs at the moment, many of them intricate and device-specific. In short, the code is completely immature and it will take quite some time before that changes.

Xposed, on the other hand, is fairly mature. Even unofficial systemless Xposed was approaching a pleasing level of stability with the 86.x releases, with Chainfire having made changes to SuperSU that vastly simplified the work that unofficial systemless Xposed had to do. One striking result of this was [MENTION=4419114]rovo89[/MENTION] being impressed enough to state that Xposed would officially support systemless installation as of v87.

Then along comes unofficial systemless Xposed 86.3 and everything has been thrown into turmoil again. A new dependency has been introduced in the form of Magisk, and many devices, such as Samsungs, cannot yet even run the code, assuming their owners would even be interested in doing so.

There have been a couple of calls to have unofficial systemless Xposed continue to support SuperSU installations, and I totally understand that desire. A lot of people have significant trust invested in SuperSU, not to mention a need for its universal app support, and are not likely to want to replace it with another root manager; certainly not before such a contender achieves 100% compatibility with the apps on their devices.

Running the unofficial systemless Xposed was a breeze prior to 86.3. With 86.3, it's become so convoluted that it now feels like overkill, assuming you can even get it to work. For many of us, unofficial systemless Xposed is now broken and its development has branched onto an uncertain track.

Don't get me wrong. I'm quite excited about Magisk, but it's brand new and very unstable. It's alpha code and certainly not ready for prime time. With that in mind, I don't believe it makes sense to tie the development of systemless Xposed to it at this early stage. Magisk needs to become a lot more reliable and a lot less fiddly first; and it needs to function without compromises on which root manager can be used. Otherwise, it's just not an attractive proposition.

For this reason, I'll be holding off on installing Magisk and unofficial systemless Xposed 86.3, and quietly hoping that [MENTION=4419114]rovo89[/MENTION] elects to apply the KISS principle and implement an official systemless framework that is much simpler and manageable in scope than what we are faced with now.
[Xposed General] Artim_96:
... That's about exactly what was said before. And of course rovo will implement it the way it was in v86.0-86.2 since everything else is not reliable. And maybe, once Magisk is reliable enough, he might implement Magisk functionality too.

---------- Post added at 07:03 PM ---------- Previous post was at 06:58 PM ----------

Can you record a log of the soft reboot?

adb wait-for-device logcat > logcat.txt
[Xposed General] tohtorin:
You can download it from here:

http://drg.fi/misc/xposed-uninstaller-topjohnwu-20160718v2.zip

EDIT: here is installer as well:

http://drg.fi/misc/xposed-v86.2-sdk23-topjohnwu.zip

---------- Post added at 22:56 ---------- Previous post was at 22:00 ----------

Could not agree more.
[Xposed General] Flam31800:
when I installed the Magisk zip, my phone lost root access and when I try updating my binary it won't!
[Xposed General] Mr.Yawnie:
You are supposed to flash Magisk on clean, unrooted base.. Then flash one of the Magisk supported root zips.
[Xposed General] an0therus3r:
Can anyone tell me which Magisk SuperUser to use and maybe also why? Should i use pph's or the other one?
[Xposed General] SpasilliumNexus:
Read the Magisk thread? Literally everything is explained....
[Xposed General] Citizen_Snips:
Read the OP of the Magisk thread, maybe? All of those questions are answered in the first post.
[Xposed General] an0therus3r:
Yeah sorry my bad. I missed the picture that actually explains everything ;)

Anyway, it runs perfect now on my OPO (1) running Sultan's ROM 6.0.1
[Xposed General] Carousel7:
Where can I find the uninstaller for previous version 86.1?
[Xposed General] lulli1:
tried everything to make this systemless work on my Nexus 5, but without success ( systemless root by chainfire - worked, Magisk - worked, systemless xposed - no way to get it working). => sorry no boot logs!

Finaly I flashed all stock.img again and installed the official rovo system version. Now all is fine again.

Just wanted to let you know for future development...
[Xposed General] -Duir-:
Going simply off your post, the answer to why it doesn't work seems right there. You can't use official SuperSU. You need to use the one patched to work with Magisk, and you need to install Magisk first.
[Xposed General] Captain_Throwback:
The new version of SuperSU that would be the basis for the systemless Xposed is unfortunately not working properly on some devices with password on boot (this applies at the very least to the HTC 10), so I think that's one reason [MENTION=4470081]topjohnwu[/MENTION] went a different direction. If that issue is worked out/fixed using a different method than Magisk, then I guess that's fine - but functionally Magisk is a pretty complete solution, even if it's still in its infancy.

I guess we'll just have to wait and see how things develop, but having a platform that allows any/all mods to be run systemlessly seems like a good basis for future development/project, imo.
[Xposed General] grep_i:
I guess to make the systemless Xposed v86.3 you need the phh superuser as explained in the OP.
[Xposed General] lulli1:
This is what you can read in the Magisk OP or Post 2:

"So for some reason if you want to use SuperSU, you can still use it; you just cannot have Android Pay working."

and this grafic is shown in Post 2:

So I found no reason why not to use Chainfires Beta systemless SU...

Maybe I will give it a new try, when the next Nexus monthly security patches are available.... thanks anyway.
[Xposed General] CSX321:
You can't use CF's beta SU. You have to use the Magisk-compatible one from link in the OP: "Magisk Compatible SuperSU".
[Xposed General] lulli1:
yes. this was what I made wrong. But it's not clearly enough documented or described in the OP.
[Xposed General] Mr.Yawnie:
Well, this is Xposed thread after all. It is very clearly informed on Magisk thread.

Edit: read earlier posts, and yeah, it could be more explicit in saying that you have to use the modded SuperSU from the thread as of now, not from Chainfire's thread.
[Xposed General] grep_i:
And that's your whole problem this is a thread about Xposed and you come here and say a lot of stuff you don't even understand about other things than Xposed.

Maybe you must study more on this material or just ask better questions ?

Nobody can't help it if you can't understand what you're reading.

To me it is clear enough.

You can ask questions here about stuff as long as you admit you don't know 2 bits about it there's always someone who is trying to help you get educated.
[Xposed General] GXGOW:
It's working flawlessly on my G Pad 8.3, but it fails to work on my OnePlus One. I've flashed both SuperSU systemless, Magisk and the latest Xposed systemless from this thread. All three are working without issues on my G Pad, but on my One, it's either Xposed or SuperSU that is working. When Xposed is working, SuperSU asks to update binaries, which fails, of course. When SuperSU is working, the Xposed app tells me Xposed isn't installed.

I've used the same method on both devices. Uninstall previous Xposed versions, start off with clean boot.img, flash SuperSU, flash Magisk, flash Xposed (in that order).

Is there anyone who could help me solve my issue? In the meantime, I'll keep running v86.2 on my One. I'm running Sultanxda's CM13.
[Xposed General] NetWasp:
Yeah i think it should be made separate, or atleast have the ability to flash to custom roms!
[Xposed General] datafoo:
Your order is incorrect and you're not using the properly modified SuperSU for Magisk.

1. Flash Magisk.

2. Flash Magisk root version - phh's superuser modified is (preferred) or SuperSU modified for Magisk as an alternate (not preferred)

3. Flash Xposed

Because of what Magisk is intended to do it needs to be flashed BEFORE root in order for root to be implemented correctly.

You can run this on custom roms without issue. It is different devices which are posing the issue as different systems operate slightly differently.

If you want separate flashing simply use 86.2 which doesn't require magisk.

The point of magisk is to give a true systemless install and help enable applications like Android Pay, work on rooted ROMs.
[Xposed General] NetWasp:
the issue is that i want to use this on Sac23 rom but i follow the instructions here and it doesnt work, i just get repeated bootloops.

I install the rom, then majisk, then the phhSU, then xposed and bootloops

Any idea?
[Xposed General] teddy0209:
What device do you have? Does modding boot.img allowed on your device?
[Xposed General] NetWasp:
Hi,

I have a Samsung Galaxy 7 Edge

Thanks
[Xposed General] teddy0209:
That's the reason why, as of now magisk don't work on sammy mm... You can use the 86.2 version instead...

Edit: It has been reported, and if you are qualified, you can contact the dev to become a tester, otherwise just wait for the update and use the previous version for the mean time...
[Xposed General] gohamstergo:
I'm a little confused. Main magisk thread says no AP with sysless xposed. This thread says yes..??
[Xposed General] g2uzer:
Im guessing you still have to turn xposed "off" reboot and then temporary unroot with his new method to get AP to work.
[Xposed General] grep_i:
No reboot needed with new version.

There's just a switch to enable / disable root temporarily.
[Xposed General] Captain_Throwback:
Actually the reboot is necessary....I'm sure the OP will be updated soon with the new info.
[Xposed General] g2uzer:
You still have to disable xposed and as far as I know even with the new method AP won't work with xposed, even if you temp unroot xposed is still "active"
[Xposed General] h4lli:
Sadly my banking app is still able to detect Xposed :(

Running Magisk & phh's root -> banking app is working after unmounting root with Magisk Manager

Running Magisk, phh's root & sys-less xposed 86.3 -> banking app is detecting xposed even after disabling xposed in installer and rebooting, only uninstalling framework AND installer makes the app work again.
[Xposed General] Mr.Yawnie:
Works just fine on my Galaxy s4 running cm13.
[Xposed General] jesssiii:
Did you mean you could NOT get Android Pay to work? If so, did you disable Xposed and reboot before trying?

Nexus 6P
[Xposed General] reayard:
For me the only reason to try the systemless root and xposed is that OTAs should still be working. But I cannot confirm this for the stock Samsung ROM on the S6.

As soon as I flash systemless supersu the update process already tells me that my system was modified and I cannot have OTAs. Even though I immediately replaced TWRP with the stock recovery after flashing supersu.

Could other S6 or S7 users report their experience with OTAs after flashing this?
[Xposed General] Mr.Yawnie:
Did you verify it indeed installed the root as systemless? Did you write "echo SYSTEMLESS=true>>/data/.supersu" in recovery terminal before flashing supersu?

The zip checks the device upon flashing and then installs either systemless or system root.
[Xposed General] reayard:
Somewhere in this thread it was mentioned to check if a file called "su.img" is located under /system or under /data to check if it is systemless or not. For me it is under /data so I assumed that I have systemless root. On the other hand I am pretty sure that TWRP was only allowed to mount /system read-only when I flashed the ZIPs.
[Xposed General] Mr.Yawnie:
Yeah, that was one of my posts. So it is systemless then.
[Xposed General] greatheights:
Everything seems to be working for me on my Nexus 6. Thanks for working this out!

I unrooted by flashing stock in Wug's NRT using No Wipe Mode. After rerooting, flashing systemless xposed, and Uninstaller the official app, Gravity Box kicked right in--before I'd even installed the Material Installer. Does that seem weird?

I don't actually use Android Pay--in this more for being able to accept the monthly OTAs--so I couldn't actually see if a transaction would go through for me, but my phone did pass the Safety Net check when I disabled Xposed.
[Xposed General] Sebastiansm:
Hello, can someone help me? I already had xposed, so I flashed the uninstaller and then the system less xposed, everything went well there, when I rebooted my phone got this warning in the installer app:
[Xposed General] bezzinado:
After reboot galaxy s7

Vérification failed

Unable to restart your device. The integrity vérification has failed .Your need to reset your device to factory default settings. This will erase all your data.

Reset device
[Xposed General] smohanv:
Sorry. I missed to add "NOT".

I could not get Android Pay to work.

---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------

I disabled Xposed and tried after soft reboot and also full reboot. I could not even add my card.
[Xposed General] topjohnwu:
I'm not familiar with Samsung devices. I used the Wanam Xposed as a base. If you need the alternative one, then I need to add one for it.

I'm using it on my HTC 10. Many Samsung users report positive feedback.

Maybe the custom rom itself is not compatible with Android Pay. Only test Android Pay on stock rom.

Samsung have knox, it should be the issue. I never use Samsung phones so I cannot know this will happen.

For those with Systemless Xposed installed but get the "xposed is not enabled", please wipe the data of Xposed Installer and reboot.
[Xposed General] Mr. Davin:
Good Job Man Keep Going

For S7 Edge Which Zip Should I Install

And Do I Need To Have TWRP

Thanks In Advance
[Xposed General] Artim_96:
At least it would be great if you would mention on the main page that there can be issues with some Note 4 variants (at least that is what Wanam says to the alternative versions) so there is one reason less to ask for help;)
[Xposed General] joshnat:
So here's my experience on Nexus 6p: I'm already running systemless root on Pure Nexus. Android Pay works fine. I flashed systemless Xposed and rebooted. Safetynet check failed. I disabled Xposed in the app, rebooted and Safetynet check passed. So, if I want to use AP, I have to disable, reboot, pay, enable, reboot. Not perfect, but a step in the right direction!
[Xposed General] egingell:
Just an FYI: systemless root has been available since Lollipop.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[Xposed General] Zyker019:
Works with LG V10 (H901). Can't use android pay though
[Xposed General] topjohnwu:
Update!! v85.2

I followed [MENTION=631273]Chainfire[/MENTION]'s suggestion not to mess with su.img lib directories. This upgrade will remove all Xposed files from su.img.

For future versions, the xposed files will be stored in a separate file in data. It should be more reliable, and won't mess up SuperSU, and I don't need the dirty workaround for SuperSU anymore.

v85.1 users please download Xposed Installer from OP, it contains the new path detection.

v85.2

All v85.0/v85.1 systemless users should flash this upgrade! Previous paths will not be supported in the future!

- Separate Systemless Xposed from SuperSU. It now uses it's own image in data (/data/xposed.img)

- Won't effect SuperSU anymore. Both are now working independently

- Massively updated flash script, should be more reliable (e.g. Prefer sukernel in su.img over bundled binary)

- (Derived from Wanam's update) Add Huawei theming engine support (details); Ensure the recompilation on Huawei EMUI Roms (details).
[Xposed General] ahrion:
You are the man
[Xposed General] JohnCorleone:
I am pretty sure that is why...especially if any of the data is from a previous device. Android Pay just makes it easier to spend money.. Lol. I want to get Xposed working for AD Block and also I like the module that lets me change my phone info, mask my IMEI, etc. I hope someone comes up with a way to protect our fingerprint biometrics from ending up in a government computer but it's probably already too late for that! Lol.
[Xposed General] ahrion:
Flashed. HTC 10. Works perfect.
[Xposed General] flatpedals:
Etoken BCR? :)