yashsingh1/xdaforums huggingface dataset:
[Xposed General] Artim_96:
No AP with XPosed and SuperSU. It should work at the moment with the modified phh's SuperUser, when you unmount it in Magisk app

Edit: ok, that's new. maybe it will work better after next update, so maybe at the moment you indeed need to reboot your phone to get AP to work
[Xposed General] koko115:
86.4 works on Samsung devices ?
[Xposed General] FPSUsername:
I didn't know August had a 0 day
[Xposed General] Artim_96:
Questionable. When you get Magisk to work out should. The bug causing a bootloop should be fixed now.

For me, it's not working. Don't get bootloops but everything else isn't working too.
[Xposed General] gohamstergo:
Hopefully a method is thought up to kill xposed via timer like root is being done. Gone without AP this long, I don't mind waiting. At least I can OTA now tho! Great work regardless!

Thanks for keeping hope alive!
[Xposed General] GTDarthYoda:
Just came to post the same thing lol
[Xposed General] vikmurthy:
Would someone mind posting the full set of instructions for this process? I only see 3 lines of instruction in the OP, and I'm not clear as to what they mean -- it feels as if they've been truncated.

I have a rooted Nexus 6P, and have downloaded 4 items:

1. Magisk v2.zip

2. phh-superuser-Magisk

3. Material Design XposedInstaller

4. Systemless Xposed Framework v86.4 (ARM version)

Is that the order in which I'm supposed to flash? Is there anything I need to do beforehand, like unroot my 6P using SuperUser?

Thanks in advance, and apologies for the newbie questions.
[Xposed General] GXGOW:
Well that's pretty dumb of me. I'll try this when I get home and report back. Thanks for the help! :D

EDIT: It's working now! Thanks a lot!
[Xposed General] grep_i:
Yes the sequence is right but I would also download TWRP.img for your device to boot from rather than flashing it on your device for this to work you need to get familiar with using adb and fastboot when your phone is connected to the computer with USB cable and in Android settings USB debug enabled.

You can than boot to custom recovery without flashing it on your device. Unroot or starting with fresh rom the choice is yours what suits you the best.

Boot to custom recovery flash the first 2 steps boot to system install step 3 open step 3 and from within there choose to install step 4 or just reboot yourself to custom recovery and flash step 4 yourself.
[Xposed General] knpk13:
It's easy if you try to understand what's actually happening. Basically you flash magisk, which modifies boot.img for universal systemless mods. Then you can flash any magisk compatible mod created by any dev after you flash magisk (like superuser or xposed). Bonus effect is you get Android pay of you follow some steps. The material design xposed installer is just the apk to use xposed framework; the apk is not flashed so you can install it whenever you want.
[Xposed General] vikmurthy:
I worked through all of the steps indicated in the prior two messages:

1. unrooted 6P using SuperUser and rebooted

2. booted into TWRP

3. flashed Magisk v2 and phh-SuperUser-Magisk

4. could not get Material Design Xposed Installer .apk to install via ES Explorer, so I simply flashed Systemless Xposed Framework v86.4 in TWRP and rebooted.

Now, the existing Xposed Installer on my phone shows the Framework as "Xposed framework version 86.4 (Systemless by topjohnwu) is active", and all of my pre-existing modules work fine.

However, when I launch Magisk Manager and press the "DISABLE ROOT" button, nothing happens. The Root Status still shows as Mounted, and I'm unable to use Android Pay.

At this point, I'm not sure where I've gone wrong. Should I reflash Magisk v.2? Should I restart the process all over again? Any advice would be much appreciated.
[Xposed General] Captain_Throwback:
You won't be able to use Android Pay with Xposed installed anyway, especially if you can't disable root. I'm sure [MENTION=4470081]topjohnwu[/MENTION] will get down to the bottom of this soon.
[Xposed General] CSX321:
You don't mention installing the phh Superuser app from Play. That's also needed. The first time you hit "Disable Root" in Magisk Manager, you should be prompted to grant it root permission. (Then you have to hit it again that first time to actually disable root.)
[Xposed General] Artim_96:
All in all it should work, at the moment there are only problems with Samsung devices.

But no, you can't just flash a version higher than 86.2. READ THE OP! When you follow these instructions it should work. Otherwise make a proper but report so it will run soon.
[Xposed General] sansnil:
Just adding my v2 testing results with AP: transaction successfully processed but had to disable Xposed and reboot. The new timed root suspension works great but Xposed is still detectable. a way to similarly suspend Xposed?

(N6 + MM stock + phh superuser + Xposed)
[Xposed General] vikmurthy:
Thank you so much -- your suggestion totally fixed the problem, and I just successfully used Magisk Manager to unmount root and set up Android Pay. It also allowed me to pay my rent for the next 5 months with the Radpad app (paying via Android Pay), so that I can earn a few thousand credit card miles. Thanks again -- and this is definitely a really cool little workaround by the OP.
[Xposed General] RandomPooka:
Would it be possible to script killing the processes used by xposed while you still have root, then enabling them again after your root timeout expires?

Or, are there changes to the system that go deeper than just simple processes that can't be disabled without turning xposed off and rebooting?

---------- Post added at 11:39 PM ---------- Previous post was at 11:27 PM ----------

These 4 processes could be identified and killed, the apps responsible for them disabled (frozen, set to non-executable, whatever), and that could theoretically prevent them from triggering SafetyNet. Doesn't it scan for all processes? Once root is available again, defrost/enable/chmod a+x the apps and get the processes started again.

Just thinking out loud here. I haven't really messed with it to see whether that still requires a reboot on restoring the app and processes.
[Xposed General] teddy0209:
I don't think it's possible. If I think of it xposed load things at boot so to unload it must require a reboot. Framework, libs, etc... As far as I know xposed is not just as simple as running and stopping a process...
[Xposed General] puneet724:
Even i tried to install new version 86.4 but failed.. can someone guide me through proper steps
[Xposed General] FPSUsername:
Use the Uninstaller, then flash magisk v2 and then xposed v84
[Xposed General] puneet724:
Did that..then it shows super su not installed..why?
[Xposed General] FPSUsername:
Okay try this:

Uninstaller

Supersu from chainfire

Magisk

Xposed

Or

Uninstaller

Magisk

Supersu for magisk (check op and 2nd post)

Xposed
[Xposed General] steveo17:
I seem to be getting random reboots and I think it has been since 86.4

Nexus 6P

Latest August Release

EX Kernel

Magisk V2

Phh Supersu

Xposed 86.4 Magisk

Log

https://www.dropbox.com/s/0cfp8a81kfjoqb1/xposed_error_20160811_071110.log?dl=0
[Xposed General] grep_i:
See no error at all in your log.

Are you sure you did not install anything else ?

Can you disable Xposed for a while and see if the random reboots stays away
[Xposed General] steveo17:
that was just the boot log after the random reboot. i guess i would not expect to see an error there right?
[Xposed General] topjohnwu:
Sorry for the slight confusion lately (and the title date error lol).

I'm finalizing Magisk, once it's stable then we can start doing tests for Android Pay.

Finger crossed
[Xposed General] grep_i:
Yes that's right, try to catch the errors with logcat if possible or try disabling Xposed just to find out if Xposed or the modules have anything to do with the random reboots
[Xposed General] Droidphilev:
hi,

playing with Magisk and some streaming app that i use. Today it seemed that i finally can hide root with Magisk for this streaming app. The problem is xposed though. I installed the Magisk compatible systemless xposed and the material design xposed installer. If i flash the zip without installing the installer the streaming app crashes. if i install the installer without flashing the zip the streaming app says my phone is rooted (this works with Magisk and phh installed only though) so disabling xposed in the installer in not enough it seems. Would there be a way to hide the installer after disabling xposed?

It's a little unclear where this question should be asked, so please don't kill me.
[Xposed General] topjohnwu:
Magisk v3 is now live!

It fixed many issues for Samsung users, Samsung users please check it out :)

The big news is:

It is confirmed that with new newer versions that auto unmounts app_process, Android Pay will work.. with transaction accepted!

Note that if you want root access, you HAVE to use [Magisk] phh's SuperUser with Android Pay Support
[Xposed General] :
Still no R&D for this awesome dude. [MENTION=243864]xda[/MENTION] stop be lazy like Google :silly:
[Xposed General] Droidphilev:
Hi,

Is there aynone who can share xposed 86.3 please? Its not in the old version post.

Thanks!
[Xposed General] topjohnwu:
LOL, I've been waiting XDA to change my title for weeks now :p

v86.4 is nearly identical with v86.3, I just added 3 lines to the mount script so disabling will actually not mount app_process. Other functionality and files are not changed at all.
[Xposed General] Droidphilev:
Ah ok, thx. I guess don't won't help me with my streaming problem together with xposed then :)
[Xposed General] JohnCorleone:
Restoring a nandroid has been very unlucky for me...lol

Edit....does anyone have a link for systemless 86.2 for the HTC 10? The link takes me to a post without a link. Thanks!
[Xposed General] topjohnwu:
My phone (and only one) is an HTC 10, and I develop all stuffs on it.

So HTC 10 will be the last device on earth to have issues lol
[Xposed General] topjohnwu:
OK guys, big news here.

A tester just confirmed that even with the simplest method of v1, Android Pay is working with successful transition.

So it's the best scenario now: Possible for Root Toggles and Xposed works with enabled

This is nice because we can now toggle root at ease instead of relying on a timeout.

So all the problems now specifically points to Nexus devices :)

Never though Nexus will one day become the issue for Android development lol, super sarcastic

People can still report Android Pay failures in this thread

I'll recruit many testers soon, please stay tuned to my threads (systemless Xposed, Magisk main thread, Magisk phh root).

I'll post the info to all threads so you won't miss it.
[Xposed General] dannycellestio:
I do have a question, and I really hope you'll see it. I've posted this on the magisk phh superuser thread, but I was highly ignored. I am forced to stick with 86.2, with no magisk, because root it definetly not working for me. It worked on v1, with phh, but still was not as good as the chainfire one. v2, no root, v3 same. It simply does not work. If I flash your phh supersu it continously denies my perms, with chainfire's magisk supersu it doesn't even ask for them. so, conclusion, phh one is not as advanced for all (or working) and chainfire's magisk-modded one still doesn't work. why's that and why not try to make a chainfire one? I am literally out of ideas right now, because of all of this root problems, my phone is a custom-ROM-ed unrooted dead creature atm..:crying:
[Xposed General] Yeti47:
Have you install the phh's supersu app from playstore? It doesn't prompt for root requests without it.
[Xposed General] topjohnwu:
I think I stated quite clearly in the first place, SuperSU will not work if app_process is unmounted. So it can never be used with Xposed if you want Android Pay.

I'm not against SuperSU, SuperSU do have many advantages over the open source root. However, the situation is that currently it can not work well, and it's closed source so I cannot even debug or modify SuperSU.

If you have issues, please post logs so I can possibly fix the issue for you.

Have you install phh's SuperUser app? Did you mess up mixing official SuperSU and Magisk?

There are simply too many possible ways you can break it. Why don't you try to revert to 100% stock before reporting the bug you've experienced :)

Hope you can understand, I'm not lazy and willing to fix bugs. Actually, I spent nearly the whole week to make Magisk fully support Samsung. To achieve this I even fixed phh's root (my fixes will be in his future releases)

But to make things clear, only bug reports with the information I want can help. Also starting clean from stock may help me identify the issues. Magisk is relatively new, custom roms might have done too much to break Magisk.
[Xposed General] dannycellestio:
Yes, of course..

No, I had both the app and the zip installed. Tried on any variant, full loaded RR, stock RR, stock MOB30Z, anything. And everything above v1 did not work with any root. On v1 I was able, no matter the ROM and its load level, to get root with both of the methods.

And yes, there's no problem. Once I'll have the time, I'll give you every kind of log you'll need for solving things. All I wanted to know is how did you manage to make that Magisk-SuperSU 2.76 and how could I run it without any problem. But I think you'll be able to give a response to that once you have the logs.

I am not so interested in using Android Pay. I simply want systemless Xposed and working root just how I got on the v1 version. And I can swear I'm not the only one in this situation.
[Xposed General] fjdifede:
V1 versión, Xposed 86.3 and pph's super user is working in for me using my bank direct pay apk my cards are not supported for Android pay. I'm sorry to not reporting before. I have oneplus 3 running oxygen os living in Canada.
[Xposed General] FlemishDroid:
Someone tried the latest version on a Samsung Galaxy S7 international? I use a stock based rom it's called Superman rom but in aroma installer you can choose between stock kernel, modified stock kernel (permisive SELinux) or Super kernel but it says stock kernel doesn't works with systemless Xposed (bootloop) so what can I do? Use modified kernel? Thx.

Sent from my lightning fast SM-G930F (S7)
[Xposed General] gohamstergo:
do a nandroid and try it.....
[Xposed General] -Duir-:
Did you try link in the 2nd post? Worked just fine for me.
[Xposed General] theleftykid:
Installed Magisk, phh SU, wipe dalvik/cahe. Booted to system fine. No issue. Then I installed the xposed v86.4 sdk23 and now it was stuck in First boot Samsumg Note 4 logo. Tried clear dalvik/cache,tried waiting for 20 minutes and still stuck on the same screen. Please help.

I am on stocked ROM and stoked kernel. Clean install via ODIN. I used twrp to flash the zip files.

EDITED: Wait, I think I need to install the -alt one since my unit is N910G. I will let you know the result. :)

UPDATE: I flashed the -alt version and Yay! My Note 4 n910G boots to the system well.. Thanks for all your work.

QUESTION: Will there be no problem if I flash XCEED kernel? Or any of you guys have suggestion which kernel is best for Magisk mod?
[Xposed General] nansah:
Hi guys

I am looking for the link to download Xposed Systemless Uninstaller for Version 86.2, the last one before Magisk was introduced. The current uninstaller version date says 20160804 and it won't allow me to uninstall 86.2 without Magisk installed. I will appreciate if someone can help me to find the link to download a compatible uninstaller for version 86.2, tnx :)
[Xposed General] FlemishDroid:
Deleted

Sent from my lightning fast SM-G930F (S7)
[Xposed General] arnz:
hey someone plz check if it works good in lenovo vibe k5(A6020a40)
[Xposed General] anagramgenius:
Why don't you test it out yourself?
[Xposed General] aer0zer0:
[MENTION=4470081]topjohnwu[/MENTION] Magisk v3 working well on motorola X pure, thank you

---------- Post added at 07:57 PM ---------- Previous post was at 07:57 PM ----------

[/COLOR [MENTION=4470081]topjohnwu[/MENTION] Magisk v3 working well on motorola X pure, thank you
[Xposed General] FlemishDroid:
https://www.dropbox.com/s/q6n5i8v1garzcjl/xposed-uninstaller-topjohnwu-20160718v2.zip?dl=0

Magisk v3 and Xposed 86.4 works on Samsung S7. Big thanks.

Sent from my lightning fast SM-G930F (S7)
[Xposed General] nansah:
Got it! You are a life saver, thanks a bunch :)
[Xposed General] tohtorin:
Few pages earlier my post.
[Xposed General] jer_stud56:
I finally realized what was making my AP not work with 86.x - it was AdAway changing the hosts file in system. I disabled the host file/removed it in AdAway. Downloaded the systemless zip for it, flashed it and then ran the host file download and install in AdAway, and it works.

Systemless zip is here: https://www.androidfilehost.com/?fid=24438995911977059 from here: http://xdaforums.com/showthread.php?t=2190753

Hope this helps someone.
[Xposed General] waylo:
Interesting. Lots of opinions on these threads on if the host file matters for AP. Thanks for sharing.
[Xposed General] dole_95:
I get a bootloop when I install this on my S6 Edge (SM-G925F) with G925FXXU1AOE3 (5.0.2, SDK21) maybe I need the alt-version? I just find it for SDK23 so maybe it doesn't exist for SDK21?

I will send the logfiles via PM :)

How to reproduce:

Flash G925FXXU1AOE3

Install Material Design Xposed Installer

Reboot into TWRP

Flash Magisk

Flash phh's SuperUser with Android Pay Support

Reboot

Reboot again into TWRP

Flash xposed-v86.4-sdk21-topjohnwu.zip

Reboot and you will get a bootloop (it will just show Samsung logo for a minute and then it reboots again)

I guess you can skip the phh's SuperUser with Android Pay Support and the extra reboot to reproduce the problem.
[Xposed General] PokemonTotalWar:
This loads, but the Xposed log is riddled with errors with no Modules enabled. It doesn't seem to cause issues, but I figured I'd report it.

http://pastebin.com/TGFhwePz

EDIT: This is on a Sprint Galaxy Note 3 (HLTESPR) running the Music of Life Note 7 port with Darklord Kernel Note 7 v1.
[Xposed General] -Duir-:
It's also enabled by default in most recent Magisk versions. You just need to tell AdAway to use the hosts in the Magisk folder and not create a symlink. The AdAway app still needs to be updated though because it will say disabled if you don't create the link but it will still work because it already updated the hosts.
[Xposed General] FlemishDroid:
You removed (systemless) SuperSu and (systemless) Xposed before trying this? Restore your stock boot.img. The S6 Edge get already Android 6 I think? The alt version is for some Note variants but you can try. I have a Samsung S7 and for me it works with Superman rom and modified stock kernel (permisive and updated Linux) the stock kernel gives bootloop with systemless Xposed on the S7 but I don't know anything about S6 Edge. On my S7 default encryption is off and dm-verity is removed but again I don't know anything about the S6 I only have the S3, S5 and S7.

What I did on my S7.

- removed systemless SuperSu 2.76 by deleting /data/su.img and /su

- installing Magisk-v3.zip (only V3! this is important because al other versions gave me bootloop)

- installing phh-superuser-magisk-v2.zip

- installing xposed-v86.4-sdk23-topjohnwu.zip

- reboot system

- installing phh superuser app

- installing Xposed Installer app from DVDandroid

Sent from my lightning fast SM-G930F (S7)
[Xposed General] dole_95:
I don't have root before I start so that's not the problem. I have tried to flash Xposed without "phh-superuser-magisk-v2.zip" and I still get a bootloop. Good suggestion about the kernel though, I can try to flash a custom kernel after I flash the ROM and before I start with everything else. Thanks for your reply!

EDIT: After installing a custom kernel I get this error when flashing Magisk: "Your boot partition size is too small... unable to flash

Updater process ended with ERROR: 1

Error installing zip file '/sdcard/Download/Magisk-v3.zip'"

At least I found out that you can flash the boot-partition from TWRP now, so I don't need to reflash the ROM every time I want to try something new!
[Xposed General] gambit1091:
I'm stuck in Huawei Logo.

Huawei GX8 MM EMUI 4.0 C636B310 (Malaysian FW Dual Sim).

I tried installing in this method.

- installing Magisk-v3.zip

- installing phh-superuser-magisk-v2.zip

- installing xposed-v86.4-sdk23-topjohnwu.zip

- reboot system

I used the latest TWRP Recovery for our device.
[Xposed General] Artim_96:
Did you restored the whole system?

If so, try it another time but this time reboot after each flashing action and wait for at least ten minutes since Magisk needs even longer than normal XPosed installations. This way you can find out, which zip is causing the issues.

And please, try to make a proper bug report like mentioned in the Magisk thread.
[Xposed General] slavanar:
Helo everyone i have problem with systemless root. after update my phone to new build i re install Magisk Then flash xposed and root . Xposed work but Root not . Any idea
[Xposed General] dole_95:
Have you installed this app?

https://play.google.com/store/apps/details?id=me.phh.superuser
[Xposed General] slavanar:
Oh thank you now it work am sorry i didnt noticed that App is removed
[Xposed General] ndhusn:
Just to be clear, should I still have to reboot to re-enable xposed after each time I use Magisk to disable root to use android pay? I mean, it's a minor inconvenience but I just want to make sure there isn't a way around it that I missed somehow.
[Xposed General] teddy0209:
Disabling root in magisk does not disable xposed... However, disabling and enabling xposed via Material Xposed Installer does require a reboot to take effect...
[Xposed General] Bonnie1977:
Has anyone tried this on a rooted Mate 7 with Marshmallow? I use AP a lot, so this sounds like a great solution. Especially since I don't want to unroot my phone. ?
[Xposed General] Artim_96:
If you haven't read it (obviously you didn't): 1. If you are already rooted or not is not relevant since you have to remove it and go back to stock before being able to use anything systemless. And 2. I don't know if it is stated in this OP but in the Magisk OP there should be stated that it at least isn't ideal yet. If you want to be able to use AP you have to use phh's SuperUser. And when you want to use XPosed, you have to go into the installer, disable XPosed, reboot (no soft reboots!) and unmount root. Then you should be able to use AP. Should be independent from device. The only real device dependant problems I read about are (of course) with Samsung devices. But they should be already fixed, so I don't see any reason why it shouldn't work if you follow the steps.
[Xposed General] garthybarthy:
I finally got around to testing AP. The first time it said on the card machine, please use another card and the 2nd time I used it elsewhere and nothing happened.

It's all installed and appears to be working correctly but there's still obviously some issues with getting AP to process transactions.
[Xposed General] Vuska:
Hi..

Can someone please help me some information.

I have Note 4 N910G, already rooted, and installed xposed framework alt version.

Can i go with this magisk ?

How ?

Uninstall xposed first ? Or just install Magisk and reflash xposed 86.4 ?

I read first page, but dont really understand.
[Xposed General] legendt:
Samsung TouchWiz 5.0 still stucks on boot. Any chance to support TW5.0 rom just like

[UNOFFICIAL] Xposed for Samsung Lollipop by arter97 does?
[Xposed General] rgawenda:
It would be far easier to flash your ROM again, then phh's systemless root and then this Xposed
[Xposed General] dole_95:
I will try to deodex my 5.0.2 ROM this weekend and see if it helps!
[Xposed General] legendt:
Well, deodex actually breaks /system so you are not systemless right? Even it works, i think it would be meaningless :(

P.S. For anyone who is going to try. Samsung Xposed SDK21 made by arter97 modded by dkcldark v85 works on most odexed tw 5.0.x roms. However when I tried to replace the bins and libs in the OP provided SDK21 version, it still stucks on boot.