Where Does AdAway Store the Hosts File?
AdAway writes its blocklist into the system hosts file at /system/etc/hosts. Preferences stay in its private sandbox.
Last updated
AdAway works by replacing one system file. Enabled blocklists compile into /system/etc/hosts, and every app on the phone inherits the blocks. That is why it needs root on classic mode.
The hosts file is shared infrastructure, not app data. Uninstalling AdAway without disabling first leaves the modified file behind. Preferences and sources sit separately in the private sandbox.
Where AdAway stores this, by platform
/system/etc/hosts
Compiled blocklist. Every lookup on the phone reads this file. Restore the stock copy by disabling AdAway before uninstall.
/data/data/org.adaway
Sources, allowlists, and preferences. Needs root to browse. The hosts file above is the operational half.
Frequently asked questions
How do I fully remove AdAway blocking?
Open AdAway and disable it, which restores the stock hosts file. A leftover file breaks name resolution long after uninstall, so always disable first.
Does AdAway need root?
Yes, root is required. AdAway remounts /system to rewrite hosts. The VPN-based local-hosts mode on newer builds avoids system writes but still filters locally.
Where do custom block sources go?
Add them in AdAway sources settings. The merged result compiles into hosts on next apply. Custom allow and block entries live in preferences.
Notice an outdated path? Let us know.