Database Develop

[SCRIPT] Permissions Init Script

Hey guys,
I had a nasty issue with Bi-Winning a couple weeks ago where I pushed custom framework and totally forgot about permissions. Apparently when you don't set the proper permissions it can really slow things down.
So I figured this could easily be avoided. So because of that and our CWM "Fix Permissions" option doesn't really do anything, I wrote this script to fix it!
Upon every boot, it will scan /system/app, /system/framework/, and /data/app and set the proper permissions for all the files in there.
Users
note if you're on Trigger 2.9.1+ or Bi-Winning V1+ you do NOT have to do this. It's built into your ROM already.
Flash the attached zip named "CWM_Flash_Permissions_Script.zip"
Ironically, it may not have the correct permissions after you flash it, so then do either of the following
1) Do these commands in ADB to set the correct permissions
Code:
adb shell
mount -o rw,remount /dev/block/stl9 /system
busybox chmod 777 /system/etc/init.d/*
or
2) Open up Root Explorer (or something similar)
navigate to /system/etc/init.d/
in there find the new file S30edt_perms
long press, and set the permissions
make it look like this
Code:
x x x
x x x
x x x
Here's the init.d script, it's really simple, but also effective
Code:
#!/system/bin/sh
# Permission script
# Written by Einherjar Dev Team
# www.edtdev.com
logFile=/data/edt/logs/S30edt_perms.log
if [ -f $logFile ]; then
rm $logFile
fi
touch $logFile
mount -o rw,remount /dev/block/stl9 /system
echo "Setting permissions" >> $logFile
for file in /system/app/* /system/framework/* /data/app/*; do
echo " setting permissions (644) for $file" >> $logFile
chmod 644 $file
done
echo "chmodding init.d folder"
chmod 777 /system/etc/init.d
for file in /system/etc/init.d/*; do
echo " setting permissions (777) for $file" >> $logFile
chmod 777 $file
done
echo "Permissions set" >> $logFile

Very cool, thanks roman.
Very cool to post the code too... lets us linux newbs get our learn on!

Poser said:
Very cool, thanks roman.
Very cool to post the code too... lets us linux newbs get our learn on!
Click to expand...
Click to collapse
I'm a Linux noobie myself!

birgertime said:
I'm a Linux noobie myself!
Click to expand...
Click to collapse
[slight OT] Just getting wifi working on an old ideapad y510 in slackware was an epic struggle... (wicd my arse)
[back on topic] I wish more devs would post script contents (though we can easily download and look in vi or notepad)... it helps the learning curve immensely
grateful for all the work EDT and rest of dev community does. We all are.
Question: What does the fix permissions CWM do then?

Poser said:
[slight OT] Just getting wifi working on an old ideapad y510 in slackware was an epic struggle... (wicd my arse)
[back on topic] I wish more devs would post script contents (though we can easily download and look in vi or notepad)... it helps the learning curve immensely
grateful for all the work EDT and rest of dev community does. We all are.
Question: What does the fix permissions CWM do then?
Click to expand...
Click to collapse
I have no clue, lol. Never bothered looking at it
edit: I hate vi.

roman im gonna add S30edt_perms.zip to my rom ..ill add you to credits

birgertime said:
I have no clue, lol. Never bothered looking at it
edit: I hate vi.
Click to expand...
Click to collapse
lol.
Vi is about as stripped down as you can get when it comes to text based editors... (I know its blasphemous... but I dig notepad++, shhh... dont tell)

I get "Bad Mode"

gamefreakgcb said:
I get "Bad Mode"
Click to expand...
Click to collapse
Hmm, ok you might need super user permissions do this and let me knkow if it works:
1) type in "adb shell"
2) type in su (don't press enter yet)
3) turn your screen on & unlock it
4) press enter on the su prompt, then his yes on the screen
then try that chmod command again.

birgertime said:
Hmm, ok you might need super user permissions do this and let me knkow if it works:
1) type in "adb shell"
2) type in su (don't press enter yet)
3) turn your screen on & unlock it
4) press enter on the su prompt, then his yes on the screen
then try that chmod command again.
Click to expand...
Click to collapse
Gave permission, still "Bad Mode"

gamefreakgcb said:
Gave permission, still "Bad Mode"
Click to expand...
Click to collapse
bad mode in the command line? gotta give me something more here
if it' s when you run chmod +x try this one:
Code:
busybox chmod 777 /system/etc/init.d/*

birgertime said:
bad mode in the command line? gotta give me something more here
if it' s when you run chmod +x try this one:
Code:
busybox chmod 777 /system/etc/init.d/*
Click to expand...
Click to collapse
When I do that, I get
chmod: /system/etc/init.d/S01edt_systcl: Read-only file system
chmod: /system/etc/init.d/S20edt_gps: Read-only file system
chmod: /system/etc/init.d/S30edt_perms: Read-only file system
chmod: /system/etc/init.d/S50edt_zipalign: Read-only file system
chmod: /system/etc/init.d/S98edt_tweaks: Read-only file system
chmod: /system/etc/init.d/S99edt_complete: Read-only file system

gamefreakgcb said:
When I do that, I get
chmod: /system/etc/init.d/S01edt_systcl: Read-only file system
chmod: /system/etc/init.d/S20edt_gps: Read-only file system
chmod: /system/etc/init.d/S30edt_perms: Read-only file system
chmod: /system/etc/init.d/S50edt_zipalign: Read-only file system
chmod: /system/etc/init.d/S98edt_tweaks: Read-only file system
chmod: /system/etc/init.d/S99edt_complete: Read-only file system
Click to expand...
Click to collapse
Oh crap, thanks for pointing that out man. Easy fix
do this
Code:
mount -o rw,remount /dev/block/stl9 /system
busybox chmod 777 /system/etc/init.d/*
should work like a charm
by the way, next time you flash a newer edt rom, they already have this fix built in. since you overwrote the file, you'll need to run the above commands to set the correct permissions as they get messed up sometimes when modifying them.

That did the trick, thanks.

The script in the .zip says
Code:
# Permission script
# Written by Roman (birgertime)
# www.edtdev.com
logFile=/data/edt/logs/S30edt_perms.log
if [ -f $logFile ]; then
rm $logFile
fi
touch $logFile
echo "Setting permissions" >> $logFile
for file in /system/app/* /system/framework/* /data/app/*; do
echo "setting permissions for $file" >> $logFile
chmod 0644 $file
done
echo "Permissions set" >> $logFile
Which is different than the OP. I'm confused.

MikeyMike01 said:
The script in the .zip says
Code:
# Permission script
# Written by Roman (birgertime)
# www.edtdev.com
logFile=/data/edt/logs/S30edt_perms.log
if [ -f $logFile ]; then
rm $logFile
fi
touch $logFile
echo "Setting permissions" >> $logFile
for file in /system/app/* /system/framework/* /data/app/*; do
echo "setting permissions for $file" >> $logFile
chmod 0644 $file
done
echo "Permissions set" >> $logFile
Which is different than the OP. I'm confused.
Click to expand...
Click to collapse
I notice that before... but got side tracked and forgot to mention something... I just pulled the one from in Bi-Winning V2 and have been ADB Push'ing that.
EDIT: Also noticed that the one that's in Dan_Brutal "Metrik Part 1- Pepperkake" is the wrong one.

Does this works on hd2 android? i really need this..

haysnamrip said:
Does this works on hd2 android? i really need this..
Click to expand...
Click to collapse
Should work on any Android that can run scripts

i flashed and its working.. no more changing permission after run fix_permissins on terminal emulator..

Hey Roman, thanks for yet another improvement for this phone!
Simple question: can I just download and push the S30edt_perms.zip to etc/int.d? And is this any good for CM7 based ROMs? I just checked and that file isn't in my init.d folder on Trigger Redux.
Thanks!
Sent from my rough sketch of a Vibrant on a brick.

[ROOT] Linux command lines if SuperOneClick fails

Hi.
I've tried many times to root my LG2X with Z4root, UniversalAndRoot, Visionary and SuperOneClick since I've bought it but it failed each time.
I've seen the [Root] topic in the developpement thread but I can't post there (less than 10 posts...) but I want to help someone to root his/her mobile.
I've searched a long time a good way to do so without SuperOneClick (which doesn't respond with Windows Seven or Ubuntu 11.04) but there is none.
There we go...
Disclaimer : I can't be responsible if you break your phone, cancel your warranty or launch your LG2X on the wall in rage.
If you want, there is already SuperOneClick which run smoothly for many geeks : LG2X SuperOneClick Forum and SuperOneClick Forum
My HTC Magic had been rooted with the command line and I've tried myself to do so with every bit of informations and tips I could find on Internet.
I recommand to test the SuperOneClick method and if it fails, come test this with a Linux terminal (psneuter, su-v2, busybox and the SuperUser.apk can be found in the SuperOneClick archive) :
Code:
adb push psneuter /data/local/tmp
adb push su-v2 /data/local/tmp
adb push busybox /data/local/tmp
adb shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
adb remount
adb shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 6755 /system/xbin/su
# busybox chown 0.0 /system/xbin/su
# busybox cp /system/xbin/su /system/bin/su
# busybox chown 0.2000 /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
adb install Superuser.apk
adb reboot
And... Normally you have permanent root on your LG2X.
You can check the files permissions with
Code:
ls -l /system/xbin/su /system/bin/su
-rwsr-sr-x root root 26264 2011-04-23 20:07 su
-rwsr-sr-x root shell 26264 2011-04-23 23:20 su
It seems that /system/xbin/su isn't necessary at all. The su command which gave you the root is the one in /system/bin/. And I had some problems with /system/xbin, I've deleted the folder (with rm /system/xbin or mv /system/xbin /dev/null, I can't recall) and applied mkdir on it again.
If this can be of help, I'll update this later.

thanks for the detailed instructions, but super one click definitely works with win7 (64bit too) as long as you have the right drivers installed

Thanks but with Windows Seven 64 bits, Linux ou Windows Seven 32 bits with Virtualbox I end up with "SuperOneClick doesn't respond" or stuck on with "chmod psneuter" (with the drivers properly installed).
It's only an alternative solution if SuperOneClick doesn't run properly for another guy.

Thanks a lot for that tips.
The problem I have now is that su isn't persistant.
When I use
$ su
It hangs up few seconds... and says "Permission denied"
I've used su-v2
Here are the su permission :
-rwsr-sr-x root shell 26324 2011-02-13 14:43 su
Is there a more up-to-date su, that will maybe fix the problem ?
Thanks.
EDIT :
Ok.
The wait time seems to come from SuperUser, I've removed it.
Now I have directly the "permission denied", and "stat failed with 2: No such file or directory" in the logcat.
Maybe that can help.

Hannes The Hun said:
thanks for the detailed instructions, but super one click definitely works with win7 (64bit too) as long as you have the right drivers installed
Click to expand...
Click to collapse
It didn't for me (after installing nightly 51)
With the step-by-step instructions I get "Failed to set prot mask (inappropriate ioctl for device)" when trying to execute psneuter.

Hi.
Sorry for the wait.
Have you resolved your problem with your rooting?

How do you 43v3r root 901 on the Bionic?

Hi Guys,
Is there a way to 43v3r root the Bionic when on the 901? I am already rooted (used path saver to get to 901) but I do not know if I am 43v3r rooted and would like to get to the 902 to flash to ICS.
Thanks for the help!
Marc

nevermind guys doing back to stock then going up.. Thanks

tell what you did to get there I am very confused at this point
Sent from my DROID BIONIC using XDA App

Back when someone discovered what exactly the update was doing to remove our root (I think it was the 5.5.893 update?), they posted a way to do it manually. It was basically just locking the file permissions on the appropriate root files so the update cannot modify them. There were three files.
OK I got off my lazy ass and googled for it.
YOU NEED TO ROOT FIRST... FOREVER ROOT ISN'T A METHOD TO ROOT. IT'S A METHOD TO RETAIN ROOT THROUGH OTA UPDATES.
Here's the main post
Here's the video from that post if you're super lazy
And here's the text if you're ultra lazy:
RootExplorer Method
go to /system/bin/
open in text editor – mount_ext3.sh
add the following lines to the very bottom
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk
ADB method
adb pull /system/bin/mount_ext3.sh
open the file in your favorite text editor
add the following lines to the very bottom
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk​Save file
adb push mount_ext3.sh /data/local
adb shell
mount -o rw,remount /dev/null /system
cat /data/local/mount_ext3.sh > /system/bin/mount_ext3.sh
chmod 777 /system/bin/mount_ext3.sh
Click to expand...
Click to collapse

[SOLVED]

SOLVED, cant find the delete button
I am not a big expert with software and stuff, but I try rooting my lg optimus 4x hd and all it says:
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
mount: Operation not permitted
mount: Operation not permitted
/system/bin/sh: can't create /system/app/Superuser.apk: Read-only file system
/system/bin/sh: can't create /system/xbin/su: Read-only file system
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
REBOOT
Can someone help me?
btw, I tried the root and the root-nobusybox

Cannot delete(access old user files and folders after reflashing Vanilla-Android 4.2

Today I reflashed Stock Android 4.2 on a Xperia T.
Before there was Cyanogenmod (Android 5) installed.
I forgot to delete all user files/folder in internal memory.
Now, I cannot delete or access old user files and folders, even as root!?!
Its a problem of the permissions, I guess.
I can RENAME folders, but cant delete/open/chmod/change permissions recursiv, not with a file manager (as root), not with adb, not with "rm - rf", nothing.
So how I can get rid of those old folders?
E.g., for camera I had to rename DCIM to DCIMold, and create a new folder to get saving pictures to work.

Hi did you use neo's cm12.1. if you did use his, did you flash uninstaller,zip if didn't flash it here is a link https://www.androidfilehost.com/?fid=95916177934533137 and if you didn't use neos im sorry i dont know
If I helped please be kind and click like :good::good:

Yes, it was neo's cm12.1.
No,i didnt flash any uninstall.zip
Thank you for the info.
But I guess its to late now?

rrutk said:
Yes, it was neo's cm12.1.
No,i didnt flash any uninstall.zip
Thank you for the info.
But I guess its to late now?
Click to expand...
Click to collapse
nope dont think its to late just flash a custom kernel and then flash the uninstaller
If i helped please be kind and click like :good::good:

alial04 said:
nope dont think its to late just flash a custom kernel and then flash the uninstaller
If i helped please be kind and click like :good::good:
Click to expand...
Click to collapse
if I send the only command from the uninstall.zip
find /sdcard -user 1023 -exec chown 2800:2800 {} \;
in Terminal as SU, nothing changes....
Will it be a difference while flashing it?

If you want to use stock rom write this in terminal:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 2800:2800 /mnt/media_rw/sdcard0
chown -R 2800:2800 /mnt/media_rw/sdcard0

krasimiretov said:
If you want to use stock rom write this in terminal:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 2800:2800 /mnt/media_rw/sdcard0
chown -R 2800:2800 /mnt/media_rw/sdcard0
Click to expand...
Click to collapse
I'm already on stock ROM now.
I did the above mentioned, but I have to use "/mnt/sdcard", because "mnt/media_rw/sdcard0" seems not exist.
chmod 777 /mnt/sdcard
chown 2800:2800 /mnt/sdcard
works.
su busybox chown -R 2800:2800 /mnt/sdcard
gives "read only filesystem".
if I do a "mount -o remount rw /sdcard" before the command it works, BUT NOTHING CHANGES.
cant delete the files.
crazy.
do I really need to flash another kernel before?
cant understand why root has no access to the files.

SOLVED.
Correct is (as SuperUser):
busybox chmod -R 777 /mnt/int_storage
busybox chown 2800:2800 /mnt/int_storage
busybox chown -R 2800:2800 /mnt/int_storage
rrutk said:
I'm already on stock ROM now.
I did the above mentioned, but I have to use "/mnt/sdcard", because "mnt/media_rw/sdcard0" seems not exist.
chmod 777 /mnt/sdcard
chown 2800:2800 /mnt/sdcard
works.
su busybox chown -R 2800:2800 /mnt/sdcard
gives "read only filesystem".
if I do a "mount -o remount rw /sdcard" before the command it works, BUT NOTHING CHANGES.
cant delete the files.
crazy.
do I really need to flash another kernel before?
cant understand why root has no access to the files.
Click to expand...
Click to collapse