Hello,
im new here and i rooted my OP 5t and it still works. But when i want to make another app to an System app i always get this Error : "mount: can't find /system in /proc/mounts".
I tried it with Link2SD or Terminal Emulator but nothing works.
Can somebody maybe help me with this problem ?
@N3xus97
Try
Code:
adb shell "mount -o rw,remount /system"
jwoegerbauer said:
@N3xus97
Try
Code:
adb shell "mount -o rw,remount /system"
Click to expand...
Click to collapse
I already did this but it doesn't work for me.
But there is a password on the TWRP is it possible that this cause the error ?
@N3xus97
Don't know because I'm not using TWRP.
BTW: /system isn't a mount point.
Related
Trying to push files from adb to my phone but it wont let me because its a read only system.
I've done adb shell mount -o rw,remount /dev/block/mtdblock3 /system but it does not work, I'm running windows 7 could this be a problem?
Make sure that USB Debugging is enabled on the phone.
Settings...Applications...Development
C:\Users\Jake\Desktop\android-sdk-windows\tools>adb shell mount -o rw,remount /d
ev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
C:\Users\Jake\Desktop\android-sdk-windows\tools>
It is enabled.
Are you in recovery mode when you're trying this? Or booted regularly?
If you're in recovery mode you'd mount it like this:
mount -o rw /dev/block/mtdblock3 /system
Jboxen said:
C:\Users\Jake\Desktop\android-sdk-windows\tools>adb shell mount -o rw,remount /d
ev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
C:\Users\Jake\Desktop\android-sdk-windows\tools>
Click to expand...
Click to collapse
follow my tutorial for ADB set-up. http://forum.xda-developers.com/showthread.php?p=6054534#post6054534
I noticed you dont have SDK in C:/ root....
or a simple command like this should mount it as read/write:
adb remount
its what i have been doing and seems to do the same thing with less commands, unless someone can point out the difference for me.
Otherwise, try
mount -o rw,remount /dev/block/mtd3 /system
That should do it. The /dev/block/mtdblock3 is only required in recovery.
ECLIPS3 said:
or a simple command like this should mount it as read/write:
adb remount
its what i have been doing and seems to do the same thing with less commands, unless someone can point out the difference for me.
Click to expand...
Click to collapse
I would also like to know the difference between the two commands:
adb remount
and
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
DeezNotes said:
I would also like to know the difference between the two commands:
adb remount
and
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
i believe they both do the same thing. just one uses the same characters
Android22 said:
follow my tutorial for ADB set-up. http://forum.xda-developers.com/showthread.php?p=6054534#post6054534
I noticed you dont have SDK in C:/ root....
Click to expand...
Click to collapse
having the SDK in C:\ root is not a necessity. People do it because it is easy to do it that way.
So ive upgraded to 2.1 Via nordic method but ADB doesn't seem to work. It worked for one time after I upgraded and I removed some useless stuff such a moxier and stuff but now it doesn't really work. ADB pull works fine but when I try to mount the device with "adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" it says "mount: Operation not permitted" and when I try to remove more files I get something like the file is read-only or something.
Same problem overhere.
xGary said:
So ive upgraded to 2.1 Via nordic method but ADB doesn't seem to work. It worked for one time after I upgraded and I removed some useless stuff such a moxier and stuff but now it doesn't really work. ADB pull works fine but when I try to mount the device with "adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" it says "mount: Operation not permitted" and when I try to remove more files I get something like the file is read-only or something.
Click to expand...
Click to collapse
If you just type ADB SHELL, do you get $ back?
Then SU, get #
Do you Titanium, Busybox and Superuser working OK at the phone?
Hello all,
I am trying to push a file to my system, however I do not seem to be able to mount my system partition.
When I try to execute the following command, I always get the error "Operation not permitted" :
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
My phone is rooted and my USB debugging is on !!
Anyone no what could cause this. It has always worked when I was still on 1.6 (rooted) and now it doesn't allow me access.
When I use Rootexplorer, I have R/W access, so root works.
Anyone has any tips or advise ?
Try...
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Tried that, and get permission denied
Should have added, make sure your screens on on the phone and allow SuperUser access when you type su.
never mind, one sec
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 !
Hey,
for years I've been remounting /system read-write with the following call from a root shell:
Code:
mount -o remount,rw /system
With Android 7.1.2 and specifically the SuperMan ROM on my SGS7 edge, this no longer works:
Code:
mount -o remount,rw /system
mount: '/dev/block/platform/155a0000.ufs/by-name/SYSTEM'->'/system': Device or resource busy
A bit of searching on the web revealed that the following, however, does work:
Code:
mount -o rw,remount /system
Can someone figure out why the order would matter?
I find this especially curious because e.g. the Synapse app seems to use remount,rw as well, at least I see the same error when trying to use it to remount the `/system` partition.
Thanks for any insights!