Database Users

XT1572 every time reboot enter in mode fastboot

Hello,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:

SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect

same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,

sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.

Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.

acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.

acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc

Sam to me. Any help?

ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.

typo - fastboot, not fasboot
fastboot oem fb_mode_clear

fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?

lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.

With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...

Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse

sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?

XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s

[SOLVED] [XT1572] Fully bricked or is there a solution ?

Hey there,
To make it short, the phone was rooted, bootloader unlocked, and it was on Resurrection Remix (don't know which one, it was Nougat 7.1.2).
I tried to restore it back to stock, lock the bootloader etc (following this guide : https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 which has files for xt1572 too ).
During the process, I got the error that a lot of people get about the Preflash validation error and yet i went through, except that I still locked at the end (I did not notice the Note about it below the command lines, I so regret it).
I also flashed the original Motorola logo (instead of "Bootloader is unlocked"), but I don't think this has anything to do with the fact that it got bricked (I can be wrong though).
Now, I can't access the phone through the cable. adb devices (with killing and restarting server) doesn't detect anything, I'm just stuck on the big Motorola logo splash screen.
Anyone has any idea on any possible way to unbrick it ? (I heard about qualcomm hsusb something but I'm just not sure where it can lead)
Thanks !

@pef6000
Bootloader is locked? What is status code...?

can't you use fastboot (from device turned off hold power + vol down) and flash stock motorola rom?

Hey there, thanks for your answers.
I can't access bootloader nor fastboot. adb doesn't show any device anymore.
I cannot even turn on or off the phone. It just reboots even if I long-press the power button. It just boots back up, and I can only leave it like this until battery is depleted.

Hold power, when screen turn off hold only vol-. It should go to bootloader.
Check and post here BL status. @pef6000
---------- Post added at 11:04 PM ---------- Previous post was at 10:58 PM ----------
Btw, if you will go to bootloader mode(locked) - you can only flash again stock 6.0.1(newest).
Without bootloader and gpt.
Check how many sparsechunks you have in zip file, I think from 0 to 11.

Sorry for being late. I tried that yesterday, but one problem after another, Windows died
I'll pass some time on it whenever I get the computer working.
I tried starting in BL and it worked !
I think the fact that it wasn't working before was due to the phone bootlooping directly on splash screen (maybe, I don't know).
Here, battery was dead since I couldn't turn it off. So I plugged the phone in while keeping vol- pressed, and it booted immediately in.
Couldn't get a hold of the status code though, the computer rebooted and crashed, so I had something else in mind, sorry :/
Anyway, I'll do that whenever I can, thanks for your help !

Here again. I accessed bootloader and I get :
AP Fastboot Flash Mode (Secure)
[…]
Console [NULL]: null
Battery OK (charging)
Device is UNLOCKED. Status Code: 3
Software status: Modified
Before this problem, when I tried to flash everything, I have parsechunks from 0 to 8, not 11.
Now, I don't really know what to do. Should I do everything back again with a 6.0.1 zip ?

pef6000 said:
Should I do everything back again with a 6.0.1 zip ?
Click to expand...
Click to collapse
Yes.
Without bootloader, gpt and Don't lock BootLoader.

Hey.
I did it, didn't lock bootloader, didn't flash bootloader.img nor gpt.bin, but it still freezes on the splash screen logo. I suppose it woudn't take as much as 15 to 30 minutes to switch from that splash screen to any other screen.
The bootloader is still accessible, and I still have the same things (unlocked, status 3, etc).
Am I doing something wrong ? :/

What is your model and what rom are you flashing?
What do you have on pc after: "fastboot getvar all"? @pef6000

It's a XT1572, European (got it in France).
I'm trying to flash the one for XT1572 in the link with the instructions : https://dl.prazaar.de/?dir=Android/XT1572/Factory/6.0.1/MPHS24.107-58-5_September_2016
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(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: TA3910197I
(bootloader) cid: 0x0007
(bootloader) channelid: 0x42
(bootloader) uid: 42C5D7001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [...]
(bootloader) meid:
(bootloader) date: 11-12-2015
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jul 6 10:58:55 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_EMEA_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g0ec7138 (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 Tue Nov 3 05:05:40 CST 2015
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=7ea7c4c-dirty
(bootloader) hyp.git: git=7ea7c4c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 2/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retfr
all: listed above
finished. total time: 0.242s

Did you flash: boot, recovery, all sparsechunks(0-11), modem, all erases? Each command ended with OK? @pef6000

Yes, I did all of this, everything turns out ok except one error (the Preflash Validation).
Now that I read it again, the post says it happens on gpt.bin, except I didn't flash it as you said.
I just did it again and I get it again at this step :
> fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41699 KB)...
OKAY [ 0.923s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.981s
Do I also not flash the modem ? :/
EDIT :
Btw, the bootloader log on the phone says "Image is too large" after the "cmd: flash:modem" line.

pef6000 said:
It's a XT1572, European (got it in France).
Click to expand...
Click to collapse
You should edit your post and remove the IMEI number...

Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000

dzidexx said:
Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000
Click to expand...
Click to collapse
From the getvar output, the bootloader is on 6.0
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
Click to expand...
Click to collapse
on MPHS24.49-18-4... I would suggest using the same version or XT1572_CLARK_RETEU_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and NOT 6.0.1. The 6.0.1 versions were only for certain variants, and I do not know if the RETFR ones had that.
And don't skip the bootloader or gpt UNLESS they actually fail... It is best to do it like this:
Also, if possible boot into the factory recovery and perform a full factory reset before beginning.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
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 [Verify number of sparse chunks and make sure you are doing the correct #]
fastboot flash modem NON-HLOS.bin [May need to be done more 2 or 3 times to "take", make sure it returns an "OKAY"]
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
My 2 cents worth... hope it helps.

@acejavelin Oh damn, thank you. I thought I checked correctly but I didn't notice the IMEI in there.
Thank you both for your help. Phone booted up on original rom, I'm happy
I'll mark this post as Solved, but I have a quick question : Can I use the XT1575 logo.bin found here :https://forum.xda-developers.com/mo...o-remove-unlocked-bootloader-warning-t3201141
Or is it better not to do so ?

Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/boot-animation-logo-bin-t3558942 @pef6000
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.

dzidexx said:
Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/[email protected]
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.
Click to expand...
Click to collapse
@pef6000 Any of these or the one you mentioned is fine.

Sorry for the late answer, I flashed the 18-8 in the end.
Thanks again, I'll mark this as solved !

Stuck with Fastboot, DFU and locked bootloader

Hello, I am totally lost... I've been trying to solve this problem but no luck... I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (stuck on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
###########
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.017s
##############
any one can help me plz.

anyone can help

t.zennad said:
anyone can help
Click to expand...
Click to collapse
I'm also in the same condition...
fastboot not accessible...
Help!!!
Axon 7 mini 7.1.1 build B2017gV1.2.0B14

Still waiting too.

Get a stock recovery (not TWRP), flash it with fasboot flash recovery recovery.img
I think tdm has a thread with all stock images, flash the one for your country
https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538
If this doesn't work, maybe the verity check fails, making the device unable to boot, then go ahead and flash system and boot via fastboot.
fastboot flash system system.img
fastboot flash boot boot.img
Good luck

just a hailmairy here but...
"(bootloader) Charger screen enabled: 'false'"
in Advanced Settings ->Developer Options->Stay Awake (while charging) [ ]
should possible be switched on as it does mentions that charging screen set to off?
Probably would only sort one item though but you never know and if it does your one more step forward.
sonnettie

HEEEEELP! From Liquid tried to flash Lineage16.....flashed bootloader...I'm stuck on fastboot. The down volume key is broken. Only up volume works but not in fastboot. Tried to adb/flash a sock recovery....only can reboot in fastboot dialogue. Any solution? Thank you.

Hello
any one can help please, i am still in same problem
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3447000
(bootloader) variant:TULIP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x12c00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5ebb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:bc13c89a
(bootloader) kernel:lk
(bootloader) product:TULIP
all:
finished. total time: 0.022s
------
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
-------
I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (loop on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
Thanks

I tried to unlock my b2017g with fastboot commands but not luck, i tried use Hydra too... i hope will find a solution soon :/

Hi Everybody, I think I have a similar issue. After many years with regular stock system I decided to change to a custom ROM, hoping I can use my phone with my native language, which was not in the stock rom.
But now I stucked in the fastboot, and I can not get out of it. I can access my phone via fastboot, I have already flashed the TWRP, but the phone can not boot into the recovery and the system. How can I fix this? Please help me, I like this phone, I would like to get it back to life.

I bricked my Axon mini n2015 by flashing No verity boot.img and a custom recovery. Now phone is stuck in fastboot mode. Help guys, what do i do?

Looks like no solution

Help For Install or search rom for my g4 play (xt1603)

Good evening, excuse my English.
I need help with a Moto G4 Play device (Xt1603) in which it does not leave the fastboot screen, and also I can not install any roms on it ... all the downloaded and tested roms only result in FAILED error and do not install, I already tried some 10 different roms and so far without success.
Trying to install by RSD or ADB Fastboot
Below I will leave the information of the cell in question
Connect in Fastboot Mode
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-81.0A
(bootloader) product: harpia
(bootloader) board: harpia
(bootloader) secure: yes
(bootloader) hwrev: 0x81B0
(bootloader) radio: 0x3
(bootloader) emmc: 16GB Samsung REV=08 PRV=07 TYPE=57
(bootloader) ram: 2GB Samsung S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: 0028860325
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: D6BF822100000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 2 15:58:59 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/harpia_t/harpia_t:6.0
(bootloader) ro.build.fingerprint[1]: PIS24.241-15.3-21/22:user/rele
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.211.22.harpia
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband[0]: M8916_20250106.08.05.14.01R HARPIA
(bootloader) version-baseband[1]: ZIL_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-g1ea7a34 (huds
(bootloader) kernel.version[1]: @ilclbld72) (gcc version 4.8 (GCC) )
(bootloader) kernel.version[2]: SMP PREEMPT Mon May 22 00:03:54 CDT
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) aboot.git: git=MBM-NG-V81.0A-0-g38d3e26
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-typeDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:hw: raw
(bootloader) partition-type:customize: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-typeem: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-sizeDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-sizeadA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-sizeadB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000300000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-sizeersist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001019000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-sizeadC: 0x000000000087e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:hw: 0x0000000000800000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:system: 0x00000000a0000000
(bootloader) partition-sizeem: 0x0000000029000000
(bootloader) partition-size:userdata: 0x00000002bdde0000
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retbr
all: listed above
Execution time is 55(s)
Done!
Press any key to go Home :crying:

Lucas2Maria said:
(bootloader) unlocked: no
(bootloader) securestate: locked
Click to expand...
Click to collapse
The bootloader on the phone is locked, so you can only flash official firmware of the same version or newer. All the official firmware I find for your exact model phone are for Marshmallow - hopefully someone else can point you to a copy of Nougat that they know will work.

hitokage004 said:
The bootloader on the phone is locked, so you can only flash official firmware of the same version or newer. All the official firmware I find for your exact model phone are for Marshmallow - hopefully someone else can point you to a copy of Nougat that they know will work.
Click to expand...
Click to collapse
I understand, so these roms you mentioned do not work for my device? or which Roman Nogaut do I have to look for? Could you help me a little more if it will not disturb you? or even tell me to download the rom

I Think what he way trying to convey was you need to Unlock Your Bootloader of your Device to flash any Custom ROM(Which I am Assuming You are Trying).
After Unlocking You need to Install Custom Recovery Called TWRP on your Device.(https://forum.xda-developers.com/g4-play/development/twrp-twrp-moto-g-play-t3453888)Then Download and Place your ROM into your SD?internal based on what are you gonna format and then Just Flash those And Enjoy!

TheWarrior01 said:
I Think what he way trying to convey was you need to Unlock Your Bootloader of your Device to flash any Custom ROM(Which I am Assuming You are Trying).
After Unlocking You need to Install Custom Recovery Called TWRP on your Device.(https://forum.xda-developers.com/g4-play/development/twrp-twrp-moto-g-play-t3453888)Then Download and Place your ROM into your SD?internal based on what are you gonna format and then Just Flash those And Enjoy!
Click to expand...
Click to collapse
I understand, but unfortunately the phone does not start, it gets stuck on the screen of fastboot and no matter what I do it does not install any rom ... because it is without system and with the bootloader blocked !!!!
this procedure mentioned would not work for me since I do not have access to the system ... more thanks and I'm waiting for someone who has the rom mentioned by the friend above

Lucas2Maria said:
I understand, but unfortunately the phone does not start, it gets stuck on the screen of fastboot and no matter what I do it does not install any rom ... because it is without system and with the bootloader blocked !!!!
this procedure mentioned would not work for me since I do not have access to the system ... more thanks and I'm waiting for someone who has the rom mentioned by the friend above
Click to expand...
Click to collapse
Do You have any Idea of What Version of Firmware You had(MM or N). If you hadnt updated in a while there was a security patch that was rolled out, so you might wanna test with that version!
I want to know that you can access Bootloader of the device or not? If you can access try unlocking it(just google on how to) and then try to flash(?)

TheWarrior01 said:
Do You have any Idea of What Version of Firmware You had(MM or N).
Click to expand...
Click to collapse
Based on the original post it seems to be a build of Marshmallow - ro.build.fingerprint[1]: PIS24.241-15.3-21/22:user/rele. I got mixed-up with all the numbers and seemed to think it was Nougat. The firmware I found of MM were older builds, so may not flash.
@Lucas2Maria
I found a link that has the same build (May 2018) that is supposed to work on the XT1600 and XT1603 (about 1GB) - https://mega.nz/#!ksIAxIjY!HjUJTmptaENjSxsycv3_cwitB45T3RfxmoE_A2q5Ssg
This one is Nougat (November 2017) and is also supposed to work (about 866MB) - https://androidfilehost.com/?fid=745849072291698642
If you use the build of Nougat I linked to, don't flash the bootloader just to be safe. The MM build is the same, so it shouldn't matter. If one of these gets the phone working again, you'll need to unlock the bootloader to install custom ROMs/firmware. If you stay stock there should be OTA updates for either version to get the phone current.
Credit - firmware links were found here and here.

hitokage004 said:
Based on the original post it seems to be a build of Marshmallow - ro.build.fingerprint[1]: PIS24.241-15.3-21/22:user/rele. I got mixed-up with all the numbers and seemed to think it was Nougat. The firmware I found of MM were older builds, so may not flash.
@Lucas2Maria
I found a link that has the same build (May 2018) that is supposed to work on the XT1600 and XT1603 (about 1GB) - https://mega.nz/#!ksIAxIjY!HjUJTmptaENjSxsycv3_cwitB45T3RfxmoE_A2q5Ssg
This one is Nougat (November 2017) and is also supposed to work (about 866MB) - https://androidfilehost.com/?fid=745849072291698642
If you use the build of Nougat I linked to, don't flash the bootloader just to be safe. The MM build is the same, so it shouldn't matter. If one of these gets the phone working again, you'll need to unlock the bootloader to install custom ROMs/firmware. If you stay stock there should be OTA updates for either version to get the phone current.
Credit - firmware links were found here and here.
Click to expand...
Click to collapse
Good afternoon,
Sorry for the delay, today I went to vote for president here in Brazil and I could only do a little test of what happened to me ....
I downloaded the two roms passed by you and unfortunately none worked,
I did for RSD and also for adbfastboot
In RSD always lock in step 2/22
And in Adb all of failed ...
I can not understand why they do not install !!! I'm annoyed because it's an emergency phone from my sister that she uses to work and talk to us family
I do not know if I'm doing something wrong or if it's the same rom that I do not want to install

Please someone else has some solution for me please !!!
I really would like to relive the phone ...

@Lucas2Maria Please try this, it's based on the Android Nougat firmware I linked above. I've tried to make this as easy to follow as possible. Based on your first post I'm assuming your computer and Fastboot see the phone. The easiest way to do this is to extract the zip file (using 7-zip, WinZip, etc.) to its own folder (directory) and copy the ADB and Fastboot files there (you can do it the other way around if you want), so files paths won't be an issue. Whatever I show in quotation marks is what to type or you can copy and paste - don't type the quotation marks themselves. We're going to skip flashing the partition table and bootloader to reduce the chance of trouble.
Code:
1 - open a command prompt and change to the folder with the firmware in it (i.e. C:\harpia_firmware)
2 - type "fastboot oem fb_mode_set" <enter/return>
3 - type "fastboot flash logo logo.bin" <enter/return>
4 - type "fastboot flash boot boot.img" <enter/return>
5 - type "fastboot flash recovery recovery.img" <enter/return>
6 - type "fastboot erase system" <enter/return>
7 - type "fastboot flash system system.img_sparsechunk.0" <enter/return>
8 - type "fastboot flash system system.img_sparsechunk.1" <enter/return>
9 - type "fastboot flash system system.img_sparsechunk.2" <enter/return>
10 - type "fastboot flash system system.img_sparsechunk.3" <enter/return>
11 - type "fastboot flash system system.img_sparsechunk.4" <enter/return>
12 - type "fastboot flash system system.img_sparsechunk.5" <enter/return>
13 - type "fastboot flash oem oem.img" <enter/return>
14 - type "fastboot flash modem NON-HLOS.bin" <enter/return> (this shouldn't be case sensitive)
15 - type "fastboot erase modemst1" <enter/return>
16 - type "fastboot erase modemst2" <enter/return>
17 - type "fastboot flash fsg fsg.mbn" <enter/return>
18 - type "fastboot erase customize" <enter/return>
19 - type "fastboot erase clogo" <enter/return>
20 - type "fastboot erase DDR" <enter/return> (this is case sensitive - DDR must be in all uppercase)
21 - type "fastboot erase cache" <enter/return>
22 - type "fastboot oem fb_mode_clear" <enter/return>
23 - type "fastboot reboot" <enter/return>
If this doesn't work, take some screenshots while going through the process so we try to figure out why or what isn't working. Another option is to ask for help in the Google+ group I got the firmware links from - https://plus.google.com/communities/103677445767173413387

hitokage004 said:
@Lucas2Maria Please try this, it's based on the Android Nougat firmware I linked above. I've tried to make this as easy to follow as possible. Based on your first post I'm assuming your computer and Fastboot see the phone. The easiest way to do this is to extract the zip file (using 7-zip, WinZip, etc.) to its own folder (directory) and copy the ADB and Fastboot files there (you can do it the other way around if you want), so files paths won't be an issue. Whatever I show in quotation marks is what to type or you can copy and paste - don't type the quotation marks themselves. We're going to skip flashing the partition table and bootloader to reduce the chance of trouble.
Code:
1 - open a command prompt and change to the folder with the firmware in it (i.e. C:\harpia_firmware)
2 - type "fastboot oem fb_mode_set" <enter/return>
3 - type "fastboot flash logo logo.bin" <enter/return>
4 - type "fastboot flash boot boot.img" <enter/return>
5 - type "fastboot flash recovery recovery.img" <enter/return>
6 - type "fastboot erase system" <enter/return>
7 - type "fastboot flash system system.img_sparsechunk.0" <enter/return>
8 - type "fastboot flash system system.img_sparsechunk.1" <enter/return>
9 - type "fastboot flash system system.img_sparsechunk.2" <enter/return>
10 - type "fastboot flash system system.img_sparsechunk.3" <enter/return>
11 - type "fastboot flash system system.img_sparsechunk.4" <enter/return>
12 - type "fastboot flash system system.img_sparsechunk.5" <enter/return>
13 - type "fastboot flash oem oem.img" <enter/return>
14 - type "fastboot flash modem NON-HLOS.bin" <enter/return> (this shouldn't be case sensitive)
15 - type "fastboot erase modemst1" <enter/return>
16 - type "fastboot erase modemst2" <enter/return>
17 - type "fastboot flash fsg fsg.mbn" <enter/return>
18 - type "fastboot erase customize" <enter/return>
19 - type "fastboot erase clogo" <enter/return>
20 - type "fastboot erase DDR" <enter/return> (this is case sensitive - DDR must be in all uppercase)
21 - type "fastboot erase cache" <enter/return>
22 - type "fastboot oem fb_mode_clear" <enter/return>
23 - type "fastboot reboot" <enter/return>
If this doesn't work, take some screenshots while going through the process so we try to figure out why or what isn't working. Another option is to ask for help in the Google+ group I got the firmware links from - https://plus.google.com/communities/103677445767173413387
Click to expand...
Click to collapse
Good night, so I tried the method that happened to me, in fact I had tried with other roms, I also published the request for help in the community of google plus, but still no one answered ... and apparently the only help will be you of the XDA ... I do not know what happens that the same can not install any rom .. the errors always the same of the logs above ...
I still need help

@Lucas2Maria - Without being able to see things (screenshots or video), it's difficult for me to troubleshoot. Did you see if Motorola has a place near you that can fix it? Motorola Brazil's repair page
The last thing I've got is to see if you can unlock the bootloader (which will wipe all data on the phone), and then try my flashing instructions again. Here is the link to Motorola's site to explain how to get a bootloader unlock code and unlock the phone (Motorola Brazil again).

Lucas2Maria said:
Please someone else has some solution for me please !!!
I really would like to relive the phone ...
Click to expand...
Click to collapse
Hello Google translator here rss @Lucas2Maria I have the moto g4 play 1603, I can make a backup via twrp. and send.
You already unlocked bootloader and twrp flash right?
if you still do not know how to do it is the first step

hitokage004 said:
@Lucas2Maria - Without being able to see things (screenshots or video), it's difficult for me to troubleshoot. Did you see if Motorola has a place near you that can fix it? Motorola Brazil's repair page
The last thing I've got is to see if you can unlock the bootloader (which will wipe all data on the phone), and then try my flashing instructions again. Here is the link to Motorola's site to explain how to get a bootloader unlock code and unlock the phone (Motorola Brazil again).
Click to expand...
Click to collapse
Screenshots

Nildo Ivan said:
Hello Google translator here rss @Lucas2Maria I have the moto g4 play 1603, I can make a backup via twrp. and send.
You already unlocked bootloader and twrp flash right?
if you still do not know how to do it is the first step
Click to expand...
Click to collapse
I can not unlock the bootloader, when I try and insert the codes sent to my email simply they fail ... I am no longer able to find out why the device can not accept the rom, if someone wants to try to help me via TeamViewer Please I'll thank you.

Lucas2Maria said:
Screenshots
Click to expand...
Click to collapse
I did some searching on Google, based on what I've found I've got some other things to try.
Is there a SD-card installed?
If so, remove it, turn the phone on, and the first thing to do depends on what happens - if it boots normally, you should be able to reinstall the SD-card (after powering down), after that depends on if you want to risk working on it more.
If after removing the SD-card, the phone goes straight to Fastboot mode, the first thing to do is enter the command for unlocking - fastboot oem unlock UNIQUE_KEY, it should then reboot on its own, if it does and goes back to Fastboot mode, follow the flashing instructions in my previous forum post.
If running the command for unlocking, gives an error:
If the error states the bootloader is already unlocked, then you'll just want to proceed to follow he flashing instructions. If it states something else post that here.
If there is no SD-card installed - power the phone all the way off, power it back on, assuming it goes straight to Fastboot mode, the first thing to do is enter the command for unlocking - fastboot oem unlock UNIQUE_KEY, it should then reboot on its own. If it does reboot and goes back to Fastboot mode, follow the flashing instructions in my previous forum post. If it doesn't reboot on its own, but doesn't give any error about the key, manually reboot. If it doesn't give a message about being unlocked, enter the command "fastboot getvar all". If you see something like (bootloader) unlocked: yes, it did unlock the bootloader, so proceed to the flashing instructions. If you see something like (bootloader) unlocked: no, post that information here.
Another possible source of trouble is the battery level is too low:
When the phone is completely off does it show the battery charging picture? If so, let it charge overnight, power it on, and try the flashing instructions again.
If the phone won't charge the battery, there are some options, but I think I've got this complicated enough - just make a post saying the phone won't charge the battery.
I need to clarify that for screenshots it helps to see what you get on the computer - the phone screenshot did help though. You can take a screenshot of the active window by pressing Alt & Print Screen simultaneously, paste it into MS Paint or other image editor, save the file, then attach it here. If it's easier to copy the text from the command window and paste it into a forum post that is fine as well.

hitokage004 said:
I did some searching on Google, based on what I've found I've got some other things to try.
Is there a SD-card installed?
If so, remove it, turn the phone on, and the first thing to do depends on what happens - if it boots normally, you should be able to reinstall the SD-card (after powering down), after that depends on if you want to risk working on it more.
If after removing the SD-card, the phone goes straight to Fastboot mode, the first thing to do is enter the command for unlocking - fastboot oem unlock UNIQUE_KEY, it should then reboot on its own, if it does and goes back to Fastboot mode, follow the flashing instructions in my previous forum post.
If running the command for unlocking, gives an error:
If the error states the bootloader is already unlocked, then you'll just want to proceed to follow he flashing instructions. If it states something else post that here.
If there is no SD-card installed - power the phone all the way off, power it back on, assuming it goes straight to Fastboot mode, the first thing to do is enter the command for unlocking - fastboot oem unlock UNIQUE_KEY, it should then reboot on its own. If it does reboot and goes back to Fastboot mode, follow the flashing instructions in my previous forum post. If it doesn't reboot on its own, but doesn't give any error about the key, manually reboot. If it doesn't give a message about being unlocked, enter the command "fastboot getvar all". If you see something like (bootloader) unlocked: yes, it did unlock the bootloader, so proceed to the flashing instructions. If you see something like (bootloader) unlocked: no, post that information here.
Another possible source of trouble is the battery level is too low:
When the phone is completely off does it show the battery charging picture? If so, let it charge overnight, power it on, and try the flashing instructions again.
If the phone won't charge the battery, there are some options, but I think I've got this complicated enough - just make a post saying the phone won't charge the battery.
I need to clarify that for screenshots it helps to see what you get on the computer - the phone screenshot did help though. You can take a screenshot of the active window by pressing Alt & Print Screen simultaneously, paste it into MS Paint or other image editor, save the file, then attach it here. If it's easier to copy the text from the command window and paste it into a forum post that is fine as well.
Click to expand...
Click to collapse
Good morning, thanks for the patience and I'm following in your footsteps ...
When turning on the phone it already tries to start the motorola logo appears and it falls on the first screen that I am posting ....
After it returns to the screen shown above I plug it into the computer and with the adb open I enter the command that sent me to unlock next to the key captured on Motorola that was sent to my email and it returns the error of the second image.
The phone has a 100% battery and it does not have a micro sd card

Lucas2Maria said:
Good morning, thanks for the patience and I'm following in your footsteps ...
When turning on the phone it already tries to start the motorola logo appears and it falls on the first screen that I am posting ....
After it returns to the screen shown above I plug it into the computer and with the adb open I enter the command that sent me to unlock next to the key captured on Motorola that was sent to my email and it returns the error of the second image.
The phone has a 100% battery and it does not have a micro sd card
Click to expand...
Click to collapse
Images

Lucas2Maria said:
Images
Click to expand...
Click to collapse
(More Googling) We're going to try once again, this time using with the Motorola version of fastboot named mfastboot - I attached a copy to this post (at the bottom - source post). Download it and first try this with the Nougat version of the firmware, if it doesn't work, try again the Marshmallow one since it was supposed to be the same version as what your phone has. We're going to put trying to unlock the bootloader aside for now. I've added two lines to flash the partition table and boot to the flashing procedure as it seems they may be necessary, and another to try to erase a partition before flashing it.
Code:
1 - open a command prompt and change to the folder with the firmware in it (i.e. C:\harpia_firmware)
2 - type "mfastboot oem fb_mode_set" <enter/return>
3 - type "mfastboot flash partition gpt.bin" <enter/return> **added**
4 - type "mfastboot flash bootloader bootloader.img" <enter/return> **added**
5 - type "mfastboot flash logo logo.bin" <enter/return>
6 - type "mfastboot erase boot" <enter/return> **added**
7 - type "mfastboot flash boot boot.img" <enter/return>
8 - type "mfastboot flash recovery recovery.img" <enter/return>
9 - type "mfastboot erase system" <enter/return>
10 - type "mfastboot flash system system.img_sparsechunk.0" <enter/return>
11 - type "mfastboot flash system system.img_sparsechunk.1" <enter/return>
12 - type "mfastboot flash system system.img_sparsechunk.2" <enter/return>
13 - type "mfastboot flash system system.img_sparsechunk.3" <enter/return>
14 - type "mfastboot flash system system.img_sparsechunk.4" <enter/return>
15 - type "mfastboot flash system system.img_sparsechunk.5" <enter/return>
16 - type "mfastboot flash oem oem.img" <enter/return>
17 - type "mfastboot flash modem NON-HLOS.bin" <enter/return> (this shouldn't be case sensitive)
18 - type "mfastboot erase modemst1" <enter/return>
19 - type "mfastboot erase modemst2" <enter/return>
20 - type "mfastboot flash fsg fsg.mbn" <enter/return>
21 - type "mfastboot erase customize" <enter/return>
22 - type "mfastboot erase clogo" <enter/return>
23 - type "mfastboot erase DDR" <enter/return> (this is case sensitive - DDR must be in all uppercase)
24 - type "mfastboot erase cache" <enter/return>
25 - type "mfastboot oem fb_mode_clear" <enter/return>
26 - type "mfastboot reboot" <enter/return>
If this still doesn't work, I'll have to see if it is possible to bypass the "Allow OEM Unlock" setting - I'm just about out of things to try.

hitokage004 said:
(More Googling) We're going to try once again, this time using with the Motorola version of fastboot named mfastboot - I attached a copy to this post (at the bottom - source post). Download it and first try this with the Nougat version of the firmware, if it doesn't work, try again the Marshmallow one since it was supposed to be the same version as what your phone has. We're going to put trying to unlock the bootloader aside for now. I've added two lines to flash the partition table and boot to the flashing procedure as it seems they may be necessary, and another to try to erase a partition before flashing it.
If this still doesn't work, I'll have to see if it is possible to bypass the "Allow OEM Unlock" setting - I'm just about out of things to try.
Click to expand...
Click to collapse
Good evening, sorry the delay in responding is in an emergency, but let's go ... I have already done all the measures passed by you and until now all I have and the failure to install the rom and I tested a 20 different rom several sites follows the images

[HELP][BRICK] ZE552KL Z012DC doesn't boot to system

Hello guys,
I need help. Definitely
My phone stopped booting into system after some service.
First a little brief:
Phone never showed any problems before.
LCD+Touch were replaced.
Phone stopped booting into system.
Stills boots/ works perfectly in fastboot, recovery and userdebug.
Tried:
factory reset
unlocking and relocking bootloader
flashing several factory and stock RAWs
stock recovery and TWRP
stock raw alone
update stock system from stock raw
twrp + stock rom + magisk
twrp + lineageos + magisk
several guides on this forum
Nothing works. Problem remains the same, doesn’t matter the alternative I try.
Now the whole story:
I’ve had this phone for a while. Always did the OTA updates. Never had problems… at all.
Some days ago, I dropped it and was finally able to break the screen. The lcd became black in some spots and had different brightness in others. Touch kind of worked, kind of got crazy after some seconds (and I had to turn the screen off and on again).
I’ve got some experience in repairing electronics and phones. So, I watched/read a dozen guides about this particular service, bought an original LCD+Touch kit, and replaced myself.
No apparent problems with that. The process is quite simple and straight forward. (I knew what I was doing. But if you tell me something might be wrong with that, I will look into it. I will take any help. Just tell me what to do.)
And so it begins.
I set my phone up again - without gluing anything, as it was the first test – and turn it on. It seems to boot normally… boot logo shows normally… boot animation seems to take longer than usual… the screen suddenly goes black.
I open the whole thing again, check every connector, everything is ok.
I try to turn it on again, now the phone turns off after just one or two seconds of boot animation.
I did then a factory reset, problem persisted just the same.
I thought to myself: “ok, then. System must be somehow corrupted.”
I updated the system to the lasted version in ASUS website trough adb sideload. Problem persisted.
“ok, maybe I must clear the system partition then… let’s go a little further”.
I read some guides, and proceeded to unlock the bootloader (flash factory raw, fastboot commands, flash oreo raw), flash TWRP and LineageOS.
When I turn it on again, a bit of hope. Boot animation takes, again, a long time. An “encrypting device” screen comes up and I believe it’s finally over. But no. The phone goes off after about 10 seconds of supposed encrypting and, when I turn it on again, same as before… two seconds of boot animation and then darkness.
After that I Just went deeper into the habbit hole.
Tried several brick fixes in sent by the XDA community.
Tried flashing RAWs using Asus Flash Tool (v1.0.0.86 (20201124)) and flashall_AFT.cmd (that comes inside de RAWs.
Tried all combination and orders I could imagine of the following RAWs:
CSC_ZE552KL_13.1301.1603.53_WW_Lock_20171128
CSC_ZE552KL_13_13_1_36_M2_6_7_P7_userdebug
WW_ZE552KL_13.20.10.137_M3.10.35_Phone-user.raw
WW_ZE552KL_14.2020.1703.28_M3.10.47.3_Phone-user.raw
WW_ZE552KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw
WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
It doesn’t matter. Whenever I flash a RAW, the phone goes to this encrypting process and then goes black. From there on, I can flash anything through adb sideload, fastboot or twrp…. It shows the boot logo, (possibly shows the dm-verity screen, depending on the set up), and goes off after about 2 seconds of boot animation.
Tested everything I could with TWRP: LCD, Touch, mounting partitions and storage seem to be working fine.
Tested everything I could with the factory RAW userdebug (using command fastboot oem enable-userdebug boots a very simple system (there’s an image below)): Again, LCD and touch work fine. Also, hard keys, wifi, Bluetooth, calling, messaging, 4G and both speakers are working.
And there we get to present time. I just don’t know what else I can do.
My next steps would be going into QFIL flashing. That would actually be new to me. But since I can use all these functions properly, it doesn’t seem to me that that’s the way to go.
Please help. I will take anything. Tell what I may have passed by. Send me the guides you think may help me, even if I’ve already tried.
I can give you any information you guys believe is pertinent.
I will start leaving here some info I think may help:
ZE552KL Z012DC ASUS_Z012DC Brazilian model BRAZIL
4GB RAM. 64GB storage.
Code:
C:\Users\Vanisi\Desktop\ZE552KL>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4236000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:O-CS4 - 4 - user
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x1fe00000
(bootloader) partition-type:asdf:ext4
(bootloader) partition-size:asdf: 0x4000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xd000000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x8000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd683f7000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xf0000000
(bootloader) cpuid:046
(bootloader) project:ZE552KL
(bootloader) serialno:H2AZB601E85****
(bootloader) kernel:lk
(bootloader) product:MSM8953
all:
Finished. Total time: 0.281s
C:\Users\Vanisi\Desktop\ZE552KL>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) Device is_authorized: false
(bootloader) ssn_num: H2AZB601E85****
(bootloader) isn_num: MB352KL0AB****
(bootloader) check_fused: 0
(bootloader) Device resize: false
(bootloader) BOOT_COUNT : 175
(bootloader) SB=Y
(bootloader) Re-partition: false
(bootloader) Device had been rooted: >>> YES <<< (Warranty void)
(bootloader) Device has copy fsg to fsgCA: false
(bootloader) Device last copy fsg status: fail
(bootloader) verity_mode: 1
(bootloader) is_ffu: false
(bootloader) verity_counter: 0
(bootloader) total verity_counter: 0
OKAY [ 0.203s]
Finished. Total time: 0.203s
C:\Users\Vanisi\Desktop\ZE552KL>fastboot oem system-info
(bootloader) board_info: msm8953
(bootloader) mem_info: 4GB
(bootloader) mmc_info:
(bootloader) product_name: ASUS_Z012D
(bootloader) product_locale: en-US
(bootloader) product_carrier: US-ASUS_Z012D-WW_Phone
(bootloader) csc_build_version: WW_ZE552KL-13.20.10.152-20161222
(bootloader) bt_mac: 2C4D5****B18
(bootloader) wifi_mac: 2C4D5****E38
(bootloader) imei: 35905207393****
(bootloader) imei2: 35905207393****
(bootloader) ssn: H2AZB601E85****
(bootloader) isn: MB352KL0A****
(bootloader) color: 1B
(bootloader) country: BR
(bootloader) customer: CKD
(bootloader) revenuecountry: BR
OKAY [ 0.188s]
Finished. Total time: 0.188s
(the **** don't actually come up... it's just to hide the information I believe may be sensitive)
Help. Please