So I screwed up. I figured that I wouldn't update the boot loader and I should be good. Let me back up.
I started off with a locked and locked AT&T MotoX running 4.4. I got the Rogers 4.4.2 firmware figuring that I can have it working if I avoid the modem etc etc. In the back of my mind I was thinking locked bootloader, everything will fail.
I flashed the partition... it worked. ok, Let's avoid the boot loader too, just in case. Flashed the logo, that worked. Flashed the boot.img, failed. Flashed motoboot.img, passed. Then I tried to continue but all failed as you can imagine.
I was prepared fro that, so I went back to the folder with the AT&T rom and trying to flash them.... oh no. Oh dear. downgrade failed. I'm locked out! I just made a rookie mistake.
Help? I guess I want to know if there is anything I can do, other than waiting on AT&T to release a version with the 30.B4 bootloader....
So you flashed gpt.bin and motoboot.img and your bootloader is locked? Have you restarted your phone yet?
It did restart but only sits in the boot loader
Sent from my Nexus 5 using Tapatalk
OK, waiting for the full AT&T 4.4.2 flash is probably the safest option.
If you're feeling brave keep reading(I am not responsible if your phone turns into a pretty paperweight)
You can try flashing the AT&T 4.4 files one at a time, the gpt.bin will fail for sure with the downgraded version error. If the files do flash you will have the combo which has the potential to brick - older firmware with a newer bootloader. The phone should work though.
Taking the OTA update from 4.4 to 4.4.2 when released will brick it!!! However I believe you could then manually flash the full 4.4.2 file and it would be OK and you'd be back to a "normal" AT&T phone.
Well, nothing flashes actually. Everything gives the following:
Partition (x) Security Version Downgrade
bidyut said:
Well, nothing flashes actually. Everything gives the following:
Partition (x) Security Version Downgrade
Click to expand...
Click to collapse
Not even the system IMG ?
Sent on my Gummy running Lenoto X
System fails too. Here's the log of me trying them all:
Code:
$ ls -l
total 1783232
[email protected] 1 skhan staff 1757 Nov 14 14:01 ATT_XT1058_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml
[email protected] 1 skhan staff 55029760 Nov 13 00:58 NON-HLOS.bin
[email protected] 1 skhan staff 10485760 Nov 13 00:58 boot.img
[email protected] 1 skhan staff 1263616 Nov 13 00:58 fsg.mbn
[email protected] 1 skhan staff 32768 Nov 13 00:58 gpt.bin
[email protected] 1 skhan staff 634418 Nov 13 00:58 logo.bin
[email protected] 1 skhan staff 1643008 Nov 13 00:58 motoboot.img
[email protected] 1 skhan staff 10485760 Nov 13 00:58 recovery.img
[email protected] 1 skhan staff 833428668 Nov 13 00:58 system.img
$ fastboot flash partition gpt.bin
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.239s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
$ fastboot flash motoboot motoboot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.362s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.612s
$ fastboot flash boot boot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.923s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.103s
$ fastboot flash recovery recovery.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.961s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.261s
$ fastboot flash system system.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'system' (777436 KB)...
OKAY [ 49.232s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 49.853s
$
bidyut said:
System fails too. Here's the log of me trying them all:
Code:
$ ls -l
total 1783232
[email protected] 1 skhan staff 1757 Nov 14 14:01 ATT_XT1058_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml
[email protected] 1 skhan staff 55029760 Nov 13 00:58 NON-HLOS.bin
[email protected] 1 skhan staff 10485760 Nov 13 00:58 boot.img
[email protected] 1 skhan staff 1263616 Nov 13 00:58 fsg.mbn
[email protected] 1 skhan staff 32768 Nov 13 00:58 gpt.bin
[email protected] 1 skhan staff 634418 Nov 13 00:58 logo.bin
[email protected] 1 skhan staff 1643008 Nov 13 00:58 motoboot.img
[email protected] 1 skhan staff 10485760 Nov 13 00:58 recovery.img
[email protected] 1 skhan staff 833428668 Nov 13 00:58 system.img
$ fastboot flash partition gpt.bin
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.239s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
$ fastboot flash motoboot motoboot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.362s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.612s
$ fastboot flash boot boot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.923s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.103s
$ fastboot flash recovery recovery.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.961s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.261s
$ fastboot flash system system.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'system' (777436 KB)...
OKAY [ 49.232s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 49.853s
$
Click to expand...
Click to collapse
Did you manually flash it? Try mfastboot
Sent on my Gummy running Lenoto X
flashallthetime said:
Did you manually flash it? Try mfastboot
Click to expand...
Click to collapse
Yes. Manually flashing. Just tried it with mfastboot v2.
Code:
$ ../osx-fastboot flash partition gpt.bin
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.239s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
$ ../osx-fastboot flash motoboot motoboot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.365s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.615s
$ ../osx-fastboot flash boot boot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.923s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.103s
$ ../osx-fastboot flash recovery recovery.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.963s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.163s
$ ../osx-fastboot flash system system.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [ 16.726s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.716s
bidyut said:
Yes. Manually flashing. Just tried it with mfastboot v2.
Code:
$ ../osx-fastboot flash partition gpt.bin
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.239s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
$ ../osx-fastboot flash motoboot motoboot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.365s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.615s
$ ../osx-fastboot flash boot boot.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.923s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.103s
$ ../osx-fastboot flash recovery recovery.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.963s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.163s
$ ../osx-fastboot flash system system.img
ERROR: could not get pipe properties
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [ 16.726s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.716s
Click to expand...
Click to collapse
Well you aren't hard bricked or soft bricked, I think we will call this f---ed up bricked. Man you're in between a rock and a hard place. Can you take it back?
Did you flash the system from your original ROM?
I don't know I'd its worth hard bricking it and trying the moto x resurrection method? Anyone else have a opinion?
Sent on my Gummy running Lenoto X
If nothing will flash then I see no options at all other then waiting for the AT&T 4.4.2 full build or having it replaced. Even then you gotta hope the AT&T build will flash properly when it is released.
It is definitely f-ed up. The only times I miss unlocked bootloader.
bidyut said:
It is definitely f-ed up. The only times I miss unlocked bootloader.
Click to expand...
Click to collapse
We already know that, unfortunately you found out the hard way. Like Steve x said, what for the 4.4.2 firmware for your carrier
Sent on my Gummy running Lenoto X
Well thanks for the help guys. At least now I have confirmation for what I knew last night.
Follow up question, any way to get the phone into an ADB accessible state that you know off? Would have been nice to get some files off the phone.
You are going to have to wait for the full 4.4.2 AT&T FXZ. Your mistake was flashing motoboot.IMG and gpt.bin. Motoboot is the bootloader and gpt.bin will define the partitions on the device. The 4.4.2 bootloader doesn't let you downgrade and the partitions may have been altered in 4.4.2.
Sent from my Moto X on KitKat
Yeah, my mistake was thinking that even those won't work.
Hello,
last Christmas I bought two Moto G 2014 and they were working fine until Friday.
One has "died", or so it seems. It was showing the logo of android with red triangle, something usual. I tried to do a wipe / factory reset, but it´s impossible because I can´t get past the fastboot screen. If I click on "Factory" the screen turns black and I can´t do nothing, only hard reset and back to fastboot screen again.
I tried to re-install the firmware so many times and following other posts on the forum, but there is no way. All FAILED, as you can see here:
FIRMWARE Auto Restore Script by Gary J Wright a.k.a Reefuge
MOTO G 2nd GEN Lollipop 5.0.2 FIRMWARE Flasher
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Presione una tecla para continuar . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
OKAY [ 3.135s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 0.330s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.004s]
finished. total time: 3.474s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
writing 'partition'...
OKAY [ 0.337s]
finished. total time: 0.386s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.129s]
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.240s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.057s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.075s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.372s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.395s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.385s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.413s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 13.333s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.402s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 13.306s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.401s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 13.314s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.388s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 12.440s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.476s
target max-sparse-size: 256MB
sending 'system' (44584 KB)...
OKAY [ 6.479s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.510s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.634s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.661s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.988s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.077s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.103s
ERASING CACHE ......
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.988s
ERASING USERDATA.......
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
DONE!.........PRESS ANY KEY TO REBOOT
Click to expand...
Click to collapse
My phone model is:
22.21.28.titan_retaildsds.retaildsdsall.en.03
I´ve tried different firmware versions (always XT1068), but same problems.
And besides, I can not activate the "debug mode" because I can´t pass the fastboot screen.
I have Windows 8 64 bits, tried in different USB ports and in a computer with XP too.
Any ideas?
Thank you in advance.
The model is XT1068, Retaildsds.
I think its a edad nand,
Is your bootloader
fburgos said:
I think its a edad nand,
Is your bootloader
Click to expand...
Click to collapse
Do you mean it´s an outdated version or something similar?
Or drivers? :/ I think I have all of them.
My bootloader is 48.82
I´ve tried with a computer with Windows XP, but the same errors again
I´ll try with a W7 computer...
I'm really sorry I didn't finish my previous post,
I think it's a dead nand, is it your bootloader unlocked?
That might prevent you from installing any firmware I'm really not an expert just trying to help a little
Well I used the script on win 7 .. Worked fine for me .. Give it a try on win 7
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
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
Hello everyone, I own a Moto g6 xt1925-4 and I decided to root the device. First thing I unlocked the bootloader, it worked (with bad key logo). Second, I flashed TWRP, which I downloaded the IMG of from the official thread here on XDA. Third, I flashed the no-verity modified image: now I think I made a mistake because I flashed a OPS image which I should suppose is Oreo but the device was already updated to PIE.
Then the troubles started. I couldn't flash magisk, so I tricked too much on the MOUNT page on TWRP, perhaps I have mounted system or storage, then I also pulled out the USB cable without safe ejection and in the end, when I rebooted the phone in Bootloader mode and pushed Start, nothing happened at all.
I thought then: I have to restore to stock. I followed the procedure on the thread here on XDA, and I should say, something happened, but strange.
Now the phone boots up, but goes in a kind of a strange bootloop, because sometimes it says the "hello moto", sometimes not, sometimes it even starts the initial configuration, but the screen flashes on and off at random, and a few centimeters of the bottom screen are black. This happened also on TWRP recovery, the bottom part of the screen appeared cut by 2/3 centimeters.
Now I surely made mistakes, but I can't get what's wrong, and most of all this in going to get me crazy. I'm near to desperation, so I pray you to help me, please!
This is the result of the stock firmware flash I tried twice. I can see a couple of "failed" and "no such files"
Microsoft Windows XP [Versione 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Programmi\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.020s]
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.090s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.250s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.461s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71577 KB)...
OKAY [ 10.255s]
writing 'modem'...
OKAY [ 0.571s]
finished. total time: 10.836s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (6780 KB)...
OKAY [ 2.464s]
writing 'fsg'...
OKAY [ 0.100s]
finished. total time: 2.564s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin': No such file or directory
C:\Programmi\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin': No such file or directory
C:\Programmi\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 3.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.300s]
finished. total time: 3.815s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.0
target reported max download size of 534773760 bytes
sending 'system' (259756 KB)...
OKAY [ 65.294s]
writing 'system'...
OKAY [ 2.293s]
finished. total time: 67.587s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.1
target reported max download size of 534773760 bytes
sending 'system' (253441 KB)...
OKAY [ 27.379s]
writing 'system'...
OKAY [ 1.763s]
finished. total time: 29.142s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.2
target reported max download size of 534773760 bytes
sending 'system' (254074 KB)...
OKAY [ 32.957s]
writing 'system'...
OKAY [ 1.773s]
finished. total time: 34.730s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.3
target reported max download size of 534773760 bytes
sending 'system' (260545 KB)...
OKAY [ 44.554s]
writing 'system'...
OKAY [ 1.803s]
finished. total time: 46.357s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.4
target reported max download size of 534773760 bytes
sending 'system' (259733 KB)...
OKAY [ 28.171s]
writing 'system'...
OKAY [ 1.813s]
finished. total time: 29.983s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.5
target reported max download size of 534773760 bytes
sending 'system' (246724 KB)...
OKAY [ 36.092s]
writing 'system'...
OKAY [ 1.682s]
finished. total time: 37.794s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.6
target reported max download size of 534773760 bytes
sending 'system' (246141 KB)...
OKAY [ 24.425s]
writing 'system'...
OKAY [ 1.702s]
finished. total time: 26.148s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.7
target reported max download size of 534773760 bytes
sending 'system' (262029 KB)...
OKAY [ 26.448s]
writing 'system'...
OKAY [ 1.933s]
finished. total time: 28.391s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.8
target reported max download size of 534773760 bytes
sending 'system' (262001 KB)...
OKAY [ 26.198s]
writing 'system'...
OKAY [ 1.803s]
finished. total time: 28.010s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.9
target reported max download size of 534773760 bytes
sending 'system' (25072 KB)...
OKAY [ 2.654s]
writing 'system'...
OKAY [ 0.170s]
finished. total time: 2.824s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash vendor vendor.img_sparsechu
nk.0
target reported max download size of 534773760 bytes
sending 'vendor' (260148 KB)...
OKAY [ 35.711s]
writing 'vendor'...
OKAY [ 2.023s]
finished. total time: 37.744s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash vendor vendor.img_sparsechu
nk.1
target reported max download size of 534773760 bytes
sending 'vendor' (178315 KB)...
OKAY [ 16.644s]
writing 'vendor'...
OKAY [ 1.412s]
finished. total time: 18.056s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.080s]
finished. total time: 0.080s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.010s]
finished. total time: 0.010s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2182 KB)...
OKAY [ 0.681s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.751s
C:\Programmi\Minimal ADB and Fastboot>fastboot reboot
EDIT:
Good news, at least for me. I solved by flashing the PIE STOCK ROM, despite I liked OREO the most, I find this PIE slower and less smooth but anyways, that's it, I have my phone back.
But still..... I can't get the root, but that's fine, I'm still enjoying the feel of victory... maybe I'll try, some day...