I'm on Ressurection Remix Mod, which comes with Magisk installed by default. It was working just fine before, but recently I've noticed it may have caused issues with battery drain. So I decided to remove Magisk - I ran magisk-uninstaller, which removed Magisk itself but the MagiskManager stayed. As I don't have su/root now I can't use Titanium Backup to remove it.
I was under the impression, that magisk-uninstaller should remove the manager as well.
How should I remove the manager altogether?
.wojtek said:
I'm on Ressurection Remix Mod, which comes with Magisk installed by default. It was working just fine before, but recently I've noticed it may have caused issues with battery drain. So I decided to remove Magisk - I ran magisk-uninstaller, which removed Magisk itself but the MagiskManager stayed. As I don't have su/root now I can't use Titanium Backup to remove it.
I was under the impression, that magisk-uninstaller should remove the manager as well.
How should I remove the manager altogether?
Click to expand...
Click to collapse
If the ROM creator has included the Manager as a system app (which is just stupid), the uninstall script can't remove it... You'll have to do it manually, either by re-rooting or from recovery.
I'm not sure if it's included as system app (seems so, can't uninstall, only 'disable'). I've tried running 'full uninstall' from Magisk Manager witout success.
Can I install SuperSU as root to remove Magisk Manager? Or will there be any conflict?
.wojtek said:
I'm not sure if it's included as system app (seems so, can't uninstall, only 'disable'). I've tried running 'full uninstall' from Magisk Manager witout success.
Can I install SuperSU as root to remove Magisk Manager? Or will there be any conflict?
Click to expand...
Click to collapse
If you only have the option to disable the app, it's installed as a system app (why, oh why :crying. There's nothing the Manager or Magisk uninstall zip can do about that.
If you've uninstalled Magisk otherwise (you've run the uninstall zip), there shouldn't be any conflict with another root solution. The Manager is only that, a manager for root and modules.
So, installing SuperSu and then uninstalling Manager with TitaniumBackup will eliminate it completely - correct?
Bonus questions:
* why is it a bad idea to install manager as a system app (vide your comment)?
* is it possible to only install MagiskSU (and have the superuser/su/root) without whole Magisk (I don't need modules and it seems that Magisk Manager is draining my battery - lot's of screen wakelock - totalling in 1h30m in 2h45m total time according to wakelock detector, however screen seems to be off)
Magisk is a systemless interface... Having any part of it installed to /system just grinds my gears. :laugh:
But, it's not only that, of course. The feature to hide the Manager is completely nonfunctional if the Manager is a system app and there are possibly other issues... It's perfectly possible that your issue with battery draining is caused by it. I don't even see the Manager on any battery usage list, and I've been using my device quite heavy today.
If you don't want modules and that part of Magisk, you can enable Core Only Mode, but you'll still needed the Manager for managing superuser requests.
Well, what you say about /system and being system-less totally makes sense now!
As for battery drain - calculation done by Android are weird quite often, but on the clean system it popped right at the top with the screen wakelock…
As for "Core mode" - I'm wondering what was causing the wakelocks - unfortunately I don't have currently screenshot with MagiskManager extended in WLD, which would show the information, but there were only 5 screen wakelocks. At any rate - given that the Manager itself was listed as the cause for the wakelocks (https://www.dropbox.com/s/aj0e6hj77cfwyw6/WLD_magisk.png?dl=0) I'm kinda reluctant to install it again.
It's quite possible that there is different culprit that drains my battery but I'm currently running quite bare-bone (even no gapps and I'm using NewPipe instead of YouTube application )
All I can say is that the Manager causing that kind of wakelock is very wrong. Possibly caused by having it installed as a system app (wild guess). I'd try with removing the system installed Manager and try again with a proper, clean install.
Went with superSu for the time being and will observer how it goes.
Oh fun:
https://www.dropbox.com/s/6aidw5czlrzpo93/WLD_supersu.png?dl=0
I'm... confused...
You could have some app spamming su requests. Check the superuser requests log.
After I posted I had similar though and the registry was spammed with ForceDoze every couple of minutes... so I guess instead of helping it was doing disservice Will see how it goes in the long run.
Related
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.
I'm on the S7 edge and the app worked without problem but suddenly once after restart all I get is "no stats have been collected yet", not just with bbs but gsam battery monitor.
The app also has superuser rights. What could be the issue?
I also have this issue. On Pixel 7.1.2 May 2017, everything works, but on Nexus 6P 7.1.2 May 2017,it shows "no stats have been collected yet" on the alarm page. I'm on 2.2.2.0 (not beta I think), and I tried to clear data, but no effect.
Any work around?
Same problem here. Exactly the same, and I would very much suspect the problem was caused by the new busybox updated earlier. Still try to figure out.
same prob. anyone solved this?
I'm having the same problem. I'm on Pixel 8, non root, just using it via APIs. Worked until about a month ago.
Same issue here. Was working up until a few hours ago. Now I'm getting the same message.
Me too. LeEco pro 3 with AICP 7.1.2.
I'm having same problem, zenity rr 7.1.2 on op3
same here on last android O preview, nexus 6p.
i think it started when switched from supersu to magisk root...
Same problem.
My phone is being kept awake but BBS is unable to report the Alarm stats ("No stats have been collected yet"). Was using Magisk earlier and was informed this was the reason, so switched to phh's superuser and still the same.
Do I have to use supersu for this?
How do you still "hide" root for legit apps, but still ensure BBS is able to accurately report all necessary stats?
Using a Nexus 6p with CarbonROM and Electron kernel, tried latest Magisk 13.3 and phh superuser.
Same problem here and no idea how to fix this.... Using the payed Play Store version.
Anyone make any progress on this? I get this message on the summary and partial wakelocks pages. I've tried installing as system app and tried doing the root commands from the terminal. I'm considering using the Xposed module to get batter stats.
I installed the app today, and it was working fine. I reset for an unrelated reason, and it now says "no stats have been collected yet". I've only heard good things about this app, but it doesn't seem stable if it breaks after a reset? Reinstalling the app doesn't seem to help.
I guess no love for us here. When the app works its awesome but it seems to throw this error more times than not.
I just switched from SuperSu to Magisk and flashed a custom kernel (Franco) on my OnePlus 3T with the stock OOS. I'm now seeing this "No stats have been collected yet" message.
having the same problem here, on magisk and also installed as system app. No responses?
Same here work with s4 rr magisk and xposed install and not with op5 same configuration
I'm was having the "no stats have been collected yet" on the partial wakelocks page and managed to fix it today. I'm using a Pixel XL on Stock Oreo with Magisk beta and the ElementalX kernel.
Disclaimer: I'm not an experienced Android dev, not my fault if this breaks your device, try at your own risk.
Here's what worked for me to get stats back:
Install the App Systemizer module from Magisk Manager (it's in downloads), don't reboot
Install the attached ZIP as a Magisk module, don't reboot
Systemize BetterBatteryStats with the App Systemizer companion app
Reboot
The attached ZIP is a modified version of the Privileged Permission Whitelist module template. I added all the permissions BBS requested into the XML file - feel free to inspect the ZIP and modify it for yourself if you don't need/want to give Greenify or F-Droid system permissions.
Thanks to @yochananmarqos and @stangri for writing the modules that made this possible!
kd- said:
I'm was having the "no stats have been collected yet" on the partial wakelocks page and managed to fix it today. I'm using a Pixel XL on Stock Oreo with Magisk beta and the ElementalX kernel.
Disclaimer: I'm not an experienced Android dev, not my fault if this breaks your device, try at your own risk.
Here's what worked for me to get stats back:
Install the App Systemizer module from Magisk Manager (it's in downloads), don't reboot
Install the attached ZIP as a Magisk module, don't reboot
Systemize BetterBatteryStats with the App Systemizer companion app
Reboot
The attached ZIP is a modified version of the Privileged Permission Whitelist module template. I added all the permissions BBS requested into the XML file - feel free to inspect the ZIP and modify it for yourself if you don't need/want to give Greenify or F-Droid system permissions.
Thanks to @yochananmarqos and @stangri for writing the modules that made this possible!
Click to expand...
Click to collapse
I updated my Privileged Permission Whitelist module to support the Play Store version and the XDA Edition.
yochananmarqos said:
Would you believe I didn't notice BetterBatteryStats was missing permissions? :silly: I thought it was no longer necessary as the How-to & FAQ in the main BBS thread states it does not require the system app anymore.
However, it turns out (at least on Oreo) it is still necessary. I noticed these two required permissions are not being granted:
android.permission.DUMP
android.permission.READ_LOGS
You can verify the permissions are granted (or not) by going to BBS Settings > Advanced > Install as system app.
I updated the module to support the Play Store version and the XDA Edition. Download in the OP.
@chamonix The above permissions will also need to be granted via adb for those running BBS on a non-rooted device.
Thanks to @kd- for figuring this out :good:
Click to expand...
Click to collapse
yochananmarqos said:
I updated my Privileged Permission Whitelist module to support the Play Store version and the XDA Edition.
Click to expand...
Click to collapse
Does this mean it's impossible to get BBS working on unrooted Oreo? I tried granting all these permissions via ADB and it still didn't work. Using a Sony XZ1 compact with locked bootloader.
Hi everyone,
I am using the application Raiffeisen Twint (version 1.2.16.0, https://play.google.com/store/apps/details?id=ch.raiffeisen.twint) on my Magisk's rooted Google Pixel (Android 8.0, Nov. 2017) without problems for a while, but since Magisk 14 versions, the application stopped working and the application reports that root is detected.
I have successfully updated to Magisk 14.5 (from 14.2), but root is still detected by the application, even with Magisk Hide activated for the application and the Magisk Manager package moved to a random name (could also be related to the updated application).
I have cleared the data of the application several times and it doesn't help and root is still detected by the application...
Anyone has a idea?
Thanks for your answers!
Like I said in the Magisk support thread, I can hide Magisk from that app just fine (on Magisk v14.5 beta)...
You don't happen to have any other mods that might trigger an app looking for root (like Xposed)? Can your device pass SafetyNet? Have you previously been rooted with any other root method and do you have any remnants of that left (root management apps, etc)? Do you have any apps that are known to be used for questionable purposes. By "questionable purposes" I mean getting access to paid features without paying, etc. Not necessarily that you use the app for this, but that the app might be used in such a manner... Etc, etc, etc. Every little detail might count.
Hi Didgeridoohan,
Thanks for helping me!
I do not have any mods installed in Magisk and also no Xposed. My device is passing SafetyNet!
I have performed a factory reset last week and since that I only rooted my device with Magisk 14.2, so no other rooting applications used. For details, I have unlocked bootloader, TWRP recovery installed and developer options and USB debugging activated.
My settings in Magisk are:
I have following applications installed on my device:
https://pastebin.com/pmt4jBMV
Do you see any applications with "questionable purpose"?
I get this message in the application:
Thanks a lot!
At a quick glance everything looks ok...
I did some experimenting with the other Raiffeisen apps you have installed, in case they also detect root and "tell" on you. At least one of them did detect root, but from what I could see it didn't make any difference for Twint.
I also tested installing a few of the root apps you had installed (in case the app looks for certain known apps), but that didn't make any difference either. I could still successfully hide root.
My guess is that it's something along these lines tough. That it's using another app or detecting a root app. You could start experimenting with that. Clearing data for the other Raiffeisen apps and adding them to MagiskHide and also removing root apps. Try disabling USB debugging and developer options as well (didn't make difference for me, but worth a shot).
Simple. Change name of package from settings in Magisk Manager, then MAKE SURE you add twint app to magisk hide list, then ERASE DATA of twint app, change package name once again and run twint. Working with Magisk 14.5. Screens if u want available. Or video.
Hi Didgeridoohan, Hi Mamama07,
Thanks for your help, but sadly none of your suggestions did worked... until the update of the application released yesterday, to fix problem related to rooted devices! [emoji3]
Thanks anyway again for your help! [emoji106]
I had the same problem (with BCV Twint) and after a few tries, changing Magisk Package Name worked!
Hi All,
I am experiencing issues with certain banking apps.
Starling Bank
and
Barclays
These two will not run however other banking apps do.
I have Magisk 17.1 running perfectly with Magisk hide turned on for those apps and changed the package name of Magisk manager and even tried uninstalling the manager as a test.
CTS Profile and SafteyNet are both passed and eveything else is working for all other apps.
Has anybody else had experience with these 2 apps ?
Im thinking maby they are detecting certain root applications but i have no idea how to find out which one i should try to uninstall.
Any help/advice/assistance would be greatly appreciated.
Thanks
Tried Magisk hide?
Edit: Never mind, didn't read that part. Try uninstalling Magisk completely.
Edit 1: Did you try clearing the app's data after hiding? The apps "remember" that the device is rooted.
I had tried uninstalling magisk using the uninstaller zip so i was completely unrooted and still didnt work that was also after clearing the app data and i ahve also tried uninstalling the apps then reinstalling them, because of this i think they have some root apps detection for example maby if titanium backup is installed it wont run. The problem is how do i know which apps its checking for i have lots of apps on my phone 500+ and to go through all root ones will take me ages. is there an easy way to find out ?
There is a thread here i have just found about this issue:
https://community.starlingbank.com/t/incorrect-android-root-detection/5068/246
even unrooted phones are being detected as rooted and its working for some with Magisk but not for others.
How do i go about getting the apps list that it detects as "unsafe"
Barclays vs Magisk
I have the same problem, magisk v17. 2, safetynet passes, but i cannot run absa bank (part of barclays). Anyone with a solution please?
Did you disable USB debug?
I've got them both running only with v16. On v17.1 or v17.2 only Barclycard.
Hi, first time posting to XDA and I'll try to be concise, but I am tremendously confused and quite frightful of having to reflash/factory reset my entire device.
I got Magisk 6.1.0(165) after my Xposed Framework became more of a problem than a solution a long time ago, with a basic desire of rooting my device to control what apps boot at launch and examine Wakelocks and run an ad blocker.
For a long time, I did not update after the headache of clearing Safetynet and getting things functional.
Magisk prompted me to update, and I decided to after I had installed a few new apps that I now wanted to block from running on boot, but I never got around to finding a method to prevent apps from loading at startup like I desired with Xposed, i previously just disabled or uninstalled the problematic apps.
Before updating, I used TWRP to run a backup and rebooted.
After the update, Magisk informed me that the latest version i had updated to, was not supported and that it would behave asif it wasn't installed at all... Great...
I downloaded the zip to my device's SD card, and after a reboot noticed that I had Two installs of Magisk. When I held the icon to view app info, one of them would behave as I expected, and the other would show me additional options like modules, downloads, superuser and hide.
When I opened the second copy of Magisk, the first one vanished from my applications tray and cannot be found anymore, and Magisk now shows it's green checkmark next to Latest Version v20.4 and Installed Version 17.1 but Safetynet gives me an API error.
Clicking Update Magisk Manager from the menu offers to install v7.5.1(267) but I am wary enough that I am unsure if I should proceed and am not even sure if Magisk has a module that I am looking for-- Something to control what apps launch on startup.
Will updating Magisk Manager show a new list of additional modules to be downloaded and perhaps something that I am looking for? Should I be worried about bootlooping my device and needing to reset it?
I once used the Boot Manager found on the Xposed Framework, but it's long since become non-functional and became the reason why I simply uninstalled what was bothering me, but now I want to keep the new applications that I have and disable their bootup on start.
Is Magisk the place that I should be looking for such a feature?
Running a Samsung GalaxyS5.