In miui9 pro. After 15.2 update magisk. The magisk manager cant able to acess internal storage. I will try many way. Wipe chaches, install sefty net.. and all permission i will enable bit. Magisk cant acess my internal storage... Please help..:crying:
Try enabling permissions inside settings, if nothing works go back to v15.1 MIUI have many compatibility issue
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.
Hi,
I tried clean install official nougat on my phone, after I setup the phone and went back to twrp to install magisk 11.1zip and the magisk manager, I open magisk manager and it only show rooted, but no root permission, also when I go to settings the only option is dark theme, update notify, 2 developer logs, nothing else. The boot image location is blank. Does anyone know what is the problem, did I do something wrong?
PS: there was no Supersu or other root installed, only magisk 11.1 and magisk manager.
Thanks!!!
LazyJr said:
Hi,
I tried clean install official nougat on my phone, after I setup the phone and went back to twrp to install magisk 11.1zip and the magisk manager, I open magisk manager and it only show rooted, but no root permission, also when I go to settings the only option is dark theme, update notify, 2 developer logs, nothing else. The boot image location is blank. Does anyone know what is the problem, did I do something wrong?
PS: there was no Supersu or other root installed, only magisk 11.1 and magisk manager.
Thanks!!!
Click to expand...
Click to collapse
Did you try building from here? https://github.com/therealahrion/Collective-Dolby-Atmos-Ports/tree/master/axon7
LazyJr said:
Hi,
I tried clean install official nougat on my phone, after I setup the phone and went back to twrp to install magisk 11.1zip and the magisk manager, I open magisk manager and it only show rooted, but no root permission, also when I go to settings the only option is dark theme, update notify, 2 developer logs, nothing else. The boot image location is blank. Does anyone know what is the problem, did I do something wrong?
PS: there was no Supersu or other root installed, only magisk 11.1 and magisk manager.
Thanks!!!
Click to expand...
Click to collapse
Did you enable magisk hide? Reboot until root options show up again and disable it
Meowdib said:
Did you try building from here? https://github.com/therealahrion/Collective-Dolby-Atmos-Ports/tree/master/axon7
Click to expand...
Click to collapse
I think that his phone is the ZTE Axon 7 rather than using the Axon 7 Dolby Atmos.
I have an error in twrp 21, he says in red:
Unable mount storage (in 2° or 3° line)
But pass, and install all...
In magisk, he not install nothing. Already actualized, nothing change.
Im in Stock rom.
How solve this problems, without change my rom Stock?
install this that solves the problem of not being able to install magisk modules
https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
Hello, so i did something to my magisk manager, i was trying to get google pay to work at wich point i have now given up, i had magisk repackaged before, so i i stalled busy box module and then i disabled it thinking maybe that if i did that i would be able to use google pay it didnt work so i rebooted everything seemed fine until i could no longer open magisk, the app freezes on the mask/logo and thats it, i had it repackaged as manager but i uninstalled it and re installed it as magisk manager thinking that may help but it didnt. I also can not grant root acess even though it says its been granted it just keeps asking me over and over.
Delta wolf said:
Hello, so i did something to my magisk manager, i was trying to get google pay to work at wich point i have now given up, i had magisk repackaged before, so i i stalled busy box module and then i disabled it thinking maybe that if i did that i would be able to use google pay it didnt work so i rebooted everything seemed fine until i could no longer open magisk, the app freezes on the mask/logo and thats it, i had it repackaged as manager but i uninstalled it and re installed it as magisk manager thinking that may help but it didnt. I also can not grant root acess even though it says its been granted it just keeps asking me over and over.
Click to expand...
Click to collapse
Uninstall magisk and repatch your boot image if that doesn't work you have to reflash your boot image and then patch the new boot image..... Now if you have a encrypted internal storage reflashkng the boot image going to bring back your encryption and you won't be able to use twrp properly and only way to fix that would be to fix decrypt zip for your device but to do that properly you have to be able to mount data in twrp to flash that zip and only way to mount data would be to format data and then you be able to click on data to flash your zip to decrypt and then flash magisk it's alot if simply un installing magisk and repatchin doesn't work for you
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
PoochyX said:
Uninstall magisk and repatch your boot image if that doesn't work you have to reflash your boot image and then patch the new boot image..... Now if you have a encrypted internal storage reflashkng the boot image going to bring back your encryption and you won't be able to use twrp properly and only way to fix that would be to fix decrypt zip for your device but to do that properly you have to be able to mount data in twrp to flash that zip and only way to mount data would be to format data and then you be able to click on data to flash your zip to decrypt and then flash magisk it's alot if simply un installing magisk and repatchin doesn't work for you
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
So if i read this correctly (im on a one plus 6 so i have my data accesable etc) i need to uninstall magisk manager, reboot twrp, uninstall magisk, re install magisk,
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