Cannot resend wipe after marking an offline Samsung Android device as disenrolledSolved

Participant
Discussion
1 day ago Sep 21, 2026

I accidentally used Mark as Disenrolled on a Samsung Android device before it completed a remote wipe. The device was offline when the wipe was sent, so it never checked in afterward. Now the device is no longer managed in Hexnode, and I cannot resend the wipe command.

Manual reset also seems blocked because the policy on the device disallows factory reset and advanced factory reset. Is there any way to restore the managed device record so I can send the wipe again, or recover the device another way?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
48 minutes ago Sep 22, 2026
Marked SolutionPending Review

Once an Android device is marked as disenrolled, Hexnode can no longer communicate with it as a managed device. The managed connection is severed, so the device record cannot be restored for sending new remote actions such as Remote Wipe.

If the device had already received and acknowledged the wipe command before being marked as disenrolled, the wipe would complete when the device came online. However, if the device was offline when the wipe was sent, the command would not have reached the device. After the device is marked as disenrolled, Hexnode cannot resend that command.

In this situation, the device must be reset manually and then re-enrolled. However, if factory reset and advanced factory reset restrictions were applied through policy, those restrictions may still prevent reset methods such as device settings reset, ADB-based reset, or hardware key reset.

Regards.
Mary Romero

Save