Database Info

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

[Q] No sim card after trying to restore to stock

I need help. I was using KK and everything was working fine. So I installed lolipop xt1039 stock version, the sim and wifi werent working
So I did the update of the radio firmware and the wifi started working but the sim chip has not.
I tried everything... Wiped cache, data, dalvinik... still nothing makes the sim card work
I even tried going back to KK and reverting the radio firmware but even in KK the sim chip is not being recognized anymore.
I managed to install recovery TWRP-v2.8.3.0, the latest peregrin build that I found in this forum.
Made a full wipe, factory, data, you name it.
After this I installed android 4.4.4, 4.4.3...via fastboot
using the steps in this thread
http://forum.xda-developers.com/moto...kxb21-t2805619
And still no network. Wifi and gps works just fine, but no sim is detected.
The sim is working just fine, I tested it on other phone and it works. I also tested another sim chip that was working in my other phone into my moto g and no luck so far.

It could be you need to upgrade your Bootloader. I only suggest this as you appear to have tried everything else. On Moto G non-LTE this step is not necessary, but with Peregrine, things may be different.
This utility will allow you to upgrade to the XT1039 Lollipop Bootloader (v41.1A) - http://forum.xda-developers.com/moto-g/development/falcon-bootloader-upgrader-tool-t3093793

lost101 said:
It could be you need to upgrade your Bootloader. I only suggest this as you appear to have tried everything else. On Moto G non-LTE this step is not necessary, but with Peregrine, things may be different.
This utility will allow you to upgrade to the XT1039 Lollipop Bootloader (v41.1A) - http://forum.xda-developers.com/moto-g/development/falcon-bootloader-upgrader-tool-t3093793
Click to expand...
Click to collapse
Do you think its worth the risk of hardbricking?

flivon said:
Do you think its worth the risk of hardbricking?
Click to expand...
Click to collapse
The only hardbrick risk is if you start trying to flash the KitKat Bootloader afterwards.

lost101 said:
The only hardbrick risk is if you start trying to flash the KitKat Bootloader afterwards.
Click to expand...
Click to collapse
I don't think its a software problem, because I did everything one could do to try to reanimate his phone and still got nothing. Also, no one complained about having this problem when installing stock LP.
I updated the bootloader. Still the problem persists... I guess I will need to buy another phone :/
Question: Would using mfastboot instead of fastboot make a difference?

flivon said:
Would using mfastboot instead of fastboot make a difference?
Click to expand...
Click to collapse
Yes, always use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065​
There are many more things to try, do not give up yet.

lost101 said:
Yes, always use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065​
There are many more things to try, do not give up yet.
Click to expand...
Click to collapse
Tried again with mfastboot. Nothing

exactly same problem here.
SIM card doesn't see any services. Also, check that you can't dial 911 or 112 - it doesn't work!

Do either of you still have an IMEI number?

lost101 said:
Do either of you still have an IMEI number?
Click to expand...
Click to collapse
I have IMEI number....
lost101, if you can help:
http://forum.xda-developers.com/showpost.php?p=61704870&postcount=44

lost101 said:
Do either of you still have an IMEI number?
Click to expand...
Click to collapse
Yes, I have IMEI number too

Try this app: https://play.google.com/store/apps/details?id=com.sibbor.getril
Edit: Nevermind, app does not support Moto G.

Gosh, exactly the same issue. Was just going to create a new post. Here is what I wrote:
tl;dr: Location-UK. Rooted MotoG and installed CM11, found that the mobile network connectivity is gone. Flashed EU spec stock 5.0.2, still no luck. Status says Radio is off. What can I do to salvage it? (Still shows a valid IMEI). WiFi works fine.

@flivon - Is your phone originally XT1039 Retail EU?
XT1039 Retail EU 5.1 Radio: http://forum.xda-developers.com/devdb/project/dl/?id=13433
Use only the following commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​

lost101 said:
@flivon - Is your phone originally XT1039 Retail EU?
XT1039 Retail EU 5.1 Radio: http://forum.xda-developers.com/devdb/project/dl/?id=13433
Use only the following commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
Click to expand...
Click to collapse
No. Its not. Its actually Brazilian retail. Also, trying to flash EU radio does not work.

@flivon - You can get more information about what is happening with radio by doing the following:
1) Dial: *#*#4636#*#*
2) Tap 'Phone information'
What is stated for:
GSM service
Network type
Also try turning radio off and on from this screen.

lost101 said:
@flivon - You can get more information about what is happening with radio by doing the following:
1) Dial: *#*#4636#*#*
2) Tap 'Phone information'
What is stated for:
GSM service
Network type
Also try turning radio off and on from this screen.
Click to expand...
Click to collapse
Turning radio on and off did nothing apparently
GSM service: Emergency calls only
Network type: Unknown

@flivon - Before trying anything else, I would like to see a mfastboot log of you flashing the Retail Brazil Firmware Image.
XT1040 Retail Brazil 5.1 Firmware Image: http://forum.xda-developers.com/showpost.php?p=61365158&postcount=592

lost101 said:
@flivon - Before trying anything else, I would like to see a mfastboot log of you flashing the Retail Brazil Firmware Image.
XT1040 Retail Brazil 5.1 Firmware Image: http://forum.xda-developers.com/showpost.php?p=61365158&postcount=592
Click to expand...
Click to collapse
The rom booted but still no sim card.
log:
Code:
C:\Users\Felipe\Desktop\fastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.042s]
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.365s]
finished. total time: 0.411s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.123s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.115s]
finished. total time: 1.240s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.069s]
writing 'logo'...
OKAY [ 0.076s]
finished. total time: 0.146s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.389s]
writing 'boot'...
OKAY [ 0.732s]
finished. total time: 1.124s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.729s]
finished. total time: 1.132s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257719 KB)...
OKAY [ 8.682s]
writing 'system'...
OKAY [ 11.477s]
finished. total time: 20.163s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257506 KB)...
OKAY [ 8.696s]
writing 'system'...
OKAY [ 10.234s]
finished. total time: 18.933s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (255259 KB)...
OKAY [ 8.583s]
writing 'system'...
OKAY [ 15.590s]
finished. total time: 24.178s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (189925 KB)...
OKAY [ 6.429s]
writing 'system'...
OKAY [ 9.097s]
finished. total time: 15.529s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60232 KB)...
OKAY [ 2.073s]
writing 'modem'...
OKAY [ 1.618s]
finished. total time: 3.695s
C:\Users\Felipe\Desktop\fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.023s
C:\Users\Felipe\Desktop\fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.023s]
finished. total time: 0.024s
C:\Users\Felipe\Desktop\fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (661 KB)...
OKAY [ 0.070s]
writing 'fsg'...
OKAY [ 5.674s]
finished. total time: 5.747s
C:\Users\Felipe\Desktop\fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.338s]
finished. total time: 0.339s
C:\Users\Felipe\Desktop\fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 3.870s]
finished. total time: 3.871s
C:\Users\Felipe\Desktop\fastboot>mfastboot reboot
rebooting...
finished. total time: 0.003s

flivon said:
The rom booted but still no sim card.
log:
<snip>
Click to expand...
Click to collapse
Fastboot log looks good. I still think you should try a brand new SIM.
EDIT: Maybe even unlock phone to all networks if not already done. Doing so may trigger a hardware change.

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

xt1033 black screen after flashing 4.4.4 or 5.02

good moorning people, i need help.
the situation is that i got my cellphone done some weird process that i cant identify, my brother inlaw took it and gave it back with unlock bootloader as a friend of his were going to``improve it´´, i guess bootloader has been unlocked as it shows the logo in red and white, and says phone is unlocked status 3. so i do get afterwards d motorola presentation and the blue moto logo and then a black screen. seen that i dont know what really happen to the cellphone, aa he had it for a long time im not sure wich firmware it had when the bad procedure happend. maybe 4.4.4 or 5.02. it may have been the actualization for ota, but i dint think so
now some important points, in fastboot mode i cant get to recovery mode with ususal botton combination, try to apply pdate from sd card or hard reset is imposible from fastboot in the phone, i cant access recovery, so i did make it happen by adb. i also tried to flas a twrp by adb but it didnt work, i got lieng android, when trying to boot into recovery.
i got a thrustable stock rom 4.4.4 brasil and flashed it and i got the primary gpt downgrade failed and the one for tz the rest of the log was just cool, but i got the black screen, from this i though that it may jus be running before the lollipop version, as it said failed for downgrade, but i dont understand so much about to make such a coclusion, researching i did found that this is just normal when downgrading, for those 2 first commands so i did flash lollipop 5.0 and got 2 other errors hab check failed for boot hab check failed for recovery, please help me with this, nest ill hang full log when flashing 5.0 , remember at the end i get black screen. Now this is interesting, the cellphone did boot now, but touch does not work, this happend already before, only once, im reeboting it at the moment and yes, the black screen has been shown again, it does not seem like touch may have any problem, it looks good, but those two times it came up it did not work.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.025s]
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.316s]
finished. total time: 0.346s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.101s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.940s]
finished. total time: 1.051s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.055s]
writing 'logo'...
OKAY [ 0.064s]
finished. total time: 0.127s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.421s]
writing 'boot'...
OKAY [ 0.607s]
finished. total time: 1.036s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.435s]
writing 'recovery'...
OKAY [ 0.617s]
finished. total time: 1.061s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 9.641s]
writing 'system'...
OKAY [ 7.984s]
finished. total time: 17.638s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256782 KB)...
OKAY [ 9.722s]
writing 'system'...
OKAY [ 8.319s]
finished. total time: 18.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260098 KB)...
OKAY [ 9.616s]
writing 'system'...
OKAY [ 8.427s]
finished. total time: 18.057s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (160376 KB)...
OKAY [ 6.036s]
writing 'system'...
OKAY [ 6.487s]
finished. total time: 12.536s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.874s]
writing 'modem'...
OKAY [ 0.824s]
finished. total time: 2.711s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.018s]
finished. total time: 0.025s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.019s]
finished. total time: 0.025s
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.086s]
writing 'fsg'...
OKAY [ 3.187s]
finished. total time: 3.287s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.024s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.028s]
finished. total time: 0.035s
C:\Program Files (x86)\Minimal ADB and Fastboot>

i suggest you get the latest firmware 5.1 for your device.
and use the same commands

I'm going to try that, thanks man.

AgentChaos said:
i suggest you get the latest firmware 5.1 for your device.
and use the same commands
Click to expand...
Click to collapse
Question, cause I really have flashed several stocks on this phone, when ur a latest version u mean like what, cause If I write that in Google all I get is like stock Rom, can u help me with this, xt1033, Brazil

I can't flash twrp or cwm, it's really complicated

Help. My phone randomly reboots into corrupt fastboot screen.

Hi all great minds of XDAdev
I have a Motorola 4G LTE XT1040, with unlocked bootloader , fastboot version 41.1A, TWRP 3.0.2.0 and stock 5.1 ROM.
I didn't have a downgrade and my phone is not bricked.
The thing is, my phone works normally until it randomly just freezes, then when I turn it on it goes to the dreaded screen with "fastboot reason: failed to initialize partition table status code 0"
If I try to select "normal startup" or something, it says "Failed to find boot image" or something like that, yet when I turn it off and on again, it starts normally. The problem is that the freezes are completely random.
I find very weird that whenever that forced restart happens it says "Status: LOCKED" when the phone isn't, and when I start fastboot manually it says unlocked and status code 3. Not only that, but can also select "Normal Startup" with no problem.
I've tried to install many ROMs and stuff through fastboot and recovery with no luck, the phone keeps restarting to the error screen and then starts normally until the next freeze.
What can I do? Is there something you think I could do to stop this? Should I post more info for you? Thank you!

fastboot flash partition

我日你打夜 said:
fastboot flash partition
Click to expand...
Click to collapse
Excuse me, what partirion should I flash? Still no luck and it's getting worse.

Flash the latest XT1040 Factory Firmware Image using Fastboot. If this does not resolve your issue, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
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

lost101 said:
Flash the latest XT1040 Factory Firmware Image using Fastboot. If this does not resolve your issue, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
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
Click to expand...
Click to collapse
Hi Lost. First of all, thank you very much, you're a great member.
Second, well, I don't know what to do. The symptoms are very random, sometimes it just goes to sleep and never wakes up, sometimes it freezes completely, then the screen locks itself and starts to flash until I hard reboot it, sometimes it goes to the corrupt fastboot screen I'm talking about. One special case which is very common under "stress" is that it goes to the lockscreen and while the screen becomes unresponsive, the lockscreen goes on and off, and the volume/power buttons work normally. Still, as it's unresponsive, it needs a hard reset to work again.
I tried your ROM and while the proccess goes normally the problem hasn't gone away (specially the "surprise lockscreen" thing). I tried to re-unlock the bootloader in one of the lucky times the phone got into the corrupt fastboot but it only says
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. total time: 0.016s
I tried to use the reset to fastboot option and the phone went to a black screen with no sings of life. Then, after a hard reset and normal fastboot reboot, there's nothing "wrong" and the screen says "unlocked".
The phone is almost unusable, as it seems to work fine until it suddenly doesn't. I'm certainly baffled.
If it helps, the phone was /probably/ in KitKat when I downloaded a stock Brazil ROM months ago to make the update to Lollipop. The phone didn't have this sudden reboot problem until a month or so ago.
This is the flash log, as you requested.
D:\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
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.336s]
finished. total time: 0.368s
D:\Minimal ADB and Fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.117s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.099s]
finished. total time: 1.221s
D:\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.063s]
writing 'logo'...
OKAY [ 0.070s]
finished. total time: 0.136s
D:\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.458s]
writing 'boot'...
OKAY [ 0.718s]
finished. total time: 1.181s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk0
target max-sparse-size: 256MB
sending 'system' (257719 KB)...
OKAY [ 10.299s]
writing 'system'...
OKAY [ 11.126s]
finished. total time: 21.447s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (257518 KB)...
OKAY [ 10.311s]
writing 'system'...
OKAY [ 9.891s]
finished. total time: 20.206s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (256627 KB)...
OKAY [ 10.376s]
writing 'system'...
OKAY [ 15.416s]
finished. total time: 25.796s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (189925 KB)...
OKAY [ 7.656s]
writing 'system'...
OKAY [ 8.848s]
finished. total time: 16.508s
D:\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60236 KB)...
OKAY [ 2.465s]
writing 'modem'...
OKAY [ 1.531s]
finished. total time: 4.001s
D:\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.025s
D:\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.023s]
finished. total time: 0.024s
D:\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (661 KB)...
OKAY [ 0.098s]
writing 'fsg'...
OKAY [ 5.681s]
finished. total time: 5.787s
D:\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.348s]
finished. total time: 0.353s
D:\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 2.999s]
finished. total time: 3.002s
D:\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.003s
Click to expand...
Click to collapse

You're not giving me enough information. I need to know exactly what Firmware Image you are flashing.
A new XT1040 Firmware Image was added in the last few days: XT1040_PEREGRINE_RETBR_5.1_LPBS23.13-35.5-1_cid12

Hi Lost, that's just the one I flashed (Brasil's newest build).

Ahasverus said:
Hi Lost, that's just the one I flashed (Brasil's newest build).
Click to expand...
Click to collapse
In the fastboot log you provided, the sparsechunks are incorrectly named.

lost101 said:
In the fastboot log you provided, the sparsechunks are incorrectly named.
Click to expand...
Click to collapse
Yeah that was due to the fastboot commands I copy/pasted, for them to work I needed to change their names. Did I do wrong?

Ahasverus said:
Yeah that was due to the fastboot commands I copy/pasted, for them to work I needed to change their names. Did I do wrong?
Click to expand...
Click to collapse
I just wanted to make sure. I do not believe the issues are related to the ROM change you mention doing a month ago. Over time, a certain percentage of Moto Gs experience corruption / failure that require a new mainboard - even if they are never dropped or get wet. The only other thing I can suggest you try is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​

lost101 said:
I just wanted to make sure. I do not believe the issues are related to the ROM change you mention doing a month ago. Over time, a certain percentage of Moto Gs experience corruption / failure that require a new mainboard - even if they are never dropped or get wet. The only other thing I can suggest you try is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
Oh, I see Well, this puts me a little wary of buying a MotoG 2015 as replacement. Will try the adb thing, thank you very much.

Ahasverus said:
Oh, I see Well, this puts me a little wary of buying a MotoG 2015 as replacement. Will try the adb thing, thank you very much.
Click to expand...
Click to collapse
Perhaps I should clarify; a certain percentage of any phone (from any manufacturer) as old as Moto G Falcon / Peregrine will fail. The phones were manufactured in 2013/2014. I still have more confidence in Motorola handsets than the alternatives in the same price range.

lost101 said:
Perhaps I should clarify; a certain percentage of any phone (from any manufacturer) as old as Moto G Falcon / Peregrine will fail. The phones were manufactured in 2013/2014. I still have more confidence in Motorola handsets than the alternatives in the same price range.
Click to expand...
Click to collapse
I see. I did the adb command formatting and it kept the same. Well, off to repair it goes. I wonder if you have an idea such I can tell the technician where to look at? Thank you so much for your help!

Ahasverus said:
I see. I did the adb command formatting and it kept the same. Well, off to repair it goes. I wonder if you have an idea such I can tell the technician where to look at? Thank you so much for your help!
Click to expand...
Click to collapse
I suspect you will be told the mainboard needs to be replaced - at pretty much the cost of a new phone. The cheapest fix would be to find a used, but functional Peregrine handset with broken screen on ebay and have the mainboard transplanted by someone who knows what they are doing.

Hi All! Just so you know, something REALLY WEIRD happened.
My phone kept locking as usual, it became ever more frequent to the point it was unusable. As a final measure I flashed the lastest brazil optimized stock rom because I thought "Well, if I'm getting it repaired, better have it on the best ROM and start anew". Then something weird happened, just as the ROM flashed and it turned into the very first "Welcome" screen, the phone froze in black, to never return. No hard reset, no corrupted fastboot screen, nothing. There I thought "Yep, it's done".
I waited for like 4 hours (was really busy) and after trying to turn it on again, I decided maybe it had no battery charge, so I plugged it in on my wall charger and then, oh god, some kind of whistling sound came from inside the phone. I could just thought "Yep it's going to explode", I was sure smoke was about to come out of the phone.. but it didn't. The sound eventually died out and then the notification LED turned on. No screen however, but the LED was permanently on.
I went to sleep with my dead phone in that state. Then after a night I woke up and went to check it, and I found.. the phone turned on, working normally. Of course I thought it was just a temporal thing but, well, it's been 3 days of normal use and it hasn't turned off, or froze, or anything. It's... fine.
It sounds like magic or voodoo, I have no idea what I did, if it's fixed or it's going to die again soon. But I thought it would be good to write this as a final post, as maybe someone will experience the same in the future and would like to have some hope, if only because he may need to backup his data.
So, what I /think/ did was
- Use TWRP Recovery and do a complete wipe of everything, even in advanced setting, just everything.
- Reboot to recovery
- Use the TWRP console command to manually insert the wiping commands lost101 suggested me as "last resort"
- Flash the lastest Brazil Optimized ROM as suggested by lost101
- ??? (Probably dry its battery to the lowest possible? like, when not even the screens turns on)
- ??? (Let it charging overnight or more, use a high voltage charger -I used Blackberry's-)
- Success.
Thank you very much lost101! And well, if you had an explanation for this weird behavior it would be much appreciated. Thanks!