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!
CelticWebSolutions said:
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!
Click to expand...
Click to collapse
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
Thank you!
hwong96 said:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes .....
Click to expand...
Click to collapse
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...
Jack_Rover said:
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...
Click to expand...
Click to collapse
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.
hwong96 said:
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. ......
Click to expand...
Click to collapse
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 /[email protected] /system
but no success, " system read only" stays, and no change.
Jack_Rover said:
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 /[email protected] /system
but no success, " system read only" stays, and no change.
Click to expand...
Click to collapse
Did you use the root checker app to verify for proper root?
hwong96 said:
Did you use the root checker app to verify for proper root?
Click to expand...
Click to collapse
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....
Jack_Rover said:
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....
Click to expand...
Click to collapse
Don't know what else to suggest, except maybe contact Chainfire on G+.
.
Hi guys.
I was editing the vold.fstab file using root explorer. When i restarted my phone i got a message "Unfortunately Usb connectivity has stopped working." when i open settings i got message "Unfortunately, Settings has stopped working". I still have my original vold.fstab file left in my sd card but sd card is not working too. I have an Xperia M rooted and unlocked bootloader Please help.
Please tell me if there is a way to reset everything and reinstall the firmware.
Thanks.
Zexter21 said:
Hi guys.
I was editing the vold.fstab file using root explorer. When i restarted my phone i got a message "Unfortunately Usb connectivity has stopped working." when i open settings i got message "Unfortunately, Settings has stopped working". I still have my original vold.fstab file left in my sd card but sd card is not working too. I have an Xperia M rooted and unlocked bootloader Please help.
Please tell me if there is a way to reset everything and reinstall the firmware.
Thanks.
Click to expand...
Click to collapse
You could try to use adb to restore the original vold.fstab to your /system/etc/ folder if your usb debugging is still working:
Code:
adb push vold.fstab /system/etc/vold.fstab
adb shell
su
chmod 755 /system/etc/vold.fstab
exit
adb reboot
If it doesn't work try an other way:
Code:
adb push vold.fstab /data/local/tmp/vold.fstab
adb shell
su
mv /data/local/tmp/vold.fstab /system/etc/vold.fstab
chmod 755 /system/etc/vold.fstab
exit
adb reboot
If any of these ways doesn't work and you have a cwm recovery try to give these commands while you are booted to recovery.
You could also make a flashable zip and you flash it from recovery.
**If you double mounted your sdcard may be corruped and you have to use a partition manager to recreate the partition of your sdcard on PC**
Thanks for the reply.
Well the usb debugging is still working. So i tried the both adb push command, it says "cannot stat 'vold.fstab': no such file or directory" . EDIT: Tried it again, says "failed to copy vold.fstab to '/system/etc/vold.fstab': Read only file system.
I also tried that chmod command but doesn't works, says "cannot chmod system/etc/vold.fstab: Read only file system.".
And about that cwm, i can't get into cwm recovery. I tried all that vol up and down things. I tried using sd card with a card reader, it works fine. Please help.
Thanks in advance.
Zexter21 said:
Thanks for the reply.
Well the usb debugging is still working. So i tried the both adb push command, it says "cannot stat 'vold.fstab': no such file or directory" . EDIT: Tried it again, says "failed to copy vold.fstab to '/system/etc/vold.fstab': Read only file system.
I also tried that chmod command but doesn't works, says "cannot chmod system/etc/vold.fstab: Read only file system.".
And about that cwm, i can't get into cwm recovery. I tried all that vol up and down things. I tried using sd card with a card reader, it works fine. Please help.
Thanks in advance.
Click to expand...
Click to collapse
To apply these changes to system partition you have to make your system partition rewritable.Try to make it rw from Root Explorer or try some adb command:
Code:
adb remount
adb shell
su
mount -o remount,rw /system
If this doesn't work try something like:
mount -o remount,rw -t {your partition type} /dev/block/{your partition name and number} /system
* To see your partition table give the command cat proc/mtd or cat /proc/emmc *
Example:
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
Then try to push the file in the system (Give the "exit" command to quit the shell before try to push the file).
Gatosbil said:
To apply these changes to system partition you have to make your system partition rewritable.Try to make it rw from Root Explorer or try some adb command:
Code:
adb remount
adb shell
su
mount -o remount,rw /system
If this doesn't work try something like:
mount -o remount,rw -t {your partition type} /dev/block/{your partition name and number} /system
* To see your partition table give the command cat proc/mtd or cat /proc/emmc *
Example:
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
Then try to push the file in the system (Give the "exit" command to quit the shell before try to push the file).
Click to expand...
Click to collapse
Okay here's what i did.
I pushed the vold.fstab that i backed up before editing. After that i copied the vold.fstab into /system/etc in R/W Mode.
Then i restarted my phone, and finally everything worked fine.
Thanks for the help mate. You've been big help to me. I couldn't have done it without you.
hello i have a problem similar to this.i edit my vold.fstab file on my emdoor em63 tablet and when i rebooted the sdcard didnt work i was switching the internal to external, I tried to push the file with adb but it says device not found adb works fine for everything else but not for my sdcard i can remount, mount, reboot, but i cant push or pull and on the table when i got to settings/apps or settings/storage force close on me what can i do?
I have liliopop CM12 installed on my Note3, I have a encrypted partition, which I mount using luks, I have the mount working now with out issues so the encrypted part can be ignored, if any one is interested I can explain how I did what I did and post the actual scripts used.
The problem is that if I su - from juicessh and then mount the partition the partition is mounted, but only the juice su'ed user can see it. I can log this user out and back in and still see it, but only this users sees it.
For instance
$whoami
10211
#su -
0
#exit
$whoami
10211
now if I run:
$su -l --shell /system/bin/sh -c 'mkdir /storage/sdcard2 ; chmod 777 /storage/sdcard2 ; mount -t ext4 /dev/sda1 /storage/sdcard2 ; df ; exit' ; df
Now this will show that /storage/sdcard2 is mounted when I'm root
when I'm non-root (AKA not ID 0) then I do not see the mount.
Now I login as root using sshdroid:
#whoami
root
#df
does not show sdcard2
Lastly via "Root explorer":
does not see anything mount in /storage/sdcard2 either.
So the issue I'm facing is that I can mount a partition as root and access it, but only as the user I mounted it as, in fact what even makes less sense is that root via sshdroid and root via juicessh can not see what the other user did (mount wise), though if I create a root accessible file that is fine. I used to do this is CM11 using the same commands (different mount points do to the OS change) without any issue. It is as if each root user is unique which is fine on the surface, but since I need access to this encrypted partition, only when accessing documents for work, which normally it is not mounted, but once mounted I need it to be accessible as any other sdcard. Any suggestions?
Thanks,
ERIC
Partly working
I got it partly working if I disable "Mount namespace separation", however I still have an issue that /storage/emulated/0 does not exist, until I use a program like Root Explorer, I mean it exists, but the shell script can not change to it (mount point not found exception), I'm assuming this is also something to do with Lilipop, but I'm not sure what or how to resolve it.
ERIC
Hi,
I state that they are not very knowledgeable about linux commands.
I have installed on my SM-G900F ROM cm12 and it works!
I created a second user, but it does not have root privileges.
I would like, however, to know how you can create a secono user with root privileges?
Thanks for the reply
Hi I am a newbie here and I hope I posted on the correct forum.
I am having a problem with my Spreadtrum SC7731 phone. It's internal storage symlink which is /sdcard /storage/sdcard0 is being broken at boot(I think). This started when I flashed supersu through twrp to root the phone. This happens after booting and then a notification will pop up and say "SD card removed, please insert a new one". After that prompt, Apps will then lose access to the Internal Storage and when you check the /storage directory, there is a sdcard0 folder inside it but it is not linked to /storage/emulated/0 which makes this directory virtually useless. I have figured out a work around myself by deleting the directories created at boot and recreating the symlinks with a small script I created:
Code:
su
rm -R /sdcard
rm -R /storage/sdcard0
ln -s /storage/emulated/0 /sdcard
ln -s /storage/emulated/0 /storage/sdcard0
after running this script, apps will have access to the internal storage and the /sdcard in the root directory is again accessible. But sometimes, it will lose its symlinks again so I have to run the script if it happens.
Again this happens after booting, then a notification will appear that the sdcard has been removed. after that happens, I checked the symlinks and its broken.
I don't really know what is the root cause but the work around is quite a hassle for me. I am looking for like a permanent solution to fix this. I don't have an External SD Card and I am not planning on buying one since the Internal Storage is Enough for me as I do not game on this phone.
bump
Bump
help pls
I have a Motorola Edge+ 2022 phone that I rooted with magisk.
I was in the process of copying files from a USB flash drive to the phone's storage, when suddenly a file stopped copying in Magisk. It's actually an empty folder now.
I am unable to do anything with this empty folder. I can't delete the empty folder (rm -rf) in Magisk or in ADB. If I try to delete it in ADB I get a permission denied error.
I've tried setting the permissions to 777 but I am unable to change the permissions. I've also tried installing Termux, then using a root terminal in Termux to delete it but that does not work. I also tried to rename (move) the folder in Termux and I get an interesting error: "Math result not representable".
Any thoughts?
navigate to /data/media/0 and try again
aIecxs said:
navigate to /data/media/0 and try again
Click to expand...
Click to collapse
That worked!!! Why does it work, is it because that mountpoint has different permissions?
/data is mount point of underlaying block partition with (kinda) raw access to ext4/f2fs file system, while /storage/emulated is sdcardfs file system emulated on top of /data/media for MTP compatibility. yes, additionally isolated mount namespaces, SELinux or disk quota may disturb disk access as the permissions differ.