Database Develop

Moto g XT1068 bootloop/bricked can't recover/flash images

HI EVERYBODY
I need your help to unbrick my moto g XT1068.
The phone have already bootloader unlocked.
I was run lollipop custom Stock rom Optimized (root, etc) and have trwp recovery.
Every things works fine and I use the fone about 1 week and today the phone turn automatically on bootloader screen.
I was unable to boot proprely on Normal Powerup and go to recovery.
error message: failed to validate recovery image - boot up failed
I then try to flash stock firmaware and I go these error:
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.010s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.274s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 5.092s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.944s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.055s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 20.023s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.370s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.399s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.380s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.411s
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 13.542s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.611s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 13.618s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.713s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 13.866s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.940s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 12.912s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.950s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.698s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.726s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.996s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.040s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.071s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.988s
rebooting...
finished. total time: 0.001s
WAS HAPPEN TO MY PHONE ? PLEASE HELP ME ALL DRIVER IS PROPRELY INSTALL

roulyz said:
HI EVERYBODY
I need your help to unbrick my moto g XT1068.
The phone have already bootloader unlocked.
I was run lollipop custom Stock rom Optimized (root, etc) and have trwp recovery.
Every things works fine and I use the fone about 1 week and today the phone turn automatically on bootloader screen.
I was unable to boot proprely on Normal Powerup and go to recovery.
error message: failed to validate recovery image - boot up failed
Click to expand...
Click to collapse
What version of TWRP are you running? Some of the older ones aren't supported anymore and have trouble flashing on the Moto G 2014. You should be using v2.8.5.0

Duck86 said:
What version of TWRP are you running? Some of the older ones aren't supported anymore and have trouble flashing on the Moto G 2014. You should be using v2.8.0.5
Click to expand...
Click to collapse
Hum was using 2.8.5.0. Does good?

roulyz said:
Hum was using 2.8.5.0. Does good?
Click to expand...
Click to collapse
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652

Duck86 said:
Its not officially supported and may be what the problem is.
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Click to expand...
Click to collapse
OK I will try but I have other xt1068 and that recovery work since 2 week pretty good on it

Duck86 said:
Its not officially supported and may be what the problem is.
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Click to expand...
Click to collapse
Why do you think TWRP 2.8.5.0 is not offical supported?
http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149
This thread is under original android development and TWRP supports Moto G 2014 with this version.They did also with 2.8.4.0.
http://teamw.in/project/twrp2/275

Wolfcity said:
Why do you think TWRP 2.8.5.0 is not offical supported?
http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149
This thread is under original android development and TWRP supports Moto G 2014 with this version.They did also with 2.8.4.0.
http://teamw.in/project/twrp2/275
Click to expand...
Click to collapse
Got the version numbers mixed up. Sorry, I shouldn't be doing numbers when I'm tired

I know that....

Duck86 said:
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Click to expand...
Click to collapse
ok for the first link, the custom recovery is openrecovery-twrp-2.8.5.0-titan.img witch I have flashed on my brick moto g
and it works good without problem.
For the 2nd link there is no recovery img on file, it just a flashage script.
All still don't work I GOT all the time:
sending 'recovery' (9694 KB)...
OKAY [ 99.815s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 114.759s
NEED HELP AGAIN

roulyz said:
ok for the first link, the custom recovery is openrecovery-twrp-2.8.5.0-titan.img witch I have flashed on my brick moto g
and it works good without problem.
For the 2nd link there is no recovery img on file, it just a flashage script.
All still don't work
NEED HELP AGAIN
Click to expand...
Click to collapse
Where did you get the stock firmware? What link are you using?

all fastboot command works but I got error from partition
ADB command don't work. It works fine when the phone ran well but not now :crying:

Duck86 said:
Where did you get the stock firmware? What link are you using?
Click to expand...
Click to collapse
the rom i flashed in the phone was Stock firmware optimised by @Shawn5162
http://forum.xda-developers.com/moto-g-2014/development/rom-stock-lollipop-rom-t3024800
and when the phone brick I have tested these link:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
and
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167

roulyz said:
the rom i flashed in the phone was Stock firmware optimised by @Shawn5162
http://forum.xda-developers.com/moto-g-2014/development/rom-stock-lollipop-rom-t3024800
and when the phone brick I have tested these link:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
and
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
Click to expand...
Click to collapse
I've been thinking on it and the only other thing I can think of is to try going through the unlock bootloader proceedure again.

Duck86 said:
I've been thinking on it and the only other thing I can think of is to try going through the unlock bootloader proceedure again.
Click to expand...
Click to collapse
I have done bootloader unlocked process again and get that error
D:\Android TOOLS\platform-tools>fastboot oem unlock MGYXUCQJ5XHSYVTLYACD
...
(bootloader) Unlock code = MGYXUCQJ5XHSYVTLYACD
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s

It looks like the partition tables have been completely removed because the "failed to write primary gpt is a Linux error". Since none of the commands will access the partitions, I would guess the partitions need to be rebuilt. I don't have a clue how to do that on a mobile though.

Tel864 said:
It looks like the partition tables have been completely removed because the "failed to write primary gpt is a Linux error". Since none of the commands will access the partitions, I would guess the partitions need to be rebuilt. I don't have a clue how to do that on a mobile though.
Click to expand...
Click to collapse
Whoouuuaaa!!! So what can I do?

Have you guys tryed
To boot recovery
fastboot boot recovery.img

USBhost said:
Have you guys tryed
To boot recovery
fastboot boot recovery.img
Click to expand...
Click to collapse
yes, but don't works. I got error

need help please

Moto G Xt 1068: failed remotely
Did u recover your device ?
---------- Post added at 09:57 AM ---------- Previous post was at 09:56 AM ----------
roulyz said:
need help please
Click to expand...
Click to collapse
Same with me, help me out pleaseee
Thanks

[Q] Bootloader problems

Hello anyone! I'm looking for some help.
i have 4.2 originaly and i update the software to 4.4, after that i unlocked my bootloader, installed custom cwm and flash CM11+12 and when i want to return to stock rom i flashed stock rogers firmware 4.2, in this step everything is ok, when i try to update to 4.4 the phone turn off and trying to install the update and then is stoped and i have a messages :
Device is locked. statuts cide : 0 (why? i try to unlock it again but failed!!!)
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
im trying to re-flash the stock recovery, reboot and flash the rom 4.2 but failed !! i dont know what i can do to make the phone working again!
Well, i wish someone could help me, thanks a lot XDA

messages error
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.306s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.243s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1588 KB)...
OKAY [ 0.427s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.723s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.008s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash logo logo.bin
< waiting for device >
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (2563 KB)...
OKAY [ 0.467s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.585s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.953s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.069s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash recovery recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.972s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.090s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (717764 KB)...
OKAY [ 46.448s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 46.565s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53644 KB)...
OKAY [ 4.224s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 4.343s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.110s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.102s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'fsg' (212 KB)...
OKAY [ 0.390s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.505s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.129s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.105s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase customize
erasing 'customize'...
(bootloader) Invalid partition name customize
FAILED (remote failure)
finished. total time: 0.105s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase clogo
erasing 'clogo'...
(bootloader) Invalid partition name clogo
FAILED (remote failure)
finished. total time: 0.101s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot fb_mode_clear

wolf1985 said:
Hello anyone! I'm looking for some help.
i have 4.2 originaly and i update the software to 4.4, after that i unlocked my bootloader, installed custom cwm and flash CM11+12 and when i want to return to stock rom i flashed stock rogers firmware 4.2, in this step everything is ok, when i try to update to 4.4 the phone turn off and trying to install the update and then is stoped and i have a messages :
Device is locked. statuts cide : 0 (why? i try to unlock it again but failed!!!)
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
im trying to re-flash the stock recovery, reboot and flash the rom 4.2 but failed !! i dont know what i can do to make the phone working again!
Well, i wish someone could help me, thanks a lot XDA
Click to expand...
Click to collapse
wolf1985 said:
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
Click to expand...
Click to collapse
(bold in the quote added by me for emphasis)
YOU CAN NOT DOWNGRADE!!! It has been warned many times that you can not downgrade due to GPT.BIN and MOTOBOOT.IMG.
The only time it was safe was downgrading from 4.4 to 4.2.2. w/Camera Update OTA as part of the SlapMyMoto/MotoWpNoMo process for those with LOCKED bootloaders,
Based on the file name you are using (from your 2nd post), you are trying to flash the ORIGINAL SHIPPING 4.2.2 ROM which does cause a brick.
Now, based your two posts, It appears your phone is an XT1058 from Rogers Canada. Is that correct? or are you just trying to flash the Rogers Canada rom?
(If your phone really is an XT1058 from Rogers)... At this point, there are two options.
1. If you can get the phone to boot into fastboot mode, Download the 4.4.4 SBF for Rogers Canada (RCI) from -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 . (NOTE: If your phone is NOT a Rogers XT1058, then download the newst SBF for your phone's carrier and model!) and use the Requirements and Option 5 from -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and hope it works. If it works, it will flash you to stock 4.4.4. At that point, you can try to re-unlock the bootloader. And never think about flashing any other older ROM again!
2. If you can't get into Fastboot mode to flash, Go to -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 for help.

Thanks KidJoe
You save me !!!!! thanks so much for your help !!!!! :good::good::good::good:

Recovery not working
i try to enter into recovery but the phone turn on, the recovery not working|

wolf1985 said:
i try to enter into recovery but the phone turn on, the recovery not working|
Click to expand...
Click to collapse
The stock recovery work fine sorry, thank you for your help

VZN XT1254 Droid Turbo All stock. bootloader locked. software:eek:fficial, bricked help!

VZN XT1254 Droid Turbo All stock. bootloader locked. softwarefficial, bricked help!
I rooted with KingRoot yesterday, and then ran SunShine installer, and somewhere between that its soft bricked my device. I was using a kinda faulty usb cable, to go back and forth between command prompts for adb and fastboot, but this issue didnt arise till my first Kingroot experience, which I must add is pretty lame, but then sunshine forced closed during the process and forced a device reboot. It rebooted in bootloader , fastboot is still working, device is charging, but the bootloader log reads : Failed to validate boot image. Cant access recovery or nothing, just fastboot, my baseband is MDM9625_104651.11.05.16.02R Quark_Custom, VZN XT1254, my locked bootloader status is keeping me from getting any of my files flashed successfully, Ive got copies of RSDlite 6.2.4 , my drivers installed, adb fastboot, and my stock image of VZN_/SU4TL-44, no success on flashing, plz help.

Just wondering, why did you use kingroot? It is not needed anymore.
https://youtu.be/6avEPGWB8E0
Sent from my XT1254 using Tapatalk

Sunshine shouldn't have bricked your device. But I believe in the moto maxx forum you'll find images to flash in fastboot.
http://forum.xda-developers.com/showthread.php?p=59659400

I'm not necessarily saying sunshine did brick my device I'm saying sunshine and kingroot together did cause some issue due to sunshine just wanting to constantly force close, so I rebooted the device, and it's got stuck in a soft brick boot loader loop, recovery including all other options but fastboot will respond, I am new with motorolla devices, especially on the 5.1 os, I picked up this phone as a trial and error device to do whatever with, I did follow rootjunkies video on using kingroot, I know now the method was outdated, lesson learned, but I can't get no fastboot flash commands to stick due to the original secured state of the bootloader, I've always steered away from motorolla and vzn due to the locking methods of the boatloader , phone was free hope I can get out of this state now lol

Thanks for the two post , I am attempting now I will update with results

Keep getting failed remote failure, I'm on a stock locked Boatloader, should I be trying rsdlite

lwilliz87 said:
Keep getting failed remote failure, I'm on a stock locked Boatloader, should I be trying rsdlite
Click to expand...
Click to collapse
RSDlite does nothing more than automate fastboot. If fastboot won't work, RSDlite won't work. What commands, exactly, are you trying to use to flash the images that you're trying to flash? If you're using that link to the Moto Maxx forum that mrkhigh provided, that won't help you, since the SU4TL-44 Droid Turbo firmware is not listed there. This is the one that you want: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip. I'm pretty sure that "remote failure" is what fastboot says when you attempt to flash an image that is not meant for the device, or an image that is an older version of the image that is on there (which is the case if you're trying to flash any of the firmwares listed on the Moto Maxx page).

Didn't note it stopped at .38

Remote failure
You are correct. yes I get remote failure, but I have already went thru rootjunk several times and downloaded that exxact VRZ_XT1254_SU4TL-44_44_CFC.xml.zip , I have the adb and fastboot both installed, and needed files, I have also mfastboot in there too. Ive ran the BAT.exe thru command prompt, Ive tried this with the same file mentioned above from rootjunkysdl, and from moto-firmware : Following out tonight
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>VRZ_XT1254
_SU4TL-44_44_CFC.bat
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>SET fastbo
ot=fastboot.exe
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.155s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash motoboot bootloader.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 5.709s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.736s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2860 KB)...
OKAY [ 0.170s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.201s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.097s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.386s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.292s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (235017 KB)...
OKAY [ 13.362s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 17.003s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (250150 KB)...
OKAY [ 14.529s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.634s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (261098 KB)...
OKAY [ 9.887s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.120s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk4
target reported max download size of 536870912 bytes
sending 'system' (246901 KB)...
OKAY [ 9.053s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.100s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk5
target reported max download size of 536870912 bytes
sending 'system' (247563 KB)...
OKAY [ 9.430s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.515s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk6
target reported max download size of 536870912 bytes
sending 'system' (246206 KB)...
OKAY [ 9.523s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.608s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk7
target reported max download size of 536870912 bytes
sending 'system' (258024 KB)...
OKAY [ 9.215s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.405s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk8
target reported max download size of 536870912 bytes
sending 'system' (260155 KB)...
OKAY [ 9.700s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.923s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk9
target reported max download size of 536870912 bytes
sending 'system' (254924 KB)...
OKAY [ 9.498s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 23.768s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk10
target reported max download size of 536870912 bytes
sending 'system' (174885 KB)...
OKAY [ 7.398s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.558s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase ddr
erasing 'ddr'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.010s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>pause
Press any key to continue . . .

lwilliz87 said:
You are correct. yes I get remote failure, but I have already went thru rootjunk several times and downloaded that exxact VRZ_XT1254_SU4TL-44_44_CFC.xml.zip , I have the adb and fastboot both installed, and needed files, I have also mfastboot in there too. Ive ran the BAT.exe thru command prompt, Ive tried this with the same file mentioned above from rootjunkysdl, and from moto-firmware : Following out tonight
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>VRZ_XT1254
_SU4TL-44_44_CFC.bat
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>SET fastbo
ot=fastboot.exe
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.155s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash motoboot bootloader.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 5.709s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.736s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2860 KB)...
OKAY [ 0.170s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.201s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.097s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.386s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.292s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (235017 KB)...
OKAY [ 13.362s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 17.003s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (250150 KB)...
OKAY [ 14.529s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.634s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (261098 KB)...
OKAY [ 9.887s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.120s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk4
target reported max download size of 536870912 bytes
sending 'system' (246901 KB)...
OKAY [ 9.053s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.100s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk5
target reported max download size of 536870912 bytes
sending 'system' (247563 KB)...
OKAY [ 9.430s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.515s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk6
target reported max download size of 536870912 bytes
sending 'system' (246206 KB)...
OKAY [ 9.523s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.608s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk7
target reported max download size of 536870912 bytes
sending 'system' (258024 KB)...
OKAY [ 9.215s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.405s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk8
target reported max download size of 536870912 bytes
sending 'system' (260155 KB)...
OKAY [ 9.700s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.923s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk9
target reported max download size of 536870912 bytes
sending 'system' (254924 KB)...
OKAY [ 9.498s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 23.768s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk10
target reported max download size of 536870912 bytes
sending 'system' (174885 KB)...
OKAY [ 7.398s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.558s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase ddr
erasing 'ddr'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.010s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Hmmmm. Interesting. Did you try entering the commands manually in a command prompt without using the batch file?

TheSt33v said:
Hmmmm. Interesting. Did you try entering the commands manually in a command prompt without using the batch file?
Click to expand...
Click to collapse
Yes I have tried entering the commands indiviually. only one that will come back with ok clear status most of the time without any failure is the fastboot flash boot boot.img , thats when i do it by itself, and today I downloaded the verizon wireless software assistant, it detected the phone needed repair, downloaded it downloads the correct software as it says, I have been selecting keep data, and then after numerous failed attempts and redownloads I been selecting erase devices data, and when it goes to flash it fails before even the first go, Im pretty sure my drivers are right, I dont know what to do . I hoping that maybe if this keeps on and with fingers crossed the new 6.0 update will hit my device soon and the software assistant will be able to update it for me with no problems, or I can flash it with no problems, right now I am uninstalling everything Motorola and gonna retry the VZW upgrade/repair again.

Sunshine did cause this unusual soft-hard brick. (Well, more like a faulty usb cable) I'll explain:
Fastboot is unable to run ANY commands that read or write to the device, EXCEPT for getvar all.
No flashing, erasing, get_unlock_data, ect.
Can't flash gpt,boot, bootloader ect.
Since I was unable to intentionally hardbrick his phone by flashing the turbo prototype engineering edition boot loader, he can't get into a hardbrick where he could use qh_loader.
To sum it up: Fastboot is broken, can't force a true hardbrick, kingroot doesn't touch any of this. Sunshine does.
This is a TRUE hardbrick, as we can unbrick hardbricks, but this is fubar'd royally.
Jtag will be the only solution

SaschaElble you just need to lay back on this stuff, you are going to do far more harm than good.
A) no sunshine didnt cause this, please backup this statement, its pretty obvious what is going on here
B) you need to stop advising people on these things, especially trying to get people to flash things that will hardbrick phones
C) example of B, motorola hasnt enabled jtag in ages
D) jtag doesnt fix emmc problems, jtag doesnt fix a hardware issue.
SunShine "doesnt touch any of that" either, again you are going off on things you don't understand. We even published a disclosure of what sunshine does touch, wish you had read it prior to throwing blame at us : http://theroot.ninja/disclosures/TRUSTNONE_1.0-11282015.pdf
This looks like some emmc issue imo.
SaschaElble said:
Sunshine did cause this unusual soft-hard brick. (Well, more like a faulty usb cable) I'll explain:
Fastboot is unable to run ANY commands that read or write to the device, EXCEPT for getvar all.
No flashing, erasing, get_unlock_data, ect.
Can't flash gpt,boot, bootloader ect.
Since I was unable to intentionally hardbrick his phone by flashing the turbo prototype engineering edition boot loader, he can't get into a hardbrick where he could use qh_loader.
To sum it up: Fastboot is broken, can't force a true hardbrick, kingroot doesn't touch any of this. Sunshine does.
This is a TRUE hardbrick, as we can unbrick hardbricks, but this is fubar'd royally.
...It's almost as if a totally different, and incompatible bootloader was flashed, but the conversion process was not completed by sunshines app. The entire partition table is messed up, and trying to flash gpt.bin to correct this fails as well. So a deeper rooted problem is present.
Jtag will be the only solution
Click to expand...
Click to collapse

A) Kingroot by itself sure didn't do it. User observed your app foreclosing and then device restarting, while this may be the intended sequence of events, the end result was a bricked turbo
B) Hardbricking via eng edition bootloader its a tested and unbrickable situtation.
C) Jtaging in this case had nothing to to with my intentional hardbrick, as hardbricks can be unbricked without jtag
D) How does this appear to be a emmc hardware problem? Device would boot into qh_loader mode if this was the case, as aboot would be unreachable.
E) Another user reported sending device out for jtag repair services, without further research I would assume such exist. In the most extreme cases, removing the emmc chip and flashing can be done.
SunShine "doesnt touch any of that" - This is assuming defined behavior, we are talking about undefined behavior = You can't prove it did, or didn't. But you can logically deduce that only sunshine modify's the way the turbo boots at the bootloader level. It may VERY well be that your app worked 100% as intended, but user's device had unexpected consequences. Still faulting sunshine.
This looks like some emmc issue imo. Again, a faulty emmc would cause the SoC to boot in to QH_Loader (unbrick mode) - This is not a faulty emmc. Even IF it was, this was directly after your app force closed and the device restarted.

SaschaElble said:
A) Kingroot by itself sure didn't do it. User observed your app foreclosing and then device restarting, while this may be the intended sequence of events, the end result was a bricked turbo
B) Hardbricking via eng edition bootloader its a tested and unbrickable situtation.
C) Jtaging in this case had nothing to to with my intentional hardbrick, as hardbricks can be unbricked without jtag
D) How does this appear to be a emmc hardware problem? Device would boot into qh_loader mode if this was the case, as aboot would be unreachable.
E) Another user reported sending device out for jtag repair services, without further research I would assume such exist. In the most extreme cases, removing the emmc chip and flashing can be done.
SunShine "doesnt touch any of that" - This is assuming defined behavior, we are talking about undefined behavior = You can't prove it did, or didn't. But you can logically deduce that only sunshine modify's the way the turbo boots at the bootloader level. It may VERY well be that your app worked 100% as intended, but user's device had unexpected consequences. Still faulting sunshine.
This looks like some emmc issue imo. Again, a faulty emmc would cause the SoC to boot in to QH_Loader (unbrick mode) - This is not a faulty emmc. Even IF it was, this was directly after your app force closed and the device restarted.
Click to expand...
Click to collapse
1.) Sunshine did not do this, period. Nothing in the sunshine apps gets anywhere near anything like this
2.) eMMC very frequently fail such that they can be read but not written. It's not uncommon at all
3.) JTAG is disabled on Motorola devices. Don't make assumptions.
By your logic, if I fill up my gas tank tomorrow and get a flat tire right afterwards, the bad gas caused it? Nice logic there.
--beaups

beaups said:
1.) Sunshine did not do this, period. Nothing in the sunshine apps gets anywhere near anything like this
2.) eMMC very frequently fail such that they can be read but not written. It's not uncommon at all
3.) JTAG is disabled on Motorola devices. Don't make assumptions.
By your logic, if I fill up my gas tank tomorrow and get a flat tire right afterwards, the bad gas caused it? Nice logic there.
--beaups
Click to expand...
Click to collapse
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?

SaschaElble said:
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
Click to expand...
Click to collapse
It is pointless indeed. We have the code, we know exactly what it is capable of, and its not capable of what's happened here. Argue all you want, you just continue to reinforce you have no clue how these devices work.
--beaups
Sent from my XT1254 using Tapatalk

Fine, I'm done.

SaschaElble said:
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
Click to expand...
Click to collapse
1) this isnt a bootloader issue, its an emmc issue, pretty dang obvious, i can see it from 30k feet up
2) I found his device ID, he never purchased sunshine (ask him), SunShine never actually ran on the device, because he never purchased it, SunShine never touched his device, just the purchasing framework (Which tests for root, basic compatibility etc) ran, and it doesnt touch anything.

Sanity tests can't cause harm?
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Either way the timing still sucks

[HELP] XT1069 stuck in fastboot

Hello everyone and sorry for my bad english.
I come here for help with my problem. I bought a Moto G2 TV (XT1069) who was stuck in fastboot mode.
But after more than 40 different procedures in 2 days, nothing worked.
Each command was returned with a failure in the cmd screen.
In fastboot mode no option works except the Barcode option.
My question is: is there a possibility that the main memory has been damaged and fastboot have been saved by being in another memory separately?
I tried everything I found here on XDA and Google and nothing work.
What disturbs me is also the fact of not knowing what version of Android it was, if the bootloader was unlocked or not and if it was with root or not.
CMD Log:
Code:
D:\Downloads\Moto\Android 6>mfastboot flash partition gpt.bin
< waiting for device >
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 5.008s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.019s
D:\Downloads\Moto\Android 6>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2184 KB)...
OKAY [ 5.083s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.100s
D:\Downloads\Moto\Android 6>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (697 KB)...
OKAY [ 5.054s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.081s
D:\Downloads\Moto\Android 6>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 5.357s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.392s
D:\Downloads\Moto\Android 6>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10280 KB)...
OKAY [ 5.375s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.425s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257435 KB)...
OKAY [ 13.094s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.134s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (255486 KB)...
OKAY [ 13.022s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.066s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (256778 KB)...
OKAY [ 13.080s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.124s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (254001 KB)...
OKAY [ 12.991s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.035s
D:\Downloads\Moto\Android 6>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (50136 KB)...
OKAY [ 6.594s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 11.635s
D:\Downloads\Moto\Android 6>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.046s
D:\Downloads\Moto\Android 6>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.047s
D:\Downloads\Moto\Android 6>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1012 KB)...
OKAY [ 5.100s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.144s
D:\Downloads\Moto\Android 6>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.046s
I accept other suggestions, although I have tried everything I found.

Have you tried flashing official Marshmallow 6.0 or 6.0.1 for your device?
I have xt1068. A month ago I was almost in a same situation. Only barcode command was working and nothing else from fastboot screen.
I have no experience in this flashing thing so I went to retailers store to fix this software issue but they failed.
Later I found official Android 6.0 thread on xda forum and just followed every step of installation Android 6.0. And Boom!! Phone is now working flawlessly on latest Android OS.
ps. While installing Android 6.0, my phone was not rooted, no custom ROM was Installed before and USB debugging was turned OFF.
I don't know if this is a proper solution or not; as I said I have no experience in flashing.
Hope this help. Ty

Hey, can you provide the link to the official android 6.0 thread?
pkirtan84 said:
Have you tried flashing official Marshmallow 6.0 or 6.0.1 for your device?
I have xt1068. A month ago I was almost in a same situation. Only barcode command was working and nothing else from fastboot screen.
I have no experience in this flashing thing so I went to retailers store to fix this software issue but they failed.
Later I found official Android 6.0 thread on xda forum and just followed every step of installation Android 6.0. And Boom!! Phone is now working flawlessly on latest Android OS.
ps. While installing Android 6.0, my phone was not rooted, no custom ROM was Installed before and USB debugging was turned OFF.
I don't know if this is a proper solution or not; as I said I have no experience in flashing.
Hope this help. Ty
Click to expand...
Click to collapse

pkirtan84 said:
Have you tried flashing official Marshmallow 6.0 or 6.0.1 for your device?
I have xt1068. A month ago I was almost in a same situation. Only barcode command was working and nothing else from fastboot screen.
I have no experience in this flashing thing so I went to retailers store to fix this software issue but they failed.
Later I found official Android 6.0 thread on xda forum and just followed every step of installation Android 6.0. And Boom!! Phone is now working flawlessly on latest Android OS.
ps. While installing Android 6.0, my phone was not rooted, no custom ROM was Installed before and USB debugging was turned OFF.
I don't know if this is a proper solution or not; as I said I have no experience in flashing.
Hope this help. Ty
Click to expand...
Click to collapse
Hello, pkirtan84.
I have experience in roms samsung and LG, but on a Motorola is my first attempt, so I figured he was doing something wrong.
Anyway, although I have already tested one rom with Android 6, could send the rom link you used? Perhaps I would not have been the wrong rom I used, not hurt to try!
Thank you

ederstk said:
Hello, pkirtan84.
I have experience in roms samsung and LG, but on a Motorola is my first attempt, so I figured he was doing something wrong.
Anyway, although I have already tested one rom with Android 6, could send the rom link you used? Perhaps I would not have been the wrong rom I used, not hurt to try!
Thank you
Click to expand...
Click to collapse
sure ederstk, here is it
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682

pkirtan84 said:
sure ederstk, here is it
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
Click to expand...
Click to collapse
Thank you, pkirtan84! I'll check when I get home and post results!
All the best!

Hello, pkirtan84. Still not working, with same messages.
I believe that the low battery warning is now in the way. I will try to recharge it and continue my tests.
Still, thank you!

ederstk said:
Hello, pkirtan84. Still not working, with same messages.
I believe that the low battery warning is now in the way. I will try to recharge it and continue my tests.
Still, thank you!
Click to expand...
Click to collapse
um.. what's not working?
download link of Android 6.0 or the process of flashing 6.0?

the flashing process. still stuck in same screen. I try searching more solutions in the web

my moto x4 xt1900-2 is bricked ...

here is my story,
i am just locking my bootloader after locking bootloader i am flashing my stock rom when i tried to flash my stock rom i get an error it says {bootloader} flash permission denied
i wont able to turn on my phone when i turn on my phone it shows your device is corrupt,
in fastboot mode showing flashing_locked
please helpp mee please what can i dooo plzzzz help...
sorry for my bad english..

Sounds like the flash that didn't take relocked the bootloader.
Have you tried unlocking it again via fastboot?

d_mouse81 said:
Sounds like the flash that didn't take relocked the bootloader.
Have you tried unlocking it again via fastboot?
Click to expand...
Click to collapse
yess i tried unlocking but it says you need to turn on oem unlocking

iampkp said:
yess i tried unlocking but it says you need to turn on oem unlocking
Click to expand...
Click to collapse
Try fastboot oem fb_mode_set before flashing and fastboot oem fb_mode_clear after flashing everything

Zokhii said:
Try fastboot oem fb_mode_set before flashing and fastboot oem fb_mode_clear after flashing everything
Click to expand...
Click to collapse
not working bro i tried..
still showing {bootloader} flash permission denied
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot devices
ZY224GW5SN fastboot
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot oem fb_mode_set
OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.007s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.124s]
Finished. Total time: 0.428s
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.285s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
Finished. Total time: 0.464s
see this
help me plz

iampkp said:
not working bro i tried..
still showing {bootloader} flash permission denied
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot devices
ZY224GW5SN fastboot
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot oem fb_mode_set
OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.007s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.124s]
Finished. Total time: 0.428s
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.285s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
Finished. Total time: 0.464s
see this
help me plz
Click to expand...
Click to collapse
Do you remember your latest installed stock rom? Was it 8.0.0 or 8.1.0? It is possible that you try to flash an older image and downgrading doesn't work. You could try to flash this one, it is the latest retail version https://androidfilehost.com/?fid=1322778262904007756. Since you have the 1900-2 variant, I don't know if it will work.. I use it on my 1900-7 and everything is absolutely fine

Zokhii said:
Do you remember your latest installed stock rom? Was it 8.0.0 or 8.1.0? It is possible that you try to flash an older image and downgrading doesn't work. You could try to flash this one, it is the latest retail version https://androidfilehost.com/?fid=1322778262904007756. Since you have the 1900-2 variant, I don't know if it will work.. I use it on my 1900-7 and everything is absolutely fine
Click to expand...
Click to collapse
i am trying to flash this img https://androidfilehost.com/?fid=1322778262903985819
i will try your img but i dont think so that it will work because
see this image
https://drive.google.com/file/d/18ycgD83N8nPmCW5N8FDeRLZy5h-C-VVW/view?usp=sharing
and ty for replying and helping.....

Zokhii said:
Do you remember your latest installed stock rom? Was it 8.0.0 or 8.1.0? It is possible that you try to flash an older image and downgrading doesn't work. You could try to flash this one, it is the latest retail version https://androidfilehost.com/?fid=1322778262904007756. Since you have the 1900-2 variant, I don't know if it will work.. I use it on my 1900-7 and everything is absolutely fine
Click to expand...
Click to collapse
just now i flashed this latetst rom and still its failed
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
ZY224GW5SN fastboot
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (37 KB)...
OKAY [ 0.002s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.112s]
finished. total time: 0.114s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.224s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.303s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (94843 KB)...
OKAY [ 2.098s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.116s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (5680 KB)...
OKAY [ 0.124s]
writing 'fsg_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.129s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bluetooth BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4564 KB)...
OKAY [ 0.101s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.126s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp dspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.362s]
writing 'dsp_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (2153 KB)...
OKAY [ 0.050s]
writing 'logo_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.054s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516148 KB)...
OKAY [ 11.385s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.390s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (523975 KB)...
OKAY [ 11.544s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.549s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (520973 KB)...
OKAY [ 11.540s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.545s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (523236 KB)...
OKAY [ 11.564s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.569s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (522092 KB)...
OKAY [ 11.523s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.527s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (487698 KB)...
OKAY [ 10.808s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 10.814s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (524133 KB)...
OKAY [ 11.573s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.577s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (222582 KB)...
OKAY [ 4.925s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.929s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system_b system_other.img
target reported max download size of 536870912 bytes
sending 'system_b' (134369 KB)...
OKAY [ 2.975s]
writing 'system_b'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.983s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (210797 KB)...
OKAY [ 4.677s]
writing 'oem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.683s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase carrier
erasing 'carrier'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
this is what its showing ...

Try the whole process on a different computer with USB 2.0 ports and maybe with mfastboot instead of regular fastboot - I had the same issue, flashing failed every time until I tried it on a older computer

Zokhii said:
Try the whole process on a different computer with USB 2.0 ports and maybe with mfastboot instead of regular fastboot - I had the same issue, flashing failed every time until I tried it on a older computer
Click to expand...
Click to collapse
bro I tried In my computer laptop and my frnds laptop but the same problem Is showing
how should I change flashing_locked status in fastboot mode
I tried this cmd fastboot flashing unlock but it says turn on OEM unlocking but I am unable to do anything how i can I turn on OEM unlocking in developer option..
help me.

iampkp said:
bro I tried In my computer laptop and my frnds laptop but the same problem Is showing
how should I change flashing_locked status in fastboot mode
I tried this cmd fastboot flashing unlock but it says turn on OEM unlocking but I am unable to do anything how i can I turn on OEM unlocking in developer option..
help me.
Click to expand...
Click to collapse
Yeah I understand you but flashing unmodified stock images should work - even with locked bootloader...

Zokhii said:
Yeah I understand you but flashing unmodified stock images should work - even with locked bootloader...
Click to expand...
Click to collapse
yes but it wont worked now moto service center is telling me that you have hardware issue....
you have to change motherboard....
is it right???

iampkp said:
yes but it wont worked now moto service center is telling me that you have hardware issue....
you have to change motherboard....
is it right???
Click to expand...
Click to collapse
You could always try doing a blank flash. There are files here, cannot say if it will help:
https://forum.xda-developers.com/moto-x4/help/moto-x4-hardbrick-blank-flash-t3857803
or this
https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529
Good luck

iampkp said:
bro I tried In my computer laptop and my frnds laptop but the same problem Is showing
how should I change flashing_locked status in fastboot mode
I tried this cmd fastboot flashing unlock but it says turn on OEM unlocking but I am unable to do anything how i can I turn on OEM unlocking in developer option..
help me.
Click to expand...
Click to collapse
In my XT1900-1 I have this status: oem_locked
Still no chances to load any firmware.
When running this command, system says:
fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (487698 KB)...
OKAY [ 10.948s]
writing 'system'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.020s
And that's where the process stops.

have the same problems
fastboot & mfastboot FAILED (remote failure)