Since I upgraded from Magisk v9 to v10, every time I reboot my phone, I get a notification from phh's Superuser that says "Install Superuser" "The su binary is out of date." When I tap the notification, it just opens the Superuser app and doesn't ask me to update anything. Root still works normally, though. This is happening on a Nexus 5X running stock build NMF26F with no modifications other than Magisk itself, and no modules except for Superuser. The same thing happens whether Magisk Hide is on or off. I tried completely uninstalling and reinstalling Magisk, which didn't fix it either. What could be causing it, and how can I fix it?
EDIT: Solved: Magisk 10.2 includes a new version of the su binary that fixes this issue.
josephcsible said:
Since I upgraded from Magisk v9 to v10, every time I reboot my phone, I get a notification from phh's Superuser that says "Install Superuser" "The su binary is out of date." When I tap the notification, it just opens the Superuser app and doesn't ask me to update anything. Root still works normally, though. This is happening on a Nexus 5X running stock build NMF26F with no modifications other than Magisk itself, and no modules except for Superuser. The same thing happens whether Magisk Hide is on or off. I tried completely uninstalling and reinstalling Magisk, which didn't fix it either. What could be causing it, and how can I fix it?
Click to expand...
Click to collapse
This is because the su binary included in Magisk is a modified one & the official phh root manager detect that it is not equal to the lastest official su binary... just ignore that notification.
This happens on Magisk 9 as well I wish there was a way to turn it off but it's not really a big deal I guess.
Deic said:
This is because the su binary included in Magisk is a modified one & the official phh root manager detect that it is not equal to the lastest official su binary... just ignore that notification.
Click to expand...
Click to collapse
Yep, I did some poking around and confirmed that. (It's also entirely because of the new Superuser module, not the new Magisk). I guess as a workaround for now, I can block the Superuser app from sending notifications. The good news is this, though:
topjohnwu said:
Right now you still have to install the phh Superuser application, however the root management should move to Magisk Manager soon, please stay tuned.
Click to expand...
Click to collapse
This will take care of it. I'm not sure why he didn't wait to change the su version code until that was done, though, as that would have avoided this problem.
EDIT: And I also now see this listed as a known issue in the main Magisk post.
I am having the same issue, except none of my apps can see root.
kiefferbp said:
I am having the same issue, except none of my apps can see root.
Click to expand...
Click to collapse
It's not at all the same issue then. You should post about it in another thread.
josephcsible said:
It's not at all the same issue then. You should post about it in another thread.
Click to expand...
Click to collapse
Sorry if I sounded like one of those noobs that posts unrelated things in a random thread. I originally thought it was somewhat related since Magisk Manager said root was properly installed, but no other app recognized it.
I managed to fix that by un-installing and re-installing the phh superuser module. I am now just in the same boat as you, and I'll patiently wait for a fix.
kiefferbp said:
Sorry if I sounded like one of those noobs that posts unrelated things in a random thread. I originally thought it was somewhat related since Magisk Manager said root was properly installed, but no other app recognized it.
I managed to fix that by un-installing and re-installing the phh superuser module. I am now just in the same boat as you, and I'll patiently wait for a fix.
Click to expand...
Click to collapse
Can confirm. On Nexus 5x 7.1.1 with no other modifications, but lost root after I updated to v10. However, after an uninstall and reinstall I was back in business. One note though, the installation through magisk manager failed, and I had to manually flash the zip in recovery.
Fixed with Magisk 10.2.
josephcsible said:
Fixed with Magisk 10.2.
Click to expand...
Click to collapse
Magisk 10.2 here .. not fixed
warriorvibhu said:
Magisk 10.2 here .. not fixed
Click to expand...
Click to collapse
Make sure it automatically updated you to the topjohnwu r2 version of Superuser. If it didn't, do it manually from https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921. If that doesn't fix the problem, then your problem isn't this problem.
josephcsible said:
Make sure it automatically updated you to the topjohnwu r2 version of Superuser. If it didn't, do it manually from https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921. If that doesn't fix the problem, then your problem isn't this problem.
Click to expand...
Click to collapse
Yup all that done .. still have the same notification ..
I have the same problem.
1) i have tryed to flash magisk 10.2 by recovery but after flashing the s7 edge goes in bootloop (tyed with SuperSu disabled and without binary installed). So i had to flash the unistaller.
2) I even tryed enabled the chainfire SuperSu just for trying to flash the magisk+phh by magisk manager. Out of date. I think it cames cause magisk try to load the chainfire supersu binary and not the SU binary magisk has.
Help me please.
P.s. i have tryed with a clean boot image charged.
I had the same issue, and also noticed that su wasn't working in ADB. It looked like some permissions were wrong on the /magisk/phh directory. I solved it by uninstalling the phh superuser module from in Magisk Manager, then reflashing phh-superuser-topjohnwu-r2.zip in recovery.
Noxious Ninja said:
I had the same issue, and also noticed that su wasn't working in ADB. It looked like some permissions were wrong on the /magisk/phh directory. I solved it by uninstalling the phh superuser module from in Magisk Manager, then reflashing phh-superuser-topjohnwu-r2.zip in recovery.
Click to expand...
Click to collapse
Tryed, no well news!
Did y have SuperSu binary installed during flashing?
Mr.Fearless said:
Tryed, no well news!
Did y have SuperSu binary installed during flashing?
Click to expand...
Click to collapse
No, I haven't had SuperSU on here at all.
Noxious Ninja said:
No, I haven't had SuperSU on here at all.
Click to expand...
Click to collapse
I've just tryed deleting all the root binary files. Nothing, After flashing magisk 10.2 by recovery the phone goes to bootloop.
Thread closed at OP's request.
Related
HTC One M9
Venom Rom - ViperOne
Phh's SuperUser installed
Magisk 11.1 installed
Android N
Flashed a new rom (Viper) and it gave me the option to install PHH's SuperUser and Magisk, so I did. Once setting up the device I updated Magisk to 11.1 and installed the PHH's SuperUser (Magisk version) off of the official RT thread here on XDA.
Magisk Manager says I have Magisk 11.1 installed correctly and it is properly rooted, but my phone does not pass safety net, instead it says "CTS Profile Mismatch." After looking through the settings I saw the option for Magisk Hide so switched it off and back on and it says...
"You are not rooted with MagiskSU, using Magisk Hide might not be enough! It's not officially supported, and you would need additional tools (e.g Suhide) to pass Safety Net."
Can someone please help me with what to do?
Thank you,
Ollie Bednal.
obednal97 said:
HTC One M9
Venom Rom - ViperOne
Phh's SuperUser installed
Magisk 11.1 installed
Android N
Flashed a new rom (Viper) and it gave me the option to install PHH's SuperUser and Magisk, so I did. Once setting up the device I updated Magisk to 11.1 and installed the PHH's SuperUser (Magisk version) off of the official RT thread here on XDA.
Magisk Manager says I have Magisk 11.1 installed correctly and it is properly rooted, but my phone does not pass safety net, instead it says "CTS Profile Mismatch." After looking through the settings I saw the option for Magisk Hide so switched it off and back on and it says...
"You are not rooted with MagiskSU, using Magisk Hide might not be enough! It's not officially supported, and you would need additional tools (e.g Suhide) to pass Safety Net."
Can someone please help me with what to do?
Thank you,
Ollie Bednal.
Click to expand...
Click to collapse
Remove PHH Superuser completely - including apk - and re-flash Magisk.
osmOsis's UnSu script does a good job of removing all traces of root.
jhedfors said:
Remove PHH Superuser completely - including apk - and re-flash Magisk.
osmOsis's UnSu script does a good job of removing all traces of root.
Click to expand...
Click to collapse
Thank you for your quick response!
Where and how do I find and install the original boot.img to remove phh's superuser?
obednal97 said:
Thank you for your quick response!
Where and how do I find and install the original boot.img to remove phh's superuser?
Click to expand...
Click to collapse
The original boot image is what is in the ROM zip. However, as you mentioned that root is preinstalled, you should flash osmOsis's UnSu zip to get rid of root before reflashing Magisk.
jhedfors said:
The original boot image is what is in the ROM zip. However, as you mentioned that root is preinstalled, you should flash osmOsis's UnSu zip to get rid of root before reflashing Magisk.
Click to expand...
Click to collapse
Thank you very much for your help, just doing it now ?
jhedfors said:
The original boot image is what is in the ROM zip. However, as you mentioned that root is preinstalled, you should flash osmOsis's UnSu zip to get rid of root before reflashing Magisk.
Click to expand...
Click to collapse
Just done it all! It works beautifully!
I messed up the first time cause I couldn't remove Superuser app completely but I got round that and did it all again and its all green lights
Installed Magisk ☑
Rooted ☑
Safety net passed ☑
Thank you very much!
obednal97 said:
Just done it all! It works beautifully!
I messed up the first time cause I couldn't remove Superuser app completely but I got round that and did it all again and its all green lights
Installed Magisk ☑
Rooted ☑
Safety net passed ☑
Thank you very much!
Click to expand...
Click to collapse
Awesome!
cts profile mismatch
i have a xiaomi device which has epic rom based on android 6.0 with magisksu preinstalled by i cant bypass safetynet check either. what should i do?? i did a reinstall of magisk but it didn't helped.
aldo-000 said:
i have a xiaomi device which has epic rom based on android 6.0 with magisksu preinstalled by i cant bypass safetynet check either. what should i do?? i did a reinstall of magisk but it didn't helped.
Click to expand...
Click to collapse
If the ROM has Magisk pre-installed, you may want to check in the ROM thread. Otherwise try everything I suggested in this thread.
jhedfors said:
If the ROM has Magisk pre-installed, you may want to check in the ROM thread. Otherwise try everything I suggested in this thread.
Click to expand...
Click to collapse
uninstalling magisk, still can't bypass safetynet test but i can play pokemon go., wired.... i will ask about the rom. do you another way making pg playable on rooted device??
aldo-000 said:
uninstalling magisk, still can't bypass safetynet test but i can play pokemon go., wired.... i will ask about the rom. do you another way making pg playable on rooted device??
Click to expand...
Click to collapse
Did you do what I suggested? If so, can you say what you did?
aldo-000 said:
i have a xiaomi device which has epic rom based on android 6.0 with magisksu preinstalled by i cant bypass safetynet check either. what should i do?? i did a reinstall of magisk but it didn't helped.
Click to expand...
Click to collapse
Is it based on Developer or Stable ROM? Develop ROMs can't pass SafetyNet because they don't have the correct CTS profile. If it's based on Stable ROM, try flashing Global Stable again and Epic ROM afterwards, that might or might not help, no guarantees. You are only guaranteed to pass CTS profile match with Global Stable. But like you said, if Pokemon Go works you don't really need CTS profile.
i have moto E 3g 2 gen[OTUS] with Recusrtion remix 5.8.1 android 7
have flashed magisk but it gives error :1 error installing magisk 11.1 , while i did same with moto e [Condor] 1st gen and got success everything is working
even i clean the old su
can you help @jhedfors
Hi, I've just switched over to magisksu from supersu. I did as you suggested above... flashed unSu and the boot image and magisk. Then installed the Magisk manager from play store. It shows the device is rooted and that latest magisk is installed. However, safenet check fails.
Any suggestions on what to do?
Thanks
neptune_ said:
Hi, I've just switched over to magisksu from supersu. I did as you suggested above... flashed unSu and the boot image and magisk. Then installed the Magisk manager from play store. It shows the device is rooted and that latest magisk is installed. However, safenet check fails.
Any suggestions on what to do?
Thanks
Click to expand...
Click to collapse
Reboot with setting everything enable except disabling magisk it worked for me
Rush94 said:
Reboot with setting everything enable except disabling magisk it worked for me
Click to expand...
Click to collapse
Tried that, but SafetyNet check still fails
neptune_ said:
Tried that, but SafetyNet check still fails
Click to expand...
Click to collapse
Try enabling hide magisk enable busybox and then reboot
Rush94 said:
Reboot with setting everything enable except disabling magisk it worked for me
Click to expand...
Click to collapse
Rush94 said:
Try enabling hide magisk enable busybox and then reboot
Click to expand...
Click to collapse
Tried that too, still fails
neptune_ said:
Tried that too, still fails
Click to expand...
Click to collapse
Try some of the tips here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Try some of the tips here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Thanks. I did read through there and tried some suggestions. Nothing seems to work.
I may have to use a rom that comes packaged with magisk?
Sent from my LG G3 using XDA Labs
I noticed today that I lost root. I searched and tried everything to fix it but I couldn't. So, I wiped out my entire phone and did a clean flash of Resurrection Remix 5.8.3 for the TMobile Note 3. Magisk worked after a clean flash.
Spent hours loading every app back on and now, Magisk isn't working again?
Please help?
Android version is 7.1.2.
Did it really lose root? I've found that randomly when you open Magisk it will claim that it has no root access, but when you close it (exit the app and swipe it away from the recents menu) and reopen it it will start functioning properly again.
Neo3D said:
I noticed today that I lost root. I searched and tried everything to fix it but I couldn't. So, I wiped out my entire phone and did a clean flash of Resurrection Remix 5.8.3 for the TMobile Note 3. Magisk worked after a clean flash.
Spent hours loading every app back on and now, Magisk isn't working again?
Please help?
Android version is 7.1.2.
Click to expand...
Click to collapse
Use un su zip first to remove the pre-installed root that rr has. Don't know if RR has root inbuilt now or not. But if it comes with root uninstall it and flash magisk on top of it and you are good to go
Me too have this problem. Magisk root sometimes gone, and i need to reboot device to make it work agan.
Tested in almost N custom roms like CM14.1, AEX, Omni, ViperOS, etc
exodius48 said:
Me too have this problem. Magisk root sometimes gone, and i need to reboot device to make it work agan.
Tested in almost N custom roms like CM14.1, AEX, Omni, ViperOS, etc
Click to expand...
Click to collapse
Did u remove built in root
shantam3108 said:
Did u remove built in root
Click to expand...
Click to collapse
If you installed magisk it will remove built in root automatically. -_-
Did you turn off magisk busybox ? It would help on fix that.
In another way, some of modules you installed may have potential to make you lose root. Trying to do enable/disable module to test it.
I did some more searching and someone said just flash Magisk again. I did that and it worked! But, then I lost root again several hours later, seems so random? I flashed Magisk again and it worked again.
I can only get two green on Magisk, the third green seems to run forever, I left it on for 10+ minutes and it still showed "testing".
BTW, I didn't flash the uninstall Magisk zip before re-flashing. I tried that way and my phone got into a bootloop. Luckily, I had a TWRP backup.
Kris Chen said:
Did you turn off magisk busybox ? It would help on fix that.
In another way, some of modules you installed may have potential to make you lose root. Trying to do enable/disable module to test it.
Click to expand...
Click to collapse
Thanks! I'll try this and see if it helps!
BTW, is anyone able to install Snapchat? I tried the Hide feature in Magisk and checked Snapchat, but it still knows I'm rooted and immediately closes after opening.
Also, the Sphero BB8 app? Anyone get that working? That one also closes right after opening.
exodius48 said:
If you installed magisk it will remove built in root automatically. -_-
Click to expand...
Click to collapse
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
---------- Post added at 01:21 AM ---------- Previous post was at 01:20 AM ----------
Neo3D said:
Thanks! I'll try this and see if it helps!
Click to expand...
Click to collapse
Also keep in mind do run magisk without any modules first to check
shantam3108 said:
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
Click to expand...
Click to collapse
Then why on AEX still loose root? It has no root prebuilt
exodius48 said:
If you installed magisk it will remove built in root automatically. -_-
Click to expand...
Click to collapse
shantam3108 said:
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
Click to expand...
Click to collapse
I just want to clarify.
If systemless SuperSU is detected, Magisk will use that. If any other root is installed, the installation script will attempt to remove it and install MagiskSU instead (not sure to be successful and might lead to issues). If no root is installed, MagiskSU will be used. To avoid issues, the unSU zip is quite useful.
From v13, Magisk will no longer be compatible with SuperSU.
Didgeridoohan said:
I just want to clarify.
If systemless SuperSU is detected, Magisk will use that. If any other root is installed, the installation script will attempt to remove it and install MagiskSU instead (not sure to be successful and might lead to issues). If no root is installed, MagiskSU will be used. To avoid issues, the unSU zip is quite useful.
From v13, Magisk will no longer be compatible with SuperSU.
Click to expand...
Click to collapse
Wow, this is very informative, thanks!
Which version of unSU.zip is the correct one to use? Is this one okay?
https://forum.xda-developers.com/showpost.php?p=63615067
Neo3D said:
Wow, this is very informative, thanks!
Which version of unSU.zip is the correct one to use? Is this one okay?
https://forum.xda-developers.com/showpost.php?p=63615067
Click to expand...
Click to collapse
That's the one to use. :good:
Neo3D said:
BTW, is anyone able to install Snapchat? I tried the Hide feature in Magisk and checked Snapchat, but it still knows I'm rooted and immediately closes after opening.
Also, the Sphero BB8 app? Anyone get that working? That one also closes right after opening.
Click to expand...
Click to collapse
It is because your device lost safety net.
You need to reflash system and gapps.
Back up data partition then wipe all then flash rom and gaps and then magisk.
After starting device first enable magisk hide.
Then restore backed up /data.
After restart enable magisk hide switches and reboot system.
Profit.
Reply it works or not.
[email protected] said:
It is because your device lost safety net.
You need to reflash system and gapps.
Back up data partition then wipe all then flash rom and gaps and then magisk.
After starting device first enable magisk hide.
Then restore backed up /data.
After restart enable magisk hide switches and reboot system.
Profit.
Reply it works or not.
Click to expand...
Click to collapse
I just flashed magisk again and safety passed!
Neo3D said:
I just flashed magisk again and safety passed!
Click to expand...
Click to collapse
Tell me how much time you have safety net pass?
[email protected] said:
Tell me how much time you have safety net pass?
Click to expand...
Click to collapse
Hi, what do you mean "how much time you have safety net pass?
Neo3D said:
Hi, what do you mean "how much time you have safety net pass?
Click to expand...
Click to collapse
This time after reinstalling magisk is it working till now?
Or root is gone after some time?
Hey XDA & Note 8'ers ,
I've finally got around to rooting my Note 8 - all is smooth and get a root confirmation through various apps.
But when I try and get SuperSU running, it keeps giving me the error 'SU Binary Occupied'.
I've flashed it with Stock, and also SuperSU through various methods,
but I keep getting the error of the SU Binary being occupied.
I've followed the instructions given by the SU App to deal with the above issue, but keep getting the same issue.
Any suggestions or advice on what I might have done wrong to keep causing this?
I'd like to get SuperSU working, but it's not the only app that is causing me issues in recognising that the device is rooted.
It's an Australian Note 8 (SM-N950F)
Cheers!
I have not rooted my note 8, but, I had a simmilar issue with my note 4, The SU that came with root did not work as intended, so I searched and found that there were several more SU apps, I dont remember names, the thing is, I tried several SU, untill one worked
I've heard of the issue but never personally encountered it ever on any of my Android phones. Not sure if it has anything to do with Super Su versions but I have used 2.82, 2.82-SR4, & 2.82-SR5 without any issues. I'm currently using 2.82-SR4 on my F.
is magisk installed? if not, try to install magisk manager and check if you might be rooted through that app. if yes you dont need super su.
winol said:
I have not rooted my note 8, but, I had a simmilar issue with my note 4, The SU that came with root did not work as intended, so I searched and found that there were several more SU apps, I dont remember names, the thing is, I tried several SU, untill one worked
Click to expand...
Click to collapse
bober10113 said:
is magisk installed? if not, try to install magisk manager and check if you might be rooted through that app. if yes you dont need super su.
Click to expand...
Click to collapse
Cheers, I had Magisk Manager already installed, but SuperSU hadn't been activated for the specific app, so it wasn't been given root access!
Easy solve.
rajalot said:
Cheers, I had Magisk Manager already installed, but SuperSU hadn't been activated for the specific app, so it wasn't been given root access!
Easy solve.
Click to expand...
Click to collapse
very simple solution reflash kernel reboot go to app drawer unistall magisk long press icon back to twrp flash supersu wipe cache dalvik reboot
As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
recepo1 said:
As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
Click to expand...
Click to collapse
working fine here. maybe a root/magisk issue.
bober10113 said:
working fine here. maybe a root/magisk issue.
Click to expand...
Click to collapse
What rom are you on and which version of magisk are you running?
recepo1 said:
What rom are you on and which version of magisk are you running?
Click to expand...
Click to collapse
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
bober10113 said:
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
Click to expand...
Click to collapse
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
recepo1 said:
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
Click to expand...
Click to collapse
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
bober10113 said:
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
Click to expand...
Click to collapse
Thank you appreciate your help i will give it a try
I have tried everything for hours to get viper4android to work with no avail until now. Go to the xda download page and select the beta version. Boom. It works. I know you might have long forgot this or already figured it out but I had to share
old legacy magisk module has been working for months and months.
Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you
urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!
For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.
One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.