I've been rooted my moto E4 plus Nicklaus phone with magisk, I can write on all the partitions, however I can't write only on OEM partition located in /OEM.
I use Root file Explorer, then adb shell su mount -o rw,remount /oem
Nothing works
Please help !
Related
Hello there,
i try to remove all gapps from my G6. It's rooted, and i have twrp 3.2.1-r1 installed. In twrp i mount /system as rw and remove some files/folders with
adb shell rm -rf /system/sample_file, or directly in twrp terminal.....
When i do a "ls -l /system/sample_file" it isn't there, however, when i unmount and remount /system, the file exists again.
Is this a twrp-issue? Maybe somebody has an idea?
At the end i want to use stock-rom, but i want to remove all gapps. I found several script here in this forum, but they don't work because it seems that i cannot mount /system as read-write with twrp....
Everything was tried, adb terminal, adb pc, different file explorers but that folder stays read-only, even can't change permissions, MAgisk 17.1. ANy ideas?
Stiiigg said:
Everything was tried, adb terminal, adb pc, different file explorers but that folder stays read-only, even can't change permissions, MAgisk 17.1. ANy ideas?
Click to expand...
Click to collapse
be careful what you wish for...
you need to remount the partitions. you can do this through adb shell or terminal emulator on your device.
Adb commands
Code:
adb shell
su
mount -o rw,remount -t ext4 /system
mount -o rw,remount -t ext4 /vendor
Daha3ker said:
be careful what you wish for...
you need to remount the partitions. you can do this through adb shell or terminal emulator on your device.
Adb commands
Code:
adb shell
su
mount -o rw,remount -t ext4 /system
mount -o rw,remount -t ext4 /vendor
Click to expand...
Click to collapse
In response for remount /vendor, it gives
Code:
'/dev/block/dm-0' is read-only
Roman2508 said:
In response for remount /vendor, it gives
Code:
'/dev/block/dm-0' is read-only
Click to expand...
Click to collapse
You need to unlock the other parts of your bootloader then. It will factory reset the device, but you need unlock flashing and unlock flashing critical. This let's you remount critical partitions. Vendor is a critical partition.
Daha3ker said:
You need to unlock the other parts of your bootloader then. It will factory reset the device, but you need unlock flashing and unlock flashing critical. This let's you remount critical partitions. Vendor is a critical partition.
Click to expand...
Click to collapse
It was figured out to be a Magisk problem
I have Moto E4 plus Nicklaus. It's rooted by magisk and installed xposed magisk module. That worked but,,,, when trying edit build.prop, I got trouble.
I can't mount system directory to RW. That's always back to RO. I use es file explorer n root explorer to do that.
I try install kernel r3 by samarv via twrp, it work.
After boot I try edit build.prop and i did it. But around less from 1 hour, I try edit build.prop again but failed. The problem is I can't mount RW system directory again.
I not try install kernel again, it's look not the right way to solve this. But I try to non active all magisk module, but failed.
Can't someone help me???
I try mount via termux, but failed. There come massage "device or resource is busy"
I use this:
/system/bin/mount -o remount,rw /system
, And this:
mount -o remount,rw /system
Screenshot:
https://www.mediafire.com/view/smcztlosyrqciyr/Screenshot_20190817-231517.png/file
Hi, can't have full access to /system folder with adb
Installed magisk OK
Installed magisk extension module 'adb_root' OK
Code:
adb root
adbd is already running as root
but when I try to delete :
Code:
adb shell rm - f /system/app/CloudService/CloudService.apk
receive Read-only file system
any help ?
Code:
adb shell
mount -o rw,remount /
/dev/block/dm-1 is read-only
Code:
adb disable-verity
verity cannot be disabled/enabled - USER build
tried 'systemrw_1.32' and 'systemrw_1.32_modded' with no success, the installation seems to have been just fine
then flashed the only file I found into /img folder with command :
Code:
fastboot flash super super_fixed.bin
but at the end, even if all is gone fine, the command give always same answer as read-only :
Code:
mount -o rw,remount /
/dev/block/dm-1 is read-only
is there a way to make MERLIN as /system RW ???
matteo555 said:
tried 'systemrw_1.32' and 'systemrw_1.32_modded' with no success, the installation seems to have been just fine
then flashed the only file I found into /img folder with command :
Code:
fastboot flash super super_fixed.bin
but at the end, even if all is gone fine, the command give always same answer as read-only :
Code:
mount -o rw,remount /
/dev/block/dm-1 is read-only
is there a way to make MERLIN as /system RW ???
Click to expand...
Click to collapse
With PixelExperienceRecovery. Mount system then with adb remuont it rw. It is mounted in mnt/system/system.
I have a rooted Pixel 7 and It was suggested that I rename a system file to prevent the system from updating itself (despite my having turned off all such options). My first attempt was to merely try renaming the file, but that didn’t work because the file systems in mounted RO.
I did some looking around, and the common approach to dealing with this issue is to remount the file system. Following is a ‘screen grab’ of my abd session:
Code:
cheetah:/ $ su
cheetah:/ $ ls /product
app etc fonts framework lib lib64 lost+found media overlay priv-app tts usr wallpaper
(this has the directory I want, so this file system)
cheetah:/ $ mount | grep product
/dev/block/dm-15 on /product type ext4 (ro,seclabel,relatime)
(this is a mounted file system)
cheetah:/ # mount -o rw,remount /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount -t ext4 /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount /dev/block/dm-15 /product
'/dev/block/dm-15' is read-only
(three attempts to remount – all failed)
So, now what should I try?
groston said:
I have a rooted Pixel 7 and It was suggested that I rename a system file to prevent the system from updating itself (despite my having turned off all such options). My first attempt was to merely try renaming the file, but that didn’t work because the file systems in mounted RO.
I did some looking around, and the common approach to dealing with this issue is to remount the file system. Following is a ‘screen grab’ of my abd session:
Code:
cheetah:/ $ su
cheetah:/ $ ls /product
app etc fonts framework lib lib64 lost+found media overlay priv-app tts usr wallpaper
(this has the directory I want, so this file system)
cheetah:/ $ mount | grep product
/dev/block/dm-15 on /product type ext4 (ro,seclabel,relatime)
(this is a mounted file system)
cheetah:/ # mount -o rw,remount /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount -t ext4 /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount /dev/block/dm-15 /product
'/dev/block/dm-15' is read-only
(three attempts to remount – all failed)
So, now what should I try?
Click to expand...
Click to collapse
I haven't used this, but maybe it can help you.
Lughnasadh said:
I haven't used this, but maybe it can help you.
Click to expand...
Click to collapse
Thank you. Seems like this might work, but after reading several pages, I am not sure how to install/use overlayfs. I have a Windows system - any chance you could point me to something that provides some guidance?
groston said:
Thank you. Seems like this might work, but after reading several pages, I am not sure how to install/use overlayfs. I have a Windows system - any chance you could point me to something that provides some guidance?
Click to expand...
Click to collapse
I've never used this before but I believe once you flash the module it makes the /system RW so you can start making modifications. There's a README that provides some information. I don't know of any other guides besides the information on that Github page.
Checking out the thread below might reveal a solution and/or give a clue or hint...
Pixel 7 Pro Stuck in read only mode (rooted with magisk 26.1) Am I missing something? HELP
Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access. Did i miss something when i rooted with Magisk? I dont...
forum.xda-developers.com
simplepinoi177 said:
Checking out the thread below might reveal a solution and/or give a clue or hint...
Pixel 7 Pro Stuck in read only mode (rooted with magisk 26.1) Am I missing something? HELP
Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access. Did i miss something when i rooted with Magisk? I dont...
forum.xda-developers.com
Click to expand...
Click to collapse
Good suggestion. I installed FX File Explorer, gave it the appropriate permissions, but was unable to change the /product filesystem to read/write.
groston said:
Good suggestion. I installed FX File Explorer, gave it the appropriate permissions, but was unable to change the /product filesystem to read/write.
Click to expand...
Click to collapse
When you say "gave it the appropriate permissions", just to confirm -- that doesn't mean that you changed the security permissions on the folder & files, correct? I hope it means you did not do what the OP in that thread had done and actually did enable root access particularly (hoping that's what you meant on "gave it appropriate permissions").
Because, in certain cases, I've changed permissions on files/folders vs. simply enabling root access mode....
Apologies in advanced if my inquiry seems fairly obvious (to the point of insulting maybe; it is not meant to be), but you never know and many foolish things has been done/assumed on this site that missed many (obvious) things because it wasn't confirmed....