RedMagic Android Enterprise enrollment stuck on Google Services loopSolved

Hi @mila_beck,

This behavior can occur on some devices with heavily customized Android setup wizards. The manufacturer’s setup flow may conflict with the Android Enterprise provisioning handshake, which can cause the Google Services acceptance screen to reload repeatedly.

For this type of case, try enrolling the device using the Android Enterprise DPC identifier instead of the standard QR flow:

1. Factory reset the device.
2. Start setup from the first welcome screen.
3. Select language and connect to a stable Wi-Fi network or mobile hotspot.
4. When the Google account sign-in field appears, do not enter a personal Google account.
5. Enter afw#hexnodemdm as the setup code.
6. Continue with the Hexnode enrollment flow.

If the device reaches a “Begin enrollment process” screen and asks for a custom server URL, enter your Hexnode portal server URL manually. If QR enrollment is offered on that screen, use the Open Enrollment QR code rather than the Android Enterprise QR code from the Android Enterprise enrollment section.

Regards,
Sienna Carter
Hexnode UEM

I ran into something similar on a custom Android build. The regular Android Enterprise QR scanner opened fine, but scanning the AE QR code kept failing or sent the device back into setup. Removing the Wi-Fi config from the enrollment profile didn’t change much for me either. Using “afw#hexnodemdm” got me further than “afw#hexnode”.