Related
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
Hi,
I'm running stock ROM with TWRP recovery.
I've managed to successfully root my Note with Magisk.
Somehow I noticed that my device loses root after a reboot and sometimes even randomly. When I go into the custom recovery and flash Magisk 14 or 14.3 everything works fine for while, till it loses root again.
Could someone shed some light on my issue, please?
Thanks in advance.
I've also themed Magisk Manager with Substratum could that be the issue?
I'm also running stock rom, losing magisk root from time to time.
When root is lost, I'm getting a notification that "new magisk V14 is available.
Reinstalling with TWRP only to lose it again a day or two later.
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Are you using the hide root feature?
If so then that is probably your issue.
opasha said:
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Click to expand...
Click to collapse
This worked for me, thank you!!
ALEXRUSS55 said:
This worked for me, thank you!!
Click to expand...
Click to collapse
Welcome :highfive:
jpasint said:
Are you using the hide root feature?
If so then that is probably your issue.
Click to expand...
Click to collapse
What issue does this cause?
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
stiffis said:
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
Click to expand...
Click to collapse
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
kenpaci said:
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
Click to expand...
Click to collapse
Looks like that worked, thanks!
stiffis said:
Looks like that worked, thanks!
Click to expand...
Click to collapse
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
webgurru said:
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
Click to expand...
Click to collapse
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
stiffis said:
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
Click to expand...
Click to collapse
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
hshah said:
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
Click to expand...
Click to collapse
Try closing those apps first, I think it goes ok as long you don't start the apps yourself because most off the apps checks root at startup, but I can't guarantee you anything
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
hshah said:
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
Click to expand...
Click to collapse
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
webgurru said:
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
Click to expand...
Click to collapse
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
hshah said:
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
Click to expand...
Click to collapse
Any luck or help from this thread to resolve?
webgurru said:
Any luck or help from this thread to resolve?
Click to expand...
Click to collapse
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
hshah said:
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
Click to expand...
Click to collapse
Thanks. In my point of view this look to be a bug in Magisk. Did you tried some older version?
I am struggling to get my m9 back to 'reasonable' battery life. I am running Viper 6.2.0 which comes with Magisk 14.0. I had updated it to 14.5 and had terrible battery (physically hot phone and battery life of about 2 hours - with a new battery). I tried updating to magisk 15.3 and SU quit working (adaware just came to a black screen and other root apps would not work) so I went back to 14.5. On the HTC forum, I was directed to try again and make sure to uninstall magisk from twrp before I installed 15.x. I had not done this before, but installed new Magisk versions over older ones. So I did try that. When I flash that full phone image from aroma (complete wipe) It complains that it cannot install Magisk 14.0 and asks to flash it separately. I happen to have a copy of 14.0 and 14.5 on my phone and can flash 14.5 from TWRP. This appears to work. But the resulting image gets hot. I restore the old boot image from the backup and try again. The only version of Magisk I can reliably flash to this image is 14.5 If I try to run the uninistaller from 1/13/2018, I get no odd messages in TWRP, but it will not boot (HTC logo appears and nothing more on both the OEM inage and Viper 6.2.0). When I install the 15.3 zip, I also get no strange messages in TWRP but the phone will not boot. I am stuck restoring from backup. What can I try?
I have restored the OEM image (installed from RUU), but I am running Magisk 14.5 on there but with 5.x Magisk Manager. In this format, SU appears to work but access needs to be granted at every boot and none of the apps show up in the list of SU enabled apps. On the SuperUser page it says 'no apps found' though the SU enabled apps do work.
A little more information. I saw this behavior before when I tried to update Magisk 14.5 to 15.3 and this was the reason I went back to 14.5. I was able to get 15.3 installed on the stock rom. Everything seems to work properly except adaware 3.2. (passes safety net, android pay seems to work, rooted apps still work). If I uninstall adaware and reinstall it, I get the same behavior. I get a black screen with a red titlebar for adaware. It appears to be requesting root access, but I never get a grant/deny dialog box. I have this behavior on both roms I have tried on the One M9 (stock and viper 6.2 based on 4.28.401.3). I just added the adblock module from TWRP and will see if the module for Magisk works for me. Thought you'd like to know. This is with stock install of HTC M9 4.30.612.12. I will post back if the phone still gets hot and burns a hole in my pocket.
https://forum.xda-developers.com/showthread.php?p=75097249#post75097249
Hi, I faced a similar problem on my OnePlus 3. Details:
Phone: OnePlus 3
ROM: Nitrogen OS Feb 6th, 2018
Magisk version: 15.3, upgraded to 16.0
Magisk Manager: 5.6.1
I had this issue since 15.3, when I upgraded to 16.0 the issue still remained. I cleared data and cache of the Magisk Manager app and that did the trick.
I can see the apps in the list, and no longer does it ask for Root Permissions for the same app repetitively.
Woo hoo. Tried this and it seems to be back! It is no longer burning a hole in my pocket. I'll run it for a few days and see if it is acceptable, but so far so good... Thanks.
Well after a week or so running this it is back burning a hole in my pocket. Light use and battery at 30% at lunch... Gotta go back to the stock rom.
Man I wish I could use this one...
keithspg said:
Well after a week or so running this it is back burning a hole in my pocket. Light use and battery at 30% at lunch... Gotta go back to the stock rom.
Man I wish I could use this one...
Click to expand...
Click to collapse
You have not shown any kind of information what it actually is that is using your battery. BetterBatteryStats, GSam, etc...
If you could provide that, someone might be able to help.
Didgeridoohan said:
You have not shown any kind of information what it actually is that is using your battery. BetterBatteryStats, GSam, etc...
If you could provide that, someone might be able to help.
Click to expand...
Click to collapse
Ok, I will try. I am running BatteryMix, currently. It does not show my anything truly useful, at least to me. It shows when my location, wifi and BT are on, but nothing stands out when I look at the programs running. It just shows a steep battery consumption curve from the moment I disconnect it from the charger in the AM. I will download BBS and see if anything becomes apparent.
My HTC HTC One M9 battery averages 1d 0h 43m (11h 15m 0s active usage) on a single charge.
This is all it says. The screen grabs show:
https://drive.google.com/file/d/11yGgYLEcxnGiVN8KWd3GTo1f_9XNdu-J/view?usp=drivesdk
https://drive.google.com/file/d/1QW1Yl2GeseVhKyFFyytWXgOkI8_rz8Zt/view?usp=drivesdk
What more information can I provide?
Running it today and the same basic info shows. Android System chewing through 50% of my battery. I can give a catlog if needed or anything else. Since 15.x of Magisk, I have had poor battery life with this ROM. With a stock rom, I do not seem to have a problem. Battery lasts much longer
(edit: I had mangled links. Fixed)
So about 6 weeks ago my 4xl froze and I forced a restart. When it booted back up it was stuck on the ”pixel is starting".
I was forced to flash the factory images and I rooted again, flashed a center clock module via magisk and was running again....until it happened again today. Any else ever have this happen?
I want root but I'm tired of this happening.
bigmatt503 said:
So about 6 weeks ago my 4xl froze and I forced a restart. When it booted back up it was stuck on the ”pixel is starting".
I was forced to flash the factory images and I rooted again, flashed a center clock module via magisk and was running again....until it happened again today. Any else ever have this happen?
I want root but I'm tired of this happening.
Click to expand...
Click to collapse
Yes, after I updated to November it happened. I was browsing google feed on the launcher. It froze then restarted to "pixel is starting". Flashing factory image without the -w didn't work, I had to wipe data. I even tried disabling all magisk modules via adb but still had to wipe data.
Interestingly, I was also using the center clock module. I've stayed away from that and haven't had a problem since.
Has anyone notified @Tulsadiver? If not he'll prolly notice this mention and chime in...
CyberpodS2 said:
Has anyone notified @Tulsadiver? If not he'll prolly notice this mention and chime in...
Click to expand...
Click to collapse
I have uploaded November updates but i run center clock and i haven't had any problems.
Tulsadiver said:
I have uploaded November updates but i run center clock and i haven't had any problems.
Click to expand...
Click to collapse
Center clock is one of my favorite mods.
Now that I think of it I was also running a couple modules to pass safetynet. Now I'm only using center clock and systemless hosts.
Thanks for chiming in
I'm starting to think it could be magisk canary. This has never happened when I was on android 10 using stable magisk. Either way I'm up and running again... rooted and still using center clock mod
I have been having a few issues lately. When I rooted my phone, I lost access to rcs messaging (like it wont let me register for it) and when I connect to a Bluetooth device it disappears from the paired list when I restart the phone. Another issue is that I no longer can see the estimated time till 100% when charging my phone. Does anyone else experience this or does anyone know how to fix it?
My kernels which I had installed are: physwizz --> carbon -> eureka -> carbon (current)
My device is rooted with magisk and the only module right now is the vipe4android module.
Any help would be appreciated.
Borkode said:
I have been having a few issues lately. When I rooted my phone, I lost access to rcs messaging (like it wont let me register for it) and when I connect to a Bluetooth device it disappears from the paired list when I restart the phone. Another issue is that I no longer can see the estimated time till 100% when charging my phone. Does anyone else experience this or does anyone know how to fix it?
My kernels which I had installed are: physwizz --> carbon -> eureka -> carbon (current)
My device is rooted with magisk and the only module right now is the vipe4android module.
Any help would be appreciated.
Click to expand...
Click to collapse
time until end of charging is not shown due to kernel. At the expense of bluetooth, it's kind of because of the firmware.
SirKosichka said:
time until end of charging is not shown due to kernel. At the expense of bluetooth, it's kind of because of the firmware.
Click to expand...
Click to collapse
I just flashed stock firmware and rooted with magisk and also installed twrp. I noticed that I am still having the bluetooth issue even tho I have a mostly stock config now.
Borkode said:
I just flashed stock firmware and rooted with magisk and also installed twrp. I noticed that I am still having the bluetooth issue even tho I have a mostly stock config now.
Click to expand...
Click to collapse
I can't help you with the problem with bluetooth
SirKosichka said:
I can't help you with the problem with bluetooth
Click to expand...
Click to collapse
Oh okay, thanks - I got to fix the issue by flashing the bluetooth library patcher module for Magisk if someone is having that issue.