This is caused by a glitch happening while the OS is loading, so the smartphone tries to reboot multiple times to fix this glitch and it never turns on.
If an error is generated when carrying out an update or for some other reason your Motorola Moto G restarts and after the first marked animations the smartphone remains frozen on a black display, you can return to the factory state without having to play commands or connect it to any PC. Motorola teaches this very precisely on its technical support page. If you google a bit, you will find other much more violent choices that lead to unlocking the bootloader, losing the warranty of the terminal. Consequently, it is preferable to continue the steps now:
IMPORTANT: Using this feature deletes each and every item on the device. The reboot will require a minimum battery level of 25%. If you can’t reboot, please charge it for 20-30 minutes and also try again.
My phone keeps turning on and off, what do I do?
The first thing is not to panic, there is a solution. You need to first estimate the various occasions that triggered the issue with your phone:
- Wrong recent updates
- Downloads of malicious apps or with progress failures
- unlocked boot manager and custom restore mode (in case of rooted phone)
- Internal storage issues, external card failures
How to fix the reboot only issue?
We must be aware that the smartphone is not blamed to death and it is very possible that it will work properly again. But in development we must sacrifice certain data that we store.
Every Android has a “Safe Mode” in which only the essential files are loaded for the phone to perform basic functionalities. There are multiple ways to start your smartphone in this mode and we will expose them to you to see if this solves the restart problem.
Why are bootloops generated?
A bootloop is not a temporary reboot, but rather an incessant reboot of new phones, trying to boot the system but failing. Most likely, some boot system file has been corrupted, causing the phone to repeatedly attempt to boot to no avail, logging in on these constant, harassed reboots.
This tends to happen thanks to three different situations: