Database Info

[Q] Problem with XT1032 and everything, not bricked

Hi guys, last day a friend give to me a moto g because he dont know how to repair it.
He said that upgrade to 4.4.4 android and install an app that cause every app stop unexpectedly, u cant do anything cause this popups and every change u do like enable usb debbuging dont work.
At 1st i try to do a hard reset with "Android system recovery <3e> KXB21.14-L1.40", wipe data and cache then reboot but nothing wiped, android boot like nothing happens.
Then i try to install custom recovery with fastboot (CWM, TWRP) and everything looks fine just like all the guides says, the same logs with success.
Then i go to recovery mode from fastboot flash mode in and again load "Android system recovery" no CWM or TWRP.
When this happens i try to install the stock rom from BR with fastboot, no error msg or warning in fastboot and everything looks fine in fastload, i write a batch file to dont misspell something
Code:
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot erase cache
fastboot erase userdata
fastboot reboot
The device reboot and again, nothing happens, just boot like i dont write anything.
I try with a lot of imgs and guides, but nothing work for me.
Someone have an idea of whats happens here? The device looks frozen or something like that, i write-erase-remove and nothing happens.
I dont know if this is a kind of brick or something.
I would greatly appreciate any help you can give me!
PS: Sorry for my bad english, first time here.

Flash TWRP or CWM again, after it flashes, do not reboot the phone, use the volume buttons to go to recovery from the fastboot menu.

In pc
Code:
D:\android-sdk\platform-tools>fastboot flash recovery clockworkmodrecovery.6051
falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (8430 KB)...
OKAY [ 0.296s]
writing 'recovery'...
OKAY [ 0.158s]
finished. total time: 0.458s
In phone
Attached files
Without reboot

Is the stock 4.4.4 ROM available for the phone? I see you tried the BR ROM already.

audit13 said:
Is the stock 4.4.4 ROM available for the phone? I see you tried the BR ROM already.
Click to expand...
Click to collapse
Yup, not working
Code:
D:\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9300GIDO
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: D31D11040F000000000000000000
(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: "Thu Aug 21 23:56:54 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxcl/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37: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.AmericaMovil.en.CL
(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]: ilclbld34) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 05:07:35 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.182s
Don't know if that help

Same problem here... Any solution? I'm on lollipop eu
Sent from my XT1032 using XDA Free mobile app

Halp!

I have the same issue
Is there anything we can try on that phone?

I have the same problem, it's over a month already

Hi,
i sent my phone to authorized service and they said that it is broken motherboard or memory. I had unlocked bootloader so they canceled my warranty and sent it back with note that they won't repair it becouse it is not worth it. So thats all with motorola. It was my first motorola phone and i will never buy their products again. I had this for for 6 months...
Greetings form Białystok, Polska.

damn i guess I'm taking a huge risk here buying this then http://www.kijiji.ca/v-cell-phone/city-of-toronto/moto-g-2nd-gen-2014/1066867806

[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.

Moto Style XT1575 only turn on in AP Fastboot Flash Mode (Secure)

Hi my moto style (XT1575) only turn on went i conected to a charger or to a usb cable and went it turn on only show the AP Fastboot flash mode screen and constantly restar sometimes. Went i try to flash the phone always i get FAILED (remote failure), and i try to unlock the bootloader and the result was this:
"(bootloader) Check 'Allow OEM Unlock' in Developer Options FAILED (remote failure) finished. total time: 0.010s"
then i try to unlock the bootloader with "WinDroid Toolkit v3.1" it say that the bootloader is unlock it, but the phone still saying DEVICE is LOCKED: Status Code:0
I had downloaded seven different software and try to flash with the fastboot tools and the seven times same result "FAILED (remote failure)."
Here is the getvar all result for see if some one know how to solve this big issue:
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.48
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 64GB Samsung REV=07 PRV=02 TYPE=57 PNM=CWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA06300BOQ
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 1B0DEA001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358986061472351
(bootloader) meid:
(bootloader) date: 12-01-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5: 692AC5F764B5BA46559407A9E5C0A74B
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Dec 3 18:43:11 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g329ac5f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Apr 21 00:11:23 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) aboot.git: git=MBM-NG-VA0.48-0-g8c942c6
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.264s
Any idea of the solution of this???

Finally i solved the problem
exploxife said:
Hi my moto style (XT1575) only turn on went i conected to a charger or to a usb cable and went it turn on only show the AP Fastboot flash mode screen and constantly restar sometimes. Went i try to flash the phone always i get FAILED (remote failure), and i try to unlock the bootloader and the result was this:
"(bootloader) Check 'Allow OEM Unlock' in Developer Options FAILED (remote failure) finished. total time: 0.010s"
then i try to unlock the bootloader with "WinDroid Toolkit v3.1" it say that the bootloader is unlock it, but the phone still saying DEVICE is LOCKED: Status Code:0
I had downloaded seven different software and try to flash with the fastboot tools and the seven times same result "FAILED (remote failure)."
Here is the getvar all result for see if some one know how to solve this big issue:
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.48
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 64GB Samsung REV=07 PRV=02 TYPE=57 PNM=CWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA06300BOQ
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 1B0DEA001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358986061472351
(bootloader) meid:
(bootloader) date: 12-01-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5: 692AC5F764B5BA46559407A9E5C0A74B
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Dec 3 18:43:11 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g329ac5f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Apr 21 00:11:23 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) aboot.git: git=MBM-NG-VA0.48-0-g8c942c6
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.264s
Any idea of the solution of this???
Click to expand...
Click to collapse
For solved it i change the batery of the phone and then flashed it with this software with the adb:
"CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml"
Download from here:
(https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833/page18)
Here's the orden of the commands that i used:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot

where to find the correct firmware for xt1955-4?

Hi everyone!
I hope this is the right place to post this issue.
I have an Motorola G7 Power
model ID XT1955-4
CID 0x0032
The phone has the bootloader unlocked.
this is all the info about it C:\mfastboot>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-a5c9d71-190702
(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: ZY326H3KLF
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: E301320D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359517095583159
(bootloader) meid:
(bootloader) date: 08-06-2019
(bootloader) sku: XT1955-4
(bootloader) carrier_sku: XT1955-4
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jun 7 10:22:15 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean_reteu/ocean:9/PPOS2
(bootloader) ro.build.fingerprint[1]: 9.114-134-2/0d27:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.2.ocean_reteu
(bootloader) ro.build.version.full[1]: .retail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_26.100.01.120.01R OCEAN_ROWDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld34) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version[2]: erelease) (GCC) ) #1 SMP PREEMPT Sun Aug
(bootloader) kernel.version[3]: 4 11:49:12 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_retail-b508f3a-190702
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab3-190702
(bootloader) tz.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) devcfg.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) keymaster.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) prov.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) aboot.git: MBM-2.1-ocean_retail-a5c9d71-190702
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: reteu2
(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.040s
I wanted to reset my phone so that I could start over with all the data and apps. I did a reset from Motorola settings. It didn't reset then. Then I went in twrp recovery in "advanced" category and I made format data (I typed format). Then the phone got stuck in bootloop.
I downloaded from web XT1955-4_OCEAN_RETEU_9.0_PPO29.80-44_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and this Motorola_Moto_G7_Power_XT1955-4_OCEAN_PPO29.80-27_CID50 and I tried to install firmware through twrp, on "Image" category (I downloaded the zip on sdcard) but it gave me "invalid zip file" error. After some more research on google I found that you can't install the stock rom through twrp, but only through fastboot.
I followed those instructions from web
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash system system.img_sparsechunk.5
mfastboot.exe flash system system.img_sparsechunk.6
mfastboot.exe flash system system.img_sparsechunk.7
mfastboot.exe flash system system.img_sparsechunk.8
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot reboot
Each command worked well, excepting:
mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256 MB
error: cannot load 'motoboot.img': No error
mfastboot.exe flash boot boot.img
(bootloader) Image signed with key bad key
mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256 MB
error: cannot load 'recovery.img': No error
The phone displayed only "bad key" so I finally downloaded a logo.bin file and ran "mfastboot flash logo logo.bin" It started, but didn't pass over the logo, so I finally did a hard reset. Then it started but without IMEI, the sim card wasn't recognized. So I did again a hard reset then flashed the other zip (the xml file). Now touchscreen doesn't work, when I go to recovery it doesn't open the twrp (because of hard reset, I think). The buttons for home and volume work.
While googling, I found that many users struggled with problems like this and not all of them fixed them.
My phone info is "model ID XT1955-4 CID 0x0032" so then I thought I need a firmware with cid32 (those 2 zips are with cid50) but I didn't find such zips for XT1955-4.
I think that because of that cid, the imei and now the touchscreen isn't working anymore.
I found an answer on the web that I should relock the bootloader but I don't know if it helps or it will block me the access through fastboot.
The questions are:
1. It's possible to fix my phone without going to service (I can't, I don't live in city)?
2. What exactly do I need to need to fix this phone?
3. If I bricked it, why it happened that?
Thanks!

use this post
dannyetlv said:
Hi everyone!
I hope this is the right place to post this issue.
I have an Motorola G7 Power
model ID XT1955-4
CID 0x0032
The phone has the bootloader unlocked.
this is all the info about it C:\mfastboot>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-a5c9d71-190702
(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: ZY326H3KLF
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: E301320D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359517095583159
(bootloader) meid:
(bootloader) date: 08-06-2019
(bootloader) sku: XT1955-4
(bootloader) carrier_sku: XT1955-4
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jun 7 10:22:15 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean_reteu/ocean:9/PPOS2
(bootloader) ro.build.fingerprint[1]: 9.114-134-2/0d27:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.2.ocean_reteu
(bootloader) ro.build.version.full[1]: .retail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_26.100.01.120.01R OCEAN_ROWDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld34) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version[2]: erelease) (GCC) ) #1 SMP PREEMPT Sun Aug
(bootloader) kernel.version[3]: 4 11:49:12 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_retail-b508f3a-190702
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab3-190702
(bootloader) tz.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) devcfg.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) keymaster.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) prov.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) aboot.git: MBM-2.1-ocean_retail-a5c9d71-190702
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: reteu2
(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.040s
I wanted to reset my phone so that I could start over with all the data and apps. I did a reset from Motorola settings. It didn't reset then. Then I went in twrp recovery in "advanced" category and I made format data (I typed format). Then the phone got stuck in bootloop.
I downloaded from web XT1955-4_OCEAN_RETEU_9.0_PPO29.80-44_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and this Motorola_Moto_G7_Power_XT1955-4_OCEAN_PPO29.80-27_CID50 and I tried to install firmware through twrp, on "Image" category (I downloaded the zip on sdcard) but it gave me "invalid zip file" error. After some more research on google I found that you can't install the stock rom through twrp, but only through fastboot.
I followed those instructions from web
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash system system.img_sparsechunk.5
mfastboot.exe flash system system.img_sparsechunk.6
mfastboot.exe flash system system.img_sparsechunk.7
mfastboot.exe flash system system.img_sparsechunk.8
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot reboot
Each command worked well, excepting:
mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256 MB
error: cannot load 'motoboot.img': No error
mfastboot.exe flash boot boot.img
(bootloader) Image signed with key bad key
mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256 MB
error: cannot load 'recovery.img': No error
The phone displayed only "bad key" so I finally downloaded a logo.bin file and ran "mfastboot flash logo logo.bin" It started, but didn't pass over the logo, so I finally did a hard reset. Then it started but without IMEI, the sim card wasn't recognized. So I did again a hard reset then flashed the other zip (the xml file). Now touchscreen doesn't work, when I go to recovery it doesn't open the twrp (because of hard reset, I think). The buttons for home and volume work.
While googling, I found that many users struggled with problems like this and not all of them fixed them.
My phone info is "model ID XT1955-4 CID 0x0032" so then I thought I need a firmware with cid32 (those 2 zips are with cid50) but I didn't find such zips for XT1955-4.
I think that because of that cid, the imei and now the touchscreen isn't working anymore.
I found an answer on the web that I should relock the bootloader but I don't know if it helps or it will block me the access through fastboot.
The questions are:
1. It's possible to fix my phone without going to service (I can't, I don't live in city)?
2. What exactly do I need to need to fix this phone?
3. If I bricked it, why it happened that?
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/g7-power/how-to/relock-bootloader-versions-t4057497
use this post, it worked for me
there is info where find stock firmware too;
as I see from your listing your firmware is here
I see one thing that may be the problem; you are booting from slot B, so should switch to slot A; boot twrp and change slot to A
it is possible that You flashed firmware to slot A but booting frob slot B and that's a reason for bootloop
i'm new in this , so maybe i'm wrong, so awaiting for corrections from more advanced users if its wrong

dannyetlv said:
Hi everyone!
I hope this is the right place to post this issue.
I have an Motorola G7 Power
model ID XT1955-4
CID 0x0032
The phone has the bootloader unlocked.
this is all the info about it C:\mfastboot>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-a5c9d71-190702
(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: ZY326H3KLF
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: E301320D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359517095583159
(bootloader) meid:
(bootloader) date: 08-06-2019
(bootloader) sku: XT1955-4
(bootloader) carrier_sku: XT1955-4
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jun 7 10:22:15 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean_reteu/ocean:9/PPOS2
(bootloader) ro.build.fingerprint[1]: 9.114-134-2/0d27:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.2.ocean_reteu
(bootloader) ro.build.version.full[1]: .retail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_26.100.01.120.01R OCEAN_ROWDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld34) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version[2]: erelease) (GCC) ) #1 SMP PREEMPT Sun Aug
(bootloader) kernel.version[3]: 4 11:49:12 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_retail-b508f3a-190702
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab3-190702
(bootloader) tz.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) devcfg.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) keymaster.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) prov.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) aboot.git: MBM-2.1-ocean_retail-a5c9d71-190702
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: reteu2
(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.040s
I wanted to reset my phone so that I could start over with all the data and apps. I did a reset from Motorola settings. It didn't reset then. Then I went in twrp recovery in "advanced" category and I made format data (I typed format). Then the phone got stuck in bootloop.
I downloaded from web XT1955-4_OCEAN_RETEU_9.0_PPO29.80-44_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and this Motorola_Moto_G7_Power_XT1955-4_OCEAN_PPO29.80-27_CID50 and I tried to install firmware through twrp, on "Image" category (I downloaded the zip on sdcard) but it gave me "invalid zip file" error. After some more research on google I found that you can't install the stock rom through twrp, but only through fastboot.
I followed those instructions from web
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash system system.img_sparsechunk.5
mfastboot.exe flash system system.img_sparsechunk.6
mfastboot.exe flash system system.img_sparsechunk.7
mfastboot.exe flash system system.img_sparsechunk.8
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot reboot
Each command worked well, excepting:
mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256 MB
error: cannot load 'motoboot.img': No error
mfastboot.exe flash boot boot.img
(bootloader) Image signed with key bad key
mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256 MB
error: cannot load 'recovery.img': No error
The phone displayed only "bad key" so I finally downloaded a logo.bin file and ran "mfastboot flash logo logo.bin" It started, but didn't pass over the logo, so I finally did a hard reset. Then it started but without IMEI, the sim card wasn't recognized. So I did again a hard reset then flashed the other zip (the xml file). Now touchscreen doesn't work, when I go to recovery it doesn't open the twrp (because of hard reset, I think). The buttons for home and volume work.
While googling, I found that many users struggled with problems like this and not all of them fixed them.
My phone info is "model ID XT1955-4 CID 0x0032" so then I thought I need a firmware with cid32 (those 2 zips are with cid50) but I didn't find such zips for XT1955-4.
I think that because of that cid, the imei and now the touchscreen isn't working anymore.
I found an answer on the web that I should relock the bootloader but I don't know if it helps or it will block me the access through fastboot.
The questions are:
1. It's possible to fix my phone without going to service (I can't, I don't live in city)?
2. What exactly do I need to need to fix this phone?
3. If I bricked it, why it happened that?
Thanks!
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

xyzex said:
https://forum.xda-developers.com/g7-power/how-to/relock-bootloader-versions-t4057497
use this post, it worked for me
there is info where find stock firmware too;
as I see from your listing your firmware is here
I see one thing that may be the problem; you are booting from slot B, so should switch to slot A; boot twrp and change slot to A
it is possible that You flashed firmware to slot A but booting frob slot B and that's a reason for bootloop
i'm new in this , so maybe i'm wrong, so awaiting for corrections from more advanced users if its wrong
Click to expand...
Click to collapse
You just saved my phone (touchsctren, imei working) and it works even after reboot. Logo is the original and there is no bad key message.
That zip file had 9 system images, what did I download had only maximum 8.
Thank you, SIR!
I got now just two more questions:
1. If I need to root again my phone and enable the bootloader, the phone may brick just like it happened now? Or is it safe?
2. If I need to start all over and reset my device, I just need to boot into the fastboot and follow again that tutorial?
Last time I formatted data from twrp and it caused bootloop. Only hard reset helped to start my phone but no imei and no touchscreen Or is it enough to only wipe cache and data and I can keep the root and the bootloader on?
I think wiping is enough for future reset.
Thanks for your responses.

dannyetlv said:
You just saved my phone (touchsctren, imei working) and it works even after reboot. Logo is the original and there is no bad key message.
That zip file had 9 system images, what did I download had only maximum 8.
Thank you, SIR!
I got now just two more questions:
1. If I need to root again my phone and enable the bootloader, the phone may brick just like it happened now? Or is it safe?
2. If I need to start all over and reset my device, I just need to boot into the fastboot and follow again that tutorial?
Last time I formatted data from twrp and it caused bootloop. Only hard reset helped to start my phone but no imei and no touchscreen Or is it enough to only wipe cache and data and I can keep the root and the bootloader on?
I think wiping is enough for future reset.
Thanks for your responses.
Click to expand...
Click to collapse
Well. First : your welcome.
Second: I'm new in this and after first readings decided that its risky to flash custom ROM without more reading. Thats because Ive seen too many descriptions of different fails.
There are many ways to brick or not. From the oters hand, I don't think that bricking this phone is a big problem if you understand better what to do. In most caces unbricking or unlooping is no problem.
So, i'm not the right person to give advanced advices because I havent got time to read mor to understand more. I like understand what i'm doing.
Answer 1. You probably didnt bricked Your phon, just flashed firmware to one slot and tried boot on other slot.
Answer2. It is one of possibilities. For me its working but somethimes problem may be caused by other mistake so in that case just look for roght answer on forum. This is a bunch of good oriented people
About bootloop. If You brick it the same way - the solution should work again. Just try to be more updated what U are dooing, so You don't make mistake. For example good start is to know little about partitions A/B (slots). What is it, and how it works.
For example you may want to read this .
There's plenty of good info created by senior members of this forum. I know it is time consuming thing but its the only way to understanding.
So, I wish You many sucessful flashings.

xyzex said:
Well. First : your welcome.
Second: I'm new in this and after first readings decided that its risky to flash custom ROM without more reading. Thats because Ive seen too many descriptions of different fails.
There are many ways to brick or not. From the oters hand, I don't think that bricking this phone is a big problem if you understand better what to do. In most caces unbricking or unlooping is no problem.
So, i'm not the right person to give advanced advices because I havent got time to read mor to understand more. I like understand what i'm doing.
Answer 1. You probably didnt bricked Your phon, just flashed firmware to one slot and tried boot on other slot.
Answer2. It is one of possibilities. For me its working but somethimes problem may be caused by other mistake so in that case just look for roght answer on forum. This is a bunch of good oriented people
About bootloop. If You brick it the same way - the solution should work again. Just try to be more updated what U are dooing, so You don't make mistake. For example good start is to know little about partitions A/B (slots). What is it, and how it works.
For example you may want to read this .
There's plenty of good info created by senior members of this forum. I know it is time consuming thing but its the only way to understanding.
So, I wish You many sucessful flashings.
Click to expand...
Click to collapse
And make sure you flash a b zip before flashing any roms

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!