Fix DroidGuard UNKNOWN_INSTALLED with BetterKnownInstalled

BetterKnownInstalled (BKI) is a Magisk/KernelSU/APatch module that edits your device’s packages.xml to fix DroidGuard UNKNOWN_INSTALLED flags; it requires root and careful backups because improper restores can brick a device.

This guide explains what BetterKnownInstalled (BKI) does, why you might need it, what you must prepare, how to download and install it, how to use it safely, and common questions and warnings. The language is simple and step‑by‑step so you can follow along.

BetterKnownInstalled
BetterKnownInstalled

What is BetterKnownInstalled

BKI patches packages.xml and clears packages-warnings.xml so Google’s DroidGuard (Play Integrity / Play Protect) recognizes apps as legitimately installed instead of UNKNOWN_INSTALLED. It changes installer attributes to com.android.vending and adjusts package source flags to reduce false warnings.

Key features

  • Sets installer, installInitiator, installerUid to Play Store values.
  • Removes problematic attributes like installOriginator, isOrphaned, and installInitiatorUninstalled when needed. 
  • Cleans packages-warnings.xml by resetting it to an empty <packages />. 
  • Includes abx2xml/xml2abx binaries for converting binary XML formats.

Requirements

  • Rooted Android device with Magisk, KernelSU, or APatch support. 
  • ADB access and a working recovery (TWRP or stock) for restores.
  • Enough free storage and a full backup of /data/system/packages.xml and /data/system/packages-warnings.xml before any change. Do not skip backups.

Download

Get the module from its official GitHub repository (search for Pixel-Props/BetterKnownInstalled). Download the latest release zip to your device. 

Install (step‑by‑step)

1. Backup first

  • Use ADB or a root file explorer to copy /data/system/packages.xml and /data/system/packages-warnings.xmlto a safe location. This is critical.

2. Install module

  • In Magisk Manager (or KernelSU/APatch installer), install the BKI zip and reboot.

3. Verify

  • After reboot, check Play Integrity or the app that showed UNKNOWN_INSTALLED. If issues persist, restore backups from recovery. 

Using and maintenance

  • The module runs at boot and edits the system files automatically.
  • Keep the module updated from GitHub.
  • If you uninstall, restore your original backups from recovery rather than manually copying files while the module is active improper restores have caused bootloops for some users.

FAQs

Will this make my device unsafe?

It modifies installer metadata to mimic Play Store installs; this is a targeted fix, but it may not guarantee every app’s Play Protect verdict.

I restored backups and now my phone bootloops help.

This has happened to others. If you face a bootloop, use recovery or fastboot to restore the original files or reflash a known good backup. Avoid manual file swaps without recovery.

Risks and warnings

  • High risk if you skip backups.
  • Possible incompatibility with future Google checks; results are not guaranteed. 

Credits and further reading

  • Project: Pixel-Props / BetterKnownInstalled (GitHub). 

Ending

If you want, I can produce a concise checklist you can copy to your phone before starting (backup commands, exact file paths, and verification steps).

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top