yashsingh1/xdaforums huggingface dataset:
[Xposed General] Artim_96:
The versions 85.x needed to modify the boot image for that, the new one just uses the work already done by SuperSU. Restoring boot just ensures that all the old stuff is gone and that there shouldn't be any compatibility issues.
[Xposed General] rfgamaral:
So I just have to run the uninstaller to restore my default boot? The one in the OP attachments or can I run the one within Xposed Installer app?
[Xposed General] THATTON:
What would cause my device to continue to say that framework is not installed? I have flashed 85, 86 and 86.1 but each time I get a message saying that framework is not installed.
[Xposed General] mikeszf:
I just installed 86.1 and it says the same to me, even though all the modules are working and the log doesn't show anything unusual
[Xposed General] THATTON:
I ended up using an older version and it worked fine. I think I flashed v86 Wanam.
[Xposed General] mikeszf:
Well I don't really mind, as long as the modules are working and isn't on system...
[Xposed General] TheManii:
The updated scripts used in v86+ are no longer compatible with CWM 6.0.4, the arguments used to call stuff in the recovery are different from those in twrp 3.0.2.

For devices where cwm is the only available custom recovery, there's simply no way to update at all beyond 85.7, at least with the standard installer.

supersu and v85.x all worked fine on cwm, it's only 86.x's scripts that are incompatible.
[Xposed General] dansan382:
Does this make sense to anyone. I used FlashFire to flash the July OTA file to my Nexus 6. After the reboot realized the Xposed framework was gone so I reflashed the zip for it. When the phone rebooted it had apparently reverted to the June update version of 6.0.1.... What gives? Now I have to reflash the OTA
[Xposed General] toddre:
V86.1 seems to have resolved my issues
[Xposed General] Arun.Gunupudi:
Hello,

I'm new to this thread

Having a problem...
[Xposed General] topjohnwu:
Can you specify what commands aren't compatible? Thanks
[Xposed General] TheManii:
It fails very early, there's no other output besides that, and I can reproduce it on all devices with CWM 6.0.4

I might try walking both twrp and cwm's source code in the future to find the lines of code involved, but im rather busy so I dont know when that'll actually happen. Regardless, supersu's systemless install mode still works fine like I mentioned.
[Xposed General] incognitonk:
So I get this error

http://i.imgur.com/i4oVd3V.png

And there is nothing in the logs

http://i.imgur.com/k03ztn0.png
[Xposed General] topjohnwu:
May you test which unzip command do CWM support?

Use adb shell and try to unzip the zip to /tmp/xposed.

Thank you very much!
[Xposed General] Portgas D. Ace:
Did you check the log for details? You could also upload the log here so we can have a look at it.

Most likely it is because of this:

If you see a line in your log that says "found /data/data/de.robv.android.xposed.installer/config/disabled" then delete that "disabled" file and reboot.
[Xposed General] reemar:
whats systemless effect on batterry/performance if any vs the regular xposed

any difference?
[Xposed General] Krillen:
*edit* Please delete this post.
[Xposed General] Portgas D. Ace:
From my experience it seems more performant and creates less lags, but this is just my personal impression.
[Xposed General] JimSmith94:
For the last few versions, my Download page has been completely empty. The Modules and other pages populate properly, just not this one. Is anyone else seeing this or can suggest a fix?

Sorry if this is in this thread already, but searching for "download" brings up too many results to search.
[Xposed General] Artim_96:
Of course not. You have to get the firmware package of your device and flash it. Or if you can extract the boot image and flash that independently do that
[Xposed General] djborek:
Its working on 5.1 ODEX Stock Rom?
[Xposed General] khushnood alam:
dos any one know how to Systemless root galaxy note 5 sm-n920c complete detail me
[Xposed General] Portgas D. Ace:
Ask in the SuperSU thread for help.
[Xposed General] MrBrowseGierza:
Anyone here got an error message of failed extracting "xposed-v86.1-sdk22-topjohnwu.zip" ?
[Xposed General] rfgamaral:
I'm completely stock so it's probably the latter.

Ok, I now understand the whole steps on the install procedure:

The only thing I'm still confused about is, where exactly do I run the uninstaller? Or is this only required if I have Xposed installed in the system? I'm confused because the guide states that the uninstaller can uninstall both system and systemless installed Xposed. Do I just need to restore the boot.img or do I still need to run the uninstaller?

Sorry for this, but I don't want to screw up anything...
[Xposed General] Artim_96:
You need to at least restore the boot.img, but better run the uninstaller too before you flash the new XPosed. That will get rid of stuff like the xposed.img in /data. Restoring the boot.img only returns the patches that where made in the boot.img like the patched SELinux policies.
[Xposed General] rfgamaral:
Ok, thanks. Will try that when I get the chance.
[Xposed General] emilrune:
Ok this thread is exciting but super confusing to me; I have the Huawei P9, running EMUI 4.1. Got the phone rooted and currently have OP's Xposed 85.7 systemless running just fine.

Now precisely what steps do I need to take, in order to upgrade to the 86.1 version? The "reflash boot image" part from the install instructions especially confuses me, how do I do this? Sorry for what's likely super obvious, but I'd gratefully appreciate an idiot-proof step by step guide from all you smart great people :P
[Xposed General] djborek:
Someone answer me my question?
[Xposed General] teddy0209:
If you have a backup in recovey, you can restore that... Reflashing supersu2.76 would also do that for you if it sees the boot.img has been patched...
[Xposed General] MrBrowseGierza:
Im trying to flash but it says failed extracting "xposed-v86.1-sdk22-topjohnwu.zip" ?
[Xposed General] TechNova:
Is the systemless xposed available for sdk 21 android 5.0 x86?

I want to try it in my zenfone 5 if it is available.....
[Xposed General] ghbuur:
i'm on CM13 and when i flash supersu 2.76 it's installing in systemless mode. but no matter what i do, xposed always "detects system-mode root" and doesn't install systemless. any idea?
[Xposed General] Fild5x:
Installed on Samsung a5h as in the signature below and working ok so far
[Xposed General] teddy0209:
CM has it's own superuser... Check for the su file in your system and delete it...
[Xposed General] ghbuur:
thx a lot! had to delete it with terminal in recovery, now systemless xposed worked..
[Xposed General] Arun.Gunupudi:
Thanks for the response.

Yesterday I tried it..

But no use....

There is no disable file in that directory ....
[Xposed General] Skuggo:
Since the last update it does not function on my s7 edge. Any clues?
[Xposed General] CraigHardy:
Yeah we will all get together with our crystal balls so we can figure it out with no information whatsoever from you!
[Xposed General] Skuggo:
No need to be rude. Just not sure if its compatible hence why i asked.
[Xposed General] CraigHardy:
Well you've given no information as to what rom your running/any other custom mods - v4a etc etc
[Xposed General] teddy0209:
Reinstall, follow the updated installation guide from the OP...
[Xposed General] Yash Doctor:
Installation successful but cant show module list in Download Section!

Any Help Please!
[Xposed General] CraigHardy:
Clear the xposed app data/ use the installer from the OP post
[Xposed General] grep_i:
Yes but reinstalling Facebook solves the problem, I guess something is not good with dex2oat
[Xposed General] Artim_96:
Well, most steps I've explained only a few post before, the tricky part is to work with Huaweis system. You need to get somewhere a file containing the whole system (like the images provided by Google for Nexus devices or the ODIN-flashable .tar.md5 files from Samsung), but I can't tell you how they look like, I never had ones for Huawei. Then it depends how the file works. If you have a normal container like .zip or .tar you can look inside and see if there is something like a boot.img. then you only need a way to flash it. Otherwise you have to flash the whole thing.
[Xposed General] emilrune:
I do have the entire stock ROM, it's posted in the P9 subforum (I think, it weighs in at 2.4gb). It is indeed zipped, I'll look at it a bit later tonight. Thanks for the advice for me and the others Artim! As I understand it, if the zip contains a boot.img, I'll just flash this via TWRP? And it won't mess with my phone/reset the ROM etc? Cheers!

Incidently: Huawei just posted a ROM update (OTA), if I read the OP correctly I'll be able to flash this on my current rooted/Xposed setup, without messing with the phone beforehand?
[Xposed General] Mogster2K:
I'm having this same problem. I think it's because Cyanogenmod has its own root built in. The Xposed installer sees that and doesn't bother to check for SuperSU's systemless root.
[Xposed General] Artim_96:
Well you could flash it through TWRP but then you would need to get rid of it again to be able to install updates (and yes, you should be able to install OTAs when /system is untouched by it don't has to. On my Samsung, downloader only don't detect modifications as long as XPosed runs but the zip files are always corrupted...). You should try Flashify. Tap on the "+"-FAB -> flash firmware package -> navigate to the update file (your internal or external storage) and select it. There should be a screen to what to flash. Possibly you can flash stock boot through that as long as it's no protected position (visible in the app under partitions). When the partition is protected, untick all selections and tap on the boxy symbol in the upper right with which you can create a flashable file for only the boot.img. At least that works with Samsung's .tar.md5 files.
[Xposed General] emilrune:
I checked Flashify, it's similar to Flash fire right? (an app which I've used before for FW flashing). Again thanks for your help, I just need confirmation that flashing a stock boot.img and system.img won't delete anything or reset settings.
[Xposed General] legendt:
It seems that SDK22 v86.1 doesn't work on S4 with Google Play 5.1 Roms with SuperSU 2.76 Systemless Mode installed. Everything is ok but the app optimization process first boot was SO FAST. After boot into system, I can't install any app, which always said "app not installed". I think it's mainly oat2dex's problem since I manually clear /cache and ART cache in rec. The first boot still presents FAST app optimization. Any ideas? [MENTION=4470081]topjohnwu[/MENTION]
[Xposed General] uncle_gonny:
OP3, stock 6.0.1, arm64

Flashing successfully from twrp xposed-v86.1-sdk23-topjohnwu.zip.

No xposed-v86.1-sdk23-arm64, nothing happens if i try to flash xposed-v86.1-sdk23-topjohnwu from topjohnwu v86 materialized xposed installer, what am i missing?

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Xposed General] Artim_96:
Oops... Don't know how I got on Flashify. I mean FlashFire of course
[Xposed General] topjohnwu:
A logcat at boot will be nice :)
[Xposed General] legendt:
As requested. Not sure this boot logcat include the info you might need.

This time I installed Material Xposed Installer in advance. Different from what I saw from the time when I test v85.7 with no luck either, it says “no xposed installed” instead of "not activated". I think the SDK22 versions never work for once as you can see there's no successful cases :(

I have to revert to working daily rom so that's all I can present for now. Thank you for your effort anyway. We are waiting for the good news!
[Xposed General] MATPOC:
Are you planning to make Systemless Xposed for SDK21 Lollipop 5.0?
[Xposed General] wind0zer:
Flashed xposed-v86.1-sdk23-topjohnwu.zip & I got System installed root detected! message. I flashed CM13, latest supersu beta, and systemless xposed in that order. The paste log is here https://paste.ee/p/4ZeMM
[Xposed General] knpk13:
Delete system/xbin/su and reflash. Worked for me.

[MENTION=4470081]topjohnwu[/MENTION] this has been asked several times, maybe you should add it to the OP? (Instructions for custom Roms)
[Xposed General] JimSmith94:
I tried that and it didn't work for me on v86, but I haven't had any more force closures on v86.1.

---------- Post added at 06:58 PM ---------- Previous post was at 06:53 PM ----------

FYI, my Download page is populated again with 86.1.
[Xposed General] DCXW:
Does it work on KitKat then?
[Xposed General] moriel5:
Why should it?

KiKat uses Dalvik, while Lollipop and up uses ART.

And KitKat's ART (found under developer settings) is completely different, so Xposed (and 99.9% of all apps) is completely incompatible with it.

Besides, systemless root and systemless Xposed are pretty much uneeded on KitKat.
[Xposed General] uncle_gonny:
So there's no v86.1-arm64 available?
[Xposed General] moriel5:
It's an all-in-one flashable package.

Good for arm, arm64, and x86.
[Xposed General] Portgas D. Ace:
Of course it is available. The .zip file is a universal installer, containing all versions (arm, arm64, x86). Just flash it, it will automatically choose the correct one.
[Xposed General] moriel5:
You beat me there. :)
[Xposed General] uncle_gonny:
I've been flashing it successfully until 86.1. I uninstalled xposed from twrp with the script in op and from /data/xposed.img, flashed stock boot.img, flashed su 2.76 systemless, flashed the zip in op, installed the materialized installer in op... But when i select the xposed-v81.1-sdk23-topjohnwu from the list, it reboots to twrp, flashes it but when it boots to system i get the "framework is not installed" message and modules don't work ?
[Xposed General] DVDandroid:
I updated my version of Xposed Installer. It has many bug fixes. Download here
[Xposed General] uncle_gonny:
I've already installed it (the latest), yet i'm still not able to get the framework installed/recognized.
[Xposed General] cge_95:
Hi,

I noted that on reboot after a Flashfire action (Tested with backup and flash zip) my Nexus is optimizing app which take a while to complete.

According to Chainfire, this is caused by Systemless Xposed, is that a known issue ?

Nexus 5 stock MM 6.0.1, Elementalx V6.19, Supersu V2.76 systemless and Xposed V86.1 systemless

Christophe
[Xposed General] hugohthuang:
me too!:crying:
[Xposed General] emilrune:
Update for any Huawei people here.

Mucked about my P9, this install procedure worked for me (after first failing with trying to flash a stock boot.img):

Reflash latest SuperSU in custom recovery (I used TWRP). This apparently "resets" the boot.img as needed

Install Xposed uninstaller zip, then the 86.1 sdk23 zip (the order matters)

Clear cache/Dalvik

Reboot, let the phone do it's thing

Enjoy 86.1 systemless Xposed
[Xposed General] Kellwa:
I have one question

Now after we have systemless xposed and systemless root

is it possible to have systemless Busybox

Because its realy needed for a lot of apps like luckypatcher for example

I hope someone is able to make it avilable
[Xposed General] slabua:
If I'm not wrong, it is already available.
[Xposed General] uncle_gonny:
I've tried installing on clean install (some way i managed to wipe everything - caches, internal, data, system - so why not to try? :P). Clean stock OxygenOS 3.2.1 on OnePlus 3 (sdk23 arm64). Flashed su v2.76 systemless, flashed xposed-v86.1-sdk23-topjohnwu.zip, installed latest dvdandroid xposed materialized, selected xposed-v86.1-sdk23-topjohnwu, rebooted to twrp automatically and back to system, without errors. "Xposed framework is not installed".

Is there something i can provide?
[Xposed General] Artim_96:
Since when is BusyBox not systemless? I had an BusyBox installer from PlayStore that installed it under /su, now I'm using a flashable zip by Osmosis which does the same. For the link you have to search in this forum, it's about 50 pages back
[Xposed General] Fangs87:
tried that, installed the new apk a few posts up

rebooted

flashed latest su

flashed uninstaller

flashed installer

wiped dalvik/art cache and cache

rebooted

still getting v86.1 systemless installed but not active
[Xposed General] ashish_chiplunkar:
thanks bro

U r just awsum. Now i m able to install xposed framework and its perfectly installed in my mobile. I tiered by finding solution for this bt u r app make my work very simple
[Xposed General] steveo17:
updated to the lastest apk that was redesigned by you. had to uninstall the old one though being that it was a different signature. hopefully this is fixed going forward
[Xposed General] KevinX8:
No need for hacked app anymore material design xposed supports 86.1 just fine now without needing hack
[Xposed General] Kellwa:
I have installer from playstore but it need root to install files to /system/xbin or /system/bin

I dont think that is systemless

If you have another installer please tell me about it

And thanks for your reply
[Xposed General] Artim_96:
I already said, link to an installer zip is about 50 pages back in this forum. Just search for osmosis, that should be enough
[Xposed General] ianmacd:
Not quite fully working for me.

After installation, the app claims that systemless 85.7 is installed, but not active. That's not correct, however. Systemless 86.1 is installed and is active.

The Samsung tab, on the other hand, correctly reports systemless 86.1.

Apart from this one glitch, the app appears to work, so it's just a cosmetic thing.

[MENTION=4470081]topjohnwu[/MENTION]'s v86 hack of the app doesn't have this problem.
[Xposed General] KevinX8:
Erm the Samsung tab is just for installation not status that is on the first page titled '' xposed status ''. This seems very abnormal, try and reinstall the app to see if this fixes it
[Xposed General] ReyPaez:
Try rebooting after installing the Supersu then go ahead and install the 86.1 installer... that's what worked for me. Good luck..
[Xposed General] anagramgenius:
Stericson busybox or Jrummy busybox. Search in the playstore.

---------- Post added at 03:22 PM ---------- Previous post was at 03:18 PM ----------

Try to delete the folder /xposed if it exists. (not /su/xposed)
[Xposed General] Kellwa:
[MENTION=5125527]Artim_96[/MENTION] [MENTION=5795078]anagramgenius[/MENTION]

I found it thank you for help
[Xposed General] moriel5:
I think that Stericsson's BusyBox works in conjuction with SuperSU better than others.

If not, than my bad.
[Xposed General] ianmacd:
Thank you.

It does exist and the xposed.prop indicates that these are, indeed, the remnants of my v85.7 installation. Strange, because I ran [MENTION=4470081]topjohnwu[/MENTION]'s uninstaller before upgrading to v86 and then later v86.1.

I can't 'rm -rf /xposed', because I get 'Device or resource busy'. Strange, because my log reports that it really is 86.1 that is running on the device.

I suppose I'm going to have to flash all of the various uninstallers until I find one that actually removes this ghost installation. Then, I can reflash systemless 86.1.

Thank you very much again for pointing me in the right direction.
[Xposed General] moriel5:
Or just remove it from TWRP, and reflash Xposed 86.1.
[Xposed General] ianmacd:
I have no custom recovery on this S7 Edge, unfortunately.

Never mind. I should be able to get things fixed without it.
[Xposed General] Fangs87:
full reboot system or reboot recovery?
[Xposed General] topjohnwu:
I have received quite some criticism since the v86 update. Many people complained it's not working.

The largest reason is that this update is MASSIVELY different with previous systemless versions.

I understand all this is quite confusing, but systemless Xposed just got a whole new mounting method, it need some time to get used to new standards, especially during the transition period when old and new methods are not compatible.

As I have seen in this thread, I would say 90%+ of the reason for breakage is caused by user error.

Please follow my installation guide in the OP!!

If you have flashed my previous version of systemless (or romracer's since it's 99% based on my method), you HAVE to restore you boot image back to stock, and flash SuperSU and new Xposed.

The previous method modifies the boot image to load the Xposed files.

If you didn't remove my modifications to the boot image or remove xposed.img in data, the old method will still run and mount the files. It will likely cause various issues, so please don't do that.

Also, just flashing the uninstaller zip won't remove my previous method!! The uninstaller zip will only remove:

System installed Xposed of all other versions

System installed Xposed with my v86+ version

Systemless Xposed with my v86+ version

It will NOT remove the previous systemless versions!!

============================================================

If the installer installed without an issue, it should work in theory.

If any issues occurs, I have to be clear: it is impossible for me to fix anything if using this new method which depends on SuperSU!

I can improve the scripts for the installer zip; I can improve the uninstaller scripts; I cannot improve the mounting process, it is handled by SuperSU.

Here I will list all known issues so far and confirmed:

Signed zip cannot be unzipped in CWM recovery. Chainfire uses his own tools to fix his SuperSU zips, so no one on earth knows how he fixed it. Will figure out how he accomplished, or I'll just skip the signing for the zips.

CM roms with root included in rom fails to detect SuperSU, should be able to fix it and accept systemless installs

Some issues with the mounting process, I CANNOT FIX IT!

SDK 22: It seems that SuperSU won't run su.d in post-fs-data. Also my binaries seems to have some issues. I will find a device running SDK 22 and debug it myself.
[Xposed General] JimSmith94:
Just want to be sure I don't screw this up. Does this new version of "XposedInstaller_by_dvdandroid.apk" supercede your previous "XposedInstaller_by_dvdandroid(modded_for_v86.0).apk"
[Xposed General] Tornado15550:
It's sad how people can't follow simple instructions. I have absolutely no issues with systemless xposed v.86.1 and want to genuinely thank you for your hard work and efforts! ?
[Xposed General] uncle_gonny:
[MENTION=4470081]topjohnwu[/MENTION] is there something I can provide, in case you're willing to, to fix (if there's any to fix) what's happening on my end? I've followed instructions in op on a clean system install. v86 systemless was working (before I wiped EVERYTHING), v86.1 isn't. Thanks in advance and I'm sorry if I annoyed someone, I'm not complaining, I'm just wondering why I can't get it working.
[Xposed General] topjohnwu:
Device name, SDK version, recovery flashing logs, boot logcats will help a lot :)
[Xposed General] uncle_gonny:
Device name: OnePlus 3 A3003

SDK version: 23 arm64

Thanks a lot for your availability, willing to help as i can
[Xposed General] axewfious:
I cannot flash neither the 86.1 zip or the uninstaller.

E: Error executing updater binary in zip

and Error installing zip file / flashing zip

I come from official xposed but uninstalled it using the official

CM13 D852 7/15/16 nightly (even updated before doing anything to make sure im clean)
[Xposed General] JimSmith94:
I had a blank Download page with the first v86.0, got it back again with v86.1, but have the blank page again after installing the latest "XposedInstaller_by_dvdandroid.apk". Is anyone else having this problem or know of a fix?
[Xposed General] topjohnwu:
Did you even read my post or post #2?

CWM recovery is not supported!!

I'll add support to it in the next version!!
[Xposed General] topjohnwu:
Thanks for the log!

Seems your recovery don't like my mounting mechanism :)

Will fix in the next release.
[Xposed General] ledezma2003:
I'm having the same issue.

Moto X Pure Edition

SU 2.76
[Xposed General] jujak82:
I did the following:

Uninstall xposted, reboot, install supersu, reboot and do nothing after it just reboot again and flash xposed, it should work.