[GUIDE] Moto G4 Plus HardBrick SOLVED - ULTIMATE UNBRICKING GUIDE

Is your device is back to life using this method?

  • Yes

    Votes: 118 67.4%
  • No

    Votes: 57 32.6%

  • Total voters
    175
Search This thread

joaopaulo_

Senior Member
Jun 6, 2013
70
9

Sky Sonu

Member
Sep 28, 2017
12
0
Reserved 2

Get latest Stock Firmware for any model of Moto G4 and G4+
from here : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
:fingers-crossed:

after flashing blank flash then dummy bootloader has installed but when flashing stock rom it shows error failure in cmd please help me out

---------- Post added at 11:16 AM ---------- Previous post was at 11:10 AM ----------

after flashing blank flash then dummy bootloader has installed but when flashing stock rom it shows error failure in cmd please help me out

same problem with me also:(:(:(
 

Outfield303

Senior Member
Nov 6, 2016
286
220
after flashing blank flash then dummy bootloader has installed but when flashing stock rom it shows error failure in cmd please help me out

---------- Post added at 11:16 AM ---------- Previous post was at 11:10 AM ----------



same problem with me also:(:(:(

Make sure you're flashing the correct GPT and Bootloader. If you're flashing older files then you'll probably get that error.
Download the Latest GPT and Bootloader files from above Thanks to @echo92 https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80
Give it a try and see what you come up with...
Good luck!
 
  • Like
Reactions: echo92

echo92

Senior Member
Jan 1, 2017
3,732
1,989
Plymouth
after flashing blank flash then dummy bootloader has installed but when flashing stock rom it shows error failure in cmd please help me out

---------- Post added at 11:16 AM ---------- Previous post was at 11:10 AM ----------



same problem with me also:(:(:(

If the Dec 2017 GPT and bootloader doesn't work, please post what errors you're getting with the stock ROM flash and which stock ROM you're using and what commands you're using to flash the software.
 

prasadak2811

Member
Oct 30, 2012
9
0
REALLY THANKS ALOT BROS
MY PHONE BACK TO NORMAL CONDITION
Connecting to server wait..Ok
Login Success
Credit : 0
PRODUCT : ATHENE_16MP
EMMC : EMMC
CID : 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
BOOTLOADER : 0X0032
MODEL : OEM_LOCKED
FINGERPRINT1 : XT1643
FINGERPRINT2 : 7.0/NPJ
Unlockdata:3A85220307641507#5A593232334752483950004D6F746F2047200000#1DC48EE88A281B608931999A6C95DAEEBE1A2C80#F4B31701000000000000000000000000

Token Copy To Clipboard.
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.005s]
finished. total time: 0.005s
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.006s]
finished. total time: 0.006s
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.005s
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.127s]
finished. total time: 0.131s
target max-sparse-size: 256MB
sending 'bootloader' (3651 KB)...
OKAY [ 0.118s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(bootloader) committing: bootloader.default.xml ...
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.431s]
finished. total time: 0.549s
target max-sparse-size: 256MB
sending 'logo' (2186 KB)...
OKAY [ 0.072s]
writing 'logo'...
OKAY [ 0.057s]
finished. total time: 0.129s
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
OKAY [ 0.378s]
finished. total time: 0.896s
target max-sparse-size: 256MB
sending 'recovery' (16484 KB)...
OKAY [ 0.522s]
writing 'recovery'...
OKAY [ 0.387s]
finished. total time: 0.909s
target max-sparse-size: 256MB
sending 'dsp' (16384 KB)...
OKAY [ 0.519s]
writing 'dsp'...
OKAY [ 0.246s]
finished. total time: 0.765s
target max-sparse-size: 256MB
sending 'oem' (96490 KB)...
OKAY [ 3.041s]
writing 'oem'...
OKAY [ 7.207s]
finished. total time: 10.249s
target max-sparse-size: 256MB
sending 'system' (261013 KB)...
OKAY [ 8.217s]
writing 'system'...
OKAY [ 5.809s]
finished. total time: 14.027s
target max-sparse-size: 256MB
sending 'system' (250842 KB)...
OKAY [ 7.896s]
writing 'system'...
OKAY [ 6.032s]
finished. total time: 13.929s
target max-sparse-size: 256MB
sending 'system' (254493 KB)...
OKAY [ 8.009s]
writing 'system'...
OKAY [ 7.694s]
finished. total time: 15.704s
target max-sparse-size: 256MB
sending 'system' (247302 KB)...
OKAY [ 7.787s]
writing 'system'...
OKAY [ 6.662s]
finished. total time: 14.450s
target max-sparse-size: 256MB
sending 'system' (260402 KB)...
OKAY [ 8.194s]
writing 'system'...
OKAY [ 5.888s]
finished. total time: 14.083s
target max-sparse-size: 256MB
sending 'system' (262057 KB)...
OKAY [ 8.257s]
writing 'system'...
OKAY [ 5.912s]
finished. total time: 14.170s
target max-sparse-size: 256MB
sending 'system' (261941 KB)...
OKAY [ 8.254s]
writing 'system'...
OKAY [ 10.897s]
finished. total time: 19.151s
target max-sparse-size: 256MB
sending 'system' (82497 KB)...
OKAY [ 2.598s]
writing 'system'...
OKAY [ 1.856s]
finished. total time: 4.454s
target max-sparse-size: 256MB
sending 'modem' (76958 KB)...
OKAY [ 2.426s]
writing 'modem'...
OKAY [ 1.110s]
finished. total time: 3.536s
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.024s
erasing 'modemst2'...
OKAY [ 0.023s]
finished. total time: 0.023s
target max-sparse-size: 256MB
sending 'fsg' (2032 KB)...
OKAY [ 0.067s]
writing 'fsg'...
OKAY [ 0.063s]
finished. total time: 0.130s
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.017s
erasing 'userdata'...
OKAY [ 0.065s]
finished. total time: 0.065s
erasing 'customize'...
OKAY [ 0.013s]
finished. total time: 0.013s
erasing 'clogo'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'DDR'...
OKAY [ 0.007s]
finished. total time: 0.007s
Flashing Completed
 

satyamspot

New member
Feb 18, 2018
2
0
Moto G4 plus Blank flash error --device not detecting

I was upgrading to Nougat from Marshmallow, because of low battery phone switched off while updating. Now phone LED is blinking when I am charging and I have almost done all the things which are to be done. The only response I got is the LED light stop blinking and nothing happens then. Help me please, I have already charged it for 2-3 hours but still, it is not turning on.

I tried for blank flash but it showing the error msg. [Error opening device].

[ 0.000] Opening device: \\.\COM3
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
[ 0.000]
 
Last edited:

cooldude1598

Member
Sep 30, 2017
6
0
Blank flash failed Moto g4 plus

tried re-inserting cable but blankflash is showing failed.
It detected my device as ******Dloader 9008
Link for pic -https://ibb.co/c4Cr7c
here is the log
Code:
**** Log buffer [000001] 2018-02-25_15:30:54 ****

[ -0.000] Opening device: \\.\COM7
[ -0.000] ERROR: device_open()->error opening device
[ -0.000] Check qboot_log.txt for more details
[ -0.000] Total time: -0.000s
[ -0.000] 
[ -0.000] qboot version 3.40
[ -0.000] 
[ -0.000] DEVICE {
[ -0.000]   name  = "\\.\COM7",
[ -0.000]   flags = "0x60",
[ -0.000]   addr  = "0x28FE6C",
[ -0.000]   api.bnr = "0x602FC8",
[ -0.000] }
[ -0.000] 
[ -0.000] 
[ -0.000] Backup & Restore {
[ -0.000]   num_entries = 0,
[ -0.000]   restoring = "false",
[ -0.000]   backup_error = "not started",
[ -0.000]   restore_error = "not started",
[ -0.000] }
[ -0.000] 

**** Log buffer [000001] 2018-02-25_15:32:21 ****

[ -0.000] Opening device: \\.\COM8
[ -0.000] ERROR: device_open()->error opening device
[ -0.000] Check qboot_log.txt for more details
[ -0.000] Total time: -0.000s
[ -0.000] 
[ -0.000] qboot version 3.40
[ -0.000] 
[ -0.000] DEVICE {
[ -0.000]   name  = "\\.\COM8",
[ -0.000]   flags = "0x60",
[ -0.000]   addr  = "0x28FE6C",
[ -0.000]   api.bnr = "0x702FC8",
[ -0.000] }
[ -0.000] 
[ -0.000] 
[ -0.000] Backup & Restore {
[ -0.000]   num_entries = 0,
[ -0.000]   restoring = "false",
[ -0.000]   backup_error = "not started",
[ -0.000]   restore_error = "not started",
[ -0.000] }
[ -0.000]
Please Help Me
c4Cr7c
 
Last edited:

echo92

Senior Member
Jan 1, 2017
3,732
1,989
Plymouth
tried re-inserting cable but blankflash is showing failed.
It detected my device as ******Dloader 9008
Link for pic -https://ibb.co/c4Cr7c
here is the log
Code:
**** Log buffer [000001] 2018-02-25_15:30:54 ****

[ -0.000] Opening device: \\.\COM7
[ -0.000] ERROR: device_open()->error opening device
[ -0.000] Check qboot_log.txt for more details
[ -0.000] Total time: -0.000s
[ -0.000] 
[ -0.000] qboot version 3.40
[ -0.000] 
[ -0.000] DEVICE {
[ -0.000]   name  = "\\.\COM7",
[ -0.000]   flags = "0x60",
[ -0.000]   addr  = "0x28FE6C",
[ -0.000]   api.bnr = "0x602FC8",
[ -0.000] }
[ -0.000] 
[ -0.000] 
[ -0.000] Backup & Restore {
[ -0.000]   num_entries = 0,
[ -0.000]   restoring = "false",
[ -0.000]   backup_error = "not started",
[ -0.000]   restore_error = "not started",
[ -0.000] }
[ -0.000] 

**** Log buffer [000001] 2018-02-25_15:32:21 ****

[ -0.000] Opening device: \\.\COM8
[ -0.000] ERROR: device_open()->error opening device
[ -0.000] Check qboot_log.txt for more details
[ -0.000] Total time: -0.000s
[ -0.000] 
[ -0.000] qboot version 3.40
[ -0.000] 
[ -0.000] DEVICE {
[ -0.000]   name  = "\\.\COM8",
[ -0.000]   flags = "0x60",
[ -0.000]   addr  = "0x28FE6C",
[ -0.000]   api.bnr = "0x702FC8",
[ -0.000] }
[ -0.000] 
[ -0.000] 
[ -0.000] Backup & Restore {
[ -0.000]   num_entries = 0,
[ -0.000]   restoring = "false",
[ -0.000]   backup_error = "not started",
[ -0.000]   restore_error = "not started",
[ -0.000] }
[ -0.000]
Please Help Me
c4Cr7c

If you're running Windows 8.1 or 10, can you check if driver signature enforcement is disabled, please?

The blankflash may require several tries to get it working, and you may have to try this sequence as well.

Or any other error, then its little tricky to solve this.
Follow the below steps.
1. Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
4. keep trying step 3 unless you dont see below logs.

Credit to: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

How did your device get into a hardbrick?

Also, please verify that the cable you're using is a high quality data USB cable or the original Motorola USB cable.
 
Last edited:

echo92

Senior Member
Jan 1, 2017
3,732
1,989
Plymouth
this method work in latest december security patch any try please tell me ?

It's not conclusive if this blankflash works with the latest December 2017 patch - there've been a few reports that suggest this blankflash does, and there have been others which have struggled to rescue their device with this blankflash.

If you've hard bricked, you could try this blankflash with the December 2017 GPT and bootloader, and report back. If you've not hardbricked, then please do not flash old stock firmware (older than the most recent stock firmware on your device) and then accept OTA updates.
 

ZaidFaris

New member
Mar 3, 2018
3
0
Error opening device

I am having moto g4 plus I recently rooted my device and unlocked the bootloader then I installed some custom roms and then installed the adroid 6 stock rom and later updated my phone toh android 7.. and my phone is hard bricked I tried a lot of time woth diffrrent blank flash files but still the same message error opening device... also my pc motherboard is 32 bits is that the reason???.... please reply this asap... I would be very thankful to you.... pls help me out... my device is moto g4 plus XT1643
 

echo92

Senior Member
Jan 1, 2017
3,732
1,989
Plymouth
I am having moto g4 plus I recently rooted my device and unlocked the bootloader then I installed some custom roms and then installed the adroid 6 stock rom and later updated my phone toh android 7.. and my phone is hard bricked I tried a lot of time woth diffrrent blank flash files but still the same message error opening device... also my pc motherboard is 32 bits is that the reason???.... please reply this asap... I would be very thankful to you.... pls help me out... my device is moto g4 plus XT1643

Are you using the blankflash from this thread? This is the latest blankflash we have access to - the ones in the opening post of the other thread you posted in may not work (as you've found out).

Try this blankflash and be aware it may take several attempts to connect to your device. Also, use the original USB cable if you can or a high quality USB data cable. Your PC motherboard should not matter - 32 bit or 64 bit architecture shouldn't matter.

As a warning to others, if you do flash older stock firmware (older than the stock firmware on your device), please do not use OTA updates. Only update with stock firmware until your device is on the newest firmware for your device region.
 
  • Like
Reactions: ZaidFaris

ZaidFaris

New member
Mar 3, 2018
3
0
Are you using the blankflash from this thread? This is the latest blankflash we have access to - the ones in the opening post of the other thread you posted in may not work (as you've found out).

Try this blankflash and be aware it may take several attempts to connect to your device. Also, use the original USB cable if you can or a high quality USB data cable. Your PC motherboard should not matter - 32 bit or 64 bit architecture shouldn't matter.

As a warning to others, if you do flash older stock firmware (older than the stock firmware on your device), please do not use OTA updates. Only update with stock firmware until your device is on the newest firmware for your device region.
Thanks for the reply.... Yes. I used blankflash from this thread but it didnt worked... I borrowed my friends laptop and it was successful and now i am typing this message from my moto g4 plus thanks to all you guys... I dont Know what's the problem with my pc... Any ways its done and i am happy all thanks to you guys... And i didnt install the stock from i just went into the recovery mode and my phone turned on and the update continued and it was completed... And when it turned on my phones battery was 1% so i think my battery wasn't charged and may be that's the reason behind opening device error
 

acetheapurva

Member
Feb 18, 2014
19
0
Jamnagar
I initially had February update for Motog4 plus, then i added a custom rom of 64 bit, due to some things i thought of going back to stock rom [December Update], that is also done, after that I got an OTA update for my phone, while it was getting installed, screen went off and nothing till now.
I had my volume button broken so i tried this method
I entered the bootloader but while flashing gpt.bin i get the following error
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [  0.004s]
writing 'partition'...
(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.067s
I know it is due to older firmware and OP it was mentioned that this is for older version, where do i get new versions of GPT and BlankFlash
 

echo92

Senior Member
Jan 1, 2017
3,732
1,989
Plymouth
I initially had February update for Motog4 plus, then i added a custom rom of 64 bit, due to some things i thought of going back to stock rom [December Update], that is also done, after that I got an OTA update for my phone, while it was getting installed, screen went off and nothing till now.
I had my volume button broken so i tried this method
I entered the bootloader but while flashing gpt.bin i get the following error
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [  0.004s]
writing 'partition'...
(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.067s
I know it is due to older firmware and OP it was mentioned that this is for older version, where do i get new versions of GPT and BlankFlash

Which December stock ROM did you flash? If you flashed the December 2017 stock ROM (NPJS25.93-14-13), I don't think we have an OTA update yet (I've not seen any mention of the February 2018 stock ROM security patch released yet), and since this stock ROM build is possibly the one directly before the Feb 2018 security patch, taking an OTA from this build would not likely brick your device. However, if you flashed the December 2016 (NPJ25.93-14) stock ROM, then yeah, you may have likely hard bricked when you took the OTA.

Which GPT and bootloader are you using? That error as you mentioned is from trying to flash a GPT/bootloader older than your current bootloader version (you cannot downgrade bootloaders usually). All the recent GPT and bootloaders from the stock firmware are mentioned in the opening post, or here's the direct Google Drive link to that folder: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M I've pulled the GPT and bootloader files from their respective stock firmwares, with NPJS25.93-14-13 (Dec 2017) being the latest stock firmware that has been leaked.

However, if you genuinely had the February 2018 stock ROM security patch (custom ROMs do not matter in this regard), then these files won't work as they're too old, and you'll have to wait for the leaked Feb 2018 stock ROM to rescue your device. Try the Dec 2017 GPT/bootloader and see how you get on.
 
Last edited:

acetheapurva

Member
Feb 18, 2014
19
0
Jamnagar
Which December stock ROM did you flash? If you flashed the December 2017 stock ROM (NPJS25.93-14-13), I don't think we have an OTA update yet (I've not seen any mention of the February 2018 stock ROM security patch released yet). However, if you flashed the December 2016 (NPJ25.93-14) stock ROM, then yeah, you may have likely hard bricked when you took the OTA.

Which GPT and bootloader are you using? All the recent GPT and bootloaders from the stock firmware are mentioned in the opening post, or here's the direct Google Drive link to that folder: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M I've pulled the GPT and bootloader files from their respective stock firmwares, with NPJS25.93-14-13 (Dec 2017) being the latest stock firmware that has been leaked.

However, if you genuinely had the February 2018 stock ROM security patch (custom ROMs do not matter in this regard), then these files won't work as they're too old, and you'll have to wait for the leaked Feb 2018 stock ROM to rescue your device. Try the Dec 2017 GPT/bootloader and see how you get on.

Looks like I got lucky, I was using files of June, browsing through the thread I got December Update's gpt and bootloader, which worked. Sorry for posting I should have browsed through the thread first.
Thank You :D :D
 

echo92

Senior Member
Jan 1, 2017
3,732
1,989
Plymouth
Looks like I got lucky, I was using files of June, browsing through the thread I got December Update's gpt and bootloader, which worked. Sorry for posting I should have browsed through the thread first.
Thank You :D :D

Good to hear your device is working again :)

I would recommend you flash the December 2017 stock ROM (NPJS25.93-14-13) in full to fully repair your device. At the moment, you've got a Dec 2017 GPT/bootloader and Dec 2016/March 2017 system. Attempts to take OTAs again will likely result in more hard bricks, unless you either do not use and remember not to use OTA updates or formally and fully update your device to the same firmware patch level as your bootloader, after which OTA updates should be safe to use.

If you wish to, in the fastboot flashing commands, you can omit 'fastboot erase userdata' to save your data, but if you've re-flashed back to stock ROM, your device may be clean anyway, so it's up to you if you wish to keep or omit that command.
 
  • Like
Reactions: acetheapurva

acetheapurva

Member
Feb 18, 2014
19
0
Jamnagar
Hi again,
The guide did work for me, I got stock ROM back again, then i started to root it again, flashed TWRP, was rooting using MAGISK 16, I didn't knew we needed to use a custom kernel for flashing that. So I ended up bricking my phone again.
This time it's not detecting the device but the LED notifications light is still glowing,
Last time when i did lsusb[A command that lists your actively listed usbs] the device was showing there but this time its not showing any Qualcom%, How do I get it detected .. Pls. Help :(
 

Top Liked Posts

  • There are no posts matching your filters.
  • 121
    Disclaimer :
    Code:
      #include<disclaimer.h>
     I am not responsible for bricked devices, dead SD cards,
     thermonuclear war, or you getting fired because the alarm app failed. 
     YOU are choosing to make these modifications,
     and if you point the finger at me for messing up your device, I will laugh at you.
     and also I shall not guarantee this method will work on your device.

    Hello guys,

    as you guys know lots of Athenes are bricked due to the last June security patch and latest blankflash's also were not working.
    and there was also some confusion between which blankflash to flash and which boot-loader and gpt files to flash.. So I will try to clarify this confusion at my best..... :)
    so lets get started......

    So, First of all download the latest BlankFlash by @marcelofilgueira [ MANY MANY HUGE THANKS TO HIM ]
    Here : https://drive.google.com/file/d/0B9rhtqQ4ZTDnTWdpX3ZaVk1pNk0/view

    There is a New BlankFlash file Provided by @rajatgupta1998
    https://forum.xda-developers.com/showpost.php?p=79013024&postcount=523
    It is available here: https://androidfilehost.com/?fid=1395089523397903736
    I can't test this blankflash because I don't have G4 Plus anymore...

    and Then connect your phone to PC( Your phone should Be detected as QualcommLoader or something like that in device manager under the ports section )
    Once connected, extract the Blankflash zip and run Blank-Flash.bat

    A command window will be open and it will flash some files to your phone....
    after 5-6 sec, your Phone will be rebooted to Fastboot Mode :D First sign of Life.... lol
    But process is not over yet....

    Now download the latest Bootloader and GPT files for the version NPJS25.93-14-8 Thanks to @tywinlannister7 and @echo92
    HERE : https://drive.google.com/open?id=0B-GUyOfb8Ogzamt6ME5fYncwdjg
    And if above files won't work then here are the Sept Patch Files of GPT and Bootloader : https://drive.google.com/file/d/0B-GUyOfb8Ogzc25FdW1WUDBMS1U/view
    and Also here are the GPT and boot-loader files for December patch if above won't worked : https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80
    and extract them into New folder. and don't forget to copy ADB and the fastboot files into that folder.
    ADB and Fastboot DOWNLOAD HERE : https://www.androidfilehost.com/?fid=673368273298979521
    Hold Shift key and press right key on the mouse and click on open command window in that folder and Paste the following command and then press Enter :
    Code:
    fastboot flash partition gpt.bin
    fastboot flash bootloader bootloader.img
    fastboot reboot-bootloader


    Once done then You can see the Fastboot mode on your screen ;)....

    The next step is easy, You just need to flash stock ROM, But you just can't flash older ROM i.e. downgrade this time, Otherwise your device can be bricked again...

    So I will recommend you to download latest ROM NPJS25.93-14-10 and Flash it. Thanks to @tywinlannister7 for providing the ROM
    DOWNLOAD LINK : https://drive.google.com/file/d/0B9tngVBGIajVQkQtLUUxR2NOTnc
    LATEST DECEMBER ROM: https://www.androidfilehost.com/?fid=745849072291698845
    Download it and then just extract it in and don't forget copy ADB and the fastboot files into that folder. Once done then Hold shift and press right key on mouse then select Open Command window here from that menu.
    then use this code to flash stock ROM :

    Code:
    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 dsp adspso.bin
    fastboot flash oem oem.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 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
    pause
    And that's it!! You will get your Athene Back to Life :cool:
    I got my Athene back to life using this method............
    ------------------------------------------------------------------------------------------------------------------------------------

    IMPORTANT NOTE:
    If You've Updated your Device to the February Security Patch Then this method probably won't work because the GPT and boot-loader version is higher then the version included inside the BlankFlash
    So Be Careful...!

    ------------------------------------------------------------------------------------------------------------------------------------

    Now anyone who's getting errors, see post #2

    ------------------------------------------------------------------------------------------------------------------------------------

    Credits :

    blankflash.zip provided by @marcelofilgueira HUGE THANKS TO HIM
    Thanks to @strongst for being always there to help
    Thanks to tywinlannister7 for latest June Stock ROM
    and also thanks to you guys for reading this........

    if you like my work then please HIT that THANKS button
    5
    Reserved 1

    Now anyone who is getting 'Waiting for devices' error while flashing, here are some tips to fix it :

    1) Remove the USB cable and reinsert it
    2) Make Sure your device is detected in Bootloader interface aka Fastboot mode, you can simple see your device listed in device manager.
    3) Install Motorola Driver IF you haven't Installed it yet. Because it can be the main reason for this error. Download it from motorola website: http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
    5
    Reserved 2

    Get latest Stock Firmware for any model of Moto G4 and G4+
    from here : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
    :fingers-crossed:
    5
    Here's a new blankflash file from OPJ28.72 build, this should work on OPJ28.111-22 as the bootloader version is same.
    Obviously I can't test it since I haven't bricked my phone. Any other news shall be given out whenever it appears.

    Download:
    blankflash_athene_8.1.0_OPJ28.72.zip
    MD5: ada83fc6809218084739ca0cc87c9f4a

    ;)
    4
    We need a updated blank flash i... Cos have install latest bootloader
    Can you please stop posting repeatedly in a demanding way? There's no newer blank flash at the moment so you have to wait if you don't want to spent money.

    Every android release users don't read/search before downgrading and taking ota and complain that there's no solution asap.
    You cannot expect that people fix YOUR faults if you have no patience.

    Thanks for understanding:)

    PS @echo92: as I expected https://forum.xda-developers.com/mo...-g4-starting-to-receive-t3839072/post77547833
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone