I am trying to root an elocity A7 and I pretty new at this. I installed root explorer but the mount r/w button does not work in the system folder. I tried the terminal command below but it does not seem to accept the command. I get back a message that says shows Usage: mount [-r] [-w] [-o options [-t type] device directory. I retried root explorer and still can't write. Thanks for any help.
- open Terminal emulator:
$ su
# mount -o remount,rw /system
- open Root Explorer \system folder and press r/w
adb remount
or search the market for "mount system"
I'm not following how to use adb remount. What would be the complete command line? Also, I can't get to the market which is why I am trying this. I read it on another thread here.
i cant find mount r/w button
download this program from the market "Mount /system (rw / ro)"
I can't get to the market on this device. Any other way of getting it?
Try the attached zip
Thank you! That worked.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Thanks For the App Recomendation
joenathane said:
download this program from the market "Mount /system (rw / ro)"
Click to expand...
Click to collapse
This was kicken my @$$ - thanks for the help and recommendation
zte with magisk
joenathane said:
Try the attached zip
Click to expand...
Click to collapse
my rom is stock but got a version that used zpst to force magisk to allow root, root is good but cant move 1 app to system without read only i tried this it says it worked but when i try to move it says i dont have permission .. guessing there isnt a recovery for this model the z835
Related
Hi,
I am trying to alter the boot xml file to get my boot sound back. I am on Modaco 2.5.1 now.
Pulled the boot sound xml file, edited. But when I try push back to phone I get the 'android adb push read-only file system' message.
How do I get round this?
Thanks
Phil
Phil_UK said:
Hi,
I am trying to alter the boot xml file to get my boot sound back. I am on Modaco 2.5.1 now.
Pulled the boot sound xml file, edited. But when I try push back to phone I get the 'android adb push read-only file system' message.
How do I get round this?
Thanks
Phil
Click to expand...
Click to collapse
Do a adb remount before doing the push should solve it.
Thanks
That solved it!
Phil
i'm having the same error when i want to delete stock apps. i'm rooted already, but not sure how to get myself to read write rights. any idea?
Get around read-only
I am having the same problem. Have you had any luck??
woowoowooty said:
I am having the same problem. Have you had any luck??
Click to expand...
Click to collapse
adb remount
"remount failed: Operation not permitted"
you cant do it while in recovery,you have to be booted up.
EXAMPLE to remove Sim Toolkit
adb remount
remount successful
adb shell rm /system/app/Stk.apk
Done...
If you still have problems type adb shell, type su,press allow on your phone screen then try again.
If it shows a $ sign when u type adb shell then u got no root son
................ delete post. ....
sorry but i am quite new to android and rootin... can u please tell me what is recovery and what is boot up.. cause i am facing teh same issue and when i try adb remount from my command prompt, i get permission denied error . Can this also be done from terminal emulator in android.. my device is rooted and i have superuser permission..
thanks in advance,
Rejo
rejo_nazi said:
sorry but i am quite new to android and rootin... can u please tell me what is recovery and what is boot up.. cause i am facing teh same issue and when i try adb remount from my command prompt, i get permission denied error . Can this also be done from terminal emulator in android.. my device is rooted and i have superuser permission..
thanks in advance,
Rejo
Click to expand...
Click to collapse
You can try it in terminal emulator after su.
Code:
$ su
# mount -o rw,remount /system
<do what you want>
# mount -o ro,remount /system
thanks for the information!
Hi.
Samsung Galaxy Ace - FroYo 2.2.1 - Rooted with superuser.
Pulled framework.jar from /system/framework/framework.jar
edited it and now pushing back.
I get
failed to copy 'framework.jar' to '/system/framework/framework.jar': Read-only file system.
I know it's a read-only file system, but I need to push that (and other files) back there.
How to allow that process?
My other option is to "FLASH" a .zip file which contains these files, and I think that puts them in their desired location, but:
What is Flashing and how is it done on my device? I've been googling for a couple hours now with no luck. Adobe Flash is taking all the search results, and some found forum entries aren't helping.
Many thanks, I hope for a quick reply.
Hi, same problem trying to push some libs and framework.jar back to where they originally pulled from. I need to do that for Arabization on Samsung Galaxy Ace running Froyo 2.2.1 with Root.
Error returs "failed: read-only file system"
I've beek googling and searching forums for a couple days now with no luck. Tried many things, commands and chmod which all failed.
The other option, which is to use update.zip on stock recovery to send the files home has failed. Got the following:
Finding update package...
Opening update package...
Installing upate...
E:Error in /sdcard/update.zip (Status 0)
Installation aborted.
I couldn't install ClockworkMod to try it there because Rom Manager does not list my phone (Samsung Galaxy Ace) in the options it gives me when I ask it to Flash ClockworkMod Recovery into my phone. I don't know which phone to choose form the list:
- Huawei Pulse Mini
- Dell Streak
- Huawei Pulse
- Commtiva Z71 (Boston, blaze, and more)
- Geeksphone ONE
- Spice MI700, Commtiva Link N700 and more)
- Huawei Ascend
Halp.
Oh just noticed I have both last posts. How progress works.
By the way,
#mount -o rw,remount /system
does not help. Trying to copy files using 'cp' commant in shell now simply brings 'file exists'. Is there an 'overwrite' attribute to add that'll fix it?
adb remount worked for me thanks..
pigfoot said:
You can try it in terminal emulator after su.
Code:
$ su
# mount -o rw,remount /system
<do what you want>
# mount -o ro,remount /system
Click to expand...
Click to collapse
champagne post. tnx!!!
pigfoot said:
You can try it in terminal emulator after su.
Code:
$ su
# mount -o rw,remount /system
<do what you want>
# mount -o ro,remount /system
Click to expand...
Click to collapse
Worked for me, thank you!
So I'm totally unable to do anything to my /system in CWM via ADB.
Code:
> adb remount
remount failed: Operation not permitted
> adb push item.apk /system/app/item.apk
Failed: Permission denied
adb shell
$: su
Segmentation fault
$: rootsh
~# mount /system
mount: mounting /dev/block/mmcblk0p9 on /system failed: Device or resource busy
~# su
# mount /system
mount: mounting /dev/block/mmcblk0p9 on /system failed: Device or resource busy
# mount /system/app
can't find /system/app in /etc/fstab/
Pressing "unmount /system" in CWM results in "Error unmounting /system!" message. I tried pressing "Fix Permissions" but it didn't help. The only thing it did was that "su" results in "Segmentation fault" instead of "Permission denied". I just flashed my Lite'nin ROM again but it didn't fix anything.
I do have root access in normal OS so I can probably do some stuff in terminal emulator. But why is /system busy all the time?
try this:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9
kaukassus said:
try this:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9
Click to expand...
Click to collapse
Thanks. That apparently mounted the /system but adb was still unable to push the files there. Maybe that is because "su" is still not working, only "rootsh". So I moved the file to my sdcard and then moved it to /system in shell.
Jiia said:
Thanks. That apparently mounted the /system but adb was still unable to push the files there. Maybe that is because "su" is still not working, only "rootsh". So I moved the file to my sdcard and then moved it to /system in shell.
Click to expand...
Click to collapse
since you are using a Secured Kernel(probably the CF-Root with CWM), you have to push the files to /sdcard
and then copy the files from the sdcard to the /system directory.
you can only push files with adb directly to the /system directory, when you are using an insecured kernel.
kaukassus said:
since you are using a Secured Kernel(probably the CF-Root with CWM), you have to push the files to /sdcard
and then copy the files from the sdcard to the /system directory.
you can only push files with adb directly to the /system directory, when you are using an insecured kernel.
Click to expand...
Click to collapse
Oh. Thanks for the info, that cleared things up! I thought you only need to have a custom recovery in order to push with adb but apparently it's about the kernel.
kaukassus said:
try this:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9
Click to expand...
Click to collapse
this not working for me ,still can't mount the system i can't rm9 at ADB at all please help 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!
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?
Hi, I have a huawei y6
I rooted with kingroot, root checker says I have my phone rooted and i even managed to uninstall some apps like google movies and google music who were just wasting space but now I can't do anything because it only shows as read only and can't change to read/ write.
I have tried with
Root Browser, it was the one I was using at first
Root explorer
es file explorer
total command
super manager
also tried with
Code:
adb shell
su
mount -o rw,remount rootfs /
chmod 777 /system
and
Code:
su
mount -o remount,rw /system
only returns:
Code:
mount: Read-only file system
I don't know what else to do
docHolmes said:
Hi, I have a huawei y6
I rooted with kingroot, root checker says I have my phone rooted and i even managed to uninstall some apps like google movies and google music who were just wasting space but now I can't do anything because it only shows as read only and can't change to read/ write.
I have tried with
Root Browser, it was the one I was using at first
Root explorer
es file explorer
total command
super manager
also tried with
Code:
adb shell
su
mount -o rw,remount rootfs /
chmod 777 /system
and
Code:
su
mount -o remount,rw /system
only returns:
Code:
mount: Read-only file system
I don't know what else to do
Click to expand...
Click to collapse
make sure that u still have root access on ur device