Database Develop

Moto G XT1068 2014 bricked and stuck in fastboot

I tried to flash my Moto G XT1068 from Android Open Source Project (AOSP) 5.1.1 to the stock firmware and relock the bootloader.
I followed these steps I found on a website:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
After I had typed those to the command prompt on the folder I had placed the firmware and mfastboot v2 I found out that the phone didnt reboot, and that it was stuck in the fastboot mode where it says failed to validate system image and something about falling-through boot mode or something.
I read the text again carefully that I didn't do anything wrong, and I didnt. I went to the comments and there were people complaining that it doesnt work and you need to add one command more
mfastboot.exe flash system system.img_sparsechunk.3
well I did type that to the command prompt and it did nothing after I tried to reboot again, so I typed all the commands again including the command I mentioned, and still nothing.
now I'm stuck in the fastboot mode where it says:
Failed to validate system image
Fastboot reason: fall-through from not charger boot mode
I'm begging for immediate help

I got the bootloader re-unlocked
I got the phone's bootloader re-unlocked
I'll keep posting more info If I dont solve this mess myself

Munkkimake said:
I tried to flash my Moto G XT1068 from Android Open Source Project (AOSP) 5.1.1 to the stock firmware and relock the bootloader.
I followed these steps I found on a website:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
After I had typed those to the command prompt on the folder I had placed the firmware and mfastboot v2 I found out that the phone didnt reboot, and that it was stuck in the fastboot mode where it says failed to validate system image and something about falling-through boot mode or something.
I read the text again carefully that I didn't do anything wrong, and I didnt. I went to the comments and there were people complaining that it doesnt work and you need to add one command more
mfastboot.exe flash system system.img_sparsechunk.3
well I did type that to the command prompt and it did nothing after I tried to reboot again, so I typed all the commands again including the command I mentioned, and still nothing.
now I'm stuck in the fastboot mode where it says:
Failed to validate system image
Fastboot reason: fall-through from not charger boot mode
I'm begging for immediate help
Click to expand...
Click to collapse
As far as I can see, you didn't lock the bootloader corectly, use this: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657

I have same problem, I had to unlock the bootloader again and it worked like normal. I ended up reflashing twrp and going back to 5.1.1 aosp rom. To clarify your phone is probably not bricked. Re unlock the bootloader with fastboot oem unlock {unique code} and flash twrp and the rom of your choice.

ethanchow said:
I have same problem, I had to unlock the bootloader again and it worked like normal. I ended up reflashing twrp and going back to 5.1.1 aosp rom. To clarify your phone is probably not bricked. Re unlock the bootloader with fastboot oem unlock {unique code} and flash twrp and the rom of your choice.
Click to expand...
Click to collapse
-----Update----
I think I have it fixed: just flash the system images again after you do
Code:
fastboot oem lock
You seem to have to flash them twice
Code:
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

ethanchow said:
-----Update----
I think I have it fixed: just flash the system images again after you do
Code:
fastboot oem lock
You seem to have to flash them twice
Code:
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
Click to expand...
Click to collapse
you found this to be working? What firmware file are you using?

ethanchow said:
-----Update----
I think I have it fixed: just flash the system images again after you do
Code:
fastboot oem lock
You seem to have to flash them twice
Code:
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
Click to expand...
Click to collapse
and in that code you arent using mfastboot? Is there no use for it?

Munkkimake said:
you found this to be working? What firmware file are you using?
Click to expand...
Click to collapse
I am using lastest one for xt1064 from here forum.xda-developers.com/moto-g-2014/orig-development/original-motorola-firmware-collection-t3153533
For adb and fastboot I am using the 15 second installer, no mfastboot.
I managed to successfully relock the bootloader and get the phone to boot to stock rom but the "unlock warning" boot logo still appears.

ethanchow said:
I am using lastest one for xt1064 from here forum.xda-developers.com/moto-g-2014/orig-development/original-motorola-firmware-collection-t3153533
For adb and fastboot I am using the 15 second installer, no mfastboot.
I managed to successfully relock the bootloader and get the phone to boot to stock rom but the "unlock warning" boot logo still appears.
Click to expand...
Click to collapse
you think that the unlock warning could somehow be removed with a locked bootloader?

Munkkimake said:
you think that the unlock warning could somehow be removed with a locked bootloader?
Click to expand...
Click to collapse
i don't know if works on stock bootloader locked, but you can try after you are on stock rom the command
mfastboot.exe flash logo logo.bin
with a modify boot logo like this but dont know if will works on locked bootloader...
if you try and the command is accepted and the device don't boot use the command again with the logo.bin file that is in the stock XML zip that you download.
in the case of not be able to flash and error that you described on OP.
before do the commands you need to check how many system.img_sparsechunk files you have and change the commands line according.
Motorola stock rom's may have up to 6 of those file maybe more in the future, the 5x.x have 4 to 6 so you need to add the lines in the script before:
mfastboot.exe flash modem NON-HLOS.bin
the rest doesn't change

All you need is
this official firmware of XT1068 https://drive.google.com/file/d/0Bzr0qvz6uRerOGRfOEptU2p0ZkU/view?usp=sharing
This is the complete zip which is having mfastboot v2 also in that and you just now need to flash below commands correctly, and you're done.
Code:
------------------------------------------------------------------|
Moto G 2014 Stock 5.0.2 Restore Script
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
hope this'll help you out
Also if you wanna get rid of that "Unlocked Warning" boot logo, you can easily flash any of the logo.bin file successfully on a locked bootloader too. So you can flash your own bootlogo, custom or stock, as you prefer.
Thanks

Thanks!
ArtRahul said:
this official firmware of XT1068 https://drive.google.com/file/d/0Bzr0qvz6uRerOGRfOEptU2p0ZkU/view?usp=sharing
This is the complete zip which is having mfastboot v2 also in that and you just now need to flash below commands correctly, and you're done.
Code:
------------------------------------------------------------------|
Moto G 2014 Stock 5.0.2 Restore Script
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
hope this'll help you out
Also if you wanna get rid of that "Unlocked Warning" boot logo, you can easily flash any of the logo.bin file successfully on a locked bootloader too. So you can flash your own bootlogo, custom or stock, as you prefer.
Thanks
Click to expand...
Click to collapse
Well I got the stock firmware through an automatic installer and yes the phone let me flash the logo.bin waiting for the official 5.1

Munkkimake said:
Well I got the stock firmware through an automatic installer and yes the phone let me flash the logo.bin waiting for the official 5.1
Click to expand...
Click to collapse
with locked bootloader you flash the logo.bin and the logo warning disappeared?

Yes and it worked! I have no longer proof of that the warranty has been void / the warranty is back
Sent from my XT1068 using XDA Free mobile app

Munkkimake said:
Yes and it worked! I have no longer proof of that the warranty has been void / the warranty is back
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
ok is nice to know that works. But only to remove that warning thing...
Because the bootloader have 3 stats:
Status code 0 =locked with warranty
Status code 3 = unlocked without warranty
Status code 2= relocked but also without warranty
check in the bootloader screen yours must be 2...
Status code 1 is unknown.

baybutcher27 said:
ok is nice to know that works. But only to remove that warning thing...
Because the bootloader have 3 stats:
Status code 0 =locked with warranty
Status code 3 = unlocked without warranty
Status code 2= relocked but also without warranty
check in the bootloader screen yours must be 2...
Status code 1 is unknown.
Click to expand...
Click to collapse
Oh, according to that, the tool program which installed the firmware, didnt lock the bootloader. I assumed that it was locked cause i was told that the bootloader warning still exists after relocking so...
Sent from my XT1068 using XDA Free mobile app

No OS Can't Boot

So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.

Speedy712 said:
So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.
Click to expand...
Click to collapse
So you have the Motorola USB drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Recent versions of ADB/Fastboot.
Latest stock firmware:
firmware.center/firmware/Motorola/Moto%20X%20%282nd%20gen-2014%29/Stock/XT1096/
Probably VICTARA_VERIZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml.zip
Extract the firmware and put the 4 ADB/Fastboot files in the folder with the firmware files.
Boot into Bootloader Mode and connect the phone, make sure the phone says "connected..."
Shift + right-click inside that folder, Open command window here... Paste these commands, BUT CHECK THE NUMBER of sparsechunks your firmware has:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear

Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!

Speedy712 said:
Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!
Click to expand...
Click to collapse
You're welcome, glad it worked!
If you want to try custom roms again, I've been using TWRP 3.0.2-1 and it seems to have no issues so far (and I'm running the latest CM Nightlies).

Gus Ghanem said:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
so with this method you dont have to use the motofastboot?

fakieskr8333 said:
so with this method you dont have to use the motofastboot?
Click to expand...
Click to collapse
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.

Gus Ghanem said:
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.
Click to expand...
Click to collapse
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.

fakieskr8333 said:
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.
Click to expand...
Click to collapse
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?

Gus Ghanem said:
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?
Click to expand...
Click to collapse
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?

fakieskr8333 said:
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?
Click to expand...
Click to collapse
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.

Gus Ghanem said:
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.
Click to expand...
Click to collapse
Thanks, I am at work now but as soon as I get home I will give it a go. I have been on iOS for over a year now and my moto has been dead since about a month after moto allowed us to unlock the verizon variant. Stupid thing lol.

how do I check the amount of sparsechunks that I have. Sorry for the dumb question
---------- Post added at 02:04 PM ---------- Previous post was at 01:44 PM ----------
I just finished doing this. I am kind of a noob at this so bear with me. I tried this and I get this message that says "Boot up failed" when I try normal powerup. I'm kind of scared..

ABSOLUTE LEGEND
i was stuck since almost 36 hours, good i dint lose hope and smash the x against the wall
YOUR A LIFE SAVER Fakieskr

Moto x stuck at bootloader warning screen and won't go anywhere else.

So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.

Slupvee said:
So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.
Click to expand...
Click to collapse
It's always a good idea to put your phone in bootloader mode and do:
fastboot getvar all
So you get all the specs of your phone, and copy the info into a Notepad file.
Did you try reflashing TWRP (twrp-3.0.2-1-victara.img)?
If that's not working, you may be able to reflash stock firmware.
https://firmware.center:8081/firmware/Motorola/
Something like this:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.

Slupvee said:
thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.
Click to expand...
Click to collapse
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?

Gus Ghanem said:
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?
Click to expand...
Click to collapse
Verizon moto x 2014 5.1

Hey did u fixed it?

Moto G6 XT1925-6 - NO RECOVERY & Reboots to bootloader

As the title says, I have no recovery and can't seem to restore the stock recovery. Also, when I boot/reboot the phone, it goes to fastboot mode. Then if I select START, it will boot to the system.
I purchased this phone used and the bootloader was already unlocked. I installed TWRP, rooted it and set it up. When I put my sim in, I could send & receive text messages and mms messages, but I was unable to talk or hear anything while on a voice call. The call is placed and/or received fine. However, once connected, I cannot hear anything nor can anyone hear me.
I want to return for a refund and have restored to factory per this guide. (the problem persists). However, I do not have a recovery. Flashing the stock recovery thru ADB appears to work but trying to boot to it goes to fastboot mode. I cannot boot/reboot the phone without it going to fastboot, then I have to select START to boot to the system. If I cannot correct these problems I will not be able to return the phone...and I can't use it as is because of the phone issue.
Thanks...and help!

Did the phone work fine when you got it?
Sent from my Moto G6 Plus using Tapatalk

Relock-it
Remember you need root to do this and usb-debugging and OEM-unlock enabled in syste settings
Download firmware ALI_RETAIL_8.0.0_OPS27.104-15-10-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
and assuming you know were to extract it to, run this command:
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 bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot and run this command ONE BY ONE and wait for each one to finish before adding the next one
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot oem fb_mode_clear

Xplorer4x4 said:
Did the phone work fine when you got it?
Click to expand...
Click to collapse
Booting up and recovery...yes.
xjunior said:
RELOCK IT
Click to expand...
Click to collapse
What will that do for me? I still don't have a recovery.
xjunior said:
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot
Click to expand...
Click to collapse
I don't understand this. How do I erase fastboot reboot? It's a command to reboot.

if you use the firmware from the guide you show in the first post is probably not the right one for your device, I have exactly same model and took me a wile to figure out how to factory reset and relock it.
yes you gonna put the first commands all at once ,
then in the cmd terminal its gonna be the last command "fastboot reboot" but do not press enter otherwise it will reboot,
erase it and
add the second part of the command, line by line not all at once like the first part.
this will bring you device back to factory and relock the bootloader ,

xjunior said:
yes you gonna put the first commands all at once ,
then in the cmd terminal its gonna be the last command "fastboot reboot" but do not press enter otherwise it will reboot,
erase it and
add the second part of the command line by line .
this will bring you device back to factory and relock the bootloader ,
Click to expand...
Click to collapse
OK. Understood. But how will relocking the bootloader help me? It reboots to fastboot...it doesn't reboot to the system/OS. What I need is a recovery to somehow be flashed and to "stick".

mn1968 said:
OK. Understood. But how will relocking the bootloader help me? It reboots to fastboot...it doesn't reboot to the system/OS. What I need is a recovery to somehow be flashed and to "stick".
Click to expand...
Click to collapse
the last command will fix that I had same problem.
if you fallow this guide.
fastboot oem fb_mode_clear
If you want to return the Phone you will need to relock the bootloader other wise they will blame you for messing up the phone.

xjunior said:
the last command will fix that I had same problem.
if you fallow this guide.
fastboot oem fb_mode_clear
If you want to return the Phone you will need to relock the bootloader other wise they will blame you for messing up the phone.
Click to expand...
Click to collapse
OK, with your help I am back in business! I actually re-followed this guide up to step 5. I then ran:
fastboot oem fb_mode_clear
I can have the phone reboot normally now! Thank you very much!!!
As far as returning, I got it used on eBay. The bootloader was already unlocked. It's the phone that doesn't work for actual calls. I just need/wanted to return it exactly like it was.
Thanks again for your help!

My pleasure

mn1968 said:
OK, with your help I am back in business! I actually re-followed this guide up to step 5. I then ran:
fastboot oem fb_mode_clear
I can have the phone reboot normally now! Thank you very much!!!
As far as returning, I got it used on eBay. The bootloader was already unlocked. It's the phone that doesn't work for actual calls. I just need/wanted to return it exactly like it was.
Thanks again for your help!
Click to expand...
Click to collapse
After reflashing stock with OPS27.82-72 (came with OPS27.82-19-4), the phone now actually works too. Very weird. I may have/want to keep the phone now.

Failed to verify Hab Image Boot

First im trying to reinstall stock firmware on a model XT1925-3, from a friend.
It was stuck at Moto Logo, i tried everything you could imagine to make it work. Nothing happens. The things I tried:
-It have locked bootloader (i cant unlock because i cant boot to "Allow OEM").
-Tried all 8 RETBR firmwares (https://mirrors.lolinet.com/firmware/moto/ali/official/RETBR/) and none worked.
-Trying the following commands:
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 flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
It goes very well, but after restart, it backs to fastboot screen and cant boot.
-Tried another cable, tried another PC, tried another port
-Attached the screen it is now
If theres anything you can do to help me. I appreciated

There's nothing wrong with your cable, your PC or something else! Otherwise you can't even process the first the command in fastboot.
So first thing I would do is booting into recovery. Although it's the stock one it will be very useful to get detailed information in your case.
Once in fastboot mode use the Vol -/+ keys to navigate to reboot to recovery and press power. Then have a look at the logs provided by the recovery. There should be two different kinds of logs - the kernel log and the recovery.log. Choose kernel.log (maybe it's called last_dmsg.log or sth like that). It provides the most detailed information on Android and why you're stuck in a bootloop. Be aware that it has more than one page which will be shown up. Have a look at the left corner on the bottom. Don't expect to find the major error on the last lines, but somewhere in the last 150 lines.
That's one thing you can do.
Another advise is to give the repair tool a chance which is mentioned in your screenshot. This is a really good option in your case.
Good luck!!