adb remount fails - mount: 'system' not in /proc/mounts

Question

I tried all the commands and suggestions available in stackoverflow and online but none worked

and many more but nothing works for me

I am getting below error - None of below commands are working.

$adb root
$adb disable-verity

For

$adb remount
remount of / failed: Permission denied
remount failed

So then I tried with different commands like

$ adb shell mount -o rw,remount /system
mount: '/system' not in /proc/mounts

$ adb shell mount -o rw,remount /
'/dev/root' is read-only


$ adb shell  mount -o rw,remount -t /dev/block/stl12 system
mount: 'system' not in /proc/mounts

$ adb shell "su 0 mount -o rw,remount /system"
mount: '/system' not in /proc/mounts

$ adb shell
$ su
# mount -o rw,remount /system

 mount: '/system' not in /proc/mounts

this might help you, as working for me with the same issue `https://github.com/d4rken/sdmaid-public/issues/2110#issuecomment-440325101` — Mohammed Sufian, Sep 16 '19 at 13:26

score 41 · Answer 1 · answered Jun 30 '20 at 08:13

41

I had the same issue.The solution is to mount the root (/). After this you can write to /system.

mount -o rw,remount /

Don't forget to reset the state to 'ro'.

mount -o ro,remount /

answered Jun 30 '20 at 08:13

Nowrose Muhammad Ragib

505
4
10

26

Sadly I'm getting `'/dev/block/dm-4' is read-only` when I run this command – Christian Saiki Oct 13 '20 at 22:02
1

It does not work for new Samsung T870 models mounting `/system` as read-only. – user1429980 Dec 31 '20 at 07:47
4

Tears. ```mount: '/dev/block/dm-0' not user mountable in fstab``` – 임정섭 Mar 05 '21 at 03:08
No result achieved with this – Vlad Apr 10 '21 at 12:50
1

worked for me :) – codingsenpi Feb 09 '22 at 06:16
Warning! Take a system backup before executing `ro`, on a real device. I had my device stuck at boot logo, glad restored it from recovery. – abitcode Mar 04 '23 at 08:52
on Google android emulator getting error: `'/dev/root' is read-only` Tried on Android 9.0 arm64 – PATAPOsha Mar 07 '23 at 08:53
this worked for Xiaomi redmi device – Baki Billah Aug 27 '23 at 04:54

score 26 · Answer 2 · edited Jul 02 '20 at 10:26

26

> adb root
> adb shell avbctl disable-verification
Successfully disabled verification. Reboot the device for changes to take effect.
> adb disable-verity
using overlayfs
Successfully disabled verity
Now reboot your device for settings to take effect
> adb reboot
> adb root && adb remount
remount succeeded
> adb push ScreenCap.apk /system/app/
ScreenCap.apk: 1 file pushed. 33.1 MB/s (1640812 bytes in 0.047s)
> adb reboot

edited Jul 02 '20 at 10:26

Gigazelle

1,424
1
24
34

answered Jul 02 '20 at 00:07

Libin Jose

277
3
2

8

On the second command, I get "/system/bin/sh: avbctl: not found" – David Gomes Oct 07 '20 at 22:39
3

`/system/bin/sh: avbctl: inaccessible or not found` – Vlad Apr 10 '21 at 12:46
1

The command `adb shell avbctl disable-verification` working for me during 2020, but now I get the same error of here above: "/system/bin/sh: avbctl: inaccessible or not found". I don't know why. – Sebastian Diaz Apr 14 '21 at 05:00
Probably the solution is pick up an emulator image that don't belong to Play Store (without that icon on AVD Manager into Android Studio). And with a "Q" Android version. Check here: https://stackoverflow.com/a/45668555/7191548 – Sebastian Diaz Apr 14 '21 at 05:11
Finally I found this worked answer. thank you a lot! – Huy Nguyen May 26 '21 at 02:37
Getting "avb_ops_user.cpp:217: ERROR: Error writing data" for the 2nd command – remondo Dec 13 '22 at 04:35

score 19 · Answer 3 · answered Oct 16 '20 at 23:39

19

(Android Q Emulator solution)

> emulator -avd Pixel_3a_XL_API_30 -writable-system
> adb shell avbctl disable-verification
> adb disable-verity
> adb root
> adb remount
> adb shell "su 0 mount -o rw,remount /system"

answered Oct 16 '20 at 23:39

niek tuytel

899
7
18

this works, thanks! tested with android 10 emulator – Sérgio Nov 14 '20 at 18:15
`verity cannot be disabled/enabled - USER build`. Any thoughts? – Egret Jan 04 '21 at 13:15
@Egret, on what type of device you are trying it? (`adb disable-verity` is the issue right? try to skip it may work) – niek tuytel Jan 04 '21 at 14:20

score 8 · Answer 4 · answered May 01 '20 at 03:21

8

If you are getting /system not in /proc/mounts error, your device system partition is not mounted with any directory. Writing to the system partition is restricted.

If you are using emulator please download previous version system image.

As of now, Android Q is not supported for writing the system partition so use android pie instead.

answered May 01 '20 at 03:21

Magudesh

419
5
13

4

This answer basically repeats the first one. The main problem with both is that lowering the API level is not a future-proof solution. Also, please include some source stating doing this is "not supported" on Android Q. – user3738870 May 01 '20 at 22:43
@Magudesh, where has it been stated that Android Q does not support writing to the system partition on a rooted device? – avelyne Aug 28 '20 at 09:55
@avelyne Rooting the android Q was supported in devices but not in emulator. If Android R released, rooting for android Q will be enabled. – Magudesh Sep 30 '20 at 13:19

The Blind Hawk · Answer 5 · 2022-08-05T07:48:15.067

You might want to check out the first answer of this thread.

To make it so that the error adbd cannot run as root in production builds does not pop up you have to choose an emulator system image that is not labelled "Google Play".

After that you have to run:

./adb root

Cold Boot your device once, then run:

% ./adb shell
$ su
# mount -o rw,remount /system

and you should be good to run any of the commands you had on your question.

For me I had to choose a Hardware without the "Play Store" logo under the Play Store column like in this photo:
(keep in mind that the UI of Android Studio might change)

score -1 · Answer 6 · answered Apr 06 '20 at 16:26

I met this issue when working on rockchip tablet device running on Android OS 8.1. And I found a way to remount the /system to rw as the steps below:

adb shell
su
mount | grep system
After step 3 you will see the cmd print out this :

/dev/block/mmcblk1p11 on /system type ext4 (ro,dirsync,seclabel,relatime,data=ordered,inod e_readahead_blks=8)

(the type and path maybe different depend on your device)
Now use the command:

busybox mount -o remount,rw –t <-type> <-path> /system

In my case, <-type> is ext4 and <-path> is /dev/block/mmcblk1p11

Hope this can help someone!

score -3 · Answer 7 · answered Apr 16 '19 at 07:51

I encountered this issue with Android API 28.

The walk-around was to use a lower version Android API level 24. After that everything works.

$ adb shell
generic_x86:/ # mount -o rw,remount /system
generic_x86:/ # exit
[~]
$ adb push /etc/hosts /system/etc/hosts
/etc/hosts: 1 file pushed. 2.2 MB/s (7458 bytes in 0.003s)

adb remount fails - mount: 'system' not in /proc/mounts

7 Answers7

Linked