Database Develop

Fail to login SnapChat -> MagiskHide Activated

I have activated MagiskHide
{
"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"
}
but SN has failed ... And i dosn't can connect
If you would know how to make everything green
Thx

https://www.didgeridoohan.com/magisk

Didgeridoohan said:
https://www.didgeridoohan.com/magisk
Click to expand...
Click to collapse
I have Delt Xposed but I am using it :/

1. Delete snapchat.
2. Install again.
3. Go to magisk hide and check snapchat
4. Try to login.
5. If it won't help, unroot phone, login to snapchat and root again.
Redmi Note 4X RR 6.0.0 Tapatalk

voxan24 said:
I have Delt Xposed but I am using it :/
Click to expand...
Click to collapse
Disable Xposed -> reboot -> Check SafetyNet (should be green) -> Login to Snapchat -> Enable Xposed -> reboot -> enjoy
Works for me.

worked for me too (last post )
on note 4 8.1.0 ustom rom with last version of magisk at the time of this post

I have the issue that I can not login on snapchat with magisk installed.
Magisk manager is hidden (as you can see a part of the package name in the 3rd line of the magisk manager part)
Snapchat is ticked in the magisk hide
You can see that safety net is passing and still I can not login on snapchat until I uninstall magisk.
I tried using a snapchat build from october 2018 (non beta) and it didn't let me log in either.

FPSUsername said:
I have the issue that I can not login on snapchat with magisk installed.
Magisk manager is hidden (as you can see a part of the package name in the 3rd line of the magisk manager part)
Snapchat is ticked in the magisk hide
You can see that safety net is passing and still I can not login on snapchat until I uninstall magisk.
I tried using a snapchat build from october 2018 (non beta) and it didn't let me log in either.
Click to expand...
Click to collapse
Did you fix it?

pixelgasm said:
Did you fix it?
Click to expand...
Click to collapse
Nope, just uninstall magisk, login and reinstall it. Use a secondary user account to login into other accounts, apparently you don't have magisk there, so it isn't being detected.

How to use Snapchat with magisk (After Ban)
FPSUsername said:
Nope, just uninstall magisk, login and reinstall it. Use a secondary user account to login into other accounts, apparently you don't have magisk there, so it isn't being detected.
Click to expand...
Click to collapse
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/...gisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ulitamte Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX

LELBOT said:
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/...gisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ulitamte Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
Click to expand...
Click to collapse
I hope you realize that it's an old post of mine. Ofc things changed in the past months. It seems to work fine if you just add snapchat to magisk hide. None of the other steps you mentioned are needed. I haven't tried it without the magisk hide, but I think that it will work as well.

Hello there,,
I am stuck in the same problem .. I did every step mentioned above and Safetynet check is always green & successful .. but still Snapchat is able to identify that I have Root on my device..
I can't find any real useful way that works 100% to hide the root. Snapchat allows me to login without problems but after like 2 - 3 days it send me a message that it will lock my account because of the " use of third-party app " ! .. Now my account is locked for 2 weeks and I read that it could be permanently locked !
I really need help .. I'm using ported samsung Note 7 fan edition ported Light Rom

aimmhr said:
Hello there,,
I am stuck in the same problem .. I did every step mentioned above and Safetynet check is always green & successful .. but still Snapchat is able to identify that I have Root on my device..
I can't find any real useful way that works 100% to hide the root. Snapchat allows me to login without problems but after like 2 - 3 days it send me a message that it will lock my account because of the " use of third-party app " ! .. Now my account is locked for 2 weeks and I read that it could be permanently locked !
I really need help .. I'm using ported samsung Note 7 fan edition ported Light Rom
Click to expand...
Click to collapse
Same problem here, I'm on Magisk v20.4 and i can't find a way to hide root to the latest Snapchat build with Android 9 even with Magisk hide activated on Snapchat and Google services.
As far as i remember, i never had this problem on Android 8 with Magisk v19.3 and Magisk hide activated.

Natizyskunk said:
Same problem here, I'm on Magisk v20.4 and i can't find a way to hide root to the latest Snapchat build with Android 9 even with Magisk hide activated on Snapchat and Google services.
As far as i remember, i never had this problem on Android 8 with Magisk v19.3 and Magisk hide activated.
Click to expand...
Click to collapse
Sad to know that you got the same problem..
Even the latest Magisk did not provide a solution for this issue.
For me the only way to use snapchat is to use a non rooted rom.. It works .. but Android phone without root is not interesting ..

aimmhr said:
Sad to know that you got the same problem..
Even the latest Magisk did not provide a solution for this issue.
For me the only way to use snapchat is to use a non rooted rom.. It works .. but Android phone without root is not interesting ..
Click to expand...
Click to collapse
I've finally found a way to make it working again !
This is what i've done :
1) Log-in to snapchat.
2) Root with magisk.
3) Magisk Hide: Snapchat, Google, Google Play Store, Google services framework, Google Play services.
4) Install Magisk module "MagiskHide Props Config" (needed to pass SafetyNet control: ctsProfile + basicintegrity).
5) Install Magisk module "HARDWARE OFF" (needed to reset SafetyNet evalType from HARDWARE to BASIC) : https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40658.
6) Go to Magisk options and select 'Hide Magisk Manager' to repack magisk with a new name (needed to completely hide the root).
7) Make sure Signature Verification is not disable and that no patches have been installed to android via "LuckyPatcher".
8) If installed, pleas uninstall "RIRU" Magisk module and any "riru"-related modules.
9) If installed, please make sure to uninstall Xposed Framework or any variant (systemless_Xposed, EdXposed, etc...) and all modules from it.
10) Make sure to uninstall LuckyPatcher if you have it and delete all residual files.
11) If installed, please uninstall Busybox and re-install it systemless-ly via the magisk module.
12) Now run this script in termux to fix snapchat root-detection (this will clean up your system file structure so it'll not return any false positives) : https://pastebin.com/haHtch32
If everything is done correctly, you should be able to use snapchat again without any issues and also without to worry about being banned again. At least for now ^^
Hope this can help.
Btw, sorry for my bad english, it's not my native language.

Magisk HIDE defeated by NemID code app

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.

MagiskHide, and other options, are not available in v23.0

Hi,
I installed Magisk.zip v23 into the system through TWRP, and Magisk.apk v23, on my Samsung Galaxy J5 (2016) Nougat 7.1.1
The phone is clearly rooted as some of the tested apps request root, which I gave.
I noticed that something is not quite alright when I open the Magisk app (see attached image)
In the image, the second part is about the App and shows the latest verion 23.0, so that looks OK.
The first part shows the value of the settings A/B, SAR, Ramdisk and the Installed version (=N/A) .
The setting Installed should show the Magisk version 23.0 instead of N/A, and that is clearly wrong.
Also, clicking the settings cogwheel (top/right) should show a long list of settings, including MagiskHide.
However, that is not the case and the options are just a few.
There is clearly something wrong with the installation of Magish.apk, but what?
So, how can that be fixed?
How do I get back all the missing settings, including MagiskHide.
Help would be very much appreciated.
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"
}

DiracDeBroglie said:
Hi,
I installed Magisk.zip v23 into the system through TWRP, and Magisk.apk v23, on my Samsung Galaxy J5 (2016) Nougat 7.1.1
The phone is clearly rooted as some of the tested apps request root, which I gave.
I noticed that something is not quite alright when I open the Magisk app (see attached image)
In the image, the second part is about the App and shows the latest verion 23.0, so that looks OK.
The first part shows the value of the settings A/B, SAR, Ramdisk and the Installed version (=N/A) .
The setting Installed should show the Magisk version 23.0 instead of N/A, and that is clearly wrong.
Also, clicking the settings cogwheel (top/right) should show a long list of settings, including MagiskHide.
However, that is not the case and the options are just a few.
There is clearly something wrong with the installation of Magish.apk, but what?
So, how can that be fixed?
How do I get back all the missing settings, including MagiskHide.
Help would be very much appreciated.
thanks
View attachment 5416439
Click to expand...
Click to collapse
Search for kdragon safety net fix

John Wu, the main contributor to Magisk, now works for Google in their Android Platform Security department. So now his job is to prevent MagiskHide to work, and now it seems he removed it from Magisk.

@DiracDeBroglie since your Magisk app doesn't recognise that you have Magisk installed, none of the options you're mentioning will be available.
First thing I would check is if the Magisk app is installed to the internal storage. If it isn't, things won't work correctly.
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed

Revolver said:
John Wu, the main contributor to Magisk, now works for Google in their Android Platform Security department. So now his job is to prevent MagiskHide to work, and now it seems he removed it from Magisk.
Click to expand...
Click to collapse
But that will have no effect on Magisk v23, that the OP is talking about. And, if you take a quick peek on GitHub and the commits over the past month (or follow the conversations in the general Magisk thread) you'll see that MagiskHide still exists, but in the new form of the deny list. Exactly how that'll work will have to wait until John releases the next Canary.

toolhas4degrees said:
Search for kdragon safety net fix
Click to expand...
Click to collapse
OP has a device from 2016. I very much doubt that it uses hardware backed key attestation... Besides, that has nothing to do with the described issue.

Didgeridoohan said:
OP has a device from 2016. I very much doubt that it uses hardware backed key attestation... Besides, that has nothing to do with the described issue.
Click to expand...
Click to collapse
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....

toolhas4degrees said:
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....
Click to expand...
Click to collapse
The latest release of USNF (currently v2.1.1) adds back a few of the props that MagiskHide currently changes, apart from disabling hardwarebacked key attestation. That is not relevant for the OP, since Magisk v23 still has all of that. The issue here is something else...
And it sounds like you're talking about the unofficial Alpha Magisk releases rather than the SafetyNet Fix, since the latter doesn't include anything that has to do with the soon to be removed modules repo.

Thanks for the reply.
I unstalled Magisk with uninstall.zip. That worked fine, rootchecker said that root was gone and banking and ID apps were working again.
Then I installed Magisk.zip again through TWRP, and that went well too.
Following reboot there was some sort of little Magisk app in the app folder (see first image). I double clicked it and it installed the full version of Magisk app (13MB), also that went well.
But the problem persists as before with Magisk app, that is: Installed=N/A and the important Settings, like Magiskhide and the Modules part, are missing, which means btw that Universal SafetyNet Fix cannot be installed anyhow.
My device is from 2016 (design 2015), so I have very strong doubts my device supports any hardware-backed attestation.
The Magisk core elements work flawlessly, Root Checker shows root, root apps like VPN hotspot work fine, and the banking and ID apps .... well, they detected root and refuse to continue working. So root is clearly OK.
Somehow the Magisk app in the user/data partition does not/cannot communicate with the Magisk core elements (sitting in the boot ramdisk I presume).
So, is there any app, tool or software to analyze, study or have a closer look at the communication between the app and the core elements?
If this doesn't work out with v23, then I won't have much of a choice but to install lower versions, v22, v21, ... until I come across a version that works, but that is really my last resort as my preference is v23.
Any suggestions ....

Didgeridoohan said:
The latest release of USNF (currently v2.1.1) adds back a few of the props that MagiskHide currently changes, apart from disabling hardwarebacked key attestation. That is not relevant for the OP, since Magisk v23 still has all of that. The issue here is something else...
And it sounds like you're talking about the unofficial Alpha Magisk releases rather than the SafetyNet Fix, since the latter doesn't include anything that has to do with the soon to be removed modules repo.
Click to expand...
Click to collapse

DiracDeBroglie said:
Thanks for the reply.
I unstalled Magisk with uninstall.zip. That worked fine, rootchecker said that root was gone and banking and ID apps were working again.
Then I installed Magisk.zip again through TWRP, and that went well too.
Following reboot there was some sort of little Magisk app in the app folder (see first image). I double clicked it and it installed the full version of Magisk app (13MB), also that went well.
But the problem persists as before with Magisk app, that is: Installed=N/A and the important Settings, like Magiskhide and the Modules part, are missing, which means btw that Universal SafetyNet Fix cannot be installed anyhow.
My device is from 2016 (design 2015), so I have very strong doubts my device supports any hardware-backed attestation.
The Magisk core elements work flawlessly, Root Checker shows root, root apps like VPN hotspot work fine, and the banking and ID apps .... well, they detected root and refuse to continue working. So root is clearly OK.
Somehow the Magisk app in the user/data partition does not/cannot communicate with the Magisk core elements (sitting in the boot ramdisk I presume).
So, is there any app, tool or software to analyze, study or have a closer look at the communication between the app and the core elements?
If this doesn't work out with v23, then I won't have much of a choice but to install lower versions, v22, v21, ... until I come across a version that works, but that is really my last resort as my preference is v23.
Any suggestions ....
Click to expand...
Click to collapse
Did you check if the app has been installed to external/adoptable storage? That would cause this exact behaviour...
Also, did you previously have Magisk installed with the app repackaged with a random name? If so, that app might still be present and could be the source of your problem. If so, you can uninstall that app and try again (but you might also have to uninstall and reinstall the regular Magisk app as well).
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_apps

@toolhas4degrees I'm not sure what you mean by that screenshot, but it just shows exactly the same thing I was talking about in the post you quoted.

Didgeridoohan said:
Did you check if the app has been installed to external/adoptable storage? That would cause this exact behaviour...
Also, did you previously have Magisk installed with the app repackaged with a random name? If so, that app might still be present and could be the source of your problem. If so, you can uninstall that app and try again (but you might also have to uninstall and reinstall the regular Magisk app as well).
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_apps
Click to expand...
Click to collapse
No, at the last install there was not any external SD card present.
No, never installed Magisk under any another name, neither did I try to hide it or so.
However, ... I did install the app Magisk.apk first a few days ago at first contact with Magisk, and then later I installed Magisk.zip through TWRP while there was an external SD present. So, .... maybe there is some remnant code laying around in the system.
I could uninstall.zip Magisk again and then look for remnants in the system and delete those. If there are any remnant left, those should probably have "magisk" in their name. Do you have any idea where to look for Magisk remnants after uninstallation?
Remember the device is a Samsung Galaxy J5 (2016) and I am not all too sure if Odin is really the most handy tool to look for code remnants. I got ADB and Fastboot installed that I used before for testing my Asus tablets. Also Terminal in TWRP I can use. If I only knew what exactly and where to look for the stuff ....

Here is an update.
As my device is still rooted by Magisk I checked out the filesystem starting from root with Solid Explorer File Manager (SE).
I found folders and files from Magisk in /root/data/adb/magisk (folder), /root/data/adb/modules (empty folder) and the file /root/data/adb/magisk.db
I uninstalled Magisk by installing uninstall.zip (from Magisk.zip) through TWRP.
And as SE needs root, I installed SuperSU-v2.82-SR5.zip through TWRP, which then worked fine.
With SE I removed magisk.db and any magisk folder at /root/data/adb/
Next thing I did was to remove, uninstall and unroot SuperSU through its own settings.
But after having clean-installed Magisk.zip again from TWRP, having installed the Magisk app using the Magisk preinstaller app in the apps folder and rebooting the device a few times, the problem hasn't gone!
And so the Magisk app pane still shows Installed = N/A, and MagiskHide, Modules and the other options are also still missing from Settings.
Any suggestions for a next move would be welcome.
thanks

DiracDeBroglie said:
installed the Magisk app using the Magisk preinstaller app in the apps folder
Click to expand...
Click to collapse
What does this mean? What's a preinstaller?

Didgeridoohan said:
What does this mean? What's a preinstaller?
Click to expand...
Click to collapse
If one performs a clean installation of Magisk.zip -- so there is no Magisk on the phone anywhere -- through TWRP, not only the core elements are installed, but also in the /data part some little Magisk app is installed that shows up in the apps folder, which I call a (pre)installer. See first image #9. Double clicking that will install the full Magisk app in the user or /data part.
So all looks ok during the installation, and rooting definitely works, but that annoying problem just persists.
I would be glad to hear any suggestions...

Ah... Now I get it. It sounded like you were using some custom unofficial stuff, and that would definitely have been a possible source of issues.
I have no suggestions, but you haven't posted any Magisk log, have you? Might be a good idea, to see if anything shows up in there. First it would be good if you could install the Canary release though, since it has more verbose logging.

Didgeridoohan said:
Ah... Now I get it. It sounded like you were using some custom unofficial stuff, and that would definitely have been a possible source of issues.
I have no suggestions, but you haven't posted any Magisk log, have you? Might be a good idea, to see if anything shows up in there. First it would be good if you could install the Canary release though, since it has more verbose logging.
Click to expand...
Click to collapse
I just had a look for those log files but couldn't find any. Any idea where to look for? In /root/data/adb/ there are no log files.

DiracDeBroglie said:
I just had a look for those log files but couldn't find any. Any idea where to look for? In /root/data/adb/ there are no log files.
Click to expand...
Click to collapse
The Magisk log is in /cache.

Didgeridoohan said:
The Magisk log is in /cache.
Click to expand...
Click to collapse
So this is what I have in the log.
01-05 19:43:01.276 262 262 I : Magisk 23.0(23000) daemon started
01-05 19:43:01.281 262 262 I : * Device API level: 25
01-05 19:43:01.296 262 264 I : ** post-fs-data mode running
01-05 19:43:01.297 262 264 I : * Mounting mirrors
01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/system
01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/data
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/cache
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/persist
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/vendor
01-05 19:43:01.299 262 264 I : * Initializing Magisk environment
01-05 19:43:02.901 262 264 I : * Running post-fs-data.d scripts
01-05 19:43:02.906 262 264 I : * Running module post-fs-data scripts
01-05 19:43:02.906 262 264 I : * Loading modules
01-05 19:43:07.207 262 538 I : ** late_start service mode running
01-05 20:43:07.209 262 538 I : * Running service.d scripts
01-05 20:43:07.227 262 538 I : * Running module service scripts
09-25 19:09:50.969 262 2470 I : ** boot_complete triggered
09-25 19:31:29.395 262 12576 W : su: request rejected (10166)
09-25 19:31:41.551 262 12618 W : su: request rejected (10166)
09-25 19:31:53.716 262 12667 W : su: request rejected (10166)
09-25 19:32:05.877 262 12707 W : su: request rejected (10166)

What is the go-to replacement for MagiskHide & the central module repo?

I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!

KaoDome said:
I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!
Click to expand...
Click to collapse
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Here. First 5 post and you should know all you need

So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?

Quantumrabbit said:
So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?
Click to expand...
Click to collapse
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.
Click to expand...
Click to collapse

Porpet said:
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
Click to expand...
Click to collapse
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you

Quantumrabbit said:
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you
Click to expand...
Click to collapse
And where did you find the deny list?

fusk said:
And where did you find the deny list?
Click to expand...
Click to collapse
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist

H
toolhas4degrees said:
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist
Click to expand...
Click to collapse
How to add modules shamiko & how to more hide features

Spartacus500 said:
H
How to add modules shamiko & how to more hide features
Click to expand...
Click to collapse
Shamiko is a flashable only need to slash magisk module. You can find it in the magisk alpha thread on telegram. You need to configure denylist first and reboot then turn off the enforce denylist toggle and flash the shamiko module.
If you are using lsposed download hide my applist xposed module and search how to use it if you want more coverage
Pm me if you want links

I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.

Drakinite said:
I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
This is quite weird and definitely shows how different devices handle root detection. I a Samsung S10+ and just installed Magisk 24 with enforce DenyList earlier this week. Today I just installed Duo Mobile and it works fine. I do not have it in the DenyList, and Magisk is not hidden. I use a custom SafetyNet fix that was installed when I originally installed an AIO TWRP/Magisk/SafetyNet fix after unlocking my bootloader. I also fail SafetyNet checks.
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?

Drakinite said:
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.

danbest82 said:
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?
Click to expand...
Click to collapse
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
anonymous-bot said:
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.
Click to expand...
Click to collapse
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.

Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
Get VD Infos and use it to scan your files. You can find it on XDA.

Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
Click to expand...
Click to collapse
Hmm ok. Like I said shimako didn't work for me either. I'm not sure why Duo is still detecting root. For reference this is what is on my DenyList:
Drakinite said:
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
YASNAC is the replacement for Momo it looks like since Momo is Riru based (https://github.com/canyie/Riru-MomoHider)

simplydat said:
Get VD Infos and use use to scan your files. You can find it in XDA
Click to expand...
Click to collapse
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?

Drakinite said:
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?
Click to expand...
Click to collapse
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.

Drakinite said:
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.
Click to expand...
Click to collapse
Awesome. Hope it stays that way!

Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!

antivirtel said:
Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!
Click to expand...
Click to collapse
Version 24102 would be v24.102. So your Magisk 24.300 is newer.

Magisk don't give superuser acess

Summary: I didn't know that magisk don't allow any app with superuser access to access some parts of the system.
{
"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"
}
(For example here is the error given by Root Essentials)
(I also had problems trying to install BusyBox)
Because I used to root old devices, with SuperSU or something else (And I didn't have any problems). And by coincidence all the attempts to access the superuser that I had made were trying to access some protected part of the system. This made me want to learn more about Android and here some workarounds for this:
For BusyBox error I just changed the install location and it works fine, to change apps install location (Move user app to system) you can use systemizer module on magisk (Using Lucky Patcher module bricked my phone )

Neither screenshot of install looks abnormal...second one is 100% correct, you'd already patched the boot image when you installed it via TWRP.....
ROM? Stock or other?
Can you install a terminal app and try:
su
do you get a prompt or error?
this would also have been better posted in this thread, more (and more experienced) eyes would see it:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
also for now ignore the detection stuff.....theres modules and settings to work around that

73sydney said:
Neither screenshot of install looks abnormal...second one is 100% correct, you'd already patched the boot image when you installed it via TWRP.....
ROM? Stock or other?
Can you install a terminal app and try:
su
do you get a prompt or error?
this would also have been better posted in this thread, more (and more experienced) eyes would see it:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
also for now ignore the detection stuff.....theres modules and settings to work around that
Click to expand...
Click to collapse
I'm using the stock ROM (Android 11)
When I try "su" on terminal magisk prompts a popup to allow it to use superuser rights

Just to confirm that I've done everything right on Magisk install.
1 - Unlock phone bootloader
2 - Install TWRP
3 - Download Magisk APK from GitHub
4 - Change .APK extension to .ZIP and put it into a SD card
5 - Open TWRP, go to install, select zip and flash
6 - Wipe dalvik cache before reboot
7 - Open Magisk installer and let it install Magisk manager

apparently i managed to uninstall appbox with luckypatcher, That's weird because when I try to move an app to system it shows this error

Adrrrrien said:
I'm using the stock ROM (Android 11)
When I try "su" on terminal magisk prompts a popup to allow it to use superuser rights
Click to expand...
Click to collapse
congrats you have a correctly rooted device, thats what should happen, it confirms what i saw in the install pictures, you have a correctly working magisk install. if youre lookign to do soemthign specific once rooted and youre haivong issues, thats an entirely different thing. The basics are working.
also you wont be able to directly write to system because thats not normal either on a system as root device/ROM, to do anything on /system, you need to use magisk modules...thats in part why magisk exists...
you dont have any problems i can see here
now if you plan to use banking or other root senstive apps, you will probably want to:
- toggle Zygisk on in Magisk Manager
- rename the magisk manager app (to *partially* hide it)
- install displaxs USNF fix from here via magisk manager: https://github.com/Displax/safetynet-fix/releases
- put the device in airplane mode
- clear data for Google Play Services and Google Play Store
- reboot
- take device off airplane mode
this will/should get you passing the Integrity Check, and from there on its what you need to use while rooted that would determine what if anything you need to install and use to hide root better, and what module you might want to use to do other things that rely on modifying system
Gentle second (and hopefully last) reminder, this is best handled by NOT creating your own thread, but by posting in this thread where fa rmore people will see it and be able to help, and where all this info is already available, meaning i neednt have typed this because its already repeated there every few days....which is way more than is needed already
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Be aware that by creating you own topic instead of reading existing ones, you are creating unnecessary work for people like me....but since youre new here im giving you a pass....very few get one

73sydney said:
congrats you have a correctly rooted device, thats what should happen, it confirms what i saw in the install pictures, you have a correctly working magisk install. if youre lookign to do soemthign specific once rooted and youre haivong issues, thats an entirely different thing. The basics are working.
also you wont be able to directly write to system because thats not normal either on a system as root device/ROM, to do anything on /system, you need to use magisk modules...thats in part why magisk exists...
you dont have any problems i can see here
now if you plan to use banking or other root senstive apps, you will probably want to:
- toggle Zygisk on in Magisk Manager
- rename the magisk manager app (to *partially* hide it)
- install displaxs USNF fix from here via magisk manager: https://github.com/Displax/safetynet-fix/releases
- put the device in airplane mode
- clear data for Google Play Services and Google Play Store
- reboot
- take device off airplane mode
this will/should get you passing the Integrity Check, and from there on its what you need to use while rooted that would determine what if anything you need to install and use to hide root better, and what module you might want to use to do other things that rely on modifying system
Gentle second (and hopefully last) reminder, this is best handled by NOT creating your own thread, but by posting in this thread where fa rmore people will see it and be able to help, adn where all thsi info is already available, meaning i neednt have typed this because its already repeated there every few days....which is way more than is needed already
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Be aware that by creating you own topic instead of reading existing ones, you are creating unnecessary work for people like me....but since youre new here im giving you a pass....very few get one
Click to expand...
Click to collapse
Thanks, you are right, any app that does not require to change /system works fine, I just don't realized because my principal goal from installing Magisk was delete system apps or something related. and sorry for the duplicate topic, I'm kinda newbie here

Adrrrrien said:
Thanks, you are right, any app that does not require to change /system works fine, I just don't realized because my principal goal from installing Magisk was delete system apps or something related. and sorry for the duplicate topic, I'm kinda newbie here
Click to expand...
Click to collapse
thats okay, i knew you were new, if you were hoping/trying to debloat/remove system/vendor apps, then i would recommend @zgfg 's debloater module here, its replaces the app you want to debloat/remove with a dummy app, its what i use - there is another, older module, but its not maintained... and has issues. This will achieve what you were hoping/trying to do directly on /system
Magisk Module Systemless Debloater
Magisk Module Systemless Debloater Download: https://github.com/zgfg/SystemlessDebloater https://github.com/Magisk-Modules-Alt-Repo/SystemlessDebloater Wiki pages by @ipdev: https://github.com/mModule/guide_sDebloater/wiki/ConfigScript with his...
forum.xda-developers.com
the beauty of magisk modules is that they are (largely, if written properly) reversible, so disabling/uninstalling reverts the changes.