Unable to mount /data

Hi All, i have been trying to flash rom but it keeps restarting back to recovery. I have flashed stock recovery, did wipe and reinstalled TWRP and still the same. I was earlier getting message unable to mount /data. I have tried wiping only data and also tried mounting it via USB connected and it works but unable to flash any rom. Please help.
Edit: I have tried TWRP 3.0.2, 3.0.0 and 2.8.0.1

unable to mount system

im not able to mount system, data etc... my phone was on charging as soon as i unplug i got lots of fc's after that phone reboot and got stuck at bootanimation, after i took out the battery and tried to switch on the phone it stuck at yu logo. in recovery (twrp) cant flash or wipe anything. i was on cm13 24th build

Attached Thumbnails

 

Mount NFS share

How can I mount a NFS share permanently on my 1st gen FTV? I'm on the latest pre-rooted ROM. Busybox and RootExplorer is installed.

mount system rw on remix os marshmellow

Ho guys there are a way to mount system rw on remix os updated to marshmellow?
I have root permissions and I try with various app but I can't mount rw...
Thx for help.

cant mount internal sd after rebooting while downloading.

i has just doned root and was downloading all my apps from the play store, then decided to update adblock and rebooted my phone, now its a hell laggy, and cant get to download mode nor recovery, and it cant mount internal sd card. i try the combo after 10 seconds off but it boot straight to the system, its like if the home botton was not detected. i need some help.....

TWRP: failed to mount \data, \system, \cache

Hey all,

Fairly new to custom roms, so hopefully I'm asking a legit question. My phone is a D855, currently on DU 10.3. I wanted to upgrade to the 10.4, doing a clean install, but I seemingly cannot wipe anything. TWRP (using 3.0.2) will give an error message: failed to mount \[...]. Interestingly, flashify labels the recovery as Stock, so maybe there is a connection.
I have been doing some googling/"xda-ing" and as it seems, going back to stock can help. BUT, for one, I hope that there's an easier way, and also I would like to know what's causing this issue. Maybe it can be avoided somehow? So maybe someone can help me with that? :)

Cheers.

how to fix unable to mount system

Please help me I want to know how to fix 'unable to mount /system,/data/catche I want to install custom ROM but I was fear of this please tell how to overcome that issue in lenovoa6000plus and I need best battery backup and ui without lags.. Please give me answer sory for my bad english

Cannot mount /data partition

today i accidentally flashed cf auto root package of sm-g920f on galaxy s7 sm-g930f and the device was stuck loop in galaxy s7 logo with senforcing red word so i reflashed stock recovery and cache.img and rebooted this time it keeps restarting on galaxy s7 logo so i flashed twrp and in twrp it said unable to mount /data.
how can i repari data partition ?

[Solved] Link2sd "mount warning" fix for all samsungs and android 5.1.1+ stock ROM

Hi.
I suppose every one samsung has the problem "mount warning" generated by Link2sd after installing it for manage second partition on external sd card. You do not have to generate scripts and restart system by Link2sd's own menu option. This solution let to mount second partition auto in boot option.
Thanks to Warre101 for the idea.

If you want to use Link2sd you have to have rooted device. I did it on samsung galaxy tab 4 with stock ROM 5.1.1..

The best application for make all operation is Total Commander (TC).

1. Create subdirectory su.d in directory /system where you store your script in left window of TC.
/system/su.d
2. Set 700 (RWX) permision for new created directory in Propertis TC's menu option .
3. In the right window of TC open directory :
/data/data/com.buak.Link2SD/files/
4. Copy the file init-link2sd.sh from right to left window.
5. Change name of this file in left window (/system/su.d directory) to 11link2sd
6. Copy renamed file back to right window and open it here in Totalcmd-Editor (installed with TC)
7. Remove not needed text , the result should be:

Code:

---

#!/system/bin/sh
sleep 4
mount -t ext2 -o rw /dev/block/mmcblk1p2 /data/sdext2

---

8. Write changes and leave editor.
9. Copy changed file back to /system/su.d (left window). Overwrite existing file.
10. Set 700 (RWX) permision for this file . /system/su.d/11link2sd

Each boot of your device new created script will mount partition needed be Link2sd for manage second partition on your external sd card.

mount folder in android 6

Hi all.
Can you help me. I need mount folder in internal_sd to external_sd how can see in all app. I tried use app Folder_mount, but this app don't work in my rom.
I have:
Android 6.0.1 (Lenovo K3 Note)
SuperSU Pro v2.76 (mount namespace separation is disabled)
BusyBox v1.21.1-jb static
mount symlinked to toolbox, umount symlinked to toybox

storage/E690-B8B6 - external_sd
/storage/emulated/0 - internal_sd

I am tried it for test

Code:

---

shell@aio_otfp_m:/ $ su
su
root@aio_otfp_m:/ # id
id
uid=0(root) gid=0(root) groups=0(root) context=u:r:init:s0
root@aio_otfp_m:/ # su -m
su -m
root@aio_otfp_m:/ # id
id
uid=0(root) gid=0(root) groups=0(root) context=u:r:init:s0
root@aio_otfp_m:/ # getenforce
getenforce
Permissive
root@aio_otfp_m:/ # grep -A5 debuggerd /init.rc
grep -A5 debuggerd /init.rc
service debuggerd /system/bin/debuggerd
    class main

service debuggerd64 /system/bin/debuggerd64
    class main

service ril-daemon /system/bin/rild
    class main
    socket rild stream 660 root radio
root@aio_otfp_m:/ # mkdir /storage/emulated/0/a
mkdir /storage/emulated/0/a
root@aio_otfp_m:/ # mkdir /storage/E690-B8B6/b
mkdir /storage/E690-B8B6/b
root@aio_otfp_m:/ # echo >/storage/emulated/0/a/1
echo >/storage/emulated/0/a/1
root@aio_otfp_m:/ # ls /storage/emulated/0/a
ls /storage/emulated/0/a
1
root@aio_otfp_m:/ # ls /storage/E690-B8B6/b
ls /storage/E690-B8B6/b
root@aio_otfp_m:/ # busybox mount -o bind /storage/emulated/0/a /storage/E690-B8B6/b
ox mount -o bind /storage/emulated/0/a /storage/E690-B8B6/b                  <
root@aio_otfp_m:/ # grep ' /storage/E690-B8B6/b ' /proc/mounts
grep ' /storage/E690-B8B6/b ' /proc/mounts
/data/media /storage/E690-B8B6/b sdcardfs rw,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,upper=0:1015:0660:0771,derive=multi 0 0
root@aio_otfp_m:/ # ls -ld /storage/E690-B8B6/b
ls -ld /storage/E690-B8B6/b
drwxrwx--x root    sdcard_rw          2016-07-04 18:30 b
root@aio_otfp_m:/ # ls -l /storage/E690-B8B6/b
ls -l /storage/E690-B8B6/b
-rw-rw---- root    sdcard_rw        1 2016-07-04 18:30 1
root@aio_otfp_m:/ # busybox umount /storage/E690-B8B6/b
busybox umount /storage/E690-B8B6/b
root@aio_otfp_m:/ #

---

mounting works, but only in one namespace. How can I need to mount for all app can see the mounting?
Thank you and sorry for my English.

TWRP unable to mount system and "Patching system image unconditionally" [XT1032]

Hello,
no matter which custom ROM I'm trying to install, the installation always gets stuck "Patching system image unconditionally". Waited for an hour and stopped it now. I have a maybe two weeks old official version of TWRP and made a factory reset before I tried to install. I already tried PAC-ROM and CM13, same error. When searching for the error cause, I saw, that in the ""Mount" menu, "System" is unchecked. Only "Cache" and "Data" are checked. But I can't check system, my phone just vibrates, but there is no checkmark after that.
Thanks for your help!
Aendroit

[Q] Failed to mount '/sdcard'. Unusual problem.

Hello good sirs. I have this big big trouble.
Android doesn't load and i keep getting same errors on everything that i tying to do inside recovery.

Yesterday i was updating my ROM. I installed newest CM, latest Torched kernel then i decided to tweak system little bit, i done everything from Lollipop improvements for HOXL after step with flashing new build.prop or formatting to F2FS (i done them without turning on system) i found that OS stuck at loading screen. After that i reboot to recovery and tried to perform standard wipe but it shoved me this errors:

Quote:

Updating partition details..... Failed to mount '/sdcard' (Invalid argument) ...done Unable to mount storage

After that i read some posts on the internet and tried to reinstall ROM, it shoved same old errors with some more.

Quote:

Installing zip file '/sdcard/ROM.zip' Checking for MD5 file... Skipping MD5 check: no MD5 file found I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts I:Legacy property environment initialized. minzip: Extracted 3 file(s) detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system about to run program [/tmp/install/bin/backuptool.sh] with 2 args run_program: child exited with status 127 detected filesystem exfat for /dev/block/platform/msm_sdcc.1/by-name/userdata mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args performing update blockimg version is 3 maximum stash entries 0 unmount of /data failed; no such volume Patching system image unconditionally... creating stash /cache/recovery/5a79362318d00cf4c316e86435b3ed38dd35082d/ 259854336 bytes free on /cache (0 needed) erasing 425983 blocks writing 113728 blocks of new data wrote 113728 blocks; expected 113728 max alloc needed was 0 deleting stash 5a79362318d00cf4c316e86435b3ed38dd35082d detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system about to run program [/tmp/install/bin/backuptool.sh] with 2 args /tmp/install/bin/backuptool.sh: cd: line 112: can't cd to /tmp/addon.d/ script succeeded: result was [0.200000]I:Updater process ended with RC=0 I:Legacy property environment disabled. Updating partition details... I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk0p35 /data __bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0! __bionic_open_tzdata: couldn't find any tzdata when looking for posixrules! __bionic_open_tzdata: couldn't find any tzdata when looking for GMT! __bionic_open_tzdata: couldn't find any tzdata when looking for posixrules! I:Can't probe device /dev/block/mmcblk0p36 Failed to mount '/sdcard' (Invalid argument) I:Actual block device: '/dev/block/mmcblk0p36', current file system: 'vfat' I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'vfat' ...done I:Can't probe device /dev/block/mmcblk0p36 I:Unable to mount '/sdcard' I:Actual block device: '/dev/block/mmcblk0p36', current file system: 'vfat' Unable to mount storage I:Set page: 'flash_done' I:operation_end - status=0 I:Set page: 'clear_vars' I:Set page: 'install' I:Set page: 'main' I:Set page: 'clear_vars' I:Set page: 'main2' I:Set page: 'advanced' I:Set page: 'confirm_action' I:Set page: 'action_page'

I tried to undo all that staff with scripts provided in guide thread, TWRP told me that everything Successful but at the end still wrote same error lines.

I have unlocked bootloader, S-OFF, latest TWRP recovery, firmware 5.18.502.1, HBOOT 2.18.
I can load into fastboot and recovery. I can access phone with adb, i can push and pull files with adb.
I can see connected phone in Windows explorer but i can't see files there is just an empty folder.

I want to reinstall recovery but i kinda scared that it will brick my phone even more.

Full log that i managed too pull from device (a lot of text) - http://pastebin.com/EL70i02L

HALP! failed to mount /data (invalid argument)

I have been trying to reinstall the stock ROM for my BLU Energy X Plus, after trying a few custom ROMs I found.
After trying SP Flash Tools (doesn't find my phone/preloader even with the VCOM drivers installed), I decided to risk playing with fastboot. Boy, am I sorry! I managed to get TWRP back as my recovery, but now /data will not mount. When I try to reformat, I get an error saying it needs a partition size. I think I really f'ed up my partition table somehow :(

pls can anyone help?

Shield won't connect to network storage, won't auto mount or manually connect

I have an Archer C7 wireless router with a USB hard drive connected to it that contains all my media. I have two linux boxes and two Windows machines that can see the share (\192.168.xxx.xxx\volume1), but the nVidia Shield TV won't see it automatically OR let me enter the address manually. KODI and SPMC both surf to and find the share and media folders therein without problem, but the Shield will not natively see it.

When I try to enter it manually, it says "CONNECTION FAILED - null is not available". I don't know what it says by null except that it can't tell anything is there at all.

The only thing I can think of is that, in Linux, I have to use "sec=ntlm" to change the dedault security in the cifs/samba command in file /etc/fstab to get it to mount, but I can't set something like that in the Shield. Even if I remove authentication altogether, the Shield still doesn't recognize the share or even the 192.168.xxx.xxx address at all. They're on the same network. I should also mention that I can connect to the share from my Android phone, so I don't think it's something with the OS. Maybe...
At this point, I'm at a total loss to get this share connected to the SHIELD.

Any ideas?

Need Help on Sph-720T! - Failed to mount /efs (Invalide argument)

When I flash stock roms using Odin, it works fine.
when I flash twrp and then go in to recovery mode, I hit clear cache davik, i get an error "Failed to mount /efs (Invalide argument)"

I never got that error before, that error appears when flashing custom roms too
Now when I load custom roms that worked before, they are getting stuck at the initial loading screen.

I search and searched the web, didnt find anything on my phones model but instructions on other phones to use ADB command line while the phones in recovery mode with system mounted
I tried everything I could find to put in the command prompt, 4+ hours of searching and I've come up bare.

If anyone could help me I would appreciate it, I just want to be able to flash custom roms with no issues.

Help :( TWRP Can't mount anything!?!?!?!?!

Today was not the best day. I wanted to try a rom out but it ended up needing 6.0 to install. I said whatever and tried to restore back to 5.1.1 (would not get past bootloader). It kinda worked... I got my my bootscreen but it stopped there. Now that I think of it, I may have needed to reflash the kernel? I couldn't perform a factory reset. It said it could not mount anything. It has been like this ever since. Anyways, I got locked out of my phone and used odin to flash 6.0 (I had a 5.1.1 file also but decided not to so I could try the ROM). I rooted it with odin and installed twrp. Same thing. Cant flash anything, backup, restore, etc. Everything else works (kinda I hate 6.0 but cant go back). I want to install xposed to get gravity box working. TL;DR I screwed up TWRP flashing a rom that needed 6.0, not 5.1.1 now I cant mount anything in TWRP. PLEASE HELP ME!!!

single din,1.8ghz,NFC,plays video music while navigating,can mount screen 3 different

https://www.carjoying.com/joying-new...ooth-wifi.html

just ordered it,has 3 position screen,fm sensitivity adjustable,299.00 no dvd,bought from link witch promises 5 year warranty,ebay said 2,will post a review when installed,going in a truck with 5000 watt orion amp,370 amp elite alt lots of cerwin vega,hope it beets my fancy pioneer double din,hope the CPU: PX3 1.8GHz Cortex A9 Quad can be rooted with custom rom?will pay any one near detroit mi to do it and root and install my galaxy note4?

Can't mount /data or /storage from TWRP on Surnia (Moto E).

This is causing problems because it means I can't back-up, wipe or - presumably - install a ROM. I read about changing the type of file-system but I don't think that's something I want to do before I have a back-up. Has anyone got any ideas?

The version of TWRP I'm using is twrp-3.0.2-0-surnia.img

ZTE v987 cannot mount /system etc. possible eMMC damage

Hello,
I got stuck and I need some help.
The phone is ZTE v987. There was bgcngm's ROM V4.0B0MOD inside.
I pulled-out-&-pushed-in the battery and after boot there was a prompt that my data needed to be erased. (I'm not excatly sure what it was). I freaked out. Turned off and boot into recovery mode (vol up + power). Performed factory reset and tried to restore backup. It didn't work. I got messages:

Quote:

Can't mount /system! Can't mount /data! Can't mount /cache!

So I tried to format all of the above. Then I tried to restore individually /system, /data, /cache. All the same.
When I enter the Recovery I get errors like here:

Quote:

E: Can't mount /cache/recovery/command E: Can't mount /cache/recovery/log E: Can't open /cache/recovery/log E: Can't mount /cache/recovery/last_log E: Can't open /cache/recovery/last_log

There are mentioned some apps like Heimdall but I couldn't find a version for my device and I'm not exactly sure what I should do.
What's more, I found info about eMMC damage and followed the link to check if my eMMC was good or bad.
I typed the command and the output was empty:

Quote:

adb shell ~ # dmesg | grep mmc0 dmesg | grep mmc0 ~ #

I read somewhere it's possible that I don't have grep installed (maybe because I wiped the data).
So I tried another command to list the eMMC-chip partition info:

Quote:

~ # fdisk -l /dev/block/mmcblk0 fdisk -l /dev/block/mmcblk0 Warning: ignoring extra data in partition table 5 Warning: ignoring extra data in partition table 5 Disk /dev/block/mmcblk0: 3853 MB, 3853516800 bytes 1 heads, 16 sectors/track, 470400 cylinders Units = cylinders of 16 * 512 = 8192 bytes Device Boot Start End Blocks Id System /dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended Partition 1 does not end on cylinder boundary /dev/block/mmcblk0p2 1665 2944 10240 83 Linux Partition 2 does not end on cylinder boundary /dev/block/mmcblk0p3 2945 4224 10240 83 Linux Partition 3 does not end on cylinder boundary /dev/block/mmcblk0p4 5825 6592 6144 83 Linux Partition 4 does not end on cylinder boundary /dev/block/mmcblk0p5 8385 91584 665600 83 Linux /dev/block/mmcblk0p6 238785 64 2145573887+ 83 Linux ~ #

I also tried to mount /system and /data in adb but it failed:

Quote:

~ # mount /system mount /system mount: mounting /emmc@android on /system failed: Invalid argument ~ # mount /data mount /data mount: mounting /emmc@usrdata on /data failed: Invalid argument

I've also downloaded the ROM and tried to install from SD.


I've saved the log and here are bottom lines:

Quote:

Updating kernel open emmc partition "boot" contents of partition "boot" didn't match EMMC:boot:4941824:a63fb5e2f91e9c21ae76325d15d98fd3 6c50c41b:4941824:a63fb5e2f91e9c21ae76325d15d98fd36 c50c41b file "EMMC:boot:4941824:a63fb5e2f91e9c21ae76325d15d98fd 36c50c41b:4941824:a63fb5e2f91e9c21ae76325d15d98fd3 6c50c41b" doesn't have any of expected sha1 sums; checking cache failed to stat "/cache/saved.file": No such file or directory failed to load cache file Flashing partition: BOOT script aborted (no error message) script aborted (no error message) Installer Error (Status 7)

Also I've got recovery.log but it's a long one and can paste here if it is needed.

I didn't try to flash trough SP Flash Tool anything because I didn't want to make things worse.
That's all the info I could gather. I don't know if it is helpful at all but I've run out of clues.
I'd be very grateful for any help.

PS. Right now I'm not able to charge the battery. For one second the red light blinks and then the screen with battery with red strip at the bottom appears and I don't believe it's charging.

amazon fire tv 4K - cannot mount an SSD

Hello
I try to connect a SSD (OCZ vertex 2 120G) via a self powered hub (Icy Box IB-120CL-U3), formatted in FAT32 to amazon fire tv 4K (fireOS 5.2.1.0), and he sees that something connect, but seems not accept the format for mounting "there was a problem mounting the inserted usb drive, please note that only FAT32 storage devices are supported"
It was a disk formatted in NTFS, that I convert to FAT32 using AOMEI free partition assistant.
I do just same with a USB key USB3 32G and it works fine

any idea whats the problem ?
thanks
mickey