Related
Hi.
I have a HTC 10 running LineageOS 14.1. In the past 4 days I have had to re install Magisk 16.3 at least 4 times daily as it keeps uninstalling itself. I have always had this issue with Magisk but it appears to have gotten worse instead of being solved.
Any suggestions as to what I can do to improve the situation?
It's likely not uninstalling itself, but something is killing the daemon. If you figure out what (aggressive battery saving might be a culprit), it would be good...
Magisk manager tells me that "Magisk is not installed" and that version 16.3 is available to install. However when I reboot it's there again so looks like you're right. Guess I'll have to have a look for what's causing it.. Thanks.
This is happening to me on OOS open beta 6. It's not really uninstalled because all my modules are present, but root does not work and the Magisk app is gone from my apps in settings and app drawer. I have to go into recovery and reflash it. This is happening on reboots at random.
it seems after the april update on stock orea 8.0 MIA1 Xiaomi this issues has become frequant.
manan001 said:
it seems after the april update on stock orea 8.0 MIA1 Xiaomi this issues has become frequant.
Click to expand...
Click to collapse
Some users are experiencing this, and I suspect it's a MagiskHide thing. You could help investigating by doing two things:
Install a beta release (use v16.3 because of the 64-bit issue with v16.4), and provide the magisk_debug.log after Magisk "uninstalls itself". You might have to grab it from recovery, since you're loosing root.
Disable MagiskHide and let it be disabled for a while to see if the issue still occurs (to confirm if it's MagiskHide or not).
Can be caused by Greenify?
I have the same problem magisk uninstalled after installing sdw hide root & sdw mock location through xposed installer
same issue but xposed included.
LG G6 Rootet Oreo Stock debloatet Magisk 17.2. same problem. deinstalling itself
kerpert said:
Can be caused by Greenify?
Click to expand...
Click to collapse
I installed greenify and this happened......probably it is the cause
m1l4droid said:
@Didgeridoohan adding Magisk as an exception in the MIUI battery saver didn't work. Not sure what to do.
Click to expand...
Click to collapse
Me neither...
There's a relatively active GitHub issue open about this issue, but there's been nothing definitive found about it yet.
The reports about this issue are so scattered, lacking in details and undefined that it's hard to say anything either way. Some users have success if disabling MagiskHide, some not so much, etc.
Someone that is experiencing the issue need to figure out what it's about. Until then there's not much to do...
It causes because of Busybox... uninstall busybox module fixed the problem for me
Didgeridoohan said:
... but something is killing the daemon. If you figure out...
Click to expand...
Click to collapse
Definition for daemon: https://www.linux.org/threads/android-services-and-daemons.10847/
How can one figure out?
kerpert said:
Can be caused by Greenify?
Click to expand...
Click to collapse
Nope. I've uninstalled greenify and magisk stopped anyway. So it's not related to greenify.
dan60 said:
How can one figure out?
Click to expand...
Click to collapse
Possibly by saving logs at the moment the daemon is killed off. Can be tricky...
If you don't want to, or don't have the skill to figure that out, you could try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Didgeridoohan said:
If you don't want to, or don't have the skill to figure that out, you could try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Click to expand...
Click to collapse
I should probably state that the module was made using a 17 template so min magisk ver. 17. There's really no telling what's killing the daemon. Also I note in the thread if magiskd is killed manually my module doesn't work. Don't know what all that is about... I've been playing around trying to kill it off manually and restart with no success using SSH as my root access. I don't expect this to work for everyone because I don't know how their daemon is dying. For some odd reason the module works for me when my daemon dies randomly so I'm happy with that. BTW I included logging which prints time and date script detects magisk not running and if it successfully restarted. The logs located in /data/local/tmp/magiskd-helper.log. I also have .pid in /data/local/run. Create dir if non-existent and . pid should be there.
Geofferey said:
I should probably state that the module was made using a 17 template so min magisk ver. 17. There's really no telling what's killing the daemon. Also I note in the thread if magiskd is killed manually my module doesn't work. Don't know what all that is about... I've been playing around trying to kill it off manually and restart with no success using SSH as my root access. I don't expect this to work for everyone because I don't know how their daemon is dying. For some odd reason the module works for me when my daemon dies randomly so I'm happy with that. BTW I included logging which prints time and date script detects magisk not running and if it successfully restarted. The logs located in /data/local/tmp/magiskd-helper.log. I also have .pid in /data/local/run. Create dir if non-existent and . pid should be there.
Click to expand...
Click to collapse
You could let the script also dump the current logcat buffer to a file (or cyclically save logcat to a file set to a certain size) when it detects the Magisk daemon not running. Might show why it dies...
Didgeridoohan said:
... try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Click to expand...
Click to collapse
Great initiative. I installed it yesterday, but sadly my oreo moto z play got unrooted again (same as if no Magiskd-helper had been flashed). But thanks for trying to help.
dan60 said:
Great initiative. I installed it yesterday, but sadly my oreo moto z play got unrooted again (same as if no Magiskd-helper had been flashed). But thanks for trying to help.
Click to expand...
Click to collapse
When you reboot does magisk come back? Could you post output of /data/local/magiskd-helper.log? I would like to see if it even attempted.
seems to have something to do with EdXposed
toggling EdXposed, Riru or Magisk Core only mode won't help
these are the logs, caught using a module provided by EdXposed's developer, the first set was caught with Edxposed modules on, the second was off
https://mega.nz/#!MZkUiYxS!GzNamoD5OSeib53mogealxJ6axtHZQ0vZ94q2V1kK-I
Are you just trying to fix brick, or do you want to know what's causing it? If you're sure it was turning on stamina, seems like you could go to /data/data/ in recovery, and delete any folders having to do with stamina/battery, (there's an app called 'com.sonymobile.superstamina), and that should reset prefs.
(btw - haven't had a chance to look at the logs yet....)
Hi everyone,
I just rooted (my 1st root) my pixel 4 yesterday to activate the soli module as in my country it doesn't work otherwise.
Soli is now working, but some app (like Netflix) cannot be used even after installing the APK from some APK database.
After looking online I understood that this was because of the safetynet checks, which are both failed (ctsprofile and basicintegrity)
Unfortunatelly, I haven't found any thread to fix it except some old for older versions or mentioning TWRP which i didn't use.
I have only 3 modules installed: Riru Edxposed / Riru Core and MagiskHide props config (and the check of all google playservice addresses in the module)
Can someone help me on that?
Thanks !
Seems like Google started detecting EdXposed yesterday, but this can be worked around by adding some Google components to the EdXposed blacklist. Take a look on the EdXposed Github for details.
Didgeridoohan said:
Seems like Google started detecting EdXposed yesterday, but this can be worked around by adding some Google components to the EdXposed blacklist. Take a look on the EdXposed Github for details.
Click to expand...
Click to collapse
The check is now green for both, thanks
But i can't still use netflix (app will remain on the logo for ever).
I tried to rename the liboem file with a root explorer but the file is not present in the folder in system\lib\ or \lib64
frikadel said:
The check is now green for both, thanks
But i can't still use netflix (app will remain on the logo for ever).
I tried to rename the liboem file with a root explorer but the file is not present in the folder in system\lib\ or \lib64
Click to expand...
Click to collapse
Hi,
Coul you please tell me if you are on custom rom?
I am on custom and only way to pass is to use Props Module in Magisk. But the Props is not loading when Riru EdXposed is active.
Thank you,
amplatfus
I just posted this on Github, kinda curious if it helps with Google Pay. I had never heard of this module before:
Has anyone tried the Hidden Core module in EdXposed? It is passing SafetyNet for me without any blacklisting or switching modes, just install and reboot.
For posterity, I am running EdXposed YAHFA 0.4.5.1. EdXposed Manager 4.5.1 under Magisk v20.1 / Android Pie.
https://ibb.co/xLBxDDV
https://ibb.co/F6y1hcH
SmilingPerson said:
I just posted this on Github, kinda curious if it helps with Google Pay. I had never heard of this module before:
Has anyone tried the Hidden Core module in EdXposed? It is passing SafetyNet for me without any blacklisting or switching modes, just install and reboot.
For posterity, I am running EdXposed YAHFA 0.4.5.1. EdXposed Manager 4.5.1 under Magisk v20.1 / Android Pie.
https://ibb.co/xLBxDDV
https://ibb.co/F6y1hcH
Click to expand...
Click to collapse
Hi,
Tried. It is not working. Still searching.
Thanks!
amplatfus said:
Hi,
Tried. It is not working. Still searching.
Thanks!
Click to expand...
Click to collapse
Yep, I recently went from rooted stock to LineageOS 16 on my phone, and can no longer use Netflix. My rooted Android media boxes also run LOS and Netflix *does* work on them, so I am perplexed. I can run the (terrible) remote control app for my Toyota by simply hiding things in Magisk and adding it to the blacklist in EdXposed Manager, otherwise it will complain about the phone being rooted. That works, but Netflix does not.
I don't need Netflix on my daily driver telephone, so no loss, but it tells us that whatever Google is doing, it is beatable. I just don't see the common ground though, it almost seems like it is device dependant. Next time I install Netflix, I am going to face due north, chant the Canadian anthem, and touch my nose with my right index finger while clutching a rosary in my left hand. Maybe that will be the ticket.
Sent from my unknown using Tapatalk
SmilingPerson said:
I just posted this on Github, kinda curious if it helps with Google Pay. I had never heard of this module before:
Has anyone tried the Hidden Core module in EdXposed? It is passing SafetyNet for me without any blacklisting or switching modes, just install and reboot.
For posterity, I am running EdXposed YAHFA 0.4.5.1. EdXposed Manager 4.5.1 under Magisk v20.1 / Android Pie.
https://ibb.co/xLBxDDV
https://ibb.co/F6y1hcH
Click to expand...
Click to collapse
You're a great bro !! after having installed the module on EdXposed and restarted my redmi note 4x (mido) with EAX Os 6.7, both the ticks were of a magnificent green! many thanks! :victory::victory::victory:
Hi Guys,
My Pixel 2XL "magically automatically" updated itself to Android 11, so I've been forced to migrate to the Canary build of Magisk
to get root back etc.
The problem I have, is that the modules are not being 'detected' despite being installed.
EG: Active Edge Mod for Pixel, module is installed in Magisk, but the app doesn't detect the installation.
Same for other Magisk modules.
I'm hoping its something simple I need to do to detect these, I've searched, but found no definitive answer.
Anyone have any suggestions? Or can point me to more info on canary?
Thanks in Advance!
I noticed v21 has been released, so I jumped back to the stable channel and updated app to 8.0.1, but strangely still have the same issue!
Modules aren't being detected.
I get the following error when I try to run energized in terminal;
/system/bin/energized[13]: .: /sbin/ .magisk/modules/energizedprotection/system/bin/setupFiles.sh: No such file or directory
You've got two rather special modules there, so they're hardly the benchmark for if things work or not.
For Active Edge Mod you're probably better of asking for help with the developer. And judging by that error the Energized developer also need to update their module, since that path no longer exists on A11 (and it's bad practise to hardcode the path like that anyway). You could edit the energized file in the module directly, to point to the correct path (check the module thread, I'm sure someone has brought this up already).
So, in conclusion: unless there are other more "normal" modules that doesn't work there's no issue and you need to contact the developers of these two modules so that they can fix them.
Thanks @Didgeridoohan, I wasn't aware that the paths had changed. That would explain a lot...
Out of curiosity, what would you consider a "normal" module? For testing purposes..
Cheers!
Thanks @Didgeridoohan, I wasn't aware that the paths had changed. That would explain a lot...
Out of curiosity, what would you consider a "normal" module? For testing purposes..
Cheers!
I always like @osm0sis' modules. They utilise the module installer scripts very nicely and pretty much always work (and if they don't something usually has gone horribly wrong).
Well, hijack the module installer scripts nicely.
Well, I do have @osm0sis BusyBox Magisk Module installed, but I think I read a tweet that TopJohnWu was incorporating a busybox binary in Magisk..
I can see that all of my Magisk modules (except Systemless Host) has a "folder icon with an i" on it. Can't find what that means.. and I get a blank screen when i press it.
Magisk has had Busybox integrated for ages... Lately it's become more usable for scripts and modules though. It's not exposed to the rest of the system like @osm0sis module is.
The icon you're seeing is the module readme. Click that and it should open in the window that you see.
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