Database Users

xt1575 invalid cid status 0x69 flash failed

i have one xt1575 moto x pure in bricked state fastboot doesn't except any command
following error on fastboot
start up failed
your device didn't start up successfully
use the software repair assistant on computer to repair your device.
connect your device to your computer to get software repair assistant
here is the getvar all info
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.1C(*)
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: b3deb886
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: 295D7A001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(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) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.1C-0-ge29f91e
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.047s
Click to expand...
Click to collapse
can anyone help with this issue bootloader was locked and get_unlock_data command also not success
mfastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.005s
Click to expand...
Click to collapse
mfastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
E:\motorola\X_Pure_XT1575_CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml>mfastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.003s
E:\motorola\X_Pure_XT1575_CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (40960 KB)...
OKAY [ 1.434s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.452s
E:\motorola\X_Pure_XT1575_CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash bootlaoder bootloader.img
target max-sparse-size: 256MB
sending 'bootlaoder' (2699 KB)...
OKAY [ 0.135s]
writing 'bootlaoder'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.190s
E:\motorola\X_Pure_XT1575_CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash modem non-hlos.bin
target max-sparse-size: 256MB
sending 'modem' (41675 KB)...
OKAY [ 1.369s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.383s
Click to expand...
Click to collapse
device start up failed

What Android version did you have before the trouble occurred? It looks like you are trying to downgrade, which isn't possible with a locked bootloader. When your bootloader is locked you must flash the same or newer Android version, all others will fail.

Thanks For Your Reply.
I returned this phone to customer but I receive one more moto x pure xt1575 with imei 0 issue i tried all modem but still imei 0
I also erased the modemst1 and modemst2 and then flash the correct fsg then still imei 0. In this phone bootloader status is engineering. How to solve this issue?

Shabby The Dev said:
Thanks For Your Reply.
I returned this phone to customer but I receive one more moto x pure xt1575 with imei 0 issue i tried all modem but still imei 0
I also erased the modemst1 and modemst2 and then flash the correct fsg then still imei 0. In this phone bootloader status is engineering. How to solve this issue?
Click to expand...
Click to collapse
Any phone with bootloader status "Engineering" should be returned to Motorola... It is not in a fully unlocked state and it is not intended for normal use (and no, it is not some "special" unlock above a regular bootloader unlock as some people say)
https://forums.lenovo.com/t5/MOTORO...g-and-Unlocked-bootloader-status/td-p/3420219

Stuck in fastboot, unable to flash stock firmware

Recently acquired a bricked moto x pure. No way of knowing for sure how it was bricked but I'm guessing attempted downgrade. When starting up the Bootloader logs say:
AP fastboot flash mode (secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from charger boot mode
CID read failure
Invalid CID status 0x69
Click to expand...
Click to collapse
fastboot getvar all gives:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.48(*)
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=07 PRV=01 TYPE=57 PNM=AGND3R
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA084034CW
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x8d
(bootloader) uid: 3862CC001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 10-07-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Mar 9 14:23:32 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.3.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g6898f68 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Sat Jan 30 14:35:02 CST 2016
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.48-0-g8c942c6
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.422s
Click to expand...
Click to collapse
I attempted to flash the CLARK_RETUS_6.0_MPHS24.49-18-3_cid9_subsidy-DEFAULT_CFC.xml stock firmware but got the following error:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.094s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.953s
Click to expand...
Click to collapse
I also tried using mfastboot, with the same results. Anybody know how to fix this?

Is your bootloader locked?

thebaconbox said:
Is your bootloader locked?
Click to expand...
Click to collapse
Yes it is. Tried to unlock it already but I get:
>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse

Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...

acejavelin said:
Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...
Click to expand...
Click to collapse
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.961s
>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.141s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.234s
Click to expand...
Click to collapse
I get the same errors if I try to flash anything.

jml1290 said:
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
I get the same errors if I try to flash anything.
Click to expand...
Click to collapse
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.

acejavelin said:
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.
Click to expand...
Click to collapse
Here's what I get:
>fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.000s
>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.000s
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.561s
Click to expand...
Click to collapse

jml1290 said:
Here's what I get:
Click to expand...
Click to collapse
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.

acejavelin said:
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.
Click to expand...
Click to collapse
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!

jml1290 said:
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!
Click to expand...
Click to collapse
Sorry... But if the bootloader is locked you might be able to register it on your Motorola account and file a warranty claim, couldn't hurt to try.

[help] TWRP won't boot after flashing on US996

I've unlocked the bootloader using LG's directions. Then, I went through the following procedure:
Code:
adb reboot bootloader
The phone reboots, and mini-instructions show on the display
Code:
fastboot getvar all
Output:
< waiting for any device >
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4d000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xced000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x180000000
(bootloader) serialno:LGUS996acc21276
(bootloader) kernel:lk
(bootloader) product:MSM8996
(bootloader) unlocked:yes
all:
finished. total time: 0.210s
Then, I run this command:
Code:
fastboot flash recovery twrp-3.0.2-1-us996.img
It appears to succeed:
target reported max download size of 536870912 bytes
sending 'recovery' (24076 KB)...
OKAY [ 0.572s]
writing 'recovery'...
OKAY [ 0.256s]
finished. total time: 0.827s
(I've tried renaming the img file to twrp.img and recovery.img, and I've tried running the flash command several times while waiting 30 seconds in between)
Then, I pull the battery, replace the back cover (is that necessary? - I'm going to wear it out!), hold down vol-down and power, wait for lg logo, let go of power while still holding vol-down, wait about a second, hold power down until I see TWRP. However, the thing I see is not TWRP! It is the stock recovery that just says I can factory wipe (or not). Am I doing something wrong? Is there a way to flash the recovery from adb using dd or something?

bshafer said:
I've unlocked the bootloader using LG's directions. Then, I went through the following procedure:
Code:
adb reboot bootloader
The phone reboots, and mini-instructions show on the display
Code:
fastboot getvar all
Output:
< waiting for any device >
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4d000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xced000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x180000000
(bootloader) serialno:LGUS996acc21276
(bootloader) kernel:lk
(bootloader) product:MSM8996
(bootloader) unlocked:yes
all:
finished. total time: 0.210s
Then, I run this command:
Code:
fastboot flash recovery twrp-3.0.2-1-us996.img
It appears to succeed:
target reported max download size of 536870912 bytes
sending 'recovery' (24076 KB)...
OKAY [ 0.572s]
writing 'recovery'...
OKAY [ 0.256s]
finished. total time: 0.827s
(I've tried renaming the img file to twrp.img and recovery.img, and I've tried running the flash command several times while waiting 30 seconds in between)
Then, I pull the battery, replace the back cover (is that necessary? - I'm going to wear it out!), hold down vol-down and power, wait for lg logo, let go of power while still holding vol-down, wait about a second, hold power down until I see TWRP. However, the thing I see is not TWRP! It is the stock recovery that just says I can factory wipe (or not). Am I doing something wrong? Is there a way to flash the recovery from adb using dd or something?
Click to expand...
Click to collapse
I had this exact same problem, along with many other users. Follow the advice here

If its a white screen that asks yes or exit say yes twice and itll take you to twrp

Need help my Moto g5plus hard brick dead solution

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

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

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

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

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

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

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

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

Softbricked XT1687, doesn't flash

Hi team,
I need help. I have a Moto G5 Plus (XT1687). A few weeks ago, it kept rebooting. Went to shut it down. Never rebooted again... After investigation, I understood it was hard bricked. I then followed some guide and managed to get it softbricked. Now, I don't actually remember which blank flash I used, but I have the feeling I used the wrong one (possibly for model XT1686), because I just can't flash anything else now (like Potter).
I don't need or want to root the phone, I just want to go back to the stock OS. I am not actually quite sure if I had Potter v.7 or 8 (or another version?).
I am far from an expert, so I am just trying to follow guides, but I don't really know what I am doing.
Anyway... I tried again to follow this guide https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396 but I don't actually go far.
Let me explain what I see...
When booting the phone, I get this screen:
https://drive.google.com/file/d/1dgwGtsSLh3VYOaD6PKJhJ2_Z5DpczY0k/view?usp=sharing
I then move to Recovery mode, and*this is what I see:
https://drive.google.com/file/d/18fPYBMkxU2N9P9zD6UB5ouKZ5w3AebQu/view?usp=sharing
In the Windows command prompt, when I type fasboot devices, I get the result
a58c134 fastboot
though nothing shows up on the phone. But I assume this is correct.
Then, when I start typing the first lines of code, I get errors in the command prompt:
https://drive.google.com/file/d/14t-amwAzANZjroGBgsnzOeE6pQgQCUdL/view?usp=sharing
Now, I do see there is some communication going on with the phone, as the phone displays something. This is what I get with the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
https://drive.google.com/file/d/1pujKmNB0zYrswztGXwJYNGNLPCeD0ZQe/view?usp=sharing
So... That's where I am. Don't really know if I managed to flash anything in the phone, but since I get all those issues, I guess that nothing is transferred. Please help!

Glencoe said:
Hi team,
I need help. I have a Moto G5 Plus (XT1687). A few weeks ago, it kept rebooting. Went to shut it down. Never rebooted again... After investigation, I understood it was hard bricked. I then followed some guide and managed to get it softbricked. Now, I don't actually remember which blank flash I used, but I have the feeling I used the wrong one (possibly for model XT1686), because I just can't flash anything else now (like Potter).
I don't need or want to root the phone, I just want to go back to the stock OS. I am not actually quite sure if I had Potter v.7 or 8 (or another version?).
I am far from an expert, so I am just trying to follow guides, but I don't really know what I am doing.
Anyway... I tried again to follow this guide https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396 but I don't actually go far.
Let me explain what I see...
When booting the phone, I get this screen:
https://drive.google.com/file/d/1dgwGtsSLh3VYOaD6PKJhJ2_Z5DpczY0k/view?usp=sharing
I then move to Recovery mode, and*this is what I see:
https://drive.google.com/file/d/18fPYBMkxU2N9P9zD6UB5ouKZ5w3AebQu/view?usp=sharing
In the Windows command prompt, when I type fasboot devices, I get the result
a58c134 fastboot
though nothing shows up on the phone. But I assume this is correct.
Then, when I start typing the first lines of code, I get errors in the command prompt:
https://drive.google.com/file/d/14t-amwAzANZjroGBgsnzOeE6pQgQCUdL/view?usp=sharing
Now, I do see there is some communication going on with the phone, as the phone displays something. This is what I get with the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
https://drive.google.com/file/d/1pujKmNB0zYrswztGXwJYNGNLPCeD0ZQe/view?usp=sharing
So... That's where I am. Don't really know if I managed to flash anything in the phone, but since I get all those issues, I guess that nothing is transferred. Please help!
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs

sd_shadow said:
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Click to expand...
Click to collapse
Thanks sd_shadow! So this is what I get:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(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) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.178s
What should I do know?

Glencoe said:
run
Thanks sd_shadow! So this is what I get:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(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) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.178s
What should I do know?
Click to expand...
Click to collapse
Don't suppose you know which software channel it was on?
Verizon, Retail, RetEU...
I would try LMSA'S Flash rescue
Unlikely that will work though.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If you are in the USA and not sure which software channel try RetUS
https://mirrors.lolinet.com/firmware/moto/potter/official
Maybe try mfastboot.exe
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs

sd_shadow said:
Don't suppose you know which software channel it was on?
Verizon, Retail, RetEU...
Click to expand...
Click to collapse
I am from Canada, and my carrier is Videotron, though we bougth the (unlocked) phone from Target, in the US, so I'd think the channel may be RetUS indeed.
sd_shadow said:
I would try LMSA'S Flash rescue
Unlikely that will work though.
Click to expand...
Click to collapse
I should have mentioned I had already tried it, and it didn't work indeed. Just checked again, and all it says is "Failed to match the connected device..."
sd_shadow said:
Maybe try mfastboot.exe
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
I followed your guide (my, I realise you are a guru on here!), and tried flashing with mfastboot (while sending each system.img chunck separately, as I have 8 system.img_sparsechunck.* files)... Looks like it failed again!
This is what I get from the Command prompt:
C:\adb\mfastboot-v2>mfastboot devices
a58c134 fastboot
C:\adb\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 2.055s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 2.076s
C:\adb\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (258396 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.388s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256514 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.399s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (246302 KB)...
OKAY [ 7.090s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.104s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.494s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.518s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.507s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.530s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.504s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.524s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (250531 KB)...
OKAY [ 7.203s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.232s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (262059 KB)...
OKAY [ 7.509s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.538s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (254142 KB)...
OKAY [ 7.289s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.318s
C:\adb\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.496s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.522s
C:\adb\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (20580 KB)...
OKAY [ 0.614s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.643s
C:\adb\mfastboot-v2>fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.038s
C:\adb\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.006s
C:\adb\mfastboot-v2>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(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) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.152s
I will try to uninstall all drivers and try again, just in case, but if you see anything else, let me know! I really appreciate your help!

Glencoe said:
I am from Canada, and my carrier is Videotron, though we bougth the (unlocked) phone from Target, in the US, so I'd think the channel may be RetUS indeed.
I should have mentioned I had already tried it, and it didn't work indeed. Just checked again, and all it says is "Failed to match the connected device..."
I followed your guide (my, I realise you are a guru on here!), and tried flashing with mfastboot (while sending each system.img chunck separately, as I have 8 system.img_sparsechunck.* files)... Looks like it failed again!
This is what I get from the Command prompt:
C:\adb\mfastboot-v2>mfastboot devices
a58c134 fastboot
C:\adb\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 2.055s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 2.076s
C:\adb\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (258396 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.388s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256514 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.399s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (246302 KB)...
OKAY [ 7.090s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.104s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.494s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.518s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.507s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.530s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.504s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.524s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (250531 KB)...
OKAY [ 7.203s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.232s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (262059 KB)...
OKAY [ 7.509s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.538s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (254142 KB)...
OKAY [ 7.289s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.318s
C:\adb\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.496s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.522s
C:\adb\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (20580 KB)...
OKAY [ 0.614s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.643s
C:\adb\mfastboot-v2>fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.038s
C:\adb\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.006s
C:\adb\mfastboot-v2>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(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) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.152s
I will try to uninstall all drivers and try again, just in case, but if you see anything else, let me know! I really appreciate your help!
Click to expand...
Click to collapse
Well I'm not hopeful.
You could try
Code:
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
Sent from my jerry_cheets using XDA Labs

sd_shadow said:
Well I'm not hopeful.
You could try
Code:
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
Click to expand...
Click to collapse
This is something I had already tried... Without luck!
C:\adb\mfastboot-v2>mfastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.006s
C:\adb\mfastboot-v2>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.137s
C:\adb\mfastboot-v2>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (5115 KB)...
OKAY [ 0.153s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.284s
C:\adb\mfastboot-v2>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (2186 KB)...
OKAY [ 0.084s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.102s
C:\adb\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.496s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.509s
Am I using the right firmware? I tried with the Potter RETUS 8.1.0...
Could it be that the bootloader is locked? If so, how do I unlock it?
Should I try to flash a blank file again? If so, how?
Or should I try to flash a bootable image on an SD card?
I am willing to try anything you can think of. This phone is already useless as is, so I have nothing to lose... I like challenges, but this one is very frustrating! But it is also a great learning experience!

Glencoe said:
T
Am I using the right firmware? I tried with the Potter RETUS 8.1.0...
Click to expand...
Click to collapse
I don't know, getvar isn't giving enough info to tell.
Do you remember where you found the blankflash?
Could you upload it somewhere? Drive, Mega, ...
Could it be that the bootloader is locked? If so, how do I unlock it?
Click to expand...
Click to collapse
bootloader is locked
Code:
(bootloader) securestate: oem_locked
Very unlikely you could unlock the bootloader as
OEM unlocking must be allowed in Dev options
which requires the phone to boot normally
but you could try
https://forum.xda-developers.com/general/rooting-roms/guide-locking-motorola-bootloader-t4079111
Should I try to flash a blank file again? If so, how?
Or should I try to flash a bootable image on an SD card?
Click to expand...
Click to collapse
Unfortunately, these are not options
The device needs to be in emergency download mode (edl)
There is no way to enter edl with a locked bootloader.
I am willing to try anything you can think of. This phone is already useless as is, so I have nothing to lose... I like challenges, but this one is very frustrating! But it is also a great learning experience!
Click to expand...
Click to collapse

sd_shadow said:
I don't know, getvar isn't giving enough info to tell.
Do you remember where you found the blankflash?
Could you upload it somewhere? Drive, Mega, ....
Click to expand...
Click to collapse
I don't actually remember where I got the blankflash, but I know I have 2 files, and I think I used the wrong one (XT1686)... Maybe that's the issue...
Those are the 2 files I have:
Don't remember, possibly XT1687: https://drive.google.com/file/d/1A5fpqO6tVSGJfQynwjlDex0LS4-yuMm9/view?usp=sharing
XT1686: https://drive.google.com/file/d/19pa9aR0j110Yk07wdwQ-AY-yHoH0nvw0/view?usp=sharing
Let me know what you think! If you have a better version, I am willing to try, if there is still a way to flash it...
sd_shadow said:
bootloader is locked
Code:
(bootloader) securestate: oem_locked
Click to expand...
Click to collapse
That's what I thought...
sd_shadow said:
Very unlikely you could unlock the bootloader as
OEM unlocking must be allowed in Dev options
which requires the phone to boot normally
but you could try
https://forum.xda-developers.com/general/rooting-roms/guide-locking-motorola-bootloader-t4079111
Click to expand...
Click to collapse
I'll give it a try!
sd_shadow said:
Unfortunately, these are not options
The device needs to be in emergency download mode (edl)
There is no way to enter edl with a locked bootloader.
Click to expand...
Click to collapse
In other words, there is no much hope to revive it...

Glencoe said:
I don't actually remember where I got the blankflash, but I know I have 2 files, and I think I used the wrong one (XT1686)... Maybe that's the issue...
Those are the 2 files I have:
Don't remember, possibly XT1687: https://drive.google.com/file/d/1A5fpqO6tVSGJfQynwjlDex0LS4-yuMm9/view?usp=sharing
XT1686: https://drive.google.com/file/d/19pa9aR0j110Yk07wdwQ-AY-yHoH0nvw0/view?usp=sharing
Let me know what you think! If you have a better version, I am willing to try, if there is still a way to flash it...
That's what I thought...
I'll give it a try!
In other words, there is no much hope to revive it...
Click to expand...
Click to collapse
I guess you could try RetIN I think it's the only XT1686 firmware
https://mirrors.lolinet.com/firmware/moto/potter/official/RETIN/

sd_shadow said:
I guess you could try RetIN I think it's the only XT1686 firmware
https://mirrors.lolinet.com/firmware/moto/potter/official/RETIN/
Click to expand...
Click to collapse
Really? Knowing my phone is XT1687? Or should I try it if I flashed the XT1686 blankflash?

Glencoe said:
Really? Knowing my phone is XT1687? Or should I try it if I flashed the XT1686 blankflash?
Click to expand...
Click to collapse
At this point I don't think it will hurt anything.
Sent from my ali using XDA Labs

sd_shadow said:
At this point I don't think it will hurt anything.
Click to expand...
Click to collapse
You're right! But I will try you other suggestion to unlock first and see how it goes (hopefully later today). Will let you know the outcome! Thanks for helping me! I really appreciate it!