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.
Related
I'm trying to unbrick my moto g. whatever I try to flash I get always these kind of errors
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.366s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.810s
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.382s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.810s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (249379 KB)...
OKAY [ 12.932s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 21.886s
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.984s
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.984s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Same problem
I have the same problem, did you find a solution? if so, what was is?
Try all the versions of Fastboot in this zip: https://www.androidfilehost.com/?fid=23578570567719065
Can you say any more about what Fastboot commands you have previously used?
I have the same problem and I didn't have found any fix :crying: I have the XT1032 model
https://forum.xda-developers.com/showthread.php?t=2317790
check this and download version 1.4.2 and copy mfastboot to the folder (1.4.2 minimal adb fastboot folder)
now everything will work.
dont use ADB from google, always use minimal adb fastboot .exe available in above link
I have somehow totally trashed my Android install. I have a UK retail Moto G XT1032.
While downloading the OTA lollipop update, the download appeared to stall. I decided to give up on the update, so I switched the phone off. When I turned it back on again, every single process crashed. "Unfortunately dialler/android.process.acore/Calendar/android.process.media/etc has stopped". I can keep tapping "OK" for ever to clear these notifications, but can't actually use the phone for anything at all.
So I decided to do a factory reset from fastboot. It made no difference.
I tried a factory reset from recovery. It made no difference.
Using fastboot, I attempted to install the stock ROM according to the guide at http://forum.xda-developers.com/showthread.php?t=2542219. Everything seemed to flash OK - I got OKAY on the PC and the commands appeared to be running on the phone OK, but when it restarted, the phone was exactly the same - my wallpaper photo was still there, and the app icons that I could glimpse behind the endless notifications were my apps.
I tried several more times, this time flashing the 4.4.4 ROM (RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF). Exactly the same results - nothing changes when I restart.
It's as if the mfastboot flash commands do nothing at all! I have run all the mfastboot commands described by the guide in the order given.
I've also tried booting to recovery and connecting to ADB, but the PC cannot see the device.
I've tried replacing the recovery with CWM and TWRP .img files, but the flash command, while seeming to work, doesn't change anything at all! The recovery that I have installed is the standard KXB21.14-L1.40.
I have tried "mfastboot.exe erase recovery", before attempting to update the recovery, but it makes no difference.
Does anybody have any idea what I am doing wrong? It seems that no "mfastboot flash xxx yyy" command works at all on my phone.
Did you installfastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.
Got the same problem. I've already posted this in a few threads and didn't get any answer, though
Sounds crazy but, when you type fastboot devices with your phone connected in fastboot mode, does the command return your phone's serial #?
Yes, everything via fastboot works (says complete, done etc.) except it doesn't affect the real system. If you sideload ADB you will see that the system, data and cache partition become read-only. I've managed to remount only data partition with write privileges, but that doesn't help.
Are you flashing each partition manually? You can see your device's serial # in fastboot?
audit13 said:
Did you install fastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.
Click to expand...
Click to collapse
Originally, I used the version of fastboot that came with the first stock ROM I tried (falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB).
Later on, I installed mfastboot and used that instead. The results were the same. Nothing seems to actually be flashed, but there are no errors on either the PC or the phone.
ADB does not work in fastboot (I don't believe it's supposed to!), but it also will not work with the version of recovery that I have, which is why I was attempting to install CWM and TWRP in its place.
audit13 said:
Are you flashing each partition manually? You can see your device's serial # in fastboot?
Click to expand...
Click to collapse
Yes. I'm currently trying the following sequence with the XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml ROM...
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
The mfastboot command returns OKAY for each of these, and a couple of yellow lines appear on the phone for each command, indicating that the right command is running, with no error messages.
I have never used mfastboot. Maybe try using fastboot to flash? I have used fastboot on my Moto G and Moto Atrix HD with great success.
Tried with fastboot, tried with mfastboot, got no errors but nothing changes. The real problem I suppose is corrupted partitions.
Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358
@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?
dog121 said:
Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358
Click to expand...
Click to collapse
I've just given it a go.
When flashing the ROMs, it basically runs the same mfastboot commands that I was running before, so the result was exactly the same.
However, the ADB Driver install button was worth trying. The driver supplied has enabled my PC to communicate with the phone using ADB when in recovery mode!
Unfortunately, after selecting "apply update from ADB" on the phone, and running "adb sideload <ROM zip file>", it sends it to the phone (taking a couple of minutes), and the phone says "Verifying update package", followed by "Installation aborted".
When you sideload, do you need some sort of special format ROM file?
audit13 said:
@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?
Click to expand...
Click to collapse
I was hoping to use the stock ROM, just to get the phone back to its original state.
If the mfastboot command does nothing, I doubt trying different ROMs will help. But I'll probably try it if I can't get anything else to work.
thanks a lot!
@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot
lost101 said:
@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Thanks for the idea. I happen to have a laptop running the latest Lubuntu.
I installed fastboot as you directed and re-flashed everything. Exactly the same. The commands all say OKAY, the yellow text on the phone says it's running the commands, but when I reboot - everything is exactly as it was before - including my wallpaper photo and app icons. And every single process on the phone is crashing.
I do not believe fastboot is actually working on this phone. The only commands that seem to work are the ones to unlock the bootloader and the one to reboot the phone.
@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
I.e first file is sparsechunk.0 not sparsechunk1
EDIT: Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
It's retail Brazil, but will work anywhere in the world.
I suggest you skip flashing the bootloader - motoboot.img
lost101 said:
@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
Click to expand...
Click to collapse
Yup.
Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
Click to expand...
Click to collapse
OK - I downloaded this and flashed it. Exactly the same as all the previous attempts. It appears to work, but when I restart, the phone is in exactly the same state as before, as if no flashing has happened.
Here is the command line output:
Code:
C:\>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.024s]
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.353s]
finished. total time: 0.380s
C:\>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.084s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.110s]
finished. total time: 1.197s
C:\>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.105s
C:\>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.360s]
writing 'boot'...
OKAY [ 0.670s]
finished. total time: 1.030s
C:\>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.695s]
finished. total time: 1.060s
C:\>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 8.140s]
writing 'system'...
OKAY [ 8.155s]
finished. total time: 16.295s
C:\>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.185s]
writing 'system'...
OKAY [ 8.690s]
finished. total time: 16.885s
C:\>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 8.265s]
writing 'system'...
OKAY [ 8.755s]
finished. total time: 121.145s
C:\>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 5.255s]
writing 'system'...
OKAY [ 6.475s]
finished. total time: 11.735s
C:\>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.605s]
writing 'modem'...
OKAY [ 0.825s]
finished. total time: 2.435s
C:\>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.020s
C:\>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.070s]
writing 'fsg'...
OKAY [ 3.180s]
finished. total time: 3.250s
C:\>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.025s]
finished. total time: 0.025s
C:\>mfastboot reboot
rebooting...
finished. total time: 0.005s
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Thanks again to all of you for your assistance in this matter.
IcyBee said:
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Click to expand...
Click to collapse
Recovery mode ADB will work in Linux. You could try side-loading the 5.0.2 OTA Update.
Hello, i have an xt1033 moto g hard bricked, it boots up normal, but the system crash till the phone reboots, i enter in the fastboot mode and try to flash 4.4.4 again or 5.0.1, no errors at all, but when i reboot the phone it dont have changed nothing, continue with the crashes and the same apps showing.
And adb devices dosnt show nothing, just fastboot recognizes the device. Already tried to flash a custom recovery, it dosnt change, no errors when trying to flash, but when you enter recovery it is the standard one, adb sideload always show an error after reading the file i send.
Already tried erase all the files, but the phone reboot as the same, crashing and rebooting.
I already tried everything i found to revive the phone but whit no luck, tried the RSDLite too but it dosnt recognize my cellphone, i dont know what to do anymore :crying:
Any help are welcome, thanks and sorry for my bad english
Post logs of what happens when you try to flash the XT1033 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Post logs of what happens when you try to flash the XT1033 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Here are my full log, system dosnt have changed nothing after all this. Same problems. Already tried to update the bootloader bot it dosnt change too
Microsoft Windows [versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0426104575 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase all
erasing 'all'...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing hob ...
(bootloader) erasing dhob ...
(bootloader) erasing fsg ...
(bootloader) erasing fsc ...
(bootloader) erasing clogo ...
(bootloader) erasing cache ...
(bootloader) erasing userdata ...
OKAY [ 4.758s]
finished. total time: 4.758s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
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.390s]
finished. total time: 0.421s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot
.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.104s]
finished. total time: 1.213s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.047s]
finished. total time: 0.125s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.661s]
finished. total time: 1.083s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.421s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.076s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257887 KB)...
OKAY [ 8.742s]
writing 'system'...
OKAY [ 7.894s]
finished. total time: 16.636s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (256762 KB)...
OKAY [ 8.940s]
writing 'system'...
OKAY [ 8.225s]
finished. total time: 17.181s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (260106 KB)...
OKAY [ 9.013s]
writing 'system'...
OKAY [ 8.315s]
finished. total time: 17.327s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (166048 KB)...
OKAY [ 5.863s]
writing 'system'...
OKAY [ 6.367s]
finished. total time: 12.230s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
target reported max download size of 536870912 bytes
sending 'modem' (49356 KB)...
OKAY [ 1.794s]
writing 'modem'...
OKAY [ 0.796s]
finished. total time: 2.605s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.047s]
writing 'fsg'...
OKAY [ 3.188s]
finished. total time: 3.251s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.000s
Never
EVER
use
fastboot erase all
You have erased partitions unique to your phone, you have lost IMEI - you will never be able to make calls over a network again. You should not have used that command. It might be possible to get a ROM booting again, but don't expect anything more than a tablet from now on. Sorry.
lost101 said:
Never
EVER
use
fastboot erase all
You have erased partitions unique to your phone, you have lost IMEI - you will never be able to make calls over a network again. You should not have used that command. It might be possible to get a ROM booting again, but don't expect anything more than a tablet from now on. Sorry.
Click to expand...
Click to collapse
i tried this command to see if something change , but the cellphone is still the same, crashing till reboots, dont know what to do to repair its os it still have the same apps installed, runing the same way, nothing works .-.
d3vileyes said:
i tried this command to see if something change , but the cellphone is still the same, crashing till reboots, dont know what to do to repair its os it still have the same apps installed, runing the same way, nothing works .-.
Click to expand...
Click to collapse
Try using mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065
same thing, i tried to lock my bootloader too but shows an error at the end, the system dont changed again.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 1.576s]
finished. total time: 1.576s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash partition gp
t.bin
target max-sparse-size: 256MB
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.359s]
finished. total time: 0.374s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash motoboot mot
oboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.112s]
finished. total time: 1.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash logo logo.bi
n
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.047s]
finished. total time: 0.109s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash boot boot.im
g
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.655s]
finished. total time: 1.061s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash recovery rec
overy.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.406s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.061s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257887 KB)...
OKAY [ 9.058s]
writing 'system'...
OKAY [ 8.189s]
finished. total time: 17.262s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256762 KB)...
OKAY [ 8.958s]
writing 'system'...
OKAY [ 8.239s]
finished. total time: 17.197s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260106 KB)...
OKAY [ 9.159s]
writing 'system'...
OKAY [ 8.317s]
finished. total time: 17.476s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166048 KB)...
OKAY [ 5.848s]
writing 'system'...
OKAY [ 6.365s]
finished. total time: 12.229s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash modem NON-HL
OS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.794s]
writing 'modem'...
OKAY [ 0.842s]
finished. total time: 2.652s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.094s]
writing 'fsg'...
OKAY [ 3.167s]
finished. total time: 3.276s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 17.434s
Download TWRP: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Use the command: mfastboot flash recovery twrp-2.8.6.0-falcon.img
Enter Recovery and confirm TWRP works.
Report back.
tried again with no luck, recovery dosnt change too, i tried the f2f and the ext4.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10184 KB)...
OKAY [ 0.382s]
writing 'recovery'...
OKAY [ 0.184s]
finished. total time: 0.569s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery openrec
overy-twrp-2.8.4.0-falcon_STOCK.img
target max-sparse-size: 256MB
sending 'recovery' (8168 KB)...
OKAY [ 0.280s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.440s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery openrec
overy-twrp-2.8.4.0-falcon_GPE.img
target max-sparse-size: 256MB
sending 'recovery' (8168 KB)...
OKAY [ 0.286s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.451s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Try: mfastboot boot openrecovery-twrp-2.8.4.0-falcon_STOCK.img
lost101 said:
Try: mfastboot boot openrecovery-twrp-2.8.4.0-falcon_STOCK.img
Click to expand...
Click to collapse
It worked, it booted on twrp, but if i try to restore or something else it give me "unable to mount /cache" error
Try to format ( wipe and format are different things) cache partition in recovery or using fastboot command
fastboot erase cache
sjandroiddeveloper said:
Try to format ( wipe and format are different things) cache partition in recovery or using fastboot command
fastboot erase cache
Click to expand...
Click to collapse
Everything i try to do it say "unable to mount /cache", i think the /cache partition is bricked, i cant repair or format it, and every time i try to do something it shows me an error :/
d3vileyes said:
Everything i try to do it say "unable to mount /cache", i think the /cache partition is bricked, i cant repair or format it, and every time i try to do something it shows me an error :/
Click to expand...
Click to collapse
I had a problem when my data partition was no mounting
Whenever I flashed a ROM or wiped data or factory reset it gave error cannot mount data
I repaired it by formating data partition using Philz recovery
I am again saying wipe and format are different concepts
Do one thing flash Philz recovery because in twrp you can only format data and not system and cache
So flash Philz touch
Go to wipe and format>Custom format and format cache partition
Then it should work
sjandroiddeveloper said:
I had a problem when my data partition was no mounting
Whenever I flashed a ROM or wiped data or factory reset it gave error cannot mount data
I repaired it by formating data partition using Philz recovery
I am again saying wipe and format are different concepts
Do one thing flash Philz recovery because in twrp you can only format data and not system and cache
So flash Philz touch
Go to wipe and format>Custom format and format cache partition
Then it should work
Click to expand...
Click to collapse
When i try to boot philz_touch_6.58.7-falcon it boots the Motorola logo and crash to a black screen, after this it boots the system
~~~~~~~edit~~~~~~
tried another version of philz touch and it worked, i'm gonna try to format now
d3vileyes said:
When i try to boot philz_touch_6.58.7-falcon it boots the Motorola logo and crash to a black screen, after this it boots the system
Click to expand...
Click to collapse
Did you try the fastboot command
fastboot erase cache
For formatting cache partition
Do it and see that in twrp (since you cannot flash Philz ) that the error is still there or not
sjandroiddeveloper said:
Did you try the fastboot command
fastboot erase cache
For formatting cache partition
Do it and see that in twrp (since you cannot flash Philz ) that the error is still there or not
Click to expand...
Click to collapse
I used the command fastboot erase cache, same error on twrp
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.000s
~~~~~~~~edit~~~~~~
now i can boot philz recovery, i formated /cache and /sdcard, in the screen shows OK but nothing changes
@d3vileyes - I would use adb push a ROM.zip and try flashing that in TWRP. Recovery mode adb is possible, but doesn't always work for Windows users. On a Linux PC / Laptop - it will always work.
ADB command: adb push rom.zip /sdcard/
XT1033 Lollipop ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
lost101 said:
@d3vileyes - I would use adb push a ROM.zip and try flashing that in TWRP. Recovery mode adb is possible, but doesn't always work for Windows users. On a Linux PC / Laptop - it will always work.
ADB command: adb push rom.zip /sdcard/
Click to expand...
Click to collapse
when i try to adb push i get this error
Failed to copy 'xt1033_retail_Brazil.zip' to '/sdcard//xt1033_retail_Brazil.zip': Read-only file system
~~~~~~edit~~~~~
Fixed this error with adb shell
mount -o remount rw /sdcard
but when i try to flash it gaves me the same error "unable to mount /cache"
don't know whats going on with the /cache folder
d3vileyes said:
I used the command fastboot erase cache, same error on twrp
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.000s
~~~~~~~~edit~~~~~~
now i can boot philz recovery, i formated /cache and /sdcard, in the screen shows OK but nothing changes
Click to expand...
Click to collapse
First of all when you formatted cache partition in Philz recovery, did it come in the logs below that formatting cache successful or something like that or it again appeared that cannot Mount cache
If it appeared that cache formatting successful then try and wipe cache this time and it should come wipe cache complete
If that happens you are good to go
Just flash a rom again and this time should be successful
sent from falcon
PRESS THANKS IF HELPED?????
Hi, today my Falcon got Bootlooped on Stock Flashable Zip Optimized v1 after severals week of working without problems.
Then i tried to Factory Reset using TRWP, but it failed.
After that i enter recovery mode and used mtp usb to copy the Zip to install it tru recovery, but after getting 44Mb of the zip file on my phone then a message appeared saying that y disconnected the cable, i cancelled the process.
On my second try i could copy anything on my phone, seems like the filesystem gone broke, all the folders appeared but they dont show files inside.
Then i tried, to flash Stock Brazilian 5.0.2 Using fastboot but always get the CANT ERASE PARTITION - CANT FLASH PARTITION.
But i can Flash Recoveries, i flashed CWM and tried to wipe without success, tried the special recovery from phill without success.
I think the problem is the partition table. al the partitions are there, i can see them, twrp says they are present, and everyone has filesize.
But i cant flash, erase partitions, cant sideload.
Please help me.
DETAILS:
MOTO G XT1032
LAST ROM: STOCK OPTIMIZED 5.1 v1b
BOOTLOADER: 41.18
RECOVERY: TRWP
LAST TRY OF RESTORING STOCK ROM:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery cwm.img
target reported max download size of 536870912 bytes
sending 'recovery' (7878 KB)...
OKAY [ 0.320s]
writing 'recovery'...
OKAY [ 0.310s]
finished. total time: 0.630s
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.043s]
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.337s]
finished. total time: 0.410s
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.100s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash rpm
FAILED (remote failure)
finished. total time: 10.948s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 5.079s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.919s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.img
target max-sparse-size: 256MB
error: cannot load 'logo.img': No error
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.370s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.784s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot fkasg system system.i
mg_sparsechunk.0
usage: fastboot [ <option> ] <command>
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 14.002s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 22.464s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 13.999s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 22.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 14.094s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 22.612s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.734s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.772s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.023s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 5.039s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.080s
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.994s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\Program Files (x86)\Minimal ADB and Fastboot>
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