Database Develop

No space in /system while df says there are 14.7MB

Just upgrade to android 6.0.1 and redoing the root,busybox stuff
While rooting, I learn that /system is quite packed. After a few research time, many suggest that to place something in /system, delete some system app(particularly those available at Play Store, e.g. Sheets, Slides, Google Music, etc). So I delete some of them and thought I can flash busybox easily.
I was wrong.
Even I go to TWRP and mount /system rewritable, no matter I use "adb push" or "cp (in adb shell)" to place busybox into /system/xbin, they tell me there is no space.
But if a use "df" in adb shell, non su mode, it tells me there are 14.7MB, while my busybox binaries only 1.05MB.
Do anyone got idea to solve this and so kind to help me? Thank you.

xerubium said:
Just upgrade to android 6.0.1 and redoing the root,busybox stuff
While rooting, I learn that /system is quite packed. After a few research time, many suggest that to place something in /system, delete some system app(particularly those available at Play Store, e.g. Sheets, Slides, Google Music, etc). So I delete some of them and thought I can flash busybox easily.
I was wrong.
Even I go to TWRP and mount /system rewritable, no matter I use "adb push" or "cp (in adb shell)" to place busybox into /system/xbin, they tell me there is no space.
But if a use "df" in adb shell, non su mode, it tells me there are 14.7MB, while my busybox binaries only 1.05MB.
Do anyone got idea to solve this and so kind to help me? Thank you.
Click to expand...
Click to collapse
yes, google did it on purpose. its not full, but it is. use a root file explorer, delete some apps, reboot. then youll be fine after

An alternative solution is to backtrack your modifications to /system and install SuperSU in systemless mode. Installing Busybox afterward will send the files to the /su/xbin directory. As a bonus, Android Pay should function normally.

Use a root explorer or in TWRP mount system and delete /system/app/(any foreign keyboards you don't need, such as GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME)

I used systemless root. Then I could install busybox at /su/xbin instead?
And just for report, it seems uninstall won't help without manual deletion of /system/app, all system apps I uninstalled through Titanium Backup automatically revived after reboot.
Sent from my Nexus 6 using XDA Free mobile app

I don't know about the other busybox installers, but Stericson's busybox installer does have /su/xbin as an available install location if systemless root is detected.

make system dir writeable

Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!

groggycl said:
Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
Click to expand...
Click to collapse
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.

mhrajib said:
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
Click to expand...
Click to collapse
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?

groggycl said:
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
Click to expand...
Click to collapse
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess

mhrajib said:
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
Click to expand...
Click to collapse
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?

groggycl said:
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
Click to expand...
Click to collapse
What kind of error do you get?? Can you do other operations through link2sd??

mhrajib said:
What kind of error do you get?? Can you do other operations through link2sd??
Click to expand...
Click to collapse
the error is the following..
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Thats the error. Tried with titanium backup pro version and it gets stuck "PROCESING" the thing... It uninstall the app I want to move to system app, but then never finishes processing..
I also used a app called mount "/system ro/rw". I grant it superuser permissions and when I hit the "mount /system rw" a message appears that says; "Your device might not be rooted or is it not compatible!"

groggycl said:
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Click to expand...
Click to collapse
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.

leledumbo said:
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
Click to expand...
Click to collapse
I've installed busybox and when I try lsof /system it says "toybox: Unknown command lsof", is there any solution?

[Question] Correct way to handle systemless root in a file manager

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.

Abnormal State - "su" binary not from Magisk has been detected

Hello!
I am on LOS GSI 19.1, S20 FE LTE Exynos (with TWRP) - when starting Magisk have this msg:
Abnormal State
A "su" binary not from Magisk has been
detected. Please remove any competing
root solution and/or reinstall Magisk.
What could be reason of that and how to fix it. :/ Maybe someone can help...

Found your thread while searching for a solution of the same problem.
I thought I will share a solution as finding useful info novadays gets harder every day.
Not to get into detailed description, generally it's caused by su existing in /system/xbin path, and in most cases shell is started with su privileges due to an entry in /system/build.prop
Just rename the /system/xbin/su under adb shell or terminal to for example ssu/zu/subackup whatever the name is and after reboot magisk shouldn't yell with a popup.
btw. I haven't encountered any misbehaviour of magisk, but for the sake of not getting this popup I made the change by the way of working with shell on other things.

YoShake said:
Found your thread while searching for a solution of the same problem.
I thought I will share a solution as finding useful info novadays gets harder every day.
Not to get into detailed description, generally it's caused by su existing in /system/xbin path, and in most cases shell is started with su privileges due to an entry in /system/build.prop
Just rename the /system/xbin/su under adb shell or terminal to for example ssu/zu/subackup whatever the name is and after reboot magisk shouldn't yell with a popup.
btw. I haven't encountered any misbehaviour of magisk, but for the sake of not getting this popup I made the change by the way of working with shell on other things.
Click to expand...
Click to collapse
Hi I found that for some reason downgrading to android 12 PE works for some reason but when I update to android 13 EvolutionX it shows the popup do you mind sharing the command for adb on how to do this because it denied access for me when I tried remounting from r/o to r/w.

AirForceNBA said:
do you mind sharing the command for adb on how to do this because it denied access for me when I tried remounting from r/o to r/w.
Click to expand...
Click to collapse
if rom you use is complied with adb root capabilites, then just use linux mv command after connecting to shell
Code:
adb root
adb shell
mv /system/xbin/su /system/xbin/zu
if not, then maybe under twrp commandline it could be possible?

AirForceNBA said:
Hi I found that for some reason downgrading to android 12 PE works for some reason but when I update to android 13 EvolutionX it shows the popup do you mind sharing the command for adb on how to do this because it denied access for me when I tried remounting from r/o to r/w.
Click to expand...
Click to collapse
I solve this issue in my gsi evolution X android 13 after flash overlyfs.zip in my magisk manager ... Click Download System Rw in this site
Magisk Modules - some Daily use Magisk Mods in 2022 | Use these Modules Daily ! » Tech Karan
Magisk Modules are here !
techkaran.co.in
and then flash overlyfs.zip using magisk manager...
Need telegram apps and account to download the file...

Hi I have the same issue. I tried to rename su in xbin but I got permission denied. Root explorer granted root and system is rw. In abd with the command above also permission denied. Xbin folder is not visible in recovery. Overlayfs module is not working with my kernel. Galaxy S21+, TWRP, Lineage 19.1, Hari GSI kernel. Any idea?

Did
K_a_m_i said:
Any idea?
Click to expand...
Click to collapse
Did you set rw on /system or /system/xbin?
Set rw on the top dir, not nested one in which you want to make changes, or you won't get permissions to change anything in any nested directory you set rw on.
Try to copy the file somewhere else and then delete it from its original path. But I bet you won't succeed. Maybe changing the owner/group and all permissions to 777 would do.
I'd also try in safe mode, or in native recovery mode (not twrp, assuming you still have access to it) using ADB

For me it disapeard by reinstalling magisk by the TWRP.

K_a_m_i said:
Hi I have the same issue. I tried to rename su in xbin but I got permission denied. Root explorer granted root and system is rw. In abd with the command above also permission denied. Xbin folder is not visible in recovery. Overlayfs module is not working with my kernel. Galaxy S21+, TWRP, Lineage 19.1, Hari GSI kernel. Any idea?
Click to expand...
Click to collapse
Are you try to flash Overlyfs first without any module in your magisk...
After you flash magisk manager in your phone and installed already, open it and then restart your phone.. then
First: flash only Overlyfs.zip in your magisk without any module installed.. then restart your phone
Second: download root explorer and grant root
Third: find su in system/xbin and rename it in ZU and save and delete zu then restart your phone
I hope I helped you with this post

Need help changing system partition/directory to Read/Write to systemize apps

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.