How to Give SuperUser Root Access to Apps via APatch

SuperUser Root Access APatch

SuperUser Root Access APatch

In this guide, we will show you the steps to give the SuperUser root access to apps via APatch. When it comes to getting elevated privileges, then Magisk was [or rather still is] the go-to choice for the masses. With the ease of flashing modules, the ability to patch boot/init_boot in just a couple of clicks, and the ability to retain root even after installing OTA, this open-source rooting solution has been ruling the charts for quite some time.

However, over the past few months, we have seen the introduction of numerous other players in this domain. From the likes of the unofficial fork of Magisk aka Kitsune, to the ones who grant root permission to applications directly in the kernel space such as KernelSU and APatch, these players are making quite a name for themselves. In this regard, I recently decided to make a switch from Magisk to APatch and the initial rooting process went quite smoothly.

However, then I realized something strange was happening with all the rooted apps. Irrespective of the app I launched, they straightaway raised a false positive that my device wasn’t rooted, even though that wasn’t the case as I double-checked via APatch and it clearly stated that rooting has been achieved successfully. So what exactly is going on here and more importantly, how to rectify this issue, or in other words, give the SuperUser root access to apps via APatch? Let’s find out.

How to Give SuperUser Root Access to Apps via APatch

Let’s turn back the clock a little bit, shall we? When you have obtained root via Magisk, then as soon as you launch a rooted app, you are straightaway greeted with the SuperUser prompt. You then have to just tap on Grant and that app will then get administrative privileges. However, after rooting the device via APatch, that SU prompt was not appearing for any app whatsoever.

So I did some further debugging of the issue and found out that we have to manually grant it the SuperUser request from the APatch, the auto prompt will not appear under any situation. So without any further ado, let’s show you the steps to manually invoke this prompt.

  1. Download and install the desired root app.
  2. Then launch APatch and go to SuperUser.SuperUser Root Access APatch
  3. Now enable the toggle next to the root app.
  4. Launch that app and it will now have root.

That’s it. These were the steps to give the SuperUser root access to apps via APatch. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution as soon as possible.

Magisk Handles SuperUser Better Than APatch

It goes without saying that Magisk tends to handle the entire SU scenario much better than APatch or even KernelSU for that matter. This is because as opposed to APatch, you don’t have to launch Magisk and grant each app SU access, instead as soon as you launch any rooted app for the first time, you will automatically be greeted with that prompt, and you a simple tap on Grant or Deny [though you always have the option to get this job done via the Magisk app as well].

SuperUser Root Access APatch

On the other hand, when it comes to APatch, you’ll always have to minimize the root app, go to APatch’s SuperUser tab, enable the toggle next to the desired app, and then come back to the app [though all this is required just for the first time usage, still, it’s quite a lengthy approach nevertheless].

Leave a Reply

Your email address will not be published. Required fields are marked *