Android TV Launcher Pushed to Google Play

Over the past decade, the tech universe has seen two drastic and widely contrasting changes with … more

Cyngn, OnePlus, Micromax – The Legal Battle

Recently, a battle has been waging in India over the rights to distribute the commercial … more

Lean Mean Battery Power Saving App Review

We talk a lot about battery topics here at XDA TV. We talk about everything from Power Banks to USB … more

Android 5.1 Possibly Coming February 2015

Google released Android 5.0 just over a month ago, and since then Lollipop has been trying to … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] How can I mount /system as writeable in adb shell?

OP CelticWebSolutions

17th December 2011, 01:00 PM   |  #1  
CelticWebSolutions's Avatar
OP Senior Member
Thanks Meter: 2,022
 
736 posts
Join Date:Joined: May 2011
Donate to Me
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?

Thanks!
17th December 2011, 06:53 PM   |  #2  
hwong96's Avatar
Senior Member
Flag Chicago
Thanks Meter: 249
 
757 posts
Join Date:Joined: Oct 2011
More
Quote:
Originally Posted by CelticWebSolutions

I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?

Thanks!

mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system

Type mount to verify rw, make your changes

mount -o ro,remount -t ext4 /dev/block/mmcblk0p8 /system

Type mount to verify ro
The Following 7 Users Say Thank You to hwong96 For This Useful Post: [ View ]
17th December 2011, 10:40 PM   |  #3  
CelticWebSolutions's Avatar
OP Senior Member
Thanks Meter: 2,022
 
736 posts
Join Date:Joined: May 2011
Donate to Me
Thank you!
6th November 2014, 11:07 AM   |  #4  
Junior Member
Thanks Meter: 2
 
16 posts
Join Date:Joined: Feb 2014
Quote:
Originally Posted by hwong96

mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system

Type mount to verify rw, make your changes .....

I don't have this tablet but a phone with similar problem.

this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.

I get this message:

error
"the item "system" is read only"

I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.

I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.

very annoying...
Last edited by Jack_Rover; 6th November 2014 at 12:14 PM. Reason: clarify...
6th November 2014, 06:56 PM   |  #5  
hwong96's Avatar
Senior Member
Flag Chicago
Thanks Meter: 249
 
757 posts
Join Date:Joined: Oct 2011
More
Quote:
Originally Posted by Jack_Rover

I don't have this tablet but a phone with similar problem.

this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.

I get this message:

error
"the item "system" is read only"

I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.

I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.

very annoying...

I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. Anyway, since you have asked I'll answer. The mount point for /system is different on each phone model. There is no one standard /system mount point. On the Nook Tablet and Nook Color it is mmcblk0p8. On your device it is different, so the command you tried will not work.
You need to find out what the /system mount point is for your phone.
Open terminal from phone and type su.
Press enter.
At the # prompt type cat /proc/mtd
Press enter.
Look at the output on the screen and see what the mount point is for /system.
A the the # prompt type mount -o rw,remount -t ext4 /dev/block/enteryoursystemmountpointhere /system
Note: replace enteryourmountpointhere with your mount point from the previous step.

Change /system to ro when done. Hope this works for you.

Also download root checker app to ensure you rooted properly.
Last edited by hwong96; 6th November 2014 at 10:14 PM.
6th November 2014, 08:37 PM   |  #6  
Junior Member
Thanks Meter: 2
 
16 posts
Join Date:Joined: Feb 2014
Quote:
Originally Posted by hwong96

I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. ......

thanks for your responce.

with that "cat ..." I got : "no such file or dir"...

I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /emmc@android /system

but no success, " system read only" stays, and no change.
6th November 2014, 10:17 PM   |  #7  
hwong96's Avatar
Senior Member
Flag Chicago
Thanks Meter: 249
 
757 posts
Join Date:Joined: Oct 2011
More
Quote:
Originally Posted by Jack_Rover

thanks for your responce.

with that "cat ..." I got : "no such file or dir"...

I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /emmc@android /system

but no success, " system read only" stays, and no change.

Did you use the root checker app to verify for proper root?
7th November 2014, 10:12 AM   |  #8  
Junior Member
Thanks Meter: 2
 
16 posts
Join Date:Joined: Feb 2014
Quote:
Originally Posted by hwong96

Did you use the root checker app to verify for proper root?

yes.

I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.

I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).

somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.

MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".

maybe kernel related? or boot loader, or .... what?

-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Last edited by Jack_Rover; 7th November 2014 at 10:37 AM. Reason: clarify...
7th November 2014, 03:53 PM   |  #9  
hwong96's Avatar
Senior Member
Flag Chicago
Thanks Meter: 249
 
757 posts
Join Date:Joined: Oct 2011
More
Quote:
Originally Posted by Jack_Rover

yes.

I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.

I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).

somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.

MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".

maybe kernel related? or boot loader, or .... what?

-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....

Don't know what else to suggest, except maybe contact Chainfire on G+.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes