Database Info

Trouble Installing Magisk (Stock S6 with TWRP)

Hi,
I was recently having some trouble with Magisk in that I flashed it however didn't gain root so I uninstalled it and thought I would try with SuperSU however upon flashing SuperSU then trying to flash Magisk there was an error with Magisk saying that there isn't enough space in the boot partition and to delete some ramdisks and right now I am at a complete loss at what to do. (SuperSU - V2.79 | Magisk - V11.6)
Any help at all is appreciated, thankyou

dasbiz said:
Hi,
I was recently having some trouble with Magisk in that I flashed it however didn't gain root so I uninstalled it and thought I would try with SuperSU however upon flashing SuperSU then trying to flash Magisk there was an error with Magisk saying that there isn't enough space in the boot partition and to delete some ramdisks and right now I am at a complete loss at what to do. (SuperSU - V2.79 | Magisk - V11.6)
Any help at all is appreciated, thankyou
Click to expand...
Click to collapse
Hi,
Try flashing the magisk uninstaller found here, then reflash magisk V11.1 found here
Magisk 11.6 is bugged.
- renolz

renolz said:
Hi,
Try flashing the magisk uninstaller found here, then reflash magisk V11.1 found here
Magisk 11.6 is bugged.
- renolz
Click to expand...
Click to collapse
Thanks! This fixed it and now I have Magisk working however was wondering if you know whether Viper4Android's Magisk Module would work with the S6 or there are more steps to follow if installing to a Samsung device?

dasbiz said:
Thanks! This fixed it and now I have Magisk working however was wondering if you know whether Viper4Android's Magisk Module would work with the S6 or there are more steps to follow if installing to a Samsung device?
Click to expand...
Click to collapse
Hi,
That depends on your kernel and what android version you are on.
Take a look at this guide, read the last pages for a little gudie on how to do it
Official V4A page can be found here, under post #2 you can read where it says "For Samsung devices"
Hope this helps.
- Renolz

Soft reboot after installing magisk modules. Phone is OOS latest stable & encrypted

Soft reboot after installing magisk modules. Phone is OOS latest stable & encrypted
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?

bramhc said:
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
Click to expand...
Click to collapse
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.

yldlj said:
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
Click to expand...
Click to collapse
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo

bramhc said:
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
Click to expand...
Click to collapse
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2

yldlj said:
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
Click to expand...
Click to collapse
Okay. Will try now. Thanks
EDIT: Confirmed. Viper4android works. Maybe it's James DSP that hasn't been updated to work with Pie. Cheers.

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.

EdXposed OOS 10 Bootloop

Installing v0.4.5.5 or v0.4.6.0 both gets me into bootloop, tried the modifed Magisk from the EdXposed peope as the newest offical version.
OOS 10.0.1 GM1913

Hirs_E_Fruit said:
Installing v0.4.5.5 or v0.4.6.0 both gets me into bootloop, tried the modifed Magisk from the EdXposed peope as the newest offical version.
OOS 10.0.1 GM1913
Click to expand...
Click to collapse
Strange.
This is the 4.6 i used.
https://github.com/ElderDrivers/EdXposed/releases/tag/v0.4.6.0
Be sure to install riru core module also.

hallo dare said:
Strange.
This is the 4.6 i used.
https://github.com/ElderDrivers/EdXposed/releases/tag/v0.4.6.0
Be sure to install riru core module also.
Click to expand...
Click to collapse
I install Magisk in TWRP and reboot,
install Riru Core and reboot,
then install EdExposed.
I did try so many different versions of Magisk and Xposed....
Sometimes i got it to work but but on some reboot for other Magisk modules it started bootloop
OR it starts I type PIN und SIMPIN then reboot and bootloop.
What OOS 10 Version, Magisk do you use?
Some install routine you follow?

I'm using magisk v20. I only use gravitybox in edxposed.
Are you getting the bootloop before you even install any modules in edxposed?

hallo dare said:
I'm using magisk v20. I only use gravitybox in edxposed.
Are you getting the bootloop before you even install any modules in edxposed?
Click to expand...
Click to collapse
The v20 provided by the EdExposed guys?
Well I bootloop after the reboot from installing EdExposed Module in Magisk

Hirs_E_Fruit said:
The v20 provided by the EdExposed guys?
Well I bootloop after the reboot from installing EdExposed Module in Magisk
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

hallo dare said:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Well I used it with the official Magisk until a few days ago where it bootlooped after a reboot when I installed a Xposed modul since then I wasnt able to get it to work again.
Yes I did remove all Xposed and Magisk Modules to try to get only the framework to work.

So it's a module causing the problem and not edxposed itself.

hallo dare said:
So it's a module causing the problem and not edxposed itself.
Click to expand...
Click to collapse
No because I cant even intall only the frame work without bootlooping.
The problem itself started with a new module but now with a "clean" OOS 10.0.1 GM1913 BA I cant get Magisk EdXposed Modul to work.

Hirs_E_Fruit said:
No because I cant even intall only the frame work without bootlooping.
The problem itself started with a new module but now with a "clean" OOS 10.0.1 GM1913 BA I cant get Magisk EdXposed Modul to work.
Click to expand...
Click to collapse
Use taichi instead

hallo dare said:
Use taichi instead
Click to expand...
Click to collapse
Typical Android, I did a flash of OOS Full System ZIP file in TWRP and then RIRU Core in Magisk, reboot and EdXposed and suddenly it works with Magisk 20.2....
But now MinMinGuard says Xposed is not enabled while the Manager says it is
Edit: MinMinGuard only excepts v0.4.5.5 ...
Edit 2: Seems the Xposed Module SudoHide is the problem because after I install this i have the bootloop

hallo dare said:
I'm using magisk v20. I only use gravitybox in edxposed.
Are you getting the bootloop before you even install any modules in edxposed?
Click to expand...
Click to collapse
I can't seem to get gravitybox to play nice. Edxposed is working as it should, but gravitybox throws a error. (System framework not responding)
What's your setup?

Chance Ill said:
I can't seem to get gravitybox to play nice. Edxposed is working as it should, but gravitybox throws a error. (System framework not responding)
What's your setup?
Click to expand...
Click to collapse
Try disabling Resource hooking support in edxposed installer settings. Or use taichi instead to run gravitybox

hallo dare said:
Try disabling Resource hooking support in edxposed installer settings. Or use taichi instead to run gravitybox
Click to expand...
Click to collapse
No look disabling resource hooking. I'm not too familiar with Tai Chi. A quick search suggest its another framework.
Any information you can give would definitely be helpful

Chance Ill said:
No look disabling resource hooking. I'm not too familiar with Tai Chi. A quick search suggest its another framework.
Any information you can give would definitely be helpful
Click to expand...
Click to collapse
Did you try the 0.4.5.5 Version?

Hirs_E_Fruit said:
Did you try the 0.4.5.5 Version?
Click to expand...
Click to collapse
Unless there's a different version than I'm using, yes. At the moment, I have riru core 19.5 and EdXposed-YAHFA-v0.4.5.5_beta.

Chance Ill said:
Unless there's a different version than I'm using, yes. At the moment, I have riru core 19.5 and EdXposed-YAHFA-v0.4.5.5_beta.
Click to expand...
Click to collapse
You get the same error with v0.4.5.5/v0.4.6.0 as shown in the picture?

Hirs_E_Fruit said:
You get the same error with v0.4.5.5/v0.4.6.0 as shown in the picture?
Click to expand...
Click to collapse
It's odd. When I flash 0.4.5.5, the device boots without issue but is unstable ( apps won't open or lags if they do, websites won't load, etc). No such issues with 0.4.6.0 except gravitybox itself.
My complete setup is stock rooted international T-Mobile OnePlus, elemental kernel, several magisk modules and of course, edxposed.

Hirs_E_Fruit said:
You get the same error with v0.4.5.5/v0.4.6.0 as shown in the picture?
Click to expand...
Click to collapse
Just a screenshot of the edxposed modules I have installed

Chance Ill said:
It's odd. When I flash 0.4.5.5, the device boots without issue but is unstable ( apps won't open or lags if they do, websites won't load, etc). No such issues with 0.4.6.0 except gravitybox itself.
My complete setup is stock rooted international T-Mobile OnePlus, elemental kernel, several magisk modules and of course, edxposed.
Click to expand...
Click to collapse
v0.4.6.0 dont work for some apps at Android 10 for example MinMinGuard
Do you use Sandhook or YAHFA?
I had also a lot of trouble and flashing full OTA did help.

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