[Q] Anyone know how to access System_Root from ADB when in Recovery? - Google Pixel XL Questions & Answers

Anyone know how to access System_Root from ADB when in Recovery?
Code:
# mount -o rw,remount /system_root
mount: can't find /system_root in /proc/mounts
Boogered up my SystemUIGoogle and wanted to replace it via ADB since I can't get back into the OS and TWRP's file manager can't access system_root either.

that should be in regular system/privapp

flex360 said:
that should be in regular system/privapp
Click to expand...
Click to collapse
Ahh, thank you but the one we modify is actually in /system_root/system/priv-app for the Pixel and 7.1.x.

Related

Need Help with ADB

i'm new to adb. i finally got it working. the correct string is added to Path, it's in my root directory C:\. i'm able to list my device, list directories, and even push/pull (did test to sdcard). i cannot, however, mount the /system directory to r/w.
this is what's happening
C:\android\android-sdk_r06-windows\android-sdk-windows\tools> adb remount
remount failed: Invalid argument
i'm in recovery trying to do this. anyone know what's going on or can maybe lend some help? thank you
mrvirginia said:
i'm new to adb. i finally got it working. the correct string is added to Path, it's in my root directory C:\. i'm able to list my device, list directories, and even push/pull (did test to sdcard). i cannot, however, mount the /system directory to r/w.
this is what's happening
C:\android\android-sdk_r06-windows\android-sdk-windows\tools> adb remount
remount failed: Invalid argument
i'm in recovery trying to do this. anyone know what's going on or can maybe lend some help? thank you
Click to expand...
Click to collapse
if you do not have a rooted, NAND unlocked, phone, you will not be able to mount /system
timothydonohue said:
if you do not have a rooted, NAND unlocked, phone, you will not be able to mount /system
Click to expand...
Click to collapse
it is rooted and NAND unlocked lol
i was actually able to push but not where i wanted.
i did
adb push com.htc.resources.apk /system/framework
but that's not where it needs to go
so i then did
adb push com.htc.resources.apk /system/framework/
and it says /system/framework is a directory, which i know lol that's where i need the file to go.
oh yeah, and i got it mounted as r/w. so now i'm just having trouble getting the file where it needs to be with the whole "is a directory" error instead of it actually pushing the file. still unable to pull a file from that location, though.
try writing the filename. it 'should' append it automatically, but if not then try
adb push com.htc.resources.apk /system/framework/com.htc.resources.apk
timothydonohue said:
try writing the filename. it 'should' append it automatically, but if not then try
adb push com.htc.resources.apk /system/framework/com.htc.resources.apk
Click to expand...
Click to collapse
this will prob work but...
now i'm getting "error: more than one device and emulator"
edit: i'm going to reboot and start all over. not sure how to kill it off since this is a little new to me ha
timothydonohue said:
try writing the filename. it 'should' append it automatically, but if not then try
adb push com.htc.resources.apk /system/framework/com.htc.resources.apk
Click to expand...
Click to collapse
this was a successful push, but the file is still not updating so i'm lost now
also, trying to pull this file back out is not working using
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb pull /system/fr
amework/com.htc.resources.apk com.htc.resources.apk
remote object '/system/framework/com.htc.resources.apk' does not exist
edit: this is what i'm looking at
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb shell mount -o
rw, remount /dev/block/mtdblock3 /system
adb server is out of date. killing...
* daemon started successfully *
BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
Usage: mount [flags] DEVICE NODE [-o OPT,OPT]
Mount a filesystem. Filesystem autodetection requires /proc be mounted.
Options:
-a Mount all filesystems in fstab
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE Filesystem type
-O OPT Mount only filesystems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a]sync Writes are [a]synchronous
[no]atime Disable/enable updates to inode access times
[no]diratime Disable/enable atime updates to directories
[no]relatime Disable/enable atime updates relative to modification ti
me
[no]dev (Dis)allow use of special device files
[no]exec (Dis)allow use of executable files
[no]suid (Dis)allow set-user-id-root programs
[r]shared Convert [recursively] to a shared subtree
[r]slave Convert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
bind Bind a directory to an additional location
move Relocate an existing mount point
remount Remount a mounted filesystem, changing its flags
ro/rw Read-only/read-write mount
There are EVEN MORE flags that are specific to each filesystem
You'll have to see the written documentation for those filesystems
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb pull /system/fr
amework/com.htc.resources.apk com.htc.resources.apk
remote object '/system/framework/com.htc.resources.apk' does not exist
/system is under mtdblock4 on our device.
if you need to mount /system as read/writeable from adb, you should just be able to use
adb remount
if you are doing it in shell, use mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
timothydonohue said:
/system is under mtdblock4 on our device.
if you need to mount /system as read/writeable from adb, you should just be able to use
adb remount
if you are doing it in shell, use mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
yeah adb remount won't work for me either.
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
remount failed: Invalid argument
i'm going to try mtdblock4
also, if you are having issues with the adb daemon, use
adb kill-server
adb start-server
that'll reboot the adb daemon
timothydonohue said:
also, if you are having issues with the adb daemon, use
adb kill-server
adb start-server
that'll reboot the adb daemon
Click to expand...
Click to collapse
thanks. yeah i started just killing it in task manager
after using "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" and trying to pull, i'm still getting /system/framework/com.htc.resources.apk does not exist
yeah, not sure what to tell you then. i can't piddle around in my own, because i'm on cm6, and won't have that.
are you sure it exists?
adb shell
# cd /system/framework
# ls
that will tell you what's in there. if you can't see it, it's not there.
from a brand new shell, (or bounce back up to the root directory)
try
find -name "*resources*.*"
that should tell you every file that contains 'resources' as a part of the file name, and where it is located.
timothydonohue said:
yeah, not sure what to tell you then. i can't piddle around in my own, because i'm on cm6, and won't have that.
are you sure it exists?
adb shell
# cd /system/framework
# ls
that will tell you what's in there. if you can't see it, it's not there.
from a brand new shell, (or bounce back up to the root directory)
try
find -name "*resources*.*"
that should tell you every file that contains 'resources' as a part of the file name, and where it is located.
Click to expand...
Click to collapse
it exists. i navigated to it using root explorer. but according to this, it doesn't exist
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # cd /system/framework
cd /system/framework
/sbin/sh: cd: can't cd to /system/framework
/ #
you can't navigate to the folder if /system isn't mounted. if you just restarted the adb server, then it won't be mounted.
timothydonohue said:
you can't navigate to the folder if /system isn't mounted. if you just restarted the adb server, then it won't be mounted.
Click to expand...
Click to collapse
that was prob the case, can't remember if i re-mounted or not when i was doing that. regardless, i was positively mounted when trying to push/pull and it wasn't working so i guess i'll just have to wait for someone to put it in a flashable zip.
i hate adb
thanks for your help dude

ADB Help

Hello there,
does anyone know how to mount the galaxy s4 as writeable via adb?
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9 /system
is the Red Coloured the right Path?
Antalor said:
Hello there,
does anyone know how to mount the galaxy s4 as writeable via adb?
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9 /system
is the Red Coloured the right Path?
Click to expand...
Click to collapse
omg no no no no.
if you are talking about trying to use "adb push <name of file> <destination file>"
Then you must use "adb remount" if it fails, you are not on an insecure kernel. Thus your only option is to push to the sdcard then use "adb shell" and navigate to your sd card and use "cp <name of file on sdcard> <destination file location>"
as for the commands, it is NOT what you have posted. it is simply
mount -o rw,remount /system
nothing else is needed. You will seriously mess something up if you try mounting it as yaffs2 considering we use ext4 now. FYI, the above command can only be entered AFTER first entering "adb shell" which gives you a command line on the device to execute commands.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
No, i want uninstall apk's/apps via adb and theerfore i have to mount it as writeable, and, also i want to:
pm list packages -f > file.txt and got error read only system...
What exactly is yaffs2?
Sent from my GT-I9505 using xda app-developers app
Antalor said:
No, i want uninstall apk's/apps via adb and theerfore i have to mount it as writeable, and, also i want to:
pm list packages -f > file.txt and got error read only system...
What exactly is yaffs2?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Then you need to use
adb shell mount -o rw,remount /system
thats it. To uninstall apks, use:
adb uninstall <package name>
And you are getting a read only system error because you are trying to create that "file.txt" file onto your "root" directory.
do this:
adb shell cd /data/media/0
then try to do your list packages.

[Q] Unable to mount /sdcard as rw

I'm currently trying to use adb to push a ROM to my sdcard on my Verizon Galaxy Nexus. However, it keeps failing due to /sdcard being a read-only filesystem.
When I adb shell into the phone and type mount, i get this (among others):
Code:
/dev/block/mmcblk0p12 on /sdcard type ext4 <ro,relatime,barrier=1,data=ordered>
Attempting to mount /sdcard as read-write is not proving fruitful:
Code:
mount -o remount rw /sdcard
Can anyone help? I'm just trying to get a rom on there so i can install it. Unfortunately, the phone never leaves the google screen when i try to boot, so recovery and fastboot are my only options.
mount -o rw,remount /dev/block/mmcblk0p12 /sdcard
try that
DonDizzurp said:
mount -o rw,remount /dev/block/mmcblk0p12 /sdcard
try that
Click to expand...
Click to collapse
Thanks for the help. It now mounts as rw. However, when i try to
Code:
adb push C:\rom.zip /sdcard/rom.zip
It fails and i get a Fil I/O error.
ttremblay said:
Thanks for the help. It now mounts as rw. However, when i try to
Code:
adb push C:\rom.zip /sdcard/rom.zip
It fails and i get a Fil I/O error.
Click to expand...
Click to collapse
To make things easier, copy the .zip file to the folder where you have ADB then try
adb push ./rom.zip /sdcard/rom.zip
I never could get things to push to sdcard while in recovery mode no matter what I tried.
adb sideload was how I always did I
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Or maybe instead of using "/sdcard" use "/data/media"?
Hello there, my samsung galaxy s2 i9100's internal sdcard suddenly became read-only shortly after updating it to 4.1. I've tried using the command: ''mount -o remount, rw /sdcard'' which works until i reboot or connect it to an external usb storage device. I'm kindly asking if anyone knows a permanent solution to my problem. P.S- I'm a bit new to this android thing so make your explanations as easy as possible. Please help

[Guide] How to disable Virtual CDrom on OOS

Just wanted to know if anyone knows how to disable the virtual cdrom in OOS when you plug in usb to pc. I have looked and there is no cdrom.iso like other phones i had.
Edit: Just overlooked the file.
If anyone is interested in disabling the virtual cdrom upon usb connection, navigate to /system/etc with a root filemanager and rename usb_drivers.iso to usb_drivers.iso.bak and reboot. or enter the following commands in adb shell and reboot. Phone MUST be rooted.
Code:
adb shell
su
mount -o remount,rw /system
mv /system/etc/usb_drivers.iso /system/etc/usb_drivers.iso.bak
mount -o remount,ro /system
Revert
Code:
adb shell
su
mount -o remount,rw /system
mv /system/etc/usb_drivers.iso.bak /system/etc/usb_drivers.iso
mount -o remount,ro /system
Edit: fixed a typo
for everyone getting this Error:
mount: '/dev/block/bootdevice/by-name/system_b'->'/system': Device or resource busy
Click to expand...
Click to collapse
You have to use this Command
mount -o rw,remount /system
Click to expand...
Click to collapse
instead of
mount -o remount,rw /system
Click to expand...
Click to collapse
Thanks!
That worked for my OnePlus 6.
Thanks!
That worked for my OnePlus 7 pro.

System remount?

Has anyone been able to remount /system as rw? FX File Explorer says it's successful but then switches automatically back to read only
I'm also trying to remount /system as rw. It seems that the patched Magisk boot file provided in this post preserves dm-verity, which disallows system partition modifications and makes it unable to remount as rw. The mount command will complain that '/dev/block/dm-8' is read-only.
Having tried repatch the boot image with unchecked 'preserve AVB 2.0/dm-verity' in the Magisk app, but resulted in a crash during boot (QUALCOMM CrashDump Mode). Can succesfully boot with that option checked. It would be fine if dm-verity can be disabled in other ways.
ichimei said:
I'm also trying to remount /system as rw. It seems that the patched Magisk boot file provided in this post preserves dm-verity, which disallows system partition modifications and makes it unable to remount as rw. The mount command will complain that '/dev/block/dm-8' is read-only.
Having tried repatch the boot image with unchecked 'preserve AVB 2.0/dm-verity' in the Magisk app, but resulted in a crash during boot (QUALCOMM CrashDump Mode). Can succesfully boot with that option checked. It would be fine if dm-verity can be disabled in other ways.
Click to expand...
Click to collapse
Have you tried fastboot?
fastboot oem disable_dm_verity
If it causes problems, replace disable with enable to get back to current state, but it shouldn't
I don't like to disable dm verity for performance concerns, but for now it would be okay until a new root method comes out
Josh McGrath said:
Have you tried fastboot?
fastboot oem disable_dm_verity
If it causes problems, replace disable with enable to get back to current state, but it shouldn't
I don't like to disable dm verity for performance concerns, but for now it would be okay until a new root method comes out
Click to expand...
Click to collapse
FAILED (remote: 'unknown command')
Finished. Total time: 0.004s
Click to expand...
Click to collapse
It was worth a shot
blackknightavalon said:
It was worth a shot
Click to expand...
Click to collapse
Are you able to flash with TWRP by any chance?
Josh McGrath said:
Are you able to flash with TWRP by any chance?
Click to expand...
Click to collapse
TWRP doesn't mount /system at the moment on anyone's devices
Correct me if I'm wrong,but devices released with Android 10 out if the box will not allow making changes to the system( i.e it will remain read-only only)
WillSmith89 said:
Correct me if I'm wrong,but devices released with Android 10 out if the box will not allow making changes to the system( i.e it will remain read-only only)
Click to expand...
Click to collapse
That's what I'm working on. I tried a workaround but got this
mount -o rw,remount /
'/dev/block/dm-8' is read-only
Click to expand...
Click to collapse
I'm trying other things as I think of them, and I have a few ideas
blackknightavalon said:
That's what I'm working on. I tried a workaround but got this
I'm trying other things as I think of them, and I have a few ideas
Click to expand...
Click to collapse
Do you know if stock Oneplus recovery will flash unsigned zips?
Not sure. Got one I can flash via Fastboot?
blackknightavalon said:
Not sure. Got one I can flash via Fastboot?
Click to expand...
Click to collapse
Maybe, let me go through my old files cause I think I have dmverity disabler for stock recovery zip
Okay, I'm getting closer. Typing in
mount -o rw,remount /system
Click to expand...
Click to collapse
as usual gives me the "not in /proc/mounts" thing, but typing in
mount -o rw,remount /product
Click to expand...
Click to collapse
gives me the "/product is read only" error.
What we need is a kernel that'll let us mount /product in order for us to REALLY start playing with this device
------------------------------------------------------------------------------------
Okay, here's the Terminal results of my latest attempts. Maybe someone can have better luck than me
OnePlus7T:/ $ su
OnePlus7T:/ # mount -o rw,remount /sbin/.magisk/block/system_root
'/sbin/.magisk/block/system_root' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-11
'/dev/block/dm-11' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-9
'/dev/block/dm-9' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-8
'/dev/block/dm-8' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-8 /system
mount: '/system' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /dev/block/dm-8 /system/product
mount: '/system/product' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /product
'/dev/block/dm-9' is read-only
OnePlus7T:/ # mount -o rw,remount /super
mount: '/super' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /product
'/dev/block/dm-9' is read-only
OnePlus7T:/ # ls -l /dev/block/by-name/super
lrwxrwxrwx 1 root root 16 1970-01-12 02:43 /dev/block/by-name/super -> /dev/block/sda15
OnePlus7T:/ # mount -o rw,remount /dev/block/sda15
mount: '/dev/block/sda15' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /dev/block/by-name/super
mount: '/dev/block/by-name/super' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /init
mount: '/init' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /system/etc/init
'/sbin/.magisk/block/system_root' is read-only
OnePlus7T:/ #
Click to expand...
Click to collapse
Okay, I have an idea but I'll have to wait for the next official build to test it
Any news on this? Really want to uninstall Google Pay and install an older version of it.
blackknightavalon said:
Okay, I have an idea but I'll have to wait for the next official build to test it
Click to expand...
Click to collapse
I'm not much help but wanted to throw some ideas out thee. have you also tried changing read/write via fastboot or terminal emulator with (I think) chmod 777?
Josh McGrath said:
I'm not much help but wanted to throw some ideas out thee. have you also tried changing read/write via fastboot or terminal emulator with (I think) chmod 777?
Click to expand...
Click to collapse
Tried it through Terminal commands via Terminal Emulator AND ADB. Haven't tried it through fastboot. I'm downloading the OTA now (been in Florida on vacation, leaving back for NYC this afternoon)
I tried to change font, but I cant remount system. any idea? ( the mogule font_changer has remove of programmer, my device is root without twrp.
You cant mount system as r/w because android 10 is read only

Categories

Resources