Bingblop/ADB-Root-Toolbox v7.21.0

ADB Application Manager Pro v7.21.0

on GitHub

A feature release on top of v7.20.0, cut from main, with the tab the owner asked for on 2026-10-30: an app firewall. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. Nothing in it has been run on a phone yet: the page was checked in a headless browser with a mock phone, the rule scripts by the Java suite (including sh -n on every script) and a build against Android 34. docs/PHONE-SCRIPT-v7.21.0.md is the check.

• Android Firewall, a new tab (two lines on the tab bar, Firewall on the bottom bar, right after Custom Fonts; on out of the box, not pinned to the bottom bar). For every app you decide whether it may use Wi-Fi and mobile data, and with the columns turned on in Options, roaming, a VPN, your LAN or Tor: what AFWall+ does, written for this app. The rules go into the kernel's own packet filter (iptables and ip6tables), so a blocked app cannot get out whatever it tries, and no service of this app runs in the background. It needs Super User, or Shizuku running as the system user (UID 1000) or as root (UID 0); the ADB shell user may not write kernel rules, so without one of those the tab is locked with a box that says why and a Set Up button, and nothing else changes.
• Allow list or block list. An allow list (the default, the safer one) lets out only the apps you tick and stops everything else; a block list stops the apps you tick. In an allow list this app and Android's DNS resolver are pre-allowed unless you untick them yourself, and an allow list with almost nothing ticked is asked about once before it is applied.
• One row per app, one round cell per network. Icon, name, package and UID; two apps that share a UID are one row. Chips filter the list (Use the internet, User apps, System apps, Special, Ticked, All) and the search box finds a row by name, package or UID. A tap on a column's head ticks every row shown. Special rows for what is not an app: the Linux kernel, Root (UID 0), Android system (UID 1000), the DNS resolver, media, VPN networking, DRM, mDNS, GPS, 464XLAT, shell and more, each with a line that says what breaks when it is blocked.
• Profiles: up to twelve rule sets (home, work, travel) with their own ticks; the mode and options are shared. New profile (empty or a copy of the current one), Rename, Delete; switching profiles while the firewall is on applies the new one at once.
• Options: Roaming, VPN, LAN and Tor columns; IPv6 too; Log stopped connections; Drop instead of reject; Block new inbound connections; Block tethered devices; Re-apply when the network changes (roaming starts or ends); Apply on boot with a delay (15 seconds out of the box), which runs the last applied script again through su after each restart; and a card for your own iptables lines before and after this app's rules.
• Log, Active rules, Backup. The Log card reads what the kernel stopped, grouped by app, newest first, with the last destination; Clear log empties dmesg and asks first. Active rules shows this app's chains as iptables prints them, with Copy. Backup saves or shares one JSON file with the mode, the options and every profile, by package name so it works on another phone; Import asks whether to replace your profiles or add the file's next to yours.
• The state is what the kernel reports. After every Apply the app reads the tables back and counts the rules of every chain against the set it sent: the chip reads OFF, ACTIVE, NOT APPLIED, NO IPTABLES or LOCKED from what it found, a line that iptables refuses is named in the status line, and a set that did not take in full is reported as not applied rather than ACTIVE. The apply never leaves a gap: the new rules are built beside the ones in force and swapped in only when complete, so a blocked app stays blocked while the rules change. The boot script checks that Apply on boot is still on after its delay before it writes anything.
• Saved Applications get a Firewall button on every card (and the tab's own Saved list button opens the same choice): Block these apps, Allow these apps or Forget their rules for every app of the list at once, in the current profile. Block and Allow mean the right thing for the mode you are in.
• Root Features has an Android Firewall row whose Open tab brings you to the tab; locked like the other rows until a privileged mode is the working mode.
• Remove all firewall rules (the red card at the end of the tab): press and hold to delete every chain this app made, for every profile and both IP families, and turn Apply on boot off. Your profiles stay saved. The guide's Android Firewall and Undoing the firewall sections explain the risks (an allow list blocks first, the special rows that carry the phone, Apply on boot after a wrong rule set) and the three ways back, including the iptables commands by hand and the boot file to delete.
• Every new text in all 14 languages.