Develop Bugs

[GUIDE][ROOT][TWRP] Marshmallow(6.01) Sprint G920P root/TWRP using Magisk and Odin

I rooted my galaxy S6 a couple of days ago and wow was it totally worth tripping Knox, any way I am writing this because I could not find a thread that had a guide usng these methods. I had to figure out how to get past several errors in TWRP and Magisk and I thought some people might be curious how I did it. I did not make any of these programs used, credit to the original authors. I did this so I could play Pokemon Go with root.
WARNING: THIS WILL TRIP KNOX AND MAY BRICK YOUR PHONE. DO THIS AT YOUR OWN RISK I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS. MAKE SURE YOU HAVE A FULL BACKUP OF YOUR DEVICE BEFORE CONTINUING. THIS WILL ALSO DISABLE OTAS.
Prerequisites:
Odin (make sure its version 3.10.6 others may not work): https://androidmtk.com/download-odin-downloader-versions
Galaxy s6 (have not tested on edge)
TWRP in .tar format for your model: https://dl.twrp.me/zerofltespr/
Stock ROM in case you mess up
Windows PC
Magisk v11.1: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk manager: https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en
Installing TWRP:
1.) Download all the necessary files and extract Odin to your desk top.
2.) Go into developer mode on your phone and enable OEM unlocking and USB debugging.
3.) Turn off your phone and enter download mode by holding power button, home button and volume down until the screen comes up that says something along the lines of installing a custom OS is dangerous, push volume up to continue.
4.) Plug your phone into your computer and start Odin.exe.
5.) Make sure Odin says "added" in the text window.
6.) Click on AP and browse for the TWRP .tar that you downloaded in the beginning.. Check the box next to AP once TWRP is loaded, then click "Start".
A.) If TWRP fails to install go to "options" and un-check "auto reboot". If this is un-checked make sure to reboot into recovering when Odin says "reset" by first exiting download mode by repeating the steps used to get into it and then holding home, power button and volume up until the TWRP logo appears.
7.) Congratulations you have now installed TWRP!
Rooting and installing Magisk:
1.) This will not work unless you have followed my previous steps.
2.) Make sure your phone is in recovery mode by holding power button, home, and volume up until the TWRP logo appears.
3.) Make sure your PC recognizes the phone and copy the Magisk 11.1 .Zip you downloaded earlier.
4.) Tap install on TWRP and and browse for the Magisk 11.1 .Zip, swipe to install.
5.) When it is done installing tap reboot.
6.) When your phone is done rebooting install Magisk manager from the play store.
7.) When you open Magisk it should say rooted with MAGISKSU in the center box.
A.) If it does not say that flash Magisk 11.1 in TWRP again.
B.) If the above does not work re-flash to stock and repeat all steps again.
8.) You are now rooted.
A.) If you would like to use Magisk hide tap the first box where it says install Magisk and follow the onscreen instructions.
1.) You can try rebooting your phone when it asks you too, but it would not install this way for me.
B.) After you have installed Magisk Framework, go into to settings and enable the hide Magisk option.
C.) Go back to the status section and tap on safety net check, it should be a green check-mark
1.) If it is not green restart and install Magisk again, then go into settings and disable and re-enable Magisk hide.
2.) If it is not green after doing the above re-flash the stock ROM and start over.
9.) You will have to reinstall Magisk Framework every-time you reboot, your root should stay installed after a reboot though.

That is the wrong version of TWRP for a Sprint phone. The correct version is here: https://dl.twrp.me/zerofltespr/
There is a thread with links to the latest stock TAR files, correct version of TWRP for this phone and SuperSU here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862

koop1955 said:
That is the wrong version of TWRP for a Sprint phone. The correct version is here: https://dl.twrp.me/zerofltespr/
There is a thread with links to the latest stock TAR files, correct version of TWRP for this phone and SuperSU here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
Thanks for pointing that out.

hmm, may I ask what advantages we get from this root method?
thank you.

You can hide your root and play Pokemon Go XD. I just think its more convientant having all my control apps super su and busy box in one place.
Sent from my SM-G920P using Tapatalk

Thank you for this.!!!!!!!!! 10/10

joej191 said:
Thank you for this.!!!!!!!!! 10/10
Click to expand...
Click to collapse
Your welcome. Glad I could help.
Sent from my SM-G920P using Tapatalk

Is magisk supposed to be installed after every reboot, or is that one of the many G920p specific issues?

I believe it is a GP20 specific issue because I have install mine after every reboot.

flett044 said:
I believe it is a GP20 specific issue because I have install mine after every reboot.
Click to expand...
Click to collapse
I just read this on the OP magisk thread: "magisk doesn't play well with Samsung devices. Try a custom kernel"
So i flashed the skyhigh kernel and now magisk is surviving restarts... the trouble is, Skyhigh auto intalls supersu and busybox.
Supersu isn't compatible with magisk, and i THINK that kind of busybox fails safetynet.
... so i used the busybox app to Uninstall busybox and the supersu app to do a full unroot and mount the stock boot image. (All to see if I could get magisk fully working) Then wipe davlik/cache, flashed the magisk.zip... booted up and opened the magisk manager, magisk was still installed, and magisksu was "properly installed"... but i fail safetynet attest now so i don't know what thats about.
Wondering if any of the veterans can chime in about any of this, since magisk indeed is pretty glitchy on the stock kernel.
Tl;dr: magisk doesn't work well with stock kernel, not sure how to get it working with custom kernel

I would also like to learn how to install magisk in sky high kernal.

Hey @tdhite do you have any input on this? I assume it would break synapse support to use magisk and magiskSu instead of supersu and the normal busybox, but worth it.
Quick recap: trying to run a magisk set-up with a custom kernel. Presumably using magiskSu.

still work?
@flett044,
Does this hidden root option still work with latest version of Pokemongo?
thanks

Yes it still works.

Nye-uhls said:
Hey @tdhite do you have any input on this? I assume it would break synapse support to use magisk and magiskSu instead of supersu and the normal busybox, but worth it.
Quick recap: trying to run a magisk set-up with a custom kernel. Presumably using magiskSu.
Click to expand...
Click to collapse
The boot routines currently use a policy tool specifically provided by SuperSu which is not available in Magisk. Access to files needed by various processes executed periodically (cortexbrain, cron jobs and others) may fail, but that would not be a critical failure, just a 'bummer' in the worst case. The startup routine is smart enough to check the policy tools and will cleanly boot even if SuperSu's tools aren't around.
Long story short, the kernel should work fine, you'll just miss out on certain things that try to run now and then to 'tune' the system.

How would I go about replacing supersu with Magisk?

tdhite said:
The boot routines currently use a policy tool specifically provided by SuperSu which is not available in Magisk. Access to files needed by various processes executed periodically (cortexbrain, cron jobs and others) may fail, but that would not be a critical failure, just a 'bummer' in the worst case. The startup routine is smart enough to check the policy tools and will cleanly boot even if SuperSu's tools aren't around.
Long story short, the kernel should work fine, you'll just miss out on certain things that try to run now and then to 'tune' the system.
Click to expand...
Click to collapse
That sounds like a pretty solid explanation for what happened when i tried running stock with skyhigh kernel and magisk.
Huge hit to battery life, and i still failed safetynet. Probably because the system showed i was using a custom kernel? I haven't been able to figure out a good way to mask that...
Anyways, good luck with implementing magisk like you said you would! I'm sure it won't be easy! You better have paypal links littered in the release post, you'll deserve it

What is the difference between Magisk and SuperSU?

JoeFCaputo113 said:
What is the difference between Magisk and SuperSU?
Click to expand...
Click to collapse
So I'm not super technical so i hope someone corrects me if i misrepresent this...
Magisk itself is basically a framework (think like xposed) except it functions from OUTSIDE of the system partition. Its only compatible with MagiskSU (a modified version of phh's superuser), magisksu is also not installed on the system partition...
Through magisk manager you can enable root, which as i understand, puts MagiskSU in the system partition in a sort of ghosted way, so its not really there? (As you can see I'm fuzzy on this part) And a step further, even with root still enabled, magisk can hide magisk and magiskSu's presence entirely from chosen apps (it automatically hides from play services so you pass safetynet)
So plain and simple, it theoretically works the same as supersu with the added benefit of being able to fully and effectively hide root...
There's still a lot of work to be done to reach it's full potential, especially in regards to compatibility with vendors and apps, but the dev believes magisk can do a lot eventually... including genuine multi-rom support.

https://www.xda-developers.com/magi...es-samsung-bugs-adds-core-only-mode-and-more/
Good news! Magisk update specifically for samsung devices! I can't wait to try this out!

Magisk on Nexus 5x

Is anyone using magisk and have Android pay working with root on the 5x ? I've been looking for a thread and can't find how to do it.
Unlock bootloader
Flash stock image
Flash TWRP
Reboot
Download magisk Manager and zip
Reboot ?
Will root apps work now with Android pay?

mikeprius said:
Is anyone using magisk and have Android pay working with root on the 5x ? I've been looking for a thread and can't find how to do it.
Unlock bootloader
Flash stock image
Flash TWRP
Reboot
Download magisk Manager and zip
Reboot ?
Will root apps work now with Android pay?
Click to expand...
Click to collapse
Make sure Magisk hide is on in magisk manager and that it passes the safety net check.

Keithn said:
Make sure Magisk hide is on in magisk manager and that it passes the safety net check.
Click to expand...
Click to collapse
Do I need to flash SU or just magisk

Got it working. Shows Superuser PHH's not the SU by chainfire. Some apps are not working as well with superuser vs SU, but at least everything seems to be working. Every now and then Magisk Manager bug and it shows loss of root. I'll try Android pay sometime today if I can

Could you make a quick guide on how you got magisk installed correctly?
I had some trouble when i tried it after updating to 7.1.2 yesterday and ended up flashing supersu instead. thx
mikeprius said:
Got it working. Shows Superuser PHH's not the SU by chainfire. Some apps are not working as well with superuser vs SU, but at least everything seems to be working. Every now and then Magisk Manager bug and it shows loss of root. I'll try Android pay sometime today if I can
Click to expand...
Click to collapse

mikeprius said:
Do I need to flash SU or just magisk
Click to expand...
Click to collapse
Magisk zip include SU binary (MagiskSU)
---------- Post added at 02:12 PM ---------- Previous post was at 02:09 PM ----------
robotzki said:
Could you make a quick guide on how you got magisk installed correctly?
I had some trouble when i tried it after updating to 7.1.2 yesterday and ended up flashing supersu instead. thx
Click to expand...
Click to collapse
If you have custom kernel, flash the stock one or that came with the Rom from recovery. Then flash Magisk 12 zip file from Magisk Thread and flash it via recovery. Then reboot and download Magisk manager ....

Is there any reason why Magisk wouldn't work with a custom jkernel? I've installed Magisk on top of pure nexus ROM with ElementalX kernel without issues before.

I'm running SAOSP with Magisk and Franco Kernel and I have root and Android Pay works. That's all I flashed. It had a hard time passing Safety Net when SuperSU was installed. So just flash Magisk without SuperSU. And I guess Android Pay can detect if you have an unlocked bootloader so Franco Kernel is used because it hides that.

I tried Android Pay twice. First time didn't go through, said on the vending machine failed. Second time worked. I checked Android Pay and see 2 charges, does the one that didn't go through just drop off eventually ? Also both charges are much higher than what the actual price was, but I assume this is just a temp charge.
I have elemental X kernel. Works fine. I decided not to mess with SU. My other apps work, plus I've tried asking Chainfire before questions about his apps he's made and he never responded. Not cool, I did buy his apps too, not just freebies.

mikeprius said:
I tried Android Pay twice. First time didn't go through, said on the vending machine failed. Second time worked. I checked Android Pay and see 2 charges, does the one that didn't go through just drop off eventually ? Also both charges are much higher than what the actual price was, but I assume this is just a temp charge.
I have elemental X kernel. Works fine. I decided not to mess with SU. My other apps work, plus I've tried asking Chainfire before questions about his apps he's made and he never responded. Not cool, I did buy his apps too, not just freebies.
Click to expand...
Click to collapse
All of my Android Pay charges initially show up as a $1.00 pending charge. After a while, they post as transactions for the full value of the purchase.

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.

For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.

Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:

neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?

Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.

That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.

Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.

neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.

Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.

I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.

Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)

Root & Xposed on WW_17.1810.1910.73 & Update WW_17.1810.1911.110

Hello i found a little way for have root & and working xposed with no bug on last firmware WW_17.1810.1910.73 & WW_17.1810.1911.110
Stock Recovery
You need adb drviers and unlocked ZenFone 6 on WW_17.1810.1910.73 or WW_17.1810.1911.110
First install last Magisk Manager
Open setting of Magisk and add custom update channel https://github.com/solohsu/magisk_files#custom-update-channel
Download ZenFone6RootXposed-10.73.img or ZenFone6RootXposed-11.110 (i have add stock boot11.110.img, we will need it for next update)
http://www.mediafire.com/folder/skzceszqu8d3j/AsusZenFone6
Now reboot device to bootloader
Code:
adb reboot bootloader
And boot with ZenFone6RootXposed-10.73.img or ZenFone6RootXposed-11.110 (not flash it, your device have a chance to bootloop)
Code:
fastboot boot ZenFone6RootXposed-10.73.img
Code:
fastboot boot ZenFone6RootXposed-11.110.img
The devices reboot automaticly
Go to Magisk and install Magisk, choose direct install
Reboot and Enjoy root
if you want Xposed flash it with magisk :
Riru Core
I use YAHFA
Android 10 ElderDrivers Xposed
And the manager
Xposed Installer​

Good morning
I have tried several times root for Android 10
The Magisk part works smoothly, but the Xposed part never works, producing a bootloop
I have extracted the boot and applied magisk, loaded the Riru Core module, but when loading ElderDrivers, the phone stays in bootloop
Do you know what the reason may be?

Works splendid, great guide!
Tried to use Sandhook first, but ended up with YAHFA instead due some xposed problems (xposed not detected).
Had an old version of Android 9, so i first upgraded it to "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1" (only supported upgrade path - 9 to 10), then to "UL-ASUS_I01WD-ASUS-17.1810.1910.73-1.1.1-user" (your specified .73)
- Later patching with your img
Thanks

it is impossible
Starting with .73 stock
at the moment I install Riru Yahfa, following the manual, it does not start again, unless install the official boot
the device stays on the Zenfone boot screen without doing anything else
I have tried the version supplied by Magisk, I don't know if you have tried another version

Why will we need the stock boot for the next update? We can't make menully update after root? I just want to make root not install xposed.
Sent from my ASUS_I01WD using Tapatalk

thanks a lot, this a really easy way to get root, but i have a little issue, i had my phone with NO pin code or fingerprint before using this method, and now if i want to ad a pin, password or gesture it simply does not get saved, every time i do the procedure to set the pin it does like if i did nothing, anyone has this issue, or know how to fix it, is there a problem if i hard reset?
any help will be good

In the latest build .110 ctsprofile is false while basicintegrity is true. Is it due to the root or the rom has not been signed by google?

Rom1995 said:
In the latest build .110 ctsprofile is false while basicintegrity is true. Is it due to the root or the rom has not been signed by google?
Click to expand...
Click to collapse
https://zentalk.asus.com/en/discussion/comment/35355/#Comment_35355

baster72 said:
Why will we need the stock boot for the next update? We can't make menully update after root? I just want to make root not install xposed.
Sent from my ASUS_I01WD using Tapatalk
Click to expand...
Click to collapse
just flash ZenFone6RootXposed-10.73 or ZenFone6RootXposed-11.110 and you willl have it
hdsporty50 said:
Good morning
I have tried several times root for Android 10
The Magisk part works smoothly, but the Xposed part never works, producing a bootloop
I have extracted the boot and applied magisk, loaded the Riru Core module, but when loading ElderDrivers, the phone stays in bootloop
Do you know what the reason may be?
Click to expand...
Click to collapse
hdsporty50 said:
it is impossible
Starting with .73 stock
at the moment I install Riru Yahfa, following the manual, it does not start again, unless install the official boot
the device stays on the Zenfone boot screen without doing anything else
I have tried the version supplied by Magisk, I don't know if you have tried another version
Click to expand...
Click to collapse
Don't flash Xposed using Magisk Download, flash it manualy :
EdXposed v0.4.6.0_beta
You will always get bootloop with v0.4.5.1_beta
_______________________________________
UPDATE for 11.110
flash boot.10.73.img for update safe
And do the same with 11.110 files.
Don't forget to add custom update channel in Magisk
And use v0.4.6.0_beta for xposed

Why can't we have any YouTube guides for anything related to this phone?

vernj123 said:
Why can't we have any YouTube guides for anything related to this phone?
Click to expand...
Click to collapse
I want to do it but I don't have another device to record.

Someone try this method to install xposed? I afraid to get bootloop.
Sent from my ASUS_I01WD using Tapatalk

Hi everyone, I hope somebody can help me out to solve an issue I just got with my zenfone,
After using an advise from DaConcho for getting back screen lock after unlocking bootloader I got in another situation.
I followed the instructions from the post and everything was going fine, I boot thought adb with the provided patched boot for Q .110 and that far no issues , when I open magisk manager to download magisk from the alternative source magisk manager prompt to complete the installation downloading some necessary files, not the magisk version, just said some files, and I click yes, then it installed something and reboot, phone started fine, but when I wanted to start the process again I found out that I loose PC connectivity.
I have no connection at all, even if I manually boot in bootloader I can't connect to PC, so no adb commands,
Please can someone help

does someone has the patched boot image for new .119 firmaware, i updated and losee magisk

baster72 said:
Someone try this method to install xposed? I afraid to get bootloop.
Click to expand...
Click to collapse
Don't be afraid just flash stock boot if you get bootloop
joesa said:
does someone has the patched boot image for new .119 firmaware, i updated and losee magisk
Click to expand...
Click to collapse
I update my links you can get stock boot here Boot & RootedBoot ZenFone6

MystikMan97130 said:
Don't be afraid just flash stock boot if you get bootloop
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
Click to expand...
Click to collapse
Thanks a lot !!! You really help a lot with this method

MystikMan97130 said:
Don't be afraid just flash stock boot if you get bootloop
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
Click to expand...
Click to collapse
can you please check link, it is not working, i can see folder but can not download

Hello, direct link:
ZenFone6RootXposed

Nice, thanks a lot for this! Rooting on stock with unlocked bootloader worked for me perfectly (did not check xposed)!

est-ce que l'on perd ses données en faisant le root ?
merci!

Latest Magisk crashes

So I tried to root a Pixel 2 XL with Android 8 and 9, installed the Magisk apk 7.5.1 and when it comes to patch the boot.img, it always requires to update the manager first. I didnt choose update, but it wont let me use the old version anymore, might be a bug.
However, when I then use the latest Magisk APK, it crashes when I select "Install". Any ideas what to do?

You could basically just flash the latest magisk canary build (the beta one) with twrp and you'll have root on your device in no time.
BTW this method is tested by me on android 11, and if it works on android 11 I think it'll work on previous versions of android as well. But, just to be on the safer side make sure you backup your device beforehand.

MridulDR said:
You could basically just flash the latest magisk canary build (the beta one) with twrp and you'll have root on your device in no time.
BTW this method is tested by me on android 11, and if it works on android 11 I think it'll work on previous versions of android as well. But, just to be on the safer side make sure you backup your device beforehand.
Click to expand...
Click to collapse
Thanks for the hint. I used the zipped Magisk and flashed it with TWRP. It still crashes when hitting the "Install" button but since the phone is rooted is not really necessary. Also, installing modules is
now possible again. Only renaming Magisk (for hiding) is something I didnt find yet, but the "Magisk Hide" Option should do the job.

Venomiz said:
Thanks for the hint. I used the zipped Magisk and flashed it with TWRP. It still crashes when hitting the "Install" button but since the phone is rooted is not really necessary. Also, installing modules is
now possible again. Only renaming Magisk (for hiding) is something I didnt find yet, but the "Magisk Hide" Option should do the job.
Click to expand...
Click to collapse
Which version of magisk are you using?
If you are on normal magisk manager(not canary), I'd suggest flashing the canary build(v21.0) and see if you are able to rename magisk manager.