Android Enterprise device stuck on Hexnode screen and not visible in reportsSolved

Participant
Discussion
2 days ago Jul 14, 2026

An Android phone was scanned for Android Enterprise enrollment, but it never completed enrollment and now keeps booting to the Hexnode screen even after restarting. The device is not showing under Manage, All Devices, Disenrolled Devices, or Disenrollment Pending Devices. Does this mean the disenroll action is still pending, or is there another step needed when the device was never fully enrolled?

Also, after enrollment using a Microsoft 365 account, is there a way to force users to use that same account in Chrome on Android?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
1 day ago Jul 15, 2026
Marked SolutionPending Review

If the Android Enterprise enrollment was not completed, the device may not appear in the regular device inventory or in the Disenrolled Devices report. The Disenrolled Devices report is generally useful for devices that were successfully enrolled first and then disenrolled later.

When a device is stuck on the Hexnode provisioning screen after an incomplete Android Enterprise setup, restarting the device usually will not clear the provisioning state. The recommended fix is to factory reset the device and start the enrollment again.

For Android Enterprise Device Owner enrollment:

  1. Factory reset the Android device.
  2. During the initial setup, use the intended Android Enterprise enrollment method, such as QR code enrollment.
  3. Complete the setup flow without exiting provisioning midway.
  4. Once enrollment completes, confirm that the device appears under Manage > Devices in the Hexnode portal.

If the device is intended to be enrolled in another MDM instead, factory reset the device and enroll it into that MDM during the out-of-box setup flow.

Marked SolutionPending Review
Participant
1 day ago Jul 15, 2026
Marked SolutionPending Review

Factory reset worked for the stuck enrollment screen. The device was never fully enrolled, so that explains why it was not showing in the device reports.

Marked SolutionPending Review
Hexnode Expert
3 hours ago Jul 16, 2026
Marked SolutionPending Review

For the Chrome account part: Hexnode cannot remotely force Chrome on Android to sign in with the same Microsoft 365 account that was used during device enrollment.

If Chrome supports the required managed app configuration for the account-related setting you want to apply, you can try deploying it through an app configuration policy. However, there is no direct Hexnode setting to enforce that the Chrome sign-in account must match the Microsoft 365 enrollment account. So the practical options are:

  • Use app configuration policies if Chrome exposes a supported managed configuration for the required behavior.
  • Otherwise, users will need to add or use the Chrome account manually, and matching it with the enrollment account cannot be enforced remotely.
Save