Develop Bugs

[SOLVED] Unable to mount '/data'

I have a KF1 v6.x (I believe since it was stock). Installed KFU 1.4a. Installed TWRP. Following a post in the [ROM-AOSP] Stock Jelly Bean 4.2.2_r1 for the Kindle Fire [02-12 4.2.2_r1] thread I wiped factory reset then wiped system PRIOR to moving the ROM to the sdcard. Now, there is no OS. I was able to put the ROM.zip on the root of the SD card but when attempting to install it I get "Unable to mount '/data'". I've tried several commands for adb to do partition stuff but didn't get anywhere with that. Not sure if FastBoot is working via KFU due to the following message.
hxxp://imageshack.us/photo/my-images/547/37437819.png/
What's my first step here? I can get into TWRP so hoping this KF isn't totally hosed

Looks like Fastboot is working?
hxxp://imageshack.us/photo/my-images/14/75434412.png/

http://forum.xda-developers.com/showthread.php?t=1949372

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
SUCCESS! :victory: Thanks soupmagnet! Pic of partition table attached showing /data is not mounted. When doing umount cmd received message "can't umount /data: invalid argument" which I guess is good since /data is not mounted in the partition table.
After removing, making, then naming the partion and quitting I received a message: Information: You may need to update /etc/fstab. 2nd pic shows /data correctly mounted.
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?

AnotherBrickedDroid said:
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?
Click to expand...
Click to collapse
1) It's hard to say really. For the sdcard, I always assumed it was from not "ejecting" it before unmounting, but I think that would be kind of hard to recreate with the data partition. If I were to speculate at this point, I would say it had to do with how certain versions of TWRP format those partitions, but I'm not sure. In either case it's pretty rare for it to happen.
2) From what I understand, you can't. Recovery is unpacked and run from active memory so any changes you make to fstab will be lost every time you reboot. But the filesystem should still be automatically checked every Nth mount.
3) Three guesses? The first two don't count?

[Q] Won't mount /data/ and won't mount /cache/

I'm currently in TWRP and when I try to install a rom, or wipe for factory reset, the recovery keeps telling me it's unable to mount /data, unable to mount /cache, and unable to mount /storage. Is there any way i can recover from this?

You could try manually mounting them from an adb shell and seeing if it errors out and if it does it might provide more info to help diagnose what's going on. I don't have the specific command handy and I'm about to goto bed, I'll see about posting it when I get up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

[Q] Can't Boot but can get into recovery, fastboot, and ADB but nothing seems to work

If I try to boot normally I get stuck on the boot screen. I can go into recovery (Clockwork Mod) but no combination of Flashing partitions seems to do anything. The one thing I've noticed is in Mounts and Storage /system; /data; /firmware/mdm; and /firmware/q6 all can be mounted. I can mount both /system and /data but the 2 /firmware partitions wont mount and if I check the log it reads
mount: mounting /dev/block/mmcblk0p16 on /firmware/q6 failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p16 (No such file or directory)
Error mounting /firmware/q6
I don't know if these 2 partitions would prevent booting up if they fail to load or if its something totally different. I've tried flashing just about everything I can find and nothing seems to take. Any help would be fantastic, if you need more info, just ask and I will do my best to get it for you. Thank You

fischerdave said:
If I try to boot normally I get stuck on the boot screen. I can go into recovery (Clockwork Mod) but no combination of Flashing partitions seems to do anything. The one thing I've noticed is in Mounts and Storage /system; /data; /firmware/mdm; and /firmware/q6 all can be mounted. I can mount both /system and /data but the 2 /firmware partitions wont mount and if I check the log it reads
mount: mounting /dev/block/mmcblk0p16 on /firmware/q6 failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p16 (No such file or directory)
Error mounting /firmware/q6
I don't know if these 2 partitions would prevent booting up if they fail to load or if its something totally different. I've tried flashing just about everything I can find and nothing seems to take. Any help would be fantastic, if you need more info, just ask and I will do my best to get it for you. Thank You
Click to expand...
Click to collapse
I was in a similar situation a few months back. Have you tried flashing a RUU? Preferably the current version or a newer version.
http://forum.xda-developers.com/showthread.php?p=46506621

Can remember if I did or not so probably worth a shot
I'm Downloading now and will let you know how that goes. Thanks.

fischerdave said:
I'm Downloading now and will let you know how that goes. Thanks.
Click to expand...
Click to collapse
Give me a holler of you don't get it booted.

[Help] /data partition empty/corrupted

I have a Samsung Galaxy S3 (SGH-I747). It was running fine on CM13 nightlies. One night I needed the phone for calculator (odd enough lol) and noticed it was turned off. I turned it back on. It seemed like it was just gonna boot like it usually does but I got a bootup message claiming that the /data partition is corrupted and needs to be reset to continue using the phone.
I followed the phones instructions and did the reset (I've had to factory reset before I really didn't care). It booted to TWRP (3.0.2-0) and started the factory reset. The log for the recovery showed many errors. Heres the log if I just boot into TWRP without doing anything:
Code:
[COLOR="Red"]Failed to mount /data and unable to find crypto footer.
Failed to mount '/data' (No such file or directory)[/COLOR]
[COLOR="red"]Unable to recreate /data/media folder.[/COLOR]
Updating partition details...
[COLOR="red"]Unable to mount '/data' (No such file or directory)[/COLOR]
...done
[COLOR="red"]Unable to mount storage
Failed to mount '/data' (No such file or directory)[/COLOR]
Full SELinux support is present.
Running boot script...
Done.
[COLOR="red"]Unable to mount /data/media/TWRP/.twrps[/COLOR]
MTP Enabled
[COLOR="red"]Failed to mount '/data' (No such file or directory)[/COLOR]
The same errors pop up when wiping the device too.
Here's what i've tried:
The corrupt data reset (didn't work)
Reinstalling a new copy of CM13 (didn't help)
I also have tried flashing stock images (AT&T) firmware. Did not work, the AT&T system says the /data partition is corrupted too and cannot do anything about it.
NOTE: The /data partition info in TWRP shows the size as 0MB!
I've posted for help on the cyanogenmod forums but no avail so far. I do not what to do next and need some suggestions.
Thanks.

Have you tried Odin to flash the stock firmware?

StoneyJSG said:
Have you tried Odin to flash the stock firmware?
Click to expand...
Click to collapse
That's what I used to get the stock firmware on it in the first place...

I'm still learning how to mod and customise android so I completely missed this.
The fix was as simple as changing the filesystem into a different format on TWRP..
Sent from my SAMSUNG-SGH-I747 using Tapatalk

TechGuyAnthony said:
I'm still learning how to mod and customise android so I completely missed this.
The fix was as simple as changing the filesystem into a different format on TWRP..
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
thanks for posting fix as i'm sure it will help others.
"err on the side of kindness"

Xperia M TWRP İnternal Storage 0 MB Problem!

Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.

didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
Your device got ebola. There is no solution. Sorry mate.

Use internal storage 0 mb problem in TWRP Recovery. No flashing kernel and roms.

didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
i am having same problem . but my internal storage is mounted as android os and my actual storage is not visible please help me.

fix for 0MB internal storage problem
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.

rak-zero said:
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.
Click to expand...
Click to collapse
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
https://imgyukle.com/i/Rk24Gt
https://imgyukle.com/i/Rk264c
https://imgyukle.com/i/Rk2fyR

didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse

rak-zero said:
didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse
I am using TWRP version 3.1.1.0. I tried to make Wipe after it restarted after operations but it still seems to be 0MB. I tried to change the file system, but not through the terminal.
Click to expand...
Click to collapse