Database Users

bootloader is bricked

Hello,
I have bricked my bootloader in the past to refresh my bootloader. I have unbricked my phone to bootloader 1.03 with blank flash. Now when i try to flash, erase do ANYTHING it won't allow me because my OEM_LOCKED state. If i try to unlock my bootloader it says:
Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.032s]
finished. total time: 0.036s
but there is no android installed.
When i try to flash a stock rom it says:
Code:
C:\Users\nick\Desktop\total firmware>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.068s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.088s
C:\Users\nick\Desktop\total firmware>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.540s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.576s
C:\Users\nick\Desktop\total firmware>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.548s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.568s
C:\Users\nick\Desktop\total firmware>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.532s]
writing 'dsp'...
(bootloader) Invalid partition name dsp
FAILED (remote failure)
finished. total time: 0.560s
C:\Users\nick\Desktop\total firmware>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (124713 KB)...
OKAY [ 3.993s]
writing 'oem'...
(bootloader) Invalid partition name oem
FAILED (remote failure)
finished. total time: 4.017s
C:\Users\nick\Desktop\total firmware>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (261790 KB)...
Everything is 'invalid partition name'.
when i try to brick my bootloader again to install try again it says
Code:
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.020s]
writing 'sbl1'...
(bootloader) Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.036s
rebooting...
And when i try to flash another bootloader it says:
Code:
PS C:\Users\nick\Desktop\total firmware> fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.250s
PS C:\Users\nick\Desktop\total firmware>
please help

I guess there is a partion problem
Look into this thread
https://forum.xda-developers.com/showthread.php?t=3496912
Sent from my Moto G4 Plus using Tapatalk

Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.

codGmer said:
Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.
Click to expand...
Click to collapse
Did you run all stock steps in order? In particular this one first:
Code:
fastboot flash partition gpt.bin
That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.
If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.

givitago said:
Did you run all stock steps in order? In particular this one first:
Code:
fastboot flash partition gpt.bin
That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.
If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.
Click to expand...
Click to collapse
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'

codGmer said:
Did you run all stock steps in order? In particular this one first:
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
Click to expand...
Click to collapse
I too have this question bro .... Plus help me if you find a solution ... I m a newbie... Nd face the same problem as yours

Sounds like fastboot expects a working partition table to start with then.
I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.
Good luck.

givitago said:
Sounds like fastboot expects a working partition table to start with then.
I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.
Good luck.
Click to expand...
Click to collapse
Im affraid i already tried booting twrp but without success.

Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: 74f9d6fa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: A420B70000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.147s

hey bro , did you get any solution of this problem?
i am getting
fastboot reason : failed to initialize partition table
any solution?

king_priithvi said:
hey bro , did you get any solution of this problem?
Click to expand...
Click to collapse
Provide more information of your problem/situation,
what happened ?
Have you flashed any firmware ?
Took any OTA ?
What was firmware version you were using ?
Tried latest December's firmware ? This> https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

I think you're flashing older bootloader & GPT then it is already installed on your device;
take a look here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
from that thread download the latest ROM and firstly flash GPT and boot-loader by following command:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
but however after flashing the latest firmware the current blankflash that we have won't work, because GPT and boot-loader version is higher.
now after you flashed the GPT and bootloader then flash the whole firmware by following commands:
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
Now once you flashed it then you're good to go:good:

i cant flash anything , my android is not installed
it kept saying
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No BootImage Found. skip to fastboot
boot up failed

king_prithvi said:
i cant flash anything , my android is not installed
it kept saying
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No BootImage Found. skip to fastboot
boot up failed
Click to expand...
Click to collapse
Are you able to flash the latest stock ROM via fastboot? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

I am getting an error when I try to flash twrp. I want to make sure I am doing it right
in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img
then I got this error
target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s
has anyone else run into this problem. Am I doing something wrong?

kiyip said:
I am getting an error when I try to flash twrp. I want to make sure I am doing it right
in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img
then I got this error
target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s
has anyone else run into this problem. Am I doing something wrong?
Click to expand...
Click to collapse
What device do you have? I'm guessing it's a Moto X4 from the TWRP name?
Are you on Nougat or Oreo? From looking at this thread, you've got 2 different build: https://forum.xda-developers.com/moto-x4/development/dev-testing-t3707432
If you are running a X4, you may have better luck over there rather than here on the Moto G4 forums, as there's more users familiar with the A/B partitioning on the Moto X4.

Ohh my bad, I had like 6 xda tabs open, I actually meant to post it there. My bad man, thank you!

got the same problem any luck yet?
Any luck yet? I got a suggestion that the problem could only get fixed flashing the memory of the phone directly with this kind of device... (search for the octopus box, I cant post links yet im new here) but im lost and they say that thing is expensive... I really want my phone to be saved on my computer. My case is exactly the same as you.... oem locked and failed partition everything and remote failure.

SOLVED!! Failed to initialize partition table
..
First of all convert phone to hard brick to Softbrick...
After that if you want to bootup phone than..IT shows bootloader log::
Failed to initialize partition Table
SOLUTION:-
1) Download Minimal ADB Drivers , gpt.bin, Motorola Device driver
For link mail me on [email protected]
2.) Now Install adb and motorola drivers .
3.) Copy gpt.bin file in ADB folder in installed drive.
4.) Open Minimal ADB and Fastboot.exe
Now Run the following command
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot
The cell phone should restart after this if you do not type the last code and enter if still yes it is not just hang up and call to enter the fastboot.
Now YOUR PROBLEM SOLVED

codGmer said:
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
Click to expand...
Click to collapse
Even I got the same error. Its because adb couldn't find the gpt.bin file in the adb folder from where you had executed the command window.
Copy the gpt.biin file in that folder and try again, that should work.

Question ... for a newbie

I have a G4plus on android 7.0. I have flash few months ago this version 7.0 on my phone before the official update from moto.
My phone is rooted. Everything will work perfectly everyday except one point...
Since the begin, when i power on the phone, the boot image will be sticken on the logo Lenovo (i have flash the boot logo Lenovo instead of your device is ...).
I need to switch off, switch on several times and waiting...
If the phone will vibrate, i need to switch off again and again...
And sometimes, it will power on to the boot animation.
Because i'm not sure of the version, i will pasted the printscreen :
Build : NPJ25.75-2
Software :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hardware :
I have free time this summer, so i want to pass using TWRP (already flash on my phone) to LineageOS or any ROM more updated...
but i want to fix this problem before !
Any idea ?
Thank you.

download stock 6.0 rom and flash using pc .
you will need to root it again after this .
then u can update officially or flash a custom rom like resurrection remix .
follow steps carefully .
Sent from my Moto G4 Plus using Tapatalk

Moto g4 plus slow charging
My moto g4 plus charging very slow campare to normal, I'm using RR ROM pls tel any one how to fix

parth00790 said:
download stock 6.0 rom and flash using pc .
you will need to root it again after this .
then u can update officially or flash a custom rom like resurrection remix .
follow steps carefully .
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Because i saw on the website, I can brick my phone... i prefer to start from a 7.0 android stock.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have relock the bootloader (if i try to upload the rom without lock, i enter in boot loop).
Keep you in touch...
In progress !
After, i want to unlock again and except skip boot loop... and flash twrp+root and migrate to lineageos after...

Always, the same problem.
In the bootloader :
- software status : modified
oem_locked (seems to be locked, OK?)
If i try to power on, i will sticked with the motorola logo (blue and M...) and vibrate, and loop, boot, logo, vibrate, loop, boot...
Again and again.
Try to flash again the rom, now with my bootloader locked.

If i tried to flash again after relock the bootloader, i will boot (with no message this device is not trusted, bad key ...)...
But after few seconds, i have a droid open with ! (red) and NO COMMAND...
What can i do please ?
At this time :
When i power on the phone :
I saw a blue screen with M logo, vibrate once ; automatic reboot.
Blue screen with M logo, vibrate once and stick on the red logo during long time (< 1 min)
Automatic reboot
and black screen with opened droid and no command written.
I will power off the phone, power on and again again ...
And sometimes, it will start to the android 7 rom (on this previous link)
Please help me

benj29 said:
If i tried to flash again after relock the bootloader, i will boot (with no message this device is not trusted, bad key ...)...
But after few seconds, i have a droid open with ! (red) and NO COMMAND...
What can i do please ?
At this time :
When i power on the phone :
I saw a blue screen with M logo, vibrate once ; automatic reboot.
Blue screen with M logo, vibrate once and stick on the red logo during long time (< 1 min)
Automatic reboot
and black screen with opened droid and no command written.
I will power off the phone, power on and again again ...
And sometimes, it will start to the android 7 rom (on this previous link)
Please help me
Click to expand...
Click to collapse
Follow this guide
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

lCrD512 said:
Follow this guide
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
This is what i already done (see my previous quote).
Thanks !

Just to be sure...
I've tried again using your link (which is the same as mine ).
But i use script batch instead of command lines...
I have downloaded the ROM.
download the script bat.
My bootloader says flashing_unlock, so i run only
To simply flash, run the "OEM Flash" file
Click to expand...
Click to collapse
At the end, the phone has rebooted with the page
"your device has been unlocked and can't be trusted
to learn more, visit : motorola.com/unlockbootloader
IT : bad key
your device will boot in 5 seconds
"
and my phone is blocked at this page....
is it normal to have bad key ?
i've try to lock again the bootloader... with the same script + lock.
EDIT : after flashing and lock again the bootloader, the phone has blue screen + red M logo.
I have waited for 1/2 minutes approx and the phone has reboot to "no-command"
Always the same problem, i don't understand !

The bad key is normal (especially with an unlocked bootloader), what's not normal is your device hanging after a flash...
Are you able to repeat the flash but executing the commands manually, please? You can copy paste each of the commands individually into your adb terminal, and check the result - it should say [OKAY] afterwards. The script, handy as it is, makes it difficult to read the outputs from each section of the flash
So the plan is:
Boot your device to the bootloader (just asking, what version is your bootloader now, B1:06?) and attach to your computer
In the adb terminal, check you're communicating with your device via 'fastboot devices', you should get a response with your device's serial number.
Open the 'OEM Flash' script in Notepad or your preferred text editor (don't run the script).
Copy each individual command line, in order, to your adb terminal and press Enter to execute that command.
EDIT - also, it's odd that on your previous flashing attempts, your device booted to the stock recovery (the opened droid with no command) rather than the system

In fact, when i saw no command, i was blocked in the recovery mode !
I tried to make a factory reset on the recovery, but the phone will do this :
- boot bluescreen, vibrate, reboot (automatic) => short time (< 15s)
- boot bluescreen => long time (1 minute) => vibrate, reboot (automatic)
- boot bluescreen, vibrate, reboot (automatic) => short time (< 15s)
- screen "no command" => recovery (power+volume up).
I try after to reboot to system...
But the phone will do the same, three reboots and recovery.
I don't understand my problem !

Thanks for your help.
After last try with lock, this is what i have on my bootloader. I will try to copy each individual command line, in order and past here the results.
BL : B1.06 (sha-0edfb0d, 2017-06-01 12:10:43)
Baseband : 8952_70030.25.03.62.01R Athene_Emea_DSDS_CUST
Product/variant : athene_16mp xt1642 32gb P2A
32 GB + 3 GB RAM
Console[Null] : null ?
Tools mode config : disabled
Battery : OK
oem_locked
software status : modified

benj29 said:
Thanks for your help.
After last try with lock, this is what i have on my bootloader. I will try to copy each individual command line, in order and past here the results.
BL : B1.06 (sha-0edfb0d, 2017-06-01 12:10:43)
Baseband : 8952_70030.25.03.62.01R Athene_Emea_DSDS_CUST
Product/variant : athene_16mp xt1642 32gb P2A
32 GB + 3 GB RAM
Console[Null] : null ?
Tools mode config : disabled
Battery : OK
oem_locked
software status : modified
Click to expand...
Click to collapse
Thanks - console [NULL] seems to be a normal response, though oem_locked means you may wish to unlock your device again before proceeding (thus, if you run into any issues, you can flash a custom ROM).
Are you unlocking by using 'fastboot oem unlock <your unlock code>' and with the OEM unlocking enabled in Developer Options?
Software status: modified might be an issue - can you remember what firmware you flashed before the soak test (the NPJ25.75-2 firmware)?
Also, as you're now on the B1:06 bootloader, try not to flash older stock firmware onto your device.

Yes, i have a problem.
Flash seems to work perfectly, see the quote after.
I start from a lock bootloader (with status modified software, how i can go back to official ?)
After the flash, the phone will start on the ROM, OK... yessss !!! NO.... if I reboot the phone i was block on the recovery again and again...
Don't understand !
C:\Program Files (x86)\Minimal 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-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.010s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.130s]
finished. total time: 0.160s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal 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.442s]
finished. total time: 0.562s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.080s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.140s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 0.373s]
finished. total time: 0.912s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.380s]
finished. total time: 0.905s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.520s]
writing 'dsp'...
OKAY [ 0.258s]
finished. total time: 0.778s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 3.045s]
writing 'oem'...
OKAY [ 7.179s]
finished. total time: 10.234s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.223s]
writing 'system'...
OKAY [ 6.132s]
finished. total time: 14.355s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250842 KB)...
OKAY [ 7.914s]
writing 'system'...
OKAY [ 5.985s]
finished. total time: 13.900s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (254485 KB)...
OKAY [ 8.018s]
writing 'system'...
OKAY [ 7.665s]
finished. total time: 15.686s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (247298 KB)...
OKAY [ 7.800s]
writing 'system'...
OKAY [ 6.589s]
finished. total time: 14.390s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (260398 KB)...
OKAY [ 8.286s]
writing 'system'...
OKAY [ 5.844s]
finished. total time: 14.134s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262041 KB)...
OKAY [ 8.247s]
writing 'system'...
OKAY [ 5.862s]
finished. total time: 14.119s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261941 KB)...
OKAY [ 8.287s]
writing 'system'...
OKAY [ 10.808s]
finished. total time: 19.096s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (82497 KB)...
OKAY [ 2.610s]
writing 'system'...
OKAY [ 1.860s]
finished. total time: 4.470s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (76954 KB)...
OKAY [ 2.428s]
writing 'modem'...
OKAY [ 1.122s]
finished. total time: 3.551s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.028s]
finished. total time: 0.028s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.030s]
finished. total time: 0.040s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (2032 KB)...
OKAY [ 0.063s]
writing 'fsg'...
OKAY [ 0.070s]
finished. total time: 0.143s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.082s]
finished. total time: 0.092s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase customize
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:customize: not found
erasing 'customize'...
OKAY [ 0.010s]
finished. total time: 0.010s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase clogo
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:clogo: not found
erasing 'clogo'...
OKAY [ 0.020s]
finished. total time: 0.024s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: -0.000s
Click to expand...
Click to collapse

echo92 said:
Thanks - console [NULL] seems to be a normal response, though oem_locked means you may wish to unlock your device again before proceeding (thus, if you run into any issues, you can flash a custom ROM).
Are you unlocking by using 'fastboot oem unlock <your unlock code>' and with the OEM unlocking enabled in Developer Options?
Software status: modified might be an issue - can you remember what firmware you flashed before the soak test (the NPJ25.75-2 firmware)?
Also, as you're now on the B1:06 bootloader, try not to flash older stock firmware onto your device.
Click to expand...
Click to collapse
Yes, i start from this Build : NPJ25.75-2.
Ok, for your remark, i don't flash older stock firmware (to prevent hard brick I supposed !)
At this time, my phone is blocked on the recovery.
Now, I unlock the bootloader using the classical method :
- phone on the bootloader (oem_locked written on the screen, software status : modified)
go on this website :
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) BLABLA0737325667#
(bootloader) BLA93232334B53465347004D6F746F2047200000#
(bootloader) BLA7E8824CF486716F8F64F4CE1E39615A649B9C#
(bootloader) BLA1B501000000000000000000000000
OKAY [ 0.129s]
finished. total time: 0.134s
Click to expand...
Click to collapse
BLA is to mask the correct code... i use the data scrub on the moto website to prevent any mistake cut/paste !
After i received the email ...
I have to run twice the commands as mark :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock MYKEY
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock MYKEY
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Bootloader is unlocked! Rebooting phone
OKAY [ 0.237s]
finished. total time: 0.240s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
And after the automatic reboot after the second command line, the phone will written on the bootloader
software status : modified
flashin_unlocked...
If i choice "start" on the bootloader, the bootpage was : "your device has been unlocked etc etc, your device will boot in 5 seconds"
and do the same thing than previous :
5 boot loops on the boot page and after 3/4 minutes will start on the motorola bluescreen and logo motorola...
Don't understand !

benj29 said:
Yes, i start from this Build : NPJ25.75-2.
Ok, for your remark, i don't flash older stock firmware (to prevent hard brick I supposed !)
At this time, my phone is blocked on the recovery.
Now, I unlock the bootloader using the classical method :
- phone on the bootloader (oem_locked written on the screen, software status : modified)
go on this website :
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
BLA is to mask the correct code... i use the data scrub on the moto website to prevent any mistake cut/paste !
After i received the email ...
I have to run twice the commands as mark :
And after the automatic reboot after the second command line, the phone will written on the bootloader
software status : modified
flashin_unlocked...
If i choice "start" on the bootloader, the bootpage was : "your device has been unlocked etc etc, your device will boot in 5 seconds"
and do the same thing than previous :
5 boot loops on the boot page and after 3/4 minutes will start on the motorola bluescreen and logo motorola...
Don't understand !
Click to expand...
Click to collapse
Hmm, that fastboot flash log and the procedure you've mentioned to unlock should work. How long are you leaving your device on the Motorola bluescreen, as after a flash/wipe it might take some time to boot?
The bootloops aren't good though, I'm wondering if the flash storage on your device is okay or if it's failing. Does your device bootloop in the bootloader or in recovery? You mentioned your device hanging whilst you were in the stock recovery?

I don't stop the phone or reboot it, i wait each time... again and again (to avoid corruption or something like this).
To be exhaustive :
1. Power on
2. Bootscreen with bad id key etc...
3. The phone will enter in boot loop (3/4 times ) and after will go in recovery with "no command".
4. enter in the recovery (power + volume up)
5. reboot to the system now from the menu
6. boot to the ROM !
I don't understand why i need to pass by the recovery...

benj29 said:
I don't stop the phone or reboot it, i wait each time... again and again (to avoid corruption or something like this).
To be exhaustive :
1. Power on
2. Bootscreen with bad id key etc...
3. The phone will enter in boot loop (3/4 times ) and after will go in recovery with "no command".
4. enter in the recovery (power + volume up)
5. reboot to the system now from the menu
6. boot to the ROM !
I don't understand why i need to pass by the recovery...
Click to expand...
Click to collapse
I'm not sure either, whether there's an issue with your system (shouldn't be, since it's a clean flash), or if that's a fallback if you get a bootloop. Are you able to boot to the home screen/setup?

Yes, sorry, i write it (my english is not good ).
Yes, after the recovery and reboot the phone using the recovery, the phone will start.
SO, at this time, I have flashed TWRP, ElementalX and root using this :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672
At this time : TWRP, root, and rom will works.
Even i need to have a complex power on sequence using the recovery

benj29 said:
Yes, sorry, i write it (my english is not good ).
Yes, after the recovery and reboot the phone using the recovery, the phone will start.
SO, at this time, I have flashed TWRP, ElementalX and root using this :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672
Click to expand...
Click to collapse
At least it's working - which root manager did you go for, phh or SuperSU or magisk?

HARD BRICKED MOTO G4 plus

my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:

https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
tried this too but device get recognise

Cooltango26 said:
my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:
Click to expand...
Click to collapse
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.

ADITYA_KUMAR said:
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.
Click to expand...
Click to collapse
after the official update from ....update in my device .......my device was struck in boot loop ...so i tries flashing the stock rom to repair that ....during flashing it giving the above mention error ........

Only other things I can think of is perhaps holding down your power button (for up to 2-3 minutes) to force a hard shutdown, and then try booting. Alternatively, hold down both the power and volume down key, see if you can boot into the bootloader (which it looks like you can, if you're trying to fastboot the stock ROM). If so, then try to boot into the stock recovery and try a cache wipe or a factory reset (the factory reset will obviously wipe your data).
If your device is under warranty (and you did not unlock your bootloader at any point), the service centre might be the best bet for you, as we can't do anything with a locked bootloader and you're unable to boot to get to OEM unlocking...

The new [Updated] blankflash file for Moto g4 plus [June security patch ]
Hello friends
here is the new [Updated] blankflash file for June security patch
i hope it will help you. here is complete guide https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
about how to install it.
if it's works for you please let me know:highfive:

TWRP flashing error-please explain

I just unlocked my bootloader but keep getting an error when trying to flash TWRP (see in red below). I have tried both 3.0.2-0 and 3.1.1.0. I got both files from the TWRP website. I have turned the phone off immediately after flashing and tried to reboot into TWRP but that hasn't worked.
Need suggestions please.
D:\Computer\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.0.2-0-athene.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12496 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Image not signed or corrupt

I got it. I re-read the "how to" thread and this is what I wasn't doing: Reboot to recovery after flashing the twrp image. Then reboot your device from recovery.
Moderator, please delete this thread. Thanks.

[help] hard brick with December patch has solution?

to be able to revive but to flash the December rom stock of error

What errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

echo92 said:
what errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
i tried with above link but no success

prasadak2811 said:
i tried with above link but no success
Click to expand...
Click to collapse
Can you provide us with some information please as well?
What device do you have, how did your device hard brick and what errors/messages are you getting?

echo92 said:
What errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
xt 1640
C:\Program Files (x86)\Minimal 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: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: 0038111937
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: D6EBBF0200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 09-15-2017
(bootloader) sku: XT1640-DS
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed May 4 19:56:34 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-13/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta
(bootloader) ro.build.version.full[1]: il.pt.BR
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband: M8952_70030.25.03.62.01R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.10.84-ElementalX-G4-2.00
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.4 201506
(bootloader) kernel.version[2]: 29 (prerelease) (crosstool-NG 1.20.0 - L
(bootloader) kernel.version[3]: inaro GCC 2015.06 - Cortex-A15) ) #1 SMP
(bootloader) kernel.version[4]: PREEMPT Thu Jan 25 12:45:01 EST 2018
(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 (0)
(bootloader) ro.carrier: retbr
all: listed above
finished. total time: 0.488s

echo92 said:
What errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
I'm getting these errors
C:\Program Files (x86)\Minimal 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-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.024s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.111s]
finished. total time: 0.138s
C:\Program Files (x86)\Minimal 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.158s]
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.622s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.101s]
writing 'logo'...
OKAY [ 0.064s]
finished. total time: 0.170s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.593s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.801s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.590s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.802s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.573s]
writing 'dsp'...
OKAY [ 0.267s]
finished. total time: 0.845s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 3.297s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.425s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.868s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.995s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250842 KB)...
OKAY [ 8.556s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.622s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (254493 KB)...
OKAY [ 8.667s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.714s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (247302 KB)...
OKAY [ 8.439s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.518s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (260402 KB)...
OKAY [ 8.872s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.918s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262057 KB)...
OKAY [ 8.904s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.956s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261941 KB)...
OKAY [ 8.897s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.977s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (82497 KB)...
OKAY [ 2.817s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.876s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (76958 KB)...
OKAY [ 2.624s]
writing 'modem'...
OKAY [ 1.136s]
finished. total time: 3.764s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.040s]
finished. total time: 0.043s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.039s]
finished. total time: 0.041s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (2032 KB)...
OKAY [ 0.096s]
writing 'fsg'...
OKAY [ 0.077s]
finished. total time: 0.179s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.042s]
finished. total time: 0.049s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.120s]
finished. total time: 0.122s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase customize
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:customize: not found
erasing 'customize'...
OKAY [ 0.033s]
finished. total time: 0.035s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase clogo
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:clogo: not found
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>

jadeilson777 said:
I'm getting these errors
<snip>
Click to expand...
Click to collapse
Thanks for that. A few things I've noted:
1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?
2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.
3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.
If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.

echo92 said:
Thanks for that. A few things I've noted:
1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?
2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.
3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.
If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.
Click to expand...
Click to collapse
1) I was in the stock rom of December with elemental kernel x to get root with magisk and was without network because of the baseband and I looked in the forum something about there I tried to transfer some files of the 1643 xt was when the hard brick occurred I used the recent blankflash and able to revive the bootloader but when trying to flash again the stock of December gave error plus the boot loader went back to normal as in the attached image

echo92 said:
Thanks for that. A few things I've noted:
1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?
2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.
3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.
If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.
Click to expand...
Click to collapse
2) Yes I was without a network and was trying to fix what happened to the hard brick
3) Yes I am trying to flash the December rom stock NPJS25.93-14-13

jadeilson777 said:
1) I was in the stock rom of December with elemental kernel x to get root with magisk and was without network because of the baseband and I looked in the forum something about there I tried to transfer some files of the 1643 xt was when the hard brick occurred I used the recent blankflash and able to revive the bootloader but when trying to flash again the stock of December gave error plus the boot loader went back to normal as in the attached image
Click to expand...
Click to collapse
jadeilson777 said:
2) Yes I was without a network and was trying to fix what happened to the hard brick
3) Yes I am trying to flash the December rom stock NPJS25.93-14-13
Click to expand...
Click to collapse
Hmm, what files did you try to transfer, was it the hw, fsg and modem partitions, and did you transfer them to the correct partitions? Those commands are very powerful and will not alert you if the incorrect partition is overwritten.
I'm guessing by the screenshot you're showing that your bootloader screen is similar, as that bootloader screen is for Osprey devices (Moto G 2015). It should be like that as you've flashed the bootloader from the stock NPJS25.93-14-13 ROM, just with athene (Moto G4) details.
How did you lose network in the first place, was it after flashing firmware?
If you can, I'd doublecheck if your bootloader is unlocked and try unlocking your bootloader (which will erase your information), as looking through your flash results, it looks like your bootloader is rejecting your flashing. NPJS25.93-14-13 should not give you pre-flash validation errors on a G4 Plus as that's the current firmware we have, unless you've flashed a different December 2017 build before or received an OTA update newer than December 2017.
If unlocking the bootloader doesn't work or doesn't resolve not being able to flash, then we may have to begin considering an expensive service repair.

echo92 said:
Hmm, what files did you try to transfer, was it the hw, fsg and modem partitions, and did you transfer them to the correct partitions? Those commands are very powerful and will not alert you if the incorrect partition is overwritten.
I'm guessing by the screenshot you're showing that your bootloader screen is similar, as that bootloader screen is for Osprey devices (Moto G 2015). It should be like that as you've flashed the bootloader from the stock NPJS25.93-14-13 ROM, just with athene (Moto G4) details.
How did you lose network in the first place, was it after flashing firmware?
If you can, I'd doublecheck if your bootloader is unlocked and try unlocking your bootloader (which will erase your information), as looking through your flash results, it looks like your bootloader is rejecting your flashing. NPJS25.93-14-13 should not give you pre-flash validation errors on a G4 Plus as that's the current firmware we have, unless you've flashed a different December 2017 build before or received an OTA update newer than December 2017.
If unlocking the bootloader doesn't work or doesn't resolve not being able to flash, then we may have to begin considering an expensive service repair.
Click to expand...
Click to collapse
my bootloader is blocked and in my opinion this is giving pre-flash error pq was in stock rom December with twrp and with elemental kernbel x

jadeilson777 said:
my bootloader is blocked and in my opinion this is giving pre-flash error pq was in stock rom December with twrp and with elemental kernbel x
Click to expand...
Click to collapse
If your bootloader is locked, then having TWRP and ElementalX on your device will cause your device to fail to boot. A locked bootloader, especially under Nougat, is quite strictly enforced, and is expecting stock recovery and stock kernel, no modifications whatsoever.
The stock ROM flash should be overwriting both partitions with the stock firmware, but as you're not bypassing the strict verification checks, then you can try to unlock your bootloader again and try to re-flash. Alternatively, if you unlock, you may be able to boot if there's still TWRP and ElementalX on your device. Your warranty is voided anyway as you'd have unlocked your bootloader in the past to flash TWRP and ElementalX.
If that doesn't work, it may suggest the flash memory or another hardware fault is present, which may require a motherboard replaement.

echo92 said:
If your bootloader is locked, then having TWRP and ElementalX on your device will cause your device to fail to boot. A locked bootloader, especially under Nougat, is quite strictly enforced, and is expecting stock recovery and stock kernel, no modifications whatsoever.
The stock ROM flash should be overwriting both partitions with the stock firmware, but as you're not bypassing the strict verification checks, then you can try to unlock your bootloader again and try to re-flash. Alternatively, if you unlock, you may be able to boot if there's still TWRP and ElementalX on your device. Your warranty is voided anyway as you'd have unlocked your bootloader in the past to flash TWRP and ElementalX.
If that doesn't work, it may suggest the flash memory or another hardware fault is present, which may require a motherboard replaement.
Click to expand...
Click to collapse
I already tried to unlock the bootloader but I get the result of fetuare disable which is the debugging usb or unlock option of oem that is disabled

jadeilson777 said:
I already tried to unlock the bootloader but I get the result of fetuare disable which is the debugging usb or unlock option of oem that is disabled
Click to expand...
Click to collapse
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.
If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.

echo92 said:
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.
If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.
Click to expand...
Click to collapse
if I was in hard brick but can revive only the bootloader and the system can not activate these options so there is no way to flip the bootloader and with the bootloader locked I can not flashear a previous ROM nor the stock of December pq was with the elemental kernel x of January 25th so I have to wait for a security patch update to flash over

echo92 said:
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.
If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.
Click to expand...
Click to collapse
I'm 16 years old and I do not have money for another motherboard or a new moto g4 plus

jadeilson777 said:
if I was in hard brick but can revive only the bootloader and the system can not activate these options so there is no way to flip the bootloader and with the bootloader locked I can not flashear a previous ROM nor the stock of December pq was with the elemental kernel x of January 25th so I have to wait for a security patch update to flash over
Click to expand...
Click to collapse
Yeah, hopefully the February 2018 security patch ROM should be on its way soon. If that doesn't fix things then you may have to visit a service centre.
---------- Post added at 06:56 PM ---------- Previous post was at 06:53 PM ----------
jadeilson777 said:
I'm 16 years old and I do not have money for another motherboard or a new moto g4 plus
Click to expand...
Click to collapse
Unfortunately a hard brick in this manner seems to be quite hard to fix, especially if you cannot flash the stock ROM (with a locked bootloader failing validation). However, we'll have to see if the newer stock ROM resolves this.

echo92 said:
Yeah, hopefully the February 2018 security patch ROM should be on its way soon. If that doesn't fix things then you may have to visit a service centre.
---------- Post added at 06:56 PM ---------- Previous post was at 06:53 PM ----------
Unfortunately a hard brick in this manner seems to be quite hard to fix, especially if you cannot flash the stock ROM (with a locked bootloader failing validation). However, we'll have to see if the newer stock ROM resolves this.
Click to expand...
Click to collapse
Can you tell me when the next update comes out if and still this month?

jadeilson777 said:
Can you tell me when the next update comes out if and still this month?
Click to expand...
Click to collapse
Honestly no idea - we've not even seen the OTA update for the February 2018 security update, just the patch notes. Could be this month, could be next month. Furthermore, that still relies on someone capturing and uploading the stock ROM firmware with that patch to Android FileHost or somewhere.