QR Code provisioning loops on Google Policy Acceptance page: switch from Provisioning Template to Blueprint to resolve

Android

If your device gets stuck in a loop on the Google Policy Acceptance screen during QR code enrollment, you may be able to resolve this by switching from a Provisioning Template to a Blueprint. This article walks you through identifying the issue and testing an alternative enrollment method.

Before you begin

This issue has been observed on Lenovo Tab K10 Gen 2 (TB311XU) devices during QR code enrollment using a Provisioning Template. The device repeatedly returns to the Google Policy Acceptance screen instead of advancing to the next enrollment step, and factory reset may not be available while the device is stuck in this state.

Note that Esper fully supports QR code enrollment on Lenovo Tab K10 Gen 2 devices using Android Enterprise, so this is likely a configuration issue rather than a platform limitation.

Step 1: Identify your Provisioning Template

1. In the Esper Console, go to Provisioning → Provisioning Templates.
2. Locate the template you used to generate the QR code for this device. If multiple templates have similar names (for example, templates named "Sentinel" or similar), verify the correct one by checking the QR code link or the template creation timestamp.

Step 2: Review your Provisioning Template configuration

1. Open the template you identified in Step 1.
2. Check for any settings that might interfere with the Google Policy Acceptance step. Pay particular attention to:
   • Google account policy enforcement settings
   • Network proxy settings
   • Enterprise restrictions or policies

Step 3: Test enrollment using a Blueprint instead

1. In the Esper Console, go to Provisioning → Blueprints.
2. Create a new Blueprint or select an existing one.
3. Generate a new QR code from this Blueprint.
4. Attempt enrollment on your Lenovo Tab K10 Gen 2 device using the new QR code.

Step 4: Interpret your results

If Blueprint enrollment succeeds: Your Provisioning Template configuration is likely the cause. Review the template settings in detail or recreate the template from scratch. Remove or adjust any non-default policies one at a time to identify which setting is causing the loop.

If Blueprint enrollment also loops: The issue may be device-firmware-related. Proceed to the next section.

Step 5: Verify successful enrollment

Enrollment is confirmed successful when:

• The device completes the full provisioning flow without looping
• The device appears as Online and Enrolled under Devices & Groups in the Esper Console
• The assigned Blueprint or Provisioning Template policies show as applied

If the device cannot factory reset

If the device is stuck in the enrollment loop and cannot factory reset through standard device settings, try a hardware factory reset:

1. Power off the device completely.
2. Hold Volume Down + Power together to enter recovery mode.
3. Select Wipe data/factory reset from the recovery menu.

For device-specific instructions, refer to Lenovo's recovery documentation for the TB311XU model.

If Blueprint enrollment also loops

If the looping persists even when using a Blueprint, collect diagnostic information:

1. If the device is accessible, go to Devices & Groups → [Device Name] → Actions → Request Bug Report to retrieve logs from the device.
2. Alternatively, pull ADB logs using the command: adb bugreport
3. Contact Esper Support and share the logs for further investigation.

Still need help?

If you've completed these steps and your device is still looping on the Google Policy Acceptance screen, or if you encounter any other issues during enrollment, submit a support ticket. Include the device model, the provisioning method you used (Template or Blueprint), and any error messages or logs you've collected.