[Q] /system mount rw on kitkat? - Nexus 4 Q&A, Help & Troubleshooting

I have a rooted stock kitkat nexus 4. I've been trying to use various sql editors to edit some values and it always fails, despite getting the popup that root has been enabled for the application.
It looks like the problem is /system is mounted ro and never manages to get remounted rw.
I tried running an app that does nothing but remount /system, which gets the same success popup but also does not change the mount to rw.
If I adb to shell, I get a non-root shell and "su" just hangs.
All the apps that want su access say they have succeeded in getting it. Ideas?

I have no idea. You may need to use a custom ROM? Your best bet is mounting it in recovery and editing the filesystem from outside.

Try to use es file explorer. It has an option to mount system rw. Always worked for me.
Sent from my Nexus 4 using xda app-developers app

Ok, I know a little bit more. The reason my adb shell was hanging on "su", was the supersu popop on the phone which I wasn't looking at.
Now I can get a root shell.
The interesting thing is that how the mount ro/rw option appears is dependent on the permission of the process. For example:
# adb shell
[email protected]:/ $ mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/ $ su
[email protected]:/ # mount |grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
That said, its not so clear if the mount permission is what I'm actually fighting. I'm trying to use sqlite to toggle preferred network mode.
One way to do that is by installing sqlite3 in /system/bin. There is an app for that but it fails, I assume because of the mount but maybe for some other reason.
Now that I have a root shell I could install sqlite3 manually, but I haven't been able to find a copy of the binary.

Ok, found a working sqlite3, installed it manually from the shell and all is well. In case anyone else is looking for one, I got it at
http://forum.xda-developers.com/attachment.php?attachmentid=1236218&d=1343863492

Related

with su access cannot modify /system

ok i have root access with busybox and su installed yet in terminal editor and adbshell i cannot remount my system as rw does anyone know why
ok update i got around my issue by using root explorer to get rw access on the system but still want to know why i cant do this
Sprint tab
How are you remounting it?
I always have good success with:
Code:
adb shell
su
remount rw /system
that is the exact code i have used and it gives me a not found error
Hmm. Check to see if /system/xbin/remount exists. If not, use Root Explorer to place this script at that location:
Code:
#!/system/bin/sh
#simplify mount rw and mount ro
#scripting wrote by forcystos - SDX - sdx-developers.com
#updated for samsunge epic by joeykrim - SDX - sdx-developers.com
case $1 in
rw)
echo "Remounting /system (/dev/stl9) in read/write mode"
/system/bin/mount -o remount,rw /dev/stl9 /system;;
ro)
echo "Remounting /system (/dev/stl9) in read-only mode"
/system/bin/mount -o remount,ro /dev/stl9 /system;;
*)
echo "usage: remount rw -or- remount ro";;
esac
Remember to change mode to 744 before executing.

Terminal command help remount help

I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now, and now I'm here. What am I doing wrong? Thanks
there
Code:
mount -o remount,rw /dev/mmcblk0p12 /system
back
Code:
mount -o remount,ro /dev/mmcblk0p12 /system
Hmm, well at least I didn't get any errors this time.
I didn't get a confirmation or that it did anything at all. Is that normal?
Run mount with no parameters and look for the line with that device name, should see rw in that line instead of ro.
Sent from my MB860 using XDA App
Thanks guys, but I resorted to busybox chmod command instead lol
I tried this and got no errors, and using cat /proc/mounts/ I see the path as rw. But when I try to copy I still get the read only file system error.
**Lol, I had the phone in usb storage mode and had to switch it to Windows Media Sync**

Unable to read/write in /system

I have been trying to add/remove files in my /system directory but I'm having quite the difficulty.
The adb terminal already has SU access, I get a #.
I've tried mount -o remount,rw /system and then going back into ASTRO to paste something but it won't let me
I did also try cd /system after trying that but it doesn't do anything....
I've also tried adb remount but I get access denied.
Is it that I need Root Explorer or is there no avail?

[Q] /system automatically remounts as ro

I'm rooted via the standard root, with CWM installed.
When I attempt to mount /system as read-write with mount -o rw,remount /dev/block/system /system, about 10 seconds later it remounts as -ro.
This means I can't change anything on there, is anyone else having this issue and is there a fix?
MrLadoodle said:
I'm rooted via the standard root, with CWM installed.
When I attempt to mount /system as read-write with mount -o rw,remount /dev/block/system /system, about 10 seconds later it remounts as -ro.
This means I can't change anything on there, is anyone else having this issue and is there a fix?
Click to expand...
Click to collapse
I had a similar problem once and I fixed it by restoring an old nandroid backup, I was never able to figure out what caused it.
I had the same issue when I installed the ota2 update, then tried to reroot. I think I was able to change permissions by installing, then opening superuser app.
Im on OTA1.
Hello,
I've got the same problem. With the following programs i have read/write access to /system only for seconds:
Esexplorer, file manager hd, root explorer, total commander , especially: adb shell
Strange thing: i have no problems with permissons when using x-plore or titanium backup.
(Currently OTA2)
Installing superuser again does not fix anything.
I have the same problem here (OTA2) :-/
A workaround I found is to chain the remount-command with the command you want to execute on /system:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/mmcblk0p3 /system && cp /sdcard/Download/kernel_modules/cifs.ko /system/lib/modules/
# ls /system/lib/modules/
bcm4329.ko
cifs.ko
scsi_wait_scan.ko
Brilliant!

Problem with Relaunch

The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
gsms said:
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
Click to expand...
Click to collapse
So, basically you are without an Android launcher or file manager?
If you made a backup with NookManager, restoring it is your best bet. If not, make sure to do so once this is sorted out. Backup early and often.
Do you have wireless ADB working? You can install (or reinstall) apps that way. Or, if you have the Market working, install any file manager that will work. That will give you access to folders again and you can copy over apps via USB and then use the file manager to install them.
I have installed adb thru usb, but now have other problem.
Trying to copy file(s), it gives me message ,that folder is read-only.
What is exact command to mount folder as read-write in adb shell ?
I tried many times - with no success...
non working-
adb remount /system/
adb remount
adb remount root/system/
and so on.................................
Please help
gsms said:
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
Click to expand...
Click to collapse
Have you tried downloading the Relaunch.apk file via a web-browser? Once the download is completed you should get a prompt on whether you want to install it.
---------- Post added at 04:27 PM ---------- Previous post was at 04:19 PM ----------
gsms said:
I have installed adb thru usb, but now have other problem.
Trying to copy file(s), it gives me message ,that folder is read-only.
What is exact command to mount folder as read-write in adb shell ?
I tried many times - with no success...
non working-
adb remount /system/
adb remount
adb remount root/system/
and so on.................................
Please help
Click to expand...
Click to collapse
To mount /system as read+write:
Code:
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
exit
After you're done with copying over the desired file into /system, just reboot the nook to revert the mounting back to read-only.
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
gsms said:
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
Click to expand...
Click to collapse
The mount command line I provided is the correct command for your purpose. Note that the command is to be entered on the NST itself after you get on it using "adb shell" command.
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
Click to expand...
Click to collapse
The folder permission 755 is inoperative since the filesystem itself is still being mounted read-only.
gsms said:
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
Click to expand...
Click to collapse
I have been able to successfully achieve this with this command:
mount -o remount rw /system
The command is simpler and thus I am less likely to make a typo.
Thanks for your entries, but i already re-rooted my Nook.
I was out of nerves to deal with adb shell....
----------------
But using "mount" command thru adb shell could be very helpful in some critical cases....
gsms said:
Thanks for your entries, but i already re-rooted my Nook.
I was out of nerves to deal with adb shell....
----------------
But using "mount" command thru adb shell could be very helpful in some critical cases....
Click to expand...
Click to collapse
Make a backup

Categories

Resources