Moto g xt1033 dead - Moto G Q&A, Help & Troubleshooting

Moto g xt1033 dead - Moto G Q&A, Help & Troubleshooting

Hi friend,
Please help me, my moto g xt1033 is dead for last 3 months.
I followed almost all steps mentioned in different forum but still stuck at the same position.
Error after Blank Flash:
D:\MOTO G\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x40A8A85
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.022s]
validating files
OKAY [ 0.002s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.003s]
sending programmer
OKAY [ 0.013s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error reading packet)

amit8091 said:
Hi friend,
Please help me, my moto g xt1033 is dead for last 3 months.
I followed almost all steps mentioned in different forum but still stuck at the same position.
Error after Blank Flash:
D:\MOTO G\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x40A8A85
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.022s]
validating files
OKAY [ 0.002s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.003s]
sending programmer
OKAY [ 0.013s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error reading packet)
Click to expand...
Click to collapse
can u just elaborate little more? means which rom were you there before and how moto g got deadc etc etc

abhi0502 said:
can u just elaborate little more? means which rom were you there before and how moto g got deadc etc etc
Click to expand...
Click to collapse
Hii first i have rooted my phone then i downgrade my moto g from lollipop to kitkat using mfastboot.
Again i m trying to upgrade my moto g to lollipop through OTA update . It started first but after few minutes my moto switch off from then it is dead. Unable to go to the recovery mode . when I press power button then notification led start blinking but screen remains black. When i plug it to desktop then it is showing as qhsusb_bulk . So i have tried those procedure for mentioned in this forum for qhsusb_bulk and all of those failed.
Please help me..

amit8091 said:
Hii first i have rooted my phone then i downgrade my moto g from lollipop to kitkat using mfastboot.
Again i m trying to upgrade my moto g to lollipop through OTA update . It started first but after few minutes my moto switch off from then it is dead. Unable to go to the recovery mode . when I press power button then notification led start blinking but screen remains black. When i plug it to desktop then it is showing as qhsusb_bulk . So i have tried those procedure for mentioned in this forum for qhsusb_bulk and all of those failed.
Please help me..
Click to expand...
Click to collapse
while downgrading from lollipop to kitkat did u flash first two commands(partition.gpt and motoboot) ?if yes your mobile got bricked. Visiting service centre is only option left

abhi0502 said:
while downgrading from lollipop to kitkat did u flash first two commands(partition.gpt and motoboot) ?if yes your mobile got bricked. Visiting service centre is only option left
Click to expand...
Click to collapse
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
i have run above commands.

amit8091 said:
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
i have run above commands.
Click to expand...
Click to collapse
so you had flashed partition.gpt and motoboot. It will definitely brick your device because you flashed kitkat based bootloader(always follow instructions carefully) . You could have avoided first two commands and started with logo.bin. Your bootloader got corrupted. You need to visit service centre.

Related

[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>

Help, hab check failed for recovery and boot

After the dumbest idea ever of downgrading to KitKat, I think i soft bricked my phone, it doesn't boot up.
When i try to flash a stock rom from bootloader it says:
Code:
hab check failed for recovery
hab check failed for boot
And when i try flashing a ROM or wiping on TWRP says:
Code:
unable to mount /data
unable to mount /cache
I tried everything i saw on XDA after googling many times the errors, nothing worked :crying:
One strange thing I saw was that when I tried "fastboot format data" it returned: "formatting is not supported for filesystem with type '' " , so, maybe, is a problem with the filesystem?
Help me, please :crying:

Done
Finally, I made it work, I erased and formatted all what i can, then through TWRP I formatted Data and now it works

Tizianop6 said:
Finally, I made it work, I erased and formatted all what i can, then through TWRP I formatted Data and now it works
Click to expand...
Click to collapse
Can you tell me the detail how to operate? Thanks!

Mr.Ju said:
Can you tell me the detail how to operate? Thanks!
Click to expand...
Click to collapse
I formatted all partitions through "fastboot erase" and other commands,flashed TWRP recovery, and then through TWRP I re-formatted all partitions

Tizianop6 said:
I formatted all partitions through "fastboot erase" and other commands,flashed TWRP recovery, and then through TWRP I re-formatted all partitions
Click to expand...
Click to collapse
Hi Mr. Ju,
I am having the exact same problem. I tried to use:
mfastboot devices
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
But it did not work. I sitll have the "hab check failed for boot" and hancheck failed for recovery" when I tried to reflash the GPE5.1 rom.
Can you please post all the mfastboot commands you used?
Thanks
Jº

Fastboot erase command is extremely dangerous and should not be played with.
@jpmaroco - Is your Bootloader locked?

Thanks lost101
No my boatloader is unlocked. I can't even wipe/factory reset with TWRP

jpmaroco said:
Thanks lost101
No my boatloader is unlocked. I can't even wipe/factory reset with TWRP
Click to expand...
Click to collapse
Try using mfastoot: https://www.androidfilehost.com/?fid=24052804347778493
Providing a log is helpful. Copy and paste command prompt after doing fastboot commands.

lost101 said:
Try using mfastoot: https://www.androidfilehost.com/?fid=24052804347778493
Providing a log is helpful. Copy and paste command prompt after doing fastboot commands.
Click to expand...
Click to collapse
Dear lost101,
Thanks for answering back. Here is the log:
E:\>mfastboot devices
TA92908ERZ fastboot
E:\>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\>mfastboot reboot
rebooting...
finished. total time: 0.000s

@jpmaroco - I meant a log of you flashing the Firmware Image.

lost101 said:
@jpmaroco - I meant a log of you flashing the Firmware Image.
Click to expand...
Click to collapse
Thanks lost101, here it goes:
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>SET fastboot=fastboot.exe
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.004s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.069s]
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.339s]
finished. total time: 0.410s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.941s]
finished. total time: 1.078s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49368 KB)...
OKAY [ 1.586s]
writing 'modem'...
OKAY [ 0.802s]
finished. total time: 2.406s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (708 KB)...
OKAY [ 0.084s]
writing 'fsg'...
OKAY [ 3.179s]
finished. total time: 3.265s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.002s]
finished. total time: 0.002s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.002s]
finished. total time: 0.018s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (76 KB)...
OKAY [ 0.100s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.178s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.384s]
writing 'boot'...
OKAY [ 0.644s]
finished. total time: 1.030s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.379s]
writing 'recovery'...
OKAY [ 0.621s]
finished. total time: 1.016s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257288 KB)...
OKAY [ 8.130s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 8.051s]
finished. total time: 16.184s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (260812 KB)...
OKAY [ 8.239s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 8.069s]
finished. total time: 16.309s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 8.290s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 10.090s]
finished. total time: 18.380s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (18680 KB)...
OKAY [ 0.640s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 0.633s]
finished. total time: 1.274s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase cache
erasing 'cache'...
OKAY [ -0.000s]
finished. total time: -0.000s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe oem fb_mode_clear
...
OKAY [ 0.006s]
finished. total time: 0.022s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>pause
Press any key to continue . . .
---------- Post added 12th December 2015 at 12:14 AM ---------- Previous post was 11th December 2015 at 11:59 PM ----------
lost101 said:
@jpmaroco - I meant a log of you flashing the Firmware Image.
Click to expand...
Click to collapse
... and I get the same results if I use mfastboot instead of fastboot.
In the Phone, after
cmd: flash:boot
I get
hab check failed for boot
after
cmd: flash: recovery
i get
hab check failed for recovery
So, this seems to me that nothing is being flashed (It still keep my old twrp-2.8.7.0.-falcon_GPE.img recovery, not the stock one in GPE5.1 Lollipop)
I can boot in TWRP (after waiting for 5-6 minutes) but I can't factory reset because it says:
E: Could not mount /data and unable to find crypto footer
E: unable to mount /data
E:unbale to recreate /data/media/folder
... done
Does the same for "Storage" (unable to mount storage)...
Factory reset complete
failed
Should I try to flash the twrp-2.8.7.0.-falcon_STOCK.img?
Thanks for all your help lost101.

Latest GPE 5.1 Firmware Image: https://www.androidfilehost.com/?fid=24269982086992480
Use mfastboot.
Use these commands only:
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.0
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

lost101 said:
Latest GPE 5.1 Firmware Image: https://www.androidfilehost.com/?fid=24269982086992480
[/COLOR]
lost101 said:
Latest GPE 5.1 Firmware Image: https://www.androidfilehost.com/?fid=24269982086992480
I just reflashed the rom you sent me. I have the same "hab check failed" errors ;-(
And the phone just stays at the swirling dots after reboot... I think It is not writing anything ;-(. It still keeps the twrp recovery. if mfastboot was working than mfastboot flash recovery recovery.img should flash the stock (gpe) recovery, correct?
Thanks once again lost101, I appreciate your help!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

jpmaroco said:
I just reflashed the rom you sent me. I have the same "hab check failed" errors ;-(
And the phone just stays at the swirling dots after reboot... I think It is not writing anything ;-(. It still keeps the twrp recovery. if mfastboot was working than mfastboot flash recovery recovery.img should flash the stock (gpe) recovery, correct?
Click to expand...
Click to collapse
Yes. Emmc appears now to be read-only - an issue that is regularly reported on this forum and one that has no solution.

lost101 said:
Yes. Emmc appears now to be read-only - an issue that is regularly reported on this forum and one that has no solution.
Click to expand...
Click to collapse
No solution? Só my moto g is dead for good and there's no way to recover it?

moto g2 4g model rooted after booting is failed
hi i am venkat
i am rooted my moto g2 4g , battery is low mobile is shutdown, after i am trying to power on the device one binary code is coming in that device is Locked status code : 0 showing
i am trying to start normal mode ,recovery mode, factory mode, but i am fail , i dont know how to solve this, please help me,
thank you ...

[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.

I can not restore the Moto G

Well...
at first, the phone was on and off, but not out of the opening of the motorola screen (that with an M).
so I followed the procedures to place a stock ROM on the device.
only began giving error permission.
and finally, do not leave the mode boot screen with the following message in pink:
failed to validate system image.
any key that I press, you give this message.
Am I forgetting any procedure that is not written?
because I followed the procedure just right:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot

wadsonleite said:
Well...
at first, the phone was on and off, but not out of the opening of the motorola screen (that with an M).
so I followed the procedures to place a stock ROM on the device.
only began giving error permission.
and finally, do not leave the mode boot screen with the following message in pink:
failed to validate system image.
any key that I press, you give this message.
Am I forgetting any procedure that is not written?
because I followed the procedure just right:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=OEoJgNUrM7U

That command list is only an example, not to be followed blindly. You have to look at the actual firmware files in the folder you have downloaded. The correct commands could be for instance:
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
Provide more information if you still need help. Model number, name of firmware image, logs - lots and lots of logs. Screenshots of command prompt.

lost101 said:
That command list is only an example, not to be followed blindly. You have to look at the actual firmware files in the folder you have downloaded. The correct commands could be for instance:
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
Provide more information if you still need help. Model number, name of firmware image, logs - lots and lots of logs. Screenshots of command prompt.
Click to expand...
Click to collapse
Lost101,
I do not know exactly what model of this machine because my brother always says Moto G.
I know it's dual because it is easy to observe it.
but the exact model I do not know what it is.
I believe it is the Moto G xt1033, but not sure.
as no power, I do not know how to identify the correct model.
how do I find the right model?
there is a way I start from 0
I can start the entire procedure as if the device had not firmware?
how to identify the firmware that is currently on the device? Any command that identifies?
Grateful

@wadsonleite - XT1033 is the Dual-SIM model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
No requirements, simply include all commands and check the names of included sparsechunk files in firmware folder. Provide a log if you have any problems. Copy and paste command prompt screen. Take screenshots.

@wadsonleite - Do not try different firmware images. If you do not know what you are doing, there is a chance you will destroy the phone. Only do what you are directed to do in this thread.

lost101 said:
@wadsonleite - Do not try different firmware images. If you do not know what you are doing, there is a chance you will destroy the phone. Only do what you are directed to do in this thread.
Click to expand...
Click to collapse
in the first link, there are several images to my device.
use which one?
4.4.2
4.4.3
4.4.4
5.0.2
5.1

wadsonleite said:
in the first link, there are several images to my device.
use which one?
4.4.2
4.4.3
4.4.4
5.0.2
5.1
Click to expand...
Click to collapse
I'll assume you want to flash the Retail Asia Firmware Image.
Retail Asia - XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7
Fastboot commands: (download mfastboot if needed)
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.0
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
Provide logs if phone does not boot into Android.

lost101 said:
I'll assume you want to flash the Retail Asia Firmware Image.
Retail Asia - XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7
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.0
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
Provide logs if phone does not boot into Android.
Click to expand...
Click to collapse
i start.
but in the first command an error occur:
The program could not be started because it is missing AdbWinApi.dll on your computer. try reinstalling it to solve this problem
emailed with 2 pictures

wadsonleite said:
The program could not be started because it is missing AdbWinApi.dll on your computer. try reinstalling it to solve this problem
Click to expand...
Click to collapse
Missing files are in this zip: https://www.androidfilehost.com/?fid=24269982086993793
Extract everything into the folder with the firmware files. Run mfastboot in command prompt from that folder.
Edit: Before you do anything else. Are you sure this Moto G is (1st Gen) and not 2nd Gen?

lost101 said:
Extract everything into the folder with the firmware files. Run mfastboot in command prompt from that folder.
Click to expand...
Click to collapse
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash partition gpt.bin
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash partition gpt.bin
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot.exe
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-P enable parallel loading for multi-fla
sh if
there is no enough memory on host to
load
whole image
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>

C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.040s]
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.325s]
finished. total time: 0.378s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.110s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.116s]
finished. total time: 1.226s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.101s]
finished. total time: 0.183s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.410s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.874s
an error occur

wadsonleite said:
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml
an error occur
Click to expand...
Click to collapse
Is there a particular reason why you have called the folder "moto g 2"? It's important to establish which generation Moto G you have.

lost101 said:
Is there a particular reason why you have called the folder "moto g 2"? It's important to establish which generation Moto G you have.
Click to expand...
Click to collapse
because there is already a folder called Moto G on PC.
to make the procedure exactly as you pointed out to me, I thought I'd create another folder to not confuse the files.

wadsonleite said:
because there is already a folder called Moto G on PC.
to make the procedure exactly as you pointed out to me, I thought I'd create another folder to not confuse the files.
Click to expand...
Click to collapse
It looks like you need to unlock the Bootloader.
Bootloader Unlocking Tutorial: http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6

lost101 said:
It looks like you need to unlock the Bootloader.
Bootloader Unlocking Tutorial: http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
Click to expand...
Click to collapse
android sdk installed:
C:\Users\Wadson\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
but the command does not work:
Microsoft Windows [versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\Users\Wadson>cd C:\Users\Wadson\AppData\Roaming\Microsoft\Windows\Start Menu\
Programs
C:\Users\Wadson\AppData\Roaming\Microsoft\Windows\Start Menu\Programs>$ fastboot
oem get_unlock_data
'$' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\Wadson\AppData\Roaming\Microsoft\Windows\Start Menu\Programs>

wadsonleite said:
android sdk installed:
C:\Users\Wadson\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
but the command does not work:
Microsoft Windows [versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\Users\Wadson>cd C:\Users\Wadson\AppData\Roaming\Microsoft\Windows\Start Menu\
Programs
C:\Users\Wadson\AppData\Roaming\Microsoft\Windows\Start Menu\Programs>$ fastboot
oem get_unlock_data
'$' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\Wadson\AppData\Roaming\Microsoft\Windows\Start Menu\Programs>
Click to expand...
Click to collapse
You already had mfastboot working. You don't need SDK or anything else. Just run the following command in the firmware files folder:
mfastboot oem get_unlock_data

lost101 said:
You already had mfastboot working. You don't need SDK or anything else. Just run the following command in the firmware files folder:
mfastboot oem get_unlock_data
Click to expand...
Click to collapse
the device lives!
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash logo logo.bin
< waiting for device >
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.031s]
writing 'logo'...
OKAY [ 0.082s]
finished. total time: 0.118s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.373s]
writing 'boot'...
OKAY [ 0.921s]
finished. total time: 1.299s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.372s]
writing 'recovery'...
OKAY [ 0.902s]
finished. total time: 1.280s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 8.521s]
writing 'system'...
OKAY [ 15.590s]
finished. total time: 24.117s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256949 KB)...
OKAY [ 8.537s]
writing 'system'...
OKAY [ 15.085s]
finished. total time: 23.628s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260404 KB)...
OKAY [ 8.650s]
writing 'system'...
OKAY [ 15.147s]
finished. total time: 23.802s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166184 KB)...
OKAY [ 5.542s]
writing 'system'...
OKAY [ 10.761s]
finished. total time: 16.311s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_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.683s]
writing 'modem'...
OKAY [ 2.180s]
finished. total time: 3.869s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.025s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.024s]
finished. total time: 0.025s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_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 [ 5.314s]
finished. total time: 5.378s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.066s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.489s]
finished. total time: 0.491s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>mfastboot reboot
rebooting...
finished. total time: 0.001s
C:\Users\Wadson\Desktop\moto g 2\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.
xml>
now I need to lock the bootloader again?
I'd like to post pictures, but I have not yet allowed the forum ..

wadsonleite said:
now I need to lock the bootloader again?
Click to expand...
Click to collapse
No.

lost101 said:
No.
Click to expand...
Click to collapse
thanks!!!
now, i think we can now close this topic

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

Database Info

welcome