[Q] Hard bricked or what?

[Aequus.Mihi]

Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).

I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.

TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything

What the hell is going on with my phone? Any ideas people?

 

[itouchables]

Somehow, your file system can't be accessed....was your phone encrypted?

 

[Aequus.Mihi]

Somehow, your file system can't be accessed....was your phone encrypted?

It wasn't, I never encrypted it.

Also fastboot getvar all shows that my partition type is RAW.
Shouldn't it be F2FS or EXT4?

Maybe anyone has a proper partition mount point list for the Moto G?
I would try mkfs.ext4 formatting every possible mount point (cache,data,system and etc)
For example dev/block/mmcblk0p38
I found a Moto X mount point list but I have no clue if it's the same or not

 

[Oliverrlh]

Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).

I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.

TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything

What the hell is going on with my phone? Any ideas people?

Hi! did you find a solution?!

 

[Aequus.Mihi]

Hi! did you find a solution?!

No. Turns out my phone memory chip was corrupted due to flashing

 

[Icon000]

No. Turns out my phone memory chip was corrupted due to flashing

I think I might have a similar situation. Can you give me an advice on how to confirm this?

The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.

Does this sound like your situation?

 

[Aequus.Mihi]

I think I might have a similar situation. Can you give me an advice on how to confirm this?

The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.

Does this sound like your situation?

That's the same situation I was in.
Even if you try to flash another ROM, it will never install.
You can't modify any files because the memory is ****ed.
I sold the phone for parts and bought a S4