This issue has been for me since i started using magisk
Everytime i update root is gone and apps dont prompt for root
The only way which worked for me is this
1. Restore system image with twrp
2. Uninstall magisk completely in twrp
3. Install the magisk latest version
4. Wipe cache n dalvik cache and reboot
5. Install magisk latest manager
6. Open it and close it
7. Run root apps still dont asks root but press back after some time root pop up comes and grant it ,this has been same since v16 the first yime i used magisk
But somehow it works like this i just uodated to 18.1 from 18.0
If you guys still get this issue you may try these steps if it works for you,logs has no issue same as usual
Related
I've had magisk installed since version 6, I've published some magisk modules already and never had a problem until today.
After a full clean reinstall of Nougat NBD90Z (with wipe) on my Nexus 6 and then flashing Magisk, phh's superuser for magisk, installing phh's superuser apk from play store and magisk manager apk I stumbled upon a previously reported (without details) bug where magisk manager would refuse to install modules from repo claiming they are not magisk modules.
I've struggled trying everything I could including the full wipe (more details here: http://forum.xda-developers.com/apps/magisk/module-app-systemizer-t3477512/69230448#69230448) and bounced some ideas off @pnwsr6 who's had the similar problem on Nexus 6 device.
I've achieved a partially working Magisk Manager (manual installs of ZIP files work, but installs from repo still fail) and here's the list of steps which lead to me having semi-working magisk manager again:
1. I flashed ZIP files of some modules in twrp (I'm attaching App Systemizer and Nexus 6 LED Enabler which I flashed)
2. After the phone booted up I saw the modules active and working
3. Within Magisk Manager I then added the ZIP file of the phh's superuser module from that thread (http://forum.xda-developers.com/attachment.php?attachmentid=3893967&d=1475554052)
4. Now at least manual installation of modules within Magisk Manager are working fine.
@topjohnwu -- I've enabled verbose logging and extra logging for bash commands, but I'm still not seeing anything in the log on top of the regular output.
Created an issue against Magisk Manager so it's easier to track for developers: https://github.com/topjohnwu/MagiskManager/issues/20
Looks like that even after flashing some modules in twrp, Magisk Manager only allows to install from zip only exactly the same ZIP I've already flashed (even a minor change and bump of versionCode results in "This ZIP is not a Magisk Module!"). So it might be an issue of Magisk Manager being unable to write to /magisk despite having storage permission and being granted root access.
Well, it works now (you'll have to wipe again). So here's the sequence of events:
1. Flashed @RatchetPanda's busybox http://forum.xda-developers.com/attachment.php?attachmentid=3850579&d=1471875389 from twrp -- got stuck on a boot animation, rebooted again in twrp, flashed magisk uninstall and it didn't help for some reason.
2. So I force-rebooted into fastboot and flashed nbd90z with wipe.
3. After apps were restored and everything was set up, I booted into twrp (it didn't even ask me if I want to allow /system modifications for some reason), added magisk v8 and phh's r259 root to the list, flashed them both.
4. Once the phone booted I could again install modules from repo/zips.
Maybe something didn't get properly wiped first two times but it's working now @pnwsr6!
I've seen this error as well on my Nexus 6 NBD90Z with Magisk v8. Started with v7 after some heavy modification on my part .
I was sometimes able to fix it by simply extracting the zip and then Magisk Manager would somehow recognize it as a module.. Other times I could extract the zip and then re-archive the contents and Magisk Manager would recognize that as a module. Weird, but doable.
stangri said:
Well, it works now (you'll have to wipe again). So here's the sequence of events:
1. Flashed @RatchetPanda's busybox http://forum.xda-developers.com/attachment.php?attachmentid=3850579&d=1471875389 from twrp -- got stuck on a boot animation, rebooted again in twrp, flashed magisk uninstall and it didn't help for some reason.
2. So I force-rebooted into fastboot and flashed nbd90z with wipe.
3. After apps were restored and everything was set up, I booted into twrp (it didn't even ask me if I want to allow /system modifications for some reason), added magisk v8 and phh's r259 root to the list, flashed them both.
4. Once the phone booted I could again install modules from repo/zips.
Maybe something didn't get properly wiped first two times but it's working now @pnwsr6!
Click to expand...
Click to collapse
I probably won't try again until next update, and hope the wipe just wasn't clearing something. I have the zip installed through twrp and working for now so I'm good till then.
just wondering if you're still having this issue with v9? I had modules installed fine under v6, but never really installed any modules under v8 to see if this problem occurred for me. now that I'm on v9, which has been wiped clean to start, I can no longer install any modules via Downloads or in the Modules section... any suggestions?
I have the same issue when trying to install viper with v9 on Nexus 6P DP2
Skickat från min Nexus 6P via Tapatalk
Same here. Find a fix ?
From what I hear, ZIP/module management has been reworked in the upcoming magisk v10, so unless you want to go the route I went thru, you can just wait for that.
stangri said:
From what I hear, ZIP/module management has been reworked in the upcoming magisk v10, so unless you want to go the route I went thru, you can just wait for that.
Click to expand...
Click to collapse
Just an FYI, I do still have this problem, but can install the zip through twrp. Maybe 10 will be the solution.
I had the same problem, I cleared magisk manager data and it works fine now
Didn't help
Sent from my SM-G532F using Tapatalk
I've published snapshot builds of magisk v10 and magisk manager v2.6, try these together to see if they'd help.
stangri said:
I've published snapshot builds of magisk v10 and magisk manager v2.6, try these together to see if they'd help.
Click to expand...
Click to collapse
I tried the latest one from the 26th, magisk manager keeps crashing when trying to install the downloaded dialer/contacts on HTC 10.
Meowdib said:
I tried the latest one from the 26th, magisk manager keeps crashing when trying to install the downloaded dialer/contacts on HTC 10.
Click to expand...
Click to collapse
Weird, do you have the same problem with magisk manager 161223?
stangri said:
Weird, do you have the same problem with magisk manager 161223?
Click to expand...
Click to collapse
Same
I need a Help to download modules using magisk
Lastest version, Included phh root, manager is from G. play,
But Modules download function is not working
Say "No modules found" for download to install via magisk.
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
newuxtreme said:
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
Click to expand...
Click to collapse
I thought Dr. Ketan's N10 ROM was pre-rooted with either Magisk or SuperSU. Did you not have this option in the AROMA Installer? If not, here is some help..
I personally recommend Magisk for root. It's just as easy to use Magisk over SuperSU. Each root solution has its own dedicated app as well. To root with Magisk you will need the latest root zip which is V14.0 along with the latest Magisk Manager apk.
You can download the latest Magisk Manager apk and the latest Magisk V14.0 root zip from the link below...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Here you can read and learn all about Magisk too. Once you download both the root zip and the apk, transfer both to your internal storage.
Next, download the no_verity_opt_encrypt_5.1 zip from here...and transfer it to your internal storage.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
(Its the second link from the bottom in the list)
Easy steps to root your device with Magisk..
Boot to TWRP Recovery
Select Backup and put a check in each box. That way if anything goes wrong you can restore the backup and have a working device.
Next, select WIPE - Advanced WIPE - Check both caches
Swipe to wipe both caches
Next, select INSTALL
Navigate to where you saved the root zip and select the zip.
Swipe to flash the zip
Click on the box to wipe the caches
Now, just in case, flash the no_verity_opt_encrypt_5.1 zip that you downloaded earlier.
Reboot your device. Once booted up, install the Magisk Manager apk. It will install as a normal app. Make sure you have enabled "unknown sources" in Settings - Lock Screen and Security so you can install apps outside of the Play Store.
Open the Magisk Manager app and set it up to your preference. It's very easy to use.
If you run into any issues don't hesitate to ask questions.
Good luck and happy flashing!
Sent from my Samsung SM-G955U using XDA Labs
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?
@rovo89
@topjohnwu
https://www.didgeridoohan.com/magisk/MagiskHelp
I have added much more information.
Reinstall firmware???
LoneWolfz said:
Reinstall firmware???
Click to expand...
Click to collapse
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
535iu said:
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
Click to expand...
Click to collapse
No maybe but i suggest you to backup all your data etc. just to be safe
Dear XDA,
Model: Xiaomi Redmi 4X(Santoni)
Used TWRP:
Installed latest Lineage OS 16.0 of November 20, 2019 with formatting internals and wiping system, vendor, dalvik and cache.
Installed lastest Magisk v20.1 from GitHub page
Booted ROM and installed "MagiskManager-v7.4.0.apk" from above link
As the result:
MagiskManager shows everything green
No root prompt in any application and Root Checker shows that root is not installed.
"Settings -> System -> 'Developer options' -> 'Root access'" have only two options: Disabled and "ADB only"
Already have tried:
Disabling power optimization entry for MagiskManager
Reinstall Magisk using MagiskManager
What might be the reason of no prompt issue?
Why not SuperSU: is it worth to tell why? For example, basically Netflix won't work etc.
Thank you very much for any working suggestion.
This happened to me too once. What helped was simply re-flashing the 20.1 Magisk zip. It contains the Manager apk, so no need to install it separately.
I Have Nexus 5x and Lineage OS 15.1.
For me it was Lineage OS issue. Instead 20191118 I flashed 20191105. I had some other weird bugs too.
Ænimal said:
This happened to me too once. What helped was simply re-flashing the 20.1 Magisk zip. It contains the Manager apk, so no need to install it separately.
Click to expand...
Click to collapse
What do you mean by reinstall? Something like that:
Wipe phone
Install Lineage OS image
Install Magisk zip
Boot
Reboot into recovery
Install Magisk zip
Boot
Are above the full steps you suggesting?
vv77vv said:
What do you mean by reinstall? Something like that:
Wipe phone
Install Lineage OS image
Install Magisk zip
Boot
Reboot into recovery
Install Magisk zip
Boot
Are above the full steps you suggesting?
Click to expand...
Click to collapse
I thought I expressed myself pretty clearly. Well, a clean install of your system is always a good idea (given you backed up all your personal data) .You can also just extract the boot.img from your LOS image and flash that in twrp prior to flashing magisk. But what I did when the root prompt didn't pop up was simply flashing the magisk zip again in twrp, (maybe wiping caches as well) and after rebooting magisk su was working as intended.. Good luck
So, I’m rooted with Magisk. Before installing the latest ‘Google play system update’, I restored images. After that, I was wondering if installing Magisk to the other slot would do the thing. Thanks in advance!
How do you solved this?
I have the same situation.
https://android-developers.googlebl...os-with-projects-treble-and-mainline.html?m=1
Looks like doesn't install to other slot. Why not just install Magisk back to current active slot thru Manager app, reboot, and see if updates were applied
This might help a bit - https://www.reddit.com/r/androidroo.../?utm_source=share&utm_medium=web2x&context=3
Thanks @amihir, but still it is not super clear.
According to the link, user reinstalled Magisk in the Magisk Manager app, and then restarted and got it working, but it is not enough information for me. Hence, in which order?
So I believe they did either this:
1. Get notification update which is ready to be installed and asked about restart.
2. Then, user first reinstalls Magisk in Magisk Manager, without restarting from Magisk Manager.
3. Then restarts the device in step 1.
or
1. Get notification update which is ready to be installed and asked about restart.
2. Presses restart.
3. After restart, user reinstalls Magisk in Magisk Manager and restarts the device.
Vantskruv said:
Thanks @amihir, but still it is not super clear.
According to the link, user reinstalled Magisk in the Magisk Manager app, and then restarted and got it working, but it is not enough information for me. Hence, in which order?
So I believe they did either this:
1. Get notification update which is ready to be installed and asked about restart.
2. Then, user first reinstalls Magisk in Magisk Manager, without restarting from Magisk Manager.
3. Then restarts the device in step 1.
or
1. Get notification update which is ready to be installed and asked about restart.
2. Presses restart.
3. After restart, user reinstalls Magisk in Magisk Manager and restarts the device.
Click to expand...
Click to collapse
I'll explain.
Today I faced this update notification so, this reddit thread helped me.
What I did -
1. Backup
2. Install Google Play System Update
3. Magisk -> Direct Install (recommended)
4. Restart
My phone safely booted up, with root intact.
Sad though that Magisk Manager does not seem to have a backup function... or maybe I have missed it.
Update: seems like Google play system updates doesn't remove root or changes the A/B slot every update.