Hi,
i accidently changed the permission of the folder "system" to READ only. atleast i think so... i used Yaffs Explorer to change permission of "system" and i ticked the first line on all 3.
again.. this was an accident cuz i didnt know what i was doing.
now the problem is my phone just keeps restarting ... and then it boots into recovery (3e) on its own...
i tried using ADB to change the permission with adb shell ... and all that.. problem is
adb works. phone connects and shows off as device.
but if i try using the adb shell command or any other command with adb ( except sideload ) it tells me
"PERMISSION DENIED" and similar messages...
i have no clue how to safe my phone now any help would be much much appreciated.
i thought something of my own...
is it possible to write a shell script which changes the permission of "system" folder to its correct one.. make it as a .ZIP file and update use it with "update from adb"
please any help^^
best regards
Krype
I assume you are rooted have you gone into CWM and reset permissions?
Related
I am using Samsung Galaxy Note with stock ICS 4.0.4 and notecore kernel v13 std by g.lewarne.
here is the link for the kernel: http://forum.xda-developers.com/showthread.php?t=1749863 (it is hydracore now. but same for tw roms)
You may have heard the program called Droid Manager by deep unknown xda presented it to us a couple of days ago.
here is the link ıf the program: http://forum.xda-developers.com/showthread.php?t=1772338
my problem is that:
the program cannot push edited build.prop file to my phone. It can do so for any other phones.
I communicated with the dev of the program and he infırmed me that the program uses busybıx and/or adb commands to push the new build.prop file. we tried a couple of things yet could bot find a sokution. we tried the way to create a new file within the phone. (cat command). We 8succeeded however we need to push "enter" button to push the content to the file which is not possible to do so with the coding of droid manager. (i dont know how to tell the problem properly since i am not a dev )
what could be the possible solutions way???
TIA
p.s: i will ask devs to look at the thread. maybe they can shed more light to the problem...
I have opened Teamviwer with "ardicli2000" and worked directly from his laptop on his phone.
Done the following via Droid Manager and Command Line (CMD):
1. remount system as RW: succeeded.
2. Create a file on "/system" using: "touch /system/1.txt" also succeeded.
3. tried pushing a file from his desktop (file name was: 1.txt) FAILED !!
No matter what, once I start using "Adb push" I fail on putting anything on "/system" I get: Permission denied :-/
but when I attempt to create anything on "/system" using busybox commands I SUCCEED !!
what could be the issue?! everything in the program functions without issues except for "adb push" to "/system" :crying:
DeepUnknown said:
I have opened Teamviwer with "ardicli2000" and worked directly from his laptop on his phone.
Done the following via Droid Manager and Command Line (CMD):
1. remount system as RW: succeeded.
2. Create a file on "/system" using: "touch /system/1.txt" also succeeded.
3. tried pushing a file from his desktop (file name was: 1.txt) FAILED !!
No matter what, once I start using "Adb push" I fail on putting anything on "/system" I get: Permission denied :-/
but when I attempt to create anything on "/system" using busybox commands I SUCCEED !!
what could be the issue?! everything in the program functions without issues except for "adb push" to "/system" :crying:
Click to expand...
Click to collapse
Could no one help
So, I was changing my boot animation and I foolishly removed the execute permissions of my system folder from users and groups and it made everything crash in a cascade. Now I am unable to boot beyond the bootloader or protocols that don't rely on the system folder. I can load fastboot on the Photon but adb cannot see the phone since I cannot boot it. If I choose 'BP Tools' from the boot loader, I can get a shell connection with my phone for about 5 seconds before it crashes, however, the permission is denied. If anyone knows a command that would bypass permissions and allow me to quickly run a shell command to change the system folder permissions back to normal I'd be so very relieved and grateful.
Here's the message when I run adb shell during that 5 second window:
exec '/system/bin/sh' failed: Permission Denied (13)
I need a quick sudo-chmod something or another to ninja that /system folder's permissions back to where they should be. I am terrible with linux so I'm hoping theres a fix as simple as the problem really is. I can do a master boot if I need to but I don't see why the whole system should turn unrecoverable because of ticking 2 little green check boxes that consist of only a few bytes... omg...
K I did a factory reset and I apparently have to flash the entire ROM because the system folder isnt touched by the wipe.
Ugh, another 10 hours to walk in the dark cause Im terrible at this stuff.
Can you boot into recovery?
If so try Recovery -> advanced -> fix permissions reboot.
Sent from my MB855 using xda app-developers app
hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
the problem was in the file permissions. i had to remove write permissions to the group. (rw-r--r--)
You can fix permissions using adb
Sent from my GT-S5830 using xda premium
the.fuzzy.guy said:
hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
Click to expand...
Click to collapse
First of all DO NOT WIPE DATA / FACTORY RESET
This will remove adb access. Depending how far you can boot, do you get adb in recovery or normal. Can you use adb shell? If you can you can us adb shell chmod 644 /system/build.prop
EDIT:
Failing that try to install a zip. Sell my links for both current and older zips
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
nasenstueber said:
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
Click to expand...
Click to collapse
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
mauricio.valladolid said:
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
Click to expand...
Click to collapse
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
nasenstueber said:
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
Click to expand...
Click to collapse
why dont you just install ext4 recovery and flash supersu.zip?
I really dont get it why are you trying to do it the hard way
Hi,
I new on XDA, I heard that this is the biggest android developers community.
first of all, sorry if my english is bad.
I have a problem with my device.
I was stupid and i've set my /system folder permissions (with ES File Explorer) to un-read and un-write able.
I dont know how to explain it, but the result of my doing is that the device had reboot himself a second after, and wont boot up anymore...
The device cant read the system folder because i've changed the permissions!
how can I restore the permissions through ADB on my PC?
or through recovery mode with the "apply update from ADB", by open it and somehow send an permission-command through ADB...
NOTE: I have a chinese phone "AKAI DRAGON" AND I DONT HAVE THE UPDATE.ZIP! I cant reinstall the android.
any help?