Database Info

[Q] Which Moto G stock firmware to use?

I'm looking to restore my Moto G to stock, but I don't know which version to choose.
Can anyone help me for which one I need because the one that I did flash, is the last one you see in the picture, and now my network (T-Mobile) isn't working anymore.
Also what is the difference between the AWSRetail.en.US and the Retail.en.US?

Model no. XT1032 is non-AWS. XT1034 is AWS. Only the later is compatible with T-Mobile’s 1700 (AWS) bands.

lost101 said:
Model no. XT1032 is non-AWS. XT1034 is AWS. Only the later is compatible with T-Mobile’s 1700 (AWS) bands.
Click to expand...
Click to collapse
Okay I really appreciate that info. Do you think you could by any chance help me fix the problem with my phone? It cant seem to connect to my carrier and the radio and gps is off. I really don't know how to fix this.. please help
And when I go into Settings>More...>Mobile Networks>Network Operators it tell says, "Error while searching for networks." And then when I try to press Choose Automatically, I get a message saying, " Your SIM card does not allow a connection to this network".
But that's not true because it has been working all this time.

Flash the AWSRetail.en.US stock firmware and everything should be fine again.

lost101 said:
Flash the AWSRetail.en.US stock firmware and everything should be fine again.
Click to expand...
Click to collapse
Are you sure? Because I actually have model no. XT1032
Also Im really sorry if I keep annoying you

Veyzo said:
Are you sure? Because I actually have model no. XT1032
Click to expand...
Click to collapse
How do you know this? All models state '1032' under About phone > Baseband version.
You have flashed the the retail XT1032 US stock firmware and radio is not working. That suggests a) have an XT1034 or b) you didn't flash correctly.

lost101 said:
How do you know this? All models state '1032' under About phone > Baseband version.
You have flashed the the retail XT1032 US stock firmware and radio is not working. That suggests a) have an XT1034 or b) you didn't flash correctly.
Click to expand...
Click to collapse
Yes I checked the Baseband version and it does say 1032. You might be right that it was flashed wrong, but Iv'e tried it about 3 times now it still isn't working.
Could you show me how to correctly flash it on a Mac? The guide I followed was the one here on xda-developers for the Moto G and I'm not sure what I could have done wrong, I really just need my network to work again.

Veyzo said:
Yes I checked the Baseband version and it does say 1032. You might be right that it was flashed wrong, but Iv'e tried it about 3 times now it still isn't working.
Could you show me how to correctly flash it on a Mac? The guide I followed was the one here on xda-developers for the Moto G and I'm not sure what I could have done wrong, I really just need my network to work again.
Click to expand...
Click to collapse
As I said, Baseband version is not an indicator of which model you have.
Fastboot flash: Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
As I said, Baseband version is not an indicator of which model you have.
Fastboot flash: Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Oh okay I understand. Well the way I know that it is XT1032 is because that is what it shows registered on my Google account. (check attached screenshot)

The answer is simple. Follow the guide, flash XT1032 firmware. If that doesn't work, flash XT1034 firmware.

lost101 said:
The answer is simple. Follow the guide, flash XT1032 firmware. If that doesn't work, flash XT1034 firmware.
Click to expand...
Click to collapse
Alright I will try doing that. Thanks for helping me

lost101 said:
The answer is simple. Follow the guide, flash XT1032 firmware. If that doesn't work, flash XT1034 firmware.
Click to expand...
Click to collapse
Okay so I flashed it, but the phone will not boot. It just stays stuck on the warning screen that tells you your bootloader is unlocked. And I was positive that I did flash it correctly because in the guide, it says that each command I enter in terminal should return with "OKAY" and they all did.
Here is my log in terminal with the commands I entered to flash the ROM (I bolded the commands and the OKAY'S) :
Last login: Thu Jul 17 17:17:15 on ttys000
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.027s]
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...
OKAY [ 0.359s]
finished. total time: 0.386s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.101s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.297s]
finished. total time: 1.398s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.091s]
writing 'logo'...
OKAY [ 0.137s]
finished. total time: 0.229s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.376s]
writing 'recovery'...
OKAY [ 1.004s]
finished. total time: 1.381s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (260693 KB)...
OKAY [ 8.202s]
writing 'system'...
OKAY [ 17.607s]
finished. total time: 25.809s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (261168 KB)...
OKAY [ 8.218s]
writing 'system'...
OKAY [ 15.416s]
finished. total time: 23.634s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (219321 KB)...
OKAY [ 6.915s]
writing 'system'...
OKAY [ 22.025s]
finished. total time: 28.940s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.527s]
writing 'modem'...
OKAY [ 2.279s]
finished. total time: 3.806s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.072s]
finished. total time: 0.072s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.071s]
finished. total time: 0.071s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (717 KB)...
OKAY [ 0.120s]
writing 'fsg'...
OKAY [ 5.355s]
finished. total time: 5.475s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase cache
erasing 'cache'...
OKAY [ 0.144s]
finished. total time: 0.144s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase userdata
erasing 'userdata'...
OKAY [ 2.202s]
finished. total time: 2.202s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot reboot
rebooting...
finished. total time: 0.001s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$
So what am I doing wrong here? Is there anything else I can do?

You did not flash boot.img
After recovery you should have
fastboot flash boot boot.img

All the fastboot commands in the correct order.
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_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot​

alresave said:
You did not flash boot.img
After recovery you should have
fastboot flash boot boot.img
Click to expand...
Click to collapse
Oh wow can't believe I missed that.. I'll try it again and see what happens

lost101 said:
As I said, Baseband version is not an indicator of which model you have.
Fastboot flash: Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Dude you are the best! That one worked like you said and my network is working again! I really do appreciate the help! ::good::good::good::

alresave said:
You did not flash boot.img
After recovery you should have
fastboot flash boot boot.img
Click to expand...
Click to collapse
OMG Thanks so much man, you noticing that just saved my phone!

Moto G X1028 issues and problems

I am a inexperienced user I am also slow and need step by step clear instructions.. I have not once ounce of a clue how to use CMD ... ok ..
I got a Moto G X1028 from a friend who said it wasn't booting up..
found out it does boot but only into Fastboot menu..
Normal power up, recovery, and factory all when clicked, make the screen go black,then a light on top of phone blinks 3 times..
Now I have gotten it to seem idk alive, when clicking the 3 choices above sometimes it randomly will ether blink 3 times or give a system failed to verify..
although sometimes when the recovery feature does go through there is a little green android laying down with a red triangle ...
I am trying to see if theres is some hope on restoring this phone through Fastboot..
The Pc recognizes the device as Fastboot falcon S but can't enter it at all ...
I am looking for a more detailed step by step on how, if possible to restore this device ..
I have attempted many tutorials all leaving me bewildered and confused ..
I have on my PC 2 roms I think thats what they are ...
philz_touch_6.57.9-falcon.img and cm-12-20150131-UNOFFICIAL-falcon.zip...
I have installed the minimal ADB and Fastboot software
and the Motorola drivers are installed and recognizes the device as 210.12.41.falcon_cdma.verizon.en.us
So I am hoping someone can help me, understand I am slow and on top of that a newb...
and bring hope that this phone can be restored to working order ..
Note: not sure if this could help it states the device is locked, Status code 0
on screen at the time of posting this is fastboot reason: volume down key pressed
usb connected, cmd: getvar:all
So:
Can this phone be restored?
Will it be a easy task?
Can it be restored if the device is locked?

Yumi Chi said:
I am a inexperienced user I am also slow and need step by step clear instructions.. I have not once ounce of a clue how to use CMD ... ok ..
I got a Moto G X1028 from a friend who said it wasn't booting up..
found out it does boot but only into Fastboot menu..
Normal power up, recovery, and factory all when clicked, make the screen go black,then a light on top of phone blinks 3 times..
Now I have gotten it to seem idk alive, when clicking the 3 choices above sometimes it randomly will ether blink 3 times or give a system failed to verify..
although sometimes when the recovery feature does go through there is a little green android laying down with a red triangle ...
I am trying to see if theres is some hope on restoring this phone through Fastboot..
The Pc recognizes the device as Fastboot falcon S but can't enter it at all ...
I am looking for a more detailed step by step on how, if possible to restore this device ..
I have attempted many tutorials all leaving me bewildered and confused ..
I have on my PC 2 roms I think thats what they are ...
philz_touch_6.57.9-falcon.img and cm-12-20150131-UNOFFICIAL-falcon.zip...
I have installed the minimal ADB and Fastboot software
and the Motorola drivers are installed and recognizes the device as 210.12.41.falcon_cdma.verizon.en.us
So I am hoping someone can help me, understand I am slow and on top of that a newb...
and bring hope that this phone can be restored to working order ..
Note: not sure if this could help it states the device is locked, Status code 0
on screen at the time of posting this is fastboot reason: volume down key pressed
usb connected, cmd: getvar:all
So:
Can this phone be restored?
Will it be a easy task?
Can it be restored if the device is locked?
Click to expand...
Click to collapse
If you have access to fastboot, it is entirely possible that you can manually restore the stock 4.4.4 ROM and recovery that way. I'll have some time in the morning where I can walk you through some steps in detail if you still need it.

a_gert said:
If you have access to fastboot, it is entirely possible that you can manually restore the stock 4.4.4 ROM and recovery that way. I'll have some time in the morning where I can walk you through some steps in detail if you still need it.
Click to expand...
Click to collapse
I would greatly appreciate that ^-^

Yumi Chi said:
I would greatly appreciate that ^-^
Click to expand...
Click to collapse
Alright, let's see what we can do for you! First things first, download the XT1028 4.4.4 stock ROM from here:
http://www.filefactory.com/file/5cg..._4.4.4_KXB21.14-L1.41_42_release-keys.xml.zip
It's big, filefactory is slow, and that's going to take a while, so you can sit back and get up to speed on the rest of things while that is in progress. The next thing you need to do is head over to the following thread and read through the first post. You will be following the process for firmware downloaded in xml.zip format: http://forum.xda-developers.com/showthread.php?t=2542219
It sounds to me like you have done at least a solid portion of the prerequisites for this, but you can run through the list to make sure. You might want to download and install the Motorola drivers (Prerequisite 'a') if you haven't already, and you'll want to get the mfastboot-v2.zip package (Prerequisite 'c'). Once you have everything downloaded and the drivers/adb/fastboot stuff installed, the basic idea here is that we are going to take the original stock firmware piece by piece and manually install it using the phone's fastboot mode. If it works correctly, it will completely replace whatever corrupted ROM and recovery files are on your device presently and may allow you to actually boot up the phone into Android 4.4.4 KitKat at a factory default condition.
Find and locate the place where you installed adb and fastboot. On my own system, I just installed it to "C:\adb" for simplicity. In the folder, you'll see adb.exe, fastboot.exe, etc. Take the mfastboot-v2.zip you downloaded above and extract the contents into the same folder -- you should now also have a "mfastboot.exe" file there, as well. Finally, take the stock firmware zip file you downloaded from the above link and extract this into the same folder (make sure all these files are actually in the same folder as the .exe's, not in some subfolder); it contains a good dozen or so files that we are going to flash onto your phone.
In Windows, if you're in the folder with the above files and you hold down the Shift key and right click somewhere in the folder, you'll have an option from the drop down menu to "Open command window here" which should get you a nice command prompt right where you need to be. Get your phone rebooted into fastboot mode, connect it to your PC, and then we can start running through the commands if everything is working correctly.
On the post I linked above, there is a series of mfastboot commands you will have to enter one by one and confirm that it returns an [OKAY] message afterward. The only variation you should have from the original post is that you need to enter an additional command for sparsechunk4 (make sure you scroll this whole list):
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If everything went well, you should be rebooted into a stock Verizon 4.4.4 ROM. Take your time, let me know if you have any additional questions about the steps or you get stuck, and good luck!

a_gert said:
Alright, let's see what we can do for you! First things first, download the XT1028 4.4.4 stock ROM from here:
http://www.filefactory.com/file/5cg..._4.4.4_KXB21.14-L1.41_42_release-keys.xml.zip
It's big, filefactory is slow, and that's going to take a while, so you can sit back and get up to speed on the rest of things while that is in progress. The next thing you need to do is head over to the following thread and read through the first post. You will be following the process for firmware downloaded in xml.zip format: http://forum.xda-developers.com/showthread.php?t=2542219
It sounds to me like you have done at least a solid portion of the prerequisites for this, but you can run through the list to make sure. You might want to download and install the Motorola drivers (Prerequisite 'a') if you haven't already, and you'll want to get the mfastboot-v2.zip package (Prerequisite 'c'). Once you have everything downloaded and the drivers/adb/fastboot stuff installed, the basic idea here is that we are going to take the original stock firmware piece by piece and manually install it using the phone's fastboot mode. If it works correctly, it will completely replace whatever corrupted ROM and recovery files are on your device presently and may allow you to actually boot up the phone into Android 4.4.4 KitKat at a factory default condition.
Find and locate the place where you installed adb and fastboot. On my own system, I just installed it to "C:\adb" for simplicity. In the folder, you'll see adb.exe, fastboot.exe, etc. Take the mfastboot-v2.zip you downloaded above and extract the contents into the same folder -- you should now also have a "mfastboot.exe" file there, as well. Finally, take the stock firmware zip file you downloaded from the above link and extract this into the same folder (make sure all these files are actually in the same folder as the .exe's, not in some subfolder); it contains a good dozen or so files that we are going to flash onto your phone.
In Windows, if you're in the folder with the above files and you hold down the Shift key and right click somewhere in the folder, you'll have an option from the drop down menu to "Open command window here" which should get you a nice command prompt right where you need to be. Get your phone rebooted into fastboot mode, connect it to your PC, and then we can start running through the commands if everything is working correctly.
On the post I linked above, there is a series of mfastboot commands you will have to enter one by one and confirm that it returns an [OKAY] message afterward. The only variation you should have from the original post is that you need to enter an additional command for sparsechunk4 (make sure you scroll this whole list):
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If everything went well, you should be rebooted into a stock Verizon 4.4.4 ROM. Take your time, let me know if you have any additional questions about the steps or you get stuck, and good luck!
Click to expand...
Click to collapse
This ^ is what I needed simple step by step you sir are amazing ! I have everything downloaded but the rom its still going atm so once that is done ill finish the rest of steps and come back here

Yumi Chi said:
This ^ is what I needed simple step by step you sir are amazing ! I have everything downloaded but the rom its still going atm so once that is done ill finish the rest of steps and come back here
Click to expand...
Click to collapse
Help ...failed
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.036s]
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...
OKAY [ 0.346s]
finished. total time: 0.382s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.156s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.094s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.109s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Yumi Chi said:
Help ...failed
Click to expand...
Click to collapse
Any idea as to the status of the phone before you got it? The bootloader status of 0 means it is still locked and it appears from the versioning you listed that it was on 4.4.4 already, so I'm not sure why you'd be having signature verification issues reflashing 4.4.4. At this point, I am honestly just guessing, but perhaps try reflashing the partition table again (the first command with gpt.bin), then reboot the phone back into fastboot mode and try to do the other commands on a second pass?

a_gert said:
Any idea as to the status of the phone before you got it? The bootloader status of 0 means it is still locked and it appears from the versioning you listed that it was on 4.4.4 already, so I'm not sure why you'd be having signature verification issues reflashing 4.4.4. At this point, I am honestly just guessing, but perhaps try reflashing the partition table again (the first command with gpt.bin), then reboot the phone back into fastboot mode and try to do the other commands on a second pass?
Click to expand...
Click to collapse
the phone has to be off??? it wont turn off while usb connected ok im confused now .....the phone once charged boot only in fast boot she said it did work but she thought the battery was just going no harm was done to the device .. atm the phone is stating hab check failed for system
failed to validate system image

a_gert said:
Any idea as to the status of the phone before you got it? The bootloader status of 0 means it is still locked and it appears from the versioning you listed that it was on 4.4.4 already, so I'm not sure why you'd be having signature verification issues reflashing 4.4.4. At this point, I am honestly just guessing, but perhaps try reflashing the partition table again (the first command with gpt.bin), then reboot the phone back into fastboot mode and try to do the other commands on a second pass?
Click to expand...
Click to collapse
Knowing my friend shes not one for updates she must have what ever update comes with this phone by default

Yumi Chi said:
the phone has to be off??? it wont turn off while usb connected ok im confused now .....the phone once charged boot only in fast boot she said it did work but she thought the battery was just going no harm was done to the device .. atm the phone is stating hab check failed for system
failed to validate system image
Click to expand...
Click to collapse
I was suggesting that after you do the mfastboot command to flash the gpt.bin file (which, from your log appeared to work corrrectly), you could then reboot the phone into fastboot mode (turn it off, turn it back on and get it back into fastboot mode) and then resume from step two. My only theory there was that it may need to actually reformat the partitions before you go back in and start flashing things and that might be why you have the error you do.
Question 30 at: http://forum.xda-developers.com/showthread.php?t=2537119 suggests that if you are failing to flash 4.4.4 at this point, you may be stuck, so I'm just trying to walk through the steps I would try myself in your scenario.

Yumi Chi said:
the phone has to be off??? it wont turn off while usb connected ok im confused now .....the phone once charged boot only in fast boot she said it did work but she thought the battery was just going no harm was done to the device .. atm the phone is stating hab check failed for system
failed to validate system image
Click to expand...
Click to collapse
Trying to find the default that comes with this phone is not my line knowledge ....
looking on a wiki this is some things i found
its a CDMA Version XT1028 for Verizon
I have a feeling it may be this default that comes with it
Operating system Android Jelly Bean 4.3[6] (Upgradable to Android 5.0 Lollipop[7])

my friend never updates her phones .... I think its a 4.3 jellybean any way to check that theory and find a stock rom ?

Yumi Chi said:
my friend never updates her phones .... I think its a 4.3 jellybean any way to check that theory and find a stock rom ?
Click to expand...
Click to collapse
The XT1028 originally shipped with 4.3 Jelly Bean, but it is no longer the stock ROM for this device. The part where you say it was recognized as "210.12.41.falcon_cdma.verizon.en.us" means that the device and bootloader have been updated to 4.4.4 KitKat, as that string would have been different were it still on 4.3 or 4.4.2.

a_gert said:
The XT1028 originally shipped with 4.3 Jelly Bean, but it is no longer the stock ROM for this device. The part where you say it was recognized as "210.12.41.falcon_cdma.verizon.en.us" means that the device and bootloader have been updated to 4.4.4 KitKat, as that string would have been different were it still on 4.3 or 4.4.2.
Click to expand...
Click to collapse
ok ill give it another shot and try reflashing

reformat the partitions how does one do this ?

Yumi Chi said:
ok ill give it another shot and try reflashing
Click to expand...
Click to collapse
Considering the phone in your hand is a Verizon model and the bootloader is locked, Best Buy has this model in stock for $30, just in case it comes to replacing it outright: http://www.bestbuy.com/site/verizon...lack/3041063.p?id=1219086346405&skuId=3041063

each time ive gotten after gpt step one: no valid gpt found

Yumi Chi said:
reformat the partitions how does one do this ?
Click to expand...
Click to collapse
You were doing this when you followed the first mfastboot command that flashed the gpt.bin. Do that again, reboot the phone and go back into fastboot mode, and then resume from the second command on the list. This may or may not work, but it's all I can think to suggest.

a_gert said:
You were doing this when you followed the first mfastboot command that flashed the gpt.bin. Do that again, reboot the phone and go back into fastboot mode, and then resume from the second command on the list. This may or may not work, but it's all I can think to suggest.
Click to expand...
Click to collapse
well the img went through the rest well failed ...
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.035s]
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...
OKAY [ 0.347s]
finished. total time: 0.385s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.123s]
finished. total time: 1.222s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.344s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.789s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.360s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.807s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (254591 KB)...
OKAY [ 13.213s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 27.487s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (245234 KB)...
OKAY [ 12.917s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.143s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (257606 KB)...
OKAY [ 13.315s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.682s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (125353 KB)...
OKAY [ 9.052s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.917s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 6.532s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.557s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (712 KB)...
OKAY [ 5.072s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.098s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.983s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot

Yumi Chi said:
well the img went through the rest well failed ...
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.035s]
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...
OKAY [ 0.347s]
finished. total time: 0.385s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.123s]
finished. total time: 1.222s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.344s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.789s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.360s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.807s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (254591 KB)...
OKAY [ 13.213s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 27.487s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (245234 KB)...
OKAY [ 12.917s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.143s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (257606 KB)...
OKAY [ 13.315s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.682s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (125353 KB)...
OKAY [ 9.052s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.917s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 6.532s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.557s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (712 KB)...
OKAY [ 5.072s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.098s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.983s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
Click to expand...
Click to collapse
Whenever something indicates FAILED, you really don't need to keep on with the following steps. What I find odd is that you are succeeding with a couple and then the remaining ones are failing. You can try to reboot after each step that succeeds, perhaps, if that helps.

MOTO G XT1032 black screen

I have a Moto G (XT1032) running Android 5.0.2 that went out of charge one day. It then decided to boot into a black screen - i.e. I can see the Motorola splash screen (animation) but all I get after that is a black (grey) screen, not responsive to touch.
I tried a few things and they didn't work -
Fastbooted and selected 'Recovery' option - The Motorola logo (first screen of startup splash screen) appears briefly. Then the device returns to fastboot menu saying 'Boot Up failed'
Fastbooted and selected 'Factory' - The Motorola splash screen appears, boots into same black (grey) screen again.
The fastboot menu says "Device is LOCKED. Status Code: 0". I did not enable USB debugging before my phone stopped working.
How do I get my phone working again?

You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​
Is there important data on the phone? Then do not use the command: mfastboot erase userdata

lost101 said:
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
Click to expand...
Click to collapse
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".

Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065​

C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.084s]
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...
OKAY [ 0.330s]
finished. total time: 0.418s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash motoboot motobo
ot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.151s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.957s]
finished. total time: 1.112s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.095s]
writing 'logo'...
OKAY [ 0.035s]
finished. total time: 0.132s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash recovery recove
ry.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.446s]
writing 'recovery'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 9.591s]
writing 'system'...
OKAY [ 7.728s]
finished. total time: 17.323s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.955s]
writing 'system'...
OKAY [ 8.082s]
finished. total time: 17.042s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 9.657s]
writing 'system'...
OKAY [ 8.179s]
finished. total time: 17.843s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 6.347s]
writing 'system'...
OKAY [ 6.282s]
finished. total time: 12.635s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.943s]
writing 'modem'...
OKAY [ 0.780s]
finished. total time: 2.727s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.022s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.090s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.279s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboot
Click to expand...
Click to collapse
Thats all that i got... i don't know what else to do...

Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2

pradeeppk said:
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
Click to expand...
Click to collapse
i do it, but i get the same message, "No Command"

lost101 said:
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
Click to expand...
Click to collapse
I see something wierd now, looks like the memory of the phone dosent save anything... sometimes, when the boot animation stops, i see the message of "1 of 1 Updates, android its updating" and then go to the black screen again... but, if i flash the phone, i shouldn't see that message, rigth? so, why i can still see it? how can i erase all the memory for sure???

Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img

lost101 said:
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
Click to expand...
Click to collapse
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja

Joncillo said:
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Click to expand...
Click to collapse
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/

lost101 said:
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
Click to expand...
Click to collapse
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?

Joncillo said:
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Click to expand...
Click to collapse
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip

lost101 said:
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
Click to expand...
Click to collapse
when i wipe the device, i get some errors.
E: MTP already enable
Formatting data using mkfs.f2fs...
Done
E: Unknown MTP message type 1:
You may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to stat '/data/data/com.google.android.gms/app_sslcache/www.googleapis.com.443'
E: Unable to stat '/data/data/com.google.android.calendar/databases/timelydata.db-shm'
...done
but don't wipe anything...
i try ADB Sideload but get an error too.
Starting ADB sideload feature... (After 10 minutes)
FAILED ADB Sideload complete.
and the CMD on windows says "Error: device not found"
also i try to install TWRP as zip, but when i restarted, enter into recovery and then i have the same android with error "No Command".

@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798

lost101 said:
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
ahhhhhhhhh... i see... so, i have a dead phone... well, i'm going to try what you said in that post, thanks for all your help!!!

Allow OEM Unlock Bootloader

Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!

axbom said:
Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!
Click to expand...
Click to collapse
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.

acejavelin said:
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.
Click to expand...
Click to collapse
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!

axbom said:
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!
Click to expand...
Click to collapse
Did you factory default prior to flashing? That is a required step...

acejavelin said:
Did you factory default prior to flashing? That is a required step...
Click to expand...
Click to collapse
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..

axbom said:
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..
Click to expand...
Click to collapse
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk

acejavelin said:
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_set
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
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...
OKAY [ 0.708s]
finished. total time: 0.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.551s]
finished. total time: 1.645s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.125s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.519s]
writing 'boot'...
OKAY [ 0.936s]
finished. total time: 1.471s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 1.486s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (243355 KB)...
OKAY [ 7.717s]
writing 'system'...
OKAY [ 8.975s]
finished. total time: 16.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (233538 KB)...
OKAY [ 7.478s]
writing 'system'...
OKAY [ 7.597s]
finished. total time: 15.092s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (256922 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 8.308s]
finished. total time: 16.521s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (257262 KB)...
OKAY [ 8.198s]
writing 'system'...
OKAY [ 8.303s]
finished. total time: 16.500s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (255507 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 8.575s]
finished. total time: 16.717s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (258021 KB)...
OKAY [ 8.225s]
writing 'system'...
OKAY [ 8.266s]
finished. total time: 16.507s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (210541 KB)...
OKAY [ 6.716s]
writing 'system'...
OKAY [ 11.695s]
finished. total time: 18.410s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.165s]
writing 'modem'...
OKAY [ 0.974s]
finished. total time: 2.155s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2159 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.172s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>
From what I can see it all looks fine?

axbom said:
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
...
From what I can see it all looks fine?
Click to expand...
Click to collapse
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?

acejavelin said:
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?
Click to expand...
Click to collapse
After issuing the reboot command at the end it goes to the white screen with the motorola logo, then the screen goes black, and then back to the motorola logo, and keep on going like that.
Yeah that's correct, 0-6 sparsechunk files. I did fastboot ERASE cache and ERASE userdata, since I can't get into the recovery menu (goes into bootloop if I try). When I try any of those commands it says Formatting is not supported for filesystem with type 'raw'.

im having the exact same problem, used the same software and carried out the same steps as you with no luck either.
from what ive read its because you need to wipe all the data first but because we get the, cant its RAW message, it wont download the firmware onto the phone even though it says it went ok. at the minute i havnt found anyone whos successfully been able to repair this fault.
mine was working perfectly untill the ota update

There is no fix for that, use your warranty if you have so

Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.

yobac said:
Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.
Click to expand...
Click to collapse
Contact Moto directly via their website.
Sent from my MotoG3 using Tapatalk

1st Flash via Adb !
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !

FaizanChauhaan said:
1st Flash via Adb !
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !
Click to expand...
Click to collapse
It's fastboot not adb lol. Contradictory sentences
Edit: BTW motoboot.img is not present, it may refer to earlier generation of moto g. There is an line to flash bootloader.img instead. Have a look here : http://forum.xda-developers.com/showthread.php?t=3187750. Thanks.
Broadcasted from Zeta Reticuli

Rebooting only into Fastboot mode

Using AEX's AOSP 7.1 rom(Indian quark) from few days. Facing many issues like app crashes and no LTE mostly. Today i wanted to call someone and clicked on phone app on home screen. Suddenly a message popped up saying phone has stopped. It showed whenever i clicked on phone app. I restarted the phone. Thatsit. Its only booting into fastboot mode. Whenever i chose to select recovery mode it only boots into fastboot. checked the bootloaderlogs and found "failed to validate boot image ret=-1 bootup failed" this message.Please, I need a serious help.

krishna13 said:
Using AEX's AOSP 7.1 rom(Indian quark) from few days. Facing many issues like app crashes and no LTE mostly. Today i wanted to call someone and clicked on phone app on home screen. Suddenly a message popped up saying phone has stopped. It showed whenever i clicked on phone app. I restarted the phone. Thatsit. Its only booting into fastboot mode. Whenever i chose to select recovery mode it only boots into fastboot. checked the bootloaderlogs and found "failed to validate boot image ret=-1 bootup failed" this message.Please, I need a serious help.
Click to expand...
Click to collapse
It's booting to the bootloader screen? You should be able to arrow up from there using the volume keys to the "recovery" option and boot to TWRP.
Once in TWRP, restore the backup you made. You did make a recent backup in TWRP, right?
OR in TWRP, do a factory reset and install a ROM. In TWRP, you can drag over whatever you want if you are connected to a PC. Works just like a flash drive. Drag over a ROM, GAPPs, etc if you don't want to install AEX's AOSP 7.1 again.

ChazzMatt said:
It's booting to the bootloader screen? You should be able to arrow up from there using the volume keys to the "recovery" option and boot to TWRP.
Once in TWRP, restore the backup you made. You did make a recent backup in TWRP, right?
OR in TWRP, do a factory reset and install a ROM. In TWRP, you can drag over whatever you want if you are connected to a PC. Works just like a flash drive. Drag over a ROM, GAPPs, etc if you don't want to install AEX's AOSP 7.1 again.
Click to expand...
Click to collapse
Its not going to recovery mode again. In bootloader logs i can see boot.img failed and the ret value is -1. Even in RSD flash tool i can see that 2/18 error or 2/22 fastboot oem fb_clear error. Tried flashing original 6.0 and 5.0 firmwares both in RSD flashtool and individual fastboot commands.But i failed. ALways booting only in Fastboot. Please help me. Im living with no phone from 3 days. Please provide me a solution...

krishna13 said:
Its not going to recovery mode again. In bootloader logs i can see boot.img failed and the ret value is -1. Even in RSD flash tool i can see that 2/18 error or 2/22 fastboot oem fb_clear error. Tried flashing original 6.0 and 5.0 firmwares both in RSD flashtool and individual fastboot commands.But i failed. ALways booting only in Fastboot. Please help me. Im living with no phone from 3 days. Please provide me a solution...
Click to expand...
Click to collapse
But you can go to recovery mode. If it's booting to the bootloader, you can arrow up to recovery and choose that.
Oh no, you flashed original 6.0 and 5.0 firmware? OK, now you have not only wiped out your custom TWRP recovery you have have flashed older bootloader over newer bootloader which BRICKS the phone. You never, never, never flash older firmware over newer firmware unless you omit gpt.bin in the flash commands.
Even then you should also omit recovery.img in the flash commands to keep custom recovery.
Your bootloader is unlocked, right? If so, there is still hope. Hold on.

ChazzMatt said:
But you can go to recovery mode. If it's booting to the bootloader, you can arrow up to recovery and choose that.
Oh no, you flashed original 6.0 and 5.0 firmware? OK, now you have not only wiped out your custom TWRP recovery you have have flashed older bootloader over newer bootloader which BRICKS the phone. You never, never, never flash older firmware over newer firmware unless you omit gpt.bin in the flash commands.
Even then you should also omit recovery.img in the flash commands to keep custom recovery.
Your bootloader is unlocked, right? If so, there is still hope. Hold on.
Click to expand...
Click to collapse
Yes. Still my device is unlocked. In fastboot mode, the text showing in yello color saying, Device is UNLOCKED. Status code :3.
Please help me.. Is it possible through teamviewer?? please please help me..

OK, read this thread.
https://forum.xda-developers.com/moto-maxx/help/bootloader-locked-acess-recovery-os-t3662683
and this one:
https://forum.xda-developers.com/moto-maxx/help/maxx-xt1225-br-hard-brick-help-please-t3661803
After that, specifically you want to download this file:
https://forum.xda-developers.com/showpost.php?p=73528589&postcount=19
Yes, it's for Brazil XT1225 but your bootloader is unlocked and there's no India equivalent posted online. You need the very latest Marshmallow stock (with latest bootloader) from Motorola and that's it. For stock you can only flash the same version bootloader you have or newer.
You will NOT be using RSDLite. You will have to use ADB fastboot. Read this post for instructions.
https://forum.xda-developers.com/dr...force-how-to-manually-flash-official-t3282077
Yes, it's for the Moto X Force, but the steps are still the same for any bootloader unlocked Motorola device. You are flashing cross-region firmware on your India XT1225 to get it back working again.
You will need to omit gpt.bin when flashing the commands.
Once your phone is working again, you will need to re-flash TWRP and root with that older SuperSu version or whatever you did the first time.
After that you can reinstall a custom ROM if you wish.

ChazzMatt said:
OK, read this thread.
https://forum.xda-developers.com/moto-maxx/help/bootloader-locked-acess-recovery-os-t3662683
and this one:
https://forum.xda-developers.com/moto-maxx/help/maxx-xt1225-br-hard-brick-help-please-t3661803
After that, specifically you want to download this file:
https://forum.xda-developers.com/showpost.php?p=73528589&postcount=19
Yes, it's for Brazil XT1225 but your bootloader is unlocked and there's no India equivalent posted online. You need the very latest Marshmallow stock (with latest bootloader) from Motorola and that's it. For stock you can only flash the same version bootloader you have or newer.
You will NOT be using RSDLite. You will have to use ADB fastboot. Read this post for instructions.
https://forum.xda-developers.com/dr...force-how-to-manually-flash-official-t3282077
Yes, it's for the Moto X Force, but the steps are still the same for any bootloader unlocked Motorola device. You are flashing cross-region firmware on your India XT1225 to get it back working again.
You will need to omit gpt.bin when flashing the commands.
Once your phone is working again, you will need to re-flash TWRP and root with that older SuperSu version or whatever you did the first time.
After that you can reinstall a custom ROM if you wish.
Click to expand...
Click to collapse
Downloaded the files from http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/ and tried all the steps from the link u provided.These are the steps i followed.
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
But failed to reboot. In bootloader logs its showing as
"failed to validate boot image ret :-1"
Fastboot reason : fall-through from normal boot mode
any other method please?? help me with this.

krishna13 said:
Downloaded the files from http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/ and tried all the steps from the link u provided.These are the steps i followed.
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
But failed to reboot. In bootloader logs its showing as
"failed to validate boot image ret :-1"
Fastboot reason : fall-through from normal boot mode
any other method please?? help me with this.
Click to expand...
Click to collapse
One thing...
On that Brazil firmware link I only see 10 sparse chunks, numbered 0-9, Yet, in your post above you have 12 listed. how are you flashing 12? (0-11) You can only flash as many sparse chunks as there are, that example from the Moto X Force thread is just an example. You have to flash the exact number.
I see you did NOT flash gpt.bin, which is good.
If your bootloader is still unlocked, this should work.
The only thing else I can suggest is this powerful temp root command first, before flashing the Brazil image. But you then have to flash an "end"/"finish" command or the next time you reboot, that itself will cause a bootloop. Over in the Droid Turbo forum, they use that temp root command to flash Sunshine, so Sunshine can then unlock the bootloader. You don't need Sunshine, I am only pointing you to the temp root file, which may help you flash this Brazil Marshmallow image.
There was another thread I can't find right now, from a person in very similar circumstances to you. His bootloader was even locked -- which was worse than you. But using that temp command, he was able to revive his phone using ADB fastboot flashing. His only problem then was not ending the temp root, and now I've lost the thread.
So, try this. Flash the temp root, followed by all the ADB fastboot commands to flash that image, followed by the command to end the temp root (it's double quotation marks with a space before them).

ChazzMatt said:
One thing...
On that Brazil firmware link I only see 10 sparse chunks, numbered 0-9, Yet, in your post above you have 12 listed. how are you flashing 12? (0-11) You can only flash as many sparse chunks as there are, that example from the Moto X Force thread is just an example. You have to flash the exact number.
I see you did NOT flash gpt.bin, which is good.
If your bootloader is still unlocked, this should work.
The only thing else I can suggest is this powerful temp root command first, before flashing the Brazil image. But you then have to flash an "end"/"finish" command or the next time you reboot, that itself will cause a bootloop. Over in the Droid Turbo forum, they use that temp root command to flash Sunshine, so Sunshine can then unlock the bootloader. You don't need Sunshine, I am only pointing you to the temp root file, which may help you flash this Brazil Marshmallow image.
There was another thread I can't find right now, from a person in very similar circumstances to you. His bootloader was even locked -- which was worse than you. But using that temp command, he was able to revive his phone using ADB fastboot flashing. His only problem then was not ending the temp root, and now I've lost the thread.
So, try this. Flash the temp root, followed by all the ADB fastboot commands to flash that image, followed by the command to end the temp root (it's double quotation marks with a space before them).
Click to expand...
Click to collapse
Yes. My bad. i had just copied commands to show u that i followed them. But in real, i had only flashed 9 of them.
and coming to your post, so should I need to download the initroot from "got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-...ader-t3639316/" and install in my system and run the .bat file? would it work for my xt1225? there mentioned other than xt1225. after flashing all the 9 system sparse chunks from brazil firmware, is this the command to end the temp root?? fastboot oem config fsg-id " "
I am confused

ChazzMatt said:
One thing...
On that Brazil firmware link I only see 10 sparse chunks, numbered 0-9, Yet, in your post above you have 12 listed. how are you flashing 12? (0-11) You can only flash as many sparse chunks as there are, that example from the Moto X Force thread is just an example. You have to flash the exact number.
I see you did NOT flash gpt.bin, which is good.
If your bootloader is still unlocked, this should work.
The only thing else I can suggest is this powerful temp root command first, before flashing the Brazil image. But you then have to flash an "end"/"finish" command or the next time you reboot, that itself will cause a bootloop. Over in the Droid Turbo forum, they use that temp root command to flash Sunshine, so Sunshine can then unlock the bootloader. You don't need Sunshine, I am only pointing you to the temp root file, which may help you flash this Brazil Marshmallow image.
There was another thread I can't find right now, from a person in very similar circumstances to you. His bootloader was even locked -- which was worse than you. But using that temp command, he was able to revive his phone using ADB fastboot flashing. His only problem then was not ending the temp root, and now I've lost the thread.
So, try this. Flash the temp root, followed by all the ADB fastboot commands to flash that image, followed by the command to end the temp root (it's double quotation marks with a space before them).
Click to expand...
Click to collapse
This is how i did this time..
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id " "
...
OKAY [ 0.003s]
finished. total time: 0.006s
C:\Users\SRK\Downloads\Motorola firmware>
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2163 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.204s]
finished. total time: 0.285s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.590s]
writing 'boot'...
OKAY [ 0.123s]
finished. total time: 0.714s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.599s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.715s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.335s]
writing 'system'...
OKAY [ 1.698s]
finished. total time: 10.118s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (239764 KB)...
OKAY [ 7.597s]
writing 'system'...
OKAY [ 1.551s]
finished. total time: 9.155s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (250695 KB)...
OKAY [ 7.947s]
writing 'system'...
OKAY [ 1.617s]
finished. total time: 9.569s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (255001 KB)...
OKAY [ 8.070s]
writing 'system'...
OKAY [ 1.592s]
finished. total time: 9.669s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (257746 KB)...
OKAY [ 8.156s]
writing 'system'...
OKAY [ 1.622s]
finished. total time: 9.782s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (261982 KB)...
OKAY [ 8.291s]
writing 'system'...
OKAY [ 1.695s]
finished. total time: 9.992s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.296s]
writing 'system'...
OKAY [ 1.608s]
finished. total time: 9.911s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (247037 KB)...
OKAY [ 7.819s]
writing 'system'...
OKAY [ 1.568s]
finished. total time: 9.393s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.307s]
writing 'system'...
OKAY [ 1.613s]
finished. total time: 9.926s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.9
target max-sparse-size: 256MB
sending 'system' (219553 KB)...
OKAY [ 6.985s]
writing 'system'...
OKAY [ 1.379s]
finished. total time: 8.371s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.013s]
finished. total time: 0.016s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.012s]
finished. total time: 0.015s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.005s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id "end"
...
FAILED (remote failure)
finished. total time: 0.011s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id "finish"
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id ""
...
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id " "
...
OKAY [ 0.002s]
finished. total time: 0.004s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot reboot
rebooting...
finished. total time: 0.004s
but same problem..no success ..same ret :-1 in bootloader logs. Did i do wrong??

krishna13 said:
and coming to your post, so should I need to download the initroot from "got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-...ader-t3639316/" and install in my system and run the .bat file? would it work for my xt1225? there mentioned other than xt1225. after flashing all the 9 system sparse chunks from brazil firmware, is this the command to end the temp root?? fastboot oem config fsg-id " "
Click to expand...
Click to collapse
Yes, but to end the temp root -- it's hard to tell due to XDA formatting --but It's fastboot oem config fsg-id "", with a space between the fsg-id part and the double quotation marks. There's NO space IN the quotation marks, just a space before it.

ChazzMatt said:
Yes, but to end the temp root -- it's hard to tell due to XDA formatting --but It's fastboot oem config fsg-id "", with a space between the fsg-id part and the double quotation marks. There's NO space IN the quotation marks, just a space before it.
Click to expand...
Click to collapse
i have downloaded auto-intiroot-xt1254_quark.so shall i simply install it in my system and run the bat file? so no problem for my phone? to end that, simply ill follow the command without spaces.
first ill install bat file,then flash all the fastboot commands of firmware,and before fastboot reboot, ill end the temp flash and reboot my device.is this the procedure???

krishna13 said:
i have downloaded auto-intiroot-xt1254_quark.so shall i simply install it in my system and run the bat file? so no problem for my phone? to end that, simply ill follow the command without spaces.
first ill install bat file,then flash all the fastboot commands of firmware,and before fastboot reboot, ill end the temp flash and reboot my device.is this the procedure???
Click to expand...
Click to collapse
Yes, you downloaded the right version. It's this one, even though you have an XT1225:
http://downloads.codefi.re/autoprime/Motorola/autoinitroot/XT1254
Yes, install the bat file via fastboot, then run the fastboot commands for firmware, then end the temp flash and try to reboot.
IF this doesn't work, I have no other ideas really. Just variations of making sure you are flashing the firmware correctly, which you seem to be doing.

ChazzMatt said:
There was another thread I can't find right now, from a person in very similar circumstances to you.
Click to expand...
Click to collapse
That was in [All Quark][Official] Stock Firmware Moto Maxx Droid Turbo Moto Turbo, and started on page 48 - post #475.

hitokage004 said:
That was in [All Quark][Official] Stock Firmware Moto Maxx Droid Turbo Moto Turbo, and started on page 48 - post #475.
Click to expand...
Click to collapse
Thank you! Thought I was going crazy. I KNEW I had discussed this just recently and the person used temp root and got the phone working again. Then I couldn't find the posts. But it was you who suggested the temp root tool and it worked.
Yeah, start on this page, with post 475:
https://forum.xda-developers.com/mo...tock-firmware-moto-maxx-droid-t3063470/page48
There was no final resolution to that person's problem but he was able to reboot the phone and it was working again, thanks to the temp root.

ChazzMatt said:
Yes, but to end the temp root -- it's hard to tell due to XDA formatting --but It's fastboot oem config fsg-id "", with a space between the fsg-id part and the double quotation marks. There's NO space IN the quotation marks, just a space before it.
Click to expand...
Click to collapse
I had run auto-init.bat which booted my phone in fastboot mode asusual.then i followed the same steps by ending the temp root like mentioned.But same happened. in bootloader logs the same ret=-1 and also Fastboot reason : Reboot mode set to fastboot.This was all i followed.
C:\Users\SRK\Downloads\NewMoto>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2163 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.247s]
finished. total time: 0.377s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.107s]
finished. total time: 0.692s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.590s]
writing 'recovery'...
OKAY [ 0.108s]
finished. total time: 0.705s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.292s]
writing 'system'...
OKAY [ 1.721s]
finished. total time: 10.018s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (239764 KB)...
OKAY [ 7.592s]
writing 'system'...
OKAY [ 1.582s]
finished. total time: 9.180s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (250695 KB)...
OKAY [ 7.937s]
writing 'system'...
OKAY [ 1.618s]
finished. total time: 9.561s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (255001 KB)...
OKAY [ 8.069s]
writing 'system'...
OKAY [ 1.592s]
finished. total time: 9.666s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (257746 KB)...
OKAY [ 8.157s]
writing 'system'...
OKAY [ 1.625s]
finished. total time: 9.787s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (261982 KB)...
OKAY [ 8.288s]
writing 'system'...
OKAY [ 1.703s]
finished. total time: 9.996s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.608s]
finished. total time: 9.907s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (247037 KB)...
OKAY [ 7.821s]
writing 'system'...
OKAY [ 1.547s]
finished. total time: 9.375s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.614s]
finished. total time: 9.912s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.9
target max-sparse-size: 256MB
sending 'system' (219553 KB)...
OKAY [ 6.959s]
writing 'system'...
OKAY [ 1.375s]
finished. total time: 8.341s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.010s]
finished. total time: 0.013s
C:\Users\SRK\Downloads\NewMoto>mfastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.005s
C:\Users\SRK\Downloads\NewMoto>fastboot oem config fsg-id ""
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.056s]
finished. total time: 0.060s
C:\Users\SRK\Downloads\NewMoto>mfastboot reboot
rebooting...
finished. total time: 0.003s
could you or someone assist me in team viewer please?? I really having bad days. no phone from 4 days.

krishna13 said:
I had run auto-init.bat which booted my phone in fastboot mode asusual.then i followed the same steps by ending the temp root like mentioned.But same happened. in bootloader logs the same ret=-1 and also Fastboot reason : Reboot mode set to fastboot.This was all i followed.
C:\Users\SRK\Downloads\NewMoto>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2163 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.247s]
finished. total time: 0.377s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.107s]
finished. total time: 0.692s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.590s]
writing 'recovery'...
OKAY [ 0.108s]
finished. total time: 0.705s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.292s]
writing 'system'...
OKAY [ 1.721s]
finished. total time: 10.018s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (239764 KB)...
OKAY [ 7.592s]
writing 'system'...
OKAY [ 1.582s]
finished. total time: 9.180s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (250695 KB)...
OKAY [ 7.937s]
writing 'system'...
OKAY [ 1.618s]
finished. total time: 9.561s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (255001 KB)...
OKAY [ 8.069s]
writing 'system'...
OKAY [ 1.592s]
finished. total time: 9.666s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (257746 KB)...
OKAY [ 8.157s]
writing 'system'...
OKAY [ 1.625s]
finished. total time: 9.787s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (261982 KB)...
OKAY [ 8.288s]
writing 'system'...
OKAY [ 1.703s]
finished. total time: 9.996s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.608s]
finished. total time: 9.907s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (247037 KB)...
OKAY [ 7.821s]
writing 'system'...
OKAY [ 1.547s]
finished. total time: 9.375s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.614s]
finished. total time: 9.912s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.9
target max-sparse-size: 256MB
sending 'system' (219553 KB)...
OKAY [ 6.959s]
writing 'system'...
OKAY [ 1.375s]
finished. total time: 8.341s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.010s]
finished. total time: 0.013s
C:\Users\SRK\Downloads\NewMoto>mfastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.005s
C:\Users\SRK\Downloads\NewMoto>fastboot oem config fsg-id ""
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.056s]
finished. total time: 0.060s
C:\Users\SRK\Downloads\NewMoto>mfastboot reboot
rebooting...
finished. total time: 0.003s
could you or someone assist me in team viewer please?? I really having bad days. no phone from 4 days.
Click to expand...
Click to collapse
These three errors you got which I'm pasting below are normal:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Click to expand...
Click to collapse
But other than that, everything shows it's flashing OK? Yet it still won't boot...
Searching the internet for that " ret=-1" error message, came across this:
https://productforums.google.com/forum/#!topic/nexus/Z-Ek9spUUMk;context-place=topicsearchin/nexus/authorid$3AAPn2wQd-FQicFC7RbavvPMsMOeXIILaxmrMVo3XYrb0P_pWrMw5VVUQIz_Dx8Ty4va61Ty_aMSFj%7Csort:date%7Cspell:false
and this:
https://productforums.google.com/forum/#!topic/nexus/9pgTA6RG85Y
Both were told they probably had hardware failure, most like flash memory.
I'm almost out of ideas. Since all your flashing did seem to go OK, how about now trying to flash TWRP again? You would be replacing stock recovery with a TWRP image. Then with phone off try using the volume + power button to boot to bootloader screen, if it will let you. Then from there you can choose TWRP. Once in TWRP (if you get that far) you can try dragging over a ROM to flash.
But if you are experiencing a hardware failure you probably won't be able to get that far.

I'm generally not very good walking people through things, but here is something to try. It's almost exactly what you've done before, except you will use mfastboot erase for specific partitions before flashing. Do NOT erase the bootloader - it can brick the phone. You shouldn't need to temp root, since your bootloader is unlocked.
From a command prompt, in the directory/folder you have ADB/(m)fastboot:
reminder do NOT erase the bootloader:
Code:
mfastboot flash bootloader bootloader.img
Code:
mfastboot erase boot
mfastboot flash boot boot.img
mfastboot erase recovery
for stock recovery use:
Code:
mfastboot flash recovery recovery.img
for TWRP (download link) use:
Code:
mfastboot flash recovery twrp-3.1.1-mod_2-quark.img
Code:
mfastboot erase system
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
if you installed TWRP:
Code:
mfastboot reboot-bootloader
then start recovery to let it make the changes to keep it from being replaced, and then reboot
for stock recovery just reboot:
Code:
mfastboot reboot
If this doesn't work it's either failing hardware as ChazzMatt stated, or time to do things you shouldn't.

hitokage004 said:
I'm generally not very good walking people through things, but here is something to try. It's almost exactly what you've done before, except you will use mfastboot erase for specific partitions before flashing. Do NOT erase the bootloader - it can brick the phone. You shouldn't need to temp root, since your bootloader is unlocked.
From a command prompt, in the directory/folder you have ADB/(m)fastboot:
reminder do NOT erase the bootloader:
Code:
mfastboot flash bootloader bootloader.img
Code:
mfastboot erase boot
mfastboot flash boot boot.img
mfastboot erase recovery
for stock recovery use:
Code:
mfastboot flash recovery recovery.img
for TWRP (download link) use:
Code:
mfastboot flash recovery twrp-3.1.1-mod_2-quark.img
Code:
mfastboot erase system
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
if you installed TWRP:
Code:
mfastboot reboot-bootloader
then start recovery to let it make the changes to keep it from being replaced, and then reboot
for stock recovery just reboot:
Code:
mfastboot reboot
If this doesn't work it's either failing hardware as ChazzMatt stated, or time to do things you shouldn't.
Click to expand...
Click to collapse
thanku for ur help. I just saw this post now. Ill try today and will update you the status.

hitokage004 said:
I'm generally not very good walking people through things, but here is something to try. It's almost exactly what you've done before, except you will use mfastboot erase for specific partitions before flashing. Do NOT erase the bootloader - it can brick the phone. You shouldn't need to temp root, since your bootloader is unlocked.
From a command prompt, in the directory/folder you have ADB/(m)fastboot:
reminder do NOT erase the bootloader:
Code:
mfastboot flash bootloader bootloader.img
Code:
mfastboot erase boot
mfastboot flash boot boot.img
mfastboot erase recovery
for stock recovery use:
Code:
mfastboot flash recovery recovery.img
for TWRP (download link) use:
Code:
mfastboot flash recovery twrp-3.1.1-mod_2-quark.img
Code:
mfastboot erase system
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
if you installed TWRP:
Code:
mfastboot reboot-bootloader
then start recovery to let it make the changes to keep it from being replaced, and then reboot
for stock recovery just reboot:
Code:
mfastboot reboot
If this doesn't work it's either failing hardware as ChazzMatt stated, or time to do things you shouldn't.
Click to expand...
Click to collapse
Nope.Bad news. Even this didnt work. All this happened because of AEX rom I suppose. Since I flashed that rom, most of the apps were force closing. I thought these bugs might be solved in future updates and continued using it. I shouldnt have flashed that rom. Should have continued RR rom. Huge terrible mistake of mine. I am not blaming the developer.Please dont take this as an offence.I know all this is our own risk and already mentioned at the beginning of the posts.Just Blaming myself...
Thanks for your and @ChazzMatt help anyways.thanku soo much..
RIP my Moto
Edit 1 : Bought new Samsung A9 pro which fulfills my needs with a good battery backup. Goodbye to my Moto Turbo.Also to this forum.
Once again My Heartful thanks to @ChazzMatt and @hitokage004