Hello,
I'm not sure this is the source of my problem but can someone post the content of his /etc/permissions/platform.xml file please? (on stock Android 5.02)
After trying the app "GL to SD" on my tablet, the internal memory /sdcard and equivalent folders (/storage/emulated/0, /storage/emulated/legacy, /storage/sdcard0) are not accessible.
I still see them in command line with ADB, but from the tablet the command line ls in /sdcard gives opendir failed: permission denied.
Or if you have any other idea...
Related
I'm using ADB and trying to move some files to system/etc (gps.conf to improve GPS signal) but everytime I try to mv in ADB shell it says it can't find the file I want to mv from /sdcard/ to /system/etc/
I've mounted the SD Card by typing mount sdcard and can see the file in ADB shell when typing ls.
What am I doing wrong?
I've got it to work using Root Explorer. Just wondering why I couldn't get it to work using adb
Are you S-off, if not that is why it failed. Also if you are not S-off root manager didn't move anything to system (at least until you reboot) because you don't have write access to the system partition while booted.
So if you are S-on do it again but then with the phone in recovery and don't forget to mount the system partition as read/write.
Cheers!
Trying to copy over a file from my Linux machine onto my Galaxy Nexus using ADB. The file is in the platform-tools directory as well to make it easier. I am trying to execute "adb push gapps-ics-12172011.zip sdcard", but it keeps saying failed to copy 'gapps-ics-12172011.zip' to 'sdcard': Is a directory. Can someone help me out?
Code:
adb push gapps-ics-12172011.zip /sdcard
The way you had it did not specify a location, but a filename.
Thanks, I'll try this when I get home.
Sent from my Galaxy Nexus using XDA
Still did not work. Found the problem though, the sdcard was under /mnt, so I did /mnt/sdcard and it worked
glad it's working, but remember not to forget the / at the end if you are pushing files to a directory
/sdcard is just a symlink.
Stop directing people to a symlink, which may or not be available.
Folks, equivalent dir to /sdcard is /data/media.
bk201doesntexist said:
/sdcard is just a symlink.
Stop directing people to a symlink, which may or not be available.
Folks, equivalent dir to /sdcard is /data/media.
Click to expand...
Click to collapse
I am not about to start telling people to adb push to /data/media, when /sdcard works fine and is universal, symlink or not. If the symlink is missing, that is kind of their fault, not mine, and they have bigger fish to fry than adb push.
As mentioned above the issue was the lack of trailing /. This command should work:
adb push gapps-ics-12172011.zip /sdcard/
So here's the thing i've been exploring the possibilities of USBHost and decided to try an usb stick so i installed Paragon https://play.google.com/store/apps/details?id=com.paragon.mounter
It took me a while to get the hang of things. At first my usbstick was formatted in fat32. I specified in paragon i would like the default mount point to be USBStorage instead of /paragonNTFS. I made a small typo at first and named the folder usbStorage
now here comes the problem.
for some reason the app created 2 subfolders called sdb1 and sdb2 and i cannot remove them
Things i've tried:
cyanogenmod file manager in root access mode
-- delete directory > "This operation needs elevated permissions. Try switching to root access mode" (translated from dutch so wording may be a bit off
-- modifying permissions of folders > denied > changing permissions failed. for security reasons some filesystems, such as on sdcards do not allow changing permissions
Same problem for Astro file manager
Same problem when attaching the tablet to computer. parent directory (and sub dirs) get "removed" in windows but when checking the file system on the tablet, the opposite is true and the directories is still present
and now it's starting to piss me off. I want that folder "usbStorage" and it's subfolders "sdb1" and "sdb2" removed. so my guess is it'll have to be done by terminal commands but my terminal experience is ZERO.
in preperation of you guys helping me installed https://play.google.com/store/apps/details?id=jackpal.androidterm the same one used in cyanogenmod roms. I tried a bit of tinkering myself but prob doing something wrong
what i've tried (in sequence, --ok behind the command means it was succesfully executed)
su --ok
cd sdcard --ok
*rm -rf /usbStorage >> *rm: not found
rm -rf /usbstorage --ok, but folder was still present
rm -rf usbstorage --rm failed for usbStorage, Directory not empty
cd usbStorage --ok
rm -rf sdb1 --ok, rm failed for sdb1, Permission denied
at that point i gave up. I hope you guys can help me out
I do have paragon configured properly now and my USBstick in NTFS is getting recognised. Upon mounting of the usbstick, it now creates a folder called "USBStorage" where the contents of the usb stick is properly displayed.
so where are those android terminal / linux masters to help me out
only thing i can add is that when opening paragon with the stick attached but unmounted i do see a line above it /dev/block/sda1 but that doesn't seem to affect mounting in the specified directory
Bump, anyone? I want and need this folder removed
Verstuurd vanaf mijn Nexus 7 met Tapatalk
From my understanding of your post.
You are rooted and using cyanogenmod?
Did you try going into the app information and clear data?
In the app drawer hold the app and then drag it to App Info
Clear data.
Did that solve it? If not continue below.
Make sure you don't have the USB stick mounted and or plugged in.
Then go into terminal and type
su
Then type.
mount
The mount command shows all listed mount points. If you don't see the usbStorage or whatever mounted.
Then type.
busybox rm -rf usbStorage
Or whatever the main directory is...
For example directory is at.
/sdcard/usbStorage
cd /sdcard
rm -rf usbStorage
Let me know how you make out.
Sent from my Galaxy Nexus using xda app-developers app
nope, my phone is running CM 10.2 (not relevant to the question) this is the nexus section and its my nexus 7 2013 running stock rom but rooted yes that needs the folders removed.
The folders i need to delete according to the Nexus 7 mount main mount path SD content
main path: /storage/emulated/0 or /storage/emulated/legacy (both are the same according according to ParagonNTFS as a folder the mount path /sdcard/USBStorage = /storage/emulated/0/USBStorage or /storage/emulated/legacy/USBStorage
important lines?
/dev/fuse /storage/emulated/0/ fuse rw,nosuid,nodev,realtime, user_id=1023, default_permissions,allow_other 0 0
/def/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatimeuser,user_id=1023, group_id=1023,default_permissions,allow_other 0 0
folders to delete are
/storage/emulated/0/usbStorage
/storage/emulated/0/usbStorage/sdb1 <= can select these just fine
/storage/emulated/0/usbStorage/sdb2
/storage/emulated/0/ParagonNTFS <= simply selecting this folder prompts CM manager "this operation needs elevated priviledges. Try switching to rootmodus, even when the CM filemanager already is in root mode
so i went
Opening terminal
su
cd sdcard (command ok)
cd usbStorage (commando ok)
busybox rm -rf sdb1
rm: can't remove 'sdb1': permission denied
Then i tried
cd /sdcard
rm -rf usbStorage
rm failed for usbStorage, Directory not empty
cd usbStorage
rm -rf sdb1
rm failed for sdb1, Permisison denied
busybox rm -rf sdb1
rm: can't remove 'sdb1': Permision denied
According to Cyanogen mod file manager:
Filesysteminfo:
Status: rw
linkpath?: /storage/emulated/0
Device: /dev/fuse
Type: fuse
Options: rw,nosuid,nodev,relatime,user_id=1023,default_permissions,allow_other
Dump / Pass: 0 / 0
even with the app ParagonNTFS uninstalled it doesnt work
hmm
try
close the app ParoganNTFS and uninstall it.
then try to delete those directories.
Also when you type
mount
does it show any of the directories you are trying to delete as mounted?
if it is try
umount /sdcard/usbStorage/sdb1
rm -rf /sdcard/usbStorage/sda1
were you able to delete the dir?
I had the same problems under very similar circumstances. Stickmount rather than paragon. The only way I could delete the dir was to boot into recovery (team win recovery project v2.7.1.1) and delete it with TWRP's terminal command. Something in the OS apparently locks on to the mount and simply will not let it go ever. It has to be done before android starts. It's very annoying. I am beginning to really be disgusted with many of the decisions google is making with regard to android. Why do they hate sdcard expansion so much? its absurd.
---------- Post added at 04:22 AM ---------- Previous post was at 04:17 AM ----------
Oh and by the way, even though the OS latched on to that folder as if its very existence depended on it, I was never able to even see the files on the USB memory stick with any file explorer. Worked just fine in kit kat and before. In some ways lollipop really sucks.
Hello,
I tried to copy all data from an old phone to a new phone by using TWRP -> backup "/system" and "/data" partitions, then restore them in TWRP on a new phone, and then I found out that only applications were copied, but not my personal files (contents from folders "DCIM", "Documents", "Downloads", etc).
So then I did a "adb pull /sdcard/" from an old phone and uploaded it "adb push /sdcard/" to a new phone. But now most applications do not have write permissions over these folders, e.g. document viewer ("org.sufficientlysecure.viewer") and file manager ("org.joa.zipperplus7") could not delete files and folders, and even system application (LineageOS Updater) could not export update file. They have only read permissions (can open documents, etc). However some applications have write permissions - e.g. "Gallery" could delete old photos from "DCIM" directory.
I have checked simple Linux permissions and for /sdcard/* on both phones and they are same: 771 (drwxrwx--x) root:sdcard_rw for directories and 660 (-rw-rw----) root:sdcard for files. lsattr shows same attributes too. But apps on old phone have write permissions to /sdcard and apps on new phone have no permissions. Am I missing something?
Any ideas on how to fix this?
help
I checked 'ps' and saw that F-Droid app is running under user "u0_a75". I have verified the chmod of the path to cache, and all dirs from /sdcard/Android/data/org.fdroid.fdroid to /sdcard/Android/data/org.fdroid.fdroid/cache/apks/f-droid.org--1/ belong to "u0_a75" and have chmod drwxrwx--x u0_a75:sdcard_rw. But F-Droid could not download any app into that directory - it reports "permission denied". I have tried to chmod 777 for the whole path above but it did not help.
Then I thought it may be a SELinux problem, so I disabled it with "setenforce 0". Still no luck - most apps could not write to their storage.
What's going on?
P.S. I found out that Camera app writes files as a root user!
well, I gave up and reinstalled everything from scratch, wiping all partitions in advance.
I've recently did a factory reset, but before doing that I backed up the internal storage partition using
Code:
adb pull /dev/block/sda29
that is my partition for /data according to /cache/recovery/log generated by twrp.
Now I have this little (128GB) file inside my pc, I mounted it into a folder but entering media/0/ it say "Permission Denied" even if I access it using root user. I think is releted with android full encryption.
I tried using testdisk for finding other files and I found a bunch of random named files that testdisk fails to recover, but at least I get into the directory...
Someone can figure out how to access those files? thanks
topongo said:
I've recently did a factory reset, but before doing that I backed up the internal storage partition using
Code:
adb pull /dev/block/sda29
that is my partition for /data according to /cache/recovery/log generated by twrp.
Now I have this little (128GB) file inside my pc, I mounted it into a folder but entering media/0/ it say "Permission Denied" even if I access it using root user. I think is releted with android full encryption.
I tried using testdisk for finding other files and I found a bunch of random named files that testdisk fails to recover, but at least I get into the directory...
Someone can figure out how to access those files? thanks
Click to expand...
Click to collapse
it could be the file extension, windows will not read ext4 files unless you download a tool, linux supports it so you could try mountiong the file on linix or with ext4 app reader (you probably wont be able to modify the data)