Related
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.
Im currently following a guide to update my encrypted N6 to 5.0.1 and it is all working well up until i go to flash the system.img that i got from 5.0.1 where i get an error.
Code:
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot flash system
system.img
target reported max download size of 536870912 bytes
sending 'system' (457800 KB)...
OKAY [ 14.332s]
writing 'system'...
(bootloader) Invalid sparse image
FAILED (status read failed (Too many links))
finished. total time: 14.353s
Im not sure where to go from here, any tips?
Chris_Krz said:
Im currently following a guide to update my encrypted N6 to 5.0.1 and it is all working well up until i go to flash the system.img that i got from 5.0.1 where i get an error.
Code:
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot flash system
system.img
target reported max download size of 536870912 bytes
sending 'system' (457800 KB)...
OKAY [ 14.332s]
writing 'system'...
(bootloader) Invalid sparse image
FAILED (status read failed (Too many links))
finished. total time: 14.353s
Im not sure where to go from here, any tips?
Click to expand...
Click to collapse
Your device won't override. So you can erase the system
fastboot erase system -w
then flash
fastboot flash system system.img
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
Hi all,
My RAZR i softbricked almost a year ago. I am determined that I will get my holidays pictures from it... please help me do so!
It gets stuck on the intel page when booting normally, I can access fastboot however I think the phone must be locked. In AP fastboot the options are:
Normal Powerup
Recovery
Factory
BP Tools
Switch Console
Power Off
Recovery will ocassionally take me to the sick looking droid.
When trying through RSD Lite I get stuck at 3/10 "boot_signed", and the phone says "preflash validation failed". I think this may be because the fastboot is locked?
When running through this guide: https://forum.xda-developers.com/showthread.php?t=2390573 unbrick.bat can't find libusb0.dll (possibly a windows 10 issue?).
I can't actually remember what version of Android I was running, however I'm pretty sure it was JB.
If anyone can advise as to what I should try next, or whether I can't recover my pictures at all, then please do get in touch.
Greg
GrogSym said:
Hi all,
My RAZR i softbricked almost a year ago. I am determined that I will get my holidays pictures from it... please help me do so!
It gets stuck on the intel page when booting normally, I can access fastboot however I think the phone must be locked. In AP fastboot the options are:
Normal Powerup
Recovery
Factory
BP Tools
Switch Console
Power Off
Recovery will ocassionally take me to the sick looking droid.
When trying through RSD Lite I get stuck at 3/10 "boot_signed", and the phone says "preflash validation failed". I think this may be because the fastboot is locked?
When running through this guide: https://forum.xda-developers.com/showthread.php?t=2390573 unbrick.bat can't find libusb0.dll (possibly a windows 10 issue?).
I can't actually remember what version of Android I was running, however I'm pretty sure it was JB.
If anyone can advise as to what I should try next, or whether I can't recover my pictures at all, then please do get in touch.
Greg
Click to expand...
Click to collapse
First u can try to flash those images manually. The fastboot command then will say a bit more than just that error.
So flash the system and boot image manually.
We can't unlock the bootloader because u will lose all data from the phone.
Hazou said:
First u can try to flash those images manually. The fastboot command then will say a bit more than just that error.
So flash the system and boot image manually.
We can't unlock the bootloader because u will lose all data from the phone.
Click to expand...
Click to collapse
When I try to flash the boot image through fastboot, I get the following:
C:\Users\Greg\Desktop>fastboot boot boot_signed
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.432s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.626s
Presumably because this is restricted (ie no root)?
When I try the image file I get:
C:\Users\Greg\Desktop>fastboot flash system system_signed
(bootloader) Variable not supported!
target reported max download size of 104857600 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 626995964 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 515375868 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 407782140 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 296858364 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 185189116 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 74765052 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 8956 is not a multiple of the block size 4096
sending sparse 'system' (90258 KB)...
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
OKAY [ 8.452s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 8.825s
Am I doing something wrong?
GrogSym said:
When I try to flash the boot image through fastboot, I get the following:
C:\Users\Greg\Desktop>fastboot boot boot_signed
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.432s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.626s
Presumably because this is restricted (ie no root)?
Click to expand...
Click to collapse
Nope, "root" is only a system thingy and is most commonly used in Android when u can access system files while u are on a running system.
In this case the command "boot" is restricted in the bootloader. No way to enable that one for us. U need to use "flash"
GrogSym said:
When I try the image file I get:
C:\Users\Greg\Desktop>fastboot flash system system_signed
(bootloader) Variable not supported!
target reported max download size of 104857600 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 626995964 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 515375868 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 407782140 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 296858364 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 185189116 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 74765052 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 8956 is not a multiple of the block size 4096
sending sparse 'system' (90258 KB)...
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 733045500 is not a multiple of the block size 4096
OKAY [ 8.452s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 8.825s
Am I doing something wrong?
Click to expand...
Click to collapse
Are u using the "fastboot" executable from the Android sdk? I recommend in this case to use the "mFastboot" executable.
The mfastboot executable in the RSD-Lite package should work just fine.
Just make sure u are using the latest JB (4.1.2) rsd-lite package.
Hazou said:
Nope, "root" is only a system thingy and is most commonly used in Android when u can access system files while u are on a running system.
In this case the command "boot" is restricted in the bootloader. No way to enable that one for us. U need to use "flash"
Are u using the "fastboot" executable from the Android sdk? I recommend in this case to use the "mFastboot" executable.
The mfastboot executable in the RSD-Lite package should work just fine.
Just make sure u are using the latest JB (4.1.2) rsd-lite package.
Click to expand...
Click to collapse
Thank you so much for your continued help - I'm afraid I'm no further ahead. I have tried the following:
C:\Users\Greg\Desktop>mfastboot flash boot boot_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.421s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 1.799s
C:\Users\Greg\Desktop>mfastboot flash system system_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.850s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 10.479s
C:\Users\Greg\Desktop>
The phone returns: (...security version downgraded then)
PIV block validation failed
EIV block validation failed for system
Invalid PIV image: system
Fastboot command failed
Does this suggest I am using the wrong image file? CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml
I can't see an alternative for a UK phone on 4.1.2
Maybe I could just fly you to my house and you can fix it for me If there is a tutorial that I should be following that I have missed, then please do let me know.
Many thanks again,
Greg
GrogSym said:
Thank you so much for your continued help - I'm afraid I'm no further ahead. I have tried the following:
C:\Users\Greg\Desktop>mfastboot flash boot boot_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.421s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 1.799s
C:\Users\Greg\Desktop>mfastboot flash system system_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.850s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 10.479s
C:\Users\Greg\Desktop>
The phone returns: (...security version downgraded then)
PIV block validation failed
EIV block validation failed for system
Invalid PIV image: system
Fastboot command failed
Does this suggest I am using the wrong image file? CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml
I can't see an alternative for a UK phone on 4.1.2
Maybe I could just fly you to my house and you can fix it for me If there is a tutorial that I should be following that I have missed, then please do let me know.
Many thanks again,
Greg
Click to expand...
Click to collapse
We can't get around that. The error message indicates that the wrong system or other images are flashed into the device. Sry, I have no clue on how to restore that.
Kitkat?
Could it be that failed OTA updates won't allow downgrades?
I have a xt890 that is bootlooping with the very same errors while trying to fastboot flash 4.1.2 en.GB.
I'm coming to the conclusion that the OTA Update partially succeeded and its no longer accepting JB firmware...
Hazou said:
We can't get around that. The error message indicates that the wrong system or other images are flashed into the device. Sry, I have no clue on how to restore that.
Click to expand...
Click to collapse
Ok, so I bought a Moto X4 (XT-1900-7) with the goal to install lineage OS. I got with android 7.1.1 installed and I updated it with the built-in updater to 8.1 (I guess). After that there were no more updates available.
I unlocked the bootloader and tried flashing pie with a flash-all script I got somewhere.
No I am stuck in a boot loop: The Motorola logo appears with the note "Verity mode is set to logging" for a few seconds, than it turns black an starts over.
When I try to flash a ROM I get:
sudo ./flash-all.sh
(bootloader) is-logicalartition: not found
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.110s]
Finished. Total time: 0.113s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9520 KB) OKAY [ 0.340s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
OKAY [ 0.188s]
Finished. Total time: 0.533s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.101s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (94843 KB) OKAY [ 3.288s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5680 KB) OKAY [ 0.186s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.010s]
Finished. Total time: 0.011s
Erasing 'modemst2' OKAY [ 0.003s]
Finished. Total time: 0.004s
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.150s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.579s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (2153 KB) OKAY [ 0.068s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (20625 KB) OKAY [ 0.692s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516148 KB) OKAY [ 17.491s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523995 KB) OKAY [ 18.490s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (520953 KB) OKAY [ 17.796s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523244 KB) OKAY [ 17.745s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (522088 KB) OKAY [ 17.449s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (487694 KB) OKAY [ 16.998s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (524133 KB) OKAY [ 18.174s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (222598 KB) OKAY [ 7.805s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system_b: not found
Sending 'system_b' (134369 KB) OKAY [ 4.625s]
Writing 'system_b' OKAY [ 1.023s]
Finished. Total time: 5.649s
(bootloader) is-logicalem__a: not found
Sending 'oem__a' (210797 KB) OKAY [ 7.291s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'carrier' OKAY [ 0.011s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.242s]
Finished. Total time: 0.243s
Erasing 'ddr' OKAY [ 0.003s]
Finished. Total time: 0.004s
Click to expand...
Click to collapse
Here is the flash-all:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 9
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
Click to expand...
Click to collapse
Since the first command of the script is "flash partition gpt.bin", I hoped I could repair the mess by flashing the right Stock ROM, so I tried several - with no luck. I got the ROMs from here: mirrors.lolinet. com/firmware/moto/payton. There are so many of them - I don't know which one is right. Not all of the ROMs tell you whether they are for my kind of X4 or not. Is it important to get a ROM specifically designed for a XT1900-7? I guess so, but why don't all the ROMs say which model they are for?
OK, so I hoped I could fix the device by installing twrp, format it and sideload a ROM. Again no luck. I managed to install the latest twrp and format the thing, but was unable to sideload anything. twrp says the internal sorage had 0MB.
I don't know what to do and need help. I am using ubuntu and have no windows pc available.
Your phone is RETEU variant on lolinet
Try flashing:
XT1900-7_PAYTON_RETEU_DS_9.0.....
You can open the script and copy each step in manually in fastboot to check for any errors, or just run the MAC script in linux.
OK, I thought so. I tried flashing said ROM and got the same problem.
sudo ./flash-all.sh
(bootloader) is-logicalartition: not found
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.128s]
Finished. Total time: 0.171s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9520 KB) OKAY [ 0.329s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
OKAY [ 0.195s]
Finished. Total time: 0.566s
Rebooting into bootloader OKAY [ 0.012s]
Finished. Total time: 0.263s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (94843 KB) OKAY [ 3.191s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5680 KB) OKAY [ 0.185s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.010s]
Finished. Total time: 0.011s
Erasing 'modemst2' OKAY [ 0.003s]
Finished. Total time: 0.003s
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.147s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.538s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (2153 KB) OKAY [ 0.076s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (20625 KB) OKAY [ 0.701s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516148 KB) OKAY [ 17.138s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523995 KB) OKAY [ 17.363s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (520953 KB) OKAY [ 17.834s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523244 KB) OKAY [ 18.286s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (522088 KB) OKAY [ 18.237s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (487694 KB) OKAY [ 17.075s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (524133 KB) OKAY [ 18.088s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (222598 KB) OKAY [ 7.794s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system_b: not found
Sending 'system_b' (134369 KB) OKAY [ 4.592s]
Writing 'system_b' OKAY [ 1.026s]
Finished. Total time: 5.634s
(bootloader) is-logicalem__a: not found
Sending 'oem__a' (210797 KB) OKAY [ 7.264s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'carrier' OKAY [ 0.010s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.170s]
Finished. Total time: 0.170s
Erasing 'ddr' OKAY [ 0.003s]
The problem is in the first line I guess:
(bootloader) is-logicalartition: not found
Click to expand...
Click to collapse
How do I address this?
If you can get into fastboot, try:
fastboot boot twrp-3.3.1-0-twrp.img (with the img file on your computer)
and fix through twrp
If you are bootloop-ing (ignore the verity thing), it simply means you do not have a valid ROM for it to boot. If it were me, I would probably grab an appropriate (stock) ROM from lolinet and RSDlite it. But I have no experience with doing that on an A/B phone, so don't know if that's good advice. But since RSDlite takes the command stack from the zip itself, I would think that would be okay.
scratch that - I don't think rsdlite works on this phone - may have to use that lenovo moto smart assistant thing but that may require a working phone that can run that app... I'll talk with moto about that.
When flashing, beware of going backwards, bootloader-wise. Same or later. some phones will brick if you try to flash a M.
johnjingle said:
If you can get into fastboot, try:
fastboot boot twrp-3.3.1-0-twrp.img (with the img file on your computer)
and fix through twrp
Click to expand...
Click to collapse
What do you mean by "fix"? I dont know, what else I can do?
KrisM22 said:
If you are bootloop-ing (ignore the verity thing), it simply means you do not have a valid ROM for it to boot. If it were me, I would probably grab an appropriate (stock) ROM from lolinet and RSDlite it. But I have no experience with doing that on an A/B phone, so don't know if that's good advice. But since RSDlite takes the command stack from the zip itself, I would think that would be okay.
scratch that - I don't think rsdlite works on this phone - may have to use that lenovo moto smart assistant thing but that may require a working phone that can run that app... I'll talk with moto about that.
When flashing, beware of going backwards, bootloader-wise. Same or later. some phones will brick if you try to flash a M.
Click to expand...
Click to collapse
I went forward and backward with the ROMs, but how can I change the bootloader? What is a "M."?
M is marshmallow - 6 - there is none for the X4 - just 7,8,and 9. N, O, and P.
When you flash a ROM, you defacto change the bootloader if needed with that flash. ou will see a reboot in the early part of the flashall stack after it has flashed a new bootloader. It's part of the flash. Going forward. You cannot do that with a flash going backward - the flash will fail.
Please remember that I am new here so this is my best guess:
I just looked at the error messages in your first post - it says it can't find modem-a
This means to me that your phone is not A/B but just one set of partitions.
It is still effectively at 8.x in terms of bootloader and in terms of partition structure.
You are trying to flash with a stack of commands that assumes you are A/B.
At some point when doing an OTA upgrade from 8.x to 9 on this phone, somebody(I have no idea who) changes the phones partition setup from one to 2 sets.
So I suspect (I dont know - everything is done at your own risk) that you could flash an appropriate 8.x ROM from lolinet but you will have to make a command stack that doesn't reference -a or -b in it. It would also be subtly different from munchy's because that is aimed at a system that has 2 sets of partitions and will not have the flash new bootloader and reboot.
You might have success looking through older threads, perhaps munchy's, or perhaps asking munchy for an older bat file that would work on a phone that still only has one partition set - flash 8.x and at least get your phone running.
THEN...
Now, as to how to get to 9 from 8, I don't think a simple flash with munchy's command stack will do it but he would be able to tell you that. Mine was converted by the OTA update to 9.
If you have a working 8 you could try lenovo moto smart assistant (lmsa) and see if that offers to flash 9 for you, though if OTA didn't offer it, I doubt it will. Whether you can grab a 9 rom from lolinet and just flash it, I have no idea. Munchy might.
EDIT: I just realized that you might now have a situation where you have a 9 bootloader but a 8 partition set. So I don't know what would happen if you find an old command stack for 8 and run it. Will there be a bootloader conflict.
KrisM22 said:
M is marshmallow - 6 - there is none for the X4 - just 7,8,and 9. N, O, and P.
When you flash a ROM, you defacto change the bootloader if needed with that flash. ou will see a reboot in the early part of the flashall stack after it has flashed a new bootloader. It's part of the flash. Going forward. You cannot do that with a flash going backward - the flash will fail.
Please remember that I am new here so this is my best guess:
I just looked at the error messages in your first post - it says it can't find modem-a
This means to me that your phone is not A/B but just one set of partitions.
It is still effectively at 8.x in terms of bootloader and in terms of partition structure.
You are trying to flash with a stack of commands that assumes you are A/B.
At some point when doing an OTA upgrade from 8.x to 9 on this phone, somebody(I have no idea who) changes the phones partition setup from one to 2 sets.
So I suspect (I dont know - everything is done at your own risk) that you could flash an appropriate 8.x ROM from lolinet but you will have to make a command stack that doesn't reference -a or -b in it. It would also be subtly different from munchy's because that is aimed at a system that has 2 sets of partitions and will not have the flash new bootloader and reboot.
You might have success looking through older threads, perhaps munchy's, or perhaps asking munchy for an older bat file that would work on a phone that still only has one partition set - flash 8.x and at least get your phone running.
THEN...
Now, as to how to get to 9 from 8, I don't think a simple flash with munchy's command stack will do it but he would be able to tell you that. Mine was converted by the OTA update to 9.
If you have a working 8 you could try lenovo moto smart assistant (lmsa) and see if that offers to flash 9 for you, though if OTA didn't offer it, I doubt it will. Whether you can grab a 9 rom from lolinet and just flash it, I have no idea. Munchy might.
EDIT: I just realized that you might now have a situation where you have a 9 bootloader but a 8 partition set. So I don't know what would happen if you find an old command stack for 8 and run it. Will there be a bootloader conflict.
Click to expand...
Click to collapse
This is the closest I got towards an explanation for my situation so far - so thank you! I found the script, I used in so many threads, but nothing else. I will keep looking. Since the phone is shipped with a Android 7, there should be more users experiencing the same conflict.
Please report back on how this goes for you...
I've done some more research on lmsa.
go here
https://www.motorola.com/us/lenovo-motorola-smart-assistant
and download it.
Watch the video for software issues(lower left of that page).
Install it.
Start it up.
You want flash/ rescue.
follow the instructions and put your phone into fastboot mode and connect to PC via USB.
If it offers you something(takes a minute) click the little download arrow and when it's downloaded, click rescue.
This is what it looks like for me before I would click the download arrow.
derknobber said:
This is the closest I got towards an explanation for my situation so far - so thank you! I found the script, I used in so many threads, but nothing else. I will keep looking. Since the phone is shipped with a Android 7, there should be more users experiencing the same conflict.
Click to expand...
Click to collapse
Hello, did you managed to fix your problem ? im having exactly the same insue on my moto g7 plus