Seamless Provisioning does not trigger on device: OEM firmware must have Esper baked in for seamless provisioning to work

Android

This article explains why Seamless Provisioning may not activate on your device after boot, and what to do instead. Seamless Provisioning requires that your device manufacturer has pre-installed the Esper agent in the device firmware. If it hasn't been, you'll need to use an alternative provisioning method.

Understanding the limitation

Seamless Provisioning works only when your device manufacturer has integrated the Esper agent directly into the device's firmware before shipment. During first boot, the pre-installed agent detects your device's pre-registration in the Esper Console and automatically begins the managed provisioning flow.

If the Esper agent is not baked into your device's firmware, no component exists at first boot to initiate this handshake—even if you've correctly pre-registered the device serial number or IMEI in the Esper Console. the Esper Console registration record is valid, but the device lacks the firmware-side component needed to act on it.

Seamless Provisioning cannot be recovered on devices without Esper in the firmware. You must switch to an alternative provisioning method.

Before you begin

Confirm with your device manufacturer whether an Esper-integrated firmware build exists for your device model. If not, Seamless Provisioning is not supported for that hardware.

How to switch to an alternative provisioning method

In the Esper Console, navigate to Devices & Groups, locate your device, click Actions, and select Remove Registration to clean up the pre-registration record.
Choose one of the following alternative methods:
- QR Code Provisioning: Complete the standard Android setup, enable Wi-Fi, then initiate provisioning via the Esper Console QR code flow.
- ADB Provisioning: Allow the device to complete standard Android setup (including enabling USB Debugging under Developer Options), then use the Esper Device Provisioner tool. Note: This method requires manual device interaction and is not suitable for automated out-of-box provisioning.
After reprovisioning, verify the device appears in Devices & Groups with status Online or Active, and that the assigned Blueprint has been applied.

Important notes

Seamless Provisioning is an OEM partnership feature that requires explicit manufacturer integration. Not all Android devices support it, regardless of Android version.
The Esper Console status "This device is registered and ready to onboard" confirms only that the pre-registration record exists—it does not confirm that your physical device has the firmware capability to act on it.
Registering by IMEI instead of serial number does not resolve missing firmware integration. Both identifiers rely on the same firmware-side agent.
If your device has only cellular connectivity at boot (no Wi-Fi), verify that your device manufacturer's OOBE allows network access over cellular during initial setup. Some OEMs restrict network access during OOBE to Wi-Fi only.

Still need help?

If your device manufacturer confirms that Esper is baked into the firmware but Seamless Provisioning still fails, or if you need assistance selecting the right provisioning method for your use case, contact Esper Support. include your device serial number, IMEI, Android version, and exact OEM firmware build number.