Hello, all!
I'm trying edit a file in /etc/ and adb says 'Failed to copy: Read-only filesystem'
Now, is this actually true? Or is this simply a permissions issue? I'm doing this on a non-rooted phone, so I can't 'touch' anything without permission errors, but is it a futile task if the filesystem is read only anyway?
I'm trying to do this from a non-rooted environment as I had intended on making this into an application, but I imagine that if I can't touch or push these files from an adb shell then I won't be able to from the application space either.
It's frustrating not to be able to edit the filesystem of my own phone, I'll be rooting if this is just a permissions problem and not an issue of a non-writable filesystem. Perhaps I could still make an application for rooted-only phones.. hrm..
Any thoughts on this?
/etc is an alias for /system/etc, and /system is a partition mounted as ro (you can confirm this yourself by running mount)
Ah, bugger. So this is hopeless (without modifying and then reflashing)?
Thanks very much.
you need to mount it read write,
mount -oremount,rw /dev/block/mtdblock3 /system
then it will be read/write
try adb remount. if it failes you need root sorry.
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
nvm I figured it out. i just put it on system and then just type sh debian.sh on the terminal and it works
Rafase282 said:
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
Click to expand...
Click to collapse
what is the error message? saying it dont work doesnt provide enough info for us to help....
it says sh: cant open aw.sh
so i still have to put the path or cd to where the file is. Is there a way to make /system my home?
no you cant make system your home, system is system, home is home. you can make a symlink if you are familiar with linux - might want to read up about shell commands
korndub said:
you need to mount it read write,
mount -oremount,rw /dev/block/mtdblock3 /system
then it will be read/write
Click to expand...
Click to collapse
Thanks it really worked!! for me i had the same problem as the other guy.
Rafase282 said:
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
nvm I figured it out. i just put it on system and then just type sh debian.sh on the terminal and it works
Click to expand...
Click to collapse
You *CAN'T* modify the / filesystem. It is part of your BOOT partition, which CANNOT be remounted rw. You would have to read, modify, and write the boot partition.
Rafase282 said:
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
nvm I figured it out. i just put it on system and then just type sh debian.sh on the terminal and it works
Click to expand...
Click to collapse
Maybe you're typing it in too literally. It should actually read like this:
mount -o remount,rw /dev/block/mtdblock3 /system
There was a typo with -oremount, there should be a space after -o.
Hope that helps.
PS. That command worked for me on a device where everything else failed.
dhkr123 said:
You *CAN'T* modify the / filesystem. It is part of your BOOT partition, which CANNOT be remounted rw. You would have to read, modify, and write the boot partition.
Click to expand...
Click to collapse
actually, / can be mounted rw, but changes are lost on reboot
new user
Firerat said:
actually, / can be mounted rw, but changes are lost on reboot
Click to expand...
Click to collapse
Hi I have my Asus Prime rooted and installed a virtuous Rom and I tried to put a fonts on the System/ fonts folder using root explorer using a instructions to fix some error on some games that need that tis fonts exist on the tablet but it said it cant because file system is read only I'm new and I don't know how to do this commands any help on how to do in a easy (explained) form.
egalpr said:
Hi I have my Asus Prime rooted and installed a virtuous Rom and I tried to put a fonts on the System/ fonts folder using root explorer using a instructions to fix some error on some games that need that tis fonts exist on the tablet but it said it cant because file system is read only I'm new and I don't know how to do this commands any help on how to do in a easy (explained) form.
Click to expand...
Click to collapse
I would recommended not posting in the g1 section. The Asus forums would be a lot more helpful.
egalpr said:
Hi I have my Asus Prime rooted and installed a virtuous Rom and I tried to put a fonts on the System/ fonts folder using root explorer using a instructions to fix some error on some games that need that tis fonts exist on the tablet but it said it cant because file system is read only I'm new and I don't know how to do this commands any help on how to do in a easy (explained) form.
Click to expand...
Click to collapse
Download EStrong File Manager and within the settings of it, enable mounting of the system as read/write.
Or, download Terminal Emulator and type this in:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
Or, try typing this in terminal/cmd:
Code:
adb remount
Or, if you plan on doing it all from recovery you could do:
Code:
adb shell "mount system"
and then you could do it all from there.
Next time, please post in the proper forum.
Read-Only /system... i just deleted the file, tich push should update/replace and then it worked... only had this bug when i was trying to modify Trebuchet.apk (homescreen)
Hi guys
Not being a linux expert, i'm stuck with the following problem..
i'm using a program who uses low level adb commands to write on the phone extSdCard...
problem: this extSdcard is seen as a readonly filesystem.
What has to be done to make this FS RW instaed of RO ?
This does not happen under windows where I can write to the extSd without problems
thks in advance for the tip
Yes, my phone is a chinese Hero H2000+.
I have managed to stick su and busybox into /system/bin using debugfs, but there's absolutely no way I could find to make /system get into read-write mode.
If I type "mount -o rw,remount /system" it seems to work for about 1 second, but then it's remounted read-only. All the changes will be reverted (files I add/remove via script). If I try to run the same command again, it will show me a message saying filesystem is read only.
Does anyone know what might be causing this?
Thanks in advance.
Hi,
I just bought a cheap simple ARNOVA84 tablet (for 50 €) with android 2.1 to play a little bit and gather experience regarding rooting before I do this on my acer A511
I came so far, that I got adb shell with root ($ -> #). But to get SuperUser or SuperSU running I need also su in /system/bin. But /system is ro. The command
# mount -o rw,remount /dev/mtdblock4 /system
does not work in any combination. I get no error, but
# mount
still shows /system ro
To remount /system google said, I would need su, which in turn I don't have yet I copied su binary to another folder and changed permission to 755. But nevertheless su seems not to work. It just gives me new line with no # and everything I type in, is repeated. I have to break shell with ctrl-c.
The /system is a cramfs and my latest information is, that cramfs is always ro and can not be changed.
1. Is this true and does it mean I can root my tablet only be upgrading it with a modified update.img containing su etc.?
2. Is there no other more safe way to root such device?
3. Does this also mean more modern tablets have another filesystem for /system?
thanks!
Rainer
I have a Sony xperia M2 D2303 with kitkat 4.4.4 and compilation number 18.3.1.C.1.17.
I have successfully rooted it using KingRoot v4.9.5.
Also I have checked that system is rooted using tools such as root checker and it says rooted.
Now, I am trying to remount /system partition as RW but without succcess.
I have googled and tried several solutions posted here but nothing works for me.
Access to /sys/kernel/security/sony_ric and try to disable sony ric security using:
problem here is that sony_ric folder is empty, I mean, there is no "enable" file and I cannot create it as partition is RO (read-only).
Using ES file explorer or other file explorers as root I have tried to remount partition as RW but it fails.
Code:
echo 0 > enable
Using ROM Toolbox pro, and then from terminal emulator I have tried some commands:
Code:
su
mount -o remount,rw /system
fails.
Code:
su
system/bin/mount -o remount,rw /system
also fails.
Code:
adb shell
su
mount -o rw,remount /system
also fails...
I have tried to install busybox but it fails as well.
I have tried the method explained here but when executing the command:
sh /sdcard/mrw/root.sh
some errors appear as script tries to do things in /system so since it is read-only (not rw) it fails.
Also I have tried the method using SuperSu-me explained here but without success. It completes ok but then SuperSu is executed automatically. SuperSu says to update binaries so I update binaries, then another screen comes saying that another root app was detected, so I press the button to uninstall it and continue installing SuperSu. SuperSu says "Installing ........" and then it crashes, that is, it appears a screen with two buttons, "How to update" and "Reboot". Kingroot, purify apps continued installed and working, and I cannot replace them with SuperSu.
So at this point I have no idea what to do...
My conclusion is that all these tools need to make changes to / and /system but since I have these two partitions set to read-only (cannot make them rw) then all these tools fail. So I think the main cause is that I have / and /system readonly.
Any help will be highly appreciated.
Please, help!
For some reason I have never been able to mount my system r/w through adb or terminal emulator. I'm not quite sure what I'm doing wrong since I've been doing it for years now. I imagine it has to do with root. I can use ES file explorer and modify system to my hearts content just not through adb or terminal emulator. I am on 7.1.1 Pure Nexus with ElementalX 1.08 and SuperSU with 2.79 binaries. I've tried to mount multiple different ways and all result in same error.
Code:
sailfish:/ # mount -o remount,rw /system
mount: '/dev/block/bootdevice/by-name/system_b'->'/system': Device or resource busy
Nvm found it. I guess it's same as Pixel C.
Code:
mount -o rw,remount /system
Geofferey said:
For some reason I have never been able to mount my system r/w through adb or terminal emulator. I'm not quite sure what I'm doing wrong since I've been doing it for years now. I imagine it has to do with root. I can use ES file explorer and modify system to my hearts content just not through adb or terminal emulator. I am on 7.1.1 Pure Nexus with ElementalX 1.08 and SuperSU with 2.79 binaries. I've tried to mount multiple different ways and all result in same error.
Code:
sailfish:/ # mount -o remount,rw /system
mount: '/dev/block/bootdevice/by-name/system_b'->'/system': Device or resource busy
Click to expand...
Click to collapse
Same here but with Oneplus 3T.
I think its kind of encripted "new way" in Android 7.1.1
Also, if you check the magisk thread there is a way to use the mount remount command inside root browser
mate9-109 said:
Same here but with Oneplus 3T.
I think its kind of encripted "new way" in Android 7.1.1
Click to expand...
Click to collapse
Nope just a different mount syntax not encrypted at all. I was kinda thinking same at first like a security feature or root keeping you from so you don't accidentally modifying system.
mount -o rw,remount /system
Instead of
mount -o remount,rw /system
Geofferey said:
Nope just a different mount syntax not encrypted at all. I was kinda thinking same at first like a security feature or root keeping you from so you don't accidentally modifying system.
mount -o rw,remount /system
Instead of
mount -o remount,rw /system
Click to expand...
Click to collapse
Sadly I tried your new syntax, adb did some stuff, but it does not work either.
Anyway thank you very much, your solution almost got it.
:good::good::good::good::good: