Why Your Old Phone Deserves a Second ROM

The drawer has a phone in it. A Pixel 3a, a Galaxy S9, maybe a OnePlus 6. The screen is fine, the battery holds most of a day, and the phone stopped receiving security patches two years ago.

That last one is the actual problem. A ROM fixes it.

Older smartphones lined up on a wooden table
Photo by John (Giannis) Tekeridis on Pexels

Samsung shipped the Galaxy S9 on Android 8 and left it on Android 10. LineageOS 21 runs Android 14 on the same hardware today. The chip was never slow. Support ended because updates cost money and the phone had already been sold.

Community firmware is a documented subculture at this point, and Wikipedia’s custom firmware article is a decent plain overview if you want the taxonomy before you dive into forum threads. LineageOS, Pixel Experience, crDroid, /e/OS. All of them target hardware that manufacturers walked away from.

A revived phone earns its keep. Dashcam. Gym music player. Desktop webcam. Kitchen recipe screen. The phone you hand to a kid or take to the beach. A Pixel 3a on a current build still takes better night photos than most new hardware under $200.

There’s a security argument hiding in here too. Samsung left the S9 on a 2022 patch level. LineageOS 21 gets monthly builds with current security bulletins merged in. On old hardware, community support outlasts the manufacturer’s.

Batteries are cheap on phones from this era, ten dollars and four screws. A 2018 phone with a fresh cell and Android 14 handles calls, maps, and podcasts without complaint. You lose a few camera tricks. You gain a phone that still patches.

The work is one evening. Unlock the bootloader, flash a custom recovery, sideload the ROM. You type `fastboot flashing unlock`, read the warning about your data, press the volume key for yes. The phone wipes itself and reboots into a setup screen. You spend the rest of the evening restoring from the backup you made first.

Phones in drawers lose value every month. Phones on nightstands run Android 14.