Database Develop

Two Magisk Manager Apps in system tray. One force closes, the other does not.

I'm having an issue where Magisk Manager (among other applications) have two icons in the app drawer. I think this is due to one of them being a "system app" and the other just being a normal application.
The issue I am having is that the normal Magisk application force closes upon launching, while the system app is able to open, but does not have any options for installing zips from repos.
I am using a Moto Z Play on 8.0. I've tried completely uninstalling Magisk and reinstalling but did not have luck with this. I'm not sure what I can do to fix this issue?
Thank you for any help!
Here are some screenshots showing this.
The system tray showing both apps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The app details for the system app (I noticed this app details is not substratum themed):
The app details for the normal app (I noticed this app details is substratum themed):
The system application showing that Magisk is installed:
But the system application showing no option to install from repos:

Uninstall both apps and reinstall with the apk from the release thread, and you should be good to go.

Thank you for the reply.
I have uninstalled both installations, and installed the v5.7.0 from the release thread. Unfortunately the application force closes upon launching. I actually started this uninstall/reinstall process due to this initial issue of the Magisk Manager force closing upon launch. From my searches this is usually fixed by clearing the applications data and cache and a reboot. However, for me those steps did not work.

One thing I find odd is that it says it "keeps stopping" but the application does launch just fine...
EDIT: Let me post back with some logcat details, once I figure out how to get those

Here is a link to the logs that I got via running ./adb logcat -v long > magisk.txt and then immediatly launching the application. I hope it is helpful: https://paste.ee/p/sJfvb

MrTissues said:
Here is a link to the logs that I got via running ./adb logcat -v long > magisk.txt and then immediatly launching the application. I hope it is helpful: https://paste.ee/p/sJfvb
Click to expand...
Click to collapse
There's this in there:
Code:
[ 07-06 16:34:52.493 29515:29536 E/AndroidRuntime ]
FATAL EXCEPTION: Thread-2 Process: com.topjohnwu.magisk, PID: 29515
java.lang.StringIndexOutOfBoundsException: length=441; index=-1
at java.lang.String.charAt(Native Method)
at com.topjohnwu.superuser.internal.StreamGobbler.run(Unknown Source:52)
Doesn't look too good...
I would be interested in seeing your Magisk debug log. If you're not already on Magisk v16.4 beta, please install that and provide the debug log that you'll find in /data/adb. It'd probably also be a good idea to run the uninstaller first and do a clean install (from which it would be interesting to see the install log).

Thanks!
Here are the logs for uninstalling Magisk, installing Magisk 16.4 beta, and then installing f2loopback fix (necessary for Moto Z): https://paste.ee/p/A9ZXz
Here are logs from Magisk itself: https://paste.ee/p/P5iyO
The need for f2loopback is maybe troubling, though I can confirm that this did work. I know Magisk is properly doing its thing b/c I am able to get root access (confirmation dialog appears) in apps like Solid Explorer so that I can provide these logs. Its just the Manager itself that has crash issues.

I see that a new version v5.8.0 was released of the Manager. Unfortunately the problem remains.
The beta version of Magisk v16.6 does not work on my phone, it causes boot loops. Maybe the f2loopback patch needs to be updated for it.

MrTissues said:
I see that a new version v5.8.0 was released of the Manager. Unfortunately the problem remains.
Click to expand...
Click to collapse
Could you provide a logcat from v5.8.0 crashing? Just to make sure that all the information collected is relevant?
The beta version of Magisk v16.6 does not work on my phone, it causes boot loops. Maybe the f2loopback patch needs to be updated for it.
Click to expand...
Click to collapse
You could test by going without the f2loopback module. It wouldn't be necessary for basic Magisk functionality, and then we'd knew if it was caused by the module or not.

Based on the orange icons, you have some things installed under your work profile as well. That's why there's 2.

I've had problems Magisk disappearing on my OnePlus 5T. I've run the Uninstaller in TWRP followed by 18.1. Now have two Magisks in the add drawer: one labelled 'Magisk Manager' which says the phone is rooted and all is well; the other (same icon) is labelled simply 'Manager' and says that Magisk isn't installed! As things stand, it's just a nuisance. Everything seems to work fine with the Magisk. I'm reluctant to uninstall the 'Manager' in case in brings down the other one, but I'd love to tidy it up.
Running OOS 9.3.

@chriscross
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers

[NO ROOT] Enable McLaren fingerprint animation on OOS 9 / Disable animation at all

Quick update: As (I hope) no one is still using OOS9, this method must be considered deprecated.
Hello,
this is how to enable the McLaren fingerprint animation from the Oneplus 6T McLaren edition on normal 6T editions without a PC, root, module, app whatsoever (depends on the method you choose). You can also choose to disable the animation at all. For the McLaren animation OOS 9.0.9 or newer is needed since the animation files are included from this verison on. You just can't enable it through the settings app. If you ask me, the unlocking feels even faster with this animation!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
OOS version greater than 9.0.9, OOS 10 does not work (if you want to disable the animation, any version will work)
Either the app below (no root), adb (no root), magisk or another root solution
Method 1: No root, on-device, super-easy
Download this app from Google Play.
Open it and confirm that "System table" is selected.
Scroll down and search for the line "op_custom_unlock_animation_style".
Touch the line and then press on "Edit value".
Enter "3" (no quotes) and confirm.
Enjoy. You can delete the app now if you want.
Can't find the line? Go with this:
Try to change your current fingerprint animation in settings and check the app for the line again (fully close it first). If there, continue above, if not continue below.
Confirm that "System table" is selected.
Tap "Add new setting". There will be 2 prompts.
Replace "NEW_SETTING" with "op_custom_unlock_animation_style" (no quotes) in the first one and confirm.
Replace "SETTING_VALUE" with "3" (no quotes) in the second one.
You should be good to go! If you want you can delete this app now.
Please note:
Some users reported that the setting didn't survive reboots when removing the app. Try for yourself.
I recommend not to mess with other settings if you don't know what you are doing.
Method 2: No root, adb needed
Connect your device and verify your adb connection by using
adb devices
Proceed by entering
adb shell settings put system op_custom_unlock_animation_style 3
All done!
Please note:
If you do not understand what adb is or how to set it up, please use method 1 from above.
Method 3: Root needed, Magisk module
Download the Magisk module .zip from the attachments below.
Install it through Magisk Manager.
Enjoy!
Please note:
There will be no module visible in Magisk Manager, no files modified and no boot scripts. To disable just select a default fingerprint animation through settings and to enable reflash the module. Don't know if TWRP flashing works.
You can alternatively use AnoopKumar's module to enable a full McLaren experience with bootanimation, fingerprint animation, wallpapers etc. Found here. Difference to my module: Enables the animation on every boot so it will overwrite your setting if you choose another animation but don't disable the module.
Method 4: Root needed, terminal solution
Open your terminal app of choice
Switch to root by entering
su
Enable the animation by entering
settings put system op_custom_unlock_animation_style 3
Extra: Disable animation at all
You can use any of the above methods
Just replace the value "3" with a non-existent animation number, for example "4" (if future OOS updates add more animations, you need to use a higher value)
Magisk module also available ("no-fp")
Extra: McLaren color theme
Head over to Settings -> Display -> Theme, and set it to "Dark".
Next, tap on "Accent color" and tap on the custom color icon.
Input the hex code "#E0610E" in there.
That's it.
Additional information:
The setting survives reboots.
You might have to try it several times to make it stick after reboots.
Some users reported that they needed to keep the app installed in order to make it stick after reboots when using method 1.
To disable the changes, just enable one of the default fingerprint animations through the settings app. This works the same way for EVERY method.
Hit thanks!

Your post doesn't view right on the XDA app, here's the actual command for others
Code:
adb shell settings put system "op_custom_unlock_animation_style" "3"

OMG. Thank you!

Lartsch said:
Hello,
this is how you can enable the McLaren fingerprint animation from the Oneplus 6T McLaren edition on normal 6T editions without any mods, modules, apps whatsoever.
OOS 9.0.10 is needed since the animation files are included with this verison (you just can't enable it through settings).
Requirements:
OOS 9.0.10
ADB up and running
Steps:
Connect your device and verify your adb connection by using
adb devices
Proceed by entering
adb shell settings put system "op_custom_unlock_animation_style" "3"
All done!
Additional information:
The setting survives reboots.
To disable it again, just enable one of the default fingerprint animations through normal settings.
Click to expand...
Click to collapse
I'll try this out later when I can get to a PC, but thanks man! It would be awesome if someone could make a Magisk module for this, since I have a feeling the animation is going to be removed from later updates for the normal 6t!

H4X0R46 said:
I'll try this out later when I can get to a PC, but thanks man! It would be awesome if someone could make a Magisk module for this, since I have a feeling the animation is going to be removed from later updates for the normal 6t!
Click to expand...
Click to collapse
If you're already rooted check OP, you can do the same with a terminal emulator and root privilege of course.

Lartsch said:
If you're already rooted check OP, you can do the same with a terminal emulator and root privilege of course.
Click to expand...
Click to collapse
......... I love you.... LOL jokes aside, thanks man! That worked! ???

H4X0R46 said:
......... I love you.... LOL jokes aside, thanks man! That worked!
Click to expand...
Click to collapse
Updated OP once more, now with an even easier method
You're welcome!

yes it works

Thanks Buddy For This really Awesome.
Way 1 Is Super Duper Easy and works like charm

Works on 9.0.9 btw
EDIT: I like 2 better tbh

Can't find that line in the app.
OS 9.0.10

Thank you very much. Method 1 with the app works. It took 10 seconds.
EDIT: I'm on 9.0.10, rooted with Magisk, no TWRP. But as the OP stater, NO ROOT IS NEEDED!

That's amazing. Thank you so much!

In the app I can not find that line?

candleworth7808 said:
Can't find that line in the app.
OS 9.0.10
Click to expand...
Click to collapse
I don't have it either, I am on the TMO variant running international 10. don't know if that makes a difference
Sent from my ONEPLUS A6013 using Tapatalk
Update
I ran the command in terminal then opened the app and the line was there twice, I removed the one I entered and changed the Vale to 3 as per instructions and I'm good to go.

If you can't find that line in the app, you can add it in the app yourself.
Simply tap +Add New Setting
Then type
op_custom_unlock_animation_style
Tap save changes
Then enter the value of 3
Tap save changes.
Then go to settings, security, fingerprints, and see McLaren!

@Lartsch Good one mate, I can confirm this works on Open Beta 1 also. You may update the OP :good:
Sent from my OnePlus6T using XDA Labs

Thank you OP.
I used the first method as i m stock and locked. Super easy.
The line wasn't present so as per suggestion i added it and it works perfectly. In settings it shows cosmos, idk why.
Edit - it didn't survive reboot, had to do it again.
Does adb shell method survive reboot?
Edit 2 - on second try it shows McLaren in settings and also survived reboot. I m glad that it works.

App worked but I had to change from default in normal phone settings before the line showed up in app. Thanks OP.

Everything is working flawless but my alert slider isn't showing the notifications of phone mute or vibrate with icon on the main screen but it's working any fixes please

Fix ctsProfile false (Rooted devices)

Hi guys.
For those of you that recently unlocked your bootloader and rooted your device with Magisk... If you don't already know, you can download a Magisk Module created by Didgeridoohan, called 'MagiskHide Props Config'. Basically this solves the issue of the ctsProfile failing in safetynet. What it does is it can change the device fingerprint to one that is certified, allowing safetynet to pass.
I lot of you probably already know this, but I've read a lot posts about ctsProfile issues.
With this module, you should be able to use ANY official huawei mate 20 pro firmware and safetynet should pass.
There is more info about this module in thread https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228

So what is the steps you need to follow?
I have u locked bootloader and safety et is failing. At cts.
Evert hing is stock and wiped.
Verstuurd vanaf mijn LYA-L29 met Tapatalk

First root the phone. Flash the patched recovery_ramdisk.img posted in this thread https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Follow the Rooting intructions.
Once you've done that. Go into Magisk Manager and search for MagiskHide Props Config
Download and install it.
Reboot the phone.
Download Terminal Emulator from the google play store
Open it and grant root access by typing su
Run the command 'props'
Then just follow the instructions.

What if I don't want the root. Is it possible to get the ctf error false to fixed without rooting but having bootloader unlocked?
Verstuurd vanaf mijn LYA-L29 met Tapatalk

aygul12345 said:
What if I don't want the root. Is it possible to get the ctf error false to fixed without rooting but having bootloader unlocked?
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Click to expand...
Click to collapse
Not that I know of. I know certain firmwares don't get the error so you could try out a few until you find one that passes safetynet.
eg. for me, I know the .183 passes safetynet without having to change the fingerprint or anything else.

DN38416 said:
First root the phone. Flash the patched recovery_ramdisk.img posted in this thread https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Follow the Rooting intructions.
Once you've done that. Go into Magisk Manager and search for MagiskHide Props Config
Download and install it.
Reboot the phone.
Download Terminal Emulator from the google play store
Open it and run the command 'props'
Then just follow the instructions.
Click to expand...
Click to collapse
What am I doing wrong?
I've unlocked bootloader, rooted, installed the module you suggested, rebooted, installed terminal emulator and ran the 'props' command.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jfenlon01 said:
What am I doing wrong?
I've unlocked bootloader, rooted, installed the module you suggested, rebooted, installed terminal emulator and ran the 'props' command.
Click to expand...
Click to collapse
Did you follow the instructions and change the device fingerprint?
Reboot after that. Check the safetynet in Magisk and it should pass ctsProfile now.
(Unless your BasicIntegrity is also failing then this module won't work)
EDIT: Sorry.. the pic didn't load before.
Hmm... Looks like the module isn't installed properly if you have that error.
are you definitely in rooted state? (Hold volume up as you boot up)

Yep, definitely rooted.

jfenlon01 said:
Yep, definitely rooted.
Click to expand...
Click to collapse
That’s weird. I’m not sure what’s wrong then. I assume you tried rebooting again?
Maybe read through the documentation on the main thread and look in the troubleshooting section? Mine works as soon as I enter the props command.
What version of Magisk are you using? 18.1?

Yeah 18.1, downloaded from this forum. I tried to patch my own with magisk but it wouldn't boot. Still no joy.

jfenlon01 said:
What am I doing wrong?
I've unlocked bootloader, rooted, installed the module you suggested, rebooted, installed terminal emulator and ran the 'props' command.
Click to expand...
Click to collapse
First type "su" to grant root

jfenlon01 said:
Yeah 18.1, downloaded from this forum. I tried to patch my own with magisk but it wouldn't boot. Still no joy.
Click to expand...
Click to collapse
I noticed this in the documentation in the thread.
"MagiskHide Props Config v2.7.2 and earlier versions won't work on Magisk v18.1-d73127b1(18006) or later, due to internal changes in Magisk."
Does that apply to your situation?

Th3PorTuGa said:
First type "su" to grant root
Click to expand...
Click to collapse
OMG I can't believe I forgot about that. Yeah make sure it has root access first sorry. Typing su will bring up the prompt to grant root access. You might need to have Magisk Manager running in the background.

DN38416 said:
I noticed this in the documentation in the thread.
"MagiskHide Props Config v2.7.2 and earlier versions won't work on Magisk v18.1-d73127b1(18006) or later, due to internal changes in Magisk."
Does that apply to your situation?
Click to expand...
Click to collapse
I tried su already guys, it's in the first screenshot.
Also magisk props config v3.5.0 so that from the documentation shouldn't apply either.
Thanks for trying to help.

jfenlon01 said:
I tried su already guys, it's in the first screenshot.
Also magisk props config v3.5.0 so that from the documentation shouldn't apply either.
Thanks for trying to help.
Click to expand...
Click to collapse
do it again and make sure Magisk manager is running beforehand
Close both apps and start again. Open Magisk Manager, then open Terminal Emulator and type su, it should then come up with the prompt to grant root access.
Once it's granted THEN you can run the 'props' command

I tried also 'props' with the ' in case that's what was required. Just can't get it to work.
[edit]
I'm thinking it's because I didn't have the Magisk Busybox module by osm0sis, installing that and will try again.
---------- Post added at 02:48 PM ---------- Previous post was at 02:34 PM ----------
Still no joy

That’s strange. Not sure what’s wrong.
I’m outa ideas. Have you tried uninstalling and reinstalling MagiskHide props module?

DN38416 said:
That’s strange. Not sure what’s wrong.
I’m outa ideas. Have you tried uninstalling and reinstalling MagiskHide props module?
Click to expand...
Click to collapse
Yep, tried that twice. Most recently after installing Magisk Busybox.
Thanks for trying to help.

I'm getting the same issue unfortunately, no idea why "props" isn't found

Will I be able to run banking apps?
Sent from my LYA-L09 using Tapatalk

Magisk Manager: Manager was denied Superuser rights (and buttons missing)

Please see the posted screenshot image for the problem. I just got a brand new OnePlus 8 Pro today, updated the firmware (it's current and running Android 11), unlocked the bootloader, installed my data, and rooted it. Since there is no TWRP for Android 11 for this device, I had to manually extract the current boot.img and patch it myself with Magisk Manager to root this device.
On the first boot after root, I launched Magisk Manager. The countdown timer was so fast, I did not have a chance to grant Magisk Manager root permissions. Now Magisk Manager is being denied Superuser permissions, and there are no buttons at the bottom of Magisk Manager to set Magisk Hide settings or set what apps are allowed Superuser/root.
I have googled as well as searched this forum for relevant help, and have found nothing helpful (really, I may have missed something, but I did try). How can I reset the apps allowed root permissions so that I can grant Magisk Manager the Superuser permissions it needs to function?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help is greatly appreciated!
I already tried force stopping Magisk Manager and clearing the storage for Magisk Manager (which did nothing to solve the problem).

https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access
Click to expand...
Click to collapse
Thank you for the reply. I found this article earlier (or a variant of it), and it does not appear to solve the issue. I don't have two different Magisk Managers installed. I just accidently denied the one Superuser access by not granting it Superuser access quickly enough.

The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.

Didgeridoohan said:
The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.
Click to expand...
Click to collapse
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).

chriv said:
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).
Click to expand...
Click to collapse
Just out of curiosity, did you solve it be deleting the database file?

Didgeridoohan said:
Just out of curiosity, did you solve it be deleting the database file?
Click to expand...
Click to collapse
I wish I could say, yes, but no. Long story short, I started over from a clean phone install. Unfortunately, (this part is off topic), I accidently upgraded to 11.0.4.4.IN11AA with an OTA after starting over (the version almost nobody has yet), didn't realize it, and patched a stock 11.0.2.2.IN11AA boot.img and flashed it to the boot partition. Magisk and root worked great, but WiFi and phone calls were broken. Now I'm stuck waiting to get the 11.0.4.4.IN11AA full package (Global/NA/US version of 11.0.4.4) to fix everything (by extracting the boot.img from a payload dumper).

So you mean that deleting the database file didn't work, or that you never tried it?

Sorry if I was unclear. I didn't try it. My phone was already in a state where I could not try it (and this no longer applied) before I saw this message. I am very grateful for the assistance/information.

I have the same problem. can you help me?

kas001 said:
I have the same problem. can you help me?
Click to expand...
Click to collapse
Have you already checked to see if this is the cause? https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access. It's definitely the best starting point.

Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.

SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.

aleep123 said:
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.
Click to expand...
Click to collapse
Can you please explain?

ivanov_16 said:
Can you please explain?
Click to expand...
Click to collapse
There's a setting in the Magisk app where you can rename it with a random package name, to hide it and make the app harder to detect. This will give it a generic Android icon and give it the same "Settings" (previously it would name the repackaged app "Manager").

OK I missed the prompt to grant access to the ADB shell. Where's the settings for all the applications permission grants? So that I can untick the "deny" for ADB shell. I've changed the setting from prompt to grant, and tried again. But the toast just says Shell denied superuser access.
Thanks.
--Chris
EDIT:
OK I just installed a terminal app and nuked
/data/adb/magisk/magisk.db
which allowed me to start the permission process over.
This sure seems like a brutal approach to grant/permission management. It also requires starting the whole process from scratch.

SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
You are a superstar!! I have been tearing my hair out for acouple of days now trying to work out why i could not reinstall magisk, this was exactly the solution to the problem i was facing, therefore i give you my gratitude.

I have the same issues after updating to v24.1 how can I Access to delete the duplicate apps of Magisk. It was naming to Settings.

After the 25206
Didgeridoohan said:
So you mean that deleting the database file didn't work, or that you never tried it?
Click to expand...
Click to collapse
I on the other hand tried it. Not sure if it works or not. After the 25206 to 25207 disaster, 25208 is finally normal except it can't hide itself anymore. Any solutions there? Many thanks. F Droid file explorer/Network Signal Guru also lost super user rights. Rootchecker now says it's not properly rooted

I tried deleting /data/adb/magisk/magisk.db with Termux but can't even access it as I get "permission denied" and am still seeing SuperUser and Modules greyed out. Tried sudo, was prompted to install 'tsu' package and it failed as it appears the host no longer exists

Unable to Install Modules

Rooted my phone (Galaxy S21 Ultra) recently, used Magisk, it seems to be working ok (ver. 25.1), although initially it seemed I couldn't install Modules from outside the app. I am unable to pass SafetyNet. Super User authorizations working fine.
After some helping from others and plenty of research, I installed Fox MMM and was able to install two modules. Now it seems I can't install modules from storage because the files themselves aren't being recognized as proper modules.
As you can see in this image, the icon itself is different from the ones recognized although they are all *.zip files. Safetynet and Shamiko are greyed out, while MagiskHide and Liboencrypt aren't - these two I can and did install.
Initially I thought it could be something to do with names, as the latter have underscores instead of dashes, but renaming them didn't work.
Neither Magisk nor Fox MMM recognize these files as modules, and they were all downloaded from GitHub.
I'm really stumped by this.
What could I do?
-- This is the image in the link, for easier access:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If the modules are correct then you can try this:
adb shell > su
magisk --install-module module.zip
If this returns error then post screenshot here.

NextGenMagisk said:
If the modules are correct then you can try this:
adb shell > su
magisk --install-module module.zip
If this returns error then post screenshot here.
Click to expand...
Click to collapse
Where do I type this?

wbane said:
Where do I type this?
Click to expand...
Click to collapse
Any terminal emulator (to skip using the adb shell command), like Termux, OR via ADB on a PC

If someone in the future finds this thread, I've got this solution:
Have you tried using Samsung's file manager? On the top left of your screenshot press the sandwich menu icon and select Samsung's file manager and try to select the module from there.​​I tried the above and it worked!​

NextGenMagisk said:
If the modules are correct then you can try this:
adb shell > su
magisk --install-module module.zip
If this returns error then post screenshot here.
Click to expand...
Click to collapse
I was stuck on Android 13 having "installation failed" message, but running this from the shell worked.

It seems like you're encountering issues with installing modules on your rooted Galaxy S21 Ultra using Magisk. Despite successfully rooting your phone and having Super User authorizations working fine, you're unable to pass SafetyNet. Additionally, you've tried installing modules from storage, but they aren't being recognized as proper modules.