Database Users

need the stock fastboot rom for the build npjs 25.93-14.4, (March security patch)

In need of the full stock firmware for the latest build NPJS 25.93-14.4(march security patch) with the bootloader relocking ability, just like the link below for the build NPJ25-93-14 as it won't allow me downgrade and relock the bootloader anymore:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
In need for relocking the bootloader as I need to try my luck with the service center for the screen burn issue.
Any help would be really appreciated.
Much thanks in advance.

You can relock using the same procedure, input those lines in cmd window, while phone is in fastboot mode:
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
Note that the first two lines HAVE to be repeated like that.

C:\mfastboot>mfastboot oem lock begin
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.004s]
finished. total time: 0.005s
C:\mfastboot>fastboot oem lock begin
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.016s]
finished. total time: 0.017s
C:\mfastboot>fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.006s]
finished. total time: 0.007s

it says still still require signed boot.img

I thought that you are on the STOCK build 25-93-14-4?
You can't go back to 25.93-14.4?

SoNic67 said:
I thought that you are on the STOCK build 25-93-14-4?
You can't go back to 25.93-14.4?
Click to expand...
Click to collapse
I'm on NPJS 25.93.14.4, i'll just downgrade to 25-93-14 and check with the commands provided.
Btw, thank you and sorry as I'm a noob and bothering you again and again.

just one thing, I'll be using the following commnads:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
for downgrading to 93-14.
That would be fine right?

Yeah, fastboot or mfastboot are equal. It's a batch file in that zip file that does the locking automatically:
Code:
mfastboot oem lock begin
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem lock
mfastboot reboot

C:\mfastboot>mfastboot oem lock begin
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.004s]
finished. total time: 0.005s
C:\mfastboot>mfastboot oem lock begin
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.011s]
finished. total time: 0.012s
C:\mfastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.043s
C:\mfastboot>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (3651 KB)...
OKAY [ 0.153s]
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.433s]
finished. total time: 0.589s
C:\mfastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (2105 KB)...
OKAY [ 0.084s]
writing 'logo'...
OKAY [ 0.055s]
finished. total time: 0.142s
C:\mfastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.653s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.821s
C:\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16484 KB)...
OKAY [ 0.649s]
writing 'recovery'...
(bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.819s
C:\mfastboot>mfastboot flash dsp adspso.bin
target max-sparse-size: 256MB
sending 'dsp' (16384 KB)...
OKAY [ 0.648s]
writing 'dsp'...
OKAY [ 0.242s]
finished. total time: 0.894s
C:\mfastboot>mfastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (96490 KB)...
OKAY [ 3.744s]
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: 3.804s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (261001 KB)...
OKAY [ 10.083s]
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: 10.149s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (250858 KB)...
OKAY [ 9.720s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.749s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (254625 KB)...
OKAY [ 9.288s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.317s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (261577 KB)...
OKAY [ 9.615s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.636s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (260443 KB)...
OKAY [ 9.842s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.880s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (248842 KB)...
OKAY [ 9.306s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.332s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (259549 KB)...
OKAY [ 9.799s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.843s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (82497 KB)...
OKAY [ 3.210s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.229s
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (76954 KB)...
OKAY [ 3.005s]
writing 'modem'...
OKAY [ 1.133s]
finished. total time: 4.142s
C:\mfastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.030s]
finished. total time: 0.031s
C:\mfastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.023s
C:\mfastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (2040 KB)...
OKAY [ 0.084s]
writing 'fsg'...
OKAY [ 0.064s]
finished. total time: 0.151s
C:\mfastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.021s]
finished. total time: 0.023s
C:\mfastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 1.322s]
finished. total time: 1.352s
C:\mfastboot>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\mfastboot>mfastboot erase clogo
erasing 'clogo'...
OKAY [ 0.017s]
finished. total time: 0.019s
C:\mfastboot>mfastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.004s]
finished. total time: 0.006s
C:\mfastboot>mfastboot reboot

SoNic67 said:
You can relock using the same procedure, input those lines in cmd window, while phone is in fastboot mode:
Note that the first two lines HAVE to be repeated like that.
Click to expand...
Click to collapse
He just can't. Motorola is a BI***, now bootloader is asking for signed boot.img, next it will ask for signed oem.img and/or system.img (it actually mandates both, but it won't tell you right straight) after that it might please to let him relock the bootloader. All of those signed images must match the gpt.bin version (i.e: NPJ.25.93-14.4)
I'm a noob, so not sure why people wonder this happens, but it sure does.
I'm very interested as well because I have another issue that can't be solved except with the requested ROM: CID = 0xDEAD, bootloader says "oem_locked" while it is not and not one type of boot is possible (that was my fault writing inconsistent dd images to phone)
Anyway, he is right, and his problem won't go away unless he gets what he stated in his very first post.

MK+2017 said:
He just can't. Motorola is a BI***, now bootloader is asking for signed boot.img, next it will ask for signed oem.img and/or system.img (it actually mandates both, but it won't tell you right straight) after that it might please to let him relock the bootloader. All of those signed images must match the gpt.bin version (i.e: NPJ.25.93-14.4)
I'm a noob, so not sure why people wonder this happens, but it sure does.
I'm very interested as well because I have another issue that can't be solved except with the requested ROM: CID = 0xDEAD, bootloader says "oem_locked" while it is not and not one type of boot is possible (that was my fault writing inconsistent dd images to phone)
Anyway, he is right, and his problem won't go away unless he gets what he stated in his very first post.
Click to expand...
Click to collapse
yupp, i too think that the bootloader can only be relocked if the latest official firmware with the latest security patch is flashed via fastboot.
If possible can anyone please provide the latest firmware for xt1643 with the march sec. patch?

I have assumed that he has just installed the update and didn't change anything in the system.

i am on stock 93-14 build, dec sec. patch. Now should i have to wait for the march firmware to be posted or is there anything else that i can still do to lock the bootloader?

Once you flash an official OTA, you cannot downgrade the bootloader and partition table to a previous version. And locking the bootloader will need the latest fastboot firmware. Also, please consider using something like pastebin or hastebin for such long logs/outputs.

that is what i need, is it possible to create the new firmware using the latest ota file?

That's I haven't updated to 93-14-4 build cause you never know what goes wrong with your phone BTW way you can temporarily fix the screen burn issue by changing the RGB values using kernel auditor or ex kernel manager
Sent from my Moto G4 Plus using Tapatalk

yupp, i am using the bluelight filter for the time being

Same thing here, guess we have to wait for official and complete firmware... -_-

yupp, waiting for the same

Good Ness e
https://forum.xda-developers.com/mo...rom-npjs25-93-14-4-march-1-t3608138?nocache=1

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.

Trashed my Bootloader, GPT tables corrupt

So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
Code:
$ fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.059s
$ fastboot flash bootloader bootloader.img
Sending 'bootloader' (5115 KB) OKAY [ 0.114s]
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.309s
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Code:
<waiting for device>
Flashing recovery results in
Code:
$ fastboot flash recovery twrp-3.2.3-1-potter.img
Sending 'recovery' (16316 KB) OKAY [ 0.351s]
Writing 'recovery' (bootloader) Image not signed or corrupt
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
Finished. Total time: 0.355s
Any help is appreciated!

Drkmatr1984 said:
So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Flashing recovery results in
Any help is appreciated!
Click to expand...
Click to collapse
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.

Also, make sure to flash the latest stock firmware, being sure not to try and revert to an earlier version. Don't flash blankflash unless you are totally bricked, with just flashing light. Your device will never be the same if you do.

riyan65 said:
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.
Click to expand...
Click to collapse
How do I use ADB if I can't get beyond fastboot? I can't load TWRP or flash TWRP to get into it to access ADB. And ADB commands don't work from the fastboot bootloader screen.
Doing "fastboot erase <partition name>" or "fastboot format:ext4 <partition name>" also fails same as the other fastboot flash commands so I can't erase my partitions from fastboot before re-flashing.

If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.

[email protected] said:
If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.
Click to expand...
Click to collapse
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
Code:
C:\ProgramData\LMSA\Download\RomFiles>fastboot devices
ZY224262W9 fastboot
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.008s
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
ZY224262W9 fastboot
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.005s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>OREO.BAT
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
FAILED (remote failure)
Finished. Total time: 0.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.146s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
Sending 'boot' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 6.967s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
Sending 'recovery' (20580 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
Sending 'dsp' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
Sending 'oem' (104608 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.012s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.0
Sending 'system' (256553 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.1
Sending 'system' (256617 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.2
Sending 'system' (254213 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.3
Sending 'system' (256710 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.4
Sending 'system' (256912 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.5
Sending 'system' (257861 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.6
Sending 'system' (260027 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.7
Sending 'system' (257601 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.8
Sending 'system' (257805 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
Sending 'modem' (71921 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
Erasing 'modemst1' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
Erasing 'modemst2' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
Sending 'fsg' (3012 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
Erasing 'cache' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
Erasing 'userdata' FAILED (command write failed
(Unknown error))
Finished. Total time: 34.761s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase customize
Erasing 'customize' FAILED (command write failed
(Unknown error))
Finished. Total time: 14.723s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase clogo
Erasing 'clogo' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
FAILED (command write failed (Unknown error))
Finished. Total time: 5.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>
Occasionally I can get a different message
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) OKAY [ 0.325s]
Writing 'bootloader' (bootloader) Validating 'boot
loader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
FAILED (status read failed (Too many links))
Finished. Total time: 0.533s
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.005s]
Writing 'partition' (bootloader) Validating 'gpt.
default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.085s
But it always fails.

Drkmatr1984 said:
If all fastboot commands fail, including ,
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
and
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Occasionally I can get a different message
and
But it always fails.
Click to expand...
Click to collapse
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/

riyan65 said:
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
I am using the latest from lolinet, they do not have the latest (OPSS28.85-13-5) uploaded there yet. I did manage to find a copy here But I am at work on slow internet so it may take me all night to finish downloading it

At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.

[email protected] said:
At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.
Click to expand...
Click to collapse
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!

Drkmatr1984 said:
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!
Click to expand...
Click to collapse
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Code:
(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: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB 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: xxxxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 6C657D3F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 03-28-2017
(bootloader) sku: XT1687
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 23:25:13 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.85R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-ElementalX-G5-3.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 Mon Oct 1 22:31:26 EDT 2018
(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: retus
(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.010s
Is it because the secure boot is on?

You should edit your imei in your getvar output.
When you recovered from hard brick before, did you use Vache's for this device, or the albus blankflash for Addison?
I assume you are trying to get into recovery by using the volume button, but have you tried fastboot commands.
Code:
fastboot reboot recovery
sometimes works.
With a copy of TWRP in your adb/fastboot folder, try
Code:
fastboot boot image twrp.img
or
Code:
fastboot boot recovery twrp.img
where you have renamed your TWRP image to the twrp.img. This boots into twrp without installing, and has been reported to work with fubarred partition tables. If it boots, you then can access tools to repair gpt partition tables via adb.

Drkmatr1984 said:
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Is it because the secure boot is on?
Click to expand...
Click to collapse
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!

nicolap8 said:
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!
Click to expand...
Click to collapse
Ok, thanks! and done!
I will give these new suggestions a try later tonight. I did hear about booting into TWRP before, but have had little luck with that. However, I think I have only tried fastboot boot twrp.img and not with recovery or image as keywords in there...

OK, so the two fastboot commands are not the correct syntax.
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot image twrp.img
fastboot: error: cannot load 'image': No such file or directory
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot recovery twrp.img
fastboot: error: cannot load 'recovery': No such file or directory
Doing this:
Code:
$ fastboot boot boot.img recovery.img
fastboot: error: cannot boot a boot.img *and* ramdisk
Almost works lol
"fastboot reboot recovery" just gives this:
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Doing "fastboot boot twrp.img" works but it hangs at the "your device is not safe" screen and never actually loads. "fastboot getvar all" returns interesting things in the slot section. Those slots don't seem normal to me. Also, my ro.fingerprint looks like it's for nougat, but my bootloader is Oreo. I'm willing to break this phone to fix it if possible, so if anyone has any riskier suggestions for me to try I'm down as I've already gone 4 days without a phone and am about to buy a new one either way.

Drkmatr1984 said:
OK, so the two fastboot commands are not the correct syntax.
Click to expand...
Click to collapse
If you are not able to get the fastboot help you have not to try to flash anything!

nicolap8 said:
If you are not able to get the fastboot help you have not to try to flash anything!
Click to expand...
Click to collapse
What? I don't understand you.
I am reading this
And am trying to understand the fastboot boot command better. It requires a kernel image and a ramdisk image. So far I have tried by using zImage from ElementalX kernel as kernel and twrp.img as Ramdisk but the boot just hangs for a long time. Does anyone know the Correct command to boot into TWRP(and kernel) from USB on this device? (Confirmed working and tested, please!)
Here are all of my attempts so far:
Code:
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26769408 bytes
Downloading 'boot.img' OKAY [ 0.563s]
booting OKAY [ 0.080s]
Finished. Total time: 0.860s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26611712 bytes
Downloading 'boot.img' OKAY [ 0.554s]
booting OKAY [ 0.073s]
Finished. Total time: 0.667s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot linux-2.6/arch/arm/boot/zImage twrp.img
fastboot: error: cannot load 'linux-2.6/arch/arm/boot/zImage': No such file or directory
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot Ele
ElementalX-G5-3.00.zip elex.zImage
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot ElementalX-G5-3.00.zip twrp.img
creating boot image...
creating boot image - 29065216 bytes
Downloading 'boot.img' OKAY [ 0.606s]
booting OKAY [ 0.081s]
Finished. Total time: 0.764s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage twrp.img
creating boot image...
creating boot image - 23590912 bytes
Downloading 'boot.img' OKAY [ 0.496s]
booting OKAY [ 0.109s]
Finished. Total time: 0.642s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage
creating boot image...
creating boot image - 6883328 bytes
Downloading 'boot.img' OKAY [ 0.154s]
booting OKAY [ 0.079s]
Finished. Total time: 0.245s

Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?

Drkmatr1984 said:
Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?
Click to expand...
Click to collapse
fastboot boot twrp.img

craigl14 said:
fastboot boot twrp.img
Click to expand...
Click to collapse
That only works when you have a boot partition that is intact.
Since my partition tables are ****ed it just hangs at boot when I run that command. I need the full command with kernel option to make it boot so that I can edit the partitions from TWRP. However, I don't know enough about the kernel of this phone, or where to obtain its sources, or how to compile them, or any of that to make it work. I'm hoping one of the ROM devs will clue me in as I can't be the only person with this phone to ever Fubar their partition tables.
I found this :
Code:
To boot with a host-side kernel image (and rootfs image)
This command allows you to download a kernel image (and optional root filesystem image) and boot the phone with those, instead of using the kernel and rootfs in the boot flash partition. It is very useful while developing a kernel or modifying the rootfs.
fastboot boot <kernel> [ <ramdisk> ]
Ex: fastboot boot linux-2.6/arch/arm/boot/zImage root-image/recovery.img-ramdisk.cpio.gz
Which seems to suggest it's possible but I just need the correct kernel and rootfs image to boot TWRP.

Moto G5 Plus unaltered went into boot loop, result; imei 0, "failed to validate",

Moto G5 Plus unaltered went into boot loop, result; imei 0, "failed to validate",
Hi all,
I stumbled on this forum while trying to figure out a way to rescue my husband's Moto G5 Plus. Yesterday it went into a constant loop of restarts, at best functioning for 5 minutes before suddenly restarting for seemingly no reason.
He is not technically proficient enough to do any error seeking, let alone booting or flashing a new rom, so for all intents and purposes the phone is unaltered except doing the standard android updates, adding common apps and so on.
Well, the phone eventually ended up in fastboot flash mode where it keeps giving the error: faild to pass validaton, backup to fastboot. I found the menu option for barcodes and both imei and SKU are set to 000000000000 or how every many 0's. Date is set to 01-01-1970, but serial number is intact.
We tried installing Software Repair Assistant, but it keeps going on "Processing device information" for hours with no result.
Also tried installing the Lenovo Moto Smart Assistant for the Rescue mode, but it gives me "Failed to match the connected device".
Ideally we would like to find a way to bring back the contents of the phone if at all possible. I found a thread regarding imei 0 issue but I couldn't see if that would also wipe all contents so I am hesitant to try that without further research.
Being a slightly paranoid lawyer, my husband doesn't believe in backing up his stuff to cloud based solutions, so all his photos of the kids (and more) are per now toast. He has a new phone (and a slightly more modern approach to cloud backups) so there is no rush to fix NOW, but we'd like to know if there's any point in trying to restore or if we should go ahead with hacks to render it wiped but usable.
Does anyone here know of a good way to resolve this issue?

MrsMotz said:
Hi all,
I stumbled on this forum while trying to figure out a way to rescue my husband's Moto G5 Plus. Yesterday it went into a constant loop of restarts, at best functioning for 5 minutes before suddenly restarting for seemingly no reason.
He is not technically proficient enough to do any error seeking, let alone booting or flashing a new rom, so for all intents and purposes the phone is unaltered except doing the standard android updates, adding common apps and so on.
Well, the phone eventually ended up in fastboot flash mode where it keeps giving the error: faild to pass validaton, backup to fastboot. I found the menu option for barcodes and both imei and SKU are set to 000000000000 or how every many 0's. Date is set to 01-01-1970, but serial number is intact.
We tried installing Software Repair Assistant, but it keeps going on "Processing device information" for hours with no result.
Also tried installing the Lenovo Moto Smart Assistant for the Rescue mode, but it gives me "Failed to match the connected device".
Ideally we would like to find a way to bring back the contents of the phone if at all possible. I found a thread regarding imei 0 issue but I couldn't see if that would also wipe all contents so I am hesitant to try that without further research.
Being a slightly paranoid lawyer, my husband doesn't believe in backing up his stuff to cloud based solutions, so all his photos of the kids (and more) are per now toast. He has a new phone (and a slightly more modern approach to cloud backups) so there is no rush to fix NOW, but we'd like to know if there's any point in trying to restore or if we should go ahead with hacks to render it wiped but usable.
Does anyone here know of a good way to resolve this issue?
Click to expand...
Click to collapse
Is your device is rooted??? Or it on completely on stock ROM???
And what the last thing you do which cause this problem.

riyan65 said:
Is your device is rooted??? Or it on completely on stock ROM???
And what the last thing you do which cause this problem.
Click to expand...
Click to collapse
It's not rooted, completely stock except following the recommended updates.
As far as I know, he did not do anything except charging the phone at night, and in the morning it had restarted, then kept restarting all day until ending in fastboot with "failed validaton".

MrsMotz said:
It's not rooted, completely stock except following the recommended updates.
As far as I know, he did not do anything except charging the phone at night, and in the morning it had restarted, then kept restarting all day until ending in fastboot with "failed validaton".
Click to expand...
Click to collapse
Then it quite hard to recover data, but not least. You can try flashing the device from this procedure.
Here is the procedure:-
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_8.1.0_OPSS28.85-17-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Now your device will boot, if not try holding power button for 10sec then it reboot it self. If it won't boot then flash the device again with the following command
[Note:- this will erase all user data]
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
This will boot you device for sure.

riyan65 said:
Then it quite hard to recover data, but not least. You can try flashing the device from this procedure.
...
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Now your device will boot, if not try holding power button for 10sec then it reboot it self. If it won't boot then flash the device again with the following command
[Note:- this will erase all user data]
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
This will boot you device for sure.
Click to expand...
Click to collapse
OK, I tried the first bunch of commands. This is the result I got:
C:\ADB>fastboot devices
6be2e0bf fastboot
C:\ADB>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.013s
C:\ADB>
C:\ADB>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.084s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.107s
C:\ADB>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.603s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.807s
C:\ADB>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.738s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.981s
C:\ADB>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.584s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 0.606s
C:\ADB>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 3.643s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.714s
C:\ADB>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 8.946s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.017s
C:\ADB>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (256514 KB)...
OKAY [ 8.872s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.896s
C:\ADB>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (246302 KB)...
OKAY [ 8.489s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.530s
C:\ADB>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 9.057s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.149s
C:\ADB>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 9.063s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.092s
C:\ADB>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 9.070s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.096s
C:\ADB>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (250531 KB)...
OKAY [ 8.684s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.725s
C:\ADB>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (262059 KB)...
OKAY [ 9.034s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.073s
C:\ADB>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (254142 KB)...
OKAY [ 8.763s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.796s
C:\ADB>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71921 KB)...
OKAY [ 2.495s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 2.522s
C:\ADB>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.019s
C:\ADB>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.034s
C:\ADB>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.126s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.146s
C:\ADB>fastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.034s
C:\ADB>
C:\ADB>fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.018s
C:\ADB>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.021s
C:\ADB>fastboot reboot

MrsMotz said:
OK, I tried the first bunch of commands.
Click to expand...
Click to collapse
Chances are the gpt got corrupted as well..
Try
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Everything will be wiped. Also make sure you downloaded the latest firmware. 17-6-2 is the latest.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Same issue, same results!
My Moto G5 Plus XT1687 experienced the same type of failure just over a month ago. First, it began randomly rebooting (never a good sign...), then my entire sms history disappeared (every sms AFTER that moment, however, behaved normally: received and listed/logged as new messages)... Then, about two days later, I woke up to a bricked phone. My phone was never rooted. Around the time of the random reboots, I had allowed my phone to update apps (I can't remember which happened first -- random reboots or app updates. I do know that I chose to update apps at that time because the phone was laggy and not behaving [even though there was ample unused storage available, and no apps stood out as memory hogs, etc.]). (Developer mode was enabled, but probably not USB debugging.)
On the barcode screen, my phone displays an IMEI of all zeros, a SKU of all zeros, and a date of 01-01-1970 (there is a serial number that may or may not be the original. It does not appear anywhere on the box label [where my actual IMEI and other numbers/codes are printed]).
I have tried flashing POTTER_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info (as well as a few older ones -- just to try) using variations* of the standard code, above (*with and without "flash partition gpt.bin" and "flash bootloader bootloader.img"...). I have not yet taken the leap of including "erase userdata", however, because I am worried about losing anything that might not have been backed up... (And if every single previous line of code has failed, will adding "erase userdata" toward the end make a difference...?)
Down the list, the results are identical to the ones posted here by MrsMotz: "FAILED (remote failure)", "failed to erase", "failed to validate", "failed to flash", "invalid signed image", etc. (I've also tried using the Lenovo Moto Smart Assistant Flash/Rescue tool [which I imagine is supposed to perform essentially the same function as flashing ROM manually] to no avail ["Failed to match connected device"]!)
I can't afford a new phone! I desperately need to make this one work again. What am I missing? Why did my phone self-brick, and how can I fix it?

Same issue, same results! Update
On the barcode screen, my phone displays an IMEI of all zeros, a SKU of all zeros, and a date of 01-01-1970 (there is a serial number that may or may not be the original. It does not appear anywhere on the box label [where my actual IMEI and other numbers/codes are printed]).
Click to expand...
Click to collapse
So, the "serial number" currently showing on my phone is not the real/actual/original serial number. My real serial number went the way of my real IMEA, I guess! Is this normal when a phone is bricked? Also, might the loss of my phone's genuine identifiers be contributing to the inability be "validated" or "recognized"...?

mahuba3 said:
So, the "serial number" currently showing on my phone is not the real/actual/original serial number. My real serial number went the way of my real IMEA, I guess! Is this normal when a phone is bricked? Also, might the loss of my phone's genuine identifiers be contributing to the inability be "validated" or "recognized"...?
Click to expand...
Click to collapse
Seems to be a hardware issue. No IMEI, no serial, date reset to 1970...
Also the random reboots and the other things happening before are pointing to that direction.
So you're still able to reach fastboot mode and flash stock firmwares. When you say you were never rooted I suspect your bootloader is still locked?
If so I'm out of ideas, there isn't much you can do with an bootloader locked device.
I'm pretty sure that your hardware is the problem, so service center (depending on the country you live in) or buying a new device seem to be the only ways to go.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
Seems to be a hardware issue. No IMEI, no serial, date reset to 1970...
Also the random reboots and the other things happening before are pointing to that direction.
So you're still able to reach fastboot mode and flash stock firmwares. When you say you were never rooted I suspect your bootloader is still locked?
If so I'm out of ideas, there isn't much you can do with an bootloader locked device.
I'm pretty sure that your hardware is the problem, so service center (depending on the country you live in) or buying a new device seem to be the only ways to go.
Click to expand...
Click to collapse
Thank you ... But darn
Bootloader is locked (screen says "oem_locked"). But, yes, I am able to reach fastboot mode. And the bootloader logs come through each time I attempt to flash anything...
PS My phone, purchased new, is only two and a half years old (I usually hold onto them much longer!). But... I did drop it into the pool at the YMCA several months ago... It had been "misbehaving" (background apps crashing) prior, but after four days in rice and silica packets, it came out working just as well as before...

@mahuba3: Any luck bro? I am also having the same issue, if you have fixed your phone, share me the details please.
mahuba3 said:
Thank you ... But darn
Bootloader is locked (screen says "oem_locked"). But, yes, I am able to reach fastboot mode. And the bootloader logs come through each time I attempt to flash anything...
PS My phone, purchased new, is only two and a half years old (I usually hold onto them much longer!). But... I did drop it into the pool at the YMCA several months ago... It had been "misbehaving" (background apps crashing) prior, but after four days in rice and silica packets, it came out working just as well as before...
Click to expand...
Click to collapse

Moto g5 plus
Any solution
I have the same problem

I'm having a very similar issue, but I can't login to bootloader screen. It just starts on a screen saying "start up failed" and when I try to run the commands you say it responds with an error
> fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.016s
> fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.016s

SAme problem here too, Just two days ago, woke up to this bricked phone.

hello there im facing the same issue i would like to recover my files from the phone. i dont care if i could use the phone further pls reply.

same problem here! i'm on a linux pc

Help needed! (newbie here)
I have a moto g5 plus (potter) and it is locked on this screen. I already tried to use the motorola recovery program but he doesn't recognize it because imei appears 0000000. I need help to bring it back to life (my computer is linux) and if possible to install the factory rom on it.
{
"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"
}

Facing the same issue, can anyone help?

NO COMMAND when booting system. TWRP has no storage, cache, etc.

Hello I've messed up and didn't flash with fastboot correctly. I try to flash a stock oreo rom via fastboot with the commands at the end of the post and it boots "NO COMMAND". Then I flashed TWRP to flash a zip with it and phone has no STORAGE or memory or anything, so it keeps failing.
Is there any way via fastboot or anything to fresh start?
fastboot getvar max-sparse-size
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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse

The last version of software for the G5 plus (potter:8.1.0/OPS28 .85-17-6-2) only shows 8 sparsechunk.x files - your batch file shows 10 sparsechunks - did you flash the proper firmware for your unit ?
Whats the model number of the phone and the file name of the firmware you used ?

I downloaded two OREO roms and tried both. Followed this post https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 but maybe I messed up when choosing the rom: selected one first, and after it failed, did a -w in fastboot and tried the next one. My phone is a g5 potter
This is the other ROM I tried: https://qc5.androidfilehost.com/dl/...er-twrp-flashable-OPSS28.85-17-6-2-aroma.zip?

https://mirrors.lolinet.com/firmware/moto/potter/official/
potter Moto G5 Plus firmware last update August 2019
XT1680(LATAM/Argentina/Chile,2GB)
XT1681(LATAM/Colombia/Mexico,2GB)
XT1683(Brazil,DS,DTV,2GB)
XT1684(Europe,3GB)
XT1685(Australia/Europe/NewZealand,3GB)
XT1686(India,3/4GB)
XT1687(USA,2GB/4GB)
==========
AMXBR
XT1683_POTTER_AMXBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
AMXCL
XT1680_POTTER_AMXLA_8.1.0_OPSS28.85-13-3_cid50_subsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
==========
AMXCO
XT1680_POTTER_AMXLA_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
AMXLA
XT1680_POTTER_AMXLA_8.1.0_OPS28.85-17-6-2_cid50_subsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
==========
AMXMX
XT1680_POTTER_AMX_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
AMXPE
XT1680_POTTER_AMXLA_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
AMZ
XT1687_POTTER_AMZ_8.1.0_OPSS28.85-17-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
ATTMX
XT1680_POTTER_ATTMX_8.1.0_OPS28.85-17-6-2_cid50_subsidy-IUSMXLA_regulatory-DEFAULT_CFC.xml.zip
==========
CC
XT1687_POTTER_CCAWS_8.1.0_OPSS28.85-17-6_cid50_subsidy-CCAWS_regulatory-DEFAULT_CFC.xml.zip
==========
LRA
XT1687_LRA_8.1.0_OPSS28.85-13-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETAIL
POTTER_RETAIL_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETAPAC
XT1684_POTTER_RETEU_SS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1685_POTTER_RETEU_DS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETAR
XT1680_POTTER_RETAR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETBR
XT1683_POTTER_RETBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETEU
XT1684_POTTER_RETEU_SS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1685_POTTER_RETEU_DS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETGB
XT1684_POTTER_RETEU_SS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1685_POTTER_RETEU_DS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETIN
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETLA
XT1681_POTTER_RETLA_DS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETLA1ST
XT1680_POTTER_RETLA1ST_8.1.0_OPSS28.85-13-5_cid50_subsidy-LATAM_SELFPERSO_regulatory-DEFAULT_CFC.xml.zip
==========
RETMX
XT1681_POTTER_RETMX_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
RETUS
XT1687_POTTER_RETUS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TEFBR
XT1683_POTTER_RETBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TEFCO
XT1683_POTTER_RETBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TEFES
XT1685_POTTER_TEFES_8.1.0_OPSS28.85-17-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TEFMX
XT1681_POTTER_TEFMX_8.1.0_OPS28.85-17-6-2_cid50_subsidy-MOVSTLA_regulatory-DEFAULT_CFC.xml.zip
==========
TIGCO
XT1681_POTTER_TEFCO_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
TIMBR
XT1683_POTTER_RETBR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
==========
---------- Post added at 05:07 AM ---------- Previous post was at 04:45 AM ----------
your fastboot commands for OPS28.85-17-6-2 should have been;
Fastboot flash partition gpt.bin
Fastboot flash bootloader bootloader.img
Fastboot flash modem NON-HLOS.bin
Fastboot flash fsg fsg.mbn
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 reboot
if you have a backup of your EFS and PERSIST:
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
whats the model of the phone and the country your in ?

Its the 2gb model. I live in Argentina. I didn't back up EFS or PERSIST sadly

I'm not an expert on the firmware, but I know which US versions to use. I believe that your phone is the XT1680, and the firmware would be XT1680_POTTER_RETAR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip under the RETAR directory at https://mirrors.lolinet.com/firmware/moto/potter/official/
In my past experience, no command was missing the recovery program TWRP. I would just fastboot it again, onto my phone, and then go back to recovery, and TWRP would be there.
It sounds like in your case the partitions may be missing, and TWRP would not see anything.
I try would fastboot the firmware listed at the lolinet mirror (use the batch file listed above that does not erase the modems and EFS/Persist) and see if it comes back. I would first delete the ADB folder and all software in it, it appears you may have had the wrong firmware. Put a new copy of the ADB software, a new copy of the extracted firmware from the mirror. See if it comes back,
If it does not work and fastboot appears to work, sounds like you would have to recover or recreate linux partitions on the phone. If there is no response from the phone, its probably bricked.
Hope that helps and thats all I can suggest.

Nivead said:
I'm not an expert on the firmware, but I know which US versions to use. I believe that your phone is the XT1680, and the firmware would be XT1680_POTTER_RETAR_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip under the RETAR directory at https://mirrors.lolinet.com/firmware/moto/potter/official/
In my past experience, no command was missing the recovery program TWRP. I would just fastboot it again, onto my phone, and then go back to recovery, and TWRP would be there.
It sounds like in your case the partitions may be missing, and TWRP would not see anything.
I try would fastboot the firmware listed at the lolinet mirror (use the batch file listed above that does not erase the modems and EFS/Persist) and see if it comes back. I would first delete the ADB folder and all software in it, it appears you may have had the wrong firmware. Put a new copy of the ADB software, a new copy of the extracted firmware from the mirror. See if it comes back,
If it does not work and fastboot appears to work, sounds like you would have to recover or recreate linux partitions on the phone. If there is no response from the phone, its probably bricked.
Hope that helps and thats all I can suggest.
Click to expand...
Click to collapse
Thank you for your help. Sadly, it doesnt work - it still says No Command. I'll quote the CMD Log down here, if anyone finds it informative.
If anyone can point me about recreating linux partitions on the android, I'd be glad. I have no idea what that is, although I'm going to look for it right now.
Bumping this post to see if anyone has an idea. Thank you Nivead.
C:\Users\Fresco\Desktop\asd>Fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.077s]
Finished. Total time: 0.257s
C:\Users\Fresco\Desktop\asd>Fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.284s]
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.548s]
Finished. Total time: 0.861s
C:\Users\Fresco\Desktop\asd>Fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (71921 KB) OKAY [ 1.737s]
Writing 'modem' OKAY [ 1.109s]
Finished. Total time: 2.892s
C:\Users\Fresco\Desktop\asd>Fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (3012 KB) OKAY [ 0.234s]
Writing 'fsg' OKAY [ 0.119s]
Finished. Total time: 0.363s
C:\Users\Fresco\Desktop\asd>Fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.525s]
Writing 'dsp' OKAY [ 0.298s]
Finished. Total time: 0.835s
C:\Users\Fresco\Desktop\asd>Fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2186 KB) OKAY [ 0.216s]
Writing 'logo' OKAY [ 0.102s]
Finished. Total time: 0.330s
C:\Users\Fresco\Desktop\asd>Fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.549s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.376s]
Finished. Total time: 0.935s
C:\Users\Fresco\Desktop\asd>Fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.628s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.481s]
Finished. Total time: 1.124s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (258396 KB) OKAY [ 5.877s]
Writing 'system' OKAY [ 3.773s]
Finished. Total time: 9.797s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256514 KB) OKAY [ 5.857s]
Writing 'system' OKAY [ 3.344s]
Finished. Total time: 9.337s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (246302 KB) OKAY [ 5.557s]
Writing 'system' OKAY [ 3.662s]
Finished. Total time: 9.355s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 5.863s]
Writing 'system' OKAY [ 3.378s]
Finished. Total time: 9.384s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 5.862s]
Writing 'system' OKAY [ 3.482s]
Finished. Total time: 9.481s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 5.928s]
Writing 'system' OKAY [ 3.369s]
Finished. Total time: 9.433s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (250531 KB) OKAY [ 5.631s]
Writing 'system' OKAY [ 3.717s]
Finished. Total time: 9.484s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (262059 KB) OKAY [ 5.870s]
Writing 'system' OKAY [ 3.786s]
Finished. Total time: 9.799s
C:\Users\Fresco\Desktop\asd>Fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (254142 KB) OKAY [ 5.677s]
Writing 'system' OKAY [ 3.338s]
Finished. Total time: 9.163s
C:\Users\Fresco\Desktop\asd>Fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (104608 KB) OKAY [ 2.437s]
Writing 'oem' OKAY [ 1.391s]
Finished. Total time: 3.892s
C:\Users\Fresco\Desktop\asd>Fastboot erase cache
Erasing 'cache' OKAY [ 0.012s]
Finished. Total time: 0.014s
C:\Users\Fresco\Desktop\asd>Fastboot erase userdata
Erasing 'userdata' OKAY [ 0.175s]
Finished. Total time: 0.177s
C:\Users\Fresco\Desktop\asd>Fastboot erase DDR
Erasing 'DDR' OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\Users\Fresco\Desktop\asd>Fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
Click to expand...
Click to collapse

bump

crata said:
I downloaded two OREO roms and tried both. Followed this post https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 but maybe I messed up when choosing the rom: selected one first, and after it failed, did a -w in fastboot and tried the next one. My phone is a g5 potter
This is the other ROM I tried: https://qc5.androidfilehost.com/dl/...er-twrp-flashable-OPSS28.85-17-6-2-aroma.zip?
Click to expand...
Click to collapse
The second ROM seems to be (by name) a TWRP flashable which means it's not possible to flash it by fastboot, only by TWRP.
Maybe that should be the way to go for you. If you can't flash any fastboot firmware maybe try a TWRP flashable.
Versions and tutorials are here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482

Wolfcity said:
The second ROM seems to be (by name) a TWRP flashable which means it's not possible to flash it by fastboot, only by TWRP.
Maybe that should be the way to go for you. If you can't flash any fastboot firmware maybe try a TWRP flashable.
Versions and tutorials are here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Click to expand...
Click to collapse
Thanks for the effort but I can't flash via TWRP because it doesn't recognize any storage