Enabling Device Owner Mode using ADB Driver
Android Debug Bridge (adb) is a command-line tool for communication between a computer and an Android device connected with it. It makes a number of device activities easier, such as installing and debugging applications and offers access to commands that are not traditionally accessible to a connected device.
On Android 5.0 (Lollipop) devices Meraki cannot enable Device Owner Mode without using ADB. This method can be used also for enrolling Android 6.0 + devices, although it is recommended for higher versions to use an over-the-air enrollment. See our Deployment Guide here for enrollment instructions and general information concerning Android Enterprise.
Note: Enabling Android Enterprise's kiosk mode requires both Device Owner enrollment and Android 6.0+.
Enabling Device Owner Mode via ADB
- First, download, install and configure the Android Debug Bridge (ADB) binary using below links for, Mac, Linux, Windows
- Download the latest Android SM app from HERE
- On a computer run the following command to initialize ADB:
- adb start-server
- Go to Settings
- Go to “About device” (Might be named slightly different)
- Click the “Build number” field 7 times. This will turn on “Developer options”
- Go back to Settings
- Go to “Developer options”
- Scroll down and enable “USB debugging”
- Your device might prompt you with a trust dialog. Click accept.
- adb install AndroidSM.apk
- ADB commands must be run in the same directory where the ADB binary was installed.
- You must be in the directory of your AndroidSM.apk file, or you must specify the full explicit path for the APK.
- Depending on hardware, this process may appear to hang after the transfer of the APK is complete. Wait until the process ends with Success.
- adb shell dpm set-device-owner com.meraki.sm/.DeviceAdmin