yashsingh1/xdaforums huggingface dataset:
[Xposed General] cerobles1:
Hey buddy I'm not sure if you got it working or not or if you even tried what I'm a about to tell you. I was having the same issues all day today and i installed and uninstalled xposed about a hundred times. Finally I went into the xposed app and clicked the Xposed Status switch off and on, did a soft reboot and it worked. Won't hurt to try.

This is due to the disabled file which it deletes on that switch, nice idea. :good:[/QUOTE] [MENTION=2522022]nymikey[/MENTION] & [MENTION=6320543]RatchetPanda[/MENTION] yes, toggling off and on, followed immediately by a soft reboot definitely works. Although next time u perform a regular reboot goes back to not active. Tried to disable to see if Android Pay works, but even after disabling systemless xposed AP will not work for me. Next weekend I'll try to flash my ROM and wipe everything to start from scratch. May even try 85.7 since I noticed someone mentioned a couple of post back that 85.7 systemless works for him to allow AP like-apps to work. Thanks u both. At least now I know how to get it to work.
[Xposed General] abaddon37:
Same error I'm getting
[Xposed General] stylemessiah:
I think his uninstaller is only looking to uninstall the systemless version, which is half the fricking job...if it installs system instead... i dont think its trying to clean that up...sheesh

I maybe wouldnt have made a zip file in a thread called Systemless that actually installed in system mode if systemless couldnt go ahead...and then not included a proper uninstaller

Im going to try the normal xposed uninstaller...

If that doesnt work, ill have to reflash the entire ROM again and wait for an official systemless

edit/update: Well it just gets weirder...i ran the normal official uninstaller (which actually works without an error) and rebooted...checked xposed app and now it says seamless 86.2...wtf?

WTF is going on...jesus...its going to be quicker to reflash the ROM again, flash g-apps, update all the apps than mess with this any further.....what a fricking mess.

Ill wait for official xposed systemless builds i think

What a time vampire......
[Xposed General] topjohnwu:
Uninstaller is updated, sorry for the inconvenience.

BTW, people are complaining issue with no logs lol.

I'm doing many things at the time, I will accidentally miss things.

[MENTION=5438654]abaddon37[/MENTION], [MENTION=962829]stylemessiah[/MENTION]

All should be working fine, I pulled request to rovo89 now.
[Xposed General] uncle_gonny:
Thank you very much, everything's working now [emoji5]

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Xposed General] abaddon37:
My comment was not meant as a complaint, just wanted to let other users know that multiple people had an issue with the uninstaller. I'm in no rush. I appreciate everything you do and respect your time.
[Xposed General] FPSUsername:
Hopefully I will not have to reinstall root to get this working and lose stweaks. I need to do a full wipe to test and I can only do that after saturday
[Xposed General] stylemessiah:
Ive just had a bad couple of ROM flashing days :)

But yeah, a working uninstall script to go along with a new release would have been ideal :)

Meanwhile im halfway back to where i was before all that happened :)

Ill give 86.2 a go, from the fresh ROM, just to make up for the rants :)

Edit/Update: Okay, 86.2 correctly detected my systemless SuperSU this time and is working fine! :)
[Xposed General] Toutatis_:
Just flashed 86.2, all good, except it's still showing 86.1 in Xposed Installer app
[Xposed General] rfgamaral:
I feel the need to reply to this since I was one of the people who asked why should I restore stock boot images.

I think you're taking this the wrong way... I didn't read anyone's else comments but I don't think anyone is questioning your instructions. I, for one, just want to understand what I'm doing and how things work. And since I didn't know what the old method did, I questioned it, what's wrong with that. I just don't like to blindly follow instructions without understanding how things work. That's all.
[Xposed General] Mar-cel:
Where can I find the Material Design Xposed Installer App ?
[Xposed General] iXaidyiu:
In the first post.
[Xposed General] topjohnwu:
Don't take it too seriously :)

It's just a small rant from me, since too many people don't follow the instructions.

Too many things got crammed together and give me a little bad mood.

Hope you enjoy the new update :)
[Xposed General] Fangs87:
It is saying my installed version of su is 2.76 which is < 2.76 and then failing.
[Xposed General] rfgamaral:
Yes, it's working nicely for me :)

After I understood everything, I just did what you instructed and everything's working just fine :)

Kudos. You too, have a nice day :)

Save​
[Xposed General] legendt:
Is SDK22 fix included in this update?
[Xposed General] Fangs87:
So I got it to install now, but still getting:

Logs:

Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (No such file or directory)Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (No such file or directory)

and

[IMG="screenshot"]http://puu.sh/q5PxZ/7904836c8e.png[/IMG]

Tried uninstalling, reinstalling, clearing dalvik / art cache and normal cache, rebooting in-between. always seems to come to this
[Xposed General] steveo17:
restore your original boot.img and then try again
[Xposed General] Fangs87:
Ok, I'll have to try and find 1.

Procedure being:

Restore boot.img

flash uninstall

flash install

wipe dalvik / art & cache?

or better to uninstall

reboot system

then flash boot

then flash un-su

then flash su

then flash installer
[Xposed General] Gabbro16Hz:
Hello i have installed SuperSU v.2.76 and systemless xposed 85.7,i can update systemless xposed at version 86.2 without uninstall the previous version??
[Xposed General] steveo17:
do you have a nexus? you should be able to get it from the factory image or flashify

also, what i did to fix it was:

restore original boot.img

reboot

flash supersu 2.76

flash xposed systemless

flash kernell
[Xposed General] Fangs87:
i'm on chroma so that boot img or stock boot img? cause i did chroma's and still no luck
[Xposed General] J.Diogo:
Hey guys,

Sorry about the stupid question, I'm a little confused.

I'm on 85.7 what should I do to update to the latest version?

Regards
[Xposed General] steveo17:
Flash your Rom again then

---------- Post added at 05:26 PM ---------- Previous post was at 05:26 PM ----------

Restore your original boot.img then flash the v86.2
[Xposed General] J.Diogo:
Thanks for the quick answer.

So, fastboot flash boot.img?

Should I disable my xposed modules first?
[Xposed General] steveo17:
No. Shouldn't matter
[Xposed General] Bajanman:
Ok popping in here drop a post about my install experience. Tried installing 86.1 had no luck the pass few days. So went back to 85.7 to have my Xposed working again.

So 2day I start with the new 86.2 update. Restored stock boot first thing to remove anything left behind. Followed the instructions in the Op, and I also tried a few different approaches to get everything working. Got that dreaded framework not active after opening the newer installer. (Tried this like 6 times still no luck)

[MENTION=4470081]topjohnwu[/MENTION]

What got mine working:

Was shocked after rebooting to see Android is updating without wiping cache after doing the above. I kinda knew it might work once the phone booted up. And to my surprise ALL is working good in systemless land...:good:

Thanx [MENTION=3006212]steveo17[/MENTION] not rebooting fixed mine, since I would reboot after each flash. So I'm happy again after getting this all set-up. Now time to go do a back-up asap.
[Xposed General] Artim_96:
Learn to read back a few pages before asking. Support for SDK22 was dropped because of incompatibility. As long as Chainfire doesn't come up with something genius (as always) to let the scripts run there the same way as on SDK22, there won't be any systemless for accept the one with the old method.

[MENTION=4470081]topjohnwu[/MENTION] maybe you should point that out in the OP instead of just writing about SuperSU v2.76. that would be more clear than the one with the post-fs-scripts. I would say most users coming here and not reading your comment on that will ask that stuff over and over again... It's already annoying enough when people can't even read to the point about how to report an error
[Xposed General] CRXed:
On a Nexus 6 you would have to reboot first after flashing SuperSU, because you needed to make space in the system partition to be able to flash Xposed.

Is this still needed for the systemless version? I would say, systemless = nothing writes to system, so even with 0 kb free it will work? Correct?
[Xposed General] Fangs87:
No dice

Flashed chroma

Flashed un su

Reboot system

Reboot recovery

Flash systemless su latest 2.67

Reboot system < needed cause su has updated binaries and without them xposed fails saying 2.67 < 2.67 with them it says 2.67 >= 2.67 .... ...

Reboot recovery

Flash systemless xposed 86.2

Flash franco 24

Same result installed not active log says same can't open log file doesn't exist

---------- Post added at 06:39 PM ---------- Previous post was at 06:13 PM ----------

Ok dice

After that

Reboot recovery

Installed Franco 25

Reboot system

Had yellow installed not active

Disabled it

Soft reboot

Enabled it

Soft reboot

Dice green check up and running.
[Xposed General] hipsterfont:
Attempting to install this on an Xperia Z5 Compact and I'm getting "Installed SuperSU: < 2.76" (installed version number is blank, just a space). It detects and mounts /data/su.img but for some reason it's not getting a valid version string I guess? I definitely installed the latest SuperSU from chainfire.eu in systemless mode several times and it shows up as version 2.76.
[Xposed General] glauberlima:
The uninstaller 20160718v2 has the compression issue as wel...

Hello [MENTION=4470081]topjohnwu[/MENTION]

The uninstaller xposed-uninstaller-topjohnwu-20160718v2.zip has the same compression issue I reported yesterday (#1193) for installer v86.1:

Archive: /sdcard/Download/XDA Forums/xposed-uninstaller-topjohnwu-20160718v2.zip

unzip: zip flags 1 and 8 are not supported

********************************

Xposed framework uninstaller zip

********************************

! Failed: Unable to extract zip file!

I'm providing a REPACKED version attached to this reply.

Thank you for your hard work on bringing Xposed to the systemless ecosystem :D
[Xposed General] topjohnwu:
Is the installer zip working? Need someone to test.
[Xposed General] Artim_96:
The 86.2-alt zip seems to be working. At least it's recompiling now and on the SuperSU topic it said something like "Supersu version 2.76>=2.76 supported"
[Xposed General] m0han:
what i got.
[Xposed General] mobileman88:
Would using adaway break the safety net?
[Xposed General] m0han:
sysless xposed error? or app error?

is this how it should be when v86.2 is installed?
[Xposed General] moriel5:
Yes.

The only picture that matters is the first one.

All the other ones show what you can download.
[Xposed General] glauberlima:
No. I'm using AdAway systemless :)

You need to run a script before installing it as described in this topic:

http://xdaforums.com/showthread.php?t=2190753
[Xposed General] m0han:
'can'? shouldn't it be showing only the ones i 'should' download? btw, how about the pic in this post?
[Xposed General] Artim_96:
No. The one you should download is linked on the first pic at the bottom which brings you directly to the tab fit your device.

And what's the point with the other pic?
[Xposed General] moriel5:
The point is something that had already been discussed, that 86.2 still isn't showing up for download in the app.

By the way m0han, sorry I hadn't noticed who posted, I was very tired when I had answered you.

I went to sleep at around 3:30am today, after testing out a Windows-compatible OS (ReactOS) in Boxes.

PS: The spelling mistake (Allt instead of All) has been fixed.
[Xposed General] Artim_96:
If you didn't realised it yet, it seems that the download links for the zips are hard coded so they won't update before the next update of the installer.
[Xposed General] moriel5:
Ah, thanks.

Once I read your post, I remembered the conversation about that matter early on in this thread.

I had literaly forgotten all about that.
[Xposed General] dimm0k:
with 86.1 the framework section showed nothing installed, however Xposed modules still worked. with 86.2 it shows that 85.7 is active. I've uninstalled with uninstaller, flashed SuperSU, and then flashed 86.x. did I miss something or is 85.7 really still on my system?
[Xposed General] Artim_96:
Is there still an xposed.img in /data? Did you really followed the guidelines in the OP - or with other words - did you restore the boot.img? Otherwise take a look at /su/xposed/system/xposed.prop, there should be the version written that is running.
[Xposed General] dimm0k:
after uninstalling Xposed with the uninstaller there is no xposed.img in /data. I thought flashing SuperSU restores the boot.img or am I mistaken there? I currently do have an xposed.img in /data and there is no /su/xposed... so if flashing SuperSU doesn't restore the boot.img, does that mean I need to clean my device and start from scratch?!
[Xposed General] Artim_96:
...yes. At least as long as you don't have a seperate file containing the boot.img (e.g. for Samsung devices you can get the system in a format flashable with ODIN that contains a boot.img, for Nexus devices the same should be found in the file provided by Google, so you only need your device specific counterpart).

But even if you can't extract the boot.img you will find somewhere the whole system as flashable, cleaning the device like with a factory reset wouldn't help, you have to flash the system, starting from scratch is not necessary (and flashing the system, rerooting it and reinstalling XPosed isn't that big of a deal except for the two recompilation processes you will run through)
[Xposed General] atharwaqas:
So i use the uninstaller provided and uninstall version 85.7 and then installed 86.2 but then when i go in the xposed material app, it shows that 85.7 systemless is active. Also i am running SU 2.76 and stock rom 6.0.1 june update.

Am i missing something here.
[Xposed General] teddy0209:
Reflashing supersu will restore your boot.img... Just manually delete the xposed.img in /data
[Xposed General] SyCoREAPER:
Tried that but it doesn't uninstall despite no errors in twrp
[Xposed General] iXaidyiu:
How about the latest version of Xposed installer by DVDandroid?

If performing that still doesnt fix your problem, you may need to restore system image ( as well as boot image ) and flash SuperSU and systemless Xposed framework again.
[Xposed General] SyCoREAPER:
Thanks may need to restore those as you said. I have the latest
[Xposed General] SpasilliumNexus:
The installer "	xposed-v86.2-sdk23-topjohnwu.zip" is doing the exact same thing too when it's put into a ROM and scripted in updater-script to install.

This is my test setup in updater-script:

package_extract_dir("xposed", "/tmp/xposed");
run_program("/sbin/busybox", "unzip", "/tmp/xposed/xposed-v86.2-sdk23-topjohnwu.zip", "META-INF/com/google/android/*", "-d", "/tmp/xposed");
run_program("/sbin/busybox", "sh", "/tmp/xposed/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/xposed/xposed-v86.2-sdk23-topjohnwu.zip");

This is the output of recovery.log:

Installing zip file '/external_sd/ROMFlashpack/xposed_test_install.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
minzip: Extracted file "/tmp/xposed/xposed-v86.2-sdk23-topjohnwu.zip"
about to run program [/sbin/busybox] with 6 args
Archive: /tmp/xposed/xposed-v86.2-sdk23-topjohnwu.zip
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
about to run program [/sbin/busybox] with 6 args
unzip: can't open /tmp/xposed/xposed-v86.2-sdk23-topjohnwu.zip[.zip]
******************************
Xposed framework installer zip
******************************
! Failed: Unable to extract zip file!
run_program: child exited with status 1
script result was [2]

I'm using TWRP 3.0.2-0 on a Moto X Pure Edition.
[Xposed General] Miustone:
Same Problem here with TWRP 3.0.2-0 on LG G5!

Used (nearly) the same Lines on my Script but it seems to not work, not matter what I do... But the biggest Problem is atm. the Material Xposed App which does still not support 86.2 Framework...

I've really not liked Xposed in the Past cause of the dirty System Method, but now with Systemless it's really welcome in my Work... No stability issues so far and it's so fine to remove if needed... Thanks alot John! I will Link Your work on my Thread once I have included it!

BR
[Xposed General] topjohnwu:
May you send me your test zip? Thanks
[Xposed General] mobileman88:
Does this systemless xposed mean that I cannot use any custom kernels since it always requires the stock boot.img? Sorry if this has been answered somewhere as I read the OP and almost all 100+ pages of this thread before asking.
[Xposed General] FPSUsername:
Uuhm, it seems that the latest currently available installer works right with 86.2 for me

View attachment 3818084
[Xposed General] dimm0k:
I'm completely lost now... I've restored my boot.img from an older backup of TWRP, ran Xposed uninstaller v2 posted in the OP, flashed SuperSU 2.76 in OP, booted into device and noticed SuperSU icon was missing however /su and files in there existed, as well as /data/su.img. To get icon back I installed SuperSU from PlayStore and it "looks" like SuperSU is fine. Xposed Installer from OP shows Xposed framework is not installed so I boot back into TWRP and flash the systemless 86.2 and boot back into device and now Xposed Installer shows 86.2 is installed but not active and to check the logs for details. Logs are empty. When I go to the Modules listing all of my modules say "This module requires a newer XposedBridge version(xx) and thus cannot be activated" where xx ranges from 30 to 84. did I screw my device up badly or is this fixable? help!

EDIT: noticed that wiping Dalvik/cache no longer triggered a compile on boot! hopefully this is a clue for anyone willing to help
[Xposed General] Artim_96:
... LEARN TO READ!!! The exact same was asked about two post above you, the solution is directly above!

---------- Post added at 07:46 AM ---------- Previous post was at 07:39 AM ----------

Who says that it requires the stock boot.img? That would also mean SuperSU wouldn't be running.

Going back to stock boot.img is only necessary if you had v85.x installed to completely remove it

---------- Post added at 07:49 AM ---------- Previous post was at 07:46 AM ----------

Check /data/data/de.robv.android.xposed.installer/conf when there is a disable file, delete it.
[Xposed General] Lim_Dul:
I have a different issue to the ones mentioned before with the installer:

I have installed v86.2 Systemless on my Nexus 6 AND all modules are working fine. However, the installer is telling me that the Xposed Framework is not installed. :confused:

Very weird - not a biggie since everything is working fine, but still.

I'm on a Nexus 6 / Android 6.0.1 July build (MOB30O). I installed SuperSU and the framework on the stock boot image but later switched to franco kernel. Might this be the problem?
[Xposed General] saikoz:
i got Xposed Version vXXX (Systemless by topjohnwu) is installed but not active" :(

nexus 5 Marshmallow 6.0.1

using latest xposed material installer

flash xposed-v86.2-sdk23-topjohnwu.zip

supersu v2.76

provided logcat during boot
[Xposed General] dimm0k:
I checked... there is no disable file in there. However if I go into the Xposed Installer and disable Xposed then I can use Android Pay again. When I enable it, I get what I posted previously and Android Pay complains not being able to access my "Wallet".
[Xposed General] Artim_96:
That's normal with XPosed. I think the file that lets the SafetyNet API succeed is independent of possible misbehaviors. But does only the installer say that it's not active or do you really don't get any changes the modules are supposed to do? In the worst case try to reinstall XPosed.

Otherwise install LiveBoot, reboot your device and upload the log. When XPosed is really not working these logs could possibly help to find out why.
[Xposed General] grep_i:
I don't think the kernel is the problem here.

Don't know how long ago you installed this but lately there were a lot of update activities on the installer due to bugfixes and incompatibility issues maybe you do not really have the latest installer.

Remove the one that's now installed.

Try downloading the installer again and do the magic again and see if that solves your problem.

If you think your problem is the same as [MENTION=6099609]Lim_Dul[/MENTION] try the above-mentioned suggestion.
[Xposed General] Nazariyhuhalo:
So I have installed the latest Xposed v86.2 on a Note 5 T-Mobile but when I open the app it says it is installed but its not active check the logs it says

Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (No such file or directory)Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (No such file or directory)
[Xposed General] hataw:
Install Guide is so complicated can you renewe it and explain step by step
[Xposed General] teddy0209:
You don't understand what part?
[Xposed General] saikoz:
okay i tried redownload and install, still same

then i flash latest beta supersu

booom its activated :) thanks
[Xposed General] Persechini:
The part I think is not being clearly transmitted is that you have to start flashing 2.76+ from scratch, not updating a previous version to 2.76
[Xposed General] teddy0209:
It was clear in the guide that you have to flash 2.76+ in recovery...
[Xposed General] dimm0k:
attached is my liveboot.log
[Xposed General] Persechini:
It would if most people would read carefully and interpret it.
[Xposed General] teddy0209:
The problem really is reading and understanding... Mostly reading, people tend to skip some, which should not be because it involves moding your device...
[Xposed General] grep_i:
Please elaborate what is not clear about this text, I almost felt offended by all the red letters and bold text.
[Xposed General] garthybarthy:
I think what he means is that the instructions state older versions than 2.76 of SU don't work BUT it doesn't state that you can't just flash 2.76 over 2.74, you have to flash 2.76 on a clean install for it to work.
[Xposed General] topjohnwu:
I viewed the logcat.

It seems that SuperSU didn't execute the script in the right way (post-fs-data)

Either you didn't properly installed SuperSU, or it's a bug in SuperSU.

Try to restore your boot image back to stock, and flash SuperSU 2.76, then flash my Xposed
[Xposed General] intruder16:
Doesn't work on MIUI. I tried official xposed too. Working xposed is here but no sources unfortunately. Can you try to make it compatible?

I can't give you logs as i am not on MIUI right now.

Thanks!
[Xposed General] dimm0k:
[MENTION=4470081]topjohnwu[/MENTION] have you been able to view my logcat as well? I may be having the same issue... and this is even AFTER I flashed my device back to stock, flashed SuperSU 2.76, rebooted, installed Xposed Installer, flashed systemless Xposed.
[Xposed General] topjohnwu:
Yes, you are experiencing the same issue. SuperSU problem that I cannot fix. Sorry :(

Seems SuperSU is not running in post-fs-data mode so reliable as my previous Xposed versions. Not sure what's the issue though.
[Xposed General] CrazyCypher:
Ok, I tried everything but no success... I had 85.x installed, I did full restore of boot.img and system.img, flashed supersu 2.76 and flashed xposed 86.2.. after reboot it still says xposed is installed but not active... I also tried to use uninstaller and everything, manually deleted xposed.img, I also in SuperSU app I selected "Full unroot" and tried to flash it again but it is the same everythime...

Any help? :(