Mt6735 Custom Rom Today
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.
The primary and most devastating barrier to custom ROM development for the MT6735 is MediaTek’s historical violation of the GNU General Public License (GPL). The Linux kernel, which forms the core of Android, is licensed under GPLv2, mandating that any manufacturer distributing kernel modifications must release their corresponding source code. MediaTek, however, has consistently released heavily obfuscated or incomplete kernel sources for the MT6735. Crucially, the proprietary modules—specifically for the Mali-T720 GPU, the 3G/4G modem, and the power management IC—are distributed only as pre-compiled binary blobs. Without access to the source code for these blobs, a custom ROM developer cannot fix bugs, patch security vulnerabilities, or port the hardware drivers to a newer Android version. The MT6735 becomes a black box: one can observe its inputs and outputs but cannot alter its internal logic. 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
