Obtaining root access (or “root”) on Android gives the user access to system files, hidden settings and advanced customization options. However, such rights not only give freedom, but also create risks: from loss of warranty to vulnerability to malware. If you bought a used smartphone, installed custom firmware, or simply suspect that root is activated on the device, it is important to check this.

In this article we will look 7 reliable methodshow to determine whether you have root access on Android, including methods without installing additional applications. You will learn what signs indicate a “rooted” device, how to use ADB-commands and specialized utilities, as well as the dangers of hidden root (for example, through Magisk). The instructions are relevant for all versions of Android - from Android 10 to the latest Android 15.

We warn: some methods require technical knowledge. If you are a beginner, start with simple methods (sections 2–3) and only then move on to advanced ones (sections 5–7).

1. Visual signs of root access

Before delving into technical details, inspect the device for obvious signs of root. They do not give a 100% guarantee, but they can alert you:

  • 🔧 Unknown applications in the menu: SuperSU, Magisk Manager, KingRoot or other utilities for root management. Their presence is a direct sign.
  • ⚙️ Changed settings menu: additional items like Developer Options → Root Access or Superuser Permissions.
  • 📱 Custom firmware: if names are specified in Settings → About phone like LineageOS, Pixel Experience or MIUI Global (Unlocked).
  • 🔄 Lack OTA updates: rooted devices often do not receive over-the-air updates due to changed system files.

Pay attention to security messages when launching banking applications (for example, SberBank Online or Tinkoff). Many of them block work on devices with root, issuing a warning like: "The device is not certified. Signs of root access detected".

⚠️ Attention: Some custom firmware (for example, CalyxOS or GrapheneOS) mask root access, but at the same time provide a high level of security. If you use such software, visual signs may be missing.

2. Checking through the Root Checker application

The easiest way is to install a specialized utility. Root Checker from the developer joeykrim (available in Google Play) analyzes system files and gives a clear verdict. How to use it:

  1. Download and install Root Checker from the official store.
  2. Launch the application and click "Check root" ("Verify Root").
  3. Wait for the result. If a green checkmark appears and the message "Root access properly installed!" —there is root.

The application also shows superuser version (for example, Magisk v26.4 or SuperSU 2.82) and the path to the binary file (/system/bin/su or /sbin/su). If the root is hidden (for example, through MagiskHide), Root Checker it may not detect it - in this case, proceed to the following methods.

💡

If Root Checker does not detect the root, but you suspect its presence, try rebooting the device and running the scan again. Some modules (for example, Magisk) are activated only after a reboot.

3. Checking through the Android terminal (without a PC)

If you do not want to install additional applications, use the built-in terminal. To do this:

  1. Install any terminal application, for example, Termux (from Google Play or F-Droid).
  2. Run it and enter the command: 
    su

    If an input prompt appears (# instead of $) - there is root. If you see a message "Permission denied" —no rights.

  3. For additional checking, run: 
    id

    The response must contain a string uid=0(root).

This method works even on devices with a hidden root (for example, through Magisk), as it checks for the presence of a binary file su directly. If the terminal displays an error "command not found", it means that the file su has been deleted or renamed.

Enter the command su and check the prompt|Execute id and find uid=0(root)|If the commands do not work, there is no root

-->

4. Using ADB for deep diagnostics

If the previous methods did not work, connect the device to the computer and use Android Debug Bridge (ADB). firmware.

Instructions:

  1. Install ADB on PC (for example, via Platform Tools from Google).
  2. Activate USB debugging in the settings developer (Settings → About phone → Build number (press 7 times) → For developers → USB debugging).
  3. Connect your phone to the PC and enter in the command line: 
    adb shell

    su

    If after the command su the invitation has changed from $ to # the root is confirmed.

  4. To check hidden root (Magisk) do: 
    adb shell

    magisk --version

    If the version is displayed (for example, 26.4) - the root is installed through Magisk.

This method also allows you to check status SafetyNet - Google's security system, which blocks rooted devices in banking applications. To do this, enter:

adb shell

su -c "magiskhide props"

⚠️ Attention: On some devices (for example, Samsung s Knoxthe use of ADB may trigger the security trigger, even if there is no root. check, disable Knox in the settings or use alternative methods.

5. Checking system files manually

Root access leaves traces in system folders. You can find them using any file manager with access to the root directory (for example, Solid Explorer or FX File Explorer). Look for:

  • 📁 File /system/bin/su or /system/xbin/su —the main sign of root.
  • 📁 Folder /magisk or /sbin/.magisk — indicates Magisk.
  • 📁 Files with rights rwsr-sr-x (for example, /system/bin/.ext/.su) - masked binaries.
  • 📁 Folder /data/adb/magisk — modules are stored here Magisk.

If you find these files, but applications like Root Checker do not detect the root, it means it is hidden using MagiskHide or similar tools. In this case, use ADB (section 4) or specialized utilities like Magisk Manager.

How to enable the display of hidden files in the file manager?

In most file managers (for example, Solid Exploreryou need to go to the settings, find the "View" or "Display" section and activate the "Show hidden files" option (Show hidden files).In FX File Explorer this is done through the menu ⋮ → Settings → Display → Show hidden files.

6. Checking through SafetyNet and banking applications

The system scans the device for modifications, including root. If it identifies the device as unsafe, many applications. (banks Google SafetyNet scans the device for modifications, including root. If it detects a device as unsafe, many applications (banks, Google Pay, Netflix) refuse to work. How to check:

  1. Install the application SafetyNet Test (for example, SafetyNet Helper Sample from Google).
  2. Run the check If status ctsProfile or basicIntegrity — false, the device is rooted or modified.
  3. Try to install a banking application (for example, SberBank or VTB OnlineIf it gives a certification error, this is an indirect sign of root.

Important: some custom firmware (for example, CalyxOS) pass SafetyNet, despite the presence of root, thanks to built-in masking mechanisms. If you need accurate confirmation, combine this method with checking through ADB or terminal.

Application/Service Behavior on a rooted device Behavior on a clean device
Google Pay Refuses to work or asks to reset settings Works without restrictions
SberBank Online Gives the error "The device is not certified" Starts without warning
Netflix Limits video quality to 480p Full HD and higher available
Pokémon GO Blocks input with a message about a changed device Works normally

7. Alternative methods: check via recovery and bootloader

If all the previous methods did not work, check recovery i bootloader. These are advanced methods that require caution:

  • 🔄 Checking recovery:
    1. Turn off the device.
    2. Hold down the button combination to enter recovery (for example, Power + Volume Up for Samsung or Xiaomi).
    3. If instead of the standard menu you see TWRP, OrangeFox or another custom recovery, root is almost certainly installed.
  • 🔧 Checking the bootloader:
    1. Connect the device to the PC and enter in ADB: 
      adb reboot bootloader
    2. In the bootloader, check the status Device State. If indicated unlocked the device is unlocked, which often means the presence of root.

      3. Please note: unlocked bootloader does not always mean root, but almost all rooted devices have an unlocked bootloader. The exception is some methods of rooting without unlocking (for example, through exploits), but they are rare and unstable.

      Yes, itself installed|Yes, but through a wizard|No, but I want to try|No and I don’t plan to|I don’t know what it is-->

      💡

      If a custom recovery is installed on the device (for example, TWRP), this is almost guaranteed to mean root access, even if system checks do not detect it.

      FAQ: Frequently asked questions about checking root access

      Is it possible to determine the root if it is hidden through MagiskHide?

      Yes, but standard applications like Root Checker may not work. Use:

      • Command su V ADB or terminal.
      • Checking files /magisk or /sbin/.magisk.
      • Specialized utilities like Magisk Manager (if installed).

      MagiskHide masks the root from applications, but not from direct system requests.

      Why don't banking applications work if there is no root?

      Possible reasons:

      • The device has unlocked bootloader (even without root it can trigger SafetyNet).
      • Installed custom firmware without root (for example, LineageOS without Magisk).
      • Triggered false trigger due to modified system files (for example, after removing built-in applications).

      Check the status SafetyNet via the app SafetyNet Test.

      How to remove root, if it is detected?

      The method depends on the rooting method:

      • For Magisk: go to Magisk Manager and select Uninstall → Complete Uninstall.
      • For SuperSU: in in the application settings, find the option Full Unroot.
      • For custom firmware: reflash the device to stock firmware via Fastboot or Odinh (for Samsung).

      After removing the root, you may need factory reset for recovery SafetyNet.

      Is it possible to get root without unlocking the bootloader?

      Technically yes, but this is rare. Some exploits (for example, DirtyCOW or KingRoot) install root without unlocking, but:

      • Such methods often are unstable and break after the update.
      • They can violate SafetyNeteven if the bootloader is locked.
      • Modern devices (starting from Android 10) are almost not susceptible to such exploits.

      On most devices, unlocking the bootloader is a mandatory step.

      What is the danger of hidden root (for example, through Magisk)?

      Hidden root is masked from applications, but does not eliminate the risks:

      • 🛡️ Vulnerability to malware: root gives apps unlimited access to the system.
      • 📱 Loss of warranty: even if the root is hidden, the manufacturer can detect modifications during diagnostics.
      • 🔄 Problems with OTA updates: system updates can break the device if incompatible modules are installed.
      • 💳 Blocking financial services: banks and payment systems (for example, Google Pay) can detect root through SafetyNet.

    If you need root for specific tasks (for example, backup via Titanium Backup), consider alternatives like ADB Backup or cloud backups.