Database Users

Magisk and Xposed installed, but Root not working

I just unlocked my bootloader on my new Axon 7 and wanted to go Systemless in regards to root, etc.
I've installed Magisk, Magisk's Xposed, and tried to install the Magisk provided PHH Superuser. Everything seemed to flash correctly and rebooting my phone and installing the companion apps shows that Magisk is working, and so is Xposed. But there's no sign of Root working except for the Magisk Manager saying Root is mounted. None of the options in Magisk Manager work either, I presume because the app doesn't have its needed root access.
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ZTE A2017U using Tapatalk

interessting, seems you are further than i am (2017G B03), which firmware version are you using? Want to try to use that boot.img
when i tried magisk it didn't mount root, nor where the toggles activated

Starvirus said:
interessting, seems you are further than i am (2017G B03), which firmware version are you using? Want to try to use that boot.img
when i tried magisk it didn't mount root, nor where the toggles activated
Click to expand...
Click to collapse
I'm on 2017U B27. Bootloader unlocked.
Sent from my ZTE A2017U using Tapatalk

So yeah, I've given up on Magisk for now. Tried to install SuperSU instead of PHH, and TWRP would crash when trying to flash it.
I tried installing SuperSU outside of Magisk, ie: normal method, and it kind of worked, but for some reason Magisk Xposed would cause the SuperSU app to freeze whenever the framework was enabled.
So without being able to get them to work together I've just given up on Magisk for now. I uninstalled Magisk Xposed, and then Uninstalled Magisk itself. Finally I restored my bootloader backup so I could start off fresh, and then installed SuperSU and Xposed normally.
I'll just have to give up on Android Pay again. Seriously wish someone would just come up with an Xposed module to bypass that stupid Safetynet api already.
Sent from my ZTE A2017U using Tapatalk

Delete...

@Oogar you deleted your post does it mean it didn't work for you? i couldn't get it to work only got as far as the OP (with a modified hybrid boot.img from EU b03 and US b27 rom) on my A2017G

Starvirus said:
@Oogar you deleted your post does it mean it didn't work for you? i couldn't get it to work only got as far as the OP (with a modified hybrid boot.img from EU b03 and US b27 rom) on my A2017G
Click to expand...
Click to collapse
Yeah I thought it was all good, but in reality things were not working. Pokémon GO is the app I was using to test. I am able to toggle root but it doesn't seem to actually do anything.
Tried going to Suhide route with SuperSU 2.65 in systemless mode, then upgrade to 2.78(SR1) but still no luck that way either. A little bit lost at this point.
Reverted back to SuperSU + Regular xposed for the time being.

@Oogar can you check if you have a magisk.log or magisk_last.log in /cache/ if so could you upload it?

Starvirus said:
@Oogar can you check if you have a magisk.log or magisk_last.log in /cache/ if so could you upload it?
Click to expand...
Click to collapse
No log at this point...restored a TWRP backup which was captured right after B27 upgrade

I am encountering the same issue and there is no magisk.log or magisk_last.log created in /cache/

From stock 4.4.3 to latest 5.0 (RU1.1.34) with Magisk v9 (xposed not yet working)

A short summary of upgrading my YotaPhone 2 to run Magisk v9 on the latest RU lollipop build (1.1.34) because I've seen no threads about Magisk here yet and writing my experience down might help others (or myself in the future).
Background: Got the phone last week from bestgear, and I'm surprised at how great it is. The EPD is much more responsive than I expected. And the phone looks just great! So much has changed/improved in the modding community in the last years (and I got out of touch with it), that I decided to go cutting edge with systemless Xposed through Magisk with root hiding, having no experience with either.
Lollipop
The phone had exactly the same about screen as in the lollipop upgrade thread so I sort-of followed that and subsequently went for the latest Russian version (RU1.1.134).
However, my setup prevented flashing directly to any of the 5.0 versions. The YotaPhoneFlasher showed that flashing /system failed (which can be seen by scrolling up on the prompt about flashing the user data). Probably due to the file size being too large. However, this procedure seemed to do the trick (see above thread for details):
Flash 5.0.0-RU1.1.124. Booting hangs at the 'Powered by Android' screen.
Flash 4.4.3-S01-003-RU1.0.3.61a. Booting succeeds.
Somehow, it now knows that it can perform an OTA update and proceeds through several versions to get to RU1.1.134
Not sure whether the RU version is worth it though, because it adds some bloatware like a Russian NFC payment app, a Russian air plane app and a dictionary app that primarily supports to/from Russian.
TWRP
Subsequently the recovery was flashed to TWRP 2.8.5.0. This seems a rather old version of TWRP though, perhaps too old to flash Magisk v9, see below. (This is my first TWRP experience as well, absolutely fabulous compared to older recoveries!)
Magisk
Magisk v9 refused to install directly. Flashing Magisk-v9.zip always ended up with either "E: footer is wrong" or "E:Error executing updater binary in zip". I tried to 'Install' from TWRP and to 'adb sideload' from both TWRP and modified stock recovery. Googling these errors lead me to believe that it might be related to the TWRP version. (The download was fine, because the zip file was exactly the same as the one that the Magisk Manager installed.)
In the end it was rather simple:
Flash Magisk-v8.zip
Install the magisk version of phh's superuser (and the corresponding Superuser app).
Install Magisk Manager
Upgrade Magisk to v9 from within the manager.
The "Emoji One" module proved that Magisk works (by replacing all the smilies). However, couldn't get Pokemon Go to login, so the root hiding might not work, but I didn't try PoGo before installing Magisk, so could be another issue.
Xposed
My actual goal was experimenting with Xposed, but the Xposed Installer keeps saying that the "Xposed Framework is installed, but not active." I'll keep you posted if I manage to get it working.
Some more notes:
A windows 10 laptop was used for all of the flashing (because the YotaPhoneFlasher software is windows only it seems).
Several reboots and cache/data wipings were omitted from the above. These did make the process take ages though, updating all the apps etc. all the time.
Thank you for all the information on this forum that let me get this far. I'm very happy with having a Lollipop YotaPhone with root.

Thank you for your detailed experience. I read the magisk thread here on XDA buy I didn't understand why is it for? And another question, why are you installing xposed? Are there benefits or special added features added to our Yotaphone?

I'm both new to Magisk and Xposed myself, and indeed it is not directly clear 'what these are for' from their xda posts. So I decided to just try them out and see for myself.
Xposed allows hundreds of modules to be installed to alter the OS in one way or the other. I'm most interested in Xprivacy, which should allow the user to limit what data / functionality apps can access and provides apps with mock data and such. Like a fine grained permission system I think.
Magisk also allows modules to alter the OS, but there seem to be only a handful, including Xposed. The selling point of Magisk is, if I understand correctly, that it does not alter the system partition. This makes it easy to apply future OTA updates etc. Supposedly it can also hide itself and root from certain apps.
It's not that important to me, so not sure whether I'll continue my exploration soon. (The Magisk threads are many, many pages, so it could take quite some research to get it to work properly.)

Did you get any further with Magisk & Xposed? My YD201 just arrived and I'm trying to decide how to proceed with hacking the crap out of it.

hippy dave said:
Did you get any further with Magisk & Xposed?
Click to expand...
Click to collapse
Not yet hippy dave. The Marshmallow beta came out soon after my initial experiments and I decided to wait for the official Marshmallow release before experimenting further. My concern was that I didn't want to redo the entire process every other week, and I messed something up so I can't boot to recovery...
The final Android 6.0 rom seems to take a while, so maybe it is worthwhile to continue with the latest beta. My plan is to first fix my recovery partition somehow, then upgrade to the latest Marshmallow beta, and then try Magisk again. I don't want to use the 'normal' system-partition-modifying Xposed because I like the cleanliness that Magisk promises. I haven't followed the Magisk development since, so maybe things have changed.
Your experiences would be welcome.

BlackShift said:
Your experiences would be welcome.
Click to expand...
Click to collapse
Makes sense, I decided to skip the MM beta for now and wait for release, but I couldn't wait that long to get root etc, so I tried Magisk out on the latest Russian LP. First I tried the latest release of Magisk 11.x, and then the latest unofficial source build 12.x, and tho it installed (with TWRP 3 latest version) and worked fine in terms of root, I couldn't get Magisk Hide to work and pass SafetyNet. Tried all the tips I could find like turning off USB debugging, turning things off & on in Magisk in a particular order with reboots in between etc. So I gave up for now and didn't get as far as trying Xposed for Magisk or any other modules.
For the time being I decided to go with the tried and tested stuff, standard root and regular Xposed, and will reevaluate when Marshmallow gets an official release or if I hear of improvements to Magisk Hide.

hippy dave said:
Makes sense, I decided to skip the MM beta for now and wait for release, but I couldn't wait that long to get root etc
Click to expand...
Click to collapse
The official MM came out a couple of days ago, but so far, no more success than you got.
Updated to MM. Forgot how, it refused to update over the air, so think I adb sideloaded the full 1.34 OTA with TWRP. Safetynet check from Magisk manager successful (of course).
Installed TWRP 3.0 and the official Magisk 12. However, the Magisk root seemed to have failed, also after a reboot. Safetynet check failed.
Installed SuperSU systemless by typing echo SYSTEMLESS=true>>/data/.supersu in the TWRP command prompt because SuperSU failed to install systemless automatically. Magisk Hide claims it doesn't operate that well with SuperSU, and safetynet check failed.
So Magisk and root access works, but not root hiding. Which kinda defeats the point of using Magisk. I didn't try many of the clever tricks you refer to though and I gave up for now. It is supposedly cleaner than other methods of rooting, so I'll keep it anyway. Next up is
(Not really relevant to this thread.) Getting 800Mhz band to work
Getting XPosed installed systemless.
Perhaps send a boot image to the Magisk team so they can improve the support for our yotaphones? Not sure how this process works.

Hi, has there been any more progress with Magisk and Yotaphone? My bank finally started using Android Pay, so I'm keen to have another crack at hiding root. I don't think there have been any changes to Yotaphone firmware since you last posted, but I don't know what progression there's been with Magisk. Maybe when I have the chance I'll try to send the Magisk people whatever they need to try and get it working.

I haven't made any attempts since last time and probably won't soon. Let us know if you are successful.

Ok I did a fresh install of the latest Russian MM (kept my data tho), installed the current Magisk release version (14.0), and it just worked straight off, Android Pay is running happily and root is working in the few root apps I've tried so far. Only downside so far is no Xposed, there's an unofficial Xposed for Magisk but it doesn't pass Safety Net so would presumably break Android Pay. I'm gonna see what Magisk modules are available and if they can fill the void, and decide from there I guess.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Woop, finally got SafetyNet passing while Xposed is running (as slightly evidenced by the circle battery).
This wasn't straightforward, and didn't end up using Magisk. This is using SuperSU, suhide v0.55, and a patched system library (I had to patch the yotaphone one myself, let me know if anyone wants it).
The only quirk now is that the Xposed Installer doesn't see the xposed framework as installed/active, even tho the framework and modules are working fine. Gonna investigate that too, but can work around it for now. edit: Compiled my own version of Xposed Installer with tweaked paths and now it works fully.

hippy dave said:
Woop, finally got SafetyNet passing while Xposed is running (as slightly evidenced by the circle battery).
This wasn't straightforward, and didn't end up using Magisk. This is using SuperSU, suhide v0.55, and a patched system library (I had to patch the yotaphone one myself, let me know if anyone wants it).
The only quirk now is that the Xposed Installer doesn't see the xposed framework as installed/active, even tho the framework and modules are working fine. Gonna investigate that too, but can work around it for now. edit: Compiled my own version of Xposed Installer with tweaked paths and now it works fully.
Click to expand...
Click to collapse
Would you please send me the patched library ?
Sent from my YD201 using Tapatalk

stanley321 said:
Would you please send me the patched library ?
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Sure thing, I'll attach it to this post. You might know that you have to fix the file contexts when you replace the original library with the patched one - I'd boot into TWRP and use adb push to put the file into place, then adb shell and use the following command in the right directory:
chcon --reference=libandroid.so libandroid_runtime.so

Is 9.0 released?

Pinch me, I may be dreaming, but I think the final 9.0.0 build has been released! Correct me if this is some kind of beta/DP.
From https://developers.google.com/android/images:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yes

Magisk 16.7 & TWRP 3.2.2-0 working fine. Unable to decrypt data in TWRP though. Any suggestions?

https://arstechnica.com/gadgets/2018/08/google-finalizes-android-p-as-android-9-pie-launching-today/

m0h1t said:
Magisk 16.7 & TWRP 3.2.2-0 working fine. Unable to decrypt data in TWRP though. Any suggestions?
Click to expand...
Click to collapse
Remove your PIN/Passcode password in Android, reboot in TWRP and do what you have to do.
Re-configure the PIN/Passcode in Android.

With PP5 running as DD did a edit of -W for PPR1 and survived the update from PP5 to PPR1 with my data intact. Great!!
Was running PP5 with twrp 3.2.1-2 and Magisk 16.4 when updated. No security or PIN. Found Magisk 16.4 on reinstall from overwrite not
working didn't get past first G screen. Rewrote over with -W still and found Magisk 16.7 worked fine... FOR NOW....ymmv

kkjb said:
With PP5 running as DD did a edit of -W for PPR1 and survived the update from PP5 to PPR1 with my data intact. Great!!
Was running PP5 with twrp 3.2.1-2 and Magisk 16.4 when updated. No security or PIN. Found Magisk 16.4 on reinstall from overwrite not
working didn't get past first G screen. Rewrote over with -W still and found Magisk 16.7 worked fine... FOR NOW....ymmv
Click to expand...
Click to collapse
How do you do -w? Does this mean I can install Android p over most recent development preview and keep root and TWRP?

Xdevillived666 said:
How do you do -w? Does this mean I can install Android p over most recent development preview and keep root and TWRP?
Click to expand...
Click to collapse
Yes, you can install stable over beta, following this guide I made, which looks like still working.
Just pick latest zips such as magisk and twrp and you're good.
I also recommend disable magisk modules before the flash, so you won't face any possible issue, just as a precaution.

I just installed Lineage OS 15.1 and got that all working... now this drops. I think I'll wait a while before I go to this.

I had no issues installing the 9.0 factory image over the 8.1 July update without the data wipe option. I reinstalled TWRP 3.2.2.0 using its install procedure. I needed to upgrade Magisk 16 to the beta version 16.7 in order to get the SafetyNet check to work properly.
So far no issues to report although Pie is not as zippy as it was running on Oreo.
Sent from my SHT-AL09 using Tapatalk

Currently running Stock Oreo with TWRP and Magisk root, AM i good to accept the auto update?

dantexaiver said:
Currently running Stock Oreo with TWRP and Magisk root, AM i good to accept the auto update?
Click to expand...
Click to collapse
I was also surprise to see that the OTA is available, even if I'm also rooted with Magisk, have unlocked bootloader and TWRP installed. So same question here, is it safe to let the auto-install do the job? Or do we need to download the OTA and install it from a computer using fastboot / adb sideload ? I'm new with this device and I read lots of story of people hardbricking there phone! I don't wan't to mess with it.

Milous98 said:
I was also surprise to see that the OTA is available, even if I'm also rooted with Magisk, have unlocked bootloader and TWRP installed. So same question here, is it safe to let the auto-install do the job? Or do we need to download the OTA and install it from a computer using fastboot / adb sideload ? I'm new with this device and I read lots of story of people hardbricking there phone! I don't wan't to mess with it.
Click to expand...
Click to collapse
I bit the bullet and did the ota update , root was broken so had to boot back into TWRP and flash Magisk but other than that things went smooth

dantexaiver said:
I bit the bullet and did the ota update , root was broken so had to boot back into TWRP and flash Magisk but other than that things went smooth
Click to expand...
Click to collapse
Ok so no problem with the modified boot.img from Magisk ? I'll wait for the latest stable for Magisk and I'll do the update via OTA if everything is fine!

Milous98 said:
Ok so no problem with the modified boot.img from Magisk ? I'll wait for the latest stable for Magisk and I'll do the update via OTA if everything is fine!
Click to expand...
Click to collapse
I ran Magisk 16.7 beta and EX kernel with no issues

dantexaiver said:
I ran Magisk 16.7 beta and EX kernel with no issues
Click to expand...
Click to collapse
Did Magisk pass safetynet with 16.7 beta?

queerquirks said:
Did Magisk pass safetynet with 16.7 beta?
Click to expand...
Click to collapse
For me it did not.

Alaadragonfire said:
For me it did not.
Click to expand...
Click to collapse
There's a 1674 version available but for pixel 2 xl. You could test that version?

queerquirks said:
Did Magisk pass safetynet with 16.7 beta?
Click to expand...
Click to collapse
With Flying Colors

I used magisk 1671, no issues, safetynet passes.
I asked in their forums, 1674 is only for pixel 2/xl

Updating Or Installing Magisk 17.0 resulted in bootloop

Is There any Other Way To Update Magisk?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

prawinraj8045 said:
Is There any Other Way To Update Magisk?
Click to expand...
Click to collapse
i am also faced same problem while updating to magisk 17

I haven't updated magisk but what method did you use to update? Via recovery or by patching the boot image?

patching the boot image failed, then tried to update via recovery, then became boot loop. can't even flash magisk v16 after this procedure in twrp. my device became rootless. i need to do full wipe and start from beginning again

Before flashing magisk 17 , I'll suggest removing 16 by flashing magisk uninstaller from twrp, after this , flash magisk 17.

Lucky me
Not happened to me, just flash via twrp and wipe devlik cache
Reboot and pray

100% working solution to upgrade Magisk to 17.00 without BootLoop
Please follow the below Steps to update Magisk without getting into a bootloop.
1. Uninstall the Magisk by using the uninstall .zip
2. Now flash the ver 17.00 and it will work just fine.
This will work 100%

I faced same issue.
Just uninstall with uninstaller and re install it will fix issues

I had just updated by patching the boot image then flashing through fastboot. It worked with no bootloops for me.

Update to v17.1

vitcp said:
patching the boot image failed, then tried to update via recovery, then became boot loop. can't even flash magisk v16 after this procedure in twrp. my device became rootless. i need to do full wipe and start from beginning again
Click to expand...
Click to collapse
You just need to use Magisk Uninstaller in TWRP before updating! Nd then install Magisk 17.1 which is latest as of today

rocky29b4u said:
Please follow the below Steps to update Magisk without getting into a bootloop.
1. Uninstall the Magisk by using the uninstall .zip
2. Now flash the ver 17.00 and it will work just fine.
This will work 100%
Click to expand...
Click to collapse
I have downloaded the uninstaller and tried running it but failed. Error 1. Says something about unable to mount partition. I even run the decrypt first but it still fail. Should I run the uninstalled from within Magisk? Appreciate any advice.

abubin said:
I have downloaded the uninstaller and tried running it but failed. Error 1. Says something about unable to mount partition. I even run the decrypt first but it still fail. Should I run the uninstalled from within Magisk? Appreciate any advice.
Click to expand...
Click to collapse
Your system partition cannot be mounted due to encryption. If possible, try uninstalling from Magisk itself

abubin said:
I have downloaded the uninstaller and tried running it but failed. Error 1. Says something about unable to mount partition. I even run the decrypt first but it still fail. Should I run the uninstalled from within Magisk? Appreciate any advice.
Click to expand...
Click to collapse
Which partition does it say about not being able to mount ?

rocky29b4u said:
Which partition does it say about not being able to mount ?
Click to expand...
Click to collapse
The uninstaller.zip that is not working with Error 1 and unable to remove magisk.
I already tried running decrypt first then run the uninstaller but still doesn't work.
Edit: Nevermind, I flashed with latest firmware, decypt, magisk 17.1, camera2api and all working fine. Rebooted to firmware 326 now with magisk 17.1. All seems to be working fine and fingerprint is faster! Will see how it goes because the fingerprint scanner usually goes back to being sloppy after a week of update.

Magisk won't install after update

Hey guys,
After updating my oos magisk won't apper -.-
What I've done:
I dirty flashed from OOS 9.0.1 to 9.0.5 with this order:
unistall magisk, installed new oos, installed magisk v19.2, installed latest franco.
After reboot I uninstalled the magisk apks, because there were two of them. After that I tried to install the latest magisk manager (v7.2) but it says "App was not installed"
What I've tried:
I tried to reinstall magisk in TWRP
I tried to reinstall OOS
nothing worked..
Does anyone have an idea what to do?

yannick818 said:
Hey guys,
After updating my oos magisk won't apper -.-
What I've done:
I dirty flashed from OOS 9.0.1 to 9.0.5 with this order:
unistall magisk, installed new oos, installed magisk v19.2, installed latest franco.
After reboot I uninstalled the magisk apks, because there were two of them. After that I tried to install the latest magisk manager (v7.2) but it says "App was not installed"
What I've tried:
I tried to reinstall magisk in TWRP
I tried to reinstall OOS
nothing worked..
Does anyone have an idea what to do?
Click to expand...
Click to collapse
How exactly did you uninstall magisk and what was your previous magisk version(before 19.2)? You're aware that newer magisk versions have issues?

strongst said:
How exactly did you uninstall magisk and what was your previous magisk version(before 19.2)?
Click to expand...
Click to collapse
Before flashing the new OOS i've flashed the magisk uninstaller.
Later in the OS i've uninstalled the magisk manager apps while simply hitting the uninstall button.
strongst said:
You're aware that newer magisk versions have issues?
Click to expand...
Click to collapse
That's why I'm always use the stable versions. Didn't thought there will be problems while uninstalling the manager apps.

I think I found the cause of the issue:
The apk installer thinks that there is currently a version of magisk manager installed..
Sorry for the big picture. Don't know how to post a better looking one...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

yannick818 said:
I think I found the cause of the issue:
The apk installer thinks that there is currently a version of magisk manager installed..
Sorry for the big picture. Don't know how to post a better looking one...
Click to expand...
Click to collapse
Solved the issue via adb.
typed: adb uninstall com.topjohnwu.magisk
After that the intallation of the magisk manager works fine
(Thanks to the magisk FAQ)