# How to Enroll Android Devices Without Camera?

Last updated: July 24, 2026

> Enroll Android devices without cameras into Mobile Device Manager Plus using the Device Owner provisioning tool via ADB with USB or Wireless Debugging; requires a Windows/macOS computer, USB cable, no Google account logged in, and a custom ManageEngine MDM Self Service app obtained from Support with Knox JSON configuration.

In certain high-security environments, such as defence organizations and restricted zones, camera-equipped devices are often banned due to security concerns. This document provides step-by-step instructions for administrators to enroll Android devices that do not have a camera.

## Pre-requisites

1. A Windows/macOS computer.
2. USB cable to connect the device to the computer or laptop.
3. Ensure that no Google account is logged in or syncing data on the device.

## Steps to enroll Android devices without camera

1. On the Laptop or computer, download the Device Owner provisioning tool from the following link for [Windows](https://www.manageengine.com/mobile-device-management/help/script/makedeviceowner.zip) or [Mac](https://www.manageengine.com/mobile-device-management/help/script/makedeviceowner.zip).
2. After downloading, extract all the files in the zip file to a location on your machine.
3. To proceed with the enrollment you need the Custom ManageEngine MDM Self Service app (previously ManageEngine MDM app). Reach out to [MDM support](https://www.manageengine.com/mobile-device-management/support.html) with JSON details which are present on the MDM Console->Enrollment->Knox Device Enrollment for getting the Custom Manageengine MDM apk file for the enrollment.

   ![How to Enroll Android Devices Without Camera? illustration 3](https://cdn.manageengine.com/mobile-device-management/images/android_knox_json.png)

4. Place the custom APK (MDMAndroidAgent.apk) file provided by [MDM support](https://www.manageengine.com/mobile-device-management/support.html) where the adb.exe file is present (`C:\Users\YourUsername\Downloads\makedeviceowner\makedeviceowner\`).

   ![How to Enroll Android Devices Without Camera? illustration 4](https://cdn.manageengine.com/mobile-device-management/images/android_adb.png)

5. **Enable Developer Options**
   - **USB Debugging:**
     1. On the Android device, go to Settings > About Phone.
     2. Tap Build Number 7 times to enable Developer Options.
     3. Go back to Settings > System > Developer Options.
     4. Enable USB Debugging.

        ![How to Enroll Android Devices Without Camera? illustration 5](https://www.manageengine.com/mobile-device-management/help/images/ADB-1.png)

     5. Connect the Android device to the computer via USB.
     6. On the device, if prompted, allow USB Debugging by selecting Allow on the pop-up.

        ![How to Enroll Android Devices Without Camera? illustration 6](https://www.manageengine.com/mobile-device-management/help/images/ADB-2.gif)

   - **Wireless Debugging:** If USB debugging is not an option, follow these steps to enable debugging via the Wireless Debugging method:
     1. Reset the device and ensure that both the device and PC are connected to the same Wi-Fi network.
     2. Navigate to Settings → Developer Options → Enable Wireless Debugging. When prompted with "Allow wireless debugging on this network?", select Allow.
     3. In Command Prompt, enter the following command to connect ADB via the device’s IP address:

        ```bash
        adb connect <ip_address>:<port>
        ```

     4. On the android device, go to Pair Device with Pairing Code under the Wireless Debugging option. In Command Prompt, enter the pairing command:

        ```bash
        adb pair <ip_address>:<port>
        ```

     5. Enter the pairing code displayed on the device when prompted.
6. Now open the Command prompt (for a windows device) or terminal (for a Mac device).
7. Open the zip file folder where **adb.exe** is present in the command prompt/terminal. Execute the below commands:

   ```bash
   Command Prompt: adb devices
   Terminal: ./adb devices
   ```

   Example:

   ```bash
   cd C:\Users\YourUsername\Downloads\makedeviceowner\makedeviceowner> adb devices
   ```

   If the device is listed, proceed. If not, recheck USB debugging and drivers.

   ```bash
   Command Prompt: makedeviceowner.bat
   Terminal: makedeviceowner.sh
   ```

   If the execution is successful, you can see a success message in the command prompt.

   **For Windows:**

   ![How to Enroll Android Devices Without Camera? illustration 7](https://www.manageengine.com/mobile-device-management/help/images/ADB-3.png)

   **For Mac:**

   ![How to Enroll Android Devices Without Camera? illustration 8](https://www.manageengine.com/mobile-device-management/help/images/ADB-4.png)

8. Open the installed **ManageEngine MDM** app on the device.
9. The app will automatically attempt enrollment.
10. Follow the additional on-screen instructions if required.
11. After succesful enrollment, ensure to **Disable Developer options (USB/Wireless Debugging)**.

## Frequently asked questions

### Why would I need to enroll an Android device that has no camera?

In high-security environments such as defence organizations and restricted zones, camera-equipped devices are often banned due to security concerns, so administrators need a way to enroll these camera-less devices into MDM.

### What do I need before enrolling a device without a camera?

You need a Windows or macOS computer, a USB cable to connect the device, and you must ensure no Google account is logged in or syncing data on the device.

### Why do I need a custom APK from MDM support for this enrollment?

The enrollment uses the Device Owner provisioning tool with a Custom ManageEngine MDM Self Service app (previously ManageEngine MDM app) APK that MDM support generates using the Knox JSON details from the MDM Console's Enrollment > Knox Device Enrollment page.

### What should I do after the device is successfully enrolled?

Once the Self Service app (previously ME MDM app) finishes enrolling the device automatically, disable Developer Options (USB/Wireless Debugging) on the device.