4 Ways to Install Apps on BoxPhone — What People Actually Use

How app installation works

Android allows two install paths:

1. Through a Store — like Play Store or Aurora — the system handles updates for you
2. Sideload an APK — install the file directly, no Store involved. You first need to enable “Install from Unknown Sources”.

On BoxPhone we mix both approaches depending on whether the device is logged into Google.

The 4 methods we actually use

1. Play Store (Official)

The standard route — log in with a Google account and install directly from Play Store.

Best for: Devices already logged into Google that need automatic updates.

Drawbacks:

• Every device must be logged into a Google account
• Every install is tied to the account — Google sees the farm-level pattern
• Some apps are region-locked — you'd need to switch the Google account region

2. Aurora Store (no login required)

Aurora Store is an open-source Play Store client — it uses an anonymous Google account so you can download apps without logging in on the device.

Best for: BoxPhone deployments that don't want to attach Google accounts but still need Play Store apps.

Installation:

1. Download the Aurora Store APK from auroraoss.com
2. Enable "Install from Unknown Sources"
3. Install Aurora Store
4. Choose "Anonymous" on first launch
5. Download apps as needed

Pros: Reaches almost every Play Store app without a login or account tracking.

3. APK Sideload from trusted sources

Download the APK directly from a website and install it — useful for apps not on Play Store or when you need a specific version.

Trusted APK sources:

• APKPure — signature verification, doesn't modify APKs
• APKMirror — signs every APK, mirror of Play Store releases
• F-Droid — open-source app repository

Warning: Don't download APKs from unknown sources — modified APKs may carry malware.

4. XAPK — the easiest path for apps with OBB / Split APKs

XAPK is a single-file format bundling APK + OBB data + split APKs (architecture, language, density). It's the right choice for large apps such as games, apps with separate data files, or apps that Play Store breaks up into multiple split APKs.

Pros: One download, no manual OBB copy into /sdcard/Android/obb, and it covers every split the device needs.

Important: XAPK is not a regular APK — you can't install it with adb install directly. It needs a special path.

Installing XAPK on BoxPhone:

Method A — Using APKPure / APKMirror Installer App (easiest)

1. Install APKPure App or APKMirror Installer on the device (sideload it as a regular APK first)
2. Copy the .xapk file onto the device
3. Open APKPure App → select the file → tap Install. The app extracts the XAPK, installs every split, and places the OBB automatically.

Method B — Extract XAPK manually and install via ADB (for batch installs)

An XAPK is just a ZIP — rename it to .zip and unzip to get:

• base.apk — the primary APK
• config.arm64_v8a.apk / config.xxhdpi.apk / config.en.apk — split APKs
• Android/obb/<package>/*.obb — data files (if any)
• manifest.json or icon.png — metadata

Install all split APKs together with install-multiple:

# unzip xapk
unzip app.xapk -d app_extracted

# install all split apks in a single command
adb install-multiple -r \
  app_extracted/base.apk \
  app_extracted/config.arm64_v8a.apk \
  app_extracted/config.xxhdpi.apk \
  app_extracted/config.en.apk

# push OBB (if present)
adb push app_extracted/Android/obb/com.example.app \
  /sdcard/Android/obb/com.example.app

# Batch across every device
for SERIAL in $(adb devices | awk 'NR>1 {print $1}' | grep -v '^$'); do
  adb -s "$SERIAL" install-multiple -r app_extracted/*.apk &
done
wait

3 things to watch for when downloading XAPK — and why they matter

1. Architecture must match the device

"Architecture" (arch) is the phone's CPU architecture — different models use different CPUs:

• arm64-v8a — ARM 64-bit (every modern phone, including Samsung S8/S9/S10)
• armeabi-v7a — ARM 32-bit (older phones)
• x86 / x86_64 — Intel (very old phones / emulators)

Inside an XAPK you'll find arch-specific splits like config.arm64_v8a.apk, config.armeabi_v7a.apk — pick the one that matches the device.

Every Samsung S8 / S9 / S10 / Note / Z Flip used in BoxPhone → use arm64-v8a

Pick the wrong arch and install fails with “Parse error” or it installs successfully but crashes on launch.

2. All splits must be present

Modern Play Store uses App Bundles, which split each app into multiple smaller files (split APKs) tailored to the device:

• base.apk — main code (required)
• config.arm64_v8a.apk — native libraries by arch
• config.xxhdpi.apk / config.xhdpi.apk — images per screen density
• config.en.apk / config.th.apk — language packs

On install, you must provide every split the device requires. Missing splits trigger errors:

• “Missing split for config.xxhdpi”
• App force-closes on launch
• Missing UI elements — wrong language, wrong-size icons

If your XAPK is missing splits, redownload from another source — the major releases on APKPure / APKMirror typically bundle complete splits.

3. The signature must be authentic

Every Android APK is signed with the developer's private key (digital signature). Android uses this to prove the APK came from the real owner and hasn't been tampered with.

Anyone modifying the APK (injecting malware, fake ads, or data-stealing code) breaks the signature immediately.

• APKPure / APKMirror — signature-checked before publishing; guaranteed to match Play Store
• Random APK sites Google turns up — mostly skip the check, risk of malware spreading across the entire farm

You can verify signatures yourself with this command (ships with the Android SDK):

# print certificate fingerprint of the APK
apksigner verify --print-certs base.apk

# show only the SHA-256 fingerprint
apksigner verify --print-certs base.apk | grep "SHA-256"

Compare the SHA-256 fingerprint with the official one (from Google Play Developer Console or the developer's site). Match = authentic; mismatch = APK has been modified — do not use it.

Pro tip: For production farms, source from APKPure / APKMirror primarily and verify the base.apk signature before deploying to 100+ devices. If a malicious XAPK reaches the entire farm, it's painful to undo.

What you need

For batch installs across many BoxPhone devices, use ADB:

# install one APK across every device
for SERIAL in $(adb devices | awk 'NR>1 {print $1}' | grep -v '^$'); do
  adb -s "$SERIAL" install app.apk &
done
wait

# Reinstall while preserving data
adb -s <SERIAL> install -r app.apk

# Auto grant permissions
adb -s <SERIAL> install -g app.apk

More install commands at ADB Shortcut Keys.

All four methods compared

Summary

Use Aurora Store as the default — covers most Play Store apps, no account required.

Use APK sideload for specific versions or apps not on the Store.

Use XAPK for games or large apps with OBB / split APKs — through APKPure App, or install-multiple for farm-scale batches.

Use Play Store only for devices that are intentionally logged in for account-bound work.

FAQ

Further reading

• ADB commands you'll actually use — including install
• What is BoxPhone?
• Deploying BoxPhone at 50–100 devices