Database Develop

Q|XT1097 ATT Wont boot

Hey, Ive received the device from a friend after he tried to unlock frp lock. For some reason he flashed a different firmware and now the device is in a bootloop.
Getvar all:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: 6020
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: ***********
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 64BF660E0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: **********
(bootloader) meid:
(bootloader) date: 10-30-2014
(bootloader) sku: XT1097
(bootloader) iccid: *********
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Sep 13 18:56:47 UTC 2016"
[B](bootloader) ro.build.fingerprint[0]: motorola/victara_att/victara:5.1/L
(bootloader) ro.build.fingerprint[1]: PES23.32-21.9-8/5:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.23.221.8.victara_att[/B]
(bootloader) ro.build.version.full[1]: .att.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8974BP_42352121.25.09.24R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.4.42-gdc3b1f6 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Wed Sep 14 04:43:25 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V60.20-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.20-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V60.20-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.20-0-gc8cfdbe
(bootloader) aboot.git: git=MBM-NG-V60.20-0-g78a2c4f
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: att
all: listed above
finished. total time: 0.075s
After some reading and trying I understand that I cant downgrade or flash other cid.
The only firmware that does not give any error is :
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-8_cid1_CFC
with this script:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 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
pause
fastboot reboot
but even with this one the phone does not boot.
what else can I try ?

The bootloader is locked.
I think you cant flash via fastboot.
Have you try factory rest from recovery?

try to unlock bootloader via motorola website. flash TWRP

Bootloader cannot be unlocked so no custom solution, also cant boot to any mode except bootloader (recovery,qcom etc.. )

deadwolf666 said:
Bootloader cannot be unlocked so no custom solution, also cant boot to any mode except bootloader (recovery,qcom etc.. )
Click to expand...
Click to collapse
You cant see recovery?
If run motorola official app on windows hels you maybe.
Is your windows drivers ok?
I cant think something else.

papsr6 said:
You cant see recovery?
If run motorola official app on windows hels you maybe.
Is your windows drivers ok?
I cant think something else.
Click to expand...
Click to collapse
I can only see boot loader if I try to boot to recovery or normal I get bootloop.
Drivers are ok because the firmware did flash without errors.

Any thing I could try to boot the phone ?

Super Mega Hard Bricked

Guys
I had unlocked the bootloader and was using the Ressuration Remix a few days ago.
Yesterday i went to install the Stock PAYTON_OPW28.46-13. I made fastboot -w and run the script.
But there was an error and my script had the command: oem lock.
It happened that he did not pass the rom and blocked the bootloader. After that I can not install any ROMs.
I tried them all.
PAYTON_OPWS27.57-25-6-10
PAYTON_OPWS27.57-40-14
PAYTON_OPW28.46-13
PAYTON_OPWS27.57-40-17
I did not succeed. The message I have is:
sending 'bootloader' (9520 KB) ...
OKAY [0.278s]
writing 'bootloader' ...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0
I noticed something different in the bootloader.
The message is: flashing_locked.
- I do not have access to TWRP
- I do not have access to recovery stock
- I do not have access to the previous ROM (deleted everything)
I have access to fastboot
I have access to the option to unlock the bootloader, but when I put the code, the following message is:
Enable USB USB debbuguing <in development option> but I can not do it because I do not have a system!
https://drive.google.com/open?id=1SuJjDUcSPgfy7uzxkcTQYRA4jhQU2TL4
Anyone know what to do?

see if this helps.
https://forum.xda-developers.com/moto-x4/help/hard-bricked-how-enter-emergency-t3757472

What about reapplying for an unlock code, and re-unlocking the bootloader? I did that on my z2 Force when it happened.

slaytanic said:
What about reapplying for an unlock code, and re-unlocking the bootloader? I did that on my z2 Force when it happened.
Click to expand...
Click to collapse
When I try to unlock it, it asks me to enable the USb Debugging option in the developer settings ...

munchy_cool said:
see if this helps.
https://forum.xda-developers.com/moto-x4/help/hard-bricked-how-enter-emergency-t3757472
Click to expand...
Click to collapse
It sounds a bit tricky but what I realized is that my phone is recognized as Fastboot Payton S and I can not install it as a Qualcomm driver

IVANWB said:
It sounds a bit tricky but what I realized is that my phone is recognized as Fastboot Payton S and I can not install it as a Qualcomm driver
Click to expand...
Click to collapse
try flashing factory firmware from fastboot?

munchy_cool said:
try flashing factory firmware from fastboot?
Click to expand...
Click to collapse
I've tried all the images, I always receive (bootloader) flash permission denied
success when installing the qualcomm drivers.
When I run blank-flash script, i get the message:
"Waiting for device"

If I try,
fastboot flashing unlock
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.013s]
finished. total time: 0.014s

I dont know what else to say.
you locked the bootloader with developer settings turned off.
I personally dont have a solution for this. let's hope someone else has.

you locked the bootloader with developer settings turned off.[/QUOTE said:
Exactly, I've tried everything ...
Click to expand...
Click to collapse

munchy_cool said:
I dont know what else to say.
you locked the bootloader with developer settings turned off.
I personally dont have a solution for this. let's hope someone else has.
Click to expand...
Click to collapse
Exactly, I've tried everything ...

IVANWB said:
I've tried all the images, I always receive (bootloader) flash permission denied
success when installing the qualcomm drivers.
When I run blank-flash script, i get the message:
"Waiting for device"
Click to expand...
Click to collapse
Have you already tried the emergency fastboot?
This worked for me when my x4 bricked.

jonathangrag said:
Have you already tried the emergency fastboot?
This worked for me when my x4 bricked.
Click to expand...
Click to collapse
Hello everyone, friend what are the commands to enter this mode?

pauloreducinobr said:
Hello everyone, friend what are the commands to enter this mode?
Click to expand...
Click to collapse
It's the same mode, but you use a different software version. Here it is.

try entering in the "cmd" command console this:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot bluetooth flash BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
If the error still appears remove "mfastboot flash oem oem.img"..who knows, maybe it works !

I sent my device yesterday for the warranty.
They said it was necessary to change the plate and the guarantee will cover.
Thanks for the help.

IVANWB said:
I sent my device yesterday for the warranty.
They said it was necessary to change the plate and the guarantee will cover.
Thanks for the help.
Click to expand...
Click to collapse
Wow, they will really cover it? Que sorte! I would not expect that
(saw your post on G+ haha)

Daaaaniel said:
try entering in the "cmd" command console this:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot bluetooth flash BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
If the error still appears remove "mfastboot flash oem oem.img"..who knows, maybe it works !
Click to expand...
Click to collapse
Can you send me the stock boot.img? I need it to examine how it works, and the full firmware will take ages to download. Thank you.
Broadcasted from Zeta Reticuli

Softbricked
So, I have a similar problem, but I can't access anything, because Motorola says "untrusted device" and this bla bla bla. The problem is the ROM, I can't found the original ROM of this phone is in use (XT1900-6). The flashing state is set to locked, and is no possible to unlock OEM. The Qualcomm drivers don't worked here, maybe I need a fresh install of Windows 10.
Anybody have a ideia to fix that?
variables:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-171216
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 004294------
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 0E141779
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: --------------------------
(bootloader) meid:
(bootloader) date: 01-25-2018
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3843
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPW27
(bootloader) ro.build.fingerprint[1]: .57-40/52:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.31.52.payton.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M660_7036.16.01.69R PAYTON_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-ge3f7ffe (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Sat Dec 16 07:34:49 CST 2017
(bootloader) git:abl: MBM-3.0-uefi-641a15b-171216
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-171216
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-171216
(bootloader) git:rpm: MBM-3.0-uefi-245b046-171216
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (343)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
Click to expand...
Click to collapse
Edit: Removed smiles on text.

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.

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.

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