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

How app installs work on Android

Android lets you install apps in two ways:

1. Through a Store — Play Store, Aurora Store, etc. The store handles updates for you.
2. Sideload an APK — install the file straight, no store involved. You need to turn on “Install from Unknown Sources” first.

On BoxPhone we mix both — it depends on whether the device is logged into Google or not.

The 4 ways we actually use

1. Play Store (Official)

The standard route — log into Google, open Play Store, install.

Good for: Devices already logged in, where you want auto-updates.

Catches:

• Every device has to be logged into a Google account
• Every install is tied to that account, so Google can see the whole farm pattern
• Some apps are region-locked, which means switching the account's country

2. Aurora Store (no login)

Aurora Store is an open-source Play Store client. It uses an anonymous Google account, so you get Play Store apps without logging into the device.

Good for: BoxPhone setups where you don't want to tie devices to Google accounts but still need Play Store apps.

How to set it up:

1. Download the Aurora Store APK from auroraoss.com
2. Turn on "Install from Unknown Sources"
3. Install Aurora Store
4. On first launch, pick "Anonymous"
5. Search, install, done

Why we like it: Covers almost every Play Store app, no login needed, no account tracking on your farm.

3. APK Sideload from trusted sites

Grab the APK file straight off a website and install it. Useful for apps not on Play Store, or when you need a specific version.

Sites we trust:

• APKPure — checks signatures, doesn't repackage APKs
• APKMirror — signs every APK, basically a mirror of Play Store releases
• F-Droid — open-source app repository

Warning: Don't grab APKs from random sites — modded APKs can carry malware.

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

XAPK is a single-file format that bundles the APK + OBB data + split APKs (architecture, language, density) together. It's what you want for big apps — games, apps with separate data files, or anything Play Store breaks into multiple split APKs.

Why we like it: One download, no manually copying OBB into /sdcard/Android/obb, and it covers all the splits the device needs.

Important: XAPK isn't a regular APK — you can't just run adb install on it. It needs a special path.

Installing XAPK on BoxPhone:

Method A — APKPure / APKMirror Installer App (the easy way)

1. Install APKPure App or APKMirror Installer on the device first (just sideload it like a regular APK)
2. Copy the .xapk file onto the device
3. Open APKPure App, pick the file, hit Install. The app unpacks the XAPK, installs every split, and drops the OBB in the right place automatically.

Method B — Unpack XAPK yourself and install via ADB (for batch jobs)

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

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

Install all the splits in one shot 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 when downloading XAPK — and why they matter

1. The architecture has to match the phone

"Architecture" (arch) just means what kind of CPU the phone uses. 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 see arch-specific splits like config.arm64_v8a.apk, config.armeabi_v7a.apk — you have to pick the one that fits the device.

For all the Samsung S8 / S9 / S10 / Note / Z Flip in BoxPhone → use arm64-v8a

Pick the wrong arch and install either fails with “Parse error”, or installs fine but crashes the moment you open it.

2. All the splits need to be there

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

• base.apk — main code (required)
• config.arm64_v8a.apk — native libraries for each arch
• config.xxhdpi.apk / config.xhdpi.apk — images at the right screen density
• config.en.apk / config.th.apk — language packs

When you install, you have to hand it every split the device needs. Miss one and you'll see:

• “Missing split for config.xxhdpi”
• App force-closes the moment it opens
• UI bits missing — wrong language, wrong-size icons

If your XAPK is missing splits, just grab a new one from somewhere else. The big releases on APKPure / APKMirror usually bundle everything you need.

3. The signature has to be real

Every Android APK is signed with the developer's private key (digital signature). Android uses that signature to confirm this APK really came from the original developer and hasn't been tampered with on the way.

The moment someone tweaks the APK (injecting malware, fake ads, data-stealing code), the signature stops matching the original.

• APKPure / APKMirror — check the signature before posting; guaranteed to match Play Store
• Random APK sites that pop up on Google — mostly don't check, and you risk spreading malware across the whole farm

You can check the signature yourself with this command (comes with 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 you get with the official one (from Google Play Developer Console or the developer's site). Same = real. Different = the APK has been modified — don't use it.

Pro tip: For a real production farm, stick to APKPure / APKMirror and verify the base.apk signature before pushing to 100+ devices. If a bad XAPK gets onto the whole farm, undoing it is painful.

What you'll need

For batch installs across a lot of BoxPhone devices, just 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 over at ADB Shortcut Keys.

All 4 methods side by side

Wrapping up

Use Aurora Store as your default — it covers most Play Store apps and you don't need to tie any account to the device.

Use APK sideload when you need a specific version or the app isn't on a store.

Use XAPK for games or big apps with OBB / split APKs — either through APKPure App, or install-multiple when you're batch-installing across the farm.

Use Play Store only on devices you're intentionally logging in for account-bound work.

FAQ

Read next

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