How to Sideload the Official Binance Android APK: Package Name, Signature, and Per-Brand Workarounds

A hands-on Binance Android sideload walkthrough covering the Google Play delisting, com.binance.dev package verification, 85 MB size check, apksigner fingerprint check, unknown-source toggles for Huawei/Xiaomi/OPPO/vivo/Samsung/Pixel/OnePlus, Xiaomi Pure Mode bypass, Android 13+ per-app install permission, INSTALL_FAILED_VERSION_DOWNGRADE remediation, and local data backup.

Published on 2026-06-22 · About 42 min read · Android APK

For Android users in mainland China, the safest path to a working Binance client is to grab the APK from the official page and sideload it. Let us anchor the trusted entry points up front: every install file should originate from the Binance Official Site or the Official Binance App entry, and the screenshots, per-brand walkthroughs, and hash lookups we curate live on the Download Page. What follows is every trap the sideload route can spring on you, written down in one place.

Why Google Play Cannot Install Binance and Sideloading Is Required

Back in Q4 2021, Google Play began delisting the main Binance client across most regions. As of today, searching Play for "Binance" in mainland China, Hong Kong, Taiwan, Japan, Korea, Singapore, and India returns no result for the flagship app. What does appear is Binance.US (US residents only), Binance Pool, Binance Wallet, and other satellite products — never the main exchange app.

The delisting is not a technical fault. It is Google Play tightening compliance for crypto exchange apps, demanding local financial licenses, custody attestations, and cross-border regulatory filings that Binance's operating entities do not hold in many regions as a "licensed exchange". That single distribution channel is closed off.

The official replacement paths are two: the web client at accounts.binance.com, and APK sideloading. Sideloading gives the closest experience to a native app for Android users. Performance, push notifications, biometric unlock, QR scanning — all present in the APK build. The web client requires several workarounds for those. This article focuses on that sideload path.

One point to emphasize: sideloading itself is a first-party supported behaviour on Android. The operating system deliberately keeps a sideload path open — otherwise ADB, enterprise distribution, and third-party stores could not function. The question is not whether you can install; it is whether the APK in your hand is the genuine build. That is why we spend so much time below on package names and signature fingerprints.

First Gate: Package Name and File Size

The package name for Binance's main Android client is com.binance.dev. It has not changed since 2018. Committing that string to memory is more useful than any QR code or domain, because Android treats the package name as the app's real identity and validates it at install time. You cannot fake it without re-signing, and the signature check downstream catches that.

File size is another quick tell. The current mainline APK stabilizes between 80 and 90 MB — the last three releases were 85.3 MB, 87.1 MB, and 84.9 MB. When you inspect a downloaded APK:

  • Under 50 MB: 99% chance it is a stub launcher that will pull the real APK mid-flow and get hijacked in the process.
  • Between 50 and 75 MB: suspicious — likely a stripped or repackaged build.
  • Between 75 and 95 MB: within the expected range, but still requires signature verification.
  • Over 100 MB: suspicious — probably repackaged with an ad SDK or a mining module.

Right-click the file in Windows Explorer or long-press it in the mobile file manager to read its size before doing anything else.

Verifying the APK Signature with apksigner

Package names can be spoofed (the installer catches this) and file sizes can be padded (features get gutted), but the digital signature cannot be forged. The official Binance APK is signed by Binance Holdings Limited under scheme V2. The Android SDK ships with apksigner for this check.

If Android Studio is installed on your PC, apksigner lives at:

Windows:  %LOCALAPPDATA%\Android\Sdk\build-tools\<version>\apksigner.bat
macOS:    ~/Library/Android/sdk/build-tools/<version>/apksigner
Linux:    ~/Android/Sdk/build-tools/<version>/apksigner

Drop the APK anywhere and run:

apksigner verify --print-certs --verbose binance.apk

The relevant lines in the output are:

Signer #1 certificate DN: CN=Binance, O=Binance Holdings Limited, ...
Signer #1 certificate SHA-256 digest: <64-character hex>
Signer #1 certificate SHA-1 digest:   <40-character hex>
Signer #1 certificate MD5 digest:     <32-character hex>

Two checks matter: the DN must contain O=Binance Holdings Limited, and the SHA-256 fingerprint must match the value published in the Binance developer docs (the binance-connect section and several public SDK README files list it). If the DN reads a personal name, a random string, or some other company, the APK has been repackaged — delete it.

On a phone without the SDK, apps like "Apk Analyzer" and "APK Editor" show signature information the same way, but those tools themselves must come from a trusted source or you are asking a thief to inspect another thief. The PC-side apksigner check remains the cleanest option.

Enabling "Unknown Sources": Per-Brand Toggle Locations

Android 6.0 and earlier used a single global "unknown sources" toggle. Versions 6.0 through 7.1 were a transition. From 8.0 onward, permission is granted per app; Android 13 refined that further with per-app plus per-session prompts. The paths below are for current 2025-2026 firmware — older builds may differ slightly.

Huawei EMUI 14 / HarmonyOS NEXT: Settings then Security then More Security Settings then External source app downloads. Pick whichever file manager will trigger the install (Files by default) and enable "Allow installation from this source". HarmonyOS NEXT uses the same path.

Xiaomi HyperOS 2.0 (formerly MIUI): Settings then Privacy Protection then Special Permissions then Install Unknown Apps. Enable it for Files, Downloads, and your browser (the browser needs it if you tap the install link directly).

OPPO ColorOS 15: Settings then System Settings then App Management then Default Apps then Install Unknown Apps. Note "System Settings", not "Apps".

vivo OriginOS 5: Settings then More Settings then Permission Management then Install Unknown Source Apps. Straightforward.

Samsung One UI 7: Settings then Apps then the specific browser or file manager then Install Unknown Apps then enable "Allow from this source". Samsung goes through the app detail page, unlike other brands.

Google Pixel (stock Android 15): Settings then Apps then Special App Access then Install Unknown Apps. Three taps, the cleanest of the lot.

OnePlus ColorOS 15 (OnePlus 12 and up share the OPPO stack): identical to OPPO. Older OnePlus 11 or 10T units on legacy OxygenOS use Settings then Security and Lock Screen then Install Unknown Apps.

A universal shortcut: tap the APK in a file manager, and when the system blocks the install, tap the "Settings" button in the popup. It jumps straight to the right permission screen and beats digging through menus every time.

Bypassing Xiaomi's Pure Mode

Xiaomi HyperOS and legacy MIUI include a "Pure Mode" that blocks any APK not sourced from the app store. The rejection reads "For your safety, this app is not allowed to install" with only an OK button — no override. This is one of the most common install roadblocks in mainland China.

To disable it (this is a legitimate first-party toggle, not a jailbreak):

  1. When the block appears, do not tap OK. Long-press the popup or pull down to find the "About Pure Mode" hint.
  2. Open the Pure Mode explanation screen, scroll to the bottom, tap "Disable Pure Mode".
  3. Confirm on the follow-up dialog, tap "Continue disabling", and enter the lock-screen PIN.
  4. APK installs are unrestricted for 24 hours, after which Pure Mode re-arms itself.

If your build lacks the disable option (some carrier ROMs strip it), the second workaround is Settings then Home Screen then Layout, switch temporarily to Classic Mode. Pure Mode is off by default in Classic Mode. Switch back afterward.

The third route is ADB. Install platform-tools on a PC, enable USB debugging in Developer Options, connect the phone, and run adb shell pm install /sdcard/binance.apk. Pure Mode does not gate ADB installs. Cleanest option but requires a computer.

Huawei EMUI and HarmonyOS NEXT Permissions

Huawei deserves its own section because HarmonyOS NEXT (Star River) left AOSP entirely in 2024 and has its own permission model.

EMUI 14 and earlier (pre-Mate 60): still an AOSP-based kernel, so the Huawei path above works and the prompts look like other Android phones.

HarmonyOS NEXT (Mate 70, Pura 70 and later): the OS no longer supports Android APKs natively, but Huawei ships an "app migration tool" and a "compatible app market". The Binance APK on NEXT must be installed via the Huawei AppGallery's "compatible apps" category, or by searching Binance directly in AppGallery — matching results carry an "Android app" label, and tapping install triggers the Android compatibility layer.

Binance on HarmonyOS NEXT is not a native HarmonyOS app. Startup takes 0.5 to 1 second longer than on EMUI in our tests, though all features work. If push notifications and background persistence matter, wait for the promised native HarmonyOS build (on the roadmap, no confirmed date).

Android 13+ "Per-App Plus Per-Session" Prompts

Android 13 (API 33) introduced a new behaviour: even if the source app has been granted install permission, the system may prompt for per-session confirmation on every install, requiring a user tap. Android 14 and 15 tightened this further, sometimes demanding the lock-screen PIN each time.

The upside is that malware that phishes an "unknown sources" grant cannot install silently — a human tap is required. The downside is friction. Handling notes:

  • When the per-session prompt appears, tap Allow. Do not tick "do not ask again"; that option occasionally freezes the state incorrectly.
  • If the lock-screen PIN is requested, enter it normally.
  • If the installer freezes at "analyzing package" for more than 30 seconds, the system is running a package scan (Google Play Protect or the vendor's scanner). Wait it out; it moves on automatically.
  • Play Protect occasionally misidentifies the Binance APK as harmful and auto-uninstalls it. To reinstall: Settings then Security then Google Play Protect then turn off "Scan apps", then install again.

That last case is most common on Pixels and stock Android, where Play Protect is deeply integrated. Vendor ROMs (Xiaomi, Huawei) usually avoid this because Play Protect is disabled on their mainland-China builds.

Backing Up Local Data Before Uninstalling

The main Binance app stores login session tokens, in-app Authenticator bindings, anti-phishing code cache, recent trading pairs, favourite coins, chart settings, and push subscriptions. These live under /sdcard/Android/data/com.binance.dev/ and /data/data/com.binance.dev/, with the latter requiring root.

Without root, four backup options exist:

Option 1: ADB backup (recommended)

adb backup -apk -shared com.binance.dev -f binance-backup.ab

This creates a .ab file on the PC. Restore with adb restore binance-backup.ab. Caveat: Android 12 and later degraded adb backup fidelity, so tokens and sensitive data will not restore. Non-sensitive settings such as chart layouts will.

Option 2: Account cloud sync

Binance shipped account-level settings cloud sync in Q1 2025 (Settings then Preferences then Cloud Sync). Enabling it pushes favourite coins, chart layouts, and price alerts. Sensitive login data (2FA, sessions) is intentionally excluded.

Option 3: Manual capture

Open Settings then Display and Experience and screenshot the language, currency, and chart theme. Screenshot the favourites list one by one. If you use the built-in Binance Authenticator, email yourself the 2FA reset link before uninstalling (Settings then Security then Google Authenticator then Change Device).

Option 4: Upgrade in place instead of reinstalling

For version upgrades, install the new APK over the old one. Local data is preserved. Only "uninstall then install" wipes state. The next section covers version-downgrade errors during in-place upgrades.

Handling INSTALL_FAILED_VERSION_DOWNGRADE

This is the most common upgrade error, thrown when Android refuses to install an APK whose versionCode is lower than the currently installed version (versionCode, not the user-visible name). Two scenarios cause it:

Scenario A: the "new" APK is actually old

Third-party download sites often cache old APKs under filenames like binance-latest.apk while the versionCode is behind. Re-download from the official page.

Scenario B: switching from beta to stable

Binance occasionally pushes beta APKs to select users (same com.binance.dev package name, but the versionCode jumps far higher than stable). Trying to install stable afterwards trips the downgrade check. To recover:

  1. Back up data (see prior section).
  2. Fully uninstall: Settings then Apps then Binance then Uninstall. Choose Uninstall, not "clear data".
  3. The system may retain leftover data. Clean it under Settings then Storage then Other App Data — remove the com.binance.dev entry.
  4. Reboot to flush PackageInstaller cache.
  5. Install the stable APK.

ADB users have a shortcut: adb install -d binance-stable.apk. The -d flag permits versionCode downgrade. This only works over the ADB channel; the on-device file manager cannot bypass the check.

Post-Install Security Checklist

After the first launch, run through these five steps to reach Binance's recommended baseline.

Step 1: Verify the package name

Settings then Apps then Binance. At the bottom of the detail page, the Package name field must read com.binance.dev. If you see com.binance.lite, com.binance.android, or a variant, you installed the wrong build — uninstall it.

Step 2: Verify the version

Open the app then Settings (avatar) then About then version. Compare against the current version published on the official site. Being one or two minor versions behind is normal. Being three or more versions off, or seeing a malformed version like 0.x.x or garbled characters, is a signal to uninstall and reinstall.

Step 3: Register or sign in

New users go through registration (referral code P394YSTZ gets fee rebates and does not affect trading otherwise). Existing users sign in directly. We recommend registering from the Binance Official Site and only signing in from the app — registration and KYC flow more reliably on the web.

Step 4: Two-factor authentication

Immediately after signing in, open Settings then Security then Two-Factor Authentication and enable at least two of:

  • Google Authenticator (recommended, offline code generation)
  • SMS verification (backup channel, watch for SIM swap risk)
  • Email verification (backup channel)

The built-in Binance Authenticator works, but binding it to the same device means losing the device costs both the app and the 2FA. Do not rely on it as the only factor.

Step 5: Device management and anti-phishing code

Settings then Security then Device Management: name the current device clearly (for example "Main phone - OnePlus 13") and remove unknown historic entries. Then Settings then Security then Anti-phishing Code: set a 4 to 20 character custom string (not your name, birthday, or a reused password). Every subsequent Binance email will carry that string; mail without it is phishing.

Once these five steps are done, add withdrawal address whitelisting, API key restrictions (if you plan to trade programmatically), and login notifications. That completes the baseline. Detailed device management and 2FA guides live under our "security settings" category.

Monthly Maintenance

Installing is not a one-shot task. Run a health check monthly:

  • 1st of each month: compare the local version against the official site. Upgrade in place if you are two or more releases behind.
  • 15th of each month: Settings then Security then Device Management. Confirm no stranger devices are listed.
  • Quarterly: pull an APK backup on the PC and re-run apksigner verify against your original SHA-256 fingerprint, confirming no silent swap.
  • Every six months: confirm 2FA devices still work and recovery keys are still accessible.

Running this rhythm keeps the Binance app on your Android in a known-good state.

FAQ

Q1: Is downloading the APK from the Binance site safe? Why no Google Play link?

A: The Binance main app is delisted from Google Play globally. There is no Play link to give. Official-site APK sideloading is the vendor-supported distribution path, and combined with the package-name and signature checks in this article it is more trustworthy than any third-party store.

Q2: apksigner says "verified using v1 scheme: true, verified using v2 scheme: false". What now?

A: v1 is the legacy JAR signature; v2 is the whole-file signature from Android 7.0. The official Binance APK carries v1 + v2 + v3 signatures — all three should read true. If v2 or v3 reads false, the APK was modified post-build (even swapping an icon breaks v2). Do not install.

Q3: After install the system says "not compatible with your device".

A: First check the Android version. The current Binance APK requires Android 8.0 (API 26) at minimum. Older devices need archived builds (not recommended — security updates missing). Then check CPU architecture. The APK ships arm64-v8a and armeabi-v7a native libraries, so nearly every phone from 2018 or later works. Users on x86 emulators (LDPlayer, Nox) need an emulator-tailored build.

Q4: The upgrade throws "App not installed". What does that mean?

A: A vague error with three common causes: 1) signature mismatch (the new APK came from an unofficial source with different signing keys), 2) insufficient storage (Android needs roughly twice the APK size free), 3) install interrupted (screen off or system sleep). Free up more than 1 GB and retry with the official APK.

Q5: Must Play Protect stay off to install the Binance APK?

A: Not necessarily. In most cases Play Protect only warns and does not block. Choose "install anyway" when it warns. Only when it flags Binance as "severely harmful" and auto-uninstalls do you need to temporarily disable it. Re-enable it afterward — it still protects against malware from other sources.

Q6: Can I run Binance on a backup phone with no SIM card?

A: Yes. The app does not require a SIM. Registration can use an email address in place of a phone number. Account tier (basic vs. advanced verification) and OTC fiat access depend on identity verification, not SIM presence. Running Binance on a backup phone as an isolation practice — separating trading from daily-driver activity — is a valid security posture.

Q7: The app hangs on the loading spinner after install. Bad APK?

A: 80% of the time it is a network issue, not the APK. Confirm binance.com opens in a browser. If the browser also fails, the local network is filtering the domain and you need to switch networks or configure a proxy. If the browser works but the app hangs, clear app data (Settings then Apps then Binance then Storage then Clear Data) and retry. Only after that consider APK integrity.

Q8: If Binance ever returns to Google Play, will the sideloaded install auto-upgrade via the store?

A: No. Play Store only upgrades apps installed through Play Store. Sideloaded and Play builds share the package name but differ in install source. Play will mark the sideloaded install as "not installed via Play" and require uninstall first. Back up local data before reinstalling.


Published on 2026-06-22