Disclaimer :
1.this tutorial is based on AOSP ROM Android 10,,, some member report that this most likely not working on Android 11,, so if you on Android 11 and above, don't expect too much, but still, good luck.
2.since official magisk drop the "MagiskHide",you need to find older version of magisk canary somewhere else.
its start from some banking app still detect root after i update it, and even i hide Magisk from that banking app and hide magisk with custom pkg id ( setting > Hide the Magisk App ) the banking app still detected.
so, here is the fix
1. install magisk canary
( if you alreay hide magisk with random package ID, restore it first )
download magisk canary from here : https://github.com/topjohnwu/Magisk
{
"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"
}
2. after reinstall magisk with canary app, go to Magisk setting, and change Update Channel to Canary. and then back to Magisk Home, and install the magisk again ( not the app )
for the Option, just klick Next, and for the Method, choose Direct Install. and Reboot.
3. download Riru module from here : https://github.com/RikkaApps/Riru/releases
4. after download Riru module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru module, flash and Reboot.
5. Now, download Riru Unshare, from here : https://github.com/vvb2060/riru-unshare
6. after download Riru_Unshare.zip module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru_Unshare.zip, flash and Reboot.
Done ! open magisk and rehide the app that previously still detect root and its should be able to open as normal without Root warning.
i hope this will help you, if so, please press the thanks button, cheers.
Nope, are you 11 or 10?
Also, was told unshare already implemented in magisk
Lu5ck said:
Nope, are you 11 or 10?
Also, was told unshare already implemented in magisk
Click to expand...
Click to collapse
Iam on 10, well idk if it already implement on magisk, but even i update to latest version of magisk, the root still detected, and at this moment, using unshare is fix my problem,,, because android user is vary between OS and devices, iam sure some people will get the same problem.
not working with "STC Pay"
the only solution for now is to delete magisk app, it will appear after a reboot.
bayu elf sabayonz said:
its start from some banking app still detect root after i update it, and even i hide Magisk from that banking app and hide magisk with custom pkg id ( setting > Hide the Magisk App ) the banking app still detected.
so, here is the fix
1. install magisk canary
( if you alreay hide magisk with random package ID, restore it first )
download magisk canary from here : https://github.com/topjohnwu/MagiskView attachment 5323957
2. after reinstall magisk with canary app, go to Magisk setting, and change Update Channel to Canary. and then back to Magisk Home, and install the magisk again ( not the app )
View attachment 5323961
for the Option, just klick Next, and for the Method, choose Direct Install. and Reboot.
3. download Riru module from here : https://github.com/RikkaApps/Riru/releases
4. after download Riru module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru module, flash and Reboot.
5. Now, download Riru Unshare, from here : https://github.com/vvb2060/riru-unshare
6. after download Riru_Unshare.zip module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru_Unshare.zip, flash and Reboot.
Done ! open magisk and rehide the app that previously still detect root and its should be able to open as normal without Root warning.
i hope this will help you, if so, please press the thanks button, cheers.
Click to expand...
Click to collapse
Cheers for this, id avoided using Riru until now, but my banks latest app update wreaked havoc on my Pixel 2XL and i suddenly couldnt add my card to google Pay. The banks app detecting root and then sending false data to Google Pay when i tried to verify killed my google Pay account. Then it killed my bank account, to the point i had to order a new card.
Then i still couldnt add the new one...until i caved in and tried Riru and Riru Unshare
Once i did all the steps, and rehid Magisk, i was fine
at android 11 bank app detect root .
Bofahad said:
at android 11 bank app detect root .
Click to expand...
Click to collapse
Some ROMS can still expose root via props etc
Case in point, after my win above, i flashed a different (new) ROM and while Google Play worked fine, my bank app and Samsung pay detected root, using the same setup as above, and the exact same Migrate backup
I reverted back to the ROM i used above and had no issues again
Sometimes you just cant win
Bofahad said:
at android 11 bank app detect root .
Click to expand...
Click to collapse
Might be because the app is scanning for known root apps
You could try xprivacylua via lsposed to block app requests for that app.
You can also use "shelter" to isolate what the apps can see
You can also use "app manager" to disable the isolated service
Last but not least, many apps are not updated to work with 11 flawlessly thus some solution might fail at times
Personally, I had to run shelter but sometimes it will fail, due to where i run the app from
My run of my banking app working with the above fix ended after 3 days
Still trying to figure out why
For sure is a problem with hidding magisk on android 11 to use some bank apps. I got this here too. C6 bank's app works with magisk hide and changed magisk manager name in android 10 but with no working with this same process on android 11.
Will back to android 10 and wait for another fix or way to get it.
bayu elf sabayonz said:
its start from some banking app still detect root after i update it, and even i hide Magisk from that banking app and hide magisk with custom pkg id ( setting > Hide the Magisk App ) the banking app still detected.
so, here is the fix
1. install magisk canary
( if you alreay hide magisk with random package ID, restore it first )
download magisk canary from here : https://github.com/topjohnwu/MagiskView attachment 5323957
2. after reinstall magisk with canary app, go to Magisk setting, and change Update Channel to Canary. and then back to Magisk Home, and install the magisk again ( not the app )
View attachment 5323961
for the Option, just klick Next, and for the Method, choose Direct Install. and Reboot.
3. download Riru module from here : https://github.com/RikkaApps/Riru/releases
4. after download Riru module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru module, flash and Reboot.
5. Now, download Riru Unshare, from here : https://github.com/vvb2060/riru-unshare
6. after download Riru_Unshare.zip module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru_Unshare.zip, flash and Reboot.
Done ! open magisk and rehide the app that previously still detect root and its should be able to open as normal without Root warning.
i hope this will help you, if so, please press the thanks button, cheers.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!! I was looking for a way to get Epic Seven (game) to work and this finally fixed it.
I did add a folder named isolated to the folder they noted
GitHub - canyie/Riru-MomoHider: A Riru module tries to make Magisk more hidden.
A Riru module tries to make Magisk more hidden. Contribute to canyie/Riru-MomoHider development by creating an account on GitHub.
github.com
Note: Since 0.0.3, all features are disabled by default, you need to create a file named /data/adb/(lite_)modules/riru_momohider/config/<config name> to enable it
Config nameDescriptionisolatedApply Magisk Hide for isolated process and app zygotes. This feature is deprecated because it will unmount Magisk modified files for every isolated processes, and the unmounting time cannot be well controlled, which may cause some modules to not work. For almost apps, Magisk Alpha or the latest Magisk canary + Riru-Unshare is enough.setnsFaster new way to hide Magisk in isolated processes. Requires config "isolated" is enabled.app_zygote_magicMake a app named "Momo" cannot detect Magisk hide is running.initrcHide the modified traces of init.rc
Cryptonite26 said:
THANK YOU SO MUCH!!!! I was looking for a way to get Epic Seven (game) to work and this finally fixed it.
I did add a folder named isolated to the folder they noted
GitHub - canyie/Riru-MomoHider: A Riru module tries to make Magisk more hidden.
A Riru module tries to make Magisk more hidden. Contribute to canyie/Riru-MomoHider development by creating an account on GitHub.
github.com
Note: Since 0.0.3, all features are disabled by default, you need to create a file named /data/adb/(lite_)modules/riru_momohider/config/<config name> to enable it
Config nameDescriptionisolatedApply Magisk Hide for isolated process and app zygotes. This feature is deprecated because it will unmount Magisk modified files for every isolated processes, and the unmounting time cannot be well controlled, which may cause some modules to not work. For almost apps, Magisk Alpha or the latest Magisk canary + Riru-Unshare is enough.setnsFaster new way to hide Magisk in isolated processes. Requires config "isolated" is enabled.app_zygote_magicMake a app named "Momo" cannot detect Magisk hide is running.initrcHide the modified traces of init.rc
Click to expand...
Click to collapse
Hi can you be more specific in detailing exactly what you did pls. I'm trying to get this same game Epic Seven to work on my rooted phone.
just enable zygisk and its done .
I know its old topic, but did you use busybox of any kind? Try uninstall it. Mine was this sucker, even using shimoko didnt give good result. U
I uninstall that, BOOM! settled....
Related
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.
I am on a honor 8 running Android 7.0 and magisk v16. I Uninstalled xposed through custom recovery, didn't do anything. anyone have any ideas? when I run the SN check both ctsprofile: and basicIntegrity: show as false.
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Didgeridoohan said:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Click to expand...
Click to collapse
I have read through this, and I'm not sure if I'm missing something but I do not see anything that applies to the problem I am experiencing.
T0blerone said:
I have read through this, and I'm not sure if I'm missing something but I do not see anything that applies to the problem I am experiencing.
Click to expand...
Click to collapse
Really? There's quite a lot of tips on how to get MagiskHide to work and SafetyNet to pass in the wiki linked from that thread. What have you tried so far? And where are your logs?
Didgeridoohan said:
Really? There's quite a lot of tips on how to get MagiskHide to work and SafetyNet to pass in the wiki linked from that thread. What have you tried so far? And where are your logs?
Click to expand...
Click to collapse
I'm brand new to rooting. I rooted my first device yesterday so to be quite honest I'm kind of lost at this point. I haven't tried anything from the forum because I didn't see anything that mentioned how to get the basicIntegrity working. I saw methods that helped the other one if you have basic integrity working but I don't know how to fix that, or anything really.
T0blerone said:
I have read through this, and I'm not sure if I'm missing something but I do not see anything that applies to the problem I am experiencing.
Click to expand...
Click to collapse
Kindly Do The Following
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Install SafetyNet Helper Sample Or SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
Dreamer(3MF) said:
Kindly Do The Following
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Install SafetyNet Helper Sample Or SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
Click to expand...
Click to collapse
I actually can't. as im so new I have less than 10 posts I'm not allowed to upload images. the root beer sample showed checks except four red x's on su binary, su exists, root native, and on root cloaking apps. SafetyNet failed with success on the request but said "fail (response payload validation failed)" and my device Certification is uncertified. hope that helps.
T0blerone said:
I actually can't. as im so new I have less than 10 posts I'm not allowed to upload images. the root beer sample showed checks except four red x's on su binary, su exists, root native, and on root cloaking apps. SafetyNet failed with success on the request but said "fail (response payload validation failed)" and my device Certification is uncertified. hope that helps.
Click to expand...
Click to collapse
For Passing The SafetyNet, Check This Post https://forum.xda-developers.com/ap...playstore-services-data-t3789498/post76682978.
Magisk-v16.4 Is Not Suitable For Most Of Us To Use Due To Many Issues So That Flash Its Replacement Magisk-v16.3.1(ThePatchedBinary) From This Link https://androidfilehost.com/?fid=962339331458996616 Or Magisk-v16.3 (Instead Of Magisk-v16.4).
T0blerone said:
I actually can't. as im so new I have less than 10 posts I'm not allowed to upload images. the root beer sample showed checks except four red x's on su binary, su exists, root native, and on root cloaking apps. SafetyNet failed with success on the request but said "fail (response payload validation failed)" and my device Certification is uncertified. hope that helps.
Click to expand...
Click to collapse
If you add the Rootbeer app to the MagiskHide list in the Manager and check again, we'll know of MagiskHide works on your device or not. With the app on the Hide list, all checkmarks should be green.
If it doesn't seem to work, the first thing to try is to toggle MagiskHide off and on in the Manager settings.
Didgeridoohan said:
If you add the Rootbeer app to the MagiskHide list in the Manager and check again, we'll know of MagiskHide works on your device or not. With the app on the Hide list, all checkmarks should be green.
If it doesn't seem to work, the first thing to try is to toggle MagiskHide off and on in the Manager settings.
Click to expand...
Click to collapse
I added it and nothing changed. I then toggled it off and on and ran the test a third time and got the same results.
T0blerone said:
I added it and nothing changed. I then toggled it off and on and ran the test a third time and got the same results.
Click to expand...
Click to collapse
Which means MagiskHide isn't working properly on your device. Or you have remnants of previous root stuff (if you were playing around with something else before flashing Magisk), or possibly stuff left over from Xposed. Have you uninstalled the Xposed Installer app?
If you can save the Magisk log to Pastebin and then post the id for that paste, we can at least take a look at that. If you then can install the beta release of Magisk (or an unofficial snapshot, since they're more up-to-date) and provide the magisk_debug.log, that would be even better.
Didgeridoohan said:
Which means MagiskHide isn't working properly on your device. Or you have remnants of previous root stuff (if you were playing around with something else before flashing Magisk), or possibly stuff left over from Xposed. Have you uninstalled the Xposed Installer app?
If you can save the Magisk log to Pastebin and then post the id for that paste, we can at least take a look at that. If you then can install the beta release of Magisk (or an unofficial snapshot, since they're more up-to-date) and provide the magisk_debug.log, that would be even better.
Click to expand...
Click to collapse
I removed the xposed installer app and the root cloaking checkmark went green.
Didgeridoohan said:
Which means MagiskHide isn't working properly on your device. Or you have remnants of previous root stuff (if you were playing around with something else before flashing Magisk), or possibly stuff left over from Xposed. Have you uninstalled the Xposed Installer app?
If you can save the Magisk log to Pastebin and then post the id for that paste, we can at least take a look at that. If you then can install the beta release of Magisk (or an unofficial snapshot, since they're more up-to-date) and provide the magisk_debug.log, that would be even better.
Click to expand...
Click to collapse
although that's green safetynet is still failed both in the magisk app and the separate safetynet test
T0blerone said:
although that's green safetynet is still failed both in the magisk app and the separate safetynet test
Click to expand...
Click to collapse
same as mine,but i use custom rom. device redmi note 2
RR, Viper, couldnt work to pass basic integrity and cts, i have tried flash safetynet fix but stillnothing
I have the same issue. But sometimes the checks fail and sometimes they dont
Same issue here
I am having the same problem. I tried everything, every possible option on the internet I could find. Managed to get "basicIntegraty: true" probably from uninstalling Xposed but I still am unable to fix "ctsProfile: false". Here are the screens from RootBeer Sample and SafetyNet:
{
"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"
}
Click to expand...
Click to collapse
Click to expand...
Click to collapse
zbysogi said:
I am having the same problem. I tried everything, every possible option on the internet I could find. Managed to get "basicIntegraty: true" probably from uninstalling Xposed but I still am unable to fix "ctsProfile: false". Here are the screens from RootBeer Sample and SafetyNet:
Click to expand...
Click to collapse
Busybox shouldn't have an impact on SafetyNet, but if you want to make sure that other apps don't defect it, uninstall the currently installed Busybox and install from the Magisk Manager instead.
For passing the CTS profile check you can use my MagiskHide Props Config module. Details here:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Didgeridoohan said:
Busybox shouldn't have an impact on SafetyNet, but if you want to make sure that other apps don't defect it, uninstall the currently installed Busybox and install from the Magisk Manager instead.
For passing the CTS profile check you can use my MagiskHide Props Config module. Details here:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
Yeah. Im in the middle of sorting out the problem with modules not working. They show up in the modules tab in Magisk but dont work :/ Thus Magisk is not working properly. I can not even change the fingerprint using the Terminal Emulator :/ cause it doesnt even recognise Magisk being installed :/
EDIT:
half a day but its sorted. Thx
T0blerone said:
I am on a honor 8 running Android 7.0 and magisk v16. I Uninstalled xposed through custom recovery, didn't do anything. anyone have any ideas? when I run the SN check both ctsprofile: and basicIntegrity: show as false.
Click to expand...
Click to collapse
You can get both to pass. Here are the steps...
1. From your magisk, install these 2 modules: Riru - Core, and Riru - EdXposed (Sandbox or Yahfa is okay]
2. Reboot your device to activate both modules.
3. Install Xposed Installer APK by DVDandroid. You can get it here: https://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
4. Reboot to activate the Xposed Installer app
5. Inside Xposed Installer app, go to downloads and install the HiddenCore Module.
6. Reboot and go back to Magisk and test the SafetyNet.
7. Boom! Everything passes now.
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:
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.