Database Info

[Q] Bricked Moto G LTE XT1045 US

I have managed to brick my Moto G 4G LTE (XT1045 US) while trying to install a custom rom. The device can turn on only in fastboot mode.
I have followed a few tutorial here, here and here which are applicable for MotoG regular edition with no success.
Flashing the partition table for my original US 4.4.3 firmware doesn't work at all. Gives me a 'Preflash validation error'. So I tried the EU 4.4.4 firmware, and in this case the partition table flashes okay, but after that while flashing the boot.img gives the same error.
Code:
G:\Moto G 4g\RET-US-4.4.3>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.359s
Code:
G:\Moto G 4g\RET-EU-4.4.4>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
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) Flashing backup GPT image...
OKAY [ 0.391s]
finished. total time: 0.438s
G:\Moto G 4g\RET-EU-4.4.4>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.297s]
finished. total time: 1.406s
G:\Moto G 4g\RET-EU-4.4.4>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.109s]
finished. total time: 0.203s
G:\Moto G 4g\RET-EU-4.4.4>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.406s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.422s
I am also including the result log of 'getvar all' after flashing the 4.4.4 the partition table.
Code:
mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113(*)
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA95000QIY
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 5CEAAC0015000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 7:31:42 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_retus/peregrine
(bootloader) ro.build.fingerprint[1]: :4.4.3/KXB21.14-L1.23-4/1:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.23.4.peregrine_re
(bootloader) ro.build.version.full[1]: tus.retus.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gbdf1753-00001-g7a4
(bootloader) kernel.version[1]: 365d ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .7 (GCC) ) #1 SMP PREEMPT Fri May 23 16:
(bootloader) kernel.version[3]: 38:14 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.094s
With my limited understanding, it looks like it's stuck somewhere between 4.4.3 and 4.4.4.
Any help/suggestion will be highly appreciated...

Just a guess that "(bootloader) Preflash validation failed" means the bootloader is locked or what your flashing isn't valid so it won't flash it.

the bootloader was unlocked before... but whatever happened, got it locked again. thats part of my problem... i cannot unlock it anymore...

I received a bricked Nexus 5, trying to get it running

It was supposedly completely bricked.
Tried various ways to manage to get it running but failed. Now i am turning to you guys.
I can fastboot it.
I was able to test SDRAM and EMMC with BoardDiag and it looks to be okay
More details:
Code:
C:\adb>fastboot getvar all
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.26
(bootloader) version-bootloader: HHZ11n
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D821(H) 16GB
(bootloader) serialno:(redacted)
(bootloader) carrier: None
(bootloader) secure-boot: yes
(bootloader) unlocked: yes
(bootloader) product: hammerhead
(bootloader) partition-size:aboot: 80000
(bootloader) partition-type:aboot: emmc
(bootloader) partition-size:boot: 1600000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:recovery: 1600000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:system: 40000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 3321fa800
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 2bc00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:persist: 1000000
(bootloader) partition-type:persist: ext4
all:
finished. total time: 0.297s
When i try to flash stock via fastboot i get:
Code:
sending 'bootloader' (3119 KB)...
OKAY [ 0.874s]
writing 'bootloader'...
FAILED (remote: invalid bootloader image
)
finished. total time: 1.062s
rebooting into bootloader...
OKAY [ 0.110s]
finished. total time: 0.110s
< waiting for device >
sending 'radio' (45425 KB)...
OKAY [ 9.734s]
writing 'radio'...
OKAY [ 3.110s]
finished. total time: 12.844s
rebooting into bootloader...
OKAY [ 0.095s]
finished. total time: 0.109s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1046266608 bytes
error: update package missing system.img
Press any key to exit...
I cannot find much info on the Bootloader that is installed
Any advice?

In bootloader what version does it say?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
In bootloader what version does it say?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
it says version-bootloader: HHZ11n
can't find much info on that one

So have you downloaded the system files from Google and extracted em until you get all the individual img files?
Sent from my Nexus 5 using Tapatalk

Griz-Lee said:
it says version-bootloader: HHZ11n
can't find much info on that one
Click to expand...
Click to collapse
I'm looking at the factory images I have saved. I have a bootloader version hhz11k and then hhz12d from one L preview to the next. I don't have a hhz11n. I may have missed an image here or there, though.

Moto G3, (soft) bricked, locked bootloader

Hey guys,
Out of nowhere my Moto G3 (2015), 1GB turned of and was stuck in a bootloop.
It was running Marshmallow.
Only thing I could access was the bootloader, which was still locked.
A friend tried to flash the stock ROM to get it to work.
Problem was...it was the Lollipop ROM.
Now...no bootloop, just the bootloader and nothing else. Can't even access Recovery options.
I did a lot of research to save my Moto G and tried to flash it with the Marshmallow ROM, but nothing works.
(bootloader) Preflash validation failed, FAILED (remote failure) is what I get when running commands with Fastboot as soon as I get to "fastboot flash boot boot.img".
Please help...sending the phone to Motorola is unfortunately not an option for me

Try using mfastboot

xMotoDA said:
Try using mfastboot
Click to expand...
Click to collapse
I did...no luck.
(bootloader) Preflash validation failed
FAILED (remote failure)

Same problem here. The phone started bootlooping itself, and since I can't turn it on I can unlock the boot loader. Tried flashing stock to it (not knowing the bootloader was locked) and now it won't even boot up past fastboot. Really hoping someone has a solution to this.

Where does it fail, at gpt.bin or bootloader.bin, and what EXACT firmware file are you trying to use and which model (XT15xx)?

acejavelin said:
Where does it fail, at gpt.bin or bootloader.bin, and what EXACT firmware file are you trying to use and which model (XT15xx)?
Click to expand...
Click to collapse
Model: Moto G3 (XT1540, osprey retus)
Firmwares:
XT1540_OSPREY_RETCA-BELL_6.0_MPI24.65-33.1-2_cid14_subsidy-BELLCA_CFC.xml
XT1540_OSPREY_RETLA_NA_6.0_MPI24.65-33.1-2_cid12_subsidy-DEFAULT_CFC.xml
XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img <--- fails here

gridikoelie said:
Model: Moto G3 (XT1540, osprey retus)
Firmwares:
XT1540_OSPREY_RETCA-BELL_6.0_MPI24.65-33.1-2_cid14_subsidy-BELLCA_CFC.xml
XT1540_OSPREY_RETLA_NA_6.0_MPI24.65-33.1-2_cid12_subsidy-DEFAULT_CFC.xml
XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img <--- fails here
Click to expand...
Click to collapse
Try this...
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
(continue rest of image)
And you should really start recovery and factory reset first if possible before starting

acejavelin said:
Try this...
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
(continue rest of image)
And you should really start recovery and factory reset first if possible before starting
Click to expand...
Click to collapse
Thank you. Tried it...same result
I can't access recovery options. Just the bootloader.
Before I had this problem I had done a factory reset, so the developer options are not enabled.
Is there any way for me to get around that to flash the stock rom?
My friend messed up my bootloader by flashing an older rom (lollipop)

Please tell me this is fixable
mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.CC
(bootloader) product: osprey
(bootloader) board: osprey
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Samsung REV=07 PRV=01 TYPE=57
(bootloader) ram: 1024MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: ZY22228JJG
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 33FFFC0A00000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 355488060450556
(bootloader) meid:
(bootloader) date: 07-01-2015
(bootloader) sku: XT1540
(bootloader) battid: SNN5965A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jul 2 13:34:33 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/osprey_retus/osprey_umts:
(bootloader) ro.build.fingerprint[1]: 6.0/MPI24.65-25/28:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.24.11.25.osprey_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband: <not available>
(bootloader) kernel.version[0]: Linux version 3.10.49-g88eb8b3 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld34) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Tue Dec 8 05:39:16 CST 2015
(bootloader) sbl1.git: git=MBM-NG-V80.CC-0-g7abea31
(bootloader) rpm.git: git=MBM-NG-V80.CC-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.CC-0-ga1c5ae6
(bootloader) hyp.git: git=MBM-NG-V80.CC-0-ga1c5ae6
(bootloader) aboot.git: git=MBM-NG-V80.CC-0-gdfaac1d
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-typeDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-typeem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:customize: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-sizeDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-sizeadA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-sizeadB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000300000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-sizeersist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001019000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-sizeadC: 0x000000000087e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-sizeem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:system: 0x0000000091000000
(bootloader) partition-size:userdata: 0x0000000121fe0000
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.331s

Yeah, I think I see the problem... the versions look messed up, partially US Retail and part Latin America, could be the cause (flashing an incorrect version is known to brick), the hardware thinks it's the US Retail version so try the newest image for that and since you can't start recovery execute the erase commands first.
fastboot erase userdata
fastboot erase cache
Problem now is its a mixed bag of 2 firmwares, might not be recoverable with a locked bootloader.

acejavelin said:
Yeah, I think I see the problem... the versions look messed up, partially US Retail and part Latin America, could be the cause (flashing an incorrect version is known to brick), the hardware thinks it's the US Retail version so try the newest image for that and since you can't start recovery execute the erase commands first.
fastboot erase userdata
fastboot erase cache
Problem now is its a mixed bag of 2 firmwares, might not be recoverable with a locked bootloader.
Click to expand...
Click to collapse
Damn...didn't work.
Fails at "fastboot flash partition gpt.bin" with the US Retail version
These are my command results:
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot oem fb_mode_set
...
OKAY [ 0.112s]
finished. total time: 0.112s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.408s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2546 KB)...
OKAY [ 0.088s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.838s]
finished. total time: 1.930s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1352 KB)...
OKAY [ 0.048s]
writing 'logo'...
OKAY [ 0.081s]
finished. total time: 0.137s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.519s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.049s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16484 KB)...
OKAY [ 0.521s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (260721 KB)...
OKAY [ 8.240s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.689s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (261542 KB)...
OKAY [ 8.267s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.317s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.300s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.364s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (246551 KB)...
OKAY [ 7.790s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.861s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [ 8.285s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.329s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 8.269s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.309s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (117920 KB)...
OKAY [ 3.731s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.766s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.7': No error
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.8': No error
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (36984 KB)...
OKAY [ 1.188s]
writing 'modem'...
OKAY [ 0.993s]
finished. total time: 2.189s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (2159 KB)...
OKAY [ 0.072s]
writing 'fsg'...
OKAY [ 0.084s]
finished. total time: 0.157s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase clogo
erasing 'clogo'...
OKAY [ 0.032s]
finished. total time: 0.032s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot oem fb_mode_clear
...
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot reboot
rebooting...
finished. total time: 0.008s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash fsg fsg.mbn
< waiting for device >
target max-sparse-size: 256MB
sending 'fsg' (2159 KB)...
OKAY [ 0.154s]
writing 'fsg'...
OKAY [ 0.382s]
finished. total time: 0.540s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.017s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.087s]
finished. total time: 0.090s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot erase clogo
erasing 'clogo'...
OKAY [ 0.078s]
finished. total time: 0.081s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.004s
C:\Users\User\Downloads\SOFTWARE\Other\OS'S\Moto G3 (XT1540, osprey retus)\XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml>mfastboot reboot
rebooting...
finished. total time: 0.008s
Can this be a driver issue? My Windows 10 laptop sees my device as "Mot Composite ADB Interface" and get Connected USB not recognized when rebooting bootloader

gridikoelie said:
Damn...didn't work.
Fails at "fastboot flash partition gpt.bin" with the US Retail version
Can this be a driver issue? My Windows 10 laptop sees my device as "Mot Composite ADB Interface" and get Connected USB not recognized when rebooting bootloader
Click to expand...
Click to collapse
Possibly, but not likely... The issue here as I stated before is you have attempted to flash a LA (Latin America) version and it partially took, so now neither ROM will flash successfully because the signatures don't match. Pre-Flash Validation Errors are bad news on a locked device, it means that either your image is incorrect or the wrong version, and you can't go outside of that with a locked bootloader (and before you ask, there is no way to unlock the bootloader if you can't boot the device to enable OEM Unlocking in the Developer Options menu).
I would first try updating to the latest Minimal ADB & Fastboot and run the commands from an Administrator command prompt, or if you are somewhat familiar with Linux go that route (it eliminates all driver issues since current distros have embedded support for Android).

acejavelin said:
Possibly, but not likely... The issue here as I stated before is you have attempted to flash a LA (Latin America) version and it partially took, so now neither ROM will flash successfully because the signatures don't match. Pre-Flash Validation Errors are bad news on a locked device, it means that either your image is incorrect or the wrong version, and you can't go outside of that with a locked bootloader (and before you ask, there is no way to unlock the bootloader if you can't boot the device to enable OEM Unlocking in the Developer Options menu).
I would first try updating to the latest Minimal ADB & Fastboot and run the commands from an Administrator command prompt, or if you are somewhat familiar with Linux go that route (it eliminates all driver issues since current distros have embedded support for Android).
Click to expand...
Click to collapse
Thank you. Appreciate it. Will try Linux later. Need to get some work done for now.
One last question? Should I try it with the US Retail ROM or de LA ROM?

gridikoelie said:
Thank you. Appreciate it. Will try Linux later. Need to get some work done for now.
One last question? Should I try it with the US Retail ROM or de LA ROM?
Click to expand...
Click to collapse
The hardware is US Retail, correct, that is what getvar all seems to show so I would try that first... if you absolutely can't get that to work and you can somehow get the LA one to flash and boot successfully, you can always unlock the bootloader and flash something else.
Of course, you are still locked... have you thought about just filing a warranty claim or is it too old?

acejavelin said:
The hardware is US Retail, correct, that is what getvar all seems to show so I would try that first... if you absolutely can't get that to work and you can somehow get the LA one to flash and boot successfully, you can always unlock the bootloader and flash something else.
Of course, you are still locked... have you thought about just filing a warranty claim or is it too old?
Click to expand...
Click to collapse
Just tried it in Ubuntu ...same result.
Warranty claim? I'm from Suriname. Would not be worth The hassle and costs.
I already ordered a Axon 7 from Amazon, but I love this phone...would really like to save it.

gridikoelie said:
Just tried it in Ubuntu ...same result.
Warranty claim? I'm from Suriname. Would not be worth The hassle and costs.
I already ordered a Axon 7 from Amazon, but I love this phone...would really like to save it.
Click to expand...
Click to collapse
With a locked bootloader your options are pretty limited... if you can't get the official firmware to flash, there isn't much else you can do. Sorry.

Hello friends!!
Thanks for your help!
I'm in the same situation as gridikoelie
Install Latin American firmware, do not unlock bootloader before. We are absurdly "locked out" of the terminal...
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.CB
(bootloader) product: osprey
(bootloader) board: osprey
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Samsung REV=07 PRV=01 TYPE=57
(bootloader) ram: 1024MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: ZY2222DXBB
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: BD0BF50A00000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3554880633xxxxx
(bootloader) meid:
(bootloader) date: 09-28-2015
(bootloader) sku: XT1540
(bootloader) battid: SNN5965A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 12 6:14:28 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/osprey_retus
(bootloader) ro.build.fingerprint[1]: 6.0/MPI24.65-25/28:us
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.24.11.2
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband[0]: M8916_2020629.41.03.21.51
(bootloader) version-baseband[1]: SA_AWS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-g88eb
(bootloader) kernel.version[1]: @ilclbld34) (gcc version 4.
(bootloader) kernel.version[2]: SMP PREEMPT Tue Dec 8 05:39
(bootloader) sbl1.git: git=MBM-NG-V80.CC-0-g7abea31
(bootloader) rpm.git: git=MBM-NG-V80.CC-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.CC-0-ga1c5ae6
(bootloader) hyp.git: git=MBM-NG-V80.CC-0-ga1c5ae6
(bootloader) aboot.git: git=MBM-NG-V80.CB-0-gcfa8344
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-typeDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-typeem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:customize: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-sizeDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-sizeadA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-sizeadB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000300000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-sizeersist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001019000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-sizeadC: 0x000000000087e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-sizeem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:system: 0x0000000091000000
(bootloader) partition-size:userdata: 0x0000000121fe0000
(bootloader) qe: qe 0/1
(bootloader) frp-state: protected (142)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.684s
Would we have some way to write directly in emmc with some jtag tool?
I will investigate...

Try to flash STOCK version 5.1.1 instead that is appropriate for your device original region and your region instead of the Stock version 6 that you are attempting to flash and see if that helps. Sometimes better luck can be achieved by flashing the firmware version (5.1.1) that your device potentially came with installed out of the box, that very same exact version as the one you saw when you first powered on your device for the very first time, thats the one that I recommend that you flash, version 5.1.1 and see if it goes thru..
Unless your device is in warranty, in my opinion there isn't any viable real reason for one wanting to keep their bootloader unlocked unless you dont qualify to have your bootloader unlocked because the possibility of things like this happening is still there and you will need to have a bootloader that wont restrict your very own efforts and attempts, legitimate attempts at rescuing your smartphone.
Potential cause of your issue:
Unless this was caused by a malware for which I dont see how any malware can cause such a boot loop inducing damage without having root rights and your device never being rooted (since you kept your bootloader locked, it is presumed you never installed things like TWRP or even bothered at rooting your device), so without root rights a malware cant perform a damage of such magnitude. So this leave me at the only other possibility:
Extensive NAND internal flash storage unit wear.
Yes, you probably wrote too much data to your Internal NAND (Motherboard integrated Solid State Drive) and eventually sectors began to fail until there were no more "extra" sectors to patch up failed ones and then live sectors began failing one by one until it affected critical system files thus causing a boot loop.
My assessment at your potential cause of failure could be wrong, but its my best case.
Anyways, good luck and see if flashing STOCK 5.1.1 helps you out.

FNetV1 said:
Try to flash STOCK version 5.1.1 instead that is appropriate for your device original region and your region instead of the Stock version 6 that you are attempting to flash and see if that helps. Sometimes better luck can be achieved by flashing the firmware version (5.1.1) that your device potentially came with installed out of the box, that very same exact version as the one you saw when you first powered on your device for the very first time, thats the one that I recommend that you flash, version 5.1.1 and see if it goes thru..
Unless your device is in warranty, in my opinion there isn't any viable real reason for one wanting to keep their bootloader unlocked unless you dont qualify to have your bootloader unlocked because the possibility of things like this happening is still there and you will need to have a bootloader that wont restrict your very own efforts and attempts, legitimate attempts at rescuing your smartphone.
Potential cause of your issue:
Unless this was caused by a malware for which I dont see how any malware can cause such a boot loop inducing damage without having root rights and your device never being rooted (since you kept your bootloader locked, it is presumed you never installed things like TWRP or even bothered at rooting your device), so without root rights a malware cant perform a damage of such magnitude. So this leave me at the only other possibility:
Extensive NAND internal flash storage unit wear.
Yes, you probably wrote too much data to your Internal NAND (Motherboard integrated Solid State Drive) and eventually sectors began to fail until there were no more "extra" sectors to patch up failed ones and then live sectors began failing one by one until it affected critical system files thus causing a boot loop.
My assessment at your potential cause of failure could be wrong, but its my best case.
Anyways, good luck and see if flashing STOCK 5.1.1 helps you out.
Click to expand...
Click to collapse
Thanks for reply FNetV1
Try flashing XT1540_OSPREY_RETUS_5.1.1_LPI23.72-65_cid9 without success.
The smartphone does not allow downgrade from 6.0 to 5.1.1, or up to an inferior version of 6.0 to the Latin American (XT1540_OSPREY_RETLA_NA_6.0_MPI24.65-33.1-2_cid12) that tries to flash at first(XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9), Starting with that does not let me go back to the old partition table 6.0 or 5.1.1. retail us. In the screen of the telephone always indicates "version downgrade for primary_gpt" and in console adb:
Code:
F:\user\Descargas\XT1540_OSPREY_RETUS_5.1.1_LPI23.72-65_cid9_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.188s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.739s
Potential cause of your issue:
Unless this was caused by a malware for which I dont see how any malware can cause such a boot loop inducing damage without having root rights and your device never being rooted (since you kept your bootloader locked, it is presumed you never installed things like TWRP or even bothered at rooting your device), so without root rights a malware cant perform a damage of such magnitude. So this leave me at the only other possibility:
Extensive NAND internal flash storage unit wear.
Yes, you probably wrote too much data to your Internal NAND (Motherboard integrated Solid State Drive) and eventually sectors began to fail until there were no more "extra" sectors to patch up failed ones and then live sectors began failing one by one until it affected critical system files thus causing a boot loop.
My assessment at your potential cause of failure could be wrong, but its my best case.
Anyways, good luck and see if flashing STOCK 5.1.1 helps you out
Click to expand...
Click to collapse
This device was tried to flash because of problems that looked like malware, did not allow receiving calls, home button did not respond, the notifications bar was not deployed complete, among others. Previously it was realized a factory restoration that had solved everything, however soon after, I had the same problems. The user always had the phone with full memory, with no space to install anything ...

Thanks for the suggestions, guys.
Still couldn't get it to flash.
I've been at it for 2 weeks now. I am just learning about flashing and I've tried 4X 6.0 and 4X 5.1.1 roms.
Same result:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
For "XT1540_OSPREY_RETLA_NA_6.0_MPI24.65-33.1-2_cid12_subsidy-DEFAULT_CFC.xml" I ran these:
sudo fastboot oem fb_mode_set
sudo fastboot flash partition gpt.bin
sudo fastboot flash bootloader bootloader.img
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash system system.img_sparsechunk.5
sudo fastboot flash system system.img_sparsechunk.6
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase customize
sudo fastboot erase clogo
sudo fastboot oem fb_mode_clear
sudo fastboot reboot
Am I doing something wrong?
Also...isn't there a way to just "format" it all and do a "clean install"? <--- excuse my noob-ness

Sprint A9 - cyclic reboot after update

I'm having issues after OTA update to Android 6.1 for my HTC A9 Sprint.
After it only cyclic reboot (white screen with HTC)
I try update from .exe and fastboot - but all firmware discontinued with error (sample below, I tested 1.10.651.1 / 1.57.651.1 / 1.60.651.4 / 2.18.651.2 - WHL for Sprint):
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>htc_fastboot flash zip 2PQ9IMG_HIA_AERO_WH[email protected]51008_15.00_F_CNV_CNV_HIAE_SPCS_1.15_003_release_453722_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 1.10.651.1
found large-zip header, file count: 23
processing file 1/23...
sending 'zip' (98243 KB)...
OKAY [ 7.336s]
writing 'zip'...
(bootloader) HOSD CL#635870
(bootloader) ERR Tag name out of size
(bootloader) ERR [SD_UPDATE_ERR] Parse zipped android_info fail!
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14 RU_ZIP_INFO_ERROR android-info missing or malformed )
finished. total time: 12.260s
htc_fastboot finished. total time: 12.954s
My CID and MID:
(bootloader) kernel: lk
(bootloader) product: htc_hiaewhl
(bootloader) version: 1.0
(bootloader) imei: 990005706399921
(bootloader) version-main: 2.18.651.2
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ930000
(bootloader) cid: SPCS_001
all:
finished. total time: 0.006s
htc_fastboot finished. total time: 0.183s
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x638000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc6000000
(bootloader) serialno:HT5BXSZ00380
all:
finished. total time: 0.069s
htc_fastboot finished. total time: 0.236s
I need help for resolved this trouble.
Thanks for help and understanding.

Question [Help] FASTBOOT COMMANDS to INSTALL these files [bootloop G100]

RSD LITE has "GET DECOMPRESS FILE SIZE ERROR" on official firmware
I want to run manual fastboot commands in sequence based on extracted firmware.
{
"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"
}
I can make batch file (.BAT)
thanks

austin_dreq said:
RSD LITE has "GET DECOMPRESS FILE SIZE ERROR" on official firmware
I want to run manual fastboot commands in sequence based on extracted firmware.
View attachment 5400837
I can make batch file (.BAT)
thanks
Click to expand...
Click to collapse
First, RSD Lite doesn't work with most windows 10 machines, so use Windows 7 or XP.
Second, unzip the firmware first.
Lmsa is the current moto flashing tool
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

something like this matching with files and rigth locations..
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 bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system super.img_sparsechunk.0
fastboot flash system super.img_sparsechunk.1
fastboot flash system super.img_sparsechunk.2
fastboot flash system super.img_sparsechunk.3
fastboot flash system super.img_sparsechunk.4
fastboot flash system super.img_sparsechunk.5
fastboot flash system super.img_sparsechunk.6
fastboot flash system super.img_sparsechunk.7
fastboot flash system super.img_sparsechunk.8
fastboot flash system super.img_sparsechunk.9
fastboot flash system super.img_sparsechunk.10
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot

sd_shadow said:
First, RSD Lite doesn't work with most windows 10 machines, so use Windows 7 or XP.
Second, unzip the firmware first.
Lmsa is the current moto flashing tool
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks mate
No win 7.
if extracted which file to select?
LMSA not working too.., EMEI not matching and no matching software too (G100)... Not an option.

ALL FAILED Commands
C:\AB Files\moto\Rescue and Smart Assistant>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.069s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.071s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.0
target reported max download size of 805306368 bytes
sending 'system_a' (459104 KB)...
OKAY [ 10.020s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.096s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.1
target reported max download size of 805306368 bytes
sending 'system_a' (497484 KB)...
OKAY [ 10.997s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.071s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.2
target reported max download size of 805306368 bytes
sending 'system_a' (521444 KB)...
OKAY [ 12.896s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.969s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.3
target reported max download size of 805306368 bytes
sending 'system_a' (500712 KB)...
OKAY [ 18.943s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.013s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.4
target reported max download size of 805306368 bytes
sending 'system_a' (486580 KB)...
OKAY [ 15.608s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 15.684s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.5
target reported max download size of 805306368 bytes
sending 'system_a' (524252 KB)...
OKAY [ 18.032s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.102s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.6
target reported max download size of 805306368 bytes
sending 'system_a' (524216 KB)...
OKAY [ 16.357s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.425s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.7
target reported max download size of 805306368 bytes
sending 'system_a' (524244 KB)...
OKAY [ 18.347s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.417s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.8
target reported max download size of 805306368 bytes
sending 'system_a' (524244 KB)...
OKAY [ 15.227s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 15.298s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.9
target reported max download size of 805306368 bytes
sending 'system_a' (200876 KB)...
OKAY [ 5.500s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.572s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.10
error: cannot load 'super.img_sparsechunk.10': No such file or directory
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash vendor vendor.img_sparsechunk.0
error: cannot load 'vendor.img_sparsechunk.0': No such file or directory
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash vendor vendor.img_sparsechunk.1
error: cannot load 'vendor.img_sparsechunk.1': No such file or directory
C:\AB Files\moto\Rescue and Smart Assistant>fastboot erase DDR
erasing 'DDR'...
(bootloader) Invalid partition name DDR
FAILED (remote failure)
finished. total time: 0.069s

austin_dreq said:
ALL FAILED Commands
C:\AB Files\moto\Rescue and Smart Assistant>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.069s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.071s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.0
target reported max download size of 805306368 bytes
sending 'system_a' (459104 KB)...
OKAY [ 10.020s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.096s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.1
target reported max download size of 805306368 bytes
sending 'system_a' (497484 KB)...
OKAY [ 10.997s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.071s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.2
target reported max download size of 805306368 bytes
sending 'system_a' (521444 KB)...
OKAY [ 12.896s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.969s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.3
target reported max download size of 805306368 bytes
sending 'system_a' (500712 KB)...
OKAY [ 18.943s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.013s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.4
target reported max download size of 805306368 bytes
sending 'system_a' (486580 KB)...
OKAY [ 15.608s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 15.684s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.5
target reported max download size of 805306368 bytes
sending 'system_a' (524252 KB)...
OKAY [ 18.032s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.102s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.6
target reported max download size of 805306368 bytes
sending 'system_a' (524216 KB)...
OKAY [ 16.357s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.425s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.7
target reported max download size of 805306368 bytes
sending 'system_a' (524244 KB)...
OKAY [ 18.347s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.417s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.8
target reported max download size of 805306368 bytes
sending 'system_a' (524244 KB)...
OKAY [ 15.227s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 15.298s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.9
target reported max download size of 805306368 bytes
sending 'system_a' (200876 KB)...
OKAY [ 5.500s]
writing 'system_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.572s
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash system super.img_sparsechunk.10
error: cannot load 'super.img_sparsechunk.10': No such file or directory
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash vendor vendor.img_sparsechunk.0
error: cannot load 'vendor.img_sparsechunk.0': No such file or directory
C:\AB Files\moto\Rescue and Smart Assistant>fastboot flash vendor vendor.img_sparsechunk.1
error: cannot load 'vendor.img_sparsechunk.1': No such file or directory
C:\AB Files\moto\Rescue and Smart Assistant>fastboot erase DDR
erasing 'DDR'...
(bootloader) Invalid partition name DDR
FAILED (remote failure)
finished. total time: 0.069s
Click to expand...
Click to collapse
What does getvar all say?
Remove the imei line before posting.
Code:
fastboot getvar all

sd_shadow said:
What does getvar all say?
Remove the imei line before posting.
Code:
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nio_retail-6b3ddf45a7-210308
(bootloader) product: nio
(bootloader) board: nio
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: SUPER
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB KIOXIA THGJFAT0T44BAILB FV=1001 WB=0
(bootloader) ram: 6GB MICRON LP5 DIE=12Gb CH=4
(bootloader) cpu: SM8250 2.1
(bootloader) serialno: ZY22C74CCP
(bootloader) cid: 0x000B
(bootloader) channelid: 0x00
(bootloader) uid: 87520939
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Fall-through from charger boot mode
(bootloader) meid:
(bootloader) date: 04-20-2021
(bootloader) sku: XT2125-4
(bootloader) carrier_sku: XT2125-4
(bootloader) battid: SB18C74375
(bootloader) battery-voltage: 4364
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retcn
(bootloader) ro.build.fingerprint[0]: motorola/nio_retail/nio:11/RRTS31.
(bootloader) ro.build.fingerprint[1]: Q1-84-24-1-2/db18d:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-10800-SMxx50.0
(bootloader) version-baseband[0]: M55_HI20_209.334.01.80R NIO_PVT_SUPERD
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Thu J
(bootloader) kernel.version[4]: ul 8 13:06:55 CDT 2021
(bootloader) git:abl: MBM-3.0-nio_retail-6b3ddf45a7-210308
(bootloader) frp-state: protected (77)
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C93720
(bootloader) primary-display[0]: tianma_nt36672c_1080x2520_670_105hz_dsc
(bootloader) primary-display[1]: _vid
(bootloader) secondary-display:
all: listed above
finished. total time: 0.332s

austin_dreq said:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nio_retail-6b3ddf45a7-210308
(bootloader) product: nio
(bootloader) board: nio
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: SUPER
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB KIOXIA THGJFAT0T44BAILB FV=1001 WB=0
(bootloader) ram: 6GB MICRON LP5 DIE=12Gb CH=4
(bootloader) cpu: SM8250 2.1
(bootloader) serialno: ZY22C74CCP
(bootloader) cid: 0x000B
(bootloader) channelid: 0x00
(bootloader) uid: 87520939
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Fall-through from charger boot mode
(bootloader) meid:
(bootloader) date: 04-20-2021
(bootloader) sku: XT2125-4
(bootloader) carrier_sku: XT2125-4
(bootloader) battid: SB18C74375
(bootloader) battery-voltage: 4364
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retcn
(bootloader) ro.build.fingerprint[0]: motorola/nio_retail/nio:11/RRTS31.
(bootloader) ro.build.fingerprint[1]: Q1-84-24-1-2/db18d:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-10800-SMxx50.0
(bootloader) version-baseband[0]: M55_HI20_209.334.01.80R NIO_PVT_SUPERD
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Thu J
(bootloader) kernel.version[4]: ul 8 13:06:55 CDT 2021
(bootloader) git:abl: MBM-3.0-nio_retail-6b3ddf45a7-210308
(bootloader) frp-state: protected (77)
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C93720
(bootloader) primary-display[0]: tianma_nt36672c_1080x2520_670_105hz_dsc
(bootloader) primary-display[1]: _vid
(bootloader) secondary-display:
all: listed above
finished. total time: 0.332s
Click to expand...
Click to collapse
Ok, That's looks fine, except I don't see the channel (ro.carrier)
It is not important as the bootloader is unlocked.
Code:
fastboot getvar ro.carrier
See my
Flashing Commands

sd_shadow said:
Ok, That's looks fine, except I don't see the channel (ro.carrier)
It is not important as the bootloader is unlocked.
Code:
fastboot getvar ro.carrier
See my
Flashing Commands
Click to expand...
Click to collapse
many thanks brother.. Will try again in the morning. Need a beer to lower my heartbeat now....

[Resovled] thanks to @sd_shadow
* Download official Firmware (google it)
* Extract the ZIP in location where you can run Fastboot command
* Open wih notepad flashfile.xml or service.xml and get the fastboot commands in link below
* https://kfhost.net/flashfile (command in English)
* Convert the commands to batch file (Paste in notepad (NAME.txt) and rename to NAME.BAT)
* Connect phone in Fastboot mode
* Click on NAME.BAT
Wait and enjoy

command to lock bootloader & proof
fastboot flashing lock

HI all! i`m stuck on bootloader... i brick my g100 trying to install a custom rom, unbrick it with EDL (thank god!).
but now i`m stuck on bootloader. I`ve confused about my phone region, already reflash the stock rom of RETBR region, but RSA tool tells me that it is RETAIL (and idk the difference).
Right now i can access my phone via bootloader, but all commands return (remote failure). Unfortunately the bootloader is now locked and when i run fastboot flashing unlock or fastboot oem unlock <my code> it returns that i need unlock OEM via Developer tools, BUT, i can access the system to do that! lol
one thing that i realize on my getvar all is that the current_slot property is empty and ro.carrier mismatch version-bootloader and others properties
any clue to save me? I`m using Linux btw mainly but have access at Windows if need to.
Bash:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nio_retail-30f264df19-220105
(bootloader) product: nio
(bootloader) board: nio
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: SUPER
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB KIOXIA THGJFAT1T84BAIRB FV=1001 WB=0
(bootloader) ram: 12GB MICRON LP5 DIE=12Gb CH=4
(bootloader) cpu: SM8250 2.1
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: EE98D533
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Fall-through from normal boot mode
(bootloader) meid:
(bootloader) date: 07-02-2021
(bootloader) sku: XT2125-4
(bootloader) carrier_sku: XT2125-4
(bootloader) battid: SB18C74374
(bootloader) battery-voltage: 3696
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/nio_retail/nio:11/RRTS31.
(bootloader) ro.build.fingerprint[1]: Q1-84-24-1-11/d6807:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-10800-SMxx50.0
(bootloader) version-baseband[0]: M55_HI20_209.334.01.89R NIO_PVT_SUPERD
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version:
(bootloader) git:abl: MBM-3.0-nio_retail-30f264df19-220105
(bootloader) frp-state: no protection (0)
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D09857
(bootloader) primary-display: tianma_nt36672c_1080x2520_670_dsc_vid
(bootloader) secondary-display:
all: listed above
finished. total time: 0.062s