[Help] SU binary detected on magisk core mode - Magisk

Hello everybody,
I realized that on my phone the SU binary is not hidden from the magisk hide apps even with magisk core mode and root mode disabled
I did the test with rootbeer fresh and here is the result:
{
"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 have the latest version of magisk and manage, my log is nearly empty and SafetyNet is passing...
I am running a Galaxy S5 klte on official LineageOS 16 (latest version, rooted only with Magisk) and on terminal (also checked in magisk hide) when I do
Code:
which su
I have
Code:
/sbin/su
Thanks for your answers

Core Only Mode and disabling Superuser access has nothing to do with hiding Magisk... Only MagiskHide and repackaging the Manager with a random name (but you seem to have that covered).
Test the Canary debug build (possibly improved and better logs). Also take a look here for tips and tricks:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Thanks, for your answer, it seems to work with the canary version !! Do you know why this is the case ?

jojo58400 said:
Do you know why this is the case ?
Click to expand...
Click to collapse
Nope...

Related

AutoMagisk error regarding SuperSu

(Sorry for the huge pics; don't know why they're displaying like that...)
I have a Nexus 6 that's rooted via the Nexus Root Toolkit. This installed SuperSu. I wasn't able to get Android Pay working by using the popular hack of unchecking the Allow Superuser box in SuperSu, so I installed Magisk and phh SuperUser following the instructions here and here. Everything seemed to go correctly, but when I try to start AutoMagisk, I get an error about needing to remove the SuperSu Magisk Module (screenshot attached.) I did this and rebooted, but am still getting the error.
Help?
{
"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"
}
Bit late but AutoMagisk doesn't support Magisk v7 and is discontinued. Use SUHide/HideSU instead
Quinny899 said:
Bit late but AutoMagisk doesn't support Magisk v7 and is discontinued. Use SUHide/HideSU instead
Click to expand...
Click to collapse
Thanks for the reply. Am I using SuHide instead of AutoMagisk, or instead of Magisk v7?
EmmyS said:
Thanks for the reply. Am I using SuHide instead of AutoMagisk, or instead of Magisk v7?
Click to expand...
Click to collapse
v7 + SuperSU + SUhide

Magisk download didn't root my phone

Hi !
I have recently decided to root my Samsung Galaxy s7 and followed a couple of tutorials on internet. But now I have a problem. I installed via twrp magisk 12.0 and Samsung antiroot removal and... my phone isn't root at the moment. I didn't had super su installed and hadn't any permission granted... someone could help me to solve my problem ? Thank you very much ! (I run 7.0)
Did you also install the Magisk Manager? You'll find a link to download it in the release thread.
Yes I did
But when I open it says that I have the last version but nothing else
Recovery log from the installation and a Magisk log, please. The recovery log you can save after flashing, go to Advanced - Copy log. The Magisk log you can find in /cache when you're in TWRP.
Attach the two files to your post.
Here
{
"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"
}
No... You haven't installed the Magisk Manager from the release thread. That's v5+ of the Manager and it doesn't work with Magisk v12. Uninstall and install the correct Manager.

Glase and Magisk

I want to use TAP & PAY with Glase. But every time it comes, no use because Root and customROM. I have one plus one with lineage-14.1-20180503 and magisk v 16.0. SafetyNet-Test true/true. Did somebody know whats happend?
Have you tried adding Glase to the (active) Magisk Hide list (tick it in the MH list), then hiding Magisk Manager with the appropriate function (you have to repackage it from the settings? What it will do is it will create a new APK file with a random package name but same icon, content and friendly name, install it and uninstall itself. An issue I noticed with this is that you have to repeat the procedure after every Manager (not SU binary) update, but it's not hard. Try and let me know if it worked
Edit: also remember to erase Glase cache, full-restart the device and - if needed - wipe Glase data
Anyone had any luck with this? Completely removed Glase, then proceeded to repackage Magisk, reinstalled Glase, selected it on Magisk Hide (while rebooting at every step) but it still recognizes the root :/
PS: on Oneplus 6.
This is Stock ROM on my S8+
{
"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"
}
Sent from my SM-G955F using Tapatalk

Snapchat won't login after root please help

I rooted my oneplus 6t a month ago its was fine using. But suddenly mu Snapchat wont login its oh no your logjn temporarily faild please try again later. I tried so many which solution which is given by xda in past like use root switch root clock (edxoposed) even try to uninstall edxposed manager , magisk hide but none of them works help me I'm really a regular user of Snapchat help me get it back and keep my root everything works fine expect the snapchat i really need a solution of that please help
{
"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"
}
You have used the wrong XPOSED module, uninstall XPOSED and install the EdXposed Snapchat one.
Sent from my ONEPLUS A6013 using Tapatalk
I install EdXposed-YAHFA-v0.4.6.5.Justins.Fork.-release.zip tell me which module
Magisk 20.4 stable
Android 10
Riru core 19.7
I just use an older version. I think I'm on 10.68. You lose some features but you can still snap
10.68 snapchat same problem still can't pass the login process
Reply please anyone

Whe magisk models turned off. After restart

매지스크 모듈 설치 후 시작하고 확인해보면 대부분의 모듈이 꺼져있는데... 작동안되는 모듈이라서 그런가요? 아니면 빌드할 때마다 다시 켜야 하나요?
Mod translation: After installing the Magisk module, start it up and check it, most of the modules are turned off... Is it because the module is not working? Or do I have to turn it back on every time I build?
{
"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 think it's because of Magisk Bootloop protector module. Something is wrong with the settings of that module which might be triggering to disable all other modules. Please check the GitHub repo of the module or post a issue there so someone can give you more info on that.
Actually sounds like bootloop protector is doing its job, one of your modules is incompatible with magisk 26. One by one activate them and restart til you find the on that trips. (if one does early I'd still check the others because it might be multiple with such a large list of modules).
실제로 bootloop 프로텍터가 작동하는 것처럼 들리는데 모듈 중 하나가 magisk 26과 호환되지 않습니다. 모듈을 하나씩 활성화하고 해당 트립을 찾을 때까지 다시 시작하십시오. (하나가 일찍 수행하는 경우 모듈 목록이 너무 많을 수 있으므로 다른 항목을 계속 확인합니다.)

Categories

Resources