Database Info

OTA Update after RSA broke my moto g7 power x1955-2?

I'm at a loss. My phone stopped booting when an OTA update was applied and then my phone battery died. I downloaded Rescue and Smart Assistant, and it immediately recognized my phone and proceeded to repair the phone. It booted just fine and I then used it all day. Again an OTA update came in, and I accepted it. I continued using my phone throughout the day, but when I went to reboot, was presented with the following error:
Code:
SSM: Android image roll back: 12, 13
failed to validate boot image
failed to pass validation, backup to fastboot
I figured I'd go back to the Rescue and Smart Assistant, but it is now telling me I have an unsupported device, whether I try to automatically detect the phone or enter the X1955-2.
My bootloader is not unlocked, I haven't rooted the phone and is otherwise all stock from Amazon. What can I do from here? I cannot afford a new phone and my life is hard without access to one.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0a6142d67e0-200508
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(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: ZY323TZHD9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: CC606A9F00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: **
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-11-2019
(bootloader) sku: XT1955-2
(bootloader) carrier_sku: XT1955-2
(bootloader) battid: SB18C28957
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 26 7:31:58 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QPOS30.52-
(bootloader) ro.build.fingerprint[1]: 29-2/397fb:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_41.178.01.156R OCEAN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Sun May 24 10:3
(bootloader) kernel.version[3]: 3:41 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-315bc626c6-200508
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-200508
(bootloader) tz.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) devcfg.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) keymaster.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) prov.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) aboot.git: MBM-2.1-ocean_retail-0a6142d67e0-200508
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retla
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P0ME
all: listed above
finished. total time: 0.021s

nickrfroberts said:
I'm at a loss. My phone stopped booting when an OTA update was applied and then my phone battery died. I downloaded Rescue and Smart Assistant, and it immediately recognized my phone and proceeded to repair the phone. It booted just fine and I then used it all day. Again an OTA update came in, and I accepted it. I continued using my phone throughout the day, but when I went to reboot, was presented with the following error:
Code:
SSM: Android image roll back: 12, 13
failed to validate boot image
failed to pass validation, backup to fastboot
I figured I'd go back to the Rescue and Smart Assistant, but it is now telling me I have an unsupported device, whether I try to automatically detect the phone or enter the X1955-2.
My bootloader is not unlocked, I haven't rooted the phone and is otherwise all stock from Amazon. What can I do from here? I cannot afford a new phone and my life is hard without access to one.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0a6142d67e0-200508
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(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: ZY323TZHD9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: CC606A9F00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: **
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-11-2019
(bootloader) sku: XT1955-2
(bootloader) carrier_sku: XT1955-2
(bootloader) battid: SB18C28957
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 26 7:31:58 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QPOS30.52-
(bootloader) ro.build.fingerprint[1]: 29-2/397fb:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_41.178.01.156R OCEAN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Sun May 24 10:3
(bootloader) kernel.version[3]: 3:41 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-315bc626c6-200508
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-200508
(bootloader) tz.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) devcfg.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) keymaster.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) prov.git: MBM-2.1-ocean_retail-03d85fce32-200508
(bootloader) aboot.git: MBM-2.1-ocean_retail-0a6142d67e0-200508
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retla
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P0ME
all: listed above
finished. total time: 0.021s
Click to expand...
Click to collapse
Could try RSD Lite if you have a pc running something lower than 10 like windows 7.
What is the firmware name rsa used?
It will be in something like c/program data/lmsa/downloads/romfiles
Sent from my Moto E (4) using Tapatalk

Help: Repair reboot after wipe failed

I tried to install the official TWRP/Magisk. Everything seem to be ok (I unlocked it) until I was on the step of "Format Data" on TWRP for deencryption. No commands showed and the loading bar was moving and moving.... I waited 8 hours but nothing seem to be happening. I turned off the phone and now it just reboots in loop. I am still able to access both the Fastboot and TWRP. When I access to TWRP first reboots (I guess it change the slot from A to B, because TWRP seems to be working only with B) then it access normally.
Please help I just want to fix the phone even if I dont root it. I tried to use the Lenovo Rescue tool but just shows the message "Unable to match the appropiate firmware. Some key information cannot be read from device".
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-6a359c146ce-200818
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB SAMSUNG KLUDG4U1EA-B0C1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=01 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: ZY3263GPSQ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x03
(bootloader) uid: 0000010C8F2A98FA0000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1970-2
(bootloader) carrier_sku: XT1970-2
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Sep 21 16:40:40 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/kane_amx/kane_sprout:10/Q
(bootloader) ro.build.fingerprint[1]: SAS30.62-28-8/ea919:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.samsung: 20190525
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2881431
(bootloader) kernel.version[0]: Linux version 4.14.113-user+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (https://and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Tue Aug 18 05:39:54 CDT 2020
(bootloader) bootloader.git: MBM-2.2-kane_retail-6a359c146ce-200818
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxmx
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.597s
As you can see my phone is the T1970-2 from Mexico. I wanted to try some firmware I found when I google it but i dont want to mess it . Thanks in advance.

alankat said:
I tried to install the official TWRP/Magisk. Everything seem to be ok (I unlocked it) until I was on the step of "Format Data" on TWRP for deencryption. No commands showed and the loading bar was moving and moving.... I waited 8 hours but nothing seem to be happening. I turned off the phone and now it just reboots in loop. I am still able to access both the Fastboot and TWRP. When I access to TWRP first reboots (I guess it change the slot from A to B, because TWRP seems to be working only with B) then it access normally.
Please help I just want to fix the phone even if I dont root it. I tried to use the Lenovo Rescue tool but just shows the message "Unable to match the appropiate firmware. Some key information cannot be read from device".
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-6a359c146ce-200818
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB SAMSUNG KLUDG4U1EA-B0C1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=01 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: ZY3263GPSQ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x03
(bootloader) uid: 0000010C8F2A98FA0000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1970-2
(bootloader) carrier_sku: XT1970-2
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Sep 21 16:40:40 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/kane_amx/kane_sprout:10/Q
(bootloader) ro.build.fingerprint[1]: SAS30.62-28-8/ea919:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.samsung: 20190525
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2881431
(bootloader) kernel.version[0]: Linux version 4.14.113-user+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (https://and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Tue Aug 18 05:39:54 CDT 2020
(bootloader) bootloader.git: MBM-2.2-kane_retail-6a359c146ce-200818
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxmx
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.597s
As you can see my phone is the T1970-2 from Mexico. I wanted to try some firmware I found when I google it but i dont want to mess it . Thanks in advance.
Click to expand...
Click to collapse
In my youtube channel Eufracio lopez available a video called Start up Failed Motorola One Vision

hello, Did any one have persist partition for xt1970-5. after flash linageos im lost baseband and imei.
Best regards
Rafal

ive bricked my phone help

hey guys im new to android and ive got my first one so i had unlocked the bootloader with ease went to root with magisk and then it went sideways very fast and now my phone wont boot properly getting stuck in a loop or just failing to boot at all saying there is no bootable a/b slot
i need help this is my phones info i got this using the adb command fastboot getarv or something like that
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiar_reteu-3b6d53a311-201102
(bootloader) product: sofiar
(bootloader) board: sofiar
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY22BFD473
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: EA161473
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805259264
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359095106449611
(bootloader) imei2: 359095106449629
(bootloader) meid:
(bootloader) date: 11-09-2020
(bootloader) sku: XT2041-3
(bootloader) carrier_sku: XT2041-3
(bootloader) battid: SB18C57587
(bootloader) battery-voltage: 3795
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiar_reteu/sofiar:10/QP
(bootloader) ro.build.fingerprint[1]: ES30.79-124-7/93db12:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Tue Jun 30 12:
(bootloader) kernel.version[3]: 14:07 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofiar_reteu-61355838c-201102
(bootloader) git:xbl_config: MBM-3.0-sofiar_reteu-61355838c-201102
(bootloader) git:rpm: MBM-3.0-sofiar_reteu-ffcccb0-201102
(bootloader) git:tz: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:hyp: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:devcfg: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:cmnlib: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:cmnlib64: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:keymaster: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) gitrov: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:abl: MBM-3.0-sofiar_reteu-3b6d53a311-201102
(bootloader) git:qupfw: MBM-3.0-sofiar_reteu-f848623-201102
(bootloader) git:uefisecapp: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C64207
all: listed above
finished. total time: 1.832s
i need help with what to do next ive got it boot once but it got stuck on the hello start screen and when i clicked nothing happened ive done my research about it but still to no prevail
so any help to fix my device would be much appereciated
p.s i dont anything about the stock rom i need for my device either

brandon213145 said:
hey guys im new to android and ive got my first one so i had unlocked the bootloader with ease went to root with magisk and then it went sideways very fast and now my phone wont boot properly getting stuck in a loop or just failing to boot at all saying there is no bootable a/b slot
i need help this is my phones info i got this using the adb command fastboot getarv or something like that
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiar_reteu-3b6d53a311-201102
(bootloader) product: sofiar
(bootloader) board: sofiar
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY22BFD473
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: EA161473
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805259264
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359095106449611
(bootloader) imei2: 359095106449629
(bootloader) meid:
(bootloader) date: 11-09-2020
(bootloader) sku: XT2041-3
(bootloader) carrier_sku: XT2041-3
(bootloader) battid: SB18C57587
(bootloader) battery-voltage: 3795
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiar_reteu/sofiar:10/QP
(bootloader) ro.build.fingerprint[1]: ES30.79-124-7/93db12:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Tue Jun 30 12:
(bootloader) kernel.version[3]: 14:07 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofiar_reteu-61355838c-201102
(bootloader) git:xbl_config: MBM-3.0-sofiar_reteu-61355838c-201102
(bootloader) git:rpm: MBM-3.0-sofiar_reteu-ffcccb0-201102
(bootloader) git:tz: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:hyp: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:devcfg: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:cmnlib: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:cmnlib64: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:keymaster: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) gitrov: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) git:abl: MBM-3.0-sofiar_reteu-3b6d53a311-201102
(bootloader) git:qupfw: MBM-3.0-sofiar_reteu-f848623-201102
(bootloader) git:uefisecapp: MBM-3.0-sofiar_reteu-9b332894-201102
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C64207
all: listed above
finished. total time: 1.832s
i need help with what to do next ive got it boot once but it got stuck on the hello start screen and when i clicked nothing happened ive done my research about it but still to no prevail
so any help to fix my device would be much appereciated
p.s i dont anything about the stock rom i need for my device either
Click to expand...
Click to collapse
Try LMSA'S flash rescue option
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
If that works use that new boot.img with Magisk
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

sd_shadow said:
Try LMSA'S flash rescue option
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
If that works use that new boot.img with Magisk
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Hey thanks for the help it worked and now I've rooted my phone proberly

"Dynamic System Update" package bricked phone

I installed a "Dynamic System Update" package and after rebooting the OS is not detected, bootloader (Vol D + Power) opens, but start and recovery lead to the same missing os screen.
Is there some way to fix this? I need my phone working
I can get to fastboot but not adb, this is `fastboot getvar all`
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-df63f3de4a8-210524
(bootloader) product: denver
(bootloader) board: denver
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM5V8001DM-B622 FV=2702 WB=2048
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_MANNAR 1.1
(bootloader) serialno: ZY22CKXBPJ
(bootloader) cid:
(bootloader) channelid: 0x99
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 788201472
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 06-16-2021
(bootloader) sku: XT2131-1
(bootloader) carrier_sku: XT2131-1
(bootloader) battid: SB18D00294
(bootloader) battery-voltage: 4333
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: boost
(bootloader) ro.build.fingerprint[0]: motorola/denver_global/denver:11/R
(bootloader) ro.build.fingerprint[1]: RE31.Q2-11-52/a40ec:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.9.16.r1-03500-MANNAR.0
(bootloader) version-baseband[0]: M4350_HI405_19.533.01.79R DENVER_BOOST
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 5.4.61-moto-gfa1749a591f9
(bootloader) kernel.version[1]: ([email protected]) (Android (6443078
(bootloader) kernel.version[2]: based on r383902) clang version 11.0.1
(bootloader) kernel.version[3]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[4]: ain/llvm-project b397f81060ce6d701042b78
(bootloader) kernel.version[5]: 2172ed13bee898b79), LLD 11.0.1 (/buildbo
(bootloader) kernel.version[6]: t/tmp/tmp6_m7QH b397f81060ce6d701042b782
(bootloader) kernel.version[7]: 172ed13bee898b79)) #1 SMP PREEMPT Mon Ma
(bootloader) kernel.version[8]: y 24 04:24:01 CDT 2021
(bootloader) git:xbl: MBM-3.0-uefi-71c7a1ab-210524
(bootloader) git:xbl_config: MBM-3.0-uefi-71c7a1ab-210524
(bootloader) git:abl: MBM-3.0-uefi-df63f3de4a8-210524
(bootloader) git:rpm: MBM-3.0-uefi-1573f88-210524
(bootloader) git:tz: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:hyp: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:devcfg: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:keymaster: MBM-3.0-uefi-9731016-210524
(bootloader) git:storsec: MBM-3.0-uefi-9731016-210524
(bootloader) git:uefisecapp: MBM-3.0-uefi-9731016-210524
(bootloader) gitrov: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:qupfw: MBM-3.0-uefi-7b29c10-210524
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C93368
(bootloader) primary-display: auo_nt36675_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.159s
Click to expand...
Click to collapse

ShayBox said:
I installed a "Dynamic System Update" package and after rebooting the OS is not detected, bootloader (Vol D + Power) opens, but start and recovery lead to the same missing os screen.
Is there some way to fix this? I need my phone working
I can get to fastboot but not adb, this is `fastboot getvar all`
Click to expand...
Click to collapse
The bootloader is locked, I doubt it can be fixed.

A slightly bigger doubt. How is the device detected as a PVT??
You can also just go to recovery and send us an image to show what it says , maybe the Lenovo Motorola Smart Assistant will help (QFIL flash tool with a good looking UI for Lenovo and moto devices , destroyed my tab due to the Lenovo Smart Assistant installing the firmware in a wrong method causing failures! but lets hope yours will survive!)

Slot b retry count is 0 , we could retry to set slot b as primary slot it might just work! but locked bootloaders don't allow this.... maybe just maybe you can ask Moto about this and they might be able to help , the device is QCOM based so QFIL should work (Lenovo Smart Assistant should also work????)

Seems lenovo moto smart assistant isn't working because support.lenovo.com is down until tomorrow.
Can the device be unlocked like this? or is that a bad idea.
I just got this phone 2 days ago, bought it after breaking my old free phone screen

ShayBox said:
Seems lenovo moto smart assistant isn't working because support.lenovo.com is down until tomorrow.
Can the device be unlocked like this? or is that a bad idea.
I just got this phone 2 days ago, bought it after breaking my old free phone screen
Click to expand...
Click to collapse
I doubt LMSA can help, it pulls info from the phone to match firmware.
Getvar all doesn't show the info needed, so you would just get an error from LMSA.
You should try Moto support

sd_shadow said:
I doubt LMSA can help, it pulls info from the phone to match firmware.
Getvar all doesn't show the info needed, so you would just get an error from LMSA.
You should try Moto support
Click to expand...
Click to collapse
support.motorola.com is also broken, but not for maintenance so who knows how long that will take to work again, this sucks...
EDIT: Its back online, I'll try it

IT WORKED! I used the updated lenovo software and it worked!

[CLOSED] Moto G7 Power (stock) fails to boot

I posted this problem over on the Moto G7 Power Questions & Answers forum which was probably the wrong place so re-postings here.
My son has a completely standard Moto G7 Power which has suddenly decided not to boot up. When power button is pressed it displays the Moto M logo screen for a while, vibrates and then powers off. Charging function and display works fine. The phone has not been modded in any way since new - the only change was probably an OTA update from android 9 to 10.
I can get into fastboot and recovery modes on the phone. Searching around it seems from other threads that it should be possible to recover phone by reflashing appropriate stock rom (this is UK version XT1955-4). However I am not having any success. I have tried both Lenovo Rescue LMSA and RSD Lite. Both seem to go through the process OK but when it comes to end and they reboot phone it behaves exactly as before.
One point I am not clear on is whether the phone must be oem unlocked to perform a reflash? I have seen this question asked several times in other threads but could find no answer provided. Some posts suggest that reflashing stock rom should work even with oem lock on provided it is the same (or later version?) as current rom on phone?
The phone is currently oem locked according to fastboot screen. I know how to unlock using developer option and Motorola supplied unlock code etc. but obviously I cannot get into android settings as phone currently does not boot.
The fastboot getvar is below.
Spoiler
F:\AndroidADK>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-cfdb645cf1d-210201
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(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: ZY3274FD52
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: F53196C300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ********************
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-07-2019
(bootloader) sku: XT1955-4
(bootloader) carrier_sku: XT1955-4
(bootloader) battid: SB18C28957
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 10 15: 6:39 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ocean_reteu/ocean:10/QPOS
(bootloader) ro.build.fingerprint[1]: 30.52-29-7-6/7287f:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_43.192.01.165R OCEAN_ROW_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Mon Feb 1 08:18
(bootloader) kernel.version[3]: :38 CST 2021
(bootloader) sbl1.git: MBM-2.1-ocean_retail-315bc626c6-210201
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-210201
(bootloader) tz.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) devcfg.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) keymaster.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) prov.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) aboot.git: MBM-2.1-ocean_retail-cfdb645cf1d-210201
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P7SP
all: listed above
Finished. Total time: 0.114s
Additional info :-
Obviously tried factory reset, cache wipe etc.
Bootloader gives following message:-
Start Up Failed .... Use Software Repair Assistant.... etc.
AP Fastboot Flash Mode (Secure)
SSM: Andorid image roll back: 19,20
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
Any suggestions folks?

dalek1999 said:
I posted this problem over on the Moto G7 Power Questions & Answers forum which was probably the wrong place so re-postings here.
My son has a completely standard Moto G7 Power which has suddenly decided not to boot up. When power button is pressed it displays the Moto M logo screen for a while, vibrates and then powers off. Charging function and display works fine. The phone has not been modded in any way since new - the only change was probably an OTA update from android 9 to 10.
I can get into fastboot and recovery modes on the phone. Searching around it seems from other threads that it should be possible to recover phone by reflashing appropriate stock rom (this is UK version XT1955-4). However I am not having any success. I have tried both Lenovo Rescue LMSA and RSD Lite. Both seem to go through the process OK but when it comes to end and they reboot phone it behaves exactly as before.
One point I am not clear on is whether the phone must be oem unlocked to perform a reflash? I have seen this question asked several times in other threads but could find no answer provided. Some posts suggest that reflashing stock rom should work even with oem lock on provided it is the same (or later version?) as current rom on phone?
The phone is currently oem locked according to fastboot screen. I know how to unlock using developer option and Motorola supplied unlock code etc. but obviously I cannot get into android settings as phone currently does not boot.
The fastboot getvar is below.
Spoiler
F:\AndroidADK>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-cfdb645cf1d-210201
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(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: ZY3274FD52
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: F53196C300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ********************
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-07-2019
(bootloader) sku: XT1955-4
(bootloader) carrier_sku: XT1955-4
(bootloader) battid: SB18C28957
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 10 15: 6:39 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ocean_reteu/ocean:10/QPOS
(bootloader) ro.build.fingerprint[1]: 30.52-29-7-6/7287f:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_43.192.01.165R OCEAN_ROW_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Mon Feb 1 08:18
(bootloader) kernel.version[3]: :38 CST 2021
(bootloader) sbl1.git: MBM-2.1-ocean_retail-315bc626c6-210201
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-210201
(bootloader) tz.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) devcfg.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) keymaster.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) prov.git: MBM-2.1-ocean_retail-aec28c6375-210201
(bootloader) aboot.git: MBM-2.1-ocean_retail-cfdb645cf1d-210201
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P7SP
all: listed above
Finished. Total time: 0.114s
Additional info :-
Obviously tried factory reset, cache wipe etc.
Bootloader gives following message:-
Start Up Failed .... Use Software Repair Assistant.... etc.
AP Fastboot Flash Mode (Secure)
SSM: Andorid image roll back: 19,20
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
Any suggestions folks?
Click to expand...
Click to collapse
@dalek1999 Thread closed as duplicate of
Moto G7 Power (unmodified) start up sticks on Moto logo screen
My son has a completely standard Moto G7 Power which has suddenly decided not to boot up. When power button is pressed it displays the Moto M logo screen for a while, vibrates and then powers off. Charging function and display works fine. The...
forum.xda-developers.com
I've moved this now closed thread from the development section, for which it didn't qualify, to Q&A; additionally, I placed your log into a spoiler for better reading and scrolling experiences. Prior to your next posting, please read all guidances and announcements that are stuck at the top of each section like
READ THIS FIRST - Development Rules
Rules for Posting in the Development Forum The following are a list of topics that we allow in the development forum [DEV] - Development for any special projects or Apps [ROM] - Custom ROMs [KERNEL] - Custom Kernels When possible please...
forum.xda-developers.com
And I well remembered your still open thread because I moved that from "GND" to Q&A just 5 days ago.
Please also review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! If you think you misplaced a thread simply report the thread including your suggestion where it should go to. Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator