FORUMS
Remove All Ads from XDA

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

102 posts
Thanks Meter: 6
 
By marcelser, Senior Member on 9th October 2017, 03:53 PM
Post Reply Email Thread
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.
 
 
9th October 2017, 11:40 PM |#2  
mauam's Avatar
Senior Member
Thanks Meter: 9,811
 
More
Quote:
Originally Posted by marcelser

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.



Try my SuperSU systemmode from here.
10th October 2017, 09:09 AM |#3  
OP Senior Member
Thanks Meter: 6
 
More
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.
The Following User Says Thank You to marcelser For This Useful Post: [ View ] Gift marcelser Ad-Free
11th October 2017, 12:38 PM |#4  
OP Senior Member
Thanks Meter: 6
 
More
So actually my problem is solved, just couldn't find out how to edit the thread title....
Post Reply Subscribe to Thread

Tags
support

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes