QR code enrollment loops on Google Policy Acceptance screen — switch to Blueprint
Android
When enrolling a device via QR code using a Provisioning Template, the device repeatedly returns to the Google Policy Acceptance screen instead of advancing through the enrollment flow, and the standard factory reset option may be unavailable while the device is stuck.
Why this happens
Certain Provisioning Template settings — such as Google account policy enforcement, network proxy configuration, or enterprise restrictions — can conflict with the Google Policy Acceptance step during QR code enrollment. Esper fully supports QR code enrollment via Android Enterprise; the loop indicates a template configuration conflict rather than a platform or device limitation.
Steps
-
Identify the Provisioning Template used to generate the QR code.
Navigate to Provisioning → Provisioning Templates in the Esper Console. Locate the template used for this enrollment. If multiple templates have similar names, confirm the correct one by checking the QR code link or the template creation timestamp. -
Review the template for settings that conflict with Google Policy Acceptance.
Open the template and check the following settings, as any of these can interrupt the Google Policy Acceptance step:- Google account policy enforcement
- Network proxy settings
- Enterprise restrictions or policies
-
Create or select a Blueprint to use as an alternative enrollment method.
Navigate to Provisioning → Blueprints in the Esper Console. Create a new blueprint with default settings, or select an existing one that does not replicate the suspect template configuration. Using a clean Blueprint isolates whether the loop is caused by the template or by the device itself. -
Generate a new QR code from the Blueprint.
Open the blueprint, generate a QR code, and note which blueprint the code corresponds to for later verification. -
Attempt enrollment using the new QR code.
Factory reset the device (see the hardware reset procedure below if the standard reset option is unavailable), then scan the Blueprint QR code to begin enrollment. -
Interpret the result and act accordingly.
- If Blueprint enrollment succeeds: The Provisioning Template configuration is the cause. Return to Provisioning → Provisioning Templates, open the original template, and disable or adjust non-default policies one at a time — re-testing enrollment after each change — until the conflicting setting is identified.
- If Blueprint enrollment also loops: The issue is likely firmware-related. Collect the device model, firmware version, and Android version, then contact Esper Support as described below.
Hardware factory reset (if the standard reset option is unavailable)
If the device is stuck in the enrollment loop and the factory reset option is inaccessible through device settings:
- Power off the device completely.
- Hold Volume Down + Power simultaneously until recovery mode loads.
- Select Wipe data / Factory reset from the recovery menu.
For model-specific recovery instructions, refer to Lenovo's official documentation for the TB311XU.
Verify
Verify: Enrollment is complete when the device finishes the full provisioning flow without returning to the Google Policy Acceptance screen, appears with a status of Online under Devices & Groups in the Esper Console, and the assigned Blueprint policies are shown as applied on the device detail page.
If this doesn't resolve it
If the loop persists after switching to a Blueprint, contact Esper Support and include the following information to speed up diagnosis:
- Device model and firmware version
- Android version on the device
- Screenshot or recording of the enrollment loop
- Name of the Provisioning Template and Blueprint tested
- Whether the loop occurs with both the template and the Blueprint QR code
Still need help?
If you're still experiencing QR code enrollment loops on the Google Policy Acceptance screen, please submit a support ticket and include details about your device model, Android version, and whether you've already attempted switching to Blueprint enrollment.
Please sign in to leave a comment.
Comments
0 comments