Database Info

[GPE][REFLASH]Pre flash validation failed for gpt moto g xt1033.

Hey
I asked a question before but no one seemed interested. On my xt1033, I installed GPE 4.4.2 Firmware. I installed Carbon ROM on it. Now, I wanted to flash back to my stock Asia Retail firmware. When I tried flashing it, I got the error below -
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Sony\Desktop\Right>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.100s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.502s
Click to expand...
Click to collapse
So, basically I even tried flashing motoboot.img and the same result appeared.
To at least allow my phone to receive calls, I tried installing stock GPE Edition ROM but the same error.
Now, u guys have any solution for it?
ANSWER FAST CAUSE NO ONE SEEMS ACTIVE HERE! ANSWER OR THIS FORUM WOULD S**K!!!!
ALSO, I tried installing it with 4.4.2 asia stock retail ROM.
I had twrp recovery installed from before where I formatted the system, cache, dalvik-cache, and wiped data/cache but still no hopes.
ANYONE HEARD ME? I'M IN DIRE NEED OF HELP!

http://forum.xda-developers.com/showthread.php?t=2834023

??
lost101 said:
http://forum.xda-developers.com/showthread.php?t=2834023
Click to expand...
Click to collapse
????
????
????
????

You may be getting this error because your bootloader is locked.
Here is a guide to unlock it:
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6​

Its fully unlocked!!!
lost101 said:
You may be getting this error because your bootloader is locked.
Here is a guide to unlock it:
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6​
Click to expand...
Click to collapse
ITS FULLY UNLOCKED!!!!
The error is something like this shown on my bootloader
cmd:flash:motoboot
version downgraded for tz
NO ONE CAN HELP ME?????:crying::crying::crying::crying::crying::crying:

OHHHHH!!!!!!!!!!!!!!!!!!!!!
Im getting f__ing irritated now!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
No one has the answer? Not even the best developers of xda?? Huh? No one? Are u all so down? I'm just a rom user but other firmware devs know a lot! Can't they come over and help? No one?

[email protected] said:
Im getting f__ing irritated now!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
No one has the answer? Not even the best developers of xda?? Huh? No one? Are u all so down? I'm just a rom user but other firmware devs know a lot! Can't they come over and help? No one?
Click to expand...
Click to collapse
I'm new to the forum, but here's what happened to me when I tried to flash CyanogenMod and back to Stock ROM.
My solution was to download a Stock ROM.xml.zip and do the following:
1. Verify that you are in a USB 2.0 connection. USB 3.0 ports (blue) do not work.
2. Download the file I posted.
3. ADB Install Tools.
4. Unzip the "mFastBootFilesForADBTools.rar" inside the folder where you installed the ADB Tools. Archive
5. Fetch the files of StockROM.xml.zip and place within the ADB Tools folder.
PS. In my case I used this Stock ROM: "Android 4.4.2
Blur_Version.171.44.31.falcon_umtsds.Brasil.en.BR. "But is BR, download a similar in your area.
6. Hold the SHIFT key and right-click within the ADB Tools folder. Choose the option: Open a command window here.
. 7 Put the following commands:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe modemst2 erase
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
* If the FAILED error occurs in the first two, ignore and continue:
* Note if the OKAY appear at all after the "logo.bin" (including this one).
* If all goes as planned, the phone will reboot and will take a while to configure the system. And be with the Stock ROM you chose.
* To update OTA, just wait about 2 minutes after connect the Wii-Fi, check the settings and try to update. If error happen, wait about 2 more minutes and try again. With that everything should be OK.
Do not blame me if it goes wrong. Just worked for me. Currently I use the Stock ROM with OTA. Android 4.4.4
--- Translated by Google Translate ---

avrtlg said:
I'm new to the forum, but here's what happened to me when I tried to flash CyanogenMod and back to Stock ROM.
My solution was to download a Stock ROM.xml.zip and do the following:
1. Verify that you are in a USB 2.0 connection. USB 3.0 ports (blue) do not work.
2. Download the file I posted.
3. ADB Install Tools.
4. Unzip the "mFastBootFilesForADBTools.rar" inside the folder where you installed the ADB Tools. Archive
5. Fetch the files of StockROM.xml.zip and place within the ADB Tools folder.
PS. In my case I used this Stock ROM: "Android 4.4.2
Blur_Version.171.44.31.falcon_umtsds.Brasil.en.BR. "But is BR, download a similar in your area.
6. Hold the SHIFT key and right-click within the ADB Tools folder. Choose the option: Open a command window here.
. 7 Put the following commands:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe modemst2 erase
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
* If the FAILED error occurs in the first two, ignore and continue:
* Note if the OKAY appear at all after the "logo.bin" (including this one).
* If all goes as planned, the phone will reboot and will take a while to configure the system. And be with the Stock ROM you chose.
* To update OTA, just wait about 2 minutes after connect the Wii-Fi, check the settings and try to update. If error happen, wait about 2 more minutes and try again. With that everything should be OK.
Do not blame me if it goes wrong. Just worked for me. Currently I use the Stock ROM with OTA. Android 4.4.4
--- Translated by Google Translate ---
Click to expand...
Click to collapse
:good:

avrtlg said:
I'm new to the forum, but here's what happened to me when I tried to flash CyanogenMod and back to Stock ROM.
My solution was to download a Stock ROM.xml.zip and do the following:
1. Verify that you are in a USB 2.0 connection. USB 3.0 ports (blue) do not work.
2. Download the file I posted.
3. ADB Install Tools.
4. Unzip the "mFastBootFilesForADBTools.rar" inside the folder where you installed the ADB Tools. Archive
5. Fetch the files of StockROM.xml.zip and place within the ADB Tools folder.
PS. In my case I used this Stock ROM: "Android 4.4.2
Blur_Version.171.44.31.falcon_umtsds.Brasil.en.BR. "But is BR, download a similar in your area.
6. Hold the SHIFT key and right-click within the ADB Tools folder. Choose the option: Open a command window here.
. 7 Put the following commands:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe modemst2 erase
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
* If the FAILED error occurs in the first two, ignore and continue:
* Note if the OKAY appear at all after the "logo.bin" (including this one).
* If all goes as planned, the phone will reboot and will take a while to configure the system. And be with the Stock ROM you chose.
* To update OTA, just wait about 2 minutes after connect the Wii-Fi, check the settings and try to update. If error happen, wait about 2 more minutes and try again. With that everything should be OK.
Do not blame me if it goes wrong. Just worked for me. Currently I use the Stock ROM with OTA. Android 4.4.4
--- Translated by Google Translate ---
Click to expand...
Click to collapse
I have the same problem, and your solution saved my day..... Thanks.

one mistake you have:
mfastboot.exe modemst2 erase
should be:
mfastboot erase modemst2

Doesn't worked for me
avrtlg said:
I'm new to the forum, but here's what happened to me when I tried to flash CyanogenMod and back to Stock ROM.
My solution was to download a Stock ROM.xml.zip and do the following:
1. Verify that you are in a USB 2.0 connection. USB 3.0 ports (blue) do not work.
2. Download the file I posted.
3. ADB Install Tools.
4. Unzip the "mFastBootFilesForADBTools.rar" inside the folder where you installed the ADB Tools. Archive
5. Fetch the files of StockROM.xml.zip and place within the ADB Tools folder.
PS. In my case I used this Stock ROM: "Android 4.4.2
Blur_Version.171.44.31.falcon_umtsds.Brasil.en.BR. "But is BR, download a similar in your area.
6. Hold the SHIFT key and right-click within the ADB Tools folder. Choose the option: Open a command window here.
. 7 Put the following commands:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe modemst2 erase
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
* If the FAILED error occurs in the first two, ignore and continue:
* Note if the OKAY appear at all after the "logo.bin" (including this one).
* If all goes as planned, the phone will reboot and will take a while to configure the system. And be with the Stock ROM you chose.
* To update OTA, just wait about 2 minutes after connect the Wii-Fi, check the settings and try to update. If error happen, wait about 2 more minutes and try again. With that everything should be OK.
Do not blame me if it goes wrong. Just worked for me. Currently I use the Stock ROM with OTA. Android 4.4.4
--- Translated by Google Translate ---
Click to expand...
Click to collapse
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.313s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash motoboot motoboot
.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.139s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.399s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.040s]
finished. total time: 0.097s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.630s]
finished. total time: 1.027s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash recovery recovery
.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.610s]
finished. total time: 1.012s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash system system.img
_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [ 9.052s]
writing 'system'...
OKAY [ 8.714s]
finished. total time: 17.783s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash system system.img
_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (237949 KB)...
OKAY [ 8.159s]
writing 'system'...
OKAY [ 7.158s]
finished. total time: 15.320s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash system system.img
_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (243326 KB)...
OKAY [ 8.325s]
writing 'system'...
OKAY [ 16.160s]
finished. total time: 24.487s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash modem NON-HLOS.bi
n
target max-sparse-size: 256MB
sending 'modem' (47476 KB)...
OKAY [ 1.677s]
writing 'modem'...
OKAY [ 0.835s]
finished. total time: 2.516s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.050s]
writing 'fsg'...
OKAY [ 3.182s]
finished. total time: 3.235s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.016s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>mfastboot.exe reboot
rebooting...
finished. total time: 0.001s
H:\Official files\MOBILE TOOLS\Moto G XT1033\ADB_Tools_and_mFastBoot_Files\RETAI
L-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml>

[Q] Help! fastboot flash appears to do nothing!

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.

No radio/mobile network connection after custom rom flash

I first flashed the stock rom and then the "minimal os" rom, but I don't get a mobile network connection. I enter my pin, but then it just says "no service". My sim works in other mobile phones 100%. and other sims also don't work in my phone, so the problem is with the phone/settings/ROM. any suggestions? I need the radio back

I recommend you fastboot flash the latest factory firmware image for your phone.
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images​
Provide a log if this does not solve your problem. Copy and paste command prompt after doing all of the fastboot commands.

Every command gave me an "okay". but after reboot the phone got stuck in the "open bootloader warning". I can not boot to the system. I want to restore the backup.ab, but I have to be in a started system with usb debugging i guess.
edit: I flashed another rom, but after installing successful and wiping data etc. I get into the recovery again after booting...
For the ADB Restore I need to get into a ROM
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
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.312s]
finished. total time: 0.343s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash motoboot motoboot.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.108s]
finished. total time: 1.201s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.109s]
finished. total time: 0.172s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.343s]
writing 'boot'...
OKAY [ 0.920s]
finished. total time: 1.279s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.936s]
finished. total time: 1.295s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk1': No error
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256933 KB)...
OKAY [ 8.081s]
writing 'system'...
OKAY [ 13.307s]
finished. total time: 21.388s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260424 KB)...
OKAY [ 8.190s]
writing 'system'...
OKAY [ 12.714s]
finished. total time: 20.904s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (162784 KB)...
OKAY [ 5.226s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.182s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.607s]
writing 'modem'...
OKAY [ 2.418s]
finished. total time: 4.040s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot erase modemst.1
erasing 'modemst.1'...
(bootloader) Invalid partition name modemst.1
FAILED (remote failure)
finished. total time: 0.031s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.094s]
finished. total time: 0.109s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.062s]
writing 'fsg'...
OKAY [ 3.494s]
finished. total time: 3.557s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 5.741s]
finished. total time: 5.741s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>mfastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Ingrid\Desktop\Moto G\Stock De Retail\XT1032_FALCON_RETDE_5.1_LPB23.13-
56_cid7_CFC.xml>

When was the last time you had a cellular signal? Have you run any fastboot commands (other than those above) since?

lost101 said:
When was the last time you had a cellular signal? Have you run any fastboot commands (other than those above) since?
Click to expand...
Click to collapse
I think I had a signal after unlocking the bootloader. than I installed the cyanpop 6.0 rom, I think there was a signal , too. Then I had the problems with gapps and installed CM13/12 but I could not get into the system so I could not see if there was a signal. when I installed the stock rom there was no signal anymore.
I only used "fastboot -w" command and I flashed "GPE_XT1032_5.1_LMY47M.M005_cid222_CFC.xml.zip" through fastboot, although my device is no google play edition. It is EU/GER Retail Edition. I just saw "XT1032_5.1 " and thought it was the correct, because I haven't seen an EU Version. This could be the reason too, but the general problems (except the radio signal) started before.
I would like to restore the backup.ab , but for that I need to get into the system. To get into the system I would like to restore my TWRP backup but it fails while restoring:
-I press "restore"
-select "data" , "system" etc.
-slide to restore
-something like "restoring data...." in the log.
-"Failed" without an error or something.

@PureChris - Check the names of the actual files when fastboot flashing. You are not using the correct names. Provide new logs.

@lost101 these are the commands from the instruction I used. There was an error on sparsechunk1 and modemst.1 because I have written them wrong, but I corrected them right after that.
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_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
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
Click to expand...
Click to collapse

PureChris said:
@lost101 these are the commands from the instruction I used. There was an error on sparsechunk1 and modemst.1 because I have written them wrong, but I corrected them right after that.
Click to expand...
Click to collapse
Those are only example commands. The sparsechunk files should match what is in the firmware folder you are working with. There may be extra sparsechunk files, and they may be named differently.
That German Firmware Image contains the following files:
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​

@lost101 , sry for being such a noob :/
Device is starting properly over and over again and my mobile connection is back yippieh Thank you! This is the first step toawards a finally working custom rom
I will do a TWRP Backup now and tomorrow I will see what happens next.
But I should not celebrate too soon.

Rebooting only into Fastboot mode

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

MotoG falcon.. Unable to wipe system/data and can't go back to stock

Hi! I've installed the latest version available of DotOs about 2 weeks ago and today I woke up with a bricked phone.
Is stuck at the boot logo and when I try to flash or wipe something with twrp I get
Code:
Error opening: '/data/propriety/184370898666... [to much to type]
I run these commands to flash the stock ROM with mfastboot:
Code:
./linux-fastboot flash partition gpt.bin
./linux-fastboot flash motoboot motoboot.img
./linux-fastboot flash logo logo.bin
./linux-fastboot flash boot boot.img
./linux-fastboot flash recovery recovery.img
./linux-fastboot flash system system.img_sparsechunk.0
./linux-fastboot flash system system.img_sparsechunk.1
./linux-fastboot flash system system.img_sparsechunk.2
./linux-fastboot flash system system.img_sparsechunk.3
./linux-fastboot flash modem NON-HLOS.bin
./linux-fastboot erase modemst1
./linux-fastboot erase modemst2
./linux-fastboot flash fsg fsg.mbn
./linux-fastboot erase cache
./linux-fastboot erase userdata
./linux-fastboot reboot
At
Code:
./linux-fastboot flash motoboot motoboot.img
I get:
Code:
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.087s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s
And at
Code:
./linux-fastboot flash motoboot motoboot.img
I get:
Code:
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.150s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.440s
Rebooting the phone goes back to DotOS boot animation and loops there

So I was using the wrong zip.. But even with the right one it just says done and nothing is changed.. same dotos bootloop same used space

dont Downgrade the bootloader to kitkat jus ignore that bootloader file or you will end up with hard brick phone.