On non-rooted Android 17, ADB uninstall of system apps fails

Original Article ↗ Hacker News Discussion ↗

Android 17’s move to block ADB-based uninstallation of system apps on non-rooted phones is being read as another step toward locking down smartphones and limiting user control. Commenters weigh the trade-offs between security, app piracy, and true device ownership, noting that “disabling” bloatware is often reversible and less effective than removal, while Google’s attestation and integrity mechanisms further entrench its ecosystem. Alternatives such as GrapheneOS, Linux-based mobile OSes, and EU regulation are raised, but many argue these options remain niche and do not yet solve the underlying dependence on tightly controlled platforms.

Android 17 Change: ADB “Uninstall” Now Just Disables System Apps

  • The change prevents full removal of system apps via ADB on non‑rooted devices; they are now disabled instead.
  • Some note this is technically how things already worked for apps in read‑only system partitions (removal only from /data, falling back to the built‑in version).
  • Others see it as another step in tightening control and limiting user ability to debloat OEM and carrier bloatware.

User Ownership vs Vendor Control

  • Many frame this as part of a broader “war on general‑purpose computing” and on users truly owning their devices.
  • Critics argue that without root and bootloader freedom, users are effectively “renting” devices under HOA‑style rules.
  • Opposing comments note that devices can still be configured extensively via Settings and that root is not strictly required for device purpose.

Debloating Strategies and Tools

  • Some suggest pausing OS updates to preserve current debloating capabilities, despite security risks.
  • Tools like Shizuku, Canta, Hail, and ShizuTools are discussed as “pseudo‑root” ways to disable/freeze system apps; concern that if ADB is restricted further, these may break as well.
  • There is debate over whether disabling apps is functionally equivalent to uninstalling, especially regarding background activity and privacy; some behavior is described as unclear.

Security, Root, and App Piracy

  • One side argues root access is a major liability for average users, enabling malware and weakening security guarantees that banking and payment apps depend on.
  • Others counter that root is controllable (explicit prompts) and that removing it is a power grab, not a necessity.
  • App piracy is discussed: Android is seen as easier to crack and sideload apps on, affecting some developers’ willingness to target the platform; others say the real difference is market demographics, not platform tech.

Alternatives, Attestation, and Regulation

  • Custom ROMs (GrapheneOS, LineageOS, pure AOSP) are presented as ways to avoid bloat, though they don’t solve the “can’t install any OS on any phone” problem.
  • Hardware attestation (Play Integrity, device attestation) is seen by some as user‑hostile control; others view it as valuable for secure key storage and anti‑fraud.
  • EU policy and sovereignty are debated: some want EU‑backed open platforms; others argue governments would likely build equally or more surveillant systems.
  • Linux phones (postmarketOS, Sailfish, PinePhone) are mentioned as promising but currently limited by power management, hardware support, app compatibility, and lack of OEM backing.