[2019.5.1][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27)

[Manok98]

i get android is starting everyboot when i flash Xposed. how to solve this?

Galaxy s6 Edge

I had the same problem when I've installed the Magisk boot IMAGE. Are you sure that the problem is the Xposed framework? By installing another version of Magisk (v.9) for me System is started and now all work perfectly.

 

[LuanTeles]

I had the same problem when I've installed the Magisk boot IMAGE. Are you sure that the problem is the Xposed framework? By installing another version of Magisk (v.9) for me System is started and now all work perfectly.

Yeap. even system xposed gives me it, only unistalling xposed solves

 

[Veronezzi]

I recently bought a Moto G4 .... Coming from a Nexus 4 with CM i never bothered to use Magisk instead of the old default root+xposed instaled into system... But because Motorola locks a lot more the device than a Nexus, i tried to used Magisk + Xposed systemless.... And i bumped into a problem....

After unlocking the bootloader (while using 100% stock rom), if i enter at the bootloader mode in the device a message indicates that my G4 is unlocked, but running official software... If i try to install SuperSu systemless everything goes OK, and the smartphone keeps showing that the software is official (even after SuperSu modified the boot image, which is a necessary step to achieve the systemless root)...

So i thought that Magisk + Xposed Systemless would work the same way... After Magisk instalation, the message keeps being "Software Official" ... But as soon as i install Xposed Systemless, and reboot the device once, then immediately the message changes to "Software Modified" and i am unable to do any OTA update...

So i'm confused: SuperSu and Magisk both modify the boot image from the G4.... But why SuperSu is capable of modify it and the system doesn't see any change, but Magisk + Xposed modify it but aren't able to prevent the change detection as SuperSu does?

To add one more info: as i said, because Magisk + Xposed Systemless make changes at the boot image that are detected by the ROM, the phone status is changed from "Software Official" to "Software Modified", breaking any OTA updates... But if i re-flash the stock boot image, the OTA updates are able to be instaled again. (but then i lose SuperSu, Magisk and Xposed Systemless)

My main question: if SuperSu can patch the boot image to work, and that change is invisible to the smartphone, allowing me to do OTA updates, why Magisk + Xposed Systemless don't use the same technique ? I'm guessing that the technique is different because , like i said, the patched boot image from Magisk + Xposed is detected as altered, while installing SuperSu only doesn't generate any problem to the OTA updates...

In the actual scenario, at least for a Moto smartphone, the Magisk + Xposed Systemless aren't actually "systemless" .... Ok, they don't change the system image, but change the boot image, which leads to blocked OTA installation (because of the SOFTWARE MODIFIED status that checks the boot image, sees the alterations and stops the update), and at the end it acts as a system modification when anyone tries to update a Moto phone wiht Magisk + Xposed Systemless installed...

 

[Captain_Throwback]

I recently bought a Moto G4 .... Coming from a Nexus 4 with CM i never bothered to use Magisk instead of the old default root+xposed instaled into system... But because Motorola locks a lot more the device than a Nexus, i tried to used Magisk + Xposed systemless.... And i bumped into a problem....

After unlocking the bootloader (while using 100% stock rom), if i enter at the bootloader mode in the device a message indicates that my G4 is unlocked, but running official software... If i try to install SuperSu systemless everything goes OK, and the smartphone keeps showing that the software is official (even after SuperSu modified the boot image, which is a necessary step to achieve the systemless root)...

So i thought that Magisk + Xposed Systemless would work the same way... After Magisk instalation, the message keeps being "Software Official" ... But as soon as i install Xposed Systemless, and reboot the device once, then immediately the message changes to "Software Modified" and i am unable to do any OTA update...

So i'm confused: SuperSu and Magisk both modify the boot image from the G4.... But why SuperSu is capable of modify it and the system doesn't see any change, but Magisk + Xposed modify it but aren't able to prevent the change detection as SuperSu does?

To add one more info: as i said, because Magisk + Xposed Systemless make changes at the boot image that are detected by the ROM, the phone status is changed from "Software Official" to "Software Modified", breaking any OTA updates... But if i re-flash the stock boot image, the OTA updates are able to be instaled again. (but then i lose SuperSu, Magisk and Xposed Systemless)

My main question: if SuperSu can patch the boot image to work, and that change is invisible to the smartphone, allowing me to do OTA updates, why Magisk + Xposed Systemless don't use the same technique ? I'm guessing that the technique is different because , like i said, the patched boot image from Magisk + Xposed is detected as altered, while installing SuperSu only doesn't generate any problem to the OTA updates...

In the actual scenario, at least for a Moto smartphone, the Magisk + Xposed Systemless aren't actually "systemless" .... Ok, they don't change the system image, but change the boot image, which leads to blocked OTA installation (because of the SOFTWARE MODIFIED status that checks the boot image, sees the alterations and stops the update), and at the end it acts as a system modification when anyone tries to update a Moto phone wiht Magisk + Xposed Systemless installed...

The simplest answer to your question is that Magisk can't use the same method as SuperSU. SuperSU is proprietary and closed source software. Magisk is open source and uses open source tools. So I don't know exactly what's different, but you'll either have to deal with it, or just use SuperSU. The point of Magisk is to avoid making system modifications, not retain the integrity of your boot.img. If your device requires a stock boot.img in order to install an OTA, then flash it, take your OTA, and then re-flash Magisk. Your mods will still be there. THAT is the point of Magisk (among other things).

 

[Anagastes]

I have a problem with the new Magsik 10.2 and xposed 87.1 .... always "not active" complete removed and new flashed, same... :S

Now I have Xposed new installed... and its show me 87.0? I have xposed framework removed weird. I try the uninstaller-zip and make it new with magisk.

 

[Manok98]

I have a problem with the new Magsik 10.2 and xposed 87.1 .... always "not active" complete removed and new flashed, same... :S

Now I have Xposed new installed... and its show me 87.0? I have xposed framework removed weird. I try the uninstaller-zip and make it new with magisk.

What Rom and devices do you have?

 

[Anagastes]

What Rom and devices do you have?

It's Elephone P9000 with AEROM (based on last stock Android 6). The framework 87.1 is now completely new flashed with magisk. And Xposed App show me 87.0 (but its active)? Magisk say 87.1 weird. And no xposed modul works...
Sorry, I have no logcat for this problem :S

So, now I start a new flash and with new magisk 10.2... wish me luck.

sorry, my failure... selinux in this rom is very bad... -.-

 

[Manok98]

It's Elephone P9000 with AEROM (based on last stock Android 6). The framework 87.1 is now completely new flashed with magisk. And Xposed App show me 87.0 (but its active)? Magisk say 87.1 weird. And no xposed modul works...
Sorry, I have no logcat for this problem :S

So, now I start a new flash and with new magisk 10.2... wish me luck.

Ok, it's a "bug". Now is only 87.1 installed, Xposed app show 87.0.
And now is Xposed "active" but module don't work. cool! xD

I got back to Magisk v9 (v10.0 i can not find to download -.- ) and Xposed 87.0

Is strage that xposed modules don't Work...If you are using phh superuser, you can try to use systemless root. I will send you in a private message the files that you are searching (Xposed 87 and Magisk v.9). You can also use RootSwitch to byapass SafetyNET, following this guide: https://forum.xda-developers.com/xp...okemons-iv-t3469462/post70364293#post70364293. :good:
Good Luck

 

[Anagastes]

Is strage that xposed modules don't Work...If you are using phh superuser, you can try to use systemless root. I will send you in a private message the files that you are searching (Xposed 87 and Magisk v.9). You can also use RootSwitch to byapass SafetyNET, following this guide: https://forum.xda-developers.com/xp...okemons-iv-t3469462/post70364293#post70364293. :good:
Good Luck

Thx, but it was my failure... selinux in this rom is very very bad... i'm now on CM13. There works fine...

 

[ModUser01]

Is strage that xposed modules don't Work...If you are using phh superuser, you can try to use systemless root. I will send you in a private message the files that you are searching (Xposed 87 and Magisk v.9). You can also use RootSwitch to byapass SafetyNET, following this guide: https://forum.xda-developers.com/xp...okemons-iv-t3469462/post70364293#post70364293. :good:
Good Luck

Thanks I had the same problem, this solves all mine!

 

[naveenfre]

how to set root access to normal i installed phh's superuser,cts profile mismatch - false,

Sent from my MotoG3 using Tapatalk

 

[Artim_96]

how to set root access to normal i installed phh's superuser,cts profile mismatch - false,

Well, with XPosed you can't pass SN, go over to the main thread and search it

 

[Wesley_NL]

it fails at installing the magisk 10.2 zip
"updater process ended with error: 1, error installing zip file -/usb-otg/android/magisk-v10.2.zip"

and i followed your guide
install clean rom of audax
removed super su
rebooted into recovery
installed magisk v10.2zip
get the error

as followes
rebooted
installed magisk app
downloaaded installed pph superuser
reboot recovery
reinstall magisk v10.2 again
and error still the same

 

[Artim_96]

it fails at installing the magisk 10.2 zip
"updater process ended with error: 1, error installing zip file -/usb-otg/android/magisk-v10.2.zip"

and i followed your guide
install clean rom of audax
removed super su
rebooted into recovery
installed magisk v10.2zip
get the error

as followes
rebooted
installed magisk app
downloaaded installed pph superuser
reboot recovery
reinstall magisk v10.2 again
and error still the same

Wrong thread. Nothing to do with XPosed

 

[Wesley_NL]

oh ok

 

[abel408]

I'm having a problem installing this with systemless supersu. Magisk manager tells me I have root and I can download and install xposed from the app. When I reboot after installation, xposed installer app tells me that "xposed is installed, but not activated".
My log says this:
Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (no such file or directory)

Looking in that directory, I do not see an error.log. It is completely empty.

Another strange thing is that after I install systemless xposed, it doesn't seem to get along with facebook and facebook messenger. Those apps keep crashing... Even though xposed isn't even working.

I've tried uninstalling everything and starting clean probably about 5 times. I can install xposed without systemless, but that is not what I want.

 

[Artim_96]

I'm having a problem installing this with systemless supersu. Magisk manager tells me I have root and I can download and install xposed from the app. When I reboot after installation, xposed installer app tells me that "xposed is installed, but not activated".
My log says this:
Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (no such file or directory)

Looking in that directory, I do not see an error.log. It is completely empty.

Another strange thing is that after I install systemless xposed, it doesn't seem to get along with facebook and facebook messenger. Those apps keep crashing... Even though xposed isn't even working.

I've tried uninstalling everything and starting clean probably about 5 times. I can install xposed without systemless, but that is not what I want.

Does it even recompile the system after installation? If not it's obviously not running, but if, does only the app day that XPosed isn't running or do modules not have any effect?

 

[abel408]

Does it even recompile the system after installation? If not it's obviously not running, but if, does only the app day that XPosed isn't running or do modules not have any effect?

How can I tell if it recompiles the system? It seems to install successfully and tells me to reboot. Xposed will not let me activate the modules. It says "The latest version of Xposed is currently not active. Did you install the framework and reboot?" And the answer is obviously yes...

 

[Artim_96]

How can I tell if it recompiles the system? It seems to install successfully and tells me to reboot. Xposed will not let me activate the modules. It says "The latest version of Xposed is currently not active. Did you install the framework and reboot?" And the answer is obviously yes...

Well, 1. The restart takes much longer and 2. It tells you
"optimizing apps
X of xx"
Of that isn't happening, the core part of installation stunt kick in, it needs to recompile every app on order to include the hooks. Then just wipe cache and dalvik cache in TWRP

 

[hogze94]

Xposed installer said that official v86 systemless was installed (after i tried flashing xposed_uninstaller.zip, also dirty flashing my rom, also tried the material design uninstaller in the app), i ignored it and installed v87 systemless topjohnwu. Now it says that v87 is installed but not active but as far as i can see, xposed and the modules are working.

Is there remnantes of both versions still installed? Can i manually delete v86?

https://imgur.com/a/GNL3E

01-06 15:04:51.274 I/Xposed  ( 1069): -----------------
01-06 15:04:51.274 I/Xposed  ( 1069): Starting Xposed version 86.1 (by romracer / 20160928), compiled for SDK 23
01-06 15:04:51.274 I/Xposed  ( 1069): Device: Redmi Note 3 (Xiaomi), Android version 6.0.1 (SDK 23)
01-06 15:04:51.274 I/Xposed  ( 1069): ROM: cm_kenzo-userdebug 6.0.1 M4B30X 8e18e9be56 test-keys
01-06 15:04:51.274 I/Xposed  ( 1069): Build fingerprint: Xiaomi/kenzo/kenzo:6.0.1/MMB29M/6.7.21:user/release-keys
01-06 15:04:51.274 I/Xposed  ( 1069): Platform: arm64-v8a, 64-bit binary, system server: yes
01-06 15:04:51.274 I/Xposed  ( 1069): SELinux enabled: yes, enforcing: yes
01-06 15:04:52.291 I/Xposed  ( 1069): -----------------
01-06 15:04:52.291 I/Xposed  ( 1069): Added Xposed (/su/xposed/system/framework/XposedBridge.jar) to CLASSPATH
01-06 15:04:52.639 I/Xposed  ( 1069): Detected ART runtime
01-06 15:04:52.650 I/Xposed  ( 1069): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing
01-06 15:04:52.928 I/Xposed  ( 1069): Loading modules from /data/app/com.Taptigo.XposedModules.IgZoom-1/base.apk
01-06 15:04:53.059 I/Xposed  ( 1069):   Loading class com.Taptigo.XposedModules.IgZoom.RootHook
01-06 15:04:53.066 I/Xposed  ( 1069): Loading modules from /data/app/tw.fatminmin.xposed.networkspeedindicator-1/base.apk
01-06 15:04:53.080 I/Xposed  ( 1069):   Loading class tw.fatminmin.xposed.networkspeedindicator.Module
01-06 15:04:53.083 I/Xposed  ( 1069): Loading modules from /data/app/com.marz.snapprefs-1/base.apk
01-06 15:04:53.182 I/Xposed  ( 1069):   Loading class com.marz.snapprefs.HookMethods
01-06 15:04:53.213 I/Xposed  ( 1069): Loading modules from /data/app/biz.bokhorst.xprivacy-1/base.apk
01-06 15:04:53.260 I/Xposed  ( 1069):   Loading class biz.bokhorst.xprivacy.XPrivacy
01-06 15:04:53.631 I/Xposed  ( 1069): Loading modules from /data/app/ma.wanam.youtubeadaway-2/base.apk
01-06 15:04:53.643 I/Xposed  ( 1069):   Loading class ma.wanam.youtubeadaway.Xposed
01-06 15:04:53.644 I/Xposed  ( 1069): Loading modules from /data/app/com.pyler.youtubebackgroundplayback-1/base.apk
01-06 15:04:53.652 I/Xposed  ( 1069):   Loading class com.pyler.youtubebackgroundplayback.YouTubeBackgroundPlayback
01-06 15:04:53.653 I/Xposed  ( 1069): Loading modules from /data/app/com.devadvance.rootcloak2-2/base.apk
01-06 15:04:53.665 I/Xposed  ( 1069):   Loading class com.devadvance.rootcloak2.RootCloak
01-06 15:04:53.665 I/Xposed  ( 1069): Loading modules from /data/app/com.germainz.crappalinks-1/base.apk
01-06 15:04:53.677 I/Xposed  ( 1069):   Loading class com.germainz.crappalinks.CrappaLinks
01-06 15:05:01.398 I/Xposed  ( 1070): -----------------
01-06 15:05:01.398 I/Xposed  ( 1070): Starting Xposed version 86.1 (by romracer / 20160928), compiled for SDK 23
01-06 15:05:01.398 I/Xposed  ( 1070): Device: Redmi Note 3 (Xiaomi), Android version 6.0.1 (SDK 23)
01-06 15:05:01.398 I/Xposed  ( 1070): ROM: cm_kenzo-userdebug 6.0.1 M4B30X 8e18e9be56 test-keys
01-06 15:05:01.398 I/Xposed  ( 1070): Build fingerprint: Xiaomi/kenzo/kenzo:6.0.1/MMB29M/6.7.21:user/release-keys
01-06 15:05:01.398 I/Xposed  ( 1070): Platform: arm64-v8a, 32-bit binary, system server: no
01-06 15:05:01.398 I/Xposed  ( 1070): SELinux enabled: yes, enforcing: yes
01-06 15:05:01.403 I/Xposed  ( 1070): -----------------
01-06 15:05:01.403 I/Xposed  ( 1070): Added Xposed (/su/xposed/system/framework/XposedBridge.jar) to CLASSPATH
01-06 15:05:01.676 I/Xposed  ( 1070): Detected ART runtime
01-06 15:05:01.698 I/Xposed  ( 1070): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing
01-06 15:05:01.912 I/Xposed  ( 1070): Loading modules from /data/app/com.Taptigo.XposedModules.IgZoom-1/base.apk
01-06 15:05:02.035 I/Xposed  ( 1070):   Loading class com.Taptigo.XposedModules.IgZoom.RootHook
01-06 15:05:02.044 I/Xposed  ( 1070): Loading modules from /data/app/tw.fatminmin.xposed.networkspeedindicator-1/base.apk
01-06 15:05:02.067 I/Xposed  ( 1070):   Loading class tw.fatminmin.xposed.networkspeedindicator.Module
01-06 15:05:02.071 I/Xposed  ( 1070): Loading modules from /data/app/com.marz.snapprefs-1/base.apk
01-06 15:05:02.187 I/Xposed  ( 1070):   Loading class com.marz.snapprefs.HookMethods
01-06 15:05:02.217 I/Xposed  ( 1070): Loading modules from /data/app/biz.bokhorst.xprivacy-1/base.apk
01-06 15:05:02.267 I/Xposed  ( 1070):   Loading class biz.bokhorst.xprivacy.XPrivacy
01-06 15:05:02.568 I/Xposed  ( 1070): Loading modules from /data/app/ma.wanam.youtubeadaway-2/base.apk
01-06 15:05:02.576 I/Xposed  ( 1070):   Loading class ma.wanam.youtubeadaway.Xposed
01-06 15:05:02.578 I/Xposed  ( 1070): Loading modules from /data/app/com.pyler.youtubebackgroundplayback-1/base.apk
01-06 15:05:02.589 I/Xposed  ( 1070):   Loading class com.pyler.youtubebackgroundplayback.YouTubeBackgroundPlayback
01-06 15:05:02.590 I/Xposed  ( 1070): Loading modules from /data/app/com.devadvance.rootcloak2-2/base.apk
01-06 15:05:02.602 I/Xposed  ( 1070):   Loading class com.devadvance.rootcloak2.RootCloak
01-06 15:05:02.602 I/Xposed  ( 1070): Loading modules from /data/app/com.germainz.crappalinks-1/base.apk
01-06 15:05:02.618 I/Xposed  ( 1070):   Loading class com.germainz.crappalinks.CrappaLinks
01-06 15:05:39.212 E/XposedInstaller( 7352): AdvancedInstallerFragment -> Unable to resolve host "raw.githubusercontent.com": No address associated with hostname
01-06 15:06:24.464 I/Xposed  ( 9446): YouTube: com.google.android.youtube 11.39.56 loaded!
01-06 15:06:24.464 I/Xposed  ( 9446): YouTube AdAway 3.4.1: Trying brute force way...
01-06 15:06:34.435 I/Xposed  ( 9807): [Taptigo-XposedZoomForInstagram] Hooking Instagram
01-06 15:06:38.347 I/Xposed  ( 9855): [Taptigo-XposedZoomForInstagram] Hooking Instagram
01-06 15:06:59.254 I/Xposed  (11123): [Taptigo-XposedZoomForInstagram] Hooking Instagram

Just reflashed stock boot.img and still saying v86 is installed.