Database Info

[Q] Unable to mount internal /sdcard

Hi everybody,
I've seen this question asked a few times but none of the answers worked with me.
Trying to create a second primary partition in my internal sdcard with MiniTool Partition I messed up the phone that now doesn't recognize the internal storage.
From TWRP I get the error message:
Code:
E:Unable to mount /sdcard
E:Unable to mount storage
I can mount the internal storage via TWRP and access it from windows or linux, I have even formatted it several times in FAT32 or ext3 to revert to the original situation but there's no way to make it discoverable by TWRP or by the OS.
As the recovery doesn't see it, it's impossible to flash a new rom because there's no place where to save the zip.
Can anyone please give me a suggestion ? :crying:

[solved]
I managed to access again to the sdcard by flashing the stock ROM from Nexus Root Toolkit

[Q] [Solved] Potentially bricked my tf700? Missing partitions

Hey all,
Long term creeper, infrequent poster. Would appreciate some guidance on whether my tf700 is recoverable or not.
After installing TWRP 2.8.1.0 to get a f2fs recovery for a fresh Cromi-KK flash, I went through a full wipe of all partitions. I was going to do this before converting the partitions to f2fs. I'd done it 20 minutes before but botched a step and had to start over. Everything was working before I began the wipe. About 15 minutes in I was growing concerned about the length of time and did a quick "adb devices".
Screen turns black for about 5 seconds and then vibrates. Tablet has rebooted. Damn. I'm pretty sure that's a bad sign. Bootup hangs after the four penguins (Cromi) and I see messages about items not available. I give it 10 minutes but it's not going anywhere. I'm able to power+volDown and boot into TWRP no issues. But that's where the problems begin. Most operations fail because:
Code:
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount storage
A quick cat /proc/partitions show:
Code:
179 0 31039488 mmcblk0
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
And no, I don't have NVflash access or backups
Any suggestions?
D

Can you still boot into the bootloader or is TWRP the only thing you can boot into?
BTW: You don't convert partitionS to f2fs. Only data gets converted to f2fs if you want to run that.
A full wipe in TWRP 2.8+ can take 90 minutes. It does a secure erase and that takes time.... You interrupted it which ain't good.
If you still can access the bootloader, reflash TWRP and try to format data. Let us know where that gets you.

Can you still boot into the bootloader or is TWRP the only thing you can boot into?
Click to expand...
Click to collapse
I can. No issues there.
If you still can access the bootloader, reflash TWRP and try to format data. Let us know where that gets you.
Click to expand...
Click to collapse
I was able to access the bootloader, reflash TWRP 2.8.1.0 again, and tried to format /data. It failed. So I rebooted to recovery once more and tried to format /data. That time it succeeded. I went through the whole process again and the above steps are 100% reproducible every time.
Output after data format:
Code:
Updating partition details...
Full SELinux support is present.
MTP Enabled.
Formatting Data using make_ext4fs function.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
and the prompt for "Back"

dnaod said:
I can. No issues there.
I was able to access the bootloader, reflash TWRP 2.8.1.0 again, and tried to format /data. It failed. So I rebooted to recovery once more and tried to format /data. That time it succeeded. I went through the whole process again and the above steps are 100% reproducible every time.
Output after data format:
Code:
Updating partition details...
Full SELinux support is present.
MTP Enabled.
Formatting Data using make_ext4fs function.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
and the prompt for "Back"
Click to expand...
Click to collapse
Hmmm - no idea what that could be, but in recovery you should have adb access.
In an adb shell try this to format the data partition:
Code:
[FONT=Arial]make_ext4fs /dev/block/mmcblk0p8
[/FONT]

berndblb said:
Hmmm - no idea what that could be, but in recovery you should have adb access.
In an adb shell try this to format the data partition:
Code:
[FONT=Arial]make_ext4fs /dev/block/mmcblk0p8
[/FONT]
Click to expand...
Click to collapse
I'm gobsmacked, confused, and grateful. After that command, this is now my partitions... Someone will one day have to explain to me how manually formatting the one partition recreated all of the other ones. My only guess is that the adb shell format is different from the TWRP format and somehow repaired the partition table?
Code:
179 0 31039488 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 28924416 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
I'm going to put on Cromi-KK to verify that everything works as planned and then do some overdue reading on backing up using the NvFlash tool. If it all works out, I'll update this thread.
Thanks,
D

dnaod said:
I'm gobsmacked, confused, and grateful. After that command, this is now my partitions... Someone will one day have to explain to me how manually formatting the one partition recreated all of the other ones. My only guess is that the adb shell format is different from the TWRP format and somehow repaired the partition table?
Click to expand...
Click to collapse
LOL - my best guess is: They were there the whole time! TWRP just couldn't mount them :cyclops:
Glad to see you up and running.
BTW, it doesn't hurt to hit the Thanks button on posts that do....

[Solved] Potentially bricked my tf700? Missing partitions
Looks like everything is up and running great with f2fs on /data as well. Once again thanks and the Thanks buttons have been properly pressed
BTW...
berndblb said:
BTW: You don't convert partitionS to f2fs. Only data gets converted to f2fs if you want to run that.
Click to expand...
Click to collapse
This one little line was very helpful. I've been flashing ROMs from the HTC Universal days (yeah... I didn't actually create an XDA account until a few years ago though). I've read and reread the f2fs documents and posts and never quite felt comfortable that there's a good step-by-step overview on exactly how to do it.
D

dnaod said:
Looks like everything is up and running great with f2fs on /data as well. Once again thanks and the Thanks buttons have been properly pressed
BTW...
This one little line was very helpful. I've been flashing ROMs from the HTC Universal days (yeah... I didn't actually create an XDA account until a few years ago though). I've read and reread the f2fs documents and posts and never quite felt comfortable that there's a good step-by-step overview on exactly how to do it.
D
Click to expand...
Click to collapse
Thanks for the buttons
If you think about it, it makes sense: f2fs improves the way data is written to flash memory and also the "garbage collection" process or how blocks on the emmc are reclaimed when no longer in use. Or that is my very rudimentary understanding of it.....
So it's all about improving write speeds to flash memory. /data is the only partition (in normal use) that gets constantly written to.
/system is normally read-only, so f2fs on /system would not improve performance at all. It's pointless.
The easiest way to change data to f2fs is in TWRP 2.8.x. That option can be found under the Wipe > Format menu.
The latest version(s) of Gparted also support it if you want to format the external /data on your microSD for a data2sd/rom2sd installation.
There's not much to write for a step-by-step:
Backup all your data on /data (= /sdcard)
Format /data to f2fs in TWRP (internal SD) or Gparted (external SD)
Reflash your rom
Restore your data
Edit: Yes, there's a way to use TWRP to format an external microSD /data partition - but that is another story :cyclops:

Format /data to f2fs in TWRP (internal SD) or Gparted (external SD)
Click to expand...
Click to collapse
This is the golden line. Once I found that option in TWRP 2.8.x, it all came together.

[Q] Partition destroyed after power loss

Hi everyone,
today i tried to update my CM11 to the newest CM12 Version. I booted into TWRP recovery and made a full Wipe. While doing this, my device had something like power loss, so the wipe could not finish.
Now the device doesn't boot anyway, after Power on it's booting into fastboot mode. The recovery isn't able to start. It is possible to use ADB and Fastboot. Using "fastboot boot /....../recovery.img it is possible to boot an recovery. The TWRP Recovery displays:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/misc'
E:Updating partition details
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/sytem'
...done
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup
E:Unable to mount '/cache'
Full SELinux support is present
E:Unable to mount '/cache'
E:Unable to set emmc bootloader message.
E:Unable to mount /'cache'
E:Unable to mount /sdcard/TWRP/.twrps when trying to read settings file.
MTP Enabled​
The "repair file system" option in TRWP Recovery doesnt work.
After several hours reading threads about similar problems i don't know what to do.
How can i repair the file system tables to reinstall the CM12 or any other ROM?
Hopefully
DragonGuard

I think, i have an idea.
What about to rewrite the complete partitions on my Sensation using adb shell and then rewrite with the partitions? Could that work?
I read an article with an similar problem here: cyanogenmod.org
The problem was that I managed to screw up the partitions on my internal storage card, so basically nothing would work properly. I could still get into recovery, though. That's key.
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Once all that's done, your recovery program should be able to mount both the /data and /cache partitions. If that's true, you're pretty much done! One thing I found was that I couldn't directly install a new OS (I tried both Cyanogen and Ultimate). In both cases, it would look for stuff in the davik-cache that it couldn't find, so something wasn't installing correctly I think. So, if that happens, flash back to the stock PB31IMG.zip (put it in the root of your /sdcard/ and let hboot install it), and then root your phone anew. That's what I ended up doing.
Again, huge credit for this goes to -Steveo- and ciwrl for helping me figure out which partitions were the right ones (and for supplying parted, which I hadn't been able to find anywhere). If something doesn't end up working, just drop me a pm and we'll see what we can do.
Click to expand...
Click to collapse
Today i would need parted for ext4 partitions and i need to know where on the internal storage i have to write which partition. Is this a possible way to repair the partitions?
Hopefully

Bump

I'm having the same problem, my recovery log shows exactly the same. Have you found a solution yet?

Hi,
i am sorry, but i haven't found any solution yet. I am looking for an HTC Sensation to pull the emmc Data system Files and rewrite it on my broken HTC Sensation. I need the /dev/block/mmcblk0 etc. files to try. In my /dev/block/ folder are only "loop" files located, i think they are part of my problem.
Greetz

[Completed] SOFT bricked lenovo s860 with twrp help needed/unable to mount partitions/

lenovo s860 2gb version with twrp 2.7.1.0
I cannot mount partitions/in recovery it says:
unable to mount data
unable to mount data
unable to recreate /data/media folder
you may need to reboot recovery to be able to use /data gain
updating partition details...
E:unable to mount /data
E:unable to mount /system
E:unable to mount /preload
E:unable to mount internal storage
...This happened after i transfered files from pc and hot unplug from PC...file system is broken i thing but i don't know what to do now...
How to fix it?
What i have:twrp backup from week ago.I need guidance how to fix file system and apply my backup !

XDA Visitor said:
lenovo s860 2gb version with twrp 2.7.1.0
I cannot mount partitions/in recovery it says:
unable to mount data
unable to mount data
unable to recreate /data/media folder
you may need to reboot recovery to be able to use /data gain
updating partition details...
E:unable to mount /data
E:unable to mount /system
E:unable to mount /preload
E:unable to mount internal storage
...This happened after i transfered files from pc and hot unplug from PC...file system is broken i thing but i don't know what to do now...
How to fix it?
What i have:twrp backup from week ago.I need guidance how to fix file system and apply my backup !
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
First, please create an account, then you may ask your question here:
http://forum.xda-developers.com/android/help
Good luck!

Nexus 5 turns on but cannot access anything

I have a Nexus 5 rooted and running Catacalysm 5.1.1 Lollipop (Sep 27, 2015 Stable final release)
Yesterday while I was on my phone all of a sudden it froze for a couple of seconds and then restarted.
When it booted it says "To start Android, Enter your Password"
I can type in literally any password and it will go to the next screen and say
"Decryption Unsuccessful"
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your google account.
Click to expand...
Click to collapse
Then the only thing I can select is "reset phone."
The thing is I never encrypted my phone. I don’t want to do a factory reset as I have some things in my phone that I need
When I go into recovery this is what I get:
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount ‘/data’
E:Unable to recreate /data/media folder
Updating partition details…
E:Unable to mount ‘/data’
…done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount ‘/data’
MTP enabled
E:Unable to mount ‘/data’
Click to expand...
Click to collapse
Also the internal storage shows 0 MB.
When I go into backup these are the sizes that are shown:
System (882MB)
Data (0MB)
Cache (12MB)
Boot (22MB)
EFS (6MB)
Click to expand...
Click to collapse
I’m using TWRP
I was wondering if anyone ran into this issue or knew anything about what is going on in my phone.
Is my phone dead? Can I get it to work again? Is there any way I can access the internal storage and retrieve my files?
Any help would be appreciated. Thank you