Database Develop

Losing root after some time, Magisk v11 + MagiskSU

pretty much title.
sometimes i lose root twice a day, sometime 3day without lose, reboot/reflash magisk fix it

Same here
Enviado de meu LG-D295 usando Tapatalk

Just experienced the same issue. After installing some modules and rebooting

I am experiencing the same thing.. but when or how I don't know... I just take reboot and again root will be back. Might be some other app like clean master or auto killing apps kills magisk services???

I had the issue too, but it stopped when I disabled MagiskHide. That of course is only a solution if you don't actually need it.
Not being an expert, I never found a way to debug the issue or contribute otherwise.

I can confirme. Also when MagiskHide is on, I experience random reboots, which is bigger problem. Any fix for it?

Karls0 said:
I can confirme. Also when MagiskHide is on, I experience random reboots, which is bigger problem. Any fix for it?
Click to expand...
Click to collapse
Just a thought: have you added any system apps/processes to the Hide list?

No, i didn't. I don't use android pay, and i don't think that hiding root may be necessary for any other system app. When I turn MagishHide I have maybe 1 min before reboot. All was fine first few hours after installation, before first root losing.
If it will help, I'm on AOSP 6.0 custom ROM. My device is i9505. What's interesting it happens only if mobile data is on. Wi-fi doesn't do any troubles.

I will throw my experience into this thread as well. I am running Magisk 11.1 with DarkRom on my Nexus 5. Everything seems to work very smooth outside of randomly loosing root. I don't have to reflash, just reboot and it comes back. I do have MagiskHide enable for Android Pay. I also have the AppSystemizer model installed to covert Action Launcher 3 to systems. No random reboots, but loosing root is annoying. I may try to disable MagiskHide and see if that solves the root drop issue. Android Pay is handy though.

Ok Folks my 2 cents in regards to this trouble, i have did some work in reproducing this Magisk Root Loss.
say i have few apps like 1) SafetyNet Sample: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en & 2) RootChekerPro app and both these apps are hided them from root using MagiskHide.
So when i launch Magisk Manager app and checked safetynet Status and then opened app1 (safetynet Sample) ran the test and then immediately did Forcestop the Magisk manager app and launched back Magisk Manager app boom the root is lost and did a reboot everything is back fine again.

I've been trying to find the cause of this issue for a couple of weeks. This is what works for me so far
1. Open Magisk Manager when root is working (either immediately after rebooting or after disabling Magisk Hide).
2. Does Magisk BusyBox and Magisk Hide.
3. Reboot
4. Enable Magisk Hide, but keep Magisk BusyBox disabled.
5. Reboot
Check if root disappears anymore.

I think Magisk Hide is causing the issue, disabled the Magisk Hide and the root stays.

It may also be releated with GApps package - it could explain why some people have this issue with losing root/stability but others no. You can try with smaller package (picko/nano).

Magisk 11.5 seems to fix the issue for me

craigacgomez said:
Magisk 11.5 seems to fix the issue for me
Click to expand...
Click to collapse
No, it's just randomly occurring.
I was having the same problem with 11.1 and flashed the 11.5. It doesn't fixed.
Then flashed the ROM and 11.1 again the root is still there.
I don't know what exactly triggers the root to hide but there is something going on.

works on first flash of 11.1, then the next reboot breaks it again. uninstalling and reinstalling magisk fixes it again until the next reboot

I switch on MagiskHide only when I need it. So far it's quite good option, doesn't require any reboots.

did more testing, I don't lose root at all when I have MagiskHide disabled. Deleting /magisk/.core/magiskhide in recovery returns root.

Mostly a "me too" post. Issue still occurs on 11.6.

I tried replacing MagiskSU with SuperSU. But still the issue remains.

OP3T Freedom OS + Snapchat?

Hey fellow xda-users.
After some time on Marshmallow (Sultans Rom), I've decided to step into the world of Freedom OS (for a variety of reasons) and it just came to my mind Snapchat nowadays scans for root. Since SU is included in the OS, I have to bypass this somehow. If i perform a backup using Titanium, will I be able to restore it and stay logged in?

Snapchat uses SafetyNet and you can easily bypass SafetyNet on FreedomOS.
At one point in the Aroma installer, the installer will ask you which SU you want, Make sure you select MagiskSU.
After you're done and boot into FreedomOS, go to apps and open Magisk Manager, then go to its settings and enable Magisk Hide then go back to the Status screen and press "Tap to start SafetyNet check" and you should pass it.
Once you pass SafetyNet check you can install Snapchat and it'll work just fine.

Mizart said:
Snapchat uses SafetyNet and you can easily bypass SafetyNet on FreedomOS.
At one point in the Aroma installer, the installer will ask you which SU you want, Make sure you select MagiskSU.
After you're done and boot into FreedomOS, go to apps and open Magisk Manager, then go to its settings and enable Magisk Hide then go back to the Status screen and press "Tap to start SafetyNet check" and you should pass it.
Once you pass SafetyNet check you can install Snapchat and it'll work just fine.
Click to expand...
Click to collapse
Thanks a lot for the detailed answer!

AquulTech said:
Thanks a lot for the detailed answer!
Click to expand...
Click to collapse
No Problemo!

I cant get safetynet to pass no matter what I do.

I have a Galaxy S4 on Optimised CM14.1. I used the magisk that came with the ROM. I got safetynet to pass once, and have never been able to get it again.
Any help is appreciated!

BeastMode6 said:
I have a Galaxy S4 on Optimised CM14.1. I used the magisk that came with the ROM. I got safetynet to pass once, and have never been able to get it again.
Any help is appreciated!
Click to expand...
Click to collapse
Check to see if selinux is set to "Permissive", safetynet will fail if it detects a kernel with selinux set to permissive. To check this in the terminal type "getenforce" if it says "permissive", you can type "su" to get a root shell then type "setenforce 1" to enable Enforcing. In adb you can type the same, however you need to type "adb shell" prior to accomplish the same. Once enabled safetynet should pass. To set the selinux back to permissive type "setenforce 0" in a root shell. good luck!
Sent from my SM-T813 using Tapatalk

It says it's enforcing already.

BeastMode6 said:
It says it's enforcing already.
Click to expand...
Click to collapse
OK, make sure you have magisk-hide enabled in the magisk manager settings. I think safetynet checks for root as well, so if your rooted with magisksu, then all you should need to do is enable magisk-hide. If you don't have the magisk manager you can download it from google play.

I have hide on, still fails. I've also restarted like 5 times to no effect.

Check if Hide is working on your device by adding a root checker app to the Hide list. If it can't detect root, at least we know the Hide works.
After that, check SafetyNet with an app like SafetyNet Playground or SafetyNet Helper. Do you pass basic integrity?
Lastly, please upload a Magisk log.

When I added root checker to magisk hide, it can still detect root. The root request message pop'ed up, and I hit grant. Safetynet playground fails on absolutely everything.

BeastMode6 said:
When I added root checker to magisk hide, it can still detect root. The root request message pop'ed up, and I hit grant. Safetynet playground fails on absolutely everything.
Click to expand...
Click to collapse
if all else fails you might try uninstalling and reinstalling magisk, it might get rid of any errant files that maybe lingering around. You never really know whats really lies under the hood with pre-packed ROMs.

brians018883 said:
if all else fails you might try uninstalling and reinstalling magisk, it might get rid of any errant files that maybe lingering around. You never really know whats really lies under the hood with pre-packed ROMs.
Click to expand...
Click to collapse
I've already tried that, didn't work.

BeastMode6 said:
I've already tried that, didn't work.
Click to expand...
Click to collapse
hmm ... you might try enabling core only mode, it could be conflicting magisk modules, if it that's culprit then you would need to then re-enable each module one by one until you trigger the error. It could be an init script and unrelated to magisk. My best advice is to do a backup, do a clean install of lineage os, then install magisk, and see if that works.

(Removed)

brians018883 said:
hmm ... you might try enabling core only mode, it could be conflicting magisk modules, if it that's culprit then you would need to then re-enable each module one by one until you trigger the error. It could be an init script and unrelated to magisk. My best advice is to do a backup, do a clean install of lineage os, then install magisk, and see if that works.
Click to expand...
Click to collapse
YAY core only mode seemed to have fixed it. It's passing now with core only mode and magisk hide.
I've made an interesting discovery. When I go to magisk hide and try to enable hide for the google play store, it now no longer passes safety net (cts mismatch) until I reboot.

BeastMode6 said:
YAY core only mode seemed to have fixed it. It's passing now with core only mode and magisk hide.
I've made an interesting discovery. When I go to magisk hide and try to enable hide for the google play store, it now no longer passes safety net (cts mismatch) until I reboot.
Click to expand...
Click to collapse
good, glad you made some progress!
Best not to hide google play store, magisk hide by default hides safety net, blocking the store may screw with google play services.
Oh since you are on a cm/lineage based rom and to save you some headaches, avoid turning on magisk's busybox implementation, since cm roms use toybox a more enhanced version of busybox it confuses the OS by overlaying the busybox binaries over toybox's binaries and magisk eventually loses root until you do reboot, not mention makes the system sluggish and almost unusable. I learned that the hard way.
Happy Tweaking!

Xposed causes Snapchat to temporarily lock account?

I have a Samsung Galaxy S6 SM-G920W8 with the UlTiMaTe NouGaT S8+ Full Port V3.1 ROM. I am rooted with Magisk V18.0, and have Snapchat enabled in Magisk Hide. Every time I install Xposed v89.3 by topjohnwu, I get a message from Snapchat team a few hours later saying that my account is being temporarily locked for 12+ hours. Is anyone else experiencing the same issue? Is there a way to stop this? Is this caused by Xposed?

Xposed or root, i dont know but i had to say goodbye to snapchat since there is no way to get it working on rooted devices,i unroot, login, then root and after a couple of hours or maybe a day cant log in...titanium backup didnt do the trick neither, it is server syncd so they find out and block u

Yes, you have to hide root from Snapchat using Magisk Hide and uninstall Snapchat.
Then flash Xposed uninstall by flashing the uninstaller zip in recovery, reboot to system, install Snapchat and hide root from it and login, once logged in reboot to recovery, flash Xposed, reboot to system and it should work and stay working.
Repeat process in future if necessary.

Redline said:
Yes, you have to hide root from Snapchat using Magisk Hide and uninstall Snapchat.
Then flash Xposed uninstall by flashing the uninstaller zip in recovery, reboot to system, install Snapchat and hide root from it and login, once logged in reboot to recovery, flash Xposed, reboot to system and it should work and stay working.
Repeat process in future if necessary.
Click to expand...
Click to collapse
That will work for MAYBE a few days. SC scans your phone now for xposed/root and will instantly ban it. Also, it keeps your device id stored on a blacklist so you'd have to change that too. They've gotten a lot sneaker about it. You can use an app like xprivacy lua or app ops to block this reading permission but it'll probably crash SC constantly. A few guys and I are trying to spoof the reading and device id and not get it to freak out but it's a slow process

agraceful said:
That will work for MAYBE a few days. SC scans your phone now for xposed/root and will instantly ban it. Also, it keeps your device id stored on a blacklist so you'd have to change that too. They've gotten a lot sneaker about it. You can use an app like xprivacy lua or app ops to block this reading permission but it'll probably crash SC constantly. A few guys and I are trying to spoof the reading and device id and not get it to freak out but it's a slow process
Click to expand...
Click to collapse
Can't say I've ever only had it work for a few days, or only ever had it maybe work. It's worked for months now without issue.
I've also not had Snapchat "scan my phone" and I don't do anything special in that department, just regular Magisk Hide.
I've had it stop working once, months ago as I said above, and I just did the process and it started working again, no device ID change or blocking of permissions.

Redline said:
Can't say I've ever only had it work for a few days, or only ever had it maybe work. It's worked for months now without issue.
I've also not had Snapchat "scan my phone" and I don't do anything special in that department, just regular Magisk Hide.
I've had it stop working once, months ago as I said above, and I just did the process and it started working again, no device ID change or blocking of permissions.
Click to expand...
Click to collapse
If you gave sc storage permission, then yes it does scan your phone periodically. It's declared in detail, in apps like app ops. Anyway though, without anyone capturing logs of when the ban is done (I'm talking to everyone that runs a sc mod of any sort) , nobody can really come up with the exact reason for them, only make educated guesses because it seems to not be one thing related \_(•-•)_/ Happy snapping!

Seems to be that Snapchat is detecting Xposed, whether it be non-systemless up to 8.1 oreo (v90 beta-3), systemless by topjohnwu, or systemless for 7.0-9.0 (EdXposed). I used Snapchat with non-systemless Xposed by rovo89 up till a month ago when I upgraded to PIE, then I used EdXposed. My new 9.0 PIE setup worked well with SnapFreedom and EdXposed until I upgraded EdXposed and Snapchat to 10.51.0.0 when I got my first ban.
Plan for attack (haven't tried, banned on alt) to use Snapchat and Xposed (Possibly also Xposed modules?) without ban:
-Use AppCloner to rebuild the snapchat apk with minimal permissions (I have premium version). I was going to go this route, but AppCloner rebuilds com.snapchat.android to com.snapchat.androie, breaking SnapFreedom. Bare permisisons: CAMERA, MICROPHONE, and maybe LOCATION? PHONE permission will give away your IMEI and other stuff, and STORAGE may trigger Xposed detection.
-Use LuckyPatcher to deny snapchat certain perissmions, including read external storage.
This thread got me thinking: https://forum.xda-developers.com/xposed/xposed-root-snapchat-uninstall-xposed-t3909199

I am using Pixen OS android 10 on oneplus 6. I have magisk root and want to install xposed. How to prevent snapchat account lock?

Magisk Zygisk + LSPosed Zygisk = black screen after boot

Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.

i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too

rf9992003 said:
i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too
Click to expand...
Click to collapse
Exactly this, bank apps can't detect the new zygisk, at least for now, just hide magisk app, delete TWRP folder and use SNF zygisk module and the black list

hi
MisiekDP said:
Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.
Click to expand...
Click to collapse
Hello, were you able to solve this?

maycomathias93 said:
hi
Hello, were you able to solve this?
Click to expand...
Click to collapse
No. You have this same problem (phone not turning on)?

yes, the only solution in this case is to run uninstall magisk and install again without lsposed. For now use edxposed without safetynet (sorry for my google translate english)

Man, I solved this problem, going from Android 9 (custom ROM where I had the problem) to 10 (also custom ROM). I hope it helps you, greetings.