Hey everyone, running into a super bizarre issue today and wondering if anyone else has seen this in their fleet. I just enrolled a Samsung device into Hexnode, pushed our standard stack of enterprise apps, and applied our usual base policies. Seemed like business as usual, but right after it finished syncing, the phone rebooted itself straight into Android Recovery mode!
I’ve used this exact model before and have never seen this happen. Has anyone dealt with similar issue before?
11 Views
Oh man, I feel your pain! If your test device takes the policy and apps just fine, then you’re almost certainly looking at an isolated hardware or OS-level fluke on that specific phone.
When it happened to me, it literally turned out to be a sticky volume rocker case that forced the device into recovery during a standard MDM-triggered reboot! If the physical buttons are fine, I’d bet money on a couple of other things: sometimes a corrupted background OTA update trips up when the MDM forces a sync, or you get a weird app/cache conflict that panics the OS. I’ve also seen failing flash storage, or just plain insufficient storage space; cause a bootloop into recovery when the system tries to aggressively install multiple APKs at once. If a factory wipe from that recovery menu doesn’t get it acting right, you might just have a hardware dud on your hands.
Don't have an account? Sign up
