Database Info

[Q] Unable to unlock bootloader of Moto G

Hi guys,
I've some trouble to unlock my brand new Moto G's bootloader.
I've tried howto from wiki.cyanogenmod. org/w/Install_CM_for_falcon.
Step 6.
Code:
# fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.160s]
finished. total time: 0.160s
There is no sim card inserted.
I've never connected the phone to my Google account or a Motorla account.
Android 4.3
Baseband MSM 8626BP_1032.3051.51.02P
System 14.91.11.falcon_umts.Retail.en.DE
Build 14.10.oQ3.X-76-LGG-11
Any ideas?
Regards,
Timm

I've updated Android to 4.4.4
System version 210.12.40.falcom_umts.Retail.en.DE
Baseband MSM8626BP_1032.390.81.01P
Build KXB21.14-L1.40
Behavior of "fastboot oem get_unlock_data" didn't change.
cid is 0x0000 so unlocking should be possible.
Any ideas?
Regards,
Timm

timm2k said:
I've updated Android to 4.4.4
System version 210.12.40.falcom_umts.Retail.en.DE
Baseband MSM8626BP_1032.390.81.01P
Build KXB21.14-L1.40
Behavior of "fastboot oem get_unlock_data" didn't change.
cid is 0x0000 so unlocking should be possible.
Any ideas?
Regards,
Timm
Click to expand...
Click to collapse
I've had this problem too. In the latest update 4.4.4 there is a bug for unlocking bootloader but there is a fix for it. i did it and it worked. i found it in the motorola forums. click the link and afterwards on the page, search moto g 4.4.4 bootloader fix in the search bar, its a zip with instructions for you how to unlock, hope it helps
https://forums.motorola.com/hives/3ba9b2429c/summary

Thanks for your reply.
Did you really get this message?:
Code:
# fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.160s]
finished. total time: 0.160s
I found a zip archive which will unlock the phone when you get your unlock key.
My phone doesn't display the unlock request key. I only get "Could not get unlock data!".
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA8<blanked>
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 168DFB010F000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Oct 13 15:30:13 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/36:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.DE
(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.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld27) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 04:49:32 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.062s

I've had this same problem. My brother has a Moto G first gen that's softbricked, and since I've worked on androids before I thought I'd fix it. I could get it to boot into fastboot, so I'm trying to install TWRP and fix his phone (stock recovery won't work). But when I enter fastboot oem get_unlock_data I have the same result....
---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------
Update: turning off the phone and rebooting into fastboot fixed the problem for me. Sorry, that probably doesn't help you :/

[Q] Having errors going back to Stock. Moto G

Moto G 1rst Gen US GSM 16 gb.
Following this:
droidviews .com /restore-moto-g-2014-to-stock-and-lock-the-bootloader/
Worked:
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
Error:
mfastboot flash system system.img_sparsechunk.0
C:\Users\........\AppData\Local\Android\sdk\platform-tools>mfastboot flash
search system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'search' (256945 KB)...
OKAY [ 10.071s]
writing 'search'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 10.091s
Any ideas please?
I had TWRP with CM 11 I think M10 on it. Trying to go back to stock because CM is too buggy. I have a Lollypop rom, phone had Kitkat on it before. I have the KK backup but I couldn't update it because of TWRP.
Maybe I have the wrong ROM? I don't know, it i hard to find a working website. This is the filename
XT1034_FALCON-RETUAWS_5.0.2_LXB22.99-36_19_cid9_CFC_1FF.xml.zip
Any help would be greatly appreciated please so I have a working phone again. This is my only phone. Thanks
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x6
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9190075M
(bootloader) cid: 0x0009
(bootloader) channelid: 0x00
(bootloader) uid: 22FDEE010F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Sep 13 22: 4:14 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retuaws/falcon_umt
(bootloader) ro.build.fingerprint[1]: s:4.4.4/KXB21.14-L1.61/60:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.61.falcon_umt
(bootloader) ro.build.version.full[1]: s.AWSRetail.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.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gc146877 ([email protected]
(bootloader) kernel.version[1]: ilclbld29) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Sat Aug 30 03:25:08 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 2/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.178s

Somehow the word search got in the command removed it and worked thanks.

[XT1039] CID 0xDEAD: CANNOT FLASH A BACKUP

First I apologize for my english. I bought this phone bricked (perhaps because of a fastboot erase all command) for a very little price... and I'm trying to repair it for personal use. A my friend has a XT1039 so I dumped all his partitions in .img files, to help me restore. The first problem I saw was that the CID was set to 0xDEAD (I think that that means that I can't flash the system sparechunks)... So I tried to restore it via fastboot flash cid cid.img but it returned a "Permission denied!" error. The device boots directly in the bootloader, printing "Device is LOCKED. Status Code: 0", but I know that the bootloader was unlocked by the first owner. I've flashed all the partitions of the motorola firmware (but none of the backup that I made whit the other phone) yet, whithout the system sparechunks that return me a "Invalid signature - preflash validation failed error". Another sorry for my poor english, I'm ready for questions, and I post the fastboot getvar all below.
Code:
XT1039>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA34801RFG
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: 40B5090A15000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "flashfail" configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 8:35: 5 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_reteu/peregrine
(bootloader) ro.build.fingerprint[1]: :5.1/LPB23.13-17/18:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.full[0]: Blur_Version.23.21.17.peregrine_r
(bootloader) ro.build.version.full[1]: eteu.reteuall.en.EU
(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: M8926_309101.02.03.14R EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42+ ([email protected]
(bootloader) kernel.version[1]: n-3421) (gcc version 4.9.4 20150629 (pre
(bootloader) kernel.version[2]: release) (crosstool-NG 1.20.0 - Linaro G
(bootloader) kernel.version[3]: CC 2015.06 - Cortex-A7) ) #1 SMP PREEMPT
(bootloader) kernel.version[4]: Wed Sep 23 19:59:44 CLT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.124s

Same situation.
I was also suffering fro erase all command and did the same as u did... Flashed files from other model . Now bootloader is locked. cid dead ,unlocked not supported. Did you ever got a solution for this.

Same issue here, DEAD CID with Moto G 2nd Gen XT-1068. Anyone can help me?

gplambi said:
I was also suffering fro erase all command and did the same as u did... Flashed files from other model . Now bootloader is locked. cid dead ,unlocked not supported. Did you ever got a solution for this.
Click to expand...
Click to collapse
Hi,
Any luck with your set. I have XT1572 with "XT1572_CLARK_RETEU_5.1.1_LPH23.116-18" currently installed. Wanted to update it to Nugget so came across CID : 0xDEAD, channelid : 0xDEAD, unlocked : Not Supported,
C:\WINDOWS\system32>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.006s
I need to know if i could install nugget or not.

Moto G7 plus (Lake) stuck on "Corrupt and non will boot" any help?

Hi Everyone!
I'm new here and need help with my LAKE XT1965-2 stuck on "your device is corrupt. it can´t be trusted and will not boot" So i know that have some smart solutions here but, all i tried was unsuccessful and i know that have a lot of Brazilians here (kkkk e ai man, sussa?) someone have a solution for this one?
Things i tried:
* LSMA - By Fastboot (Yes, i can go to fastboot but, aways receive a "Primary Partition fail message"
* ADB - command by command one at one, unfortunately unsuccessful.
* RSD LITE - Fail =(
* LAST one - EDL also unsuccessful
My device is NOT with debugging enabled and NOT bootloader unlocked. Any ideias?
Here is my GETVAR ALL:
Code:
D:\Lake Rom\minimal_adb_fastboot_1.4.3_portable>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200524
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(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=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0054198036
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577093484259
(bootloader) meid:
(bootloader) date: 02-12-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 4274
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPWS30.6
(bootloader) ro.build.fingerprint[1]: 1-21-11/e25a6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: M636_13.45.02.60R LAKE_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Sun M
(bootloader) kernel.version[3]: ay 24 11:04:26 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-200524
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-200524
(bootloader) gitmic: MBM-3.0-lake_retail-efaf0cccb-200524
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-200524
(bootloader) git:tz: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:hyp: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:devcfg: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:keymaster: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) gitrov: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:storsec: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) frp-state: protected (77)
(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: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.254s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Richteeer said:
My device is NOT with debugging enabled and NOT bootloader unlocked. Any ideias?
Click to expand...
Click to collapse
That's the main problem you have.
Your phone has A/B partition layout hence its recovery partition is part of boot partition. Everything is managed by the boot partition now. Thus you now boot the recovery into the boot partition rather than flashing it to the non-existing recovery partition.
So this is my recommendation: boot into a custom recovery like TWRP and from therein flash a Custom ROM:
Code:
fastboot devices
fastboot boot twrp.img

jwoegerbauer said:
That's the main problem you have.
Your phone has A/B partition layout hence its recovery partition is part of boot partition. Everything is managed by the boot partition now. Thus you now boot the recovery into the boot partition rather than flashing it to the non-existing recovery partition.
So booting into a custom recovery like TWRP is required to flash a Custom ROM:
Code:
fastboot devices
fastboot boot twrp.img
Click to expand...
Click to collapse

Good idea but, here we have:
Code:
downloading 'boot.img'...
OKAY [ 0.734s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.754s

Wondering why you don't carefully read posts?

jwoegerbauer said:
Wondering why you don't carefully read posts?
Click to expand...
Click to collapse
I think I missed something, can you help me?
I'm new here, thanks for your patience

Richteeer said:
Hi Everyone!
I'm new here and need help with my LAKE XT1965-2 stuck on "your device is corrupt. it can´t be trusted and will not boot" So i know that have some smart solutions here but, all i tried was unsuccessful and i know that have a lot of Brazilians here (kkkk e ai man, sussa?) someone have a solution for this one?
Things i tried:
* LSMA - By Fastboot (Yes, i can go to fastboot but, aways receive a "Primary Partition fail message"
* ADB - command by command one at one, unfortunately unsuccessful.
* RSD LITE - Fail =(
* LAST one - EDL also unsuccessful
My device is NOT with debugging enabled and NOT bootloader unlocked. Any ideias?
Here is my GETVAR ALL:
Code:
D:\Lake Rom\minimal_adb_fastboot_1.4.3_portable>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200524
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(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=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0054198036
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577093484259
(bootloader) meid:
(bootloader) date: 02-12-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 4274
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPWS30.6
(bootloader) ro.build.fingerprint[1]: 1-21-11/e25a6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: M636_13.45.02.60R LAKE_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Sun M
(bootloader) kernel.version[3]: ay 24 11:04:26 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-200524
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-200524
(bootloader) gitmic: MBM-3.0-lake_retail-efaf0cccb-200524
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-200524
(bootloader) git:tz: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:hyp: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:devcfg: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:keymaster: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) gitrov: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:storsec: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) frp-state: protected (77)
(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: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.254s
View attachment 5277135
Click to expand...
Click to collapse
Try flashing
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then try LMSA again

sd_shadow said:
Try flashing
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then try LMSA again
Click to expand...
Click to collapse
Hi Sd_Shadow
I´ve got this error with fastboot commands:
Code:
C:\QPWS30.61-21-11>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.006s
C:\QPWS30.61-21-11>fastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (37 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Failed to commit transaction!
(bootloader) Transaction cancelled!
FAILED (remote failure)
finished. total time: 0.034s
C:\QPWS30.61-21-11>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.014s

Question Bought a soft bricked edge 2021 and all it does it bootloop after flashing firmware multiple ways

Hi,
I don't understand what the issue is with this this phone. It continually just bootloops. It gives the error plese see pick:
I tired:
1. Lenovo's rescue tool-it successfully flashed; still bootloops.
2. Verizon's firmware tool-it successfully flashed; still bootloops.
3. Downloaded the firmware manually and manually flashed every file; still bootloops.
The phone turns on every time, I can boot to fastboot and recovery. Bootloader says oem_locked. I don't know what else to do. I thought this would be an easy fix.

lolwatpear said:
Hi,
I don't understand what the issue is with this this phone. It continually just bootloops. It gives the error plese see pick:
I tired:
1. Lenovo's rescue tool-it successfully flashed; still bootloops.
2. Verizon's firmware tool-it successfully flashed; still bootloops.
3. Downloaded the firmware manually and manually flashed every file; still bootloops.
The phone turns on every time, I can boot to fastboot and recovery. Bootloader says oem_locked. I don't know what else to do. I thought this would be an easy fix.
Click to expand...
Click to collapse
Can you post
fastboot getvar all
Please remove your imei

SyberHexen said:
Can you post
fastboot getvar all
Please remove your imei
Click to expand...
Click to collapse
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-berlna_global-ebfa575b6e-220324
(bootloader) product: berlna
(bootloader) board: berlna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: VZW
(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_KODIAK 1.0
(bootloader) serialno: ZD2223NZCV
(bootloader) cid: 0x0033
(bootloader) channelid: 0x83
(bootloader) uid: 65414223
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxx
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-08-2022
(bootloader) sku: XT2141-1
(bootloader) carrier_sku: XT2141-1
(bootloader) battid:
(bootloader) battery-voltage: 4218
(bootloader) iccid: 89148000007374885701
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: vzw
(bootloader) ro.build.fingerprint[0]: motorola/berlna_globalv/berlna:11/
(bootloader) ro.build.fingerprint[1]: RRM31.Q3-23-39-1-1/83c2c:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.14.r1-16900-LAHAINA.0
(bootloader) version-baseband[0]: M7325_HI43_45.1293.01.42R BERLNA_PVT_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-g6571075f035f
(bootloader) kernel.version[1]: ([email protected]) (Android (6877366
(bootloader) kernel.version[2]: based on r383902b1) clang version 11.0.
(bootloader) kernel.version[3]: 2 (https://android.googlesource.com/tool
(bootloader) kernel.version[4]: chain/llvm-project b397f81060ce6d701042b
(bootloader) kernel.version[5]: 782172ed13bee898b79), LLD 11.0.2 (https:
(bootloader) kernel.version[6]: //android.googlesource.com/toolchain/llv
(bootloader) kernel.version[7]: m-project b397f81060ce6d701042b782172ed1
(bootloader) kernel.version[8]: 3bee898b79)) #1 SMP PREEMPT Wed Sep 15 0
(bootloader) kernel.version[9]: 9:20:11 CDT 2021
(bootloader) git:abl: MBM-3.0-berlna_global-ebfa575b6e-220324
(bootloader) frp-state: no protection (0)
(bootloader) current-slot:
(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: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D09212
(bootloader) primary-display: tianma_nt36672e_1080x2460_vid
(bootloader) secondary-display: none
all: listed above
finished. total time: 0.115s
Thanks

SyberHexen said:
Can you post
fastboot getvar all
Please remove your imei
Click to expand...
Click to collapse
anything you gathered from that information?

lolwatpear said:
anything you gathered from that information?
Click to expand...
Click to collapse
Bootloader seems out of date compared to the factory firmware available for vzw.
I don't think the firmware is flashing correctly.
Please try using Moto Flash pro:
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
With this vzw firmware:
BERLNA_GLOBAL_S1RMS32.68-43-16-9_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_cid51_CFC.xml.zip
drive.google.com

SyberHexen said:
Bootloader seems out of date compared to the factory firmware available for vzw.
I don't think the firmware is flashing correctly.
Please try using Moto Flash pro:
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
With this vzw firmware:
BERLNA_GLOBAL_S1RMS32.68-43-16-9_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_cid51_CFC.xml.zip
drive.google.com
Click to expand...
Click to collapse
Now it gives me "no valid operating system could be found". think this is an EMMC issue? Here's the updated getvar all:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-berlna_global-c0108f80f8d-23
(bootloader) version-bootloader[1]: 0324
(bootloader) product: berlna
(bootloader) board: berlna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: VZW
(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_KODIAK 1.0
(bootloader) serialno: ZD2223NZCV
(bootloader) cid: 0x0033
(bootloader) channelid: 0x83
(bootloader) uid: 65414223
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-08-2022
(bootloader) sku: XT2141-1
(bootloader) carrier_sku: XT2141-1
(bootloader) battid:
(bootloader) battery-voltage: 4191
(bootloader) iccid: 89148000007374885701
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: vzw
(bootloader) ro.build.fingerprint[0]: motorola/berlna_globalv/berlna:11/
(bootloader) ro.build.fingerprint[1]: RRM31.Q3-23-39-1-1/83c2c:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.14.r1-16900-LAHAINA.0
(bootloader) version-baseband[0]: M7325_HI43_45.1293.01.42R BERLNA_PVT_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-g6571075f035f
(bootloader) kernel.version[1]: ([email protected]) (Android (6877366
(bootloader) kernel.version[2]: based on r383902b1) clang version 11.0.
(bootloader) kernel.version[3]: 2 (https://android.googlesource.com/tool
(bootloader) kernel.version[4]: chain/llvm-project b397f81060ce6d701042b
(bootloader) kernel.version[5]: 782172ed13bee898b79), LLD 11.0.2 (https:
(bootloader) kernel.version[6]: //android.googlesource.com/toolchain/llv
(bootloader) kernel.version[7]: m-project b397f81060ce6d701042b782172ed1
(bootloader) kernel.version[8]: 3bee898b79)) #1 SMP PREEMPT Wed Sep 15 0
(bootloader) kernel.version[9]: 9:20:11 CDT 2021
(bootloader) git:xbl: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) git:xbl_config: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) git:abl: MBM-3.0-berlna_global-c0108f80f8d-230324
(bootloader) git:aop: MBM-3.0-berlna_global-8cce5a89-230324
(bootloader) git:tz: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:hyp: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:devcfg: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:keymaster: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:storsec: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:uefisecapp: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:prov: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:qupfw: MBM-3.0-berlna_global-a2abf7e-230324
(bootloader) git:cpucp: MBM-3.0-berlna_global-a2abf7e-230324
(bootloader) git:shrm: MBM-3.0-berlna_global-56ea1542f-230324
(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: SB28D09212
(bootloader) primary-display: tianma_nt36672e_1080x2460_vid
(bootloader) secondary-display: none
(bootloader) fdr-allowed: yes
all: listed above
finished. total time: 0.135s

lolwatpear said:
Now it gives me "no valid operating system could be found". think this is an EMMC issue? Here's the updated getvar all:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-berlna_global-c0108f80f8d-23
(bootloader) version-bootloader[1]: 0324
(bootloader) product: berlna
(bootloader) board: berlna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: VZW
(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_KODIAK 1.0
(bootloader) serialno: ZD2223NZCV
(bootloader) cid: 0x0033
(bootloader) channelid: 0x83
(bootloader) uid: 65414223
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-08-2022
(bootloader) sku: XT2141-1
(bootloader) carrier_sku: XT2141-1
(bootloader) battid:
(bootloader) battery-voltage: 4191
(bootloader) iccid: 89148000007374885701
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: vzw
(bootloader) ro.build.fingerprint[0]: motorola/berlna_globalv/berlna:11/
(bootloader) ro.build.fingerprint[1]: RRM31.Q3-23-39-1-1/83c2c:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.14.r1-16900-LAHAINA.0
(bootloader) version-baseband[0]: M7325_HI43_45.1293.01.42R BERLNA_PVT_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-g6571075f035f
(bootloader) kernel.version[1]: ([email protected]) (Android (6877366
(bootloader) kernel.version[2]: based on r383902b1) clang version 11.0.
(bootloader) kernel.version[3]: 2 (https://android.googlesource.com/tool
(bootloader) kernel.version[4]: chain/llvm-project b397f81060ce6d701042b
(bootloader) kernel.version[5]: 782172ed13bee898b79), LLD 11.0.2 (https:
(bootloader) kernel.version[6]: //android.googlesource.com/toolchain/llv
(bootloader) kernel.version[7]: m-project b397f81060ce6d701042b782172ed1
(bootloader) kernel.version[8]: 3bee898b79)) #1 SMP PREEMPT Wed Sep 15 0
(bootloader) kernel.version[9]: 9:20:11 CDT 2021
(bootloader) git:xbl: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) git:xbl_config: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) git:abl: MBM-3.0-berlna_global-c0108f80f8d-230324
(bootloader) git:aop: MBM-3.0-berlna_global-8cce5a89-230324
(bootloader) git:tz: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:hyp: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:devcfg: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:keymaster: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:storsec: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:uefisecapp: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:prov: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:qupfw: MBM-3.0-berlna_global-a2abf7e-230324
(bootloader) git:cpucp: MBM-3.0-berlna_global-a2abf7e-230324
(bootloader) git:shrm: MBM-3.0-berlna_global-56ea1542f-230324
(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: SB28D09212
(bootloader) primary-display: tianma_nt36672e_1080x2460_vid
(bootloader) secondary-display: none
(bootloader) fdr-allowed: yes
all: listed above
finished. total time: 0.135s
Click to expand...
Click to collapse
Hmm let's try flashing manually in bootloader using fastboot
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot -w
fastboot set_active b
fastboot set_active a
fastboot reboot bootloader
Please note and forward any commands that fail

SyberHexen said:
Hmm let's try flashing manually in bootloader using fastboot
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot -w
fastboot set_active b
fastboot set_active a
fastboot reboot bootloader
Please note and forward any commands that fail
Click to expand...
Click to collapse
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.260s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Due to locked bootloader I guess?
--------------------------------------------------------
fastboot set_active b
fastboot set_active a
These commands just aren't recognized in terminal.
--------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.

lolwatpear said:
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.260s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Due to locked bootloader I guess?
--------------------------------------------------------
fastboot set_active b
fastboot set_active a
These commands just aren't recognized in terminal.
--------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
Click to expand...
Click to collapse
Bad news pretty sure this has been unlocked and relocked by some paid tools or exploited in general.
If you're willing to spend 60 usd send me a pm or contact me on telegram for better responses @SyberHexen

SyberHexen said:
Bad news pretty sure this has been unlocked and relocked by some paid tools or exploited in general.
If you're willing to spend 60 usd send me a pm or contact me on telegram for better responses @SyberHexen
Click to expand...
Click to collapse
I really appreciate the help. Just going to return it. It's not worth the effort for what I planned to use it for. Thank you.

Have you
lolwatpear said:
I really appreciate the help. Just going to return it. It's not worth the effort for what I planned to use it for. Thank you.
Click to expand...
Click to collapse
have you fixed your issue i have same model with same problem
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-berlna_global-c0108f80f8d-23
(bootloader) version-bootloader[1]: 0324
(bootloader) product: berlna
(bootloader) board: berlna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: VZW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB SKhynix H9HQ21AECMADAR FV=A002 WB=2048
(bootloader) ram: 6GB SKHYNIX LP4x DIE=16Gb M5-M8=06 06 00 10
(bootloader) cpu: SM_KODIAK 1.0
(bootloader) serialno: ZY22DF6JQZ
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: B959D531
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: allowed
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-25-2021
(bootloader) sku: XT2141-1
(bootloader) carrier_sku: XT2141-1
(bootloader) battid: SB18D10749
(bootloader) battery-voltage: 3763
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: unknown
(bootloader) ro.build.fingerprint[0]: motorola/berlna_global/berlna:11/R
(bootloader) ro.build.fingerprint[1]: RMS31.Q3-23-39-2-2-6/8aadbb:user/r
(bootloader) ro.build.fingerprint[2]: elease-keys
(bootloader) ro.build.version.qcom: LA.UM.9.14.r1-16900-LAHAINA.0
(bootloader) version-baseband[0]: M7325_HI43_45.1293.01.44R BERLNA_PVT_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-g3865606212fe
(bootloader) kernel.version[1]: ([email protected]) (Android (6877366
(bootloader) kernel.version[2]: based on r383902b1) clang version 11.0.
(bootloader) kernel.version[3]: 2 (https://android.googlesource.com/tool
(bootloader) kernel.version[4]: chain/llvm-project b397f81060ce6d701042b
(bootloader) kernel.version[5]: 782172ed13bee898b79), LLD 11.0.2 (https:
(bootloader) kernel.version[6]: //android.googlesource.com/toolchain/llv
(bootloader) kernel.version[7]: m-project b397f81060ce6d701042b782172ed1
(bootloader) kernel.version[8]: 3bee898b79)) #1 SMP PREEMPT Fri Jan 7 21
(bootloader) kernel.version[9]: :44:52 EST 2022
(bootloader) git:abl: MBM-3.0-berlna_global-c0108f80f8d-230324
(bootloader) frp-state: protected (77)
(bootloader) current-slot:
(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: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D09212
(bootloader) primary-display: tianma_nt36672e_1080x2460_vid
(bootloader) secondary-display: none
(bootloader) fdr-allowed: yes
all: listed above
Finished. Total time: 0.187s

SyberHexen said:
Bootloader seems out of date compared to the factory firmware available for vzw.
I don't think the firmware is flashing correctly.
Please try using Moto Flash pro:
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
With this vzw firmware:
BERLNA_GLOBAL_S1RMS32.68-43-16-9_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_cid51_CFC.xml.zip
drive.google.com
Click to expand...
Click to collapse
SyberHexen said:
Bootloader seems out of date compared to the factory firmware available for vzw.
I don't think the firmware is flashing correctly.
Please try using Moto Flash pro:
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
With this vzw firmware:
BERLNA_GLOBAL_S1RMS32.68-43-16-9_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_cid51_CFC.xml.zip
drive.google.com
Click to expand...
Click to collapse
Thank you so much for the firmware. I looked so long for it but never could get the one with the 9 at the end. Thank you!