Database Develop

[Q] Help: Device locked: 5.1 fastboot flash fails

I have a Moto-maker-made Moto X with T-mobile sim (I think XT1053) and never installed any custom ROMs. The soak from couple weeks ago soft-bricked the phone (factory reset from fastboot menu just powers off the phone). I can get into fastboot, but the device is locked (status code 0). Do I have to unlock it in order to apply the factory image? The steps below fail currently.
I got the TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz from motorola, and ran all fastboot steps until "fastboot flash boot boot.img" which failed:
Windows output:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.913s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.664s
Phone output:
Failed to hab check for boot: 0x56
preflash validation failed for boot

gromul said:
I have a Moto-maker-made Moto X with T-mobile sim (I think XT1053) and never installed any custom ROMs. The soak from couple weeks ago soft-bricked the phone (factory reset from fastboot menu just powers off the phone). I can get into fastboot, but the device is locked (status code 0). Do I have to unlock it in order to apply the factory image? The steps below fail currently.
I got the TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz from motorola, and ran all fastboot steps until "fastboot flash boot boot.img" which failed:
Windows output:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.913s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.664s
Phone output:
Failed to hab check for boot: 0x56
preflash validation failed for boot
Click to expand...
Click to collapse
your bootloader must be unloced

Thanks, that fixed it.

Moto G 2014 softbrick, should I let the phone rest in peace?

Hello, I got the MotoG 2014 from Amazon in the US, it came with Kitcat and in the first week it installed the OTA for Lollipop, and I was very happy with my purchase then after a couple of months it started to update something while on low battery and then the phone died, I was out of the US so turning it back to Amazon was not possible. I couldn't do anything from the recovery so I unlocked it and found some RETUSGLB Lollipop ROM and flashed it using fastboot and it came back to life. After two weeks, while I was using it, the screen went black, it would boot up and stay on the Motorola animated logo, again the recovery wouldn't work, so I decided to flash the same Llollipop again, but this time the fastboot flash command only worked with the "fastboot flash partition gpt.bin" all the others (motoboot, boot, logo, recovery, etc) gave me an error:
(bootloader) Failed to flash
FAILED (remote failure)
I've tried many of the recommendations of the forum to no avail, right now when I try to boot up the MotoG normally, it stays in a garbled screen, I guess the logo image is corrupt. Tried to flash a different Lollipop ROM, but it fails to flash also. I can boot to fastboot and use some commands like "fastboot oem partition" and "fastboot getvar all". I don't say the MotoG is hardbricked because when is in fastboot the pc recognizes it as Moto g 2014 . I cannot install any of the custom recoverys because the flash into recovery fails, but I can boot up Cyanogenmod recovery into ram. Tried to install an update from the external SD card using CM but it gives error messages about being unable to mount files and directories, which leads me to think that the Linux file system is corrupted. Cannot use ADB because fastboot nor CM recovery have the option. Using ADB sideload from CM gives error about being unable to mount files and directories too.
Since the MotoG is useless now, and I'm loosing hope about this phone, and I'm mad at Motorora for the cheap quality of their engineering that allowed the phone to fail in the first place. I'm thinking about the procedure I've seen on the forum, but used on the Moto G 2013, the one that wipes the bootloader and then blankflash the phone, risking a Hardbrick. Some people in the forum says that blankflash for 2013 wouldn't work on the 2014, others say it would, from the emmc standpoit both devices seems the same to me.
Sorry for the long story. Any suggestion to recover the MotoG is appreciated.
Thanks in advance.

Don't know exactly what wrong.
Try this : http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
It should fix your problem (There is bootloader files included in the zip file so try flashing that.)
If you think my solution isn't good enough,, wait for someone who can tell you a proper answer. Peace.

I tried your suggestion but it failed to flash as other Roms did:
Code:
Easy Installer - Lollipop 5.x.x Moto G (2nd Gen) 2014
For XT1063, XT1064, XT1068 and XT1069
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel choose option 6
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 1
RETURNING TO STOCK ROM - FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
OKAY [ 0.319s]
finished. total time: 0.356s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.106s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 100.145s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.024s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.989s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.351s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.377s

linuxtron said:
I tried your suggestion but it failed to flash as other Roms did:
Code:
Easy Installer - Lollipop 5.x.x Moto G (2nd Gen) 2014
For XT1063, XT1064, XT1068 and XT1069
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel choose option 6
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 1
RETURNING TO STOCK ROM - FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
OKAY [ 0.319s]
finished. total time: 0.356s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.106s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 100.145s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.024s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.989s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.351s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.377s
Click to expand...
Click to collapse
Add me on Hangouts ( https://plus.google.com/108108436166506337243 ) or join #titandev at freenode.

Need help!! moto g6 forge (cricket) xt 1922-9 oficial original rom

Hi all,
I have a problem I have a moto g6 forge 16gb (cricket) I installed a different version (retail) to be exact but now the phone goes into fastboot mode and I get the following message: "start up failed, your device didn't star up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant ".
Now I can not enter the system, I need to reinstall the original system that I do not have or how I can fix the problem. What I know is that it's possible to fix, it if it's software no?
Can anybody help me?
Regards,

i tried this but no luck...
C:\Users\Ricardo\Desktop\platform-tools>fastboot oem fb_mode_set
OKAY [ 0.002s]
Finished. Total time: 0.004s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.011s]
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: '')
Finished. Total time: 0.114s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash bootloader bootloader.img
Sending 'bootloader' (7483 KB) OKAY [ 0.792s]
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.959s]
Finished. Total time: 1.770s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
Sending 'modem' (76974 KB) OKAY [ 5.679s]
Writing 'modem' OKAY [ 1.922s]
Finished. Total time: 7.621s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash fsg fsg.mbn
Sending 'fsg' (2380 KB) OKAY [ 0.307s]
Writing 'fsg' OKAY [ 0.175s]
Finished. Total time: 0.500s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash dsp adspso.bin
Sending 'dsp' (16384 KB) OKAY [ 1.843s]
Writing 'dsp' OKAY [ 0.483s]
Finished. Total time: 2.342s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash boot boot.img
Sending 'boot' (16384 KB) OKAY [ 0.867s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 1.116s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.0
Sending 'system' (521139 KB) OKAY [ 32.457s]
Writing 'system' (bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 32.604s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.1
Sending 'system' (504408 KB) OKAY [ 25.827s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 25.863s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.2
Sending 'system' (515109 KB) OKAY [ 23.901s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 24.041s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.3
Sending 'system' (487226 KB) OKAY [ 26.055s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 26.258s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash oem oem.img
Sending 'oem' (364938 KB) OKAY [ 19.066s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 19.144s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash vendor vendor.img
Sending 'vendor' (230306 KB) OKAY [ 11.192s]
Writing 'vendor' (bootloader) Security version downgrade
(bootloader) Image v failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 11.404s
C:\Users\Ricardo\Desktop\platform-tools>fastboot erase carrier
Erasing 'carrier' OKAY [ 0.120s]
Finished. Total time: 0.214s
C:\Users\Ricardo\Desktop\platform-tools>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.085s]
Finished. Total time: 0.098s
C:\Users\Ricardo\Desktop\platform-tools>fastboot erase DDR
Erasing 'DDR' OKAY [ 0.189s]
Finished. Total time: 0.203s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash logo logo.bin
Sending 'logo' (1423 KB) OKAY [ 0.096s]
Writing 'logo' OKAY [ 0.150s]
Finished. Total time: 0.260s
C:\Users\Ricardo\Desktop\platform-tools>fastboot oem fb_mode_clear
OKAY [ 0.003s]
Finished. Total time: 0.005s
C:\Users\Ricardo\Desktop\platform-tools>fastboot reboot

richi323 said:
Hi all,
I have a problem I have a moto g6 forge 16gb (cricket) I installed a different version (retail) to be exact but now the phone goes into fastboot mode and I get the following message: "start up failed, your device didn't star up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant ".
Now I can not enter the system, I need to reinstall the original system that I do not have or how I can fix the problem. What I know is that it's possible to fix, it if it's software no?
Can anybody help me?
Regards,
Click to expand...
Click to collapse
Well you can't Flash the retail firmware on that device. You need to flash the exact same firmware that was on the device before you bricked it. You can definitely use ADB and fastboot if you can get the phone into fastboot mode.
it's failing because you're trying to install an older firmware than the one you have. You're lucky it did not succeed flashing the GPT. That is the partition index. if you had successfully flash that and the bootloader from an older firmware than what you had you would have a hard brick on your hands with no chance of recovering it without a blank flash file.
Run
Fastboot getvar
To see what version of the software you have on your device. then use fastboot to flash the same or a newer version that is correct for your device.
Look here
https://mirrors.lolinet.com/firmware/moto/jeter/official/
Try cricket or att

madbat99 said:
Well you can't Flash the retail firmware on that device. You need to flash the exact same firmware that was on the device before you bricked it. You can definitely use ADB and fastboot if you can get the phone into fastboot mode.
it's failing because you're trying to install an older firmware than the one you have. You're lucky it did not succeed flashing the GPT. That is the partition index. if you had successfully flash that and the bootloader from an older firmware than what you had you would have a hard brick on your hands with no chance of recovering it without a blank flash file.
Run
Fastboot getvar
To see what version of the software you have on your device. then use fastboot to flash the same or a newer version that is correct for your device.
Look here
https://mirrors.lolinet.com/firmware/moto/jeter/official/
Try cricket or att
Click to expand...
Click to collapse
Hello and thanks for answering, yes i use this rom https://mirrors.lolinet.com/firmwar...ubsidy-CRICKET_regulatory-DEFAULT_CFC.xml.zip to restore my phoen but no luck, and retus rom the problem started but i see this rom is for moto g(6) play, i don´t know if cricket has another rom , my moto g6 forge has jeter OCP27.91-42 and I can not find that rom anywhere.
I have reviewed and donwloaded the att, retus and cricket but internally (3 roms) all are for moto g(6) play and tried with fastboot both with the same error result.
I've seen on Youtube a person who has moto G6 Forge with rom motorola/ jeter_a/jeter 8.0.0 /ocp27.91.41/43 and i think all the roms for this model should be the same but I can not find this rom.
sorry for my english i hope it is understood, any idea?

i have this with fastboot getvar all:
(bootloader) ro.build.fingerprint[0]: motorola/jeter_a/jeter:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-41/43:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.43.jeter_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0

richi323 said:
i have this with fastboot getvar all:
(bootloader) ro.build.fingerprint[0]: motorola/jeter_a/jeter:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-41/43:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.43.jeter_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
Click to expand...
Click to collapse
You may have yours updated to a build version that hasn't been released yet for download. I can't really help with that. You're supposed to check for a download of your current firmware before trying to flash anything. you're probably going to have to just wait until that firmware is either posted here in the Forum or uploaded to that website.

madbat99 said:
You may have yours updated to a build version that hasn't been released yet for download. I can't really help with that. You're supposed to check for a download of your current firmware before trying to flash anything. you're probably going to have to just wait until that firmware is either posted here in the Forum or uploaded to that website.
Click to expand...
Click to collapse
You are right, I thought that it was rom of my phone. It was the update of my phone and that with the retus I could return to retail but apparently I am still learning.
maybe someone upload the rom or I'll wait for it to be published, like you say.
pd. if it possible that make a rom with other moto g6 forge without root and install with fastboot with the bad moto g6 forge
Thank you,

today with XT1922-9_JETER_A_CRICKET_8.0.0_OCPS27.91-62-7_cid1_subsidy-CRICKET_regulatory-DEFAULT_CFC.xml my phone works again
i have a question, how can I do to unlock my moto g6 forge and use other sim?
I have tried to unlock (by code) it with 2 companies but they can not
regards

What commands do I need to put when I flash the rom? Thank you

HippiexPunk said:
What commands do I need to put when I flash the rom? Thank you
Click to expand...
Click to collapse
Use the commands in the file. You can use RSDlite with a Windows PC and it will flash it all for you. Or use RSDlite XML to batch to convert it to a .bat file for one click in fastboot. It converts it to a batch file to perform that flashes for you.
If you want to wipe data and start fresh, choose the flashfile.xml in the firmware. If you want to try to keep data, use the servicefile.xml.
If you are using official firmware, you don't need the bootloader unlocked
Find the tools here
Use RSDlite 6.2.4
works fine on windows 10.
Great tools on that page.
Get firmware from https.mirrors.lolinet.com

It looks like I'm in a similar situation. Today I went to upgrade my Cricket Moto G6 Play (XT1922-9) to Android Pie, which is available for the XT1922-9 but only for the RETUS channel. I ran the batch file in fastboot and received the "Preflash validation failed" on the boot, recovery and system partitions. Now the device only boots to the bootloader because it fails to validate the boot image. Likewise, recovery mode is inaccessible because it can't validate the recovery image. (Interestingly enough, neither of these images were actually flashed.)
Now the locked device seems completely bricked. Motorola wouldn't allow me to unlock the bootloader, and trying to flash the latest Oreo ROM for the Cricket channel also fails validation. (I had OCPS27.91-62-10 installed, but that doesn't seem to be available for download. I tried OCPS27.91-62-19.)
So am I really stuck on the bootloader with no inability to flash known-good (and properly signed) OEM firmware? How can Motorola create a system that's so fragile?

Moto G5S Plus | TWRP Bootloop

I've checked lots of other posts here, but none of them worked for me.
I've installed a somewhat quirky custom ROM (Pixel experience 12) on my Moto G5S Plus, and now I can't get into TWRP, because it bootloops.
When I try to erase/format any partition that might solve the problem from fastboot, I get:
> fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.000s
the same happens for recovery & userdata.
I can't reinstall stock ROM because the first command also doesn't work:
> flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
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.063s
Also, the custom ROM is working fine, the only problem is TWRP not starting.
Do you guys have any clue on how to solve this?

Made a mistake trying to flash my XT2041-4

I followed steps to install the original build onto my g power and wiped the partition but then the flashing the bootloader failed. Now I can see I needed to unlock the bootloader first and I had not done that. I wiped the partition. I can get the phone into fastboot and that is it. Trying to go into recovery mode fails with "No valid operating system could be found. The device will not boot."
My device is the XT2041-4 and I was intending to revert back to Android 10 and now I'm stuck. I'm not sure how to unlock the bootloader. What can I do to recover? Or is there a way to get a build back on it?
Code:
[email protected]:~/android/stockmoto$ fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.004s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.359s]
Finished. Total time: 0.364s
[email protected]:~/android/stockmoto$ sudo fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.444s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/stockmoto$

Dang, I got a code to unlock the bootloader but I didn't enable a setting before wiping the partition. Any tips?
Code:
[email protected]:~/android/stockmoto$ sudo fastboot oem unlock (code snipped)
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/stockmoto$