Android device still managed after Hexnode disenrollment is pendingSolved

Hello @im_dany ,

When a disenrollment command is triggered from Hexnode UEM, the command must reach the device for the MDM profile and associated restrictions to be removed from the physical device.

If the device is offline, not checking in, or unable to communicate with Hexnode, the Disenroll device action remains in the Pending state. Marking the device as disenrolled from the portal only updates its status in the console; it does not remove the MDM profile from the device unless the command is received and processed by the device.

In this situation, there are two possible outcomes:

1. If the device comes back online and can communicate with Hexnode, the pending disenrollment command may complete and remove management.
2. If the device cannot communicate with Hexnode anymore, the MDM profile cannot be removed remotely.

For an Android device that cannot receive the remote command, the usual recovery path is a manual factory reset, preferably through hardware recovery mode if the device settings are restricted.

Regards,
Simon Scott
Hexnode UEM

Okayy, but in my case the device still has the management policy active locally which blocks factory reset. It also blocks power-off, so I cannot turn the device off and use the Power + Volume key combination to boot into recovery mode. The device is basically stuck managed even though it is no longer active in the portal.

If the device cannot receive Hexnode commands and the active local policy also blocks power-off or factory reset, Hexnode cannot remove the management profile from the device remotely.

At that point, recovery mode or a standard factory reset may not be accessible from the device itself. The remaining practical option is to contact the device manufacturer or an authorized service center and have them re-flash the stock OS firmware onto the device.