Database Info

Anyone running stock rooted 9.0.3 upgrade to Magisk 18.1 yet?

I was thinking of trying to fix a few minor things like won't boot with charger plugged in and Google Pay getting screwed up every once in a while...but figured I would ask first.
To be safe I was going to nandroid backup, TWRP Magisk Uninstaller, TWRP Magisk 18.1 installer and try it out later on....it seems people have reported bootloops on other phones upgrading from the Magisk Manager app...
MW

I am in 9.0.3 but under xxx no limits magisk rom.
It works well

0xPraeT0Rian said:
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
Click to expand...
Click to collapse
Using the new magisk 18.1 or 18?

You asked about 18.1.
I am on 9.0.3 with 18.1 magisk and the new magisk manager

Hi to all,
I am on OB12, and I'm no longer able to root since I tried to upgrade from Magisk 18 to 18.1
I already tried the 2 last versions of Magisk uninstaller and also to reflash OB12, but still impossible to root.
What is very strange is that if I flash Smurfkernel it says that I'm rooted, but after booting, no Magisk APK and impossible to install it !
Any suggestions?
Thank in advance for any help.

I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.

No problems here.

b.huss2 said:
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
Click to expand...
Click to collapse
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)

OP here -- I updated and am having no issues, but I did it all through TWRP by uninstalling Magisk 18.0 first and then re-installing 18.1 before rebooting. I had already updated Magisk Manager from the app.
Only thing I noticed was I had to reset up all my settings (Magisk hide for Direct TV Now, and re SU authorize all root apps). First reboot everything was slow with root apps waiting for SU access before the request came through, but then everything was fine once it was granted.

michelD said:
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
Click to expand...
Click to collapse
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)

b.huss2 said:
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
Click to expand...
Click to collapse
Yes I tried this too, but unsuccessfully !
And I'm even not sure that a full wipe will help, because it concerns another partition.

Accidentally Soft Bricked OP6; Recovered But Cannot Re-Install Magisk

Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY

If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815

tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Thank you so much for your suggestion, and reply. Magisk and TWRP were up to date (the latest releases); Magisk v20.1, and TWRP 3.3.1.2 ("Enchilada"). My device is a OnePlus 6 running Android 9, last updated August 1st of this year, "ONEPLUS A6003_22_190911"
I will try your suggestion and respond as soon as possible. If there is anything else you need to know, ask. I am new to the concept of forums so I've been kinda flopping around like a fish out of water. :laugh:

Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Hello, just wanted to update you. I am happy to report your suggestion worked. Sadly I still lost my data, but that's alright; all the important bits were already backed up. Just lost the home screen layout and some application settings. All the same, I am now successfully running my rooted device and couldn't be happier! Thanks! :laugh::good:

Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
Hey, I'm in a similar situation you were in and I'm stuck in a bootloop after I flashed/installed busybox from magisk repo, I wanted viper 4android as well and while installing viper it said that I'd need busybox. Soon after I install busy box from magisk I'm in this bootloop, i have access to twrp luckily and i tried deleting this busybox and viper 4android module from twrp file manager but still I'm in a boot loop, can you guide me on how you managed to get out of this bootloop?? Thanks

How to root - the most easy, most reliable way?

Now that I have (almost accidentally) upgraded my phone to Android 11 (stock), I would like to root my POCO F2.
I am currently not interested in any custom-ROM, but I need root for proper backup and a couple of other functions.
But what is the best way? I don't want to loose Fingerprint, and Banking-applications?
I understand after unlocking the BL, I can install MAGISK by flashing a patched Boot-image.
People in this forum recommend to flash TWRP, and then install MAGISK as the better way.
So, if there is an OTA-upgrade available my TWRP and MAGISK will be gone - but what about data?
With a previous device (Xiaomi A1) instead of flashing TWRP I was just booting into TWRP to install MAGISK, is this possible with our POCO F2?
After rooting, what will NOT be working?
Who can answer?
Thanks!

Anybody?
Let me rephrase:
Installing MAGISK by flashing a patched Boot-image seems easier and a smaller change to the overall system, compared to flash TWRP and the patched Boot-image.
The method recommended by MAGISK is also flashing the patched Boot-image. Nevertheless a lot of people recommend to go via TWRP. Why? What is the advantage?

Why do you want to root your device?
just downgrade .

I like Titanium Backup, all apps working with Android Auto (eg Screen2Auto), Tasker ..
So are you saying rooting and still have Fingerprint and Banking apps working under Android 11 is not possible?

Tiemichael said:
I like Titanium Backup, all apps working with Android Auto (eg Screen2Auto), Tasker ..
So are you saying rooting and still have Fingerprint and Banking apps working under Android 11 is not possible?
Click to expand...
Click to collapse
Nothing said of all this, maybe here you will find the answers to your questions.
https://forum.xda-developers.com/t/...droid-11-and-magisk-on-xiaomi-eu-rom.4170031/

Lost root after installing TWRP. Can anyone share patched boot image for 11.0.5.1.GM21AA?

As above, I would appreciate it if someone could share a copy of a Magisk patched 11.0.5.1.GM21AA boot image. Thanks!
P.S. - Do not update to Magisk 24 or 24.1 unless you want to have to mess around with your phone!

Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.

Dan3ll1 said:
Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.
Click to expand...
Click to collapse
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?

benengyj said:
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?
Click to expand...
Click to collapse
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.

Frodolo said:
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.
Click to expand...
Click to collapse
Once you've upgraded to 24 or 24.1 it seems that the only way to go back to an older version is to use the built-in uninstall button in the Magisk app. Just trying to flash a new boot image over it doesn't seem to stick.
In my case, I had to:
Uninstall any version of the Magisk app
Install 24.1
Extract the boot image using Payload Dumper
Creating a 24.1 patched boot image to re-root my device
Uninstalling 24.1 using the uninstall button in the Magisk app
Install Canary Magisk (23 should work too)
Create a new 23 patched boot image and root using it
Still have not gotten around to fixing my MagiskHide and SafetyNet failing though, I think that requires some cache clearing and other steps to resolve. Also somehow managed to get rid of my TWRP accidentally along the way too, so I'll have to reinstall that again.

Thanks a lot!

benengyj said:
Uninstalling 24.1 using the uninstall button in the Magisk app
Click to expand...
Click to collapse
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?

¿GotJazz? said:
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?
Click to expand...
Click to collapse
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol

benengyj said:
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol
Click to expand...
Click to collapse
Yep, that's weird. I was having (a ton of) trouble getting my phone rooted at the time, so that's why I didn't see it.

Magisk 24.1 no Zygisk option available

I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.

Your screenshot shows that Magisk is not installed.
You only installed the app. Try install in the upper right corner and choose for direct install without patching.

Prof_Shekhar said:
I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Click to expand...
Click to collapse

xabu said:
Your screenshot shows that Magisk is not installed.
You only installed the app. Try install in the upper right corner and choose for direct install without patching.
Click to expand...
Click to collapse
Thank you xabu for your reply.
I had tried to install it numerous times using the direct install method as suggested by you but it gives me a "installation failed" message (Screenshot attached).
Also, presuming that my previously installed magisk v 23.0 may not have been uninstalled during the process of auto update to magisk version 24.1 (only 24.1 app installed but not magisk itself not upgraded due to unknown reasons), I reinstalled the app v 23 and uninstalled magisk completely. Frustrated, I installed the stock firmware again, reinstalled TWRP and flashed magisk 24.1. However, the result appears to be same. No magisk installation.
It appears to me that magisk v 23 is not yet completely uninstalled as if I delete this 24.1 app, reinstall app for 23.1 most of the functionality comes back though not all. I still can't hide magisk but it passes safety check.

Also I have tried to uninstall any previous version of magisk using renamed magisk app as uninstall.zip via TWRP. Also I get following message:
"cannot find vbmeta partition, patch vbmeta in boot image.
Removing magisk files."
Now when I go to Magisk app, I get only option to "select and patch a file."
Appreciate if anyone can suggest me a way forward.

Also, I get the vbmeta partition not found error while trying to install Magisk via TWRP (screenshot attached)

I have selected and installed Magisk patched boot image file using ODIN3. Removed TWRP. Tried to install using Magisk app 24.1 but get installation failed due to unable to check signature (screenshot attached).
Request some guidance.

Start here ....
Magisk - The Age of Zygisk.​Your questions are very interesting but too difficult for me to answer. Magisk 24.1 normally replaces the 23 almost automatically .... By uninstalling the module the situation becomes completely different and you should probably start from scratch. In my link "start here" you'll find the place where real specialists are.
Wishing you all the best !

Appreciate your advice.
However, I have reinstalled the stock firmware 3 times since this morning just as to ensure that I start from a clean slate. Also used Adb commands to uninstall any remanants of the previous Magisk manager if at all left there.
However, still stuck with the puzzling question as to where am I going wrong.

Prof_Shekhar said:
Also I have tried to uninstall any previous version of magisk using renamed magisk app as uninstall.zip via TWRP. Also I get following message:
"cannot find vbmeta partition, patch vbmeta in boot image.
Removing magisk files."
Now when I go to Magisk app, I get only option to "select and patch a file."
Appreciate if anyone can suggest me a way forward.
Click to expand...
Click to collapse
Exact same issue for me!

Also for me....same tests that @Prof_Shekhar have done

Prof_Shekhar said:
I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Click to expand...
Click to collapse
The same thing happened to me so i tried and tried and tried for like 4-5 hours after reinstalling multiple times the firmware so i gave up and came to the conclusion that its not supported yet for a few phones like the Note8 (SM-N950F ~ my version of the phone).So the only thing you can do rn is to stick to version 23.0 then go to settings and change the channel to custom channel and paste this link "https://raw.githubusercontent.com/t...304e59f631280cc26ccc6d40a7cf04f7f37/beta.json" in there so the magisk version doesn't update itself or you update it by accident

Beast-chan said:
The same thing happened to me so i tried and tried and tried for like 4-5 hours after reinstalling multiple times the firmware so i gave up and came to the conclusion that its not supported yet for a few phones like the Note8 (SM-N950F ~ my version of the phone).So the only thing you can do rn is to stick to version 23.0 then go to settings and change the channel to custom channel and paste this link "https://raw.githubusercontent.com/t...304e59f631280cc26ccc6d40a7cf04f7f37/beta.json" in there so the magisk version doesn't update itself or you update it by accident
Click to expand...
Click to collapse
@Beast-chan
Hope you were able to install Magisk 24.1 Canary version without any further issues.

Prof_Shekhar said:
@Beast-chan
Hope you were able to install Magisk 24.1 Canary version without any further issues.
Click to expand...
Click to collapse
tbh i didnt try the Canary version...does it work or why do you ask?

Beast-chan said:
tbh i didnt try the Canary version...does it work or why do you ask?
Click to expand...
Click to collapse
@Beast-chan
Definitely. I have installed Magisk 24.1 Canary using patched AP file from stock firmware, and then reinstalled the Magisk 24.1 Canary version. It has been working without any issues since then.
Don't forget to install universal safetyNet Fix.
Let me know if you run into any issues.

Prof_Shekhar said:
@Beast-chan
Definitely. I have installed Magisk 24.1 Canary using patched AP file from stock firmware, and then reinstalled the Magisk 24.1 Canary version. It has been working without any issues since then.
Don't forget to install universal safetyNet Fix.
Let me know if you run into any issues.
Click to expand...
Click to collapse
ok ty i will try it