Database Develop

Losing root after a while?!

Hello folks!
I have a weird problem with my rooted OPX 3.1.3. I'm still using this version because Xposed is not yet officially supported with the november patch (last time I checked, it was being tested).
I haven't been able to successfully hide supersu and Xposed with Chainfire's SuperSU (even tough I think it's very good!). So, instead, I'm using PHH's SuperSU 266-2 with Magisk v9 (and Xposed 86.6). As expected, I can use Android Pay (by hiding it with Magisk Hide functionality), but after a while, I lose the root access... I don't know what to do to cause the problem, I just know it happens. So, I can't give you a step-by-step to reproduce it, which makes it more difficult to diagnose.
A reboot "fix" this, but it's kind of annoying. As this happened to someone else? What could cause this kind of problem?
Thanks and let me know if you need more info!

Remove magisk manager from greenfy-like apps, close the androidpay app after using anf if possible keep magisk manager opened worked for me

My setup is SuperSU 2.78 SR4, suhide, magisk v9, rootswitch 1.3.3.2 and PoGo and Android Pay works. I used the ramdisk patch. Root is never lost.

gamer765 said:
My setup is SuperSU 2.78 SR4, suhide, magisk v9, rootswitch 1.3.3.2 and PoGo and Android Pay works. I used the ramdisk patch. Root is never lost.
Click to expand...
Click to collapse
Um magisk thosent do anything in that case as supersu is independent from it and su hide is the only thing doing anything in that case

Majesty00 said:
Hello folks!
I have a weird problem with my rooted OPX 3.1.3. I'm still using this version because Xposed is not yet officially supported with the november patch (last time I checked, it was being tested).
I haven't been able to successfully hide supersu and Xposed with Chainfire's SuperSU (even tough I think it's very good!). So, instead, I'm using PHH's SuperSU 266-2 with Magisk v9 (and Xposed 86.6). As expected, I can use Android Pay (by hiding it with Magisk Hide functionality), but after a while, I lose the root access... I don't know what to do to cause the problem, I just know it happens. So, I can't give you a step-by-step to reproduce it, which makes it more difficult to diagnose.
A reboot "fix" this, but it's kind of annoying. As this happened to someone else? What could cause this kind of problem?
Thanks and let me know if you need more info!
Click to expand...
Click to collapse
The "losing root" problem with Magisk Hide is known and under investigation. I saw someone claiming that they didn't experience it anymore after doing a complete uninstall of Magisk and starting over. Otherwise, the only solution at the moment is to reboot the device or disable Magisk Hide.

Xmaster24 said:
Um magisk thosent do anything in that case as supersu is independent from it and su hide is the only thing doing anything in that case
Click to expand...
Click to collapse
I'm giving him an alternative that works where he doesn't lose root spontaneously and need to reboot to fix.

gamer765 said:
I'm giving him an alternative that works where he doesn't lose root spontaneously and need to reboot to fix.
Click to expand...
Click to collapse
But magisk in your alternative those nothing it's completely inactive, he would only find magisk useful if he was using another module but not xposed as superSU plus systemless xposed always leads to SN fail

Majesty00 said:
Hello folks!
I have a weird problem with my rooted OPX 3.1.3. I'm still using this version because Xposed is not yet officially supported with the november patch (last time I checked, it was being tested).
I haven't been able to successfully hide supersu and Xposed with Chainfire's SuperSU (even tough I think it's very good!). So, instead, I'm using PHH's SuperSU 266-2 with Magisk v9 (and Xposed 86.6). As expected, I can use Android Pay (by hiding it with Magisk Hide functionality), but after a while, I lose the root access... I don't know what to do to cause the problem, I just know it happens. So, I can't give you a step-by-step to reproduce it, which makes it more difficult to diagnose.
A reboot "fix" this, but it's kind of annoying. As this happened to someone else? What could cause this kind of problem?
Thanks and let me know if you need more info!
Click to expand...
Click to collapse
+1
I have same issue. I randomly loose root and I have no idea why. I hope someone can help.
I also will try to disable the magisk hide and see if it helps.

FlintStoned- said:
+1
I have same issue. I randomly loose root and I have no idea why. I hope someone can help.
I also will try to disable the magisk hide and see if it helps.
Click to expand...
Click to collapse
I am having the same problem, but am not using the Magisk hide feature. Have to reboot to restore root - very annoying!

I disabled battery optimization on magisk and super user so we'll see if these fixes it or not.
Edit: as long as magisk hide is on this doesn't seem to help. It's a bug with magisk hide apparently.

I have noticed this twice, and it seems to be related to having the phone die from low battery? This is the only common condition I can recognize with the last two times it has happened.

Revenge282 said:
I have noticed this twice, and it seems to be related to having the phone die from low battery? This is the only common condition I can recognize with the last two times it has happened.
Click to expand...
Click to collapse
This happens to my phone and it's not died from having low battery.

Link_of_Hyrule said:
This happens to my phone and it's not died from having low battery.
Click to expand...
Click to collapse
Yeah, I let it die last night with Magisk Hide off, so that certainly seems to be the issue. I kept root and other modules after I turned it back on.
But even with Magisk Hide on, I never experienced any issues unless the phone died. I had rebooted it a ton of times and never lost any modules. I'm convinced that it has something to do with a "ungraceful" reboot situation and how Magisk Hide must unload itself.

Maybe that's an issue as well but my phone if I pick it up after it's been sitting there and charging or a good amount of battery and try to use root it says there isn't root unless I restart.

The same issue with Magisk hide on Xiaomi Redmi Note 3 Pro
Sent from my Xiaomi Redmi Note 3 using XDA Labs

Started experiencing this on Nexus 6p stock NMF26F. Predominantly happening overnight.

tzortst said:
Started experiencing this on Nexus 6p stock NMF26F. Predominantly happening overnight.
Click to expand...
Click to collapse
Also facing this problem on Nexus 6 (nougat 7.0.1).
In addition to this, when ROOT is lost, Magisk Log is empty.
It happens whatever the day/hour... it just seems to happen after a few hours without using the phone.
- Phone never dead due to battery empty
- android pay DISABLED
- PokemonGO not installed
- Android installed from a Factory Image (november patch NBD91P)
- Magisk V9 + phh_root_r266-2 (the only module)
- magisk hide ENABLED + magisk busybox DISABLED + systemless hosts ENABLED
- greenify installed, but neither Magisk Manager nor SuperSU in the greenified applications

lebaud07 said:
Also facing this problem on Nexus 6 (nougat 7.0.1).
In addition to this, when ROOT is lost, Magisk Log is empty.
It happens whatever the day/hour... it just seems to happen after a few hours without using the phone.
- Phone never dead due to battery empty
- android pay DISABLED
- PokemonGO not installed
- Android installed from a Factory Image (november patch NBD91P)
- Magisk V9 + phh_root_r266-2 (the only module)
- magisk hide ENABLED + magisk busybox DISABLED + systemless hosts ENABLED
- greenify installed, but neither Magisk Manager nor SuperSU in the greenified applications
Click to expand...
Click to collapse
Magisk log is empty because the Magisk Manager can't access the cache folder where it's located (no root, remember ).
It's a known bug, probably due to Magisk Hide being a little too aggressive.

I've noticed that I lose root every time I open Magisk Manager, so I've decided to hide it from to app drawer & have Greenified it in an attempt to stop it from running at all after initial boot - will report back if it works or not.
Edit: so I rebooted and haven't opened the Magisk Manager app since last boot and haven't lost root yet, so, so far so good. (15hrs 30m uptime) - will update if I do.
Edit2: haven't lost root in 2 days now, so looks like a temporary fix?

enabling Magiskhide caused me to lose root

Pixel 3 XL - Root goes away when using "Hide Magisk Manager"

Hello All,
I'm running the latest november patch. I'm running into issues when using "Hide Magisk Manager". After reboot, a second Magisk Manager is installed. This causes neither Magisk Manager to load and also causes root to no longer work.
So far the only way to fix this is to uninstall both magisk manager packages. Uninstall Magisk from Recovery and then Reinstalling.
This is needed to play Pokemon Go.
Thanks,
O

I am also experiencing the same issue. Pixel 3 XL, root via TWRP, reboot to system, launch Magisk Manager, click on repackage magisk, end up with two apps, one completely nonfunctional and the other working, but using the regular magisk package name.
---------- Post added at 07:41 AM ---------- Previous post was at 06:43 AM ----------
Just wanted to provide a quick update, while googling for the issue I believe it may be related to this
https://forum.xda-developers.com/showpost.php?p=77340171&postcount=26376
---------- Post added at 07:52 AM ---------- Previous post was at 07:41 AM ----------
Another quick update, I followed their steps, and it works to maintain root of the repackaged magisk; however, upon reboot root is lost as somehow another copy of magisk shows up installed (i presume from where i repackaged the first one). It seems at though magisk manager keeps overwriting the magisk.db with one that doesn't have the info of the new repackaged app.

Does anyone know if this is fixed in 17.4? If so, we can use 17.4 until it's fixed in beta branch.
Thanks @yourmghq for finding the post and workaround. I'm trying it now.

The canary build is working for me, however, someone noted that they were having problems. In either case the way I got it working with canary was updated to the custom url in magisk manager, installed the apk for the new magisk manager, downloaded the canary magisk zip, rebooted to recovery, reflashed magisk and I reflashed the kernel I am using just for thoroughness, and rebooted and it worked for me.

xomikronx said:
Does anyone know if this is fixed in 17.4? If so, we can use 17.4 until it's fixed in beta branch.
Thanks @yourmghq for finding the post and workaround. I'm trying it now.
Click to expand...
Click to collapse
Did you get it to work? I am having the same issue here.

there is currently a work around if you want to use it with 17.3. Follow this guide here: https://forum.xda-developers.com/showpost.php?p=77340171&postcount=26376
Must better than using Canary.

xomikronx said:
there is currently a work around if you want to use it with 17.3. Follow this guide here: https://forum.xda-developers.com/showpost.php?p=77340171&postcount=26376
Must better than using Canary.
Click to expand...
Click to collapse
What on earth makes you feel that the linked, convoluted, workaround would be better than simply installing the, currently quite stable, Canary build?

Didgeridoohan said:
What on earth makes you feel that the linked, convoluted, workaround would be better than simply installing the, currently quite stable, Canary build?
Click to expand...
Click to collapse
Because as stated by another user, the canary build has some issues/quirks at the moment.
Feel free to use whatever option works for you. The workaround is fine for me until 17.4 becomes beta.

Lost ability to use magisk canary

Curious if anyone else is running into this issue or if I'm just completely missing something but for the last month or two, I completely lost the ability to get on any canary or canary_debug build channel of magisk. I have tried everything, flashing multiple different builds of canary_debug.zip along with the canary_debug.apk's and no matter what I do the option to select canary or canary_debug under the update channel options is gone. As a result of this, as soon as I use the "hide magisk manager" feature, my magisk app reverts to the beta.apk which is the old UI and I have some random issues with that apk not displaying all my installed modules. I have completely uninstalled magisk and reinstalled, I have factory reset, I've tried stock ROMs, custom ROMs and nothing works. Someone please direct me on what I'm doing wrong, I have never ever run into this issue before in all my time using magisk.

1dopewrx05 said:
Curious if anyone else is running into this issue or if I'm just completely missing something but for the last month or two, I completely lost the ability to get on any canary or canary_debug build channel of magisk. I have tried everything, flashing multiple different builds of canary_debug.zip along with the canary_debug.apk's and no matter what I do the option to select canary or canary_debug under the update channel options is gone. As a result of this, as soon as I use the "hide magisk manager" feature, my magisk app reverts to the beta.apk which is the old UI and I have some random issues with that apk not displaying all my installed modules. I have completely uninstalled magisk and reinstalled, I have factory reset, I've tried stock ROMs, custom ROMs and nothing works. Someone please direct me on what I'm doing wrong, I have never ever run into this issue before in all my time using magisk.
Click to expand...
Click to collapse
As posted in Magisk canary forum:
Didgeridoohan
26-02-2020, 12:35 AM
Not having the Canary channel in the Manager settings is a bug, of course (it's a Canary release after all). Fixed upstream, so add a custom channel and wait for a new release (no ETA, of course).
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page301

Tulsadiver said:
As posted in Magisk canary forum:
Didgeridoohan
26-02-2020, 12:35 AM
Not having the Canary channel in the Manager settings is a bug, of course (it's a Canary release after all). Fixed upstream, so add a custom channel and wait for a new release (no ETA, of course).
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page301
Click to expand...
Click to collapse
Thanks buddy, I appreciate the answer. Glad I'm not crazy. Funny thing is a few hours ago, I flashed a new rom to try out (PixelDust) and after flashing the patched boot.img I had the canary debug option back. I will add in my specific case, I didn't have Canary as the bug-report you linked states because my magisk manager was the old UI, which correct me if I'm wrong, isn't Canary. I could not get the new UI to stick, hence it switching to the beta build that was permanently selected in options.

Note9 Randomly Reboots and Partly Goes Back to a Previous State

Hey guys!
I recently flashed my Galaxy Note9 (SM-N960F, One UI 2.5) with TWRP and Magisk, all being the latest version. However my phone would just reboot randomly and I could barely find a pattern. I could only infer that the reboot is system level since most of the time I was launching a system-level app like Bixby, Torch, or just simply swipe down the notification panel. If related, 19:30 seems to be the time my phone would definitely reboot recently.
By ''partly goes back to a previous state' I mean some of my apps would be replaced to their factory version. Like I used YouTube Vanced, and after this one reboot it went back to its factory version. And Gboard was exiled of all its permissions once. My Edge Panel was reset after one boot. Some of the adb tweaks were reset.
I'm half sure this is a kernel problem, and the only modifications I did to my kernel were Magisk and Universal DM-Verity. I don't know if it's a DM-Verity problem.
I tried to disable my root permission for apps but it didn't help. Also Googled how to catch system logs but none of these worked.
If you're experiencing the same problem or have an idea of how to solve this issue please feel free to leave a comment!

Maspon said:
Hey guys!
I recently flashed my Galaxy Note9 (SM-N960F, One UI 2.5) with TWRP and Magisk, all being the latest version. However my phone would just reboot randomly and I could barely find a pattern. I could only infer that the reboot is system level since most of the time I was launching a system-level app like Bixby, Torch, or just simply swipe down the notification panel. If related, 19:30 seems to be the time my phone would definitely reboot recently.
By ''partly goes back to a previous state' I mean some of my apps would be replaced to their factory version. Like I used YouTube Vanced, and after this one reboot it went back to its factory version. And Gboard was exiled of all its permissions once. My Edge Panel was reset after one boot. Some of the adb tweaks were reset.
I'm half sure this is a kernel problem, and the only modifications I did to my kernel were Magisk and Universal DM-Verity. I don't know if it's a DM-Verity problem or I just disabled too many system apps (Galaxy Themes, Bixby Service, Galaxy Friends and stuff).
I tried to disable my root permission for apps but it didn't help. Also Googled how to catch system logs but none of these worked.
Whether you're experiencing the same problem or have an idea of how to solve this issue please feel free to leave a comment!
Click to expand...
Click to collapse
Happened to me as well few months ago.
I suspect it is related to safetynetfix or hideprop. I used safetynetfix for samsung, and update latest hideprop, now i never experienced the random reboot.

xfakexbloodx said:
Happened to me as well few months ago.
I suspect it is related to safetynetfix or hideprop. I used safetynetfix for samsung, and update latest hideprop, now i never experienced the random reboot.
Click to expand...
Click to collapse
Thanks for the reply! I just flashed Universal SafetyNet Fix. Now my phone is stuck in bootloop. It would just reboot infinitely. May I possibly get the SafetyNet Fix you're using?

Maspon said:
Thanks for the reply! I just flashed Universal SafetyNet Fix. Now my phone is stuck in bootloop. It would just reboot infinitely. May I possibly get the SafetyNet Fix you're using?
Click to expand...
Click to collapse
Based on this post
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Try to read each page, some people say it works, some people say it doesn't. I've tried and updating my magiskhide prop and it works.

xfakexbloodx said:
Based on this post
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Try to read each page, some people say it works, some people say it doesn't. I've tried and updating my magiskhide prop and it works.
Click to expand...
Click to collapse
Thanks a lot! My phone now boots normaly and it's a Success on SafetyNet. Hope no more random reboots afterwards.
I'm particularly curious what variant of DM-Verity did you use? I googled for DM-Verity for Samsung this morning and did get a Samsung-only patch. I'm not sure if DM-Verity patch could contribute to these reboots.

Maspon said:
Thanks a lot! My phone now boots normaly and it's a Success on SafetyNet. Hope no more random reboots afterwards.
I'm particularly curious what variant of DM-Verity did you use? I googled for DM-Verity for Samsung this morning and did get a Samsung-only patch. I'm not sure if DM-Verity patch could contribute to these reboots.
Click to expand...
Click to collapse
Sorry no idea about that. I'm using alexis rom though..

xfakexbloodx said:
Sorry no idea about that. I'm using alexis rom though..
Click to expand...
Click to collapse
Sadly my phone still rebooted this morning. I caught the last kernel message and I hope it will help

banking app detecting root

I got a new banking app today that detects root, its https://play.google.com/store/apps/details?id=no.vipps.bankid
no problem with the Swedish bankid or other Norwegian banking apps. google pay/wallet works.
I tried blocking it in magisk block list. then with Shamiko, I'm afraid to test too many thing since google wallet is working now.

Try this modified USNF module. The issue you may be having is the new Play Integrity API.

I tried the previous version and now this one, still the same. I'm in no hurry to fix it, all other stuff work and the old bankid solution works 2 more years I think (hope)

I'm in your exact same position.
I have the MagiskHide module and used the DenyList, I also tried Shamiko, no luck for this app.
I tried the modified USNF module and no luck either.
I have several other apps where the above methods to avoid detection are working without problems, but not this one.

In the same boat as you guys. Also tried the modified magisk delta project with the old magisk hide, no luck.
Where is this?
SafetyNet is good, all other banking-and wallet-apps is working. RootBeer is not detecting root.
Oneplus 7t pro, stock latest stable rom. Magisk delta. Hide root from all apps. Renamed magisk app.

same problem here. tried everything i could find and no luck. might be a DRM problem? because 1 other issue i cant fix is apps like Netflix and prime video which are currently unusable because of DRM.

My app was updated today, and immidiatly after the update I tried activating/logging in, and to my surprise it worked. There is a one hour grace/waiting period to activate, and I'm currently waiting for that.
If it is not working after the wait, I will update this post. So if no update, it is working.
See my previous post in this thread about my setup.

jale said:
My app was updated today, and immidiatly after the update I tried activating/logging in, and to my surprise it worked. There is a one hour grace/waiting period to activate, and I'm currently waiting for that.
If it is not working after the wait, I will update this post. So if no update, it is working.
See my previous post in this thread about my setup.
Click to expand...
Click to collapse
same for me. so its probably okay for everyone for now. disable auto update on it now hahaha and lets hope it stays that way.

Can confirm, it works now without any change to Magisk or other modules.
I waited the 1h period and after that I was able to activate it and use it to login.
I am using Shamiko and a modified USNF module, but probably are not required.

Great to know that it's working now. But, for next time i can give u guyz some more option to keep in mind:
**renaming/deleting the "twrp/fox" folder of the recovery, deleting all files related to magisk or xposed. Also, hiding developer mode option by "devoptshide" from lsposed. **