For a Moto G5, the most defensible answer is the last officially supported LineageOS branch for the exact cedric variant, with an important limitation: LineageOS now marks the Moto G5 as no longer maintained. That makes LineageOS 18.1, the retired Android 11 branch, a useful documented reference point rather than a current blanket recommendation. A Moto G5 owner should choose a ROM only after confirming the precise handset variant, bootloader status, build date, and recovery plan. An old phone can still be useful, but an unsupported community build is not automatically safer or better than the stock software already installed.
Start by identifying the phone, not by downloading a ROM
“Moto G5” is a marketing name; ROM compatibility is decided by the device codename and model. LineageOS identifies the Moto G5 as cedric and lists XT1670, XT1671, XT1672, XT1675, XT1676, and XT1677 among the relevant models. Check the model number in Android’s device information and compare it with the ROM project’s own device page before doing anything else. A file intended for a different Moto generation, a Plus model, or another codename can leave the phone unable to boot.
This is also where old forum advice becomes risky. A thread may be accurate for a particular country variant, firmware revision, recovery, or Android generation and still be wrong for another G5. Treat the exact model, codename, required firmware, and build date as a single compatibility check. If any one of those details is absent from the maintainer’s documentation, stop there rather than filling the gap with a similarly named download.
Why LineageOS is the best documented historical choice
LineageOS is the clearest starting point because its project documentation explicitly recorded support for cedric. The device page says the phone previously supported LineageOS 17.1, based on Android 10, and 18.1, based on Android 11. That history is valuable: it provides a known device name, an official project record, and a reference for what the project once supported. It does not mean the project currently issues security updates for the Moto G5.
For someone comparing archived options, 18.1 is the more capable of those two documented branches because it is the later Android generation. It may be appropriate for a secondary device that can tolerate the age of both the hardware and the software. It is a poor reason to assume that every “Android 11 for cedric” file found on a mirror or video channel is trustworthy. The quality question is the individual build and maintainer, not merely the Android number printed in its title.
LineageOS also records a device-integrity quirk for cedric. That matters in practice: a custom operating system may cause banking, payment, streaming, workplace, or game applications to reject the phone even when normal calls and basic apps work. Test the applications that actually matter before retiring another phone or wiping the existing installation. Do not rely on claims that a ROM will make all such checks disappear.
Bootloader and recovery status decide whether a ROM is realistic
A custom operating system cannot be evaluated separately from the path used to install and recover it. The LineageOS documentation describes entering the G5 bootloader interface by powering the phone off and holding Volume Down with Power. That is useful for confirming that the phone can reach its basic bootloader screen, but it is not proof that the device is eligible for unlocking or ready for a particular installation procedure.
Before considering a change, establish four things: whether the bootloader is already unlocked or can legitimately be unlocked for that exact handset; whether the project documentation identifies a supported recovery and required firmware; whether a complete backup exists outside the phone; and whether a verified stock restoration route is available for that model. Installation can erase user data, and an older device can be especially awkward to restore when official files or drivers have disappeared. Keep the existing system until those questions have answers.
Do not turn a ROM comparison into a collection of bypasses. A guide promising that an unlocked bootloader, root access, or a particular add-on will guarantee payment-app compatibility is not making a reliable promise. The sensible target is a stable, documented installation that suits a spare handset, a development device, or a user who accepts that some protected services may not work.
How to assess an unofficial cedric build
There may be newer unofficial builds for cedric, but “newer Android” should be treated as a claim to investigate, not a recommendation. Prefer a maintainer page that identifies the exact device and publishes a recent changelog, install notes, known issues, and a support channel where faults are discussed. Look for clear evidence that the download is still available from the maintainer or project rather than a re-upload site. Check whether the camera, mobile data, calls, Wi-Fi, Bluetooth, storage encryption, and charging are listed as working or problematic.
A build that is fast in a short video can still have an unreliable camera, broken emergency-call behaviour, weak battery life, or a security patch level too old for sensitive use. Read the known-issues section before the feature list. If the project only has old comments and no current maintainer activity, regard it as an archive. That can be fine for experimentation, but it is not a strong choice for a primary phone.
Choose by intended use
- For the least ambiguous historical route: use the LineageOS cedric page as the benchmark, and treat its retired 17.1 and 18.1 support as historical rather than current support.
- For a spare phone used for simple tasks: an archived, well-documented build may be acceptable after backing up data and testing the few required apps.
- For banking, work authentication, or a device that must receive prompt security fixes: an unsupported Moto G5 is a weak fit. Keeping the stock phone offline for limited use or replacing it is often the more dependable decision.
- For experimentation: choose only a build with exact-model documentation, a stated recovery path, and an independently verified way back to stock.
What to know before committing
The best ROM for Moto G5 is therefore conditional rather than a modern leaderboard winner. LineageOS 18.1 is the best documented last official reference for cedric, while LineageOS itself says the device is no longer maintained. Begin with the model number, confirm the codename, preserve a recovery route, and judge every unofficial build by its documentation and current maintenance. If the needed apps fail integrity checks or the phone cannot be restored confidently, do not flash it. That conclusion is more useful than installing a newer-looking Android version with no dependable support behind it.