Restore Non Booting Moto G 2013 After Lollipop Update

If your Moto G 2013 stuck in bootloop after updating to Android 5 Lollipop, here are some ways to help you get out of bootloop and get your phone ready for daily use. A bootloop means your phone stuck indefinitely on the boot animation logo. Normally, firmware update will not cause any issue, but if you have not followed the instruction carefully, you might end up with a non-booting system.

Moto G

In this tutorial, we will show you know how to restore a non-booting Moto G (2013) after Android 5 Lollipop update. As well as, it will also restore the stock firmware back again. The process requires knowledge about ADB, Fastboot, and command prompt; however, if you have followed the guide carefully, you can give back life to your softbricked Moto G.

If your Moto G became non-booting after installing the Android 5 Lollipop update, you can fix it by following the guide below. This tutorial is for Moto G XT1028, XT1031, XT1032, XT1033 and XT1034.

There are two methods to restore a non-booting Moto G, the first method does not need to downgrade to Android 4.4.4 KitKat, as this method works with Lollipop ROMs too.

Requirements:

1. You need to have a custom recovery (CWM/TWRP) installed
2. Stock firmware zip file for Moto G XT1028, XT1031, XT1032, XT1033 and XT1034 [Download from here]
3. ADB and Fastboot

Method 1:

1. Boot your phone into custom recovery mode. Recovery will have adb on by default, so leave recovery as it is.

2. Connect your phone to your PC and open command prompt and issue the command: cd directory-with-adb.exe-and-fastboot.exe

3. Now, issue the command: adb devices. If Moto G drivers have installed properly, the phone will show up. If not, download the driver here and install it.

3. Now, from recovery wipe /data and media

4. Open command prompt and execute: adb push rom.zip /sdcard/rom.zip

It will take some time to install the ROM. If you face a not working SIM or WiFi, extract the downloaded ROM zip file and navigate to extracted firmware folder using cmd and issue:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

Method 2:

1. Extract the downloaded firmware file to a folder.

2. Download and extract mfastboot-v2.zip and copy its content to the same folder where the extracted firmware files.

3. Reboot your Moto G into the Bootloader Mode. To do so, turn off your phone and then press and hold the Volume (-) and Power buttons simultaneously for a few seconds.

4. Connect your phone to your PC via USB cable.

5. Now, launch a command window from inside the firmware folder (click shift key, right click and select open command window here option).

6. In the command window, issue the following commands one by one:

fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot

Note: If firmware includes four ‘system.img_sparsechunk’ or you do not want to erase the userdata, you can modify the command.

You have now successfully installed a fresh ROM on your Moto G and the phone the phone should work as usual. (Source – XDA)

Kannan is a computer and Android enthusiast, a blogger by passion and a tech freak. His always ready-to-help attitude, knowledge and hard work is what drives him.

3 Comments

  1. DILJITH

    May 26, 2016 at 11:20 pm

    Thanks for your help brother. It worked for my moto g3 which was stuck on the boot logo. Though I never expected a positive result, it happened. Thanks again 🙂

  2. Sahil Arora

    Apr 10, 2016 at 12:52 pm

    Hello, May I know how to modify the command if I don’t want to delete userdata?

    • Kannan

      Apr 10, 2016 at 4:26 pm

      Do not flash the userdata image file otherwise you will lose all your installed apps and their data

Leave a Reply

Your email address will not be published. Required fields are marked *