pdf icon
Category Filter

Device Owner Provisioning using Android Debug Bridge (ADB)

This method is recommended for Device Owner provisioning only when the Android device cannot be provisioned using Near-Field Communication (NFC). This Android provisioning method can also be used for enrolling devices without Google Services as Device Owner (fully managed corporate device). As the name suggests this method uses Android Debug Bridge (or ADB) to provision devices as Device Owner and is applicable for devices running 5.0 or later versions.

Note: For a device to be successfully enrolled using ADB enrollment, the device shouldn't have a passcode configured manually. Post enrollment, even if the device had a passcode configured earlier and is now removed or if the device currently has a passcode configured, the inventory actions clear/reset passcode will fail. In this case, wipe the device and enroll the device again.

Steps for provisioning

These are the steps you should provision in the mobile device to configure ADB enrollment:

  1. Factory reset the mobile device to be managed, if it is already in use or boot up if it is a new device.
  2. Follow the on-screen instructions to configure basic device settings and ensure you do not have any Google account logged in or syncing any data.
  3. Go to Settings > About Device, and tap on the Build Number for 7 times to enable Developer mode.
  4. Now, navigate back to Settings and select Developer Options . Then enable USB debugging.
  5. ADB 1

  6. Click Allow to confirm the USB Debugging pop-up appearing on the device.
  7. ADB 2

  8. Again navigate back to Settings and select Security. Enable Install from unknown sources (only applicable for devices with OS version lesser than or equal to 7.1.1 )
  9. Now connect your device to the Mac machine or Windows machine which is used to configure ADB Enrollment.
  10. Enable the option Transferring files on the mobile device to which the USB is connected.
  11. In the machine download the Device Owner provisioning tool from the following link for Windows or Mac.


      The Device Owner Provisioning file should be downloaded once every 2 months to get the updated app. The updated app can be pushed to new devices or be used for future enrollments.

  12. After downloading, extract all the files in the zip file to a location on your machine.
  13. Now open the Command prompt (for a windows device) or terminal (for a Mac device).
  14. Open the zip file folder in the command prompt/terminal and execute the command makedeviceowner.bat for windows or makedeviceowner.sh for Mac OS.
  15. The ME MDM app will be installed, and the Device owner profile will be configured after the successful execution of the command. If the execution is successful, you can see a success message in the command prompt as shown below:
    • For Windows
    • ADB  3

    • For Mac
    • ADB 4

  16. Ensure the Google Play app running on the device is the latest version. You can also update the Google Play app to the latest version.
  17. Now open the ME MDM app in the mobile device and Scan QR, by navigating to Enrollment -> Android -> QR Code Enrollment in the MDM web console. Once the QR code is scanned, the device will be listed under the EMM token enrollment view.
  18. You can then assign users to the enrolled devices either individually or in bulk using a CSV file, to complete enrollment.

Troubleshooting tips

  • While trying to enroll a Xiaomi device, the command makedeviceowner.bat does not get executed and displays an error.
  • A few Xiaomi devices cannot be enrolled using ADB enrollment method if MIUI optimization is turned on. To enroll these devices, turn off MIUI optimization by navigating to Settings ->Build number. Tap on the build number 6 to 8 times to enable Developer options and disable MIUI optimization. Perform the above mentioned steps again to successfully enroll these devices.


Jump To