[Bug Report] Xiaomi Redmi 12C — Android Enterprise Fully Managed Enrollment Fails via Zero-touch and QR Code with Microsoft Intune

Overview

We are a Microsoft-certified and Google-certified partner providing enterprise mobility management support. We are reporting a reproducible Android Enterprise enrollment failure on Xiaomi Redmi 12C (HyperOS 1.0.16.0.UCVMIXM) that affects both Zero-touch enrollment and QR code-based fully managed provisioning with Microsoft Intune.

This issue was first observed on MIUI 14 and has persisted through the subsequent HyperOS 1 upgrade without any improvement. We are therefore treating this as a device-specific issue on certain Xiaomi models, rather than a problem introduced by HyperOS specifically.

We have already reported this issue to both Microsoft and Xiaomi. Despite more than six months having passed, neither party has made meaningful progress toward a resolution. Both Microsoft Intune and the Redmi 12C remain listed in the AER directory as compatible, and enterprise customers continue to purchase and deploy this combination based on that listing. We are therefore bringing this issue to Google's attention and respectfully requesting Google's involvement in resolving this matter, given Google's responsibility for the integrity of the AER certification program.

Device information

• Device: Xiaomi Redmi 12C
• OS: Android 14 (UP1A.231005.007)
• HyperOS version: 1.0.16.0.UCVMIXM (Global ROM)
• Google Play Services: 23.42.12 (190400-574052649)
• AER validated: Yes (Android 12, 13, 14 — validated August 2023)
• Zero-touch support: Yes (per AER directory)
• IMEI registered: IMEI 1 (SIM slot 1, numerically lower value)

Issue 1 — Zero-touch enrollment (Intune, Fully Managed)

After factory reset with a valid Zero-touch configuration assigned in the portal, the following flow is observed:

  Wi-Fi connected
  → "Checking info..." (waiting screen)
  → Work setup walkthrough
  → "Just a sec..." (waiting screen)
  → Error dialog appears:
      Title:  "Redmi 12C is already set up"
      Body:   "If you have questions, contact your IT admin"
  → Tapping OK prompts "Reset phone"

The error appears after the work setup walkthrough completes, indicating the setup wizard proceeds further than the initial Wi-Fi check but fails at the point where Device Owner provisioning should be committed.

Confirmed behaviors:

• Removing the device from the Zero-touch portal allows normal setup to proceed
• Re-adding the device to the portal reproduces the error consistently
• The error occurs regardless of which Configuration is assigned
• The error occurs with both Microsoft Intune DPC and TestDPC (see Issue 1b below)

Issue 1b — Zero-touch enrollment (TestDPC)

The same failure is reproduced with TestDPC, confirming this is not an Intune-specific issue:

  Wi-Fi connected
  → "Checking info..." (waiting screen)
  → TestDPC "How will you use this phone?" screen — "Use for work only" selected
  → Work setup walkthrough
  → "Just a sec..." (waiting screen)
  → Error dialog:
      Title:  "Redmi 12C is already set up"
      Body:   "If you have questions, contact your IT admin"
  → Tapping OK prompts "Reset phone"

Since TestDPC reproduces the identical error at the identical step, the root cause is confirmed to be in device's provisioning layer, not in the EMM configuration.

Issue 2 — QR code enrollment (Intune, Fully Managed)

Note: Intune Fully Managed enrollment does not use Google account sign-in. Authentication is performed via Microsoft Entra ID within a WebView.

The following flow is observed:

  QR code scanned
  → Wi-Fi connected
  → "Checking info..." (waiting screen)
  → Work setup walkthrough
  → Entra ID login screen (WebView)
  → User signs in with licensed Microsoft 365 account
  → Enrollment is initiated (WebView at manage.microsoft.com)
  → "Setting up device... Less than a minute" screen
  → Returns to Entra ID account selection screen
  → Loop repeats indefinitely

The loop occurs after Entra ID authentication succeeds and the enrollment WebView at manage.microsoft.com begins processing. This indicates Device Owner provisioning is initiated but not committed, causing the session to reset.

Confirmed behaviors:

• Reproduced on a brand-new Intune tenant (ruling out tenant misconfiguration)
• Reproduced with Conditional Access policies fully disabled
• Works correctly on all other tested AER-certified devices with the same tenant and configuration
• TestDPC completes QR code enrollment successfully on the same device

Root cause analysis

Issue 1 / 1b: The "already set up" error appears after the work setup walkthrough, at the point where Device Owner should be committed to the system. HyperOS 1's setup wizard appears to reject the Device Owner grant at this stage, then surfaces the error dialog regardless of which DPC is used. This is a platform-level failure in HyperOS 1's handling of the Android Enterprise provisioning API.

Issue 2: The QR code loop occurs after Entra ID authentication completes and manage.microsoft.com initiates enrollment. Since TestDPC succeeds via QR code on the same device, the DPC provisioning mechanism is functional. The failure is specific to the Device Owner commitment step when triggered via the Intune enrollment flow, suggesting HyperOS 1 does not correctly handle the provisioning callback in this context.

Impact

This device is AER-certified with Zero-touch support confirmed in the AER directory. The inability to complete fully managed enrollment via either Zero-touch or QR code contradicts the AER certification criteria and prevents enterprise deployment at scale.

Steps to reproduce

Issue 1 (Zero-touch, any DPC):

1. Register Redmi 12C IMEI 1 in the Zero-touch portal
2. Assign a valid Fully Managed Configuration (Intune or TestDPC)
3. Factory reset the device
4. Connect to Wi-Fi during setup
5. Proceed through the work setup walkthrough
6. Observe: "Redmi 12C is already set up" error dialog after "Just a sec..." screen

Issue 2 (QR code, Intune):

1. Factory reset the device
2. Tap the screen 6 times on the welcome screen to launch the QR reader
3. Scan a valid Intune Fully Managed QR code
4. Connect to Wi-Fi and proceed through the work setup walkthrough
5. Sign in with a licensed Microsoft 365 account via the Entra ID WebView
6. Observe: infinite loop between Entra ID account selection and "Setting up device..." screen

Expected behavior

Issue 1: Device should complete Device Owner provisioning and hand off to the DPC after "Just a sec..." without surfacing the "already set up" error.

Issue 2: Device should complete Device Owner provisioning after Entra ID authentication and successfully enroll in Intune.

Vendor engagement history

• Xiaomi: Reported. Response was that the issue is on Microsoft's side because TestDPC can complete QR code enrollment. No further action taken.
• Microsoft: Reported. Response was that the issue is on Xiaomi's side because enrollment works correctly on Pixel devices. No further action taken.
• Status: Unresolved for 6+ months. No official statement or fix committed by either party.

Multiple independent reports of the same issue exist in Microsoft Q&A and Microsoft Tech Community forums, indicating this affects a broader set of customers and deployments.

Reference forum threads (no official resolution in any of these):

• https://learn.microsoft.com/en-us/answers/questions/2118554/intune-enrollment-loop-xiaomi-redmi-14c
• https://learn.microsoft.com/en-us/answers/questions/2200643/intune-enrollment-fails-infinite-loop-at-pick-an-a

Request to Google

Both Microsoft Intune and the Redmi 12C are listed in the AER directory as compatible with Android Enterprise. Customers and partners rely on this listing as a signal of verified interoperability. The issues documented here demonstrate that this combination does not function as certified, and that the underlying problem has existed since at least MIUI 14.

We respectfully request that Google:

1. Investigate the Xiaomi Redmi 12C setup wizard behavior that prevents Device Owner provisioning from completing, a problem that predates HyperOS and has been present since MIUI 14
2. Engage Xiaomi directly to address the platform-level incompatibility identified in this report
3. Consider the accuracy of the current AER listing for Redmi 12C until the issue is resolved
4. Request that both Xiaomi and Microsoft provide an official public statement and resolution timeline, given that multiple enterprise customers have been affected and neither party has issued any formal response to date
5. Provide guidance on the expected timeline for resolution

The AER program's value to the enterprise community depends on the accuracy and reliability of its certifications. We trust that Google will take appropriate action to maintain that standard.

Best regards,

Sho Sawada, CEO @ ZUNDA Inc.