yashsingh1/xdaforums huggingface dataset:
[Xposed General] tg9z1:
First log of Magisk - Xposed is not run. The status of Xposed in "Framework" tab in XposedInstaller is "Xposed Version 89.2 (Systemless by topjohnwu) is installed but not active".

Second log - Xposed run properly.

In the first log it seemed to me the suspicious line:

04-24 08:43:30.608 425 784 E Magisk : opendir: /sbin/.core/img/.core/service.d failed with 2: No such file or directory

I use XposedInstaller APK from first post in this thread.

P.S. Now Xposed is active.
[Xposed General] Legendary Cryptid:
I recently purchased a Mi A1, and got everything set up. Does systemless Xposed work with Mi A1 running 8.0.0 Oreo? Can anyone confirm this, with little to no problem?
[Xposed General] woopies:
[IMG="app_process64"]https://drive.google.com/file/d/12AyT6ip2NZK0AOeisGhafRgd3kivFeMv/view?usp=sharing[/IMG]

xposed-v89.2-sdk24-topjohnwu.zip

%s%s..../magisk/xposed..CLASSPATH.......%s:%s... No path found
[Xposed General] zatzh:
stuck on samsung boot logo

i flash xposed systemless sdk 23 module using magisk when i reboot my galaxy j700f [MM] it stuck on samsung logo .

after this i flash rom again with odin to fix this

how i install xposed using magisk ?
[Xposed General] oreo27:
Yup. I'm running it with no issues.
[Xposed General] four ruttrawit:
Help! I cant install any xposed module. It's show "download failed error 1000" I use systemless xposed sdk24.
[Xposed General] Adam3Sixty:
FYI:

OnePlus 5T

OxygenOS 5.1.1 / Android 8.1

Magisk root

Latest Systemless Xposed

All working perfectly :) thank u!!
[Xposed General] vacs03:
Sdk 27 not working on latest magisk 16.4
[Xposed General] Ja_som:
logs
[Xposed General] vacs03:
Here it is
[Xposed General] vacs03:
Delete pls
[Xposed General] n0j0e:
For me Xposed works but Xposed installer says:

Xposed-Framework is not installed.
[Xposed General] mrjuniork:
Same for me... Xposed SDK 27 not working. "framework not installed"... Modules are working though
[Xposed General] _mysiak_:
Magisk 16.4 broke Xposed for me as well, interestingly Gravitybox module is still active. Relevant dmesg:

Line 3244: [ 80.008740] type=1400 audit(1525010734.024:258): avc: denied { execute } for pid=2379 comm="main" path="/data/dalvik-cache/arm64/system@framework@XposedBridge.jar@classes.dex" dev="dm-0" ino=611000 scontext=u:r:zygote:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
Line 3256: [ 80.252122] type=1400 audit(1525010734.024:259): avc: denied { execute } for pid=2379 comm="main" path="/data/dalvik-cache/arm64/system@framework@XposedBridge.jar@classes.dex" dev="dm-0" ino=611000 scontext=u:r:zygote:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
Line 3257: [ 80.252138] type=1400 audit(1525010734.267:260): avc: denied { execute } for pid=2379 comm="main" path="/data/dalvik-cache/arm64/system@framework@XposedBridge.jar@classes.dex" dev="dm-0" ino=610996 scontext=u:r:zygote:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
Line 3270: [ 80.452240] type=1400 audit(1525010734.267:261): avc: denied { execute } for pid=2379 comm="main" path="/data/dalvik-cache/arm64/system@framework@XposedBridge.jar@classes.dex" dev="dm-0" ino=610996 scontext=u:r:zygote:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
Line 3440: [ 90.069262] type=1400 audit(1525010744.084:282): avc: denied { execute } for pid=2380 comm="main" path="/data/dalvik-cache/arm/system@framework@XposedBridge.jar@classes.dex" dev="dm-0" ino=611050 scontext=u:r:zygote:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
Line 3442: [ 90.347888] type=1400 audit(1525010744.084:283): avc: denied { execute } for pid=2380 comm="main" path="/data/dalvik-cache/arm/system@framework@XposedBridge.jar@classes.dex" dev="dm-0" ino=611050 scontext=u:r:zygote:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
Line 3443: [ 90.347932] type=1400 audit(1525010744.364:284): avc: denied { execute } for pid=2380 comm="main" path="/data/dalvik-cache/arm/system@framework@XposedBridge.jar@classes.dex" dev="dm-0" ino=611340 scontext=u:r:zygote:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
Line 3444: [ 90.661929] type=1400 audit(1525010744.364:285): avc: denied { execute } for pid=2380 comm="main" path="/data/dalvik-cache/arm/system@framework@XposedBridge.jar@classes.dex" dev="dm-0" ino=611340 scontext=u:r:zygote:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
Line 7243: [ 330.887481] type=1400 audit(1525012459.975:4168): avc: denied { read } for pid=12359 comm="posed.installer" name="xposed.prop" dev="rootfs" ino=28574 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=file permissive=0
Line 7248: [ 359.954748] type=1400 audit(1525012459.975:4168): avc: denied { read } for pid=12359 comm="posed.installer" name="xposed.prop" dev="rootfs" ino=28574 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=file permissive=0
[Xposed General] pa.pn2:
Same here.was working till magisk 08/04 version.

All versions after have the issue.

I think the xposed app has to be updated somehow
[Xposed General] hurray:
I have the same with Lineage OS 14.1, Magisk 16.4 and Xposed 89.2 (api 25):

Xposed-Modules are working well but the installer says xposed were not be installed.
[Xposed General] jwds1978:
[MENTION=4419114]rovo89[/MENTION] [MENTION=4470081]topjohnwu[/MENTION] For me, after upgrading Magisk to 16.4, Xposed modules don't work at all — unlike others whose modules work regardless of status within the installer.

__ EDIT — 30 April 2018 __

I've since uninstalled systemless Xposed and installed the official Xposed to /system — Xposed is working again. I need Xposed, as I have many Xposed modules installed, and all of my other Magisk modules are working without issue.
[Xposed General] Artim_96:
No. There is a bootloader unlock for the verizon S5 but that's it. But most Samsung phones have an not unlockable bootloader. So as long as you don't get the unlock key from Samsung there is no way to unlock it. And since they don't want you to unlock it there is no way. Don't know what you misunderstood but the majority of devices have a locked bootloader you can't unlock
[Xposed General] ldeveraux:
I "misunderstood" your false blanket statement. No big deal
[Xposed General] Artim_96:
There is nothing wrong about it. Just because Verizon seems to allow you to unlock the bootloader of a few devices it has nothing to do with Samsung devices having an unlockable bootloader.

Your statement saying S5 can be unlocked is wrong since the bootloader is from Verizon, so only one of a dozen versions of the S5 cab be unlocked because Verizon let's you do so. Samsung devices without heavy carrier modifications (like the international variants) - or with other words with a Samsung-made bootloader can't be unlocked. And even most carriers don't do what verizon does.

The comment was to someone who just says he has a Note 4, so the chance that he has the unlockable verizon version is very small since we're not in a verizon galaxy note 4 forum.
[Xposed General] Citizen_Snips:
If you want unlockable bootloaders go with Nexus devices. Started on the GNex, haven't looked back since. Coming from a Droid X2 (256bit encrypted bootloader) it was a huge difference!
[Xposed General] ldeveraux:
As RoyJ said, the only device that "allows" a user to unlock the bootloader (without a dev edition) is the nexus. Neither developers nor carriers want an unlocked bootloader, that's why it's locked and so difficult to circumvent. It's not rocket science, just don't claim that Samsungs can't be unlocked, especially since Beaups unlocked the Note 4 months ago...
[Xposed General] Artim_96:
Or at least a Motorola or HTC 10 where you can unlock it too, yes.

Still hoping Google brings some good Nexus devices this year since I didn't liked the ones from last year and I will go back to Nexus. No ugly useless crap, easier modification/lot of development and Developer Previews:cool:
[Xposed General] tartanpion:
I think a more general solution for "odin flashable" devices is to extract the stock recovery image from the firmware from sammobile and

- install twrp with odin

- root systemless with the latest supersu (at this time 2.74.2) with twrp

- flash the stock recovery with odin

- and do all the others stuffs with flashfire

For fastboot flashable devices use at first step the "fastboot boot" command to boot from trwp without install it.

Any comment ?
[Xposed General] Artim_96:
Wrong. Motorola gives you the tools on their website without any dev editions and it looks like HTC is going the same way since it is so with the HTC 10.

You can unlock the verizon variant, yes, but that does not mean you can unlock the note 4 in general since the verizon variant is only a very small variant in the myriad of versions.

---------- Post added at 03:51 PM ---------- Previous post was at 03:43 PM ----------

If there is cf autoroot for use that. Since it's available for all Samsung and Nexus devices is the easiest way. And since both this and SuperSU are made by Chainfire the zip files will be updated if there is a new SuperSU version. That is way easier than getting the huge update file and needing an flashing orgy through ODIN.

For fastboot flashable devices there are .img files for SuperSU you can just flash through fastboot
[Xposed General] tartanpion:
Are you sure that all the cf auto root have ever the latest version of supersu. No information on the website. Perhaps it's just a particular case cause cf autoroot for galaxy note 4 are based on a recent firmware 6.0.1 and thus use the latest version.

For fastboot flashable devices : where are the .img files for the latest supersu ? chainfire himself recommend to use twrp ?
[Xposed General] Artim_96:
They are always automatically updated when he pushes out a new version. It always takes some time, but a few days later they are all up to date.

And the .imgs are under the list of ODIN flashables.

Sure, he recommends to use TWRP WHEN YOU WANT TO USE A RECOVERY but if you have the possibility to use Autoroot use it, especially since you should not change the recovery for OTAs.
[Xposed General] jb_bryant:
I'm trying to restore my system and boot but it's saying it can't because it's mounted as read only. How would I restore? I'm s-on fyi
[Xposed General] CardinalDeath:
How do I get the latest I can't download it 85.7v
[Xposed General] Artim_96:
Already tried the web version of the forum? I just downloaded about two hours ago and didn't had any problems...
[Xposed General] Ruuu:
Can anyone who has Samsung Note 5 with system less xposed please tell me exactly steps to flash it.

I've ended up losing both private mode+dm-verity. Please!
[Xposed General] akirainblack:
Flashfire worked like a dream, had to select the Auto-mount option. Thanks.
[Xposed General] matrixios:
I would like to know if someone has the LG g2 if xposed systemless working on it. anyway I have to say a big thumbs up to the programmer to the promising work

Στάλθηκε από το LG-D802 μου χρησιμοποιώντας Tapatalk
[Xposed General] teddy0209:
You can restore boot without mounting rw, restore a system.img backup instead of a system backup to benefit from systemless...
[Xposed General] teddy0209:
It would be better to ask in the G2 forum... If G2 allows modification of boot.img without any extra step, then it should work as is...
[Xposed General] Artim_96:
I don't have one (anymore), but why should it not work? This is meant to work on every device. So as long as you can use systemless root there is not really a reason why it shouldn't work.
[Xposed General] moriel5:
One reason - Bump.
[Xposed General] mr_oxalis:
lineage os 15.1

magisk 16.4

xposed still work well
[Xposed General] nendraharyo:
Got a bootloop on my stock 8.0 XZ Premium, April security patch using 90.1-beta Xposed module on Magisk 16.2. Guess i'll have to wait then.
[Xposed General] J4jks:
Xposed system or systemless with magisk
[Xposed General] zputnyq:
I don't have any problem, I'm on xperia m4 stock 6.0.1 with stable magisk v16.

What I did to install it was just installing xposed framework (apk) first then flash the systemless xposed magisk module
[Xposed General] siealex:
This problem exists ONLY on Magisk 16.4, not 16.0 or 16.3.
[Xposed General] siealex:
Maybe the full logcat will help... Look for errors after 21:21:05.
[Xposed General] TheLoonyRebel:
Well documented that the March and April security patches on Sony devices are borking Xposed from working.
[Xposed General] skullkid383:
SDK 25 modules working but apk not picking up xposed magisk 16.4
[Xposed General] _mysiak_:
With SElinux set to permissive, Xposed app detects the installation status correctly. It's not a correct fix, but a workaround until Magisk/Xposed app gets updated.

1. terminal -> su, setenforce 0

2. open Xposed app

3. terminal -> su, setenforce 1
[Xposed General] Augustoandro:
I recently installed Xposed Framework for Sdk 21 using magisk manager.

It is installed but Greenify is not able to detect it.

What should I do?
[Xposed General] Siminica:
could you please suggest a working terminal app? I already have termux but is complaining about some lib being 64-bit instead of 32-bit, which is something also mentioned in release notes for magisk 16.4, saying that developers should modify their apps...
[Xposed General] _mysiak_:
I have been using this one for couple of years already, no issues so far https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
[Xposed General] Fif_:
Terminal Emulator (jackpal.androidterm).
[Xposed General] Siminica:
does your solution allow modules to see xposed framework?

after setting permissive the xposed installer show framework as active but none of my modules (greenify, gravity box) are able to interact with it

and after seeing the framework active if I return to restricted, framework shows again as uninstalled

so probably permissive should be set on boot
[Xposed General] J4jks:
Xposed has been running after upgrading directly upon beta 16.3to 16.4. But after restoring stock boot image magisk lost and Xposed too,

Even after flashing magisk 16.4 + Xposed also Xposed not working

05-02 06:51:20.508 I/Xposed ( 528): -----------------

05-02 06:51:20.508 I/Xposed ( 528): Starting Xposed version 89.2 (Systemless), compiled for SDK 25

05-02 06:51:20.508 I/Xposed ( 528): Device: Redmi Note 3 (Xiaomi), Android version 7.1.2 (SDK 25)

05-02 06:51:20.508 I/Xposed ( 528): ROM: NJH47F

05-02 06:51:20.508 I/Xposed ( 528): Build fingerprint: Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V8.2.1.0.MHOCNDL:user/release-keys

05-02 06:51:20.508 I/Xposed ( 528): Platform: arm64-v8a, 64-bit binary, system server: yes

05-02 06:51:20.508 I/Xposed ( 528): SELinux enabled: yes, enforcing: no

05-02 06:51:23.728 I/Xposed ( 528): -----------------

05-02 06:51:23.728 I/Xposed ( 528): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH

05-02 06:51:25.419 I/Xposed ( 528): Detected ART runtime

05-02 06:51:25.437 I/Xposed ( 528): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing

05-02 06:51:30.503 I/Xposed ( 529): -----------------

05-02 06:51:30.503 I/Xposed ( 529): Starting Xposed version 89.2 (Systemless), compiled for SDK 25

05-02 06:51:30.503 I/Xposed ( 529): Device: Redmi Note 3 (Xiaomi), Android version 7.1.2 (SDK 25)

05-02 06:51:30.503 I/Xposed ( 529): ROM: NJH47F

05-02 06:51:30.503 I/Xposed ( 529): Build fingerprint: Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V8.2.1.0.MHOCNDL:user/release-keys

05-02 06:51:30.503 I/Xposed ( 529): Platform: arm64-v8a, 32-bit binary, system server: no

05-02 06:51:30.503 I/Xposed ( 529): SELinux enabled: yes, enforcing: no

05-02 06:51:32.638 I/Xposed ( 529): -----------------

05-02 06:51:32.638 I/Xposed ( 529): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH

05-02 06:51:33.637 I/Xposed ( 529): Detected ART runtime

05-02 06:51:33.653 I/Xposed ( 529): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing

PS: back to beta 16.3 then after very module needed to reinstall ,then only working properly even though xposed shows :xposed installed '
[Xposed General] _mysiak_:
I am using only Gravitybox and it works fine even if Xposed app reports Xposed framework as not installed. In my case, the issue with Xposed app is mainly cosmetic.
[Xposed General] Siminica:
mine did too after I installed magisk 16.4, it even survived the reboot - xposed installer showed framework not installed but modules working fine, but after that I updated greenify and xposed required reboot and everything xposed related stopped working. for the moment the only solution working for me was to set permissive on boot - everything works as expected - and set restrictive after that - framework shows not installed but modules working
[Xposed General] Augustoandro:
Try Terminal Emulator
[Xposed General] aillez:
Thank you for the trick. this working well.

you can use this app for more convenient.

https://xdaforums.com/android/apps-games/app-selinux-switch-t3656502

Hopes this help.
[Xposed General] DirkStorck:
Hi, for some reason ever Xposed stops working even though after a clean install of the module it doesn't work anymore.

I have attached the xposed log and a screenshot of the installer.

May someone could help :) uninstalling and reinstalling of the module doesn't help

Thank you
[Xposed General] Badger50:
Are you using magisk 16.4 beta by chance?
[Xposed General] DirkStorck:
No I am magisk 16.3. I had it working for quit some time but now it stopped working. It even doesn'z work after removing the module and installing it again.

EDIT: For now I have it working again. I remember that I have updated my kernel, so I went back to an older one. Than I had so flash magisk 16.3 since the old kernel uses 16.0 and after that I have flashed this module from within the reovery. So for now it works again.
[Xposed General] VK'ed:
I have installed xposed v89 sdk25 arm64 through magisk.

Sometimes on reboot, xposed fails to load.

How do i solve this?
[Xposed General] upoclipse:
I have encountered the same issue. What I did was flash version 16.3 magisk and all is well. Seems to me there was a bug or something with 16.4. Owh.. and some kernel such as caessium or latest franco R39 not work well with 16.0 and above.
[Xposed General] DirkStorck:
I always have been using 16.3. I never updated to 16.4. Had that problem yesterday again. Suddenly apps started crashing/force closing and I had to reboot the phone after that I have the described problem. For now I have uninstalled xposed. I can live with that for now... Let's see how it works when Oreo comes out and I make a clean install of the ROM.
[Xposed General] upoclipse:
What kernel are you on? I'm on Boeffla 3.0 beta 5 and it works like a charm with official Lineageos 15.1
[Xposed General] otonieru:
For anyone who have xposed problem on 16.4

either go back to 16.3

or

go to / directory and move xposed.prop to /system

now xposed installer will detect xposed properly.
[Xposed General] _mysiak_:
What's the point of systemless Xposed then? :)
[Xposed General] mattiadj:
It's possible to use xposed on stock odexed oreo rom?

Inviato dal mio SM-G935F utilizzando Tapatalk
[Xposed General] VK'ed:
Help please
[Xposed General] ghoster76:
Yes, that saved my day, bro
[Xposed General] Dizzy90:
Does anybody else have a mi note 2 on this thread? Is it working on yours??? Tell me your set up.

---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------

Mi note 2 - miui 9 - oreo - sdk 26

Magisk 16 working

xposed-v90.1-sdk26-beta3-topjohnwu.zip not working, boot loop, regardless of flashing in twrp with topjohnwu's xposed magisk installer.

This kind of thing happened in SDK 24 till [MENTION=260994]SolarWarez[/MENTION] modified the xposed zip with something from purify OS. I imagined it took into account special miui settings.

Anybody else with MIUI oreo getting xposed to work?
[Xposed General] LoliIsMe:
Having crash issue on sdk 27 on redmi 3 (ido), mainly Google play service and Google, tried changing roms and the problem still persist, booting the phone with xposed disabled temporary solve the problem
[Xposed General] Harshiv989:
Anyone tried Samsung SM-E700H/F/X devices ? On Android Lollipop 5.1.1(SDK 22) with Magisk 16 stable. Safety net passes as of now.

Would xposed break Android Pay ( % probability) ? Even if Exposed installed systemless ly ?
[Xposed General] teddy0209:
100% it would break... Unless you disable the xposed module.
[Xposed General] J4jks:
Wow ,updated xposed framework (systemless) to v89.3 and everything is back to normal with Magisk v16.4

Thankyou very much [MENTION=4470081]topjohnwu[/MENTION]
[Xposed General] topjohnwu:
Updates!

I slightly updated the scripts to work with the changes in Magisk v16.4.

As you know currently I have very limited free time, I can't test everything before I went back to the military camp, that's why the latest Magisk releases are always dubbed "beta", and fixes will always take a week before I can finally touch my computer.

Hope you can understand :)
[Xposed General] Ibuprophen:
As a Disabled Retired Military Veteran myself, I would like to THANK YOU, [MENTION=4470081]topjohnwu[/MENTION], for your Military Service! :thumbup:

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Xposed General] Obedtetsu:
I got same issue with you, do you use magisk or supersu?

I got no problem when I'm using systemless supersu with suhide etc, got this problem when i start using magisk, got same problem with you, always inactive everytime i "regular" reboot my phone but active when soft reboot my phone.

I got this problem with magisk got no problem if using supersu, but if I'm using supersu, some apps detected xposed & hooks, but with magisk xposed undetected and only hooks detected.
[Xposed General] gametimebrizzle:
Did you think it could be because space doesn't exist and the Earth is flat...?

I think it *all* has to do with this.
[Xposed General] Cavaler:
Xiaomi Mi6 with official LOS and Magisk 16.4:

xposed-v90.1-sdk27-beta3-topjohnwu.zip - works perfectly

xposed-v90.2-sdk27-beta3-topjohnwu.zip - infinite boot...

Flashing 90.1 again - all working again.
[Xposed General] newuserrr:
About note 4 n910c with stock

After searching for the forum i'm so confused. :confused: . At the page 200 and 201 there are alt version for note 4 but now op don't have it. Secondly, will my phone bootloop if i install xposed v89.3 ? Some people don't install the 87.3 but still have their Samsung devices with xposed work. I don't want to flash now because i can't backup (my sdcard is full). So what version of xposed should i install ? The wanam's build cause bootloop after a few reboot. :(
[Xposed General] Legendary Cryptid:
Using the module makes my CaptivePortalLogin crash and not work. Sometimes the Play Store crashes too. Any way to fix this?

Typed from my Xiaomi Mi A1 using XDA Labs
[Xposed General] teddy0209:
We wouldn't know it unless you are willing to flash. It's should be easy to recover from boot loop, since this is systemless.
[Xposed General] Undefeatable:
Guys, did anybody tried to install Xposed on Huawei Mate 10 recently and survived the bootloop?? And also i have a very important question, using fastboot is it possible to goto recovery mode??
[Xposed General] teddy0209:
2nd question, Yes...
[Xposed General] Undefeatable:
Great, can you please tell me how to do that?? Because when i go into bootloop the only think i know how to go through it is the fastboot.
[Xposed General] teddy0209:
Can't you use hardware button on your device? ( That would be more convenient)

Try fastboot reboot recovery
[Xposed General] Undefeatable:
The problem is that i know if i hold volume up and power button i will go into recovery mode but i don't know why in that case the default huawei recovery shows up not TWRP!! I want TWRP to be my default when i use hardware buttons.
[Xposed General] newuserrr:
Sorry for the wrong information, my bad. It was bootloop because of using TiBU with systemless root not wanam's xposed