Has anyone had any luck applying Substratum themes? I read a post 2 months ago from a user that said he was succesful but that's about it. I've tried various themes and none of them have worked. Do I have to delete Theme Editor, go back to the stock theme of EMIUI and then try substratum? I'm confused. I'm rooted, obviously.
I would think you need the substratum framework in place for it to work. In aosp roms they usually bake the framework in for it to work.
sent from my rotary phone
jr313 said:
I would think you need the substratum framework in place for it to work. In aosp roms they usually bake the framework in for it to work.
sent from my rotary phone
Click to expand...
Click to collapse
nope. it's running compatible to hwdesigns. I applied a sub theme ( see pictures attached )
on some FW it's quite tricky to mount the vendor partition rw. I mounted it manually via es file explorer, installed substratum, installed the theme and applied it. everything needs root of course
WieserZ1C said:
nope. it's running compatible to hwdesigns. I applied a sub theme ( see pictures attached )
on some FW it's quite tricky to mount the vendor partition rw. I mounted it manually via es file explorer, installed substratum, installed the theme and applied it. everything needs root of course
Click to expand...
Click to collapse
Hmmm. That didn't work for me. Looking inside SuperSU, it seems that substratum doesn't even ask for root permissions. All I have inside SuperSU is Rom Control and Viper. When I go into setting inside substratum, it says "rooted mode (certified)" but I can't apply any themes. I checked and everything in my root folder has drw permissions, including vendor. Any tips?
try delete App data, then uninstall, flash your choice of root ( as I guess SuperSU ) again, reboot, then reinstall ... it has to ask for root privilege, otherwise it won't perform. The last chance I could advise if it doesn't work after previous steps is to delete SuperSU app data too.
WieserZ1C said:
nope. it's running compatible to hwdesigns. I applied a sub theme ( see pictures attached )
on some FW it's quite tricky to mount the vendor partition rw. I mounted it manually via es file explorer, installed substratum, installed the theme and applied it. everything needs root of course
Click to expand...
Click to collapse
Please help me too. my overlay folder is also read only and I don't have es file explorer option because it doesn't work (with root) on my device after marshmallow update.
CheifX said:
Please help me too. my overlay folder is also read only and I don't have es file explorer option because it doesn't work (with root) on my device after marshmallow update.
Click to expand...
Click to collapse
Couldn't you just mount it from a terminal?
Code:
su
mount -o rw,remount /vendor
I am super noob
ante0 said:
Couldn't you just mount it from a terminal?
Code:
su
mount -o rw,remount /vendor
Click to expand...
Click to collapse
Please click on image
CheifX said:
Please click on image
Click to expand...
Click to collapse
What happens if you type
mount -o remount,rw /vendor
?
You might have have to type just "mount" to check which device /vendor is at and what fs it uses
Example: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /vendor
Yaffs2=fs, /dev/block/mtdblock3=device in this example. Type mount to find out where vendor is located and replace device and fs with the ones you find. I take it you're not using a Mate 9?
I also want to apply this
ante0 said:
What happens if you type
mount -o remount,rw /vendor
?
You might have have to type just "mount" to check which device /vendor is at and what fs it uses
Example: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /vendor
Yaffs2=fs, /dev/block/mtdblock3=device in this example. Type mount to find out where vendor is located and replace device and fs with the ones you find. I take it you're not using a Mate 9?
Click to expand...
Click to collapse
unfortunately, I can't found vendor in these commands.
[email protected]_4G:/ # mount
mount
rootfs / rootfs ro,seclabel 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/memcg cgroup rw,relatime,memory 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/expand/760fbce2-4992-4d33-879e-8458ca5696c1 ext4 rw,dirsync
,seclabel,nosuid,nodev,noatime 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user
_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id
=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_i
d=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/default/self/primary fuse rw,nosuid,nodev,noexec,noatime,
user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/sdio_emmc/by-name/system /system ext4 ro,seclabel,noatime,da
ta=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/userdata /data ext4 rw,seclabel,nosuid,nod
ev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev
,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/prodnv /productinfo ext4 rw,seclabel,nosui
d,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,gro
up_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/self/primary fuse rw,nosuid,nodev,noexec,noatime,user_id=1023
,group_id=1023,default_permissions,allow_other 0 0
/dev/block/loop0 /su ext4 rw,seclabel,noatime,data=ordered 0 0
/dev/block/loop1 /su ext4 rw,seclabel,noatime,data=ordered 0 0
[email protected]_4G:/ #
CheifX said:
unfortunately, I can't found vendor in these commands.
[email protected]_4G:/ # mount
mount
rootfs / rootfs ro,seclabel 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/memcg cgroup rw,relatime,memory 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/expand/760fbce2-4992-4d33-879e-8458ca5696c1 ext4 rw,dirsync
,seclabel,nosuid,nodev,noatime 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user
_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id
=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_i
d=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/default/self/primary fuse rw,nosuid,nodev,noexec,noatime,
user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/sdio_emmc/by-name/system /system ext4 ro,seclabel,noatime,da
ta=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/userdata /data ext4 rw,seclabel,nosuid,nod
ev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev
,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/sdio_emmc/by-name/prodnv /productinfo ext4 rw,seclabel,nosui
d,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,gro
up_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/self/primary fuse rw,nosuid,nodev,noexec,noatime,user_id=1023
,group_id=1023,default_permissions,allow_other 0 0
/dev/block/loop0 /su ext4 rw,seclabel,noatime,data=ordered 0 0
/dev/block/loop1 /su ext4 rw,seclabel,noatime,data=ordered 0 0
[email protected]_4G:/ #
Click to expand...
Click to collapse
Ah. Try mounting /system as rw.
'mount -o rw,remount /system' or remount,rw, whichever works. I thought /vendor was the problem, but it's probably /system/vendor/overlay.
All Black
ante0 said:
Ah. Try mounting /system as rw.
'mount -o rw,remount /system' or remount,rw, whichever works. I thought /vendor was the problem, but it's probably /system/vendor/overlay.
Click to expand...
Click to collapse
Hahaha changed theme prity easily by changing vendor,overlay to RW with X-Plore (a file manager). Anyway thanks to everyone for replying
Related
Hi all, I would like to check if my internal storage is really EXT4.
I tried fstab, but it is not implemented on Android.
How can I do?
Thx
Use the "mount" command from the terminal or adb shell.
Output will look like the code below. I've highlighted some of the filesystem types for clarity.
As you can see, it's actually a mixture of ext4 and yaffs2; no nasty RFS like other Galaxy S phones.
What makes you think you're not on ext4?
$ mount
rootfs / rootfs ro,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
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/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock6 /efs yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:3 /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:3 /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,errors=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.rovio.angrybirds-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.eamobile.sims3_na_qwf-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/com.onepassword.passwordmanager-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.nbadigital.gametimelite-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-4 /mnt/asec/com.eamobile.nfsshift_na_wf-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
Click to expand...
Click to collapse
darn your quicker than me, was just hunting through the forums for the post with the different partitions and their filesystems on, find it and come back to paste and BOOM, distorted loop is on the case heheh.
Ths for beating me to it
Ok, looks like it is both yaffs2 and Ext4. Right?
jamiemac1977 said:
darn your quicker than me, was just hunting through the forums for the post with the different partitions and their filesystems on, find it and come back to paste and BOOM, distorted loop is on the case heheh.
Ths for beating me to it
Click to expand...
Click to collapse
Oops! If I'd known you were on the case... LOL.
I guess typing mount in my adb shell is quicker than form searching.
lmerega said:
Ok, looks like it is both yaffs2 and Ext4. Right?
Click to expand...
Click to collapse
Yes. /cache & /efs are yaffs2 /system & /data are ext4. sdcard is vfat.
10x [10 chars]
there is a fstab when in recovery mode. does this have any effect on what mounts where when you boot normally?
[edit] never mind. init.rc and the like take the place of fstab [/edit]
Thread now changed to testing for a.i
http://sourceforge.net/projects/team...r.zip/download
test on any rom, buildprop and init.d tweaks ONLY!
Ok, now that we are talking about time management, you are wasting mine. If this is not something that you can provide OP, then don't respond.
Thread Cleaned. Let's try this again.
Here's what I sent you back in October. I'll validate my current ICS (AOKPm6r5) mounts when I get home in an hour or two and give you that in another post.
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
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/mtdblock2 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/void/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/void/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
The part the was problematic was that the sdcard mount wasn't the last... 179:1 is the sdcard, but there's a 179:2, per this:
[email protected]:/etc/init.d $ ls /dev/block/vold/*
ls /dev/block/vold/*
/dev/block/vold/179:0
/dev/block/vold/179:1
/dev/block/vold/179:2
Click to expand...
Click to collapse
Anyways, I'll check both of those again in another hour or two. If I remember.
Re: Need your mount ARGGGGHHHH
What exactly is this storage swap that you speak of.
Sent from my Nexus 4 using xda app-developers app
During boot:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell mount
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,mode=600 0 0
proc /proc proc rw,noatime 0 0
sysfs /sys sysfs rw,noatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock2 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /radio yaffs2 rw,noatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,noatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
Click to expand...
Click to collapse
After boot is completed:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell mount
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,mode=600 0 0
proc /proc proc rw,noatime 0 0
sysfs /sys sysfs rw,noatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock2 /system yaffs2 ro,noatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /radio yaffs2 rw,noatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,noatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /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:1 /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,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
Apparently wiping my sdcard yesterday fixed the extra partition issue though.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls /dev/block/vold/*
/dev/block/vold/179:0
/dev/block/vold/179:1
Click to expand...
Click to collapse
But that doesn't mean other people (like my wife) might not still have issues with an extra partition at the end.
Theraze said:
During boot:After boot is completed:Apparently wiping my sdcard yesterday fixed the extra partition issue though.But that doesn't mean other people (like my wife) might not still have issues with an extra partition at the end.
Click to expand...
Click to collapse
Thanks!!! what is the rom your using?
anoymonos said:
What exactly is this storage swap that you speak of.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
when your on ICS or JB your apps will automatically go to internal storage and it will fill internal up real quick
this script will make your phone think the sdcard is your internal storage and your internal storage your sdcard. problem solved
however because JB is moving onto multiuser devices i have to redo the script which is what im working
dsexton702 said:
Thanks!!! what is the rom your using?
Click to expand...
Click to collapse
That's AOKP milestone 6 revision 5.
wanna test the new tweaks from a.i for me? just select buildprop and init.d tweaks for this test
URL will be back up in 5 min
more than welcome to describe any details in this thread
dsexton702 said:
wanna test the new tweaks from a.i for me? just select buildprop and init.d tweaks for this test
http://sourceforge.net/projects/teamacid/files/dsexton702/A.I/Adrenaline-Injector.zip/download
more than welcome to describe any details in this thread
Click to expand...
Click to collapse
I see a multi core tweak in etc. Is this cross platform yet or still for the 4g only?
hechoen said:
I see a multi core tweak in etc. Is this cross platform yet or still for the 4g only?
Click to expand...
Click to collapse
its not only for the 4g, the multi core will be rebuilt in the next day or so to work for all multi core devices
as for the test package download the new link i post because its the real test package lol
Ok this link is the zip i need you to test http://sourceforge.net/projects/teamacid/files/dsexton702/A.I/Adrenaline-Injector.zip/download
remember just init.d and buildprop for now
Just flashed over CM 10.1. It boots and seems to be running fine. No problems with aroma either. Not the best ROM to run a full test on as wifi is borked, it doesn't deep sleep and my sim card is in my other phone . lol I'm most likely gonna flash the internal2sd just to see what it does. If that's a bad idea it's on me. Just to curious not too. When you get the multicore done let me know I'd be happy to flash it on my Skyrocket for you.
hechoen said:
Just flashed over CM 10.1. It boots and seems to be running fine. No problems with aroma either. Not the best ROM to run a full test on as wifi is borked, it doesn't deep sleep and my sim card is in my other phone . lol I'm most likely gonna flash the internal2sd just to see what it does. If that's a bad idea it's on me. Just to curious not too. When you get the multicore done let me know I'd be happy to flash it on my Skyrocket for you.
Click to expand...
Click to collapse
lol you can try the internal2external but because of the multi user options now the it will just output that its not a real file or directory
it will be fixed soon though and you will be the first i tell about the multi core, speaking of that, could you send me all the .txt files in /system/etc for me on your skyrocket
dsexton702 said:
lol you can try the internal2external but because of the multi user options now the it will just output that its not a real file or directory
it will be fixed soon though and you will be the first i tell about the multi core, speaking of that, could you send me all the .txt files in /system/etc for me on your skyrocket
Click to expand...
Click to collapse
Sub folders as well or just the two in system/etc ?
hechoen said:
Sub folders as well or just the two in system/etc ?
Click to expand...
Click to collapse
whatever .sh or .txt files in your etc folder i wanna look at please no folders just scripts in the etc folder
dsexton702 said:
whatever .sh or .txt files in your etc folder i wanna look at please no folders just scripts in the etc folder
Click to expand...
Click to collapse
PM sent.
Direction for this thread has changed refer to OP
I screwed up a bit here. I was using the stock recovery to format my /cache partition but about 5 minutes in it froze. Figuring that something had went wrong i hard rebooted the phone and now when I boot it appears that my internal sdcard partition has disappeared.
In adb I tried to cd into /sdcard and the directory is missing entirely
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
same thing here
Code:
[email protected]:/ $ cd /storage/emulated/legacy
/system/bin/sh: cd: /storage/emulated/legacy: No such file or directory
My mountpoinits show no sign of sdcard anywhere
Code:
127|[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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 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 /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/dm-0 /mnt/asec/com.trueaxis.jetcarstunts-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.tribok.android.livewallpaper.nightflare.pro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.robbers.clock-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
If anyone has any suggestions I would appreciate them. I would really like to be able to recover my data from the device before I wipe it.
Alias.TDP said:
I screwed up a bit here. I was using the stock recovery to format my /cache partition but about 5 minutes in it froze. Figuring that something had went wrong i hard rebooted the phone and now when I boot it appears that my internal sdcard partition has disappeared.
.
Click to expand...
Click to collapse
Here you go, just flash cache.img on this thread (method 2)
http://forum.xda-developers.com/showthread.php?t=2513701
Your data may be lost at all so, if it does not work, then use flash-all method (method 1)
GUGUITOMTG4 said:
Here you go, just flash cache.img on this thread (method 2)
http://forum.xda-developers.com/showthread.php?t=2513701
Your data may be lost at all so, if it does not work, then use flash-all method (method 1)
Click to expand...
Click to collapse
Thanks dude that worked
Alias.TDP said:
Thanks dude that worked
Click to expand...
Click to collapse
Glad it's fixed. Keep that thread in the first aid kit:cyclops:
Remember - NEVER reboot your phone when it's trying to wipe. Some of these phones take an exceptionally long time to wipe depending on your recovery.
I have TF700 running Crombi-KK F2FS on data, and added the 'discard' flag to fstab.cardhu to (hopefully) ensure trim of flash memory. Is there some way to verify that the discard function is working?
gc2712 said:
I have TF700 running Crombi-KK F2FS on data, and added the 'discard' flag to fstab.cardhu to (hopefully) ensure trim of flash memory. Is there some way to verify that the discard function is working?
Click to expand...
Click to collapse
The fstab,cardhu gets modified by my boot process depending upon what you chose. I intentionally remove the discard option as it cause me bootloops.
However to check if yours has persistd ( and it may have if you haven't been anywhere near data2sd or rom2sd) is run the following in a terminal
mount | grep /dev/block/*
look for the /data and you will see what options it has been mounted with, interested to see if discard has persisted and why it won't work on my device
sbdags said:
The fstab,cardhu gets modified by my boot process depending upon what you chose. I intentionally remove the discard option as it cause me bootloops.
However to check if yours has persistd ( and it may have if you haven't been anywhere near data2sd or rom2sd) is run the following in a terminal
mount | grep /dev/block/*
look for the /data and you will see what options it has been mounted with, interested to see if discard has persisted and why it won't work on my device
Click to expand...
Click to collapse
I tried running the above command in terminal. Without su just got 'permssion denied' on all. With su there was no response in terminal at all So just tried:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 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
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
mobi.mgeek.TunnyBrowser_cache /data/data/mobi.mgeek.TunnyBrowser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Looks like the discard flag was just ignored? Any way to make it persist?
gc2712 said:
I tried running the above command in terminal. Without su just got 'permssion denied' on all. With su there was no response in terminal at all So just tried:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 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
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
mobi.mgeek.TunnyBrowser_cache /data/data/mobi.mgeek.TunnyBrowser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Looks like the discard flag was just ignored? Any way to make it persist?
Click to expand...
Click to collapse
You can't edit the fstab directly as it gets replaced by the kernel on every boot.
so go to /system/boot/print.d
Open 30fstab-f2fs in a text editor
On this line change it from
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime,//;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
to
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime/discard/;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
Reboot but be prepared for a bootloop that you can only fix by undoing what you just did.... Have a nandroid ready to go
sbdags said:
You can't edit the fstab directly as it gets replaced by the kernel on every boot.
so go to /system/boot/print.d
Open 30fstab-f2fs in a text editor
On this line change it from
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime,//;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
to
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime/discard/;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
Reboot but be prepared for a bootloop that you can only fix by undoing what you just did.... Have a nandroid ready to go
Click to expand...
Click to collapse
Just a cautious check on syntax before I do this. Every other flag on that line is of the form: ;s/flagx,// , yet in this instance you suggest just forward slash after 'nodiratime', ending with just a forward slash instead of two forward slashes. Is this intentional or should the syntax be: //;s/nodiratime,//;s/discard,//;s/noauto_da_alloc, etc.
Although I've used linux for years (Since Red Hat 7!) and have just enough knowledge to follow instructions to edit scripts, I still don't grasp syntax very well. (Just enough to know if I get it wrong things screw up
Also, if I save a copy of the 30fstab-f2fs file to sdcard can I simply copy it back using TWRP (latest) instead of a full nandroid restore?
Sorry if these are dumb questions. Your help is greatly appreciated.
gc2712 said:
Just a cautious check on syntax before I do this. Every other flag on that line is of the form: ;s/flagx,// , yet in this instance you suggest just forward slash after 'nodiratime', ending with just a forward slash instead of two forward slashes. Is this intentional or should the syntax be: //;s/nodiratime,//;s/discard,//;s/noauto_da_alloc, etc.
Although I've used linux for years (Since Red Hat 7!) and have just enough knowledge to follow instructions to edit scripts, I still don't grasp syntax very well. (Just enough to know if I get it wrong things screw up
Also, if I save a copy of the 30fstab-f2fs file to sdcard can I simply copy it back using TWRP (latest) instead of a full nandroid restore?
Sorry if these are dumb questions. Your help is greatly appreciated.
Click to expand...
Click to collapse
Yes it is my correct - my edit will replace nodiratime with discard Your edit will look for discard (which isn't there) and replace it with nothing
Personally I'd do a full nandroid but yes as long as you can partially recover then that single file should be ok.
sbdags said:
Yes it is my correct - my edit will replace nodiratime with discard Your edit will look for discard (which isn't there) and replace it with nothing
Personally I'd do a full nandroid but yes as long as you can partially recover then that single file should be ok.
Click to expand...
Click to collapse
Many thanks (red face here). I'll give it a try today and do the full nandroid backup just in case. Will report back the result.
Well! That was a debacle.:crying:
Changed to:
"$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime/discard/;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu "
It didn't boot loop, but eventually booted into a screen which said, "Encryption Unsuccesful. Encryption was interrupted and can't complete. As a result your tablet is no longer accessible" etc....
Thank god for the nandroid! When I reflashed the nandroid, TWRP reported that it was formatting system to ext4 even though it was originally F2FS. However when I rebooted and checked in terminal it indicated that the FS on system was in fact F2FS.
# mount |grep /dev/block/mmcblk0p8
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
No idea why, but its all working again, but alas, no 'discard' option. Could this be the reason?
[email protected]:/ # fstrim -v /data
fstrim: FITRIM: Inappropriate ioctl for device
Don't know what that error means and google wasn't my friend this time.
gc2712 said:
I tried running the above command in terminal. Without su just got 'permssion denied' on all. With su there was no response in terminal at all So just tried:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 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
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
mobi.mgeek.TunnyBrowser_cache /data/data/mobi.mgeek.TunnyBrowser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Looks like the discard flag was just ignored? Any way to make it persist?
Click to expand...
Click to collapse
Here is my /dev/block* information:
Code:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0
[COLOR="RoyalBlue"]/dev/block/mmcblk0p8 /datai ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0[/COLOR]
[COLOR="RoyalBlue"]/dev/block/mmcblk1p2 /data f2fs rw,noatime,background_gc=on,discard,user_xattr,acl,errors=panic,active_logs=6 0 0[/COLOR]
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
browser_cache /data/data/com.android.browser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:49 /Removable/MicroSD texfat rw,relatime,uid=1000,gid=1015,umask=0000,
allow_utime=0022,nls=utf8,min_prealloc_size=64k,readahead=4M,discard,errors=continue 0 0
[email protected]:/ #
It seems to stick with the "discard" mounting flag...
LetMeKnow said:
Here is my /dev/block* information:
Code:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0
[COLOR="RoyalBlue"]/dev/block/mmcblk0p8 /datai ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0[/COLOR]
[COLOR="RoyalBlue"]/dev/block/mmcblk1p2 /data f2fs rw,noatime,background_gc=on,discard,user_xattr,acl,errors=panic,active_logs=6 0 0[/COLOR]
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
browser_cache /data/data/com.android.browser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:49 /Removable/MicroSD texfat rw,relatime,uid=1000,gid=1015,umask=0000,
allow_utime=0022,nls=utf8,min_prealloc_size=64k,readahead=4M,discard,errors=continue 0 0
[email protected]:/ #
It seems to stick with the "discard" mounting flag...
Click to expand...
Click to collapse
What is the additional partition mmcblk1p2 for data? The partition mmcblk0p8 which on my system is my data partition has been located on /datai and is ext4 on yours. How does that happen? Are you using data2sd or something?
gc2712 said:
What is the additional partition mmcblk1p2 for data? The partition mmcblk0p8 which on my system is my data partition has been located on /datai and is ext4 on yours. How does that happen? Are you using data2sd or something?
Click to expand...
Click to collapse
Yes, you are correct. I am using Data2sd. I am running f2fs on my external data partition (/dev/block/mmcblk1p2) and leave my internal data partition as ext4 because it is just a backup data partition that I actually never use it.
LetMeKnow said:
Yes, you are correct. I am using Data2sd. I am running f2fs on my external data partition (/dev/block/mmcblk1p2) and leave my internal data partition as ext4 because it is just a backup data partition that I actually never use it.
Click to expand...
Click to collapse
Ah! Mystery solved then. sbdags was right then that with internal F2FS /data the discard option will bootloop, or, as in my case boot and trash the data partition requiring factory reset. Hopefully, the F2FS file system and KitKat manage garbage collection well enough without fstrim/discard as I don't want to reinstall again as ext4 at this point. Perhaps someone will make it work in the future.
gc2712 said:
Ah! Mystery solved then. sbdags was right then that with internal F2FS /data the discard option will bootloop, or, as in my case boot and trash the data partition requiring factory reset. Hopefully, the F2FS file system and KitKat manage garbage collection well enough without fstrim/discard as I don't want to reinstall again as ext4 at this point. Perhaps someone will make it work in the future.
Click to expand...
Click to collapse
Hmm, I did help one user using f2fs on internal data partition with discard flag on JB Rom. He had no issue until moving on with KK Rom. If I can have the tf700 long enough, I will test it out on the internal data so we can rule it out...
Garbage collection is to reclaim your locked up or old memory that old apps keeps holding on without using them. I believe that is what it is for but I may be wrong...
I'm currently using ElementalX kernel with built in exfat/ntfs and Stickmount for mount/unmount support.
I can mount and read files from exfat usb sticks as well as rename and delete. My issue however is when I try to create files. When I copy from internal memory to usb drive I get permission denied errors.
I'm trying to troubleshoot if this is the kernel, or some rom related issue. Would anyone know off hand if this is a limitation of the kernel or suggestions to remedy the issue?
I've already verified it is mounted writable and the phone sees free space
Code:
[email protected]:/storage/sdcard0/usbStorage/sda1 # df | grep sda1
/data/media/0/usbStorage/sda1 58.9G 24.2G 34.7G 131072
[email protected]:/storage/sdcard0/usbStorage/sda1 # mount | grep sda1
/dev/block/sda1 /data/media/0/usbStorage/sda1 exfat rw,nosuid,nodev,relatime,fmask=0000,dmask=0000,allow_utime=0022,iocharset=utf8,namecase=0,errors=remount-ro 0 0
[email protected]:/storage/sdcard0/usbStorage/sda1 # echo "test">/data/media/0/usbStorage/sda1/test.file
sh: can't create /data/media/0/usbStorage/sda1/test.file: Permission denied
1|[email protected]:/storage/sdcard0/usbStorage/sda1 # echo "test">/storage/sdcard0/usbStorage/sda1/test.file
sh: can't create /storage/sdcard0/usbStorage/sda1/test.file: Permission denied
1|[email protected]:/storage/sdcard0/usbStorage/sda1 # echo "test">/storage/emulated/0/usbStorage/sda1/test.file
sh: can't create /storage/emulated/0/usbStorage/sda1/test.file: Permission denied
Plug the USB stick in with exfat. Open a terminal emulator. Type "mount" and press enter.
What's the output? Copy/paste please
Sent from my Nexus 5 using Tapatalk
rootSU said:
Plug the USB stick in with exfat. Open a terminal emulator. Type "mount" and press enter.
What's the output? Copy/paste please
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick response. I updated original post with more information. Full mount here:
Code:
[email protected]:/storage/sdcard0/usbStorage/sda1 # 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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=050,gid=1028 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/mobi.beyondpod.unlockkey-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.gvoip-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/sda1 /data/media/0/usbStorage/sda1 exfat rw,nosuid,nodev,relatime,fmask=0000,dmask=0000,allow_utime=0022,iocharset=utf8,namecase=0,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nomblk_io_submit,nodelalloc,errors=panic,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/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/storage/sdcard0/usbStorage/sda1 #
I'm using sshdroid for remote terminal to root in. I have also tried using a terminal emulator on the device with the same results so I just stuck with using sshdroid for all my testing.