Database Users

[[Video Tutorial]] Downgrade Moto E Android 5.0.2 to Stock 4.4.4

Here's The Video Tutorial on Downgrading Your Moto E from Android 5.0.2 to STOCK KitKat 4.4.4. Yes ! 4.4.4.
http://youtu.be/w7S5WmlPgrI
1. Download Stock 4.4.4
2. Download mfastboot.
3. Download ADB. ( Download Links are in video description)
Now flash Stock 4.4.4 using adb.
commands :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If every command you entered was successfully executed, your phone will reboot into stock firmware ! And I bet it would not brick your phone...
THANK.
Get Me On ; [email protected]
Like Us On Facebook www.facebook.com/axayleo

Will it work on locked bootloader..

Yes
mukulgupta690 said:
Will it work on locked bootloader..
Click to expand...
Click to collapse
Yes It will because the Stock firmwares are officially signed by Motorola.

I have installed soak test version of android 5.0.2...will i get the official update in future...motorola guys says that if you installed softer manually you will not get that please help..

You will get update if you have not rooted and installed custom recovery.
mukulgupta690 said:
I have installed soak test version of android 5.0.2...will i get the official update in future...motorola guys says that if you installed softer manually you will not get that please help..
Click to expand...
Click to collapse
It depends on if you have rooted and installed custom recovery or not. But if you are not on root you will get update for sure...

Will unlocking and locking the bootloader show the status code 2 in reocvery menu???

KaziRahman said:
Will unlocking and locking the bootloader show the status code 2 in reocvery menu???
Click to expand...
Click to collapse
locked bootloader is not required to get OTA update, the only require is stock recovery and stock rom.

Thanks , it worked after unlocking Bootloader

please read the sticky warning thread for this issue.
[WARNING] IMPORTANT DOWNGRADING / HARD BRICKING INFORMATION
USE THIS AT YOUR OWN RISK!!!!!!

Unable to Downgrade from Lollipop
Hi , i tried downgrading from soak test lollipop to 4.4.4 and i get the following error . Help me if possible . I have locked bootloader.
C:\Users\ \Desktop\ \ \Stock 4.4.4> fastboot flash boot boo
t.img
target reported max download size of 299892736 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.353s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.033s
C:\Users\ \Desktop\ \ \Stock 4.4.4>fastboot flash recovery
recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 1.939s]
finished. total time: 2.318s
C:\Users\ \Desktop\ \ \Stock 4.4.4>fastboot.exe flash syst
em system.img_sparsechunk.0
target reported max download size of 299892736 bytes
sending 'system' (243072 KB)...
OKAY [ 8.025s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.701s

sham4u2sam said:
Hi , i tried downgrading from soak test lollipop to 4.4.4 and i get the following error . Help me if possible . I have locked bootloader.
C:\Users\ \Desktop\ \ \Stock 4.4.4> fastboot flash boot boo
t.img
target reported max download size of 299892736 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.353s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.033s
C:\Users\ \Desktop\ \ \Stock 4.4.4>fastboot flash recovery
recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 1.939s]
finished. total time: 2.318s
C:\Users\ \Desktop\ \ \Stock 4.4.4>fastboot.exe flash syst
em system.img_sparsechunk.0
target reported max download size of 299892736 bytes
sending 'system' (243072 KB)...
OKAY [ 8.025s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.701s
Click to expand...
Click to collapse
Download the signed stock rom by motorola, the problem will be solved. This rom is not official/signed. OP just updated a faulty link.

bhumik147 said:
Download the signed stock rom by motorola, the problem will be solved. This rom is not official/signed. OP just updated a faulty link.
Click to expand...
Click to collapse
can u provide link for that , searched in XDA coudnt find it .

My mistake, There is no Stock Image by motorola yet for 4.4.4

A Complete solution for your Comment.
bhumik147 said:
Beware of this post , it will lead you to hard brick your device permanently.
Click to expand...
Click to collapse
Oh then why didn't the same procedure bricked sorry hard bricked my device A-Hole. Don't Spam Shaking your Moto G. This is for Moto E.
1. The commands include flashing gpt.bin partition and motoboot which will lead to hardbrick on downgrade from 5.0.2.
I am also Moto G user, from experience in that phone i know how downgrading destroys your device.
Click to expand...
Click to collapse
Isn't it funny. You at least had read the sticky that what makes your device get in Hard brick.
That's by downgrading to 4.4.2 and then upgrading via OTA to 4.4.4. A-Hole so, STFU.
Read This S**thead
http://forum.xda-developers.com/moto-e/general/warning-downgrading-information-moto-e-t3062859
2. Also, the images are not officially signed by motorola. i.e 4.4.4 ROM. Proof is in the image.
I Thank god , my bootloader was locked and i failed to flash the ROM properly.
Click to expand...
Click to collapse
So, search for Official KitKat 4.4.4 Stock Rom for Moto E on XDA itself. You'll find the same ROM. And Keep Sharing Screenshot Thats good for you jerk.
And talking about what happened in your screenshot go head on to Motorola's official website and Download official 4.4.2 KitKat Stock Rom and flash it. I bet you'll see the same. That's an not yet fixed problem with moto E.
Research before you say A-Hole.
The commands of downgrade should be :
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
"with for a SIGNED ROM"
Click to expand...
Click to collapse
Now this last answer to whole of your post.
This is if you are downgrading from 4.4.4 to 4.4.2...
Not if you're getting off with lollipop. Okay Read Heading Carefully it downgrading from lollipop to KitKat 4.4.4
A MeanHead Watch my Video Carefully It worked and I successfully downgraded to KitKat. And Everyone even a noon knows that to install Lollipop soak test one must be on Stock android 4.4.4. And After flashing this I successfully Upgraded to Lollipop. So get Life and don't spam. Like you're jealous or something.
If it was supposed to brick my device would have bricked first I do this almost every 2 Week. And never ever encountered a soft brick you talking about hardbrick...

Toledo_JAB said:
please read the sticky warning thread for this issue.
[WARNING] IMPORTANT DOWNGRADING / HARD BRICKING INFORMATION
USE THIS AT YOUR OWN RISK!!!!!!
Click to expand...
Click to collapse
Yeah You are Right. It will HARDBRICK if someone downgrades to 4.4.2 and then upgrades via OTA to 4.4.4.
But Mine is Downgrading directly to 4.4.4 from 5.0.2 so no issues like Hard brick isn't.
Meanwhile i never encountered it.
btw thanks a lots for a useful link...

meakshay_mishra said:
Yeah You are Right. It will HARDBRICK ..
Click to expand...
Click to collapse
oh , sorry bro. I had a great misunderstanding. Sorry for the trouble, you are right about it. The only solution is we have to wait for stock 5.0.2 Image by motorola to lock the bootloader.

bhumik147 said:
oh , sorry bro. I had a great misunderstanding. Sorry for the trouble, you are right about it. The only solution is we have to wait for stock 5.0.2 Image by motorola to lock the bootloader.
Click to expand...
Click to collapse
But I think Motorola is thinking to upgrade Moto E directly to 5.1

meakshay_mishra said:
But I think Motorola is thinking to upgrade Moto E directly to 5.1
Click to expand...
Click to collapse
More later we will get the official taste. Anyways, 5.0.1 is not smooth like in other devices , which is saok's issue and aosp issue too.

meakshay_mishra said:
Here's The Video Tutorial on Downgrading Your Moto E from Android 5.0.2 to STOCK KitKat 4.4.4. Yes ! 4.4.4.
http://youtu.be/w7S5WmlPgrI
1. Download Stock 4.4.4
2. Download mfastboot.
3. Download ADB. ( Download Links are in video description)
Now flash Stock 4.4.4 using adb.
commands :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If every command you entered was successfully executed, your phone will reboot into stock firmware ! And I bet it would not brick your phone...
THANK.
Get Me On ; [email protected]
Like Us On Facebook www.facebook.com/axayleo
Click to expand...
Click to collapse
Does it work on rooted MotoE ? I read somewhere that its works only none rooted and stock recovery installed phone
Anyone tried this method?

it worked for me

Converted XT1033 5.1 GPe to Stock Moto 5.0.2

So I was searching through the threads to find me solution for me to go back to Moto Stock 5.0.2 from GPe 5.1 since my device is a XT1033 I couldn't simply flash the Lollipop firmware on the GPe firmware. Now I'm not sure if there is a better way but here is how I achieved it; it's a little long but till I have no other way here it is:
Don't worry about the bootloader at this stage. 41.19 will automatically go to 41.18 when you shift but won't have any effect so here's the procedure:
First flash back to KitKat GPe the normal way using the following commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
(Be cautious as to not to flash the partition and logo function this will cause your device to brick due to incompatible partition and other things)
Once this is done and your phone boots up, power down again and then flash it to XT1033 KitKat Firmware using the exactly same commands as you did for 5.1 to 4.4.4 GPe. (The above commands)
After the phone boots up on 4.4.4 Moto Stock power the device down yet again; Now there are two ways either flash the 5.0.2 entirely using the following commands:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
This is a better way to go to Lollipop;
Or else you could sideload the update file using the adb function in the stock recovery(I personally suggest don't do this).
For this reboot to bootloader, scroll to recovery and press the volume up when u see the dead android, press the volume button for couple of seconds and then the power button then using update via adb sideload use send the file using adb sideload followed by "update.zip"
Hope this help's...
Asia Retail Links:
4.4.4 Moto Stock: https://drive.google.com/file/d/0B5uo5LCdnblrVlhsRmdyeDRYV1E/edit
4.4.4 GPe : http://www.filefactory.com/file/14mn1ui7sx0t/GPE_XT1032_KOT49H.M004_CFC.xml.zip
5.0.2 Moto Stock : https://drive.google.com/file/d/0B5uo5LCdnblrcHJMblF3MlhaUjQ/edit
Brazil Retail Links:
4.4.4 Moto Stock: http://d-h.st/7sG
5.0.2 Moto Stock: http://d-h.st/buH** (Only update zip -- Official Soak test)
http://www.filefactory.com/file/3buo0jqjvn41/BRASIL_XT1033_5.0.2_LXB22.46-28_cid12_CFC.xml.zip (Full Firmware)
Charge the device to 100% I suggest cause this a very long procedure and it drains about nearly half the battery at least it did for me.
**Tip for the Brazilian update since I couldn't get the full package you'll have to update to 4.4.4 by flashing using the command provided and then transfer the 5.0.2 zip file onto the device and then flash via stock recovery. I'll certainly try to get hold of the entire firmware of 5.0.2. I still suggest using the full firmware flash; start new.

Wt abt Indian version??

manoj36 said:
Wt abt Indian version??
Click to expand...
Click to collapse
What about it the XT1033 model number is the India/Brazilian variant both can use the same technique.

Hi!
Great tutorial! Will help many peoples!
But, I have two questions:
1 - Your tutorial works on XT1033 Brazilian firmare?
2 - Can you upload/give the link of 4.4.4 and 5.0.2 XT1033 Brazilian firmwares?
I've sucessfully installed GPE 5.1, but I want the "get back option" safe in my computer.
Cheers!
Note: English isn't my first language, so please excuse any mistakes.

dipeters said:
Hi!
Great tutorial! Will help many peoples!
But, I have two questions:
1 - Your tutorial works on XT1033 Brazilian firmare?
2 - Can you upload/give the link of 4.4.4 and 5.0.2 XT1033 Brazilian firmwares?
I've sucessfully installed GPE 5.1, but I want the "get back option" safe in my computer.
Cheers!
Note: English isn't my first language, so please excuse any mistakes.
Click to expand...
Click to collapse
Okay I'll answer to both you worries;
1. This tutorial could possibly work on the Brazilian firmware because it's almost one and the same the flashing of the system image.
2. I'll edit the OP; thanks for the tip
Cheers..

siddharthnair96 said:
Now I'm not sure if there is a better way but here is how I achieved it; it's a little long but till I have no other way here it is:
Click to expand...
Click to collapse
Dude, i dont know how much i can thank you! I had tried like a dozen ways to do this but all failed. Finally i decided to give your method a try this weekend, and it just worked awesomely! I am back on my original xt1033 ... now from there i installed cm12.1 which works flawlessly and even the sms is working (dual sim) which was for some weird reason wasnt working on my converted gpe on which I had installed cm12.1.
Again, thanks and keep sharing your great work

"Tip for the Brazilian update since I couldn't get the full package you'll have to update to 4.4.4 by flashing using the command provided and then transfer the 5.0.2 zip file onto the device and then flash via stock recovery. I'll certainly try to get hold of the entire firmware of 5.0.2. I still suggest using the full firmware flash; start new."
I get confused here.
Should I use the Full firmware 5.0.2 Brazillian and the other firmwares? [GPE KK 4.4.4 + BR KK 4.4.4 + BR LOLLI 5.0.2]
Or I flash the both 4.4.4 and flash the zip update? [GPE KK 4.4.4 + BR KK 4.4.4 + 5.0.2 ZIP]
Sorry for inconvenience

dipeters said:
"Tip for the Brazilian update since I couldn't get the full package you'll have to update to 4.4.4 by flashing using the command provided and then transfer the 5.0.2 zip file onto the device and then flash via stock recovery. I'll certainly try to get hold of the entire firmware of 5.0.2. I still suggest using the full firmware flash; start new."
I get confused here.
Should I use the Full firmware 5.0.2 Brazillian and the other firmwares? [GPE KK 4.4.4 + BR KK 4.4.4 + BR LOLLI 5.0.2]
Or I flash the both 4.4.4 and flash the zip update? [GPE KK 4.4.4 + BR KK 4.4.4 + 5.0.2 ZIP]
Sorry for inconvenience
Click to expand...
Click to collapse
My mistake you didn't understand GPe 5.1 -> GPe 4.4.4 -> BR KK 4.4.4 -> BR LP 5.0.2 (Use the full system flashing and do it )

Successfully converted from GPE 5.1 to Asia 5.0.1
Thanks !!

guys i flashed logo by error(automated flash .bat file).my phone is stuck at google logo what should i do????
plz help
i reverted back to 5.1 gpe and retried the operation.here is my log....
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot flash boot
boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.356s]
writing 'boot'...
OKAY [ 0.922s]
finished. total time: 1.310s
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot flash reco
very recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.373s]
writing 'recovery'...
OKAY [ 0.948s]
finished. total time: 1.323s
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot flash syst
em system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot flash syst
em system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot flash syst
em system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot flash syst
em system.img_sparsechunk.1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.1': No error
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot flash syst
em system.img_sparsechunk.2mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.2mfastboot': No error
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot flash mode
m NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47484 KB)...
OKAY [ 1.590s]
writing 'modem'...
OKAY [ 2.281s]
finished. total time: 3.871s
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot erase mode
mst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.028s
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot erase mode
mst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot flash fsg
fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (719 KB)...
OKAY [ 0.094s]
writing 'fsg'...
OKAY [ 5.340s]
finished. total time: 5.434s
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot erase cach
emfastboot erase cache
erasing 'cachemfastboot'...
(bootloader) Invalid partition name cachemfastboot
FAILED (remote failure)
finished. total time: 0.022s
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot erase cach
e
erasing 'cache'...
OKAY [ 0.098s]
finished. total time: 0.100s
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot erase user
data
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.477s
C:\Users\fazel\Downloads\Compressed\GPE_XT1032_KOT49H.M004_CFC.xml_2\GPE_XT1032_KOT49H.M004_CFC.xml>mfastboot reboot
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
i can flas back to 5.1 gpe every thing works fine......plz help me....what should i do ...redraw bug is killing me

any one?

deadfazel said:
any one?
Click to expand...
Click to collapse
Open the bootloader setting and start re-flashing again the entire sequence.

how to use mfastboot
siddharthnair96 said:
Okay I'll answer to both you worries;
1. This tutorial could possibly work on the Brazilian firmware because it's almost one and the same the flashing of the system image.
2. I'll edit the OP; thanks for the tip
Cheers..
Click to expand...
Click to collapse
please give me step by step instructions to revert back to stock, how to use mfastboot

Please tell me how to convert moto g gpe 5.1 to moto g xt1033 5.1 falcon asia retail dual sim

@siddharthnair96...hey I am having xt1033 Indian version.... It is running on cm13 (lollipop bootloader)...now i want to convert it to gpe to flash miui 7 ROM.....I should not flash KitKat bootloader right ??? Can u tell plz me exact commands to run by skipping bootloader.....

Bricked phone trying to root, now unable to flash stock rom

So I successfully installed TWRP recovery.
I then tried to flash SuperSU, but that gave me a boot loop, so I wanted to try and flash the stock rom again.
I wiped my phone with TWRP.
I wasn't totally sure what the correct version of the ROM was to download. I can't check because the phone is already wiped. It's a UK Moto X Play "lux XT1562 16GB P2C" single sim slot. I had installed an OTA update yesterday. I downloaded XT1562_LUX_RETEU_6.0.1_MPD24.107-52.xml.zip, would that be the correct version? Is there any way to know for sure?
So when I tried to flash the stock rom I ran into problems.
I ran "fastboot flash partition gpt.bin" and I got "(bootloader) Preflash validation failed".
I saw someone say that this could be because you need to flash the correct version of the bootloader first, so I did "fastboot flash bootloader bootloader.img" which was successful, but even after restarting "fastboot flash partition gpt.bin" still failed.
I'm really confused as to what I'm doing wrong. Am I having problems because I'm trying to flash the wrong version of the bootloader, or a version older then that which I had on my phone before wiping? Is this the kind of error you'd get if you were trying to downgrade, or should that work fine?
Help greatly appreciated!
Edit: Should I possibly try flashing 5.1.1 X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip or is flashing an older version a bad idea?

Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen

tavares_one said:
Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen
Click to expand...
Click to collapse
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
It fails when I try and flash gpt.bin
Code:
❯ fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.143s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.740s
and on the bootloader logs is says
Code:
cmd: getvar:partition-type:partition
cmd: getvar:max-download-size
cmd: download 00008000
cmd: flash:partition
version downgraded for primary_gpt

johtso said:
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
Click to expand...
Click to collapse
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Dio-Genes said:
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
Click to expand...
Click to collapse
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.

johtso said:
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.
Click to expand...
Click to collapse
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot

fablebreton said:
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
...
Click to expand...
Click to collapse
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s

johtso said:
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s
Click to expand...
Click to collapse
Your bootloader is unlocked ?

fablebreton said:
Your bootloader is unlocked ?
Click to expand...
Click to collapse
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"

johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.

johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
if impossible with stock and if Twrp ok why not flash a custom rom

minimale_ldz said:
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.
Click to expand...
Click to collapse
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU

johtso said:
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU
Click to expand...
Click to collapse
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says

minimale_ldz said:
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says
Click to expand...
Click to collapse
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Edit: It worked! You're an absolute life saver! So confusing that those two ROM are named so similarly..

johtso said:
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Click to expand...
Click to collapse
No idea what it means, but both your getvar info and linked firmware are MPDS. Anyway - good luck.

need help relocking bootloader

sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks

millede74 said:
sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
Click to expand...
Click to collapse
You can script them if you know how to make one. Otherwise enter them one at a time. You only need to flash this once so if you do them once each it doesn't take a long time.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
then
Code:
fastboot oem lock
you may have to repeat this last lock command until it works. I had to do it 4-5 times.

I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?

millede74 said:
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
Click to expand...
Click to collapse
fastboot needs to be in the folder with the 29.114-16-7-2 files.

Thanks

Note that you need to run the fastboot oem lock command a few times in the beginning (before you flash) and after you flash a few more times for this to completely work!

Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong

millede74 said:
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
Click to expand...
Click to collapse
Do them one at a time and post the results of each command here so we can see.

Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?

millede74 said:
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
Click to expand...
Click to collapse
It does the same thing as the commands above. The process is just automated.

This is what i get when running
ptn107 said:
It does the same thing as the commands above. The process is just automated.
Click to expand...
Click to collapse
C:\ProgramData\LMSA\Download\RomFiles>fastboot dev
ZY225FR3QL fastboot
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
mmand erases all user data.
(bootloader) Please re-run this command to continu
OKAY [ 0.014s]
Finished. Total time: 0.020s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
oid images now
(bootloader) Then re-run this command to lock
OKAY [ 0.018s]
Finished. Total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.008s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.010s]
Finished. Total time: 0.016s
C:\ProgramData\LMSA\Download\RomFiles>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.006s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem fb_mode_set
OKAY [ 0.005s]
Finished. Total time: 0.011s
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash partition gpt.bin
fastboot: error: cannot load 'gpt.bin': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash bootloader bootloader.img
fastboot: error: cannot load 'bootloader.img': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash modem NON-HLOS.bin
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash fsg fsg.mbn
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>

Correct me if I'm wrong but doesn't lmsa download the firmware as a zip file in C:\ProgramData\LMSA\Download\RomFiles ? If that's the case you need to make sure the files are extracted before running commands.

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?