yashsingh1/xdaforums huggingface dataset:
[Xposed General] Tenome7:
Hey Eleo.,,,

Even I experienced the crashing of Magisk while searching for a module.......

Yesterday......I received an update notification of the Magisk apk.....and after installing the apk.......Magisk works like heaven........

Try updating the apk once.......:good::)
[Xposed General] Eleo:
I already did it yesterday from stable/beta channel. My current ROM is not as stable as to put it under canary magisk burden with verbose logging, unfortunately.

Regards.
[Xposed General] labello29:
hello if you're talking about galaxy note 3 sm n9005 (C9 Pro Port) magisk v17.1 works fine
[Xposed General] Eleo:
Of course not that:rolleyes::eek:

We already finished testing and released that ROM as STABLE long time ago with Aspire team. I am on another ROM that is BEING developed and not as stable for release and not as stable for canary builds yet. And no. You cannot ask anything about the developing ROM.
[Xposed General] labello29:
oh sorry i thought i talked about note 3 however since we are in the speech with the new magisk xposed framework does not work
[Xposed General] Eleo:
Already explained REPEATEDLY in that ROM development thread AND this thread. Please read and search. PLEASE. You never read and never search and always complain.

On this thread:

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/post76831920

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/post77025681

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/post77527296

On THAT thread:

https://xdaforums.com/galaxy-note-3/development/rom-aspireteam-c9-pro-v2-0-t3610152/post76944333

And I answered your SAME question on THAT thread:

https://xdaforums.com/galaxy-note-3/development/rom-aspireteam-c9-pro-v2-0-t3610152/post76577651

And I am answering AGAIN. Any magisk version newer than 16.2 will NOT be able to flash 87.3 UNLESS magisk xposed 87.3 zip will be updated to newer magisk package. And it does not look like it will be ever updated, so use the same procedure shown to you.

Ok?
[Xposed General] EoneRizuwan:
Hi, need help here. I'm on latest version of Magisk, 17.1, but I can't install or update some modules recently. I keep getting processing error. From searching about the problem, some suggestion is to create MagiskManager folder but I already have it but nothing changes. Some weird thing to notice that recent successful install module get download on sdcard/download folder instead of the magiskmanager folder. I don't know if I can delete the magiskmanager to replace with new folder without messing up with already installed modules there.
[Xposed General] Eleo:
Magiskmanager folder only holds the zip files that have been downloaded. It does not hold installed files. Please try to go enable beta channel in magiskanager app and update to 17.2. Some fixes have been done on 17.2.

Also, what is your device model? Android version?

I advise to check canary builds for reported fixes:

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
[Xposed General] EoneRizuwan:
So i can just delete already downloaded zip and magisk apk?

I'm using Moto g falcon, Los 14.1 Android 7.1.2

I might try the beta build but is it stable for daily use?
[Xposed General] Eleo:
Beta is good enough. You dont need to delete the folder unless you need to free some space. It doesnt hurt to have it. I backup those zips on my external sdcard just in case (only latest ones)
[Xposed General] EoneRizuwan:
I think it just my slow network connection cause those processing error problem, it work just fine now with more stable one. Though I still couldn't understand why the downloaded zip file go to sdcard/download instead of sdcard/magiskmanager folder.
[Xposed General] jenslody:
The MagiskManager-folder is deprecated, because some root-detection apps use it to decide whether your device is rooted or not.
[Xposed General] Voutsjude:
im getting bootloop with huawei p10 lite android 8.0
[Xposed General] 3bodi9:
I try beta4-test1

It's work well

But magisk root not respond if any app need root

Any idea?
[Xposed General] vofferz:
Hiding Xposed Installer from banking app?

Hi!

I have latest Magisk and systemless Xposed installed on my phone running Nougat 7.1.1.

If I disable Xposed framework from Magisk, the phone passes Safetynet checks, but still my banking app automatically stops working. I noticed that I can start the banking app only if I also uninstall the Xposed Installer app, so I guess it also has some direct check for Xposed and not only Safetynet.

I was wondering if there is some way (maybe withing Magisk?) to hide the Xposed Installer app from the banking app.

I understand that it's not possible to get it working with Xposed enabled, but it's frustrating to always uninstall and then reinstall Xposed Installer in addition to disabling/enabling xposed and booting the phone.
[Xposed General] topstarnec:
miui 10 (android 8.1 base) is not supported by the Xposed.

So mi 8, mix 2s etc don't work. Please fix it.
[Xposed General] _hunter:
Had the same issue. And after I removed xposed with 'mm' -- was able to boot normally.
[Xposed General] Lernos:
I tried the beta4-test1 on my Honor 7x EMUI 8.0 and it does work, but I have the same problem - Magisk won't give root permissions, which makes everything pointless. I wonder if it could be fixed. Using beta3 made me bootloop though, barely made it out of there.
[Xposed General] spawnlives:
Not sure what your issues are but in regards to exposed apps they don't require root access to work. They rely on the exposed framework to work. This is why root permissions are not showing up in magisk.
[Xposed General] Lernos:
Hah, no, you misunderstand. With Xposed installed, Magisk can't give root permissions to anything. Let's say I download Uninstall Expert after installing Xposed and want to disable a system app - Uninstall Expert will send a root request and never get a reply from Magisk! Let's say I want to rewrite a file in /system using Root Explorer - oh, but I can't! Magisk won't give the permission to make it from read only to R/W. This basically makes my whole app arsenal dysfunctional.
[Xposed General] Ænimal:
You need xposed for shakespeare..
[Xposed General] Suryo75:
If it just bootloop you can uninstal xposed, google it
[Xposed General] Dante63:
Since package name and services aren't randomized like magisk... The App search for xposed & thus, doesn't work when it finds it...
[Xposed General] moein_hz72:
so , as i understand from the quotes, we cant have both magisk and xposed working Simultaneously?

need magisk for root access and xposed for gravity box, what should we i do now?

i am running oreo on honor 8:(
[Xposed General] amg314:
On my Oreo device I use both Magisk 17.1 and Xposed with no problem))
[Xposed General] SupDr:
xposed-v87.3-sdk22- and sdk23 for samsung devices NOT working with the latest magisk 17

Install failed

Help plz
[Xposed General] 3bodi9:
The problems in huawei devices

تم الإرسال من ALP-L29 باستخدام Tapatalk
[Xposed General] moein_hz72:
my device ( honor 8 ) has android 8.0.0 with magisk 17.2 install on it

but after flashing sdk26 beta3, it got bootloop,i had tested beta4 too, and again bootloops!

which version of xposed you currently using?
[Xposed General] Eleo:
Please SEARCH before posting

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/post77696001
[Xposed General] amg314:
17.2 is beta version((

API 26 --> Oreo (see screenshot)
[Xposed General] shashank017:
When i try to refresh download list,it show error toast,& list doesn't update. See screenshot
[Xposed General] amg314:
You have received Error 302 - Moved Temporarily

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/302

IMO, the problem lies on the "other side" - requested file is unrichable((
[Xposed General] sumitarora2:
I am also facing this problem from last two days and it is fixed just by clearing data of xposed installer app
[Xposed General] shashank017:
Yeah it worked
[Xposed General] Donphillipe:
Is there anyone who would be willing to help me diagnose why Xposed won't run on my BLU Studio XL 2 phone? I have been working on it for weeks and while installing virtually every verion of Magisk 14 - 17.2 and while re-flashing with factory ROM and starting over as many times as that, I'm still Xposed-less. Now while Magisk provides a working root and all other apps needing root work, installing Xposed seamless shows the green panel but no Xposed apps work on it. An odd thing is switching the Xposed installer off/on doesn't matter, the light stays green saying it's working but of course none of the Xposed apps work. Once you install about 6 Xposed apps, sometimes the "working" green light will turn red which is meaningless since apps don't work green/red anyway

The only clue I can find is the error when viewing the Xposed log file:

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

Another hint is that someone in another post says this phone uses toybox which confuses Xposed.

I've tried all the suggestions found using chmod -R 770 (and even 777) to the /data/data and /data/user/0 directories where the xposed framework data resides to no avail. This doesn't make the log file work.

**** Flashing Magisk though TWRP, have tried installing Xposed systemless via the Magisk instll menu including the universal version, the 87.3 systemless version and the 89.3 version, as well as tried also installing them via TWRP. All installations fail with similar results which I described above.

**** Android 6.0. Note: I just installed the exact same files in a BLU R1 PLUS with the exact same procedure of using TWRP to install Magisk and Magisk installer to install Xposed from the module list and the install worked without a glitch - have everything working including Xprivacylua. There's just something odd about this BLU STUDIO XL 2
[Xposed General] Eleo:
Try to open xposed installer app info page and give permission for storage.
[Xposed General] Donphillipe:
Yes, I did that but it is still broken. Can't open the log file. Using Root Browser, there appears to be no log file. Thanks..
[Xposed General] Fif_:
Capture a logcat while the system boots with Xposed installed. The missing Xposed log file may be due do a missing directory: uninstall and reinstall the Xposed Installer and reboot. Do not clear data for the Xposed Installer. If it still fails, post a link to your logcat.

Edit: are you using the correct Xposed Installer? You need 3.1.5 for system installs of Xposed, and 3.1.5-magisk for systemless installs.
[Xposed General] nxb:
On nougat carbon rom 7.1.2:

Install Xposed magisk version and auto timezone goes to GMT0. Regular xposed doesn't do this. I know it sounds strange but I verified multiple times by installing/uninstalling the module. Guess systemless xposed isn't happening for me.
[Xposed General] ncandroid84:
Bootloop!!!!!!!

Moto G5sPlus

Android 8.1 Stock

-----------English (Sorry for mi english iam use translator)-----------

After installing the xposed SDK27 through MagiskManager and rebooting the cell phone, I am in a nice bootloop, leaving no other option to restore the full backup !!!!

I did not work the mountmagisk module to uninstall the xposed from the recovery !!!!

Going back to the Xposed theme, would you know what is going on in bootloop ???

-------------------------Español------------------------------------

Luego de instalar el xposed SDK27 a través de MagiskManager y reiniciado el celular, quedo en un bonito bootloop, no quedando otra opcion que restrablecer la copia de seguridad completa!!!!

No me funcionó el modulo mountmagisk para desinstalar el xposed desde el recovery !!!!

Volviendo al tema Xposed, sabrían decirme que es lo que esta pasando que queda en bootloop???
[Xposed General] darkdaemon32:
Xposed does not work on 8.1 latest security patches. Try contacting Xposed Dev because this is not magisk problem. Having same issue on 3 other devices with 8.1
[Xposed General] tedted80:
I can't even download the Xposed Installer in the attachment...

it says "401 Gone"
[Xposed General] darkdaemon32:
Just flash the magisk module uninstaller terminal app and run the terminal commands to remove the Xposed module. Downloads can be found in he magisk modules thread

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

Just use the module linked here and flash in TWRP. Follow instructions on the thread https://xdaforums.com/showpost.php?p=72542167&postcount=242
[Xposed General] Donphillipe:
Here is the link to my captured logcat.txt

https://drive.google.com/file/d/1eMh3BkaRbWYKESyVlXutFLVHtkHoOQBw/view?usp=sharing

I did just as you specified, started it from the Windows command line, with

adb logcat -d > logcat.txt

Thank you!
[Xposed General] Fif_:
Well Xposed seems to be running as there's a stack trace in your logcat that shows XposedBridge.main. XPrivacyLua even seems to be running from that same stack trace. But the logcat you captured didn't start at boot, where important Xposed messages would be.

Can you try capturing one from boot? (Enable USB debugging if not enabled already, shut down the device, connect it to the computer, on the computer start adb logcat, then boot the device).
[Xposed General] Donphillipe:
Here it is: https://drive.google.com/file/d/16XMIkzLawJVPJA0kVCCWt8nrGXl8df1b/view?usp=sharing
[Xposed General] Fif_:
I still see traces of Xposed running, but not the Xposed starting messages, which is odd.

Adb logcat was running on the computer before the device was turned on?

Are you using systemless or system install of Xposed?

Also your SD card seems corrupted, there are some messages about this in the log (FSCK). It's a remote possibility that it interferes with Xposed, but unlikely.

I would still try to fix that before proceeding further.
[Xposed General] Donphillipe:
This phone by default has some option that causes all the active apps to re-activate when I boot but since this is my first run with Andoid 6, that may be just part of the package.

Yes, positively this is what happened. Powered off, when I plug in the phone the driver begins loading and unloading as is common waiting to be SP Flashed. A snipit of the console:

C:\Program Files (x86)\Minimal ADB and Fastboot>adb logcat -d > logcat2.txt

- waiting for device -

C:\Program Files (x86)\Minimal ADB and Fastboot>
[Xposed General] Fif_:
You can try to bump up the log file size in Settings > Developer Options > Logger buffer size to the max (16 MB here) to capture the log from the start.

Then redo the log capture.
[Xposed General] Donphillipe:
Much larger:

https://drive.google.com/open?id=1EAQiUGZsmfwOLSBu7p0c9Ej5EhYFTwAx
[Xposed General] Fif_:
Now we're onto something: SELinux.

It seems to interfere with Xposed operations:

10-04 15:01:13.888 562 562 I Xposed : -----------------
10-04 15:01:13.888 562 562 I Xposed : Starting Xposed version 89, compiled for SDK 23
10-04 15:01:13.888 562 562 I Xposed : Device: Studio XL 2 (BLU), Android version 6.0 (SDK 23)
10-04 15:01:13.888 562 562 I Xposed : ROM: BLU_S0270UU_V6.0.04.02_GENERIC
10-04 15:01:13.888 562 562 I Xposed : Build fingerprint: BLU/Studio_XL_2/Studio_XL_2:6.0/MRA58K/1517622290:user/release-keys
10-04 15:01:13.888 562 562 I Xposed : Platform: armeabi-v7a, 32-bit binary, system server: yes
10-04 15:01:13.888 562 562 I Xposed : SELinux enabled: yes, enforcing: yes
10-04 15:01:13.910 752 752 W zygote : type=1400 audit(0.0:15): avc: denied { search } for name="de.robv.android.xposed.installer" dev="dm-0" ino=361360 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0 tclass=dir permissive=0
10-04 15:01:13.910 750 750 W sed_service_app: type=1400 audit(0.0:16): avc: denied { search } for name="de.robv.android.xposed.installer" dev="dm-0" ino=361360 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0 tclass=dir permissive=0
10-04 15:01:13.910 562 562 W zygote : type=1400 audit(0.0:17): avc: denied { read } for name="input" dev="tmpfs" ino=3234 scontext=u:r:zygote:s0 tcontext=u:object_r:input_device:s0 tclass=dir permissive=0
10-04 15:01:13.910 750 750 W sed_service_app: type=1400 audit(0.0:18): avc: denied { search } for name="de.robv.android.xposed.installer" dev="dm-0" ino=361360 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0 tclass=dhaz10-04 15:01:13.924 752 752 E Xposed : Permission denied while renaming log file /data/data/de.robv.android.xposed.installer/log/error.log -> /data/data/de.robv.android.xposed.installer/log/error.log.old
10-04 15:01:13.925 562 562 I Xposed : -----------------
10-04 15:01:13.926 562 562 I Xposed : Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH

That's why you don't have an Xposed log.

You can try to disable SELinux altogether. Or maybe Xposed has been installed improperly (like with wrong SELinux contexts).

How did you install Xposed?
[Xposed General] Donphillipe:
Give me about an hour to restore my system and install anew and run another log. In desperation there is a chance that I tried installing it directly from TWRP after it failed from direct install from Magisk, I can't remember actually how clean this install is. What version of Magisk should I be testing to install Xposed and should I install the generic one that tests to see what SDK I have installed or should I page down in the list and install the specific SDK23? Thanks!
[Xposed General] Donphillipe:
I believe this fresh restore and installation is a better illustration of the issue. I apologize, the last install was a serious botched job of many trials and errors. This one begins from a fresh install. (How about that it took me 7 hours instead of 1)

https://drive.google.com/file/d/1U408Hu7lTV2hTHSoeQ-UrwGWiakf31r-/view?usp=sharing
[Xposed General] Fif_:
The same SELinux error happens in this log file.

You can look for it yourself.

Was that a systemless or system install of Xposed? I assume systemless given the forum.

Have you tried the Unity Xposed module as opposed to the SDK-specific module? The Unity module is updated more frequently. If you had the Unity Xposed module, have you tried the SDK-specific one?
[Xposed General] Donphillipe:
Magisk installed from TWRP install; Xposed Unity run from Module add button on Magisk zpp. (Then stand alone 89.3 SDK(23) versions would not even unzip to install on this phone. Xposed systemless installer too.

I looked over the logs but this is my first experience seeing this log. I am a Windows guy and not even very good at that. I do appreciate the help and I hope someone sees a way for me to enjoy Xposed on the BLU STUDIO XL 2 which has been collecting dust in my closet for over a year awaiting Xposed. I now have a second crack in my old phone screen so my days are numbered. Thanks!

**** What would be my options from this point? Surely SELinux is running on other phones with Xposed, so how would I go about resolving my issue? Does the developer add new phones, is there a queue, etc???? Thanks again.
[Xposed General] FartyParty:
I guess no one here have gotten it to work on the new Sony phones?
[Xposed General] grymkmb:
Clear the app data and then make sure all modules are enabled again. Reboot.
[Xposed General] zoel.fahmi:
Hello

I've bought Redmi Note 4x

Already unlocked (bootloader)

Flash twrp, custom rom then custom kernel

Also magisk

The thing is, it'll go missing sometime

Any advice?

Also, mind to tell me about advanced setting?
[Xposed General] Fif_:
You can either:

1. Report a bug with Xposed, and wait for the fix.

2. Report a bug with Magisk and/or systemless Xposed. The bug may come from Magisk, or the Xposed packaging.

3. Run with SELinux disabled (potentially insecure, but you already run Xposed which is considered insecure in some circles). There are Magisk modules for that, but they may not with. You can also find a kernel with SELinux off, or hack the bootimage to pass selinux=off to the kernel at boot.

4. Hack the SELinux contexts, either by altering the contexts of the system image or Xposed installation, or adding a policy exception. Again, this may be insecure, but less so than solution #3.

5. Change ROMs or downgrade to an earlier android version.

No easy solution: #3 & #4 are not for the faint of heart, #1 is unlikely to produce quick results, #2 may work or not. #5 is your best shot.
[Xposed General] TheLazyHatGuy:
Installer link not working

Does anyone have a working link for the Xposed Installer. The one in attachments doesn't work
[Xposed General] DallasBelt:
For me it does work. Maybe it's a temporary server error? Anyway, here's the link to my personal cloud.
[Xposed General] enderffx:
This is probably the most stupid question ever asked:

Should i REALLY just install that XposedInstaller (v315) or then also start it and let it install its thing ?

Greetings. Ender
[Xposed General] jenslody:
Install systemless xposed through MagiskManager, install the xposed-installer from this thread and from inside the installer (yes you have to start it from app-drawer) install the xposed modules you want.
[Xposed General] enderffx:
Ah okay, so a different order ?

FIRST install xposed via Magisk downloader THEN install & use the 315 XposedInstaller ?

Did i get that right ?

Ender

P.S. sorry to be so tedious, but last time i bricked my Huawei P20 Pro it was a big mess :)
[Xposed General] jenslody:
I would say both should work in general.

I do not use xposed anymore.

Be sure to have a backup and if possible a working TWRP and "Magisk Manager for RecoveryMode", so you can disable the xposed-module from TWRP if it bricks your phone, what is always possible, but normally easy to fix (by disabling or removing it from TWRP) if it is systemless.
[Xposed General] enderffx:
okay, will try, thank you :)
[Xposed General] Eleo:
There is a module called Xposed framework (with no sdk beside it). That one has a script that decides on your sdk and installs Xposed installer apk beside xposed framework. You can try that
[Xposed General] enderffx:
Hi !

Meanwhile i did a full TWRP backup and installed Xposed..

However i have a problem as it does not really seem to work:

I installed Xposed via 3 methods (to try each possibility):

-via Magisk Download

-via XposedInstaller315

-via TWRP/Recovery

In all cases all seems to be fine, XposedInstaller shows a green Status Icon and correctly tells the Xposed version.

BUT my desired App (App2VR) shows "Xposed disabled" when starting.

Also 2 other xposed apps i tried (sensor disable & wake up on charge) do not work.

What i am doing wrong ?

OR is P20Pro / 8.1 not fully supported ?

Greetings,

Ender
[Xposed General] spawnlives:
Did you make sure that they were enabled and rebooted your phone.

Also as you mention I would check the module threads as they may not be updated to work on latest Android versions.
[Xposed General] enderffx:
Yes i made very sure of that.

Also deleted Dalvik and rebooted again.

I fear you are right and i am where i begun if my needed module is simply not working.

I need to find a module that IS working to make sure the Xposed is okay but not the module i need (App2VR)

Thnank you for your help !

Ender
[Xposed General] spawnlives:
You could try xprivacylua it's up to date

Also since exposed is still in beta stage for Oreo there are some bugs which will effect some modules.
[Xposed General] enderffx:
Hi !

hmm, i read up about xprivacylua but it seems it has nothing to do with my need (displaying a normal App in split screen aka vr mode).

Or did i misunderstand you ?

:)

Ender
[Xposed General] spawnlives:
I meant use xprivacylua to test exposed functionality

I don't use vr mode so I can't help you with an alternative app sorry.
[Xposed General] enderffx:
Ah okay !

I will try that (and other apps / modules) to prove or disprove that Xposed works in principle...

Greetings,

Nils

---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------

Ah okay !

I will try that (and other apps / modules) to prove or disprove that Xposed works in principle...

Greetings,

Nils
[Xposed General] plopingo:
XposedInstaller_3.1.5-Magisk.apk link is dead. Any can help for a mirror? Thanks
[Xposed General] Eleo:
https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/post77818423