Database Users

Please help - official OTA Nougat update has left phone in boot loop

Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you

adavies said:
Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you
Click to expand...
Click to collapse
First of all, "adb devices" doesn't work on the bootloader. The adb app only works in recovery or while booted into the system. Secondly, is your bootloader unlocked? How you proceed depends on that. If you still want to install Nougat there are a couple of options. Let me know your current bootloader status. Above all, don't panic and do something rash.
Here is a link to your phone's stock firmware" https://www.filefactory.com/file/5c...24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip

Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.

Also thank you for the link to the firmware, I just checked and this is the same file that I already downloaded so I do at least have peace of mind that I selected the right one.

Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.

_wyrm said:
Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.
Click to expand...
Click to collapse
Hi, thanks for your reply, sadly I have tried all the options from the bootloader with no success, they do the following:
START - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
RESTART BOOTLOADER - Just takes me back to the same bootloader screen immediately
RECOVERY MODE - Takes me back to android man fallen over with 'No command' underneath
POWER OFF - turns it off (obviously lol)
FACTORY MODE - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BARCODES - displays white screen with four barcodes relating to IMEI, SKU, DATE and SERIAL NUMBER
BP TOOLS - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
QCOM - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BOOTLOADER LOGS - Doesn't do anything when I click the power button on this option but shows some yellow text on the screen that says 'Fastboot reason: Volume down key pressed'
That is all the options I have then, none seem to resolve the problem.
Thank you

Also, I'm not sure if this is relevant but when I ran the flashstock.bat file to try and install the files from XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml, I noticed as the text scrolled up the CMD window that there was several mentions of:
slot count not found
slot suffixes not found
has-slot system not found
invalid signed image
These lines appear several times, I'm not sure if this is part of the problem or not. If the CMD window didn't automatically close I would have copied and pasted exactly what it says.
Thanks again

Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.

adavies said:
Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.
Click to expand...
Click to collapse
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
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 erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612

_wyrm said:
Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.
Click to expand...
Click to collapse
Hi, thank you for your reply, I just downloaded and tried the RSD Lite software. It detected my phone on Port number 1 as 'Fastboot athene_13mp S' and I selected the 'flashfile.xml' and pressed start. Unfortunately it stopped with the status 'Failed flashing process. 3/27 flash partition "gpt.bin" -> Phone returned FAIL.' Does anyone know how to get round this?
Thank you

pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
]
Click to expand...
Click to collapse
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.

adavies said:
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.
Click to expand...
Click to collapse
Did you manually flash the fastboot images in the sequence provided?
If that doesn't work, I would send it back to Motorola. If it isn't in warranty, well, rip.

pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
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 erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
I do still get the serial number when running 'fastboot devices', do you think unlocking the bootloader might be the answer? I went through te steps yesterday to get the code, was a little put off by voiding the warranty though. With regards to running the commands one at a time, I think I am now getting a bit confused on the correct procedure of where to run the commands from. I have tried running it from the folder for 'Minimal ADB and fastboot' (this folder contains all the files from the stock firmware folder as well which I copied and pasted in there) and also directly from the stock firmware folder itself. I will paste the results of each below (sorry to confuse the issue, my head is fried now, lol).
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.049s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I stopped after the second line as the text above suggests to me that part has failed so no point continuing. When running directly from the firmware folder I get the following :
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot devices
ZY223H6QF4 fastboot
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.062s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>
Again this seems to fail also but with some slightly different messages. Interesting that it failed on the gpt.bin part as this was also mentioned when it failed on RSD Lite.

If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.

_wyrm said:
If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.
Click to expand...
Click to collapse
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you

adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.

adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
AFAIK, this one isnt safe to skip.. Im out of ideas, sorry. Try another usb cable just in case.. but if it keeps failing at the same point you will probably need to send it to motorola service.

pastorbob62 said:
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.
Click to expand...
Click to collapse
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>

adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.

negusp said:
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.
Click to expand...
Click to collapse
You may be right. He has not successfully unlocked the phone so therefore his warranty should still be good.
---------- Post added at 04:18 PM ---------- Previous post was at 03:51 PM ----------
adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
I don't understand why you can't flash the stock ROM. Your baseband version is still on stock. That said if you want to continue trying give this a shot: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943 This will bring you up to Nougat the latest release. It does not require an unlocked bootloader and has been used on your model.
Or here: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
Otherwise I would go ahead and do a warranty return. Your warranty should still be okay since you did not go through with unlocking the bootloader.
Click to expand...
Click to collapse

Help, my Moto X Style XT1752 Brick :(

Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
https://www.youtube.com/watch?v=njXQYn53SPc
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.

AlexAndroid said:
Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.
Click to expand...
Click to collapse
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.

acejavelin said:
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.
Click to expand...
Click to collapse
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.

AlexAndroid said:
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.
Click to expand...
Click to collapse
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?

acejavelin said:
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?
Click to expand...
Click to collapse
You mean this? (attached image)

Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you

AlexAndroid said:
Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you
Click to expand...
Click to collapse
Do you know how to use fastboot and adb? This is from a computer...

acejavelin said:
Do you know how to use fastboot and adb? This is from a computer...
Click to expand...
Click to collapse
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(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 Micron S8 SDRAM DIE=6Gb M5=x3 M6=x0 M7=x0 M8
(bootloader) ram[1]: =x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ---
(bootloader) cid: 0x0007
(bootloader) channelid: 0x51
(bootloader) uid: 368A71011E000000000000000000
(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: -----
(bootloader) meid:
(bootloader) date: 12-13-2016
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Feb 5 7:26: 3 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_APAC_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ga389d53 (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 Dec 8 06:27:17 CST 2016
(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 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retapac

AlexAndroid said:
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(bootloader) date: 12-13-2016
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
Click to expand...
Click to collapse
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
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 # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot

acejavelin said:
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
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 # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?

AlexAndroid said:
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?
Click to expand...
Click to collapse
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.

acejavelin said:
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.
Click to expand...
Click to collapse
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s

AlexAndroid said:
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s
Click to expand...
Click to collapse
Then your choices are Moto repair or wait for the 20-16 firmware to be released.

acejavelin said:
Then your choices are Moto repair or wait for the 20-16 firmware to be released.
Click to expand...
Click to collapse
Do Motorola's official technical services have the necessary firmware?

AlexAndroid said:
Do Motorola's official technical services have the necessary firmware?
Click to expand...
Click to collapse
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/

If you are in warranty and u haven't unlocked your boot loader yet you can give silly reason's like i revived updates last night but battery was low and while updating it turned off and now my phone isn't booting up

acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Hello, finally I take the equipment to an official technical service of Motorola, where they told me that they could not repair it since the cell phone did not take Software. Is this possible or would it be that the technical service did not have the necessary software version?

acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Good afternoon, I return the subject after a long time since yesterday I thought to try again, and I found that the cell now turns on, but when trying to complete the initial configuration, after choosing the language gives me to select the wifi networks, where it does not detect any, and I do not enable the jump or forward button, and I'm stuck there again, it's very strange, as soon as I enter that screen, it gives me the option to add a new network, and I can see that says Mac Address with pure zeros, as if it did not have MAC.
If I try to enter the recovery, now I see "No Command" (previously not directly entered), and there is no way to skip this "No Command", I have tried all the methods that appear online.
EDIT: I was able to get into recovery, but I do not know if it can help me now.
Any ideas? he seems to be brigado, but not as much as before

Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.

Edvin73 said:
Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.
Click to expand...
Click to collapse
I still have a problem, when the device is turned on, it always turns on Bootloader mode, and I have to select "Start" to turn it on. This is why when you want to upgrade to Android 7 via OTA, when the device is restarted during installation, it enters Bootloader mode, select "Start", restarts the update, restarts in Bootloader, and remains in an infinite cycle.
Is there a solution to this? I have already activated USB debugging in order to unlock the Bootloader.
Thank you!!

Twrp .img file to big for flashing?

So I recently got a moto x style (pure) running android 6.0 marshmallow and have unlocked the bootloader. But when trying to flash twrp 3.1 I get this message
target reported max download size of 536870912 bytes
sending 'recovery' (34102 KB)...
OKAY [ 1.141s]
writing 'recovery'...
(bootloader) Image size exceeded partition limits
(bootloader) image size exceeds limit
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.205s
Is there anyway to fix this and how can I fix it?

What command did you enter?
"fastboot flash..."?

Your recovery partition (mmcblk0p32) should be about 11264 blocks @ 4096kB per block so ~46.14MB... more than enough room for TWRP with 40%+ to spare.
What is the command you entered EXACTLY and can you boot TWRP successfully?
Code:
fastboot boot twrp-3.1.1-0-clark.img

acejavelin said:
Your recovery partition (mmcblk0p32) should be about 11264 blocks @ 4096kB per block so ~46.14MB... more than enough room for TWRP with 40%+ to spare.
What is the command you entered EXACTLY and can you boot TWRP successfully?
Code:
fastboot boot twrp-3.1.1-0-clark.img
Click to expand...
Click to collapse
No i can not boot it trough fastboot boot twrp-3.1.1-0-clark.img it just reboots as normal.

dzidexx said:
What command did you enter?
"fastboot flash..."?
Click to expand...
Click to collapse
Yes and I also tried mfastboot flash which doesn't work either.

isetnt said:
Yes and I also tried mfastboot flash which doesn't work either.
Click to expand...
Click to collapse
What is the output of "fastboot getvar all"? (Mask out IMEI please)?

Never encountered this issue.. i think maybe there might be some less storage remaining on your device?? Try uninstalling some apps,imgs and try again!
Hopefully should work

Sagar_1401 said:
Never encountered this issue.. i think maybe there might be some less storage remaining on your device?? Try uninstalling some apps,imgs and try again!
Hopefully should work
Click to expand...
Click to collapse
It's recovery... It has its own partition only for that, has nothing to do with app space.

acejavelin said:
What is the output of "fastboot getvar all"? (Mask out IMEI please)?
Click to expand...
Click to collapse
When doing it I get this output
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA44904I9X
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 8D13D20B0B000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 10-16-2014
(bootloader) sku: XT1095
(bootloader) iccid: 8901260002767386677
(bootloader) cust_md5: 94CDE6B08D9D17B4BF64FA14E8B18163
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 28 12:23:55 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/victara_tmo/victara:6.0/M
(bootloader) ro.build.fingerprint[1]: PE24.49-18/20:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.11.18.victara_tmo
(bootloader) ro.build.version.full[1]: .tmo.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.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_T
(bootloader) version-baseband[1]: MO_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g389e46b ([email protected]
(bootloader) kernel.version[1]: ilclbld87) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Nov 3 16:55:43 CST 2015
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: unknown

Sagar_1401 said:
Never encountered this issue.. i think maybe there might be some less storage remaining on your device?? Try uninstalling some apps,imgs and try again!
Hopefully should work
Click to expand...
Click to collapse
It's another partition but it still wouldn't be a problem as I've only used about 20-30% of my memory

isetnt said:
(bootloader) product: victara
(bootloader) sku: XT1095
Click to expand...
Click to collapse
Your problem is clear, you don't have a Moto X Pure/Style, you have a Moto X 2nd Gen or Moto X 2014 (which is sometimes called "Pure" but it's different), try this one: https://twrp.me/devices/motorolamotox2014.html

acejavelin said:
Your problem is clear, you don't have a Moto X Pure/Style, you have a Moto X 2nd Gen or Moto X 2014 (which is sometimes called "Pure" but it's different), try this one: https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
Okay so I got the right img and it flashes but when doing fastboot boot recovery.img it just restarts as normal. Should i flash a custom boot img?

isetnt said:
Okay so I got the right img and it flashes but when doing fastboot boot recovery.img it just restarts as normal. Should i flash a custom boot img?
Click to expand...
Click to collapse
I don't know the intricacies of that device... Some devices you can't boot recovery directly with fastboot and that's normal
Honestly you should go to the Moto X 2014 area and read or ask there. Not trying to blow you off, you are just more likely to get right answers there.

acejavelin said:
I don't know the intricacies of that device... Some devices you can't boot recovery directly with fastboot and that's normal
Honestly you should go to the Moto X 2014 area and read or ask there. Not trying to blow you off, you are just more likely to get right answers there.
Click to expand...
Click to collapse
Okay i will

acejavelin said:
Your recovery partition (mmcblk0p32) should be about 11264 blocks @ 4096kB per block so ~46.14MB... more than enough room for TWRP with 40%+ to spare.
What is the command you entered EXACTLY and can you boot TWRP successfully?
Click to expand...
Click to collapse
i got the same error as him while flashing stock rom for XT1550.tried everything, but the boot,recovery and modem(yes now there is no signal) won't flash.

debojyotidey said:
i got the same error as him while flashing stock rom for XT1550.tried everything, but the boot,recovery and modem(yes now there is no signal) won't flash.
Click to expand...
Click to collapse
Are you sure you are flashing twrp for xt1550?
https://eu.dl.twrp.me/osprey/
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
https://forum.xda-developers.com/devdb/project/dl/?id=17769

dzidexx said:
Are you sure you are flashing twrp for xt1550?
https://eu.dl.twrp.me/osprey/
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
https://forum.xda-developers.com/devdb/project/dl/?id=17769
Click to expand...
Click to collapse
i flashed the twrp by squid.i can flash twrp successfully, and even boot in twrp,flash roms and stuffs using twrp and then boot into that rom too.problems arise when i flash stock recovery, boot,modem.thing is, the size of those (say boot.img is abt 16MB, when i try to flash it using fastboot,the size which is getting flashed(shown by sending...) is abt 32MB.it's very strange,but also the only thing i can relate to the error message i get 'Image size exceeded partition limits'.
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
debojyotidey said:
i flashed the twrp by squid.i can flash twrp successfully, and even boot in twrp,flash roms and stuffs using twrp and then boot into that rom too.problems arise when i flash stock recovery, boot,modem.thing is, the size of those (say boot.img is abt 16MB, when i try to flash it using fastboot,the size which is getting flashed(shown by sending...) is abt 32MB.it's very strange,but also the only thing i can relate to the error message i get 'Image size exceeded partition limits'.
Click to expand...
Click to collapse
now if i flash roms using the twrp,since modem isn't there (after execution of fastboot erase modem..... command,i don't recall exactly) rom is working with exception of modem stuffs.

You downloaded & upacked stock from here:
https://mirrors.lolinet.com/firmware/moto/osprey/official/RETASIA/
Flashed modems/baseband this way:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
And now you haven't any sim or wifi?
Did you try to flash stock boot.img in twrp? @debojyotidey

dzidexx said:
You downloaded & upacked stock from here:
https://mirrors.lolinet.com/firmware/moto/osprey/official/RETASIA/
Flashed modems/baseband this way:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
And now you haven't any sim or wifi?
Did you try to flash stock boot.img in twrp? @debojyotidey
Click to expand...
Click to collapse
the problem started when i went to flash stock.not from your link though.by seeing the file size in the link you provided i can say it might be the same file.the thing is that when i tried to flash the boot,recovery and modem they showed that 'Image size exceeded partition limits'.so when i observed the file size that was getting flashed(say stock recovery which is about 16MB),it showed that the size of the file getting flashed is 32MB.this is very strange. however, when i tried flashing twrp which is 8156KB,it showed that the file size getting flashed is 8156KB.
so even when the boot,recovery and modem steps failed to get flashed(flash partition gpt.bin and bootlader not getting flashed i know the reason) i tried booting, which obviously didn't boot.so next i flashed twrp and then a custom rom,it booted!! but everything related to modem,like wifi,sim,etc were broken.i think it is expected. also now the software status is showing 'modified'.

I don't know why.
Maybe try another version min.adb&fastboot(uninstall previous first)
https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/ @debojyotidey

Unable to flash stock rom......please help

Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance

yshiv666 said:
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
Click to expand...
Click to collapse
Which ROM version you are trying ?
Try with latest September's patch one available here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

____Mdd said:
Which ROM version you are trying ?
Try with latest September's patch one available here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
yes I had tried it but it is not working

yshiv666 said:
yes I had tried it but it is not working
Click to expand...
Click to collapse
Was your bootloader unlocked ?
In bootloader loader screen it shows locked now, and system modified !
Baseband is unknown in bootloader screen, so i can say modem is not getting installed, (plus there may be other things too which are not getting installed)
Noe, do it, Flash ROM again,
But with entering one command at time,
After flashing/ending of one command, check that you are getting "OKAY"..
Let us know if there is any error or "FAILED" at command end.

____Mdd said:
Was your bootloader unlocked ?
In bootloader loader screen it shows locked now, and system modified !
Baseband is unknown in bootloader screen, so i can say modem is not getting installed, (plus there may be other things too which are not getting installed)
Noe, do it, Flash ROM again,
But with entering one command at time,
After flashing/ending of one command, check that you are getting "OKAY"..
Let us know if there is any error or "FAILED" at command end.
Click to expand...
Click to collapse
yes!!!! it says "FAILED" at the end.... see the screenshot of CMD

yshiv666 said:
yes!!!! it says "FAILED" at the end.... see the screenshot of CMD
Click to expand...
Click to collapse
That screenshot is of system,
What about bootloader and gpt ?
Again, tell me which version of ROM you are trying ?

____Mdd said:
That screenshot is of system,
What about bootloader and gpt ?
Again, tell me which version of ROM you are trying?
Click to expand...
Click to collapse
here is the screenshot for gpt.bin and bootloader.img!!!!!
and I'm flashing Sept 01 Security Patch which you have mentioned above.........

yshiv666 said:
here is the screenshot for gpt.bin and bootloader.img!!!!!
and I'm flashing Sept 01 Security Patch which you have mentioned above.........
Click to expand...
Click to collapse
I have never faced or seen anyone with this like issue,
Wait a while, @echo92 has better experience with this like stuff, he will guide you better than me.
Till than you can try blank flash again, with replacing gpt and bootloader from ROM's zip.

____Mdd said:
I have never faced or seen anyone with this like issue,
Wait a while, @echo92 has better experience with this like stuff, he will guide you better than me.
Till then you can try blank flash again, with replacing gpt and bootloader from ROM's zip.
Click to expand...
Click to collapse
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:

yshiv666 said:
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
Click to expand...
Click to collapse
Wait, December's !
You got your device back is good thing, but remain stuff will be of September's patch..
Now if you get update notification for December's patch dont take it... It will brick your device again.
You will have to wait for fastboot ROM of December's patch..
Till then, keep your phone on September...
Don't take OTA...
When December's patch build is available flash it with fastboot...

yshiv666 said:
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
Click to expand...
Click to collapse
Good to hear you got your device working. As ____Mdd has mentioned, I would strongly recommend you wait for the Dec 2017 stock ROM to flash. Looking at your bootloader details, since you've got a Dec 2017 GPT, a June/September 2017 bootloader and a marshmallow baseband, you likely cannot safely take OTA updates.
Because you've downgraded from Nougat to marshmallow, taking OTA updates runs a high risk of hard bricking again and our current blank flash may not work on your device now you've flashed the Dec 2017 GPT. Thus, do not take OTA updates until you flash the Dec 2017 Nougat stock ROM (which isn't available yet), and if you later downgrade again, do not accept OTA updates. Else the OTA updates may corrupt your newer bootloader again (bootloaders do not downgrade) with no recourse except to wait for a newer blankflash or a 8000+ rupees repair.

I have the same case and it sends me an error in the boot.
Can somebody help me

Turning OEM on without phone turning on
al3al3al3jandr0 said:
I have the same case and it sends me an error in the boot.
Can somebody help me
Click to expand...
Click to collapse
I am trying to flash my ROM as the phone is not turning on in any method be it normal of recovery mode or factory mode. My phone MOTO G4 Plus is unable to flash the ROM as it is OEM_LOCKED and None of the options from the bootloader menu works. On selecting any of the options from the power button nothing happens except for the barcodes which show the barcode and RESTART BOOTLOADER restarts the bootloader.
Please help someone.
Is there a way to unlock OEM without turning the phone on as I can't turn it on.

qjzxvkw said:
I am trying to flash my ROM as the phone is not turning on in any method be it normal of recovery mode or factory mode. My phone MOTO G4 Plus is unable to flash the ROM as it is OEM_LOCKED and None of the options from the bootloader menu works. On selecting any of the options from the power button nothing happens except for the barcodes which show the barcode and RESTART BOOTLOADER restarts the bootloader.
Please help someone.
Is there a way to unlock OEM without turning the phone on as I can't turn it on.
Click to expand...
Click to collapse
why doesn't it boot??? What were you doing before this happened. Please give the details

Heeth21 said:
why doesn't it boot??? What were you doing before this happened? Please give the details
Click to expand...
Click to collapse
Nothing I just kept it for charging overnight. And it doesn't power on in the morning. I plugged it while it was on though.
Someone suggested it has damaged its motherboard.

qjzxvkw said:
Nothing I just kept it for charging overnight. And it doesn't power on in the morning. I plugged it while it was on though.
Someone suggested it has damaged its motherboard.
Click to expand...
Click to collapse
Hmm, do you recall if there was an update notification at all before you put your device on charge?
Without getting your device to boot, there's no way to toggle the OEM_unlocking function unfortunately.
If you can, when you've plugged your device to your computer and booted to the bootloader:
1)Open a minimal ADB command window on Windows (download/install minimal ADB from here: https://forum.xda-developers.com/showthread.php?t=2317790 other fastboot/adb tools should work too)
2)Type 'fastboot devices' without quotes into the window. Press Enter - your device should respond with its serial number.
3)If you get that response, type 'fastboot getvar all' without quotes. Press Enter.
4)Please paste the output here or upload it as a text file (or paste it into a site like pastebin and put the link here). You may wish to omit the IMEI.
We could try to re-flash the stock firmware that you had, but if that doesn't solve things it may start to look like a hardware failure.

yshiv666 said:
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
Click to expand...
Click to collapse
make sure your bootloader is unlocked. and let me know.

echo92 said:
Hmm, do you recall if there was an update notification at all before you put your device on charge?
Without getting your device to boot, there's no way to toggle the OEM_unlocking function unfortunately.
If you can, when you've plugged your device to your computer and booted to the bootloader:
1)Open a minimal ADB command window on Windows (download/install minimal ADB from here: https://forum.xda-developers.com/showthread.php?t=2317790 other fastboot/adb tools should work too)
2)Type 'fastboot devices' without quotes into the window. Press Enter - your device should respond with its serial number.
3)If you get that response, type 'fastboot getvar all' without quotes. Press Enter.
4)Please paste the output here or upload it as a text file (or paste it into a site like pastebin and put the link here). You may wish to omit the IMEI.
We could try to re-flash the stock firmware that you had, but if that doesn't solve things it may start to look like a hardware failure.
Click to expand...
Click to collapse
Thanks for the response: Here is everything you asked:
I am sure there was no update notification as I always download any update that is released as soon as I see it. So I might have updated already.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223BGGD2 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223BGGD2
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 6E23DD0000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *************
(bootloader) meid:
(bootloader) date: 06-06-2016
(bootloader) sku: XT1643
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Apr 20 23:52: 3 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-4/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.201.4.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_INDIA_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (208)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.244s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Thanks. It was indeed a hardware problem. Motherboard was broken in two pieces just below camera position.

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