this is weird , i try to copy some files from my internal SDcard to the external Sdcard by using Root Explorer
it keep says "the paste operation failed. it may be that there was not enough free space on the target file system "
but serious , i have 20 GB left in my external Sdcard ... and the file was only 8 MB ..
weird thing is that it happens sometime and sometimes it doesn't happen.
sometimes on /data partition , sometimes /system , like i try to replace boot animation or such .
i tried few ROMs all happens on me as well.
i tried to creat a empty text files .txt , and write something in it and it can be saved. so it just get me confused what's going on :crying:
Using any scripts?
Permissions correct?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
you should remove some apps from system folder because there is a limited space for apps in this folder
you can check it :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alfares43 said:
you should remove some apps from system folder because there is a limited space for apps in this folder
Click to expand...
Click to collapse
...and /data? /extSdCard?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
...and /data? /extSdCard?
Click to expand...
Click to collapse
I faced the same problem before in system folder
and solved it by removing some apps
i have no idea what to do for the other folders .. :silly:
Do you get the same issue if you try doing it with terminal emulator or adb? I wonder if it is some setting on root explorer that maybe limits file size or something. If you use another file explorer program do you have the same problem?
rootSU said:
Using any scripts?
Permissions correct?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Sdcard doesn't have permissions ...
alfares43 said:
you should remove some apps from system folder because there is a limited space for apps in this folder
you can check it :
Click to expand...
Click to collapse
1.5 GB left in system and 5 GB in data.. so no really the case ...
wangdaning said:
Do you get the same issue if you try doing it with terminal emulator or adb? I wonder if it is some setting on root explorer that maybe limits file size or something. If you use another file explorer program do you have the same problem?
Click to expand...
Click to collapse
I didn't try ADB, but when I failed to move around the internal and external sdcard, I can manually copy it into PC and then paste it back in...
In other words, I can access (delete, paste or such) from my PC but can't do it with Root Explorer
Sent from my GT-I9300 using xda premium
qtwrk said:
Sdcard doesn't have permissions ...
Click to expand...
Click to collapse
Of course it does!, if it didn't have permissions, you wouldn't be able to use it! It is mounted with permissions. Linux basic knowledge EVERYTHING has permissions.
Hence my question "Using any scripts?"!
Since you skipped that question, I am going to assume no.
But FYI, no space errors are 1 of 2 things.
1) No space
2) Wrong permissions
So something for you to think about....
You should check output of terminal command "mount" next time you have this error
rootSU said:
Of course it does!, if it didn't have permissions, you wouldn't be able to use it! It is mounted with permissions. Linux basic knowledge EVERYTHING has permissions.
Hence my question "Using any scripts?"!
Since you skipped that question, I am going to assume no.
But FYI, no space errors are 1 of 2 things.
1) No space
2) Wrong permissions
So something for you to think about....
You should check output of terminal command "mount" next time you have this error
Click to expand...
Click to collapse
This was why I say no permission...
I more think about media scan? But seems highly unlikely.
If it is not mounted or permission error ... then why I was able to create empty text files and write save it? this operation does write on it, doesn't it?
Sent from my GT-I9300 using xda premium
Try other root explorers then....
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Of course it does!, if it didn't have permissions, you wouldn't be able to use it! It is mounted with permissions. Linux basic knowledge EVERYTHING has permissions.
Hence my question "Using any scripts?"!
Since you skipped that question, I am going to assume no.
But FYI, no space errors are 1 of 2 things.
1) No space
2) Wrong permissions
So something for you to think about....
You should check output of terminal command "mount" next time you have this error
Click to expand...
Click to collapse
Code:
[email protected]:/ $ mount
rootfs on / type rootfs (ro,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,nodiratime)
proc on /proc type proc (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
sysfs on /sys type sysfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=600)
none on /dev/cpuctl type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpu)
tmpfs on /storage type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
none on /acct type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/fuse type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=775,gid=1000)
/dev/block/mmcblk0p3 on /efs type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p9 on /system type ext4 (ro,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,commit=100,barrier=1,data=ordered,noauto_da_alloc,discard)
tmpfs on /system/lib/modules type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,barrier=1,journal_async_commit,data=writeback,noauto_da_alloc,discard)
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /mnt/ntfs type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=777,gid=1000)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
[email protected]:/ $
I can't read this... m a little help please?
Sent from my GT-I9300 using xda premium
qtwrk said:
Code:
[email protected]:/ $ mount
rootfs on / type rootfs (ro,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,nodiratime)
proc on /proc type proc (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
sysfs on /sys type sysfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=600)
none on /dev/cpuctl type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpu)
tmpfs on /storage type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
none on /acct type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/fuse type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=775,gid=1000)
/dev/block/mmcblk0p3 on /efs type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p9 on /system type ext4 (ro,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,commit=100,barrier=1,data=ordered,noauto_da_alloc,discard)
tmpfs on /system/lib/modules type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,barrier=1,journal_async_commit,data=writeback,noauto_da_alloc,discard)
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /mnt/ntfs type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=777,gid=1000)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
[email protected]:/ $
I can't read this... m a little help please?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
This is the line you want:
Code:
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Which is normal for an AOSP ROM.
A touchwiz ROM would look like....
Code:
vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Anyway, you ruled something out there (if you ran this when you got the error)
rootSU said:
This is the line you want:
Code:
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Which is normal for an AOSP ROM.
A touchwiz ROM would look like....
Code:
vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Anyway, you ruled something out there (if you ran this when you got the error)
Click to expand...
Click to collapse
Yeah... last time it shows error at beginning, and after I reboot it once and now it says error after the paste is completed, with refresh I can see the file in place and md5 checks identical.
That was the line when I got error...
I'm gonna try other files manager...
Sent from my GT-I9300 using xda premium
qtwrk said:
Yeah... last time it shows error at beginning, and after I reboot it once and now it says error after the paste is completed, with refresh I can see the file in place and md5 checks identical.
That was the line when I got error...
I'm gonna try other files manager...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
es file explorer> menu> root explorer on> grant.... then again menu> click root explorer> mount r/w and enable write permissions and you can copy/cut/paste data anywhere. this is what i always do.
:good:
I have a Huawei T-Mobile Mytouch 4G Q slider (U8730) and i have successfully rooted it. I havent flashed any ROM's or anything like that and i have browsed through alot of the forums and Google and havent found what i need to know. I need to know how to use the "mount a filesytem read-write" command, i know the syntax:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
i just dont know what information to input in the command.
i know i can use:
# mount
and that will give me a lot of info but im not too sure what im looking for.
if theres another thread about this, i apologize, im new to this forum and not 100% how to navigate.
heres what it says when i do # mount
im not sure what im looking for here
please help O:
mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p14 /HWUserData vfat rw,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /.cust_backup vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/loop0 /cust ext3 ro,relatime,barrier=0,data=writeback 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 ro,relatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered 0 0
hwvefs /data/huawei_hwvefs fuse.hwvefs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,er
rors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.ultimateguitar.tabs-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.ovelin.guitartuna-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/net.andchat-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.ddm.iptools-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
Which specific partition do you want to mount read write?
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
Which specific partition do you want to mount read write?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
oh man!! im not sure what that means! just need to mount rw for apps
orionsfl said:
oh man!! im not sure what that means! just need to mount rw for apps
Click to expand...
Click to collapse
Partition refers to a specific file system. For example the /boot partition contains the kernel and ramdisk for booting up your device (Note: /boot partition and bootloader partition are not the same thing), the /cache partition contains cache files, the /system partitions contains your system apps and other system folder such as bin and xbin and other. What apps are you trying to use that you need to mount rw for? But if you wanted to modify your /system partition for example you would run the following command from ADB shell or terminal emulator to mount it rw (Read/write):
Code:
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p12 /system
Let me know if you still have questions about this.
Try this:
https://play.google.com/store/apps/details?id=com.beansoft.mount_system
Hit thanks if I helped.
Sent from my Nexus 4 using Tapatalk 2
Hi,
No matter what I do, I can't remount "/system" and "/" to RW. :crying:
Does anyone know how to resolve this issue?
I am running on KK 4.4.2 version 14.3.A.0.757.
My Current File System Status
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /tmp tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apps_log /mnt/idd ext4 rw,seclabel,nosuid,nodev,noexec,noatime,discard,nobarrier,data=ordered 0 0
tmpfs /storage/remote tmpfs rw,seclabel,relatime,size=1024k,nr_inodes=256,mode=750,gid=1028 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,seclabel,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
[email protected]:/ #
You obviously do not have the permission to do that, so the question is, are you rooted, and if so root again and be sure to have the latest SuperSU installed with updated binaries.
Sent from my Z Ultra
LordManhattan said:
You obviously do not have the permission to do that, so the question is, are you rooted, and if so root again and be sure to have the latest SuperSU installed with updated binaries.
Sent from my Z Ultra
Click to expand...
Click to collapse
Yes, I am able to gain root access but unable to boot into recovery
Sent from my C6833 using XDA Premium 4 mobile app
[email protected] said:
Yes, I am able to gain root access but unable to boot into recovery
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What kernel are you on?
How did you get root?
Bootloader unlocked?
blueether said:
What kernel are you on?
How did you get root?
Bootloader unlocked?
Click to expand...
Click to collapse
My kernel version is 3.40-perf [email protected] #1 and bootloader is unlocked.
I gained root by downgrading my firmware to .532 version and install rooting using a program called Root_with_Restore_by_Bin4ry_v33. After rooting is successful, install dualrecovery and upgrade my firmware to .757 version by flashing a specific zip file via recovery followed by flash FTF with Flashtool.
Am I doing it correctly? Is there a better way to do it?
[email protected] said:
My kernel version is 3.40-perf [email protected] #1 and bootloader is unlocked.
I gained root by downgrading my firmware to .532 version and install rooting using a program called Root_with_Restore_by_Bin4ry_v33. After rooting is successful, install dualrecovery and upgrade my firmware to .757 version by flashing a specific zip file via recovery followed by flash FTF with Flashtool.
Am I doing it correctly? Is there a better way to do it?
Click to expand...
Click to collapse
I would try to reflash supersu and see if that fixes it
I'm not sure. I'm having the same issue, sort of. I can mount /system to read write easily but can't mount back to read only. Getting "resource busy" message. Running a 4.4.2 LG G2 ROM. Could it have anything to do with how /system is formatted within TWRP recovery? Idk.. Luckily not being able to mount as read only isn't exactly an issue but more of a nuisance.
Edit:: Found a solution minutes after posting.
Code:
su
mount -o remount,rw /system # works fine
mount -o remount,ro /system # resource busy error
mount -o remount ro /system # works fine without comma
With this knowledge I can go through and fix a few scripts that have the comma between remount and ro. Not sure why this is as it's always worked fine ever since my OG DROID.
Any updates ??
EvilMember said:
Any updates ??
Click to expand...
Click to collapse
Strange I'm using this rom: http://forum.xda-developers.com/xpe...14-4-0-118-t2859660/post56113642#post56113642
And I can't mount system to RW, had same issue before on stock but Super SU reflash fixed it...now no way to moint system to RW
MidnightHarvester said:
I'm not sure. I'm having the same issue, sort of. I can mount /system to read write easily but can't mount back to read only. Getting "resource busy" message. Running a 4.4.2 LG G2 ROM. Could it have anything to do with how /system is formatted within TWRP recovery? Idk.. Luckily not being able to mount as read only isn't exactly an issue but more of a nuisance.
Edit:: Found a solution minutes after posting.
Code:
su
mount -o remount,rw /system # works fine
mount -o remount,ro /system # resource busy error
mount -o remount ro /system # works fine without comma
With this knowledge I can go through and fix a few scripts that have the comma between remount and ro. Not sure why this is as it's always worked fine ever since my OG DROID.
Click to expand...
Click to collapse
FAIL:
this doing nothing.
mount -o remount ro /system
[email protected]:/ # mount | grep /system
mount | grep /system
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,noatime,nodiratime,noauto_da_alloc,data=ordered)
dmesg
<6>EXT4-fs (mmcblk0p30): re-mounted. Opts: (null)
kernel ignoring your command. problem is with some service open file for writing in /system and not letting go.
find the service! kill it, mount as RO.
I tried to downgrade to 148 to get the cm install to work. Lost access to internal storage. I was using twrp 2.8.7.0 or 2.8.0, flashed the rooted stock ROM from another post here and lost access. I've tried the su command "restorecon -v -R /data/media" and now I can see the internal storage from the settings menu but not change the location from there.
Here is my terminal command "mount" result
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/log /log ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/vold/179:65 /storage/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
[email protected]:/ $
What do I do now? I want to install the cm preview
Thanks for your time
CM12 and all other ROMs require you update your phone to Lollipop, B3xx.
xordos said:
CM12 and all other ROMs require you update your phone to Lollipop, B3xx.
Click to expand...
Click to collapse
And I'm ready to do that but I'm stuck in 4.3 with no access to the internal storage when I try to flash a new ROM. I'm thinking about going back to the recovery and get the ota update again and trying the cm install from there. Opinions?
Update* I got back to stock 309 with no ability to ota upgrade or install cm via twrp. Twrp still reports "unable to mount internal SD" but I have been able to browse, read, and write to it through the preloaded file explorer, after the "returncon -v -R data/media/" command through terminal in twrp 2.8.7.0.
once you are in 309, follow the cm install thread, and no need to worry about internal storage, at least for now.
copy rom and gapp to sdcard, which is called external storage, and flash it in twrp.
Getting stuck still at install in twrp. Cannot post a link to a screenshot so I'm gonna try to type it out. "this package supports bootloaders ... This device has boot loader unknown." And "e: error executing binary inside of zip..." I've tried all three of the custom ROM zips, cm, carbon, and PAC ROM with the same results.
What now?
notshure said:
Getting stuck still at install in twrp. Cannot post a link to a screenshot so I'm gonna try to type it out. "this package supports bootloaders ... This device has boot loader unknown." And "e: error executing binary inside of zip..." I've tried all three of the custom ROM zips, cm, carbon, and PAC ROM with the same results.
What now?
Click to expand...
Click to collapse
Unmount in lollipop and format it. Or re run b309.
Also that unknown bootloader error, one reason is you didn't flash the twrp recovery from that CM preview thread 1st post. You have to flash that recovery image even you already have working twrp.
xordos said:
Also that unknown bootloader error, one reason is you didn't flash the twrp recovery from that CM preview thread 1st post. You have to flash that recovery image even you already have working twrp.
Click to expand...
Click to collapse
then there was cyanogen and much rejoicing. Thanks :good: