Database Info

[Q] Moto G screen is on but black, can't boot in recovery mode, debugging is off

Hello everyone.
I have trouble with my Moto G (XT1032). Like in the topic the phone is on. I can blindly click on some things that i remember where they are and i hear the sound of them but...
I cant boot into recovery mode, the debug mode is off so i cant use adb. It happened after battery died and when i put it to recharge this weird thing happens.
Phone is unlocked and custom rom (Lollipop from this forum).
I really dont know what to do, please help.
EDITED:
Oh, and adb and fastboot don't "see" the device. Yes i have all drivers installed.

I have the same problem. I am not able to install recovery.img. it gives me this error:
sending 'recovery' (7880 KB)...
OKAY [ 0.266s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.239s
and mismatched partion size. How can I recovery it?
---------- Post added at 05:53 PM ---------- Previous post was at 05:12 PM ----------
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>"Step 2_1.bat"
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.359s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.702s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.320s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.718s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (255843 KB)...
OKAY [ 13.119s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 22.057s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (245954 KB)...
OKAY [ 12.853s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.089s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (235703 KB)...
OKAY [ 12.494s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 24.256s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 6.520s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.559s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.999s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.999s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (717 KB)...
OKAY [ 5.085s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.108s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.999s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.983s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>

I have tried everything. everything I try to flash fails, why? I think thhat the smartphone is broke

XT1033 Hard Brick Help

Hello, i have an xt1033 moto g hard bricked, it boots up normal, but the system crash till the phone reboots, i enter in the fastboot mode and try to flash 4.4.4 again or 5.0.1, no errors at all, but when i reboot the phone it dont have changed nothing, continue with the crashes and the same apps showing.
And adb devices dosnt show nothing, just fastboot recognizes the device. Already tried to flash a custom recovery, it dosnt change, no errors when trying to flash, but when you enter recovery it is the standard one, adb sideload always show an error after reading the file i send.
Already tried erase all the files, but the phone reboot as the same, crashing and rebooting.
I already tried everything i found to revive the phone but whit no luck, tried the RSDLite too but it dosnt recognize my cellphone, i dont know what to do anymore :crying:
Any help are welcome, thanks and sorry for my bad english

Post logs of what happens when you try to flash the XT1033 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
Post logs of what happens when you try to flash the XT1033 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Here are my full log, system dosnt have changed nothing after all this. Same problems. Already tried to update the bootloader bot it dosnt change too
Microsoft Windows [versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0426104575 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase all
erasing 'all'...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing hob ...
(bootloader) erasing dhob ...
(bootloader) erasing fsg ...
(bootloader) erasing fsc ...
(bootloader) erasing clogo ...
(bootloader) erasing cache ...
(bootloader) erasing userdata ...
OKAY [ 4.758s]
finished. total time: 4.758s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.390s]
finished. total time: 0.421s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot
.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.104s]
finished. total time: 1.213s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.047s]
finished. total time: 0.125s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.661s]
finished. total time: 1.083s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.421s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.076s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257887 KB)...
OKAY [ 8.742s]
writing 'system'...
OKAY [ 7.894s]
finished. total time: 16.636s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (256762 KB)...
OKAY [ 8.940s]
writing 'system'...
OKAY [ 8.225s]
finished. total time: 17.181s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (260106 KB)...
OKAY [ 9.013s]
writing 'system'...
OKAY [ 8.315s]
finished. total time: 17.327s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (166048 KB)...
OKAY [ 5.863s]
writing 'system'...
OKAY [ 6.367s]
finished. total time: 12.230s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
target reported max download size of 536870912 bytes
sending 'modem' (49356 KB)...
OKAY [ 1.794s]
writing 'modem'...
OKAY [ 0.796s]
finished. total time: 2.605s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.047s]
writing 'fsg'...
OKAY [ 3.188s]
finished. total time: 3.251s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.000s

Never
EVER
use
fastboot erase all​
You have erased partitions unique to your phone, you have lost IMEI - you will never be able to make calls over a network again. You should not have used that command. It might be possible to get a ROM booting again, but don't expect anything more than a tablet from now on. Sorry.

lost101 said:
Never
EVER
use
fastboot erase all​
You have erased partitions unique to your phone, you have lost IMEI - you will never be able to make calls over a network again. You should not have used that command. It might be possible to get a ROM booting again, but don't expect anything more than a tablet from now on. Sorry.
Click to expand...
Click to collapse
i tried this command to see if something change , but the cellphone is still the same, crashing till reboots, dont know what to do to repair its os it still have the same apps installed, runing the same way, nothing works .-.

d3vileyes said:
i tried this command to see if something change , but the cellphone is still the same, crashing till reboots, dont know what to do to repair its os it still have the same apps installed, runing the same way, nothing works .-.
Click to expand...
Click to collapse
Try using mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065​

same thing, i tried to lock my bootloader too but shows an error at the end, the system dont changed again.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 1.576s]
finished. total time: 1.576s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash partition gp
t.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.359s]
finished. total time: 0.374s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash motoboot mot
oboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.112s]
finished. total time: 1.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash logo logo.bi
n
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.047s]
finished. total time: 0.109s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash boot boot.im
g
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.655s]
finished. total time: 1.061s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash recovery rec
overy.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.406s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.061s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257887 KB)...
OKAY [ 9.058s]
writing 'system'...
OKAY [ 8.189s]
finished. total time: 17.262s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256762 KB)...
OKAY [ 8.958s]
writing 'system'...
OKAY [ 8.239s]
finished. total time: 17.197s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260106 KB)...
OKAY [ 9.159s]
writing 'system'...
OKAY [ 8.317s]
finished. total time: 17.476s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166048 KB)...
OKAY [ 5.848s]
writing 'system'...
OKAY [ 6.365s]
finished. total time: 12.229s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash modem NON-HL
OS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.794s]
writing 'modem'...
OKAY [ 0.842s]
finished. total time: 2.652s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.094s]
writing 'fsg'...
OKAY [ 3.167s]
finished. total time: 3.276s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 17.434s

Download TWRP: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Use the command: mfastboot flash recovery twrp-2.8.6.0-falcon.img
Enter Recovery and confirm TWRP works.
Report back.

tried again with no luck, recovery dosnt change too, i tried the f2f and the ext4.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10184 KB)...
OKAY [ 0.382s]
writing 'recovery'...
OKAY [ 0.184s]
finished. total time: 0.569s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery openrec
overy-twrp-2.8.4.0-falcon_STOCK.img
target max-sparse-size: 256MB
sending 'recovery' (8168 KB)...
OKAY [ 0.280s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.440s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery openrec
overy-twrp-2.8.4.0-falcon_GPE.img
target max-sparse-size: 256MB
sending 'recovery' (8168 KB)...
OKAY [ 0.286s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.451s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Try: mfastboot boot openrecovery-twrp-2.8.4.0-falcon_STOCK.img

lost101 said:
Try: mfastboot boot openrecovery-twrp-2.8.4.0-falcon_STOCK.img
Click to expand...
Click to collapse
It worked, it booted on twrp, but if i try to restore or something else it give me "unable to mount /cache" error

Try to format ( wipe and format are different things) cache partition in recovery or using fastboot command
fastboot erase cache

sjandroiddeveloper said:
Try to format ( wipe and format are different things) cache partition in recovery or using fastboot command
fastboot erase cache
Click to expand...
Click to collapse
Everything i try to do it say "unable to mount /cache", i think the /cache partition is bricked, i cant repair or format it, and every time i try to do something it shows me an error :/

d3vileyes said:
Everything i try to do it say "unable to mount /cache", i think the /cache partition is bricked, i cant repair or format it, and every time i try to do something it shows me an error :/
Click to expand...
Click to collapse
I had a problem when my data partition was no mounting
Whenever I flashed a ROM or wiped data or factory reset it gave error cannot mount data
I repaired it by formating data partition using Philz recovery
I am again saying wipe and format are different concepts
Do one thing flash Philz recovery because in twrp you can only format data and not system and cache
So flash Philz touch
Go to wipe and format>Custom format and format cache partition
Then it should work

sjandroiddeveloper said:
I had a problem when my data partition was no mounting
Whenever I flashed a ROM or wiped data or factory reset it gave error cannot mount data
I repaired it by formating data partition using Philz recovery
I am again saying wipe and format are different concepts
Do one thing flash Philz recovery because in twrp you can only format data and not system and cache
So flash Philz touch
Go to wipe and format>Custom format and format cache partition
Then it should work
Click to expand...
Click to collapse
When i try to boot philz_touch_6.58.7-falcon it boots the Motorola logo and crash to a black screen, after this it boots the system
~~~~~~~edit~~~~~~
tried another version of philz touch and it worked, i'm gonna try to format now

d3vileyes said:
When i try to boot philz_touch_6.58.7-falcon it boots the Motorola logo and crash to a black screen, after this it boots the system
Click to expand...
Click to collapse
Did you try the fastboot command
fastboot erase cache
For formatting cache partition
Do it and see that in twrp (since you cannot flash Philz ) that the error is still there or not

sjandroiddeveloper said:
Did you try the fastboot command
fastboot erase cache
For formatting cache partition
Do it and see that in twrp (since you cannot flash Philz ) that the error is still there or not
Click to expand...
Click to collapse
I used the command fastboot erase cache, same error on twrp
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.000s
~~~~~~~~edit~~~~~~
now i can boot philz recovery, i formated /cache and /sdcard, in the screen shows OK but nothing changes

@d3vileyes - I would use adb push a ROM.zip and try flashing that in TWRP. Recovery mode adb is possible, but doesn't always work for Windows users. On a Linux PC / Laptop - it will always work.
ADB command: adb push rom.zip /sdcard/
XT1033 Lollipop ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

lost101 said:
@d3vileyes - I would use adb push a ROM.zip and try flashing that in TWRP. Recovery mode adb is possible, but doesn't always work for Windows users. On a Linux PC / Laptop - it will always work.
ADB command: adb push rom.zip /sdcard/
Click to expand...
Click to collapse
when i try to adb push i get this error
Failed to copy 'xt1033_retail_Brazil.zip' to '/sdcard//xt1033_retail_Brazil.zip': Read-only file system
~~~~~~edit~~~~~
Fixed this error with adb shell
mount -o remount rw /sdcard
but when i try to flash it gaves me the same error "unable to mount /cache"
don't know whats going on with the /cache folder

d3vileyes said:
I used the command fastboot erase cache, same error on twrp
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.000s
~~~~~~~~edit~~~~~~
now i can boot philz recovery, i formated /cache and /sdcard, in the screen shows OK but nothing changes
Click to expand...
Click to collapse
First of all when you formatted cache partition in Philz recovery, did it come in the logs below that formatting cache successful or something like that or it again appeared that cannot Mount cache
If it appeared that cache formatting successful then try and wipe cache this time and it should come wipe cache complete
If that happens you are good to go
Just flash a rom again and this time should be successful
sent from falcon
PRESS THANKS IF HELPED?????

Moto G X1028 issues and problems

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

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

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

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

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

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

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

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

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

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

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

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

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

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

reformat the partitions how does one do this ?

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

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

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

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

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

[Q] [XT1032] Can't Mount or Erase Partitions - PLEASE HELP

Hi, today my Falcon got Bootlooped on Stock Flashable Zip Optimized v1 after severals week of working without problems.
Then i tried to Factory Reset using TRWP, but it failed.
After that i enter recovery mode and used mtp usb to copy the Zip to install it tru recovery, but after getting 44Mb of the zip file on my phone then a message appeared saying that y disconnected the cable, i cancelled the process.
On my second try i could copy anything on my phone, seems like the filesystem gone broke, all the folders appeared but they dont show files inside.
Then i tried, to flash Stock Brazilian 5.0.2 Using fastboot but always get the CANT ERASE PARTITION - CANT FLASH PARTITION.
But i can Flash Recoveries, i flashed CWM and tried to wipe without success, tried the special recovery from phill without success.
I think the problem is the partition table. al the partitions are there, i can see them, twrp says they are present, and everyone has filesize.
But i cant flash, erase partitions, cant sideload.
Please help me.
DETAILS:
MOTO G XT1032
LAST ROM: STOCK OPTIMIZED 5.1 v1b
BOOTLOADER: 41.18
RECOVERY: TRWP
LAST TRY OF RESTORING STOCK ROM:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery cwm.img
target reported max download size of 536870912 bytes
sending 'recovery' (7878 KB)...
OKAY [ 0.320s]
writing 'recovery'...
OKAY [ 0.310s]
finished. total time: 0.630s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.043s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.337s]
finished. total time: 0.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash rpm
FAILED (remote failure)
finished. total time: 10.948s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 5.079s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.919s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.img
target max-sparse-size: 256MB
error: cannot load 'logo.img': No error
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.370s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.784s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot fkasg system system.i
mg_sparsechunk.0
usage: fastboot [ <option> ] <command>
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 14.002s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 22.464s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 13.999s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 22.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 14.094s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 22.612s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.734s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.772s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.023s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 5.039s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.080s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.994s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\Program Files (x86)\Minimal ADB and Fastboot>

Motorola Moto G 8GB - Cant Reset/Flash

Hi,
I have a problem. Can anyone help ?
I have 2 (two) Motorola Moto G 8GB, one of then works fine, is my personal phone (android 5.0.2 - retail.uk - bootloader lock).
But my problem is with the second one, i bought him used with a software problem that to me looks simple. Turn on the phone and show me the screen notification of bootloader unlock and enter in the system. But when in the system simple crashed everything and receive notification like for example: "unfortunately, sytemui has stopped.", "unfortunately, dialer has stopped.", etc..
Seems easy to solved, just do a reset, right ?
The problem starts when i try to reset via software (settings > backup) won't reset!! I click in the button and nothing happens. And via hardware (Vol + Power) i do "wipe cache partition" and "wipe data/factory reset" he resets but still the same, nothing change.
When i try flash a rom he flashes but nothing change, stay the same!
Flashing recieve this pink errors:
hab check failed for boot
hab check failed for recovery
Phone Information:
VersãoAndroid
4.4.4
Versão Bandbase
MSM8626BP_1032.390.81.01P RETUSA_GLB_CUST
Versão Kernel
3.4.42-gc146877
Versão sistema
210.12.61.falcon_umts.retail.en.us
Numero Compilação
KXB21.14-L1.61
- Can anyone help?
- Any ideas?

Sounds like a failed eMMC. If that is the case, there is nothing that can be done.
Sent from my XT1031

Try flashing the Factory Firmware Image: (I assume XT1032 5.0.2 Retail US?)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​

lost101 said:
Try flashing the Factory Firmware Image: (I assume XT1032 5.0.2 Retail US?)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​
Click to expand...
Click to collapse
Thanks for reply,
Already did that (i guess) and no positive results.
Let me try explain to see if is anything wrong.
I follow this guide; http://forum.xda-developers.com/showthread.php?t=2542219
Download this:
Download mfastboot-v2.zip http://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280
[ c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip]
XT1032 (Global GSM) - [4.4.4] - Retail US
https://drive.google.com/file/d/0B6RNTe4ygItBeUd1WXZFaEY4UjA/view
Installed Minimal ADB and Fastboot and extrated mfastboot-v2 and Rom to there
Executed Minimal ADB.
Results:
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.344s]
finished. total time: 0.391s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.109s]
finished. total time: 1.219s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.047s]
finished. total time: 0.125s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.391s]
writing 'boot'...
OKAY [ 0.672s]
finished. total time: 1.063s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.391s]
writing 'recovery'...
OKAY [ 0.703s]
finished. total time: 1.094s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257791 KB)...
OKAY [ 8.469s]
writing 'system'...
OKAY [ 7.954s]
finished. total time: 16.423s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256969 KB)...
OKAY [ 8.438s]
writing 'system'...
OKAY [ 8.094s]
finished. total time: 16.548s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (256909 KB)...
OKAY [ 8.438s]
writing 'system'...
OKAY [ 8.094s]
finished. total time: 16.532s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (152521 KB)...
OKAY [ 5.031s]
writing 'system'...
OKAY [ 6.735s]
finished. total time: 11.766s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49368 KB)...
OKAY [ 1.688s]
writing 'modem'...
OKAY [ 0.797s]
finished. total time: 2.484s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (709 KB)...
OKAY [ 0.109s]
writing 'fsg'...
OKAY [ 3.188s]
finished. total time: 3.297s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Seems to me everything is done correctly, but the phone stays the same. And in the phone i have 2 pink errors when flashing boot.img and recovery.
Errors (see the photos):
Had check failed for recovery
Had check failed for boot

Could you unlock Bootloader (if not already done) and flash TWRP. Then try a custom ROM.

lost101 said:
Could you unlock Bootloader (if not already done) and flash TWRP. Then try a custom ROM.
Click to expand...
Click to collapse
Dude, i can't flash anything. I flash via bootloader and have 2 errors just on the phone "Had check failed for recovery" , "Had check failed for boot".
I try "adb sideload" and the installation aborted by himself and say " installation aborted"
See what happens here (photos): https://drive.google.com/folderview...dFMHNMWngzMkhNWW9mVi0wM1dfeW1KOHc&usp=sharing

You have a failed eMMC. There is nothing that can be done to "save" or "restore" your device.
Sent from my XT1031

Nice ..
Who the **** is emmc ? is like a HDD on a pc ?

brunodpferreira said:
Nice ..
Who the **** is emmc ? is like a HDD on a pc ?
Click to expand...
Click to collapse
Embedded Multi Media Card - http://www.datalight.com/solutions/technologies/emmc/what-is-emmc
Sent from my XT1031