Failed Pushing Device Details error during Seamless enrollment: factory reset via Esper logo tap

Android

Title: Seamless enrollment stuck on "Failed Pushing Device Details" — factory reset to recover

When a device pre-installed with Esper by an OEM or reseller encounters a network problem during first-time Seamless enrollment, it displays a Failed Pushing Device Details error and freezes on the provisioning screen with no access to Android Settings.

Why this happens

Seamless enrollment calls Esper's provisioning API endpoints during setup. If the network drops, a firewall blocks those endpoints, or a proxy intercepts the traffic, the handshake fails mid-flow and the device cannot recover on its own — it has no path back to Settings to retry or connect to a different network.

Recover the device and complete enrollment

Trigger the hidden factory reset. On the stuck device, tap the Esper logo rapidly and repeatedly (approximately 7–10 times in quick succession) on the provisioning or error screen. A Factory Reset option will appear. This gesture is built into the Esper Agent on supported OEM builds specifically to allow recovery when the device is locked to the provisioning screen.
Confirm the factory reset. Select Factory Reset and confirm when prompted. The device will wipe and reboot to its factory state.
Connect to a different network before retrying enrollment. Once the device reaches the initial setup screen, connect it to a network that is not subject to the same firewall or proxy rules — for example, a mobile hotspot from a smartphone. This bypasses the network conditions that caused the original failure.
Allow Seamless enrollment to restart automatically. On OEM-preloaded devices, Seamless enrollment triggers automatically after the device connects to the internet. If your OEM provided manual provisioning instructions, follow those instead.
Confirm the device appears in the Esper Console. Navigate to Devices & Groups and confirm the device is listed with a status of Active or Online.

Verify: The device should appear in Devices & Groups with a status of Active or Online within 5 minutes of completing enrollment. If it appears but shows Inactive, open the device record and check the Activity Feed for any follow-on errors.

If the Esper logo tap does not reveal the factory reset option

The recovery gesture may not be available on all OEM builds or Esper Agent versions. Contact your OEM or device reseller directly to perform a hardware factory reset using the physical button combination or recovery mode specific to your device model. Once the device is wiped, return to step 3 above.

If the device fails again after switching networks

If enrollment fails on the alternate network as well, the issue is unlikely to be network-specific. Before contacting support, collect the following information:

Esper device serial number (visible on the error screen or device packaging)
Hardware serial number printed on the device
Esper Agent version (visible on the provisioning screen or obtainable via ADB)
Any error codes or on-screen messages photographed at the time of failure
Any ADB logs captured during the failed enrollment attempt

If the device keeps failing on your original network

A firewall or proxy is likely blocking Esper's provisioning API endpoints. Share Esper's network requirements documentation with your network administrator and ask them to whitelist the required domains and ports. Retry enrollment on the original network after the firewall rules are updated.

If this doesn't resolve it

If the device still cannot complete enrollment after a factory reset, a network change, and verifying firewall rules, contact Esper Support and provide the collected information listed above along with a description of each step already attempted. This allows the support team to investigate provisioning logs without needing to retrace steps already completed.

Still need help?

If you're still experiencing "Failed Pushing Device Details" errors during Seamless enrollment, submit a support ticket and include your device model, the exact error message, and the steps you've already taken to resolve the issue (such as factory reset attempts).