Database Info

Any "Not granting permission" HACK?

I can't grant some permission in android for my apks, eg : android.permission.INJECT_EVENT
even I have putted the apk in /system/app, the system still doesn't grant the permission
Is there any way to let my custom program can have such permission ( using root? or how to modify the system config ? But not using system cert...)

[Q] Clean up after switching to SuperSU

Hi guys,
The rom I use (Endymion) comes with Superuser, but I changed to SuperSU. Everything works fine, but now I'd like to clean up and uninstall the old superuser system app. Titamium Backup is too scared to do so, so I have to do it manually.
I deleted all updates to Superuser (like u uninstall non system apps) and renamed Superuser.apk in /system/app/ to Superuser.apk.old. Now it seems to be gone but are there additional files I shall and can safely remove (rename it first and test) for Superuser clean up purposes (R/W rights, Root Explorer or adb shell are manageable for me)?
Thx,
Kwisatz

you could also delete the app's folder in /data/data, it should be something like com.k(something).superuser

[Q]Deleting preinstalled apps

I am trying to get rid of lots of bloatware that I don't want in my new unlocked Motorola Atrix hd phone. I have rooted the phone and got terminal emulator and su working. When I read around on the internet, there are posts describing to remount the /system/app for read/write, delete the apk and odex files and the remount again for read only.
My understanding is that root should be able to "rm" those files in "su" mode if you can see them. So why do we have to remount them before deleting and after? What does it do? What happens if I simply "rm" the apk and odex files in /system/app without remounting before or after, I mean if I am able to "rm"?
Thank you.

I believe the logic is that for security reasons the system/app partition is mounted in read-only mode by default. With root privileges, you can mount it as read/write and make changes such as removing apk files. When you're done editing, you should remount the /system/app partition as read-only, restoring it to its default state. If you don't, any process could theoretically make changes to the files in that partition which could damage your OS or apps.

So we remount the partition because we cannot delete them otherwise. That means if we are able to delete them without remounting, it is OK to do so. Correct?

I believe so. But just to be sure, I would strongly advice to make a nandroid backup before you delete any files.

skipperx said:
I am trying to get rid of lots of bloatware that I don't want in my new unlocked Motorola Atrix hd phone. I have rooted the phone and got terminal emulator and su working. When I read around on the internet, there are posts describing to remount the /system/app for read/write, delete the apk and odex files and the remount again for read only.
My understanding is that root should be able to "rm" those files in "su" mode if you can see them. So why do we have to remount them before deleting and after? What does it do? What happens if I simply "rm" the apk and odex files in /system/app without remounting before or after, I mean if I am able to "rm"?
Thank you.
Click to expand...
Click to collapse
Just use this app free from the Play Store: https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
No messing around with Terminal and any commands.

I found out. I could not delete even as su and got a msg that it was read only. That's why we need to remount.

Or you can use Titanium Backup. TB has option to backup system app&data and then remove.
It's safer...

You can also freeze apps with TB. If something goes wrong, you can unfreeze it or do factory reset.

su binary question (no troubleshooting)

Hello, i read a lot on google about root but didn't find the answears that i'm looking for, hope some of you can explain.
I want to access the /system of my phone to change hosts file for example.
I know i need root access for that of course but that is my question.
What is neccessary for that, is placing the su binary in
/system/xbin/su
enough to access /system?
do i have then root access? or i need busybox, superuser.apk and some commands also?
thank you guys

if you have su already pushed into system partition means you got root access but if you dont have supersu installed you can't manage permissions that an application would request

so it is just the *su binary* necessery without chmod or something else? (theoretic)

Change the permissions read/write

1. I'm using an app.
2. My device has been rooted, i'm using root explorer
3. I want to change the permissions (revoke "write" access) of file A in root/data/user/0/com.app name/cache
4. Open the app.
5. File A is still being modified.
6. I revoked write permissions of the parent folder.
7. Open the app.
8. File A is still being modified.
What should I do? I cannot delete that file, or the app will crash. I only want the app to read file A, without being able to modify it.

To change file permissions use Androids shell command CHMOD.

xXx yYy said:
To change file permissions use Androids shell command CHMOD.
Click to expand...
Click to collapse
I'm using the root explorer app. If I use chmod to revoke a file's permission, will it be granted again when I open the app?

NO

xXx yYy said:
NO
Click to expand...
Click to collapse
I have tried it, only read permission, but the file still gets modified when I open the app.