Provisioning fails with "The device is already set up" due to residual system account on SPRD/Unisoc device

Android

If you're seeing the error "The device is already set up" when trying to enroll a SPRD/Unisoc-based device in Esper, even after a factory wipe, this article will help you diagnose and resolve the issue.

Before you begin

This issue affects certain Android devices built on SPRD (Spreadtrum/Unisoc) chipsets. Check whether your device is affected by running an ADB command to inspect system accounts on the device.

How to check for residual system accounts

1. Connect your device to a computer with ADB installed.
2. Run the following command:

   adb shell dumpsys account

3. Look for an entry like this:

   Account {name=Phone, type=sprd.com.android.account.phone}

4. If you see an account with type sprd.com.android.account.phone or sprd.com.android.account.usim, your device has a residual system account that is blocking Esper enrollment.

Why this error occurs

Android's Device Owner provisioning process requires that no accounts exist on the device at enrollment time. Some SPRD-based devices come with a system-level phone account pre-registered by the manufacturer's firmware. This account survives factory resets because it's registered at the firmware level, not the user level. Even without a physical SIM card, the firmware's authenticator service re-registers the account on every boot, which prevents Esper from becoming the Device Owner.

How to resolve this issue

This issue requires intervention from your device manufacturer (ODM). Follow these steps:

1. Contact your device's manufacturer and request one of the following:
   • A modified firmware or system image that does not pre-register the sprd.com.android.account.phone account, or
   • A method to remove the account before enrollment (such as a pre-provisioning ADB command or factory reset script)
2. Once the manufacturer provides a clean firmware build, flash it to your device.
3. Verify the fix by running:

   adb shell dumpsys account

4. Confirm the output shows:

   Accounts: 0

5. Attempt Esper provisioning again using your standard method (QR code, Zero-Touch, or another enrollment method).

If the manufacturer cannot provide a fix

If your device manufacturer is unable to modify the firmware or is unresponsive, this device model may not be compatible with Esper enrollment. Contact Esper Support to discuss alternative solutions or to document the device as unsupported for your deployment.

Additional notes

• This issue is specific to SPRD/Unisoc chipsets and will not appear on devices with Qualcomm, MediaTek, or other chipsets.
• Performing additional factory resets will not resolve this issue, as the account is re-registered by the firmware on every boot.
• If you see a Google account (type=com.google) in addition to SPRD accounts, you must manually sign out of that Google account before enrollment, in addition to obtaining the manufacturer's firmware fix.
• This restriction applies to all Esper enrollment methods, including QR codes, Zero-Touch, KME, and NFC.

Still need help?

If you've followed these steps and continue to experience issues, submit a support ticket with the output of adb shell dumpsys account and your device model number. Our support team can help determine if there are additional options available for your specific device.