Many Android users want a clean way to separate personal apps from work‑related ones without the hassle of a second device or rooting the phone. Android’s work profile (also called a managed profile) offers exactly that: a sandboxed space that behaves like a separate user, with its own app drawer, notification channel, and data store. This tutorial walks you through creating a work profile on any Android 7.0+ device using only ADB – no manufacturer‑specific tools, no root, and no enterprise enrollment required.
Build number seven times).adb devices. You should see a device serial number with the word device next to it.
adb devices
List of devices attached
ABCD1234567890 device
If you see unauthorized, check the phone for a prompt asking to Allow USB debugging and tap Allow.
adb shell getprop ro.build.version.sdk to see the SDK level (e.g., 30 for Android 11). The work‑profile feature is available from API 24 (Android 7.0) onward.Android treats a work profile as a special user with the --managed flag. The following command creates it as a child of the primary user (user 0).
adb shell pm create-user --profileOf 0 --managed "Work Profile"
The command returns a line like Success: created user id 10. Remember the user ID – you’ll need it later to move apps.
What happens under the hood? Android creates a separate data directory (e.g., /data/user/10/) and a distinct launcher entry. The system also adds a small badge (a briefcase) to the work‑profile apps, making it clear which side they belong to.
Once enabled, you’ll notice a new work‑profile icon (a briefcase) appears in the status bar. The work profile now has its own app drawer, accessible by swiping up on the home screen or by tapping the briefcase badge.
Not every app can be moved; only those that support the managed‑profile flag. System apps (e.g., Settings) stay in the primary user, but most third‑party apps can be duplicated.
adb shell pm list packages or use adb shell pm list packages -3 for user‑installed apps.pm install‑existing command to create a work‑profile instance:
adb shell pm install-existing --user 10 com.example.app10 with the user ID you obtained in Step 2 and com.example.app with the real package name.
/data/user/10/. The original app remains in the personal profile, so you now have two isolated instances.
Example: To duplicate WhatsApp (package com.whatsapp) into the work profile, run adb shell pm install-existing --user 10 com.whatsapp. You’ll then have two independent WhatsApp installations – one for personal chats, one for work‑related communications.
Because each profile has its own app sandbox, permissions are granted per‑profile. To adjust permissions:
Alternatively, you can use ADB to grant a permission without opening the UI:
adb shell pm grant --user 10 com.example.app android.permission.CAMERAReplace the package name and permission as needed.
Android provides several ways to toggle the work profile on the fly:
adb shell am start -a android.settings.USER_SETTINGSWhen the profile is disabled, its apps disappear from the launcher and cannot run, but their data remains intact.
Because the work profile has its own user ID, you can back it up independently using adb backup:
adb backup -user 10 -apk -shared -all -f work_profile.abThis creates a single .ab file containing apps, APKs, and data for the work profile. To restore later:
adb restore work_profile.abWarning: The backup is not encrypted by default. Use the -encrypt flag and a strong password if you store the file in the cloud.
If you decide the work profile is no longer useful, you can delete it cleanly:
adb shell pm remove-user 10 to ensure the user ID is fully removed from the system.
After removal, the briefcase badge disappears and the device returns to a single‑profile state.
Some OEMs restrict the pm command for non‑system users. Ensure you are using a user‑debug build or enable the adb root flag if your device permits it. If the command still fails, try the same steps on a device with a stock AOSP build.
adb reboot.Not all apps support a managed instance. If you see Failure [INSTALL_FAILED_ALREADY_EXISTS] or INSTALL_FAILED_INVALID_APK, the app likely lacks the necessary manifest flag (android:managedUser). In that case, you can only use the app in the personal profile.
When you turn the work profile off, Android may clear runtime permissions for security. After re‑enabling, revisit the app’s permission screen and re‑grant any needed permissions.
This usually indicates the device is locked or the screen is off. Unlock the device, keep it awake, and retry the adb backup command.
adb backup -user 10 to an encrypted archive on your PC.By following the steps above you can create a fully functional work profile on any Android 7.0+ device without rooting or enrolling in a corporate MDM. The profile gives you a sandbox for apps, independent permissions, and a clear visual separation, all while keeping your personal data safe. Use the troubleshooting section to address common hiccups, and adopt the best‑practice tips to keep the profile tidy and secure over time.









