How to Unbrick a Bricked Moto G 3rd Gen (Restore Bootloader & Stock Firmware)

Flashing custom recovery, rooting, installing custom ROMs and custom kernels are the most common causes for bricking an Android phone like the Moto G 3rd Gen. Performing any of the above said things carelessly can end up with a non-booting system. This situation is called soft bricked, which is hard to recover in most cases, because it damages the bootloader.

In this tutorial, we let you know how to unbrick a bricked Moto G 3rd Gen (all variant) including Moto G Turbo edition. If you have bricked your 3rd Gen Moto G 2015, you can unbrick it by restoring bootloader and installing stock firmware on it. However, you should have knowledge on ADB and fastboot commands.

moto-g-2015

Below guide supports all variant of Moto G (3rd Gen) including Moto G Turbo edition, 1GB and 2G RAM versions, such as XT1550, XT1556, XT1557, XT1540, XT1541, etc. However, depending on the model, you may need to make small alteration in the commands, which is also detailed in the guide.

Warning: The below mentioned file is taken from XDA. We are not responsible for anything that goes wrong. Follow the guide at your own risk. Also, playing with Fastboot commands can seriously damage your phone, so take extreme care while issuing commands.

Unbrick a Bricked Moto G 3rd Gen

Disclaimer: Follow the instruction at your own risk. We will not be liable if any damage occurs to your device and/or its components. Backup all data you have on the phone before proceeding.

1. Download [HERE] and install Motorola drivers on your computer

2. Setup ADB and Fastboot drivers on your computer

3. Download [HERE] latest Fastboot zip file (for Windows and Linux)

4. Download stock firmware for your Moto G3 [HERE]. Download correct firmware for your model number.

5. Unzip both the Fastboot zip file and firmware zip file and save the entire file inside the ADB installation folder (C:\adb)

6. Switch off your phone and boot into fastboot mode by pressing ‘Volume down’ then ‘Power’ button.

[Alternatively, connect your phone to your PC and issue the command adb reboot-bootloader from ADB installation folder]

7. Now, go to the folder where you have saved the extracted firmware file, open a command window there and issue the below commands one-by-one.

[The command ‘system.img_sparsechunks’ may differ in number and name. Always check contents of folder you are working with. You must flash all of the sparsechunk files you have]

fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
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 system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

After rebooting your Moto G 3, set up your phone and enjoy. Any question? Leave it in the comment section below. (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.

7 Comments

  1. Costas

    Sep 15, 2016 at 12:41 pm

    Hi man!! At step 6, i used the alternative option [Alternatively, connect your phone to your PC and issue the command adb reboot-bootloader from ADB installation folder] but i get:
    * daemon not running.starting it now on port 5037*
    * daemon started successfully*
    error: device ”not found.

    Is there anything i can do?

    • Kannan

      Sep 15, 2016 at 2:19 pm

      It means you have not installed fastboot driver on your computer

      • Costas

        Sep 15, 2016 at 5:01 pm

        thanks for the answer. i install the fastboot and i get the same error: device ‘null’ not found

      • Costas

        Sep 15, 2016 at 7:18 pm

        in the first step about motorolla drivers installation, i get current version: N/A

        • Kannan

          Sep 15, 2016 at 9:30 pm

          Motorola drivers is not fastboot driver. Follow one of my guide to install fastboot drivers

  2. Ayan

    Aug 28, 2016 at 10:14 pm

    we have normally 7 sparsechunk files

    • Kannan

      Aug 29, 2016 at 8:34 am

      There might have changes. Change the code accordingly, if so

Leave a Reply

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