[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

StAr1oRd

New member
Apr 12, 2017
2
0
0
getting 'remote failure' error while flashing partition

view


Please get me through this.
 

echo92

Senior Member
Jan 1, 2017
3,732
1,989
223
Plymouth
view


Please get me through this.

What files are you flashing to get this error? That error suggests you're flashing a GPT/bootloader that is older than the one on your device, and so is blocking the flash.

Try one of the later GPT/bootloader files, and then flash the latest stock ROM for your device. If you do downgrade, please do not use OTA updates, else you may hard brick again.

https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M for the GPT/bootloader collection
 

suva12296

Member
Apr 10, 2018
15
2
0
kolkata
Moto g4(4th gen)

My moto g4(4th gen) got hard bricked while using factory reset and I have updated my phone to feb security update and you also mention there feb security updated phone won't be apply this process. then how can I unbrick my phone .
 

abhi212b

Senior Member
Feb 16, 2016
552
161
0
Noida
www.youtube.com

suva12296

Member
Apr 10, 2018
15
2
0
kolkata
As far as i know, you only need gpt.bin... As the bootloader is not updated.. So just check out the Feb OTA file already posted in this forum..
https://forum.xda-developers.com/moto-g4-plus/how-to/ota-february-2018-npjs25-93-14-15-t3770286

download it and extract gpt.bin... Nd use the same old December 2017 bootloader and rom that's in the op... Your phone will boot and you'll have OTA notification... Update your phone and you are done!! :D

Yep it worked , Thanks a lot
 

jalbarran

Member
Mar 28, 2018
6
0
0
Maracaibo
Can not flash anything!

Guys, my Moto G4 Plus XT1644 is bricked, I can see fastboot in the screen when I turn it on, but if I try to flash anything, I get only errors.

This is what I get when I try to flash partition gpt.bin:

Code:
NPJS25_93_14_15_Feb2018_GPT_bootloader # fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [  0.004s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.

(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.072s

Please Help!
 

echo92

Senior Member
Jan 1, 2017
3,732
1,989
223
Plymouth
Guys, my Moto G4 Plus XT1644 is bricked, I can see fastboot in the screen when I turn it on, but if I try to flash anything, I get only errors.

This is what I get when I try to flash partition gpt.bin:

Code:
NPJS25_93_14_15_Feb2018_GPT_bootloader # fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [  0.004s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.

(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.072s

Please Help!

Hmm, what happens when you try to boot? If you have fastboot, that suggests your bootloader is okay (as fastboot mode is enabled by the bootloader).
 

jalbarran

Member
Mar 28, 2018
6
0
0
Maracaibo
More details in this post

Hmm, what happens when you try to boot? If you have fastboot, that suggests your bootloader is okay (as fastboot mode is enabled by the bootloader).

My phone boots into fastboot mode only, and shows an error saying that it could not boot into normal mode, that is the only thing my phone does!

I wrote more details in this post a few weeks ago, this is the post: https://forum.xda-developers.com/showpost.php?p=76045343&postcount=318

There are a lot more details about my phone bricked!

Thanks for the reply!
 

Nihar

Senior Member
Sep 13, 2012
505
596
123
Pune
Stuck on waiting for firehose to get ready

Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 2418 (0x972)
[ 0.004] ...cpu.sn = 23377026 (0x164b482)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.mbn
[ 0.008] Sending programmer
[ 0.228] Handling things over to programmer
[ 0.228] Identifying CPU version
[ 0.229] Waiting for firehose to get ready
[ 60.334] Waiting for firehose to get ready
[120.445] ...MSM8952 unknown
[120.445] Determining target secure state
[120.447] Waiting for firehose to get ready
[180.545] ...secure = no
[180.554] Flashing GPT...
[180.555] Flashing partition:0 with gpt_main0.bin
[180.555] Initializing storage
[180.557] Waiting for firehose to get ready
[240.666] Configuring device...
[1494.755] Waiting for firehose to get ready
[1554.848] Waiting for firehose to get ready
[1614.944] Waiting for firehose to get ready
[1675.044] Waiting for firehose to get ready
[1735.152] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[1735.152] Check qboot_log.txt for more details
[1735.152] Total time: 1735.153s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error


I'm having this issue when i am trying to get the g4 plus to boot.. Any help?? It doesn't boot into fastboot or anything.. just stuck on the blank screen with white led blinking. It happened when an update was installing and the phone switched off on its own when it had more than 80% charge.. Any help?
 
  • Like
Reactions: Hackers Network

Outfield303

Senior Member
Nov 6, 2016
286
220
43
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 2418 (0x972)
[ 0.004] ...cpu.sn = 23377026 (0x164b482)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.mbn
[ 0.008] Sending programmer
[ 0.228] Handling things over to programmer
[ 0.228] Identifying CPU version
[ 0.229] Waiting for firehose to get ready
[ 60.334] Waiting for firehose to get ready
[120.445] ...MSM8952 unknown
[120.445] Determining target secure state
[120.447] Waiting for firehose to get ready
[180.545] ...secure = no
[180.554] Flashing GPT...
[180.555] Flashing partition:0 with gpt_main0.bin
[180.555] Initializing storage
[180.557] Waiting for firehose to get ready
[240.666] Configuring device...
[1494.755] Waiting for firehose to get ready
[1554.848] Waiting for firehose to get ready
[1614.944] Waiting for firehose to get ready
[1675.044] Waiting for firehose to get ready
[1735.152] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[1735.152] Check qboot_log.txt for more details
[1735.152] Total time: 1735.153s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error


I'm having this issue when i am trying to get the g4 plus to boot.. Any help?? It doesn't boot into fastboot or anything.. just stuck on the blank screen with white led blinking. It happened when an update was installing and the phone switched off on its own when it had more than 80% charge.. Any help?

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...!
Read the OP Carefully Please
 

echo92

Senior Member
Jan 1, 2017
3,732
1,989
223
Plymouth
My phone boots into fastboot mode only, and shows an error saying that it could not boot into normal mode, that is the only thing my phone does!

I wrote more details in this post a few weeks ago, this is the post: https://forum.xda-developers.com/showpost.php?p=76045343&postcount=318

There are a lot more details about my phone bricked!

Thanks for the reply!

Okay, thanks for that post. Here's a few things I noted:
1)Did you use the blankflash from this thread? Your screenshots point to it being used, with no baseband, a default serial number and showing OEM_locked. It seems that using a blankflash 'locks' your bootloader until you can flash a GPT/bootloader onto your device.
2)Are you able to find another PC to flash the stock ROM with? Ensure you're using the original Motorola cable or a high quality USB cable. You may wish to try the Feb 2018 GPT/bootloader too, see if that flashes https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M then try to flash the firmware.
3)However, those errors don't look good - failed to program partition table and a read datablock error do suggest a hardware fault (and a fairly major one, it may be flash memory failure as per your hypothesis 1.). However, I'd try to flash the stock ROM again and see how you go. If the flash doesn't work, despite fastboot/bootloader being active, that does point to either block corruption or flash memory failure. I'm hoping the flash does work and repairs what ever data corruption was encountered...
 
  • Like
Reactions: junin_BsB

jalbarran

Member
Mar 28, 2018
6
0
0
Maracaibo
Okay, thanks for that post. Here's a few things I noted:
1)Did you use the blankflash from this thread? Your screenshots point to it being used, with no baseband, a default serial number and showing OEM_locked. It seems that using a blankflash 'locks' your bootloader until you can flash a GPT/bootloader onto your device.
I tried to use blankflash, but blankflash never connected, I guess because the phone was in fastboot mode already.
2)Are you able to find another PC to flash the stock ROM with? Ensure you're using the original Motorola cable or a high quality USB cable. You may wish to try the Feb 2018 GPT/bootloader too, see if that flashes https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M then try to flash the firmware.
I tried to flash in a linux and windows computer, with the original motorola cable, and had no success, I also tried to use the Feb 2018 GPT, but it shows FAILED when trying to flash anything.
3)However, those errors don't look good - failed to program partition table and a read datablock error do suggest a hardware fault (and a fairly major one, it may be flash memory failure as per your hypothesis 1.). However, I'd try to flash the stock ROM again and see how you go. If the flash doesn't work, despite fastboot/bootloader being active, that does point to either block corruption or flash memory failure. I'm hoping the flash does work and repairs what ever data corruption was encountered...
I still hope my phone is not hardware bricked, anything else I could try to make my phone work again?
 

echo92

Senior Member
Jan 1, 2017
3,732
1,989
223
Plymouth
I tried to use blankflash, but blankflash never connected, I guess because the phone was in fastboot mode already.

I tried to flash in a linux and windows computer, with the original motorola cable, and had no success, I also tried to use the Feb 2018 GPT, but it shows FAILED when trying to flash anything.

I still hope my phone is not hardware bricked, anything else I could try to make my phone work again?

Hmm, without being able to flash anything, it's difficult to suggest anything. What does the FAILED message also report, is it still the 'read datablock failed' or 'failed to program partition table'?

I'm hoping others can contribute, as otherwise your device is likely needing a hardware service. It could be that the flash memory controller or portions of your flash memory have failed, which a service centre or repair shop might be best able to help you with.
 

erica butson

Member
Jan 17, 2018
40
17
0
Flashing February Partition didn't work

Hi, I have download NPJS25_93_14_15_Feb2018_GPT_bootloader.zip and flashed on December update, My phone is soft bricked. I can access only bootloader and cannot access recovery. Is there anyway i can recover this device?
After flashing the feb updates here is the log, Please help
C:\Users\jay\Downloads\Compressed\ADB+and+Fastboot\ADB and Fastboot>fastboot flash partition gpt.bin
(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.000s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.141s]
finished. total time: 0.141s

C:\Users\jay\Downloads\Compressed\ADB+and+Fastboot\ADB and Fastboot>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.120s]
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.459s]
finished. total time: 0.579s

C:\Users\jay\Downloads\Compressed\ADB+and+Fastboot\ADB and Fastboot>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.191s]
finished. total time: 0.191s









C:\Users\jay\Downloads\Compressed\ADB+and+Fastboot\ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2238L75Q
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 9CEB7F0000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358187070533255
(bootloader) meid:
(bootloader) date: 06-02-2016
(bootloader) sku: XT1643
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 21 0:57:57 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:6.0.1/M
(bootloader) ro.build.fingerprint[1]: PJ24.139-63/64:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.31.64.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband[0]: M8952_70009.08.03.48R ATHENE_INDIA_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g061c37c (hudsoncm
(bootloader) kernel.version[1]: @ilclbld87) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Thu Aug 4 19:33:05 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (142)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.391s
 

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