[Q] media scanner permission denied on '/storage/sdcard0/.android_secure/', - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
Trying to figure out why media scanner service is running all the time, draining my battery I came accross this error in logcat:
Code:
W/MediaScanner( 2774): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
I tried fixing permissions, and it still happens.
I tried changing permissions, in order to make media scanner work without errors, by running:
Code:
chmod 777 /storage/sdcard0/.android_secure
which resulted in the following error:
Code:
Unable to chmod /storage/sdcard0/.android_secure: Read-only file system
I'm running slim bean 2.7 on my i9000 sgs.
Any idea how to resolve this issue?

ziflingus said:
Hi,
Trying to figure out why media scanner service is running all the time, draining my battery I came accross this error in logcat:
Code:
W/MediaScanner( 2774): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
I tried fixing permissions, and it still happens.
I tried changing permissions, in order to make media scanner work without errors, by running:
Code:
chmod 777 /storage/sdcard0/.android_secure
which resulted in the following error:
Code:
Unable to chmod /storage/sdcard0/.android_secure: Read-only file system
I'm running slim bean 2.7 on my i9000 sgs.
Any idea how to resolve this issue?
Click to expand...
Click to collapse
Looking for something else and saw this old post. For future reference, just create a she'll script in /system/xbin and use busybox to run a short script with umask=0000 and the remount sdcard0 and probably extSdCard also just to be safe until it's figured out. Can use managers or taskbomb to run it...

Related

ADB issues with 2.2?

I getting permission denied errors when I try to re-copy mkfs.yaffs2 to /data/misc
D:>adb push mkfs.yaffs2 /data/misc/mkfs.yaffs2
failed to copy 'mkfs.yaffs2' to '/data/misc/mkfs.yaffs2': Permission denied
Anyone else having permission issues?
Resolved. Updated adb first.
while I was updating, I remembered you cant push straight to /data or /system.
Need to dump to sdcard first, then use cat.. o.0

[Q] adb mount system help

Hi guys i have read around and i have seen that some experienced the same problem but i couldn't find and answer so here i go: i am trying to push an app to /system/app but it seems that i can't remount the system as read-write:
C:\AndroidSDK\tools>adb push app.apk /system/app
failed to copy 'app.apk' to '/system/app/app.apk': Read-only file system
C:\AndroidSDK\tools>adb remount
remount failed: Operation not permitted
C:\AndroidSDK\tools>adb shell sysrw
sysrw: not found
do you think you can help, please?
i have superuser installed and busy box but when i try to update busy box it gives me an error saying that: The application failed, either because your device is not nand unlocked or we were unable to remount....

V8 rooted but no CWM

I was on v8 non-rooted.
I followed the instructions here to the letter:
http://forum.xda-developers.com/showthread.php?t=1566729&page=4
didn't have any issues at all, no errors.
I'm confirmed on V8 and do have root but can't access CWM. Attempting to run the new AIO again gives the following:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: Read-only file system
7781 KB/s (5345280 bytes in 0.670s)
Unable to chmod /system/xbin/busybox: Read-only file system
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Press any key to continue . . .
Any ideas how to get to CWM?
Looks like you need to root again after your upgrade. Run MT's Root&RecoveryAIO.bat again and select the "Root ZV8" option.
[EDIT]
My bad. That's what you are trying to do! I've been up all night and am tired. Did you get any errors when you ran the "Prepare for Update" option before you upgraded? That option actually pushes the superuser files back to your phone and the "Root ZV8" option just goes back and set's the permissions. You can try manually running these commands with adb first.
Files\adb push Files\zergrush /data/local/tmp/zergrush
Files\adb shell "chmod 755 /data/local/tmp/zergrush"

[Q][DEV] system() call fail when executing native app with su permission

Hi all,
I have run into very disturbing problem when developing a native app with NDK. When my program calls system(), popen() or other function of that kind the return value of system() call is 32512 (which is 127: "command not found"). popen() does not return error code but crashes when trying to read() (returns -1). I have tested this on basic commands such as ls, ps, etc. Tried to provide a full path to the binaries as well without success.
The issue appears only when executing binary with su (I have tried interactive su, su -c and many other variations- I run it via adb shell). When calling system() without su permission then commands are executed correctly. When programmatically reading files in /system/bin (when my program is run with su) I see all files and everything is accessible.
I have verified that su is installed correctly, I can do all kind of root-only stuff without any problem. My program when executed with su permission is able to enter protected areas of Android.
I have tried to switch context without any luck. There is no interesting logcat output that could point to any permission I could allow with supolicy.
This happens on Samsung S3 i9300, S4 i9505, S5 G900F, Note3 N9005...
Happens both on SELinux enforcing and permisive.
Code:
[email protected]:/ $ su -v
2.45:SUPERSU
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Any help and clues are much appreciated.
Thanks,
Piotr.
Turns out that the reason is that fork() is prohibited when executable is not located under /system. When placed binary on /system/bin everything works fine.

Error installing Xposed Framework: can't create '/system/bin/app_process

This error is killing me :/
Could really use some help..
Error says:
Copying Xposed-Disabler-Recovery.zip...
Mounting /system writable...
Backup already exists at /system/bin/
app_process.orig
Copying app_process...
cp: can't create '/system/bin/app_process': File
exists
Tried looking around the forum but haven't found a solution yet
I'm on a huawei g7 using android 4.4 rooted
Still no solution. I tried finding a way to manually install the app_process but i can't find any tut on it
So i think every file on /system is write protected to i tried to unlock it with
su
mount -o rw,remount /system
cd /system
chmod -R -i *
But i didn't work :/
oke so i tried to run the installer one last time tonight and for some reason it installed the framework without problems. i have no idea why..

Categories

Resources