Hello, firstly sorry for bad english. My device is a Samsung s3 mini running 4.2.2 touchwiz. I'm trying to make that old phone my music player with viper4android. I installed latest magisk and magisk manager. Whenever I install a module installation happens without any issues. But after a reboot I can't see any changes that module makes. For example after installing viper4android it seems like it's installed on magisk manager but there aren't a app on app drawer, I tried few a more modules such as audio library patch etc. they all behave same. Looks like installed but has no effect over system. Secondly when I try to uninstall any of the modules it won't uninstall. I uninstall, reboot and it's still there. What can I do to solve my problem?
Related
Good afternoon all,
First time poster so be gentle.
I have recently rooted my Samsung Galaxy S7 Edge (SM-G935F) by using Magisk as well as installing TWRP on it.
I am currently trying to install modules from Magisk to enhance my device but have found that when I have installed them and go to reboot it puts me in a boot loop where the Samsung logo just pulses until I have to manually reboot the device causing me to then have to reformat the drive and load everything again.
I was trying to install and use:
AM3D Zirene Sound
Android Mic Fix
Emoji One
Tethering Enabler
Xposed Framework (SDK 24)
Is this a known issue and is anyone able to give advice/assistance with this please?
Thanks in advance
DarkByD3sign
Install one module at a time until you find the culprit. My first guess would be Xposed.
And there's no need to wipe your device...
Make sure you have the Mount Magisk script on your device. If you experience issues you can then boot to TWRP, flash that and then you can navigate to /magisk with the TWRP file manager and delete the module folder.
More tips like this can be found in the installation and troubleshooting guide.
Hi, does someone have root issue on s7 edge while using a banking app ? I can use my mobile banking app as my device is rooted, even tried magisk hide without success..
scribbclubber said:
Hi, does someone have root issue on s7 edge while using a banking app ? I can use my mobile banking app as my device is rooted, even tried magisk hide without success..
Click to expand...
Click to collapse
There might be more to it than just using MagiskHide:
https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
Hey all,
I've installed a version of the google phone app via apkmirror and it works. But I want to hide the dialler app!
I am using Oreo 8.0.0.362 and tried to freeze dialler with titanium backup, and although it says it is Frozen I still see the icon and it still works.
Can I uninstall dialler? Is there a solution to getting rid of it?
And! What latest apk of google phone can we use? I've got a v14 nonnexus atm.
Never mind! Apparently unfreezing and freezing again made it go away!
I do wonder what Google phone app we can use!
If you have Magisk 15.4 installed on Oreo (EMUI 8) then you can install my module (attached). It's based on @P1N2O module (https://github.com/Magisk-Modules-Repo/google-framework-magisk) I've only updated version and files inside which are taken from GApps for Android 8.0 ARM64 2018-02-17.
After that you're able to install Google Dialer straight from Play Store You can set it as default dialer and it works almost perfectly - from time to time Mate9 show system InCall UI for incoming calls instead of google's. I don't know really why, I have no time to check it.
rufik said:
If you have Magisk 15.4 installed on Oreo (EMUI 8) then you can install my module (attached). It's based on @P1N2O module (https://github.com/Magisk-Modules-Repo/google-framework-magisk) I've only updated version and files inside which are taken from GApps for Android 8.0 ARM64 2018-02-17.
After that you're able to install Google Dialer straight from Play Store You can set it as default dialer and it works almost perfectly - from time to time Mate9 show system InCall UI for incoming calls instead of google's. I don't know really why, I have no time to check it.
Click to expand...
Click to collapse
Cool! I had 15.4 installed and tried to add your module. And although it says it succeeded, I cant find phone in the app store. Check-in magisk I Saw that I'm at v16 now.
Can I reflash the 15.4 in twrp and try again?
Ok this is strange. I used the magisk uninstaller, and then reinstalled a 15.4 version for mate 9, which ante0 sent me.
Installed the manager and magisk says I have 15.4
Cant install your module though. It says data/magisk is not set up properly and that I should install magisk v14.0+!
EDIT: uninstalled magisk, installed it again and tried the module. Same error. Tried it again, and it worked! Nice! So, if at first you dont..
After flashing module you can try to clear data of Google Play Store and reboot.
If you encounter errors after flashing magisk just try to dirty flash it again. I think this module should work with magisk 16 if module template hasn't changed.
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.
I noticed something strange, on my phone and I'm trying different ways to solve it, but it just does not "work".
I have 2 x Magisk icons in my phone and I cannot remove them, so that I only have 1 x Magisk.
Here's some background,...
My phone: OnePlus 6 [OP6], with stock Oxygen OS 9.0.9 [OOS 9.0.9] Android and running custom kernel [Omega].
I had been running a ROM [xXx NoLimits] which is a Magisk Module.
For last 11+ months, I have had no issues with my phone, no issues with Magisk, and no issues with root really.
I updated to Magisk v20.0 (but it seems it was the Beta / Canary channel) and also,
I had used the "Hide Magisk Manager" feature, for 1 specific app. to work.
Just this week, I noticed some issues with my phone or that I had 'lost' root
This happens rarely, and I just reinstall Magisk, but it resolves itself.
So, I went looking and saw an odd thing: 2 x Magisk icons.
Since then, I have tried:
- Magisk Uninstaller [Magisk-uninstaller-20191011.zip]
- Flashed unpatched BOOT.img file, Flashed TWRP. Then, rebooted to TWRP.
- Flashed Magisk, flashed the custom kernel.
Still, I saw 2 x Magisk icons.
I could see 1 Magisk was on STABLE channel, while other was on CANARY channel.
This was strange.
So, I changed the CANARY to STABLE, etc. etc...
Anyway, too many combinations of uninstalling and removing root, reinstall Magisk, etc... and I still don't know how to really uninstall Magisk and start from ZERO again.
I have lost Magisk's association to my Magisk modules too.
Can anyone help or advise?
Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
I think I resolved my issue now...
I uninstalled Magisk using the official Magisk Uninstaller.
I also uninstalled the 2 x Magisk apps in my launcher, using this .APK ---> "Uninstalled SystemApps" ( https://github.com/nicolaserlonghi/UninstallSystemApps )
Then, I had to go through re-installing the BOOT.img, Magisk and most importantly, the ROM (which itself was a Magisk module).
Slowly, it populated the Magisk module list and 'SuperUser' lists, and I think I got the phone back into how I had it.
Didgeridoohan said:
Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
Click to expand...
Click to collapse
Yes, exactly.
Thanks for this tip, but I reached this conclusion anyway...
and used another .apk (Unsinstall SystemApps) to remove the Magisk Manager (which was the result of using "Magisk Manager Hide",
but then I must have mixed up Stable & Canary builds of Magisk on the phone, etc.)
Didgeridoohan said:
Sounds like you just have two Managers installed.
Click to expand...
Click to collapse
One thing weird though is, quite a few modules that were previously installed are missing from the Magisk "modules" section.
When I 're-install' them, they still don't show in the "modules" section.
For Example:
Vanced, Advanced Charging Controller, etc... all have been installed, but not showing up in Magisk.
I just had a weird situation of 2 different Magisk installs (at first it seemed like 2 x Managers), but it could be 2 different Magisk builds:
stable and canary
I don't know how to explain it, but maybe the Magisk Uninstaller doesn't work properly on Canary builds?
Anyway, my issue now is modules don't get listed in the Magisk Manager.
No, you did not have two different Magisk builds installed at the same time. Can't happen...
And without more to go on (logs, etc) it's gonna be real hard to help with the module issue.
Hi. I recently updated my Moto G5s Plus(Sanders) from Android 10 to Android 11(PixelExperience). I used Magisk v21 while installation and everything worked fine. Then I installed the the v22 update through the app. However after downloading and opening the new Magisk, it shows that Magisk isn't installed and that there are updates for both Magisk and Magisk manager. Upon clicking install for manager, nothing happens, no downloading or anything. But on clicking for Magisk, it shows a select and patch method, which I don't know what to do with .
Attaching screenshot below.
Did you by any chance have the Magisk app repackaged with a random name before updating? When moving to v22+ from older releases you need to do that with the app unhidden.
If you did have the app hidden before updating you might now have two apps installed, but you should be able to fix that by uninstalling both and installing the v22.1 apk again manually.
Didgeridoohan said:
Did you by any chance have the Magisk app repackaged with a random name before updating? When moving to v22+ from older releases you need to do that with the app unhidden.
If you did have the app hidden before updating you might now have two apps installed, but you should be able to fix that by uninstalling both and installing the v22.1 apk again manually.
Click to expand...
Click to collapse
Oh my, I actually did have it hidden. I just noticed the dual apps( I think I didn't notice it before because the second one had the default android logo icon) l. Much thanks for the help