Database Info

Moto G Boot up failed

Good my phone has suddenly been hung and when forced reboot is then left in the logo of motorola and it's not from there, I tried to make this tutorial and "appears" that does everything well but then when rebooting just does not start as usual
When trying to enter the recovery says "boot up failed" and tried to install a custom recovery and I get the same

angelgzg said:
Good my phone has suddenly been hung and when forced reboot is then left in the logo of motorola and it's not from there, I tried to make this tutorial and "appears" that does everything well but then when rebooting just does not start as usual
When trying to enter the recovery says "boot up failed" and tried to install a custom recovery and I get the same
Click to expand...
Click to collapse
Try to reflash the stock firmware or, even better, the 4.4.4 of your stock firmware.

oversleeper said:
Try to reflash the stock firmware or, even better, the 4.4.4 of your stock firmware.
Click to expand...
Click to collapse
Where I can download a 4.4.4 firmware and not a full upgrade? and 4.4.3 and try anything

angelgzg said:
Where I can download a 4.4.4 firmware and not a full upgrade? and 4.4.3 and try anything
Click to expand...
Click to collapse
Here

oversleeper said:
Here
Click to expand...
Click to collapse
I get these errors trying
hab check failed for boot
hab check failed for recovery

angelgzg said:
I get these errors trying
hab check failed for boot
hab check failed for recovery
Click to expand...
Click to collapse
That's because you're flashing a non stock firmware. Just ignore that error. Run all commands and all should work properly.

oversleeper said:
That's because you're flashing a non stock firmware. Just ignore that error. Run all commands and all should work properly.
Click to expand...
Click to collapse
This error also should ignore it?
piv signed invalid system image
Just do not start everything but it stays on the logo and I can not get into the recovery?
I'm thinking that the problem is hardware: ((((

angelgzg said:
This error also should ignore it?
piv signed invalid system image
Just do not start everything but it stays on the logo and I can not get into the recovery?
I'm thinking that the problem is hardware: ((((
Click to expand...
Click to collapse
Run the command fastboot.exe getvar all or mfastboot.exe getvar all and post the result.

oversleeper said:
Run the command fastboot.exe getvar all or mfastboot.exe getvar all and post the result.
Click to expand...
Click to collapse
C:\Users\Usuario\Desktop\Minimal ADB and Fastboot>mfastboot.exe getvar all
version: 0.5
version-bootloader: 4111
product: falcon
secure: yes
hwrev: 0x83C0
radio: 0x1
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
ram: 1024MB Samsung S4 SDRAM DIE=4Gb
cpu: MSM8226 CS
serialno: TA93005UU8
cid: 0x0009
channelid: 0x00
uid: C3A9C5020F000000000000000000
unlocked: no
iswarrantyvoid: no
mot_sst: 0
max-download-size: 536870912
reason: Volume down key pressed
imei:
meid:
date:
sku:
iccid:
cust_md5:
max-sparse-size: 268435456
current-time: "Wed Aug 6 0:23: 7 UTC 2014"
ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
ro.build.fingerprint[2]: ease-keys
ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
ro.build.version.full[1]: s.Retail.en.US
ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
ro.build.version.qcom[1]: .04.04.02.048.020
version-baseband:
kernel.version[0]: Linux version 3.4.42-g26ca2df ([email protected]
kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
sbl1.git: git=MBM-NG-V41.11-0-gcff5797
rpm.git: git=MBM-NG-V41.11-0-g71b1aae
tz.git: git=MBM-NG-V41.11-0-ga27c415
aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
qe: qe 0/1
ro.carrier: unknown
all: listed above
finished. total time: 0.155s

angelgzg said:
C:\Users\Usuario\Desktop\Minimal ADB and Fastboot>mfastboot.exe getvar all
version: 0.5
version-bootloader: 4111
product: falcon
secure: yes
hwrev: 0x83C0
radio: 0x1
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
ram: 1024MB Samsung S4 SDRAM DIE=4Gb
cpu: MSM8226 CS
serialno: TA93005UU8
cid: 0x0009
channelid: 0x00
uid: C3A9C5020F000000000000000000
unlocked: no
iswarrantyvoid: no
mot_sst: 0
max-download-size: 536870912
reason: Volume down key pressed
imei:
meid:
date:
sku:
iccid:
cust_md5:
max-sparse-size: 268435456
current-time: "Wed Aug 6 0:23: 7 UTC 2014"
ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
ro.build.fingerprint[2]: ease-keys
ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
ro.build.version.full[1]: s.Retail.en.US
ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
ro.build.version.qcom[1]: .04.04.02.048.020
version-baseband:
kernel.version[0]: Linux version 3.4.42-g26ca2df ([email protected]
kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
sbl1.git: git=MBM-NG-V41.11-0-gcff5797
rpm.git: git=MBM-NG-V41.11-0-g71b1aae
tz.git: git=MBM-NG-V41.11-0-ga27c415
aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
qe: qe 0/1
ro.carrier: unknown
all: listed above
finished. total time: 0.155s
Click to expand...
Click to collapse
Download this.

oversleeper said:
Download this.
Click to expand...
Click to collapse
Now try this firmware installation and does everything well without errors but when restart is the motorola logo
any way to know if this completely-dead?

angelgzg said:
Now try this firmware installation and does everything well without errors but when restart is the motorola logo
any way to know if this completely-dead?
Click to expand...
Click to collapse
Since you are under warranty the best thing to do is to send it to Motorola...

oversleeper said:
Since you are under warranty the best thing to do is to send it to Motorola...
Click to expand...
Click to collapse
Well I bought it from amazon USA, I'm from Venezuela so I think that's not a possibility? that alternatives do I have? it could be converted into brick? unbrick then?
I also tried unlocking the bootloader and I get the message in purple unlocked and restarted but then goes into fastboot mode as if not done
I changed usb cable and now I get status code = 3, but now does not advance after the warning screen and enter android recovery goes the "no command"

angelgzg said:
Well I bought it from amazon USA, I'm from Venezuela so I think that's not a possibility? that alternatives do I have? it could be converted into brick? unbrick then?
I also tried unlocking the bootloader and I get the message in purple unlocked and restarted but then goes into fastboot mode as if not done
I changed usb cable and now I get status code = 3, but now does not advance after the warning screen and enter android recovery goes the "no command"
Click to expand...
Click to collapse
Ok... now your bootloader is unlocked and your warranty gone, so you can try the next level. Follow my thread. You have to use the bricker script, then when your device will be recognized as qhsusb_bulk I'll give you the tool to reflash the bootloader.

oversleeper said:
Ok... now your bootloader is unlocked and your warranty gone, so you can try the next level. Follow my thread. You have to use the bricker script, then when your device will be recognized as qhsusb_bulk I'll give you the tool to reflash the bootloader.
Click to expand...
Click to collapse
Well now the computer does not pass the warning screen when entering the bootloader and recovery I get the android with exclamation mark and says no command
this is the phone info using this command (mfastboot.exe getvar all)
C:\Minimal ADB and Fastboot>mfastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4111
(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 Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA93005UU8
(bootloader) cid: 0x0009
(bootloader) channelid: 0x00
(bootloader) uid: C3A9C5020F000000000000000000
(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: "Wed Aug 6 3:39:14 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
(bootloader) ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.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-g26ca2df ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.11-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.11-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.054s
C:\Minimal ADB and Fastboot>

oversleeper said:
Ok... now your bootloader is unlocked and your warranty gone, so you can try the next level. Follow my thread. You have to use the bricker script, then when your device will be recognized as qhsusb_bulk I'll give you the tool to reflash the bootloader.
Click to expand...
Click to collapse
after using the recommended script happens happens happens
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y / N]?, And
target-sparse max-size: 256MB
sending 'fsg' (102 KB) ...
OKAY [0.027s]
writing 'fsg' ...
OKAY [3.145s]
finished. Total time: 3.175s
target-sparse max-size: 256MB
sending 'rpm' (200 KB) ...
OKAY [0.038s]
writing 'rpm' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.330s
target-sparse max-size: 256MB
sending 'SBL1' (264 KB) ...
OKAY [0.057s]
writing 'SBL1' ...
OKAY [0.028s]
finished. Total time: 0.088s
target-sparse max-size: 256MB
sending 'sdi' (32 KB) ...
OKAY [0.058s]
writing 'sdi' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.343s
target-sparse max-size: 256MB
sending 'tz' (400 KB) ...
OKAY [0.084s]
writing 'tz' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.392s
rebooting ...
finished. Total time: 0.003s
Your device is now hard bricked!
Press any key to continue. . .
But still I can get into fastboot mode and the pc recognizes me as android device

angelgzg said:
after using the recommended script happens happens happens
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y / N]?, And
target-sparse max-size: 256MB
sending 'fsg' (102 KB) ...
OKAY [0.027s]
writing 'fsg' ...
OKAY [3.145s]
finished. Total time: 3.175s
target-sparse max-size: 256MB
sending 'rpm' (200 KB) ...
OKAY [0.038s]
writing 'rpm' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.330s
target-sparse max-size: 256MB
sending 'SBL1' (264 KB) ...
OKAY [0.057s]
writing 'SBL1' ...
OKAY [0.028s]
finished. Total time: 0.088s
target-sparse max-size: 256MB
sending 'sdi' (32 KB) ...
OKAY [0.058s]
writing 'sdi' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.343s
target-sparse max-size: 256MB
sending 'tz' (400 KB) ...
OKAY [0.084s]
writing 'tz' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.392s
rebooting ...
finished. Total time: 0.003s
Your device is now hard bricked!
Press any key to continue. . .
But still I can get into fastboot mode and the pc recognizes me as android device
Click to expand...
Click to collapse
Try to download this and run the boot loader tool first. Post the result.

oversleeper said:
Try to download this and run the boot loader tool first. Post the result.
Click to expand...
Click to collapse
It seems like everything I do not change anything
Install recovery shows no error, but still comes out the same and yet so
C:\Users\PC\Desktop\Tools\DeviceInfo>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4111
(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 Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA93005UU8
(bootloader) cid: 0x0009
(bootloader) channelid: 0x00
(bootloader) uid: C3A9C5020F000000000000000000
(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: "Wed Aug 6 14: 2:16 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
(bootloader) ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.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-g26ca2df ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.11-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.11-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.055s
C:\Users\PC\Desktop\Tools\DeviceInfo>pause
Presione una tecla para continuar . . .

angelgzg said:
It seems like everything I do not change anything
Install recovery shows no error, but still comes out the same and yet so
C:\Users\PC\Desktop\Tools\DeviceInfo>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4111
(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 Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA93005UU8
(bootloader) cid: 0x0009
(bootloader) channelid: 0x00
(bootloader) uid: C3A9C5020F000000000000000000
(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: "Wed Aug 6 14: 2:16 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
(bootloader) ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.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-g26ca2df ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.11-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.11-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.055s
C:\Users\PC\Desktop\Tools\DeviceInfo>pause
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
Try the others 2 tools in the package. Don't worry I think your device is ok.

oversleeper said:
Try the others 2 tools in the package. Don't worry I think your device is ok.
Click to expand...
Click to collapse
What other options do I have?

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

HELP Saving data before hard reset with only recovery mode accessible

After updating by itself with almost empty battery (probably to Android 10) my device wont boot up anything except Fastboot and Recovery Mode. On this device I did not modify anything at all previously, no root, no custom bootloader no nothing. I did not even unlock developer options/usb debugging in the settings, which is probably what now haunts me. I know a factory reset will be an easy fix, but I would really like to recover at least some data first, which seems pretty impossible to do but im not just ready to give up.
I can get very limitied acces through ADB.
- If I choose "Apply update from ADB" in Recovery mode, my PC reconizes the device in the device-manager and I can choose drivers etc. But obvioulsly not view files in the explorer or anythng else helpful.
- The command "fastboot getvar all" works and spits out a huge list of variables about the phone
- The command "adb devices" displays a number and "sideload" when the option "Apply update from ADB" is selected in the Recovery, but nothing at all is displyed when that option is not selected.
- I can't get any pull, backup etc. commands to work.
All of this is probably because I never activated the developer options on my phone. So my question is basically can I retreive my data in any way, or can I somehow activate the developer options with what I have right now.
Another option I got recommended is getting a clean Anroid ROM and loading it with the option "Apply update from SD card" or trying to use "sideload" again to get it there. But I can not find a clean Image of Android for the Motorola G7 power anywhere that I could try out, only custom ROMS and I know that these will delete my data for certain.
I would be very thankfull for any recommendations.
this is what the ADB commands spit out:
(with "Apply Update from ADB" running)
PS C:\adb\platform-tools> .\adb devices
List of devices attached
ZY3266SVDK sideload
(in Fastboot):
PS C:\adb\platform-tools> .\adb devices
List of devices attached
PS C:\adb\platform-tools> .\adb pull "sdcard"
adb: error: failed to get feature set: no devices/emulators found
PS C:\adb\platform-tools> .\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY3266SVDK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x2a
(bootloader) uid: D7DCF56600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359507099705734
(bootloader) meid:
(bootloader) date: 06-04-2019
(bootloader) sku: XT1955-2
(bootloader) carrier_sku: XT1955-2
(bootloader) battid: SB18C28957
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 6 17:46:47 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPOS29.114-
(bootloader) ro.build.fingerprint[1]: 134-13/6abfe:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.18.ocean.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_26.100.01.120.03R OCEAN_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld105) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 09:26:39 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-516ad1ccba-200403
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) devcfg.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) keymaster.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) prov.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: protected (277)
(bootloader) ro.carrier: altmx
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.154s

Jhon3323 said:
After updating by itself with almost empty battery (probably to Android 10) my device wont boot up anything except Fastboot and Recovery Mode. On this device I did not modify anything at all previously, no root, no custom bootloader no nothing. I did not even unlock developer options/usb debugging in the settings, which is probably what now haunts me. I know a factory reset will be an easy fix, but I would really like to recover at least some data first, which seems pretty impossible to do but im not just ready to give up.
I can get very limitied acces through ADB.
- If I choose "Apply update from ADB" in Recovery mode, my PC reconizes the device in the device-manager and I can choose drivers etc. But obvioulsly not view files in the explorer or anythng else helpful.
- The command "fastboot getvar all" works and spits out a huge list of variables about the phone
- The command "adb devices" displays a number and "sideload" when the option "Apply update from ADB" is selected in the Recovery, but nothing at all is displyed when that option is not selected.
- I can't get any pull, backup etc. commands to work.
All of this is probably because I never activated the developer options on my phone. So my question is basically can I retreive my data in any way, or can I somehow activate the developer options with what I have right now.
Another option I got recommended is getting a clean Anroid ROM and loading it with the option "Apply update from SD card" or trying to use "sideload" again to get it there. But I can not find a clean Image of Android for the Motorola G7 power anywhere that I could try out, only custom ROMS and I know that these will delete my data for certain.
I would be very thankfull for any recommendations.
this is what the ADB commands spit out:
(with "Apply Update from ADB" running)
PS C:\adb\platform-tools> .\adb devices
List of devices attached
ZY3266SVDK sideload
(in Fastboot):
PS C:\adb\platform-tools> .\adb devices
List of devices attached
PS C:\adb\platform-tools> .\adb pull "sdcard"
adb: error: failed to get feature set: no devices/emulators found
PS C:\adb\platform-tools> .\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY3266SVDK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x2a
(bootloader) uid: D7DCF56600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359507099705734
(bootloader) meid:
(bootloader) date: 06-04-2019
(bootloader) sku: XT1955-2
(bootloader) carrier_sku: XT1955-2
(bootloader) battid: SB18C28957
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 6 17:46:47 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPOS29.114-
(bootloader) ro.build.fingerprint[1]: 134-13/6abfe:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.18.ocean.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_26.100.01.120.03R OCEAN_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld105) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 09:26:39 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-516ad1ccba-200403
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) devcfg.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) keymaster.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) prov.git: MBM-2.1-ocean_retail-e4c78bcf8f-200403
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: protected (277)
(bootloader) ro.carrier: altmx
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.154s
Click to expand...
Click to collapse
Have u tried to fastboot a recovery image like orange fox if u still need more help head over to Moto g7 power soport group in tellagram

roadkill42 said:
Have u tried to fastboot a recovery image like orange fox if u still need more help head over to Moto g7 power soport group in tellagram
Click to expand...
Click to collapse
Oh ok thanks a lot I will look into that. Is "mG7Power" the group?

Jhon3323 said:
Oh ok thanks a lot I will look into that. Is "mG7Power" the group?
Click to expand...
Click to collapse
Motog7 power suport force. Or motog7 power suport

Stuck in useless bootloader! Help!

I tried installing Lineage 18.1, the appropriate Gapps and Magisk. Booted directly into TWRP (without flashing it) and did everything as per usual, followed the instructions, so no rebooting in-between etc.
Now all my phone can do is bootloader. Notably, the usual "broken android guy" picture is gone and so are the labels of the volume up/down buttons (though they do function and it displays "restart bootloader" or "recovery mode" or "factory" etc on top of the screen). Trying to boot, even with "fastboot continue", just brings me back to the bootloader, same with attempting to use recovery (shows error message and brings me back).
The serial number has changed from what it used to be and while fastboot does detect the device (with the aforementioned new ID), it can't do anything. All attempts to boot or flash are met with errors, usually accompanied with:
FAILED (remote: '')
and usually with "permission denied". Bootloader claims "oem_locked". Trying to "oem get_unlock_data"
Attempting to flash recovery to boot shows "invalid partition name boot" (changing it to "boot_a" or "boot_b" doesn't help). Can't just boot the recovery image from the computer either - once again, "permission denied" and FAILED (remote: '').
The oem unlock command returns "feature disabled".
The getvar current-slot command returns "current-slot: "
Trying to set active slot to either A or B returns "Command is not allowed".
Trying to flash stock image is no use, as no commands (outside of getvar max-sparse-size) work at all.
Motorola's Rescue Assistant couldn't detect my device (or rather, it could - said my device is '' and wasn't able to do anything with it). I've reinstalled the Motorola drivers and it was no help, although I admittedly can't find it in the device manager - should it be under "Ports" or is "Android Device -> Motorola ADB Interface" all that's supposed to show?
Bootloader screen:
Code:
AP Fastboot Flash Mode (Secure)
BL: MBM-2.1-ocean_retail-cfdb645cf1d-210201
Baseband:
Product/variant: ocean radio6 64GB PVT1
Serial Number: d890e31
CPU: SDM632
eMMC: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
DRAM: 4GB MICRON LP3 DIE=3Gb M5=FF M6=01 M&=00 M8=5F
Console [NULL]: null
Console [default]: ttyMSM0,115200,n8
(I can switch between the two with "Switch console" via the volume buttons)
Tools Mode Config: DISABLED/ENABLED
(can switch with "Switch Tools mode" via volume buttons)
Battery OK
oem_locked
Transfer Mode: USB Connected
I'm running out of ideas. I've had trouble before, but at least then I could use the bootloader to attempt some fixing. Worst case scenario used to be losing all data and having to reflash the stock. This is so much worse - I can't even do anything! Does anyone have any ideas??
EDIT: getvar all results just in case:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-cfdb645cf1d-210201
(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: d890e31
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ocean_retail-cfdb645cf1d-210201
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
all: listed above

UPDATE: The command oem blankflash successfully sends my phone into blank flash mode. However, all attempts at blankflashing end immediately with a:
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
error message.
Code:
**** Log buffer [000001] 2021-04-03_13:03:13 ****
[ -0.000] Opening device: \\.\COM7
[ 0.009] Detecting device
[ 4.031] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.031] Check qboot_log.txt for more details
[ 4.031] Total time: 4.032s
[ 4.031]
[ 4.031] qboot version 3.40
[ 4.031]
[ 4.031] DEVICE {
[ 4.031] name = "\\.\COM7",
[ 4.031] flags = "0x64",
[ 4.031] addr = "0x61FE4C",
[ 4.031] api.bnr = "0xE52CF8",
[ 4.031] }
[ 4.031]
[ 4.031]
[ 4.031] Backup & Restore {
[ 4.031] num_entries = 0,
[ 4.031] restoring = "false",
[ 4.031] backup_error = "not started",
[ 4.031] restore_error = "not started",
[ 4.031] }
[ 4.031]

Try to reflash stock firmware from https://mirrors.lolinet.com/firmware/moto/ then you will be able to boot stock. The next time you flash a custom Rom flash copypartitionsAB.zip before flashing anything else

Help needed on custom rom

EDIT:
1 - I don't really care about rooting the phone. I'd simply like to have Lineage OS on it.
2 - I don't really care about having a installed version of TWRP, I can do the fastboot boot only if that would work to install lineage on there.
So I unlock the bootloader fine.
Now following this :
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
I am able to
fastboot boot twrp.img
Then I do the install of the .zip from the TWRP site.
Wipe davlik and reboot
System starts fine. I reboot in bootloader mode (power + volumn down) then go to recovery
it has that
N/A in the top corner, flash black and buzz, flash black again then the androdi starts normally.
I read somewhere the this is a bootloop - and I should install Magisk from TWRP, which I did probably incorrectly at one point.
Booting back into fastboot boot twrp.img
I wipe advanced (system davlik data system)
Then Advanced Fix Recovery Bootloop
Then this seems to be not good:
Unpacking Boot...
Backing up Boot...
Patching kernel...
(in red)
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
So did I screw up my kernel while trying to install magisk ? What would be the next step?
Would it make sense to flash the original firmware from here:
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com
The question I would have is which one should I choose in there:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
The retail one? Mine is factory unlocked, not connected to any network,
MPN: Moto G7 Play, XT1952-1
Network: Unlocked
The phone still work fine (I think, didn't do more than booting and checking the internet).

damaru said:
EDIT:
1 - I don't really care about rooting the phone. I'd simply like to have Lineage OS on it.
2 - I don't really care about having a installed version of TWRP, I can do the fastboot boot only if that would work to install lineage on there.
So I unlock the bootloader fine.
Now following this :
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
I am able to
fastboot boot twrp.img
Then I do the install of the .zip from the TWRP site.
Wipe davlik and reboot
System starts fine. I reboot in bootloader mode (power + volumn down) then go to recovery
it has that
N/A in the top corner, flash black and buzz, flash black again then the androdi starts normally.
I read somewhere the this is a bootloop - and I should install Magisk from TWRP, which I did probably incorrectly at one point.
Booting back into fastboot boot twrp.img
I wipe advanced (system davlik data system)
Then Advanced Fix Recovery Bootloop
Then this seems to be not good:
Unpacking Boot...
Backing up Boot...
Patching kernel...
(in red)
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
So did I screw up my kernel while trying to install magisk ?
Click to expand...
Click to collapse
If you tried to install magisk, it may be interfering with TWRP.
damaru said:
What would be the next step?
Would it make sense to flash the original firmware from here:
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com
The question I would have is which one should I choose in there:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
The retail one? Mine is factory unlocked, not connected to any network,
MPN: Moto G7 Play, XT1952-1
Network: Unlocked
The phone still work fine (I think, didn't do more than booting and checking the internet).
Click to expand...
Click to collapse
A few different options
to find the correct Firmware you need to know
Software Channel, Codename, Software Version, and Model #
all of these can be found in the getvar all (remove imei before posting getvar all)
Code:
fastboot getvar all
or you can use LMSA's rescue option, LMSA will find the newest firmware for your device,
So if it's the same Software version as what is on the device, can just flash the boot.img from the firmware folder.
Code:
fastboot flash boot boot.img
or use
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

sd_shadow said:
fastboot flash boot.img
Click to expand...
Click to collapse
That would be fastboot flash boot boot.img right?
I've downloaded the appropriate firmware using fastboot getvar all to get the right model. The phone boots properly (it wasn't after I used the wrong firmware). But then I get to the same error when I fastboot boot twrn.img and try the advance Fix Recovery Bootloop.
When I did flash the whole firmware, the Bad Code was back, then I flashed TWRP and then the N/A was there and when I tried to boot to recovery the same loop happened.
From my lack of understanding, did I updated the Kernel when I reflashed the firmware? And does magisk modify my Kernel. How would I put back the original kernel?
Thanks for the support it's greatly appreciated! I've been on this for too many hours now!

As you mentioned that I should remove my emei before posting this I though that posting it might help
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:56:26 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.010s

damaru said:
That would be fastboot flash boot boot.img right?
Click to expand...
Click to collapse
correct
damaru said:
As you mentioned that I should remove my emei before posting this I though that posting it might help
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:56:26 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.010s
Click to expand...
Click to collapse
Well, a few things don't look right.
Code:
(bootloader) reason: Reboot mode set to fastboot
Likely cause from not using fb_clear after flashing
Code:
fastboot oem fb_mode_clear
Baseband is missing
Code:
(bootloader) version-baseband: <not found>
Did you use firmware from RetCA?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

Yes this is the one I used. I might have done more fastboot stuff than what was in the xml file (these are from the post itself and not from the firmware file):
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
which in the retca xml only had :
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>
should I reflash the whole thing, omitting the erase at the end?

damaru said:
Yes this is the one I used. I might have done more fastboot stuff than what was in the xml file (these are from the post itself and not from the firmware file):
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
which in the retca xml only had :
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>
should I reflash the whole thing, omitting the erase at the end?
Click to expand...
Click to collapse
No, if you used fastboot oem fb_mode_clear
then something else is going on

So the rescue and smart assistant is not working on that particular model (or so Lenovo say) should I try anyway?
I get a Start Up Failed now. So I can't boot in the normal phone anymore. Not sure what I did wrong. So to get back to a normal phone flashing the whole firmware wouldn't help?
I'm at a place where I'd like to bring back the phone to exactly how it was stock so that I can go trough the TWRP process which seems to be straight enough...
EDIT 1 trying with the rescue software I get
Device missed [ro.build.version.full]
Please contact after sale service to re-write
EDIT 2
Reflashed the whole thing and the phone is work now.
Trying to re-install TWRP from:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Using the TWRP page information, I tried to install it and then when I try to reboot it goes trough the boot loop. Phone boots fine, back the N/A in the top corner of the boot screen. Get back in fastboot boot twrp, the wipe davlik, try to fix the bootloop, get the same freaking error :
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
Phone boots fine though.
Try to fix Magisk (by installing the APK ):
Installation
The Magic Mask for Android
topjohnwu.github.io
Trying to Fix Magisk, using the apk, with the Boot.img that I used to reflash the whole phone didn't seems to work. I was able to create a custom boot img, and then the phone boot it doesn't say BAD CODE but a series of 40 numbers appears on the top screen. When I go back to the Magisk APK it shows that it's not installed, or more appropriate Installed: N/A ...
Trying to install lineage from the zip from the lineage site.
By booting in fastboot boot twrp, I wipe davlik, system, data, the install from zip I get:
Error installing zip file '/external_sd/lineage-18.1-2021-6-6-nightly-channel-signed.zip
Updating partition details...
...done
So, no idea where to go from there. Maybe I'm doing all that stuff in the wrong order. Should I try to reflash the boot, then not trying to install TWRP and trying to install Lineage like that? Is that possible?
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:37:43 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/channel/channel:9/PPYS29.
(bootloader) ro.build.fingerprint[1]: 105-220-3/74206:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.8.channel.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_37.155.01.146R CHANNEL_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.011s

damaru said:
So the rescue and smart assistant is not working on that particular model (or so Lenovo say) should I try anyway?
I get a Start Up Failed now. So I can't boot in the normal phone anymore. Not sure what I did wrong. So to get back to a normal phone flashing the whole firmware wouldn't help?
I'm at a place where I'd like to bring back the phone to exactly how it was stock so that I can go trough the TWRP process which seems to be straight enough...
EDIT 1 trying with the rescue software I get
Device missed [ro.build.version.full]
Please contact after sale service to re-write
EDIT 2
Reflashed the whole thing and the phone is work now.
Trying to re-install TWRP from:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Using the TWRP page information, I tried to install it and then when I try to reboot it goes trough the boot loop. Phone boots fine, back the N/A in the top corner of the boot screen. Get back in fastboot boot twrp, the wipe davlik, try to fix the bootloop, get the same freaking error :
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
Phone boots fine though.
Try to fix Magisk (by installing the APK ):
Installation
The Magic Mask for Android
topjohnwu.github.io
Trying to Fix Magisk, using the apk, with the Boot.img that I used to reflash the whole phone didn't seems to work. I was able to create a custom boot img, and then the phone boot it doesn't say BAD CODE but a series of 40 numbers appears on the top screen. When I go back to the Magisk APK it shows that it's not installed, or more appropriate Installed: N/A ...
Trying to install lineage from the zip from the lineage site.
By booting in fastboot boot twrp, I wipe davlik, system, data, the install from zip I get:
Error installing zip file '/external_sd/lineage-18.1-2021-6-6-nightly-channel-signed.zip
Updating partition details...
...done
So, no idea where to go from there. Maybe I'm doing all that stuff in the wrong order. Should I try to reflash the boot, then not trying to install TWRP and trying to install Lineage like that? Is that possible?
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:37:43 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/channel/channel:9/PPYS29.
(bootloader) ro.build.fingerprint[1]: 105-220-3/74206:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.8.channel.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_37.155.01.146R CHANNEL_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.011s
Click to expand...
Click to collapse
I don't think you need to Install TWRP to install Lineage
Just boot twrp and install the Rom
Edit: Looks like you tried that already
Make sure you are using the preinstall zip before installing the rom
Install LineageOS on channel | LineageOS Wiki
wiki.lineageos.org