Hello!
Is exist Magisk module that can disable Samsung device waking up on home button press?
Early i use Xposed module for disabling home wake up. But now i prefere do not use Xposed modules because when it enabled, Magisk cant pass SafetyNet test.
My question is: how to pass SafetyNet test and disable home button wake up at the same time?
There are no modules that will do this for you, out of the box, no. Xposed and Magisk does not work the same way (not even close)...
As a general rule: if it can't be done without Xposed, it can't be done with Magisk.
What you'd probably have to do is to manually edit system files to change the button behaviour (which should be possible) and then either just push those edited files to your system or systemlessly mount them with a Magisk Module.
Editing the files is best asked about in your device's forum and you'll find instructions on how to make a Magisk Module in the module template.
Hey!
I have a biiiiiiiiiiiiig issue over here.
I struggled to install Xposed (for Nougat) normally and even if it's installed "normally" I need to have the module (Xposed SDK 24) in magisk enabled or it will give me : "xposed is installed but not active".
Xposed Testbuild module is disabled.
I can't get Snaptools to work (Module Inactive : Activate module and reboot), and as I saw on the list of modules that are compatible with Xposed, Snapprefs isn't compatible either.
Do you have an idea of why it give us those "warnings"?
Did you resolve this issue by any chance?
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
mrspeccy said:
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
Click to expand...
Click to collapse
Thanks a lot. I have been searching for a while since I moved to use Zygisk and finally found this post.
However, do you know if there is any reliable detector about init.rc hiding? I've been using MagiskDetector. While it correctly showed that init.rc was not modified after installing your module, after a day or two it would suddenly report modified init.rc. I've read posts saying MagiskDetector is not accurate as it sometimes reports this even if magisk is not installed. I just want to make sure init.rc has been correctly hidden. Thanks.
You're welcome. My module just runs the same code as riru-momohider for hiding init.rc modficiations. The sudden detection you mention may be a false positive of MagiskDetector. Since I installed the module (under Magisk Zygisk) the security app that checks for init.rc modifications never reported "root found" again. I do not know of any other detectors for init.rc modifications.
mrspeccy said:
You're welcome. My module just runs the same code as riru-momohider for hiding init.rc modficiations. The sudden detection you mention may be a false positive of MagiskDetector. Since I installed the module (under Magisk Zygisk) the security app that checks for init.rc modifications never reported "root found" again. I do not know of any other detectors for init.rc modifications.
Click to expand...
Click to collapse
I see. Thanks for your reply.
Hi, I begin to think it is not a false positive from MagiskDetector when it shows init.rc is modified by Magisk. Because the work profile in my phone has very strong root detection logic, and I just now it detected root and wiped out my work profile automatically
While other bank apps, root checkers, and even Momo could not detect at that moment, MagiskDetector did report init.rc modified.
I saved the logs from MagiskDetector when 1) it did not report init.rc modified and 2) it reported init.rc modified and compared the details. What I found is that there is a line in the log from 2) which is not there in 1) :
svc name init.svc.mdnsd
Any idea what this service is and is it supposed to be hidden by InitRcHider?
mrspeccy said:
....The sudden detection you mention may be a false positive of MagiskDetector.......I do not know of any other detectors for init.rc modifications.
Click to expand...
Click to collapse
dohanin said:
....I begin to think it is not a false positive from MagiskDetector when it shows init.rc is modified by Magisk....What I found is that there is a line in the log from 2) which is not there in 1): svc name init.svc.mdnsd...
Click to expand...
Click to collapse
i installed the module. it didn't work on reboot. i mean, MagiskDetector app reported 'modified'. i then cleared cache and data for MagiskDetector and ran the app; it asked me to 'reboot and try', which i did. now, it says 'not modified'. thanks!
mrspeccy said:
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
Click to expand...
Click to collapse
It works, thanks.
yes, clearing data and cache of MagiskDetector sometimes work, but sometimes I had to re-install initrchider module in Magisk as well.
still puzzled on why after it worked, after a day or two, MagiskDetector would suddenly report Init.rc modified, without me changing anything or even reboot
dohanin said:
yes, clearing data and cache of MagiskDetector sometimes work, but sometimes I had to re-install initrchider module in Magisk as well.
still puzzled on why after it worked, after a day or two, MagiskDetector would suddenly report Init.rc modified, without me changing anything or even reboot
Click to expand...
Click to collapse
Apparently does this without magisk even installed which is why canyie commented that test in MagiskDetector is broken... When asked by @osm0sis if will be fixed vvb2060 said MD is deprecated / he she is working on Momo now... PW
mrspeccy said:
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
Click to expand...
Click to collapse
On Android 11+, there maybe also init.svc_debug_pid.******
need resetprop --delete init.svc_debug_pid.$1
Work this Samsung Android 8.0, 9.0 Pie ?
This module does not work on Samsung Galaxy S7 edge Custom Pie 9.0 Rom, module active and magisk detector app and momo app shows nothing hidden
Zygisk - Shamiko lastest version now includes hiding init
huskydg said:
Zygisk - Shamiko lastest version now includes hiding init
Click to expand...
Click to collapse
Magisk Detector Test still show "init.rc has been modified by Magisk". Any configue.
z1022 said:
Magisk Detector Test still show "init.rc has been modified by Magisk". Any configue.
Click to expand...
Click to collapse
Detect modified init.rc is not always correct, so i think nearly there are no app detect it
Magisk detector shows once hidden init.rc and over time shows modified. The most reliable application detecting system modifications is MOMO 4.0.1 APP, it always shows if init.rc is modified, and if not it does not.
Spartacus500 said:
Magisk detector shows once hidden init.rc and over time shows modified. The most reliable application detecting system modifications is MOMO 4.0.1 APP, it always shows if init.rc is modified, and if not it does not.
Click to expand...
Click to collapse
I use MOMO 4.0.1 APP, it shows init.rc is modified. How can I fix it ? If I have already used Shamiko and InitRChider.
z1022 said:
I use MOMO 4.0.1 APP, it shows init.rc is modified. How can I fix it ? If I have already used Shamiko and InitRChider.
Click to expand...
Click to collapse
What phone model do you have ? I have Samsung Galaxy S7 edge 9.0 Pie and on Shamiko module it doesn't hide init.rc.
Just ignore because detect init.rc not always correct. I don't use initrc hider but momo don't detect it
mrspeccy said:
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
Click to expand...
Click to collapse
Hi @mrspeccy,
is your module source somewhere public? The Module is not working on my Device (AL10 Oreo 8.0.0) so I would like to look into it. Also it seems to be a good starting point for another Module Project. Injecting custom *.rc and fstab files without editing the ramdisk image.
Cheers
NewBit
While I was testing my root on MOMO, I found it is detecting Xposed Framework when I'm hooking any LSPosed module to it. If I don't hook anything to MOMO, It says the environment is normal.
So I'm sure there are many apps that detect the Xposed Hooks/Module hooks.
My question is, How can we bypass this Xposed Hook detection by Apps?
My Device: OP6T
Magisk 24.1
Facing same issues. I'll appreciate someone to give reply to this.
This is an issue with the developer of LSPosed, and what he said in the support group was: don't use MOMO or don't use Xposed.
No mod hides Xposed from MOMO and no developer accepts complaints about MOMO unless the device has a problem
It's more in
brenosnt said:
This is an issue with the developer of LSPosed, and what he said in the support group was: don't use MOMO or don't use Xposed.
No mod hides Xposed from MOMO and no developer accepts complaints about MOMO unless the device has a problem
Click to expand...
Click to collapse
This is even more interesting
"Hide my applist" was an xposed modules I used on my lsposed which never triggered xposed hook "abnormal environment" error
However "Device ID masker lite" and "Android Faker" modules do detected xposed when I hook MOMO, and TB checker..
Lsposed dev "don't use xposed" I do not understand this, are modules not Xposed?
Ace_Cole said:
It's more in
This is even more interesting
"Hide my applist" was an xposed modules I used on my lsposed which never triggered xposed hook "abnormal environment" error
However "Device ID masker lite" and "Android Faker" modules do detected xposed when I hook MOMO, and TB checker..
Lsposed dev "don't use xposed" I do not understand this, are modules not Xposed?
Click to expand...
Click to collapse
No, unfortunately all he wants to say is that he won't do anything to hide it from Momo if the phone doesn't have a problem
brenosnt said:
No, unfortunately all he wants to say is that he won't do anything to hide it from Momo if the phone doesn't have a problem
Click to expand...
Click to collapse
Okay I get your point, but is there any way to know if other apps check for xposed hooks?
And if No
Is there any xposed manager with a fix of this issue?
Ace_Cole said:
Okay I get your point, but is there any way to know if other apps check for xposed hooks?
And if No
Is there any xposed manager with a fix of this issue?
Click to expand...
Click to collapse
I believe that LSPosed is the best option in this regard, unless you are going to use non-root modification (which I have honestly never tested).
I recommend that you try to check LSPosed module by module (deactivate them all and reactivate one by one) to see if any of them is the cause of the error, since with me it is not showing this error
brenosnt said:
I believe that LSPosed is the best option in this regard, unless you are going to use non-root modification (which I have honestly never tested).
I recommend that you try to check LSPosed module by module (deactivate them all and reactivate one by one) to see if any of them is the cause of the error, since with me it is not showing this error
Click to expand...
Click to collapse
Okay.
Well I have only 3 modules
* Hide my Applist
* Android faker
* Device ID masker lite
However MOMO works great when hooked with Hide my Applist and I get everything working "environment is normal"
But when hooked in lsposed with either Android faker
I get "xposed framework found"
Abnormal environment error
Check screenshot
Ace_Cole said:
Okay.
Well I have only 3 modules
* Hide my Applist
* Android faker
* Device ID masker lite
However MOMO works great when hooked with Hide my Applist and I get everything working "environment is normal"
But when hooked in lsposed with either Android faker
I get "xposed framework found"
Abnormal environment error
Check screenshot
Click to expand...
Click to collapse
Use HMA to hide the Xposed modules, however I'm pretty sure the two "Faker" modules are the cause. I found other reports on the web of them causing this error.
I believe there is no way to use them and succeed, but you can try using MagiskHide Props Config to do device emulation and uninstall problematic Xposed modules
brenosnt said:
Use HMA to hide the Xposed modules, however I'm pretty sure the two "Faker" modules are the cause. I found other reports on the web of them causing this error.
I believe there is no way to use them and succeed, but you can try using MagiskHide Props Config to do device emulation and uninstall problematic Xposed modules
Click to expand...
Click to collapse
I think no way really to use those 2 without getting caught in between
I so much love the Android faker because of ability to mask Mac address.. very useful, and hardware serial it can spoof.. I think no way to stay hidden from xposed for me
Ace_Cole said:
I think no way really to use those 2 without getting caught in between
I so much love the Android faker because of ability to mask Mac address.. very useful, and hardware serial it can spoof.. I think no way to stay hidden from xposed for me
Click to expand...
Click to collapse
brenosnt said:
Use HMA to hide the Xposed modules, however I'm pretty sure the two "Faker" modules are the cause. I found other reports on the web of them causing this error.
Click to expand...
Click to collapse
HMA really handles the hide of xposed modules well.
I have another tester app
TB checker, HMA hide all modules for both MOMO and TB checker and my phone got clean, even other apps
Just that I can't hook any app in Android faker without getting caught by "xposed framework found"
Ace_Cole said:
I think no way really to use those 2 without getting caught in between
I so much love the Android faker because of ability to mask Mac address.. very useful, and hardware serial it can spoof.. I think no way to stay hidden from xposed for me
Click to expand...
Click to collapse
Does your device not have MAC randomization?
There is a module called MacRandomizationEnabler that does this at Magisk level, which can be more effective (requires Android 10+)
brenosnt said:
Does your device not have MAC randomization?
There is a module called MacRandomizationEnabler that does this at Magisk level, which can be more effective (requires Android 10+)
Click to expand...
Click to collapse
I owned Xiaomi Redmi 9 with Android 10
Does that app works? I'll have to look to it
I'll try that and give feedback. Thanks