hi i rooted my phone and im trying to install audio mods but im unable to mount system partition as rw mode please help me to fix
You are not allowed to write to /system partition, even with root. It's by default for phones come with A10 out of the box.
but what is solution for installing viper audio mod
you can try magisk module, sure it will work.
jatinyaadav said:
you can try magisk module, sure it will work.
Click to expand...
Click to collapse
not working
yes, earlier i faced it too when i have to change the host file for ads blocking, but a magisk module for adblocking sorted out, and i checked if host file is changed or not, but it was changed though I think this is the problem of android 11, google doesn't wants any change in system, I hope this can be solved in custom rom but of now there is no sign of development for this device..
Hi @marshharsha you can try my SystemRW script
Good luck!
Related
Hello, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
icy201 said:
Hello, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
Click to expand...
Click to collapse
download root checker from the play store and make sure that u have root access on your device
messi2050 said:
download root checker from the play store and make sure that u have root access on your device
Click to expand...
Click to collapse
It says i have properly installed root access. Something fishy is going on with my root and my system.
icy201 said:
It says i have properly installed root access. Something fishy is going on with my root and my system.
Click to expand...
Click to collapse
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
messi2050 said:
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
Click to expand...
Click to collapse
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
icy201 said:
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
Click to expand...
Click to collapse
Your device does not have twrp/cwm port ?
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
These are the only possible solutions ive been able to find that do kinda make sense.
"It's because you need a boot.img with r.o secure=0 in the build prop" i went and looked and my file says r.o secure=1 that would explain why my system will not mount as r/w.
Another post i found said -
"I've found the source of the problem asking in the MIUI forums, the boot image will not accept a modified /system.
You have to use the adb interface: adb devices then adb disable-verity.
Disclaimer: I'm not responsible for any damage caused by these operations."
The second solution seems more reasonable and alot easier to do. My question now is: will one or both of these solutions possibly fix both my problems? And the second solution disabling verify should that be okay to do without messing up my device? I do have that recovery i could flash but dont wanna do anything that might make the phone not boot into recovery.
icy201 said:
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
Click to expand...
Click to collapse
Yes that's normal , your problem is because of a buggy root
messi2050 said:
Yes that's normal , your problem is because of a buggy root
Click to expand...
Click to collapse
I just remembered something. I think i know what bugged it. I was trying to do an ota update for my device and it wouldnt let me. I found another app by chainfire called flashfire. I tried to flash the ota update and i had the option "inject supersu" enabled even though i already had supersu installed and everything else i needed for root. I guess doing that messed up all my su files ect.. But how do i fix it? I cant uninstall root cause my /system folder is locked into r/o. If i press full unroot in supersu it will remove the app (although it takes a while!) but all the files needed for root stay.
Guess there just no fixing this phone. Someone really hacked it good i guess, problem is still there and nothing can fix it...
Update - thread can be closed
Problem fixed, to fix the problems i was having i had to download the stock system files for my device and flash them, after that just installed the latest supersu 2.78 zip and remount problem is fixed.
Hello. I installed emui 9.1 on my mate20pro with the dload method. I unlocked the bootloader again and rooted the system with patched recovery. The phone is rooted, but the system partition remains in ro. I have tried various apps to mount the system in rw, but without success. I have also tried some commands found on the net both through adb and emulator, but nothing to do. I have also tried using rootexplorer which has been granted root permissions, but fails to modify anything, nor to insert or delete files within the system folders. What can be done?
ernia66 said:
Hello. I installed emui 9.1 on my mate20pro with the dload method. I unlocked the bootloader again and rooted the system with patched recovery. The phone is rooted, but the system partition remains in ro. I have tried various apps to mount the system in rw, but without success. I have also tried some commands found on the net both through adb and emulator, but nothing to do. I have also tried using rootexplorer which has been granted root permissions, but fails to modify anything, nor to insert or delete files within the system folders. What can be done?
Click to expand...
Click to collapse
it's the new filesystem called erofs (Extendable Read-Only File System)
So there's nothing to do?
Sorry OP if this is off topic , but its about magisk and root in 9.1
I have the "system partition remains in ro" issue too , its annoying yes , but I have a bigger problem
When "rooted" , the phone app ( dialer ), and the contacts app both get broken and crash .. So I have to fastbootflash twrp and lose root to make those apps to work normally again
Anyone with the same problem ?
I need root so I can change and use the font ( I like ) with a magisk module
ernia66 said:
So there's nothing to do?
Click to expand...
Click to collapse
Magisk can already 'replace on the fly' file from /system systemless-y.
It dies already support erofs.
Check Magisk documentations.
There is also a way to mount custom erofs partition....
which is?
ernia66 said:
which is?
Click to expand...
Click to collapse
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
oslo83 said:
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
Click to expand...
Click to collapse
Unfortunately I am not able to do it
:crying:
pvillasuso said:
Sorry OP if this is off topic , but its about magisk and root in 9.1
I have the "system partition remains in ro" issue too , its annoying yes , but I have a bigger problem
When "rooted" , the phone app ( dialer ), and the contacts app both get broken and crash .. So I have to fastbootflash twrp and lose root to make those apps to work normally again
Anyone with the same problem ?
I need root so I can change and use the font ( I like ) with a magisk module
Click to expand...
Click to collapse
use search button pls, you will find the solution already posted
ilos said:
use search button pls, you will find the solution already posted
Click to expand...
Click to collapse
Shhh
Here Rootexplorer paying app does not help writing on erofs partitions...
- Or did you meant something else ?
Magisk Doc. :
https://topjohnwu.github.io/Magisk/
So far, out-of-the-box, Magisk is already ready to replace systemless-ly files and paths on /system easily when used with modules.
-Module just need a a small tweak to add Magisk systemless-ly compatibility to other erofs partitions like /cust
Another way would be to bind or mount...
ilos said:
use search button pls, you will find the solution already posted
Click to expand...
Click to collapse
Wow , what , where ???
I did search but maybe I didnt use the right keywords for such an specific issue
Any extra help , would be very appreciated !
oslo83 said:
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
Click to expand...
Click to collapse
I'd like to create my own partition but I don't know how to do it. Is there any online guide for beginners that I can try?
oslo83 said:
Shhh
Here Rootexplorer paying app does not help writing on erofs partitions...
- Or did you meant something else ?
Click to expand...
Click to collapse
my reply was not for you but for the off topic before my reply: contact, ph app and message force close after root.
as I said, there is already a solution about force close.
Anyway I can only write in /system/etc and some over folders
oslo83 said:
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
Click to expand...
Click to collapse
Hi, I saw that you managed to get a custom erofs partition mounted using magisk. I was wondering if the same could be done for the/product folder because that would allow me to fix the DPI scaling issues found on EMUI 9.0-9.1. Would it be possible to see the code for your magisk module?
Ok, So.
After having a look at what I did with this WorkInProgress...
So far there is 2 main way I thought about and played with:
Method A
A1/
Using the mkfs.erofs tool to make your custom erofs partition and mount it over the original one. (mayne umount it before)
Thanks @ph03n!x for his work on mkfs.erofs.
Thanks @ante0 for his android arm build.
A2/
I did not yet tryed to flash via fastboot or adb these modded erofs images.
Method B
What I'm actually doing is just mounting systemless-y with a magisk module whole folders over erofs one ;
In post-fs-data.sh, I'm doing:
mount -o bind $MODDIR/cust /cust
mount -o bind $MODDIR/version /version
With a ~150MB custom /cust it is working ; It should be tryed/perfected for bigger folders.
Another way, to not replace/spoof the whole folders could be to mount the whole list of custom files at their respective path (-to be tested)
PS: I'm not sure if update-binary module's file should be modded with some:
mount /cust 2>/dev/null
@ line 42
Sources:
https://forum.xda-developers.com/huawei-p30-pro/how-to/erofs-mounting-accessing-img-t3944193
oslo83 said:
Ok, So.
After having a look at what I did with this WorkInProgress...
So far there is 2 main way I thought about and played with:
Method A
A1/
Using the mkfs.erofs tool to make your custom erofs partition and mount it over the original one. (mayne umount it before)
Thanks @ph03n!x for his work on mkfs.erofs.
Thanks @ante0 for his android arm build.
A2/
I did not yet tryed to flash via fastboot or adb these modded erofs images.
Method B
What I'm actually doing is just mounting systemless-y with a magisk module whole folders over erofs one ;
In post-fs-data.sh, I'm doing:
mount -o bind $MODDIR/cust /cust
mount -o bind $MODDIR/version /version
With a ~150MB custom /cust it is working ; It should be tryed/perfected for bigger folders.
Another way, to not replace/spoof the whole folders could be to mount the whole list of custom files at their respective path (-to be tested)
PS: I'm not sure if update-binary module's file should be modded with some:
mount /cust 2>/dev/null
@ line 42
Sources:
https://forum.xda-developers.com/huawei-p30-pro/how-to/erofs-mounting-accessing-img-t3944193
Click to expand...
Click to collapse
I'm rather new to this trying to do something similar on my EMUI9.1 using Magisk, I'm having a problem that i can replace anything in most other folders without much problem like /etc/ for example, but when i try to substitute /vendor/, whatever i put it the folder does not only fail to get substituted, it even disappears from the $MODDIR/system/vendor folder upon restart!
I.e. let's say I create a new file in $MODDIR/system/etc. Upon restart i'm successfully seeing that same file appear /etc.
However when I create a new file under $MODDIR/system/vendor, Upon restart i'm not seeing that under /vendor. ALSO the file is gone from $MODDIR/system/vendor like it was never there.
Any idea what is happening? I've also tried manually mounting in the post-fs-data.sh, where i put the following:
mount -o bind $MODDIR/system/vendor /vendor
That actually caused my system to freeze on the loading screen. I had to reset magisk to non-modded settings in order to get it to run again.
Any help's appreciated.
pvillasuso said:
Sorry OP if this is off topic , but its about magisk and root in 9.1
I have the "system partition remains in ro" issue too , its annoying yes , but I have a bigger problem
When "rooted" , the phone app ( dialer ), and the contacts app both get broken and crash .. So I have to fastbootflash twrp and lose root to make those apps to work normally again
Anyone with the same problem ?
I need root so I can change and use the font ( I like ) with a magisk module
Click to expand...
Click to collapse
i got the solution of above problem from this https://forum.xda-developers.com/huawei-p30-pro/how-to/guide-magisk-root-p30-pro-bl-code-t3938285
Hi I have almost the same issue after updating to EMUI 9.1 the phone hardbricked. It only shows as fastboot on my PC I tried flashing but not sending the img files please help
Hello to all...
After the last system update from pie to android 10(stock rom) I can't change system media folder to be writable, so I can change the lock/unlock sounds. I have tried to do that first with Es explorer, than with Root explorer and Fx explorer, but nothing helps. Also I have tried to find "Documents"(to enable) in App list in main settings but there is no "Documents" in list.
The phone is rooted and every file explorer that have I tried getting granted root permissions. In earier versions of miui I didn't had this kind of problem.
Is there anyone who knows how to solve this ?
try x-plore
Roydamenz said:
try x-plore
Click to expand...
Click to collapse
Thanks for the reply but i don't think that problem is with any file explorer. Btw, I have tried X-plore, also.
Had the same problem and I've solved it by changing twrp to this unofficial twrp 3.3.1 beta08! After flashing this recovery boot to twrp and under mount, check system and vendor then reboot. Let me know if it worked.
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-3-1-beta01-touch-t3987567/amp/
is possible, but I can't remember exactly that I've also flashed this:
https://github.com/Zackptg5/Disable...Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
wizard8400 said:
is possible, but I can't remember exactly that I've also flashed this:
https://github.com/Zackptg5/Disable...Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Click to expand...
Click to collapse
Ok, before i do that... could it be solve from Magisk manager>Advanced settings>uncheck Preserve AVB 2.0/dm-verity ? I am on Magisk 20.2.
I remember that after flashing dfe zip those checks were cleared in magisk, I don't know if the zip does more. First try flashing that twrp, I think that will be enough.
wizard8400 said:
I remember that after flashing dfe zip those checks were cleared in magisk, I don't know if the zip does more. First try flashing that twrp, I think that will be enough.
Click to expand...
Click to collapse
Nothing was successful. First I flashed that TWRP from link. Than, after I tried, I also flash that zip through TWRP, but still can't paste files in system media folder.
For the information after flashed that zip, in Magisk advanced settings first two options was unchecked.
For now, I found that this is related to Android 10 changes.
did you go to twrp>mounts and check system and vendor, after flashing that version of twrp? was twrp beta08 the one you flashed? It worked for me, had the exact same problem after flashing 11.0.4
wizard8400 said:
did you go to twrp>mounts and check system and vendor, after flashing that version of twrp? was twrp beta08 the one you flashed? It worked for me, had the exact same problem after flashing 11.0.4
Click to expand...
Click to collapse
Sorry, Wizard8400 for my too quick response. It actually helped. But, for now only with Root Exporer, which is enough for me. And Root exporer does that change to r/w only once. With next operation it will be ask once again to change from r/o to r/w.
I didn't change anything in TWRP Mount section. Personally, I had thinking but didn't dare.
Thanks for everything !
As a recommendation, you cand try this file explorer, it has root features, and it never let me down:
https://forum.xda-developers.com/showthread.php?t=1523691
wizard8400 said:
As a recommendation, you cand try this file explorer, it has root features, and it never let me down:
https://forum.xda-developers.com/showthread.php?t=1523691
Click to expand...
Click to collapse
Yes, I had that file explorer. Very good. And with some really useful option like some sort of shift/click similar options for multiple files checking.
I really like Es file explorer and until now I was satisfied.
I wanted to install andrax or kali nethunter but I can't install busybox to /system, when I try to install busybox(meefik) it gaves me this:
### BEGIN INSTALL
Remounting /system to rw ... done
Copying busybox to /system/xbin ... fail
Changing permissions for busybox ... fail
Copying ssl_helper to /system/xbin ... fail
Changing permissions for ssl_helper ... fail
Removing old applets ... done
Installing new applets ... fail
### END
And if I try to manually move the busybox to /system/xbin it says that there isn't enough space(via MiXplorer)
And I tried with Stericson busybox and It would show that there is only 6 mb on /system, after pressing install it would say that it is not installed and then crash.
Please help.
same thing happened to me So I installed busybox from the magisk module
Kritikumarb said:
same thing happened to me So I installed busybox from the magisk module
Click to expand...
Click to collapse
Busybox for android NDK?
Edit: cause that one is broken for me
I'm having the same problem, Im unable to move apps to the system it says that I don't have space.
I need help cos I need to make some apps in the system
elefantex said:
I'm having the same problem, Im unable to move apps to the system it says that I don't have space.
I need help cos I need to make some apps in the system
Click to expand...
Click to collapse
I downgraded to miui 11 pie cause Android Q is buggy and unstable
The Bluetooth is broken, busybox and /system
root first with latest magisk canary
exodius48 said:
root first with latest magisk canary
Click to expand...
Click to collapse
Not needed, android 10 is very unstable
The solution is to downgrade to pie
Now everything works
I tried using custom roms but probably the android Q firmware for poco f1 is broken or incomplete
AxelStrife said:
Not needed, android 10 is very unstable
The solution is to downgrade to pie
Now everything works
I tried using custom roms but probably the android Q firmware for poco f1 is broken or incomplete
Click to expand...
Click to collapse
Lol,, I always use busybox NDK on android 10, no problms so far. The problem is memeUI itself. :laugh:
I run into following problem. I have successfully rooted my phone and installed magisk. Now what I try is to replace the bootanimation.zip...
But it fails at permissions. I granted superuser access via Magisk to the app (Es file explorer) and I also toggled the root option to in in this app. But whichever I try it fails neither can I delete or write to the system. I also tried different root explorers facing the same issue.
Those someone know how to solve this?
Thanks in advance
Graru1
Same issue here.
Sadly don't know an solution
Your /system partition where you want to replace the file is read only. Flash a custom rom or use this automatic script from this thread to rebuild your /system partition as read-write and you will be able to replace the files.