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.
Related
I've seem many threads about it, but couldn't really find a solution.
I just pulled out my sdcard to do some updates in my rom (I was running Th3Bill's miui v4).
I've copied a couple of .zips to try, and when I inserted back, my I /sdcard wasn't mounting.
I've tried to format in windows (fast and normal mode); I've putted this very same card in my tabled (xoom2 me) and it was working fine.
I've tried to run format /sdcard in cwm. same error mounting;
I went to advance > show log:
CWM-based Recovery v5.0.2.7-atrix5
Error mounting /sdcard!
ro.bootloader=unknown
ro.hardware=olympus
ro.revision=33776
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand. file not found...
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory)
W:failed to mount /dev/block/mmcblk1 (No such file or directory)
Error mounting /sdcard!
I've tried some stuff on adb (someone mentioned it, not sure what it means):
C:\Users\Neon\Documents\Android\Auto stuff>adb shell ln -n -s /data/media /sdcar
d
ln: /sdcard/media: File exists
C:\Users\Neon\Documents\Android\Auto stuff>adb shell ls -a -l
drwxr-xr-x 21 root root 0 Aug 7 02:15 .
drwxr-xr-x 21 root root 0 Aug 7 02:15 ..
drwxr-xr-x 2 root root 0 Aug 7 02:15 boot
drwxrwx--x 5 system cache 4096 Aug 7 01:43 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Aug 7 02:15 datadata
-rw-r--r-- 1 root root 3875 Jan 1 1970 default.prop
drwxr-xr-x 9 root root 3260 Aug 7 02:15 dev
drwxr-xr-x 2 root root 0 Aug 7 02:15 emmc
drwxr-xr-x 2 root root 0 Aug 7 02:15 etc
-rwxr-x--- 1 root root 94404 Jan 1 1970 init
-rwxr-x--- 1 root root 783 Jan 1 1970 init.rc
drwxr-xr-x 2 root root 0 Aug 7 02:15 osh
drwxr-xr-x 2 root root 0 Aug 7 02:15 pds
drwxr-xr-x 2 root root 0 Aug 7 02:15 preinstall
dr-xr-xr-x 95 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 Sep 5 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Aug 7 02:15 sd-ext
drwxr-xr-x 2 root root 0 Aug 7 02:16 sdcard
drwxr-xr-x 14 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Aug 7 02:15 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 9731 Jan 1 1970 ueventd.olympus.rc
-rw-r--r-- 1 root root 4078 Jan 1 1970 ueventd.rc
What do I need to do?
Maybe is there some pins not working in my phone? Because I've tried another micro sd and got same error!
Thanks in advance!
Sounds like you really do have some issues with the built-in card slot. Try inspecting it visually, maybe there is some visible damage. Other than that, I'm not sure what can you do... Maybe claim warranty on it?
You should also never run random commands if you don't have at least some idea what they do. Those commands have nothing to do with fixing the sdcard, luckily for you they didn't work.
ravilov said:
Sounds like you really do have some issues with the built-in card slot. Try inspecting it visually, maybe there is some visible damage. Other than that, I'm not sure what can you do... Maybe claim warranty on it?
You should also never run random commands if you don't have at least some idea what they do. Those commands have nothing to do with fixing the sdcard, luckily for you they didn't work.
Click to expand...
Click to collapse
Well, Actually those commands weren't trying to fix it, and I know what ls does, I wasn't much sure about how ln works, but I know that it wouldn't damage my stuff.
I just checked some stuff here, it seems to be a hardware issue indeed, when I put my nail under the card, it reads! Unfortunately I can't claim warranty. I bought this phone used, via ebay, like and year ago, from a seller in USA (I'm in Brazil). I'll try to arrange some workaround (maybe some paper under it might work,...) and hope it works properly.
Hi all,
I'm just hacking at my rk3188 box, and trying to get XBMC to read my ext4 external hard drive.
However when the hard drive is mounted, XBMC only sees an empty directory!
Also, in the terminal, "su'ing" as an app user, the directory appears empty also.
This worked perfectly with android 4.2, 4.4 seems be more troublesome.
Code:
[email protected]_872xu:/ # ls -ailrt /mnt/usb_storage/usb/
3222 dr-xr-xr-x 3 media 1023 60 Sep 9 11:32 ..
10959 -rw-rw-rw- 1 root root 0 Sep 9 11:35 testing
8841 drwxrwxrwx 2 media root 60 Sep 9 14:18 .
[email protected]_872xu:/ # mount -t ext4 /dev/block/sda1 /mnt/usb_storage/usb
[email protected]_872xu:/ # ls -l /mnt/usb_storage/usb/backup/
-rwxrwxr-x 1 root root 2147483648 Sep 9 11:20 arch.img
drwxrwxrwx 2 root root 4096 Sep 7 17:30 init.d
[email protected]_872xu:/ # su - app_65
[email protected]_872xu:/ $ ls -l /mnt/usb_storage/usb/backup/
/mnt/usb_storage/usb/backup/: No such file or directory
1|[email protected]_872xu:/ $ ls -l /mnt/usb_storage/usb
-rw-rw-rw- root root 0 2014-09-09 11:35 testing
dmarkey said:
Hi all,
I'm just hacking at my rk3188 box, and trying to get XBMC to read my ext4 external hard drive.
However when the hard drive is mounted, XBMC only sees an empty directory!
Also, in the terminal, "su'ing" as an app user, the directory appears empty also.
This worked perfectly with android 4.2, 4.4 seems be more troublesome.
Code:
[email protected]_872xu:/ # ls -ailrt /mnt/usb_storage/usb/
3222 dr-xr-xr-x 3 media 1023 60 Sep 9 11:32 ..
10959 -rw-rw-rw- 1 root root 0 Sep 9 11:35 testing
8841 drwxrwxrwx 2 media root 60 Sep 9 14:18 .
[email protected]_872xu:/ # mount -t ext4 /dev/block/sda1 /mnt/usb_storage/usb
[email protected]_872xu:/ # ls -l /mnt/usb_storage/usb/backup/
-rwxrwxr-x 1 root root 2147483648 Sep 9 11:20 arch.img
drwxrwxrwx 2 root root 4096 Sep 7 17:30 init.d
[email protected]_872xu:/ # su - app_65
[email protected]_872xu:/ $ ls -l /mnt/usb_storage/usb/backup/
/mnt/usb_storage/usb/backup/: No such file or directory
1|[email protected]_872xu:/ $ ls -l /mnt/usb_storage/usb
-rw-rw-rw- root root 0 2014-09-09 11:35 testing
Click to expand...
Click to collapse
No ideas?
This thing has been a thorn in modding my phone ever since I rooted it - root has no read access to sdcard0 at all.
Whenever the external sdcard is mounted, root can only access sdcard1 after adding media_rw group to android.permission.WRITE_EXTERNAL_STORAGE, which works OK most of the times but there are some apps that rely on working with an external sdcard and root together unfortunately. Whenever the external sdcard is unmounted, same things happen with it - no access as root whatsoever. (user has full access)
Something of particular interest is the output of ls -l:
Code:
[email protected]_M3:/storage $ ls -l
drwxrwx--x root sdcard_r 1970-01-01 01:00 sdcard0
drwxrwx--x root sdcard_r 2015-08-10 02:48 sdcard1
[email protected]_M3:/storage $ su
[email protected]_M3:/storage # ls -l
drwx------ root root 2015-08-10 02:47 sdcard0
drwxrwx--x root sdcard_r 2015-08-10 02:48 sdcard1
[email protected]_M3:/storage #
and I don't really know where to begin to fix it. The stock ROM is doomed from the start with this it seems...
For the record; I'm using SuperSU and I have tried formatting my (2GB) sdcard to FAT32 and it didn't work.
Just restore the file tonoriginal data and use an app to do this.
Foldermount will work best.
Try this with thd help of this app ypu can read both sd cards at same time and keep game heavy data on sdcard as well
Sent from my SM-G355H using XDA Free mobile app
lolwhat file are you even talking about? Nothing has been touched there and that output of ls -l shows the permissions aren't as they're supposed to be for root.
FolderMount isn't exactly the thing I'm looking for. I need to fix permissions for root's access to the sdcard0 folder, plain and simple. For instance - I can't install Viper4Android because of this (though oddly I did manage to do it earlier, some black magic I did and don't remember lol). It wouldn't bother me if the sdcard folder in the ramdisk wasn't linked to the sdcard0 folder or if the permissions weren't tampered with and they were it seems.
I feel like as if I would have an easier time porting Cyanogenmod to my device than figuring this out...
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