Biden2020prez I may have said before but after all my trials and errors I do believe the only ways to write to system are:
- signed ota package loaded by recovery
- custom recovery
- flashing super from fastboot or sp tools
- replace the code that sets the partitions as read only (mmc definitely won't let you disable it without a reboot and then you must still stop it from being enabled)
Problems I've had with each:
haven't tried making an ota package. Doesn't look fun and would still need to replace the verification keys in recovery.img.
I can't get adbd to run from recovery. Don't really know enough to port existing custom recovery like twrp.
this would take a lot of work to make a particular modification and rather solve this such that you all can make your own edits easily. But if the only thing everyone wants is chromium removed this is an option.
I can't find out where the emmc is set read-only to remove from the boot kernel. There is code in the OT_4058W kernel source but the partition names don't match up so I don't think that's what does it. I also tried using the recovery kernel in boot.img and nothing seemed different about it.
The MTK guys were smart in using the emmc's built in write protection! I think logically the best place to concentrate on is custom recovery. It should not be so difficult to fix this SELinux policy issue but for some reason my recovery images don't always boot even with somewhat small changes..
May have to force myself to take a break though. My chores are piling up here. 🙂
