Database Info

[Q] fstab can't mount system, sdcard, or anything really.

So yeah, my phone was regular 2.3.4 and it wouldn't always reboot easily (took multiple tries). So I figured I'd install CyanogenMod 7 like all the cool kids. I'm a programmer, this should be easy, right? Wrong.
So after much trial and error fastboot decided to randomly find my phone and let me unlock it (long story...). I start playing around with adb and fastboot, having a good old time. I decide to do the ClockworkMod Recovery image and it works great. I try to do an "update from sdcard" with the latest CyanogenMod for Nexus S and it amazingly works!... Except that it still won't boot up. It sits on the Google loading screen--I suspect failing to mount anything.
I found out about this:
Code:
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/platform/s3c-sdhci.0/by-name/media (null)
2 /system ext4 /dev/block/platform/s3c-sdhci.0/by-name/system (null)
3 /cache yaffs2 cache (null)
4 /data ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata (null)
5 /misc mtd misc (null)
6 /boot mtd boot (null)
7 /recovery mtd recovery (null)
8 /bootloader mtd bootloader (null)
9 /radio mtd radio (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Notice all of the (null)s....
Also this:
Code:
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
E:Can't mount /sdcard/update.zip
Installation aborted.
mtd: successfully wrote block at 0
I:Set boot command ""
E:Unable to write to ums lunfile (No such file or directory)
...and this, clearly from fstab:
Code:
/dev/block/platform/s5pc110-onenand # mount -a
mount -a
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/userdata on /data failed
: No such file or directory
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/system on /system failed
: No such file or directory
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/media on /sdcard failed:
No such file or directory
There's no s3c-sdhci.0 in /dev/block/platform.... only s5pc110-onenand (which happens to be the title of the processor and memory used in my phone).
So yeah, that's where my brain gives out.
I'd like to install CM7, or at the least get a working phone back somehow.
Oh yeah, I tried doing adb shell and a nandroid restore command w/ downloaded nandroid backup. No love. It told me "unknown volume for path [/sdcard] Can't mount /sdcard". No ****.
Ideas?
Thanks!

Small update:
about 1 out of 100 times, it'll allow me to mount the sdcard after some random fiddling. I have tried multiple recovery images, erasing partitions, flashing random things... nothing works!
The one or two times it mounted the sdcard, I was able to perform an "update from sdcard" but then it would just do what it has done for a long time--sit at the google loading screen for hours and never actually boot into the real OS.
Sigh. Hardware issue maybe?

Hi,
what's your phones status?
My Nexus seems at a similar state now I came across http://forum.xda-developers.com/showthread.php?t=991276 and had to try it (why not, I have nandroid backups, Titanium etc. ...) I applied a setting, rebooted and got stuck at the google logo. It would boot into recovery but there it has no access to sdcard, system, data (but cache is mounted). After lots of fiddling I got it to work once, whiped, flashed a rom and all looked good again. But now I did a reboot and the phone is stuck again and in recovery (CWM 3.something) I get no sdcard
What happened and how to fix it?

I managed to flash a stock system back on the phone and it still didn't work, so I called Samsung and they let me RMA the phone. I got it back three weeks later, in good shape. They had to replace the PBA, the mainboard, and they did it all for free. They even gave me a shipping label to use when I shipped it out. Nice.
At the least, I think it's necessary to flash a stock bootloader and lock the phone before calling them.
Good luck!

Good for you
I tried flashing a stock rom, both using fastboot and also using Odin, both methods fail or get stuck while flashing the system.img
Looks like I've screwed up
If I could at least once get to the data on sdcard ...

i think i found a workaround
i tried flashing the old clockworkmod (3.1.0.1) and the flashing the latestest one twice and then clockworkmod was able to mount the sdcard. huge relief. installed the rom and then rebooted and the system booted well.
also tried installing the clockwork manager app and flashing the latest recovery from the app and then rebooted into recovery. it was able to mount the sdcard now.
not sure if this random success or a fix. it worked.

Had the same exact issue. Sprint tech replaced the phone for me for $35 without insurance. But basically the internal memory would only mount once every 10-100 reboots.
Definitely a manufacturing issue.

obsanity said:
Had the same exact issue. Sprint tech replaced the phone for me for $35 without insurance. But basically the internal memory would only mount once every 10-100 reboots.
Definitely a manufacturing issue.
Click to expand...
Click to collapse
Have you tried reflashing the recovery twice?
Did the sprint tech provide the details on what exactly the issue was?
In my case, the phone is contract free and I have to approach samsung support if this issue occurs again.
Since the sdcard is some times mounting, i am hopeful that there should be a way out via sw.

gsrdemon said:
Have you tried reflashing the recovery twice?
Did the sprint tech provide the details on what exactly the issue was?
In my case, the phone is contract free and I have to approach samsung support if this issue occurs again.
Since the sdcard is some times mounting, i am hopeful that there should be a way out via sw.
Click to expand...
Click to collapse
Samsung service center repaired the device (mother board replaced); in warranty.
Sent from my Nexus S

[Q] Has anyone gotten encryption to work on Pyr'o'Ice ICS (or another ICS) ROM?

In the Pyr'o'Ice ICS Desensed 1.1.3 ROM, there is an option to encrypt the phone data. I would really like to do this, but unfortunately it does not seem to work. I have also tried the 1.1.0 ROM with similar results.
The UI allows me to start the encryption process, however one of the following happens (all of these happen within about 1 minute of starting the process, not over an hour like the informational message states it will take):
1. I am presented with a screen saying the encryption process failed, and I have to wipe the phone. The screen does not go away unless I do something.
2. I see the 'encryption process failed' screen, but only for a second and then the phone reboots into normal operation.
3. I do not see the 'encryption process failed' screen, and the phone boots into normal operation.
In case #2 and #3 I am able to use 'adb shell' to gain access to /data before I enter in the PIN on the device. Additionally, /proc/mounts is the same before and after the process.
I am running clockworkmod recovery 5.0.2.7 and have hboot 1.44.1107 with S-OFF. I always do a wipe before flashing any ROM.
Has anyone gotten this to work (even with another ROM), and if so how? Does anyone know how the encryption is supposed to work (e.g. is the filesystem supposed to be encrypted itself, or just some files)?
I really don't like the idea of having personal data on something that doesn't at least have data at rest encryption.

So far I've tried every ICS ROM I can find, and the ones that have an option for encryption all seem to have the same errors (from adb logcat):
D/Cryptfs ( 138): unmounting /data succeeded
E/Cryptfs ( 138): Cannot get block device name of extra partition
E/Cryptfs ( 138): Cannot load dm-crypt mapping table. (Invalid argument)
I/Cryptfs ( 138): Making empty filesystem with command /system/bin/make_ext4fs -a /data -l 1252770816 /dev/block/dm-0
E/Cryptfs ( 138): Error creating empty filesystem on /dev/block/dm-0
Which makes me think something is not right with my existing partitions or formatting, causing it to fail. Looking at the android crypto docs (which I can't post a link to currently, the forum won't let me), I got the idea to make the data filesystem a bit smaller than it's partition using make_ext4fs -l (at first I tried leaving an extra 16K at the end, then I tried 1M), but I got the same results. Previously I'd always used the wipe option in clockworkmod recovery, which I assume makes the filesystem stretch to the entire size of the partition.
Interestingly enough, doing both the inplace and wipe encryption methods seem to have the same results. Even though the inplace option is the only one presented in the UI that I can find, digging around through the code I found I could run "/system/bin/vdc cryptfs enablecrypto wipe <password>" to do the wipe+encrypt option.
Hasn't anyone gotten encryption to work on ICS?

Still no luck finding a build that this works on. Has anyone?
cuddlebug said:
So far I've tried every ICS ROM I can find, and the ones that have an option for encryption all seem to have the same errors (from adb logcat):
D/Cryptfs ( 138): unmounting /data succeeded
E/Cryptfs ( 138): Cannot get block device name of extra partition
E/Cryptfs ( 138): Cannot load dm-crypt mapping table. (Invalid argument)
I/Cryptfs ( 138): Making empty filesystem with command /system/bin/make_ext4fs -a /data -l 1252770816 /dev/block/dm-0
E/Cryptfs ( 138): Error creating empty filesystem on /dev/block/dm-0
Which makes me think something is not right with my existing partitions or formatting, causing it to fail. Looking at the android crypto docs (which I can't post a link to currently, the forum won't let me), I got the idea to make the data filesystem a bit smaller than it's partition using make_ext4fs -l (at first I tried leaving an extra 16K at the end, then I tried 1M), but I got the same results. Previously I'd always used the wipe option in clockworkmod recovery, which I assume makes the filesystem stretch to the entire size of the partition.
Interestingly enough, doing both the inplace and wipe encryption methods seem to have the same results. Even though the inplace option is the only one presented in the UI that I can find, digging around through the code I found I could run "/system/bin/vdc cryptfs enablecrypto wipe <password>" to do the wipe+encrypt option.
Hasn't anyone gotten encryption to work on ICS?
Click to expand...
Click to collapse

FYI I finally got it to work with the latest CM9 build, although the manual method I mentioned above was needed ("/system/bin/vdc cryptfs enablecrypto wipe <password>"), since the gui encryption option still didn't work.

[Completed] Unable to encrypt Motorola RAZR HD, solutions found don't fit

Would appreciate if someone can point me to the right direction here.
Having some problem to encrypt my internal SD card.
Motorola RAZR HD (XT925)
CM 11-20140104-SNAPSHOT-M2-xt925
SELinux Permissive
Problem and symptoms:
1. If I follow the normal procedure to encrypt (charged >80%, connected to USB, removed external SD card), as soon as the "green wireframe robot" appears it gets stuck there without the percentage encryption appearing. I searched and found this means encryption hasn't even started. It's true. I boot and nothing has happened.
2. If I try the same through command line running this command
vdc cryptfs enablecrypto inplace 1234
I get the following error message
200 -1 5 (or something like that)
3. The results of adb logcat when trying either the GUI or terminal are:
E/Cryptfs ( 313): Cannot get size of block device
Solutions:
I looked everywhere for solutions, but found nothing quite like the issue I'm having. See:
1. One place mentions trying to connect USB to power supply instead of computer, because that worked for him. Didn't work for me.
2. Most complaints about not being able to encrypt mention the following as the error:
E/Cryptfs ( 2407): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
This is NOT the error message I get. Maybe after I solve the problem of the current error message this other one will come up, but so far my error message is different and I have no reason to believe that the proposed solution to this error message (resizing data partition) would solve the issue.
3. The only explanations I found about the reason of my error message (Cannot get size of block device) is that you can't encrypt yaffs, only ext4. But I checked and my data partition is ext4:
$ mount | grep /data
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=writeback,noauto_da_alloc 0 0
and
$ cat /fstab.qcom
shows that /system /data /cache /firmware and /persists are ext4, that mmc_host and msm_hsusb_host are vfat, and all others are emmc
What am I overlooking? What else can the problem be?
Also a question: should I expect response time (you know, lags) to be significantly worse after encryption? And battery consumption?
Thank you.

Hi,
As it's a custom rom you are running, you will need to register on XDA and ask about your issue in the thread you downloaded the rom from.
Good luck!

[Q] [BRICK'd?] Can't mount /data /cache /system

One day, about 2-3 weeks ago, on my way to home, I decided to install an other ROM (5.1.1 ivanchi -> CM9). Went straight into recovery (TWRP 2.8.5 or 6) and formatted everything except microsd, everything seemed to go as planned. Then proceeded to install the ROM; it gets stuck, can't get pass the booting screen even after 20-30 minutes. Force-Reboot into recovery and receive "unable to mount /data | /system | /cache error". Tried changing fs-type of /data /cache /system to any other type, no success.
Got back home, tried installing RUU. Got stuck at 39%. every. single. time. !! Tried an older RUU, same response.
Then tried even oem lock + flash recovery_signed.img + boot boot.img with fastboot and then RUU install. Then again with unlocked bootloader. Still no! But, I didn't tried lock + recovery signed + boot + S-On, because I am afraid not to be able to regain S-Off at this state.
Even tried a parted format, implying that one guy managed to make it work in the end. See topic here : link.
Tried doing guy's steps but after parted /dev/block/mmcblk0 I receive Error: Can't have overlapping partitions. Tried then parted /dev/block/mmcblk0p23 (userdata), it works, and if I try mkfs/rm on partition 1, it says it's in use (p23p1 ...).
Output:
~ # parted /dev/block/mmcblk0p23
parted /dev/block/mmcblk0p23
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p23
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p23: 1253MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 1253MB 1253MB ext4
(parted) rm
rm
rm
Partition number? 1
1
1
Error: Partition /dev/block/mmcblk0p23p1 is being used. You must unmount it
before you modify it with Parted.
(parted) mkfs
mkfs
mkfs
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
Yes/No? yes
yes
yes
Partition number? 1
1
1
Error: Partition /dev/block/mmcblk0p23p1 is being used. You must unmount it
before you modify it with Parted.
I can format my /data /system /cache one at the time, after doing reboot recovery and that's only in CWM 6.0.1.2. But this CWM isn't able to install ROMs somehow, wether it gets stuck of just plain fails. So, if I want to install a ROM, after the format, I have to install 4Ext (latest) recovery and do it there. Install everything from recovery, boot, sign in for GApps etc etc and while trying to install apps from Google Play, after about 4 to 6 apps, it gives a black screen, leaving no option but remove battery and reboot. Do that and get stuck on bootsplash / bootscreen. Everytime!
If then I try formatting paritions using 4Ext most of the time it fails, making them unmountable again after all.
Tried everything mentioned running PG58IMG with firmware 3.33, Hboot 1.27.1100, worldwide english (.104.). Tried fashing rom.zip as the PG58IMG.zip from fastboot in rebootRUU (gets stuck at [RUU]WP,dzdata,0) and now even from sdCard (gets stuck at [6] USERDATA).
I dug furthermore into bricked Sensation, seeing a QHSUSB brickbug (thread). It is refeered to be a bootloader brickbug; problem which I am not facing right now. Eventho, followed OP's instruction my freshly installed Ubuntu 14.04 can't detect my HTC. Also did some of the YouTube instructions, connecting sdcard's plate with lower pin from the back (trolled?!) (video), yet nothing.
Out of disperation, asked hinxnz and rzr86, and both of you adviced me to try thread 1 or 2 (relying on sdCard as primary/sec partitions). Good advices but I don't consider this be the best solution for this problem; STILL HAVE HOPE MAKING INTERNAL SD TO WORK! :d
ASK ME ANYTHING REGARDING MY PROBLEM! Will post every bit of information you consider relevant.
PLEASE HELP!

u tried ruu, didnt work, tried firmware, didnt work. @rzr86 and @hinxnz gave u those guides coz its the only known way to fix/bypass that problem on xda. maybe there is another way but no one has found it yet. u could take ur phone to a repair shop, pay bout a hundred bucks, connect it to jtag and hope for the best, but that might not even flash partitions back.
personally i dont see how twrp is still allowed to be downloaded on xda in the sensation thread coz it keeps killing peoples phones. that jus my opinion tho.

Atm my phone is literally bricked, QHSUSB brick because of my stupidity... Maybe I will make it to work again; anyways...
For the partition problem, don't the HTC has some kind of .pit files like Samsung does? They should! Also, what if someone with a 'healthy' Pyramid does a dd of the /dev/block/mmcblk* for those with fk'd partitions to use ?

Hi, one more here with wrecked partitions by TWRP factory reset....
Trying to Ruu the Sensation, but RUU has been getting stuck in the process ... I'll edit if I success.
Thanks for all the info out htere!
Edit: no success, even tried at last to fix partitions (parted and fdisk) via ADB, device is now dead. So sad HTC or any ever gave the details for the partition table, a simple script might have solved this.

I'm just catching up on this one.
If I read this right,the information on the partitions was trashed by TWRP recovery?
There was a member that stated the HTC Desire used to be able to have it's partitions reconfigured,IIRC.
Perhaps this is the first step to achieving that with the Sensation?
Sent from my SM-N915W8 using XDA-Developers mobile app

I'm too woried nowadays....i got the error can't mount system,data,cache inmy xolo a600...i can't flash custom rom or can't do factory data reset...but when i try to factory reset using my stock firmware recovery it's done...but in twrp & cwm recoverys say can't mount system,data,cache...i also can't connect my device to pc using usb mode,mtp...my pc said unknown device detected...what to do?...i just really tired & tensed please please please guys give me the solution...please...!!

Unable to mount cache/data...

Hi, i have a problem with my sensation.. When i tried to do factory reset from phone settings including SD card (i didnt needed anything from sd) before installing new rom, something went wrong. After that format my phone doesnt boot any more, it get stuck on rom logo. I still can enter bootloader and recovery (TWRP 2.8.6) but when i try to use factory reset (wipe) again in recovery it shows me this (i cant upload images so i took everything in text):
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount '/cache'
MTP Enabled
Formtatting Cache using make_ext4fs function.
E:Unable to mount '/cache'
Formtatting Data using make_ext4fs function.
E:Unable to mount '/data'
Wiping android secure
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/system'
...done
and on top i get message Factory reset complete - successful.
Then when i try to install rom i get this:
Format and Mount System, Mount Data...
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/' rom.zip
Error flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/system'
...done
And there i get zip install complete - failed... Is my device briked? I dont even know what should i do.. I tried to search something similar but didnt realy found any solution. Maybe anyone knows this problem?
Bootloader info:
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OPENADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012.17:33:34
P.s. Sorry for my english

Sounds like good old "there goes your motherboard". I've had it happen last week or so.

you used wipe option from twrp
big mistake
see here if you have any luck
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
pay attention to the last posts

As @Harakhti and @rzr86 said, you are in deep trouble, just like many of us. Unfortunately, no one knows a solution to this problem. It is an old phone and most Android tech "wizards" have upgraded to newer devices, so I am not so sure we will ever get one. People here try their best to come up with solutions (and are being helpful), but the diagnosis is always the same: eMMC blocks are corrupted, no data is allowed to be written on them. Possible fixes? Complete repartition, but we need to have detailed information about whole partition/block layout, and the right knowhow.
Check the thread @rzr86 has linked. There is a post by @Harakhti that provides some (very) technical information about a similar problem. It could be related to our Sensations, but this doesnt solve our issues unfortunately.
But you know whats the real problem? I am convinced that the TWRP pyramid .zip on their official website caused this problem to appear in the first place. 4EXT and ivanovichs recovieries seem to be safe. Amount of people who encountered this problem and soft-hardbricked their phones keeps on growing every day. And yet, this .zip is still on that website, so more and more people who are looking to mod their old smartphones are installing this buggy version. We, as a community on xda, should make sure that no more phones will be damaged by this glitchy piece of software.
Still, I am sorry for that. I am in the exact situation. My phone is being "repaired" by my fathers friend, but I am pretty much convinced that this phone is a lost cause. Unless a miracle happens. Sometimes they do. Most of the time not.

XTacDK said:
above post
Click to expand...
Click to collapse
This is pretty summarizing and accurate, except I got bricked with Ivanich's TWRP R14 for CM13.
The issue, if it's what I assume to be, would be that the eMMC just burns itself out when given a secure erase command. This possibility is tough, since it's about almost impossible to find a replacement motherboard for this device (FYI, the price for the mainboard is around 50€ at the time of writing, which is a hella lot for a device that costs around €95 total in a retail store around here).
To be honest, I'm not keen on getting a new phone, so if I turn out to be wrong, then I'll be happy that I can keep it for a few more years. This device has proven that it's absolutely capable of running any and all Android versions as long as you have a decent SD card.

I srcewed up my data partition with @ivanich twrp on one of my two sennys.
Weired since I formatted partitions many times on one phone in twrp, but the first time I switched from 4ext to twrp on the other phone,
the partition was corrupted after 1st wipe.
I still use this phone as a daily driver with @hinxnz mod "All Data on SD-EXT" (here) using a fast class 10 card.
There's definately no remarkable performance difference between the 2 phones + now I have a larger data partition.

Harakhti said:
This is pretty summarizing and accurate, except I got bricked with Ivanich's TWRP R14 for CM13.
The issue, if it's what I assume to be, would be that the eMMC just burns itself out when given a secure erase command. .
Click to expand...
Click to collapse
Funny thing is that secure erase has been disabled in kernel few years ago the same goes for discard and other dangerous things, also it has been disabled in userspace utils like mkfs.*
At the most cases it's ends up like this:
Jonas_HtcSensation said:
Hello ivanich,
I accidently formatted /data with the TWRP that is linked in your cm13 thread.
As i know now this will mess up the partitions for our Sensation as some other people have experienced as well.
I dont blame any one else than myself for not looking into TWRP enough, but maybe it is an good idea to warn people about using TWRP in your initial post.
When there is a recovery that is 'promoted' by a qualified person as you, people often think that everything fully works on this recovery. As happend to me.
So maybe just add a warning? If i manage to get my phone working somehow, i will make an instruction that can also be added.
Thank you for your work on our phone, i used your cm 12 for a long time and it was awesome.
Jonas
Click to expand...
Click to collapse
Quote:
Originally Posted by ivanich
Hi, perhaps you a first person who bricked /data partition with TWRP from https://drive.google.com/folderview?...p=sharing#list . I'm using twrp almost every day and formating partitions, including /data, 7-10 times per day without any issues, also AFAIK the were no reports about such problems with my twrp builds. Sometimes peoples bricked their phones with official twrp builds
Okay. You seem to be right, sorry.
I looked into my Download history:
I downloaded ~6 different versions from your google drive and 1 single version from twrp direct.
With my luck i bricked my phone the one time i had the wrong twrp installed... That makes it even annoying for me
Sorry to bother you,
Click to expand...
Click to collapse

ivanich said:
Funny thing is that secure erase has been disabled in kernel few years ago the same goes for discard and other dangerous things, also it has been disabled in userspace utils like mkfs.*
At the most cases it's ends up like this:
Click to expand...
Click to collapse
Odd. Thanks for the heads-up. All I did was change between the CM12 and CM13 versions, so I'm not sure how I screwed it up (particularly, formatting got stuck in 2.8.7.0 R14 for CM13).
But I guess the suspicion's correct and I blew my MMC, right?

Harakhti said:
Odd. Thanks for the heads-up. All I did was change between the CM12 and CM13 versions, so I'm not sure how I screwed it up (particularly, formatting got stuck in 2.8.7.0 R14 for CM13).
But I guess the suspicion's correct and I blew my MMC, right?
Click to expand...
Click to collapse
I'm not sure about that. Discarding device blocks: 4096/305852 - according to your log mkfs was completed succesfully but discard failed. Try to boot into recovery and play with mkfs and data partition, something like this:
make_ext4fs /dev/block/mmcblk0p23
or
mkfs.f2fs /dev/block/mmcblk0p23

Hey, @ivanich
Its good to see you here
Maybe those commands will help other people. They did nothing for me. unfortunately. I tried commands with mmcblk0p23, 22 and 24 (/data, /system, /cache), but it all said something in lines of "make ext4fs not found"
Either my ADB was not setup properly (weird because every other command i needed worked fine) or my partition table was broken beyond means of repair.

ivanich said:
I'm not sure about that. Discarding device blocks: 4096/305852 - according to your log mkfs was completed succesfully but discard failed. Try to boot into recovery and play with mkfs and data partition, something like this:
make_ext4fs /dev/block/mmcblk0p23
or
mkfs.f2fs /dev/block/mmcblk0p23
Click to expand...
Click to collapse
Code:
~ # mkfs.f2fs /dev/block/mmcblk0p23
F2FS-tools: mkfs.f2fs Ver: 1.5.0 (2015-11-05) [modified by Motorola to reserve space]
Info: Debug level = 0
Info: Label =
Info: Segments per section = 1
Info: Sections per zone = 1
Info: Trim is enabled
Info: sector size = 512
Info: total sectors = 2446818 (1194 MB)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.4.110-ga791ac3-05576-g23ced4d ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Dec 30 20:19:53 EET 2015"
Info: Discarding device: 0 sectors
Code:
~ # make_ext4fs /dev/block/mmcblk0p23
Creating filesystem with parameters:
Size: 1252769792
Block size: 4096
Blocks per group: 32768
Inodes per group: 7648
Inode size: 256
Journal blocks: 4778
Label:
Blocks: 305852
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/76480 inodes and 10067/305852 blocks
Then it freezes. Logs:
http://pastebin.com/4NSf9zBG
Last 5 lines repeat forever.