hi guys,
i hope someone can help me out with this;
i have rooted my DHD with Visionairy and all works fine, except...
doh...i forgot to check the option to set rw on /system partition
now i have tried the following from Terminal App;
#su
#mount -o rw -t yaffs2/dev/block/mtdblock3 /system
i read somewhere that this should set rw on /system but it didn't work;
then i tried the 'Unroot Now' option in Visionairy but that doesn't work either....
how can i set rw on my /system partition??
thnx in advance!
odin
Hey mate, I had the same problem. Took a mistake while entering mount information before I figured out where I went wrong.
Try entering 'mount' by itself, you'll get all your relivant information. You need to find '/system' in the stings of information and then which 'mmcblk0p*' (the * will be a number, your folder might be something different, like mtdblock3) it is attached to.
I think some ROM's use different locations, as I was told something simmilar to you, which wasn't working, I'm no expert so I had to fiddle and look to find the right string.
For example mine goes;
/dev/block/mmcblk0p25 on /system type ext3 (ro,relatime,errors=continue,data=or)
This told me I had to enter the following string to set it to rw;
mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
This seemed to work for me, but I need to enter it every time I restart the handset and want to change something in the /system folder.
Related
Going through the steps in this thread to update the lockscreen images, I have a question about messing around with the system files.
Which is the better method?
1) While the phone is up and running, start adb shell and mount the system using this command:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
or
2) Boot into the modified recovery screen, start adb shell and then use these steps:
Code:
mount /system
{copy, move, edit files files... whatever...}
umount /system'
reboot
Would the second method be the more correct (or cleaner) method, or does it not really matter?
You might want to replace the second part with just
Code:
{copy,move,edit,etc}
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
The first step already mounts the partition so the mount in step 2 is kinda redundant. Also, a reboot can be helpful, I've not found it necessary in most cases...the phone adjusts pretty well to change usually (at least it adjusts to removal of programs or even taking rosie out and adding it back in).
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!
Hello!
I tryed to install the old ubuntu.bat, had a lot of problems, In the end, I tried to revert and put back the original webdock.
So, I made a mistake and the file mountosh disapears, but i have the mountosh.new in the /system/bin.
I tried to rename and I cant because I think the partition is read only now. unable to "chmod 755 /system/bin", i received the message "read-only file system"
anybody can help me?
I need to umount and remount the filesystem? (rootfs?), but how I make this?
"mount -o remount,rw /system" than when you are done "mount -o remount,ro /system"
Hi,
I'm new to Android, so please bear with me. I just recently picked up a Nexus 4 to play with. It came with 4.2 on it, and I have done the OTA updates to 4.3 and then 4.4. I decided to root the device and followed the instructions here. That all seems to work OK and I can get root using adb.
The first thing I tried to do next was change the hostname from android-something to a hostname that I could remember. I did a bunch of searching here and found the following commands suggested:
Code:
getprop net.hostname
setprop net.hostname
If I run these commands, the hostname changes. The problem is once I reboot, the name is back to what it was originally. I even tried remounting /system as rw, as I saw in some other post, and running the command again like this:
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
setprop net.hostname NEWNAME
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
I tried rebooting after that and the name change still doesn't stick. What am I doing wrong?
bigdweeb said:
Hi,
I'm new to Android, so please bear with me. I just recently picked up a Nexus 4 to play with. It came with 4.2 on it, and I have done the OTA updates to 4.3 and then 4.4. I decided to root the device and followed the instructions here. That all seems to work OK and I can get root using adb.
The first thing I tried to do next was change the hostname from android-something to a hostname that I could remember. I did a bunch of searching here and found the following commands suggested:
Code:
getprop net.hostname
setprop net.hostname
If I run these commands, the hostname changes. The problem is once I reboot, the name is back to what it was originally. I even tried remounting /system as rw, as I saw in some other post, and running the command again like this:
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
setprop net.hostname NEWNAME
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
I tried rebooting after that and the name change still doesn't stick. What am I doing wrong?
Click to expand...
Click to collapse
It shouldn't be changed
Anyway, try this https://play.google.com/store/apps/details?id=com.tiranodroid.change.hostname&hl=es
luiseteyo said:
It shouldn't be changed
Anyway, try this https://play.google.com/store/apps/details?id=com.tiranodroid.change.hostname&hl=es
Click to expand...
Click to collapse
Thanks for the reply. I had seen that there were apps for this, but I figured it would work on the cli if an app could do it.
Why do you say it shouldn't be changed? I've never had a device that you weren't supposed to change the name of.
Hi,
I am unable to edit build.prop (flashing B15 and B13-chinese bootstack enabled nav bar - I want to remove it) as I can not mount /system as RW. When doing so, either via Terminal, ADB Shell or simply a file explorer app, I generally get a "Device busy" error or some other random error.
I have tried those commands so far in Shell:
mount -o remount,rw /system
mount -o remount,rw -t ext4 /dev/block/bootdevice/by-name/system /system
All commands have been tried on the three available kernels.
Any help is much appreciated!