Home » Topic » Can't write to system files

Can't write to system files

Welcome. Forums BLOX2 Forum General Can't write to system files

This topic contains 9 replies, has 4 voices, and was last updated by  spidermonkey720 2 months, 1 week ago.

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #517

    Marvin
    Participant

    Howw do you make system rw? Any attempt with terminal or apps just causes a reboot and system is ro.

    #520

    ieatgravity
    Keymaster

    It has been noted that the kernel has a security feature built in that forces a reboot when ever the system is remounted RW. This prevents malware (and root users) from gaining access to the system partition. This being the case has made us look to alternative solutions to modifying the system, one of which is Magisk. Magisk is capable of modifying the system partition systemlessly, and is very easy to create modules for.

    What exactly are you trying to do? Perhaps I can offer an alternative approach.

    all the best,
    ieatgravity

    #535

    Erick
    Participant

    Just a thought, but would it be possible to side-load another kernel that doesn’t have the security built-in so as to write to the system?  Or would this be detected later on and cause a boot loop?  Honestly, I wouldn’t mind writing to the system as well so I can change governor settings as well as a few other little tweaks.

    #539

    ieatgravity
    Keymaster

    If it were only so easy!

    Draco and myself have spent a lot of time attempting to compile the kernel source code that BLU put out to fix this issue. Though our attempts have not been quite fruitful. This is something we will continue to investigate. In the mean time I have hosted the Kernel source code here on the site if you wish to try to compile it yourself.

    #572

    Erick
    Participant

    So it’s not the watchdog then?

    #574

    ieatgravity
    Keymaster

    What do you mean?

    #610

    Erick
    Participant

    This :  https://www.kernel.org/doc/Documentation/watchdog/watchdog-api.txt

    I figured it was one of the parameters of keeping the watchdog open and could be bypassed by passing the ‘V’ character to the watchdog to close it without reboot. I used to have similar problems with routers. The kernel could also be compiled to allow the watchdog to be disabled from the source of it is the issue.

    #611

    ieatgravity
    Keymaster

    Hmm quite possible, though I was under the impression it was a coded kernel panic. Earlier today I was playing around with /proc/sys/kernel/panic config file (default is 5) which means it reboots 5 seconds after a kernel panic. Changing it to 0 ( echo “0” > /proc/sys/kernel/panic) prevents the system from automatically rebooting after the remount RW command is issued, rather the entire system freezes up and you manually have to reboot the phone.

    #616

    Erick
    Participant

    I’ll be honest, that sounds like it might be the wrong file. What we need to accomplish is preventing the panic in the first place. Even if hard-coded into the kernel, there are parameters that should be able to be sent under certain circumstances. I’ll have to do some research, but I can’t at the moment.

    #748

    spidermonkey720
    Participant

    I have magisk, tried 3 of your OS’s still it resets when I try some app like app2sd or anything to modify the system. any advice

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.

Skip to toolbar