Set Up Android Device Owner Mode for a Child‑Safe Phone (No Root)

When you hand a phone to a child you want it to behave like a locked‑down tablet: only the apps you approve can run, system settings are hidden, and accidental purchases are impossible. Android’s Device Owner mode gives exactly that level of control, but it’s rarely documented for everyday users because the setup usually assumes a corporate deployment. This guide shows you how to enable Device Owner on a personal phone without rooting, using only free tools and a lightweight kiosk‑style app.

Why Device Owner Is Different from a Regular Admin

Android distinguishes between two kinds of management:

• Device Owner – a single app that owns the entire device. It can enforce policies that affect every user, disable the status bar, block factory resets, and hide system settings.
• Profile Owner – an app that manages a work profile (the “Work” space you see on many phones). It can only control the work profile, not the personal side.

For a child‑safe phone you need the broader reach of a Device Owner, because you want to restrict the whole device, not just a profile.

Before You Start

Make sure the phone is fully charged (or plugged in) before you begin. A reset will wipe everything, so back up photos, contacts, and any important files first.

Step 1 – Prepare the Phone (Factory Reset)

Skipping the account sign‑in prevents the device from automatically enrolling in any corporate MDM that could block the Device Owner command.

Step 2 – Install a Compatible Device‑Owner App

Several free apps are built to be a Device Owner; the open‑source Android Kiosk project is a good reference. For simplicity we’ll use the Play Store version of SureLock Lite, which declares a DeviceAdminReceiver and can be set as Device Owner via ADB.

If you prefer a completely offline approach, download the APK from the project’s GitHub releases page, transfer it via USB, and install with adb install. The crucial part is that the APK’s manifest contains a <receiver> with the android:permission="android.permission.BIND_DEVICE_ADMIN" attribute.

Step 3 – Enable USB Debugging and Connect to Your PC

If the device appears as unauthorized, disconnect and reconnect the cable, then re‑accept the prompt.

Step 4 – Grant Device‑Owner Status via ADB

The ADB command dpm set-device-owner tells Android which app should become the Device Owner. The syntax requires the full component name of the app’s DeviceAdminReceiver. For SureLock Lite the component is com.surefox.surelock/.admin.DeviceAdminReceiver.

Why this works: During the first‑boot provisioning Android checks for a pending dpm set-device-owner request. Because the device is freshly reset, it accepts the command without any additional authentication.

Step 5 – Verify the Device‑Owner Status

If you see the full Settings UI, double‑check that the component name in step 4 matches the exact package name of the app you installed.

Step 6 – Configure Parental Controls Inside the Kiosk App

SureLock Lite (or any kiosk app) provides a simple UI to pick allowed apps, block the status bar, and prevent app installs. The exact layout varies by app, but the general workflow is:

1. Launch the kiosk app and tap the Settings gear icon.
2. Under Allowed Apps, add only the games, educational tools, or media players you want the child to use.
3. Enable Block Status Bar and Disable Volume Buttons if you want a completely sealed experience.
4. Turn on Prevent Uninstall of Allowed Apps – this uses the Device Owner API to lock the selected packages.
5. Optionally set a Screen Timeout of 5 minutes or less to conserve battery.

When you’re done, press the home button (if visible) to return to the locked home screen. The child will now see only the apps you approved, and attempts to open Settings will be blocked.

Alternative: Using Google Family Link

If you prefer a cloud‑based solution, Google’s Family Link app can enforce many of the same restrictions without requiring a Device Owner. The trade‑off is that Family Link relies on a Google account for the child and cannot hide the status bar completely. For a truly locked‑down device, Device Owner remains the most powerful option.

Troubleshooting Common Issues

• Command fails with “Device is already provisioned” – This means the phone was not freshly reset. Perform another factory reset, then repeat steps 1‑4 before any other apps are installed.
• ADB reports “Security exception: Not allowed to set device owner” – Verify that you used the exact component name. Also ensure the app’s manifest includes the android:permission="android.permission.BIND_DEVICE_ADMIN" attribute.
• After setting Device Owner, the phone boots into a black screen – Some custom ROMs or heavily skinned manufacturers (e.g., Xiaomi, Huawei) may block Device Owner on a non‑enterprise build. In that case, consider flashing a stock AOSP‑based ROM or using a different kiosk app that supports those OEM restrictions.
• Unable to disable the status bar – Not all kiosk apps implement the full setStatusBarDisabled API. Try an app that explicitly advertises “Full‑screen kiosk” support, such as Fully Kiosk Browser.

Safety and Maintenance Tips

• Keep a backup of the ADB command – If you ever need to remove the Device Owner (for example, to repurpose the phone), you can run adb shell dpm remove-active-admin com.surefox.surelock/.admin.DeviceAdminReceiver while the device is in Safe mode. Safe mode disables third‑party apps, allowing you to break the lock.
• Regularly update the kiosk app – Security patches are released for many parental‑control apps. Updating ensures new exploits can’t bypass the restrictions.
• Don’t install additional apps from unknown sources – With Device Owner active, the system will block side‑loading unless you explicitly allow it. Stick to the Play Store or the pre‑approved APKs you’ve added.

Once you’ve completed the steps above, the phone behaves like a dedicated child device: the home screen shows only approved apps, system settings are hidden, and accidental purchases are impossible. You can still connect the phone to a PC via ADB for occasional maintenance, but everyday use remains safe and simple for the child.