MOTO G ( XT 1033 16 GB Dual Sim ) Bootloop + E:unable to mount '/cache'

@googlecardboard wrote:

@PaytmKaPoojari wrote:

@googlecardboard wrote:

@PaytmKaPoojari wrote:

@googlecardboard do this ask someone with the same mobile model no to download these apps

https://play.google.com/store/apps/details?id=m...

or

https://play.google.com/store/apps/details?id=c... ( i prefer this one )

and check the block for the data partition which maybe around 11 to 13 gb on his phone format the above code for the same block .

Please note : These are formatting blocks so double check the block no before formatting since block nos are model specific

also make ext4fs formats the partition dont worry .

I already found partition layout of my model here
“http://forum.xda-developers.com/showthread.php?...”

I asked this ques to one expert on XDA forum and he too confirmed that data partition is
mmcblk0p36

but error log says unable to write on mmcblk0p0

so I am confused what to do now

which one to format ??

unfortunately ur emmc is dead . I think emmc repair is possbile but you will need a really good guy to do it with jtag repair tool and emmc card reader

can u do it ??

I don’t have the resources to do it. U can try manish market area in mumbai or gaffar market in delhi and ask them repair shops u need to do Emmc repair /boot repair. Half of the people are really dumb but trying various shops may get u what u need.

@PaytmKaPoojari wrote:

@googlecardboard wrote:

@PaytmKaPoojari wrote:

@googlecardboard wrote:

@PaytmKaPoojari wrote:

@googlecardboard do this ask someone with the same mobile model no to download these apps

https://play.google.com/store/apps/details?id=m...

or

https://play.google.com/store/apps/details?id=c... ( i prefer this one )

and check the block for the data partition which maybe around 11 to 13 gb on his phone format the above code for the same block .

Please note : These are formatting blocks so double check the block no before formatting since block nos are model specific

also make ext4fs formats the partition dont worry .

I already found partition layout of my model here
“http://forum.xda-developers.com/showthread.php?...”

I asked this ques to one expert on XDA forum and he too confirmed that data partition is
mmcblk0p36

but error log says unable to write on mmcblk0p0

so I am confused what to do now

which one to format ??

unfortunately ur emmc is dead . I think emmc repair is possbile but you will need a really good guy to do it with jtag repair tool and emmc card reader

can u do it ??

I don’t have the resources to do it. U can try manish market area in mumbai or gaffar market in delhi and ask them repair shops u need to do Emmc repair /boot repair. Half of the people are really dumb but trying various shops may get u what u need.

I live in jaipur
neways just checked xda about this error and saw threads my emmc is now read only
that means i cant delete and cant flash nething
flashing will be done but after rebooting nothing will gonna changed

ab koi new mobile lena padegah

did u try flashing by connecting it to pc? I recovered one moto g 2nd gen which was bricked while installing ota. for same mobile moto service center and 3rd party guy had said it needs mobo replacement. so don’t lose hope. see videos on YouTube and try flashing completely as long as u don’t care about the data on it.

@harpy.eagle wrote:

did u try flashing by connecting it to pc? I recovered one moto g 2nd gen which was bricked while installing ota. for same mobile moto service center and 3rd party guy had said it needs mobo replacement. so don’t lose hope. see videos on YouTube and try flashing completely as long as u don’t care about the data on it.

It’s not an update issue it’s an emmc issue as some bad sectors block have made it unusable for the time being. Emmc failing is rare but it occurs and though features like fschk and stuff are created for repairing the bad blocks sometimes even they fail. In such a case only a professional repair shop who has hardware and software to directly connect to the emmc card can perform a reflash of that emmc

And fastboot is primitive enough to not throw any errors during flashing stock rom. But since the data partition is corrupt and non functional then even if it shows success nothing is written to the system image since emmc is now read only

@googlecardboard wrote:

@PaytmKaPoojari wrote:

@googlecardboard wrote:

@PaytmKaPoojari wrote:

@googlecardboard do this ask someone with the same mobile model no to download these apps

https://play.google.com/store/apps/details?id=m...

or

https://play.google.com/store/apps/details?id=c... ( i prefer this one )

and check the block for the data partition which maybe around 11 to 13 gb on his phone format the above code for the same block .

Please note : These are formatting blocks so double check the block no before formatting since block nos are model specific

also make ext4fs formats the partition dont worry .

I already found partition layout of my model here
“http://forum.xda-developers.com/showthread.php?...”

I asked this ques to one expert on XDA forum and he too confirmed that data partition is
mmcblk0p36

but error log says unable to write on mmcblk0p0

so I am confused what to do now

which one to format ??

unfortunately ur emmc is dead . I think emmc repair is possbile but you will need a really good guy to do it with jtag repair tool and emmc card reader

can u do it ??

It requires jtag which itself is costly enough and only mobile repair shop keeps it for repairing. I think you should drop the idea to recover the phone. Get a cheap Android one if you’re low on budget and able to find a good deal.

I have both Moto G and bought Spice dream uno for 2800rs from Flipkart. Moto G 1st gen lags as compared to Spice dream uno and I’m amused how fast these Android one phones are as compared to 10k phs. Else, you can also buy Redmi prime which is around 6-7k.

@rv2012 wrote:

@googlecardboard wrote:

@PaytmKaPoojari wrote:

@googlecardboard wrote:

@PaytmKaPoojari wrote:

@googlecardboard do this ask someone with the same mobile model no to download these apps

https://play.google.com/store/apps/details?id=m...

or

https://play.google.com/store/apps/details?id=c... ( i prefer this one )

and check the block for the data partition which maybe around 11 to 13 gb on his phone format the above code for the same block .

Please note : These are formatting blocks so double check the block no before formatting since block nos are model specific

also make ext4fs formats the partition dont worry .

I already found partition layout of my model here
“http://forum.xda-developers.com/showthread.php?...”

I asked this ques to one expert on XDA forum and he too confirmed that data partition is
mmcblk0p36

but error log says unable to write on mmcblk0p0

so I am confused what to do now

which one to format ??

unfortunately ur emmc is dead . I think emmc repair is possbile but you will need a really good guy to do it with jtag repair tool and emmc card reader

can u do it ??

It requires jtag which itself is costly enough and only mobile repair shop keeps it for repairing. I think you should drop the idea to recover the phone. Get a cheap Android one if you’re low on budget and able to find a good deal.

I have both Moto G and bought Spice dream uno for 2800rs from Flipkart. Moto G 1st gen lags as compared to Spice dream uno and I’m amused how fast these Android one phones are as compared to 10k phs. Else, you can also buy Redmi prime which is around 6-7k.

yeah I dropped idea already after this emmc thing
now will gonna buy another phone
budget can be stratched upto rs 15000
waiting for a good phone

Dude … just flash the recovery again and it will work.. Also, are you using recovery for FALCON only??

PS: IDK if yo problem got solved or not..

I think you need to fix gpt first…..

@Joker wrote:

Dude … just flash the recovery again and it will work.. Also, are you using recovery for FALCON only??

PS: IDK if yo problem got solved or not..

Give him the falcon recovery link if you can.

Hi Guys,

I have very similar issue. I am also unable to flash custom recovery, stock/custom ROM..

Phone – Moto G -1st Gen. (XT1033) – Falcon, India, Asia retail
Issue – Bootloop, not booting android
Current State of phone,
1. Can access to recovery menu
2. Wiped cache – did not help
3. wiped data/factory reset – did not help

However, one thing in my case seems different is eMMC is not having any bad blocks but /system partition seems damaged/corrupted.
when I ran e2fsck manually from command line, following is output:

/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 (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

@jignesh_shah

Glad I found this thread .the only way would be an emmc partition repair . Mostly the Chinese profesisonal software package could help but if u can find one . Google out for professional emmc repair tool if any available online for moto devices .Afraid it’s the only viable solution I see for ur device at the moment . Another option is buying another emmc card from aliexpress , shouldering the emmc on the phone ( needs some serious efforts to refit the new emmc ) , identity a method to copy blocks and data from old emmc to new and hope everything works .

Tldr : go for a professional repair software if any

@PaytmKaPoojari Appreciate your response.

1. can i erase entire flash? I have backed up partitions from my phone such as PDS, HOB,DHOB, fsc (not sure if anything else is required). I assume if run flash erase all and then I flash everything back and later I restore above partitions it shall make functionally working phone. what do you say?
2. I understand that you mean eMMC is physcially okay but since there are unsolvable S/W errors, i should try replace eMMC

@jignesh_shah wrote:

@PaytmKaPoojari Appreciate your response.

1. can i erase entire flash? I have backed up partitions from my phone such as PDS, HOB,DHOB, fsc (not sure if anything else is required). I assume if run flash erase all and then I flash everything back and later I restore above partitions it shall make functionally working phone. what do you say?
2. I understand that you mean eMMC is physcially okay but since there are unsolvable S/W errors, i should try replace eMMC

Bro I caution u to try at ur own cost . Research well before erasing all partitions since even if u erase all those partitions maybe ur bad sectors will still be corrupt .there’s this merapi tool available which is capable of emmc devices which is there for mediatek devices I do not know if that would work with even urs .Also the thing is replacing an emmc isnt a childs play + u would have to be careful when reflashing the emmc with the new partition sizes and data. I am currently away from this online world so won’t be able to help u much since I am hardly on internet these days due to work . If u are able to resolve the issue do update on the thread . Once I get some free time maybe next weekend onwards if I get any solution I’ll try to tag u .

@PaytmKaPoojari , Appreciate your suggestions buddy.

I did try ‘mfastboot erase all’ and then flashed all the usual stuff as following,
p((. mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem fb_mode_clear
mfastboot.exe reboot-bootloader
pause

But the end result is same. Phone is in same condition as earlier i.e. bootloop. So,I suspect that somehow eMMC is in read-only.

as far as retrieving partitions, I believe it shall be taken care by gpt.bin (1st command in above list)

Meantime, I will check out for Merapi tool…

also, let me know if you can think of anything else to try…