Never mind.
Should have done my homework before posting.
Apparently it has something to do with app encryption in JB.
But still, I could successfully copy the pkg.apk from the asec mount and install it later on.
============================================================================
Hope this is not a repost.
I am running CM10.1. I think the stock does the same.
Can anybody educate me why Android decide to install the apps into the mounted asec device /dev/block/dm-XX rather than /data/app after a few apps installed?
What is the benefit of doing this?
My understanding is that this is for the phones that has external SD card.
On galaxy nexus we have none. Unless there is performance benefit, I don't see the point of doing this.
Is there an easy way to revert them back to the /data/app?
Thanks a lot.
chinabull said:
Never mind.
Should have done my homework before posting.
Apparently it has something to do with app encryption in JB.
But still, I could successfully copy the pkg.apk from the asec mount and install it later on.
============================================================================
Hope this is not a repost.
I am running CM10.1. I think the stock does the same.
Can anybody educate me why Android decide to install the apps into the mounted asec device /dev/block/dm-XX rather than /data/app after a few apps installed?
What is the benefit of doing this?
My understanding is that this is for the phones that has external SD card.
On galaxy nexus we have none. Unless there is performance benefit, I don't see the point of doing this.
Is there an easy way to revert them back to the /data/app?
Thanks a lot.
Click to expand...
Click to collapse
How did you pull the app?
First you have root your phone to do this. (Assuming you have done it already).
For example, I had "world of goo" installed.
[email protected]:/ # mount |grep goo
/dev/block/dm-2 /mnt/asec/com.twodboy.worldofgoofull-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
Then you go directly to the asec mounted directory:
[email protected]:/ # cd /mnt/asec/com.twodboy.worldofgoofull-1
[email protected]:/mnt/asec/com.twodboy.worldofgoofull-1 # ls -l
drwxr-xr-x system system 2012-12-08 01:47 lib
drwx------ root root 1969-12-31 19:00 lost+found
-rw-r----- system all_a113 48148276 2012-12-08 01:47 pkg.apk
-rw-r--r-- system system 117558 2012-12-08 01:47 res.zip
The pkg.apk is the one you want.
Cheers!
Related
Hi all,
couple of questions I hope somebody can answer for me ?
1. If I connect my Hero phone to my XP PC and run adb shell and then SU so I get the # prompt, what user am I logged in as ? is it root ? I tried whoami command but it was not a recognised command.
2. What is special about the system directory, because if I try and do
#chmod 777 system
I get this error: Unable to chmod system: Read-only file system
but no problem if I do same command to the sys directory. Both sys and system have same file permissions:
drwxr-xr-x root root 2009-08-27 03:51 system
drwxr-xr-x root root 1970-01-01 01:00 sys
so what makes the system directory a Read-only file system ?
I hope this makes sense, I'm only just starting to dabble with this linux stuff.
The answer to the first question is you are indeed logged in as root, su will(...should...) log you in as root for the entire session.
with # you are root. the id command works.
/system is the "rom" part, it should not be changed and therefore is usually mounted RO. you can remount it RW with the usual mount options or adb remount. why would you want to change the permissions of the folder? i don't think it's good idea tbh, you should not mess with system files unless you know what you are doing.
kendong2 said:
with # you are root. the id command works.
/system is the "rom" part, it should not be changed and therefore is usually mounted RO. you can remount it RW with the usual mount options or adb remount. why would you want to change the permissions of the folder? i don't think it's good idea tbh, you should not mess with system files unless you know what you are doing.
Click to expand...
Click to collapse
OK, thanks for explaining. tbh I was just seeing what I could and could not do, I will take your advice and not mess with the system files any more.
So the read only thing, is to do with mounting rather than file permissions from what you say. I think I need to read up on the subject.
Cheers
gudge said:
OK, thanks for explaining. tbh I was just seeing what I could and could not do, I will take your advice and not mess with the system files any more.
So the read only thing, is to do with mounting rather than file permissions from what you say. I think I need to read up on the subject.
Cheers
Click to expand...
Click to collapse
do whatever you like, i learned most of what i know by trial&error just be prepared to break it, never go without a backup...
Ok, so whats the deal!?
There's no SD card in the Gnex, so it has this "virtual SD CARD" which is simply a folder in the filesystem right?
Therefore, if I format the phone, it should also format the /sdcard/ directory too right?
I thought so! But no?
How reliable is this "virtual sdcard" and by what means can it be formatted??
When am I in danger of losing information on it, and when can I be sure it wont be formatted?
Normally I would just pop it out if I was afraid it would get formatted.
Also why doesnt the camera folder get erased when doing a format!?
TL;DR
Please explain
How the /sdcard/ works and in what situations am I in danger of formatting it?
Does a "nandroid" backup back up this part of the phone??
Why do certain directories not get erased when I factory reset my phone? Whats the rhyme & reason behind this?
Maybe explain the camera and screenshot folders too?
Factory resetting from the stock recovery will wipe the /data/media/ directory.
All custom recoveries will wipe /data/ while ignoring /data/media/ (thus leaving it intact).
Anything you have on your "SD card" will be saved into /data/media/.
That includes pictures, nandroids, downloads, etc.
And no, nandroids do not back this up.
Seems like a close enough thread for question without starting a new one. My nexus is reporting 2gb used for apps, 1.5 for pictures/video, 3gb free and 13gb total. So where did I lose 7gb? I can't seem to locate this other 7gb of used space. When I use root explorer it seems my sdcard shows twice once as sdcard and another time as sdcard0. Any ideas what I can do to get space back?
Sent from my Galaxy Nexus using xda premium
mr mystery said:
Seems like a close enough thread for question without starting a new one. My nexus is reporting 2gb used for apps, 1.5 for pictures/video, 3gb free and 13gb total. So where did I lose 7gb? I can't seem to locate this other 7gb of used space. When I use root explorer it seems my sdcard shows twice once as sdcard and another time as sdcard0. Any ideas what I can do to get space back?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Flashed many ROM's?
Herman76 said:
Flashed many ROM's?
Click to expand...
Click to collapse
Ya I've flashed a lot AOKP builds before wiping and going to JB. Any idea how I can get my space back?
Sent from my Galaxy Nexus using xda premium
mr mystery said:
Ya I've flashed a lot AOKP builds before wiping and going to JB. Any idea how I can get my space back?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Same here.
Since JB i have sdcard0 as well, and it seems to have the same data as the other...
yalouf said:
Same here.
Since JB i have sdcard0 as well, and it seems to have the same data as the other...
Click to expand...
Click to collapse
Yeah, exactly same
Sent from my Galaxy Nexus using xda premium
Does anyone know if superwipemwould help here, I've never used it but if it will get me storage back in order I'll give it a go.
mr mystery said:
Does anyone know if superwipemwould help here, I've never used it but if it will get me storage back in order I'll give it a go.
Click to expand...
Click to collapse
Why not just try wiping your Dalvik cache and see what happens?
ya tried that already
I'm short 7gb any ideas would be much appreciated, can I format it somehow and then flash again somehow or would formatting the whole drive be a bad thing???
I was playing in gallery in JB, and noticed my pictures save to sdcard0
Related?
Anybody with a standard (can be rooted ROM) ICS rom post the terminal output of this two commands please.
df
ls -l /
The reason is that my sdcard card is linked to /storage/sdcard0 so I want to check how is mounted on ICS and so that I may fix this as I have the same issue
jjarrin said:
Anybody with a standard (can be rooted ROM) ICS rom post the terminal output of this two commands please.
df
ls -l /
The reason is that my sdcard card is linked to /storage/sdcard0 so I want to check how is mounted on ICS and so that I may fix this as I have the same issue
Click to expand...
Click to collapse
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 346M 48K 346M 4096
/mnt/asec 346M 0K 346M 4096
/mnt/obb 346M 0K 346M 4096
/system 643M 253M 390M 4096
/data 13G 7G 5G 4096
/cache 425M 55M 369M 4096
/factory 19M 8M 11M 4096
/mnt/sdcard 13G 7G 5G 4096
[email protected]:/ $ ls -l /
drwxr-xr-x root root 2012-07-05 08:49 acct
drwxrwx--x system cache 2012-07-04 17:55 cache
-rwxr-x--- root root 245720 1970-01-01 01:00 charger
dr-x------ root root 2012-07-05 08:49 config
lrwxrwxrwx root root 2012-07-05 08:49 d -> /sys/kernel/debug
drwxrwx--x system system 2012-07-01 13:22 data
-rw-r--r-- root root 120 1970-01-01 01:00 default.prop
drwxr-xr-x root root 2012-07-05 08:49 dev
lrwxrwxrwx root root 2012-07-05 08:49 etc -> /system/etc
drwxrwxr-x radio radio 2011-11-29 22:27 factory
-rwxr-x--- root root 98868 1970-01-01 01:00 init
-rwxr-x--- root root 2344 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 1324 1970-01-01 01:00 init.omap4pandaboard.rc
-rwxr-x--- root root 18533 1970-01-01 01:00 init.rc
-rwxr-x--- root root 7350 1970-01-01 01:00 init.tuna.rc
-rwxr-x--- root root 3532 1970-01-01 01:00 init.tuna.usb.rc
drwxrwxr-x root system 2012-07-05 08:49 mnt
dr-xr-xr-x root root 1970-01-01 01:00 proc
drwxr-xr-x root root 1970-01-01 01:00 res
drwx------ root root 2012-07-01 08:01 root
drwxr-x--- root root 1970-01-01 01:00 sbin
lrwxrwxrwx root root 2012-07-05 08:49 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-07-05 08:49 sys
drwxr-xr-x root root 2012-07-01 13:17 system
-rw-r--r-- root root 272 1970-01-01 01:00 ueventd.goldfish.rc
-rw-r--r-- root root 3825 1970-01-01 01:00 ueventd.rc
-rw-r--r-- root root 1656 1970-01-01 01:00 ueventd.tuna.rc
lrwxrwxrwx root root 2012-07-05 08:49 vendor -> /system/vendor
[email protected]:/ $
This is from CM9 nightly ROM.
Edit: Just realized you wanted the output from Standard ROM, disregard if this is different
Swiftkey'ed on my CM9 Galaxy Nexus
Thank you:good:
It seems that the way the system is creating the symbolic link to sdcard is either different on JB or is just messed up because for me it shows sdcard -> /storage/sdcard0 and the def shows /storage/sdcard0 as the mount point.
I'll try to change this to what is shown on your output. Maybe it will fix the issue.
Fingers crossed
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.
Environment: SG3 + recently up-ed to NC2 (rooted, as all the other previous images I used). Trying to get rid of the "camera click", as I've done it many times in the past, but in this instance here is what I'm experiencing:
[email protected]:/system/media/audio/ui # mv camera_click.ogg camera_click.old
failed on 'camera_click.ogg' - Read-only file system
[email protected]:/system/media/audio/ui # ls -l camera*
-rw-r--r-- root root 9520 2014-03-08 05:12 camera_click.ogg
-rw-r--r-- root root 4786 2014-03-08 05:12 camera_focus.ogg
[email protected]:/system/media/audio/ui # chmod 755 camera*
Unable to chmod camera_click.ogg: Read-only file system
Any ideas how to fix?
TIA
Sent from my SGH-T999 using Tapatalk
Root doesn't automatically change the file system from R/O to R/W. You still need to change it. Use a root file manager like root explorer to make it really easy to do.
And how did you root? Did you remove Knox? Knox, and sometimes seLinux will prevent root access.
Sent from my SM-N900T using Tapatalk
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
Did you try to set to r/w on the folder, rather than just the files?
Sent from my SM-N900T using Tapatalk
Thanks for replies, so far, but looking at the output again it just occurred to me that in fact this is mounted RO, rather than RW, which may explain why chmod fails... I wonder - should that be the case - if I could force a RW mounting of the file system, w/out bricking the phone.
Sent from my Nexus 7 using Tapatalk
netfortius said:
Thanks for replies, so far, but looking at the output again it just occurred to me that in fact this is mounted RO, rather than RW, which may explain why chmod fails... I wonder - should that be the case - if I could force a RW mounting of the file system, w/out bricking the phone.
Click to expand...
Click to collapse
# mount -o remount,rw /system ... duh! Sorry for all the noise
I'm rooted but for some reason every time I try to add notification sounds to system/product/media/audio/notifications using Root Explorer I get a failed to copy error.
Anyone found a way to do this?
I don't know if I'm missing something here but why don't you add it to the notification folder in your storage?
cky2000 said:
I don't know if I'm missing something here but why don't you add it to the notification folder in your storage?
Click to expand...
Click to collapse
Facebook messenger for some reason doesn't see them in storage and I'm trying to add a custom notification for it.
Also I'm wondering why I'm not able to add to system folders.
I noticed this as well I was trying to change the bootanimation.zip out and that specific folder will not let me r/w,,but I am rooted and it works every place else?
I've tried three different root explorers, and the product folder will not mount.
I'll keep trying and update if I find something that works.
Options seem TWRP file manager when available or adb.
Archangel said:
I noticed this as well I was trying to change the bootanimation.zip out and that specific folder will not let me r/w,,but I am rooted and it works every place else?
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk
I am guessing it is a Magisk thing since there are reports of it having difficulties with some apps.
micmars said:
I've tried three different root explorers, and the product folder will not mount.
I'll keep trying and update if I find something that works.
Options seem TWRP file manager when available or adb.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
bp328i said:
Facebook messenger for some reason doesn't see them in storage and I'm trying to add a custom notification for it.
Also I'm wondering why I'm not able to add to system folders.
Click to expand...
Click to collapse
If I add them to the notification/storage folder they do show up in fb messenger. They are at the bottom of the list. Same here cannot mount that one folder with whatever app I use. I tried 17.3 and 17.4.
cky2000 said:
If I add them to the notification/storage folder they do show up in fb messenger. They are at the bottom of the list. Same here cannot mount that one folder with whatever app I use. I tried 17.3 and 17.4.
Click to expand...
Click to collapse
I figured out my issue why it was not showing up. I did not grant messenger rights to storage.
Still weird about not being able to mount that one folder.
It has nothing to do with Root Explorer.
I too wanted to change out bootanimation (it's blindingly white).
So I tried ADB and it just kinda said "no".
Code:
C:\android>adb shell
crosshatch:/ $ su
crosshatch:/ # cd /
crosshatch:/ # dir
/system/bin/sh: dir: not found
127|crosshatch:/ # ls
acct default.prop init.rc lost+found product system
bin dev init.recovery.blueline.rc metadata res system_root
bugreports dsp init.recovery.crosshatch.rc mnt root ueventd.rc
cache etc init.recovery.sdm845.rc odm sbin vendor
charger firmware init.usb.configfs.rc oem sdcard
config init init.usb.rc persist sepolicy
d init.crosshatch.rc init.zygote32.rc postinstall storage
data init.environ.rc init.zygote64_32.rc proc sys
crosshatch:/ # cd product
crosshatch:/product # ls
app build.prop etc lost+found media priv-app
crosshatch:/product # cd media
crosshatch:/product/media # ls
audio bootanimation.zip
crosshatch:/product/media # rm bootanimation.zip bootanimation.old
rm ro bootanimation.zip (y/N):y
[B]rm: bootanimation.zip: Read-only file system[/B]
rm: bootanimation.old: No such file or directory
1|crosshatch:/product/media # ls
audio bootanimation.zip
crosshatch:/product/media #
lol just noticed it's read only.
I forgot to set the r/w command and can't remember it.
Might also need to set to permissive.
But right now I've gotta go watch some NCAA.
---------- Post added at 02:22 PM ---------- Previous post was at 01:50 PM ----------
I set it to permissive and tried both the old and newer rw commands but neither let me modify /system/product/media/ or /product/media/.
Code:
mount -o remount,rw /system
mount -o rw,remount /system
This is weird I have never seen a folder stay read only after being bootloader unlocked and rooted? Guess Google doesnt want us changing out that crazy white boot animation??