It's the icing on your cake (or whipped cream on your android pie) of desperation. You may not have had the easiest time to root your device, but you feel you have overcome all obstacles. It's only now that you find that those apps and mods you've rooted for still do not work. The characters indicate a lack of root access. Do not lose hope, because we have a few tricks up our sleeve.
If the problem is really a lack of root access, you either never really lost it, it's lost, a setting is down, it's undetected, something is broken for certain apps, or something is blocking your app. There is also the possibility that another problem exists (apart from the lack of root access). We review and review all scenarios and offer solutions. After all, root is only as useful as the apps you use it with-unless you're modifying files directly, but even then you're probably using a root access file explorer.
: Check Your Root Status
One reason your apps may not be able to access root is because it does not exist. Perhaps you followed our Magisk guide to the letter, but things still went awry. How do you really know if you do not look?
First, download the Root Checker app from joeykrim via the link below. Open it and tap Verify Root. Then click Grant when prompted to give the app superuser access. Then look for a message that says "Congratulations, root access is properly installed on your device!" If you receive this message, root will work on your phone, so it must be a problem with a particular app. In this case, go to step 4. If You Did not Receive Congratulations If the Root Checker has never asked you to grant superuser access, go to step 2.
Step 2: Make sure Magisk is not hibernating
If Root Checker did not give you that Congratulations! message, you probably are not properly rooted. However, before you go back to rooting, make sure that an app or mod does not damage the root management system.
If you use apps like Greenify, make sure the Magisk Manager is not in hibernation. If you're using apps that you need to hide from Magisk, such as For example, banking apps, turn off Magisk and close these apps when you're done.
If this is not the case, you need to redo the root problem. You probably already did this if you ever tried to become root, but to make sure, make sure you unlock the bootloader. If you need help with this part, we've covered the process for many popular modding phones:
Next, we recommend that you install TWRP for your recovery at the conclusion of the rooting process. You're then ready to go root with Magisk, which is easy by flashing a ZIP file into TWRP.
Sometimes installing Magisk fails because the custom restore you are using is outdated. If your device does not have a current version of TWRP (3.2.x or later), you can root using Magisk by patching your boot image.
You must have the current current firmware (ie the firmware version that matches your current build number). For Google devices, do this here . For OnePlus check here . For Essential, look here . If you're using a different phone, it's best to search the XDA forums for the latest firmware.
If you have a copy of your current firmware, extract the ZIP or TAR file and drag the file boot.img file. Save this file to your phone's internal memory for Magisk Manager to access. Then open the Magisk Manager, tap "Install" in the main menu, press "Install" again at the command prompt, select "Patch Boot Image File" and select the unzipped IMG file.
Magisk will patch the boot image to be created If you are using a rooted version, save this file in your phone's memory. Now all you have to do is transfer the patched boot image to your computer and flash it with Fastboot. This part is a bit complicated. See the link below for a complete solution:
Another method that sometimes you can uninstall, restart, and then reinstall the latest version of Magisk. Depending on your operating system, it may also be helpful to upgrade to an older version of Magisk. Normally this is not ideal. Updated versions fix bugs and introduce new features.
Step 4: Restart (The Ol & Cure-All)
Rebooting the device will solve all sorts of complaints, especially if it's the first reboot since the Magisk flashing. So do it now and when you get up again, check if root works. If not, see troubleshooting steps below.
. Some apps have internal settings that help them root access, or they can prevent root access. Take for example Ghost Commander File Manager. There are two different modes of operation: Normal and Root. All you need is root to optimize your system using Root, but that's probably why you're here. You can also use Ghost Commander to redeploy file systems.
Specially for Ghost Commander there are several ways to call the root mode. One is to prefix the file path using root: (d. H. root: / data ). You can also enable it from the Home screen by going to Settings -> Advanced -> Show advanced startup items. Another option is to use the tool button for access with a single keystroke.
Terminal emulator apps are a different type of app, typically one special command is required to enable root. You usually need to run "su" in the shell to use root. Unless you're explicitly asked if you want to give superuser access to an app, check the app's settings to make sure it's not requested by you. Most rooted apps are not shy, but sometimes they are also easy to miss.
ES File Explorer / Manager PRO is another app that requires manual activation of root. Press the menu key (top left, 3 lines) and tap on "Root Explorer".
Outside of our three examples, there are many other apps that do not request root by default. To make sure this is not your problem, go to app settings and check all options thoroughly.
Step 6: Check Magisk Manager Superuser Privileges
Did you know that Magisk Manager has a section of its settings made sure that certain apps are granted root access? Even if these are old messages, try switching any app you're having problems into in the list of apps with superuser access. Scroll down the Magisk settings and make sure these superuser settings are set up correctly.
You can configure the Magisk Superuser Settings section to your preference, but the default settings are as follows: Superuser Access: Apps and ADB; Multiuser mode: Only the owner has root access. Mount Namespace Mode: Root sessions inherit the namespace of the requester. Automatic answer: prompt; Request timeout: 10 seconds; Superuser notification: toast.
Some apps find it hard to find the root directory through Magisk because they search the superuser binaries at a specific location. The best solution to this problem is to simply update the app. As more and more people use systemic roots, more and more rooted apps are adapting. If you're already using the latest version of the app, contact the developer for assistance, or look for an alternate app that has recently been updated.
You can think of this next troubleshooting tip as a safe mode from Magisk. To make sure that a module does not cause problems with root access, go to the Modules section of the page menu of Magisk Manager. Then disable all modules and restart the computer. If root works while restoring, re-enable the modules one at a time and restart them after each reboot until you find the culprit.
Alternatively, in the Magisk Manager settings, you can find the "core-only mode" or "if" You can not boot, you can set a file named ".disable_magisk" in / cache (/ data / cache on some Devices). This is a good approach if you already know that a particular module is causing your root problems. It helps you uninstall the troublemaker.
If you detected in step 8 that your problem was due to an app that was looking for an incorrect application for the non-root system Magisk binaries look for another option for another application
You can place a pointer or path to SU by creating a symbolic link. This can be achieved by using an Android terminal emulator to insert the symlink, but MagiskHide will probably fail as SU is now exposed. As an alternative, XDA senior member Laggardkernel developed a Magisk module that can do this systematically. This destroys SafetyNet. The module can be flashed either in the Magisk Manager or via a custom recovery, and you can retrieve it at the following link.
However, I had trouble flashing, and it seems like there was only support for Magisk V12. So you may just have the first opportunity to insert the symlink itself, which in my opinion breaks off too much from the functionality of Magisk.
Step 10: Handle incorrect implementation of F2FS
If your device is not being used F2FS (Flash-Friendly File System) does not require this step. If this is the case, it is possible that the file system will break root by preventing Magisk from being mounted at boot time.
There are several ways to solve this problem, but the most efficient way is to find a new kernel without a file system. Another, sometimes more problematic, approach is reformatting your / data partition as ext4. If you choose this route, you can use the TWRP wipe option. It's just that some devices designed to use F2FS have problems booting as ext4.
For most standard cores, ADB (Android Debug Bridge) will only run in safe mode, even if rooted. This makes it difficult to access root when you use ADB to run commands on Android from your desktop. With the (root) ADBD Insecure app, you can run ADBD (Android Debug Bridge Daemon) in "insecure mode", so that you can access system files and directories, for example, by running the "adb push / pull" command or your system partition create writable with "adb remount". The daemon is the access to the shell.
ADBD Insecure can be installed from the Google Play Store or you can simply search for it by name in your Play Store app. You must enable USB debugging. Make sure your developer options are turned on by tapping Settings -> Phone, then tapping Build Number seven times quickly.
Step 12: Install Magisk SELinux Manager
This is a way to extract the big guns, and it can be just as risky as if you were taking that word literally. Android uses a principle called Security-Enhanced Linux (SELinux for short) to ensure security. By default, any request to the operating system that is not explicitly allowed is denied. Software runs only with minimal rights and offers some damage control against attacks or incorrect processing. Depending on the root app, SELinux can prevent the desired actions from being performed.
SELinux has two modes: permissive and enforce. In permissive mode, SELinux logs policy violations, but the event is not blocked. Enforcement mode logs and blocks any action that violates the SELinux policy. XDA Junior Member Jman 420 has found a way to enable SELinux permissive mode at boot, which can help with your root crisis, but can also be a risky endeavor.
For one thing, he's set your own. Aside from the fact that there are some tools and apps that are known to be bad or do not work in forced mode at all. For many people, the roots are far too risky. For others, the best things in life involve at least some risk.
Magisk root has many advantages over traditional rooting methods, but if your apps can not access it, it does not feel particularly advantageous. After all, one supposed benefit of Magisk is that rooting and then using root is easy. However, with a variety of devices, systems and apps, many variables play a role – and many potential problems. If you have other ways to resolve issues with apps that use root to access Magisk, let us know in the comments section.
Do not Miss: 8 Must-Have Magisk Modules for OnePlus Phones