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
Related
Magisk v16.4 (also tried v16.0)
I've hidden the app in the HIDE list, I repackaged Magisk, force stopped NemID, cleared cache and data, and the app still spots root. I've successfully hidden apps from root before using this method, so it's just this app here that somehow goes beyond the usual. Are there any further steps I can take to hide root from the app more thoroughly?
Thanks
{
"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"
}
Launchy21 said:
Magisk v16.4 (also tried v16.0)
I've hidden the app in the HIDE list, I repackaged Magisk, force stopped NemID, cleared cache and data, and the app still spots root. I've successfully hidden apps from root before using this method, so it's just this app here that somehow goes beyond the usual. Are there any further steps I can take to hide root from the app more thoroughly?
Thanks
Click to expand...
Click to collapse
I believe that the app detects root by any of the following things :-
1. Bootloader unlocked detection
2. Custom ROM detection
3. Presence of apps that require root
4. Reading log of root being used (which is very rare, but possible)
5. Some very private code that renders Magisk useless
Tested it, and the app looks for both Magisk and the Manager. With the app on the Hide list and the Manager repackaged I can open the app without issue. It doesn't seem to "remember" root. This is on stock OxygenOS and also NitrogenOS (both on Oreo).
The app might be detecting other properties of the ROM your using (if not stock) or other known root apps on your device. Try running a logcat when the app detects "root" to maybe see what it's detecting, or simply uninstall some root apps and try again.
It works for me aswell, im using custom rom 8.1, hide the app, repackage, reboot, open app
So if that doesnt work, you might wanna try another rom as mentioned above me
It seems the app changed its way of detecting root after their upgrade on 25/6. It also worked for me before by using Magisk Hide and repack Magisk manager, but not anymore.
It is a losing battle anyway, just a matter of time. So I do not expect this method will work for good.
yeah my nemid app also stopped working a few days ago. This is not good if its not possible to hide root from an app anymore
Since there are users reporting that they can open up the app with MagiskHide active for NemID and the Manager repackaged, it's very likely that the app is detecting some other thing on your device. It could be a property of a custom ROM you're using, it could be a root app, etc... Possible solutions: try a different ROM (as stock as possible), uninstall root apps, etc.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Ok I'm running Samsung s7 stock oreo w. Root. Knox is tripped
Removed all apps needing root, installed magiskhide props config module, disabled systemless hosts.
Still no go. It worked until before latest update
mbeltoft said:
Ok I'm running Samsung s7 stock oreo w. Root. Knox is tripped
Removed all apps needing root, installed magiskhide props config module, disabled systemless hosts.
Still no go. It worked until before latest update
Click to expand...
Click to collapse
What Magisk version do you have? If not on beta v16.4, the issue might be that the app has a sub-process that previous Magisk versions can't hide automatically. Scratch that... Just went back and saw that the OP has tested it on v16.4.
Or, if you're unlucky it's checking Knox...
Does it only check for root at the start, or is it other points as well? As stated before, I can open the app just fine on both my Oneplus 3T and Nexus 6.
AFAIK it's only checking at start-up. It shows it's load screen for a few seconds ( but longer than before when it was working) and then give the error screen OP posted.
If you leave the app and reenter it it will show the main screen but jump back to the error screen whenever a button is pressed
I tested this on a pixel 2 with stock rom in this order :
All root apps installed, no magisk or root : working fine
All root apps installed, no magisk or root, custom kernel: working fine
All root apps installed, root and magisk, magisk hidden+magisk hide: not working
No root apps installed, root and magisk, magisk hidden+magisk hide: not working
No root apps installed, root and magisk, magisk manager not installed+magisk hide: working
I then tried cloning the apk without changing the name: not working
I tried cloning the app but changing the name of Magisk Manager from "Magisk Manager" to just "Manager" and then Nemid worked again.
Could it be the Nemid app is just looking to see if there's an app called Magisk Manager installed and if there is, the app failes
Unfortunately the cloned app doesn't work. Maybe we could have the "Hide magisk" function rename the app name too?
//Peter
Just tried cloning an entirely different app and renaming it "Magisk Manager" - after this the nemid app failed, so I guess that confirms that nemid just checks the name.
//Peter
Nice detective work.
By uninstall the app (not unroot) NemID works. If you use magisk 16.6 you can just reboot phone to get the manager again or just install the apk.
But if being able to change magisk managers name to something generic (like manager) or a custom name could be a great solution (I would change name to NemID). Because if nemid can defeat magiskhide, others will follow
I posted the findings in the beta thread but I think it got removed during thread cleanup. Any other way to let the developers know?
peter_dk01 said:
I posted the findings in the beta thread but I think it got removed during thread cleanup. Any other way to let the developers know?
Click to expand...
Click to collapse
It's already on the to-do list.
Didgeridoohan said:
It's already on the to-do list.
Click to expand...
Click to collapse
Perfect! Thank you ?
Didgeridoohan said:
It's already on the to-do list.
Click to expand...
Click to collapse
Unfortunately, the change is not included in the latest 5.8.1 release.
kqueenc said:
Unfortunately, the change is not included in the latest 5.8.1 release.
Click to expand...
Click to collapse
Manager v5.8.1 was simply a bug fix. Stability is prioritised over new features. You'll have to wait, and that feature will be available when it's available. Not before that...
Didgeridoohan said:
Manager v5.8.1 was simply a bug fix. Stability is prioritised over new features. You'll have to wait, and that feature will be available when it's available. Not before that...
Click to expand...
Click to collapse
Is there any other workaround to change the name of Magisk Manager App in order to bypass the check? And will there be any other consequence (like root cannot be detected by other app)?
kqueenc said:
Is there any other workaround to change the name of Magisk Manager App in order to bypass the check? And will there be any other consequence (like root cannot be detected by other app)?
Click to expand...
Click to collapse
Until there is a feature like that, you can uninstall or freeze the Manager whenever you need to use whatever app detects it.
Hey,
I have the problem that if I install Magisk and repack the App with a different name, the app will be duplicated after reboot. If I do not reboot, the app will start (Without hiding Magisk Manager self and only the app, not) One says that I have to install manager app, and the other stuck on splash screen.
Here is a screenshot of the "hidden" magisk manager, after reboot I dont have root access to make another screenshot cause there is now "hey, here is root acquired prompt"
{
"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"
}
I really need this feature for using an important app. Without the magisk manager hide function it will be dedected (Magisk Hide for app is active)
Using Honor 8x wit EMUI 8.2, Android 8.1 and Magisk v17.1 (stable)
Hope anyone have a solution.
Regards
Schmand
Schmand said:
Hey,
I have the problem that if I install Magisk and repack the App with a different name, the app will be duplicated after reboot. If I do not reboot, the app will start (Without hiding Magisk Manager self and only the app, not) One says that I have to install manager app, and the other stuck on splash screen.
Here is a screenshot of the "hidden" magisk manager, after reboot I dont have root access to make another screenshot cause there is now "hey, here is root acquired prompt"
I really need this feature for using an important app. Without the magisk manager hide function it will be dedected (Magisk Hide for app is active)
Using Honor 8x wit EMUI 8.2, Android 8.1 and Magisk v17.1 (stable)
Hope anyone have a solution.
Regards
Schmand
Click to expand...
Click to collapse
First of all, download latest Magisk version (17.3 as of now). Then uninstall Magisk from TWRP by using the uninstaller zip. Reboot your device, then reboot back to recovery and install the latest Magisk version again. Reboot and open Magisk Manager, then re-install Magisk with a different package name. Open Magisk Manager again and use the Magisk Hide option to select Google Play Services as well as Google Play Store in addition to the app that shouldn't detect Magisk. Reboot your device again and check if everything works as intended.
Portgas D. Ace said:
First of all, download latest Magisk version (17.3 as of now). Then uninstall Magisk from TWRP by using the uninstaller zip. Reboot your device, then reboot back to recovery and install the latest Magisk version again. Reboot and open Magisk Manager, then re-install Magisk with a different package name. Open Magisk Manager again and use the Magisk Hide option to select Google Play Services as well as Google Play Store in addition to the app that shouldn't detect Magisk. Reboot your device again and check if everything works as intended.
Click to expand...
Click to collapse
Hey, which services exactly? Just fingind the google play store app. But not the other one you mentioned. If I just hide them (with the app) it doesnt work )=
Schmand said:
Hey, which services exactly? Just fingind the google play store app. But not the other one you mentioned. If I just hide them (with the app) it doesnt work )=
Click to expand...
Click to collapse
Magisk hides itself from Google Play Service by default, forgot about it. Did you also re-install Magisk Manager with a different package name? You also might want to try deleting the Magisk Manager folder on your internal storage and reboot.
Portgas D. Ace said:
Magisk hides itself from Google Play Service by default, forgot about it. Did you also re-install Magisk Manager with a different package name? You also might want to try deleting the Magisk Manager folder on your internal storage and reboot.
Click to expand...
Click to collapse
Hey, that doesnt work, too. After I hide magisk most of the time it say, that I dont have magisk installed. If I remove the hided app and install normal magisk manager app. Everything works fine, but without the app I need (cause will detected that magisk installed). Testet also with RR rom. Same result ._.
//SmallEditAgain
If I dont reboot now, anything work. Until I reboot => Brocken
@Schmand
I had the same "Magisk not installed" issue when re-installing Magisk with a different package name. I then just rebooted my device again and the "new" Magisk Manager app showed up. When I opened it, it said "Magisk installed" and everything was working from there on.
By the way, what's the app that you are trying to hide Magisk from?
Portgas D. Ace said:
@Schmand
I had the same "Magisk not installed" issue when re-installing Magisk with a different package name. I then just rebooted my device again and the "new" Magisk Manager app showed up. When I opened it, it said "Magisk installed" and everything was working from there on.
By the way, what's the app that you are trying to hide Magisk from?
Click to expand...
Click to collapse
Hey, thats not working for me )= Tried many times.
The app I want to hide is "Sparkasse pushTAN" now I just deinstall Magisk every time I need a tan. But that is verry stupid work ._.
Have you tried the latest Canary build? The issue described by the OP is caused by magisk.db issues, and those should have been taken care of with some recent commits.
Didgeridoohan said:
Have you tried the latest Canary build? The issue described by the OP is caused by magisk.db issues, and those should have been taken care of with some recent commits.
Click to expand...
Click to collapse
Latest canary build? What did you mean, downloaded and installed magisk 17.3 (Beta)
//EDIT
Set up the custom repository to canary build and updated magisk manager and patched boot image. Now I hide the app and will see whats happening
//UPDATE
It worked for me. Thank you a lot :good::highfive::highfive:
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
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.
Greetings everyone,
I have been working on implementing Magisk on the Nox emulator with the aim of enabling financial applications to function. I am seeking assistance with this and would also like to share my knowledge, which I have accumulated over the past week. Although I am relatively new to this area, I have a sense that I am getting closer to achieving my desired outcome.
Here is a breakdown of my current setup:
Nox x64 Android 9
Magisk Delta v25.2.10
Modules:
- Universal Safetynet-Fix v2.4
- Shamiko v0.6
- MagiskHide Props Config v6.1.2
- BusyBox Android NDK v1.34.1
- LSPosed (Zygisk) v1.8.6 + HideMyApplist Module
Installed Root Apps:
- FDroid
- Termux
- LSPosed
- HideMyApplist
- ApplistDetector
- YASNAC (Another Detector)
Apart from these apps, I have only installed financial applications.
The following are the issues that I have encountered along with my questions:
1. ApplistDetector detects the org.lsposed.manager module, even though it is almost clean. Is there a workaround for this issue? I have attempted to add the detector in HideMyApplist, but the results were not satisfactory.
2. I have translated some Vietnamese and Russian Magisk communities, and they added the following processes to MagiskHide. I have replicated their work for now. Here is a list of those processes and the issues I have encountered for each of them:
com.google.android.ims (this does not show on my MagiskHide)
com.google.android.gms (this is a GooglePlay Services process, and when I add this and reboot, the process goes into a crash loop)
com.android.vending (this is a GooglePlaystore process, and like com.google.android.gms, it also causes a crash loop)
com.google.android.gsf (Google Services Framework settings look different from how it appears on an actual phone, as it usually has two processes inside, and I can only see one on my MagiskHide, which also causes a crash loop)
com.android.statementservice
com.google.ar.core (this does not show in my MagiskHide, but it is most likely because it is for GooglePlay Augmented Reality). Is it mandatory to have all services to make the spoofing work? I do not think so, but I am pretty sure some are missing for my goal.
3. None of the financial apps that I have installed would start. They either get into a crash-loop, freeze on the logo screen/blank screen, or do not do anything when clicked on. This is most likely due to the fact that I cannot add com.android.vending and com.google.android.gsf without running into the annoying popup-crash-loop from both services. I just end up removing them again from the MagiskHide list to stop the damn popups.
4. I am not yet sure what exactly I am supposed to do with MagiskHide Props Config.
Here are the steps I've performeed to get to my current (malfunctioning) setup (not in 1:1 chronological order):
1. Install Magisk Delta (Direct install on system partition) to root.
2. Drag all root-apps into Nox, one after one.
3. Log in to PlayStore, and download the financial apps.
4. Install all Magisk Modules (and LSPosed HideMyApplist Module).
5. In MagiskHide, add all necessary services and financial apps services.
6. In HideMyApplist, add all root-detector apps, financial apps, and Google's services from the previous list on Whitelist Mode + Exclude System Apps. Then, I add root-related apps such as Termux and LSPosed apps with Blacklist Mode.
7. Set custom device in Nox (I did Samsung S22 Ultra (5G) - SM-G988B). Then, make a new fingerprint in Termux with MagiskHide Props Config. Type: su, props, 1, f, and select Samsung, then select S22 Ultra (5G) - SM-G988B, type y and reboot
I am eager to continue my progress and develop this thread into a comprehensive guide with the assistance of fellow XDA members for those interested in spoofing Magisk on emulators. Thank you in advance for your help <3
Poprook (@grinninz on Telegram)
i think we need to relock the bootloader to pass the Strong integrity test... recently one of my bank app has stopped working after 3 month of using ... i have tried everything after the update... passed all rootchecking test and still doesn't work (it just hang the app). only conclusion is: the bank app now check my bootloader...my other bank apps still work, is just that particular bank app is not working
but something is strange... i have the same setup on the other phone (xiaomi), all the setup are same with my current phone (sony Xperia 1 iii), with latest version etc.. and that particular bank app works... seriously now, i dont know whats going on
Does anyone know how to pass basic and device integrity on an emulator with magisk?
UPDATE/EDIT:
I've managed to almost hide root succesfully.
I additionally installed this LSPosed module: "Play Integrity Bypass" (made to work with Shamiko), which seemed to have done the trick, all apps are opening with MagiskHide enabled.
Settings:
- Zygisk Enabled
- MagiskHide Enabled
- Google (Play/Framework) Services
- Financial + Detector Apps
- HMA with Financial + Detector apps on whitelist, root apps on blacklist
ApplistDetector has become 100% clean
Does anyone know how I can hide these last two detections from Oprek Detector?
{
"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"
}
poprook said:
UPDATE/EDIT:
I've managed to almost hide root succesfully.
I additionally installed this LSPosed module: "Play Integrity Bypass" (made to work with Shamiko), which seemed to have done the trick, all apps are opening with MagiskHide enabled.
Settings:
- Zygisk Enabled
- MagiskHide Enabled
- Google (Play/Framework) Services
- Financial + Detector Apps
- HMA with Financial + Detector apps on whitelist, root apps on blacklist
ApplistDetector has become 100% clean
Does anyone know how I can hide these last two detections from Oprek Detector?
View attachment 5880043View attachment 5880049
Click to expand...
Click to collapse
Are you able to pass Device certification on Play Store with this?