Database Develop

Always boots to recovery... Any known fix?

Hi,
I could use some help... One of my G5S Plus phones boots into stock recovery "No command" screen every time I power on. I work around this by entering the stock recovery (Power + Vol Up) and selecting bootloader. Once bootloader loads, I simply hit start and the phone boots properly. All else seems fine -- operation is good.
I've had this issue ever since I unlocked/rooted/TWRP/magisk when I first got the phone. To be honest, I'm not sure I got the mods installed correctly, which is why I have given up and returned to stock. So, I recently flashed the stock Oreo via fastboot and relocked the bootloader. Again, all works fine except for the boot to recovery mode after powering up.
I researched the forum on this issue, but didn't find any solution, though it seems many others have the issue. I'm hoping there is a guru here that knows how to fix this. Examples of others with similar issues:
HTML:
https://forum.xda-developers.com/android/help/moto-g5s-plus-twrp-recovery-boot-loop-t3762077
HTML:
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-recovery-boot-loop-t3772621
HTML:
https://forum.xda-developers.com/moto-g4/help/moto-g4-recovery-boot-loop-t3608348
One thing I did find here on the forums... but it was related to the G5 -- Something to do with the misc partition???:
HTML:
https://forum.xda-developers.com/g5/how-to/fix-phone-reboots-recovery-mode-started-t3705325
Here's my Getvar all...
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 5
(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: Deleted
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: E3DC2DC800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: Deleted
(bootloader) meid:
(bootloader) date: 09-17-2017
(bootloader) sku: XT1806
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon May 11 10: 8:29 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders/sanders:8.1.0/OPS
(bootloader) ro.build.fingerprint[1]: 28.65-36/9fea:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.31.40.sanders.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.79R SANDERS_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gd0e0d1a (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Aug 10 22:52:41 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=MBM-NG-VC2.11-0-g92e5e21-dirty
(bootloader) tz.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) devcfg.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) keymaster.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) cmnlib.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) cmnlib64.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) prov.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
Here are the commands I used to flash -- I tried to erase DDR, but permission was denied:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
Followed by these commands to relock the bootloader
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock

By seeing "(bootloader) imei: Deleted" and "(bootloader) serialno: Deleted" i can tell that the phone is really messed up.
I've found this guide, but it says you need STOCK NOUGAT but you're on OREO, but it might help you.

It seems the latest OTA fixed the issue. It complained about the recovery partition during install, but appears to have overwritten it/fixed it during the upgrade. Wife hasn't complained since the update.

Coala990 said:
By seeing "(bootloader) imei: Deleted" and "(bootloader) serialno: Deleted" i can tell that the phone is really messed up.
I've found this guide, but it says you need STOCK NOUGAT but you're on OREO, but it might help you.
Click to expand...
Click to collapse
LOL. I manually deleted them before posting the text. I should have been more clear about that.
The wife is running Oreo just fine and getting OTA updates. The only issue is that the phone cold boots to stock recovery. Easy workaround... Power + Vol Down on cold boot into bootloader, then press power to select "start" directly from bootloader. Then, it boots just fine.

Unable to flash any file, or go anywhere past Fastboot on Moto G5s Plus XT1800

Hi guys, this is my first post here in XDA, and i'm kinda desperate... a couple of weeks ago my Moto G5s Plus (rooted, but with official Nougat firmware) turned itself off overnight, and ever since won't turn on except on Fastboot mode. Every time I try to Start the device normally, the Bootloader Logs appear with the message "Start up failed; failed to validate boot image". The same thing happens when I try to go into Factory or even Recovery mode (instead of failed to validate boot image, it says, failed to validate recovery image).
When I plug it into my PC, it is recognized but only as Android Bootloader Mode. I've tried different files of official firmware in order to flash them via fastboot, but it's no use... it just says "Preflash validation failed", and so on.
When I enter the command getvar_all, this is what it shows:
C:\Users\IVAN\Sanders\Stock\Third>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.06(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(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: 229d978d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 881733DA00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 1
(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.06-0-g1e22c44
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
Finished. Total time: 0.250s
I've noticed that both the CID and the IMEI are gonners, but as I can't flash anything, there's no way of trying the "Validus" method to restore the IMEI (which I've already done a couple of months ago, after the first root).
I've tried by setting my PC into Test Mode, so as to "skip" the validation of the flash images, but it shows the exact same message. RSD Lite won't even show my device when plugged. I couldn't erase user data, cache or even system partitions, because it says "Permission denied".
These are some of the fastboot commands i've tried to reflash stock (I looked for the latest Oreo firmware, so as to be sure that I wasn't downgrading):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
exit
...always answering "REMOTE failure". I've tried to describe the problem as thoroughly as I could; I hope someone can gimme a hand :good:

Iv_Milh said:
Hi guys, this is my first post here in XDA, and i'm kinda desperate... a couple of weeks ago my Moto G5s Plus (rooted, but with official Nougat firmware) turned itself off overnight, and ever since won't turn on except on Fastboot mode. Every time I try to Start the device normally, the Bootloader Logs appear with the message "Start up failed; failed to validate boot image". The same thing happens when I try to go into Factory or even Recovery mode (instead of failed to validate boot image, it says, failed to validate recovery image).
When I plug it into my PC, it is recognized but only as Android Bootloader Mode. I've tried different files of official firmware in order to flash them via fastboot, but it's no use... it just says "Preflash validation failed", and so on.
When I enter the command getvar_all, this is what it shows:
C:\Users\IVAN\Sanders\Stock\Third>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.06(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(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: 229d978d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 881733DA00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 1
(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.06-0-g1e22c44
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
Finished. Total time: 0.250s
I've noticed that both the CID and the IMEI are gonners, but as I can't flash anything, there's no way of trying the "Validus" method to restore the IMEI (which I've already done a couple of months ago, after the first root).
I've tried by setting my PC into Test Mode, so as to "skip" the validation of the flash images, but it shows the exact same message. RSD Lite won't even show my device when plugged. I couldn't erase user data, cache or even system partitions, because it says "Permission denied".
These are some of the fastboot commands i've tried to reflash stock (I looked for the latest Oreo firmware, so as to be sure that I wasn't downgrading):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
exit
...always answering "REMOTE failure". I've tried to describe the problem as thoroughly as I could; I hope someone can gimme a hand :good:
Click to expand...
Click to collapse
friend I have the same problem, I think it is the firmware that is used, the one that should be used is the NPSS26.116-26-4

Matiasnck said:
friend I have the same problem, I think it is the firmware that is used, the one that should be used is the NPSS26.116-26-4
Click to expand...
Click to collapse
Hi Matias, thanks for answering. I've already tried with several firmware files, the latest one being SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml, always getting the same errors. Do you think that by using a specific file, the "Preflash valitation failed" errors should stop? I'll try again with that file you suggested, and see what happens... I hope it works; I'm not sure, but I think I've already tried that one.
The Moto drivers are allegedly ok, and I've downloaded again Minimal ADB, so I'm trying to convince myself those aren't the ones keeping me from reflashing.

Iv_Milh said:
Hi Matias, thanks for answering. I've already tried with several firmware files, the latest one being SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml, always getting the same errors. Do you think that by using a specific file, the "Preflash valitation failed" errors should stop? I'll try again with that file you suggested, and see what happens... I hope it works; I'm not sure, but I think I've already tried that one.
The Moto drivers are allegedly ok, and I've downloaded again Minimal ADB, so I'm trying to convince myself those aren't the ones keeping me from reflashing.
Click to expand...
Click to collapse
I still have the same problem, I will try a new computer, maybe that's it?

Matiasnck said:
I still have the same problem, I will try a new computer, maybe that's it?
Click to expand...
Click to collapse
The only way that by using another computer the error would stop, would be that the drivers in your current pc aren't the ones you're supposed to have, in my opinion. Try it, anyways... there's nothing to lose.

Hi , please try this and let me know if it works or not, thanks
https://github.com/laginimaineb/Alohamora?files=1

whodat711 said:
Hi , please try this and let me know if it works or not, thanks
https://github.com/laginimaineb/Alohamora?files=1
Click to expand...
Click to collapse
Can you explain what I should do with that?

Could you solve it?

Try lenovo smart assistant
https://support.lenovo.com/us/en/downloads/ds101291

whodat711 said:
Try lenovo smart assistant
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
I am new to this thread, but I found this and THANK YOU! I hope this will save my day!

whodat711 said:
Hi , please try this and let me know if it works or not, thanks
https://github.com/laginimaineb/Alohamora?files=1
Click to expand...
Click to collapse
Hi, thanks for the reply; could you please explain what I should do with that? I see the python files, but i'm not sure on how to use them.

whodat711 said:
Try lenovo smart assistant
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
I've already tried it, but so far it has failed to whether recognize my device, or just got stuck in the process of reading it. Motorola Device Manager, Software Upgrade Assistant, RSD Lite, Wondershare... none of them have worked for me.

base band lost after brick

irst sorry for english i'm using the translator
so let's go, i was running on my z3 android pie 9, after rooting the device and making a change to the more specific nvram folder in the mp0b_001 file, and making the hardreset by twrp gave it soft brick, i did update and now it doesn't recognize chip does not even find wifi and for inconvenience frp is active
when i try to flesha other rom i get the error "(bootloader) flash permission denied"
the return of my getvar and this:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0048275417
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: E6583D07
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354106092734554
(bootloader) meid:
(bootloader) date: 06-26-2018
(bootloader) sku: XT1929-5
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20118
(bootloader) battery-voltage: 4176
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-2/7699:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.3.beckham.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gcc5f412 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Mar 27 12:33:10 CDT 2019
(bootloader) git:abl: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) git:xbl: MBM-3.0-beckham_retail-d286d94-190327
(bootloader) gitmic: MBM-3.0-beckham_retail-d286d94-190327
(bootloader) git:rpm: MBM-3.0-beckham_retail-4696e9e-190327
(bootloader) git:tz: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:hyp: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:devcfg: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib64: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:keymaster: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) gitrov: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:storsec: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.107s
already tried almost everything and nothing box does not recognize bootloader locked and stuck in frp

SM0K1NG said:
irst sorry for english i'm using the translator
so let's go, i was running on my z3 android pie 9, after rooting the device and making a change to the more specific nvram folder in the mp0b_001 file, and making the hardreset by twrp gave it soft brick, i did update and now it doesn't recognize chip does not even find wifi and for inconvenience frp is active
when i try to flesha other rom i get the error "(bootloader) flash permission denied"
the return of my getvar and this:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0048275417
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: E6583D07
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354106092734554
(bootloader) meid:
(bootloader) date: 06-26-2018
(bootloader) sku: XT1929-5
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20118
(bootloader) battery-voltage: 4176
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-2/7699:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.3.beckham.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gcc5f412 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Mar 27 12:33:10 CDT 2019
(bootloader) git:abl: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) git:xbl: MBM-3.0-beckham_retail-d286d94-190327
(bootloader) gitmic: MBM-3.0-beckham_retail-d286d94-190327
(bootloader) git:rpm: MBM-3.0-beckham_retail-4696e9e-190327
(bootloader) git:tz: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:hyp: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:devcfg: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib64: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:keymaster: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) gitrov: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:storsec: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.107s
already tried almost everything and nothing box does not recognize bootloader locked and stuck in frp
Click to expand...
Click to collapse
I also have a Z3 and when I was rooted in it, gave soft brick and when I was upgrading putting a Stock Rom ended up zeroing IMEI and no longer works WiFi if anyone can help me please I'm desperate. :crying:

First, Make sure to use Google's official adb & fastboot executables, do not use other variants = https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Second, Then make sure to set an active slot BEFORE you start flashing otherwise you will get permission denied. Here's a detailed explanation = https://forum.xda-developers.com/showpost.php?p=79673160&postcount=7
Third, if that doesn't work and you don't have backup of the EFS partition, you won't be able to recover it without activating warranty and that's pretty much it.

I solved this!
After trying all possible procedures and ROMS, and causing hard brick on my Moto Z3 Play several times, I solved the problem with a Sprint operator firmware. With it, I recovered the baseband, so wifi and network signal (SIM 1 and 2) went back to work.
This is the firmware:
XT1929-3_BECKHAM_SPRINT_9.0_PCWS29.85-36-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC (download)
Use these commands in fastboot mode:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Wait for the first boot (takes a few minutes) and check if you have fixed the problem.
If it is fixed, you can flash the latest firmware available for your device and region. I, for example, used the firmware XT1929-6_BECKHAM_RETBR_9.0_PPWS29.131-27-1-22.
Then, if you are unable to make other updates via OTA, use the Rescue and Smart Assistant (LMSA) program to update.
My Moto Z3 Play now has the latest firmware available and is working perfectly.

Loko_vr said:
After trying all possible procedures and ROMS, and causing hard brick on my Moto Z3 Play several times, I solved the problem with a Sprint operator firmware. With it, I recovered the baseband, so wifi and network signal (SIM 1 and 2) went back to work.
This is the firmware:
XT1929-3_BECKHAM_SPRINT_9.0_PCWS29.85-36-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC (download)
Use these commands in fastboot mode:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Wait for the first boot (takes a few minutes) and check if you have fixed the problem.
If it is fixed, you can flash the latest firmware available for your device and region. I, for example, used the firmware XT1929-6_BECKHAM_RETBR_9.0_PPWS29.131-27-1-22.
Then, if you are unable to make other updates via OTA, use the Rescue and Smart Assistant (LMSA) program to update.
My Moto Z3 Play now has the latest firmware available and is working perfectly.
Click to expand...
Click to collapse
Bro!
Thank you so freaking much!! It works amazingly good!

I have the same problem but my bootloader is blocked, I can't flash.

Moto x4-4 no señal no imei no radio

Hello, I wanted to ask for help, since my motorcycle x4 since I installed a system, the signal was lost and the wifi did not turn on but I installed a system that was for that version which is the xt1900-4 and recovered the wifi but did not recover the signal and the radio is off can you help me please oh and also my imei is on ¨0¨ baseband: (not found)

Oscar.J.T.G said:
Hello, I wanted to ask for help, since my motorcycle x4 since I installed a system, the signal was lost and the wifi did not turn on but I installed a system that was for that version which is the xt1900-4 and recovered the wifi but did not recover the signal and the radio is off can you help me please oh and also my imei is on ¨0¨
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
To make sure you have the correct codename and software channel for the device.
And post it here after you remove the IMEI
Some info about getvar here
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

Oscar.J.T.G said:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-a5ca046-190905
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY225264H7
(bootloader) cid: 0x0032
(bootloader) channelid: 0x29
(bootloader) uid: 418E6933
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 06-15-2018
(bootloader) sku: XT1900-4
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3961
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-a5ca046-190905
(bootloader) git:xbl: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) gitmic: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190905
(bootloader) git:tz: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:hyp: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:devcfg: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:keymaster: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) gitrov: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:storsec: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.094s
Click to expand...
Click to collapse
Ok, so
product: payton is the codename
ro.carrier: openmx is the software channel
ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret is the current software version
sku: XT1900-4 is the model #
securestate: flashing_unlocked is bootloader unlocked
So it looks like this is the firmware you should flash
https://mirrors.lolinet.com/firmware/moto/payton/official/OPENMX/
You can flash with fastboot or mfastboot.exe
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
or try LMSA's Flash Rescue option (my preferred method)
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
if using fastboot or mfastboot.exe
command should be like
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
but could be a little different so check the flashfile.xml
You may need to also run
Code:
fastboot erase userdata
mfastboot.exe commands are the same just use mfastboot.exe instead
Code:
mfastboot.exe erase userdata

sd_shadow said:
Ok, so
product: payton is the codename
ro.carrier: openmx is the software channel
ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret is the current software version
sku: XT1900-4 is the model #
securestate: flashing_unlocked is bootloader unlocked
So it looks like this is the firmware you should flash
https://mirrors.lolinet.com/firmware/moto/payton/official/OPENMX/
You can flash with fastboot or mfastboot.exe
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
or try LMSA's Flash Rescue option (my preferred method)
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
if using fastboot or mfastboot.exe
command should be like
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
but could be a little different so check the flashfile.xml
You may need to also run
Code:
fastboot erase userdata
mfastboot.exe commands are the same just use mfastboot.exe instead
Code:
mfastboot.exe erase userdata
Click to expand...
Click to collapse
Ready I installed that firmware and my moto x4 still has no imei signal ¨0¨
version-baseband: M660_7045.36.01.100q PAYTON_LATAM_CUST

Oscar.J.T.G said:
Ok, so
product: payton is the codename
ro.carrier: openmx is the software channel
ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret is the current software version
sku: XT1900-4 is the model #
securestate: flashing_unlocked is bootloader unlocked
So it looks like this is the firmware you should flash
https://mirrors.lolinet.com/firmware/moto/payton/official/OPENMX/
You can flash with fastboot or mfastboot.exe
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
or try LMSA's Flash Rescue option (my preferred method)
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
if using fastboot or mfastboot.exe
command should be like
but could be a little different so check the flashfile.xml
You may need to also run
mfastboot.exe commands are the same just use mfastboot.exe instead
Ready I installed that firmware and my moto x4 still has no imei signal ¨0¨baseband: (not found)
Click to expand...
Click to collapse
Try LMSA
Sent from my ali using XDA Labs

sd_shadow said:
Try LMSA
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
failed to match the connected device reconnect device then try again, that comes out on LMSA

Hardware or software problem?

I have a Moto Z3 Play (not rooted) with stock firmware. Phone started to freeze up (delayed reactions, system UI error, messages, etc). I restart the phone and it takes 25 mins for the phone to restart. I then do a factory reset, but after the reset the phone is still freezing up and taking 25 mins to restart. I then reflash the latest stock firmware for my phone via fastboot commands, but a fresh install does nothing. The phone is still freezing up and taking 25 mins to restart. Any suggestions?
Sent from my LGUS997 using XDA-Developers Legacy app

NardVa said:
I have a Moto Z3 Play (not rooted) with stock firmware. Phone started to freeze up (delayed reactions, system UI error, messages, etc). I restart the phone and it takes 25 mins for the phone to restart. I then do a factory reset, but after the reset the phone is still freezing up and taking 25 mins to restart. I then reflash the latest stock firmware for my phone via fastboot commands, but a fresh install does nothing. The phone is still freezing up and taking 25 mins to restart. Any suggestions?
Sent from my LGUS997 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sounds like hardware issue.
What does getvar all say?
Code:
fastboot getvar all
Which firmware version are you flashing?
Which commands are you using?
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Sounds like hardware issue.
What does getvar all say?
Code:
fastboot getvar all
Which firmware version are you flashing?
Which commands are you using?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Flashing firmware
XT1929-4_BECKHAM_RETUS_9.0_PPWS29.183-29-1-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (latest one for my phone)
I tried flashing earlier releases of the software but they all do the same thing.
I basically just ran down the commands in the flashfile.xml file.
I didn't get any error messages.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fasboot erase userdata
fastboot erase ddr
The getvar info is below.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-beckham_retail-d3390b3ac2-20
(bootloader) version-bootloader[1]: 0627
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZY225634PT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 14C22580
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351886090741478
(bootloader) meid:
(bootloader) date: 09-15-2018
(bootloader) sku: XT1929-4
(bootloader) carrier_sku: XT1929-4
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 3806
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 183-29-1-21/09dfb:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.491.23.beckham.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05900-sdm660.0
(bootloader) version-baseband: M636_30.77.01.101R BECKHAM_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gec1a370acdbf
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.
(bootloader) kernel.version[2]: x 20150123 (prerelease) (GCC) ) #1 SMP P
(bootloader) kernel.version[3]: REEMPT Sat Jun 27 03:02:22 CDT 2020
(bootloader) git:abl: MBM-3.0-beckham_retail-d3390b3ac2-200627
(bootloader) git:xbl: MBM-3.0-beckham_retail-0e3a02b40-200627
(bootloader) git:pmic: MBM-3.0-beckham_retail-0e3a02b40-200627
(bootloader) git:rpm: MBM-3.0-beckham_retail-cf74f0b-200627
(bootloader) git:tz: MBM-3.0-beckham_retail-96615c5a1-200627
(bootloader) git:hyp: MBM-3.0-beckham_retail-96615c5a1-200627
(bootloader) git:devcfg: MBM-3.0-beckham_retail-96615c5a1-200627
(bootloader) git:cmnlib: MBM-3.0-beckham_retail-96615c5a1-200627
(bootloader) git:cmnlib64: MBM-3.0-beckham_retail-96615c5a1-200627
(bootloader) git:keymaster: MBM-3.0-beckham_retail-96615c5a1-200627
(bootloader) git:prov: MBM-3.0-beckham_retail-96615c5a1-200627
(bootloader) git:storsec: MBM-3.0-beckham_retail-96615c5a1-200627
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.610s

NardVa said:
Sounds like hardware issue.
What does getvar all say?
Flashing firmware
XT1929-4_BECKHAM_RETUS_9.0_PPWS29.183-29-1-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (latest one for my phone)
I tried flashing earlier releases of the software but they all do the same thing.
I basically just ran down the commands in the flashfile.xml file.
I didn't get any error messages.
The getvar info is below.
Click to expand...
Click to collapse
Did you relock the bootloader?
You could try Lmsa's flash rescue option
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my payton_sprout using XDA Labs

After unlocking the bootloader and flashing different software versions with no luck (rule out software problem), I opened up a warranty repair with Motorola. I'm guessing the issue was hardware because they sent me a free replacement (different imei number from the phone I sent in).
Sent from my LGUS997 using XDA-Developers Legacy app