Quick Answer: Putting Android 16 on a keypad phone is harder than unlocking it. The bootloader unlock can take one toggle and one command, but the boot chain still has to accept the new system. Verified Boot, an unsigned vbmeta image, or an old kernel can stop the phone before Android starts. Take a full raw partition backup before you flash, keep the original firmware ready, and test on a spare phone first.

My mother's phone started dropping calls, so we replaced it with a Kapsys SmartVision3. It's a keypad phone with a talking interface built in, and we bought it used for about $400. It ran Android 11 on a MediaTek Helio P60 with 4 GB of RAM, and within months it was barely usable. I tried to put a modern Android on it. The attempt failed in ways that show where most ROM projects actually break, and where the common advice falls short.

The keypad is the hard part, not the Android version

Most guides treat a phone as "Android plus a kernel." This one wasn't. Kapsys patched the Android system itself. Every key press goes through a library called libinput.so, and the vendor added a function called SV3KeyboardForTalkback that converts arrow presses into TalkBack commands. The dialer, status bar, and settings were also patched to work with that layer.

That's why the feature that makes this phone useful for a blind user is the same thing that blocks a standard port. A Generic System Image (GSI) such as LineageOS assumes the hardware interface behaves like stock Android. On this phone it doesn't, so a clean LineageOS 23.2 build would almost certainly lose the arrow-key navigation she relies on.

Debloating looked like the cheap route. Universal Android Debloater NG can disable preinstalled apps, but it can't fix a base system that's out of date. The actual trouble was resource pressure. The author counted about 25 heavy apps competing for 4 GB of RAM, and the Google app had updated itself from the Play Store and entered a crash loop. Because the phone routes all voice input through that app, dictation died with it.

Unlocking the bootloader was the easy part

Here's the step that surprised me most. Unlocking took one toggle in developer options and one command:

fastboot flashing unlock

The author's log recorded it finishing in 69.642 seconds, with no account, waiting period, or unlock code request. Then fastboot getvar unlocked returned unlocked: yes.

That's where the good news ends. An unlocked bootloader gives you permission to flash. It doesn't tell you the phone will boot what you flash. Many devices wipe user data during unlock, so back up first. And if the phone's IMEI lives in a partition you might touch, check it yourself rather than trusting a rule of thumb. The author believed the unlock wouldn't touch the IMEI, and this phone's protect1 and protect2 partitions are exactly the kind of storage you should verify, not assume.

Why adb backup gave me zero bytes

Most people reach for adb backup first, and that's the trap. It asks you to confirm on the phone's screen. The author pressed "allow" three times, and every time the output file stayed at zero bytes. There was no error, just an empty file that looked like a backup.

A full copy needs a lower-level approach. On MediaTek chips, the tool mtkclient talks to BROM (the Boot ROM, a small program burned into the chip) over USB. BROM mode works even when Android won't boot. The catch is getting into it. You hold the volume keys while connecting the cable, and the timing is fussy. Here, the phone showed up for about four seconds, then booted Android normally. The author spent around forty minutes trying every combination before the window opened long enough to work.

Here's the practical rule: adb backup copies what apps choose to expose, while a raw partition dump copies everything, including the boot chain you'll need if something goes wrong. Start with the dump. Use adb backup only for app data you can afford to lose.

Boot loops, recovery logs, and the vbmeta trap

After flashing the GSI, the phone didn't show a boot animation. It showed "Can't load Android system. Your data may be corrupt" and dropped into recovery. The obvious move was a factory reset, and the phone rebooted straight back into recovery. Doing the same thing again was never going to give a different result.

The recovery menu included "View recovery logs," so the author photographed 397 lines of log and ran them through OCR. The OCR mangled the formatting, but the key detail survived: the recovery filesystem table mapped /system, /vendor, /product, and /data to A/B slot partitions. Recovery knew about the partitions. It didn't know why the boot had failed. A recovery log only covers recovery, not the boot that died before it.

The actual blocker sat in the Android Verified Boot chain. As the Android Open Source Project documentation on Verified Boot explains, the vbmeta image at boot carries a flag that disables verification. The author had set that flag, but the image wasn't signed at all. This phone refused the unsigned image before it read the flag. Re-signing with Google's public test key got the phone to fall back into fastboot instead of recovery. That was progress, but not a booting system.

This is the counter-intuitive part: the popular advice says "disable verification and flash." The reality is that the disable flag only counts if the image carrying it passes the signature check first.

Reading the kernel's last words

The phone still wouldn't finish booting. To see where it died, the author needed the kernel's final messages. On MediaTek devices those usually live in the expdb partition, a crash log that survives reboots. Reading it meant mtkclient again.

This time the tool got past the handshake, and then the phone froze. The log showed DAXFlash uploading stage 1, a jump to 0x200000, and a successful sync, then an error at the status check (0xC0070004). Nothing on the screen responded. mtkclient disables the hardware watchdog so it can work on a device in a bad state. The watchdog is also the timer that normally resets a stuck phone. Without it, the only way out was holding the power button for 15 seconds.

The fix was a small wrapper script that starts mtkclient the moment the device appears, which avoided the long manual timing window. The author got a full copy of the storage, though the write-up says it came hours later than planned and about seven flashes too late. The kernel is also old. The Helio P60 vendor drivers in this build date from December 2021, and the kernel is 4.14.186, which is much older than what current Android releases expect. That could be the root cause, but the logs don't prove it yet.

Options compared

ApproachKeeps keypad and TalkBack?Main riskEffort
Debloat with UAD-NGYesBreaking shared system apps, like the Google appLow
Stay on Kapsys firmwareYesAndroid 11, April 2024 patch, and stalled app updatesNone
LineageOS 23.2 GSILikely no (custom keypad layer)Boot failure, vbmeta signing, and lost arrow navigationHigh
Full custom port with kernel workPossibleOld 4.14 kernel and vendor blobs that may not matchVery high

For most people, the sensible choice is to keep the original firmware and debloat carefully. A GSI port only makes sense if you're prepared to work through the boot chain and keep a recovery path ready.

What I'd do differently

If you're considering this for anyone who depends on a phone, the order matters. Here's the sequence I'd follow:

  1. Take a full raw partition backup with mtkclient before anything else.
  2. Save the original firmware and the exact build number, so you can flash back.
  3. Verify the IMEI and nvram-related partitions are backed up.
  4. Test on a spare device before touching the one in use.
  5. Sign any vbmeta image you modify, and don't rely on the disable flag alone.

Some people will argue that a clean port is worth the risk. That's fair, as long as you can say what you'd lose. In this case the author lost days, and a phone that someone needs for calls can't afford that kind of downtime.

Frequently Asked Questions

What is a GSI in Android?

A Generic System Image (GSI) is a standard Android system build that runs on many devices by reusing the phone's own vendor drivers. It works best on phones that follow Google's Project Treble architecture. Custom hardware layers, like the keypad and TalkBack integration on a SmartVision3, often don't survive the switch, so you may lose features you rely on.

Can you install Android 16 on a keypad phone?

Sometimes, but not easily. Unlocking the bootloader is usually simple, but the phone still has to accept the new system through Verified Boot, and its kernel and drivers must support it. Keypad phones with custom input layers are harder because the vendor's changes to the Android base may not carry over. Expect real kernel and vendor work, not just a flash.

How do I back up a MediaTek phone before flashing?

Use mtkclient to read the partitions over BROM mode, which works even when Android won't start. Run it with the rl (read) command and skip userdata only if you have another copy. Standard adb backup is not enough, since it can return a zero-byte file without reporting an error. Keep the output in a safe place and verify the file sizes.

Why does my phone keep booting into recovery after a custom ROM?

Recovery usually loads when the main system fails to start. Common causes are an unsigned or incorrectly signed vbmeta image, a mismatched kernel or vendor driver, or a corrupted partition. Recovery logs only describe what recovery saw, so check the kernel crash log in expdb for the real failure point. Fixing the boot chain is often more important than the Android version.

Keep the phone working for the person who needs it

If you're about to port Android 16 to a keypad phone, pull a raw backup and write down your fallback before you flash anything. Then try the process on a spare device and note the first point where it breaks. Doing this will show you whether the risk is worth it for the person who depends on that phone, and it'll save you from the seven-flash mistake.