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
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.
Hello,
I just got my P10 (VTR-L29) yesterday, coming from a P8 Lite that I used to play a lot with and I already miss the adblock and the clean debloated system.
According to the new version of Magisk here, there is a new install method that works if you don't have a custom recovery like it used to be in the past. The new method modifies the boot.img via Magisk Manager, stores it in a folder and then you have to flash it with adb.
My question is: Do I have to unlock my phone in order to do that trick? Anyone else that tried something similar?
Nobody?
Maybe I'm not clear enough..
Steps to reproduce:
-install Magisk Manager 14 and use the inside app patcher
-find the patched boot.img on storage
-move the boot.img in PC storage
-use the PC in order to flash the patched boot.img
-reboot and wait
It's supposed to work that way but I don't want to unlock the bootloader,atleast for now.
Is it safe to do?
Xperias do not boot with the bootloader locked if boot.img is changed. I guess it will be the same for Huaweis.
So the only way to do that is to unlock the bootloader..seems like I have to do it lol.
Magisk v14 is working on my device. Unfotunately, i cannot pass safetynet. How about you guys?
Working but I Guess that You unlocked the bootloader,right?
You can try to use the universal safetynet fix, flash it in twrp and check.
Firicel69 said:
Working but I Guess that You unlocked the bootloader,right?
You can try to use the universal safetynet fix, flash it in twrp and check.
Click to expand...
Click to collapse
Already tried that (the new one for v14). Unfortunately, it didn't work.
Thank you anyway
garris_bibop said:
Magisk v14 is working on my device. Unfotunately, i cannot pass safetynet. How about you guys?
Click to expand...
Click to collapse
I had the same problem. Maybe my experience will help:
Open Magisk manager and check Log->Magisk. Are there any messages from MagiskHide? It should be.
Try this:
1. Open Magisk manager and disable Magisk hide.
2. Reboot
3. Open Magisk manager and enable Magisk hide.
I used commands in Terminal Emulator
Code:
su
magiskhide --disable
magiskhide --enable
At first it didn't work out but after a lot of desperate enabling/disabling and few reboots MagiskHide started to work (I couldn't determine the reason of its misbehaving).
For now I successfully pass SafetyNet checks.
Hi,
Sometimes I have some problems with my devices and want to disable Magisk just to be sure it's not the cause of the problems. My question is - if I uninstall it from Magisk Manager, and then after some time reinstall again will all modules with their configurations remain untouched? If not then is there any way to backup them somehow? Thanks in advance.
As long as you restore the stock boot image and keep the Magisk image intact, you'll have temporarily disabled Magisk and all your modules will still be installed and intact. Just flash the Magisk zip again to enable.
Easiest way to do this should be to use the "Restore Images" option when pressing "Uninstall" in the Manager.
Thank you. will do this that way. When installing again can't I just use "Install" from Magisk Manager?
You can patch your boot image and then flash the patched image manually. You can not install Magisk directly, since that requires superuser access...
Thanks, works like a charm.
Re: Temporarily Disable Magisk & Complete Removal?
Didgeridoohan said:
As long as you restore the stock boot image and keep the Magisk image intact, you'll have temporarily disabled Magisk and all your modules will still be installed and intact. Just flash the Magisk zip again to enable.
Easiest way to do this should be to use the "Restore Images" option when pressing "Uninstall" in the Manager.
Click to expand...
Click to collapse
Thanks! :good:
"...Easiest way to do this should be to use the "Restore Images" option when pressing "Uninstall" in the Manager." - That's what I did on Galaxy S5 SM-G900M (klteub) running Official 16.0 build 2019-03-04 klte + Open GApps ARM 9.0 Pico + Magisk v18.1 to temporarily disable Magisk so I could test an unofficial addonsu alternative.
Note that a manual reboot is required to disable Magisk after using "Restore Images" as the reboot is not automatic like when using Completely uninstall.
I have 2 questions:
I see that the 99-magisk.sh survival script is still in /system/addon.d/ so if I update the firmware would it restore Magisk & re-enable it?
I'm happy with the addonsu so would running the Latest Uninstaller from the Magisk thread completely delete 100% of the files installed by Magisk & the mods it made to the original setup & in /Data?
***
Hi, when i select the restore image option it says "stock backup does not exist" but i have it in root/data...
Today I have installed Built-In BusyBox module by zgfg to overwrite meefik's busybox binaries in /system/xbin which I couldn't remove due Resource or Device Busy error.
Then I found out that busybox is one of the ways to detect modified android so I want to remove it but module unfortunately doesn't come with uninstaller so I am stuck with busybox in my /system/xbin directory with no way to remove. All I found on Magisk's docs is to replace files or directories not remove them but 2018's version said that removal is possible, just that it is hassle or something.
Can anyone help?
Additional info: I don't have any Custom Recovery and don't tell me to get one.
Click to expand...
Click to collapse
NOTE! To help others with same problem I am planning to compile answer as Magisk Module so please open PR in this repo:
Click to expand...
Click to collapse
GitHub - UltraStudioLTD/BuiltIn-BusyBox-Uninstaller: Uninstall busybox
Uninstall busybox. Contribute to UltraStudioLTD/BuiltIn-BusyBox-Uninstaller development by creating an account on GitHub.
github.com
Have you tried removal via TWRP?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
lemon567 said:
Have you tried removal via TWRP?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
Click to expand...
Click to collapse
I don't have TWRP and I can't install any Custom Recovery.
Please don't tell me to follow that or this instructions to install them, I followed everything and still no luck.
What you could do is enter safmode of your phone (Google how to enter safe mode for your phone) and remove the files manually or use the BusyBox cleaner zip and flash it in magisk manager and if you're lucky it will remove it
Release v1.29.0-YDS-201807132149 · yashdsaraf/bb-bot
Bot to compile, package and release busybox for all android architectures - Release v1.29.0-YDS-201807132149 · yashdsaraf/bb-bot
github.com
Unfortunately safe mode in my phone is kinda broken, I think. Cause every 3rd party app was not only disabled but also disappeared like magic. Also I don't trust unknown ZIPs so I haven't tried that link.
**I solved problem by disabling every Magisk module I had, rebooting and after that it succeed in deletion with no problem**
Hello,
I stuck in quite specific situation. I am using OnePlus 7T Pro (HD1913) with installed the most recent stock Oxygen OS 12.1 MP2 - 11.F.17. EU (Android 12) and Magisk 25.2 (25200)(33) stable release.
What I did I used Magisk hide option and renamed package to random one. After this operation succeeded by mistake I uninstalled Magisk Manager from my device, and that was big mistake. Since I installed Magisk Manager from apk file once again it doesn't detect Magisk root installation anymore. In result installed apps for which there were granted root privileges when Magisk Manager properly detected Magisk Root installation (before hiding operation) still have root privilleges (e.g. Tasker, Total Commander in my configuration). Of course for new apps Magisk Manager behaves like there would be no root so it doesn't ask for granting root privilleges.
What can I do now to make Magisk Manager aware that Magisk root is installed in my system? Is there any way to achieve that (below there is some explanation why it is a bit tricky to root Oxygen OS 12.1 MP2)?
Below there are steps which I already done and some explanation why I cannot simply re-root my device with Magisk package with e.g. TWRP etc.
1. Currently there is no working TWRP compatible with Oxygen OS 12.1 MP2. Whenever I try to perform 'fastboot boot twrp.img' (and many other users confirm that in this forum) bootloader stuck and TWRP is not being loaded. I didn't found any resolution for that. This is the reason why I cannot simply reroot my device with Magisk package again.
2. I tried to extract 'boot.img' from Oxygen OS 12.1 MP2 firmware and used Magisk Manager to patch it. Unfortunately it didn't resolve the issue becasue after command 'fastboot boot patched_magisk_boot.img' Magisk Manager still doesn't detect Magisk root.
3. Before the whole described here issue occurred in order to root my device I had to use Magisk Manager with the last version of Oxygen OS working on Android 11 (rooted with Magisk) and performed patching to inactive slot directly from Magisk Manager just after installation (before reboot) of Oxygen OS 12.1 MP2. This is the only way which worked for me. This is the reason why I cannot simply perform this process again now because I would have to erase all my data / configuration and revert to the previous Oxygen OS.
Thanks
A new APP desktop shortcut will be generated after random naming. Please look for it on your mobile phone
Hi phidix, have you solved the problem? I got into exactly the same trap and still looking for a way out...
It looks like I found the solution.
First, I ensured that I had the latest stock ROM installed without any modifications. For that, I downloaded the official ROM and flashed it manually using the old system updater with the local upgrade option. Just to be on the safe side, I had repeated that twice, so both A and B slots eventually contained the same stock ROM.
Then I installed Cygisk, the same steps as for Magisk (I extracted boot.img from the firmware, patched it with Cygisk and flashed with fastboot).
Voilà, my phone reverted to being rooted.