Database Info

Hard bricked my XOOM help

NOTE: Says when on rsd mode failed to boot 0x00001
on fastboot same + is says failed to format pds and does't connect to the pc after that
i have over 50 hours in 5 days looking for way to fix no luck .
i try my luck with Fastboot. I first tried flashing the recovery with no luck. I then tried flashing over the official moto files (boot/sytstem/....)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
....
If i follow that order boot/system and recovery fail then userdata says it works and it lets me flash the other options (but clearly just says they work it looks like it's lying)
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
.......
C:\SDK_tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 11.598s]
writing 'userdata'... OKAY [ 0.164s]
finished. total time: 11.764s
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.688s]
writing 'boot'... OKAY [ 3.462s]
finished. total time: 4.151s
.....
If I try fastboot oem unlock I'm prompted with the unlock message and after hitting accept. I see the following error on the screen
ERROR: Failed to format UDA.
Error while unlocking device.
My next try was with RSD light. I tried flashing all of the images for my xoom off this site . all of them give me the following error:
Failed flashing process. Failed Flashing process. Interface AP-OS: Error flashing subscriber unit. Device API error: 0xE0020085 Address: 0x1F870 Command: ADDR (0xE0222085); phone connected
I ran out of ideas on what to do next. One post i saw said try using a nand backup but I can't find one that will work.
Any help would be great. I really love my XOOM and I'm sad i can't fix it.

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

MOTO G XT1032 black screen

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

Stuck on boot animation after resetting to stock

Hi,
A friend asked me to look at his Nexus 5.
It seemed as though his son was trying to flash a custom rom but somewhere along the way things went wrong and it got stuck on the boot animation.
I tried resetting it to factory using this thread.
Followed method 2 and finished it up with "Wipe data/factory data" reset. I did not however relock the boot loader.
I used the factory image 6.0.1 (MMB29S).
Everything went well, no errors, but even after doing all that the phone is still stuck on the boot animation. I tried redoing the "Wipe data/factory data" reset, but the phone is still stuck on boot animation.
I left for around 20 minutes with no change.
All the other threads I have read seem to indicate doing the "wipe data/factory data" reset should correct this issue but it hasn't seemed to help.
I also found this thread. The last post could possibly be another option.
Is there anything I can try? or is there a log I can look?
Any suggestions would be greatly appreciated.
Cheers

Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.

audit13 said:
Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.
Click to expand...
Click to collapse
Thanks for the reply.
I did as you suggested, unfortunately I am still stuck on boot animation.
Output from command
Code:
c:\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.014s]
sending 'userdata' (137318 KB)...
OKAY [ 4.510s]
writing 'userdata'...
OKAY [ 9.149s]
finished. total time: 21.673s
I was just looking at the contents of the zip I downloaded from the developer site. The data stamps on the images seem old. Most date back to 2009. Perhaps I have downloaded the wrong files?

Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?

audit13 said:
Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?
Click to expand...
Click to collapse
Yes the userdata.img did come from the mmb29s ROM. I have no other ROM files downloaded.
Yes I did I believe, if I recall correctly, these were my steps:
Booted phone into fastboot by pressing the power and down volume key
flashed the userdata.img using the command provided
Used the volume rocket to select "Recovery"
When the dead Android appeared I pressed the power button and up volume rocker to display the menu
Proceeded to the option to wipe and reset data
Rebooted the phone
I am pretty sure those were the steps I used.
Should I have rebooted first before going directly into Recovery?

Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?

audit13 said:
Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?
Click to expand...
Click to collapse
No I didn't notice any error messages unfortunately.
And I don't recall seeing any error messages during any of the other steps I have performed.
The commands all seem to successfully execute with no errors.
Does it at all make sense for me to go back and completely redo all the steps from the tutorial in my first post?
I can post the outputs from all the commands if you think that would at all be helpful?

I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.

audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Okay perfect. I will give method 1 a try tonight (I am unfortunately at work right now).
I will report back tonight... hopefully with good news

audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Sorry for the late reply on this.
I got around to doing the steps above.
Unfortunately I am still stuck on the boot animation screen.
Here is the output from the commands I ran
Code:
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
OKAY [ 0.500s]
finished. total time: 0.797s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.078s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.540s]
writing 'radio'...
OKAY [ 3.125s]
finished. total time: 4.665s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.063s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.109s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.781s]
sending 'recovery' (10012 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.828s]
erasing 'system'...
OKAY [ 1.297s]
sending 'system' (1020413 KB)...
OKAY [ 32.163s]
writing 'system'...
OKAY [ 69.508s]
erasing 'userdata'...
OKAY [ 8.326s]
sending 'userdata' (137318 KB)...
OKAY [ 4.500s]
writing 'userdata'...
OKAY [ 9.138s]
erasing 'cache'...
OKAY [ 0.672s]
sending 'cache' (13348 KB)...
OKAY [ 0.625s]
writing 'cache'...
OKAY [ 1.078s]
rebooting...
finished. total time: 130.775s
Press any key to exit...
////// -------- AFTER COMPLETE POWER OFF AND REBOOT -------- \\\\\\\\
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.625s]
finished. total time: 0.641s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.384s]
finished. total time: 8.399s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.220s]
sending 'userdata' (137318 KB)...
OKAY [ 4.516s]
writing 'userdata'...
OKAY [ 9.156s]
finished. total time: 21.892s
Everything seemed to go okay.
Does everything in the output above look okay?

Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?

audit13 said:
Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?
Click to expand...
Click to collapse
Yes I did do that and did the clear of the cache as well since it posted that error message like you said it would.
So I did both as you explained.
I took a picture of the phone itself after the userdata wipe.
https://www.dropbox.com/s/k05s06avrha1lfv/IMG_20160206_153435.jpg?dl=0

Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.

audit13 said:
Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.
Click to expand...
Click to collapse
Well that sucks!
I had read that in some cases this can be caused by a hardware issue. Any chance it could be that?
Btw, the links I provided to the stock Google images, were they the correct images?

These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?

audit13 said:
These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?
Click to expand...
Click to collapse
hi,
sorry for my late reply. I got sick and just didn't have it in me to try anything new.
I tried flashing 5.0.1 tonight and unfortunately wound up in another boot loop. I will have to try the steps again where you manually reflash userdata. Hopefully I will have time tomorrow!

Hi
My phone has the exact same problem as stated by OP. I even tried flashing kitkat and lollipop but the problem persist. The phone still stuck at boot animation screen. PLS help.

Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?

audit13 said:
Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?
Click to expand...
Click to collapse
The bootloader is now locked. Still, I can't boot the phone completely. stuck at Google boot animation.

At this point, I would conclude that something is wrong with the memory chip.

How to get out of Boot loop MOTO G XT1033?

One Fine morning when I checked my phone it said "optimizing app 69 out of 109"..Battery drained out . Recharged and noticed Device wont start and won't go past the "Moto G logo POwered by android" screen .
Steps taken so far :
Unlocked bootloader . Device status shows unlocked status 3 .
1. Followed the steps @ http://forum.xda-developers.com/showthread.php?t=2542219
No errors using XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip
Result:--> problem persists
Code:
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>vin
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
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.300s]
finished. total time: 0.326s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.930s]
finished. total time: 1.031s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.059s]
finished. total time: 0.104s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.408s]
writing 'boot'...
OKAY [ 0.587s]
finished. total time: 1.001s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (9488 KB)...
OKAY [ 0.401s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.577s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 9.347s]
writing 'system'...
OKAY [ 7.850s]
finished. total time: 17.201s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256953 KB)...
OKAY [ 9.122s]
writing 'system'...
OKAY [ 8.006s]
finished. total time: 17.133s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260396 KB)...
OKAY [ 9.446s]
writing 'system'...
OKAY [ 7.997s]
finished. total time: 17.449s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166572 KB)...
OKAY [ 6.084s]
writing 'system'...
OKAY [ 6.310s]
finished. total time: 12.400s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.835s]
writing 'modem'...
OKAY [ 0.826s]
finished. total time: 2.667s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.017s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.053s]
writing 'fsg'...
OKAY [ 3.177s]
finished. total time: 3.234s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.024s
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>pause
Press any key to continue . . .
C:\Users\vinesriv\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xm
l>mfastboot reboot
rebooting...
2. When I use
Code:
Fastboot erase recovery
Fastboot Flash recovery twrp-3.0.2-0-falcon.img
And reboot in recovery mode the system still uses stock recovery .
3. I am able to
Code:
Fastboot boot twrp-3.0.2-0-falcon.img
and I can see the twrp recovery . I used it to wipe cache and user data .
Used this to install : XT1033_Retail_Asia_51_Untouched.zip
Got error
Symlink failed error code 1 . Rebooted in recovery and this error was gone . Successfully installed zip .
Result :--- Problem persists
4. when I tried booting into cynogen recovery or twrp-3.0.2-0-falcon.img recovery , I am not able to install cynogen mod rom -- cm-13.0-20160916-NIGHTLY-falcon.zip and the error is cannot Can't install this package on top of incompatible data .
5 . When I use cm-11-20140504-SNAPSHOT-M6-falcon.zip I get some symlinks failed .
Overall I feel the flashing although is not giving any error , it is not writing anything .
The reason I believe that is 1... after flashing recovery and trying to boot recovery it goes to standard recovery and not custom recovery.
2. My problem of bootloop remains unresolved.
I am not an expert so not sure if rooting is required and if yes, even then I am not sure how to be sure if my device is rooted . I have tried using r2-motog-superboot.zip and also tried installing supersu.zip using twrp without errors. But, how do I tell if it is rooted successfully and what difference should I see?
How to get out of this bootloop .? One more thing:- is it possible to test if this is a hardware issue like disk failure or something?
I keep getting IO error on Dalvik-cache/arm while trying to wipe partitions using twrp.
Any help will be appreciated .

try wiping data and recovery partition then installing the recovery followed by the zip.

Paradox♀ said:
try wiping data and recovery partition then installing the recovery followed by the zip.
Click to expand...
Click to collapse
I have tried that ..unless,, you are suggesting different commands than what I have already posted?

@vinny_80 - Your phone is exhibiting a number of the classic signs of 'corrupt emmc.' This is most likely the end of the road for your handset.

lost101 said:
@vinny_80 - Your phone is exhibiting a number of the classic signs of 'corrupt emmc.' This is most likely the end of the road for your handset.
Click to expand...
Click to collapse
That hurts !!
Is there a definitive test for this to be sure of corruption in Emmc ? I cant use adb to verify this , I guess ?
Further-- if emmc is corrupt,, would I be able to boot to twrp recovery.img using fastboot as I did? even stock recovery opens fine if I erase and install the same ... so I guess emmc is not corrupt and hence the question..whats the best way to test this ?

vinny_80 said:
That hurts !!
Is there a definitive test for this to be sure of corruption in Emmc ? I cant use adb to verify this , I guess ?
Further-- if emmc is corrupt,, would I be able to boot to twrp recovery.img using fastboot as I did? even stock recovery opens fine if I erase and install the same ... so I guess emmc is not corrupt and hence the question..whats the best way to test this ?
Click to expand...
Click to collapse
Recovery is read-only. That's what you are describing, and that is an indication of corrupt emmc. Booting into TWRP via fastboot boot twrp.img is possible with corrupt emmc. One other user managed to flash CM13 and still use the handset - but with frequent read-only issues I imagine.

vinny_80 said:
That hurts !!
Is there a definitive test for this to be sure of corruption in Emmc ? I cant use adb to verify this , I guess ?
Click to expand...
Click to collapse
Boot TWRP, try to wipe and install something, then run
Code:
adb shell dmesg > dmesg.txt
adb pull /tmp/recovery.log
Check both files for messages indicating corruption, e.g. mmcblk errors in dmesg or I/O errors in recovery.log. You can also upload the files if you can't make sense of them yourself.

_that said:
Boot TWRP, try to wipe and install something, then run
Code:
adb shell dmesg > dmesg.txt
adb pull /tmp/recovery.log
Check both files for messages indicating corruption, e.g. mmcblk errors in dmesg or I/O errors in recovery.log. You can also upload the files if you can't make sense of them yourself.
Click to expand...
Click to collapse
Here it goes:- I am not very hopeful
And I assume service center wont help either ? thoughts?
Regards
Vineet

vinny_80 said:
Here it goes:- I am not very hopeful
Click to expand...
Click to collapse
Yes, those I/O errors on mmcblk0 in dmesg indicate that there is something very wrong with your eMMC (internal flash storage device). Looks like a hardware defect to me.

If you have a Back Up ROM, maybe you can restore only the System ( With TWRP ) then try Flashing a New ROM, Hope this Help you.

Same problem here, XT1032, stuck on optimizing apps with RR 5.7.4 (MM). TWRP still working, reflashing same or older RR ROM worked, but still got stuck while optimizing apps. Already got a backup of contacts, logs and sms. What exactly are the recommended steps from here?
1. Wipe anything apart from cache/dalvik before flashing a ROM again?
2. Does it make sense to try other MM ROMs
3. Flashing factory rom?

Guttergorm said:
Same problem here, XT1032, stuck on optimizing apps with RR 5.7.4 (MM). TWRP still working, reflashing same or older RR ROM worked, but still got stuck while optimizing apps. Already got a backup of contacts, logs and sms. What exactly are the recommended steps from here?
1. Wipe anything apart from cache/dalvik before flashing a ROM again?
2. Does it make sense to try other MM ROMs
3. Flashing factory rom?
Click to expand...
Click to collapse
Flash the latest XT1032 Factory Firmware Image using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
mFastboot download: https://www.androidfilehost.com/?fid=24052804347778493
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

Downgrade to a previous version.
I almost wasted an entire day on that ROM. But, this WORKED for me and got it fixed.
Cannot pinpoint what exactly worked.
But, I can say it for sure that do not use that ROM. (XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip)
I tried that and it seems the recovery img has some problems. Use just the previous version of it.
(XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip)
You can find it here - Google - xt1033 firmware - firmware.center/firmware/Motorola link.
(Sorry, being this my 1st comment xda forum not allowing me to post a link here.)
Also, I followed some answers where they have said you will get some errors like "preflash validation failed" on your PC cmd line for boot img and system.img_sparsechunk, etc. Also, messages in red/pink on mobile fastboot cmd line suggesting "Downgrading to ..". But that's okay. Let it be. Give it 2-3 tries and at least wait 4-5 mins at boot.
It worked for me.
I am guessing it has some problems in downgrading.
(I am comparatively new to xda and mobile booting, so, my interpretation might be wrong, but, solution worked.
Experts feel free to correct my answers wherever you want. Just wanted to put it here because saw a lot of people facing this problem.)