I installed Xposed on BlueStacks (rooted) and install Xposed Framework: de.robv.android.xposed.installer_v29_665be7.apk.
Trying to install/update the framework and get this following errors:
Copying Xposed-Diabler-Recovery.zip...
Mounting /system writable...
Segmentation fault
Could not mount /system writable
Trying to continue anyway...
Segmentation fault
Failed to create a backup of /system/bin/app_process
I update my SuperSU and installed BusyBox. But nope, i get "please flash the xposed-disabler-recovery.zip in SD Card"
Why am i get this following issue?
Is Xposed can't be run/installed in x64 PC??
Seems like you did many things already, except for reading the OP. There's a link to an additional app that you need to install.
Or just check the FAQ / Known issues thread.
rovo89 said:
Seems like you did many things already, except for reading the OP. There's a link to an additional app that you need to install.
Or just check the FAQ / Known issues thread.
Click to expand...
Click to collapse
what link??
dhrumilshah49 said:
what link??
Click to expand...
Click to collapse
Check the FAQ, it's there.
Hi @rovo89 , so here is the situation
I've:
-installed BS 0.8.8.8006 - OK
- ROOT (1) with BSMT - OK
- disable auto update (6) with BSMT - OK
- install superuser (S) with BSMT - OK
- xposed installer (X) with BSMT -OK
Then I click install/update in framework , I grant the super user permission to Xposed, then got an error
"SD Card :/mnt/sdcard/Android/data/de.robv.android.xposed.installer/files
Copy of Xposed-Disabler-Recovery.zip...
Mount of /system in writing...
Segmentation fault
Impossible to mount /system in writing
Continue anyway...
Backup already exists at /system/bin/app_process.orig
Copy of app_process...
Segmentation fault
impossible to copy app_process to / system/bin
(sorry for the translation the original message is in french)
It's written in red " It seems you have a known problem ( "Segmentation fault")with your ROM. Install the Framework Xposed might not work or make problems . Click here for more details."
When I click it suggests to install busybox. I've tried to install them and then reboot. But now it never starts !
So I've done all the steps again and now I got the error message again...
Please any suggestion will be appreciated.
Regards
I'd recommend using Genymotion instead of Bluestacks, as Xposed installs fine on it. I might be wrong but I don't see rovo trying to "fix" Xposed to work with a closed source emulator with heavy modifications from what I've seen.
Hey guys,
So I've had this keyboard called Fleksy installed for a while, even joined their beta program.
I've tried uninstalling it and to my surprise it turned into a system app, and is located in /system/app.
I tried removing it but it indicated 'cannot remove read only system app'.
I tried mounting my system as rw, and it is mounted so as of now, but the error continues and I cannot delete it.
I also tried removing over folders/files from /system/app and it indicates 'device or resource busy'.
I am running 8.0.0 with Magisk 20.1, TWRP and an unlocked bootloader.
I'm also using some models for battery conservation such as FDE, an app called Servicely and AFWall+.
Does anyone have any idea?
Thanks!
Boot into TWRP, mount rw /system and try to delete
Some users of my file manager app have asked me to support systemless root, especially writing to the /system folder.
I told them to just create a Magisk module as described here:
https://topjohnwu.github.io/Magisk/guides.html
However, I was told that other file managers like MiXplorer can write to /system just fine. I can indeed confirm that this works with MiXplorer.
So I did some research, like searching via Google, StackOverflow, on GitHub, and here on XDA, and looking through all threads since 1.1.2019 manually, but couldn't find any definitive answers.
My questions:
1. What's the correct way to detect systemless root versus regular root? This is not about bypassing MagiskHide - my app has been granted root access. For example, should I look for folders like /sbin/.magisk/ or /sbin/.core/ or /data/adb/modules/? Or for one of these entries in /proc/mounts:
tmpfs / tmpfs ro,seclabel,relatime 0 0
/dev/loop0 /system ext4 rw,seclabel,noatime 0 0
/dev/loop0 /sbin/.magisk/mirror/system ext4 rw,seclabel,noatime 0 0
They are probably different for various Magisk versions, that's why I ask for the correct way to do it.
2. Once I know that the device is using systemless root, what's the correct way to write to /system?
a) It works when I mount the root folder "/" for read/write, then I can write to /system just fine, and the files are preserved after a reboot.
b) I can also write to /sbin/.magisk/mirror/system, which is already mounted as read/write, but that path may change between Magisk versions?
Sorry if this has been answered before - please point me to the right page if it has been answered.
It's not about systemless root, but Androids system-as-root. That's what you need to check for.
On a device that uses SAR and doesn't use a completely read-only partition you just need to mount root ("/") rw and you're done (just like you already wrote). I don't have time to go into more details then that at the moment, but that should give you something to start with.
And don't tinker with Magisk's internal paths and files. That will likely just lead to trouble...
Thanks for your reply - you are right, it's better to remount "/" instead of trying to find the internal paths.
However, how do I determine whether a system uses system-as-root as you call it? In my current implementation for older root methods, I look in /proc/mounts where the current path is mounted. For example, when a user tries to write to /system/media, I look in the mounts file for /system/media, then if it isn't found, for /system, and finally for /. This doesn't work with Magisk, because /system is there too. Here the first 2 line from a mounts file with Magisk:
tmpfs / tmpfs ro,seclabel,relatime 0 0
/dev/loop0 /system ext4 rw,seclabel,noatime 0 0
So I see that "/system" is mounted as "rw" and don't ask the user to remount "/". I need a way to detect that Magisk's new root method is used, so I need to ignore /system and remount "/" instead.
What do you mean when you talk about "Magisk's new root method"? MagiskSU shouldn't any effect on this...
Are you talking about how magic mounting deals with SAR? That was changed in Magisk v20. But still, John's just using the standard Android way of dealing with SAR so there's no mystery to it. You'll always find "/system" in proc with Magisk, because of Magisk modules and magic mounting.
If you need to check for a specific Magisk version you can always do that with the Magisk binary, and you can take a look at how Magisk determines if a device is SAR here (if I remember correctly, I'm in no way an expert on Magisk internals).
I mean the difference between older methods (e.g. SuperSU, or Magisk v19) where you would actually write to /system, and the newer method used by Magisk v20, where /system remains untouched and the data is written to overlays (via modules or tmpfs). I need a way to detect what the system uses. In the first case, I need to remount /system as rw and write to it, and in the second case, I need to remount "/" as rw.
Why don't you ask other developers how they've got it working? That would probably be the best approach...
That's why I ask in a developer forum...
chris_g said:
That's why I ask in a developer forum...
Click to expand...
Click to collapse
I've given you a few pointers already on how you can proceed... You have a way of detecting Magisk version and a way of detecting SAR, linked in one of my previous replies. If you need more than that I'm not your guy and you'll have to hope someone else can come along and give you what you want.
But since you say that MiXplorer works, why not ask there how they do it?
I'd like to delete /system/recovery-from-boot.p file on Ulefone Armor 7E, android 9, kernel version 4.9.117 no TWRP yet, Magisk 20.4 installed, root is working. ES Exlplorer or Mixplorer can't delete it however Mixplorer shows RW. Through adb I got read-only file system error (even with insecure adb). If I want to remount as RW I get following errors, mount: '/system' not in /proc/mounts or mount: '/dev/root' not user mountable in fstab.
I also could delete bloatware from /system/priv-app only with Magisk module: [Terminal] Debloater v17.3.2. Can you please help me how can I delete /system/recovery-from-boot.p? I there maybe another Magisk module to delete files from /system?
K_a_m_i said:
I'd like to delete /system/recovery-from-boot.p file on Ulefone Armor 7E, android 9, kernel version 4.9.117 no TWRP yet, Magisk 20.4 installed, root is working. ES Exlplorer or Mixplorer can't delete it however Mixplorer shows RW. Through adb I got read-only file system error (even with insecure adb). If I want to remount as RW I get following errors, mount: '/system' not in /proc/mounts or mount: '/dev/root' not user mountable in fstab.
I also could delete bloatware from /system/priv-app only with Magisk module: [Terminal] Debloater v17.3.2. Can you please help me how can I delete /system/recovery-from-boot.p? I there maybe another Magisk module to delete files from /system?
Click to expand...
Click to collapse
What do you want to achieve by deleting that file? I guess you are on stock?
I guess you could try to remount via a terminal app, or maybe mask it through magisk.
However, this question should be asked first in your device's forum--and please, not in any random unrelated thread. That way somebody with the same problem could find any discussion about it much more easily.
I've rooted a Pixel 5 with Android 13 and Magisk 25.2, but the system partition/directory is not allowing any changes. Specifically, I'm training to systemize an app by having it moved to priv-apps, but I'm getting no space errors. Does anyone know how to allow read/write access to the system partition/directory so I can systemize an app?
Thanks
Yes I root my vivo y23L with kingo root app it install its superuser as system app I try to deleted the super user but no thing happen I use many app that can remove system app but still app not uninstall when I try remount system to rw phone say permission denied I need help thanks
same here android 12 rooted. it seem we cant modify any system files
Did you guys tried this cmd as root ?
Code:
mount -o remount,rw /system
I'm working on it guys. Old version of my script currently only supports EXT4 partitions with the infamous SHARED_BLOCKS read-only feature. (you can make it work beyond A12 if you disable the sdkCheck() function in the script but chances are it will only work on /product in modern EROFS devices)
New upcoming version of my script should have full support for EROFS and then some... If only some expert developer told me how to properly use that make_ext4fs binary...
ace2nutzer said:
Did you guys tried this cmd as root ?
Code:
mount -o remount,rw /system
Click to expand...
Click to collapse
That doesn't seem to work. When executed it states that the /dev/block it corresponds to is read-only.