Skip to main content
Yashwanth
Yashwanth
Level 1.5: Cupcake
April 6, 2026
Question

Motorola Moto G 5G (2022) Stuck in Reboot Screen

  • April 6, 2026
  • 2 replies
  • 53 views

Hi everyone,
 

I’m looking for guidance on an issue affecting multiple Motorola Moto G 5G (2022) devices that are currently stuck on the reboot screen and unable to boot into the system.
 

We’ve already tried several troubleshooting steps, including performing a hard reset and attempting to clear the app cache via recovery mode. However, the usual options such as “Wipe data/factory reset” and “Clear cache” are not available. The devices only show limited options like reboot system, bootloader, and power off.
 

Because of this, we’re unable to proceed with standard recovery or reset methods, and the devices remain unusable. Has anyone encountered a similar issue or found additional troubleshooting steps that might help resolve this? Any suggestions, especially around accessing full recovery mode or alternative recovery methods would be greatly appreciated.
 

Thanks in advance for your help!

2 replies

Yashwanth
YashwanthAuthor
Level 1.5: Cupcake
April 6, 2026

This is the screen currently displayed on the affected devices. We have observed this issue on models such as Moto G Power and Moto G 5G (2022), running Android versions 12, 13, and 15.

Moombas
Moombas
Level 4.4: KitKat
April 7, 2026

This can be because the manufacturer doesn’t provide these options in their oem (we know that from the past from HMD). In that case, reach out to the manufacturer if they can provide a tool to you to wipe the devices otherwise you may need to send them to repair (can generate costs).

You can verify that if you have devices yet unboxed if the options aren’t available there as well already.

Otherwise as this screen you show below points to an MDM, reach out to their support.

Yashwanth
YashwanthAuthor
Level 1.5: Cupcake
April 7, 2026

Thanks for your input and example of HMD. We’ve tested this with multiple OEMs including Vivo, Samsung, LG and Motorola, all with the same configurations and restrictions applied.

 

The behaviour is consistent across Vivo and Samsung devices, where everything works as expected. However, the issue appears only on certain Motorola devices (across different models and OS versions).

 

Based on this, it doesn’t seem to be related to MDM or configuration, but rather something specific to Motorola’s implementation/OEM limitations.

Moombas
Moombas
Level 4.4: KitKat
April 8, 2026

That’s why i asked you to check on a completely fresh device (not enrolled) out of the box.

And btw. Motorola provides a flash tool (Lenovo = Motorola): Software fix

BUT depending on your setup you can’t flash enrolled devices (we for example block this on our devices for example). And as always when it comes to flashing: Always on own risk.

Terms & ConditionsCookie settingsAccessibility statement