MOTO G XT1032 black screen - Moto G Q&A, Help & Troubleshooting

I have a Moto G (XT1032) running Android 5.0.2 that went out of charge one day. It then decided to boot into a black screen - i.e. I can see the Motorola splash screen (animation) but all I get after that is a black (grey) screen, not responsive to touch.
I tried a few things and they didn't work -
Fastbooted and selected 'Recovery' option - The Motorola logo (first screen of startup splash screen) appears briefly. Then the device returns to fastboot menu saying 'Boot Up failed'
Fastbooted and selected 'Factory' - The Motorola splash screen appears, boots into same black (grey) screen again.
The fastboot menu says "Device is LOCKED. Status Code: 0". I did not enable USB debugging before my phone stopped working.
How do I get my phone working again?

You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​
Is there important data on the phone? Then do not use the command: mfastboot erase userdata

lost101 said:
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
Click to expand...
Click to collapse
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".

Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065​

C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.084s]
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.330s]
finished. total time: 0.418s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash motoboot motobo
ot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.151s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.957s]
finished. total time: 1.112s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.095s]
writing 'logo'...
OKAY [ 0.035s]
finished. total time: 0.132s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash recovery recove
ry.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.446s]
writing 'recovery'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 9.591s]
writing 'system'...
OKAY [ 7.728s]
finished. total time: 17.323s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.955s]
writing 'system'...
OKAY [ 8.082s]
finished. total time: 17.042s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 9.657s]
writing 'system'...
OKAY [ 8.179s]
finished. total time: 17.843s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 6.347s]
writing 'system'...
OKAY [ 6.282s]
finished. total time: 12.635s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.943s]
writing 'modem'...
OKAY [ 0.780s]
finished. total time: 2.727s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.022s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.090s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.279s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboot
Click to expand...
Click to collapse
Thats all that i got... i don't know what else to do...

Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2

pradeeppk said:
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
Click to expand...
Click to collapse
i do it, but i get the same message, "No Command"

lost101 said:
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
Click to expand...
Click to collapse
I see something wierd now, looks like the memory of the phone dosent save anything... sometimes, when the boot animation stops, i see the message of "1 of 1 Updates, android its updating" and then go to the black screen again... but, if i flash the phone, i shouldn't see that message, rigth? so, why i can still see it? how can i erase all the memory for sure???

Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img

lost101 said:
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
Click to expand...
Click to collapse
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja

Joncillo said:
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Click to expand...
Click to collapse
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/

lost101 said:
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
Click to expand...
Click to collapse
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?

Joncillo said:
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Click to expand...
Click to collapse
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip

lost101 said:
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
Click to expand...
Click to collapse
when i wipe the device, i get some errors.
E: MTP already enable
Formatting data using mkfs.f2fs...
Done
E: Unknown MTP message type 1:
You may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to stat '/data/data/com.google.android.gms/app_sslcache/www.googleapis.com.443'
E: Unable to stat '/data/data/com.google.android.calendar/databases/timelydata.db-shm'
...done
but don't wipe anything...
i try ADB Sideload but get an error too.
Starting ADB sideload feature... (After 10 minutes)
FAILED ADB Sideload complete.
and the CMD on windows says "Error: device not found"
also i try to install TWRP as zip, but when i restarted, enter into recovery and then i have the same android with error "No Command".

@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798

lost101 said:
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
ahhhhhhhhh... i see... so, i have a dead phone... well, i'm going to try what you said in that post, thanks for all your help!!!

Related

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

Please help!! phone doesn't boot up

hey guys,
I used a youtube video and I did a thing with 5.x to 4.4.4 gpe but after my phone just doesn't boot up.
Do I have a bricked phone? It's Stuck at the bootloader menu with the error ''Boot up failed'' please help!!!
(sorry for bad english)
Be careful with downgrading. What model Moto G do you have?
lost101 said:
Be careful with downgrading. What model Moto G do you have?
Click to expand...
Click to collapse
I have moto g 4g version the 1st gen
and I think it didn't was a downgrade. my phone was 4.4.4 kitkat. it was really dumb of me to do this
poolta321 said:
I have moto g 4g version the 1st gen
and I think it didn't was a downgrade. my phone was 4.4.4 kitkat. it was really dumb of me to do this
Click to expand...
Click to collapse
I already tried to flash TWRP, CWM and Philz but it didn't work it still said Boot up failed
poolta321 said:
I have moto g 4g version the 1st gen
and I think it didn't was a downgrade. my phone was 4.4.4 kitkat. it was really dumb of me to do this
Click to expand...
Click to collapse
The safest thing would be to flash a custom recovery and then a ROM zip.
TWRP custom Recovery: https://www.androidfilehost.com/?fid=95916177934553450
Stock KitKat ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Stock Lollipop ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
--
To flash TWRP use the fastboot command: fastboot flash recovery twrp-2.8.6.0-falcon.img
You can then use ADB to transfer or sideload a ROM zip to phone for flashing.
Related tutorial: http://forum.xda-developers.com/moto-g/general/twrp-adb-sideloading-tutorial-t3006563
EDIT: Since you just updated the post to state you have a 4G Moto G - do not flash non-4G ROMs or firmware images - that includes GPE!
lost101 said:
The safest thing would be to flash a custom recovery and then a ROM zip.
TWRP custom Recovery: https://www.androidfilehost.com/?fid=95916177934553450
Stock KitKat ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Stock Lollipop ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
--
To flash TWRP use the fastboot command: fastboot flash recovery twrp-2.8.6.0-falcon.img
You can then use ADB to transfer or sideload a ROM zip to phone for flashing.
Related tutorial: http://forum.xda-developers.com/moto-g/general/twrp-adb-sideloading-tutorial-t3006563
Click to expand...
Click to collapse
Already tried to flash TWRP but still says Boot up failed when I go to recovery.
(my phone has a SD card slot)
poolta321 said:
Already tried to flash TWRP but still says Boot up failed when I go to recovery.
(my phone has a SD card slot)
Click to expand...
Click to collapse
You should only be flashing ROMs / Firmware / Recoveries available here: http://forum.xda-developers.com/moto-g/4g-development
lost101 said:
You should only be flashing ROMs / Firmware / Recoveries available here: http://forum.xda-developers.com/moto-g/4g-development
Click to expand...
Click to collapse
yes I know but when I flash TWRP and I go to recovery it says boot up failed
poolta321 said:
yes I know but when I flash TWRP and I go to recovery it says boot up failed
Click to expand...
Click to collapse
I'm going to assume you have flashed the XT1032 partition table (gpt.bin) - that could be the cause.
If you flash the full Factory Firmware image, that should fix everything.
4G Firmare images: http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
I'm going to assume you have flashed the XT1032 partition table (gpt.bin) - that could be the cause.
If you flash the full Factory Firmware image, that should fix everything.
4G Firmare images: http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Tried the 4G tutorial before... it didn't work
poolta321 said:
Tried the 4G tutorial before... it didn't work
Click to expand...
Click to collapse
but im going to try this again.
what is the difference with retial europe and orange europe?
poolta321 said:
but im going to try this again.
what is the difference with retial europe and orange europe?
Click to expand...
Click to collapse
I'm also being helped here http://forum.xda-developers.com/moto-g/help/stuck-boot-failed-t3104617
poolta321 said:
but im going to try this again.
what is the difference with retial europe and orange europe?
Click to expand...
Click to collapse
Orange version is one created for the network / carrier called Orange.
Do the fastboot commands manually, one at a time, and post a complete log here if the process is not successful.
lost101 said:
Orange version is one created for the network / carrier called Orange.
Do the fastboot commands manually, one at a time, and post a complete log here if the process is not successful.
Click to expand...
Click to collapse
Okay I'm gonna do that. but first I need to download the file and it says that it takes 2 hours to finish
(Slow internet connection)
poolta321 said:
Okay I'm gonna do that. but first I need to download the file and it says that it takes 2 hours to finish
(Slow internet connection)
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g/help/stuck-boot-failed-t3104617/post60653710#post60653710
I heard that I hard bricked my phone:crying:
poolta321 said:
http://forum.xda-developers.com/moto-g/help/stuck-boot-failed-t3104617/post60653710#post60653710
I heard that I hard bricked my phone:crying:
Click to expand...
Click to collapse
If the phone turns on and shows the fastboot screen, it's not hard-bricked to me. Proceed as I suggested.
lost101 said:
If the phone turns on and shows the fastboot screen, it's not hard-bricked to me. Proceed as I suggested.
Click to expand...
Click to collapse
yes but he said that the bootloader was messed up and that there was no way to fix it
poolta321 said:
yes but he said that the bootloader was messed up and that there was no way to fix it
Click to expand...
Click to collapse
I read what he said, but I do not agree. I suggest you do as I describe above.
lost101 said:
I read what he said, but I do not agree. I suggest you do as I describe above.
Click to expand...
Click to collapse
Okay so what do I need to do?
(I'm away for a while)
poolta321 said:
Okay so what do I need to do?
(I'm away for a while)
Click to expand...
Click to collapse
Okay I'm back. and I did what you said but it didn't work. when I turn on my phone it says: Fastboot Reason: Fall-trough from normal boot mode.
Here is the cmd log:
G:\Program Files\SDK\platform-tools>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
G:\Program Files\SDK\platform-tools>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.366s
G:\Program Files\SDK\platform-tools>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.140s]
finished. total time: 0.218s
G:\Program Files\SDK\platform-tools>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.372s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.841s
G:\Program Files\SDK\platform-tools>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.381s]
writing 'recovery'...
OKAY [ 0.964s]
finished. total time: 1.348s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.0
target max-sparse-size: 256MB
sending 'system' (260841 KB)...
OKAY [ 8.458s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.851s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.1
target max-sparse-size: 256MB
sending 'system' (236285 KB)...
OKAY [ 7.760s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.827s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.2
target max-sparse-size: 256MB
sending 'system' (257383 KB)...
OKAY [ 8.364s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.437s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.3
target max-sparse-size: 256MB
sending 'system' (33384 KB)...
OKAY [ 1.163s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.236s
G:\Program Files\SDK\platform-tools>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (59132 KB)...
OKAY [ 2.200s]
writing 'modem'...
OKAY [ 2.831s]
finished. total time: 5.037s
G:\Program Files\SDK\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.026s]
finished. total time: 0.029s
G:\Program Files\SDK\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.088s]
finished. total time: 0.090s
G:\Program Files\SDK\platform-tools>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (661 KB)...
OKAY [ 0.107s]
writing 'fsg'...
OKAY [ 5.061s]
finished. total time: 5.170s
G:\Program Files\SDK\platform-tools>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.103s]
finished. total time: 0.105s
G:\Program Files\SDK\platform-tools>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.218s]
finished. total time: 0.219s
G:\Program Files\SDK\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.003s

Allow OEM Unlock Bootloader

Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!
axbom said:
Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!
Click to expand...
Click to collapse
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.
acejavelin said:
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.
Click to expand...
Click to collapse
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!
axbom said:
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!
Click to expand...
Click to collapse
Did you factory default prior to flashing? That is a required step...
acejavelin said:
Did you factory default prior to flashing? That is a required step...
Click to expand...
Click to collapse
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..
axbom said:
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..
Click to expand...
Click to collapse
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk
acejavelin said:
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_set
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
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.708s]
finished. total time: 0.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.551s]
finished. total time: 1.645s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.125s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.519s]
writing 'boot'...
OKAY [ 0.936s]
finished. total time: 1.471s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 1.486s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (243355 KB)...
OKAY [ 7.717s]
writing 'system'...
OKAY [ 8.975s]
finished. total time: 16.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (233538 KB)...
OKAY [ 7.478s]
writing 'system'...
OKAY [ 7.597s]
finished. total time: 15.092s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (256922 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 8.308s]
finished. total time: 16.521s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (257262 KB)...
OKAY [ 8.198s]
writing 'system'...
OKAY [ 8.303s]
finished. total time: 16.500s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (255507 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 8.575s]
finished. total time: 16.717s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (258021 KB)...
OKAY [ 8.225s]
writing 'system'...
OKAY [ 8.266s]
finished. total time: 16.507s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (210541 KB)...
OKAY [ 6.716s]
writing 'system'...
OKAY [ 11.695s]
finished. total time: 18.410s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.165s]
writing 'modem'...
OKAY [ 0.974s]
finished. total time: 2.155s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2159 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.172s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>
From what I can see it all looks fine?
axbom said:
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
...
From what I can see it all looks fine?
Click to expand...
Click to collapse
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?
acejavelin said:
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?
Click to expand...
Click to collapse
After issuing the reboot command at the end it goes to the white screen with the motorola logo, then the screen goes black, and then back to the motorola logo, and keep on going like that.
Yeah that's correct, 0-6 sparsechunk files. I did fastboot ERASE cache and ERASE userdata, since I can't get into the recovery menu (goes into bootloop if I try). When I try any of those commands it says Formatting is not supported for filesystem with type 'raw'.
im having the exact same problem, used the same software and carried out the same steps as you with no luck either.
from what ive read its because you need to wipe all the data first but because we get the, cant its RAW message, it wont download the firmware onto the phone even though it says it went ok. at the minute i havnt found anyone whos successfully been able to repair this fault.
mine was working perfectly untill the ota update
There is no fix for that, use your warranty if you have so
Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.
yobac said:
Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.
Click to expand...
Click to collapse
Contact Moto directly via their website.
Sent from my MotoG3 using Tapatalk
1st Flash via Adb !
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !
FaizanChauhaan said:
1st Flash via Adb !
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !
Click to expand...
Click to collapse
It's fastboot not adb lol. Contradictory sentences
Edit: BTW motoboot.img is not present, it may refer to earlier generation of moto g. There is an line to flash bootloader.img instead. Have a look here : http://forum.xda-developers.com/showthread.php?t=3187750. Thanks.
Broadcasted from Zeta Reticuli

problem of flash stock rom (xt1033)

My phone just suddenly get bricked, I'm do not do anything before,not root ,not unlock bootloader ,not flash third-party roms.
I'm only update from ota (from 4.4 to 5.0 and 5.0 to 5.1), just the offical method to update.
now,i come here to find the way and get my phone back .
the situation now is unlocked bootloader (bootloader version :41.1A)
and try to flash stock rom XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip
i just follow the guide in forum ,but get a trouble like that:
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash pa
rtition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.032s]
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.333s]
finished. total time: 0.375s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash mo
toboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.112s]
finished. total time: 1.232s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash lo
go logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.101s]
finished. total time: 0.173s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash bo
ot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.379s]
writing 'boot'...
OKAY [ 0.776s]
finished. total time: 1.166s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash re
covery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.392s]
writing 'recovery'...
OKAY [ 0.767s]
finished. total time: 1.171s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash sy
stem system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 8.318s]
writing 'system'...
OKAY [ 12.417s]
finished. total time: 20.747s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash sy
stem system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256949 KB)...
OKAY [ 8.258s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 29.086s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
I have try many times but still cant flash the sysem system.img_sparsechunk.1,
but i can flash the part system.img_sparsechunk.0
Does any one know what is my problem?(or my phone is already dead.)
PS: I'm sorry about that my english is not good,if anything wrong or can not understanding,please ask me.
thanks everyone.
Maybe that sparsechunk did not extract fully from the zip. Re-extract, or download the entire zip again.
lost101 said:
Maybe that sparsechunk did not extract fully from the zip. Re-extract, or download the entire zip again.
Click to expand...
Click to collapse
First, thanks to your suggestion.
I just re-download the roms from the different websites
then use 7 zip to extract the both file and try again ,still get the same result as i say that on the topic.
BY the way ,thank you for your suggestion.
Try an 'external' factory reset via Stock Recovery:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050​
lost101 said:
Try an 'external' factory reset via Stock Recovery:
motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050​
Click to expand...
Click to collapse
thanks your suggestion
i just follow the guide of the website,but i get the problem in step 4, i can see the Android figure lying on his back,but my screen continue twinkling ,after i press and hold the Power button then press and release the Volume Up button, the phone come back to the fastboot screen.
Is that root the phone can get help?
More: I'm use the 16GB version xt1033 ,is that wrong gpt.bin in rom?
tom0079 said:
i just follow the guide of the website,but i get the problem in step 4, i can see the Android figure lying on his back,but my screen continue twinkling ,after i press and hold the Power button then press and release the Volume Up button, the phone come back to the fastboot screen.
Click to expand...
Click to collapse
Keep trying, you should be able to enter recovery mode. The instructions are press and hold Vol up, then tap Power button - not what you describe.
lost101 said:
Keep trying, you should be able to enter recovery mode. The instructions are press and hold Vol up, then tap Power button - not what you describe.
Click to expand...
Click to collapse
After that ,i try several methods, and do some stupid things and relock the bootloader,
i can't flash any part of the roms now,is there any way to unlock the bootloader again?
(P.S. the status in fastboot mode still show up unlock)
mfastboot oem unlock​
lost101 said:
mfastboot oem unlock​
Click to expand...
Click to collapse
It's not work!
http://forum.xda-developers.com/moto-g/help/guide-root-xt1032-xt1033-moto-g-running-t2965507
i have done what in the link, so get trouble
New 5.1 Factory Firmware Images are now available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
For now, the only XT1033 image you can use is: XT1033_FALCON_RETBR_DS_5.1_LPBS23.13-56-2_cid12 (you can change language to english during setup)
I would try flashing that firmware image via mfastboot. When the new XT1033 Asia firmware image becomes available, you can change to that if you want.
lost101 said:
New 5.1 Factory Firmware Images are now available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
For now, the only XT1033 image you can use is: XT1033_FALCON_RETBR_DS_5.1_LPBS23.13-56-2_cid12 (you can change language to english during setup)
I would try flashing that firmware image via mfastboot. When the new XT1033 Asia firmware image becomes available, you can change to that if you want.
Click to expand...
Click to collapse
thanks for your reply, i had tried the rom you provided to me, it still get the same result,all the steps are showing the result "failure".
Can you tell me that have big chance to make my phone return normal ?
If not, that's the time for me to give up.
tom0079 said:
thanks for your reply, i had tried the rom you provided to me, it still get the same result,all the steps are showing the result "failure".
Can you tell me that have big chance to make my phone return normal ?
If not, that's the time for me to give up.
Click to expand...
Click to collapse
Show me the log from command prompt when flashing the firmware image.
I have some issue with my Moto G XT1033
tom0079 said:
My phone just suddenly get bricked, I'm do not do anything before,not root ,not unlock bootloader ,not flash third-party roms.
I'm only update from ota (from 4.4 to 5.0 and 5.0 to 5.1), just the offical method to update.
now,i come here to find the way and get my phone back .
the situation now is unlocked bootloader (bootloader version :41.1A)
and try to flash stock rom XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip
i just follow the guide in forum ,but get a trouble like that:
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash pa
rtition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.032s]
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.333s]
finished. total time: 0.375s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash mo
toboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.112s]
finished. total time: 1.232s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash lo
go logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.101s]
finished. total time: 0.173s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash bo
ot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.379s]
writing 'boot'...
OKAY [ 0.776s]
finished. total time: 1.166s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash re
covery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.392s]
writing 'recovery'...
OKAY [ 0.767s]
finished. total time: 1.171s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash sy
stem system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 8.318s]
writing 'system'...
OKAY [ 12.417s]
finished. total time: 20.747s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash sy
stem system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256949 KB)...
OKAY [ 8.258s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 29.086s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
I have try many times but still cant flash the sysem system.img_sparsechunk.1,
but i can flash the part system.img_sparsechunk.0
Does any one know what is my problem?(or my phone is already dead.)
PS: I'm sorry about that my english is not good,if anything wrong or can not understanding,please ask me.
thanks everyone.
Click to expand...
Click to collapse
Getting some "Preflash validiation error" on my Moto XT1033 while flashing gpt.bin and motoboot.img and I'm also unable to factory reset and wipe dalvik cache and also I'm unablle to flash TWRP or any other custom recovery and unable to re-lock my bootloader Showing some Partition error....Help me plz....
MY device is bricked

Nexus 5 bootloop & recovery doesn't work

First of all, I'm german, so sorry if something's wrong with my English
Hey I've got a Nexus 5 laying around (I don't use it) and it is bootlooping. I would like to fix it but nothing works.
1. Power button isn't stuck (checked it)
2. I can boot into the bootloader
3. fastboot works fine
4. Can't get into Recovery ( when I boot into Recovery the Google Logo comes up and it keeps restarting)
5. Flashing a fresh Android doesn't work
6. Flashing a custom Recovery doesn't work
7. I don't know anything about the phone (I just got it because i wanted the display for my other Nexus 5)
8. bootloader is unlocked
I have fastboot and adb on a Windows and a Linux machine. Thanks for your help
Your English is perfect (apart from the lower case on "German" ) - if you hadn't started with that sentence I would never have known.
At the risk of boring people who may have already seen this post in other threads, see if this advice helps at all. If you have a working bootloader screen it may work. You can ignore the first sentence about backup, since in your situation it's redundant.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/images#hammerhead) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Didn't work...
Here's my output:
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash bootloader bootloader.img
target didn't report max-download-size
sending 'bootloader' (2506 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
OKAY [ 0.453s]
finished. total time: 0.688s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash radio radio.img
target didn't report max-download-size
sending 'radio' (42033 KB)...
OKAY [ 1.422s]
writing 'radio'...
OKAY [ 2.891s]
finished. total time: 4.313s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 1.109s]
finished. total time: 1.109s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash system system.img
target didn't report max-download-size
erasing 'system'...
OKAY [ 0.516s]
sending 'system' (692940 KB)...
OKAY [ 21.893s]
writing 'system'...
OKAY [ 46.692s]
finished. total time: 69.132s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase boot
erasing 'boot'...
OKAY [ 0.234s]
finished. total time: 0.234s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (8620 KB)...
OKAY [ 0.484s]
writing 'boot'...
OKAY [ 0.734s]
finished. total time: 1.234s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.500s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash cache cache.img
target didn't report max-download-size
erasing 'cache'...
OKAY [ 0.484s]
sending 'cache' (13348 KB)...
OKAY [ 0.625s]
writing 'cache'...
OKAY [ 1.063s]
finished. total time: 2.188s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (14626 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 1.125s]
finished. total time: 1.797s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
When i boot to recovery the google logo appears and still restarts all the time.
As i said, i've already tried flashing a custom recovery and Android before... Didn't work for me..
Sorry to hear that. I've never seen the "target didn't report" message. Maybe a hardware problem?
I thinks it's a hardware failure. I found somebody else having this problem on the google forum. They say the flash storage is demaged. Not repairable. But thanks for the quick reply.
Budden6800i said:
I thinks it's a hardware failure. I found somebody else having this problem on the google forum. They say the flash storage is demaged. Not repairable. But thanks for the quick reply.
Click to expand...
Click to collapse
Why you are using krt16m image? It's old...
Please download M4B30Z and try again...

Categories

Resources