lgexalter1 so far I've only had success doing it on the phone itself with magiskboot, which takes a bit of time to repack. I work out of /data/local/tmp:

/data/data/com.topjohnwu.magisk/lib/libmagiskboot.so unpack boot.img
/data/data/com.topjohnwu.magisk/lib/libmagiskboot.so cpio ramdisk.cpio 'add 0700 overlay.d/custom.rc custom.rc'
/data/data/com.topjohnwu.magisk/lib/libmagiskboot.so repack boot.img neutron.img

if you're messing with super I did get it open using lpunpack. Not sure where that came from though...

  • yeti replied to this.

      • yetiLevel 3 - Gold Member

        • Post #416

        neutronscott that explains why my images wouldn't get repacked correctly when I tried working with an overlay. thanks for this

          • darthLevel 6 - Platinum Elite Member

            • Post #417

            Why is 'Modules' greyed out in my magisk app? Also when I try running Gflip6_TF:/ # magisk --install-module terminaldebloater-v5.1.zip I get: Incomplete Magisk install?
            Would terminal debloater work to uninstall the browser?

              darth go to settings and enable zygote or whatever and reboot

                Hi everyone! I am in yeshiva and cannot really be involved in this now. I just want to say, I am keeping updated on your guys' project and I'm really excited.

                [Login to see the link] You're really amazing. We're so glad you made your way to these forums, and we all owe you a big thanks!

                • FlippyLevel 6 - Platinum Elite Member

                  • Post #422

                  Is this the same as the Alcatel My flip 2? Because that seems to run Kai OS...

                    EnriqueMcquade There was a patch in android 11 that accidentally broke virtual mouses. The patch seems useless for flip phones anyway, i don't know how we would disable it though. If i have a chance, ill try to research more about the patch and see what needs to be done to fix it.

                      EnriqueMcquade Are you guys still working on the custom recovery?

                      I was hoping to quickly enable adb in the recovery img but not really sure what to do with this:

                      C:\Users\m\Downloads\mtk>adb shell
adbd F 09-03 18:47:05   311   311 shell_service.cpp:380] Could not set SELinux context for subprocess
libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 311 (adbd), pid 311 (adbd)

                        darth I read through the instructions and that doesn't seem to address the problem with these partitions. This removed the "shared_blocks" feature, which we don't have:

                        Gflip6_TF:/data/local/tmp # tune2fs -l /dev/block/dm-2 | grep -e vol -e feat
Filesystem volume name:   /
Filesystem features:      ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize

                          • FlippyLevel 6 - Platinum Elite Member

                            • Post #432

                            shadowmyst Ok so a bit irrelevant but their naming scheme is terrible!!

                              What would happen if you uninstalled browser and installed A new app with the same package name. Would the app be replaced with browser on a reboot?

                                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. 🙂

                                    neutronscott we also want to remove fm Radio and maybe hotspot. Depending on the circumstances we may want to also add system apps or make other modifications. We are certainly very grateful for all you've done thus far and sorry its preventing you from getting things done. I wish i could do things myself rather than telling other people to try them, Unfortunately i can't.