Hi,
I was looking at my phone file structure and I see that the apk's that are part of the Rom are stored in /system/app but Ican't see where apk's installed from the Market get installed too. Can anyone explain please ?
Cheers
check data/app
/data/ is empty ?
gudge said:
/data/ is empty ?
Click to expand...
Click to collapse
Usually they go to:
/data/app and /data/app-private
but if you use apps2sd they go to:
/system/sd/app and /system/sd/app-private
shelnes said:
Usually they go to:
/data/app and /data/app-private
but if you use apps2sd they go to:
/system/sd/app and /system/sd/app-private
Click to expand...
Click to collapse
Thanks for the reply.
Its really strange then, as I don't have apps2sd, but muy /data/ directory is empty (according to Astro), yet I have at least 30 market installed apk's.....so where the hell can they be !
gudge said:
so where the hell can they be !
Click to expand...
Click to collapse
Exactly where they are supposed to be! /data/apps
The issue seems to be Astro - in Astro, my /data directory is empty, but using SUFBS it is not.
Regards,
Dave
astro wont help here.
open comand line from windows
using "cd" command go to AndroidSDK\tools
In my case it's " cd c:\AndroidSDK\tools"
then: "adb shell"
then "cd data\app"
and to see content of data\app type "ls"
Thanks
OK, thanks all, I can see the apk's now. I had not considered that Astro might not be displaying the contents. I tried the adb method and also downloaded SUFBS (its called SU File Manager & Terminal on the market now).
Cheers
/data is only readable for the user "system":
drwxrwx--x 1 1000 1000 2.0K Feb 19 12:19 data
that's why you don't see anything. you need an app that looks with root rights into this directory to see the contents.
kendong2 said:
/data is only readable for the user "system":
drwxrwx--x 1 1000 1000 2.0K Feb 19 12:19 data
that's why you don't see anything. you need an app that looks with root rights into this directory to see the contents.
Click to expand...
Click to collapse
Thanks, now I get it
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...
I am using DeFrost 9.0b with spare parts that lets you install apps on the sdcard. I am trying to backup all my apps that I downloaded and installed but I can't find them on the sdcard with root explorer.
Does anyone know where on the sdcard the apps are downloaded?
look in the android secure folder on the root of the SD card
Nekromantik said:
look in the android secure folder on the root of the SD card
Click to expand...
Click to collapse
I did and it is empty. ???
Sandule said:
I did and it is empty. ???
Click to expand...
Click to collapse
that is where they are meant to be.
So I dunno where else it could have placed them.
Nekromantik said:
that is where they are meant to be.
So I dunno where else it could have placed them.
Click to expand...
Click to collapse
Could it be a permission issue. I can't seem to change the permissions for the .android_secure folder. Is there a specific way that I need to change permissions in root explorer?
Did you direct the apps to the correct location with pm SetInstallLocation 2?
As suggested, the apps should be inside encrypted files within the /sdcard/.android_secure folder, whose contents are visible in recovery mode only.
So how can I get to the files then?
Should also work by using a Terminal Emulator.
Go to the Android Market, download an app called "ConnectBot".
Sign in to it, set is to local.
try the following (enter these commands):
su
ls -l /sdcard/.android_secure
I think you could also install Apps2SD using the Terminal Emulator with these commands:
su
pm setInstallLocation 2
Let me know if that helps at all.
Regards,
Mas.
I have already performed the setinstallLocation 2
When I do the ls command nothing comes up.
Not sure then mate
May be worth trying a full wipe again, re-flashing the rom and installing A2SD?
-------------------------------------
Sent via the XDA Tapatalk App
Its really bothering me. When flashing a Rom in the aroma I choose this red theme I never used. Well in the vrtheme folder on my SD card (internal storage) there is a bunch of. PNG files that show up in my gallery. If I try to delete from gallery they just come back. And if try to delete from file explorer with root permissions. It says file can not be deleted. This doesn't make sense or am I missing something?
Help would be appreciated.
Thank you
Give this a shot (assuming you are rooted)
find the folder they are in (for arguments' sake let's say they are in /storage/sdcard0/vrtheme/
download terminal emulator app
open it and type the following commands without quotes...
"su"
"rm /storage/sdcard0/vrtheme/*.png"
see if they are gone now.
Admiral Sir Manley Power said:
Give this a shot (assuming you are rooted)
find the folder they are in (for arguments' sake let's say they are in /storage/sdcard0/vrtheme/
download terminal emulator app
open it and type the following commands without quotes...
"su"
"rm /storage/sdcard0/vrtheme/*.png"
see if they are gone now.
Click to expand...
Click to collapse
Thank for trying to help. But if I go to directory all the way down to the PNG file I would have to repeat like 150 times
But anyways when I tried it. I was granted rights for su. Then received the # in terminal.
Then I did rm followed by file path.
It said permissions denied :/
Just wanted to report my findings. If you do a search for aroma file manager on xda. With that you can delete anyfile on SD card if given operation denied with any normal file explorer with root access.
FYI - sdcard0 is not really your SD Card at all. sdcard0 is the internal storage memory. extSdCard is your actual SD Card. And UsbDriveA, UsbDriveB, etc.. are your external drives like USB thumb drive, USB external drive, etc.
If you deleted file/s and then later came back that is because the file/s are being put back with the related app/s that the file/s are related too. Deal with the related app/s in order to stop the deleted file/s from reappearing.
If you can't delete the file/s at all then change the permissions of the file/s you want to delete and/or change the permissions with the folder that holds the file/s to be deleted. Then you can delete the file/s. You can change permissions with a file manager like Root Explorer, though you need to be rooted to change some permissions. Be careful. Deleting the wrong file/s can make your device bricked.
---------- Post added at 01:08 PM ---------- Previous post was at 12:34 PM ----------
trevor7428 said:
Thank for trying to help. But if I go to directory all the way down to the PNG file I would have to repeat like 150 times
But anyways when I tried it. I was granted rights for su. Then received the # in terminal.
Then I did rm followed by file path.
It said permissions denied :/
Click to expand...
Click to collapse
You wouldn't have to delete each .png file separately. Just type exactly what Admiral Sir Manley Power typed. The line command he wrote uses the wild card ( * ) so the command would delete all .png files within that folder at the same time.
Change the permissions of the folder that holds the files. Then try it. Make sure the app related to the files are not still caching the files. Caching the files would make the files to be currently in use. That would make the files not available to be deleted. You can also use another theme app, force kill the app related to the .png files, then delete the files. Then go back to that theme app.
JaguarXT said:
FYI - sdcard0 is not really your SD Card at all. sdcard0 is the internal storage memory. extSdCard is your actual SD Card. And UsbDriveA, UsbDriveB, etc.. are your external drives like USB thumb drive, USB external drive, etc.
If you deleted file/s and then later came back that is because the file/s are being put back with the related app/s that the file/s are related too. Deal with the related app/s in order to stop the deleted file/s from reappearing.
If you can't delete the file/s at all then change the permissions of the file/s you want to delete and/or change the permissions with the folder that holds the file/s to be deleted. Then you can delete the file/s. You can change permissions with a file manager like Root Explorer, though you need to be rooted to change some permissions. Be careful. Deleting the wrong file/s can make your device bricked.
Click to expand...
Click to collapse
I no SD card should be external. But on our note 2 the directory for internal is labeled SD card. Then vrtheme was in a folder named. " 0" I tried to change permissions and even the owner of file and folder, but it wouldn't let me with root permissions. That's why I was so stumped I had to post on xda.
And its not that the file would get deleted then put back it was I couldn't delete at all. There was no app to my knowledge for vrtheme.
trevor7428 said:
Thank for trying to help. But if I go to directory all the way down to the PNG file I would have to repeat like 150 times
But anyways when I tried it. I was granted rights for su. Then received the # in terminal.
Then I did rm followed by file path.
It said permissions denied :/
Click to expand...
Click to collapse
try this instead...
rm -f /storage/sdcard0/vrtheme/*.png"
if that doesn't work... try this....
chmod 777 /storage0/vrtheme
chmod 777 /storage0/vrtheme/*.png
rm -rf /storage/storage0/vrtheme
Admiral Sir Manley Power said:
try this instead...
rm -f /storage/sdcard0/vrtheme/*.png"
if that doesn't work... try this....
chmod 777 /storage0/vrtheme
chmod 777 /storage0/vrtheme/*.png
rm -rf /storage/storage0/vrtheme
Click to expand...
Click to collapse
I thanked everyone who replied, but I actually got it figured out. I flashed this zip file in recovery called aroma file manager. While let me delete whole folder from recovery. I appreciate all who helped.
I'm at bit of a loss here. Been rooting and all that for quite a long time.
Anyway, my freind has a mobile network not found error, upon investigation, it appeared he has *4999* IMEI problem. Fortuately, it appears he has EFS folder back up. I'm trying to restore it etc, but just am unable to create any folders in the internal memory of the phone, I'm rooted and on latest omnirom.
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Using root explorer, go to "efsbackup folder, select all files & folders there, and click Copy.
Still in root explorer, go to "efs" folder of your device(It is located where all main folders like data, system, etc.).
In "efs" folder, click paste. It will ask you if you want to replace your files, select replace to all files(So all your files from "efsbackup" folder will be in "efs" folder)
Now open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Now write:
Code:
busybox chown 1001:1001 /efs/nv_data.bin
Then click enter.
Now write:
Code:
busybox chmod 06755 /efs/nv_data.bin
Then click enter.
Reboot device. Now everything should work.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2389426
Please help
[SOLVED]
Just tried another program from playstore called 'Root Browser'
phrozenflame said:
[SOLVED]
Just tried another program from playstore called 'Root Browser'
Click to expand...
Click to collapse
Ok apparentely it copies the files but not the folders or i cant see the original folders and it copies them with 'folderame-copy' affix :|
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??