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.
Related
Hey! First off, thank you to the creator of magisk, it's amazing and very useful
However, I can't seem to get Fire Emblem Heroes to work. OP3T on stock rom, TWRP and magisk 11.1, nothing else. Using MagiskSU for greenify and adaway and everything works. Manager says I pass the safety net check (used to give a profile mismatch but that went away after rebooting) and I've enabled magisk hide for the app, to no avail.
For what it's worth PoGo seems to be working fine.
What further info could I give you to help and where do I get it?
Thanks!!!!
pqueiro said:
Hey! First off, thank you to the creator of magisk, it's amazing and very useful
However, I can't seem to get Fire Emblem Heroes to work. OP3T on stock rom, TWRP and magisk 11.1, nothing else. Using MagiskSU for greenify and adaway and everything works. Manager says I pass the safety net check (used to give a profile mismatch but that went away after rebooting) and I've enabled magisk hide for the app, to no avail.
For what it's worth PoGo seems to be working fine.
What further info could I give you to help and where do I get it?
Thanks!!!!
Click to expand...
Click to collapse
Trying to update the game e get the message "your device isn't compatible with this version"
Rcpbarba said:
Trying to update the game e get the message "your device isn't compatible with this version"
Click to expand...
Click to collapse
I just updated from 1.0.2 to 1.1.0 and keep getting the same error message as before (the good old 803-3001).
This is supposed to be a connection error message, but it doesn't make sense -- if I hotspot off my magisk'd OP3T to a stock OPO or a stock iPad, the game works fine, so it stands to reason the connection is good.
Hence my suspicion that it's probably a SafetyNet issue (FE:H, like PoGo, uses SafetyNet -- might be a Nintendo thing). Any idea how to get around it?
Thanks!
Might be an issue where the app also relies on another app or service to find a rooted device. See this thread, the Hiding root post under "Dependencies": https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Might be an issue where the app also relies on another app or service to find a rooted device. See this thread, the Hiding root post under "Dependencies": https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Good idea. I didn't think of that, but alas, the game doesn't ask for any permissions (and none listed in settings) -- so if they do use 3rd party software to check, it doesn't show up in the permission list.
Inspired by Pocket Morty's dependency on Google Play Games, I went and installed that too (I'd removed it as a cruft-reduction exercise) to see if that was it, but it's not. Still doesn't work, same error message.
pqueiro said:
Good idea. I didn't think of that, but alas, the game doesn't ask for any permissions (and none listed in settings) -- so if they do use 3rd party software to check, it doesn't show up in the permission list.
Inspired by Pocket Morty's dependency on Google Play Games, I went and installed that too (I'd removed it as a cruft-reduction exercise) to see if that was it, but it's not. Still doesn't work, same error message.
Click to expand...
Click to collapse
Yeah, I don't think it has to be as a result of permissions (note to self: update the text)... It might also be that the app is looking for certain prop values. Both of these are hard to figure out without decompiling the apk.
Didgeridoohan said:
Yeah, I don't think it has to be as a result of permissions (note to self: update the text)... It might also be that the app is looking for certain prop values. Both of these are hard to figure out without decompiling the apk.
Click to expand...
Click to collapse
Well now, that's substantially more complicated and probably out of my league I'll have to stick to playing it on the iPad. It's not impossible, just annoying.
Thanks!
you could try on nox pc emulator too, it is working on 1.1 (i had to disable root tho)
i will try with magisk on my phone until i install the apps on LineageOS13
EDIT: @pqueiro it works on LineageOS 13 and using Magisk 11.1, without problems, so i guess can be something of the rom (i can pass the net check too, and PoGo without problems)
panchovix said:
you could try on nox pc emulator too, it is working on 1.1 (i had to disable root tho)
i will try with magisk on my phone until i install the apps on LineageOS13
EDIT: @pqueiro it works on LineageOS 13 and using Magisk 11.1, without problems, so i guess can be something of the rom (i can pass the net check too, and PoGo without problems)
Click to expand...
Click to collapse
The plot thickens. Let me check on my "playground" phone if I can replicate that.
@pqueiro
did you install the game when the Phone was already rooted?
I can replicate this issue when installing the game on already rooted devices - but if I install the game on a non-rooted device and apply magisk afterwards the game launches proper.
Create a nandroid backup, flash the rom and try to launch the game while non-rooted and see if it makes a difference for you.
Klassikal said:
@pqueiro
did you install the game when the Phone was already rooted?
I can replicate this issue when installing the game on already rooted devices - but if I install the game on a non-rooted device and apply magisk afterwards the game launches proper.
Create a nandroid backup, flash the rom and try to launch the game while non-rooted and see if it makes a difference for you.
Click to expand...
Click to collapse
FYI, tried this (took the opportunity when updating Oxygen OS) and it worked a treat! All is good. Backup > unroot > update > install > magisk all the things and it's working fine.
Thanks!
Let's bring some love to our google-phones!
[Reserved for feature meaningful content]
P.S. As of now, you may check my AFH folder with all my builds - https://www.androidfilehost.com/?w=files&flid=183895
[***Reserved***]
goodwin_c said:
Let's bring some love to our google-phones!
[Reserved for feature meaningful content]
P.S. As of now, you may check my AFH folder with all my builds - https://www.androidfilehost.com/?w=files&flid=183895
Click to expand...
Click to collapse
Where's the Magisk uninstaller for Pixel phones?
Haha called us fan boy's FML guess so..
Getting the 5min unroot like everyone else I guess.
Now that you have your own thread, any chance you'll be pushing to Git more frequently for those of use who can build it on our own?
I'd appreciate it if you could.
So the 13.3 will lose root with Magisk Hide enabled after a little bit. 13_10 (the previous version) should work, but will no longer pass Safety Net....is that the correct state of things?
skaforey said:
So the 13.3 will lose root with Magisk Hide enabled after a little bit. 13_10 (the previous version) should work, but will no longer pass Safety Net....is that the correct state of things?
Click to expand...
Click to collapse
Yes. Fix is on it's way. Hope i can publish it tomorrow.
admiralspeedy said:
Now that you have your own thread, any chance you'll be pushing to Git more frequently for those of use who can build it on our own?
I'd appreciate it if you could.
Click to expand...
Click to collapse
I'm trying my best. But it is pain in ass to merge official commits with my work. Sometimes it's hard to find time even to prepare new build. But i'll try to update github more offten
DodoGTA said:
Where's the Magisk uninstaller for Pixel phones?
Click to expand...
Click to collapse
It's second in my todo list. First i have to fix Hide crashes and installation issue (somehow magisk.img is not created properly on fresh installs). So, after that, i'll work on uninstall script
skaforey said:
So the 13.3 will lose root with Magisk Hide enabled after a little bit. 13_10 (the previous version) should work, but will no longer pass Safety Net....is that the correct state of things?
Click to expand...
Click to collapse
There's a temporary fix for 13_10 but it won't survive a reboot
Sent from my Pixel XL using Tapatalk
Soooperstar said:
There's a temporary fix for 13_10 but it won't survive a reboot
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'm using a Tasker profile to keep this working for the time being. If it's cool, I could create an apk in a few hours that will do the same thing.
raynan said:
I'm using a Tasker profile to keep this working for the time being. If it's cool, I could create an apk in a few hours that will do the same thing.
Click to expand...
Click to collapse
Yea that would be cool
Sent from my Pixel XL using Tapatalk
I thought you could place a file in the /magisk/.core/service.d/ folder (with 755 permissions) that gets ran on startup to do the same thing?
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Looks like my last local build of 13.3 is working solid (finally!), but i forgot my usb cable at office, so can't debug why creation of magisk.img fails during flashing.
So, for now i'm uploading build without fixed install step. Check my AFH!
p.s. new package is Magisk-v13.3-Pixel-b1.zip
getting "magisk image mount failed" with 13.3 and 13.3-b1 on my Pixel XL. Do I need to be on the latest bootloader? I'm using April's at the moment. I just freshly installed Lineage by invisblek
jkashuba07 said:
getting "magisk image mount failed" with 13.3 and 13.3-b1 on my Pixel XL. Do I need to be on the latest bootloader? I'm using April's at the moment. I just freshly installed Lineage by invisblek
Click to expand...
Click to collapse
This is known issue if you are installing latest build and before you had no Magisk. You can wait day or two until i will fix this, or you can use workaround: install Magisk v13 (new10 suffix) and after that install latest 13.3-b1
apologies for dbl reply. i didnt catch your post goodwin.
p.s. thx for all your hard work.
Installed 13.3-b1 with no issue. Root present and working, but SafetyNet is failing (was working previously under 13.3). I tried rebooting, but this did not help. This does not require a new apk, does it?
skaforey said:
Installed 13.3-b1 with no issue. Root present and working, but SafetyNet is failing (was working previously under 13.3). I tried rebooting, but this did not help. This does not require a new apk, does it?
Click to expand...
Click to collapse
try to re-enable Magisk Hide and wait minute or two to give it to settle
P.S. Next release will come with uninstall script
goodwin_c said:
try to re-enable Magisk Hide and wait minute or two to give it to settle
P.S. Next release will come with uninstall script
Click to expand...
Click to collapse
I disabled it, then re-enabled it, then rebooted, and it didn't fix it.....do i need to reboot after I disable it?
Google Pay has stopped working over a week ago and i was hoping for a fix but nothing has come? Did I do something wrong?
Running Android 6.1.6 Magisk Manager
Edit
There is also a bug with the manager? When i select apps for Magisk Hide it doesn't save and when i reload the list all that apps are unticked again??
Thanks in advance
Logs?
Didgeridoohan said:
Logs?
Click to expand...
Click to collapse
Magisk doesn't show any logs, where do I go to turn on Android logging?
JoshuaM765 said:
Magisk doesn't show any logs, where do I go to turn on Android logging?
Click to expand...
Click to collapse
There's your problem...
MagiskHide uses Android logging to detect when it needs to hide from an app or process.
Have you disabled logd? Used something like Kernel Adiutor to disable logs? Etc... Turn it back on and things will start working again.
[HIDE[/HIDE]
Didgeridoohan said:
There's your problem...
MagiskHide uses Android logging to detect when it needs to hide from an app or process.
Have you disabled log's? Used something like Kernel Adiutor to disable logs? Etc... Turn it back on and things will start working again.
Click to expand...
Click to collapse
I don't ever remember disabling logs or using a kernel adiutor. Would I need to edit to turn it on and how would I go about doing this?
Just to confirm, run this in a terminal emulator:
Code:
su -c magiskhide --enable
If it reports that logs are disabled, we can keep on this track.
The question is what happened "over a week ago" that caused things to change. Did you by any chance update Magisk? From v15.4 there was a change that for some devices wrongly disables MagiskHide because it can't detect that Android logging is running. That's been fixed and should be in the next release. You could try the unofficial snapshots by @kantjer, if you're impatient... Just be aware that they might not be built from release ready code.
Didgeridoohan said:
Just to confirm, run this in a terminal emulator:
Code:
su -c magiskhide --enable
If it reports that logs are disabled, we can keep on this track.
The question is what happened "over a week ago" that caused things to change. Did you by any chance update Magisk? From v15.4 there was a change that for some devices wrongly disables MagiskHide because it can't detect that Android logging is running. That's been fixed and should be in the next release. You could try the unofficial snapshots by @kantjer, if you're impatient... Just be aware that they might not be built from release ready code.
Click to expand...
Click to collapse
It was working then I got Xposed for Magisk but that put it in a boot loop so i factory reset and rerooted with Magisk and its now stopped working. When I do the terminal emulator i get "Logb is not running, cannot run logcat"
JoshuaM765 said:
It was working then I got Xposed for Magisk but that put it in a boot loop so i factory reset and rerooted with Magisk and its now stopped working. When I do the terminal emulator i get "Logb is not running, cannot run logcat"
Click to expand...
Click to collapse
Is logcat running? You can test this by using an app like Matlog. If it shows the log, it is a matter of the Magisk v15.4+ bug of detecting logging fully. Solution in that case would be to wait for the next release, test an unofficial snapshot linked above, or revert to a Magisk version prior to v15.4.
Didgeridoohan said:
Is logcat running? You can test this by using an app like Matlog. If it shows the log, it is a matter of the Magisk v15.4+ bug of detecting logging fully. Solution in that case would be to wait for the next release, test an unofficial snapshot linked above, or revert to a Magisk version prior to v15.4.
Click to expand...
Click to collapse
Yes Matlog works, where would i get an unoffical snapshot from?
JoshuaM765 said:
Yes Matlog works, where would i get an unoffical snapshot from?
Click to expand...
Click to collapse
I linked it a few posts ago...
Oh, sorry missed those.
Thanks for all the help, i will report back if it works.
Thanks so much, it was solved using the custom Magisk update link that you posted, Thanks again
JoshuaM765 said:
Thanks so much, it was solved using the custom Magisk update link that you posted, Thanks again
Click to expand...
Click to collapse
Thank you. That's the first confirmation I've seen of anyone with this issue having things working with the current code. That means the fix works...
Next official release (likely a beta) will have the fix included.
I'm also having trouble getting Google pay to work. The app also automatically gets disabled by my phone, and i have to search for it in the play store to re enable it. Magiskhide is enabled. Might it be because I'm in Mexico right now?
basily said:
I'm also having trouble getting Google pay to work. The app also automatically gets disabled by my phone, and i have to search for it in the play store to re enable it. Magiskhide is enabled. Might it be because I'm in Mexico right now?
Click to expand...
Click to collapse
Kindly Do The Following
- Clear Data&Cache Of Google Pay
- Disable Telephone Permission Of Google Play Services
- Try To Use Google Pay
Dreamer(3MF) said:
Kindly Do The Following
- Clear Data&Cache Of Google Pay
- Disable Telephone Permission Of Google Play Services
- Try To Use Google Pay
Click to expand...
Click to collapse
Thanks for the advice, but i tried it and same result.
basily said:
Thanks for the advice, but i tried it and same result.
Click to expand...
Click to collapse
Send The Full Logcat Of Google Pay & Inform Me About The Installed Version Of Magisk.
Didgeridoohan said:
Just to confirm, run this in a terminal emulator:
Code:
su -c magiskhide --enable
If it reports that logs are disabled, we can keep on this track.
The question is what happened "over a week ago" that caused things to change. Did you by any chance update Magisk? From v15.4 there was a change that for some devices wrongly disables MagiskHide because it can't detect that Android logging is running. That's been fixed and should be in the next release. You could try the unofficial snapshots by @kantjer, if you're impatient... Just be aware that they might not be built from release ready code.
Click to expand...
Click to collapse
I have the same issue as my Google Pay doesn't work now (after 16.3). Now I am on magisk 16.4.
I tried this Terminal command, su -c magiskhide --enable which returns that hide is already enabled.
My Google Pay was working normal now not working. By the way, SafetyNet test pass through.
smohanv said:
I have the same issue as my Google Pay doesn't work now (after 16.3). Now I am on magisk 16.4.
I tried this Terminal command, su -c magiskhide --enable which returns that hide is already enabled.
My Google Pay was working normal now not working. By the way, SafetyNet test pass through.
Click to expand...
Click to collapse
If you have MagiskHide working (passing SafetyNet), there's no need to mess with the enable command. That was just to confirm if the user has an issue where Magisk couldn't detect if logging was running (that's been fixed in v16.4).
Does Google Pay still work on Magisk v16.0? Or is it a matter of an update to Google Pay? What happens if you disable Telephone permissions for Google Play Services (like users of the Tez app have to do)? Or If you add all phone services you the Hide list?
Dreamer(3MF) said:
Send The Full Logcat Of Google Pay & Inform Me About The Installed Version Of Magisk.
Click to expand...
Click to collapse
Ok, I'm trying to get a logcat using terminal, but it keeps coming out at over 1mb, and xda won't let me attach a text file over 512kb. Shall i get it with adb with some filtering? I'm not very familiar with logcats, so your suggestion would be welcome.
I'm on the latest stable magisk: v16.0. For safetynet check, it successes, but ctsProfile, and basicIntegrity false.
I'm on a Nexus 6P, fully updated.
Does anyone know how can I hide the root from Random Dice?
Im getting detected on my rooted xiaomi so I had to download bluestacks to contact the support (the only way to contact them is from the game).
What I've tryed:
- Updated magisk to 20.4 & Magisk Manager to 7.5.1
- Checked the game in magisk hide
- Renamed magisk
I even asked the support of the game itself
(can't post links, had to split it )
https://
gyazo.com/877390260da6af57370f6f59b53773b2
Somehow they knew I was on bluestacks soo probs I'd better not use that anymore...
As far as I can see Magisk has no issues hiding from the app. If the app is detecting Bluestacks though, and you are using it, that's not something that Magisk can help with.
Didgeridoohan said:
As far as I can see Magisk has no issues hiding from the app. If the app is detecting Bluestacks though, and you are using it, that's not something that Magisk can help with.
Click to expand...
Click to collapse
Yes, sorry I should have explained better, Im getting detected on my rooted xiaomi so I had to download bluestacks to contact the support (the only way to contact them is from the game).
sapu98 said:
Yes, sorry I should have explained better, Im getting detected on my rooted xiaomi so I had to download bluestacks to contact the support (the only way to contact them is from the game).
Click to expand...
Click to collapse
When does the game detect root? I tested and without adding the app to the Hide list I got an error 666 at start and the app closed down. But, with the app on the list and with the Manager hidden I could start it without issue.
This was tested on a OnePlus 3T, Android 9, with Canary build 20409 and hidden Manager 284.
More hiding tips can be found here: https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Didgeridoohan said:
When does the game detect root? I tested and without adding the app to the Hide list I got an error 666 at start and the app closed down. But, with the app on the list and with the Manager hidden I could start it without issue.
This was tested on a OnePlus 3T, Android 9, with Canary build 20409 and hidden Manager 284.
More hiding tips can be found here: https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
I get this error as soon as i launch the app
https://imgur.com/a/RUBpGiA
The first time I installed the game (about a month ago), I also had that 666 error and fixed it with magisk hide, but now im getting this.
sapu98 said:
I get this error as soon as i launch the app
https://
gyazo.com/877390260da6af57370f6f59b53773b2
The first time I installed the game (about a month ago), I also had that 666 error and fixed it with magisk hide, but now im getting this.
Click to expand...
Click to collapse
That's the same link you posted in the OP...
Sounds like the app is detecting something else than Magisk then (stuff that Magisk can't hide). You can find info about that in the link I posted above.
Didgeridoohan said:
That's the same link you posted in the OP...
Sounds like the app is detecting something else than Magisk then (stuff that Magisk can't hide). You can find info about that in the link I posted above.
Click to expand...
Click to collapse
fail, sorry ahah https://imgur.com/a/RUBpGiA
sapu98 said:
fail, sorry ahah https://imgur.com/a/RUBpGiA
Click to expand...
Click to collapse
If none of the things in my link works, that message might mean that they've simply blocked you. You've contacted them, sure, but since you did that through Bluestacks they might think that's the issue. You probably need to keep talking to them for a possible unblock.
Hi, im running Android 10 with OneUI 2.5 rooted by Magisk v.21 on my Samsung Galaxy NOTE 10 Lite,
Root is working correctly, i have root access for donated FDE.AI, X-Plore file manager and etc..
Im using few Magisk modules, like Viper4Android and they works well too.
But, any atempt to download or install Magisk module from its own online reposirory ends with "Error downloading file", and atempt to check SafetyNet status gives me "SafetyNet API error" afzer hiting Ok to download SafetyNet API...
I searched on google, and here on the forum for similar problems, but i found topics from 2017 year (outdated)
Can anyone hp me solve this prob please?
Both those issues (module download error and SafetyNet API error) suggest that there are Internet connection problems.
There's been a couple of similar reports, but those have usually been fixed by clearing data for, or reinstalling the Manager.
Also make sure that you don't have any firewall rules or similar that might be restricting internet access for the Manager.
Thx for respone. I tried to delete Managers cache and App data too, nothing changes. I also tried to reinstall App, but no change.
About internet connection, yesterday I had to downgrade Magisk from v.21 beta to v.20.4 stable for unexpected random reboots 5times a day.. I done that in Magisk Manager App, selecting "Direct install (recommended)". Magisk downloaded necessery files without any problem and flashed it.
And, i dont use any third party security apps (antivirus, firevall).
So, any idea? After downgrade magisk reboots solved, here reported issue no.
No idea. A logcat might show what's up:
https://www.didgeridoohan.com/magisk/MagiskHelp
Heres my logcat, filters: level error, keyword magisj
Heres my new logcat, printed at error level verbose, filtered by keyword magisk.
I see only one problem, file permission (write permission), but where magisk wont write? Im able seriously give 777 permissions to this folder ?
Or did anybody see anything else?..
For now, nothing changes in my phone configuration.. FW version the same as in 1. Post, magisk v 20.4, actual stable magisk manager.. I also tried canary magisk manager, but the canary version wont load module list and crashed down at all, including UI.
KubikMichal5 said:
Heres my new logcat, printed at error level verbose, filtered by keyword magisk.
I see only one problem, file permission (write permission), but where magisk wont write? Im able seriously give 777 permissions to this folder
Or did anybody see anything else?..
For now, nothing changes in my phone configuration.. FW version the same as in 1. Post, magisk v 20.4, actual stable magisk manager.. I also tried canary magisk manager, but the canary version wont load module list and crashed down at all, including UI.
Click to expand...
Click to collapse
I have not had any opportunity to look at your log (and the new one won't download since it seems like the XDA attachments server is acting up again, good thing there's a new one on the way).
But, that the Canary Manager will crash when you try to access the modules list is yet another sign that your issue is that the Manager cannot get an internet connection (that's a currently known bug).
Thx u for your time . So, its known bug, but is there some way to solve it and get magisk manager functional? Or its not a global issue and its not specific to each user
It's a known issue that the Manager will crash when you enter the modules download section without an internet connection. It's not a common issue that the Manager can't get a connection at all.
I still suspect that there's something on your device that is blocking internet access for the Manager somehow.
Have the same problem.Magisk Manager 8.0.2 on Android 9,Magisk is working fine,but i become no update info for modules and i cant download any module,but 3 days ago all was ok,weird.
I think, that is not any app blocking magisk internet connection. The last stable mahisk manager dont have any problem to load online module list, and download of magisk core is aleays possible, as install ing core too....
But, i dont have time right now for test it, it is possible to reboot to safe mode and there run magisk?
I still cant understand that some app blocking magisk internet connection...
Look at my screenshot of magisk manager latest stable version, the connection working, magisk showing modules wich got updated today......
Sorry, but i still hope, that magisk manager do not have internet connection error, in screen, he knows about the module updated version, but it still wont download..
Im ready for N770FXXU6CTJ2 update, im going to flash it right now... Im confused of magisk support,
Is that last one with the Stable or Canary Manager? There seems to be something weird going on, and there have been some similar reports.
I suggest that you switch over to Canary again (Magisk and Manager) and grab a verbose logcat when you have connection issues. Upload that to a new GitHub issue where you also make sure to give all possible details as to what works and don't work on the stable Manager contra what works and doesn't work on the Canary Manager.
That way, better eyes than mine might be able to take a look at it and see if there is indeed something going on.
Nevermind... See below.
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Ok... Nice to know I wasn't wrong. :good:
Sad to see that app being used...
KubikMichal5 said:
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Click to expand...
Click to collapse
Awesome,hughe thanx,works for me.Cheers!!!
KubikMichal5 said:
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Click to expand...
Click to collapse
Life saver! It solved my problem too. Huge thanks!
KubikMichal5 said:
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Click to expand...
Click to collapse
Thanks!!!!
I'm having an issue also with passing safetynet on Razer Phone 2 (Cheryl 2). Rooted with Magisk 22.1 and TWRP arter Kernel. Had a rough time getting the "new" all-in-one Magisk installed properly. I'm using adfree for an adblocker. I've cleared the hosts file and rebooted MANY times, to no avail. Thinking I may need to uninstall Magisk and go back to 20.4 and install the old Magisk Mgr. app. Any help would be appreciated. If you need log files, let me know. I DO have root as Ti Backup, ROM Toolbox, adfree all have root access.