Bootloader error when starting Moto G3

ExequielVqz

New member
Aug 10, 2018
3
0
0
A relative brought me his Moto G3 (XT1542) because it did not turn him on, he told me that the device was being updated and turned it off without knowing that something bad could happen, then he wanted to turn it on and send it to the following screen:


When "Start" was selected using the power button, the Motorola logo was displayed for a fraction of a second and the following screen appeared:


No matter which option is selected, "Bootloader Log" appears in all.
I have already tried to load the stock firmware but it does not take it, the same error continues.

I already thank you if you can help me solve this, it is already giving me headaches :mad:

Sorry for my bad English, I had to translate it because I don't speak that language. :(
 

Viva La Android

Senior Member
Jul 31, 2019
407
156
53
Corbin, KY
This error is indicative that either the ramdisk or kernel is corrupted. However, this is a soft brick and can be restored by using fastboot mode or RSD-Lite to flash an official firmware package to your device. Doing so will restore the device back to a factory stock state (but will not relock the bootloader if it has been unlocked. But, since relocking the bootloader carries no advantage except warranty related advantages, this is of little consequence). Official firmware packages for the Moto G 2015 can be found here https://mirrors.lolinet.com/firmware/moto/osprey/official/
Select the most current package for your variant. There are numerous guides here on XDA for restoring Moto devices using fastboot or RSD-Lite. The best fastboot guide I have seen is @lost101's tutorial & firmware repo here https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
(Official firmware is available at either of the above links. Just choose a link and find the most current build for your device.) @R1ffR4ff's earlier post linking the Lenovo Motorola Smart Assistant should also fully restore your device, and is less complicated than manually flashing an official firmware package. As such, the methods outlined in my post should only be used if the Smart Assistant did not do the trick.
 
Last edited: