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.
Related
I'v just rooted my Tab, I don't know if I'm losing the plot but I can't figure out how to write to the system partition? I can't find any apps that will work (for free) and "adb remount" doesn't work. "remount failed: Operation not permitted"
Am I missing something?
alias_neo said:
I'v just rooted my Tab, I don't know if I'm losing the plot but I can't figure out how to write to the system partition? I can't find any apps that will work (for free) and "adb remount" doesn't work. "remount failed: Operation not permitted"
Am I missing something?
Click to expand...
Click to collapse
adb remount doesn't work because /default.prop needs ro.secure set to 0 (not 1). This can't be changed easily without modifying the boot.img.
However, you can remount /system as a r/w filesystem using ADB by opening a shell and:
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p1 /system
or
Code:
su
mount -o rw,remount -t ext3 /dev/mtdblock3 /system
Regards,
Dave
foxmeister said:
adb remount doesn't work because /default.prop needs ro.secure set to 0 (not 1). This can't be changed easily without modifying the boot.img.
However, you can remount /system as a r/w filesystem using ADB by opening a shell and:
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p1 /system
or
Code:
su
mount -o rw,remount -t ext3 /dev/mtdblock3 /system
Regards,
Dave
Click to expand...
Click to collapse
Thanks, so which should I actually use, the former or the latter?
I've personally used the first command, but I saw the second one on another thread and it seems to work as well.
To be honest, I think it's ignoring the parameter anyway.
Regards,
Dave
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**
I am trying to copy modules to /system/lib/modules/. I have rooted with Gingerbreak. I have superuser permissions both with adb and from terminal emulator. I have changed system to rw both from TE and with ADB. I used this command: mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 system/ What am I doing wrong. System shows up as mounted rw when checking with cat /proc/mounts
Well, that basically works for me, but unless you did a typo on the "system/" only in the forums you got it slightly wrong.
su
mount -o remount,rw /dev/block/mmcblk0p3 /system
Click to expand...
Click to collapse
You don't need the "-t ext4" option.
Do I need busybox? It wasn't a typo. I get "permission denied" when I try to push the file. Not "access denied" as in the name. If it makes any difference. I have tried to cp from adb shell also. Same problem.
After installing busybox all went fine.
[WTF][4.2.2] "mount -o remount ro /" doesn't work but "mount -o remount,ro /" does??
Mod: You can delete this thread... Sorry, I was so nervous about that....
Hey Guys,
I was developing on my kernel in init.rc and I recognized that / doesn't get remounted read-only in my script.
I couldn't understand that. The command runs, but / don't get mounted ro. WTF???!
So I tested a bit and here is what I found out:
Code:
mount -o remount rw /
remounts / rw.
Code:
mount -o remount ro /
Doesn't remount / read-only.
Instead,
Code:
mount -o remount,ro /
works.
What the hell is going on here??!? I am using Android 4.2.2. Also happens with stock-kernel. Can someone confirm this?
I am pretty sure I used the old command on Android < 4.2.2 and it worked. Or?!
It doesn't matter if you use toolbox or busybox.
Thanks,
vorcers
Edit:
ahh,
Code:
mount -o remount /
remount's / rw. That solves the mystery. :silly:
This also happens on real systems. I think there is some bug in mount / the remount option. Because any word behind remount and prior / is ignored / no error. Instead, if you swap ro and remount, mount prints errors.
I am trying to create an overlay folder under /system/vendor so that I can throw a layers apk there to hide the nav bar. I am currently using the build.prop method which doesn't work nicely with the Now on Tap action of Swipe Navigation which is what I am ultimately trying to fix.
I tried using Solid Explorer to simply create the new directory like I did previously in 7.0 and 6.x but was unable to do so (action failed). I decided to try using the terminal and create the folder and move files from there but got the message that the system was read-only. I then attempted to mount system a few different ways all of which failed. I did use su before entering these commands.
Code:
angler:/system/vendor $ mkdir overlay
mkdir: 'overlay': Read-only file system
angler:/system/vendor $ mount -o rw,remount,rw /system
mount: '/dev/block/platform/soc.0/f9824900.sdhci/by-name/system' not user mountable in fstab
angler:/system/vendor $ /system/bin/mount -o rw,remount,rw /system /system
mount: '/system' not in /proc/mounts
angler:/system/vendor $ /system/bin/mount /system
mount: bad /etc/fstab: No such file or directory
Googling around didn't yield much in the way of solutions other than these different methods of mounting system. Am I just unable to mount system as rw in 7.1.1 currently, and if so, is there another way to accomplish what I want?
I'm trying to find thread I read this from, so if I find it I'll post link to it. When I was on early 7 previews that was set up with systemless root I went into twrp and then went to terminal and typed the following, touch su. When your in terminal cd to both bin and xbin and type command "touch su" without quotes. Then reboot and you should be able to use something like es file explorer to get into and write in /system. Hope that helps.
Found it, look to post = 15
http://forum.xda-developers.com/nexus-6p/help/es-file-explorer-doesnt-understand-t3242775
Unfortunately that did not end up working for me, thanks for looking up the link for me though!
On Nougat the rw mount command should be typed like this:
mount -o rw,remount /system
then for touch:
touch sbin/su
Thank you blitz for clarifying.
Hmm... it seems like the mount worked but the touch did not. I ended up using just "touch su" but ran into a different error with mkdir. I think I may just be out of luck for now. Thank you both for your help!
Code:
~ # mount -o rw,remount /system
~ # cd /system/bin
/system/bin # touch sbin/su
touch: sbin/su: No such file or directory
/system/bin # touch su
/system/bin # cd /system/xbin
/system/xbin # touch su
/system/xbin # cd /system/vendor
/vendor # mkdir overlay
mkdir: cannot create directory 'overlay': No space left on device
AbuShabanov said:
Hmm... it seems like the mount worked but the touch did not. I ended up using just "touch su" but ran into a different error with mkdir. I think I may just be out of luck for now. Thank you both for your help!
Code:
~ # mount -o rw,remount /system
~ # cd /system/bin
/system/bin # touch sbin/su
touch: sbin/su: No such file or directory
/system/bin # touch su
/system/bin # cd /system/xbin
/system/xbin # touch su
/system/xbin # cd /system/vendor
/vendor # mkdir overlay
mkdir: cannot create directory 'overlay': No space left on device
Click to expand...
Click to collapse
I'm not sure what you're trying to accomplish but still:
The touch sbin/su means creating an empty file called su in the sbin subdirectory under the current directory. So if there is no subdir named sbin under /system/bin, then it's not going to work
Secondly, you should know about the ls command: ls -la lists the files in the current directory, and remember than in unix and linux terminology, a directory is also a file so you'll also see directories (including current "." and parent "..")
Third, you should know about the df command which shows filesystem disk space usage. df -h will show you how much free space you have an all of your filesystems, including system.
Last, with great power comes great responsibilities. Running the wrong command as root will easily make your system unusable.
I have substratum installed and inside /system/vendor there is a link (again a file) called overlay which links to directory /system/overlay where apks are.
rchtk said:
I'm not sure what you're trying to accomplish
Click to expand...
Click to collapse
I am trying to create an overlay folder under /system/vendor so that I can throw a layers apk there to hide the nav bar.
rchtk said:
I have substratum installed and inside /system/vendor there is a link (again a file) called overlay which links to directory /system/overlay where apks are.
Click to expand...
Click to collapse
Are you on the 7.1.1 (NPF10C)? If so it sounds like you have accomplished what I am trying to do. I'm only familiar with the basic unix commands as I haven't actively used it in about 5 years. Would you mind sharing how to create the link to /system/overlay from /system/vendor, or does Substratum take care of that? Offhand it sounds like a symbolic link but my terminology is pretty rusty.
AbuShabanov said:
I am trying to create an overlay folder under /system/vendor so that I can throw a layers apk there to hide the nav bar.
Are you on the 7.1.1 (NPF10C)? If so it sounds like you have accomplished what I am trying to do. I'm only familiar with the basic unix commands as I haven't actively used it in about 5 years. Would you mind sharing how to create the link to /system/overlay from /system/vendor, or does Substratum take care of that? Offhand it sounds like a symbolic link but my terminology is pretty rusty.
Click to expand...
Click to collapse
Yes 7.1.1.
Substratum created the overlay directory and the link to it.
Manually that would be:
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
mkdir /system/overlay
cd /system/vendor
ln -s /system/overlay
mount -o ro,remount -t auto /vendor
mount -o ro,remount -t auto /system
But links do take a very small amount of bytes (roughly name and target) so for that, you'll need some space in your vendor partition (no space left on /vendor). check with "df".
I have 3.8MB free (that's an original vendor + overlay link)
rchtk said:
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
mkdir /system/overlay
cd /system/vendor
ln -s /system/overlay
mount -o ro,remount -t auto /vendor
mount -o ro,remount -t auto /system
Click to expand...
Click to collapse
Well, this works and I was able to mount system and vendor, create the link, move the apk file, etc but it appears that the apk itself is not working on NPF10C. Thank you for your help and the refresher on the unix commands!