• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Can't fix permissions?!

modhatter6811

Android Enthusiast
So ordinarily (at least on any other device) I can open up terminal, type su, then "busybox fix_permissions" and it does its thing. However, all I get is sh: fix_permissions not found. Any ideas how to go about this? Can we fix permissions using TWRP? I've tried every variant of fix permissions as well, ex:
busybox fix_permissions
busybox fix_perm
busybox fix permissions
busybox fix perm
I've also tried all of these without invoking busybox as well. Same story, applet not found, or sh not found. I know damn well one of those should be correct.
 
You can fix permission via twrp. You can also use terminal commands to chmod. Example " chmod 644 /<path> " or use the stericson fix permission app for individual apps.
https://play.google.com/store/apps/details?id=com.stericson.permissionfix
*Edit*
Also regarding busybox commands make sure your busybox is updated and all the applets are installed and linked. Busybox installer is a user friendly method for this.
 
You can fix permission via twrp. You can also use terminal commands to chmod. Example " chmod 644 /<path> " or use the stericson fix permission app for individual apps.
https://play.google.com/store/apps/details?id=com.stericson.permissionfix
*Edit*
Also regarding busybox commands make sure your busybox is updated and all the applets are installed and linked. Busybox installer is a user friendly method for this.

Busybox was the first thing that I checked. Its up to date. Will TWRP fix all permissions system wide? I should have worded myself better in the op. I used to be able to do it on my old Triumph through terminal, and have all permissions corrected at once, without specifying any path. The problem I have is that I don't know the original permissions, and they seem to be different for different devices (API? I'm guessing here). So matching them to my AWE... Makes for a problem. Also, any ideas why I can't mass fix them through terminal?
 
Twrp fixes permission for system, system/app, data/data, data/app

Sweet! I was doing some thinking about why it doesn't work on mass scale through terminal, (which would be my preferred option), and I think it had something to do with the ROM my older phone was running. I believe there is a script for it. Going to do some digging. :D
 
Busybox was the first thing that I checked. Its up to date. Will TWRP fix all permissions system wide? I should have worded myself better in the op. I used to be able to do it on my old Triumph through terminal, and have all permissions corrected at once, without specifying any path. The problem I have is that I don't know the original permissions, and they seem to be different for different devices (API? I'm guessing here). So matching them to my AWE... Makes for a problem. Also, any ideas why I can't mass fix them through terminal?

fix_permissions is a shell script that gets inserted in the ROM during compilation, so whatever ROM you're on didn't include it. I would just grab it from https://github.com/CyanogenMod/android_vendor_cm/tree/cm-11.0/prebuilt/common/bin and copy to /system/bin on your phone for now, and if you're not on stock make a friendly suggestion to your ROM dev.
 
fix_permissions is a shell script that gets inserted in the ROM during compilation, so whatever ROM you're on didn't include it. I would just grab it from https://github.com/CyanogenMod/android_vendor_cm/tree/cm-11.0/prebuilt/common/bin and copy to /system/bin on your phone for now, and if you're not on stock make a friendly suggestion to your ROM dev.

I had a feeling one existed. Thank you for saving me trouble of finding it! This will be of huge help to me always. :D

Update: Have an issue. I can't grab it. There's no way to download it, and I'm not sure how to use github through android. I don't have access to regular WiFi but sparingly and even then, I'd still be using my awe. I tried creating a script, by copying the text then moved it to system/bin but neither terminal by its self or with the invocation of busybox will recognize it. Perhaps improper permissions? (the irony that would be) I set permissions as rwxr-xr-x. I took a guess here based on other scripts that I thought would have the same kind of authority as fix permissions.
 
Back
Top Bottom