| Problem | Solution |
|---------|----------|
| No IMEI / No signal | Restore NVRAM backup via TWRP or use Maui Meta Tool. |
| Camera shows green lines | Flash stock camera libs from your original firmware. |
| Wi-Fi MAC becomes 00:00:00:00 | Edit /persist/wlan_mac.bin (requires root). |
| Device bootloops after flashing | Reflash stock boot.img via SP Flash Tool, then dirty flash ROM. |
| Screen stays black after call | Disable “Pocket mode” and “Prevent accidental wake-up”. |
Project Treble support on MT6735 is spotty. While some newer MT6737 devices received official Treble support, older MT6735 models generally did not. Consequently, booting standard AOSP GSIs (like Pixel Experience or LineageOS) is often impossible or requires heavy kernel modification.
The room smelled faintly of solder and old plastic. Under the desk lamp, Asha spread the stripped phone on a towel: a cracked screen, faded logo, Mediatek MT6735 stamped near the camera. It had been in her pocket the night her grandfather finally stopped waking up; now it was the only thing that felt like his voice.
She'd rescued it from a drawer because he had loved tinkering — flashing kernels, coaxing ancient phones into doing new tricks. Asha didn't know how to write firmware, only how to read forums late at night and follow instructions with trembling fingers. Still, she had a plan: build a custom ROM that would make the phone fast enough to replay his recorded lessons without skipping, and quiet enough to sit beside her while she graded papers.
The first downloads took hours. She read build guides, study logs, and long threads where strangers argued about partitions and bootloaders like a congregation debating scripture. People posted successes and disasters: bricked devices, resurrected bricks, kernel forks that ran like poetry, kernels that forgot how to call. Asha printed a checklist, then checked it twice. mt6735 custom rom
"Backup first," the forum insisted, in caps and afraid faces. She clipped the phone to her laptop, watched terminal lines scroll like a heartbeat. A partition image saved to a folder labeled "grandpa_backup." Her hands steadied.
Compiling the ROM felt like composing a song. Each dependency added a new note: a patched kernel for the MT6735, a leaner launcher, a permission manager that didn't nag for every sensor reading. She removed bloatware — the apps her grandfather never used — and slipped in two small things: an old audio player he had loved and a shortcut that opened a folder called Lessons, where she planned to place his recordings.
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."
It wasn't perfect. Some camera features refused to wake, and the battery indicator read slightly off. But the voice files played, clear and whole. Her grandfather's lessons — about how to fix a leaky sink, how to argue with patience, how to forgive — flowed through a little speaker that, moments earlier, had been on the verge of silence. | Problem | Solution | |---------|----------| | No
She left the phone on the table and walked into the kitchen with a kettle whistling. The speaker kept playing as if it, too, remembered him. Later, she posted a short write-up on the forum: which kernel she used, the tweaks that reduced stutter, where she'd replaced a proprietary blob with an open driver. People replied with congratulations and a few technical questions; one user sent a message asking if she could share the patched kernel.
Asha hesitated, thumb hovering over the upload button. The kernel was a puzzle assembled from many hands. Some would call it a mod, others a tribute. She tapped "Share." The file began to upload, seed for someone else's rescue.
Months passed. The custom ROM thread grew a little green vine of comments: users showing off their resurrections, grandparents' voices preserved in low-bitrate songs, thank-yous in broken English. In one reply, someone posted a photo of a phone on a windowsill, sunlight catching its worn plastic. The caption read simply, "For my dad."
Asha opened the Lessons folder that night and added a new recording: her grandfather's laugh, the one that always came just before a story. She pressed save and felt a strange, small peace. The ROM had done what she wanted: it hadn't brought him back, but it made him easier to find. Project Treble support on MT6735 is spotty
When her student messaged the next morning asking how she'd learned to keep both patience and stubbornness, Asha showed them the phone. "I rebuilt the little things that mattered," she said. "Sometimes that’s all a machine needs to keep a voice alive."
And somewhere across the forum, another user, solder iron idly humming, downloaded the kernel and began to write their own checklist, hands already trembling with the same careful hope.
Not all ROMs are equal. Due to the limited RAM (usually 1–2GB) and eMMC speed, you need lightweight ROMs. Forget about heavy Pixel-like interfaces. Here are the best performers.
RR is a classic. For MT6735, Android 10 builds are the "sweet spot" because hardware acceleration for the Mali-T720 is fully optimized.
Unlike Qualcomm’s Snapdragon series, MediaTek has historically been closed-source hostile toward developers. The MT6735 is no exception. There’s no full CAF (Code Aurora Forum) equivalent, no easily accessible kernel tree with clean commits. Most custom ROMs for MT6735 rely on leaked or reverse-engineered kernel sources from OEMs—often incomplete, buggy, or compiled with proprietary user-space blobs.
This means you won’t find official LineageOS or crDroid builds for most MT6735 devices. What exists comes from independent developers on 4PDA, XDA-Developers, or MTK-focused Telegram groups, often ported from similar reference designs (like the MT6735 common tree used for Gionee, Infinix, or Doogee).