Hi,
i have problems to get Magisk respectively Magisk Manager to work proberly.
Everytime i open Magisk Manager the changes notification appear and althought i disable supersu notification popup it appears everytime a app request root.
The settings i changed doesnt stick
I tried older Magisk and Manager version, reinstalled, cleared cache but nothing works.
This all was done on LOS14.1 and i also tried Omnirom 8.1 but there is exact same problem.
I trtied to get help with this in Magisk section (here, here,here) but it seems noone can help me with this.
This must be a Redmi Note 4 (mido) specific problem as with all my other devices there are no problems at all.
Hopefully someone have an idea whats the problem here.
der_Kief said:
Hi,
i have problems to get Magisk respectively Magisk Manager to work proberly.
Everytime i open Magisk Manager the changes notification appear and althought i disable supersu notification popup it appears everytime a app request root.
The settings i changed doesnt stick
I tried older Magisk and Manager version, reinstalled, cleared cache but nothing works.
This all was done on LOS14.1 and i also tried Omnirom 8.1 but there is exact same problem.
I trtied to get help with this in Magisk section (here, here,here) but it seems noone can help me with this.
This must be a Redmi Note 4 (mido) specific problem as with all my other devices there are no problems at all.
Hopefully someone have an idea whats the problem here.
Click to expand...
Click to collapse
I'm unable to understand what exactly do you mean?
Are you unable to use root? What rom do you use? Do you have super su previously installed, and did you flash magisk over it?
ok i will try to explain a little better
Magisk is working so far and apps are getting root.
But as far as i start Magisk Manager the "changes" notification appears every time (which should only displayed once after new install or update of Magisk Manager)
Also when i disable the supersu notification popup inside Magisk Manager it wont stick. Every time i open an app the popum informs that root is granted.
The only solution i have so far is to hide Magisk Manager with the option inside the Magisk Manager settings.
Its hard to describe and i hope its now understandable
Here posted some logs !
der_Kief said:
ok i will try to explain a little better
Magisk is working so far and apps are getting root.
But as far as i start Magisk Manager the "changes" notification appears every time (which should only displayed once after new install or update of Magisk Manager)
Also when i disable the supersu notification popup inside Magisk Manager it wont stick. Every time i open an app the popum informs that root is granted.
The only solution i have so far is to hide Magisk Manager with the option inside the Magisk Manager settings.
Its hard to describe and i hope its now understandable
Here posted some logs !
Click to expand...
Click to collapse
I see now. What magisk version u using? I'm on v16.0 and it works fine, even the changed settings work well
MyNameIsRage said:
I see now. What magisk version u using? I'm on v16.0 and it works fine, even the changed settings work well
Click to expand...
Click to collapse
Magisk v16 and Manager v5.6.1
But i tried older verions of Magisk and Manager but it doesnt help at all.
Also i reinstalled ROMs (LOS and Omni) tried different recoveries..... no go.
I have no idea ... on my other devices no problem at all.
I hope someone see an error in the logs.
The following lines doenst look as they should
W/SharedPreferencesImpl( 9451): java.io.FileNotFoundException: /data/user/0/com.topjohnwu.magisk/shared_prefs/com.topjohnwu.magisk_preferences.xml (Permission denied)
W/pool-1-thread-1( 9525): type=1400 audit(0.0:146): avc: denied { rename } for name="com.topjohnwu.magisk_preferences.xml" dev="mmcblk0p49" ino=1664194 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=ubject_r:app_data_file:s0 tclass=file permissive=0
These lines doesnt appear in the logs of my working devices but I compared the permission of that folder with one of my working devices but it looks OK.
Dude are you using Dual boot? Then this is expected
no i dont use Dual boot.
But maybe i did something wrong at Installation ?
Unlock Bootloader -> flash Recovery -> format Data and wipe -> flash ROM, GApps and Magisk
der_Kief said:
no i dont use Dual boot.
But maybe i did something wrong at Installation ?
Unlock Bootloader -> flash Recovery -> format Data and wipe -> flash ROM, GApps and Magisk
Click to expand...
Click to collapse
Your flash queue is right, but possibly you should try flashing magisk after one boot. (Just flash rom and gapps, reboot , set up device, and then boot to recovery and flash magisk)
then the Redmi Note 4 must be something special
With my other devices i made it exactly the same and there are no problems at all.
Maybe next time i flash new/update ROM i will try it ....
Related
I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?
Hello friends. Yesterday my redmi note 4x snapdragon (mido) showed a strange problem. I was using phone normally and then a notification popped out from magisk. It was about the updates available for both - magisk manager and magisk. I first updated the manager from the app itself by clicking on 'install'.
But after it finished installing the magisk manager, when it reopened it showed that magisk was not installed!
Then I check my root applications (greenify, mixplorer) and they also were not getting root access. Neither There was a prompt for granting root acess.
I checked my root status from the root checker app from playstore and it showed - 'root access available but not properly installed'
Please suggest me what should I do to update magisk or get magisk working back.
Other details-
Rom - aosp extended official 6.3 pie treble
Kernel - Franco kernel r20
Previous magisk installed- 18.00
New available magisk - 20.3
New magisk manger that I updated - 7.5.1
Everything was working fine on my device previously.
Please help me guys.
Thanks in advance.
Solved the issue!
AviralSri said:
Hello friends. Yesterday my redmi note 4x snapdragon (mido) showed a strange problem. I was using phone normally and then a notification popped out from magisk. It was about the updates available for both - magisk manager and magisk. I first updated the manager from the app itself by clicking on 'install'.
But after it finished installing the magisk manager, when it reopened it showed that magisk was not installed!
Then I check my root applications (greenify, mixplorer) and they also were not getting root access. Neither There was a prompt for granting root acess.
I checked my root status from the root checker app from playstore and it showed - 'root access available but not properly installed'
Please suggest me what should I do to update magisk or get magisk working back.
Other details-
Rom - aosp extended official 6.3 pie treble
Kernel - Franco kernel r20
Previous magisk installed- 18.00
New available magisk - 20.3
New magisk manger that I updated - 7.5.1
Everything was working fine on my device previously.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
So friends, i figured out the solution myself. And I am describing it here in case anyone faces such a problem.
First of all, i forgot to mention one strange thing - while i was updating the magisk manager to new 7.5.1 version from the manager itself, during its installation, i got 2 prompts from google play store which said that i should not install this app as it is not a trusted application. But i clicked on "Install Anyway" both the times and it installed.
After then, when i opened the updated maanger, it showed that magisk is not installed (the new manager app also took some time greator than usual, on its first launch). And then the root access went from everywhere on my device.
Then i thought of uninstalling the magisk from flashing the Magisk-uninstaller-zip-file and then installing the magisk-v-18.zip again, but after searching for some time about uninstalling the magisk, i came to know that there are greater chances of my device going into a bootloop.
For one last time, i tried this - uninstalled magisk manager 7.5.1. Then installed MagiskManger 7.4.0 again. And when i launched it, it showed me Magisk-v18 installed!. Also the app showed me that updates are available for both - manager and magisk. App also showed the superuser menu, Magisk Hide menu. I thought that the problem was solved. But quickly i found that still other root apps were not working. When i reopened the Magisk-Manger-7.4.0, it displayed a message - "A addition setup is needed for root to work". But i did not update from there. Instead i followed a safe path -
Solution - 1. Download official Magisk-20.3 and copy in your phone's internal storage.
2. Then copy the original unaltered boot.img of the rom you're using in your internal storage.
3. Boot into TWRP recovery. Go into "install", and select "install image". Then select your boot.img and swipe to flash.
(Here, i did not wipe anything before flashing. Just flashed the img file over)
4. Reboot to your system. Now your android be cleanly unrooted.
5. Again reboot to TWRP. Select "install", and select and flash the Magisk20.3.zip file and reboot to your system.
Voila!!! Here you go! Your system is now properly rooted with latest magisk!
Thanks!
I just installed the app and it shows that " Launching the app on rooted device is blocked". So I uninstalled it and then reinstalled it again and used magisk hide. Also, I have hide magisk manager already enabled in magisk settings but the app still doesn't budge and somehow still detects root and thus I can't use it. Any solutions ?
I'm on MIUI EU 11.0.6 rooted with magisk 20.4
seshStation 5.1 kernel
Official latest TWRP recovery.
MasterFURQAN said:
I just installed the app and it shows that " Launching the app on rooted device is blocked". So I uninstalled it and then reinstalled it again and used magisk hide. Also, I have hide magisk manager already enabled in magisk settings but the app still doesn't budge and somehow still detects root and thus I can't use it. Any solutions ?
I'm on MIUI EU 11.0.6 rooted with magisk 20.4
seshStation 5.1 kernel
Official latest TWRP recovery.
Click to expand...
Click to collapse
Do you pass safetynet?
There's a magisk hide config module in magisk downloads if you don't.
sotosgolf said:
Do you pass safetynet?
There's a magisk hide config module in magisk downloads if you don't.
Click to expand...
Click to collapse
Yes I'm passing safety net. Both the magisk manager and the check SafetyNet app confirm the same.
MasterFURQAN said:
Yes I'm passing safety net. Both the magisk manager and the check SafetyNet app confirm the same.
Click to expand...
Click to collapse
You could flash your original boot image and see if it's related with the kernel, just in case.
sotosgolf said:
You could flash your original boot image and see if it's related with the kernel, just in case.
Click to expand...
Click to collapse
I was thinking the same. I'll reply with the results. Thanks
You could try renaming the magisk manager.
It worked for me with the McDonald's App.
You can find it in the settings from magisk manager. Give the app a random name like managerxy3 and use magisk hide option, just in case.
Maybe try core mode only, if you only need root and don't use any modules.
SpitFireXB360 said:
You could try renaming the magisk manager.
It worked for me with the McDonald's App.
You can find it in the settings from magisk manager. Give the app a random name like managerxy3 and use magisk hide option, just in case.
Maybe try core mode only, if you only need root and don't use any modules.
Click to expand...
Click to collapse
I already have that enabled (Hide magisk manager). It's in the OP. I only have busybox by osmosis installed in magisk modules.
I just installed Paytm First Games (Lite? ) and upon launching it asked to Login via OTP/Paytm. I didn't proceed any further. Magisk 20.4,crDroid 6.4.
MasterFURQAN said:
I was thinking the same. I'll reply with the results. Thanks
Click to expand...
Click to collapse
Sorry about the delay. I flashed the original stock boot from MIUI EU but the app still detects root somehow.
Any Guesses ?
amn1987 said:
I just installed Paytm First Games (Lite? ) and upon launching it asked to Login via OTP/Paytm. I didn't proceed any further. Magisk 20.4,crDroid 6.4.
Click to expand...
Click to collapse
Yup the lite version on the play store works but not the full version downloadable from their official website
So is there any solution to this??
How the paytmfirstgame (full version) deteck root after renaming magisk , passing safetynet and hiding app from magisk manager. I think magisk is now not a bigshot
Still can't open Paytm First Games even after using Magisk Hide
Any solution?
Facing the same issue. Do we have any solution on how to make the paytmfirstgames app work on rooted device?
Has anyone updated their Magisk version after initial install?
I'm on Magisk 22, and version 22.1 is available. I don't have a burning need for 22.1 but have found from experience that it's best to not lag behind too much; eventually some or other module will require a recent version.
I'm guessing it's similar to initial install, but done from within the Magisk app using 'Recovery Mode'. First for me doing this, so figured I'd ask about pitfalls to avoid from folks who have already done this.
EDIT: To answer my own question (since I'm so impatient), yes. Just remember to rename Magisk-v22.1.apk to .zip before rebooting to save you some time after Magisk reboot takes you to TWRP.
Arobase40 said:
This is indeed an important update so better do the update but prepare yourself to update more stuffs if you want to keep EdXposed and his modules working...
I didn't think about downloading Magisk-v22.1.apk and to rename to .zip before flashing it with TWRP so I had to update the Magisk manager before I could update Magisk itself.
After that you may or may not update the Riru and Riru edXposed modules as the edXposed was not working anymore for me . So I had to also update the edXposed manager.
And don't forget to reboot many times...
Finally you could also update the AFWall+ from the PlayStore... ^
Click to expand...
Click to collapse
All working well here with:
Magisk 22.1
Riru v25.3.3.r393.ed83041
Riru - EdXposed v0.5.2.2_4683-master
EdXposed Manager 4.6.2
Arobase40 said:
This is not related with the Magisk update but can you tell what is actually your Tab S6 SafetyNet status ?
Click to expand...
Click to collapse
I have no idea. I've never looked in to what it even means; sonething that is needed for some apps, from what I've read?
What do want me to look for?
Arobase40 said:
Well, to be short the SafetyNet status indicates what you can potentially do with a rooted device such as creating Secure Folder, installing and use banking apps, probably use Netflix or some other apps or features you would be able to run with a non-rooted device.
So, to know your SafetyNet status you simply have to open your Magisk manager and tap the "Verify SafetyNet" option on the Magisk welcomm screen. Then it may ask or may not ask you the permission to download external modules,do so and then it will tell you if you pass this test or not !
If I ask you that it because some weeks ago I passed all the test with my Tab S6 and my 2 Galaxy Note 9 and now they all fail for some unknown reasons and as I changed nothing in the Magisk environment and the edXposed environment except updating some Samsung and Google apps ! ^^
So I want to try to understand how it comes and when it comes this SafetyNet compatibility was broken... ^^
If other users could also check their SafetyNet status and indicate if there was a change it may help.
Click to expand...
Click to collapse
I tapped 'Check SafetyNet' and got (see screenshot). Not interested in going any further. I hope you understand. fwiw, I too have an S6 with all Google and most Samsung apps either frozen or deleted; at last count 149 of them.
Hola Amigos,
I have A Mido (2GB RAM) device with Superior OS (Phoniex,Android Q) Installed.I installed Magisk and whenever I flash any modules,
Magisk Crashes(Not Magisk Manager).Here's what I mean:The wallpaper I apply using Magisk get reset to default one.
Many Automatic Modules(Modules that start woring on boot) stop for 5-10 seconds and then work. App that I was using before the
crash also crashes.
It happens pretty frequently.
I installed Magisk like this:
Booted to TWRP
Wiped System,Dalvik,Vendor,Data,Cache
Formatted Data
Flashed Superior OS,Open Gapps Pico A10
Rebooted to System
After setting up Google
Rebooted to TWRP
Flashed Magisk 24.3.zip
Rebooted to System.
Installed Each Module one at a time and Rebooted,Then installed second module.....
Sometimes even of I don't install any module the Magisk Manager crashes.
The Modules that I use:
Google Sans Font System Lessly : https://www.pling.com/p/1457664/
MIUI Wallpaper and Akira Wallpaper(Live) : https://www.pling.com/p/1423749/
JamesDSP : https://zackptg5.com/downloads/jdsp_v4.4.zip
XDA Thread of (JamesDSP) (This is not a module): https://forum.xda-developers.com/android/apps-games/app-reformed-dsp-manager-t3607970
Naruto Sharingan BootAnimation for all devices : https://www.pling.com/p/1595951/
Godspeed Mode V X7 All devices : https://www.pling.com/p/1596710/
I am on stock kernel and TWRP 3.5.1
How can I fix these Crashes??
Also Fingerprint and auto rotate sensor are not working even if I uninstall Magisk,Whereas it works if I use UBPorts
Alpha V 1.1
Thanks for help!!!
I have same problem since I updated magisk to 26.1 and when I downgrade it to 25 or 24 stell same problem I tried to change magisk to kernel su the new root app and when I try to add one module at least It makes my app crash but it work only to give root access to any app I want and it is hidden from any app can detect root like bank apps this is crash log of one app of though apps https://bin.kv2.dev/~645360ede599576ea02c5490
And the screen shot the tree apps that crash when use modules
Mady_H said:
I have same problem since I updated magisk to 26.1 and when I downgrade it to 25 or 24 stell same problem I tried to change magisk to kernel su the new root app and when I try to add one module at least It makes my app crash but it work only to give root access to any app I want and it is hidden from any app can detect root like bank apps this is crash log of one app of though apps https://bin.kv2.dev/~645360ede599576ea02c5490
And the screen shot the tree apps that crash when use modules
Click to expand...
Click to collapse
Turns out James dsp and boot animation modules caused the crashes . Safety Net fix and shamiko did not cause the crash . Maybe you could try uninstalling unnecessary modules , btw which modules do you use ?
LolFlasherNoob said:
Turns out James dsp and boot animation modules caused the crashes . Safety Net fix and shamiko did not cause the crash . Maybe you could try uninstalling unnecessary modules , btw which modules do you use ?
Click to expand...
Click to collapse
Iam using ahamiko and safety net fix and hide my app list and ls posed I tried to add zygisk on kernelsu and when I did that it made my apps crash again and I tried to add module to install metrolla dailer phone to record calls it made my apps crash and ls posed zygisk didn't make any thing
So what is common with zygisk for kernelsu and jsp and boot animation
+
I will try to clean install the rom and root again to see what is going on and try to flash new rom to see if it is common in another rom or not
Mady_H said:
Iam using ahamiko and safety net fix and hide my app list and ls posed I tried to add zygisk on kernelsu and when I did that it made my apps crash again and I tried to add module to install metrolla dailer phone to record calls it made my apps crash and ls posed zygisk didn't make any thing
So what is common with zygisk for kernelsu and jsp and boot animation
+
I will try to clean install the rom and root again to see what is going on and try to flash new rom to see if it is common in another rom or not
Click to expand...
Click to collapse
Consider this guide .
Although it's for redmi note 11 , the rom flashing part is universally applicable to all devices.
[GUIDE] LATEST/UNIVERSAL FLASHING GUIDE FOR TWRP,OTHER RECOVERY AND ALL ROMS [Spes/Spesn] Redmi Note 11
: Combined four How To Guide threads into one. Post #2 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi Note 11[WINDOWS-Only] Post #3 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi...
forum.xda-developers.com