yashsingh1/xdaforums huggingface dataset:
[Xposed General] Artim_96:
Very strange. The v86-alt is the first one that seems to refuse to install... At least it does not recompile art-cache.

I already flashed the system a few times new because yesterday I didn't realized at first that I still had to wait for the alt version, to 85.7 should be definitely gone, and I already deleted the xposed.img from /data. And even flashfire didn't seem to have any problems.

Here are the logs by Liveboot and FlashFire.

EDIT: under /su I have the folder xposed, its subfolder system and its three subfolders bin, framework and lib, but they are empty.

Permissions for xposed and all its subfolders are drwxrwxrwx. SuperSU 2.76 is installed of course.
[Xposed General] jujak82:
After full wipe i still have the following error: xposed v86 installed but not active, please check log...

And in log...it says log cannot read error.

Plsss help.

Thx in advance

I have supersu 2.76 installed
[Xposed General] teddy0209:
Did you install the apk from the OP? The one moded for v86?
[Xposed General] jujak82:
yes, i installed that one.

i am on nexus 6p and xtra rom, never had an issue with xposed till now.
[Xposed General] teddy0209:
Did it flashed ok, can you see the xposed files in /su?
[Xposed General] jujak82:
nope i dont see xposed in su.

should i flash it again?
[Xposed General] teddy0209:
Yes, and save your recovery log just in case so you have something to post here... [emoji6]

Edit: start with supersu2.76 with reboot in between
[Xposed General] 洛城天使:
I really want try it , but I can't download it , form China
[Xposed General] teddy0209:
Try different browser, or xda app from play store...
[Xposed General] Yokisen:
Is it available for one plus2?
[Xposed General] Yokisen:
Which version should i choose?

I couldn't find arm64 system less.
[Xposed General] Semtronix:
Anyone having issues where the app says it doesn't detect the framework, reflash your kernel (boot.img), flash SuperSU 2.76, flash v86 Xposed. Fixed it for me using Franco on stock 6P.

It's an all in one installer. It has every version in one file. Just download it from the OP and run it.
[Xposed General] jujak82:
IT WORKED :d

THXXX
[Xposed General] teddy0209:
Good... Glad it worked for you...
[Xposed General] 洛城天使:
can't download it ,someone could upload it to http://yun.baidu.com ？
[Xposed General] topjohnwu:
Maybe I messed up something.

Will check now.
[Xposed General] teddy0209:
How are you trying to download it? Try different browsers... Or try xda app from play if you're using phone...
[Xposed General] enotar:
Any idea on when sdk22 will be out? Tkz
[Xposed General] moriel5:
It will take some time, check a bit back on this page for the details.

And try reading at least the last three pages before posting, the answers are generally there already.
[Xposed General] di3cbl:
Is there any danger with using Android pay with root and xposed? I was wondering if for example some malware could potentially steal credit card information much more easily.
[Xposed General] GXGOW:
As long as you don't install any malicious apps, there shouldn't be any problem AFAIK
[Xposed General] Artim_96:
Well, you should already have learned to only install apps from trusted sources, otherwise it would be already careless to even consider root out even XPosed since they are kind of "Chuck Norris modes". But I'm very sure Google already did enough to ensure there are as less possibilities as possible to steal any information. That's why credit card information is never transmitted for payments, only cryptographic tokens. And Google has even its own "anti malware suite" on most devices (at least if you have Google play services installed) to detect known malware... Besides their numerous additions to Android like SELinux, Address space randomization etc.

About every year security researchers make oh so critical security issues to draw attention to their not working software, but if you wait for month you never really find any real world issues.

So the chance to catch something that it more than adware is very low as long as you don't load your stuff from very questionable sources is extremely low... And just never give root rights respectively activate modules if you don't really trust the app and know what it was to do
[Xposed General] aldanopolis:
I have one issue, when I install always do in system mode, but I have systemless root. When I check the installer, I note it the Comprobation, and my phone have cyanogenmod, and this ROM have su in system/xbin.

Enviado desde mi Moto G mediante Tapatalk
[Xposed General] topjohnwu:
Fixed the scripts (haven't released yet) :)

New update with improved scripts will come soon (source already updated)

SDK22, SDK23, and alt version will come with the next release.
[Xposed General] Artim_96:
So better wait for 86.1?

Thank you very much by the way:good:
[Xposed General] an0therus3r:
Same here: (OnePlus One)

ROM: cm13.0-ZNH2K-20160624-Sultan-bacon

Xposed Installer 3.0 alpha4 by dvdandroid - 23/06/16

Xposed: xposed-v86.0-sdk23-topjohnwu.zip

SuperSU: beta-2.76

Xposed Installer reports: Xposed Framework is not installed but all seems to work fine.
[Xposed General] gdecker:
From recovery I reflashed the boot partition. Rebooted. From recovery reflashed supersu. Rebooted. This killed the framework. Reinstalled the latest xposed installer. From pulldown chose v86 alt and let it do it's thing. All is well. Thanks [MENTION=4470081]topjohnwu[/MENTION].
[Xposed General] kalapapa:
Try to uninstall the xposed installer and install the newer version from op

Then reboot phone, check all modules switches, reboot again, and everything should work
[Xposed General] sd3993:
SuperSU 2.76 successfully installs in systemless mode but xposed v86 says system root install detected. 85.7 successfully installs in systemless mode

---------- Post added at 07:55 PM ---------- Previous post was at 07:49 PM ----------
[Xposed General] Fangs87:
Also getting the systemless is installed but not active, but amy modules are not checked or enabled and I cant enable them.
[Xposed General] Artim_96:
Sure that you installed the modified XPosed installer? Otherwise maybe try deleting app data.
[Xposed General] Fangs87:
Yea installed mod installer and mod xposed app from op.

tried deleting app data still nogo.
[Xposed General] AndKacz:
Since there is a lot information in this thread I am just looking for some clarification.

Currently running, non-systemless Xposed (v85). From what I've read, I should uninstall existing framework and installer app, Flash stock system.img, install the modded Xposed installer and framework and that should be it or am I missing anything?
[Xposed General] moriel5:
I had never uninstalled the old one.

Just installed the modded app, and immediately afterwards flashed the new framework.

An additional soft reboot was required to make it work properly.

But others seem to be having problems.

Edit: Yes, you do need to uninstall it, somehow I had missed the "non".
[Xposed General] teddy0209:
Flash supersu2.76 before the framework...
[Xposed General] AndKacz:
I have SuperSu 2.76 installed currently, would I still need to install it? I guess it doesn't hurt to flash it again.
[Xposed General] teddy0209:
You're restoring system.img as you said, it is better to start clean to avoid possible problems...
[Xposed General] sorewinner:
Yep. Me, too. I rolled back to 85.7, until this is fixed. I'm running CYM 13.0, which has Privacy Guard. Maybe that's what v86 is seeing as "system root".
[Xposed General] AndKacz:
Duh, of course! Sorry about that, my brain doesn't want to work properly today.
[Xposed General] santanah:
Systemless v86 works perfectly fine one opo3 with oos321. Thanks for your work!
[Xposed General] koko115:
S7Edge works SUPER ;)
[Xposed General] ren0.1:
[MENTION=4470081]topjohnwu[/MENTION] , I've now wiped the data for the Xposed installer, rebooted, wiped the ART cache - because the systemless uninstaller and the v86.0 installer didn't do that - and brought the phone back up. The Xposed installer still claims that the Xposed framework isn't installed at all. All of my Xposed modules are working, however - and I know that the sdk23 systemless v86.0 release is installed, because I installed it.

Is this a bug in the twice-modded Xposed installer?

Please help.
[Xposed General] topjohnwu:
1. Restore your boot image back to stock

2. Flash SuperSU 2.76

3. Flash Xposed

This should definetely work :)
[Xposed General] Captain_Throwback:
Actually I've tried this on my HTC 10, and I have the same issue that the others are reporting. The app tells me the framework is installed, but not active. The "Log" area of the app tells me it can't read the error.log. All of the files appear to be in the right place, but it's just not working for some unknown reason. I'll grab a logcat after I get back from lunch and maybe that'll help figure it out.

One thing potentially noteworthy - I have a pattern set up on boot on my encrypted device. I might not be able to get a log early enough, but I'll give it a shot. LiveBoot doesn't appear to work with the password set on boot.
[Xposed General] topjohnwu:
So my previous own modded boot release handles this without issues.

This is very likely to be an SuperSU issue. Will need to investigate more.

Can you pull a boot logcat for me?
[Xposed General] Dudash:
I may have figured out the problem.. or at least part of it. I was trying to install v86 through the only TWRP for the VZW Galaxy S5 that can read the SD card which is the only one I use for obvious reasons, 3.0.2-0. I figured I'd try to install it using one of the versions that don't recognize the ext-sd card, 3.0.2-2, and it flashed fine.

Why is it that noone can compile a version that recognizes all scripts/flashes all zips fine and that can also read the ext-sd card? >.<

Anyways, it flashed fine, but when the phone booted, it still said Xposed wasn't installed through your modded Material Xposed Installer apk.

I decided to start over (again), flash stock, delete xposed.img from/data, flash SuperSU 2.76, then flash v86 through the version of TWRP that it actually flashes through.

If that doesnt work, I may just try what I should've tried when it wouldn't flash through TWRP the first time, using FlashFire.

Phone just finished flashing stock through Odin and is optimizing, but I'll keep updating with progress.

UPDATE:

After flashing TWRP 3.0.2-2, SuperSU 2.76, and your Systemless Xposed v86, the phone booted and it is indeed active in your Modded Material Xposed Installer.

Thanks for all the great work and hope you can get the script working in all versions of TWRP!
[Xposed General] Rhazi3l:
I got a OP3. Did a clean full rom install of Oxygen 3.2.1 and SU 2.76.

Rebooted, went back to recovery and flashed xposed v86. Rebooted again and installed the mod version of xposed installer for v86.

Everything is working as it should, but it doesn't say it's systemless and from the framework drop down on Xposed Installer there is no option for v86 systemless.

Is there anyway of checking if it's installed as systemless or not?

BTW great work =)

EDIT:

Solved already. For some reason it wasn't detecting /data/su.

Reinstalled SuperSU, uninstalled Xposed and reinstalled it again. Now it detected fine and it's systemless :)
[Xposed General] ianmacd:
v86 systemless installs perfectly here on my S7 Edge (G935F) and S2 Tab (T710).

Many thanks for the continued work on this, [MENTION=4470081]topjohnwu[/MENTION].

As we now know, systemless installation is planned to be officially supported from v87 onwards, but that will still leave Samsung users out in the cold. Will you continue to create Wanam-based systemless builds in the future, or do you see your work as finished once systemless is officially supported?

I'm just curious whether those of us who use Wanam's builds may have to return to system-based installation in the future.

Cheers again for all the hard work.
[Xposed General] Captain_Throwback:
Logs and screenshots attached. Hope they help!
[Xposed General] gaganit:
A side question..

How to enable tethering (Nexus 6) without modifying build.prop? I believe modifying build.prop would change the system hence making it pointless to have system less root and xposed
[Xposed General] Artim_96:
You should ask that in a Nexus 6-specific forum.

But yes, as one of the next projects it would be great to be able to apply changes like the ones on build.prop and installing apps as systemapps without modifying /system in a simple way, at least if that's possible. I don't think that I understand what's exactly going on to enable systemless root/XPosed enough to say if that's even possible.
[Xposed General] aer0zer0:
Works perfect here on my 10
[Xposed General] Cares:
Super buggy on my N6P. Seems like every other restart (random) it won't detect that Xposed framework is installed. Didn't have this problem with the previous version.
[Xposed General] topjohnwu:
Thanks for the logs :)

It's a SuperSU problem, I'll report to [MENTION=631273]Chainfire[/MENTION]. More details please look at my post in SuperSU developer thread:

http://xdaforums.com/showpost.php?p=67721540&postcount=55
[Xposed General] sansnil:
I had to re-flash the stock AOSP MM kernel to get the new version to take on my N6 which I don't normally have to do with a new version and the new framework isn't detected either. Oddly, all my modules appear to work and so far I have had any random restarts.

I know topjonwu is already on this with chainfire so just reporting if helpful (I don't use secure boot).
[Xposed General] LuanTeles:
on NOBLE UX N7 BASED ROM on galaxy s6 edge it says installed but not activated, systemless su 2.76
[Xposed General] teddy0209:
Try it again...

Reflash supersu, this will restore your backup boot.img and repatched it... Reboot check if su is working, then Flash the framework...
[Xposed General] OT-Xtreme:
sounds great tnx
[Xposed General] Zulake:
I have exactly the same issue on my S7 Edge.

SuperSU Pro v2.76 is installed as stated in OP.

//Edit: Never mind, I reinstalled it from within the app and now it appears to be working. Guess something didn't flash right.
[Xposed General] Fangs87:
Same issue i'm having, looks like im not the only 1.
[Xposed General] legendt:
Thank you for the great news! :good: When will we have SDK22 version? My manufacture won't provide 6.0 updates .
[Xposed General] hgoldner:
[MENTION=5447216]aer0zer0[/MENTION], did you have to remove 85.7 or were you able to go right from 85.7 to 86 on your 10?
[Xposed General] aer0zer0:
Clean install, I borked something in my rom, so I updated the rom zip to 2.76 supersu, and just collected the systemless updates and flashed it all clean. I don't see why it wouldn't work to just update.

---------- Post added at 05:12 PM ---------- Previous post was at 05:11 PM ----------

Is it not working via standard update?
[Xposed General] crumble6:
I can't seem to figure this out either - the toggle switch that was there to disable Xposed is not there to re-enable it.
[Xposed General] teddy0209:
Just restored system img on my M9, to try this... It works as it should!!! Will be tracking this... Thanks for sharing mate!!!
[Xposed General] -leo-:
awesome! will there be official release.......lol
[Xposed General] Cass67:
Seems to be a bug just now with the current version. Delete the xposedinstaller dir on sdcard .. Its named something like that and reboot and it will come back.
[Xposed General] ryanguy426:
Not working with Dirty Unicorns 10.2 (6.0.1), Nexus 6. Systemless Root, Systemless Xposed.
[Xposed General] topjohnwu:
Just applied OTA on my 10 without even restoring the boot image :D

Received notification, pressed download and install ---> Done!!

All smooth and clean, systemless is so nice :)
[Xposed General] teddy0209:
Use the 85.1
[Xposed General] ryanguy426:
That's the ZIP I flashed. It shows up as 85.0 in the installer though.
[Xposed General] teddy0209:
Oh, my bad... i have arm64 device and shows 85.1... Just post a log as stated in the OP for them to help you better...
[Xposed General] ndhusn:
I deleted the folder and rebooted but the toggle switch is still missing. I'm on a Nexus 5X, fully updated.
[Xposed General] Ja_som:
Do what those red lines say...
[Xposed General] ryanguy426:
The log file doesn't exist according to the log tab in the installer. Also manually checked with Solid Explorer and the log folder is empty.
[Xposed General] Ja_som:
Without log, no one can help you...
[Xposed General] Cass67:
Try removing the app and installing it again. Dont think it impacted me this but this was one additional step i did before i removed the folder.. I have toggle and this was all i done.
[Xposed General] ndhusn:
Thanks, that worked. I guess I'll have to wait for an update...disabling Xposed, rebooting, using Android Pay, deleting Xposed folder on SD card, uninstalling Xposed installer, rebooting, installing Xposed installer, enabling modules, and then rebooting is a little more work than I'm willing to do when I could just pull out my wallet. :)

It's awesome to see the dev is on the right track, though!
[Xposed General] topjohnwu:
That might be some bug in the Xposed Installer, I cannot fix it :D:D
[Xposed General] sovanyio:
Hm.. the installer is not seeing the framework.

Verified the files are in /su and double checked the disable file (which is not there) but there are still no logs and no toggle.
[Xposed General] Kellwa:
It's working for me (htc desire 820)

XStana module not detecting xposed but it's working

First time after a lot of lagging in every thing but now it's better

Every time i boot it shows (android is upgrading: starting apps) and takes a bit long time
[Xposed General] SpasilliumNexus:
/data/data/de.robv.android.xposed.installer/conf > delete "disabled" > reboot
[Xposed General] Cata98:
Have anyone tried with the nexus 5 (hammerhead)? i've flashed as the guide said but it's still booting! (10-15 minutes).
[Xposed General] hgoldner:
I flashed v86 over 85.7 (I'm on systemless rooted stock Verizon 10, which is still 1.19 based) and the app still shows it's running 85.7. Nothing's wrong; all the modules are working, so I'm not inclined to press the issue.
[Xposed General] PHYCLOPSH:
Will Xposed v86.0 break compatibility with CM13 using it's built-in root, not SuperSU?

(flashing SuperSU results in bootloop/secureboot error for me with CM13)
[Xposed General] aer0zer0:
I have flashed over top of various 85.x versions with no problem. That is good to know then. Are you using the deodexed base, or working directly off the update?
[Xposed General] hgoldner:
"Pure" stock, post [MENTION=711482]beaups[/MENTION]' magic trick for Verizon 10's. Never flashed another ROM, just TWRP and systemless root, then Xposed. When the 1.8x OTA finally comes down (I've been running it on a test 10 for weeks now), I'll just go back to stock recovery and take the OTA, then reroot and reflash Xposed.
[Xposed General] aer0zer0:
If it wasnt for the powersaver mode by default in [MENTION=2586080]andybones[/MENTION] deodex base, thats what i would be on. Highly recommend tbaldens kernel for our base FYI.
[Xposed General] JimSmith94:
Is anyone else getting constant Facebook force closing on this latest version, like I am and as Captain_Throwback mentioned in this SuperSU developer post? http://xdaforums.com/showpost.php?p=67728560&postcount=59
[Xposed General] teddy0209:
It's not ok to just flash the update (it's not just an ordinary update)... The previous version has it's own img in data and patches the boot.img while the new v86 installs directly inside su img and does not modify the boot.img... So in order to properly install v86, you have to reflash supersu (this will restore your backup boot.img and repatch it), then flash the v86 framework (with reboot in between flashes).
[Xposed General] hgoldner:
Is a reasonable alternative to restore a Nandroid of stock boot.img (assuming that I have one, which I do), then reflashing supersu, then reflashing Xposed, or do I need to remove Xposed first?
[Xposed General] teddy0209:
Yes you can restore the stock boot.img manualy then reflash supersu and then xposed... (just remove the xposed.img in /data if it is still there, you can also do that in twrp's file manager)...
[Xposed General] beaups:
Magic trick?
[Xposed General] hgoldner:
It's magic to me, [MENTION=711482]beaups[/MENTION]. :o
[Xposed General] puneet724:
I am getting Facebook force closures after installing 86v
[Xposed General] toddre:
Yes, and after some reboots inactive too
[Xposed General] topjohnwu:
v86.1 Update!

This update contains some script improvements. Uninstaller is also updated.

Everything is now re-compiled with proper compiler tools on my computer, might fix some issues with ART.

SDK 22, SDK 23, alt versions are all live.

Updated OP with proper installation instructions, people with issues please follow them before reporting (the boot image part is important!!)

Also, SuperSU might have some minor issues with bind mounting, especially if you use encryption with PIN code required on boot (secure boot).

I won't roll back to my previous methods (rock solid, but requires boot image modification). My aim is to release a version using techniques which will exist in future official releases. So if you really ran into issues, you have to wait for Chainfire to update SuperSU, or download v85.7 in second post, that release have the best systemless support anywhere on XDA now. However, always use v86+ version if possible.
[Xposed General] topjohnwu:
And the #1000 post is mine :)
[Xposed General] SyCoREAPER:
And well deserved.
[Xposed General] jujak82:
I flashed version 86.1 but after restart it says i am still on v86.0. am i doing something wrong. Should i unnistall v86.0 first?

Thx in advance
[Xposed General] knpk13:
Does systemless xposed have any benefits for custom Roms?

I'm on CM. Is there any way to force a systemless install with v86 and up? Because the in built superuser gets detected( I assume?) and system xposed gets flashed, even if SuperSU 2.76 is installed.

I could install systemless in 85.7, though I realize that was because it patched the boot.img, and you explained your reasons for the new method very well.
[Xposed General] Mr.Yawnie:
Disable CM superuser from developer settings and flash SuperSU. Then flash this systemless xposed.
[Xposed General] Artim_96:
Thank you very very much. Now it's running perfectly:laugh::good:
[Xposed General] Captain_Throwback:
If you're not using SuperSU, then you don't have su.img mounted at /su, so systemless isn't possible. v86.x in systemless mode depends on SuperSU, as it says in the OP.
[Xposed General] knpk13:
I've never used the in built superuser. Always latest SuperSU. Updated my earlier post. I've read all the instructions and new update info. :)

[MENTION=5401674]Mr. Y[/MENTION]awnie does it work for you? Cm superuser is already disabled and I'm on SuperSU. (Do I need to let rom and SuperSU boot once, and then flash systemless xposed?)
[Xposed General] Captain_Throwback:
Delete /system/xbin/su and try it again.
[Xposed General] teddy0209:
v86.1 is working as it should... ?

flashed over v86
[Xposed General] Mr.Yawnie:
Well now I'm on OP3 stock, but yes, it was working for me with CM13 on Galaxy S4. :) you might have to force systemless root.
[Xposed General] rfgamaral:
How to properly update this to the latest v86.1 SYSTEMLESS version? I'm kinda confused...
[Xposed General] Krillen:
I install 86.1 alt and it looks like it installs fine but when I check the app upon reboot it still shows 86.0 installed (Note 4 910P).
[Xposed General] Artim_96:
Stated in the OP. At least run the uninstaller zip. If it fails to install restore your boot image and system.

---------- Post added at 10:41 PM ---------- Previous post was at 10:37 PM ----------

Maybe clear cache of the installer or look in the logs. In the first line or so there should be the version.

Otherwise look into /su/xposed/system/xposed.prop, there should be the version too.
[Xposed General] rfgamaral:
I've read the OP and I'm still confused. Why do I have to uninstall first? Why restore boot? I thought this didn't mess with any of that...
[Xposed General] Captain_Throwback:
The new version doesn't, but the previous version (v85.x, which you have) did.
[Xposed General] koko115:
86.1 S7Edge works :)