Dear XDA,
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.
Already have tried:
Disabling power optimization entry for MagiskManager
Reinstall Magisk using MagiskManager
What might be the reason of no prompt issue?
Why not AddonSU: this addon disables some applications to use such as Bank or GooglePay which are important here.
Why not SuperSU: is it worth to tell why?
Thank you very much for any working suggestion.
Related
When i launch magisk manager 5.8.3 or 5.9.1, it requires updating the version of magisk. Almost all modules require a version higher than 17. Phone "zte blade v9". Twrp does not decrypt userdata. I can install magisk 16.0 - 16.7 any version.
How i can install magisk 18 or 19?
No logs in adb logcat. Phone reboots after logo.
Sorry if this problem has already been discussed.
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
SOLVED
I just learned, addonsu is no longer supported by LOS 17.x
Magisk is the way to go
mod can delete this question if desired
I put LOS 17.1 on my G7plus and installed addonsu-16.0-arm64 via adb sideload.
After rebooting I see no root option in the developer options, nowhere anything about root...
installing addon-su-16.0 succeeded, there was no error message...
What could have gone wrong or what am i missing?
Thanks
papperlapapp said:
Hi there,
I put LOS 17.1 on my G7plus and installed addonsu-16.0-arm64 via adb sideload.
After rebooting I see no root option in the developer options, nowhere anything about root...
installing addon-su-16.0 succeeded, there was no error message...
What could have gone wrong or what am i missing?
Thanks
Click to expand...
Click to collapse
They removed addonsu for LineageOS 17.
LineageOS is dropping its own superuser implementation, making Magisk the de facto solution
Yes, I read it now.
The only way now is Magisk.
have installed Magisk now according to
Installation
The Magic Mask for Android
topjohnwu.github.io
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.