A common strategy among hobbyist developers is to use “stock” binaries from the factory firmware—a process known as . However, the MT6735’s architecture imposes severe version lock-in. MediaTek’s proprietary libMtkOmxVdec.so (video decoder) and audio.primary.mt6735.so are compiled against a specific kernel version (typically Linux 3.18) and specific userspace libraries (like Bionic libc). When attempting to upgrade from Android 6.0 to Android 9.0, these older blobs become incompatible with the newer linker, SELinux policies, and graphics stack (SurfaceFlinger). The developer is forced to either patch the Android framework to emulate old kernel interfaces—an unstable, time-consuming process—or abandon the project. Consequently, most MT6735 custom ROMs are merely “debloated stock” or superficial Android 7.1.2 builds that reuse 90% of the original vendor partition.
In conclusion, the pursuit of a custom ROM for the MT6735 is a quixotic endeavor. The platform’s fate is sealed not by a lack of computational power—for the 64-bit, quad-core Cortex-A53 design is adequate—but by a deliberate corporate strategy of secrecy. The absence of GPL-compliant kernel sources, the fragility of binary blob dependencies, and the lack of low-level documentation transform what should be a software porting task into a forensic reconstruction of a black box. For the user still holding a 2016 MT6735 phone, the only practical path to longevity is a lightweight, debloated version of the stock Android 6.0 or 7.0 ROM, not a true custom operating system. The MT6735 remains a monument to the failure of open-source enforcement in mobile hardware, a reminder that a chipset’s true longevity lies not in its silicon, but in the source code its manufacturer chooses to share. mt6735 custom rom
Even when a developer successfully compiles a basic Android Open Source Project (AOSP) build, the MT6735’s proprietary architecture ensures that core smartphone features will fail catastrophically. The is a notorious example. MediaTek’s camera HAL (HAL3) is tightly coupled with its proprietary ISP (Image Signal Processor) and sensor tuning libraries, which are device-specific and signed with private keys. As a result, a generic LineageOS build for the MT6735 may boot, but the camera will produce green-tinted, garbled images—or crash the entire system. Similarly, the RIL (Radio Interface Layer) , which manages cellular connectivity, relies on closed-source vendor libraries (e.g., mtk-ril.so ). Porting these libraries from Android 6.0 (Marshmallow) to Android 10 (Q) is an exercise in guesswork, often leading to persistent crashes, inability to read SIM cards, or no mobile data. Unlike Qualcomm’s relatively well-documented rmnet and qmi interfaces, MediaTek provides no public RIL specification. A common strategy among hobbyist developers is to