Database Users

Error to "flash" the fastboot in Moto X Play XT1563

Hello guys,
I'm trying to downgrade my Moto X Play XT1563, I found a tutorial on the Internet using the fastboot for such a feat. From what I saw, many people use this tutorial to upgrade or simply go back to what it was before "flash".
But in the first command line, when I type in CMD, an error appears:
> fastboot flash partition gpt.bin
target reported max download size of 268435456 byte
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.485s
The tutorial is for this purpose doubt
1) Extract the Fastboot / ADB and images (zip ROM), extract the two zip's to a folder of your choice
2) Restart your phone mode 'Bootloader' (Turn off the cell and then press the volume button (minus) and (power for 2 seconds) and then release the power.)
It would be interesting to have activated in the "Developer options" the option "Allow OEM Unlock"
3) Now the CMD, enter the commands:
NOTE: system.img_sparsechunk may contain name or number, so check if you have only modify the hour.
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
fastboot erase userdata
fastboot reboot
I wonder if someone could help me solve this case, please.

You're lucky that it failed. It's totally okay.
Don't flash the Partition Table - gpt.bin and skip the bootloader.
It's not recommended to do so and there are even threads in this sub forum to warn people.
See: http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253
It can lead to bricking your device.
So just skip fastboot flash partition gpt.bin and fastboot flash bootloader bootloader.img, do everything else.

THANKS!
Wardenn said:
You're lucky that it failed. It's totally okay.
Don't flash the Partition Table - gpt.bin and skip the bootloader.
It's not recommended to do so and there are even threads in this sub forum to warn people.
See: http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253
It can lead to bricking your device.
So just skip fastboot flash partition gpt.bin and fastboot flash bootloader bootloader.img, do everything else.
Click to expand...
Click to collapse
Man you are the ****ing best! You save my phone. Thank you very much! I was so stressed! THANKSSSS!

Can't re-lock bootloader!

So I tried CM13 and wanted to go back to everything official. So I restored the ROM from this place: https://github.com/motoxplay/stock
...using this guide: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Then I tried read the official Motorola guide to re-locking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Unfortunately it doesn't work. Using the guide, at the first step, I get this message:
Code:
fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.141s
So I searched more on the web and ended up trying this:
Code:
fastboot oem lock
or
Code:
fastboot oem lock begin
and get this:
Code:
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.023s]
finished. total time: 0.023s
I also found someone around here who said that by flashing the ROM his bootloader was locked again. That didn't work for me. I'm still getting this
Code:
"Device is UNLOCKED. Status Code: 3"
on the bootloader.
What can I do?

My guess is you tried to flash wrong firmware, like Lollipop on the phone that already had Marshmallow. Or something that can't be flashed on locked bootloader, like retail firmware on carrier branded phone.

minimale_ldz said:
My guess is you tried to flash wrong firmware, like Lollipop on the phone that already had Marshmallow. Or something that can't be flashed on locked bootloader, like retail firmware on carrier branded phone.
Click to expand...
Click to collapse
Well for the bootloader they only give us 5.1 and my ROM is 6.1. But when I tried to flash the 5.1 ROM from the same page I got the same message. I'm a bit stuck.
Then I tried to reinstall TWRP and again same message.
I'm stuck...

OK so I was able to install TWRP and then try to go back to 5.1 but that didn't work. It's a shame I thought I could trust that Motorola would give good information.

Oh! Now I got it!
So, just in case someone is confused like I was, here's how to do it. First, find the right ROM. Then, go into fastboot.
Code:
fastboot oem lock begin
You'll get the message that's in the title "Please fully flash the signed build before locking phone" (which should have been obvious I know but I thought it was an error message). Nevertheless, after that message appears you flash the ROM like you would. For me it was:
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.99
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
To finish the locking I did
Code:
fastboot oem lock
And that was it!!

Prosis said:
Oh! Now I got it!
So, just in case someone is confused like I was, here's how to do it. First, find the right ROM. Then, go into fastboot.
Code:
fastboot oem lock begin
You'll get the message that's in the title "Please fully flash the signed build before locking phone" (which should have been obvious I know but I thought it was an error message). Nevertheless, after that message appears you flash the ROM like you would. For me it was:
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.99
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
To finish the locking I did
Code:
fastboot oem lock
And that was it!!
Click to expand...
Click to collapse
Which ROM you used (5.1.1 or 6.0)?
Did you get it from GitHub or official site of Motorola?
Which country are you from?

xboysz said:
Which ROM you used (5.1.1 or 6.0)?
Did you get it from GitHub or official site of Motorola?
Which country are you from?
Click to expand...
Click to collapse
That was in my OP : https://github.com/motoxplay/stock
You can't get it from an official source nor Motorola.
I used 6.0.1 the Canada Telus ROM. It also worked with the Bell version.

Prosis said:
That was in my OP :
You can't get it from an official source nor Motorola.
I used 6.0.1 the Canada Telus ROM. It also worked with the Bell version.
Click to expand...
Click to collapse
Thank you so much.
After hours of searching i couldn't find the right way to lock the bootloader.
Your post was like needle in the haystack for me.
Btw what's the status code of your bootloader?

xboysz said:
Thank you so much.
After hours of searching i couldn't find the right way to lock the bootloader.
Your post was like needle in the haystack for me.
Btw what's the status code of your bootloader?
Click to expand...
Click to collapse
You're welcome! I understand the frustration!
My status is 2. You can't get it back to what it was. 2 is an indicator that it was unlocked but that it's now locked.

Fail flash XT1575, firmware stock.

Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!

Lisandro4m41 said:
Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Click to expand...
Click to collapse
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.

acejavelin said:
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
Click to expand...
Click to collapse
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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 erase clogo
fastboot oem fb_mode_clear

Lisandro4m41 said:
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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 erase clogo
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.

acejavelin said:
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
Click to expand...
Click to collapse
Thanks! Right now I'm downloading the firmware of the Motorola official page. I hope it works. Thanks again!

I downloaded the firmware from the official website, but I can not install it, how I go about flashing?

Lisandro4m41 said:
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Click to expand...
Click to collapse
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?

Lisandro4m41 said:
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Click to expand...
Click to collapse
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.

acejavelin said:
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
Click to expand...
Click to collapse
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?

Lisandro4m41 said:
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Click to expand...
Click to collapse
Usually it means either the bootloader is still locked (which we know your's is unlocked) or the file is incorrect for your device. Sometimes it's a random error, try erasing the modemst1 and modemst2 first, then flash NON-HLOS.bin a time or two until it gives and OK and continue from there like normal.

I have not retested flash, but I solved my problem. The problem was that the phone was locked in Claro AR. No relation to the Bootloader error, but got what I wanted haha. Thanks for your time.
Greetings from Argentina.

FAILED (remote: Flashing is not allowed for Modem Partitions )

So I've been encountering this problem whenever I'm trying to do anything to the Modem Partitions on the Essential Phone:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
PM1LHMA7C1303309 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.032s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modemst1 modemst1.img
target reported max download size of 536870912 bytes
sending 'modemst1' (2048 KB)...
OKAY [ 0.765s]
writing 'modemst1'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.794s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modemst2 modemst2.img
target reported max download size of 536870912 bytes
sending 'modemst2' (2048 KB)...
OKAY [ 0.168s]
writing 'modemst2'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.240s
And... flashing the img file using
Code:
fastboot flash modem_a or modem_b
didn't provide the result I wanted.
If anyone have some inputs would be really appreciated. Thanks...

Did you unlock critical? I don't remember the exact commands but it's similar to unlocking the bootloader.

gk1984 said:
Did you unlock critical? I don't remember the exact commands but it's similar to unlocking the bootloader.
Click to expand...
Click to collapse
I did. I've done both
Code:
fastboot flashing unlock
and
Code:
fastboot flashing unlock_critical
I'll be trying to flash older essential fastboot.img(s) to see wether that would change anything. Because from the r/essential on reddit, people actually were able to flash onto the modemst partitions.
reddit*com/r/essential/comments/9e9to8/invalid_sim_network_locked_fix_for_the_september/
I was doing the automatic steps, but the phone literally doesn't respond to .bat file provided. So I tried doing it manually, and it was when I hit this partition problem.
If it's not asking to much, would someone confirm wether or not flashing onto this partition is possible? Thanks

You must unlock and downgrade bootloader (old android 7 rom) on last android 7 and 8,9 roms you cannot flash modemst part bcs security patches
flash NMK24B factory image first and after unlock_critical you can flash modemst parts
download rom from here https://www.essential.com/developer/current-builds
and after flash modemst parts you can flash android 8.1 rom and check if is it unlocked bcs after flash modemst parts phone stay in locked state on android 7

veisen said:
You must unlock and downgrade bootloader (old android 7 rom) on last android 7 and 8,9 roms you cannot flash modemst part bcs security patches
flash NMK24B factory image first and after unlock_critical you can flash modemst parts
download rom from here essential*com/developer/current-builds
and after flash modemst parts you can flash android 8.1 rom and check if is it unlocked bcs after flash modemst parts phone stay in locked state on android 7
Click to expand...
Click to collapse
So I've been trying to flash the NMK24B, I hadn't been successful these previous days, but I found a trick from this youtube video;
youtube*com/watch?v=RrMLqSXcxjI
So I'll proceed to flash the modemst partitions, and give you guys update.

Phone is Sim Unocked Now
So this is the manual process to do all this, if your phone isn't responding to the automatic procedure according to https://www*reddit*com/r/essential/comments/9e9to8/invalid_sim_network_locked_fix_for_the_september/.
Flash NMK24B on fastboot by running flashall.bat. If it's not sending package to the phone, then install Minimal ADB and copy fastboot.exe from Minimal ADB directory to NMK24B directory, the run the flashall.bat.
After the above procedure you will boot into adroid, re-enable usb debugging, then go to fastboot again. Open cmd from Minimal ADB and flash modemst, which you can find from reddit post above on Essential Unlock>Data>Modemst:
Code:
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
Resources are from the reddit post above. Credits goes to the creator of this trick (in which I do not know who).

Need your help. I just accidently selected radioband USA settings on my htc one m8. Now the network is completely gone. I saw on the internet to erase my modemst1 and modemst2 using fastboot. But it says that "failed (remote:not allowed). What does this mean? And how it'll allow me?
---------- Post added at 09:49 AM ---------- Previous post was at 09:45 AM ----------
Khan97bilal said:
Need your help. I just accidently selected radioband USA settings on my htc one m8. Now the network is completely gone. I saw on the internet to erase my modemst1 and modemst2 using fastboot. But it says that "failed (remote:not allowed). What does this mean? And how it'll allow me?
Click to expand...
Click to collapse
I also have s off. Bootloader unlocked. And device rooted.

Moto G5 Plus unaltered went into boot loop, result; imei 0, "failed to validate",

Moto G5 Plus unaltered went into boot loop, result; imei 0, "failed to validate",
Hi all,
I stumbled on this forum while trying to figure out a way to rescue my husband's Moto G5 Plus. Yesterday it went into a constant loop of restarts, at best functioning for 5 minutes before suddenly restarting for seemingly no reason.
He is not technically proficient enough to do any error seeking, let alone booting or flashing a new rom, so for all intents and purposes the phone is unaltered except doing the standard android updates, adding common apps and so on.
Well, the phone eventually ended up in fastboot flash mode where it keeps giving the error: faild to pass validaton, backup to fastboot. I found the menu option for barcodes and both imei and SKU are set to 000000000000 or how every many 0's. Date is set to 01-01-1970, but serial number is intact.
We tried installing Software Repair Assistant, but it keeps going on "Processing device information" for hours with no result.
Also tried installing the Lenovo Moto Smart Assistant for the Rescue mode, but it gives me "Failed to match the connected device".
Ideally we would like to find a way to bring back the contents of the phone if at all possible. I found a thread regarding imei 0 issue but I couldn't see if that would also wipe all contents so I am hesitant to try that without further research.
Being a slightly paranoid lawyer, my husband doesn't believe in backing up his stuff to cloud based solutions, so all his photos of the kids (and more) are per now toast. He has a new phone (and a slightly more modern approach to cloud backups) so there is no rush to fix NOW, but we'd like to know if there's any point in trying to restore or if we should go ahead with hacks to render it wiped but usable.
Does anyone here know of a good way to resolve this issue?

MrsMotz said:
Hi all,
I stumbled on this forum while trying to figure out a way to rescue my husband's Moto G5 Plus. Yesterday it went into a constant loop of restarts, at best functioning for 5 minutes before suddenly restarting for seemingly no reason.
He is not technically proficient enough to do any error seeking, let alone booting or flashing a new rom, so for all intents and purposes the phone is unaltered except doing the standard android updates, adding common apps and so on.
Well, the phone eventually ended up in fastboot flash mode where it keeps giving the error: faild to pass validaton, backup to fastboot. I found the menu option for barcodes and both imei and SKU are set to 000000000000 or how every many 0's. Date is set to 01-01-1970, but serial number is intact.
We tried installing Software Repair Assistant, but it keeps going on "Processing device information" for hours with no result.
Also tried installing the Lenovo Moto Smart Assistant for the Rescue mode, but it gives me "Failed to match the connected device".
Ideally we would like to find a way to bring back the contents of the phone if at all possible. I found a thread regarding imei 0 issue but I couldn't see if that would also wipe all contents so I am hesitant to try that without further research.
Being a slightly paranoid lawyer, my husband doesn't believe in backing up his stuff to cloud based solutions, so all his photos of the kids (and more) are per now toast. He has a new phone (and a slightly more modern approach to cloud backups) so there is no rush to fix NOW, but we'd like to know if there's any point in trying to restore or if we should go ahead with hacks to render it wiped but usable.
Does anyone here know of a good way to resolve this issue?
Click to expand...
Click to collapse
Is your device is rooted??? Or it on completely on stock ROM???
And what the last thing you do which cause this problem.

riyan65 said:
Is your device is rooted??? Or it on completely on stock ROM???
And what the last thing you do which cause this problem.
Click to expand...
Click to collapse
It's not rooted, completely stock except following the recommended updates.
As far as I know, he did not do anything except charging the phone at night, and in the morning it had restarted, then kept restarting all day until ending in fastboot with "failed validaton".

MrsMotz said:
It's not rooted, completely stock except following the recommended updates.
As far as I know, he did not do anything except charging the phone at night, and in the morning it had restarted, then kept restarting all day until ending in fastboot with "failed validaton".
Click to expand...
Click to collapse
Then it quite hard to recover data, but not least. You can try flashing the device from this procedure.
Here is the procedure:-
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_8.1.0_OPSS28.85-17-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Now your device will boot, if not try holding power button for 10sec then it reboot it self. If it won't boot then flash the device again with the following command
[Note:- this will erase all user data]
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash 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 erase clogo
fastboot oem fb_mode_clear
fastboot reboot
This will boot you device for sure.

riyan65 said:
Then it quite hard to recover data, but not least. You can try flashing the device from this procedure.
...
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Now your device will boot, if not try holding power button for 10sec then it reboot it self. If it won't boot then flash the device again with the following command
[Note:- this will erase all user data]
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash 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 erase clogo
fastboot oem fb_mode_clear
fastboot reboot
This will boot you device for sure.
Click to expand...
Click to collapse
OK, I tried the first bunch of commands. This is the result I got:
C:\ADB>fastboot devices
6be2e0bf fastboot
C:\ADB>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.013s
C:\ADB>
C:\ADB>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.084s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.107s
C:\ADB>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.603s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.807s
C:\ADB>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.738s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.981s
C:\ADB>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.584s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 0.606s
C:\ADB>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 3.643s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.714s
C:\ADB>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 8.946s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.017s
C:\ADB>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (256514 KB)...
OKAY [ 8.872s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.896s
C:\ADB>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (246302 KB)...
OKAY [ 8.489s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.530s
C:\ADB>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 9.057s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.149s
C:\ADB>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 9.063s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.092s
C:\ADB>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 9.070s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.096s
C:\ADB>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (250531 KB)...
OKAY [ 8.684s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.725s
C:\ADB>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (262059 KB)...
OKAY [ 9.034s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.073s
C:\ADB>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (254142 KB)...
OKAY [ 8.763s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.796s
C:\ADB>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71921 KB)...
OKAY [ 2.495s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 2.522s
C:\ADB>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.019s
C:\ADB>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.034s
C:\ADB>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.126s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.146s
C:\ADB>fastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.034s
C:\ADB>
C:\ADB>fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.018s
C:\ADB>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.021s
C:\ADB>fastboot reboot

MrsMotz said:
OK, I tried the first bunch of commands.
Click to expand...
Click to collapse
Chances are the gpt got corrupted as well..
Try
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash 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 erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Everything will be wiped. Also make sure you downloaded the latest firmware. 17-6-2 is the latest.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Same issue, same results!
My Moto G5 Plus XT1687 experienced the same type of failure just over a month ago. First, it began randomly rebooting (never a good sign...), then my entire sms history disappeared (every sms AFTER that moment, however, behaved normally: received and listed/logged as new messages)... Then, about two days later, I woke up to a bricked phone. My phone was never rooted. Around the time of the random reboots, I had allowed my phone to update apps (I can't remember which happened first -- random reboots or app updates. I do know that I chose to update apps at that time because the phone was laggy and not behaving [even though there was ample unused storage available, and no apps stood out as memory hogs, etc.]). (Developer mode was enabled, but probably not USB debugging.)
On the barcode screen, my phone displays an IMEI of all zeros, a SKU of all zeros, and a date of 01-01-1970 (there is a serial number that may or may not be the original. It does not appear anywhere on the box label [where my actual IMEI and other numbers/codes are printed]).
I have tried flashing POTTER_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info (as well as a few older ones -- just to try) using variations* of the standard code, above (*with and without "flash partition gpt.bin" and "flash bootloader bootloader.img"...). I have not yet taken the leap of including "erase userdata", however, because I am worried about losing anything that might not have been backed up... (And if every single previous line of code has failed, will adding "erase userdata" toward the end make a difference...?)
Down the list, the results are identical to the ones posted here by MrsMotz: "FAILED (remote failure)", "failed to erase", "failed to validate", "failed to flash", "invalid signed image", etc. (I've also tried using the Lenovo Moto Smart Assistant Flash/Rescue tool [which I imagine is supposed to perform essentially the same function as flashing ROM manually] to no avail ["Failed to match connected device"]!)
I can't afford a new phone! I desperately need to make this one work again. What am I missing? Why did my phone self-brick, and how can I fix it?

Same issue, same results! Update
On the barcode screen, my phone displays an IMEI of all zeros, a SKU of all zeros, and a date of 01-01-1970 (there is a serial number that may or may not be the original. It does not appear anywhere on the box label [where my actual IMEI and other numbers/codes are printed]).
Click to expand...
Click to collapse
So, the "serial number" currently showing on my phone is not the real/actual/original serial number. My real serial number went the way of my real IMEA, I guess! Is this normal when a phone is bricked? Also, might the loss of my phone's genuine identifiers be contributing to the inability be "validated" or "recognized"...?

mahuba3 said:
So, the "serial number" currently showing on my phone is not the real/actual/original serial number. My real serial number went the way of my real IMEA, I guess! Is this normal when a phone is bricked? Also, might the loss of my phone's genuine identifiers be contributing to the inability be "validated" or "recognized"...?
Click to expand...
Click to collapse
Seems to be a hardware issue. No IMEI, no serial, date reset to 1970...
Also the random reboots and the other things happening before are pointing to that direction.
So you're still able to reach fastboot mode and flash stock firmwares. When you say you were never rooted I suspect your bootloader is still locked?
If so I'm out of ideas, there isn't much you can do with an bootloader locked device.
I'm pretty sure that your hardware is the problem, so service center (depending on the country you live in) or buying a new device seem to be the only ways to go.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
Seems to be a hardware issue. No IMEI, no serial, date reset to 1970...
Also the random reboots and the other things happening before are pointing to that direction.
So you're still able to reach fastboot mode and flash stock firmwares. When you say you were never rooted I suspect your bootloader is still locked?
If so I'm out of ideas, there isn't much you can do with an bootloader locked device.
I'm pretty sure that your hardware is the problem, so service center (depending on the country you live in) or buying a new device seem to be the only ways to go.
Click to expand...
Click to collapse
Thank you ... But darn
Bootloader is locked (screen says "oem_locked"). But, yes, I am able to reach fastboot mode. And the bootloader logs come through each time I attempt to flash anything...
PS My phone, purchased new, is only two and a half years old (I usually hold onto them much longer!). But... I did drop it into the pool at the YMCA several months ago... It had been "misbehaving" (background apps crashing) prior, but after four days in rice and silica packets, it came out working just as well as before...

@mahuba3: Any luck bro? I am also having the same issue, if you have fixed your phone, share me the details please.
mahuba3 said:
Thank you ... But darn
Bootloader is locked (screen says "oem_locked"). But, yes, I am able to reach fastboot mode. And the bootloader logs come through each time I attempt to flash anything...
PS My phone, purchased new, is only two and a half years old (I usually hold onto them much longer!). But... I did drop it into the pool at the YMCA several months ago... It had been "misbehaving" (background apps crashing) prior, but after four days in rice and silica packets, it came out working just as well as before...
Click to expand...
Click to collapse

Moto g5 plus
Any solution
I have the same problem

I'm having a very similar issue, but I can't login to bootloader screen. It just starts on a screen saying "start up failed" and when I try to run the commands you say it responds with an error
> fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.016s
> fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.016s

SAme problem here too, Just two days ago, woke up to this bricked phone.

hello there im facing the same issue i would like to recover my files from the phone. i dont care if i could use the phone further pls reply.

same problem here! i'm on a linux pc

Help needed! (newbie here)
I have a moto g5 plus (potter) and it is locked on this screen. I already tried to use the motorola recovery program but he doesn't recognize it because imei appears 0000000. I need help to bring it back to life (my computer is linux) and if possible to install the factory rom on it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Facing the same issue, can anyone help?