Rooting (obtaining root access) on Android opens up the user with advanced system management options: from removing built-in applications to fine-tuning performance. However, along with the benefits come risks, from loss of warranty to security vulnerabilities. How can you determine whether your smartphone is rooted, especially if you bought it second-hand or suspect third-party interference?

This article will help understand the issue even for those who are far from technical nuances. We will look at visual signs, software verification methods (including hidden settings and specialized utilities), as well as hardware indicatorsthat indicate the presence of root. We will pay special attention to myths and misconceptions - for example, why the absence of an application SuperSU does not mean that the device is clean.

Important: some methods require connecting your smartphone to a computer or installing additional software. If you are not sure of your actions, it is better to contact a specialist - incorrect manipulations can lead to bootloader blocking or data loss bootloader lock or data loss.

1. Visual signs of rooted Android

The first thing worth checking is the external manifestations of root access. They are not always obvious, but some symptoms should alert you:

  • 🔍 Unknown applications in the menu: SuperSU, Magisk Manager, KingRoot or other utilities for managing superuser rights. Even if they are not in the main list, check hidden folders or application settings.
  • ⚙️ Non-standard items in menu: for example, option Developer Options → Root Access (if it is active) or section Superuser in settings.
  • 📱 Changed boot logo: on some firmware, after rooting, an unlocked lock (unlocked bootloader) or a warning about a changed system appears.
  • 🔄 Automatic OS updates are disabled: manufacturers often block OTA updates on rooted devices.

Pay attention to security breach reports when launching banking applications or services like Netflix, Google Pay. They may refuse to work on rooted devices due to requirements SafetyNet.

⚠️ Attention: Some custom firmware (for example LineageOS) imitate standard Android, but already contain built-in root. Check the firmware version in Settings → About phone → Build number.
📊 Have you ever rooted your smartphone?
Yes, I did it myself
Yes, but through the workshop
No, but I’m thinking about it
No and I’m not planning to

2. Checking through the developer settings

Hidden menu For developers may indicate the presence of root access, even if visually everything looks normal. To get there:

  1. Open Settings → About phone.
  2. Find the item Build number and tap on it 7 times in a row (a notification “You have become developer")
  3. Return to the main settings menu - a new section will appear there For developers.

Inside, look for the following indicators:

  • 🔓 Bootloader status: item OEM Unlocking enabled (on non-rooted devices it is usually disabled or absent).
  • 🛠️ USB debugging: if it is active without your knowledge, it is suspicious.
  • 📊 Item "Root Access": on some firmware you can see the current one here rights status (for example, Apps and ADB).

If the section For developers has already been activated before you, this does not necessarily mean root. But in combination with other signs, you should be wary.

💡

On some devices Samsung and Xiaomi the developer menu may be called differently: Developer options or Advanced → Accessibility.

3. Using specialized applications

The most reliable way is to install utilities that scan the system for the presence of root. Here are the top 3 proven tools:

Application What it checks Link (Play Market) Features
Root Checker Presence of subinary, access to /system joeykrim.rootcheck Simple interface, but may give false positives on some custom firmware.
Magisk Manager Status Magisk (popular rooting method) com.topjohnwu.magisk The application itself requires root for full operation, but even without rights it will show whether it is installed Magisk.
SafetyNet Test Passing tests Google SafetyNet com.scottyab.safetynet.sample If the test fails (ctsProfile: false), this indirectly indicates changes in system.

How to use Root Checker:

  1. Download and install the application from Google Play.
  2. Launch it and click Verify Root.
  3. If a message appears Root access is properly installed on this device! the device is rooted.
⚠️ Attention: some applications (for example, Titanium Backup) require root to work. If they are installed and functioning, this is a 100% sign of rooting.

Download Root Checker from the official store|

Launch the application and click "Verify" Root"|

Check the result (message about root status)|

Delete the application after checking (if not necessary)-->

4. Checking via ADB (for advanced users)

If you know how to work with the command line line Android Debug Bridge (ADB) will give the most accurate result. This method bypasses application restrictions and checks the system at a low level.

You will need:

  • 🖥️ A computer with ADB drivers installed.
  • 📱 Smartphone with USB debugging enabled (in the developer menu).
  • 🔌 USB cable (preferably original).

Instructions:

  1. Connect your phone to the PC and open the command line (cmd on Windows or Terminal on macOS/Linux).
  2. Enter the command to check the presence of su-binary: 
    adb shell "su -v"

    If you see the version in the response (for example, su: version 2.82), there is root.

  3. Check access to system folders: 
    adb shell "ls /system/bin/su"

    If the file exists, the device is rooted.

Additionally, you can check the status Magisk:

adb shell "magisk -v"
What to do if ADB does not see the device?

Make sure that:

1. USB debugging is enabled (Settings → For developers → USB debugging).

2. The correct drivers are installed (Windows may require Google USB Driver).

3. A high-quality cable is used (cheap cables often do not transfer data).

4. The USB port on the PC is working (try a different port).

If the problem persists, restart both devices and reconnect.

5. Checking the integrity of system files

Rooting often leaves traces in system folders. Even if root access have been removed, some files may remain. Check the following paths (via a file manager with access to the root or ADB):

  • 📁 /system/bin/su or /system/xbin/su - the main binary. root.
  • 📁 /system/app/SuperSU or /system/priv-app/SuperSU — folders with applications for rights management.
  • 📁 /data/adb/magisk — traces Magisk.
  • 📁 /cache/recovery —modified recovery (for example, TWRP).

If you cannot access these folders through standard Explorer, use FX File Explorer or Solid Explorer with root mode enabled (if available). An alternative is the ADB command:

adb shell "ls -la /system/bin | grep su"

Pay attention to the file modification dates. If they are significantly newer than the firmware release date, this may indicate interference.

⚠️ Attention: deleting files manually. (for example, /system/bin/su) without rolling back the firmware will not return the device to its original state. This can lead to bootloop (loop reboot).

6.

Some manufacturers build in physical indicators rooting into devices. For example:

  • 🔐 Bootloader status: on devices Samsung with Knox when the bootloader is unlocked, a flag Knox 0x1is triggered, which cannot be reset. Checked through boot mode (Download Mode): turn off the phone, then press Volume down + Power + Home (on new models - Volume up + down + USB-C cable).
  • 📱 Color indicator: on some Xiaomi and OnePlus when the bootloader is unlocked, the orange LED lights up when charging.
  • 🔧 Service menu: enter in dialer ##4636## (works on some devices *#06#), then go to Phone information. Item Bootloader status can show Unlocked.

On devices with Qualcommprocessors (most flagships) you can check the status via EDL mode (emergency boot), but this requires special equipment and knowledge.

💡

Physical indicators (for example, Knox status or LED color) are the only way to detect rooting if it was carefully “disguised” at the software level.

7. Online services and alternative methods

If If you don’t want to install applications or connect your phone to a PC, you can use online tools. They are less accurate, but sometimes they help:

  • 🌐 SafetyNet Test online: some sites (for example, safetynet.nekox.me) allow you to check the status SafetyNet through a browser Open the site on your phone and follow the instructions.
  • 📊 Check via Google Play: try installing an application that requires SafetyNet (for example, Pokémon GO or Google Pay). If the installation is blocked with an error The device is not certified, this is indirect. sign.
  • 🔍 Log analysis: applications like Logcat Extreme can show system logs, where sometimes there are mentions of su or magiskd.

Limitation of online methods: they often give false positives results on custom ROMs or devices with an unlocked bootloader, but without actual root.

⚠️ Attention: Some "root checks" on the Internet may be fraudulent and require installing suspicious APKs. Never download files from unreliable sources!

Frequently asked questions

Is it possible to hide root from banking applications?

Yes, with help Magisk and module MagiskHide (or its analogues in new versions). However, banks are constantly updating detection methods, so there is no absolute guarantee. An alternative is to use the second user space (Island, Shelter) to isolate applications.

If I remove SuperSU, will the phone become “clean”?

No. Removing the root management application does not cancel the superuser rights. You must also remove the binary su from the system folders and, preferably, flash the device with the official firmware.

How to check root on a phone without access to the settings?

If the phone is locked or on it. the screen is broken, but it turns on, connect it to the PC and use ADB commands (see section 4). If the device does not respond, the only option left is a hardware check (for example, via Knox on Samsung).

Can a virus root the phone without my knowledge?

Theoretically yes, but in practice this is extreme. It is unlikely. To obtain root, you need to unlock the bootloader, which is usually accompanied by warnings and data reset. Viruses can use already have root access, but not obtain them yourself.

How to completely remove root and return the warranty?

You need to:

  1. Delete all root applications and binaries (su, magisk).
  2. Return standard recovery (if installed TWRP).
  3. Reflash the device official firmware via Odin (Samsung), Fastboot or Mi Flash (Xiaomi).
  4. Lock the bootloader (if possible for your model).

Please note that on some devices (for example, with Knox), the rooting status may remain in the hardware flag, and the manufacturer will see it.