Database Info

[Q] how to un-soft-brick MOTO 4G LTE Falcon 4.4.4

I think I permanently soft bricked my phone.
Possible reasons
I tried to to flash cm-12-20150115-NIGHTLY-falcon from recovery-clockwork-touch-6.0.4.7-falcon . I couldn't figure out how to go to recovery mode from fastboot, so I went there with command prompt via "fastboot boot openrecovery-twrp-2.7.1.0-xt1032.img" . From there, I went to flash CM 12 nightly, but I made one fatal error, I never backed up my stock rom The device restarted, but it took me to "Fastboot reason: Fall-through from normal boot mode". I tried to go to recovery and normal powerup, but I got the message "boot up failed".
Attempted fixes
I scoured the interned to find a possible solution, I tried to re-install a new recovery from fastboot, but I always got the message "Mismatched partition size". I tried to boot from a recovery like I did before with "fastboot boot openrecovery-twrp-2.7.1.0-xt1032.img", but I had no avail, as this message showed up:
downloading 'boot.img'...
OKAY [ 0.275s]
booting...
FAILED (remote failure)
finished. total time: 0.476s
I even followed this thread, http://forum.xda-developers.com/showthread.php?t=2542219 (for restoring the stock firmware), and did everything down to the very letter, and it still didn't work. I kept getting messages like "bab check failed for boot" or "bab check failed for recovery"
I am at my wits end. I don't know if there is anything else to do. If anyone can find a solution to my problem, I'll be forever grateful.
Here is some useful info:
I rememeber updating my phone from ICS to KITKAT (4.4.4) months before i tried to root/flash it.
I bought my phone in the US
"get var all" returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA95000LZM
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 85054F0115000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 16 21:19:52 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_retus/peregrine
(bootloader) ro.build.fingerprint[1]: :4.4.4/KXB21.14-L1.56/56:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.56.peregrine_r
(bootloader) ro.build.version.full[1]: etus.retus.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-gc20375a-00001-g804
(bootloader) kernel.version[1]: 2017 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .7 (GCC) ) #1 SMP PREEMPT Wed Aug 6 01:2
(bootloader) kernel.version[3]: 3:55 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 1/1
(bootloader) ro.carrier: retus
all: listed above

croissanwish said:
I think I permanently soft bricked my phone.
Possible reasons
Click to expand...
Click to collapse
Why are you flashing falcon(xt1032) stuff to your peregrine(xt1045)?
They are not interchangeable.

meekrawb said:
Why are you flashing falcon(xt1032) stuff to your peregrine(xt1045)?
They are not interchangeable.
Click to expand...
Click to collapse
Oh I didn't know that. I'm kind of new to this. Which recovery should I flash?

@croissanwish Hi you have a MOTO G 4G (XT1042 in your case). You need to use this custom recovery https://www.androidfilehost.com/?fid=95864024717072097 TWRP 2.8.3.0 (Credits to Somcom3X). Then and only then flash the custom firmware you want from the http://forum.xda-developers.com/moto-g/4g-development area
If you still have issues after that then PM me.

hacktrix2006 said:
@croissanwish Hi you have a MOTO G 4G (XT1042 in your case). You need to use this custom recovery https://www.androidfilehost.com/?fid=95864024717072097 TWRP 2.8.3.0 (Credits to Somcom3X). Then and only then flash the custom firmware you want from the http://forum.xda-developers.com/moto-g/4g-development area
If you still have issues after that then PM me.
Click to expand...
Click to collapse
Thanks, I got it to work now, it turns out I was using the wrong recovery.

Moto G XT1032 8GB - Completely stock and bootloader locked stuck on Motorola logo

Hello everyone,
last week my Moto G (never unlocked, and completely stock) stopped working. I was on lastest official update, that is Lollipop 5.1, but the problem didn't come up with the update, this was later.
One morning (I have not been shutting down the phone for 1 month I guess) I wake up, it's off. I switch it on and it stays on Motorola logo forever.
If I try to go to fastboot (bootloader version 41.1A) it works, but if I select any option (except the barcode one, the only one working) the phone will go back to the Motorola logo, so I am unable to factory reset and even to go in recovery!
So I tried to erease everything using fastboot and PC: it can communicate with PC, and all commands work EXCEPT the commands that must act on partitions, they ALWAYS return "Remote failure" error.
At that point I tried to unlock the bootloader, maybe that was the problem, but no, same error, always.
Any idea guys? Save my phone please
This is the output for fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9290CPXQ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: BAAE0F020F000000000000000000
(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 Oct 3 15:18:41 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_reteu/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.EURetail.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: MSM8626BP_1032.3116.98.00R EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 18:36:22 CDT 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 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.068s

I have the same exact problem!
Nabbolo said:
Hello everyone,
last week my Moto G (never unlocked, and completely stock) stopped working. I was on lastest official update, that is Lollipop 5.1, but the problem didn't come up with the update, this was later.
One morning (I have not been shutting down the phone for 1 month I guess) I wake up, it's off. I switch it on and it stays on Motorola logo forever.
If I try to go to fastboot (bootloader version 41.1A) it works, but if I select any option (except the barcode one, the only one working) the phone will go back to the Motorola logo, so I am unable to factory reset and even to go in recovery!
So I tried to erease everything using fastboot and PC: it can communicate with PC, and all commands work EXCEPT the commands that must act on partitions, they ALWAYS return "Remote failure" error.
At that point I tried to unlock the bootloader, maybe that was the problem, but no, same error, always.
Any idea guys? Save my phone please
This is the output for fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9290CPXQ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: BAAE0F020F000000000000000000
(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 Oct 3 15:18:41 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_reteu/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.EURetail.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: MSM8626BP_1032.3116.98.00R EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 18:36:22 CDT 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 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.068s
Click to expand...
Click to collapse
My phone was stuck on blue logo in a bootloop, unable to access anything even after entering bootloader. I flashed the firmware through amd but the problem still exists! Please help

It sounds like emmc corruption for which there is no cure. Unfortunately, without an unlocked Bootloader - your options are limited. However we can try some things.
Flash the latest XT1032 (try both GPE and Retail) Factory Firmware Image using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
It sounds like emmc corruption for which there is no cure. Unfortunately, without an unlocked Bootloader - your options are limited. However we can try some things.
Flash the latest XT1032 (try both GPE and Retail) Factory Firmware Image using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
What are the chances with having an unlocked Bootloader?

Xephor_EX said:
What are the chances with having an unlocked Bootloader?
Click to expand...
Click to collapse
How do you mean? Is there a question mark over if the Bootloader is locked or Unlocked? Assuming the Bootloader is locked, the flashing the factory firmware image may resolve a partition issue - if one exists - and allow you to then unlock the Bootloader.
Make sure you are following the Bootloader unlocking tutorial: http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6

lost101 said:
How do you mean? Is there a question mark over if the Bootloader is locked or Unlocked? Assuming the Bootloader is locked, the flashing the factory firmware image may resolve a partition issue - if one exists - and allow you to then unlock the Bootloader.
Make sure you are following the Bootloader unlocking tutorial: http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
Click to expand...
Click to collapse
No, I mean that my bootloader is unlocked, I tried flashing the stock firmwares but the problem still persists.

Xephor_EX said:
No, I mean that my bootloader is unlocked, I tried flashing the stock firmwares but the problem still persists.
Click to expand...
Click to collapse
fastboot boot twrp.img​
Factory reset (and format data if necessary) and flash a custom ROM.

lost101 said:
fastboot boot twrp.img​
Factory reset (and format data if necessary) and flash a custom ROM.
Click to expand...
Click to collapse
I can't enter recovery. The only option which works is the Barcodes one :/

Xephor_EX said:
I can't enter recovery. The only option which works is the Barcodes one :/
Click to expand...
Click to collapse
I didn't ask you to enter Recovery. Do that command via fastboot.

lost101 said:
I didn't ask you to enter Recovery. Do that command via fastboot.
Click to expand...
Click to collapse
I know, I did that. After the the fastboot flashes twrp, the phone screen goes black and shows the moto logo then re-enters bootloader.

Xephor_EX said:
I know, I did that. After the the fastboot flashes twrp, the phone screen goes black and shows the moto logo then re-enters bootloader.
Click to expand...
Click to collapse
I just need to be clear, you are doing:
fastboot boot twrp.img​
not:
fastboot flash recovery twrp.img​

lost101 said:
I just need to be clear, you are doing:
fastboot boot twrp.img​
not:
fastboot flash recovery twrp.img​
Click to expand...
Click to collapse
Mhm, yes.

It looks bad for you. The only remaining option (in my opinion) is to treat the phone as a hard-brick, and unbrick it. This may be a way to undo whatever corruption has occurred on the phone.
[HOW TO] Unbrick Moto G 2013! [Falcon, Peregrine] [Lollipop guide]​

lost101 said:
It looks bad for you. The only remaining option (in my opinion) is to treat the phone as a hard-brick, and unbrick it. This may be a way to undo whatever corruption has occurred on the phone.
[HOW TO] Unbrick Moto G 2013! [Falcon, Peregrine] [Lollipop guide]​
Click to expand...
Click to collapse
Will try it tomorrow. Thanks for the help man, appreciate it.
---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------
Xephor_EX said:
Will try it tomorrow. Thanks for the help man, appreciate it.
Click to expand...
Click to collapse
The phone has actually died before in 2015 due to downgrade from 5.1 Brazil to 4.4.4 updating to 5.0.2 through OTA. A lot of people had been waiting for the mbm files for lollipop and I only got it unbricked through that method in June and now this happened :/

Invalid boot image header - boots but not

Hi,
I have a very strange problem:
I have a XT1032 now is all stock (Android 5.1) but when I wanna boot the phone normal just restarting I get "invalid boot image header" from bootloader. If I reboot to system via TWRP it boots without a problem.
The strange thing is the bootloader output this:
C:\Users\maxim\Desktop\XT1032_FALCON_RETEU_5.1_LPBS23.13-56-2_cid7_CFC.xml>mfastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9290CK5K
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 88AD00020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(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: "Wed Jun 29 21:10:15 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_gpe/falcon_umts:4.
(bootloader) ro.build.fingerprint[1]: 4.4/KTU84P.M003/18:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full:
(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-AeroKernel-g8f87852
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.7
(bootloader) kernel.version[2]: (GCC) ) #63 SMP PREEMPT Wed Nov 5 17:52
(bootloader) kernel.version[3]: :07 CET 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.061s
1.
(bootloader) ro.build.fingerprint[0]: motorola/falcon_gpe/falcon_umts:4.
(bootloader) ro.build.fingerprint[1]: 4.4/KTU84P.M003/18:user/release-keys
2.
(bootloader) kernel.version[0]: Linux version 3.4.42-AeroKernel-g8f87852
Even if I flash CM 13 or reflash the whole firmware with bootloader gpt etc..same problem. I don't know why it says Aero Kernel when I have stock CM 13 or stock 5.1 and boots without a problem. and why GPe ????
I forgot something: if I do mfastboot reboot just that it boots in recovery instead of OS. The recovery is flashed on recovery partition.
using thse:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
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 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
@lost101 any ideeas ?
Thank you very much !

@Eurofighter_ty - Via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​

lost101 said:
@Eurofighter_ty - Via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
Thank you very much ! It worked. I searched on Google for solutions but that thread did not show up.

[Q] Moto G stuck on "Warning Bootloader unlocked" screen[but RECOVERY, FASTBOOT work]

[Q] Moto G stuck on "Warning Bootloader unlocked" screen[but RECOVERY, FASTBOOT work]
A friend sent the phone(MOTO G XT 1069) for assistance, and I believe they bricked the phone, but they told him the "board is defective" .
I have tried mfastboot + adb with ROM 4.4.4 STOCK(all commands) and others ROM's, but it restarts on the same white screen, it vibrates but does not leave this screen(warning bootloader...) ... and RSD LITE (a failure happens) ...
Ps: it can also receive charge through the charger.
ps¹: Should I really give up?
thanks

LOG fastboot:
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4887
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x7
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: 0434404824
(bootloader) cid: 0x000C
(bootloader) channelid: 0x19
(bootloader) uid: DFB473060F000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355***********2
(bootloader) meid:
(bootloader) date: 2014-12-11
(bootloader) sku: XT1069
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jul 8 21:38:38 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retbr_dstv/titan_ud
(bootloader) ro.build.fingerprint[1]: stv:6.0/MPB24.65-34-3/3:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.81.3.titan_retbr_
(bootloader) ro.build.version.full[1]: dstv.retbr.en.BR
(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:
(bootloader) kernel.version[0]: Linux version 3.4.42-g3a1ecea-00026-g0a0
(bootloader) kernel.version[1]: ded4 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Mon Aug 22 14:
(bootloader) kernel.version[3]: 24:06 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V48.87-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.87-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.87-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.87-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.87-0-g1b80345
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: 04*******4
(bootloader) sutinfo:
(bootloader) ro.carrier: retbr
all: listed above
finished. total time: 0.069s

Sorry can't help you much as I'm a bit of a novice but think people will need more info.
What recovery are you using ...twrp ?
And is it the latest version ,does it Boot into the bootloader menu OK ?
I'm not even sure which version of moto g that is but presuming its newer than my xt1039 so why try such a old ROM?
Sent from my XT1039 using Tapatalk

steve.loveday said:
Sorry can't help you much as I'm a bit of a novice but think people will need more info.
What recovery are you using ...twrp ?
And is it the latest version ,does it Boot into the bootloader menu OK ?
I'm not even sure which version of moto g that is but presuming its newer than my xt1039 so why try such a old ROM?
Sent from my XT1039 using Tapatalk
Click to expand...
Click to collapse
Recovery: Apparently it is stock, is written "Android Recovery"
Old ROM, was to try to see if he(moto g) would come back ...
thanks and forgive my english

Desmios said:
Recovery: Apparently it is stock, is written "Android Recovery"
Old ROM, was to try to see if he(moto g) would come back ...
thanks and forgive my english
Click to expand...
Click to collapse
Sounds like its just had its bootloader unlocked at that's it
Double check your model is definitely xt1069 and follow this guide to put new recovery and ROM
https://wiki.cyanogenmod.org/w/Install_CM_for_titan
Sent from my XT1039 using Tapatalk

I had exactly the same problem as you on an XT1032. It was a faulty internal storage (faulty hardware). It lets you flash the files and replace recovery and everything, but never boots, always stays at the bootlogo, not even bootanimation.
You can try the following:
a) Download the stock firmware from another source, then flash it again via mfastboot, read carefully the command output in the computer and in the fastboot screen. Both should say OK or report success in some way. Check if some command causes pink/red message lines in the fastboot screen.
b) Maybe you're forgetting some command in mfastboot?
c) Try flashing TWRP, then wiping all partitions from there and then flashing CyanogenMOD or another stable ROM. If there's an IO error, TWRP's verbosity will help you finding it.
Good luck.

moralesnery said:
I had exactly the same problem as you on an XT1032. It was a faulty internal storage (faulty hardware). It lets you flash the files and replace recovery and everything, but never boots, always stays at the bootlogo, not even bootanimation.
You can try the following:
a) Download the stock firmware from another source, then flash it again via mfastboot, read carefully the command output in the computer and in the fastboot screen. Both should say OK or report success in some way. Check if some command causes pink/red message lines in the fastboot screen.
b) Maybe you're forgetting some command in mfastboot?
c) Try flashing TWRP, then wiping all partitions from there and then flashing CyanogenMOD or another stable ROM. If there's an IO error, TWRP's verbosity will help you finding it.
Good luck.
Click to expand...
Click to collapse
Hello
My Moto G is also stuck on the unlocked bootloader screen, i cant even turn my mobile off (only via fastboot-> recover -> turn mobile off ).
I would flash a rom but i went totally wrom it seems.. im a noob with this things..
So, I have cyanogenmod recovery, but ive already tried to factory reset, wipe system partition and cache, but nothing has changed.
My PC dont recognize my MOTO G anymore because USB debugging is probably off.. Thats why i cant use command promt now ...
So.. is my mobile broken forever?
Or is there someone who can fix it?
(I was also wondering if someone is Dutch here, so i can bring the phone to repair it... if he can be repaired)
Im afraid he will never works again
Kind regards
Lauji
UPDATE: Solved by new recovery (twrp) and flashed another rom with GApps Package.

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