my /system folder is read only and i was trying to change permissions to r/w with yaffs explorer but i keep getting error "unable to chmod /system -read only file system
i can change permissions for other folders in the same directory. any thoughts on a fix
The same as root explorer?try opening superuser to see whether it is permission granted
i had this problem with root explorer before and i read that i needed to update to the latest version which fixed my problem, perhaps the same for whatever app you were using
I tried re- rooting, the app has root access and I have the latest app, i even cleared tbe app data and reinstalled. this happend afyer I updated to gingerblur 3.5. think the rom could be the issue?
I have the same problem. I'm trying to edit a file but it is only read only. I am also rooted using gingerblur 3.5
Sent from my MB860 using XDA App
going back to gingerblur 3.1 and see if that fixes it. i will report back shortly
so going back to 3.1 and installing an older version of yaffs explorer did not work
i found busybox installer from the marker and installed that and then installed the default busybox v1.19 and now i was able to write to /system/app again so i can install my app.
give that a shot
You have to mount the filesystem as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Related
I updated JID6 using ODIN
Rooted using OCLF One click
Using Root Explorer I am unable to modify these files after JID6 update.
Previously i was able to move/delete these files. Not anymore.
Current Permission is rw-r--r--
I tried to modify my permsission, but it does not permanently apply. Does anybody else have this problem.. Even after its been rooted, i can't make these permission changes therefore i can't move/delete these files.
Bootup: system/etc/PowerOn.wav
Shutdown: system/media/audio/ui/Shutdown_128.ogg
Did you remount /system rw?
busybox mount -o rw,remount /system
samlot said:
I updated JID6 using ODIN
Rooted using OCLF One click
Using Root Explorer I am unable to modify these files after JID6 update.
Previously i was able to move/delete these files. Not anymore.
Current Permission is rw-r--r--
I tried to modify my permsission, but it does not permanently apply. Does anybody else have this problem.. Even after its been rooted, i can't make these permission changes therefore i can't move/delete these files.
Bootup: system/etc/PowerOn.wav
Shutdown: system/media/audio/ui/Shutdown_128.ogg
Click to expand...
Click to collapse
I have the exact same problem. I posted a thread pretty much identical to this one. Still no answer...
busybox mount -o rw,remount /system
worked for me. Once remounted I could rename the startup/shutdown sounds.
Thanks guys for responding, Thats it. Once I installed Busy Box i was able to move those files again. I guess after the JI6 update, it removes your previously installed busy box. I coulda swear i had busy box already installed when i was using titanium backup. But then I remember i had to Re-Root the phone as well.
rmeden said:
busybox mount -o rw,remount /system
worked for me. Once remounted I could rename the startup/shutdown sounds.
Click to expand...
Click to collapse
So just to be clear....type that string exactly as shown into terminal on the phone and that's it? Then I can delete (not rename) the sound files?
yes. you should have needed to do it the first time, too... /system is always mounted read-only.
and you also need a root shell (su)
chui101 said:
yes. you should have needed to do it the first time, too... /system is always mounted read-only.
and you also need a root shell (su)
Click to expand...
Click to collapse
Sweet! That worked for me! I had to change back to the samsung keyboard because everytime I used the , key in terminal SwiftKey would crash.
No more obnoxious startup/shutdown sounds! Woooo hoooo! Made my Friday!
So, I'm rooted. S=OFF, I get su access in Terminal, and I have the latest busybox installed in /system/bin. But, after a reboot of the device I can only get R/W access to certain parts of the directory structure - /system is unfortunately not one of them.
Now, here's the weird part: When I start the app Busybox Installer (downloaded from the market), the app searches for busybox installations and tells me I have the latest in /system/bin (this I already know). Once I have started this Installer without doing anything else, I can gain full R/W access to /system.
So, there seems to be some sort of strange busybox issue and how it relates to system R/W access. Is the latest busybox incompatible with this stock ROM?
Root explorer issues
I am also having the same issue I can not get R/W access in the system folder. I have been trying to re-map the Genius button. I am able to remove "bloatware" by using Titanium backup. I definitely have permanent root on the phone, so I am confused by this issue. I have been searching and have not seen other similar complaints. I tried the busybox from the above post but still am not able to R/W access.
You need the latest version of root explorer. Will solve the issue.
Sent from my HTC Glacier
Since updating to the new froyo I have root, but I cannot get root explorer to be able to access /system in any way possible, it reads it but cannot write/modify.
I have replaced every root file with a new version, even tried the /system on boot set to r/w method with that market app. Its getting frustrated as this has ALWAYS worked before.
Did you come from voodoo?
Sent from my SCH-I500 using XDA App
I had a lot of trouble with Root Explorer as well. Super Manager has worked much better with the r/w access.
Sent from my SCH-I500 using XDA App
I'll give it a shot using that other app and see what happens.
That app still only has r/o access. Super user isn't granting my phone r/w access for /system.
Ev3rM0r3 said:
Since updating to the new froyo I have root, but I cannot get root explorer to be able to access /system in any way possible, it reads it but cannot write/modify.
I have replaced every root file with a new version, even tried the /system on boot set to r/w method with that market app. Its getting frustrated as this has ALWAYS worked before.
Click to expand...
Click to collapse
You positive you still are root? Try the root process again just for ****s and giggles...
Run one of the following with your phone connected to your computer and try again.
Voodoo:
Code:
adb shell mount -o remount,rw -t ext4 /dev/block/stl9 /system
Non-Voodoo:
Code:
adb shell mount -o remount,rw -t rfs /dev/block/stl9 /system
Yes, I'm getting this too.
Not only this. I use android commander to see what's in the folders.
While I'm in CWM in the phone, Android Commander shows only one folder in /system. That folder is /system/etc. This might explain why I can't flash anything into my phone to save my life. Anyone know what could be causing this?
It's odd because when my phone boots up, Android Commander shows /system will all of it's glory...
ev3rm0r3 said:
since updating to the new froyo i have root, but i cannot get root explorer to be able to access /system in any way possible, it reads it but cannot write/modify.
I have replaced every root file with a new version, even tried the /system on boot set to r/w method with that market app. Its getting frustrated as this has always worked before.
Click to expand...
Click to collapse
and don't double post!!!
http://forum.xda-developers.com/showthread.php?t=955487
I have the exact same issue. Just talked it over with Adrynalyne.
You are going to have to download an All-In-One Odin Package such as
http://forum.xda-developers.com/showthread.php?t=867648
Then, you're going to have to start over and flash your CWM Recovery from jt
http://forum.xda-developers.com/showthread.php?t=942021
Then you Odin flash the modem of the ROM that you want to install, then you use CWM to flash the ROM that you want to install...
Make sure that you do to not flash using Phone. Use PDA option in Odin.
Apparently, it's a corrupt dbdata partition that is causing it. This can happen occasionally when installing VooDoo... Just another reason to stay away from VooDoo...
BTW, Is this working for you? I think it's working for me as of yet. I'm not done yet so I can't assure you yet.
I don't think is working for me... If it worked for someone else let me know. I don't know what happened.
Re-establishing ROOT using CWM with Adrynalyne modified ChainsDD superuser +busybox package from the link below...
http://forum.xda-developers.com/showthread.php?t=913470
I just installed root explorer and set my system to RW, I can see it all the way through in ADB. Then I re-locked it in root explorer.
Upgraded from factory rooted image of 4.3 to the OTA KRT160 I was able to get this rooted and the bootloader has been unlocked.
Cannot mount /system as r/w from either ROM Pro toolbox or ES Files Explorer. 4.3 has no such issues. Anyone else having these problems or know a way to mount this. I want to update my hosts file and a few other things.
Edit: This method works, just not any apps
adb shell
$su
#mount -ro remount,rw /system
make changes in shell
#mount -ro remount,ro /system
zosimov21 said:
Cannot mount /system as r/w from either ROM Pro toolbox or ES Files Explorer. 4.3 has no such issues. Anyone else having these problems or know a way to mount this. I want to update my hosts file and a few other things.
Edit: This method works, just not any apps...
Click to expand...
Click to collapse
Tried that on a rooted Moto X...still no joy. Among other things, it's keeping AdAway from installing.
Edit: I eventually found MotoWpNoMo, which fixed my problem. It permanently removes write protection from /system. Maybe there's something similar for your device.
I had an issue with read write in es. You have to not only slide the root explorer option to on but also tap on root explorer text to change system to r/w. Hope this helps
phatscientist said:
I had an issue with read write in es. You have to not only slide the root explorer option to on but also tap on root explorer text to change system to r/w. Hope this helps
Click to expand...
Click to collapse
Man I've been looking for your tip 2 days. And here you go. Awesome. Same thing with H/K LiveStage sound buried under option line.
I've flashed the latest Android 5.0 build (LRX21T) to my Nexus 4 using the flash-all script. Then I flashed CF-Auto-Root for build LRX21T using the root-windows script. I now have the SuperSU app installed and I can grant superuser permissions.
The problem is that apps that require root don't really seem to get root, even if I granted superuser permissions. Some apps just get stuck, some give error messages and others just don't do anything. I also can't remount /system as rw myself using a terminal emulator. I've installed BusyBox in both /system/xbin and /system/bin, but it's still not working.
Apps that don't work: ES File Explorer, Cabinet, App Eater, Build Prop Editor, Root Uninstaller...
I just want to edit my build.prop and delete some system apps. Does anyone have the same problem or knows a way to at least edit build.prop?
Thanks!
The issues in this thread are similar to my issue, but I can't find a solution there.