Hello!
Could anybody tell me quickly what the default permissions are on /system/framework are? I ****ed up:
chmod -R 644 /system/framework/, instead of chmod -R 644 /system/framework/*. Now it won't boot.
Apparently it was 755, now it's fixed.
Related
I need to batch apply a set of permissions to these two folders and all files contained within. I'm moving my ringtones to these so that they preserve upon an SD Unmount, but I need to know the proper command in Terminal Emulator to do so. The files need rw-r-r-
/system/media/audio/ringtones
/system/media/notifications
Any help on this would be greatly appreciated.
if you want to apply a permission to the folder and also(recursive) to all of its contents...
you can use this:
su -c chmod -R 777 /path/to/directory
NOTE: 777 = rwx-rwx-rwx
My Kindle fire hdx 8.9 worked normally since I bought it. Yesterday I remove the signature to install google service, and the wrong was it can't restart and I reset it to the factory from recovery. Now it still rest on the colored "kindle fire". But it seems some processes have been loaded because the MTP devices can be found in PC and the adb mode seems work normally. I think some steps losed in the boot. Can I recover it by adb mode or other methods? Thank you.
I reset it to the factory from recovery.
Click to expand...
Click to collapse
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
ONYXis said:
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
Click to expand...
Click to collapse
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
tianlie said:
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
Click to expand...
Click to collapse
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
ONYXis said:
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
Click to expand...
Click to collapse
"adb push services.odex /data/local/tmp" This command give an error: device not found.
Does it need the file "services.odex"? Where?
Thanks a lot.
The complete response:
D:\win32>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount /system
mount -o remount /system
[email protected]:/ # rm /system/framework/services.odex
rm /system/framework/services.odex
[email protected]:/ # adb push services.odex /system/framework/
adb push services.odex /system/framework/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ # chmod 755 /system/framework/services.odex
chmod 755 /system/framework/services.odex
Unable to chmod /system/framework/services.odex: No such file or directory
10|[email protected]:/ # reboot
reboot
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
ONYXis said:
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
Click to expand...
Click to collapse
It should be 14.3.2.5. OK. I wait you.:good:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
ONYXis said:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
Click to expand...
Click to collapse
That's great! Kindle is upgrading... Select language, register, the desktop come back.
Thank you, ONYXis, you are my god!:good:
To others, don't think the factory set is best.
Thank you again.
Basically, I was installing an app as a system app with ADB. When I suddenly accidentally.
DID: adb shell chmod 644 /system/app/
And now I get the error: Unfortunately the process Com.Android.Phone has stopped.
And it says no SIM CARD! I broke the permissions and I wanna fix this.
The Message pops up every second!
What are the original permissions for /system/app/ so I can set it back and be relieved!?
Use
Code:
chmod 644 /system/app/*
and reboot phone.This will fix your problem.
asderdd said:
Use
Code:
chmod 644 /system/app/*
and reboot phone.This will fix your problem.
Click to expand...
Click to collapse
I instead did chmod 777 /system/app/
But thanks anyways.
P.S. What does the '*' do?
I have installed term_init.sh for Init.d support. The scripts run perfectly from SM script manager app. However, they never run upon booting.
I have rooted - Marshmallow.
Any ideas please?
Try this:
1. Create /system/etc/install-recovery.sh (if not exist) set perms to 0755 (rwxr-xr-x) and ownership to 0:2000 (root:shell)
and write:
#!/system/bin/sh
/system/bin/sysinit
2. Create /system/bin/sysinit and set perms to 0755 (rwxr-xr-x) and ownership to 0:2000 (root:shell)
and write:
#!/system/bin/sh
run-parts /system/etc/init.d
3. Create dir /system/etc/init.d and set perms to 0755 (rwxr-xr-x) and ownership to 0:2000 (root:shell)
4. Create /system/etc/init.d/00test and set perms to 0755 (rwxr-xr-x) and ownership to 0:2000 (root:shell)
and write:
#!/system/bin/sh
echo "init.d executed script at boot" > /data/initd.log
5. Reboot and check if /data/initd.log file exist
Thanks!
Yes, the term-init.sh which I installed does everything you have noted above with all permissions. The script executes within Script Manager App but won't execute on boot as intended. Thus, the log file doesn't appear in /data/test.log
Still stuck?
I never do that, so I don't know what can go wrong, but try add init.d service to init.rc:
# Run init.d scripts
service sysinit /system/bin/logwrapper /vendor/bin/busybox run-parts /system/etc/init.d
class main
user root
group shell
oneshot
So I'm trying to test a script, test.sh which I saved in /cache. Chmod + x test.sh returns bad mode, Chmod 777 and others, 700, 666, etc. does nothing to change the file's permissions and no errors are given. Just for giggles ./test.sh returns not found. Rooted with Magisk, issued su beforehand, terminal app has root (Terminal Emulator). What gives?
Even more interesting....
ls -la shows no changes, however Power File Browser shows the script is 770 and is able to change permissions and shows the permissions changing. It also shows that the script now simply named test is also getting it's permissions changed with chmod, so perhaps there is an issue with ls -la in Stricson's Busybox? But why can't I ./ ?
Ok. Doing a which ls and which chmod shows /bin, but busybox is in /xbin, however calling busybox directly busybox ls -la and gives the same result doesn't show the +x but busybox chmod +x does work, so the chmod in the stock ROM doesn't support using +.
Busybox ./test does nothing either.
Found the issue with the file not running ./ and not found had #!/bin/sh and it requires #!/system/bin/sh at the top of the script.
In conclusion the ls -la command does not work correctly.