Database Users

[Q] Moto G XT1068 Sem Wi-fi

Hello, good day forum guys.
I come here to present a certain problem happened to my device as they do not know if with some of you also hear this case.
First I went here on the site in search of updating the xt1068 for android version 5.0 lollipop found him this link http://forum.xda-developers.com/moto-g-2014/development/xt1068-lollipop-dual-sim -t2938439
I made the correct procedure as well as the tutorial says downloaded the rom RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC
Installed with this procedure
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 NON-HLOS.bin modem
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
Waited for him to call, but rather called as the rom is the xt1064 appeared only a chip but everything perfect, then I downloaded the update with the fix to work both supdate-nofsg-working.zip chip - https://drive.google. with / open? id = 0B3 ... eG8 & authuser = 0
And installed the [Recovery] [Titan] TWRP 2.8.0.1 is Moto G 2014 to install the update done so I ended up not liking it had many bugs, I have tried several times to return to the previous version of 4.4.4 but could not because of these errors
In cell dizversion downgraded for primary gpt *
already on the PC it here target max-sparse-size: 256MB
sending 'partition' (32 KB) ...
OKAY [0.078s]
writing 'partition' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.390s *
But I managed to come back with one backup I had my rom was just not as before, because I can no longer install any rom update over it by the CMD command promp.
Soon after I installed this rom http://www.htcmania.com/showthread.php?t=914821
sure it is from another forum but need your help after I installed this rom already with the above problems my device was not taking no chip was saying he was no chip, I ended up doing something I ended up doing work after you install these versions of xt1068 by CMD RETAILDSDSALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC_SVC.xml
* RETAILDSDSALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml
RETBR_XT1068_4.4.4_KXB21.85-18_cid12_CFC.xml
RETGBALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml
I tried all these versions give the chip but ended up working for my surprise the WiFi did not want to turn on, already changed the kernel but nothing worked if anyone can help me I will be very grateful because I do not want to take guarantee for surely I already lost it .

reflash your modem and fsg files...from dsds firmwares

[ QUOTE = k2wl ; 57107527 ] reflash your modem and fsg files ... from dsds firmware [ / QUOTE]
Not found in the firmware that modem not only that comes when I draw these are
boot
flashfile
fsg
gpt when I install this appears this message D : \ Zeca Files \ Moto G 2014 \ RETGBALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml > fast
boot flash motoboot motoboot.img
Reported target max download size of 536870912 bytes
sending ' motoboot ' ( 2184 KB) ...
OKAY [ 0.140s ]
writing ' motoboot ' ...
( bootloader ) Motoboot : Preflash validation is tz
( bootloader ) Preflash validation failed
FAILED (remote failure )
finished. Total time: 0.423s
soon
motoboot when I install this appears this message D : \ Zeca Files \ Moto G 2014 \ RETGBALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml > fast
boot flash motoboot motoboot.img
Reported target max download size of 536870912 bytes
sending ' motoboot ' ( 2184 KB) ...
OKAY [ 0.140s ]
writing ' motoboot ' ...
( bootloader ) Motoboot : Preflash validation is tz
( bootloader ) Preflash validation failed
FAILED (remote failure )
finished. Total time: 0.423s
NON- HLOS when I install this appears this message D : \ Zeca Files \ Moto G 2014 \ RETGBALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml > fast
boot flash motoboot motoboot.img
Reported target max download size of 536870912 bytes
sending ' motoboot ' ( 2184 KB) ...
OKAY [ 0.140s ]
writing ' motoboot ' ...
( bootloader ) Motoboot : Preflash validation is tz
( bootloader ) Preflash validation failed
FAILED (remote failure )
finished. Total time: 0.423s
recovery
servicefile
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3

[[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

Droid Turbo Downgrade 5.1 Lollipop OTA to 4.4.4 Kitkat

Hi, i know some of you are not very happy with the update, and ONLY if you took the OTA (and not flashed the full image) there is still hope for you.
im not sure if this will work, i need someone with a Droid Turbo (DT) to try.
the risk is 0, if this metod doesnt work, it will simply not flash, so no risk on it.
First you have to download the original Kitkat Firmware of Droid Turbo:
https://mega.co.nz/#!hZVThbjC!SqvNd7KYqYEvnbHRulVKJ2N9dsjMuNXpkcl1h-ENL3g
Requisites:
Android Studio or Minimal ADB and Fasboot (i personally recommend Minimal Adb and Fastboot because thats all we gonna need and its lighter than Android Studio 2 Mb vs 800Mb)
Kitkat Firmware
mFastboot (motorola Fastboot) i uploaded it for you: https://mega.co.nz/#!MVtz1DLb!CZTh_-wCl-qyta4Q0yZuPk_TB6Wq7Z4zElk6eArXrXk
Installation:
1.- Install MAaF
Install Minimal ADB and Fastboot
2.- Install mFastboot
Copy the contents of mfastboot.zip and put them on Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot)
Now you have working Fastboot AND mFastboot
3.- Copy Firmware
Copy the contents of your desired firmware to Minimal ADB and Fastboot Folder like this:
VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml
unzip and put all content of the file on the Minimal ADB and Fastboot Folder
Now you are ready to flash!
First turn off your device and Put it on fastboot mode (Power and volume down for 2 seconds with your phone off)
4.- Get Detected
type
Code:
fastboot devices
on minimal adb to see if your pc detects your phone on fastboot mode
if you get some numbers and letters like the picture you are ready to go.
if not, you are missing drivers, looks for Motorola Device Manager
5.- Install
Copy and Paste these commands on Minimal ADB and Fastboot:
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
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 system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot erase cache
mfastboot reboot
Click to expand...
Click to collapse
and thats all, as easy as copy from here and paste on cmd.
i highly recommend that you erase everything for a smoother experience, but some people want to keep all their files, so this line its optional
mfastboot erase userdata
Click to expand...
Click to collapse
and thats all, as easy as copy from here and paste on cmd.
when your phone finishes flashing just press enter to execute mfastboot reboot and you will boot kitkat again
Once again i have not tried this, the bigger risk is that you will have to flash lollipop again in case it doesnt work.
Anyone willing to try? be the first to downgrade to Kitkat!

Gonna test it out now!!
Thanks man!!!
Also below is a link for the 21.128-15_15_CFC_SVC.xml (got errors when trying to unzip your download @Jaocagomez)
http://www.rootjunkysdl.com/files/Droid%20Turbo/Firmware/VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml.zip

You are going to get a Preflash Validation failed error message from fastboot. This was attempted when people had soft bricks from sideloading the ota and there was no img available.
http://gyazo.com/c5d1be6c5a88265bf13af3cbce30ce12

I didn't side load mine, i took the OTA and as per his directions this MAY work with the OTA so it is worth a shot.
---------- Post added at 12:01 PM ---------- Previous post was at 11:24 AM ----------
{
"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"
}
There is now no hope whatsoever for those who took the OTA. I think it is time I accidentally drop my phone and call for a replacement. Although the only thing i truly wanted root for was to kill the wakelocks using amplify, greenify, and powernap. This phone still get 2days worth of battery with 5.1, just feel emasculated without root :'(

weaver11b said:
I didn't side load mine, i took the OTA and as per his directions this MAY work with the OTA so it is worth a shot.
---------- Post added at 12:01 PM ---------- Previous post was at 11:24 AM ----------
There is now no hope whatsoever for those who took the OTA. I think it is time I accidentally drop my phone and call for a replacement. Although the only thing i truly wanted root for was to kill the wakelocks using amplify, greenify, and powernap. This phone still get 2days worth of battery with 5.1, just feel emasculated without root :'(
Click to expand...
Click to collapse
what happens if you skip bootloader.img?

This happens:
C:\adb>mfastboot flash radio radio.img
target max-sparse-size: 256MB
sending 'radio' (85544 KB)...
OKAY [ 2.682s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
OKAY [ 1.734s]
finished. total time: 4.420s
C:\adb>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.786s
C:\adb>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 0.472s]
finished. total time: 0.994s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\adb>

weaver11b said:
This happens:
C:\adb>mfastboot flash radio radio.img
target max-sparse-size: 256MB
sending 'radio' (85544 KB)...
OKAY [ 2.682s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
OKAY [ 1.734s]
finished. total time: 4.420s
C:\adb>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.786s
C:\adb>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 0.472s]
finished. total time: 0.994s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\adb>
Click to expand...
Click to collapse
Looks like its not gonna work, damn

weaver11b said:
I didn't side load mine, i took the OTA and as per his directions this MAY work with the OTA so it is worth a shot.
---------- Post added at 12:01 PM ---------- Previous post was at 11:24 AM ----------
There is now no hope whatsoever for those who took the OTA. I think it is time I accidentally drop my phone and call for a replacement. Although the only thing i truly wanted root for was to kill the wakelocks using amplify, greenify, and powernap. This phone still get 2days worth of battery with 5.1, just feel emasculated without root :'(
Click to expand...
Click to collapse
Side loading the OTA zip and taking the OTA update are the samething.
There is the same amount of hope as there has always been. This method was already tried at least two weeks ago, there is nothing special about it. It is the same way you flash any motorola image from fastboot.

what about flashing kitkat with mofo?
not free but it could work

How is this any different than RootJunky's youtube method of reverting back to stock KK firmware? If you click on the VRZ_XT1254_KDF21.128-15_15_CFC.bat in the folder you download from his site file in fastboot it runs these commands which are similar to yours.
SET fastboot=fastboot.exe
%fastboot% oem fb_mode_set
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot bootloader.img
%fastboot% flash radio radio.img
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
%fastboot% flash system system.img_sparsechunk4
%fastboot% flash system system.img_sparsechunk5
%fastboot% flash system system.img_sparsechunk6
%fastboot% erase ddr
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% oem fb_mode_clear
pause
This is the standard way of reverting back to the original KK firmware and I've been able to do it from a Mofo'd CF Lollipop image fine. If you took the Lollipop OTA this method is gonna be incompatible with the updated Lollipop bootloader. You need the original KK bootloader for this to work.

sorry, dont work after flash original image brazil 5.0.2 rsdlite?

Jaocagomez said:
Looks like its not gonna work, damn
Click to expand...
Click to collapse
based on this I am closing this thread

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.

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?