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.

Can not flash Stock Image

I will flash the latest POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but i get every time a failed.
Code:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.078s
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>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' (5115 KB)...
OKAY [ 0.109s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.390s

I recently flash the stock rom using this method, is the easiest way.
https://youtu.be/qjbU72RH_Rk
Hope this helps you...

That video is over a year old and the AFH firmware listed for G5+ isn't as complete as the latest official list here, also you don't need to install certain utilities he mentions.
HOW TO UNBRICK MOTO G5 PLUS AND RESTORE TO STOCK
I'd recommend that 4-27-17 article meant just for our phone containing a link to a toolkit with everything you need including the POTTER_NPN25.137-35 firmware. Your variant's firmware may be different though. so check in settings and get the correct one at the above link I gave, if necessary. I've successfully restored to stock several times using this method.

I have a EU Version i think. Have buy in Austria. Have download .35 but its 7.0 and not 7.1. Security Patch show me January 2017? Befor i have unlock the Bootloader its have show me March 2017 i think.

hi will it work ?
will it work definitely ?

[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.

Need help my Moto g5plus hard brick dead solution

Hi everybody today I want to flash pixel rom pie 9
but Why I don't know my phone to have hardbrick,
I can try to unlock bootloader again, but I still the code on CMD
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.016s]
finished. total time: 0.016s
Can help me pls
Sorry for my language

terawoot said:
Hi everybody today I want to flash pixel rom pie 9
but Why I don't know my phone to have hardbrick,
I can try to unlock bootloader again, but I still the code on CMD
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.016s]
finished. total time: 0.016s
Can help me pls
Sorry for my language
Click to expand...
Click to collapse
PS C:\Users\Skincat\Desktop\motog5+\mfastboot> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 5f9fd45e
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 8B55166800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(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) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.078s

terawoot said:
PS C:\Users\Skincat\Desktop\motog5+\mfastboot> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 5f9fd45e
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 8B55166800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(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) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.078s
Click to expand...
Click to collapse
then now I still only this
(bootloader) Not in unlocked state
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.088s
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.366s
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.055s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.098s
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.378s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.564s
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.464s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.689s
target reported max download size of 534773760 bytes
sending 'system' (256557 KB)...
OKAY [ 5.579s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.641s
target reported max download size of 534773760 bytes
sending 'system' (256617 KB)...
OKAY [ 5.564s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.599s
target reported max download size of 534773760 bytes
sending 'system' (253985 KB)...
OKAY [ 5.563s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.596s
target reported max download size of 534773760 bytes
sending 'system' (256710 KB)...
OKAY [ 5.563s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.589s
target reported max download size of 534773760 bytes
sending 'system' (256912 KB)...
OKAY [ 5.573s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.579s
target reported max download size of 534773760 bytes
sending 'system' (257861 KB)...
OKAY [ 5.575s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.609s
target reported max download size of 534773760 bytes
sending 'system' (260027 KB)...
OKAY [ 5.639s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.679s
target reported max download size of 534773760 bytes
sending 'system' (257785 KB)...
OKAY [ 5.567s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.610s
target reported max download size of 534773760 bytes
sending 'system' (257830 KB)...
OKAY [ 5.563s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.600s
target reported max download size of 534773760 bytes
sending 'modem' (71925 KB)...
OKAY [ 1.555s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.583s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.004s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.019s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.072s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.111s
error: cannot load 'BTFM.bin'
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.008s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
...
(bootloader) Not in unlocked state
OKAY [ 0.086s]
finished. total time: 0.087s
rebooting...

Are you trying to flash a firmware or unlock the bootloader? Anyways the firmware you are trying to flash isn't the latest. It won't downgrade. Try the latest firmware.
Your bootloader seems to be locked.
You need to unlock that first. Try turning on OEM unlock from developer settings and then try the unlock data command.
And please follow guides or chances are you won't be able to recover the phone.

debdeep98 said:
Are you trying to flash a firmware or unlock the bootloader? Anyways the firmware you are trying to flash isn't the latest. It won't downgrade. Try the latest firmware.
Your bootloader seems to be locked.
You need to unlock that first. Try turning on OEM unlock from developer settings and then try the unlock data command.
And please follow guides or chances are you won't be able to recover the phone.
Click to expand...
Click to collapse
But I can't not start up my phone. so I think the bootloader is broken.

terawoot said:
But I can't not start up my phone. so I think the bootloader is broken.
Click to expand...
Click to collapse
Are you able to bring the device in bootloader/stock recovery mode?
If yes boot to bootloader mode with the key combination (I think it was power and vol down or power and vol up) and fastboot flash the latest stock firmware for your region:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
You don't need an unlocked bootloader for that.

terawoot said:
But I can't not start up my phone. so I think the bootloader is broken.
Click to expand...
Click to collapse
No it's not broken. If you are flashing oreo fimware there are 9 system sparse chunks(0-8). Make sure u flash them all.

terawoot said:
But I can't not start up my phone. so I think the bootloader is broken.
Click to expand...
Click to collapse
debdeep98 said:
No it's not broken. If you are flashing oreo fimware there are 9 system sparse chunks(0-8). Make sure u flash them all.
Click to expand...
Click to collapse
For Oreo the whole sets of commands are for
Locking:
-----------------
fastboot oem lock
fastboot oem lock
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 system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
-------------------
Flashing:
-------------------
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0 fastboot flash system system.img_sparsechunk.1 fastboot flash system system.img_sparsechunk.2 fastboot flash system system.img_sparsechunk.3 fastboot flash system system.img_sparsechunk.4 fastboot flash system system.img_sparsechunk.5 fastboot flash system system.img_sparsechunk.6 fastboot flash system system.img_sparsechunk.7 fastboot flash system system.img_sparsechunk.8 fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
-----------------------------------
The same commands for Nougat:
Flashing:
-----------------------------------
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 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
--------------------------
Locking:
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock

[Start Up Failed] [Error: Failed to pass validation ] I cant flash stock.

First: Sorry for my horrible english.
Second: I have a G5+ with a wrong SKU model (See screenshots) XT1601 (Is from G4 play, and yes, the phone is original)
{
"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"
}
So, the other day i want to flash via terminal stock 8. ( I cant unlock bootloader, so i cant have twrp or similar)
And... My phone got bricked. And now, i cant unlock OEM, and cant flash any rom via all the known methods (Lenovo assistant etc) because the assistant dont recognize my phone (Bc the model in the phone is wrong XT1601) and i dont know what rom i need to flash because i dont find the exact rom i have working before.
And when i try to flash any rom i got this kind of messages in my device:
[Start Up Failed] [Error: Failed to pass validation ] [Fastboot reason: UTAG "bootmode" configured on fastboot]
And the Stock Recovery is gone.
I try to unlock OEM via all the known methos with no luck.
And i try THIS without any luck too.
Any method to revive the phone?
Thanks!

Did you try fastboot oem fb_mode_clear ?
May be try to flash a newer firmware. The latest one.
Oreo has 9 system files. systemsparsechunk(0-8). Did you flash all the files? Bc some guides have only 5 files(0-4).

debdeep98 said:
Did you try fastboot oem fb_mode_clear ?
May be try to flash a newer firmware. The latest one.
Oreo has 9 system files. systemsparsechunk(0-8). Did you flash all the files? Bc some guides have only 5 files(0-4).
Click to expand...
Click to collapse
My device dont have recovery Stock anymore, is this a problem?
And, what rom i need to flash?

Gothorian said:
My device dont have recovery Stock anymore, is this a problem?
And, what rom i need to flash?
Click to expand...
Click to collapse
No need to use recovery. You need to boot into bootloader (also no need to be unlocked) and enter the command debdeep98 suggests.

lpulido said:
No need to use recovery. You need to boot into bootloader (also no need to be unlocked) and enter the command debdeep98 suggests.
Click to expand...
Click to collapse
Ok, considering my device have a wrong SKU and the screenshots, what rom i need to flash? Im from Argentina.
EDIT: Yes, i try fb_mode_clear but still nothing, maybe i need to find the correct rom.

Gothorian said:
Ok, considering my device have a wrong SKU and the screenshots, what rom i need to flash? Im from Argentina.
EDIT: Yes, i try fb_mode_clear but still nothing, maybe i need to find the correct rom.
Click to expand...
Click to collapse
Can you post the picture of bootloader, so we could confirm which firmware your device needs.but still you You could flash your country firmware from here.
Link:-https://mirrors.lolinet.com/firmware/moto/potter/official/
And here is the procedure thread :-https://forum.xda-developers.com/g5...stboot-flash-stock-oreo-t3848433/post77752702

Gothorian said:
Ok, considering my device have a wrong SKU and the screenshots, what rom i need to flash? Im from Argentina.
EDIT: Yes, i try fb_mode_clear but still nothing, maybe i need to find the correct rom.
Click to expand...
Click to collapse
So I'm guessing your model is xt1680. So just flash the latest retail firmware 85-17-6 from link riyan mentioned. Update channels won't matter anymore since update cycle is over.

debdeep98 said:
So I'm guessing your model is xt1680. So just flash the latest retail firmware 85-17-6 from link riyan mentioned. Update channels won't matter anymore since update cycle is over.
Click to expand...
Click to collapse
Ok, let me try, but u need to know i downloaded the correct rom i have before and try to flash it without luck. And the terminal give me this kind of results (And with other roms i try too):
And then, i reboot my phone and got Start Up Failed. Error: Failed to pass validation etc etc etc.
Edit: Yes, i have drivers installed.

Gothorian said:
Ok, let me try, but u need to know i downloaded the correct rom i have before and try to flash it without luck. And the terminal give me this kind of results (And with other roms i try too):
And then, i reboot my phone and got Start Up Failed. Error: Failed to pass validation etc etc etc.
Click to expand...
Click to collapse
Yeah.. no.. It says security version downgrade.. Means you are on a newer firmware and you are trying to flash an older firmware.. Try the latest firmware..
Try
Code:
fastboot getvar all
. This should show the last build id.. it should be (bootloader) ro.build.fingerprint. something like this.. you either get the lastest firmware or the one you are already on..
I don't remember correctly but flashing older firmware bricks the device. I think. There are guides to restore.
Edit. Okay just saw that you are on 92-4. Just try an OPS build.

debdeep98 said:
Yeah.. no.. It says security version downgrade.. Means you are on a newer firmware and you are trying to flash an older firmware.. Try the latest firmware..
Try
Code:
fastboot getvar all
. This should show the last build id.. it should be (bootloader) ro.build.fingerprint. something like this.. you either get the lastest firmware or the one you are already on..
I don't remember correctly but flashing older firmware bricks the device. I think. There are guides to restore.
Edit. Okay just saw that you are on 92-4. Just try an OPS build.
Click to expand...
Click to collapse
Sorry im new with Moto Devices, (All my life i have Samsungs) what are OPS build? And where i find it?
Thanks for u help.

Gothorian said:
Sorry im new with Moto Devices, (All my life i have Samsungs) what are OPS build? And where i find it?
Thanks for u help.
Click to expand...
Click to collapse
Your build no (compilacion) starts with NPS. That is a nougat(7) build. OPS are the Oreo(8) builds.
What is the version of the firmware you are trying to flash? And which guide are you using?

debdeep98 said:
Your build no (compilacion) starts with NPS. That is a nougat(7) build. OPS are the Oreo(8) builds.
What is the version of the firmware you are trying to flash? And which guide are you using?
Click to expand...
Click to collapse
Sorry for the delay guys.
im not use any guide, and for the version, i have a lot here in my pc, but nothing works.
Sorry for the bad quality.
I try everything, but nothing. Every time i end here. Maybe is the wrong version/variant XT1601. (Look at the photo)
Idk if a blankfkash work... But i need one for my variant.

Gothorian said:
Sorry for the delay guys.
im not use any guide, and for the version, i have a lot here in my pc, but nothing works.
Sorry for the bad quality.
I try everything, but nothing. Every time i end here. Maybe is the wrong version/variant XT1601. (Look at the photo)
Idk if a blankfkash work... But i need one for my variant.
Click to expand...
Click to collapse
Why don't you use Lenovo Moto smart assistant app in your pc as it will flash the device with the latest firmware and you don't need to do anything.

riyan65 said:
Why don't you use Lenovo Moto smart assistant app in your pc as it will flash the device with the latest firmware and you don't need to do anything.
Click to expand...
Click to collapse
Because Lenovo Moto smart assistant dont recognize mi phone.

Gothorian said:
Sorry for the delay guys.
im not use any guide, and for the version, i have a lot here in my pc, but nothing works.
Sorry for the bad quality.
I try everything, but nothing. Every time i end here. Maybe is the wrong version/variant XT1601. (Look at the photo)
Idk if a blankfkash work... But i need one for my variant.
Click to expand...
Click to collapse
The baseband and bl are ok. Model is different. I don't think blank flash would work and don't try that unless you are only left with the blink notif light.
Try flashing this file.
[https://mirrors.lolinet.com/firmwar...bsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip]
Does the bootloader unlock?
From the picture it says security version downgrade. So this should work.

debdeep98 said:
The baseband and bl are ok. Model is different. I don't think blank flash would work and don't try that unless you are only left with the blink notif light.
Try flashing this file.
[https://mirrors.lolinet.com/firmwar...bsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip]
Does the bootloader unlock?
From the picture it says security version downgrade. So this should work.
Click to expand...
Click to collapse
Let me try flashing the rom u post. And no. I cant unlock bootloader sadly.

debdeep98 said:
The baseband and bl are ok. Model is different. I don't think blank flash would work and don't try that unless you are only left with the blink notif light.
Try flashing this file.
[https://mirrors.lolinet.com/firmwar...bsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip]
Does the bootloader unlock?
From the picture it says security version downgrade. So this should work.
Click to expand...
Click to collapse
Still nothing. I adjunt the code in ADB/Fastboot:
Code:
Microsoft Windows [Versión 10.0.17763.503]
(c) 2018 Microsoft Corporation. Todos los derechos reservados.
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot devices
ZY2245XNKB fastboot
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.172s]
finished. total time: 0.203s
C:\Users\orcri\Desktop\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-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.156s
C:\Users\orcri\Desktop\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' (5115 KB)...
OKAY [ 0.125s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(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 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.781s]
finished. total time: 0.922s
C:\Users\orcri\Desktop\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.078s]
writing 'logo'...
OKAY [ 0.141s]
finished. total time: 0.234s
C:\Users\orcri\Desktop\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.407s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.672s
C:\Users\orcri\Desktop\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' (20580 KB)...
OKAY [ 0.516s]
writing 'recovery'...
(bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.812s
C:\Users\orcri\Desktop\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.391s]
writing 'dsp'...
OKAY [ 0.297s]
finished. total time: 0.719s
C:\Users\orcri\Desktop\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-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.516s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.687s
C:\Users\orcri\Desktop\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' (256557 KB)...
OKAY [ 6.141s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.312s
C:\Users\orcri\Desktop\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' (256617 KB)...
OKAY [ 6.098s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.176s
C:\Users\orcri\Desktop\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' (253985 KB)...
OKAY [ 6.092s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.186s
C:\Users\orcri\Desktop\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' (256710 KB)...
OKAY [ 6.178s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.240s
C:\Users\orcri\Desktop\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' (256912 KB)...
OKAY [ 6.093s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.125s
C:\Users\orcri\Desktop\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' (257861 KB)...
OKAY [ 6.069s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.147s
C:\Users\orcri\Desktop\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' (260027 KB)...
OKAY [ 6.191s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.269s
C:\Users\orcri\Desktop\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' (257785 KB)...
OKAY [ 6.129s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.223s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.8
(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' (257830 KB)...
OKAY [ 6.194s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.272s
C:\Users\orcri\Desktop\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' (71925 KB)...
OKAY [ 1.735s]
writing 'modem'...
OKAY [ 1.141s]
finished. total time: 2.891s
C:\Users\orcri\Desktop\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.047s]
finished. total time: 0.047s
C:\Users\orcri\Desktop\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.047s]
finished. total time: 0.062s
C:\Users\orcri\Desktop\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' (3012 KB)...
OKAY [ 0.094s]
writing 'fsg'...
OKAY [ 0.125s]
finished. total time: 0.235s
C:\Users\orcri\Desktop\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.031s]
finished. total time: 0.047s
C:\Users\orcri\Desktop\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.187s]
finished. total time: 0.203s
C:\Users\orcri\Desktop\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'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.062s
C:\Users\orcri\Desktop\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'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.172s]
finished. total time: 0.188s
C:\Users\orcri\Desktop\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.266s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_set
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.172s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(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 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.578s]
finished. total time: 0.766s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.234s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.438s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.703s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.532s]
writing 'recovery'...
(bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.828s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.391s]
writing 'dsp'...
OKAY [ 0.301s]
finished. total time: 0.722s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.506s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.646s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (256557 KB)...
OKAY [ 6.149s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.274s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (256617 KB)...
OKAY [ 6.109s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.140s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (253985 KB)...
OKAY [ 6.156s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.218s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (256710 KB)...
OKAY [ 6.172s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.234s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (256912 KB)...
OKAY [ 6.017s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.048s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (257861 KB)...
OKAY [ 6.265s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.312s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (260027 KB)...
OKAY [ 6.356s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.396s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (257785 KB)...
OKAY [ 6.057s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.182s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (257830 KB)...
OKAY [ 6.156s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.203s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71925 KB)...
OKAY [ 1.766s]
writing 'modem'...
OKAY [ 1.109s]
finished. total time: 2.875s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.062s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.125s]
finished. total time: 0.219s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.187s]
finished. total time: 0.187s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.031s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.047s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.031s
C:\Users\orcri\Desktop\Minimal ADB and Fastboot>fastboot oem fb_mode_set
And in Fastboot i got this:Invalid PIV system image. Why the phone cant flash any rom? it worries me.
In Bootloader Logs i got this:
Set Up Failed. Your device didn't start up successfully try to conect...
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-Through from normal boot mode
And yes, im trying flash the rom u gaveme.

Gothorian said:
Still nothing. I adjunt the code in ADB/Fastboot:
And in Fastboot i got this:Invalid PIV system image. Why the phone cant flash any rom? it worries me.
In Bootloader Logs i got this:
Set Up Failed. Your device didn't start up successfully try to conect...
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-Through from normal boot mode
And yes, im trying flash the rom u gaveme.
Click to expand...
Click to collapse
Can you post the procedure how you are flashing the ROM in device.

riyan65 said:
Can you post the procedure how you are flashing the ROM in device.
Click to expand...
Click to collapse
Im use this procedure, basically y extract the xml.zip into fastboot lite folder, run the CMD first i do "fastboot device" if the pc recognize my phone and copy/paste all the commands and wait.

Did you buy the device brand new or was it second hand?
It looks like the device was already bricked once and someone blank flashed it.
Flashing isn't working because the model no is different probably.
Someone managed to flash oreo with the Z Play bootloader the phone boots up but there is no connectivity.