Moto E5 plus bricked - fastboot only - all stock - Moto E5 Questions & Answers

Hi all.
My phone bricked out of the blue, all stock, locked fastboot, no upgrades installed for quite some time, only Play Store apps installed.
It can't get past fastboot. When I try to Start Android, it shows "Failed to validate boot image. ERROR: failed to pass validation, backup to fastboot".
Same messages when I try to enter Recovery Mode.
Tried installing TWRP, but I can't get the fastboot unlock code, shows error message below:
C:\Program Files\Android\Android Studio>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.004s]
finished. total time: 0.004s
Baseband field is blank, and IMEI is 0.
Product/Variant is showing: hannah 000000000000000 16GB P3
ATM I have no need for custom roms, unlocks or anything like that, but if it's the way to go, I would go for it.
Any ideias on how to approach this?
Below I send all vars, if it helps somehow:
C:\Program Files\Android\Android Studio>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BE.4F(*)
(bootloader) product: hannah
(bootloader) board: hannah
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: d0f001b8
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 1ECC453900000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VBE.4F-0-g4e3d3ac
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.055s

What variant do u have

Pbsipher1 said:
What variant do u have
Click to expand...
Click to collapse
Thanks for your reply, and I apologize if I don't answer this correctly, I'm not very knowledgeable in these things...
I'm from Brazil, and bought it here, so doing some research, I found this:
OPP27.91-146 Brazil / XT1944-4
I don't know if there's any way to check it within fastboot as well... a lot of vars are blank at this moment...
The only other thing that looks like a variant here is: hannah

Lenovo Moto Smart Assistant
Try using the "Lenovo Moto Smart Assistant". After installing, connect your phone to your computer, open the program, click flash - rescue - and follow the instructions.

Ex novo said:
Try using the "Lenovo Moto Smart Assistant". After installing, connect your phone to your computer, open the program, click flash - rescue - and follow the instructions.
Click to expand...
Click to collapse
Just tried that, but no dice. Tried all variations of Moto E5, never got recognized.
"Failed to match the connected device. Please plug it out, and try again".
Tried plugging it out/in several times, but no luck.
Thank you for the suggestion, though.

Have the same problem. Could you fix it? Thx

Only hope is blankflash or possibly flashing newer stock firmware, its on telegram group

I seem to have the same issue.
Did you manage to find a way to fix this?

Related

HELP! Moto G6 in bootloader

Hello people, my Moto G6 is left with the bootloader screen and does not leave there
I tried the Rescue and Smart Assistant and the device does not recognize me
I tried loading it with the minimal_adb_fastboot_1.4.3_portable a ROM and it throws errors at me
It seemed to me that it was because I had the bootloader blocked, I read the procedure to unlock it through the Motorola page, but throwing the fastboot oem get_unlock_data throws me error
If the same thing happens to someone or you know how to solve it, I listen to your suggestions before throwing it away:good:
Cheers
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-32ffece-200210
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: 1c089a85
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 822086D800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ali_retail-32ffece-200210
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.106s
fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.034s]
finished. total time: 0.035s
DrStranger said:
Hello people, my Moto G6 is left with the bootloader screen and does not leave there
I tried the Rescue and Smart Assistant and the device does not recognize me
I tried loading it with the minimal_adb_fastboot_1.4.3_portable a ROM and it throws errors at me
It seemed to me that it was because I had the bootloader blocked, I read the procedure to unlock it through the Motorola page, but throwing the fastboot oem get_unlock_data throws me error
If the same thing happens to someone or you know how to solve it, I listen to your suggestions before throwing it away:good:
Cheers
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-32ffece-200210
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: 1c089a85
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 822086D800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ali_retail-32ffece-200210
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.106s
fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.034s]
finished. total time: 0.035s
Click to expand...
Click to collapse
I don't believe there is a fix.
Bootloader is locked and Lenovo rescue isn't working.
Maybe someone else has some ideas.
Sent from my ali using XDA Labs
---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------
Is this a Verizon model?
Sent from my ali using XDA Labs

MOTO G7 - Fastboot problem after installing rom

Good morning friends! I have a problem that has become painful for me these past few days! I took my moto g7 xt1962-4 (river) and installed a PixelExperience recovery and a rom for this build.
Version: 10
File name: PixelExperience_river-10.0-20201123-1209-OFFICIAL.zip
MD5 hash: 4f9130df18136891e982baa925fc9bc6
Date: November 23, 2020 12:09 UTC
Downloads: 121
However after installing the recovery and finalizing the installation of the zip (ROM) my device restarted and remained on fastboot, I tried to use the minimal adb to repair the device, I tried to use rsd to repair the device, and I also used the tool lenovo repair, if anyone knows what is happening, thank you. Below I will leave the reading of getvar all.
(before installing the rom the bootloader was unlocked and now the oem_locked status)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-f238a87f119-201124
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 1056de9d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-f238a87f119-201124
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.113s
C:\Program Files (x86)\Minimal ADB and Fastboot>
João Pedro Cordeiro said:
Good morning friends! I have a problem that has become painful for me these past few days! I took my moto g7 xt1962-4 (river) and installed a PixelExperience recovery and a rom for this build.
Version: 10
File name: PixelExperience_river-10.0-20201123-1209-OFFICIAL.zip
MD5 hash: 4f9130df18136891e982baa925fc9bc6
Date: November 23, 2020 12:09 UTC
Downloads: 121
However after installing the recovery and finalizing the installation of the zip (ROM) my device restarted and remained on fastboot, I tried to use the minimal adb to repair the device, I tried to use rsd to repair the device, and I also used the tool lenovo repair, if anyone knows what is happening, thank you. Below I will leave the reading of getvar all.
(before installing the rom the bootloader was unlocked and now the oem_locked status)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-f238a87f119-201124
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 1056de9d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-f238a87f119-201124
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.113s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
When the bootloader changes from unlocked to lock by itself or after flashing a rom, only fix I've seen is.
Booting to EDL Mode
Try
Code:
fastboot oem blankflash
If you can boot a custom recovery like TWRP
see reboot options for EDL
or use
Code:
adb reboot edl
With twrp booted.
If device is in Emergency Download Mode (EDL Mode)
Screen will be black and will be shown as Qualcomm device on PC
i also faced this problem when i flash the lineageos, this is a low version bootloader and cannot turn to edl mode, i use TinyFastbootScript fix this issue.
get a stock rom and flash the BP/BL.
net time you'd better install the copy-partitions-20200903_1329.zip before flash a new custom rom.
I managed to get him to go to edl and use blankflash but still no ah how to install twrp or firware
I bought another plate for the device, I thank everyone on the forum for their attention, you are excellent people, and now we have a story about a brick
sd_shadow said:
When the bootloader changes from unlocked to lock by itself or after flashing a rom, only fix I've seen is.
Booting to EDL Mode
Try
Code:
fastboot oem blankflash
If you can boot a custom recovery like TWRP
see reboot options for EDL
or use
Code:
adb reboot edl
With twrp booted.
If device is in Emergency Download Mode (EDL Mode)
Screen will be black and will be shown as Qualcomm device on PC
Click to expand...
Click to collapse
everything worked fine on EDL but it still doesn't work, I can put it in qualcomm mode but I didn't succeed
João Pedro Cordeiro said:
everything worked fine on EDL but it still doesn't work, I can put it in qualcomm mode but I didn't succeed
Click to expand...
Click to collapse
you mean the phone can worked on EDL mode but you cannot use blankflash function?
blankflash - mirrors.lolinet.com > firmware > motorola > lake > blankflash
make sure the edl driver has been installed and check the 9008 mode shown in the device manager.
after the blankflash the phone can be set to bootloader mode, then you can do other trying.

Moto G6 Play Recovery

Hi,
I was hoping someone may be able to point me in the right direction with an issue with a Moto G6 play that seems to be stuck with what I'm guessing is a corrupted firmware. The phone is my partners and was totally standard, she asked me to take a look yesterday as it seemed to be locked on the charging screen. I managed to get it to power off but it seems to have gone into the boot loader where I have various warnings about being unable to validate the image (Boot or recovery).
The only options I seem to have are:-
Bootloader logs
switch tools mode
start
restart bootloader
recovery mode
power off
factory
barcodes
bp tools
Qcom
but pressing the power button on each of these seems to cycle to the next one rather than take me to a sub menu.
I did manage to get to the android droid with the open hatch once, but can't seem to get back to that.
I'm not entirely sure what version the phone is and when I run the getvar option with fastboot it looks like a lot of the fields are blank (Not sure if this is normal):-
C:\Users\sgpow\AppData\Local\Android\Sdk\platform-tools>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-aljeter_retail-b1f322d35c1-2
(bootloader) version-bootloader[1]: 00404
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: 8a7cd3d2
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 159A3D7400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-aljeter_retail-b1f322d35c1-200404
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.314s
I have tried to follow a few guides to reflash back to stock, but have had no success so far. Suspect that may be down to not being able to identify the correct stock roms.
Any thoughts or help greatly appreciated.
Regards
Frank

Moto G5S Plus - not able to flash stock rom, stuck at bootscreen, fastboot fails with remote error

Hi All,
My moto g5s plus( Indian model - XT 1804 ) has stopped booting altogether for last few days. Things I have already tried:
Try recivering using "Recovery Mode" from boot options
dint work, keeps coming back to bootloader screen with error "Failed to validate recovery image"
Install Moto/Lenovo assistant and try flashing using that tool
This does not work because IMEI and SKU on my device are set to all 0s.
RSA downloads the firmware and fails when it starts to flash the same because of IMEI/SKU being all 0s.
Flash the RSA downloaded firmware manually( RSA looked at my IMEI number and downloaded - SANDERS_OPS28.65_36_14_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml )
The very first step involving gpt.bin keeps failing with below error
Code:
fastboot flash partition gpt.bin
(bootloader) is-logical:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.171s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
Fastboot is able to list my device when I run "fastboot devices" command.
Output of fastboot get all variables is below
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: MY_SERIAL_NUMBER ( this has a value, I have redacted it on purpose )
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: MY_UID ( this has a value, I have redacted it on purpose )
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.019s
What should be my next step to flash this stock rom?
This device is not rooted neither was it running a custom rom.
PS: ADB is not able detect this device either.
bump.
Tried booting TWRP image, no luck. TWRP boot itself fails :'(
I'm almost at your exact situation, were you able to solve it? I don't know if my phone is considered bricked or not
Same situation for me, after a couple of years I still didn't find any solution.

Motorola Moto G5S Plus (XT1802) that does not boot, calls now on the Bootloader screen (failed to validate boot image)

Hello guys
First I apologize for my bad English
I'm new in the business, I came across the first big problem with a Motorola Moto G5S Plus (XT1802) that doesn't boot, it turns on the Bootloader logs screen, and presents the following messages:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Volume down key pressed
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
The device worked perfectly, it started to crash, with difficulties to restart, then it crashed in the bootloader. I put root a while ago, and I was with android 8.1.0. I've tried everything.
Here is my output of the command "fastboot getvar all":
C:\Users\PRISTON TALE\Desktop\Comandos ADB Romtekcell>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: 2006e0b2
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: FBC7888C00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.141s
As you can see in the command output and in the attached photos, what worries me the most is that both the IMEI and the model are zeroed, neither the IMEI number nor the XT1802 appears. On the Barcodes screen, everything is also reset, with the exception of the serial, which appears perfectly.
Same situation for me, no solution available after 2 years.

Categories

Resources