Database Develop

[Q] [HELP] XT1068 with CM12-Titan-Unofficial. Touch screen dead

I recently bought the phone specifically to install mods and to understand more about the hardware. So I'm an absolute noob but hopefully not too dumb to follow simple instructions.
I installed the cm-12-20150304-UNOFFICIAL-titan image and things were (mostly) good.
Today I saw for the first time that the phone had detected an UPDATE. It was marked NIGHTLY but I had seen other new images on the web site that didn't appear as updates so I decided to try it. The update was downloaded and then I booted into TWRP (2.8.4) to install it.
On reboot I discovered that the touchscreen didn't work any more - no response to any contact.
I booted into TWRP and found that was affected in the same way.
I attempted to use 'fastboot' to flash a clean copy of TWRP:
--> fastboot flash recovery openrecovery-twrp-2.8.4.0-titan.img
as the start of escaping from this but I keep getting a 'Mismatched partition size (recovery)'
Then I tried just booting the recovery image:
--> fastboot boot openrecovery-twrp-2.8.4.0-titan.img
But when TWRP starts up the screen still doesn't respond.
I've tried wiping the device:
--> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.268s]
erasing 'cache'...
OKAY [ 0.082s]
finished. total time: 0.352s
and I've tried flashing a stock firmware.
--> fastboot update RETDEALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC.xml.zip
4.4.4_KXB21.85-14_cid7_CFC.xml.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
And now I am at a loss. I've exhausted my knowledge and creativity (for now) but I don't want to make things worse (if possible) through ignorance.
Is the phone 'dead'?

i have the same issue with my moto g, i've ran out of ideas for a while but im still looking for an answer so if you happen to find out whats wrong let me know!

If I find anything I will but I suspect we both have dead phones - spares rather than repair .
I tried resolving the 'Mismatch partition size' by formatting the 'recovery' partition but I just get 'cannot format partition of type raw'. My suspicion is that the partitioning/formatting of the internal memory is completely corrupted but it doesn't show up as a storage device when I connect it to my computer anymore and I can't get ADB running so I can't get any more information or anyway to zap it back to base settings so I think it may be a lost cause.
On the other hand even if the partitioning/formatting is all gone to pot the phone is, somehow, finding enough of TWRP to get the initial screen loaded - where is it finding that?
I also don't understand why 'fastboot boot TWRP.img' doesn't work because that should bypass the internal storage and go straight to RAM. That makes me worry that 'somehow' the update has screwed the screen hardware even though I find that hard to believe.
Well, as I said I bought the phone for a learning experience and I've certainly had that.

Same here (XT1068). After bootloader update and nightly installation touchscreen is dead. Its also dead after rebooting to recobery.

Ended up by restoring to factory: http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
Everything is working again after several boots.

How?
modules said:
Ended up by restoring to factory: http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
Everything is working again after several boots.
Click to expand...
Click to collapse
Exactly how did you do this? Every attempt I have made to flash the phone has failed.
Never mind, I thought you were just pointing me at firmware files. I followed the link and tried the tool but same problem.
It really doesn't like writing the partition information
Thanks for the brief hope though..

jmangan said:
Exactly how did you do this? Every attempt I have made to flash the phone has failed.
Never mind, I thought you were just pointing me at firmware files. I followed the link and tried the tool but same problem.
It really doesn't like writing the partition information
Thanks for the brief hope though..
Click to expand...
Click to collapse
I read your first post.. You did not install the stock firmware correctly! You have to extract the stock firmware zip file and flash each and every file with separate commands!
Sent from my Moto G 2014

Not really the problem
pranshubatra707 said:
I read your first post.. You did not install the stock firmware correctly! You have to extract the stock firmware zip file and flash each and every file with separate commands!
Sent from my Moto G 2014
Click to expand...
Click to collapse
Yeah, that was my earliest efforts. I corrected that and I got the same result doing it manually as I got using the automated tool above:
Restore to Stock Android 5.0.2 for Motorola Moto G 2014 (XT1068)
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.054s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.116s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.154s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.060s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.101s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.445s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.494s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.454s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.476s
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 10.393s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.420s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 10.623s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.742s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 10.549s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.596s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 9.315s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 9.375s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 2.494s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 2.594s
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.024s
erasing 'modemst2'...
OKAY [ 0.078s]
finished. total time: 0.079s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.117s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.174s
erasing 'cache'...
OKAY [ 0.104s]
finished. total time: 0.109s
erasing 'userdata'...
OKAY [ 0.246s]
finished. total time: 0.248s
rebooting...
finished. total time: 0.002s
Press any key to exit
There is a definite problem with the formatting/partitioning of the built in storage. I can't load ADB because the screen doesn't respond and normal flashing produces the results above. (Ignore the battery low message; it's been on charge for four hours but isn't updating the values although it shows as charging).
Thanks for contributing though.

jmangan said:
Yeah, that was my earliest efforts. I corrected that and I got the same result doing it manually as I got using the automated tool above:
Thanks for contributing though.
Click to expand...
Click to collapse
You are trying to restore to stock android lollipop? Did you receive the official android update or not? If not then your bootloader isn't updated to lollipop bootloader.. Try downloading factory image of kitkat for your device and then try restoring it maybe?
Try this
http://forum.xda-developers.com/showthread.php?p=55373304
Sent from my Moto G 2014 using XDA Free mobile app

jmangan said:
Yeah, that was my earliest efforts. I corrected that and I got the same result doing it manually as I got using the automated tool above:
Restore to Stock Android 5.0.2 for Motorola Moto G 2014 (XT1068)
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.054s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.116s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.154s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.060s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.101s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.445s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.494s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.454s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.476s
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 10.393s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.420s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 10.623s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.742s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 10.549s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.596s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 9.315s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 9.375s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 2.494s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 2.594s
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.024s
erasing 'modemst2'...
OKAY [ 0.078s]
finished. total time: 0.079s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.117s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.174s
erasing 'cache'...
OKAY [ 0.104s]
finished. total time: 0.109s
erasing 'userdata'...
OKAY [ 0.246s]
finished. total time: 0.248s
rebooting...
finished. total time: 0.002s
Press any key to exit
There is a definite problem with the formatting/partitioning of the built in storage. I can't load ADB because the screen doesn't respond and normal flashing produces the results above. (Ignore the battery low message; it's been on charge for four hours but isn't updating the values although it shows as charging).
Thanks for contributing though.
Click to expand...
Click to collapse
are you kidding? look at your log dude!
its saying failed because of low battery. just charge it up full and try again

ggunzio said:
are you kidding? look at your log dude!
its saying failed because of low battery. just charge it up full and try again
Click to expand...
Click to collapse
He stated already that the device has been on charge for 4hrs.
Sent from my Moto G 2014

Giving up
pranshubatra707 said:
He stated already that the device has been on charge for 4hrs.
Sent from my Moto G 2014
Click to expand...
Click to collapse
Thanks, pranshubatra707, saved me pointing it out.
Well, since I can no longer see the internal storage when the phone is connected in windows, and since I can't format it with fastboot (type of 'raw' not supported) I thought maybe parted might be able to help so I plugged it into a Linux machine but parted doesn't see the storage device either.
It could be that with the various fixes MTP has been turned off/damaged (but when I had an external SD car installed Windows could still see that). But I think that's it, last throw of the dice. The partitions are gone/unrecognised. There appears to be no way to re-create/restore them and without them flashing A:WAYS fails.
I was also tempted to try booting linux on a USB stick but I doubt that the phone will boot off USB so that seems like just a waste of time - unless anyone knows better?
Thanks for the suggestions but I'm facing up to a dead phone.

My touchscreen just went non responding after installing a cm12 based rom.. I erased userdata, system and cache via bootloader with fastboot commands and restored my phone to stock kitkat.. I even restored recovery.. Then touchscreen went working again!
Sent from my XT1068

Well i'm facing the same problem after flashing some CM 12 based roms which need lollipop bootloader.
If someone has a solution for the problem please tell us.

stefan230 said:
Well i'm facing the same problem after flashing some CM 12 based roms which need lollipop bootloader.
If someone has a solution for the problem please tell us.
Click to expand...
Click to collapse
You have to update your bootloader before flashing cm12 roms
Sent from my XT1068

pranshubatra707 said:
You have to update your bootloader before flashing cm12 roms
Sent from my XT1068
Click to expand...
Click to collapse
I flashed lollipop bootloader before of course. The Rom I installed were the latest CM 12 nightly bulid and the latest Team UB build, which both need lollipop bootloader to boot.
My problem is that if the rom is booted the touch screen does not respond any more. Even if I try to restore a backup using TWRP 2.8.6.0 the touch screen does not respomd either.

​
pranshubatra707 said:
You have to update your bootloader before flashing cm12 roms
Sent from my XT1068
Click to expand...
Click to collapse
that's BS, I've updated my bootloader and the ROM (CM12 official) didn't even boot, and touchscreen wasn't working in recovery
I just flashed stock KK which is what I'm running now

My friend is having this problem with his XT1068 too. He's stuck in KitKat:
If he flashes CM12, the touchscreen won't work. CM will boot as usual, and TWRP too, but the touchscreen won't work on neither. The ROM was flashed with a Lollipop bootloader so that's not the problem.
He's on stock KitKat by following this tutorial. But when he downloads the Lollipop OTA, it won't install in the stock recovery, giving an error. Thus, he's stuck on KK.
Any ideas? Many thanks in advance!

Hi,
I posted already on antoher thread (microkat) but was sent away to supposedly here
I've got the same issue, but my history was CM12->wipe+install Titan Z-> wipe+install Microkat-> restore CM12.
Using the link to restore the device
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
you may be able to get it up and running again. This works as well with the Linux fastboot.
What I was able to discover during the troubleshooting was the output of getvar in the error case:
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.4/KXB21.85-14/9:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.14.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-pINKman-kk4.4 (sluk
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.7 (GCC) ) #15021
(bootloader) kernel.version[2]: 9 SMP PREEMPT Thu Feb 19 15:31:25 CET 20
(bootloader) kernel.version[3]: 15
The pinkman kernel is actually related to microkat. But whatever I flashed, boot, motoboot, recovery, the output remained the same. A friend came to the idea to flash the system as well, as in the link. The output is now:
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3112.96.00R EMEA_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-ge35b7bb-00001-gf6a
(bootloader) kernel.version[1]: 3942 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Wed Feb 25 01:
(bootloader) kernel.version[3]: 09:46 CST 2015
Also the baseband got a value again. I will continue in the next days.

Hi, I know this thread is quite old, but I ran into the same problem.
Actually I bought the phone used and it arrived like this :/
Can any of you guys help?
If I try "mfastboot format motoboot" it tells me that raw filesystem ist not supported.
The firmware restore batchfile gives me this output:
mfastboot output said:
D:\My Stuff\Downloads\motog\Moto G 2014 [XT1068] Restore to Android 5.0.2 (22.99
.16)>"Auto Restore Script.bat"
Restore to Stock Android 5.0.2 for Motorola Moto G 2014 (XT1068)
error: device not found
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
OKAY [ 0.331s]
finished. total time: 0.369s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash rpm
FAILED (remote failure)
finished. total time: 100.227s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.040s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 20.005s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.341s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.745s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.354s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.764s
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 13.128s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 26.701s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 13.005s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.330s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 13.183s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.525s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 13.031s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.874s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 6.051s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.483s
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 6.580s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.618s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.992s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.994s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.079s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.114s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
rebooting...
Click to expand...
Click to collapse
Device Info said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4882(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D22FVX2
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: A5E6C5060F000000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "flashfail" configured as fastboot
(bootloader) imei: 35xxxxxxxxxx
(bootloader) meid:
(bootloader) date: 10-17-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Dec 20 17:54:23 UTC 1969"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.46-28/28:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.28.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3105.93.00R EMEA_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:38:33 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.82-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.82-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.82-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.83-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D22FVX2
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.073s
Click to expand...
Click to collapse
I was also wondering what this means:
"(bootloader) reason: UTAG "flashfail" configured as fastboot"
I appreciate any hint.

XT1072 - Unable To Install Stock OS

Hello everbody
A a year ago I tried to install a stock rom on my XT1072, but accidentally used an XT1068 rom. When I used "mfastboot getvar all" my phone got recognized as a TITAN instead of a THEA. I managed to install Lineage, but now my phone is stuck and restarts after a few seconds while showing the "Warning Bootloader Unlocked" message.
I tried to flash the latest version of Lineage "lineage-14.1-20170728-nightly-thea" but it failed and the screen displayed the following message.
Updater process ended with ERROR: 7
Erorr installing Zip file 'sdcard1/lineage-14.1-20170728-nightly-thea-signed.zip'
Updating partition details. . .
Failed to mount '/data' (Invalid argument
. . .done
I googled this error and it appears that my device is incompatible with the OS. I think it's because of the mismatching info I highlighted in the seconds hidden part.
After this, I tried to install this (https://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075) stock rom, but most of the commands failed
C:\XT1072 - 6.0 Stock Rom>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.040s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.381s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
error: cannot load 'bootloader.img': No error
C:\XT1072 - 6.0 Stock Rom>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.074s]
writing 'logo'...
OKAY [ 0.111s]
finished. total time: 0.196s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.402s]
writing 'boot'...
OKAY [ 0.389s]
finished. total time: 0.800s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.397s]
writing 'recovery'...
OKAY [ 0.403s]
finished. total time: 0.809s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256869 KB)...
OKAY [ 13.664s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.789s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257163 KB)...
OKAY [ 11.165s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.290s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (261045 KB)...
OKAY [ 13.967s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 14.045s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (248543 KB)...
OKAY [ 13.439s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.501s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (83796 KB)...
OKAY [ 4.510s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.541s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60992 KB)...
OKAY [ 2.558s]
writing 'modem'...
OKAY [ 2.070s]
finished. total time: 4.637s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.026s]
finished. total time: 0.029s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.024s]
finished. total time: 0.027s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (320 KB)...
OKAY [ 0.107s]
writing 'fsg'...
OKAY [ 0.100s]
finished. total time: 0.213s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.166s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.108s]
finished. total time: 1.281s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.139s]
finished. total time: 0.142s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.463s]
finished. total time: 0.465s
All of the system.img_sparsechunk failed with an "Image is too large" message and gpt.bin failed with "version downgraded for primary_gpt". After this I did "mfastboot getvar all" after I noticed that the bootloader version changed from 48.21 to 48.22. The phone is now recognized as a THEA again, but some parts are still labeled TITAN instead of THEA
C:\XT1072 - 6.0 Stock Rom>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4822
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB ID=15 REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C22D9DG
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid: DDF97E0215000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 353310062384405
(bootloader) meid:
(bootloader) date: 07-03-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Aug 23 22:51:53 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retde/titan_umtsds:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXB22.99-16/10:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retde
(bootloader) ro.build.version.full[1]: .retdeall.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:47:29 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.22-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.22-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.22-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.22-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.22-0-g1b80345
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C22D9DG
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
finished. total time: 0.128s
Is there any way to fix my phone and install the Stock or Lineage Rom? Thanks for all kinds of advice or suggestions

[Help - Moto X2 boot in Fastboot mode] more info. here.

Hi guys,
My Moto X2 (XT1097) not boot in normal mode (only in fast boot screen), i try flash stock rom with RSD Lite 6.2.4 with "XT1097_VICTARA_RETBR_6.0_MPES24.49-18-7_cid12_CFC.xml" but all times i get error...
Error info in fastboot sreen:
"Failed to validate system image"
"Fastboot Reason: Fail-through from normal boot mode"
if i try flash via "Moto Auto Flash Tool v7.1" i receive errors = (bootloader) Invalid signed image - (bootloader) Preflash validation failed - FAILED (remote failure)
Adicional Info:
1º Normal powerup, Recovery and Factory not work (if try acess return to fastboot menu and show "boot up failed")
2º I have unlock code in my e-mail (but i get error to try unlock via fastboot and device still lock)
3º In RSD Lite the device is detected (Fastboot Victara S) but "device propertis" all info is "N/A"
4º In RSD Lite after start flashing, the error show is "failed flashing process 6/27 flash boot "boot.img" -> Phone Returned FAIL."
Tecnical information:
Model: Moto X2 - XT1097
Device is Locked.
Status code: 0
Software Status: Official
Moto Auto Flash Tool v7.1 info:
Code:
Moto Auto Flasher / Root Script By Jamesjerss
________________________________________________________________________________
Connect in Fastboot Mode
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: 0011988140
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: 0000000000000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353320064305837
(bootloader) meid:
(bootloader) date: 2015-06-12
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jun 28 4:41: 2 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retbr/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: br.retbr.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_S
(bootloader) version-baseband[1]: INGLELA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:44:51 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: retbr
all: listed above
Execution time is 1(s)
Done!
Press any key to go Home
If i try flash via "Moto Auto Flash Tool v7.1"
Code:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.093s]
finished. total time: 0.106s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2022 KB)...
OKAY [ 0.086s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.341s]
finished. total time: 0.431s
FLASHING BOOTLOADER..
target max-sparse-size: 256MB
error: cannot load 'Firmware\bootloader.img': No error
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (1454 KB)...
OKAY [ 0.075s]
writing 'logo'...
OKAY [ 0.045s]
finished. total time: 0.124s
FLASHING BOOT...
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.366s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.385s
FLASHING RECOVERY...
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.369s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.374s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS...
target max-sparse-size: 256MB
error: cannot load 'Firmware\system.img': No error
target max-sparse-size: 256MB
sending 'system' (257335 KB)...
OKAY [ 8.399s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.442s
target max-sparse-size: 256MB
sending 'system' (256636 KB)...
OKAY [ 8.389s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.427s
target max-sparse-size: 256MB
sending 'system' (256815 KB)...
OKAY [ 8.400s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.436s
target max-sparse-size: 256MB
sending 'system' (260318 KB)...
OKAY [ 8.506s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.541s
target max-sparse-size: 256MB
sending 'system' (260548 KB)...
OKAY [ 8.520s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.552s
target max-sparse-size: 256MB
sending 'system' (249475 KB)...
OKAY [ 8.151s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.188s
target max-sparse-size: 256MB
sending 'system' (256925 KB)...
OKAY [ 8.398s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.432s
target max-sparse-size: 256MB
sending 'system' (257925 KB)...
OKAY [ 8.436s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.469s
FLASHING MODEM...
target max-sparse-size: 256MB
sending 'modem' (63188 KB)...
OKAY [ 2.079s]
writing 'modem'...
OKAY [ 0.852s]
finished. total time: 3.177s
erasing 'modemst1'...
OKAY [ 0.009s]
finished. total time: 0.010s
erasing 'modemst2'...
OKAY [ 0.007s]
finished. total time: 0.009s
target max-sparse-size: 256MB
sending 'fsg' (871 KB)...
OKAY [ 0.052s]
writing 'fsg'...
OKAY [ 0.054s]
finished. total time: 0.110s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.252s]
finished. total time: 0.254s
ERASING USERDATA...
erasing 'userdata'...
OKAY [ 1.463s]
finished. total time: 2.884s
Done!...Press any key to Go Menu There Press R to Reboot
Please, any help...
Sorry my english is rusty.

I need help with my smartphone

Hi all.
I write here to tell you my problem.
First of all I want to apologize for my language since I use a translator.
I have a MOTO G5S PLUS (xt1800) that sticks to the logo.
I attach images of the compilation that I had installed.
{
"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"
}
As you can see, I have OEM_LOCK and that does not allow me to unlock the boot loader.
I understand that, having OEM_LOCK, the only thing I can do is install a firmware equal to or higher than the one I have installed.
so perform the steps of the following tutorial to be able to repair
https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967?nocache=1
I'm sorry to say that it did not work. nor did any other method work that I know of. I leave here the error of ADB Minimal.
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: -0.000s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot oem fb_mode_set
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.062s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash bootloader bootloade
r.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.109s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(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 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.531s]
finished. total time: 0.656s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71925 KB)...
OKAY [ 1.544s]
writing 'modem'...
OKAY [ 1.092s]
finished. total time: 2.636s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3024 KB)...
OKAY [ 0.062s]
writing 'fsg'...
OKAY [ 0.125s]
finished. total time: 0.187s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.359s]
writing 'dsp'...
OKAY [ 0.281s]
finished. total time: 0.655s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.109s]
finished. total time: 0.156s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.374s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.546s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash recovery recovery.im
g
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.686s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (256355 KB)...
OKAY [ 5.523s]
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: 5.586s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (262115 KB)...
OKAY [ 5.617s]
writing 'system'...
(bootloader) Invalid sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.617s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (259034 KB)...
OKAY [ 5.556s]
writing 'system'...
(bootloader) Invalid sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.571s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262013 KB)...
OKAY [ 5.617s]
writing 'system'...
(bootloader) Invalid sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.633s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 5.609s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.624s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 5.610s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.625s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (259637 KB)...
OKAY [ 5.594s]
writing 'system'...
(bootloader) Invalid sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.609s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (240915 KB)...
OKAY [ 5.197s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.212s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 5.601s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.633s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (233189 KB)...
OKAY [ 4.992s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.992s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash system system.img_sp
arsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (65436 KB)...
OKAY [ 1.405s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.405s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (145482 KB)...
OKAY [ 3.121s]
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.168s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot erase cache
erasing 'cache'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.125s]
finished. total time: 0.125s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot erase DDR
erasing 'DDR'...
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Users\Nadia\Desktop\COLOCAR FIRMWARE AQUI>fastboot oem fb_mode_clear
Click to expand...
Click to collapse
please. If anyone knows how I can solve it, I would greatly appreciate it. From already thank you very much.

try flashing the latest version of the stock 8.1

Android 9.0 OTA?

Has anyone in the States received the Android Pie update yet? I've been waiting patiently for it, and I've tried to flash an OTA flash rom that I found on the internet but it requires a different, older build number than mine. My phone is on OPSS27.104-92-4. Has anyone gotten the update yet or is there an OTA image out there that will flash to that build version?

Check your SKU and channel and find out if it has been released here: https://mirrors.lolinet.com/firmware/moto/ali/official/

I know I am anxiously awaiting this myself. Moto G6 on Straight Talk(Tracfone) and looks like it's still not showing up. This is just a backup phone for me and as soon as it updates I'm giving it to my granddaughter to replace her hand me down S5. I'd love to manually flash it and move on but not sure I want to try the ones already available.

RedFoxGaming said:
Has anyone in the States received the Android Pie update yet? I've been waiting patiently for it, and I've tried to flash an OTA flash rom that I found on the internet but it requires a different, older build number than mine. My phone is on OPSS27.104-92-4. Has anyone gotten the update yet or is there an OTA image out there that will flash to that build version?
Click to expand...
Click to collapse
You definitely need your SKU and update channel to know for sure.

There's nothing for the tracfone channel which is what mine is on. I'm gonna try to sideload the Retail rom but I'm guessing I'm not going to get too far until tracfone releases 9.0 on their channel, if they ever do. Tracfone is really good about not ever pushing the first update.

You can upgrade to Pie manually by downloading the RETUS file and flashing it by following this guide. I'm currently on Pie and it works fine

AgentICS said:
You can upgrade to Pie manually by downloading the RETUS file and flashing it by following this guide. I'm currently on Pie and it works fine
Click to expand...
Click to collapse
I tried that, but I don't know if I'm just doing something wrong or tracfone is really locked down, all I got was an erased phone and a bunch of file verification and signature errors and following the guide, it never actually flashed anything. Also, following the steps, after extracting the image to my adb folders, some of the commands point to files the image itself did not have.
EDIT: To be fair, maybe it's because my bootloader is OEM locked and I have no idea how to unlock it when motorola states it doesn't qualify and won't help me past that point. Freaking Straighttalk. I use fastboot getvar all and have a CID return of 0x000F and they state it's not eligible for the bootloader to unlock.
EDIT 2: Doing further research, I realized I need to use fastboot and not adb, since this is a firmware image and not an OTA update. But still having issues getting the image to flash period. I really hope I don't have to unlock the bootloader, cause if I do, I'm stuck until tracfone releases the firmware officially, if they ever do.
EDIT 3: Here is what it's doing. I cannot get this firmware to flash, period.
Code:
C:\android\adb\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.091s]
finished. total time: 0.101s
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.199s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(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 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.461s]
finished. total time: 0.663s
target reported max download size of 534773760 bytes
sending 'modem' (62668 KB)...
OKAY [ 1.589s]
writing 'modem'...
OKAY [ 0.560s]
finished. total time: 2.151s
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.202s]
writing 'fsg'...
OKAY [ 0.113s]
finished. total time: 0.318s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.417s]
writing 'dsp'...
OKAY [ 0.172s]
finished. total time: 0.592s
target reported max download size of 534773760 bytes
sending 'logo' (2182 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.065s]
finished. total time: 0.129s
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.593s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.824s
target reported max download size of 534773760 bytes
sending 'recovery' (22628 KB)...
OKAY [ 0.579s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.831s
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 7.169s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.260s
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.557s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.580s
target reported max download size of 534773760 bytes
sending 'system' (262143 KB)...
OKAY [ 6.548s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.563s
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.530s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.559s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.540s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.555s
target reported max download size of 534773760 bytes
sending 'system' (259192 KB)...
OKAY [ 6.688s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.750s
target reported max download size of 534773760 bytes
sending 'system' (240044 KB)...
OKAY [ 6.106s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.250s
target reported max download size of 534773760 bytes
sending 'system' (259920 KB)...
OKAY [ 6.645s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.740s
target reported max download size of 534773760 bytes
sending 'system' (250489 KB)...
OKAY [ 6.490s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.508s
target reported max download size of 534773760 bytes
sending 'system' (151620 KB)...
OKAY [ 3.902s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.970s
target reported max download size of 534773760 bytes
sending 'vendor' (261620 KB)...
OKAY [ 6.613s]
writing 'vendor'...
(bootloader) Image v failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.667s
target reported max download size of 534773760 bytes
sending 'vendor' (187916 KB)...
OKAY [ 4.687s]
writing 'vendor'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.703s
target reported max download size of 534773760 bytes
sending 'oem' (157217 KB)...
OKAY [ 3.928s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.978s
erasing 'modemst1'...
OKAY [ 0.019s]
finished. total time: 0.021s
erasing 'modemst2'...
OKAY [ 0.020s]
finished. total time: 0.021s
erasing 'DDR'...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.202s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.316s
...
OKAY [ 0.003s]
finished. total time: 0.005s

RedFoxGaming said:
I tried that, but I don't know if I'm just doing something wrong or tracfone is really locked down, all I got was an erased phone and a bunch of file verification and signature errors and following the guide, it never actually flashed anything. Also, following the steps, after extracting the image to my adb folders, some of the commands point to files the image itself did not have.
EDIT: To be fair, maybe it's because my bootloader is OEM locked and I have no idea how to unlock it when motorola states it doesn't qualify and won't help me past that point. Freaking Straighttalk. I use fastboot getvar all and have a CID return of 0x000F and they state it's not eligible for the bootloader to unlock.
EDIT 2: Doing further research, I realized I need to use fastboot and not adb, since this is a firmware image and not an OTA update. But still having issues getting the image to flash period. I really hope I don't have to unlock the bootloader, cause if I do, I'm stuck until tracfone releases the firmware officially, if they ever do.
Click to expand...
Click to collapse
Official firmware will flash without unlocking the bootloader. They're signed. You definitely have to use fastboot commands. With the phone in fastboot mode.

madbat99 said:
Official firmware will flash without unlocking the bootloader. They're signed. You definitely have to use fastboot commands. With the phone in fastboot mode.
Click to expand...
Click to collapse
I made an edit in my previous post showing the errors I get when I try to use fastboot to do this. Everything past trying to flash boot.img fails due to a verification issue.

RedFoxGaming said:
I tried that, but I don't know if I'm just doing something wrong or tracfone is really locked down, all I got was an erased phone and a bunch of file verification and signature errors and following the guide, it never actually flashed anything. Also, following the steps, after extracting the image to my adb folders, some of the commands point to files the image itself did not have.
EDIT: To be fair, maybe it's because my bootloader is OEM locked and I have no idea how to unlock it when motorola states it doesn't qualify and won't help me past that point. Freaking Straighttalk. I use fastboot getvar all and have a CID return of 0x000F and they state it's not eligible for the bootloader to unlock.
EDIT 2: Doing further research, I realized I need to use fastboot and not adb, since this is a firmware image and not an OTA update. But still having issues getting the image to flash period. I really hope I don't have to unlock the bootloader, cause if I do, I'm stuck until tracfone releases the firmware officially, if they ever do.
EDIT 3: Here is what it's doing. I cannot get this firmware to flash, period.
Code:
C:\android\adb\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.091s]
finished. total time: 0.101s
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.199s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(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 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.461s]
finished. total time: 0.663s
target reported max download size of 534773760 bytes
sending 'modem' (62668 KB)...
OKAY [ 1.589s]
writing 'modem'...
OKAY [ 0.560s]
finished. total time: 2.151s
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.202s]
writing 'fsg'...
OKAY [ 0.113s]
finished. total time: 0.318s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.417s]
writing 'dsp'...
OKAY [ 0.172s]
finished. total time: 0.592s
target reported max download size of 534773760 bytes
sending 'logo' (2182 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.065s]
finished. total time: 0.129s
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.593s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.824s
target reported max download size of 534773760 bytes
sending 'recovery' (22628 KB)...
OKAY [ 0.579s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.831s
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 7.169s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.260s
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.557s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.580s
target reported max download size of 534773760 bytes
sending 'system' (262143 KB)...
OKAY [ 6.548s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.563s
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.530s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.559s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.540s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.555s
target reported max download size of 534773760 bytes
sending 'system' (259192 KB)...
OKAY [ 6.688s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.750s
target reported max download size of 534773760 bytes
sending 'system' (240044 KB)...
OKAY [ 6.106s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.250s
target reported max download size of 534773760 bytes
sending 'system' (259920 KB)...
OKAY [ 6.645s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.740s
target reported max download size of 534773760 bytes
sending 'system' (250489 KB)...
OKAY [ 6.490s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.508s
target reported max download size of 534773760 bytes
sending 'system' (151620 KB)...
OKAY [ 3.902s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.970s
target reported max download size of 534773760 bytes
sending 'vendor' (261620 KB)...
OKAY [ 6.613s]
writing 'vendor'...
(bootloader) Image v failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.667s
target reported max download size of 534773760 bytes
sending 'vendor' (187916 KB)...
OKAY [ 4.687s]
writing 'vendor'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.703s
target reported max download size of 534773760 bytes
sending 'oem' (157217 KB)...
OKAY [ 3.928s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.978s
erasing 'modemst1'...
OKAY [ 0.019s]
finished. total time: 0.021s
erasing 'modemst2'...
OKAY [ 0.020s]
finished. total time: 0.021s
erasing 'DDR'...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.202s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.316s
...
OKAY [ 0.003s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Try redownloading the zip, maybe it was corrupted. Also, don't use the script on the post with all the commands, that didn't work for me. I did all the commands manually and that's the only way I got it to work. Equally, don't worry about the missing BTFM.bin or dspso.bin as I too was missing them.

AgentICS said:
Try redownloading the zip, maybe it was corrupted. Also, don't use the script on the post with all the commands, that didn't work for me. I did all the commands manually and that's the only way I got it to work. Equally, don't worry about the missing BTFM.bin or dspso.bin as I too was missing them.
Click to expand...
Click to collapse
Even doing it manually and I've been using the Moto XML to Batch script and it won't work. Doing it manually causes it to fail for the same reason. And I can't try RDS Lite cause my device refuses to show up no matter what I do. I'm going to try a different computer.

RedFoxGaming said:
Even doing it manually and I've been using the Moto XML to Batch script and it won't work. Doing it manually causes it to fail for the same reason. And I can't try RDS Lite cause my device refuses to show up no matter what I do. I'm going to try a different computer.
Click to expand...
Click to collapse
I don't mean to double post but it wont let me edit the post for some reason. Here is my output from typing in all the commands manually. It works fine until I get to boot.img and all the system image files. I'm afraid TracFone has the bootloader locked down so hard it won't let me install the images. And there is no way to my knowledge to unlock this bootloader.
Code:
c:\Users\Cody\Downloads\XT1925-6_ALI_RETUS_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.528s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.776s
c:\Users\Cody\Downloads\XT1925-6_ALI_RETUS_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.532s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.780s
c:\Users\Cody\Downloads\XT1925-6_ALI_RETUS_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.532s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.792s
c:\Users\Cody\Downloads\XT1925-6_ALI_RETUS_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 5.718s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.822s

RedFoxGaming said:
I tried that, but I don't know if I'm just doing something wrong or tracfone is really locked down, all I got was an erased phone and a bunch of file verification and signature errors and following the guide, it never actually flashed anything. Also, following the steps, after extracting the image to my adb folders, some of the commands point to files the image itself did not have.
EDIT: To be fair, maybe it's because my bootloader is OEM locked and I have no idea how to unlock it when motorola states it doesn't qualify and won't help me past that point. Freaking Straighttalk. I use fastboot getvar all and have a CID return of 0x000F and they state it's not eligible for the bootloader to unlock.
EDIT 2: Doing further research, I realized I need to use fastboot and not adb, since this is a firmware image and not an OTA update. But still having issues getting the image to flash period. I really hope I don't have to unlock the bootloader, cause if I do, I'm stuck until tracfone releases the firmware officially, if they ever do.
EDIT 3: Here is what it's doing. I cannot get this firmware to flash, period.
Code:
C:\android\adb\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.091s]
finished. total time: 0.101s
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.199s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(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 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.461s]
finished. total time: 0.663s
target reported max download size of 534773760 bytes
sending 'modem' (62668 KB)...
OKAY [ 1.589s]
writing 'modem'...
OKAY [ 0.560s]
finished. total time: 2.151s
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.202s]
writing 'fsg'...
OKAY [ 0.113s]
finished. total time: 0.318s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.417s]
writing 'dsp'...
OKAY [ 0.172s]
finished. total time: 0.592s
target reported max download size of 534773760 bytes
sending 'logo' (2182 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.065s]
finished. total time: 0.129s
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.593s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.824s
target reported max download size of 534773760 bytes
sending 'recovery' (22628 KB)...
OKAY [ 0.579s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.831s
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 7.169s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.260s
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.557s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.580s
target reported max download size of 534773760 bytes
sending 'system' (262143 KB)...
OKAY [ 6.548s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.563s
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.530s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.559s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.540s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.555s
target reported max download size of 534773760 bytes
sending 'system' (259192 KB)...
OKAY [ 6.688s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.750s
target reported max download size of 534773760 bytes
sending 'system' (240044 KB)...
OKAY [ 6.106s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.250s
target reported max download size of 534773760 bytes
sending 'system' (259920 KB)...
OKAY [ 6.645s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.740s
target reported max download size of 534773760 bytes
sending 'system' (250489 KB)...
OKAY [ 6.490s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.508s
target reported max download size of 534773760 bytes
sending 'system' (151620 KB)...
OKAY [ 3.902s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.970s
target reported max download size of 534773760 bytes
sending 'vendor' (261620 KB)...
OKAY [ 6.613s]
writing 'vendor'...
(bootloader) Image v failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.667s
target reported max download size of 534773760 bytes
sending 'vendor' (187916 KB)...
OKAY [ 4.687s]
writing 'vendor'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.703s
target reported max download size of 534773760 bytes
sending 'oem' (157217 KB)...
OKAY [ 3.928s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.978s
erasing 'modemst1'...
OKAY [ 0.019s]
finished. total time: 0.021s
erasing 'modemst2'...
OKAY [ 0.020s]
finished. total time: 0.021s
erasing 'DDR'...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.202s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.316s
...
OKAY [ 0.003s]
finished. total time: 0.005s
Click to expand...
Click to collapse
RedFoxGaming said:
I don't mean to double post but it wont let me edit the post for some reason. Here is my output from typing in all the commands manually. It works fine until I get to boot.img and all the system image files. I'm afraid TracFone has the bootloader locked down so hard it won't let me install the images. And there is no way to my knowledge to unlock this bootloader.
Code:
c:\Users\Cody\Downloads\XT1925-6_ALI_RETUS_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.528s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.776s
c:\Users\Cody\Downloads\XT1925-6_ALI_RETUS_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.532s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.780s
c:\Users\Cody\Downloads\XT1925-6_ALI_RETUS_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.532s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.792s
c:\Users\Cody\Downloads\XT1925-6_ALI_RETUS_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 5.718s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.822s
Click to expand...
Click to collapse
Preflash validation failure means that the file you're trying to flash is older than the installed version. Usually that's the case, however, uses of other Moto G's have reported it being because of a locked bootloader which is probably the case according tothis thread

If I have to unlock my Bootloader I'm screwed on this update.

AgentICS said:
You can upgrade to Pie manually by downloading the RETUS file and flashing it by following this guide. I'm currently on Pie and it works fine
Click to expand...
Click to collapse
Have you had any issues with "OK Google" not working correctly?

Ragarianok said:
Have you had any issues with "OK Google" not working correctly?
Click to expand...
Click to collapse
I have not, it's worked so far. Even on the lock screen it wakes up the phone

RedFoxGaming said:
Even doing it manually and I've been using the Moto XML to Batch script and it won't work. Doing it manually causes it to fail for the same reason. And I can't try RDS Lite cause my device refuses to show up no matter what I do. I'm going to try a different computer.
Click to expand...
Click to collapse
Are you sure your device is Ali? Not Aljeter or something. Is it a g6 or g6 bla bla something?

It is a straighttalk (although it's got TracFone branding on it) Motorola G6 XT1925DL
It's got 3GB ram and 32GB storage
And if it makes a difference the current build of 8.0.0 that's on here is the January 1st OPSS27.104-92-4

I'm very certain that it's because of the bootloader not being unlocked. Others mentioned on the other Pie thread it being because of the bootloader being locked. I do remember that stock Android Recovery has an "Apply update from ADB/external memory" but I don't know if Moto such option in the recovery, if so, use that. That might work.

It does have that option, but it just fails immediately if I try to use adb. I haven't been able to find an OTA update firmware that will work with adb sideload either.
And I've been in contact with Motorola, they stated that this phone is not eligible for unlock due to their policy not allowing TracFone phones too have their Bootloader unlocked