Magisk and /Systempartition rw???

Search This thread

Rootbbit

Member
Jan 2, 2022
10
1
Hey, thank you!
Yes, I really have some very important questions for someone who knows their stuff!
So: I have an almost unknown smartphone, a Beafon X5. With Android 7.0.
A great device, just for one.. "Modder" like me, a bit problematic, because absolutely no custom software can be found for it...
But now I've managed to trying Rootaccess For the device.. With your Awesome app, Mtk Easy root and magisk.
My questions :
# can I somehow change the /system/ directory to rwx 7777 for me? Because now it doesn't work, just because of the systemless root. (at least I think) The chown/chmod commands Not working.
It will be" read-only file system" every time printed. I just want to replace the boot animation.
# Question 2:
Why can I only use after every reboot, mtk-Easy-root again from new, to activate magisk?? Why didnt work magisk, Although the SU is insatlled? Only if the mtk script has been run before, I can use the superuser in the magisk Manager Serve.
Have you an idea for this Problem?
Thank you, and best wishes from germany!
by Felix
 

Slim K

Senior Member
May 16, 2015
186
2
122
HTC One (M8)
Sony Xperia Z5
Hey, thank you!
Yes, I really have some very important questions for someone who knows their stuff!
So: I have an almost unknown smartphone, a Beafon X5. With Android 7.0.
A great device, just for one.. "Modder" like me, a bit problematic, because absolutely no custom software can be found for it...
But now I've managed to trying Rootaccess For the device.. With your Awesome app, Mtk Easy root and magisk.
My questions :
# can I somehow change the /system/ directory to rwx 7777 for me? Because now it doesn't work, just because of the systemless root. (at least I think) The chown/chmod commands Not working.
It will be" read-only file system" every time printed. I just want to replace the boot animation.
# Question 2:
Why can I only use after every reboot, mtk-Easy-root again from new, to activate magisk?? Why didnt work magisk, Although the SU is insatlled? Only if the mtk script has been run before, I can use the superuser in the magisk Manager Serve.
Have you an idea for this Problem?
Thank you, and best wishes from germany!
by Felix
For question 1:
Android as a system (linux-like) mounts the system partition as ro (Read-only) by default when booting. In order to be able to modify it, you need to remount the desired partition as rw (read-write) as follows:
While being a root user (#) enter this command in adb or terminal on your phone:
Code:
mount -o rw,remount /system
To revert back to ro (you should do it after you're done), use:
Code:
mount -o ro,remount /system

For question 2:
That app is based on Mtk-su exploit. You can read an article from xda here. Basically, your device's bootloader stays locked, but root resets every reboot, because the attained privileges are only temporary. (su gets to run from /data/local/tmp).
Remember!!! You Bootloader is still locked, meaning AVB and dm-verity are still active. If you modify system (changing the total checksum), you will brick your device!!! And if you unlock the Bootloader, then what's the point of Mtk-su ..........
Hope I helped you somehow. :cowboy:
 
  • Like
Reactions: aIecxs

Rootbbit

Member
Jan 2, 2022
10
1
Schlank K:
Thank you, but I'm not a complete noobThank you, but I'm not a complete noob 😹😹😹😹 Thanks, really. But I tried these methods ed for a long time...
The same thing still happens, I mounted, there is no contradiction, but then nothing actually happened either...
Individual blocks can be mounted in the main directory, but not specifically the system/block. I actually only planned to do this stupid boot animation from the system/media folder. Delete/replace/rename/move zip, whatever, to finally get rid of the thing for my own ani...
And there it started. I've already spent several hours on the net to find a way. There are many options, but none have worked for me so far..
 

Attachments

  • Screenshot_20220121-080818.png
    Screenshot_20220121-080818.png
    108.2 KB · Views: 8

Rootbbit

Member
Jan 2, 2022
10
1
Hey, thanks
I've already tried that. Detects my system Not.
Hey, thanks
I've already tried that. Detects my system Not.
In addition
AVB ( dm-verity ) is bootloader related. You typically use Fastboot to disable it.
I've already tried that. My fastboot gets the same message. I have already tried the system block mounting, via dev/blocks/ but there I also get the read-only message.
Or mounting via busybox, I've already done everything.
I've googled a lot about it, and found nothing else that helps , otherwise I wouldn't have asked here on xda.
There are these read-only ROMs, how do I recognize them? Is ext4 not also read-only from manufacturer from
Thanks, guys
 

aIecxs

Senior Member
Feb 17, 2016
1,630
464
gitlab.com
is your bootloader unlocked!?
you know disable-verity is adb applet, don't you?

you have been warned don't do this on locked bootloader. happy bricking..

btw there is such thing like magisk modules no need to modify system partition at all. just read the Magisk Developer Guides Module Tricks section
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hey, thank you!
    Yes, I really have some very important questions for someone who knows their stuff!
    So: I have an almost unknown smartphone, a Beafon X5. With Android 7.0.
    A great device, just for one.. "Modder" like me, a bit problematic, because absolutely no custom software can be found for it...
    But now I've managed to trying Rootaccess For the device.. With your Awesome app, Mtk Easy root and magisk.
    My questions :
    # can I somehow change the /system/ directory to rwx 7777 for me? Because now it doesn't work, just because of the systemless root. (at least I think) The chown/chmod commands Not working.
    It will be" read-only file system" every time printed. I just want to replace the boot animation.
    # Question 2:
    Why can I only use after every reboot, mtk-Easy-root again from new, to activate magisk?? Why didnt work magisk, Although the SU is insatlled? Only if the mtk script has been run before, I can use the superuser in the magisk Manager Serve.
    Have you an idea for this Problem?
    Thank you, and best wishes from germany!
    by Felix
    For question 1:
    Android as a system (linux-like) mounts the system partition as ro (Read-only) by default when booting. In order to be able to modify it, you need to remount the desired partition as rw (read-write) as follows:
    While being a root user (#) enter this command in adb or terminal on your phone:
    Code:
    mount -o rw,remount /system
    To revert back to ro (you should do it after you're done), use:
    Code:
    mount -o ro,remount /system

    For question 2:
    That app is based on Mtk-su exploit. You can read an article from xda here. Basically, your device's bootloader stays locked, but root resets every reboot, because the attained privileges are only temporary. (su gets to run from /data/local/tmp).
    Remember!!! You Bootloader is still locked, meaning AVB and dm-verity are still active. If you modify system (changing the total checksum), you will brick your device!!! And if you unlock the Bootloader, then what's the point of Mtk-su ..........
    Hope I helped you somehow. :cowboy: