Mt6735 Custom Rom
The Short Answer (TL;DR)
Do not buy an MT6735 device expecting a thriving custom ROM scene. If you already own one, lower your expectations significantly. You will likely be limited to LineageOS 14.1 (Android 7.1.2) or a buggy LineageOS 15.1 (Android 8.1) build. Development is dead, and security patches are ancient.
Late into the night, the build finished. The flash tool recognized the phone, the progress bar crawled, then leapt. For seconds that felt like years, nothing happened. Then the boot animation stuttered, the tiny logo flickered, and the screen filled with a new, cleaner interface: gentle colors, simple icons, and the boot message she'd edited to read: "For K. — Carry on." mt6735 custom rom
CrDroid: Offers a balance of LineageOS stability with additional customization features. Essential "Pieces" for Installation The Short Answer (TL;DR) Do not buy an
Build steps
- Set up Linux build environment (Ubuntu recommended). Install packages, Java, repo tool.
- Initialize Android source (repo sync of chosen branch).
- Place device tree, kernel tree, and vendor blobs in appropriate directories (device//, kernel//, vendor/).
- Configure BoardConfig.mk and device.mk to match partition layout, hardware, and features. Ensure the Android.mk/Android.bp files include correct kernel image path and DTB usage.
- Build kernel with cross-compiler, produce zImage/Image.gz or Image and dtb if required.
- Run lunch for device and make bacon (or make -jN).
- Resolve build errors iteratively: missing HALs, proprietary blobs, incorrect compiler flags, or mismatched kernel headers.
- Produce flashable images: system.img, boot.img, recovery.img, vendor.img as needed, or a signed boot/recovery if the device enforces verification.