[Q] [Help] AT&T flashed with Rogers boot 30.B4 - Moto X Q&A

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.

Related

Return to stock issues

Hello all,
I am attempting to reset my Nexus 6 XT1103 and I think I've tried everything.
I tried to run "flash-all.bat" and command shows:
Code:
C:\Users\Default.Default-PC>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3524 KB)...
OKAY [ 0.127s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.145s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio' (48360 KB)...
OKAY [ 1.595s]
writing 'radio'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.616s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2004185752 bytes
error: update package missing system.img
Press any key to exit...
When I try and run a single file piece by piece it shows:
Code:
C:\Users\Default.Default-PC>fastboot flash bootloader bootloader-angler-angler-02.01.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3524 KB)...
OKAY [ 0.126s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.135s
I am running Windows 10 and all drivers up and operational. Has anyone ran into this before? I searched the forums but was unable to find the answer I needed.
Thanks in advance for your assistance!
Angler is code name for Nexus 6P. You are trying to flash wrong image.
https://developers.google.com/android/nexus/images#shamu
So I just happened to buy the 6P. Didn't even realize I was clicking it. Let's pretend this post was never here...
Sent from my Nexus 6P using Tapatalk

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

VZN XT1254 Droid Turbo All stock. bootloader locked. softwarefficial, bricked help!
I rooted with KingRoot yesterday, and then ran SunShine installer, and somewhere between that its soft bricked my device. I was using a kinda faulty usb cable, to go back and forth between command prompts for adb and fastboot, but this issue didnt arise till my first Kingroot experience, which I must add is pretty lame, but then sunshine forced closed during the process and forced a device reboot. It rebooted in bootloader , fastboot is still working, device is charging, but the bootloader log reads : Failed to validate boot image. Cant access recovery or nothing, just fastboot, my baseband is MDM9625_104651.11.05.16.02R Quark_Custom, VZN XT1254, my locked bootloader status is keeping me from getting any of my files flashed successfully, Ive got copies of RSDlite 6.2.4 , my drivers installed, adb fastboot, and my stock image of VZN_/SU4TL-44, no success on flashing, plz help.
Just wondering, why did you use kingroot? It is not needed anymore.
https://youtu.be/6avEPGWB8E0
Sent from my XT1254 using Tapatalk
Sunshine shouldn't have bricked your device. But I believe in the moto maxx forum you'll find images to flash in fastboot.
http://forum.xda-developers.com/showthread.php?p=59659400
I'm not necessarily saying sunshine did brick my device I'm saying sunshine and kingroot together did cause some issue due to sunshine just wanting to constantly force close, so I rebooted the device, and it's got stuck in a soft brick boot loader loop, recovery including all other options but fastboot will respond, I am new with motorolla devices, especially on the 5.1 os, I picked up this phone as a trial and error device to do whatever with, I did follow rootjunkies video on using kingroot, I know now the method was outdated, lesson learned, but I can't get no fastboot flash commands to stick due to the original secured state of the bootloader, I've always steered away from motorolla and vzn due to the locking methods of the boatloader , phone was free hope I can get out of this state now lol
Thanks for the two post , I am attempting now I will update with results
Keep getting failed remote failure, I'm on a stock locked Boatloader, should I be trying rsdlite
lwilliz87 said:
Keep getting failed remote failure, I'm on a stock locked Boatloader, should I be trying rsdlite
Click to expand...
Click to collapse
RSDlite does nothing more than automate fastboot. If fastboot won't work, RSDlite won't work. What commands, exactly, are you trying to use to flash the images that you're trying to flash? If you're using that link to the Moto Maxx forum that mrkhigh provided, that won't help you, since the SU4TL-44 Droid Turbo firmware is not listed there. This is the one that you want: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip. I'm pretty sure that "remote failure" is what fastboot says when you attempt to flash an image that is not meant for the device, or an image that is an older version of the image that is on there (which is the case if you're trying to flash any of the firmwares listed on the Moto Maxx page).
Didn't note it stopped at .38
Remote failure
You are correct. yes I get remote failure, but I have already went thru rootjunk several times and downloaded that exxact VRZ_XT1254_SU4TL-44_44_CFC.xml.zip , I have the adb and fastboot both installed, and needed files, I have also mfastboot in there too. Ive ran the BAT.exe thru command prompt, Ive tried this with the same file mentioned above from rootjunkysdl, and from moto-firmware : Following out tonight
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>VRZ_XT1254
_SU4TL-44_44_CFC.bat
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>SET fastbo
ot=fastboot.exe
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.155s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash motoboot bootloader.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 5.709s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.736s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2860 KB)...
OKAY [ 0.170s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.201s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.097s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.386s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.292s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (235017 KB)...
OKAY [ 13.362s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 17.003s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (250150 KB)...
OKAY [ 14.529s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.634s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (261098 KB)...
OKAY [ 9.887s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.120s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk4
target reported max download size of 536870912 bytes
sending 'system' (246901 KB)...
OKAY [ 9.053s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.100s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk5
target reported max download size of 536870912 bytes
sending 'system' (247563 KB)...
OKAY [ 9.430s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.515s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk6
target reported max download size of 536870912 bytes
sending 'system' (246206 KB)...
OKAY [ 9.523s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.608s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk7
target reported max download size of 536870912 bytes
sending 'system' (258024 KB)...
OKAY [ 9.215s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.405s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk8
target reported max download size of 536870912 bytes
sending 'system' (260155 KB)...
OKAY [ 9.700s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.923s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk9
target reported max download size of 536870912 bytes
sending 'system' (254924 KB)...
OKAY [ 9.498s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 23.768s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk10
target reported max download size of 536870912 bytes
sending 'system' (174885 KB)...
OKAY [ 7.398s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.558s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase ddr
erasing 'ddr'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.010s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>pause
Press any key to continue . . .
lwilliz87 said:
You are correct. yes I get remote failure, but I have already went thru rootjunk several times and downloaded that exxact VRZ_XT1254_SU4TL-44_44_CFC.xml.zip , I have the adb and fastboot both installed, and needed files, I have also mfastboot in there too. Ive ran the BAT.exe thru command prompt, Ive tried this with the same file mentioned above from rootjunkysdl, and from moto-firmware : Following out tonight
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>VRZ_XT1254
_SU4TL-44_44_CFC.bat
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>SET fastbo
ot=fastboot.exe
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.155s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash motoboot bootloader.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 5.709s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.736s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2860 KB)...
OKAY [ 0.170s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.201s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.097s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.386s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.292s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (235017 KB)...
OKAY [ 13.362s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 17.003s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (250150 KB)...
OKAY [ 14.529s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.634s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (261098 KB)...
OKAY [ 9.887s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.120s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk4
target reported max download size of 536870912 bytes
sending 'system' (246901 KB)...
OKAY [ 9.053s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.100s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk5
target reported max download size of 536870912 bytes
sending 'system' (247563 KB)...
OKAY [ 9.430s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.515s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk6
target reported max download size of 536870912 bytes
sending 'system' (246206 KB)...
OKAY [ 9.523s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.608s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk7
target reported max download size of 536870912 bytes
sending 'system' (258024 KB)...
OKAY [ 9.215s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.405s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk8
target reported max download size of 536870912 bytes
sending 'system' (260155 KB)...
OKAY [ 9.700s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.923s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk9
target reported max download size of 536870912 bytes
sending 'system' (254924 KB)...
OKAY [ 9.498s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 23.768s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk10
target reported max download size of 536870912 bytes
sending 'system' (174885 KB)...
OKAY [ 7.398s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.558s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase ddr
erasing 'ddr'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.010s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Hmmmm. Interesting. Did you try entering the commands manually in a command prompt without using the batch file?
TheSt33v said:
Hmmmm. Interesting. Did you try entering the commands manually in a command prompt without using the batch file?
Click to expand...
Click to collapse
Yes I have tried entering the commands indiviually. only one that will come back with ok clear status most of the time without any failure is the fastboot flash boot boot.img , thats when i do it by itself, and today I downloaded the verizon wireless software assistant, it detected the phone needed repair, downloaded it downloads the correct software as it says, I have been selecting keep data, and then after numerous failed attempts and redownloads I been selecting erase devices data, and when it goes to flash it fails before even the first go, Im pretty sure my drivers are right, I dont know what to do . I hoping that maybe if this keeps on and with fingers crossed the new 6.0 update will hit my device soon and the software assistant will be able to update it for me with no problems, or I can flash it with no problems, right now I am uninstalling everything Motorola and gonna retry the VZW upgrade/repair again.
Sunshine did cause this unusual soft-hard brick. (Well, more like a faulty usb cable) I'll explain:
Fastboot is unable to run ANY commands that read or write to the device, EXCEPT for getvar all.
No flashing, erasing, get_unlock_data, ect.
Can't flash gpt,boot, bootloader ect.
Since I was unable to intentionally hardbrick his phone by flashing the turbo prototype engineering edition boot loader, he can't get into a hardbrick where he could use qh_loader.
To sum it up: Fastboot is broken, can't force a true hardbrick, kingroot doesn't touch any of this. Sunshine does.
This is a TRUE hardbrick, as we can unbrick hardbricks, but this is fubar'd royally.
Jtag will be the only solution
SaschaElble you just need to lay back on this stuff, you are going to do far more harm than good.
A) no sunshine didnt cause this, please backup this statement, its pretty obvious what is going on here
B) you need to stop advising people on these things, especially trying to get people to flash things that will hardbrick phones
C) example of B, motorola hasnt enabled jtag in ages
D) jtag doesnt fix emmc problems, jtag doesnt fix a hardware issue.
SunShine "doesnt touch any of that" either, again you are going off on things you don't understand. We even published a disclosure of what sunshine does touch, wish you had read it prior to throwing blame at us : http://theroot.ninja/disclosures/TRUSTNONE_1.0-11282015.pdf
This looks like some emmc issue imo.
SaschaElble said:
Sunshine did cause this unusual soft-hard brick. (Well, more like a faulty usb cable) I'll explain:
Fastboot is unable to run ANY commands that read or write to the device, EXCEPT for getvar all.
No flashing, erasing, get_unlock_data, ect.
Can't flash gpt,boot, bootloader ect.
Since I was unable to intentionally hardbrick his phone by flashing the turbo prototype engineering edition boot loader, he can't get into a hardbrick where he could use qh_loader.
To sum it up: Fastboot is broken, can't force a true hardbrick, kingroot doesn't touch any of this. Sunshine does.
This is a TRUE hardbrick, as we can unbrick hardbricks, but this is fubar'd royally.
...It's almost as if a totally different, and incompatible bootloader was flashed, but the conversion process was not completed by sunshines app. The entire partition table is messed up, and trying to flash gpt.bin to correct this fails as well. So a deeper rooted problem is present.
Jtag will be the only solution
Click to expand...
Click to collapse
A) Kingroot by itself sure didn't do it. User observed your app foreclosing and then device restarting, while this may be the intended sequence of events, the end result was a bricked turbo
B) Hardbricking via eng edition bootloader its a tested and unbrickable situtation.
C) Jtaging in this case had nothing to to with my intentional hardbrick, as hardbricks can be unbricked without jtag
D) How does this appear to be a emmc hardware problem? Device would boot into qh_loader mode if this was the case, as aboot would be unreachable.
E) Another user reported sending device out for jtag repair services, without further research I would assume such exist. In the most extreme cases, removing the emmc chip and flashing can be done.
SunShine "doesnt touch any of that" - This is assuming defined behavior, we are talking about undefined behavior = You can't prove it did, or didn't. But you can logically deduce that only sunshine modify's the way the turbo boots at the bootloader level. It may VERY well be that your app worked 100% as intended, but user's device had unexpected consequences. Still faulting sunshine.
This looks like some emmc issue imo. Again, a faulty emmc would cause the SoC to boot in to QH_Loader (unbrick mode) - This is not a faulty emmc. Even IF it was, this was directly after your app force closed and the device restarted.
SaschaElble said:
A) Kingroot by itself sure didn't do it. User observed your app foreclosing and then device restarting, while this may be the intended sequence of events, the end result was a bricked turbo
B) Hardbricking via eng edition bootloader its a tested and unbrickable situtation.
C) Jtaging in this case had nothing to to with my intentional hardbrick, as hardbricks can be unbricked without jtag
D) How does this appear to be a emmc hardware problem? Device would boot into qh_loader mode if this was the case, as aboot would be unreachable.
E) Another user reported sending device out for jtag repair services, without further research I would assume such exist. In the most extreme cases, removing the emmc chip and flashing can be done.
SunShine "doesnt touch any of that" - This is assuming defined behavior, we are talking about undefined behavior = You can't prove it did, or didn't. But you can logically deduce that only sunshine modify's the way the turbo boots at the bootloader level. It may VERY well be that your app worked 100% as intended, but user's device had unexpected consequences. Still faulting sunshine.
This looks like some emmc issue imo. Again, a faulty emmc would cause the SoC to boot in to QH_Loader (unbrick mode) - This is not a faulty emmc. Even IF it was, this was directly after your app force closed and the device restarted.
Click to expand...
Click to collapse
1.) Sunshine did not do this, period. Nothing in the sunshine apps gets anywhere near anything like this
2.) eMMC very frequently fail such that they can be read but not written. It's not uncommon at all
3.) JTAG is disabled on Motorola devices. Don't make assumptions.
By your logic, if I fill up my gas tank tomorrow and get a flat tire right afterwards, the bad gas caused it? Nice logic there.
--beaups
beaups said:
1.) Sunshine did not do this, period. Nothing in the sunshine apps gets anywhere near anything like this
2.) eMMC very frequently fail such that they can be read but not written. It's not uncommon at all
3.) JTAG is disabled on Motorola devices. Don't make assumptions.
By your logic, if I fill up my gas tank tomorrow and get a flat tire right afterwards, the bad gas caused it? Nice logic there.
--beaups
Click to expand...
Click to collapse
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
SaschaElble said:
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
Click to expand...
Click to collapse
It is pointless indeed. We have the code, we know exactly what it is capable of, and its not capable of what's happened here. Argue all you want, you just continue to reinforce you have no clue how these devices work.
--beaups
Sent from my XT1254 using Tapatalk
Fine, I'm done.
SaschaElble said:
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
Click to expand...
Click to collapse
1) this isnt a bootloader issue, its an emmc issue, pretty dang obvious, i can see it from 30k feet up
2) I found his device ID, he never purchased sunshine (ask him), SunShine never actually ran on the device, because he never purchased it, SunShine never touched his device, just the purchasing framework (Which tests for root, basic compatibility etc) ran, and it doesnt touch anything.
Sanity tests can't cause harm?
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Either way the timing still sucks

Moto x returning to stock

I Have Tried Everything But I Keep Getting This Failure In Flashing Partition . My Dad Is Getting Really Upset Reply Fast
G:\Moto X>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.248s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.117s
G:\Moto X>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.379s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.215s]
finished. total time: 5.605s
G:\Moto X>fastboot flash logo.bin
unknown partition 'logo.bin'
error: cannot determine image filename for 'logo.bin'
G:\Moto X>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
G:\Moto X>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.945s]
writing 'recovery'...
OKAY [ 1.203s]
finished. total time: 2.156s
G:\Moto X>mfastboot flash system system.img
'mfastboot' is not recognized as an internal or external command,
operable program or batch file.
G:\Moto X>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54276 KB)...
OKAY [ 3.674s]
writing 'modem'...
OKAY [ 3.582s]
finished. total time: 7.275s
G:\Moto X>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.462s]
finished. total time: 0.473s
G:\Moto X>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.488s]
finished. total time: 0.494s
G:\Moto X>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.339s]
writing 'fsg'...
OKAY [ 0.832s]
finished. total time: 1.183s
G:\Moto X>fastboot erase userdata
(bootloader) Variable not supported!
erasing 'userdata'...
OKAY [ 1.019s]
finished. total time: 1.027s
G:\Moto X>fastboot erase cache
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 0.792s]
finished. total time: 0.797s
G:\Moto X>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.328s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.344s
G:\Moto X>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.453s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.546s]
finished. total time: 6.006s
G:\Moto X>fastboot flash logo.bin
unknown partition 'logo.bin'
error: cannot determine image filename for 'logo.bin'
G:\Moto X>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
G:\Moto X>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.933s]
writing 'recovery'...
OKAY [ 1.203s]
finished. total time: 2.142s
G:\Moto X>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1394581432 bytes
error: cannot load 'system.img': Not enough space
G:\Moto X>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54276 KB)...
OKAY [ 3.666s]
writing 'modem'...
OKAY [ 3.596s]
finished. total time: 7.293s
G:\Moto X>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.469s]
finished. total time: 0.484s
G:\Moto X>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.469s]
finished. total time: 0.469s
G:\Moto X>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.339s]
writing 'fsg'...
OKAY [ 0.829s]
finished. total time: 1.190s
G:\Moto X>fastboot erase userdata
(bootloader) Variable not supported!
erasing 'userdata'...
OKAY [ 1.031s]
finished. total time: 1.047s
G:\Moto X>fastboot erase cache
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 0.797s]
finished. total time: 0.813s
G:\Moto X>
What are you trying to do? Dowgrade to kk?
Moderator Edit:
Please use "Quick Reply" rather than "Reply" so we don't have to edit the entire OP as a quote and thus get some page real estate back. And improve page load times. Thanks.
YedanyXD said:
What are you trying to do? Dowgrade to kk?
Moderator Edit:
Please use "Quick Reply" rather than "Reply" so we don't have to edit the entire OP as a quote and thus get some page real estate back. And improve page load times. Thanks.
Click to expand...
Click to collapse
I tried with the version on my dad's phone which was 5.1 still doesn't work. I had a backup in twrp and when I restore with that it says unable to wipe psg and phone doesn't boot.
xXAmartyAXx said:
I tried with the version on my dad's phone which was 5.1 still doesn't work. I had a backup in twrp and when I restore with that it says unable to wipe psg and phone doesn't boot.
Click to expand...
Click to collapse
Do you have bootloader unlocked? Downgrade to kk or reinstall stock 5.1 by cmd
YedanyXD said:
Do you have bootloader unlocked? Downgrade to kk or reinstall stock 5.1 by cmd
Click to expand...
Click to collapse
Boot loader unlocked
First tried to install kk accidentally then installed 5.1 by cmd but it is stuck in boot loader unlocked screen

my moto x4 xt1900-2 is bricked ...

here is my story,
i am just locking my bootloader after locking bootloader i am flashing my stock rom when i tried to flash my stock rom i get an error it says {bootloader} flash permission denied
i wont able to turn on my phone when i turn on my phone it shows your device is corrupt,
in fastboot mode showing flashing_locked
please helpp mee please what can i dooo plzzzz help...
sorry for my bad english..
Sounds like the flash that didn't take relocked the bootloader.
Have you tried unlocking it again via fastboot?
d_mouse81 said:
Sounds like the flash that didn't take relocked the bootloader.
Have you tried unlocking it again via fastboot?
Click to expand...
Click to collapse
yess i tried unlocking but it says you need to turn on oem unlocking
iampkp said:
yess i tried unlocking but it says you need to turn on oem unlocking
Click to expand...
Click to collapse
Try fastboot oem fb_mode_set before flashing and fastboot oem fb_mode_clear after flashing everything
Zokhii said:
Try fastboot oem fb_mode_set before flashing and fastboot oem fb_mode_clear after flashing everything
Click to expand...
Click to collapse
not working bro i tried..
still showing {bootloader} flash permission denied
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot devices
ZY224GW5SN fastboot
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot oem fb_mode_set
OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.007s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.124s]
Finished. Total time: 0.428s
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.285s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
Finished. Total time: 0.464s
see this
help me plz
iampkp said:
not working bro i tried..
still showing {bootloader} flash permission denied
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot devices
ZY224GW5SN fastboot
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot oem fb_mode_set
OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.007s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.124s]
Finished. Total time: 0.428s
C:\Users\acer\Desktop\PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.285s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
Finished. Total time: 0.464s
see this
help me plz
Click to expand...
Click to collapse
Do you remember your latest installed stock rom? Was it 8.0.0 or 8.1.0? It is possible that you try to flash an older image and downgrading doesn't work. You could try to flash this one, it is the latest retail version https://androidfilehost.com/?fid=1322778262904007756. Since you have the 1900-2 variant, I don't know if it will work.. I use it on my 1900-7 and everything is absolutely fine
Zokhii said:
Do you remember your latest installed stock rom? Was it 8.0.0 or 8.1.0? It is possible that you try to flash an older image and downgrading doesn't work. You could try to flash this one, it is the latest retail version https://androidfilehost.com/?fid=1322778262904007756. Since you have the 1900-2 variant, I don't know if it will work.. I use it on my 1900-7 and everything is absolutely fine
Click to expand...
Click to collapse
i am trying to flash this img https://androidfilehost.com/?fid=1322778262903985819
i will try your img but i dont think so that it will work because
see this image
https://drive.google.com/file/d/18ycgD83N8nPmCW5N8FDeRLZy5h-C-VVW/view?usp=sharing
and ty for replying and helping.....
Zokhii said:
Do you remember your latest installed stock rom? Was it 8.0.0 or 8.1.0? It is possible that you try to flash an older image and downgrading doesn't work. You could try to flash this one, it is the latest retail version https://androidfilehost.com/?fid=1322778262904007756. Since you have the 1900-2 variant, I don't know if it will work.. I use it on my 1900-7 and everything is absolutely fine
Click to expand...
Click to collapse
just now i flashed this latetst rom and still its failed
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
ZY224GW5SN fastboot
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (37 KB)...
OKAY [ 0.002s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.112s]
finished. total time: 0.114s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.224s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.303s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (94843 KB)...
OKAY [ 2.098s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.116s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (5680 KB)...
OKAY [ 0.124s]
writing 'fsg_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.129s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bluetooth BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4564 KB)...
OKAY [ 0.101s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.126s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp dspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.362s]
writing 'dsp_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (2153 KB)...
OKAY [ 0.050s]
writing 'logo_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.054s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516148 KB)...
OKAY [ 11.385s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.390s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (523975 KB)...
OKAY [ 11.544s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.549s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (520973 KB)...
OKAY [ 11.540s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.545s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (523236 KB)...
OKAY [ 11.564s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.569s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (522092 KB)...
OKAY [ 11.523s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.527s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (487698 KB)...
OKAY [ 10.808s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 10.814s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (524133 KB)...
OKAY [ 11.573s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.577s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (222582 KB)...
OKAY [ 4.925s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.929s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system_b system_other.img
target reported max download size of 536870912 bytes
sending 'system_b' (134369 KB)...
OKAY [ 2.975s]
writing 'system_b'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.983s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (210797 KB)...
OKAY [ 4.677s]
writing 'oem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.683s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase carrier
erasing 'carrier'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\acer\Desktop\last tryy\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\PAYTON_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
this is what its showing ...
Try the whole process on a different computer with USB 2.0 ports and maybe with mfastboot instead of regular fastboot - I had the same issue, flashing failed every time until I tried it on a older computer
Zokhii said:
Try the whole process on a different computer with USB 2.0 ports and maybe with mfastboot instead of regular fastboot - I had the same issue, flashing failed every time until I tried it on a older computer
Click to expand...
Click to collapse
bro I tried In my computer laptop and my frnds laptop but the same problem Is showing
how should I change flashing_locked status in fastboot mode
I tried this cmd fastboot flashing unlock but it says turn on OEM unlocking but I am unable to do anything how i can I turn on OEM unlocking in developer option..
help me.
iampkp said:
bro I tried In my computer laptop and my frnds laptop but the same problem Is showing
how should I change flashing_locked status in fastboot mode
I tried this cmd fastboot flashing unlock but it says turn on OEM unlocking but I am unable to do anything how i can I turn on OEM unlocking in developer option..
help me.
Click to expand...
Click to collapse
Yeah I understand you but flashing unmodified stock images should work - even with locked bootloader...
Zokhii said:
Yeah I understand you but flashing unmodified stock images should work - even with locked bootloader...
Click to expand...
Click to collapse
yes but it wont worked now moto service center is telling me that you have hardware issue....
you have to change motherboard....
is it right???
iampkp said:
yes but it wont worked now moto service center is telling me that you have hardware issue....
you have to change motherboard....
is it right???
Click to expand...
Click to collapse
You could always try doing a blank flash. There are files here, cannot say if it will help:
https://forum.xda-developers.com/moto-x4/help/moto-x4-hardbrick-blank-flash-t3857803
or this
https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529
Good luck
iampkp said:
bro I tried In my computer laptop and my frnds laptop but the same problem Is showing
how should I change flashing_locked status in fastboot mode
I tried this cmd fastboot flashing unlock but it says turn on OEM unlocking but I am unable to do anything how i can I turn on OEM unlocking in developer option..
help me.
Click to expand...
Click to collapse
In my XT1900-1 I have this status: oem_locked
Still no chances to load any firmware.
When running this command, system says:
fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (487698 KB)...
OKAY [ 10.948s]
writing 'system'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.020s
And that's where the process stops.
have the same problems
fastboot & mfastboot FAILED (remote failure)

Moto G5S Plus sanders 1802 in need of a mmcblk0 file ?

Hey guys, recently I hard bricked my sanders 1802 in way that everything I tried does not work.
After I flashed lineage 16.0, the fingerprint sensor and some other things were not working, then I tried downgrading it back to stock via fastboot, Sanders retail 8.1.
After that everthing went to hell. It got into bootloop. So i tried to restore it via Leonovo Moto Smart Assistant. Went back to bootloop and started showing some cache mount issues.
I tried over 10 different ROMs and every time it showed cache mout problems or ERROR 6, 7 and 1 in TWRP and sometimes kernel issues.
I've already tried flashing new kernels, tried every ERROR 6 and 7 solutions that are available online and nothing happens.
Right now I have it at the best shape possible, it has the latest TWRP installed (3.2.1 sanders r20), it does not show any cache nor kernel errors when I try to install a ROM, but it keeps giving me the ERROR 7 even when I delete the assert line on the updater-script file.
Searching the XDA foruns I found someone talking about getting a fresh start for the phone by flash the sdcard with mmcbk0.img. I'm not even sure if that's the right path to solve my problem, but I thought I give it a try since I have no idea what else to do.
I'm pretty noob on everything regarding android, just followed everything easily when it comes to tutorials.
Can someone please help me? Is the new mmcbk0.img file the right path or should I try somthing else? I talked to a "expert" guy here in my city and he said that the phone is gone and there's nothing I can do. Is it possible?
Have you tried TWRP 3.3
pradeeppk said:
Have you tried TWRP 3.3
Click to expand...
Click to collapse
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
voliveira92 said:
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
Click to expand...
Click to collapse
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
pradeeppk said:
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
Click to expand...
Click to collapse
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
voliveira92 said:
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
Click to expand...
Click to collapse
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
HTML:
pradeeppk said:
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
Click to expand...
Click to collapse
I'm pretty sure that I'm not missing anything.
I was able to flash Twrp 3.3.0 from this thread (https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-3-0-t3940378), but now it keeps giving me Error 7 and 'unable to mount system'.
Tried lineage and Havocs ROM. Tried altering the assert line again and no changes.
pradeeppk said:
Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there.
Click to expand...
Click to collapse
Wrong command format
voliveira92 said:
it gives me this error message:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
D302Thakur said:
Wrong command format
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
Click to expand...
Click to collapse
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
voliveira92 said:
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
Click to expand...
Click to collapse
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
pradeeppk said:
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
Click to expand...
Click to collapse
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
voliveira92 said:
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
Click to expand...
Click to collapse
Those are the lines that came with error. The phone went on a bootloop after clearing the cache and userdata.
platform-tools>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (504333 KB)...
OKAY [ 11.743s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.804s
platform-tools>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (495479 KB)...
OKAY [ 11.539s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 15.942s
platform-tools>fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system' (65436 KB)...
OKAY [ 1.528s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.552s
platform-tools>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (335882 KB)...
OKAY [ 7.802s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.841s
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
pradeeppk said:
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
Click to expand...
Click to collapse
Ok, so I repaired system file, formated data, cache and system and tried to flash from TWRP and fastboot.
On TWRP I got the same ERROR 7 as always (tried Pixel Experience and Havoc OS, as well stock firmware Sanders_NPS26.1):
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Tried again editing the assert line and the same ERROR 7 anyway.
And via fastboot (stock firmware) I got this and the phone went on bootloop after rebooting:
fastboot oem fb_mode_set
...
OKAY [ 0.004s]
finished. total time: 0.004s
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.073s
fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.704s]
finished. total time: 0.828s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.109s]
finished. total time: 0.163s
fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.419s]
finished. total time: 0.816s
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.496s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.511s]
finished. total time: 1.007s
fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.385s]
writing 'dsp'...
OKAY [ 0.286s]
finished. total time: 0.670s
fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (327830 KB)...
OKAY [ 7.627s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.669s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (524260 KB)...
OKAY [ 12.189s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.260s
fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (522314 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 6.230s]
finished. total time: 18.391s
fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (522269 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 7.196s]
finished. total time: 19.356s
fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (524204 KB)...
OKAY [ 12.207s]
writing 'system'...
OKAY [ 6.143s]
finished. total time: 18.349s
fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (524139 KB)...
OKAY [ 12.211s]
writing 'system'...
OKAY [ 6.929s]
finished. total time: 19.141s
fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (435100 KB)...
OKAY [ 10.111s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.502s
fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (75360 KB)...
OKAY [ 1.758s]
writing 'modem'...
OKAY [ 1.088s]
finished. total time: 2.846s
fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (2452 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 0.118s]
finished. total time: 0.178s
fastboot erase cache
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.018s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.334s]
finished. total time: 0.334s
fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot oem fb_mode_clear
...
OKAY [ 0.118s]
finished. total time: 0.118s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.131s]
finished. total time: 0.185s
I have the option of switching the system file to another format on TWRP (EXT2, EXT3, EXT4, FAT, exFAT, F2Fs), could any of those help?
voliveira92 said:
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
D302Thakur said:
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Ok, so I tried the stock you recomended and used the codes you provided.
Here's what I got. Frozen at boot screen. Tried from -fastboot- and -minimal adb and fastboot-.
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.000s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.002s]
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.057s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.519s]
finished. total time: 0.641s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71941 KB)...
OKAY [ 1.678s]
writing 'modem'...
OKAY [ 0.980s]
finished. total time: 2.658s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3024 KB)...
OKAY [ 0.071s]
writing 'fsg'...
OKAY [ 0.120s]
finished. total time: 0.191s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.382s]
writing 'dsp'...
OKAY [ 0.254s]
finished. total time: 0.637s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.097s]
finished. total time: 0.150s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.396s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.357s]
finished. total time: 0.754s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.490s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.452s]
finished. total time: 0.942s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.097s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.099s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (249863 KB)...
OKAY [ 5.809s]
writing 'system'...
OKAY [ 2.935s]
finished. total time: 8.744s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (260323 KB)...
OKAY [ 6.091s]
writing 'system'...
OKAY [ 3.729s]
finished. total time: 9.820s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.105s]
writing 'system'...
OKAY [ 3.309s]
finished. total time: 9.414s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 6.098s]
writing 'system'...
OKAY [ 3.106s]
finished. total time: 9.203s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.097s]
writing 'system'...
OKAY [ 2.928s]
finished. total time: 9.025s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.104s]
writing 'system'...
OKAY [ 2.986s]
finished. total time: 9.090s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (255675 KB)...
OKAY [ 5.971s]
writing 'system'...
OKAY [ 3.487s]
finished. total time: 9.459s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (242629 KB)...
OKAY [ 5.647s]
writing 'system'...
OKAY [ 2.830s]
finished. total time: 8.478s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (239745 KB)...
OKAY [ 5.575s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 6.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (65436 KB)...
OKAY [ 1.518s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.520s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (135426 KB)...
OKAY [ 3.150s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.153s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.009s]
finished. total time: 0.009s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.124s]
finished. total time: 0.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.001s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot
rebooting...
finished. total time: 0.001s
voliveira92 said:
fastboot flash system system.img_sparsechunk.0
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.9
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.10
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash oem oem.img
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
D302Thakur said:
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
Click to expand...
Click to collapse
Brazil, model XT1802
voliveira92 said:
Brazil, model XT1802
Click to expand...
Click to collapse
Can anyone please help me with this? I'm almost giving up on this device but I can't accept that there's nothing else I can try.

Categories

Resources