I'm having the darndest time trying to figure out a certain issue I'm having. For some reason I cannot edit or delete or even write to certain folders of my internal storage. I have searched the forums for fixes, and the common sense fix keeps coming up, permissions.
In Terminal Emulator I am looking at the permissions for all the folders on my internal /sdcard and they disply as:
Code:
drwxrwxr-x
as expected. Yet when I try to delete say for example /sdcard/Download it tells me the folder is Read Only.
I even chmod to change the permissions and they just dont change. The reason I use the Download folder as an example is because I cannot download any files, like an updated ROM from any browser, it just fails. It is extremely annoying. My Prime is rooted, unlocked, and running Virtuous S .28
To make matters worse, I am deployed to Afghanistan and my laptop recently died, so all I have are my Prime and Desire HD phone to work with.
If anyone has any ideas on how to resolve this I'm all ears.
Many thanks in advance.
TrailorParkKid said:
I'm having the darndest time trying to figure out a certain issue I'm having. For some reason I cannot edit or delete or even write to certain folders of my internal storage. I have searched the forums for fixes, and the common sense fix keeps coming up, permissions.
In Terminal Emulator I am looking at the permissions for all the folders on my internal /sdcard and they disply as:
Code:
drwxrwxr-x
as expected. Yet when I try to delete say for example /sdcard/Download it tells me the folder is Read Only.
I even chmod to change the permissions and they just dont change. The reason I use the Download folder as an example is because I cannot download any files, like an updated ROM from any browser, it just fails. It is extremely annoying. My Prime is rooted, unlocked, and running Virtuous S .28
To make matters worse, I am deployed to Afghanistan and my laptop recently died, so all I have are my Prime and Desire HD phone to work with.
If anyone has any ideas on how to resolve this I'm all ears.
Many thanks in advance.
Click to expand...
Click to collapse
What's the output of the "ls -l /sdcard/Download"??
craigacgomez said:
What's the output of the "ls -l /sdcard/Download"??
Click to expand...
Click to collapse
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # ls -l /sdcard/Download
-rw-rw-r-- root sdcard_rw 63816 2012-03-07 14:40 -1
-rw-rw-r-- root sdcard_rw 63733 2012-03-07 14:40 -2
-rw-rw-r-- root sdcard_rw 334117 2012-03-07 13:03 12th CAB Packing List FINAL.docx
-rw-rw-r-- root sdcard_rw 62524 2012-03-07 02:35 ALERT ROSTER.pptx
drwxrwxr-x root sdcard_rw 2012-07-02 10:29 Adobe Reader
-rw-rw-r-- root sdcard_rw 346301 2012-03-07 14:40 CJTF computer user agreement.pdf
-rw-rw-r-- root sdcard_rw 10041835 2012-06-18 07:44 DebugfsRoot_v1.8.zip
drwxrwxr-x root sdcard_rw 2012-06-23 16:10 FAQ
drwxrwxr-x root sdcard_rw 2012-06-23 16:10 MANUAL
-rw-rw-r-- root sdcard_rw 4045147 2012-06-22 23:21 Phonesky.apk
-rw-rw-r-- root sdcard_rw 162197 2012-03-07 14:40 SFC CRIST-DA FORM 2875_BLANK FORM.pdf
-rw-rw-r-- root sdcard_rw 4036382 2012-06-23 19:18 Signed_Vending-mod.apk
-rw-rw-r-- root sdcard_rw 622047 2012-06-23 11:27 UnLock_Device_App_V6.apk
-rw-rw-r-- root sdcard_rw 4031699 2012-06-23 18:14 Vending-3.5.16-mod.apk
-rw-rw-r-- root sdcard_rw 16903 2012-03-07 14:40 _CJTF USER AGREEMENT INSTRUCTIONS.docx
[email protected]:/ #
File permissions of /data/media issues
TrailorParkKid said:
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # ls -l /sdcard/Download
-rw-rw-r-- root sdcard_rw 63816 2012-03-07 14:40 -1
-rw-rw-r-- root sdcard_rw 63733 2012-03-07 14:40 -2
-rw-rw-r-- root sdcard_rw 334117 2012-03-07 13:03 12th CAB Packing List FINAL.docx
-rw-rw-r-- root sdcard_rw 62524 2012-03-07 02:35 ALERT ROSTER.pptx
drwxrwxr-x root sdcard_rw 2012-07-02 10:29 Adobe Reader
-rw-rw-r-- root sdcard_rw 346301 2012-03-07 14:40 CJTF computer user agreement.pdf
-rw-rw-r-- root sdcard_rw 10041835 2012-06-18 07:44 DebugfsRoot_v1.8.zip
drwxrwxr-x root sdcard_rw 2012-06-23 16:10 FAQ
drwxrwxr-x root sdcard_rw 2012-06-23 16:10 MANUAL
-rw-rw-r-- root sdcard_rw 4045147 2012-06-22 23:21 Phonesky.apk
-rw-rw-r-- root sdcard_rw 162197 2012-03-07 14:40 SFC CRIST-DA FORM 2875_BLANK FORM.pdf
-rw-rw-r-- root sdcard_rw 4036382 2012-06-23 19:18 Signed_Vending-mod.apk
-rw-rw-r-- root sdcard_rw 622047 2012-06-23 11:27 UnLock_Device_App_V6.apk
-rw-rw-r-- root sdcard_rw 4031699 2012-06-23 18:14 Vending-3.5.16-mod.apk
-rw-rw-r-- root sdcard_rw 16903 2012-03-07 14:40 _CJTF USER AGREEMENT INSTRUCTIONS.docx
[email protected]:/ #
Click to expand...
Click to collapse
TrailerParkKid,
I'm having similar issues. The /sdcard folder is a sym-linked to /storage/sdcard0. /storage/sdcard0 is virtualized from /data/media. I noticed that in this folder the user\group is root\root with permissions -rwx------.
I think we have permissions issues in this directory. If I change the permissions to -rwxrwxrwx then things start working, however I don't like that answer.
I was unable to fix it by changing any permissions through TE. I was finally able to use another device to download the Stock JB ROM modded with the new bootloader and the current version of TWRP. The new version of TWRP allowed me to use my external SD card to flash, so I used the Full Wipe flash to completely wipe the internal SD card. It was a last resort, but I didn't really have a choice. Since then I have been able to download files without issue.
My solution to repair /data/media/
TrailorParkKid said:
I was unable to fix it by changing any permissions through TE. I was finally able to use another device to download the Stock JB ROM modded with the new bootloader and the current version of TWRP. The new version of TWRP allowed me to use my external SD card to flash, so I used the Full Wipe flash to completely wipe the internal SD card. It was a last resort, but I didn't really have a choice. Since then I have been able to download files without issue.
Click to expand...
Click to collapse
TrailorParkKid,
Good to see you got it working. There's always more than one way to fix things. I suspect the Full Wipe of internal SD card probably set the permissions up correctly so that subsequent downloaded files would inherit the correct settings. I did that as well, but then I also restored my backed up files. Those files and directories then got the wrong permissions.
My solution was the following 3 lines executed from /data/media/. Hope this also assists someone else googling...
find . -type d -exec chmod 775 {} ";"
find . -type f -exec chmod 664 {} ";"
find . -exec chown media_rw:media_rw {} ";"
Related
Hi, I am using tnt 4.4.0 on my g tablet and I see the system/apps directory with loads of apk's that came packaged with the tnt rom.
My question or issue is this.
When I download an app from the marketplace I can't seem to figure out where it goes.
Using file expert v3.1.0 I searched all over and still no luck.. using this same app I can make backups of my apps by clicking the apps tab and long clicking an app and selecting backup but I would assume the original Zip or APK that I downloaded is on my device somewhere?
Or is it just unzipping from the market and I then have to zip them into a new file with an apk extension?
Innerchaos said:
My question or issue is this.
When I download an app from the marketplace I can't seem to figure out where it goes.
Click to expand...
Click to collapse
To answer this part of your question:
Downloaded apps are either in /data/app or /mnt/asec (this, after much filesystem path-manipulation magic post system boot) for apps moved to SD card:
Code:
$ su
# find /data/ -name *.apk
/data/app/com.google.android.street-1.apk
/data/app/com.google.android.youtube-1.apk
/data/app/com.android.vending-2.apk
/data/app/com.curvefish.widgets.wifionoff.donate-1.apk
/data/app/com.jasoncalhoun.android.systeminfowidget-1.apk
/data/app/com.facebook.katana-1.apk
/data/app/com.dataviz.docstogoapp-1.apk
/data/app/org.zooper.acw-1.apk
/data/app/jackpal.androidterm-1.apk
/data/app/com.curvefish.apps.appremover-1.apk
/data/app/com.curvefish.widgets.bluetoothonoff-1.apk
/data/app/com.noshufou.android.su-1.apk
/data/app/org.adwfreak.launcher-1.apk
#
# find /mnt/asec/ -name *.apk
/mnt/asec/com.rovio.angrybirdsrio-2/pkg.apk
/mnt/asec/com.google.android.apps.maps-2/pkg.apk
/mnt/asec/com.alensw.PicFolder-1/pkg.apk
/mnt/asec/com.farproc.wifi.analyzer-2/pkg.apk
/mnt/asec/com.redirectin.rockplayer.android.unified-2/pkg.apk
/mnt/asec/com.speedsoftware.rootexplorer-2/pkg.apk
/mnt/asec/com.google.android.voicesearch-1/pkg.apk
/mnt/asec/com.dataviz.docstogo-2/pkg.apk
/mnt/asec/net.androidcomics.acv-1/pkg.apk
/mnt/asec/com.rovio.angrybirdsseasons-1/pkg.apk
/mnt/asec/com.seesmic-1/pkg.apk
/mnt/asec/com.rovio.angrybirds-1/pkg.apk
/mnt/asec/com.adobe.flashplayer-1/pkg.apk
/mnt/asec/com.google.android.gm-1/pkg.apk
/mnt/asec/com.google.android.stardroid-1/pkg.apk
As to your other questions, I don't have definitive answers, but, looking inside those 2 directories (/data, and, /mnt/sdcard after you've unmount it) might prove instructive.
My mnt/asec directory is empty as well
Innerchaos said:
My mnt/asec directory is empty as well
Click to expand...
Click to collapse
Did you run the find command as root? (Or, have root permissions when you looked inside /mnt/asec?)
/mnt/asec might also be empty simply because you haven't moved any apps to the SD card.
The actual .apk files are in /mnt/sdcard/.android_secure/, but with a .asec extension instead of .apk. You'll have to unmount /mnt/sdcard in Settings > Storage first, then mount it again manually for you to see the files in that directory:
Code:
$ su
# mount -r -t vfat /dev/block/mmcblk3p1 /mnt/sdcard
# ls -l /mnt/sdcard/.android_secure/
total 124216
-rwxr-xr-x 1 root root 13870592 Jun 8 23:17 com.adobe.flashplayer-2.asec
-rwxr-xr-x 1 root root 2161664 May 30 03:37 com.alensw.PicFolder-1.asec
-rwxr-xr-x 1 root root 7483904 May 20 08:44 com.dataviz.docstogo-2.asec
-rwxr-xr-x 1 root root 2161664 Jun 3 03:24 com.farproc.wifi.analyzer-2.asec
-rwxr-xr-x 1 root root 8548352 May 26 22:18 com.google.android.apps.maps-2.asec
-rwxr-xr-x 1 root root 4290560 May 17 10:22 com.google.android.gm-1.asec
-rwxr-xr-x 1 root root 4290560 May 17 10:21 com.google.android.stardroid-1.asec
-rwxr-xr-x 1 root root 4290560 May 17 10:22 com.google.android.voicesearch-1.asec
-rwxr-xr-x 1 root root 9612800 May 17 10:22 com.redirectin.rockplayer.android.unified-2.asec
-rwxr-xr-x 1 root root 21321728 May 17 10:21 com.rovio.angrybirds-1.asec
-rwxr-xr-x 1 root root 19192832 May 19 19:58 com.rovio.angrybirdsrio-2.asec
-rwxr-xr-x 1 root root 22386176 May 17 10:21 com.rovio.angrybirdsseasons-1.asec
-rwxr-xr-x 1 root root 3226112 May 17 10:22 com.seesmic-1.asec
-rwxr-xr-x 1 root root 2161664 May 24 20:11 com.speedsoftware.rootexplorer-2.asec
-rwxr-xr-x 1 root root 2161664 May 28 16:03 net.androidcomics.acv-1.asec
#
# umount /mnt/sdcard
You won't see those files when the SD card is mounted normally by Android. Then, the /mnt/sdcard/.android_secure directory will appear to be empty.
You might also have to use /dev/block/mmcblk2p1 instead of /dev/block/mmcblk3p1 in the mount command above, if you run a Gingerbread-based ROM.
Hello XDA-Developers!
I want to install Back Track 5 ARM in my AllWinner A10 based tablet, I followed the lesson for Galaxy and I downloaded the boot script for Galaxy and the bt5.img(3.25G). I changed some of the codes to launch BT5 in external sdcard and suit my ROM,then launched it, only to find some errors. Well, the source code of the boot script(modified by myself to suit my device) like this:
perm=$(id|busybox cut -b 5)
if [ "$perm" != "0" ];then echo "This Script Needs Root! Type : su";exit;fi
mount -o remount,rw /dev/block/mmcblk0p1 /system
export kit=/mnt/extsd/BT5
export bin=/system/bin
export mnt=/mnt
mkdir -p $mnt
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export HOME=/
if [ -b /dev/loop2 ]; then
echo "Loop device exists"
else
busybox mknod /dev/loop2 b 7 0
fi
busybox mount -o loop,noatime -t extsd $kit/bt5.img $mnt
busybox mount --bind /dev/pts $mnt/dev/pts
busybox mount --bind /proc $mnt/proc
busybox mount --bind /sys $mnt/sys
busybox sysctl -w net.ipv4.ip_forward=1
echo "nameserver 8.8.8.8" > $/etc/resolv.conf
echo "127.0.0.1 localhost bt5" > $/etc/hosts
busybox chroot $/bin/bash
echo "Shutting down BackTrack ARM For Xoom"
umount $/dev/pts
umount $/proc
umount $/sys
umount $mnt
when I launch the script(bootbtV) in Terminal Emulator, only to find some errors like this:
[email protected]:/ $ su
[email protected]:/ # cd mnt/extsd/BT5
[email protected]:/mnt/extsd/BT5 # sh bootbtV
Loop device exists
mount: mounting /dev/loop8 on /mnt failed: No such device
mount: mounting /dev/pts on /mnt/dev/pts failed: No such file or directory
mount: mounting /proc on /mnt/proc failed: No such file or directory
mount: mounting /sys on /mnt/sys failed: No such file or directory
net.ipv4.ip_forward = 1
bootbtV[23]: can't create $/etc/resolv.conf: No such file or directory
bootbtV[24]: can't create $/etc/hosts: No such file or directory
chroot: can't change root directory to $/bin/bash: No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/mnt/extsd/BT5 #
Well, In my opinion, according to the errors "No such file or directory", I think it is the difference between my device and Galaxy that causes the errors. In my device, the file structure is different from what the boot script means, such is the file structure of my device's root directory:
drwxr-xr-x root root 2013-01-16 11:22 acct
drwxrwx--- system cache 2013-01-16 09:51 cache
dr-x------ root root 2013-01-16 11:22 config
lrwxrwxrwx root root 2013-01-16 11:22 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-13 17:14 data
-rw-r--r-- root root 116 1970-01-01 08:00 default.prop
drwxr-xr-x root root 2013-01-16 11:27 dev
lrwxrwxrwx root root 2013-01-16 11:22 etc -> /system/etc
-rwxr-x--- root root 105268 1970-01-01 08:00 init
-rwxr-x--- root root 2344 1970-01-01 08:00 init.goldfish.rc
-rwxr-x--- root root 19030 1970-01-01 08:00 init.rc
-rwxr-x--- root root 2644 1970-01-01 08:00 init.sun4i.rc
-rwxr-x--- root root 2230 1970-01-01 08:00 init.sun4i.usb.rc
-rwxr-x--- root root 1637 1970-01-01 08:00 init.trace.rc
-rwxr-x--- root root 3915 1970-01-01 08:00 init.usb.rc
-rwxr-x--- root root 1536000 1970-01-01 08:00 initlogo.rle
drwxrwxr-x root system 2013-01-16 11:22 mnt
-rw-r--r-- root root 782728 1970-01-01 08:00 nand.ko
dr-xr-xr-x root root 1970-01-01 08:00 proc
drwx------ root root 2012-10-11 13:57 root
drwxr-x--- root root 1970-01-01 08:00 sbin
lrwxrwxrwx root root 2013-01-16 11:22 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-01-16 11:22 sys
drwxr-xr-x root root 2013-01-13 17:59 system
-rw-r--r-- root root 272 1970-01-01 08:00 ueventd.goldfish.rc
-rw-r--r-- root root 3879 1970-01-01 08:00 ueventd.rc
-rw-r--r-- root root 1313 1970-01-01 08:00 ueventd.sun4i.rc
lrwxrwxrwx root root 2013-01-16 11:22 vendor -> /system/vendor
I think, the only way to launch BT5 in my device successfully is to modify the boot script so that it can suit my device, especially the file structure. But I am a green hand in Linux, I don't know what does some of the codes mean, if you are good at Linux script, would you please give me some advice?
Thank you very much!
OK - it seems that it is fairly easy to load Facer and all the Facer faces that you have onto your Watch. I won't go into much detail here - you can search other threads on this site or others for details on how to do this (many of the steps can be found in this thread: http://forum.xda-developers.com/android-wear/development/getting-watchmaker-watch-android-wear-t3262448). But the basic idea is to load the wearable .apk file extracted from the Facer app on the Android host (the device which you run Facer and create/load/modify your watch faces) onto the watch, and then copy the key watch folders to the watch as well. You will need the Android SDK tools to do this, along with a USB connection to the watch (most watches except the original Moto 360 come with one - the charging cable, which also contains data lines). You can use two free tools from the Play Store to help with these tasks - ES File Manager and AirDroid.
The basic idea is to first create all the faces that you wish to use on either an Android device or Emulator (Android host).
After this, if you examine your Android host device, you will see two Facer folders in the /sdcard folder - Facer, and Facer2. You only need to use part of the Facer folder.
Steps:
1. Install Facer from the Play Store on the Android host device and develop your watches.
2. Install the wearable .apk (*adb install ...*) onto the watch.
3. Copy the /sdcard/Facer folder to your PC or Mac. Then remove everything except the long hex-string folders - these are the watch face folders.
4. Copy this modified Facer folder to the watch using *adb push ...*
5. Reboot the watch, then press the watch face (brings up the watch face selector), scroll until you find the Facer icon, press the settings
button and then select the Facer watch face that you want to use.
That should be it. If you examine the file structure on the watch after this, you will find a couple of new folders - none_selected and sync.
and a watchface_1.zip file.
As you add new watches, new hex-string folders will be created on the host Android device. Just transfer those folders to your PC or Mac and
then transfer them back to your watch.
Kevin
Please can somebody upload wholeFacer directory from watch with few installed watchfaces ? i need to see how look folder structure with multiple load faces. Thanks a lot.
x5ox1 said:
Please can somebody upload wholeFacer directory from watch with few installed watchfaces ? i need to see how look folder structure with multiple load faces. Thanks a lot.
Click to expand...
Click to collapse
Here are some directory structures from my Android host and watch. First, the host:
adb -e shell ls -al /sdcard/Facer
-rwxrwx--- root sdcard_r 0 2016-01-25 14:59 .nomedia
drwxrwx--- root sdcard_r 2016-01-25 14:59 135d95fb-06cb-4a2a-832c-5fc45e9b9fb0
drwxrwx--- root sdcard_r 2016-01-25 14:59 6b07b86c-ebda-49af-bb31-d9ec8a71da03
drwxrwx--- root sdcard_r 2016-01-25 14:59 848a2270-9d55-4353-a62b-b153badcce69
drwxrwx--- root sdcard_r 2016-01-25 14:59 9358cc22-8f49-411c-a725-607636a1b0ee
-rwxrwx--- root sdcard_r 331653 2016-01-25 14:59 Colorful.zip
-rwxrwx--- root sdcard_r 524582 2016-01-25 14:59 Digiloge.zip
-rwxrwx--- root sdcard_r 101885 2016-01-25 14:59 E3 Military.zip
-rwxrwx--- root sdcard_r 357285 2016-01-25 14:59 E3 Supply Co Aviator.zip
-rwxrwx--- root sdcard_r 94620 2016-01-25 14:59 Moto Dark.zip
drwxrwx--- root sdcard_r 2016-01-25 14:59 b7c9deb0-e43d-4892-ae96-2b826681c2f4
I have 5 installed watch faces - the Moto Dark resides in the b7c9deb0... folder
adb -e shell ls -al /sdcard/Facer/b7c9deb0-e43d-4892-ae96-2b826681c2f4
-rwxrwx--- root sdcard_r 562 2016-01-25 16:21 description.json
drwxrwx--- root sdcard_r 2016-01-25 14:59 fonts
drwxrwx--- root sdcard_r 2016-01-25 14:59 images
-rwxrwx--- root sdcard_r 9342 2016-01-25 15:23 preview.png
-rwxrwx--- root sdcard_r 1874 2016-01-25 15:23 watchface.json
-rwxrwx--- root sdcard_r 238 2016-01-25 15:23 watchface_settings.json
Now, the watch:
adb -d shell ls -al /sdcard/Facer
drwxrwx--- root sdcard_r 2016-01-25 15:25 135d95fb-06cb-4a2a-832c-5fc45e9b9fb0
drwxrwx--- root sdcard_r 2016-01-25 15:25 6b07b86c-ebda-49af-bb31-d9ec8a71da03
drwxrwx--- root sdcard_r 2016-01-25 15:25 848a2270-9d55-4353-a62b-b153badcce69
drwxrwx--- root sdcard_r 2016-01-25 15:25 9358cc22-8f49-411c-a725-607636a1b0ee
drwxrwx--- root sdcard_r 2016-01-25 15:25 b7c9deb0-e43d-4892-ae96-2b826681c2f4
drwxrwx--- root sdcard_r 2016-01-25 14:40 none_selected
drwxrwx--- root sdcard_r 2016-01-25 14:40 sync
-rw-rw---- root sdcard_r 652974 2016-01-25 14:40 watchface_1.zip
Note that I only copied the first 5 (hex) folders from the host to the watch; the rest was created by Facer after starting it on the watch.
And finally:
adb -d shell ls -al /sdcard/Facer/b7c9deb0-e43d-4892-ae96-2b826681c2f4
-rw-rw---- root sdcard_r 562 2016-01-27 22:01 description.json
drwxrwx--- root sdcard_r 2016-01-25 15:25 fonts
drwxrwx--- root sdcard_r 2016-01-25 15:25 images
-rw-rw---- root sdcard_r 9342 2016-01-25 15:25 preview.png
-rw-rw---- root sdcard_r 1874 2016-01-25 15:25 watchface.json
-rw-rw---- root sdcard_r 238 2016-01-25 15:25 watchface_settings.json
This appears to be exactly the same as on the host.
Hope this helps.
Kevin
I've create a directory /storage/sdcard2 and mounted it as follows:
mkdir sdcard2
chmod 771 /storage/sdcard2
chgrp 1015 /storage/sdcard2
So it has looks like:
drwxrwx--x 3 root sdcard_rw 60 Feb 12 20:17 sdcard2
Now the external storage looks like:
drwxrwx--x 19 root sdcard_rw 32768 Dec 31 1969 DE52-F3E6
So they match exactly, but for some reason while most apps (non-root) can see and view /storage/DE52-F3E6 nothing but root apps can see /storage/sdcard2 (if I su* others can see it in a console but not access it). In Android (CM12) 5.1, this worked fine, in (CM13) 6.0.1 I'm going crazy. I thought it might be namespace separation in Super SU, but that does not appear to be the case it is as if there is another block that only allows root to see non-standard directories (or files) since creating a file in /storage has the exact same issue.
How do I fix this as it makes using 6.0.1 useless as I can not manually mount my secondary partition on the SD Sard and get access to the data on it (except as root).
su - u_10034
127|[email protected]:/storage # su - u0_a334
[email protected]:/storage $ ls -al
drwxr-xr-x 6 root root 140 Feb 12 20:06 .
drwxr-xr-x 28 root root 0 Feb 12 19:59 ..
drwxrwx--x 19 root sdcard_rw 32768 Dec 31 1969 DE52-F3E6
drwx--x--x 5 root sdcard_rw 4096 Dec 31 2014 emulated
drwxrwx--x 3 root sdcard_rw 60 Feb 12 20:17 sdcard2
drwxr-xr-x 2 root root 60 Aug 2 2015 self
[email protected]:/storage $
At a minimum I want to at be able to access the sdcard2 directory same as I can access DE52-F3E6 the permissions match, but the SE (ls -n) setting differ, but I can not find what setting I need to use there to allow the same access as DE52-F3E6 since DE52-F3E6 is a device and sdcard2 is a directory.
Thanks,
ERIC
First I'm on 7.1.1 LineageOS v20, I have my SD card formated using ext2 since I need 4+ GB files for TWRP backups. This works and I can create files and folder ..., however I've found that if I pull the SD card and on a computer set the permission to say 777 all is fine, but on the Phone, I can for instance create a directory using root-explorer, but can not set permission or copy files into it. If I create the folder on the computer I can copy files into it however. Next say I backup using Ti-backup to the external SDcard it works fine, but of I install a new ROm I can not access the previous backup files. I can not change the permissions on the file to 777 either from a terminal.
Really this is what upsets me, as root in a terminal I can not set permissions on a file as it does nothing, for instance on /storage/emulated/0 I have:
h918:/storage/emulated/0 # ls
drwxrwx--x 3 root sdcard_r 4096 Mar 14 19:35 .rr
-rw-rw---- 1 root sdcard_r 1369542927 Apr 1 22:28 01update.zip
-rw-rw---- 1 root sdcard_r 884357956 Apr 1 22:34 02update.zip
-rw-rw---- 1 root sdcard_r 1057588047 Apr 1 22:41 03update.zip
drwxrwx--x 2 root sdcard_r 4096 Mar 9 23:06 3DMarkAndroid
drwxrwx--x 2 root sdcard_r 4096 Mar 4 18:20 Alarms
....
as root I execute:
h918:/storage/emulated/0 # chmod 777 *.zip
h918:/storage/emulated/0 # chmod 777 *.zip
h918:/storage/emulated/0 # ls -al
drwxrwx--x 43 root sdcard_r 4096 Apr 1 22:35 .
drwx--x--x 4 root sdcard_r 4096 Jan 1 2016 ..
-rw-rw---- 1 root sdcard_r 2557 Apr 1 20:20 .bash_history
drwxrwx--x 3 root sdcard_r 4096 Mar 14 19:35 .rr
-rw-rw---- 1 root sdcard_r 1369542927 Apr 1 22:28 01update.zip
-rw-rw---- 1 root sdcard_r 884357956 Apr 1 22:34 02update.zip
-rw-rw---- 1 root sdcard_r 1057588047 Apr 1 22:41 03update.zip
drwxrwx--x 2 root sdcard_r 4096 Mar 9 23:06 3DMarkAndroid
drwxrwx--x 2 root sdcard_r 4096 Mar 4 18:20 Alarms
...
The permissions remain unchanged, why I'm root I should be able to change permissions.
looking at mount the options are:
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
The SD card looks similar:
/dev/fuse on /storage/ea8c26be-fcbc-4773-b799-5e64ef33f641 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/ea8c26be-fcbc-4773-b799-5e64ef33f641 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/ea8c26be-fcbc-4773-b799-5e64ef33f641 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Nothing here should block ROOT from change the permissions. I simply want as root or as any root application to be able to create a directory change file permission and access data written as another root app, all of which make it possible to use the phone and backup/restore safely.
I can only assume something is blocking me form using the device the way I want and operating on files, since pulling the card to a computer allows setting 777 and then it works as I want, what I want is to set the umask to 777 for everything, as for security that can be damned as I need to be able to backup and restore safely first, something I can not do now as Tibackup can not access it's own files on restore unless I first pull the card and set the permissions on a computer, which is unacceptable.
Files created on the phone have permissions 700 or something similar, even though on the phone they are listed as having more, this explains the issue as it is not for instance: -rw-rw---- but -rw-------, however root should still be able to access the file and can not, nor can root change the settings.
ERIC