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.

[Q] Bricked moto g xt1068 won't flash anything from fastboot, help!

Hello, my moto g xt1068 was in a bootloop, I've tried to flash back a stock firmware but it always give me an error like this "(bootloader) | Failed to erase partition (bootloader) Failed to flash partition logo | FAILED (remote failure)" and now it has only the "AP fastboot flash mode", no system and no recovery.
Some more info:
- My bootloader is unlocked;
- I can't boot any recovery using fastboot boot command, I got the error "Incomplete boot image for booting" (cwm,twrp, stock)
- My partitions are "raw" I suspect this is the main problem
- I've tried using windows and osx
- I've tried using fastboot and mfastboot
- I'm not able to use RSD lite, it' doesn't recognize my device
- I've tried a lot of stock firmware, no difference
Please help me, there is anything else to try? Is my phone dead (maybe emmc failure)?
Here is the output of fastboot getvar all:
HTML:
(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 Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D223XTZ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid: 233A12050F000000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "flashfail" configured as fastboot
(bootloader) imei: 353321068993768
(bootloader) meid:
(bootloader) date: 09-13-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 15:41:58 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retde/titan_umtsds:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXB22.46-28.1/1:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.26.1.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-gdd242b0 ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jan 23 13:23:41 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.82-0-g72f9f12
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D223XTZ
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
finished. total time: 0.085s

This is technically not an answer....
Which ROM where you using when your phone began boot looping (stock or custom). What you should have done was try a complete factory reset(did this a couple of times to my xt1068 when it was in boot loop). Can i ask the names of the stock firmware you used (the full information about them) and the commands you used. Let me see if i can help you

sagar846 said:
Which ROM where you using when your phone began boot looping (stock or custom). What you should have done was try a complete factory reset(did this a couple of times to my xt1068 when it was in boot loop). Can i ask the names of the stock firmware you used (the full information about them) and the commands you used. Let me see if i can help you
Click to expand...
Click to collapse
Thank you for your answer.
I had a stock firmware 5.02 with stock recovery, can't remember the exact version but i guess it was the "retde" one
I tried to wipe cache and userdata but it won't get out of the boot loop (did you mean this by full factory reset?)
I've tried RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml,Retaildsdsall_XT1068_5.0.2_LXB22.99-16_Easy_Installer, RETAILDSDSALL_EU_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml, RETAILDSDSALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC_SVC.xml, XT1068_4.4.4_DSDS_ALL.23_Easy_Installerand and even RETUGLB_XT1063_5.0.2_LXB22.46-28_cid9_CFC.xml
I tried also some variation on the fastboot commands but mainly like this:
HTML:
mfastboot.exe oem fb_mode_set
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 oem fb_mode_clear
mfastboot.exe reboot

kesy85 said:
Thank you for your answer.
I had a stock firmware 5.02 with stock recovery, can't remember the exact version but i guess it was the "retde" one
I tried to wipe cache and userdata but it won't get out of the boot loop (did you mean this by full factory reset?)
I've tried RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml,Retaildsdsall_XT1068_5.0.2_LXB22.99-16_Easy_Installer, RETAILDSDSALL_EU_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml, RETAILDSDSALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC_SVC.xml, XT1068_4.4.4_DSDS_ALL.23_Easy_Installerand and even RETUGLB_XT1063_5.0.2_LXB22.46-28_cid9_CFC.xml
I tried also some variation on the fastboot commands but mainly like this:
HTML:
mfastboot.exe oem fb_mode_set
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 oem fb_mode_clear
mfastboot.exe reboot
Click to expand...
Click to collapse
when you type the fastboot comand: fastboot devices, what's written on the screen?

dani.galla said:
when you type the fastboot comand: fastboot devices, what's written on the screen?
Click to expand...
Click to collapse
Only the serial number followed by fastboot, but I think it's right, no?
ZX1D223XTZ fastboot

kesy85 said:
Only the serial number followed by fastboot, but I think it's right, no?
ZX1D223XTZ fastboot
Click to expand...
Click to collapse
Yes, right, means that the computer recognizes the phone.
When you flash stock via fastboot, gives you errors?
Have you tried with the easy installer tool? (this: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612)

dani.galla said:
Yes, right, means that the computer recognizes the phone.
When you flash stock via fastboot, gives you errors?
Have you tried with the easy installer tool? (this: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612)
Click to expand...
Click to collapse
yes to both the questions.
I've tried also using easy installer but it's simply a .bat file containing the same commands I manually use.
And i've got this errors while flashing stock firmware:
HTML:
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.027s]
writing 'partition'...
OKAY [ 0.324s]
finished. total time: 0.351s
mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.101s]
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.186s
mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.028s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.988s
mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.325s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.344s
mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.334s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.358s
mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257619 KB)...
OKAY [ 13.069s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.137s
mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256618 KB)...
OKAY [ 13.045s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.140s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260464 KB)...
^[[AOKAY [ 13.159s]
writing 'system'...
^[[A(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.237s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260464 KB)...
OKAY [ 13.164s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.246s
mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (244081 KB)...
OKAY [ 12.647s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.689s
mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (36088 KB)...
OKAY [ 6.149s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.178s
mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.558s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.584s
mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.992s
mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s

kesy85 said:
yes to both the questions.
I've tried also using easy installer but it's simply a .bat file containing the same commands I manually use.
And i've got this errors while flashing stock firmware:
HTML:
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.027s]
writing 'partition'...
OKAY [ 0.324s]
finished. total time: 0.351s
mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.101s]
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.186s
mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.028s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.988s
mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.325s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.344s
mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.334s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.358s
mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257619 KB)...
OKAY [ 13.069s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.137s
mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256618 KB)...
OKAY [ 13.045s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.140s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260464 KB)...
^[[AOKAY [ 13.159s]
writing 'system'...
^[[A(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.237s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260464 KB)...
OKAY [ 13.164s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.246s
mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (244081 KB)...
OKAY [ 12.647s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.689s
mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (36088 KB)...
OKAY [ 6.149s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.178s
mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.558s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.584s
mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.992s
mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
Click to expand...
Click to collapse
Everything failed, very strange.
Try to update your drivers, and the try to flash again.
If you can, try with an other computer, and an other cable data.

dani.galla said:
Everything failed, very strange.
Try to update your drivers, and the try to flash again.
If you can, try with an other computer, and an other cable data.
Click to expand...
Click to collapse
Already did this, 1 windows 8.1 PC, 1 windows 10 PC, 1 virtual windows 7 pc, 1 mac book osx 10.10, drivers from motorola, multiple data cables, single adb and composite adb no difference

Small update, managed to get rsd lite to work but no difference, flash fails anyway.
and there is the full output of easy installer:
HTML:
FIRMWARE Auto Restore Script by Gary J Wright
MOTO G 2nd GEN Lollipop 5.0.2 FIRMWARE Flashe
Plug in USB CABLE and Put Phone in AP FASTBOO
Premere un tasto per continuare . . .
* server not running *
* daemon not running. starting it now on port
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 99.122s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 4.992s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition tabl
FAILED (remote failure)
finished. total time: 10.265s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 5.086s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.936s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.023s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.999s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.351s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.374s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.335s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recove
FAILED (remote failure)
finished. total time: 10.374s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS...
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 13.104s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.174s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 13.135s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.268s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 13.104s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.190s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 12.324s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.378s
target max-sparse-size: 256MB
sending 'system' (44584 KB)...
OKAY [ 6.614s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.435s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 7.067s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 12.106s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.031s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.070s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.109s
ERASING CACHE ......
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.031s
ERASING USERDATA.......
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.015s
DONE!.........PRESS ANY KEY TO REBOOT
Please help me :crying:

[/QUOTE]Please help me :crying:[/QUOTE]
Unfortunately this is an issue faced by a few users including myself, there is no solution at the moment and it seems that some people who have returned the phone to Motorola had to pay to have the motherboard replaced. Sorry

same problem here too, please Sir give solution

is there a solution yet? I have the same problem
Please help me :crying:[/QUOTE]
Unfortunately this is an issue faced by a few users including myself, there is no solution at the moment and it seems that some people who have returned the phone to Motorola had to pay to have the motherboard replaced. Sorry[/QUOTE]

Is there any solution for this thing till now?
---------- Post added at 11:34 AM ---------- Previous post was at 11:29 AM ----------
kesy85 said:
Hello, my moto g xt1068 was in a bootloop, I've tried to flash back a stock firmware but it always give me an error like this "(bootloader) | Failed to erase partition (bootloader) Failed to flash partition logo | FAILED (remote failure)" and now it has only the "AP fastboot flash mode", no system and no recovery.
Some more info:
- My bootloader is unlocked;
- I can't boot any recovery using fastboot boot command, I got the error "Incomplete boot image for booting" (cwm,twrp, stock)
- My partitions are "raw" I suspect this is the main problem
- I've tried using windows and osx
- I've tried using fastboot and mfastboot
- I'm not able to use RSD lite, it' doesn't recognize my device
- I've tried a lot of stock firmware, no difference
Please help me, there is anything else to try? Is my phone dead (maybe emmc failure)?
Here is the output of fastboot getvar all:
HTML:
(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 Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D223XTZ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid: 233A12050F000000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "flashfail" configured as fastboot
(bootloader) imei: 353321068993768
(bootloader) meid:
(bootloader) date: 09-13-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 15:41:58 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retde/titan_umtsds:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXB22.46-28.1/1:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.26.1.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-gdd242b0 ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jan 23 13:23:41 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.82-0-g72f9f12
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D223XTZ
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
finished. total time: 0.085s
Click to expand...
Click to collapse
Any update on this?

I have the same problem. Anybody solved it?

The first error appears, when flashing bootloader (motoboot.img). Your bootloader might prevent to be flashed or maybe downgraded?
Try flashing fastboot files and skip the motoboot.img step. I would recommend to flash in terminal step by step, don' t use this script. Flash files according to the content of Stock Rom folder.
mfastboot.exe flash partition gpt.bin
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
RED files should be in your folder, sometimes there are less system.img_sparsechunk files
Go to terminal or power shell (as admin) and flash step by step

I did everything
mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 99.341s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 104.596s
mfastboot.exe format system
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.006s
mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.025s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.983s
mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.327s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.717s
mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.343s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.741s
mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 13.378s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 26.916s
mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.694s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.725s
mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.991s
mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.983s
mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.044s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.063s
mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.003s
mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
But i get everything FAILED
Mayby i have problem with emmc?

please nothing solution? ita a hardware problem? not software problem?

cmcshm said:
please nothing solution? ita a hardware problem? not software problem?
Click to expand...
Click to collapse
If you connect the device to your PC as what is it shown? If not in Windows explorer in the control panel/device manager?
Sent from my Moto G 2014 using XDA Labs

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.

Broken fastboot oem unlocking issus on moto g5 plus Hannah. Please help

Hello all so I unlocked my boot loader and then I think something odd happened BC it's saying its locked buy still seems to be unlocked. Anyway I keep done loading firmware and side loading iywand it simply won't work if any of you can makd full tsrp backup I could use twrp to hopefully rescue devjcs

this is when i attemp the unlock again
PS C:\Users\Jack\Desktop\New folder> fastboot.exe oem unlock X46SMX5XO4VBGBTL6XO4
...
(bootloader) invalid boot state
OKAY [ 0.004s]
finished. total time: 0.006s
PS C:\Users\Jack\Desktop\New folder>
this is what happens when attempting flashingfactory image
PS C:\Users\Jack\Desktop\New folder> fastboot.exe oem unlock X46SMX5XO4VBGBTL6XO4
...
(bootloader) invalid boot state
OKAY [ 0.004s]
finished. total time: 0.006s
PS C:\Users\Jack\Desktop\New folder>
PS C:\Users\Jack\Desktop\New folder> fastboot flash partition gpt.bin
>> fastboot flash bootloader bootloader.img
>> fastboot flash modem NON-HLOS.bin
>> fastboot flash fsg fsg.mbn
>> fastboot erase modemst1
>> fastboot erase modemst2
>> fastboot flash bluetooth BTFM.bin
>> fastboot flash dsp dspso.bin
>> fastboot flash boot boot.img
>> fastboot flash system system.img_sparsechunk.# (do this for each numbered variant normally starting with 0)
>> fastboot flash system_b system_b.img_sparsechunk.# (do this for each numbered variant normally starting with 0)
>> fastboot flash oem oem.img
>> fastboot flash oem_b oem_other.img
>> fastboot flash vendor vendor.img_sparsechunk.# (do this for each numbered variant normally starting with 0)
>> fastboot erase carrier
>> fastboot erase userdata
>> fastboot erase DDR
>> fastboot flash logo logo.bin
>> fastboot reboot
< waiting for device >
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.006s]
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.073s
target reported max download size of 535822336 bytes
sending 'bootloader' (7483 KB)...
OKAY [ 0.244s]
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.522s]
finished. total time: 0.780s
target reported max download size of 535822336 bytes
sending 'modem' (76610 KB)...
OKAY [ 2.414s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.440s
target reported max download size of 535822336 bytes
sending 'fsg' (1984 KB)...
OKAY [ 0.065s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.071s
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.018s
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.017s
error: cannot load 'BTFM.bin'
error: cannot load 'dspso.bin'
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.521s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.545s
do : The term 'do' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:10 char:49
+ fastboot flash system system.img_sparsechunk.# (do this for each numb ...
+ ~~
+ CategoryInfo : ObjectNotFound: (do:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
do : The term 'do' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:11 char:53
+ fastboot flash system_b system_b.img_sparsechunk.# (do this for each ...
+ ~~
+ CategoryInfo : ObjectNotFound: (do:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
target reported max download size of 535822336 bytes
sending 'oem' (150840 KB)...
OKAY [ 4.749s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.774s
error: cannot load 'oem_other.img'
do : The term 'do' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:14 char:49
+ fastboot flash vendor vendor.img_sparsechunk.# (do this for each numb ...
+ ~~
+ CategoryInfo : ObjectNotFound: (do:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
erasing 'carrier'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.006s
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.006s
target reported max download size of 535822336 bytes
sending 'logo' (1423 KB)...
OKAY [ 0.055s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.087s
rebooting...
finished. total time: 0.111s
PS C:\Users\Jack\Desktop\New folder> fastboot oem config
...
(bootloader) <UTAG name="battery" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) Battery detection control
(bootloader) ("test" or "no_eprom")
(bootloader) </description>
(bootloader) </UTAG>
(bootloader) <UTAG name="bootmode" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) To force certain bootmode
(bootloader) (valid values are "fastboot", "factory", "bp-tools", "q
(bootloader) com", and "on-device-diag")
(bootloader) </description>
(bootloader) </UTAG>
(bootloader) <UTAG name="carrier" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see http://goo.gl/lojLh3
(bootloader) </description>
(bootloader) </UTAG>
(bootloader) <UTAG name="factory_kill_timeout" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) Timeout to shutdown in factory if usb is disconnected.
(bootloader) By default, this feature is disabled.
(bootloader) 0 - shutdown immediately
(bootloader) n - shutdown phone in n seconds: 1 ~ 100
(bootloader)
(bootloader) </description>
(bootloader) </UTAG>
(bootloader) <UTAG name="fsg-id" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) FSG IDs, see http://goo.gl/gPmhU
(bootloader) </description>
(bootloader) </UTAG>
(bootloader) <UTAG name="enable_dump_gpt" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) Indicate if the oem command to dump gpt is enabled (tru
(bootloader) e|false)
(bootloader) </description>
(bootloader) </UTAG>
OKAY [ 0.141s]
finished. total time: 0.144s