EDP provisioning stuck at 53%–84% via Wireless Debugging on Rockchip devices (RK3576 / RK3399)

Android

When provisioning a Rockchip RK3576 or RK3399 device using Wireless Debugging in the Esper Device Provisioner (EDP), the progress bar stalls between 53% and 84% and does not advance — or EDP becomes unresponsive entirely.

Why this happens

Rockchip RK3576 and RK3399 processors respond more slowly than typical Android hardware during the Esper Agent installation phase. EDP does not time out automatically, so the progress bar appears frozen even though installation is still running in the background. Network instability between the host machine and the device over the ADB Wireless Debugging connection can also interrupt the installation mid-way.

Step 1: Wait before taking any action

1. Do not close EDP. Leave the provisioning session running.
2. Wait 5–10 minutes after the progress bar stalls. On Rockchip devices, the Esper Agent installation phase is significantly slower than the earlier steps, and the bar will resume moving once installation completes.
3. If the bar advances beyond 84%, allow the process to finish without interruption.

Step 2: Verify network connectivity

Wireless Debugging relies on a stable ADB connection over your local network. Dropped packets or firewall rules that block Esper endpoints will cause provisioning to stall.

1. Confirm your host machine and the device can reach all required Esper network endpoints. See Firewall Requirements for the full list.
2. If you cannot confirm endpoint access, retry provisioning using a different network — for example, a mobile hotspot tethered to the host machine — to rule out local network interference.
3. If your host machine connects to the network over Wi-Fi, switch to wired Ethernet to eliminate wireless interference on the ADB connection.

Step 3: Recover from a frozen EDP session

If EDP has stopped responding entirely and the progress bar has not moved after 10 minutes, follow these steps to collect diagnostic logs before restarting.

1. Open a terminal on your host machine.
2. Capture ADB logs from the device before closing EDP. Replace <device-ip> and <port> with the values shown in the Wireless Debugging settings on the device:

   adb -s <device-ip>:<port> logcat -d > edp_device_log.txt

   Save this file — you will need it if the issue persists.
3. Force-quit the EDP application.
4. Reboot the target device.
5. Re-enable Wireless Debugging on the device under Settings → Developer Options → Wireless Debugging and note the new IP address and port.
6. Restart EDP and begin a new provisioning session from the beginning.

Verify

Verify: Once provisioning completes, log in to the Esper Console and navigate to Devices & Groups. Locate the device in the list and confirm its status shows Online and that your assigned blueprint has been applied. The device should reach this state within 5 minutes of EDP reporting completion.

If this doesn't resolve it

If provisioning stalls consistently across multiple fresh attempts and on different networks, contact Esper Support with the following information:

• EDP version number
• Host operating system and version (Windows or macOS)
• Device firmware and build number — found at Settings → About Device
• The edp_device_log.txt file captured in Step 3
• EDP application logs from the host machine (location varies by OS)
• The exact percentage where provisioning consistently stalls
• Number of devices affected (single device or fleet)

--- **Improved title:** EDP provisioning stalls at 53%–84% on Rockchip devices — how to recover

Still need help?

If you're still experiencing provisioning issues on your Rockchip devices, please submit a support ticket and include your device model (RK3576 or RK3399), the percentage where provisioning is stuck, your wireless debugging setup details, and any error logs from the provisioning process.