Greetings, is it possible to mount something only for one specific application ?
Is it possible to mount read only a folder inside data partition ?
I would like to lie to an application to make it look like nothing exist at some path.
I usually did it using xprivacy but this project is not maintained anymore and doesn't work properly on Android 6.
Considering mounting namespaces are used in Android, it should be possible, just don't know how to get that result.
Related
I understand that the solution to this question may already exist in the forums, however, I did check high and low for it, and was unable to locate one.
Here goes:
I like (as I'm sure others do) to install apps2sd, something I'm able to do thanks to the actively-rooted and cyanogen-modded N1 that I use.
Unfortunately, the actual *install* files *themselves* from all Market-downloaded apps seem to remain in the phone's internal memory, clogging up preciously limited space. How do I get rid of these install files? I tried using a file manager to go into the mnt/asec directory to get rid of *.pkg's, but these seem to be uninstall-protected (I'm not even sure if I'm making a mistake from the get-go in trying to purge the *.pkg's), so I'm kind of back to the drawing board on this one.
Any help on this would be pretty invaluable folks.
Thanks,
Eli
If you've installed a lot, your dalvik cache will grow pretty big. That's found in /data/dalvik-cache.
Thanks Rusty - but my /data dir is completely empty (unless there are invisible folders; if there are, who you know how I can make them visible?).
Best,
Eli
You need SU access to view /data, make sure what you're using to browse it supports that.
Ahh, thanks Rusty - will do that
Your DATA folder is inaccessible, unless you use Root Explorer or other file explorer with root privileges (ES Explorer, for example - but it doesn't work with all ROMs).
There are no PKGs. There are APKs. And you're wrong in your assumption that they aren't used. This is no PC, this is Android, forget what you used to know, you need to learn again. APKs are the actual applications being ran, without them you can't execute anything, and using old Apps2SD, AKA Apps2EXT, you can move your /data/data to SD (EXT partition) and /data/dalvik-cache to /cache. CM doesn't support Apps2EXT, but it can be easily installed and used, following the guide in DarkTremor's thread. Read Wiki in my sig, it'll point you in the right direction. You can start by reading FAQ, question 9.
seekingandroid said:
I understand that the solution to this question may already exist in the forums, however, I did check high and low for it, and was unable to locate one.
Here goes:
I like (as I'm sure others do) to install apps2sd, something I'm able to do thanks to the actively-rooted and cyanogen-modded N1 that I use.
Unfortunately, the actual *install* files *themselves* from all Market-downloaded apps seem to remain in the phone's internal memory, clogging up preciously limited space. How do I get rid of these install files? I tried using a file manager to go into the mnt/asec directory to get rid of *.pkg's, but these seem to be uninstall-protected (I'm not even sure if I'm making a mistake from the get-go in trying to purge the *.pkg's), so I'm kind of back to the drawing board on this one.
Any help on this would be pretty invaluable folks.
Thanks,
Eli
Click to expand...
Click to collapse
1) The .apk isn't the install file it _is_ the application. The are no "install only" parts to an android app
2) Anything on /mnt/asec is already on your sdcard using froyo-style a2sd
3) .so files in /data/data/xxx/lib and /data/dalvik-cache are the primary causes of full /data partitions
howdy yy'all
i have sucessfully upgraded my nexus 7 to 4.2 today but when using storage analyser i get error
unable to detect detect any valid sdcard or usb device
i have installed apps succesffuly with sd data being installed on the device
please can some advise the method i used for upgrade was
nexus toolkit
flashed stock 4.1.2 lost root and cwm
upgraded using tool kit to 4.2 and then reflashed root and cwm
same problem here... they prob just need to update something for 4.2... suspect an update will follow soon
The multi-user abilities in 4.2 are now causing havoc with some apps. used to be /data/media on 4.12. On 4.2, now the partition is /data/media/0/ for the 1st user, /data/media/1/ for the second, and so on and so on. If you're rooted, I think creating a symlink manually should fix this. I suggest you don't create other uses, just stick with the one for now, then you just need a single symlink from /data/media/0 back to just /data/media
There will need to be a lot of apps updated.....
rootbrain said:
The multi-user abilities in 4.2 are now causing havoc with some apps. used to be /data/media on 4.12. On 4.2, now the partition is /data/media/0/ for the 1st user, /data/media/1/ for the second, and so on and so on. If you're rooted, I think creating a symlink manually should fix this. I suggest you don't create other uses, just stick with the one for now, then you just need a single symlink from /data/media/0 back to just /data/media
There will need to be a lot of apps updated.....
Click to expand...
Click to collapse
I could not have said this any better. There will be Hundreds of not thousands of apps that will have to be updated.. Nearly any app that stores data without it having any logic for looking for where to store it at..
I Like the multi user . will create a guest user to keep prying eyes (my son ) off my tablet.
New software has bugs to work out.. this one going to have more then useual
erica_renee said:
I could not have said this any better. There will be Hundreds of not thousands of apps that will have to be updated.. Nearly any app that stores data without it having any logic for looking for where to store it at..
Click to expand...
Click to collapse
Any app which manually specifies a path, such as apps like Storage Analyzer must do in order to operate, should be few. The vast majority of apps ask Android to store the data and Android handles the path.
as xposed for nougat is already arrived officially many modules are not working
there is either File Based Encryption in data partition or by wiping data partition from twrp removes it
anybody able to read shared_prefs either with FBE or without it successfully so that it works properly,if that so please let us know how so that other module developers can fix their modules as well
the issue is that you can not read Preferences like used to before
HTML:
pref = new XSharedPreferences(BuildConfig.APPLICATION_ID);
so any values saved in shared_prefs can not be read by xposed at the moment on nougat atleast on galaxy s7 930F
i am looking for workaround,i tried putting prefs in /data/here it works but not so stable
This seems to work OK for me:
https://developer.android.com/refer...xt.html#createDeviceProtectedStorageContext()
https://developer.android.com/refer...renceManager.html#setStorageDeviceProtected()
I adjusted one of my modules to use Device Protected Storage and it seems to initialize preferences fine on FBE devices.
i need tester for this
because i am unable to boot if i flash magisk or supersu without formating data partition ,so i format /data partition and rooted which eventually remove encryption from /data partition so unable to test
i saw your commit but would be fine if i got tested with encrypted /data partition to test
C3C076 said:
This seems to work OK for me:
https://developer.android.com/refer...xt.html#createDeviceProtectedStorageContext()
https://developer.android.com/refer...renceManager.html#setStorageDeviceProtected()
I adjusted one of my modules to use Device Protected Storage and it seems to initialize preferences fine on FBE devices.
Click to expand...
Click to collapse
I have the same issue. To fix it, actually, we don't need to touch device protected storage. But we do need to set up the package folder permission and the preference file permission.
I set the folder to 711, and the file to 644. Then the preference works well. XSharedPreference.makeWorldReadable should set the file permission. And you may need to set up the folder permission manually with setExecutable(true, false).
guangyu.zhou said:
I have the same issue. To fix it, actually, we don't need to touch device protected storage. But we do need to set up the package folder permission and the preference file permission.
I set the folder to 711, and the file to 644. Then the preference works well. XSharedPreference.makeWorldReadable should set the file permission. And you may need to set up the folder permission manually with setExecutable(true, false).
Click to expand...
Click to collapse
The thing is OS automatically changes permissions of preference files back and removes readable flags. This happens when preferences are committed to the filesystem.
To work around this I had to implement a solution that tracks those changes and adjusts permissions as necessary.
https://github.com/GravityBox/Gravi...o/nougat/gravitybox/SettingsManager.java#L371
https://github.com/GravityBox/Gravi...ougat/gravitybox/WorldReadablePrefs.java#L157
C3C076 said:
The thing is OS automatically changes permissions of preference files back and removes readable flags. This happens when preferences are committed to the filesystem.
To work around this I had to implement a solution that tracks those changes and adjusts permissions as necessary.
https://github.com/GravityBox/Gravi...o/nougat/gravitybox/SettingsManager.java#L371
https://github.com/GravityBox/Gravi...ougat/gravitybox/WorldReadablePrefs.java#L157
Click to expand...
Click to collapse
Yeah, you're right. So we need to proactively set it readable to work around it.
By the way, Gravity Box is a great project. It helps me a lot on the exposed development.
Hello, Can i help me.
Android 7.1.1 (Nougat) can not be used XSharedPreference can not read the contents of the file,How to solve this problem?Thank you
Sorry for probably wrong-posting, but I need a solution _fast_!! Can anybody help me _please_?
I'm a Windows user, I don't really know much about Linux-based systems & thus am not able to interpret any logs or do Linux console commands and stuff... and the fbind readme / help isn't all that easy to understand for Linux-illiterates either. Problem:
I mounted a folder from my external SD card to my internal SD by adding the following line to the config.txt file:
from_to InternalFolder .externalfolder
This seems to _work_, my 'old' app (Maverick from Code Sector) now sees all map tile data that is actually on the external card within the internal folder & can access it.
However, after 2 days or so, the folder link suddenly seems to be 'gone' (internal folder shows as empty). Only solution is to reboot the phone, then all is back to normal again.
I already tried to turn off battery savings for the Magisk app and for Maverick, with had no effect.
Question: what could cause this 'disappearance' of an as it seems correctly bound folder? What could I do to keep such links 'alive' even when they are not used/accessed for a longer time? Is there an *easy way* to 'reset' fbind without rebooting the phone? Or did I forget an important command in the config.txt / should I add something beside the above line?
I'm running Android Marshmallow on a Samsung Galaxy S5 mini DuoS
Good day,
I recently discovered malware in the root directory under the / prism folder that installed an app called Yandex into my system and contained various hidden APKs. (and files with .sogou at the end).
These manipulated my internet browser in some way and I was only able to remove them by flashing the stock rom.
Now I get the message from TWRP that the partition / prism could not be mounted. Even so, everything seems to be working fine on the device.
Now there is no more content in the / prism directory. What is usually stored there and what is its purpose?
Do I have to rework something?
I can't find an explanation anywhere else on the Internet ...
Thank you and best regards
According to https://github.com/PrismLibrary/Prism
Prism provides an implementation of a collection of design patterns that are helpful in writing well-structured and maintainable XAML applications, including MVVM, dependency injection, commands, EventAggregator, and others.
Click to expand...
Click to collapse
In short Prism is a framework to build applications which in turn it's built on top of another framework called Xamarin (XAML for Android).
As of why it's in the root directory I suspect is part of AppCloud, Samsung's system app, that basically does remote installation of apks.
If it is correlated to AppCloud (Big IF) then:
If you are rooted and on stock OS and have that app enabled it's not far fetched to think that there is an exploit for it out there and basically anyone could remote install any APK through root privileges and the backdoor that AppCloud system app gives the.
It's could be as easy as editing a file from within the malicious app which could change the behaviour and URL from which it fetches the needed apks. Whereas installing apks from within the malicious app needs explicit OS permissions (which AppCloud has).
I too had apps installed post-upgrade by the AppCloud system app, but I don't have root to analyse this further so all the above are just speculations based on the two things you said and my previous observations.
In the end you could have contracted the malware in a million different ways. That's how it goes with root access on OS and careless root management.
I have to admit that I was too careless with root privileges and experimented with little knowledge.
Hope that helps others to deal with it more intensively beforehand.
Your explanation helped me, the problem is a bit more serious, it is probably about corrupt security certificates in the system that are administered from outside
In this case, is it even possible to reset or delete the CA certificates? I guess I fell into a spoofing trap.
Maybe flash the stick rom again through Odin?
Is that embarrassing: D
Sorry for the graveyard post but I don't see any other threads about this.
Prism is the name of the NSA surveillance program. I guess that this is exactly that.
It's hidden because you can only see that it exists with root and most people don't have root.
I have this folder too on my rooted Galaxy Fold 4. It was already in the stock ROM and I cannot remove it because the directory is mounted as read only.
If found the mounts file (which is also read-only) and it says:
Code:
/dev/block/platform/soc/1d84000.ufshc/by-name/prism /prism ext4 ro,seclabel,relatime,i_version 0 0
I tried to give me the permission to write / delete the folder but "permission denied" ... and yes I did that as root.
Nexariuss said:
Sorry for the graveyard post but I don't see any other threads about this.
Prism is the name of the NSA surveillance program. I guess that this is exactly that.
It's hidden because you can only see that it exists with root and most people don't have root.
I have this folder too on my rooted Galaxy Fold 4. It was already in the stock ROM and I cannot remove it because the directory is mounted as read only.
If found the mounts file (which is also read-only) and it says:
Code:
/dev/block/platform/soc/1d84000.ufshc/by-name/prism /prism ext4 ro,seclabel,relatime,i_version 0 0
I tried to give me the permission to write / delete the folder but "permission denied" ... and yes I did that as root.
Click to expand...
Click to collapse
did you ever find anymore about this? ive found it on two of my phones. both samsung. cant find much online about it...