i need to mount android emulator system partion as rw by adb commands
adb -s emulator-5554 shell mount -o rw,remount
adb -s emulator-5554 shell mount -o rw,remount /system
adb -s emulator-5554 shell mount -o rw,remount /data
adb -s emulator-5554 shell mount -o rw,remount /data/data
and i got always this error
Usage: mount [-r] [-w] [-o options] [-t type] device directory
could not open /proc/mounts
Click to expand...
Click to collapse
also i try to put it into writable system by cmd
or edit file path and add -writable-system next to it but still fail
i hope some one can help me here
Related
can't remount...trying to push .apk
sh-3.2# ./adb devices
List of devices attached
TA07302MDF device
sh-3.2# ./adb remount
remount failed: Operation not permitted
sh-3.2# ./adb shell
$ su
#
you can see i have root
droid x2 liberty 3 rom moto one click root
fixed it for anyone else having trouble
sh-3.2# ./adb devices
List of devices attached
TA07302MDF device
sh-3.2# ./adb remount
remount failed: Operation not permitted
sh-3.2# ./adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system/framework
# exit
$ exit
sh-3.2# ./adb push framework-res.apk system/framework/
1055 KB/s (4096287 bytes in 3.788s)
sh-3.2#
thetdy said:
fixed it for anyone else having trouble
sh-3.2# ./adb devices
List of devices attached
TA07302MDF device
sh-3.2# ./adb remount
remount failed: Operation not permitted
sh-3.2# ./adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system/framework
# exit
$ exit
sh-3.2# ./adb push framework-res.apk system/framework/
1055 KB/s (4096287 bytes in 3.788s)
sh-3.2#
Click to expand...
Click to collapse
accually you could just us this
# mount -o remount,rw /dev/block/mtdblock3 /system
should work just fine without the -t yaffs2 i know it works on the samsungs
Ok so the Rezound has the bootloader unlocked and rooted with 1click method.
Root Explorer, and Root Checker verify.
Going into adb I am trying to adb rm /system/app/".apk"
It doesnt work.
I tried adb remount and it is not letting me and says operation not permitted.
If I type in adb shell I get the $, then type in su and get #
Titanium Backup. More than worth the money. You can freeze, remove, and backup anything/everything.
Sent from my ADR6425LVW using xda premium
Code:
adb shell
su
busybox mount -o rw,remount -t / rootfs
rm /system/app/NameOfApp.apk
busybox mount -o ro,remount -t / rootfs
adb shell
$ su
su
# busybox mount -o rw,remount -t yaffs2 /rootfs
busybox mount -o rw,remount -t yaffs2 /rootfs
mount: can't find /rootfs in /proc/mounts
# rm /system/app/com.mobitv.client.nfl2010.apk
rm /system/app/com.mobitv.client.nfl2010.apk
rm failed for /system/app/com.mobitv.client.nfl2010.apk, Read-only file system
Try ROM Toolbox. You can find it free in Market.
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mmcblk029p /system
This Will Mount The System As "read/write" And Switch It To "ro" To Go Back To "read-only"
Xtreme Outcast said:
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mmcblk029p /system
This Will Mount The System As "read/write" And Switch It To "ro" To Go Back To "read-only"
Click to expand...
Click to collapse
I would suggest to drop the extra bits that someone could mis-type and shorten this to
"busybox mount -o remount,rw /system"
It's worked for me and takes a little chance out of the equation. Just my opinion take it for what it's worth.
I Was In A Rush Yesterday That I Typed In The Wrong Code And Just Realized It Now When He Said It Didn't Work. It's All Fixed Thanks For The Suggestions Always Appreciated On My Posts Or Threads.
"Operation not permitted"
What is causing this? I really want to push some files to my EVO.
Help
I have done it previously on other Roms i have flashed. I am currently on Goodies 1.5.
typhoonikan said:
"Operation not permitted"
What is causing this? I really want to push some files to my EVO.
Help
I have done it previously on other Roms i have flashed. I am currently on Goodies 1.5.
Click to expand...
Click to collapse
I believe the adb binary has to be replaced with one that has permission to do this, it is often disabled in stock builds.
an easy way around this is
adb shell
su
mount -o remount rw, /system
modplan said:
I believe the adb binary has to be replaced with one that has permission to do this, it is often disabled in stock builds.
an easy way around this is
adb shell
su
mount -o remount rw, /system
Click to expand...
Click to collapse
I typed just as you did. No help.
My results as copy and pasted:
c:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount rw, /system
mount -o remount rw, /system
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
c:\Android>adb remount
remount failed: Operation not permitted
typhoonikan said:
I typed just as you did. No help.
My results as copy and pasted:
c:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount rw, /system
mount -o remount rw, /system
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
c:\Android>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
What I posted remounts the system partition read/write. No need to adb remount after that, you can write to /system at that point.
- Root devices
Code:
adb shell
su
mount -o remount,rw /system
rm /system/csc/language.xml
reboot
Or
Code:
adb shell
su
mount -o remount,rw /system
mv /system/csc/language.xml /system/csc/language.xml.bak
reboot
Done
I'm trying to put some firmware file under /system/vendor/firmware or /system/etc/firmware, it shows the fs is read only, so I remounted /system/ as read/write with
Code:
mount -o rw,remount /system
, and used su, but when I try to create any file under these 2 location, a permission denied error still occurs. I tried to do so in both termux and adb, the same result. What's causing this? Thanks
@kdlsw
Try
Code:
adb shell "su -c 'mount -o rw,remount -t auto /system'"
jwoegerbauer said:
@kdlsw
Try
Code:
adb shell "su -c 'mount -o rw,remount -t auto /system'"
Click to expand...
Click to collapse
Tried it, still the same error.
I'm not sure if this is the remount problem, if I don't remount, the error is different (Read-only file system), after remount it's permission denied.
@kdlsw
I'm pretty sure the MOUNT worked successfully, otherwise you'ld have got an error returned: I guess you got returned "remount succeeded".
It seems to me dm_verity is enabled what blocks writing to /system: Hence disable it and reboot, then run commands as needed
Code:
adb devices
adb disable-verity 2>nul >nul
adb reboot
adb wait-for-device
adb shell "su -c 'mount -o rw,remount -t auto /system'"
<YOUR ADDITIONAL COMMANDS HERE>
jwoegerbauer said:
@kdlsw
I'm pretty sure the MOUNT worked successfully, otherwise you'ld have got an error returned: I guess you got returned "remount succeeded".
It seems to me dm_verity is enabled what blocks writing to /system: Hence disable it and reboot, then run commands as needed
Code:
adb devices
adb disable-verity 2>nul >nul
adb reboot
adb wait-for-device
adb shell "su -c 'mount -o rw,remount -t auto /system'"
<YOUR ADDITIONAL COMMANDS HERE>
Click to expand...
Click to collapse
thank you! I'll try this! I also found a workaround, mounting the directory in recovery, and the problem is gone. Thanks!