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
Related
Hi, I follow the goide, but my root dont work on 100%. For example titanium backup works, root checker say that I have root. BUT when I want rename somu app I cant - (I want my camera sound off http://forum.xda-developers.com/showthread.php?t=1882926 )
Screens:
https://www.dropbox.com/sh/1sty7ryzi1mi761/htzFysqjI7
Where is problem?
Can't help you with your problem exactly, but why dont you choose Camera Sound 4?
Sound 4 = Sound off
Sound 4 = sound off, after you change the file CameraApp.apk... BUT I cant du this - look on the screens.
AW: My root dont work?
You must remount the /system partition as rw (readable AND writable). Use a file manager which can do that (e.g. ES File Explorer). Usually there's an option in their settings menu to mount /system writable. Or use terminal emulator and type
Code:
su
mount -o remount, rw /system
Remember to mount the partition as read-only again afterwards.
Tente fazer novamente
Remove root and reinstall...
muellersmattes said:
You must remount the /system partition as rw (readable AND writable). Use a file manager which can do that (e.g. ES File Explorer). Usually there's an option in their settings menu to mount /system writable. Or use terminal emulator and type
Code:
su
mount -o remount, rw /system
Remember to mount the partition as read-only again afterwards.
Click to expand...
Click to collapse
Thanks you, this help
muellersmattes said:
You must remount the /system partition as rw (readable AND writable). Use a file manager which can do that (e.g. ES File Explorer). Usually there's an option in their settings menu to mount /system writable. Or use terminal emulator and type
Code:
su
mount -o remount, rw /system
Remember to mount the partition as read-only again afterwards.
Click to expand...
Click to collapse
Worked for me! THX
This error is killing me :/
Could really use some help..
Error says:
Copying Xposed-Disabler-Recovery.zip...
Mounting /system writable...
Backup already exists at /system/bin/
app_process.orig
Copying app_process...
cp: can't create '/system/bin/app_process': File
exists
Tried looking around the forum but haven't found a solution yet
I'm on a huawei g7 using android 4.4 rooted
Still no solution. I tried finding a way to manually install the app_process but i can't find any tut on it
So i think every file on /system is write protected to i tried to unlock it with
su
mount -o rw,remount /system
cd /system
chmod -R -i *
But i didn't work :/
oke so i tried to run the installer one last time tonight and for some reason it installed the framework without problems. i have no idea why..
While I was trying to install the "GSAM Root Companion" app and having it fail, and I discovered that the problem was that /system is still mounted RO. No problem, says I, and fired up my terminal app, pop into a root prompt with su, and issue the old invocation:
Code:
#mount -o remount,rw /system
mount: Invalid argument
I did some googling, and tried various different ways of laying out the command that other people have had luck with. I didn't have any
Code:
# /system/bin/mount -o remount,rw /system
# /system/bin/mount -o remount,rw /system /system
# /system/bin/mount -o rw,remount,rw /system
# /system/bin/mount -o remount,rw /dev/block/platform/mtk-msdc.0/by-name/system
# /system/bin/mount -o remount,rw /dev/block/platform/mtk-msdc.0/by-name/system /system
..etc..
My device is properly rooted (typing 'su' in the terminal prompt gives me my '#' prompt), selinux is set to 'permissive' (per the output of 'getenforce'), but all of them just keep giving me "Invalid Argument". At this point, the only thing I can think of is that it's actually blocked in the kernel, but as I'm hardly an expert, I figured I should put it up here before I gave up for good.
Anyone have a line on this?
Solved (sort of)
When even TWRP wouldn't remount /system to RW, I figured it was just time to throw up my hands and reflash.
TL;DR
Reflash /system to stock using SPTool
Reflash TWRP using SPTool
Allow TWRP to change /system to RW
DO NOT allow TWRP to try to install SuperSu.
The Longer Process, for anyone interested in the details
Removed SD, SIM, and Battery
Used SPTool to flash BLU_V0030UU_V07_REPAIR shared by "William Smith", excluded "boot", "recovery", and "preloader"
SPTool: https://app.box.com/s/rhok6s65sfsmrkq9w6021dnqgj6l5120
Repair Rom: https://www.mediafire.com/folder/s7m0q284yuvd2/BLU#61m7ikt8k97j9
Install Battery, no SD or SIM, and boot into TWRP
Allowed TWRP to mount system as RW, wipe Dalvik, Cache, Data, and exit. Allowed root
Boot would not pass the white "BLU" screen.
Used SPTool to reflash the same image as in 3, but only "system"
Straight reboot - Passed white boot screen to colored logo.
It took awhile but eventually got to the setup wizard.
Booted into recovery. Got stock recovery (Overwritten by the stock recovery because I stopped TWRP from changing it, at a guess).
Removed Battery. Used SPTool to reinstall TWRP
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
Replaced battery. Booted into recovery. Got TWRP
Allowed modifications to /system
Rebooted to system. Did NOT allow TWRP to install SuperSU. Phone booted
Before installing SD/SIM, went through setup process.
* Skipped adding SIM
* Added google account
Powered down phone, inserted SD card with SuperSU zip, installed from TWRP
* Wiped Dalvik, then rebooted into system
SuperSu: https://docs.google.com/uc?id=0B9srKhKuVIMna0xCdXlLS2dIYUU
Verified Root.
Rebooted into TWRP and installed Xposed. Rebooted. Lingered for awhile on white screen, but passed.
XPosed Framework and Installer thread: http://forum.xda-developers.com/showthread.php?t=3034811
Installed XPosed Installer
Used ES File Explorer to confirm /system was read/writable.
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....
Hi everyone,
in pixel 2, I can get super su for adb shell, and can remount the system, /vendor partition
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
but in pixel 3 with magisk 18 or 19, I always fail to remount /vendor
blueline:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-1'->'/vendor': I/O error
I need to modify some file under/vendor/etc
I've disable Preserve AVB 2.0/dm-verity and Preserve forceencryption in advanced Settings from Magisk, unfortunately do no avail,
any idea is appreciated
misslebulletttttt said:
Hi everyone,
in pixel 2, I can get super su for adb shell, and can remount the system, /vendor partition
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
but in pixel 3 with magisk 18 or 19, I always fail to remount /vendor
blueline:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-1'->'/vendor': I/O error
I need to modify some file under/vendor/etc
I've disable Preserve AVB 2.0/dm-verity and Preserve forceencryption in advanced Settings from Magisk, unfortunately do no avail,
any idea is appreciated
Click to expand...
Click to collapse
This isn't working for me either. Tried with TWRP and regular module install. My changes to files on /vendor/etc just get overwritten. On magisk 18 and Pie.
If there's a Magisk mask active (modules magic mounting files) you might have issues if you want to do something other than systemless modifications.
The real partitions are found in /sbin/.magisk/mirror, you can try editing that. Or, editing in recovery (TWRP) should always work, since Magisk isn't active then.
loserinru said:
This isn't working for me either. Tried with TWRP and regular module install. My changes to files on /vendor/etc just get overwritten. On magisk 18 and Pie.
Click to expand...
Click to collapse
so do I, want to move some file to /vendor/etc, adb push definitely not working, so copy to /sdcard,
mount -o rw,remount -t auto /vendor
cp /sdcard/XXX /vendor,
however
mount -o rw,remount -t auto /vendor
always show mount: '/dev/block/dm-1'->'/vendor': I/O error,
tried with the movement in TWRP, but after booting into system, it's gone,
any other method to overcome ?
Didgeridoohan said:
If there's a Magisk mask active (modules magic mounting files) you might have issues if you want to do something other than systemless modifications.
The real partitions are found in /sbin/.magisk/mirror, you can try editing that. Or, editing in recovery (TWRP) should always work, since Magisk isn't active then.
Click to expand...
Click to collapse
Hi, I've copied the new file to sdcard, boot into TWRP, in TWRP do the file movement from sdcard to /vendor/etc with success, however, every time after booting into system, the modification is gone, same as the guy replied in the second thread,
any method for the movement is pretty appreciated
Magisk is not active in TWRP, so there's something else going on... Check /sbin/.magisk/mirror/vendor/etc if the modification is there, and take a look at the Magisk log (you'll need the Canary debug build for more verbose logging) if anything shows there.
Didgeridoohan said:
Magisk is not active in TWRP, so there's something else going on... Check /sbin/.magisk/mirror/vendor/etc if the modification is there, and take a look at the Magisk log (you'll need the Canary debug build for more verbose logging) if anything shows there.
Click to expand...
Click to collapse
I solved this by modifying the install script of Magisk,
if [ -z $KEEPVERITY ]; then
if $SYSTEM_ROOT; then
- KEEPVERITY=true
+ KEEPVERITY=false
ui_print "- System-as-root, keep dm/avb-verity"
else
KEEPVERITY=false
fi
fi
and install Magisk again in TWRP
this can help to disable dm-verity completely, now I can remount /vendor without I/O error
Didgeridoohan said:
If there's a Magisk mask active (modules magic mounting files) you might have issues if you want to do something other than systemless modifications.
The real partitions are found in /sbin/.magisk/mirror, you can try editing that. Or, editing in recovery (TWRP) should always work, since Magisk isn't active then.
Click to expand...
Click to collapse
Riiii I always do system edits threw twrp instead of Un mounting modules like viper and air audio plug-in and do systemless system edits threw the OS
Sent from my SM-J327P using Tapatalk