Root File Manager for Android — Full System File Access

AnExplorer gives full root access to advanced Android users. Browse, copy, move, rename, and edit files in every protected partition of your device — /system, /data, /cache, /vendor, and more.

What Root Access Unlocks

How AnExplorer Handles Root

AnExplorer detects root access automatically. When you navigate to a restricted path, it requests the su permission from your root manager (Magisk, SuperSU, KingRoot). You grant it once per session.

Modifications are done safely:

• System partition is remounted read-write before writing, then read-only immediately after
• Dangerous operations (delete /system/framework/...) prompt a confirmation
• Root operations are logged in the session for review

Common Root Use Cases

Edit /etc/hosts — System-Level Ad Blocking

Replace/append entries in the hosts file to block analytics domains and ad networks at the network layer. AnExplorer's Text Editor opens the file with root write access.

Edit /system/build.prop

Change device fingerprint, DPI, screen density, or enable hidden developer options. AnExplorer makes a backup copy before saving.

Browse App Private Data

Open /android/data/com.example.app/ to inspect databases, shared preferences, and cache files. Useful for developers debugging installed apps.

Silent APK Install/Uninstall

The APK Installer can silently install APKs and remove system bloatware without Android's confirmation screen when root is available.

Copy System Fonts or Ringtones

Add custom fonts to /system/fonts/ or custom ringtones to /system/media/audio/ringtones/ — changes survive app Restarts.

Backup App Data

Copy the entire /android/data/[package]/ folder before a factory reset to preserve app data (logins, game saves, configs).

ADB Root Access (No Physical Root Required)

AnExplorer supports ADB-based root for devices that have ADB debugging enabled but are not Magisk-rooted. This gives elevated file access without modifying the device's system partition.

How ADB Root Works

ADB root (adb root) restarts the ADB daemon with root permissions. AnExplorer can then:

• Browse normally restricted paths (e.g. /android/data/, /data/app/)
• Read and copy protected files
• Run commands with elevated privileges

Requirements: Developer Options enabled, USB Debugging or Wireless Debugging on, and the device must allow adb root (most stock production builds disable this; AOSP emulators and developer/engineering builds allow it).

WiFi ADB Root

Android 11+ supports wireless ADB pairing:

1. Enable Developer Options → Wireless Debugging on the device
2. Open AnExplorer → Tools → ADB Connect → pair via IP:port and pairing code
3. AnExplorer negotiates ADB root session automatically when the device permits it
4. Navigate to restricted paths — AnExplorer requests elevated access transparently

USB ADB Root

1. Connect device via USB and trust the host PC
2. Ensure USB Debugging is enabled
3. AnExplorer detects the connection and escalates to ADB root if the device allows it
4. Browse /android/data/, /system/, or other restricted paths

ADB Root vs Magisk Root

Supported Root Managers

• Magisk (recommended — systemless root)
• SuperSU
• KingRoot
• Any SU binary at standard paths
• ADB root — via USB or WiFi ADB (developer/engineering builds; no Magisk required)