Moto G (India) - XT1033 - can't FLASH anything (bootloop)

[jignesh_shah]

Further on investigating, I ran command

e2fsck -y /dev/block/mmcblk0p34 where /system is mounted. following is a log:

/dev/block/mmcblk0p34 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Error reading block 54295 (Attempt to read block from filesystem resulted in short read) while reading directory block. Ignore error? yes

Force rewrite? yes

Directory inode 395, block #0, offset 0: directory corrupted
Salvage? yes

Missing '.' in directory inode 395.
Fix? yes

Setting filetype for entry '.' in ??? (395) to 2.
Missing '..' in directory inode 395.
Fix? yes

Setting filetype for entry '..' in ??? (395) to 2.
Pass 3: Checking directory connectivity
'..' in /etc (395) is <The NULL inode> (0), should be / (2).
Fix? yes

Unconnected directory inode 408 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 413 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 418 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 436 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 466 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 491 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 508 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 553 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 560 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 720 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 729 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 7871 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 7875 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 7879 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 7885 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 7888 (/etc/???)
Connect to /lost+found? yes

Unconnected directory inode 15799 (/etc/???)
Connect to /lost+found? yes

Pass 4: Checking reference counts
Unattached inode 202
Connect to /lost+found? yes

Inode 202 ref count is 2, should be 1. Fix? yes

Unattached inode 203
Connect to /lost+found? yes

Inode 203 ref count is 2, should be 1. Fix? yes

Unattached inode 205
Connect to /lost+found? yes

Inode 205 ref count is 2, should be 1. Fix? yes

Unattached inode 206
Connect to /lost+found? yes

Inode 206 ref count is 2, should be 1. Fix? yes

Unattached inode 220
Connect to /lost+found? yes

Inode 220 ref count is 2, should be 1. Fix? yes

Unattached inode 222
Connect to /lost+found? yes

Inode 222 ref count is 2, should be 1. Fix? yes

Unattached inode 227
Connect to /lost+found? yes

Inode 227 ref count is 2, should be 1. Fix? yes

Unattached inode 240
Connect to /lost+found? yes

Inode 240 ref count is 2, should be 1. Fix? yes

Unattached inode 243
Connect to /lost+found? yes

Inode 243 ref count is 2, should be 1. Fix? yes

Unattached inode 244
Connect to /lost+found? yes

Inode 244 ref count is 2, should be 1. Fix? yes

Unattached inode 247
Connect to /lost+found? yes

Inode 247 ref count is 2, should be 1. Fix? yes

Unattached inode 249
Connect to /lost+found? yes

Inode 249 ref count is 2, should be 1. Fix? yes

Unattached inode 250
Connect to /lost+found? yes

Inode 250 ref count is 2, should be 1. Fix? yes

Unattached inode 265
Connect to /lost+found? yes

Inode 265 ref count is 2, should be 1. Fix? yes

Unattached inode 273
Connect to /lost+found? yes

Inode 273 ref count is 2, should be 1. Fix? yes

Unattached inode 368
Connect to /lost+found? yes

Inode 368 ref count is 2, should be 1. Fix? yes

Unattached inode 369
Connect to /lost+found? yes

Inode 369 ref count is 2, should be 1. Fix? yes

Unattached inode 371
Connect to /lost+found? yes

Inode 371 ref count is 2, should be 1. Fix? yes

Unattached inode 372
Connect to /lost+found? yes

Inode 372 ref count is 2, should be 1. Fix? yes

Unattached inode 373
Connect to /lost+found? yes

Inode 373 ref count is 2, should be 1. Fix? yes

Unattached inode 374
Connect to /lost+found? yes

Inode 374 ref count is 2, should be 1. Fix? yes

Unattached inode 376
Connect to /lost+found? yes

Inode 376 ref count is 2, should be 1. Fix? yes

Unattached inode 383
Connect to /lost+found? yes

Inode 383 ref count is 2, should be 1. Fix? yes

Unattached inode 407
Connect to /lost+found? yes

Inode 407 ref count is 2, should be 1. Fix? yes

Inode 408 ref count is 3, should be 2. Fix? yes

Unattached inode 410
Connect to /lost+found? yes

Inode 410 ref count is 2, should be 1. Fix? yes

Unattached inode 411
Connect to /lost+found? yes

Inode 411 ref count is 2, should be 1. Fix? yes

Inode 413 ref count is 3, should be 2. Fix? yes

Unattached inode 416
Connect to /lost+found? yes

Inode 416 ref count is 2, should be 1. Fix? yes

Unattached inode 417
Connect to /lost+found? yes

Inode 417 ref count is 2, should be 1. Fix? yes

Inode 418 ref count is 4, should be 3. Fix? yes

Unattached inode 420
Connect to /lost+found? yes

Inode 420 ref count is 2, should be 1. Fix? yes

Unattached inode 424
Connect to /lost+found? yes

Inode 424 ref count is 2, should be 1. Fix? yes

Unattached inode 428
Connect to /lost+found? yes

Inode 428 ref count is 2, should be 1. Fix? yes

Unattached inode 431
Connect to /lost+found? yes

Inode 431 ref count is 2, should be 1. Fix? yes

Unattached inode 432
Connect to /lost+found? yes

Inode 432 ref count is 2, should be 1. Fix? yes

Unattached inode 433
Connect to /lost+found? yes

Inode 433 ref count is 2, should be 1. Fix? yes

Unattached inode 434
Connect to /lost+found? yes

Inode 434 ref count is 2, should be 1. Fix? yes

Inode 436 ref count is 5, should be 4. Fix? yes

Unattached inode 450
Connect to /lost+found? yes

Inode 450 ref count is 2, should be 1. Fix? yes

Unattached inode 452
Connect to /lost+found? yes

Inode 452 ref count is 2, should be 1. Fix? yes

Unattached inode 455
Connect to /lost+found? yes

Inode 455 ref count is 2, should be 1. Fix? yes

Unattached inode 459
Connect to /lost+found? yes

Inode 459 ref count is 2, should be 1. Fix? yes

Unattached inode 460
Connect to /lost+found? yes

Inode 460 ref count is 2, should be 1. Fix? yes

Unattached inode 465
Connect to /lost+found? yes

Inode 465 ref count is 2, should be 1. Fix? yes

Inode 466 ref count is 3, should be 2. Fix? yes

Unattached inode 470
Connect to /lost+found? yes

Inode 470 ref count is 2, should be 1. Fix? yes

Unattached inode 471
Connect to /lost+found? yes

Inode 471 ref count is 2, should be 1. Fix? yes

Unattached inode 472
Connect to /lost+found? yes

Inode 472 ref count is 2, should be 1. Fix? yes

Unattached inode 473
Connect to /lost+found? yes

Inode 473 ref count is 2, should be 1. Fix? yes

Unattached inode 476
Connect to /lost+found? yes

Inode 476 ref count is 2, should be 1. Fix? yes

Unattached inode 477
Connect to /lost+found? yes

Inode 477 ref count is 2, should be 1. Fix? yes

Unattached inode 478
Connect to /lost+found? yes

Inode 478 ref count is 2, should be 1. Fix? yes

Unattached inode 480
Connect to /lost+found? yes

Inode 480 ref count is 2, should be 1. Fix? yes

Unattached inode 481
Connect to /lost+found? yes

Inode 481 ref count is 2, should be 1. Fix? yes

Inode 491 ref count is 7, should be 6. Fix? yes

Inode 508 ref count is 3, should be 2. Fix? yes

Inode 553 ref count is 3, should be 2. Fix? yes

Unattached inode 558
Connect to /lost+found? yes

Inode 558 ref count is 2, should be 1. Fix? yes

Inode 560 ref count is 4, should be 3. Fix? yes

Inode 720 ref count is 3, should be 2. Fix? yes

Inode 729 ref count is 3, should be 2. Fix? yes

Unattached inode 733
Connect to /lost+found? yes

Inode 733 ref count is 2, should be 1. Fix? yes

Unattached inode 1126
Connect to /lost+found? yes

Inode 1126 ref count is 2, should be 1. Fix? yes

Unattached inode 1129
Connect to /lost+found? yes

Inode 1129 ref count is 2, should be 1. Fix? yes

Unattached inode 1485
Connect to /lost+found? yes

Inode 1485 ref count is 2, should be 1. Fix? yes

Unattached inode 1493
Connect to /lost+found? yes

Inode 1493 ref count is 2, should be 1. Fix? yes

Unattached inode 1495
Connect to /lost+found? yes

Inode 1495 ref count is 2, should be 1. Fix? yes

Unattached inode 1505
Connect to /lost+found? yes

Inode 1505 ref count is 2, should be 1. Fix? yes

Unattached inode 1773
Connect to /lost+found? yes

Inode 1773 ref count is 2, should be 1. Fix? yes

Unattached inode 1775
Connect to /lost+found? yes

Inode 1775 ref count is 2, should be 1. Fix? yes

Unattached inode 1784
Connect to /lost+found? yes

Inode 1784 ref count is 2, should be 1. Fix? yes

Unattached inode 1785
Connect to /lost+found? yes

Inode 1785 ref count is 2, should be 1. Fix? yes

Inode 7871 ref count is 3, should be 2. Fix? yes

Inode 7875 ref count is 3, should be 2. Fix? yes

Inode 7879 ref count is 3, should be 2. Fix? yes

Inode 7885 ref count is 3, should be 2. Fix? yes

Inode 7888 ref count is 3, should be 2. Fix? yes

Inode 15799 ref count is 3, should be 2. Fix? yes

Pass 5: Checking group summary information

/dev/block/mmcblk0p34: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p34: 2204/62464 files (8.3% non-contiguous), 244167/249856 blocks

 

[skyrajparmar]

No, I am still trying to get /system. I have not got succeeded with getting /system partition as most of the people I know have unrooted device.

Okay..... whenever i have a free Wi-Fi.... i will upload it for u.....

 

[jignesh_shah]

Great, it would be very helpful.

btw, if you might have got chance to look at previous log, it seems that there are no bad blocks in eMMC. but there is corruption in /system folder.

Is there any way i can remove existing /system folder and put new using following commands?
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3

I am still unclear in difference between above commands and coping /system folder!!!

 

[skyrajparmar]

Great, it would be very helpful.

btw, if you might have got chance to look at previous log, it seems that there are no bad blocks in eMMC. but there is corruption in /system folder.

Is there any way i can remove existing /system folder and put new using following commands?
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3

I am still unclear in difference between above commands and coping /system folder!!!

may be this helpful (it is for moto g 2015)
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750

 

[jignesh_shah]

@skyrajparmar, I dont see anything new in the article which might resolve the error I am getting. Also, it does not make sense to flash XT1033 with images for other version...

I would prefer to wait for getting /system folder.

appreciate your support though!!!

 

[Paradox♀]

Hey you can boot into fastboot which means that your phone is not hard bricked thats is a great news.
You can try wiping the partitions in the fastboot if the bootloader is unlocked
Try this in fastboot mode:
(Use mfastboot) :- http://forum.xda-developers.com/atta...1&d=1442444179

Code:
mfastboot erase system
mfastboot erase cache
mfastboot erase userdata
mfastboot erase recovery
mfastboot erase modemst1
mfastboot erase modemst2
Then install the stock rom or flash recovery then install a custom ROM.

Hit thanks if it worked..!
Stay Crazy

 

[jignesh_shah]

@Paradox, appreciate your response.

Sure, I will try erasing partitions and flashing again. I will post the result once I am done.

I have just held myself back before erasing partitions to make sure i dont erase information such as IMEI etc. which are critical once phone (if) comes back to life!!! so far, I have backed up PDS...

meantime, some related observations so far:
- I have tried flashing partitions (without erasing) before but it does not do anything.
- After unlocked bootloader, I am unable to flash TWRP, I can boot TWRP though.
- erased system partition and flashed again. e2fsck still shows error on /system

any thoughts/comments for above?

 

[_3psilon_]

@Paradox, appreciate your response.

Sure, I will try erasing partitions and flashing again. I will post the result once I am done.

I have just held myself back before erasing partitions to make sure i dont erase information such as IMEI etc. which are critical once phone (if) comes back to life!!! so far, I have backed up PDS...

meantime, some related observations so far:
- I have tried flashing partitions (without erasing) before but it does not do anything.
- After unlocked bootloader, I am unable to flash TWRP, I can boot TWRP though.
- erased system partition and flashed again. e2fsck still shows error on /system

any thoughts/comments for above?

So strange, I have the very same problem. Just happened 2 days ago. I opened up a thread, but having very similar symptoms, maybe we'll find some support together.

P.S. I erased every partition and it looks like the memory was read-only, it didn't actually erase any data...

 

[jignesh_shah]

@_3psilon_, yeah, strangely we both are having very similar issue (I dont have battery/cache thing. Also, phone gets detected with TWRP as MTP and works with fastboot, ADB) and I have not seen any other post discussing such issue.

Unfortunately, we both dont have any solution.
anyways, In case, I found the solution, i will post it. I hope you also do the same...

my best wishes!!!

 

[Revolver95]

@_3psilon_, yeah, strangely we both are having very similar issue (I dont have battery/cache thing. Also, phone gets detected with TWRP as MTP and works with fastboot, ADB) and I have not seen any other post discussing such issue.

Unfortunately, we both dont have any solution.
anyways, In case, I found the solution, i will post it. I hope you also do the same...

my best wishes!!!

Please do post it when you find it.
I am facing the same problem. Phone starts in recovery mode as soon as the warning splash screen disappears and refuses to boot up normally no matter what I flash, whether it's through TWRP or mfastboot

EDIT: That didn't take long....
I just had to use this tool to flash stock 5.1 (along with mfastboot and adb) :https://basketbuild.com/filedl/devs?dev=Fabio-San&dl=Fabio-San/Moto Tools/flash5.1.zip

Thanks to FabioSan for making this thread http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788

 

[jignesh_shah]

I tried 'mfastboot erase all' and reinstalled everything but result is same!!!

so i believe eMMC has somehow become read only or worse corrupted.

I see few post where people have tried various solution without success:
http://forum.xda-developers.com/moto-g/help/damaged-internal-sd-t2866484

so , I am not having much hope...

over the weekend, I will search for some local service center who can replace eMMC.

any more suggestions from anyone always welcome...

 

[Revolver95]

I tried 'mfastboot erase all' and reinstalled everything but result is same!!!

so i believe eMMC has somehow become read only or worse corrupted.

I see few post where people have tried various solution without success:
http://forum.xda-developers.com/moto-g/help/damaged-internal-sd-t2866484

so , I am not having much hope...

over the weekend, I will search for some local service center who can replace eMMC.

any more suggestions from anyone always welcome...

Did you try the flash5.1.bat? I posted it a while ago in this thread

 

[jignesh_shah]

Did you try the flash5.1.bat? I posted it a while ago in this thread

@Revolver95, yes, i tried flash5.1.bat and result is same. Its not affecting flash (eMMC)

btw, flash5.1.bat is doing nothing different. It also executes same bunch of commands using mfastboot which are given are in many other articles...

anyways, appreciate your suggestion and time...