Database Develop

Unable to flash xposed framework on SM-G925F

Hello. 1st of all i need to say i dont really know what i am doing but... here is what i am trying and failing at.
I own a samsung galaxy s6 edge ( SM-G925F ) runing android 6.0.1 , rooted with superSU 2.74
I am trying to install xposed framework but all i am doing is bootloops and fails.
After many bootloops with twrp , i had to do an emergency recovery using Smart Switch.
I have rooted the phone again with SuperSU 2.74 , dowloaded Flashfire , xposed Installer and xposed v8.51 sdk23-arm64-custom-build-by-wanam
This is what happens when i try to flash it.
Code:
-Mounting /system and /vendor read-write
mount: can't find /system in /proc/mounts
!Failed: /system could not be mounted !
What am i doing wrong?

sharkat said:
Hello. 1st of all i need to say i dont really know what i am doing but... here is what i am trying and failing at.
I own a samsung galaxy s6 edge ( SM-G925F ) runing android 6.0.1 , rooted with superSU 2.74
I am trying to install xposed framework but all i am doing is bootloops and fails.
After many bootloops with twrp , i had to do an emergency recovery using Smart Switch.
I have rooted the phone again with SuperSU 2.74 , dowloaded Flashfire , xposed Installer and xposed v8.51 sdk23-arm64-custom-build-by-wanam
This is what happens when i try to flash it.
Code:
-Mounting /system and /vendor read-write
mount: can't find /system in /proc/mounts
!Failed: /system could not be mounted !
What am i doing wrong?
Click to expand...
Click to collapse
Try with the 'mount /system read/write' option unticked.

What version of framework are you using just curious to see if I have already tried it or not I have been unable to find any Roms frameworks or mods to work I'm on G925R

SuperSU making /system read-only in TWRP and FlashFire?

Hi,
I'm running CyanogenMod13 on my galaxy S4 with TWRP 3.1.1.0 and I wanted to flash XPosed. The xposed page says that it's only compatible with SuperSU so I installed latest Stable SuperSU 2.82 and deactivated root access on CM13 in developer options. Then I tried flashing Xposed framework zip but it complained about /system beeing a read-only file system and I realized that TWRP didn't ask me anymore if I want read-only file system (which it always did before I installed SuperSU) anymore. Looking into "Mount" I see that "system" is not mounted by default but also making a checkbox there doesn't change anything even if "Mount system read-only" is not checked. BTW: Do I have to apply the mounts somehow or is activating the "checkbox" actually enough. Maybe my problem is just that system is not mounted r/w which is my current guess but I don't know how to mount it r/w now that SuperSU is installed.
Then I though, ok if mounts are incorrect in TWRP let's use FlashFire. So I selected to mount system r/w in option for flashing and started the flash. Again even if I selected mount system partition r/w flashfire reported read-only file system. I also tried downgrading to SuperSU 2.79 but same effect.
What the hell is going on since I flashed SuperSU. Is my root now partially broken? The Apps all are working fine, it's just modifying system partition is somehow not possible neither in TWRP nor FlashFire....
Any help or insight will be greatly appreciated.

marcelser said:
Hi,
I'm running CyanogenMod13 on my galaxy S4 with TWRP 3.1.1.0 and I wanted to flash XPosed. The xposed page says that it's only compatible with SuperSU so I installed latest Stable SuperSU 2.82 and deactivated root access on CM13 in developer options. Then I tried flashing Xposed framework zip but it complained about /system beeing a read-only file system and I realized that TWRP didn't ask me anymore if I want read-only file system (which it always did before I installed SuperSU) anymore. Looking into "Mount" I see that "system" is not mounted by default but also making a checkbox there doesn't change anything even if "Mount system read-only" is not checked. BTW: Do I have to apply the mounts somehow or is activating the "checkbox" actually enough. Maybe my problem is just that system is not mounted r/w which is my current guess but I don't know how to mount it r/w now that SuperSU is installed.
Then I though, ok if mounts are incorrect in TWRP let's use FlashFire. So I selected to mount system r/w in option for flashing and started the flash. Again even if I selected mount system partition r/w flashfire reported read-only file system. I also tried downgrading to SuperSU 2.79 but same effect.
What the hell is going on since I flashed SuperSU. Is my root now partially broken? The Apps all are working fine, it's just modifying system partition is somehow not possible neither in TWRP nor FlashFire....
Any help or insight will be greatly appreciated.
Click to expand...
Click to collapse
Try my SuperSU systemmode from here.

Thanks for the link and it also gave me hint what to google for. It seems that my SuperSU is running in systemless mode, so I would need Systemless Xposed too. Unfortunately this also requires Magisk to be installed and Magisk doesn't work with adoptable storage which I can not live without. So I will give your SuperSU version a try and run it in System Mode and try to install official xposed too. Hopefully this works.
Edit:
I had a hard-time switching from systemless mode to system mode cause you have to completely unroot and restore the patched boot image fully (just un-rooting and restoring doesn't do the trick) fortunately I had a nandroid backup from prior to rooting with untouched backups of "boot" and "system" which I could restore. Finally I was able to install the system mode SuperSU (although I didn't use your package, but created a .supersu file with SYSTEMLESS=false) and flashed it.
This now enabled me to run latest Xposed in system mode which was failing when trying to flash in systemless mode. I would have needed magisk (which is incompatible with adoptable storage) to run it systemless. I tried using the old 86.2 systemless xposed but that always resulted in a boot loop whenever I activated one of the xposed modules). Now it's working fine., Thanks for the hint ho led me find out what system mode and systemless really is.

So actually my problem is solved, just couldn't find out how to edit the thread title....

Problems with mounting the system

My Magisk does not mount the system in RW, when the system changes, the smartphone hangs. Smartphone BQ Aquaris X Android 7.1.1

Xtriel said:
My Magisk does not mount the system in RW, when the system changes, the smartphone hangs. Smartphone BQ Aquaris X Android 7.1.1
Click to expand...
Click to collapse
It's systemless. Make /system changes in recovery. You can use twrp file manager to edit things in /system or /oem

madbat99 said:
It's systemless. Make /system changes in recovery. You can use twrp file manager to edit things in /system or /oem
Click to expand...
Click to collapse
So it's not a bug?
And yes i use TWRP File manager

I have the some problem. I mount system rw in esexplore and when i change some file i have info system is ro, or systemui crash.

koko115 said:
I have the some problem. I mount system rw in esexplore and when i change some file i have info system is ro, or systemui crash.
Click to expand...
Click to collapse
Well that is kinda strange. You should be able to change things since you have root, but some devices do tend to lock up changing certain files while the system is running. Depending on the file of course.
For instance,y moto e4 locks up if I modify anything in /oem. So I have to do it in recovery.

I also have this problem on my Lenovo TAB 4.
When I remount /system to rw, android hangs/freezes and only thing that unfreeze my device is power button reboot.
Can someone help me with that?

[Q] How to get RW on /system with Magisk

Hi Community,
i recently upgraded my phone and now use magisk instead of super su.
But since the switch (root) uninstaller pro has no rw on /system to delete apps despite him having root.
how can i fix this?

Xiaomi Mi 9T Pro Global Miui 10 - Can't mount system r/w

So as the title says, I can't edit the system partition in Android which is really annoying. I've been trying to install busybox and managed it via a Magisk Module, but can't remove system apps in Titanium Backup.
I've tried ADB but it won't work, I've tried TWRP and that didn't work so I chanaged to OrangeFox TWRP and that works.
Any ideas how to allow system r/w?