Apps have always required the WRITE_EXTERNAL_STORAGE privilege in order to modify files in the internal file storage or SD card, but they could read files from these places without any privileges. Apparently, in Jelly Bean they added READ_EXTERNAL_STORAGE for this purpose, but it was not enforced.
Well, KitKat now enforces this privilege so that any app that does not have READ_EXTERNAL_STORAGE will not be able to read files, as I found out right away when installing one of my apps on my Nexus. I'm glad I remembered right away that I read something about it or it would have taken a while to figure out (the app didn't crash, but couldn't see any files either).
By the way, this only affects read-only apps since the WRITE_EXTERNAL_STORAGE privilege automatically grants READ access as well.
Just thought someone else might want to know...
Related
I have been reading about "Fixing permissions" and I can see that ROM Manager on my Nook (running Phiremod v5.2 with CM7) has that function.
But what exactly does "Fixing permissions" mean?
When do I need to do that?
And what are the consequences?
Hope anyone can explain it to me - or guide me to a "ROM Manager/Fixing Permissions for Dummies"
http://en.wikipedia.org/wiki/Filesystem_permissions
Fixing Permissions does exactly what it says really. It fixes the file system access permission to the correct settings if for some reason they aren't set right which seems to happen from time to time. As far as I know there are no issues or consequences to running the script outside of wasting a few minutes while it runs since it's basically restoring things back to how they should of been.
Thanks for the reference and the answer.
Regarding the Nook, what interests me is why this is necessary from time to time. But maybe I shouldn't think about it too much
Caspar...as you add new apps or change ROMS, the filesystem permissions often get changed. sometimes they get changed to values that are detrimental(like a file getting set to read only when it needs to be writable). That's why the need for fixing the permissions.
If you don't do this, you sometimes end up with a scenario where an app expects to be able to write some information and can't. This generates an error, which if the app isn't able to handle it, crashes the app.
A well written app will have thought of this already, but most times developers just expect the proper permissions and don't add in error handling code, saving themselves work and the program some size.
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.
GoodDayToDie said:
Two problems with that.
First of all, the app's install directory is read-only to the app permissions. You can't create, delete, or modify any file there from within the app (without some sort of "jailbreak" at least).
Second, and possibly more importantly, the permissions sandbox (or "appcontainer") that the phone uses to restrict an app is created at app install. Modifying the manifest is unlikely to have any benefit whatsoever (it certainly didn't help on WP7).
A good idea, though. Always glad to see people checking for such things.
Click to expand...
Click to collapse
As wp8.1 allows to move an app to the sd-card, I think point one should be ok. So how about modifying the app? I plugged my sd-card to the pc but all app files are kind of encrypted..
I tried it with @GoodDayToDie Webserver 0.5.0. http://1drv.ms/1flmBN4
thanks
gipfelgoas said:
As wp8.1 allows to move an app to the sd-card, I think point one should be ok. So how about modifying the app? I plugged my sd-card to the pc but all app files are kind of encrypted..
I tried it with @GoodDayToDie Webserver 0.5.0. http://1drv.ms/1flmBN4
thanks
Click to expand...
Click to collapse
as my phone doesn't support SD Card please send me one of does little apps you moved to sd card (please send a free app to me)
I will check it
but if you want to try adding Capabilities to app then re-write it in the folder it's surely not possible .
application capabilities are all checked and stored in your phone exactly when you install them (from your pc using Developer Unlock or from store)
Le Sigh...
This has been discussed extensively long, long ago. The manifest is only parsed at installation. You can do whatever you want to the manifest afterwards; it doesn't seem to have any effect.
It wouldn't help much anyhow. You wouldn't be able to *launch* a sideloaded app with Interopservices if not interop-unlocked. This can be tested by interop-unlocking a phone, sideloading an interop app, resetting the MaxUnsignedApp value to undo the unlock, and trying to run the app.
Hello!
I'm on a rooted Cricket Android 4.4.2 device.
ROM Version: 1.11.506.1
Software Number: 1.11.506.1
HTC Sense 6
Baseband: 1.101.1372.19
Can somebody please tell me how to get rid of the annoying software update that has been coming the last week?
Is there way to somehow either change my software number to trick the phone into thinking I'm updated or perhaps I should update? If so, how?
I appreciate the help.
Using a root file explorer and freezing the updater app manually would probably be the safest (personally I like Root Browser by JRummy hasn't been updated in awhile but if ain't broke it don't need to be, and it is a tool I know will always perform these critical tasks correctly)
By freezing the the system updater app in the following way, you will be able to easily reverse the process using the same process. While there are some mods that can hide the notification itself (eg.: Xposed FW), this method completely disables the update check process, thus freeing up system resources. Twofold if you look at it this way imo, rather than adding potentially harmful additional resources.
# Open your root fs explorer
# navigate to fs root:
/
# then to:
/system/priv-app
# locate the file:
Updater.apk
# append ".bak" to the file name. In other words rename it to:
Updater.apk.bak
# note: no need to mess with it's .odex file, it never hurt no one. Also depending on your fs explorer and personal settings, the app's icon thumbnail has likely changed to a blank white square/unkown/generic file icon and is totally normal.
# profit and celebrate the newly liberated space in your notifications and don't forget to miss that pesky "remind me later" pop up.
#should there be an update that your are feeling compelled to (try) and install simply remove ".bak" from the files name and proceed as usual. Note that the only thing you should be changing in all this is +/- ".bak" from the file name. Don't go trying to change this or other apps file name. It don't work like that. Speaking of other apps, I urge great caution against going ape$#¡+ and doing this carelessly, especially for apps anywhere under "/system".
# The Disable button on the App Info pages should be the primary resource for disabling apps for most users. Know what the app does and is used for on your system BEFORE making changes or worse yet, deleting it.
~/#: print <INSERT STANDARD DISCLAIMER, AKA CYA STATEMENT HERE>
Don't just say it, hit that thanks button if I helped you in any way!!!
Sent from my HTC Desire 510 using Tapatalk
wow thank you so much :laugh:
jackunoff said:
Using a root file explorer and freezing the updater app manually would probably be the safest (personally I like Root Browser by JRummy hasn't been updated in awhile but if ain't broke it don't need to be, and it is a tool I know will always perform these critical tasks correctly)
By freezing the the system updater app in the following way, you will be able to easily reverse the process using the same process. While there are some mods that can hide the notification itself (eg.: Xposed FW), this method completely disables the update check process, thus freeing up system resources. Twofold if you look at it this way imo, rather than adding potentially harmful additional resources.
# Open your root fs explorer
# navigate to fs root:
/
# then to:
/system/priv-app
# locate the file:
Updater.apk
# append ".bak" to the file name. In other words rename it to:
Updater.apk.bak
# note: no need to mess with it's .odex file, it never hurt no one. Also depending on your fs explorer and personal settings, the app's icon thumbnail has likely changed to a blank white square/unkown/generic file icon and is totally normal.
# profit and celebrate the newly liberated space in your notifications and don't forget to miss that pesky "remind me later" pop up.
#should there be an update that your are feeling compelled to (try) and install simply remove ".bak" from the files name and proceed as usual. Note that the only thing you should be changing in all this is +/- ".bak" from the file name. Don't go trying to change this or other apps file name. It don't work like that. Speaking of other apps, I urge great caution against going ape$#¡+ and doing this carelessly, especially for apps anywhere under "/system".
# The Disable button on the App Info pages should be the primary resource for disabling apps for most users. Know what the app does and is used for on your system BEFORE making changes or worse yet, deleting it.
~/#: print <INSERT STANDARD DISCLAIMER, AKA CYA STATEMENT HERE>
Don't just say it, hit that thanks button if I helped you in any way!!!
Sent from my HTC Desire 510 using Tapatalk
Click to expand...
Click to collapse
I'm gonna chime in here and I know you're trying to help but this really isn't helping because you didn't actually freeze the app like you said. All you did was change the apps name so now when the system actually calls upon that app it's simply going to error out and actually cause it to use more resources and not less as you said albeit it will not show up anymore but that's not the way to stop it! If I go into /system/priv-app and change Phonesky.apk to Phonesky.apk.bak the play store is going to break and then send me the error to my screen every second until I fix it and that uses more resources and the only reason you're not seeing the error on the screen for the Updater is because it's doing it behind the scene in a log. Now the real way to stop this app is to actually really freeze it or uninstall it so the system actually knows the app is no longer there and there are plenty of apps in the play store that can do that.
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
Khiddfrost said:
wow thank you so much :laugh:
Click to expand...
Click to collapse
You should read my post above.
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...