Database Develop

How to edit hosts file?

How are you able to edit the hosts file in systemless route? I used SuperSU 2.66 flashed on MMB29S build. All I want to do is set up some redirects and possibly adaway.

swaderade said:
How are you able to edit the hosts file in systemless route? I used SuperSU 2.66 flashed on MMB29S build. All I want to do is set up some redirects and possibly adaway.
Click to expand...
Click to collapse
You have to make some space. Is not systemless root that is the problem. Changes in marshmallow made the system partition full. Reboot into twrp, mount system in rw and delete some unneeded apps in system/apps
Korean and Hindu keyboards for example. But dont delete the latin one. Or some google apps that can be added back in from the store.

TonikJDK said:
You have to make some space. Is not systemless root that is the problem. Changes in marshmallow made the system partition full. Reboot into twrp, mount system in rw and delete some unneeded apps in system/apps
Korean and Hindu keyboards for example. But dont delete the latin one. Or some google apps that can be added back in from the store.
Click to expand...
Click to collapse
I deleted sheets using Titanium, so it must be the mounting. Time to go search on how to do that. Thanks!
Trying `adb shell mount -o rw,remount /system` and get `mount: can't find /system in /proc/mounts`.

swaderade said:
I deleted sheets using Titanium, so it must be the mounting. Time to go search on how to do that. Thanks!
Trying `adb shell mount -o rw,remount /system` and get `mount: can't find /system in /proc/mounts`.
Click to expand...
Click to collapse
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.

TonikJDK said:
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
Click to expand...
Click to collapse
Totally didn't even see that option. You just reboot after checking it? Every time I go back to it, it's unchecked.

TonikJDK said:
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
Click to expand...
Click to collapse
Since checking mount system does nothing, I went into Advanced > Terminal and did an `rm -rf GoogleHindiIME` and still can't edit the hosts file.

swaderade said:
Totally didn't even see that option. You just reboot after checking it? Every time I go back to it, it's unchecked.
Click to expand...
Click to collapse
I mount in twrp. Delete hindu and korean with the file manager in twrp. Reboot, install adaway and it works. I have never manually edited it.
No, the system mount in twrp does not stick on reboot. Mounting system with systemless root is tricky as I understand it. So I just avoid it.

You can't mount system as rw in a booted Android system unless you have a permissive kernel, and you should not have a permissive kernel.

Had the same problem and didn't want to remove things from /system. You can follow the steps here: http://forum.xda-developers.com/showthread.php?t=3266107
Systemless root on 6.0.1 - How to edit build.prop
Sent from my Nexus 6 using Tapatalk

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....

Where Magisk save changed systemfiles? and how change system partition

Hello.
My english ist bad. Sorry.
I use / test first time Magisk and first time devices with guid partitin table.
I modifying the system partition. if Everything works, i want to save changes permanent in the partition.
1.Where are the changes to the system partition saved bye magisk?
I ask, because i read, magisk not changes the system partition if i install apps?
the system partiton is not changed. that's how I understand this.
2. If I want to change the system partition real / permanent, how can I do that?
I want to install some system app after install magisk and and if no bootloops and all works, i want to save it in "real system partition".
3. If i change files on system partion in recovery modus (TWRP), are this real changes or magisk save partion too?
I hope you unterstand my bad english.
Thanks Toshy

Editing in TWRP is real system modification, Magisk isn't initiated then. If you've got a Magisk mask (you've got a module that is mounting files to /system, systemlessly) causing modifications to disappear after a reboot you can also try editing the real /system while booted, in /sbin/.magisk/mirror.

Thank.
for my devices i not found working root methods. only "magisk" works.
if my sytempartitions changes works, i want to make this changes permant.
When I deinstall magisk, the system partition is restored to its original state.
How can I prevent this?
in twrp i can see the files in the system partition. but i cant save / backup the system and restore later, because i restore a parte of magisk to.
What can i do, do deinstall magisk withou restore systempartion or make changes permanent?
Is there an "addon" / module or a config change to make this?
Greetings Toshy

Question Could not mount system in RW mode. Can you?

Did anybody had a luck of getting RW on C25s ? If so, what was the procedure? Of course, I'm aware of shared_blocks feature, which I removed for all system partitions already.
It's funny, but even if flag rw is set as a mounting option in both fstab files - you'll never get RW for any system partitons. You'll never see RW not only for system / vendor / odm but for all my_ partitions - all of them fail to mount in RW.
And no, it's not funny, it's weird.

vp1117 said:
Did anybody had a luck of getting RW on C25s ? If so, what was the procedure? Of course, I'm aware of shared_blocks feature, which I removed for all system partitions already.
It's funny, but even if flag rw is set as a mounting option in both fstab files - you'll never get RW for any system partitons. You'll never see RW not only for system / vendor / odm but for all my_ partitions - all of them fail to mount in RW.
And no, it's not funny, it's weird.
Click to expand...
Click to collapse
all partitions are set to RO because of dynamic partitions

gianonceu said:
all partitions are set to RO because of dynamic partitions
Click to expand...
Click to collapse
This does not answer my question how to get RW on this particular model. Probably, you know that RW can be easily achieved on other realme phones. Actually, on dozens of phones with super partition where we're bound to have dynamic partitions.
Also, when you say "...partitions are set to RO..." what exactly you mean? Set by whom? To repeat: I've manually removed shared_blocks features on all super sub-partitions and then re-created super. When I flash it, I can clearly check in TWRP that tune2fs -l does not show shared_blocks anymore. So, who has set partitions to RO?
If you know what mechanism of android sets RO on super sub-partitions with shared_blocks removed - please share your knowledge.

Well, judging by no responses the question appears to be of almost zero interest for forum members. Is this the case?

I'm glad to confirm that RW on all super partitions can be easily achieved if RMX3195 runs A12.
However, you'll need to convert erofs dynamic partitons of super to ext4 ones. I did it manually in linux. After partitions are converted you also will have to make certain effort to remove bloatware from ext4 partitions. If bloatware isn't removed then total size of ext4 partitions will exceed max size of super and you will not be able to re-construct super.
Funny enough, I failed to get RW on A11.

so i have this problem yet

Congratulations @vp1117 for successfully making your device RW
Did you use the Yuki guide that's basically a copy paste from the thread in my signature (with the addition of a make_ext4fs binary) ? Where did you find those selinux context files for each subpartition of super to plug into the make_ext4fs binary? Without the proper context files the magic is not going to work right?
Thanks!

vp1117 said:
I'm glad to confirm that RW on all super partitions can be easily achieved if RMX3195 runs A12.
However, you'll need to convert erofs dynamic partitons of super to ext4 ones. I did it manually in linux. After partitions are converted you also will have to make certain effort to remove bloatware from ext4 partitions. If bloatware isn't removed then total size of ext4 partitions will exceed max size of super and you will not be able to re-construct super.
Funny enough, I failed to get RW on A11.
Click to expand...
Click to collapse
Can u guide me in same issue I'm also stuck paid no problem

lebigmac said:
Congratulations @vp1117 for successfully making your device RW
Did you use the Yuki guide that's basically a copy paste from the thread in my signature (with the addition of a make_ext4fs binary) ? Where did you find those selinux context files for each subpartition of super to plug into the make_ext4fs binary? Without the proper context files the magic is not going to work right?
Thanks!
Click to expand...
Click to collapse
Hi!
No, I did not use anybody's guide.
I just took a file (product.img, if I recall it correctly) from the old firmware (it was in ext4 format since it was A11 firmware where erofs fs was not implemented yet), mounted it in linux and then just copied into it all files from system_ext.img. Repeated same excersise for my_bigball.img, my_heytap.img, my_preload.img, my_stock.img subpartitions. All contexts were preserved by using proper option of cp command.
And no, I never used make_ext4fs binary.
I made several attempts to re-construct super.img, and I was able to make RW not only for above mentioned 5 subpartitions, but for all 13 subpartitions of super. However, upon some thinking, I decided that I did not need RW for the rest of 8 subpartitions as I did not find much of bloatware in them. So, to make things easier for me I have now RW only for system_ext / my_bigball / my_heytap / my_preload / my_stock. The rest of subpartitions remain in erofs format.
The main riddle for me is that why I failed to achieve RW using same procedure when my RMX3195 ran A11... But I do not plan to return to A11, so this question is already a history for me.

vp1117 said:
Hi!
No, I did not use anybody's guide.
I just took a file (product.img, if I recall it correctly) from the old firmware (it was in ext4 format since it was A11 firmware where erofs fs was not implemented yet), mounted it in linux and then just copied into it all files from system_ext.img. Repeated same excersise for my_bigball.img, my_heytap.img, my_preload.img, my_stock.img subpartitions. All contexts were preserved by using proper option of cp command.
And no, I never used make_ext4fs binary.
I made several attempts to re-construct super.img, and I was able to make RW not only for above mentioned 5 subpartitions, but for all 13 subpartitions of super. However, upon some thinking, I decided that I did not need RW for the rest of 8 subpartitions as I did not find much of bloatware in them. So, to make things easier for me I have now RW only for system_ext / my_bigball / my_heytap / my_preload / my_stock. The rest of subpartitions remain in erofs format.
The main riddle for me is that why I failed to achieve RW using same procedure when my RMX3195 ran A11... But I do not plan to return to A11, so this question is already a history for me.
Click to expand...
Click to collapse
Bro can u try something for me?
In your root dir have folder with name "proc" can u go inside and cut file and move to sdcard or any other modifications to check whether this past also editable or not?

How to mount andoid system

How do I mount the android system as RW? I wish to change my boot animation however the request is blocked as system isnt mounted. I tried to mount using Termux but Magisk denied the permission.
edit: device is Motorola G Stylus 5G XT2131-1.

Magisk version? Android version?

surajpai524 said:
Magisk version? Android version?
Click to expand...
Click to collapse
magisk v26.1 android 12

Android version above 9 or 10 cannot mount system as rw. You need to create a Magisk module to replace or change anything in system partition. On mount it will Magic Mount the module systemlessly.