yashsingh1/xdaforums huggingface dataset:
[Xposed General] NAKOLS:
I've installed your Xposed on my Nexus 5X with PureNexus 6.0.1 (security updates August 2016), tried with Magisk v12 + SuperSU 2.82 systemless + suhide 0.55 aaaaaaand..... it magically WORKS!!! SafetyNet passes like on the old 86.2!!

Thank you very much :D :D :D

EDIT: I haven't followed the tutorial in README.txt, I've only flashed SuperSU with echo SYSTEMLESS etc., then Magisk, suhide and your Xposed and everything just works, don't know the reason for all those passages like copy dalvik cache and copy 05suhide, can you explain me? Is it better if I do everything again following exactly the guide?

EDIT2: ok, I've read your previous comments, I'm sorry for not doing it before... Anyway, as I said, I've flashed the whole thing without copying any files and no errors on Xposed log nor lag/crashes/slowdowns, seems that I'm very lucky (or maybe it's the PureNexus, I don't really know)
[Xposed General] Didgeridoohan:
The main prerequisite for this to work would be a security patch no later than October 2016. IIRC the current suhide (0.55) does not work on any later patches, unless some manual patches are applied to your device (found somewhere in the suhide thread) or if your OEM/ROM developer have taken care of that.

And, just as a FYI, this is from the OP of the suhide thread:

Maybe use links instead... :D
[Xposed General] NathanBrake:
Oh. I thought you meant you wanted voulunteers with Nougat. I guess it was a misunderstanding, sorry for the bother.
[Xposed General] DragonFire1024:
Question. Has anyone tried to install Xposed on a Amazon Fire HD 8, or any other Amazon tablet WITHOUT root? I installed the installer and it says my device is compatible for the official install and systemless. Just curious.
[Xposed General] Artim_96:
Magisk=root. You can turn it off of course, or what exactly do you mean?
[Xposed General] DragonFire1024:
There currently is no root for any tablets running the most recent FireOS, 5.3.3.0. I also can't get an img file of my device. So I was wondering if anyone has tried to install xposed on any of these devices, regardless of what Xposed it is.
[Xposed General] Artim_96:
There don't has to be any root. What you need is method to fish something. That means either an unlockable bootloader or done other way to install a custom recovery.

But that topic does not belong here. For that you need to go to that devices forum.
[Xposed General] DragonFire1024:
I came here because no one answered me there. Why is a custom recovery an absolute must? Because of the bootloader? All I ever hear is custom this and that.
[Xposed General] Artim_96:
Because otherwise it's simply impossible to flash anything. Only other way would be to somehow root with supersu (which also needs flashing) and then flash through FlashFire
[Xposed General] otyg:
[MENTION=4470081]topjohnwu[/MENTION] can you expand your xposed modules to support MIUI based roms? they latest miui update broke SolarWarez's xposed and looking for some alternatives since I am not sure if he is still active.
[Xposed General] Artim_96:
Only if there is a working one for your device. Topjohnwu only made the existing one systmless, he doesn't create new versions. So this is the song place to ask for
[Xposed General] Dbzfan:
I miss xposed!
[Xposed General] Artim_96:
Then make it yourself or stop complaining...
[Xposed General] Dbzfan:
Someones cranky , just stating something, not complaining.
[Xposed General] post-mortem:
I did, too. In fact, I missed it so much I downgraded to M so I can use Xposed again. :D
[Xposed General] Artim_96:
Can you imagine how annoying af it is if for month non stop people are complaining about that? You can probably continue 'till you are grey but at the moment it doesn't look like XPosed would be continued any time soon. So as long as there is nothing new from rovo, just learn to love that XPosed is possibly dead. And don't go in other peoples nerves about it not existing for Nougat. We all know that and we can't change it.
[Xposed General] bnbagiz:
not working for me .. h815 with lineage os 13 installed, magisk beta v13 tried to install it through magisk interface -> did not work ("xposed is not installed") and tried it through twrp 3.1.1.0 with this attached file from this thread -> did not work ("xposed is not installed")
[Xposed General] Artim_96:
Is it working in v12?
[Xposed General] bnbagiz:
did not test it, because i need the safetynet bypass to be able to use my banking app. the xposed module for that doe not work anymore, so magisk v13 is the only option.. i guess i need to renounce xposed for now..

except someone can tell me why xposed is not working with magisk v13
[Xposed General] Artim_96:
:eek:

Please don't tell me you expect SN to pass with active XPosed...
[Xposed General] bnbagiz:
lol no, thats why i want to stick to magisk v13, just wanted to use some xposed modules besides that. but i realised the tan app is not closing for some seconds.. so magisk's SN pass is not enough to make this stupid tan app working :confused:
[Xposed General] grymkmb:
Can you use an older version of the banking app?
[Xposed General] bnbagiz:
Sadly no :-/ the company doesn't allow to use older versions
[Xposed General] lover:
you can use v12 and this magisk's module: https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431 to bypass SN
[Xposed General] tdurdenn:
Gotta figure out what suhide does to allow xposed to work with root toggled off. Create that just for xposed profit.
[Xposed General] Mizen:
Rocking! Thanks [MENTION=4470081]topjohnwu[/MENTION]http://cloud.tapatalk.com/s/594d21c7b432c/Screenshot_20170623-220306.jpg?
[Xposed General] phnord:
I'm confused; will this module in Magisk v13 pass SafetyNet? If not, is there a way for me to currently pass SafetyNet with Xposed enabled, and if so how? What Magisk version / Xposed version / additional modules / additional software will I need?

(Fwiw, I'm on LG G3 Fulmics 7.6 ROM [MM-based], and it passes SafetyNet with Magisk v13, but not once I add this Systemless Xposed module)
[Xposed General] steve51184:
only way to use root and xposed and pass safetynet is suhide
[Xposed General] lover:
xposed v87 wont let you pass SN, but Telperion made some modifications, here: https://xdaforums.com/showpost.php?p=72548221&postcount=3932

you can give it a try only install the modified xposed module and see if it works

if you are using magisk hide then there is no need for SuHide which does not work anymore
[Xposed General] Didgeridoohan:
If you're going to use that workaround you

have

to use suhide, which in turn means you have to be on security patch October 2016 or earlier.
[Xposed General] slayer.1942:
Hello guys

I have a samsung s7 at&t unlocked, I wanna throw it to trash.

I wanna buy a phone that has lolipo android 5 and is the best candidate for rooting with Xposed and be able to install [Xposed] Security Bypasser afterward.

what phone do you suggest?

I wanted to buy moto g4 cause it s a good phone with low price! is that phone smoothly support xposed??

thx
[Xposed General] lover:
yeah SuHide needs root by superuser and on security patch October 2016 or earlier. with all powerful access xposed gives i wonder why no1 makes a xposed module to fake some stuff to bypass safety net

don't throw it to trash give it to me ? ;)

xposed works just fine in Marshmallow no need to have lollipop! you can buy OnePlus3T its the last device which can be downgraded to MM (ships with MM but maybe some with N) also it has very suitable price and 6gb Ram / 128gb storage....
[Xposed General] phnord:
I'm on Fulmics 7.6, which comes with Android Security Patch Level February 2017 :/

Is there no way to use that workaround, then? Is there any other workaround that I can adopt – perhaps a SuperSU one that I keep hearing about?
[Xposed General] Didgeridoohan:
That is the SuperSU workaround...

Look in the suhide thread. Not too long ago I put a link there for a thread with some patches you could apply to possibly make it work on later security patches.

Other than that, it's pre November patches only...
[Xposed General] phnord:
So to be clear, then, I should migrate *away* from Magisk over to SuperSU if I want to go that direction? There's no need / reason to have Magisk if I'm doing this with SuperSU and suhide, right - that would just be unnecessarily (and potentially problematically) redundant?
[Xposed General] Didgeridoohan:
Did you even take a look at the link [MENTION=288641]lover[/MENTION] posted? Do that...

FYI, that guide won't work with Magisk v13+ (SuperSU compatibility removed).
[Xposed General] phnord:
I missed the guide; thank you for calling that to my attention! Will do :)
[Xposed General] KostWarCZE:
OPT LineageOS 14.1 android 7.1.2. SDK25 arm64-v8a

Is there anyway how to run it or exposed in general on OnePlus TWO with LineageOS 14.1 (Android 7.1.2.) with SDK25 / ARM64-v8a ?

(xposed with material design supports sdk23 max as far as i know)
[Xposed General] Didgeridoohan:
And that's as far as it goes. So the answer to your question is: no.

Edit: information that you probably would have been able to find by just browsing the Xposed forum threads... It's one of the most talked about topics in here.
[Xposed General] Artim_96:
Yes. Just write it yourself.
[Xposed General] TimmyTimz:
Hello,

Can I use SDK 23 with my rom?

Please view attached screenshot.

PS: I already have Magisk installed, I'm on this thread thanks to it.
[Xposed General] grymkmb:
You're running a Nougat Rom, so Xposed for SDK 23 will not work on your Rom. If you want Xposed, you need a Marshmallow Rom.
[Xposed General] TimmyTimz:
Hello,

Thanks for letting me know, I'll stick with my Nougat Rom ?
[Xposed General] Didgeridoohan:
Wow... That's one of the most obnoxious and intrusive signature I've ever seen.

Edit: Any reason you keep it so big (almost 1300x500 px)?
[Xposed General] TimmyTimz:
Is it really? ??

The signature about Jellykat Rom? I haven't changed my signature in years lOl, I've only just started using this site again thanks to finally getting an S7 Edge after my Note 2 packed up a while back.

I don't even recall how to change it, it was my mate that helped me out with my signature back then.
[Xposed General] Didgeridoohan:
:laugh: Yes it is and that's the one... Open up the forum on a computer and you'll see.

Forum options, in the XDA control panel - Edit signature.
[Xposed General] EViollet:
https://xdaforums.com/profile.php?do=editsignature

Please. ;)
[Xposed General] EngineManShawn:
This is my 1st Run at Majestic and Systemless Root. This is all trial and error for me. Can someone please point me in the direction of privacy and Xposed. Please, I am on LineageOS 7.1.2 using an S4 L720T Sprint. I like what I'm seeing just don't understand the entire concept YET. I don't want to go back to what I know ( lollipop and below) cause nobody will give any type of good advise or help. So sick of trial and error!:crying: Can I have a hand please?
[Xposed General] fake2die:
No..

Because no Xposed for nougat (Android 7) for now..
[Xposed General] wbdy95:
My ZUK EDGE brush the card screen ....
[Xposed General] Naudiz:
Is anyone successfully running systemless xposed on latest Magisk13.1?
[Xposed General] elhennig:
Which system?

There is

no

xposed for Nougat!
[Xposed General] Chainfire:
I don't run Xposed so I haven't tried anything, but aside from the points you raise yourself in the OP I have some comments:

(1) sukernel. Why are you including sukernel in the package? It should already be installed by SuperSU into /su/bin? Expect issues with this in the future.

(2) /su/lib: I see you are using both /su/lib and /su/lib64. /su/lib should be used for max-bits binaries: 32 bit on 32 bit systems, 64 bit on 64 bit systems - not 32 bit on 64 bit systems. Please use /su/lib32 and /su/lib64 instead if that fits better with your setup.
[Xposed General] :
Systemless SU

I hope you'll excuse the nube question, but where can I find Systemless SU? I'm currently running v2.65 Pro on MM. I have NOT selected "Install SuperSU into /system" ... does that mean my setup is Systemless?

---------- Post added at 10:15 AM ---------- Previous post was at 10:09 AM ----------

Damn! To think I was just about to install this ... I'm now glad I read the rest of the comments. It seems that there's still more work to do to make it polished. I'll keep my eye on it ... great work though =)
[Xposed General] romracer:
1) Easy to fix.

2) This replicates the setup already in place by Android itself on your /system partition. The libraries in /su/lib (or /system/lib in a non-systemless Xposed) are used by the 32-bit Zygote (and some of the *oat tools in /system/bin). The same is true of the libraries in /su/lib64 or /system/lib64; they are used by the 64-bit Zygote. Android has no /system/lib32 (at least my Nexus phones don't). Are you proposing the layout set forth by Android should be abandon when placing files into /su's file system?
[Xposed General] masterv1:
Installed it on s7 edge. Xposed is working, but I can't test if android pay is working (can't install it through play store).

When I disable xposed then all xposed apps aren't working after reboot.

Gesendet von meinem SM-G935F mit Tapatalk
[Xposed General] Mr.Yawnie:
Of course the xposed modules are not working when xposed is disabled.. That's the definition of disabled = not usable. The option to disable xposed is there to (possibly) get android pay to work. Right now it's either or. The advantage of this systemless xposed is that it only requires quick reboot to switch between on and off, and not uninstalling whole xposed framework from system, which then causes all apps to optimize, which in turn takes time.
[Xposed General] Chainfire:
/su was created for SuperSU, what the layout is in /system is irrelevant, it was never meant to reflect /system. SuperSU installs the most-bits version of its tools (32-bits on 32-bit devices, 64-bit on 64-bit devices) in /su/bin and /su/lib. It has never made the distinction because there's always only one version installed.

I am not proposing anything. I am simply warning that this can potentially end up mixing 32-bit and 64-bit libraries in the same folder, which is a jolly bad idea, and it will at some point end up making some binary malfunction. A work-around is using lib32 and lib64 instead (or if the entire folder is going to be bound, lib32_bind and lib64_bind).
[Xposed General] WhammyDroid:
Thanks for creating this! Will the systemless changes be submitted to rovo89 for consideration?
[Xposed General] LuanTeles:
Now my bootlogo says kernel is not enforcing!

how to get rid of it?
[Xposed General] JohnCorleone:
I am very excited that you put this together and that you have the HTC 10 (as I do) so I know that everything will work if I properly follow the steps. Are you s-off or s-on? Also did you change CID and/or MID? I am looking to keep my T-Mobile firmware (for now) because I got the 30 channel Sling TV package for $13.99 a month and I want to keep that discount! I am bone stock because I was pretty much hoping that this would come along... HUGE THANKS for your work! :svetius:

---------- Post added at 01:15 AM ---------- Previous post was at 01:08 AM ----------

Did the developers ever get Xposed working on the S6 or S6 Edge? I am not being a smarta$$, I just remember a period where it wasn't playing nicely with Samsung's ART modifications
[Xposed General] Cass67:
Nice, seems to work on LG G5..
[Xposed General] JohnCorleone:
Sometimes you can add a card but it won't work when you go to pay. This is as far as people got using Xposed and Root Cloak module before these new goodies came along.

---------- Post added at 01:26 AM ---------- Previous post was at 01:24 AM ----------

Did you actually use Android Pay to buy something or just add the card? If you already tested paying, I am getting everything ready as soon as I get back home!
[Xposed General] romracer:
Sorry, I'm not trying to be obtuse, it was a genuine question. As the options for "system-less" things expands, I think these are valid questions so that we can be sure to all follow the same guidelines.

If no special meaning should be held to the layout of /system, then its no problem to use /su/lib32 and /su/lib64. Perhaps it adds additional complexity to falling back to /system/lib (when relevant) but only trivially so. I guess in hindsight SuperSU could have used /su/lib64 when appropriate, but SuperSU's implementation should be treated as a blackbox anyway (imho) so we shouldn't expect SuperSU to fit "our" patterns.

Regarding mixing libraries, can you elaborate? Is it possible for the dynamic linker to load a 32-bit library into a 64-bit binary (or vice-versa)? I've never had luck with that. Additionally, unless these /su/lib* paths are being added to every process's LD_LIBRARY_PATH, how is the linker ever going to even find them? Remember, at least for Xposed, the libraries placed there are bind mounted to /system (where the linker is actually looking).

Lastly, regarding lib32_bind and lib64_bind, are these documented anywhere? I find nothing in Google for them except for your earlier post today. They seem like what we really want anyway (at least here).
[Xposed General] Cass67:
Not used it yet, added card only.

Though have found an issue, after disabling xposed via toggle and rebooting it appears that the toggle has gone to re-enable xposed, installing the same framework or installer app seems not to fix it. Installer sees framework is installed but just not active.. Dunno what im missing here..

Edit - not missing anything, its a bug. Post 751 on material design installer thread describes this toggle behaviour.
[Xposed General] RobboW:
Installed this to my Oppo Find 7 (arm 32 bit) running OmniROM 6.0

Working nicely!

Will be interesting to apply the next full Omni update and see what survives.

I don't care about Android Pay.
[Xposed General] Sapphire999:
Did anyone test it on Samsung touchwiz?(in my case galaxy note 4)
[Xposed General] topjohnwu:
Thanks for the heads up! I learned a lot from your systemless SuperSU, also shamelessly "borrowed" your ramdisk patching binary to save a lot of headache unpacking/repacking boot image :D. Here I'll answer the questions

The flashing script will also handle the case that /data is not able to mount, such as devices with proprietary encryption that TWRP cannot decrypt correctly. I'll create /cache/su.img if /data/su.img and /cache/su.img are both not found, and place the files over there. I this case, we cannot access the sukernel installed into su.img. Then the mount_xposed.sh should merge /cache/su.img to /data/su.img (the same thing you've done in launch_daemonsu.sh).

What are the disadvantages including the binaries in the package? May you tell me the potential issues that might happen in the future?

Just like what [MENTION=2476451]romracer[/MENTION] said, I reflected the layout of /system, so that the flashing script is easy to write. I can separate the library installing commands with their own functions, but I don't see what will really cause problems. I bind mount individual files in the folders, not mirror the whole directory into system. If you're really concerned about the issue, a better way is to put all Xposed released files into a directory, and reflect system folders as subdirectories in that folder (so I don't have to massively change my flashing script).

Again, many thanks, Chainfire :)
[Xposed General] nansah:
Did you figure a way to let it show? All the pictures I'm seeing seems to be only showing on the 64bit version but not the 32bit version like OPO......

Any thoughts?
[Xposed General] topjohnwu:
Nah... maybe I forgot to update xposed.prop in the arm version.

If everything is working fine for you, then it's good. v85.0 and v85.1 only differs in the flash script, the files are the same.
[Xposed General] nansah:
Thanks for the clarification, I appreciate that ????
[Xposed General] ahrion:
I already have the official xposed installed with systemless root. Can I just use the official uninstaller and then flash this? Or is there another protocol besides doing a complete wipe?
[Xposed General] loogielv:
Yep I even made a video of it let me see if I can't edit out my info post for you
[Xposed General] koko115:
I try. And still no working.
[Xposed General] topjohnwu:
How about this one?
[Xposed General] boldie007:
On my S7 edge xposed seamless is working since the first release.

But just if i root with CF autoroot. If I unroot with TWRP and SuperSU the device is unroot but xposed seamless never worked (and i was not able to encrypt the storage)
[Xposed General] koko115:
Still dont work
[Xposed General] topjohnwu:
And is v85.2 working? Please check.

It's impossible lol, I literally just added the 85.2 script back :p:p
[Xposed General] topjohnwu:
Oh, forget to ask.

Is the /data readable from TWRP on S7? This might be the issue :)
[Xposed General] boldie007:
For info.

V85.3 is not working on my S7edge.

V85.2 is working fine.
[Xposed General] topjohnwu:
OK, thanks for the clear confirmation

Will you please upload a full bug report as stated in the OP?

This will help a lot :)

S7 should be the last piece of the puzzle, hope I can fix it
[Xposed General] loogielv:
Okay I am confirming Android pay works. I have system of routes I have system list Xposed and I am running n920t with Jovi's awesome awesome deathstalker Rom.

Edit:

Pretty funny that Android pay works but Google voice to text is not the best :)

I have systemless root and systemless Xposed
[Xposed General] idbl_fanatic:
What is the newest build number that this works with?
[Xposed General] Artim_96:
It should run on any Android 6.0.1 system (except for Galaxy S7 for now), independent from build numbers since it's very unlikely that Google tries to "patch" that before the N release. And when all 6.0.1 devices are supported, there will be a version for 5.x
[Xposed General] Nodens:
85.3 and 85.4 tests not working on S6 Edge+ as well. 85.2 does.
[Xposed General] topjohnwu:
Samsung users please provide a complete bug report!!

I really want to fix this :p:p, but in theory if v85.2 is working, than my previous test builds MUST work.

It should be some other factors that I've missed. I need recovery logs, boot image, and boot logs, thanks!!
[Xposed General] bizaff:
FYI - I installed the June images on a Nexus 5x, then systemless root and xposed. When I got the Material Design Xposed Installer in, the framework reported the right version (85.3 systemless for me), but showed "Error loading Xposed Zip frameworks". After some tinkering, it appears the installer needs internet access to ping a few sites. (I have Xprivacy and AFWall+ running) Once I let the Xposed Installer through, the error went away.

This looked concerning at first but it's not really.. I think the Xposed Installer should give a better error.
[Xposed General] Bajanman:
Ok I'm posting after flashing a new Rom with systemless root included.

I was having a few problems at first getting the framework to actually work right. So I decided to start over with a fresh install and to my surprise everything is working perfectly. I will post what I have on my phone and what I did.

Device>910c

Rom>DN5 .06 with stock permissive kernel

Super su 2.7.1

85.3

Xposed installer from the Op

My install instructions:

After briefly setting up my the Rom. I rebooted to Twrp recovery flashed 85.2 and waited for the phone to boot up and upgrade the system.

Then go to your file explorer of choice and install the Xposed installer from the Op. Rebooted once again, then opened the installer too see 85.2 in green. At this time I tried to switch off Xposed and rebooted from the installer. After the phone booted up nothing changed using the toggle switch. So I noticed the update for 85.3 and was hesitant to install the new version thinning soothing might get messed up. So I made a backup of my working system, and flashed the 85.3 rebooted and found 85.3 installed OK ?.

Now 2day while at work decided to mess with Android pay too see if it would let me go thru the set-up process. Yes it passed!

[MENTION=4470081]topjohnwu[/MENTION]

I have to tell you thank you very much for your work. I'm a VERY happy guy!!

Having Android pay and my modules working in prefect harmony is priceless.

Look below>>

Regards,

Bajanman