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

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.

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

How to Relock the bootloader on moto z xt-1650-03

Hi All,
NOTE: I am not responsible for anything that might happen to your device while doing this. (it most likely is not).
I have made this tutorial just to help other people I noticed there was no step by step tutorial on how to Relock the bootloader on moto z xt-1650-03 so I have decided to make a guide explaining How to Relock the bootloader on moto z xt-1650-03. Submit a Thanks to lesbianu, he helped me out figuring this...
1 - Download GRIFFIN_OPLS27.76-51-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Rom ( I used https://androidfilehost.com/?fid=5862345805528054929 )
2 - Download the Android SDK Platform-Tools ( I used the latest from Google: https://developer.android.com/studio...platform-tools )
3 - Extract the Android SDK Platform-Tools and within that same folder also extract the ROM
4 – On the address bar. Type CMD and Hit Enter.
5 – To Check device connectivity. Type “adb devices”
6 – Boot into bootloader mode. type “adb reboot bootloader”
7 – Ones you are into bootloader mode. Check the Device connectivity Again. Type “fastboot devices”
As soon as you press enter key, you’ll see a message saying ‘List of devices attached’ along with some random numbers. This will confirm that your Moto Z has properly connected to your computer.
8 - Run the first set of commands i.e.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
9 – Once the Flashing is Done. Directly press the power button to boot the device. let the device boots up completely.
10 – complete the first time phone configuration process. (Make sure Internet is working on your device)
11 - after completing the setup go to the setting - system - about phone - tap on the built no several time to unlock the developer options.
12 – Go to the developer option and click on "OEM unlocking" and “Allow USB debugging”
13 – Don’t reboot your Device. And Connect your Phone to PC.
14 - Again open the same folder, where you extracted your ROM and SDK tools and within that same folder again open a command prompet and type “ adb reboot bootloader “
ones again you will come back to the bootloader mode.
15 - after the phone is back to bootloader mode, run the second set of commands I.e.
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash boot boot.img
fastboot oem lock
14 – After the last set of commands if everything goes well then Congrats you just relocked your Bootloader... Successfully....

as a question, what version of bootloader do you have? or doesn't care to the process?

eLaDiio said:
as a question, what version of bootloader do you have? or doesn't care to the process?
Click to expand...
Click to collapse
the first script updates the bootloader

Hello,
I need some help.
After following your guide it starts the ROM fine.
After a restart of the phone i get stuck in "no command" screen. (wipe don´t help in this case)
Starting thru the fastboot "start" will boot the phone correctly!
After that I tried to get back to LinageOS, now same problem, always boots to TRWP after installing ROM, starting correctly und restart phone.
May be this is ab Problem with the bootloader?
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB TOSHIBA THGBF7G8K4LBATRB FV=0300
(bootloader) ram: 4GB SKHYNIX LP4 DIE=8Gb M5=06 M6=03 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: EAE795CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-24-2017
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:8.0.0/OPL
(bootloader) ro.build.fingerprint[1]: S27.76-51-5/6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.6.griffin.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.29.01R SRD
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gbf602b0 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue May 29 07:26:28 CDT 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.03-0-g722a114
(bootloader) tz.git: git=d9d553d-dirty
(bootloader) hyp.git: git=d9d553d-dirty
(bootloader) devcfg.git: git=d9d553d-dirty
(bootloader) keymaster.git: git=d9d553d-dirty
(bootloader) cmnlib.git: git=d9d553d-dirty
(bootloader) cmnlib64.git: git=d9d553d-dirty
(bootloader) prov.git: git=d9d553d-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
I think here is the Problem: Reboot mode set to fastboot
fastboot oem fb_mode_clear doesn´t change it.
Any suggestions?

Its methods working after update ota to may security patch?

Ceptoz said:
Its methods working after update ota to may security patch?
Click to expand...
Click to collapse
as YamazakiRobert told, the first script updates the bootloader. so it desent matter which version of bootloader you have. The rom is having the latest version of the Bootloader, so if you are on the old version of bootloader, this will update your bootloader version and then you can relock your bootloader with the second sets of commands.

dorscht said:
Hello,
I need some help.
After following your guide it starts the ROM fine.
After a restart of the phone i get stuck in "no command" screen. (wipe don´t help in this case)
Starting thru the fastboot "start" will boot the phone correctly!
After that I tried to get back to LinageOS, now same problem, always boots to TRWP after installing ROM, starting correctly und restart phone.
May be this is ab Problem with the bootloader?
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB TOSHIBA THGBF7G8K4LBATRB FV=0300
(bootloader) ram: 4GB SKHYNIX LP4 DIE=8Gb M5=06 M6=03 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: EAE795CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-24-2017
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:8.0.0/OPL
(bootloader) ro.build.fingerprint[1]: S27.76-51-5/6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.6.griffin.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.29.01R SRD
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gbf602b0 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue May 29 07:26:28 CDT 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.03-0-g722a114
(bootloader) tz.git: git=d9d553d-dirty
(bootloader) hyp.git: git=d9d553d-dirty
(bootloader) devcfg.git: git=d9d553d-dirty
(bootloader) keymaster.git: git=d9d553d-dirty
(bootloader) cmnlib.git: git=d9d553d-dirty
(bootloader) cmnlib64.git: git=d9d553d-dirty
(bootloader) prov.git: git=d9d553d-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
I think here is the Problem: Reboot mode set to fastboot
fastboot oem fb_mode_clear doesn´t change it.
Any suggestions?
Click to expand...
Click to collapse
what does it shows you on -
fastboot oem fb_mode_clear
and
fastboot oem fb_mode_set

saifprvz said:
what does it shows you on -
fastboot oem fb_mode_clear
and
fastboot oem fb_mode_set
Click to expand...
Click to collapse
C:\ADB\tools>fastboot oem fb_mode_set
OKAY [ 0.005s]
Finished. Total time: 0.007s
C:\ADB\tools>fastboot oem fb_mode_clear
OKAY [ 0.004s]
Finished. Total time: 0.006s
and after reboot and check with "fastboot getvar all" still:
(bootloader) reason: Reboot mode set to fastboot

Guys for me everything worked but when i try OTA update it doesnt install it says error when trying to install it any help pls

I relocked the bootloader before the OP opened this thread: https://forum.xda-developers.com/showpost.php?p=77177509&postcount=110
The July OTA installed just fine on mine!
Try to sideload the OTA zip using a PC... If you are still receiving an error, the only way I can see it: is to unlock the bootloader again and then re-locking it back. If all goes well, you can re-test the July OTA. Good luck! :good:

lesbianu said:
I relocked the bootloader before the OP opened this thread: https://forum.xda-developers.com/showpost.php?p=77177509&postcount=110
The July OTA installed just fine on mine!
Try to sideload the OTA zip using a PC... If you are still receiving an error, the only way I can see it: is to unlock the bootloader again and then re-locking it back. If all goes well, you can re-test the July OTA. Good luck! :good:
Click to expand...
Click to collapse
I dont really know what sideload means and how it works can u give me detailed instructions please

Hard to explain it step-by-step, check this tutorial: https://www.getdroidtips.com/moto-z-android-oreo-opl27-76-57/
Use all the information from there, but when you reach Step-8 Now to flash the firmware give the following command, use this command:
Code:
ADB sideload Blur_Version.27.231.8.griffin.retail.en.US (OPLS27.76-51-7).zip
The OTA file to update to 1 June 2018 it's HERE (I downloaded it using @erfanoabdi's tool).
Hope you can mange it!
---------- Post added at 10:01 PM ---------- Previous post was at 09:59 PM ----------
You can change the OTA filename from Blur_Version.27.231.8.griffin.retail.en.US (OPLS27.76-51-7).zip to OTA.zip, so the command will become:
Code:
ADB sideload OTA.zip

I have OPLS27.77-51-7 (July update) - Can I safety do this as pots #1 with GRIFFIN_OPLS27.76-51-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Rom Software?

If you updated via OTA to the latest firmware you'll have to wait for the corresponding firmware zip file to emerge on internet. It should contain your latest build in the name of the zip, something like: GRIFFIN_OPLS27.77-51-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
The firmware file from the 1st post it's older than your current installed ROM. You will receive errors...

Works all the guide, i will put my info about if works the update via OTA, thanks for the guide
i can't update my phone, while was installing send error on the screen, i will force it by sideload anyway

If you receive error, check it. Others got an error related to bluetooth firmware...

lesbianu said:
If you receive error, check it. Others got an error related to bluetooth firmware...
Click to expand...
Click to collapse
i had the same error about the bt firm when i tried to sideload

Here is another guy with the same problem. I wrote there what I would do...

lesbianu said:
Here is another guy with the same problem. I wrote there what I would do...
Click to expand...
Click to collapse
Hi, so i tried everything (sideload, reflash) and it didnt work.
I unlocked my bootloader again and installen the OTA then through phone, and it worked. But I'd like to lock my bootloader, can u tell me how to do that now without flashing the older versions? So just locking it now.

If you updated to the latest version: OPLS27.76.-51-7 (1 July security patch) you cannot re-lock the bootloader until a OPLS27.76.-51-7 full firmware .zip file will be available for download. Sorry!
You had to re-flash OPLS27.76-51-5, re-lock the bootloader and after that to test the latest OTA (I wrote the steps on the post for the other guy). That way your phone would be locked and updated to the latest ROM. Now you have to wait...
---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------
@Pathera

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