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.
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
I booted into blue_spark_v2 twrp and wiped system, data, and cache. flashed the new 9/24 havoc and blue_spark_v2 and rebooted into recovery to flash open_sapps and magisk. This is where it all went wrong.. I'm not hard bricked as I am in bootloader so I have fastboot options, however, I cannotboot twrp as it gives me :
[email protected]:/home/bkeaver/Downloads/PIE# fastboot boot twrp-3.2.3-x_blu_spark_v9.85v2_op6.img
downloading 'boot.img'...
OKAY [ 0.738s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.754s
[email protected]:/home/bkeaver/Downloads/PIE#
nothing I do is working.. if do a fastboot getvar all I see the following for slot info.:
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
I can't seem to switch to the other slot or get anywhere.. Some help from someone would be great if possible and I would appreciate it. also I am on a linux computer and don't have access to windows...
bkeaver said:
I booted into blue_spark_v2 twrp and wiped system, data, and cache. flashed the new 9/24 havoc and blue_spark_v2 and rebooted into recovery to flash open_sapps and magisk. This is where it all went wrong.. I'm not hard bricked as I am in bootloader so I have fastboot options, however, I cannotboot twrp as it gives me :
[email protected]:/home/bkeaver/Downloads/PIE# fastboot boot twrp-3.2.3-x_blu_spark_v9.85v2_op6.img
downloading 'boot.img'...
OKAY [ 0.738s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.754s
[email protected]:/home/bkeaver/Downloads/PIE#
nothing I do is working.. if do a fastboot getvar all I see the following for slot info.:
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
I can't seem to switch to the other slot or get anywhere.. Some help from someone would be great if possible and I would appreciate it. also I am on a linux computer and don't have access to windows...
Click to expand...
Click to collapse
Go to guides forum and download fastboot flashable firmware and flash full firmware. Just follow the thread instructions and you be fine. Had your problem to
nickwarn said:
Go to guides forum and download fastboot flashable firmware and flash full firmware. Just follow the thread instructions and you be fine. Had your problem to
Click to expand...
Click to collapse
Thanks! I will give it a shot.. I didn't see that when I looked through those threads..
Hey i hard bricked my g8 plus. I forget to unlock oem bootloader and now i cant start the phone. when flash the stock rom the screen stay in "your device is corrupt. it cant be trusted and will not boot"
What can i do? the phone cant start and cant unlock bootloader
Have you tried blankflash tool? Download from
mirrors.lolinet.com/firmware/moto/doha/blankflash/
andymore said:
Have you tried blankflash tool? Download from
mirrors.lolinet.com/firmware/moto/doha/blankflash/
Click to expand...
Click to collapse
Can you explain me how i need to use the blankflash file pls? i never tried that
felixp_ said:
Can you explain me how i need to use the blankflash file pls? i never tried that
Click to expand...
Click to collapse
Your device is not hard bricked. It just can't start. Use the Lenovo moto smart assistant to flash the device. It will use signed image post by Motorola and able to boot the device.
Hard bricked= no bootloader, no fastboot. Nothing can be done
{
"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"
}
riyan65 said:
Your device is not hard bricked. It just can't start. Use the Lenovo moto smart assistant to flash the device. It will use signed image post by Motorola and able to boot the device.
Hard bricked= no bootloader, no fastboot. Nothing can be done
Click to expand...
Click to collapse
Thanks for the explain. my phone is in fastboot but cant flash/start the phone
The lenovo moto smart assistant says "this device is not supported"
felixp_ said:
Hey i hard bricked my g8 plus. I forget to unlock oem bootloader and now i cant start the phone. when flash the stock rom the screen stay in "your device is corrupt. it cant be trusted and will not boot"
What can i do? the phone cant start and cant unlock bootloader
Click to expand...
Click to collapse
take it back to recovery center. the only last option i guess
felixp_ said:
Thanks for the explain. my phone is in fastboot but cant flash/start the phone
The lenovo moto smart assistant says "this device is not supported"
Click to expand...
Click to collapse
Which firmware did you flash? Did you get any error while flashing the device?
riyan65 said:
Which firmware did you flash? Did you get any error while flashing the device?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/doha/official/RETAIL/ this firmware and yes it show an error but cant remember what it says . i think i lose the phone :crying:
i had the same message and i fixed my phone, use fastboot and extract the rom into ur minimal adb folder and copy these comands into the terminal
make sure the rom is the one for your phone model - region
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
btw you should also be able to lock / unlock your bootloader from fastboot terminal how many times you want, just unlock your bootloader 1st, using this guide https://www.getdroidtips.com/how-to...s/#Steps_to_Unlock_Bootloader_on_Moto_G8_Plus
esrd43 said:
i had the same message and i fixed my phone, use fastboot and extract the rom into ur minimal adb folder and copy these comands into the terminal
make sure the rom is the one for your phone model - region
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
btw you should also be able to lock / unlock your bootloader from fastboot terminal how many times you want, just unlock your bootloader 1st, using this guide https://www.getdroidtips.com/how-to...s/#Steps_to_Unlock_Bootloader_on_Moto_G8_Plus
Click to expand...
Click to collapse
thank you for your help, just the one thing i am not able to do, is turn off the bootloader, cause i do not have access to android at this moment, cause the phone is in ap fastboot mode secure all the time i want to start it.
felixp_ said:
thank you for your help, just the one thing i am not able to do, is turn off the bootloader, cause i do not have access to android at this moment, cause the phone is in ap fastboot mode secure all the time i want to start it.
Click to expand...
Click to collapse
You can't unlock the bootloader until it enabled in developer options "allow OEM unlock". You need to enable allow OEM unlock option in able to unlock the bootloader. And by the way, flashing the firmware should boot the device. And what error does it give when flashing?
riyan65 said:
You can't unlock the bootloader until it enabled in developer options "allow OEM unlock". You need to enable allow OEM unlock option in able to unlock the bootloader. And by the way, flashing the firmware should boot the device. And what error does it give when flashing?
Click to expand...
Click to collapse
after flashing it shows "your device is corrupt. It cant be trusted and will not boot".
Then it back to Ap fastboot mode (secure).
No booteable A/B slot
Failed to boot linux, falling back to fastboot
Fastboot reason: Fall-through from charger boot mode
felixp_ said:
after flashing it shows "your device is corrupt. It cant be trusted and will not boot".
Then it back to Ap fastboot mode (secure).
No booteable A/B slot
Failed to boot linux, falling back to fastboot
Fastboot reason: Fall-through from charger boot mode
Click to expand...
Click to collapse
I want you to post the flashing logs, you get when flashing. Eg:- fastboot flash bootloader bootloader. Img
Successful flashed or security downgrade (flash failed)
Like this I want you to Post.
riyan65 said:
I want you to post the flashing logs, you get when flashing. Eg:- fastboot flash bootloader bootloader. Img
Successful flashed or security downgrade (flash failed)
Like this I want you to Post.
Click to expand...
Click to collapse
ok there is the flash logs:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
...
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 805259264 bytes
sending 'partition' (37 KB)...
OKAY [ 0.037s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.506s]
finished. total time: 0.547s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 805259264 bytes
sending 'bootloader' (14204 KB)...
OKAY [ 0.558s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'uefi_sec.mbn' to 'uefisecapp'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'qupfw.elf' to 'qupfw'
(bootloader) - flashing 'xbl_config.elf' to 'xbl_config'
(bootloader) - flashing 'xbl.elf' to 'xbl'
OKAY [ 0.360s]
finished. total time: 0.985s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 805259264 bytes
sending 'logo_a' (2864 KB)...
OKAY [ 0.137s]
writing 'logo_a'...
OKAY [ 0.101s]
finished. total time: 0.243s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805259264 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.980s]
writing 'boot_a'...
OKAY [ 0.739s]
finished. total time: 2.722s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
error: cannot load 'recovery.img': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
error: cannot load 'adspso.bin': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 805259264 bytes
sending 'oem_a' (11940 KB)...
OKAY [ 0.472s]
writing 'oem_a'...
OKAY [ 0.154s]
finished. total time: 0.636s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 805259264 bytes
sending 'system_a' (524284 KB)...
OKAY [ 15.100s]
writing 'system_a'...
OKAY [ 0.048s]
finished. total time: 15.147s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 805259264 bytes
sending 'system_a' (524284 KB)...
OKAY [ 14.866s]
writing 'system_a'...
OKAY [ 0.052s]
finished. total time: 14.921s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 805259264 bytes
sending 'system_a' (524284 KB)...
OKAY [ 14.254s]
writing 'system_a'...
OKAY [ 0.056s]
finished. total time: 14.316s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 805259264 bytes
sending 'system_a' (489108 KB)...
OKAY [ 14.398s]
writing 'system_a'...
OKAY [ 0.068s]
finished. total time: 14.465s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 805259264 bytes
sending 'system_a' (521120 KB)...
OKAY [ 14.594s]
writing 'system_a'...
OKAY [ 0.063s]
finished. total time: 14.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target reported max download size of 805259264 bytes
sending 'system_a' (49320 KB)...
OKAY [ 1.490s]
writing 'system_a'...
OKAY [ 0.072s]
finished. total time: 1.566s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 805259264 bytes
sending 'modem_a' (81040 KB)...
OKAY [ 3.074s]
writing 'modem_a'...
OKAY [ 0.502s]
finished. total time: 3.580s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.140s]
finished. total time: 0.143s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.154s]
finished. total time: 0.157s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 805259264 bytes
sending 'fsg_a' (11196 KB)...
OKAY [ 0.540s]
writing 'fsg_a'...
OKAY [ 0.191s]
finished. total time: 0.738s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.101s]
finished. total time: 0.105s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.155s]
finished. total time: 0.156s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase customize
erasing 'customize'...
(bootloader) Invalid partition name customize
FAILED (remote failure)
finished. total time: 0.111s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase clogo
erasing 'clogo'...
(bootloader) Invalid partition name clogo
FAILED (remote failure)
finished. total time: 0.110s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
...
OKAY [ 0.106s]
finished. total time: 0.110s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
This is my getvar all list:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-59ad2f5404-200404
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY326SMLCT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 1DF84B82
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 357207100965938
(bootloader) imei2: 357207100965946
(bootloader) meid:
(bootloader) date: 10-11-2019
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid: SB18C52857
(bootloader) battery-voltage: 3684
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:9/PPIS29.65-51-
(bootloader) ro.build.fingerprint[1]: 3/3b59e:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.3.doha.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.11.r1-03300-NICOBAR.0
(bootloader) version-baseband: M6125_06.09.02.10R DOHA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.98-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld87) (clang version 6.0.9 for Androi
(bootloader) kernel.version[2]: d NDK) #1 SMP PREEMPT Sat Apr 4 01:13:12
(bootloader) kernel.version[3]: CDT 2020
(bootloader) git:abl: MBM-3.0-doha_retail-59ad2f5404-200404
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: retla
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(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: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) pcb-part-no: SB28C54618
Pls i need help with the firmware im not sure if is RETAIL or RETLA.
And the complete fiwmare is DOHA_*RETLA OR RETAIL*_9.0_PPIS29.65-51-3. Is that correct or im wrong?
hmm, try searching in google for how to enable oem unlock from fastboot, the try to unlock your bootloader, that should work
or ask mode details about the blankflash if anyone knows about it
felixp_ said:
This is my getvar all list:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-59ad2f5404-200404
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY326SMLCT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 1DF84B82
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 357207100965938
(bootloader) imei2: 357207100965946
(bootloader) meid:
(bootloader) date: 10-11-2019
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid: SB18C52857
(bootloader) battery-voltage: 3684
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:9/PPIS29.65-51-
(bootloader) ro.build.fingerprint[1]: 3/3b59e:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.3.doha.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.11.r1-03300-NICOBAR.0
(bootloader) version-baseband: M6125_06.09.02.10R DOHA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.98-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld87) (clang version 6.0.9 for Androi
(bootloader) kernel.version[2]: d NDK) #1 SMP PREEMPT Sat Apr 4 01:13:12
(bootloader) kernel.version[3]: CDT 2020
(bootloader) git:abl: MBM-3.0-doha_retail-59ad2f5404-200404
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: retla
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(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: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) pcb-part-no: SB28C54618
Pls i need help with the firmware im not sure if is RETAIL or RETLA.
And the complete fiwmare is DOHA_*RETLA OR RETAIL*_9.0_PPIS29.65-51-3. Is that correct or im wrong?
Click to expand...
Click to collapse
First, remove your IMEI, serial no, from thread
Second, everything is flashing without any Major error, but the device is not booting. Due to wrong firmware you are flashing, your device is retla and you are flashing retain firmware, due to which the device cause bootloop. Download the retla firmware and flash the device. It should boot. And remove the command of bootloader and gpt, just to be safe.(could cause hard bricked)
what is the exact message you get when you try to unlock your bootloader using fastboot oem unlock?
his problem is once u flash another rom even if official, your device can't start because the bootloader is locked, and to unlock the bootloader u need to enable that "usb debugging" and "allow oem unlock" from developer options which u can't access because u can't enter android.
try searching for that blankflash method, there's alot of videos on youtube and google that can guide u
also u might have chosen the wrong rom for your device
esrd43 said:
what is the exact message you get when you try to unlock your bootloader using fastboot oem unlock?
his problem is once u flash another rom even if official, your device can't start because the bootloader is locked, and to unlock the bootloader u need to enable that "usb debugging" and "allow oem unlock" from developer options which u can't access because u can't enter android.
try searching for that blankflash method, there's alot of videos on youtube and google that can guide u
also u might have chosen the wrong rom for your device
Click to expand...
Click to collapse
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
But i cant start the phone. i flashed the firmware and then when it reboot the screen stay in "Your device is corrupt. it cant be trusted and will not boot. I have enabled usb debugging but oem unlock no in developer options. and now i cant access to android
felixp_ said:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
But i cant start the phone. i flashed the firmware and then when it reboot the screen stay in "Your device is corrupt. it cant be trusted and will not boot. I have enabled usb debugging but oem unlock no in developer options. and now i cant access to android
Click to expand...
Click to collapse
I see now, I re-locked my bootloader and got exactly the same message as you but I could unlock it again to be able to boot again.
your phone for sure can be fixed, i think blankflash is the solution but I never used that before
still try flashing the RETLA rom for your device instead of RETAIL, who knows if that may work
https://mirrors.lolinet.com/firmware/moto/doha/official/RETLA/