Hi,
I have this idea and I like to know your opinion:
- At time the MagiskHide is a good method for use some Apps (wallet?) when you run in Core mode. This is a great function and really works (I hope for a long time). However, when you aren't running in Core mode, for example when Xposed is enabled, if you run one of such Apps it detects the presence of the su/root. So my idea is adding to Magisk the option to "hibernate" the Apps inside the list of MagiskHide when is not running in Core mode. And when the Core mode is on, then automatically "re-enable" the App.
The objective is quite simple: Block the execution of any "sensible" Apps when the detection can be done.
What you think?
If MagiskHide doesn't work on your device unless you activate Core Only Mode there's something wrong. It might be that that's how your device works, or there might be something else...
MagiskHide works perfectly fine, when when not in Core Only Mode.
Xposed though, that's a whole different matter. There's currently no way to hide Xposed, so it is very likely that what happens when you enable Core Only Mode is that the Xposed module gets deactivated and whatever app was triggering no longer do so (since you've deactivated Xposed).
Didgeridoohan said:
If MagiskHide doesn't work on your device unless you activate Core Only Mode there's something wrong. It might be that that's how your device works, or there might be something else...
Xposed though, that's a whole different matter. There's currently no way to hide Xposed, so it is very likely that what happens when you enable Core Only Mode is that the Xposed module gets deactivated and whatever app was triggering no longer do so (since you've deactivated Xposed).
Click to expand...
Click to collapse
Hi @Didgeridoohan,
Thank you for your comment!
However, I feel you misunderstood my suggestion. Let me explain more:
In my phone (at time, with Stock ROM and a Custom kernel), I can run Magisk in both modes: CORE and FULL. Both work like a charm! However, the SafetyNET check only pass in CORE mode (with MagiskHide enabled), not in FULL mode. Obviously, this is because in the FULL mode I run Xposed and the MagiskHide doesn't work.
So, when I like to run some wallet or banking App, I need to boot in CORE mode. This is mandatory!
And when I don't like to use such Apps, then I can boot in FULL mode.
Where is the problem? When running in FULL mode all Apps that can detect su/root are "active". You can use some Xposed modules (like BootManager) for not launching them at boot. However, if the App isn't "hibernated" it can be executed at any moment. And when it's executed, at this moment it detects the root... and fails. Moreover, it not only fails, but it can send a message to the App's provider... and insert you in a blacklist. So a full blocking of the App when running in Magisk FULL mode is necessary.
My idea is a simple "auto-hibernating" of the Apps in the MagiskHide list when running in non CORE mode.
You understand now what, when and why?
manos78 said:
So, when I like to run some wallet or banking App, I need to boot in CORE mode. This is mandatory!
Click to expand...
Click to collapse
Well... Core mode isn't necessary. You should be able to simply deactivate the Xposed module.
But yeah, I get your idea. Can't say much about it though...
Didgeridoohan said:
Well... Core mode isn't necessary. You should be able to simply deactivate the Xposed module.
Click to expand...
Click to collapse
If you want to be completly sure that SafetyNET is OK, then you really need to boot in CORE mode.
So, my idea at time is:
- Include the function "reboot in Core mode" inside the Magisk Tool. The concept is simple: one flag (for example one file like /magisk/.boot_one_shot_in_core) that forces Magisk to boot in Core mode... but only one time (the file is automatically removed after the boot).
- Create a Magisk Module that "hides Apps in the MagiskHide list". This module is as well very simple: it replaces the apks of the Apps in the list by a dummy file. So, when Magisk boots in FULL (normal) mode then the module "hides" the Apps, and you can't use them. However, when Magisk boots in CORE mode, the module is overpassed and the Apps be there (not hidden).
So, the idea is quite simple: the regular boot is booting with Magisk enabled (FULL mode); and when you like to boot in CORE mode it's only one-time... so in the next reboot. And when reboot again you return to the FULL mode.
I found this is the best and simple solution to execute/hide sensible Apps that really need to have SafetyNET enabled.
What you think?
Hi,
Regarding this idea: Create a Magisk Module that "hides Apps in the MagiskHide list. Anyone interested on work on it?
The concept is quite simple: If the module is active, it hides (aka mount fake .apk) all Apps in the MagiskHide list (or in a internal list).
You like this idea?
On Android 8.0 Oreo, after enable modue XInternalSD, all the apps like Power Toggles which can control airplane mode and GPS through root all stop working.
As we know, after Android 4.2, apps only can control airplane mode through root by
Code:
su (get root permission)
settings put global airplane_mode_on 1 (Turn off Airplane mode is 0)
am broadcast -a android.intent.action.AIRPLANE_MODE --ez state false
As the same way, when XInternalSD actived, I try to active airplane mode manually by above command also failed. if XInternalSD doesn't actived, it woks well.
And this bug can easily reappear on Android Emulator(SDK 26 x86 image), I tested. And it happened on my phone (LG V20 US996). So I think it happened in all Android Oreo (xposed v90 beta3).
So that means, I can't use XInternalSD and some apps like Power Toggles to control airplane mode and GPS at the same time. And I also no idea why it cause that.
(emmmm, I guess, it seems XInternalSD cause broadcast unable sending or settings vaule unable to write)
And I also check the source code of XInternalSD and I no idea too... Just some hook of storage.
And.... Even I disabled all the features in XInternalSD (uncheck Custom path tointernal SD; uncheck full access to external sd; uncheck Enable for apps..etc; ), just make the module actived, the problem also be caused.
And...This module work fine in Android 7.1 and before. No those problem.
Anybody can help me deal with it?
Finally I found a module called XCoolDroid and it works well on Android Oreo with no that problem.
Hi folks,
I would like to use MAGISK on my Samsung "S4 active" phone, running with LineageOS 14.1. The root option is currently enabled in the developer settings and SU is working. TWRP is installed and the bootloader is unlocked. Now I would like to switch to MAGISK in order to be able to play Ingress without loosing the ability using Titanium-Backup and Viper4Android.
- Must I perform a factory reset to make MAGISK up and running?
- Must I uninstall SU before I'm trying to install MAGISK ?
- Must I disable the root option in the developer settings ?
- Other things I have to be done as prerequisite ?
Thanks
Tom
For many apps magisk hide works, but not for Cofidis app.
Things I tried:
- removed app, reboot, install and before starting the app set it in magisk hide
- hide magisk mgr
- USB debugging off
- allow OEM unlock off
- turned off developer tools
- tried magisk canary
- renamed TWRP backup folder
It seems that during install the app already detects the root.
Hello,
I have found a solution that works for me.
Uninstall Cofidis, hide the Magisk application (see in the settings), install Cofidis then erase the application data (in case Play Store has restored them), configure Cofidis in Magisk Hide.
In my opinion, the Cofidis application checks if Magisk is installed.
Tell me if this was helpful to you.
Cordially
How to delete this message?
I am running MIUI13 v13.1.22.10.24 on my xiaomi MIX4.I want to enable my root access in my security space,which user id is 999.I have set magisk multi user mode to user_independent.I reboot my phone and switch to serurity space,install magisk manager,but manager still tells me that root is not available.What should I do?
Magisk version is 68874bf5-alpha