How to Extract an APK from Any Android Device Using ADB Pull
Description
What adb pull apk Actually Does — and Why You’d Need It
Imagine you’ve spent months using an app that suddenly disappears from the Play Store. No warning, no alternative, no backup. The only copy that exists is sitting on your Android device right now — and unless you know how to reach it, it’s gone the moment you factory-reset or switch phones. That’s precisely the situation where adb pull apk becomes essential.
In plain terms: adb pull is an Android Debug Bridge command that copies a file from your Android device to your computer. When you target an APK file path with that command, you extract the actual installable app package — no root required in most cases, no third-party app store involved. The result is a local .apk file you can back up, sideload onto another device, or archive indefinitely.
This guide covers the full process: setting up ADB, locating the correct APK path on your device, running the pull command, handling the errors that actually trip people up, and understanding which apps you can and cannot extract this way.
Setting Up ADB Before You Pull Anything
ADB (Android Debug Bridge) is a command-line tool included in Android’s platform tools — you need it installed on your computer before any of the steps below will work. Fortunately, setup is straightforward on Windows, macOS, and Linux.
Installing Platform Tools
Download the Android SDK Platform Tools package directly from Google’s official developer site. You do not need to install Android Studio or the full SDK — Platform Tools is a standalone download. Extract the zip to a folder you’ll remember (e.g., C:platform-tools on Windows or ~/platform-tools on Mac/Linux). Then add that folder to your system’s PATH environment variable so you can run adb from any terminal window without typing the full path every time.
On Windows, the quickest way to test this is to open Command Prompt and type adb version. If it returns a version number, you’re set. If it says “command not found,” your PATH isn’t configured correctly yet — that’s the single most common setup mistake.
Enabling USB Debugging on Your Android Device
Your phone won’t respond to ADB commands unless USB Debugging is active. Here’s how to enable it:
- Open Settings → About Phone and tap Build Number seven times rapidly. You’ll see a message saying “You are now a developer.”
- Go back to the main Settings menu. A new Developer Options entry will have appeared — tap it.
- Scroll down and toggle USB Debugging to on.
- Connect your phone to your computer via USB. A prompt will appear on the phone asking you to authorize the connection — tap Allow and optionally check “Always allow from this computer” to avoid repeating this step.
Run adb devices in your terminal. Your device’s serial number should appear with the status “device” next to it. If it shows “unauthorized,” check your phone’s screen — the authorization dialog may still be waiting for your input.
Finding the APK Path Using adb shell pm
Before you can run adb pull apk, you need the exact file path where Android has stored the app’s APK — and that path isn’t obvious. Android stores installed apps in locations like /data/app/, but the subfolder names are randomized strings, not the app’s display name.
Using pm list packages to Find Your App
The Package Manager (pm) tool inside ADB shell lets you query installed apps by their package name. Run this:
adb shell pm list packages
This dumps every installed package. The list can be long — hundreds of entries on a typical phone. To narrow it down, pipe through grep (Mac/Linux) or findstr (Windows):
- Mac/Linux:
adb shell pm list packages | grep youtube - Windows:
adb shell pm list packages | findstr youtube
Replace “youtube” with any part of the app’s name or developer name you know. The output returns lines like package:com.google.android.youtube — the string after the colon is the package name you need for the next step.
Getting the Full APK File Path
Once you have the package name, run:
adb shell pm path com.google.android.youtube
Android will return something like:
package:/data/app/~~xK2lPdRs/com.google.android.youtube-abc123==/base.apk
Copy everything after package: — that full string is the path you’ll use in the pull command. Note that split APKs (common in newer Android versions) may show multiple paths: base.apk plus split_config.arm64_v8a.apk and similar. More on handling those in a moment.
Running the adb pull apk Command
With the APK path confirmed, pulling the file to your computer is a single command. The syntax is straightforward, but the details matter for avoiding common errors.
Basic Pull Command Syntax
The general form is:
adb pull <remote-path-on-device> <local-destination-on-computer>
For the YouTube example above:
adb pull /data/app/~~xK2lPdRs/com.google.android.youtube-abc123==/base.apk ~/Desktop/youtube.apk
If the pull succeeds, the terminal will show a progress line and confirm with something like 1 file pulled, 0 skipped. 45.2 MB/s. The file will appear at your specified destination.
If you omit the local destination, ADB drops the file in whatever directory your terminal is currently in — which is fine, but naming it explicitly (like youtube.apk) prevents confusing unnamed files from piling up.
Handling Split APKs
Modern Android apps — especially large ones from Google and major developers — are often delivered as split APK sets rather than a single base.apk. This is Android’s App Bundle system at work. The pm path command will return multiple lines for these apps.
You have two practical options here. First, pull each file individually and rename them logically. Second, use a tool like apktool or combine them with SAI (Split APKs Installer) on another Android device. The base.apk alone is often enough to get the core app working, but some features or device-specific graphics won’t load without the split configs — so pulling all parts matters if you’re trying to preserve full functionality.
To pull all splits cleanly, you can target the entire app directory rather than the individual file:
adb pull /data/app/~~xK2lPdRs/com.google.android.youtube-abc123==/ ~/Desktop/youtube-apks/
This pulls the directory and its contents, giving you base.apk plus every split file in one go.
Common Errors and What They Actually Mean
| Error Message | Likely Cause | Fix |
|---|---|---|
| remote object does not exist | Path is wrong or has a typo | Re-run pm path and copy the path exactly, including special characters |
| Permission denied | App is protected or path is system-only | On rooted devices: use adb root first; on non-rooted: system apps may be inaccessible |
| error: device not found | USB debugging not active or cable issue | Re-check USB debugging and run adb devices to confirm connection |
| error: more than one device/emulator | Multiple devices connected | Use adb -s <serial> pull ... to target the right device |
Which Apps You Can (and Cannot) Extract
Not every installed app is accessible via adb pull on a non-rooted device. Understanding the distinction upfront saves a lot of frustration.
User-Installed Apps — Generally Accessible
Apps you downloaded from the Play Store or sideloaded yourself live in /data/app/. ADB can access this directory without root on most Android versions, because these apps are intentionally readable by the system. The adb pull apk process works reliably for this category — productivity apps, utilities, games you’ve downloaded, and most third-party software fall here.
System Apps — Usually Blocked Without Root
Pre-installed system apps live in /system/app/ or /system/priv-app/. On non-rooted devices, ADB does not have permission to read these directories. Even pm path will return a path, but the actual pull will fail with a permission error. If you specifically need a system APK, rooting the device first (or using a rooted ADB session with adb root on emulators and developer builds) is the only non-destructive path forward.
Apps with Copy Protection
Some apps set a flag called FLAG_EXTERNAL_STORAGE or use Android’s forward-locking mechanism to prevent their APK from being copied. This was more common pre-2014 but still exists in some paid apps that actively want to prevent redistribution. When you pull these APKs, the file exists and transfers — but it either won’t install on another device or installs with features intentionally broken. Legally, extracting and redistributing paid APKs is a copyright violation in most jurisdictions regardless of technical capability, so the ethical use case here is personal backup on your own devices.
How to Download and Use This Guide’s Approach — Step by Step
If you want to use the adb pull apk method today, the download button above links to the Android SDK Platform Tools — the only component you actually need. Once you have it, follow these numbered steps in order:
- Download and extract Platform Tools from the link above to a folder on your computer.
- Add the folder to your PATH (or navigate to it in terminal each session).
- Enable USB Debugging on your Android device as described in the setup section above.
- Connect your phone via USB and confirm the connection with
adb devices. - Find the package name using
adb shell pm list packages | grep <appname>. - Get the APK path with
adb shell pm path <package.name>. - Pull the APK with
adb pull <path> ~/Desktop/myapp.apk. - Verify the file on your computer — it should open as a valid ZIP archive (APKs are ZIP-based) if you want to inspect it.
The entire process, once ADB is installed and USB debugging is active, takes under two minutes for a typical app. The setup is a one-time cost; subsequent pulls are fast.
A Safety Note Before Installing Any APK
If you’re pulling an APK to install on another device, verify the source carefully. An APK you extracted yourself from a known app is inherently trustworthy — you know its origin. APKs obtained from unknown third-party sites carry real risk: repackaged apps sometimes contain malware that survives inside the original app’s code. Always verify the APK’s package name and, where possible, compare its SHA-256 hash against the original before installing on a new device. Android will also warn you if a new installation’s certificate doesn’t match an existing version — pay attention to those warnings.
ADB Over Wi-Fi — Pulling APKs Without a Cable
USB isn’t strictly required. Android 11 and later support wireless ADB debugging natively, and even older versions can use the adb tcpip method after an initial wired connection.
For Android 11+: go to Developer Options → Wireless Debugging, tap it, then use the pairing code option to pair your computer to the device over your local network. Once paired, adb connect <device-ip>:<port> establishes the connection, and from that point adb pull commands work identically to wired. Transfer speeds over Wi-Fi are slower than USB — expect roughly 2–5 MB/s on a typical home network versus 30–50 MB/s over USB 3.0 — but for extracting a 50 MB APK, the difference is under a minute either way.
Frequently Asked Questions
Does adb pull apk work without rooting my phone?
Yes, for the vast majority of user-installed apps. The /data/app/ directory where downloaded apps live is accessible via ADB without root. The exception is system pre-installed apps stored in /system/app/ — those require root access or a developer build with adb root enabled.
Why does adb pull say “Permission denied” even though I have USB debugging on?
USB debugging grants ADB shell access, but not root-level file permissions. If the APK lives in a root-protected directory (system apps, or some newer Android versions with stricter sandboxing), ADB will hit the permission wall. Try adb shell pm path <package> to confirm the path is correct first — sometimes the error is simply a wrong path, not a genuine permissions issue.
Can I install the pulled APK on a different Android device?
Usually yes, with two conditions: the target device must run an Android version compatible with the app’s minimum SDK requirement, and you must enable “Install from unknown sources” on the target device. If the app uses split APKs, you’ll need to install all split files together — tools like SAI (Split APKs Installer) make this straightforward.
Is it legal to pull an APK from my own device?
Extracting an APK for personal backup from a device you own is generally considered legal in most countries. Distributing that APK to others — especially for paid apps — typically constitutes copyright infringement. Use extracted APKs responsibly and only transfer them to devices you own or control.
What is ADB Platform Tools and is it free?
Android Debug Bridge is part of the Android SDK Platform Tools package, which Google provides completely free of charge through the official Android developer site. It’s a small download (around 10–15 MB), contains no ads or subscriptions, and is updated regularly alongside new Android releases.
Can I extract an APK over Wi-Fi instead of USB?
Yes. Android 11 and later support wireless ADB natively through Developer Options → Wireless Debugging. On older Android versions, you can enable TCP/IP mode (adb tcpip 5555) after an initial USB connection, then disconnect the cable and use adb connect <device-ip>:5555 for all subsequent commands including adb pull.
Further reading: Google Play services ↗️
