Moto G8+ : No O/S, internal storage Encrypted, TWRP frozen screen. Pls help - General Questions and Answers

Hi everyone, I wanted to install Lineage OS on my Moto G8 Plus.
Followed guides that allowed me to Unlock Bootloader, to Root the phone and finally flash TWRP 3.5_0_10-0
All well until I Advanced Wiped (with TWRP) the phone and selected the folders System, Data and Vendor.
Now my issue is that recovery mode brings me to TWRP but the screen is completely frozen, can't tap on anything whatsoever so that's gone.
If I plug my phone into my laptop (Ubuntu) the internal storage comes up as fully gibberish so I imagine it's encrypted.
I don't know what to do next. I am not that experienced with commands that switch slots and all that. This is what getvar all gives me:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-7326ad2e6a-210301
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROWN
(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: ZY227HRQRK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 032952C5
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805263360
(bootloader) reason: Volume down key pressed
(bootloader) imei: 357209104685090
(bootloader) imei2: 357209104685108
(bootloader) meid:
(bootloader) date: 06-10-2020
(bootloader) sku: XT2019-1
(bootloader) carrier_sku: XT2019-1
(bootloader) battid: SB18C52858
(bootloader) battery-voltage: 3839
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: timit
(bootloader) ro.build.fingerprint[0]: motorola/doha_reteu_n/doha_n:10/QP
(bootloader) ro.build.fingerprint[1]: IS30.28-Q3-28-26-4-1-3/f0a9a:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.45R DOHA_ROWNDSDS_CUST
(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 Sat Apr 10 04:
(bootloader) kernel.version[3]: 04:10 CDT 2021
(bootloader) git:xbl: MBM-3.0-doha_retail-f16f9625d-210301
(bootloader) git:xbl_config: MBM-3.0-doha_retail-f16f9625d-210301
(bootloader) git:rpm: MBM-3.0-doha_retail-cea405b-210301
(bootloader) git:tz: MBM-3.0-doha_retail-567e196d-210301
(bootloader) git:hyp: MBM-3.0-doha_retail-567e196d-210301
(bootloader) git:devcfg: MBM-3.0-doha_retail-567e196d-210301
(bootloader) git:cmnlib: MBM-3.0-doha_retail-567e196d-210301
(bootloader) git:cmnlib64: MBM-3.0-doha_retail-567e196d-210301
(bootloader) git:keymaster: MBM-3.0-doha_retail-567e196d-210301
(bootloader) gitrov: MBM-3.0-doha_retail-567e196d-210301
(bootloader) git:abl: MBM-3.0-doha_retail-7326ad2e6a-210301
(bootloader) git:qupfw: MBM-3.0-doha_retail-25b246c-210301
(bootloader) git:uefisecapp: MBM-3.0-doha_retail-567e196d-210301
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C71286
Click to expand...
Click to collapse

Related

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

moto g8 power softbricked

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

Question Help with Soft Brick

I was trying to restore my G Stylus 5g. I flashed the stock rom with LMSA and then attempted to relock the bootloader. Now when the phone starts up it says that it has no OS and just reboots to fastboot. I tried running LMSA and it gets about 35% done and the throws an error about single partition. I downloaded the stock rom from lolinet and tried to manually flash but get permission denied errors. I have seen similar users with this issue and the problem was that the firmware version was different from the software channel my getvar all output shows that both the software channel and the firmware version is RETUS.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-b5c341d0203-220831
(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: 256GB MICRON MT256GASAO8U21 FV=0609 WB=2048
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_MANNAR 1.1
(bootloader) serialno: ZY22C8XLQM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: D683CFFF
(bootloader) token: inactive
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 05-20-2021
(bootloader) sku: XT2131-1
(bootloader) carrier_sku: XT2131-1
(bootloader) battid: SB18D01192
(bootloader) battery-voltage: 3689
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/denver_global/denver:11/R
(bootloader) ro.build.fingerprint[1]: RES31.Q2-11-66-10/f33db7:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.16.r1-03500-MANNAR.0
(bootloader) version-baseband: M4350_HI405_19.533.01.95R DENVER_NA_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-gb5d4f8e724aa
(bootloader) kernel.version[1]: ([email protected]) (Android (6573524
(bootloader) kernel.version[2]: based on r383902b) clang version 11.0.2
(bootloader) kernel.version[3]: (https://android.googlesource.com/toolc
(bootloader) kernel.version[4]: hain/llvm-project b397f81060ce6d701042b7
(bootloader) kernel.version[5]: 82172ed13bee898b79), LLD 11.0.2 (/buildb
(bootloader) kernel.version[6]: ot/tmp/tmpF3FjA8 b397f81060ce6d701042b78
(bootloader) kernel.version[7]: 2172ed13bee898b79)) #1 SMP PREEMPT Mon J
(bootloader) kernel.version[8]: an 31 06:03:39 CST 2022
(bootloader) git:xbl: MBM-3.0-uefi-286ca43aa-220831
(bootloader) git:xbl_config: MBM-3.0-uefi-286ca43aa-220831
(bootloader) git:abl: MBM-3.0-uefi-b5c341d0203-220831
(bootloader) git:rpm: MBM-3.0-uefi-8408d804-220831
(bootloader) git:tz: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:hyp: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:devcfg: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:keymaster: MBM-3.0-uefi-d9ee9c15-220831
(bootloader) git:storsec: MBM-3.0-uefi-d9ee9c15-220831
(bootloader) git:uefisecapp: MBM-3.0-uefi-d9ee9c15-220831
(bootloader) gitrov: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:qupfw: MBM-3.0-uefi-43fe43f-220831
(bootloader) frp-state: no protection (0)
(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: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D06412
(bootloader) primary-display: auo_nt36675_fhd_vid
(bootloader) secondary-display:
(bootloader) fdr-allowed: yes
robertr1229 said:
I was trying to restore my G Stylus 5g. I flashed the stock rom with LMSA and then attempted to relock the bootloader. Now when the phone starts up it says that it has no OS and just reboots to fastboot. I tried running LMSA and it gets about 35% done and the throws an error about single partition. I downloaded the stock rom from lolinet and tried to manually flash but get permission denied errors. I have seen similar users with this issue and the problem was that the firmware version was different from the software channel my getvar all output shows that both the software channel and the firmware version is RETUS.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-b5c341d0203-220831
(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: 256GB MICRON MT256GASAO8U21 FV=0609 WB=2048
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_MANNAR 1.1
(bootloader) serialno: ZY22C8XLQM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: D683CFFF
(bootloader) token: inactive
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 05-20-2021
(bootloader) sku: XT2131-1
(bootloader) carrier_sku: XT2131-1
(bootloader) battid: SB18D01192
(bootloader) battery-voltage: 3689
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/denver_global/denver:11/R
(bootloader) ro.build.fingerprint[1]: RES31.Q2-11-66-10/f33db7:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.16.r1-03500-MANNAR.0
(bootloader) version-baseband: M4350_HI405_19.533.01.95R DENVER_NA_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-gb5d4f8e724aa
(bootloader) kernel.version[1]: ([email protected]) (Android (6573524
(bootloader) kernel.version[2]: based on r383902b) clang version 11.0.2
(bootloader) kernel.version[3]: (https://android.googlesource.com/toolc
(bootloader) kernel.version[4]: hain/llvm-project b397f81060ce6d701042b7
(bootloader) kernel.version[5]: 82172ed13bee898b79), LLD 11.0.2 (/buildb
(bootloader) kernel.version[6]: ot/tmp/tmpF3FjA8 b397f81060ce6d701042b78
(bootloader) kernel.version[7]: 2172ed13bee898b79)) #1 SMP PREEMPT Mon J
(bootloader) kernel.version[8]: an 31 06:03:39 CST 2022
(bootloader) git:xbl: MBM-3.0-uefi-286ca43aa-220831
(bootloader) git:xbl_config: MBM-3.0-uefi-286ca43aa-220831
(bootloader) git:abl: MBM-3.0-uefi-b5c341d0203-220831
(bootloader) git:rpm: MBM-3.0-uefi-8408d804-220831
(bootloader) git:tz: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:hyp: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:devcfg: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:keymaster: MBM-3.0-uefi-d9ee9c15-220831
(bootloader) git:storsec: MBM-3.0-uefi-d9ee9c15-220831
(bootloader) git:uefisecapp: MBM-3.0-uefi-d9ee9c15-220831
(bootloader) gitrov: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:qupfw: MBM-3.0-uefi-43fe43f-220831
(bootloader) frp-state: no protection (0)
(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: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D06412
(bootloader) primary-display: auo_nt36675_fhd_vid
(bootloader) secondary-display:
(bootloader) fdr-allowed: yes
Click to expand...
Click to collapse
try reflashing it in qfil maybe?
robertr1229 said:
I was trying to restore my G Stylus 5g. I flashed the stock rom with LMSA and then attempted to relock the bootloader. Now when the phone starts up it says that it has no OS and just reboots to fastboot. I tried running LMSA and it gets about 35% done and the throws an error about single partition. I downloaded the stock rom from lolinet and tried to manually flash but get permission denied errors. I have seen similar users with this issue and the problem was that the firmware version was different from the software channel my getvar all output shows that both the software channel and the firmware version is RETUS.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-b5c341d0203-220831
(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: 256GB MICRON MT256GASAO8U21 FV=0609 WB=2048
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_MANNAR 1.1
(bootloader) serialno: ZY22C8XLQM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: D683CFFF
(bootloader) token: inactive
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 05-20-2021
(bootloader) sku: XT2131-1
(bootloader) carrier_sku: XT2131-1
(bootloader) battid: SB18D01192
(bootloader) battery-voltage: 3689
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/denver_global/denver:11/R
(bootloader) ro.build.fingerprint[1]: RES31.Q2-11-66-10/f33db7:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.16.r1-03500-MANNAR.0
(bootloader) version-baseband: M4350_HI405_19.533.01.95R DENVER_NA_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-gb5d4f8e724aa
(bootloader) kernel.version[1]: ([email protected]) (Android (6573524
(bootloader) kernel.version[2]: based on r383902b) clang version 11.0.2
(bootloader) kernel.version[3]: (https://android.googlesource.com/toolc
(bootloader) kernel.version[4]: hain/llvm-project b397f81060ce6d701042b7
(bootloader) kernel.version[5]: 82172ed13bee898b79), LLD 11.0.2 (/buildb
(bootloader) kernel.version[6]: ot/tmp/tmpF3FjA8 b397f81060ce6d701042b78
(bootloader) kernel.version[7]: 2172ed13bee898b79)) #1 SMP PREEMPT Mon J
(bootloader) kernel.version[8]: an 31 06:03:39 CST 2022
(bootloader) git:xbl: MBM-3.0-uefi-286ca43aa-220831
(bootloader) git:xbl_config: MBM-3.0-uefi-286ca43aa-220831
(bootloader) git:abl: MBM-3.0-uefi-b5c341d0203-220831
(bootloader) git:rpm: MBM-3.0-uefi-8408d804-220831
(bootloader) git:tz: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:hyp: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:devcfg: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:keymaster: MBM-3.0-uefi-d9ee9c15-220831
(bootloader) git:storsec: MBM-3.0-uefi-d9ee9c15-220831
(bootloader) git:uefisecapp: MBM-3.0-uefi-d9ee9c15-220831
(bootloader) gitrov: MBM-3.0-uefi-fd869ed7-220831
(bootloader) git:qupfw: MBM-3.0-uefi-43fe43f-220831
(bootloader) frp-state: no protection (0)
(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: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D06412
(bootloader) primary-display: auo_nt36675_fhd_vid
(bootloader) secondary-display:
(bootloader) fdr-allowed: yes
Click to expand...
Click to collapse
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
blankflash!!! use correct last working firmware version!!!
maddog3030 said:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
blankflash!!! use correct last working firmware version!!!
Click to expand...
Click to collapse
I tried this. I used all three versions of the blankflash with the latest firmware. I still get a permission denied error after getting into fastboot and trying to flash the signed firmware.
robertr1229 said:
I tried this. I used all three versions of the blankflash with the latest firmware. I still get a permission denied error after getting into fastboot and trying to flash the signed firmware.
Click to expand...
Click to collapse
If your info dump is still the same your bootloader's still locked
maddog3030 said:
If your info dump is still the same your bootloader's still locked
Click to expand...
Click to collapse
Yes,
The bootloader is locked. I was trying to flash back to the factory signed firmware. I flashed it back before locking the bootloader. My assumption was that even with a locked bootloader you can flash the same factory firmware. I would like to try and recover the phone but at this point if it's a lost cause.
robertr1229 said:
Yes,
The bootloader is locked. I was trying to flash back to the factory signed firmware. I flashed it back before locking the bootloader. My assumption was that even with a locked bootloader you can flash the same factory firmware. I would like to try and recover the phone but at this point if it's a lost cause.
Click to expand...
Click to collapse
Take your case here
Motorola Blankflash
Request blankflash by giving device informations
t.me
And ask for help.

Bricked XT2113-3 and flash failure (even with LMSA)

Hi everybody
I have a big problem with my MOTO G 5G so i'll try to explain it carefully:
I was using stock kiev Android 11 ROM from LMSA, which helped me a year ago for a soft brick. Everything went ok and afterwards i rooted using Magisk. So i also unlocked my bootloader.
Since then the phone started to ask for an OTA update, which i never did for obvious reasons.
Now, yesterday mobile data didn't work properly so i thought to restart the phone (it was not the first time i restarted since rooting).
BAM! Soft brick with bootloop.
I've been trying everything during this 24 hours:
- LMSA flashes the firmware and completes the procedure, but the phone stays bricked.
- same with fastboot with both a downloaded firmware (right carrier and everything) and LMSA downloaded firmware
- tried to switch partitions and it started, but after the initial configuration procedure it crashes entering bootloop again
Please help me if you have any ideas... I don't know how this could be possible. I love this phone so much and I don't want to trash it!
here is the getvar maybe it can help...
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-kiev_retail-45a34bc590e-221115
(bootloader) product: kiev
(bootloader) board: kiev
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM2V8001CM-B707 FV=1500 WB=16777216
(bootloader) ram: 6GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 10
(bootloader) cpu: SM_BITRA_H 1.0
(bootloader) serialno: ZY22BFMSHS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: F316FBCC
(bootloader) token: inactive
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-24-2020
(bootloader) sku: XT2113-3
(bootloader) carrier_sku: XT2113-3
(bootloader) battid: SB18C85232
(bootloader) battery-voltage: 4062
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: timit
(bootloader) ro.build.fingerprint[0]: motorola/kiev_retaile/kiev:11/RZKS
(bootloader) ro.build.fingerprint[1]: 31.Q3-25-15-11/feee1:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-11500-SMxx50.0
(bootloader) version-baseband[0]: M7225_HI251_22.578.01.39R KIEV_ROWDSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Tue N
(bootloader) kernel.version[4]: ov 15 13:30:36 CST 2022
(bootloader) git:xbl: MBM-3.0-kiev_retail-93822280-221115
(bootloader) git:xbl_config: MBM-3.0-kiev_retail-93822280-221115
(bootloader) git:abl: MBM-3.0-kiev_retail-45a34bc590e-221115
(bootloader) git:aop: MBM-3.0-kiev_retail-f135681-221115
(bootloader) git:tz: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:hyp: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:devcfg: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:keymaster: MBM-3.0-kiev_retail-775ecfe-221115
(bootloader) git:storsec: MBM-3.0-kiev_retail-775ecfe-221115
(bootloader) git:uefisecapp: MBM-3.0-kiev_retail-775ecfe-221115
(bootloader) gitrov: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:qupfw: MBM-3.0-kiev_retail-7a60101-221115
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 2
(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: 2
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86666
(bootloader) primary-display: tm_ft8756_666_1080x2300_vid
(bootloader) secondary-display:
all: listed above

Question Bootloop after Custom ROM / Rescue & Smart Assistant Moto G Stylus 5g 2022 (milanf XT2215-4)

I have a Moto G Stylus 5g 2022 (milanf XT2215-4) [MetroPCS / T-Mobile] that recently bootlooped after flashing Arrow OS Android 13 from A-Team and reverting back to stock.
I've downloaded the recent version from their Telegram group and followed their instructions.
I managed to get the Custom Rom to boot although I had no wifi connection, so I decided to revert back to stock ROM using Rescue & Smart Assistant.
Although big mistake because now the Stock OS does not even boot and I'm stuck with a bootloop nor can I install the Custom ROM !
I can access Fastboot & Recovery, although sometimes it reverts back to TWRP that i flashed in order to achieve the custom ROM. The bootloader is unlocked and rooted.
Any answers? I've tried everything and even attempted to use moto's old RSD Lite tool / manually flash the stock rom.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-1887fb15044-230427
(bootloader) product: milanf
(bootloader) board: milanf
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB MICRON MT128GAXAU2U227X FV=0107 WB=2048
(bootloader) ram: 6GB MICRON LP4x DIE=16Gb M5-M8=FF 07 00 10
(bootloader) cpu: SM_STRAIT 1.0
(bootloader) serialno: ZY22GR3NSK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x85
(bootloader) uid: FB6D3EB4
(bootloader) token: inactive
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-14-2023
(bootloader) sku: XT2215-4
(bootloader) carrier_sku: XT2215-4
(bootloader) battid: SB18D33989
(bootloader) battery-voltage: 3807
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: tmo
(bootloader) ro.build.fingerprint[0]: Must use __system_property_read_ca
(bootloader) ro.build.fingerprint[1]: llback() to read
(bootloader) ro.build.version.qcom: LA.UM.9.16.r1-09800-MANNAR.QSSI12.0
(bootloader) version-baseband[0]: M6375_HI434_12.262.01.50.17u MILANF_PV
(bootloader) version-baseband[1]: T_NA_CUST
(bootloader) kernel.version[0]: Linux version 5.4.197-PizzaG_x64-g45fbe4
(bootloader) kernel.version[1]: bf439e-dirty ([email protected]) (And
(bootloader) kernel.version[2]: roid (6443078 based on r383902) clang ve
(bootloader) kernel.version[3]: rsion 11.0.1 (https://android.googlesour
(bootloader) kernel.version[4]: ce.com/toolchain/llvm-project b397f81060
(bootloader) kernel.version[5]: ce6d701042b782172ed13bee898b79), GNU ld
(bootloader) kernel.version[6]: (binutils-2.27-bd24d23f) 2.27.0.20170315
(bootloader) kernel.version[7]: ) #1 SMP PREEMPT Wed Apr 26 21:26:58 CDT
(bootloader) kernel.version[8]: 2023
(bootloader) git:xbl: MBM-3.0-uefi-37c4c3a68-230427
(bootloader) git:xbl_config: MBM-3.0-uefi-37c4c3a68-230427
(bootloader) git:abl: MBM-3.0-uefi-1887fb15044-230427
(bootloader) git:rpm: MBM-3.0-uefi-d808fb4-dirty-230427
(bootloader) git:tz: MBM-3.0-uefi-2b95735f-230427
(bootloader) git:hyp: MBM-3.0-uefi-2b95735f-230427
(bootloader) git:devcfg: MBM-3.0-uefi-2b95735f-230427
(bootloader) git:keymaster: MBM-3.0-uefi-7ec6b152-230427
(bootloader) git:storsec: MBM-3.0-uefi-7ec6b152-230427
(bootloader) git:uefisecapp: MBM-3.0-uefi-7ec6b152-230427
(bootloader) git: qrov: MBM-3.0-uefi-2b95735f-230427
(bootloader) git:qupfw: MBM-3.0-uefi-86fe38d-230427
(bootloader) frp-state: no protection (0)
(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: 4
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D38304
(bootloader) snapshot-update-status: none
(bootloader) primary-display: csot_nt36672e_1080x2460_120_vid
(bootloader) secondary-display:
(bootloader) fdr-allowed: yes
all: listed above
finished. total time: 0.423s
fastboot says you have a custom kernel installed, did you receive errors when reverting to stock? At what point in bootup is it restarting?
No i haven't retrieved any errors when flashing to stock using Rescue & Smart Assistant / TinyFastboot . Although still receiving boot loop.

Categories

Resources