-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not hiding Magisk properly? #94
Comments
Recently, Fate GO began detecting the Magisk Manager much like it detects the Xposed Installer. Chances are the manager is not one of the apps explicitly hidden by ANRC, since it was never actually being detected in the past. |
Well I found a keywords list I could add to. Tried adding things like "magisk", "data/data/com.topjohnwu.magisk", "data/user/0/com.topjohnwu.magisk" and "magisk manager" I didn't seem to have any more luck than I did previously. Main problem is that its not giving me a log or error code. It just crashes so I'm not sure what reason its for. Wouldn't really be that annoyed with it not working if I could tie Fate to Google Play games and just sign in to different devices as I need/like to like I can with SIF. Instead I have to keep a transfer code on standby. Not the best insurance. Anyway to message the developers so they could possibly add that feature. |
@LoungeKatt Yeah...It's for personal use and document is not necessary. |
Well I tried redirecting /proc/mounts to a similar file I created, along with telling it to hide com.topjohnwu.magisk. Still no luck, I did finally manage to get an error, its 92. According to my googling abilities, its xposed or some other unknown reason, because it sure as hell isn't a modified apk. I'm still convinced its Magisk because I'm not sure what I'm doing wrong/differently from my tablet which still runs it fine, it even updated last night and I played it. Made a deal with the devil that as long as I can keep loging in and playing fate on the tablet, I'll buy saint quartz when I can get my hands on my sisters Motorola DROID Turbo. Which will basically be, should I say "SafetyNet". Because she never roots her phone or unlocks the bootloader. |
@T3hFyrefly After having no luck with Fate/GO, I did some testing. Lineage 2 detected Xposed with "Bypass XignCode" enabled and Remote Play (PS4) detected root with "Root Hide" enabled. Also tried various debugging steps (reinstalling the library, old injection method, etc). I have no warnings (after enabling the "Disable SELinux at Boot" option), so there is a chance it isn't hiding anything. I have heard rumors that you can rename the apps in the /data/app folder to temporarily hide without actually removing them. I am not sure if that will work for Magisk, though. |
I have the zs570kl from ASUS running the img: WW_4.12.40.1698.20161228 (Android 6.0.1)
Using ANRC v0.0.91.7 TEST 20170602
I have magisk 13.3 installed along with systemless xposed (v87 SDK23 arm64 by topjohnwu). FateGO doesn't seem to want to launch at all. I've tried all options along with regular xposed. It just crashes. I have a tablet also running 6.0.1 (Pixel C running RemixOS) and it seems to do fine with SuperSU regular Xposed and ANRC. I think it might be detecting something from Magisk.
My security patches are for October 2016
I've set Magisk Manager to also try and hide root and Magisk along with Rootcloak but it seems no matter how I try to combine or stack them it doesn't want to work.
Sorry if I gave too much info but I wanted to give as much as possible in case any of it helps.
Root Hide v2 Daemon also seems to randomly get turned off. Not sure what that is about.
On a semi related note: I expected Love Live SIF to be the game giving me tons of problems but it seems a basic hide Magisk check was more than enough to get it running.
The text was updated successfully, but these errors were encountered: