Database Users

[FIRMWARE] [XT1069] [STOCK] [5.0.2] [FASTBOOT] RETBR_XT1069_5.0.2_LXB22.46-28.zip

Stock ZIP Firmware for XT1069
File: RETBR_XT1069_5.0.2_LXB22.46-28.zip​
Tested and working 100%!
Stock, retail firmware for XT1069. Android Lollipop 5.0.2.
DOWNLOAD LINK: Mega
PLEASE NOTE: Your device will be fully wiped!
Be warned and backup your data.
Proceed at your own risk! Do not blame me for bricked devices.
Instructions:
1. Download and unzip firmware file from above.
2. Download mfastboot from here and unzip in the same folder as firmware files.
3. Boot your device into bootloader and connect to computer via USB.
2. Flash firmware with fastboot. Flashing commands provided below.
ATTENTION! For Lollipop firmware, there's a 4th system.img_sparsechunk. (KitKat FW had only 3 files.)
Please see changes in flashing commands below.
Code:
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 system system.img_sparsechunk.4
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
mfastboot.exe reboot
After reboot, enjoy your fresh Lollipop.
Notes: This is the stock Motorola firmware file, for XT1069 device (only!), Android version 5.0.2 (Lollipop).
This firmware is NOT rooted.
To remove the "Unlocked Bootloader Warning", please refer to my other topic, here.
Screenshot:
{
"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"
}
Any comments, please write below.
If you like, hit THANKS button. :good:

rafaelbrunner said:
Stock ZIP Firmware for XT1069
File: RETBR_XT1069_5.0.2_LXB22.46-28.zip​
Tested and working 100%!
Stock, retail firmware for XT1069. Android Lollipop 5.0.2.
DOWNLOAD LINK: Mega
PLEASE NOTE: Your device will be fully wiped!
Be warned and backup your data.
Proceed at your own risk! Do not blame me for bricked devices.
Instructions:
1. Download and unzip firmware file from above.
2. Download mfastboot from here and unzip in the same folder as firmware files.
3. Boot your device into bootloader and connect to computer via USB.
2. Flash firmware with fastboot. Flashing commands provided below.
ATTENTION! For Lollipop firmware, there's a 4th system.img_sparsechunk. (KitKat FW had only 3 files.)
Please see changes in flashing commands below.
Code:
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 system system.img_sparsechunk.4
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
mfastboot.exe reboot
After reboot, enjoy your fresh Lollipop.
Notes: This is the stock Motorola firmware file, for XT1069 device (only!), Android version 5.0.2 (Lollipop).
This firmware is NOT rooted.
To remove the "Unlocked Bootloader Warning", please refer to my other topic, here.
Screenshot:
Any comments, please write below.
If you like, hit THANKS button. :good:
Click to expand...
Click to collapse
Friend would offer me only the file MOTOBOOT.img ???

iamDeeh said:
Friend would offer me only the file MOTOBOOT.img ???
Click to expand...
Click to collapse
If you want to update your bootlaoder .. There's a thread for that ! With all necessary links ! Refer that please

Unable to flash my xt1069
Hello , my xt1069 is stock in initial logo becouse that i follow all steps in this tutorial but when reboot nothing happens is still stock in initial logo. I hope that you help me. Sorry for my bad english

reisyreinier said:
Hello , my xt1069 is stock in initial logo becouse that i follow all steps in this tutorial but when reboot nothing happens is still stock in initial logo. I hope that you help me. Sorry for my bad english
Click to expand...
Click to collapse
This is a stock firmware so your phone should be stock after flashing.
What do you mean with "initial logo"?

reisyreinier said:
Hello , my xt1069 is stock in initial logo becouse that i follow all steps in this tutorial but when reboot nothing happens is still stock in initial logo. I hope that you help me. Sorry for my bad english
Click to expand...
Click to collapse
Do you mean Stuck at boot logo?

reefuge said:
Do you mean Stuck at boot logo?
Click to expand...
Click to collapse
Yes, that's what I meant is stuck at boot logo. I unlock the bootloader and do the process again but the result is the same. When i execute comands the phone show yellows letters, in other post i read that this is a good signal and all commands return OK but when restart still stuck at boot logo. The phone is Motorola XT1069 dual sim

Is it worth to update it from Kitkat to Lollipop? Why?

reisyreinier said:
Yes, that's what I meant is stuck at boot logo. I unlock the bootloader and do the process again but the result is the same. When i execute comands the phone show yellows letters, in other post i read that this is a good signal and all commands return OK but when restart still stuck at boot logo. The phone is Motorola XT1069 dual sim
Click to expand...
Click to collapse
have you deleted usercache and datacache once you have flashed all files BEFORE you reboot ?
put phone into ap fastboot mode and run my test -reset .bat file from the attached zip file (please unzip to pc )
choose option 5 - reset
choose option 4 - reboot
choose option 6 - exit

reefuge said:
have you deleted usercache and datacache once you have flashed all files BEFORE you reboot ?
put phone into ap fastboot mode and run my test -reset .bat file from the attached zip file (please unzip to pc )
choose option 5 - reset
choose option 4 - reboot
choose option 6 - exit
Click to expand...
Click to collapse
Yes, i delete usercache and datacache before reboot but anyway i run your script and this is the result for option 5
FACTORY RESET
ECHO is off.
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.016s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.031s]
finished. total time: 0.094s
Done!.........
Then reboot and nothing happens the phone is still stuck in boot logo.
Is there any pre-condition to run the process(i mean battery fully charged, etc)?
I ask you that becouse all commands return ok but dont do anything.
This is the log for complete process
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
OKAY [ 0.309s]
finished. total time: 0.328s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2184 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.991s]
finished. total time: 1.087s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (697 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.059s]
finished. total time: 0.131s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.362s]
writing 'boot'...
OKAY [ 0.192s]
finished. total time: 0.554s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.373s]
writing 'recovery'...
OKAY [ 0.193s]
finished. total time: 0.566s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257607 KB)...
OKAY [ 8.103s]
writing 'system'...
OKAY [ 4.578s]
finished. total time: 12.681s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (256614 KB)...
OKAY [ 8.071s]
writing 'system'...
OKAY [ 4.911s]
finished. total time: 12.982s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (259672 KB)...
OKAY [ 8.166s]
writing 'system'...
OKAY [ 4.764s]
finished. total time: 12.930s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (240897 KB)...
OKAY [ 7.581s]
writing 'system'...
OKAY [ 3.939s]
finished. total time: 11.520s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (38920 KB)...
OKAY [ 1.269s]
writing 'system'...
OKAY [ 0.658s]
finished. total time: 1.927s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49356 KB)...
OKAY [ 1.595s]
writing 'modem'...
OKAY [ 0.812s]
finished. total time: 2.406s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.059s]
finished. total time: 0.059s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1013 KB)...
OKAY [ 0.117s]
writing 'fsg'...
OKAY [ 0.046s]
finished. total time: 0.163s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.063s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.067s]
finished. total time: 0.067s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot -w
erasing 'userdata'...
OKAY [ 0.018s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.068s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.048s]
finished. total time: 0.178s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot reboot
rebooting...
finished. total time: 0.001s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$
thanks in advance for your time

reisyreinier said:
Yes, i delete usercache and datacache before reboot but anyway i run your script and this is the result for option 5
FACTORY RESET
ECHO is off.
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.016s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.031s]
finished. total time: 0.094s
Done!.........
Then reboot and nothing happens the phone is still stuck in boot logo.
Is there any pre-condition to run the process(i mean battery fully charged, etc)?
I ask you that becouse all commands return ok but dont do anything.
This is the log for complete process
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
OKAY [ 0.309s]
finished. total time: 0.328s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2184 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.991s]
finished. total time: 1.087s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (697 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.059s]
finished. total time: 0.131s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.362s]
writing 'boot'...
OKAY [ 0.192s]
finished. total time: 0.554s
[email protected]sarrollo22:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.373s]
writing 'recovery'...
OKAY [ 0.193s]
finished. total time: 0.566s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257607 KB)...
OKAY [ 8.103s]
writing 'system'...
OKAY [ 4.578s]
finished. total time: 12.681s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (256614 KB)...
OKAY [ 8.071s]
writing 'system'...
OKAY [ 4.911s]
finished. total time: 12.982s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (259672 KB)...
OKAY [ 8.166s]
writing 'system'...
OKAY [ 4.764s]
finished. total time: 12.930s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (240897 KB)...
OKAY [ 7.581s]
writing 'system'...
OKAY [ 3.939s]
finished. total time: 11.520s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (38920 KB)...
OKAY [ 1.269s]
writing 'system'...
OKAY [ 0.658s]
finished. total time: 1.927s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49356 KB)...
OKAY [ 1.595s]
writing 'modem'...
OKAY [ 0.812s]
finished. total time: 2.406s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.059s]
finished. total time: 0.059s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1013 KB)...
OKAY [ 0.117s]
writing 'fsg'...
OKAY [ 0.046s]
finished. total time: 0.163s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.063s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.067s]
finished. total time: 0.067s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot -w
erasing 'userdata'...
OKAY [ 0.018s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.068s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.048s]
finished. total time: 0.178s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot reboot
rebooting...
finished. total time: 0.001s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$
thanks in advance for your time
Click to expand...
Click to collapse
I will say the 1st boot after flashing can take 10 minutes + so it may seem stuck but isn't... have you left a good 15 to 20 minutes to pass before confirming its stuck // also you do have a xt1069 for certain?
battery must be over about 25% if I remember correctly -- think it refuses and says about battery too low in >10% in red -
I know with my xt1068 not only is there 8gb and 16gb but also early and late version (the late having a toshiba front cam) and uses LXB22-99-16 (feb 25th build) as opposed to (6th jan build) -my xt1068 can run either build as the early model
are xt1069 dual sim like xt1068 with added dtv ?

reefuge said:
I will say the 1st boot after flashing can take 10 minutes + so it may seem stuck but isn't... have you left a good 15 to 20 minutes to pass before confirming its stuck // also you do have a xt1069 for certain?
battery must be over about 25% if I remember correctly -- think it refuses and says about battery too low in >10% in red -
I know with my xt1068 not only is there 8gb and 16gb but also early and late version (the late having a toshiba front cam) and uses LXB22-99-16 (feb 25th build) as opposed to (6th jan build) -my xt1068 can run either build as the early model
are xt1069 dual sim like xt1068 with added dtv ?
Click to expand...
Click to collapse
Sorry for the delay, but I had connectivity issues
I had never waited the 10 min, so I followed your advice, but after 30 min the outcome was the same, the phone was stuck at the boot logo. Yes my phone is dual sim and supports dtv. Im very shure that i have an xt1069, my intention is upload a picture from back side of my phone(label) but i dont know how to upload a picture to here.
thanks in advance

Hey, my frontal camera dont work after installing this rom, Im sure that is the correct rom (motorola moto g DTV ), and the camera was working before.
what should i do? factory reset again??
----
edit:
i think i found the solution, so i'm just trying to use another rom instead

thalesw said:
Hey, my frontal camera dont work after installing this rom, Im sure that is the correct rom (motorola moto g DTV ), and the camera was working before.
what should i do? factory reset again??
----
edit:
i think i found the solution, so i'm just trying to use another rom instead
Click to expand...
Click to collapse
Use this later version for toshiba front cam you need this LXB22.91-16 version for xt1069 BR stock rom

I think I'm bricked. Can't seem to flash stock firmware.

C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.371s
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash bootloader bootloader.img
error: cannot load 'bootloader.img'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.103s]
writing 'logo'...
OKAY [ 0.067s]
finished. total time: 0.174s
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash boot boot.img
error: cannot load 'boot.img'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.0
error: cannot load 'system.img_sparsechunk.0'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.1
error: cannot load 'system.img_sparsechunk.1'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.2
error: cannot load 'system.img_sparsechunk.2'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.3
error: cannot load 'system.img_sparsechunk.3'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.4
error: cannot load 'system.img_sparsechunk.4'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.5
error: cannot load 'system.img_sparsechunk.5'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.6
error: cannot load 'system.img_sparsechunk.6'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.7
error: cannot load 'system.img_sparsechunk.7'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.8
error: cannot load 'system.img_sparsechunk.8'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash system system.img_sparsechunk.9
error: cannot load 'system.img_sparsechunk.9'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash modem NON-HLOS.bin
error: cannot load 'NON-HLOS.bin'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.018s
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.010s]
finished. total time: 0.016s
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1356 KB)...
OKAY [ 0.046s]
writing 'fsg'...
OKAY [ 0.046s]
finished. total time: 0.098s
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin'
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot erase cache
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.021s
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.172s]
finished. total time: 0.175s
C:\Users\\Downloads\Blur_Version.23.21.18.clark_retus.retus.en.US>fastboot reboot
I've reinstalled fastboot drivers. My phone won't boot up. It shows the "bootloader is unlocked" screen, the shows the "M" Motorola logo, then goes black.
I fortunately have a backup phone, but I am not getting anywhere.
Any help is appreciated.

can you do a "fastboot getvar-all" ?
And is your bootloader unlocked?

Try renaming that long filename.
Try not using a script to flash.

this for you
http://forum.xda-developers.com/moto-x-style/help/guide-motorola-moto-x-purestyle-xt1575-t3348673

need the stock fastboot rom for the build npjs 25.93-14.4, (March security patch)

In need of the full stock firmware for the latest build NPJS 25.93-14.4(march security patch) with the bootloader relocking ability, just like the link below for the build NPJ25-93-14 as it won't allow me downgrade and relock the bootloader anymore:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
In need for relocking the bootloader as I need to try my luck with the service center for the screen burn issue.
Any help would be really appreciated.
Much thanks in advance.

You can relock using the same procedure, input those lines in cmd window, while phone is in fastboot mode:
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
Note that the first two lines HAVE to be repeated like that.

C:\mfastboot>mfastboot oem lock begin
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.004s]
finished. total time: 0.005s
C:\mfastboot>fastboot oem lock begin
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.016s]
finished. total time: 0.017s
C:\mfastboot>fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.006s]
finished. total time: 0.007s

it says still still require signed boot.img

I thought that you are on the STOCK build 25-93-14-4?
You can't go back to 25.93-14.4?

SoNic67 said:
I thought that you are on the STOCK build 25-93-14-4?
You can't go back to 25.93-14.4?
Click to expand...
Click to collapse
I'm on NPJS 25.93.14.4, i'll just downgrade to 25-93-14 and check with the commands provided.
Btw, thank you and sorry as I'm a noob and bothering you again and again.

just one thing, I'll be using the following commnads:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.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 flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
for downgrading to 93-14.
That would be fine right?

Yeah, fastboot or mfastboot are equal. It's a batch file in that zip file that does the locking automatically:
Code:
mfastboot oem lock begin
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.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 flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem lock
mfastboot reboot

C:\mfastboot>mfastboot oem lock begin
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.004s]
finished. total time: 0.005s
C:\mfastboot>mfastboot oem lock begin
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.011s]
finished. total time: 0.012s
C:\mfastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.043s
C:\mfastboot>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (3651 KB)...
OKAY [ 0.153s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(bootloader) committing: bootloader.default.xml ...
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.433s]
finished. total time: 0.589s
C:\mfastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (2105 KB)...
OKAY [ 0.084s]
writing 'logo'...
OKAY [ 0.055s]
finished. total time: 0.142s
C:\mfastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.653s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.821s
C:\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16484 KB)...
OKAY [ 0.649s]
writing 'recovery'...
(bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.819s
C:\mfastboot>mfastboot flash dsp adspso.bin
target max-sparse-size: 256MB
sending 'dsp' (16384 KB)...
OKAY [ 0.648s]
writing 'dsp'...
OKAY [ 0.242s]
finished. total time: 0.894s
C:\mfastboot>mfastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (96490 KB)...
OKAY [ 3.744s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.804s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (261001 KB)...
OKAY [ 10.083s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.149s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (250858 KB)...
OKAY [ 9.720s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.749s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (254625 KB)...
OKAY [ 9.288s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.317s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (261577 KB)...
OKAY [ 9.615s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.636s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (260443 KB)...
OKAY [ 9.842s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.880s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (248842 KB)...
OKAY [ 9.306s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.332s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (259549 KB)...
OKAY [ 9.799s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.843s
C:\mfastboot>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (82497 KB)...
OKAY [ 3.210s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.229s
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (76954 KB)...
OKAY [ 3.005s]
writing 'modem'...
OKAY [ 1.133s]
finished. total time: 4.142s
C:\mfastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.030s]
finished. total time: 0.031s
C:\mfastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.023s
C:\mfastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (2040 KB)...
OKAY [ 0.084s]
writing 'fsg'...
OKAY [ 0.064s]
finished. total time: 0.151s
C:\mfastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.021s]
finished. total time: 0.023s
C:\mfastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 1.322s]
finished. total time: 1.352s
C:\mfastboot>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\mfastboot>mfastboot erase clogo
erasing 'clogo'...
OKAY [ 0.017s]
finished. total time: 0.019s
C:\mfastboot>mfastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.004s]
finished. total time: 0.006s
C:\mfastboot>mfastboot reboot

SoNic67 said:
You can relock using the same procedure, input those lines in cmd window, while phone is in fastboot mode:
Note that the first two lines HAVE to be repeated like that.
Click to expand...
Click to collapse
He just can't. Motorola is a BI***, now bootloader is asking for signed boot.img, next it will ask for signed oem.img and/or system.img (it actually mandates both, but it won't tell you right straight) after that it might please to let him relock the bootloader. All of those signed images must match the gpt.bin version (i.e: NPJ.25.93-14.4)
I'm a noob, so not sure why people wonder this happens, but it sure does.
I'm very interested as well because I have another issue that can't be solved except with the requested ROM: CID = 0xDEAD, bootloader says "oem_locked" while it is not and not one type of boot is possible (that was my fault writing inconsistent dd images to phone)
Anyway, he is right, and his problem won't go away unless he gets what he stated in his very first post.

MK+2017 said:
He just can't. Motorola is a BI***, now bootloader is asking for signed boot.img, next it will ask for signed oem.img and/or system.img (it actually mandates both, but it won't tell you right straight) after that it might please to let him relock the bootloader. All of those signed images must match the gpt.bin version (i.e: NPJ.25.93-14.4)
I'm a noob, so not sure why people wonder this happens, but it sure does.
I'm very interested as well because I have another issue that can't be solved except with the requested ROM: CID = 0xDEAD, bootloader says "oem_locked" while it is not and not one type of boot is possible (that was my fault writing inconsistent dd images to phone)
Anyway, he is right, and his problem won't go away unless he gets what he stated in his very first post.
Click to expand...
Click to collapse
yupp, i too think that the bootloader can only be relocked if the latest official firmware with the latest security patch is flashed via fastboot.
If possible can anyone please provide the latest firmware for xt1643 with the march sec. patch?

I have assumed that he has just installed the update and didn't change anything in the system.

i am on stock 93-14 build, dec sec. patch. Now should i have to wait for the march firmware to be posted or is there anything else that i can still do to lock the bootloader?

Once you flash an official OTA, you cannot downgrade the bootloader and partition table to a previous version. And locking the bootloader will need the latest fastboot firmware. Also, please consider using something like pastebin or hastebin for such long logs/outputs.

that is what i need, is it possible to create the new firmware using the latest ota file?

That's I haven't updated to 93-14-4 build cause you never know what goes wrong with your phone BTW way you can temporarily fix the screen burn issue by changing the RGB values using kernel auditor or ex kernel manager
Sent from my Moto G4 Plus using Tapatalk

yupp, i am using the bluelight filter for the time being

Same thing here, guess we have to wait for official and complete firmware... -_-

yupp, waiting for the same

Good Ness e
https://forum.xda-developers.com/mo...rom-npjs25-93-14-4-march-1-t3608138?nocache=1

Moto X Play XT1562 Having Network Problem (NO SIGNAL)

Please suggest me what i do ? i am not having network in my moto x play xt1562 from yesterday, i tried to turn off/on aeroplan mode and change SIM card but even then no signal, sim card working fine in other mobile.
i also tried to select network manually , and switch from 4g lte to 3g or 2g but not working.

Do you have IMEI?

Issued Solved
ziom5510 said:
Do you have IMEI?
Click to expand...
Click to collapse
I have solved the issue, not its 6.0, but got update of 7.1.1, NOW ITS Not comming

Hi. M having same problem in my x play what to do
Should I roll back to marshmallow
Plz provide twrp flasable room of lollipop or marshmallow
Vodafone slot2 - 358967063233173
Jio slot1 - 358967063233165

even i am having the same issue

Moto x play . No service status
Unable to register on network . Signal comes goes .
In low
Coverage area unable to register ..
Device is nougat version.
What to sumbody help me ..

techeligible3322 said:
Please suggest me what i do ? i am not having network in my moto x play xt1562 from yesterday, i tried to turn off/on aeroplan mode and change SIM card but even then no signal, sim card working fine in other mobile.
i also tried to select network manually , and switch from 4g lte to 3g or 2g but not working.
Click to expand...
Click to collapse
Facing same issue.. sim1jio4g.. and sim2airtel
Tried different sim. But problem persists.. moto xplay india android nougat
---------- Post added at 05:02 AM ---------- Previous post was at 04:58 AM ----------
Sim1jio sim2airtel.. tried sim change
Changed sim slot, tried netwrok reset, and factory reset too
Problem still persists
Moto xplay india
Nougat android ( ota ver.)

techeligible3322 said:
Hey i have foxed this issue, before i was having this issue, just go to google, and type there
" moto x play network issue techeligible ". Open that site and follow all steps from there
Click to expand...
Click to collapse
Thanks alot ,brother. Hope there will b a permanent solution for this problem
---------- Post added at 04:21 PM ---------- Previous post was at 04:01 PM ----------
Is there any permanent solution via root(i.e. on rooted moto xplay. Apps/mods o)

shivm500 said:
Thanks alot ,brother. Hope there will b a permanent solution for this problem
---------- Post added at 04:21 PM ---------- Previous post was at 04:01 PM ----------
Is there any permanent solution via root(i.e. on rooted moto xplay. Apps/mods o)
Click to expand...
Click to collapse
Try this one first then let me know

techeligible3322 said:
Try this one first then let me know
Click to expand...
Click to collapse
Thought it worked but itsnt . Both netwrks emergency calls only

shivm500 said:
Thought it worked but itsnt . Both netwrks emergency calls only
Click to expand...
Click to collapse
Did u reboot in fastboot ? And then download adb bypass tool in computer?

techeligible3322 said:
Did u reboot in fastboot ? And then download adb bypass tool in computer?
Click to expand...
Click to collapse
I followed the whole process via adb and the commands ..
Network just keep on droping and most of the time its emergency calls only..

shivm500 said:
I followed the whole process via adb and the commands ..
Network just keep on droping and most of the time its emergency calls only..[/QUOTE
Ah, that actually worked fine with me when i use commands okay, dis you also download firmware ??? I guess i downloaded 1gb file
Click to expand...
Click to collapse

techeligible3322 said:
shivm500 said:
I followed the whole process via adb and the commands ..
Network just keep on droping and most of the time its emergency calls only..[/QUOTE
Ah, that actually worked fine with me when i use commands okay, dis you also download firmware ??? I guess i downloaded 1gb file
Click to expand...
Click to collapse
I did adb fastboot
Nd thay commands
Dont know about firmware
Pls guide
(Iam on nougat)
Click to expand...
Click to collapse

Ok today i will search that firmware as well ok

Download Firmware
shivm500 said:
techeligible3322 said:
I did adb fastboot
Nd thay commands
Dont know about firmware
Pls guide
(Iam on nougat)
Click to expand...
Click to collapse
Go to Device Settings > About > check what's written with "BUILD NUMBER", mine is MPDS24-11..., this is to make sure you are downloading right firmware from below site. just match detail with build number firmware.
You can download your device Android 7.1 Firmware from below link
https://github.com/motoxplay/stock
-after downloading finish, just flash your device with this firmware.
Flash With Firmware:
-Extract the downloaded firmware to somewhere you can use adb.exe.
-Reboot device in "Bootloader Mode" by pressing "Volume Down + Power Key".
-Copy and past "ADB Commands Prompt" where you have "Downloaded extracted firmware".
-Press "Control + Shift + Mouse Right click", then open "Windows Command Prompt here".
-Connect device to computer.
Note: Make sure, "Moto X Play Firmare", and "ADB" both are in same folder.
Copy & Past below commands in to adb command prompt window, to flash with firmware:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash 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 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
Best of luck
Click to expand...
Click to collapse

After flash with firmware, soft reset your device and then I hope this would fix your network issue

thnx

shivm500 said:
techeligible3322 said:
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
D:\New folder>adb reboot bootloader
D:\New folder>fastboot oem fb_mode_set
...
OKAY [ 0.009s]
finished. total time: 0.009s
D:\New folder>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.803s]
finished. total time: 0.811s
D:\New folder>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.093s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.796s]
finished. total time: 1.891s
D:\New folder>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (3080 KB)...
OKAY [ 0.109s]
writing 'logo'...
OKAY [ 0.151s]
finished. total time: 0.261s
D:\New folder>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.188s]
writing 'boot'...
OKAY [ 1.388s]
finished. total time: 2.579s
D:\New folder>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32752 KB)...
OKAY [ 1.174s]
writing 'recovery'...
OKAY [ 1.397s]
finished. total time: 2.572s
D:\New folder>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (255439 KB)...
OKAY [ 8.619s]
writing 'system'...
OKAY [ 9.509s]
finished. total time: 18.129s
D:\New folder>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (261106 KB)...
OKAY [ 8.810s]
writing 'system'...
OKAY [ 7.097s]
finished. total time: 15.908s
D:\New folder>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (248342 KB)...
OKAY [ 8.364s]
writing 'system'...
OKAY [ 8.959s]
finished. total time: 17.323s
D:\New folder>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (257578 KB)...
OKAY [ 8.682s]
writing 'system'...
OKAY [ 10.331s]
finished. total time: 19.012s
D:\New folder>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (254106 KB)...
OKAY [ 8.567s]
writing 'system'...
OKAY [ 6.541s]
finished. total time: 15.107s
D:\New folder>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (262050 KB)...
OKAY [ 8.822s]
writing 'system'...
OKAY [ 7.905s]
finished. total time: 16.727s
D:\New folder>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (236003 KB)...
OKAY [ 7.942s]
writing 'system'...
OKAY [ 9.900s]
finished. total time: 17.842s
D:\New folder>fastboot flash system system.img_sparsechunk.7
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.7': No error
D:\New folder>fastboot flash system system.img_sparsechunk.7
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.7': No error
D:\New folder>fastboot flash system system.img_sparsechunk.7
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.7': No error
D:\New folder>fastboot flash system system.img_sparsechunk.8
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.8': No error
D:\New folder>fastboot flash system system.img_sparsechunk.9
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk.9': No error
D:\New folder>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (37377 KB)...
OKAY [ 1.260s]
writing 'modem'...
OKAY [ 0.703s]
finished. total time: 1.963s
D:\New folder>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
D:\New folder>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
D:\New folder>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (1314 KB)...
OKAY [ 0.062s]
writing 'fsg'...
OKAY [ 0.047s]
finished. total time: 0.109s
D:\New folder>fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
D:\New folder>fastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
D:\New folder>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.031s
D:\New folder>fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.016s
D:\New folder>fastboot reboot
rebooting...
finished. total time: -0.000s
Click to expand...
Click to collapse
after 6 the 7th 8th and 9th sparse chunk
didnt happened
Click to expand...
Click to collapse

shivm500 said:
shivm500 said:
after 6 the 7th 8th and 9th sparse chunk
didnt happened
Click to expand...
Click to collapse
hey no problem, I also did same like this and got failed but even then after I reboot my device in bootloader, and then again restart my drive normal after I got my Singal issue solved
Click to expand...
Click to collapse

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?