LineageOS 17.1 adds support for new OnePlus, Samsung, Xiaomi, and other devices following server hack

LineageOS 17.1 adds support for new OnePlus, Samsung, Xiaomi, and other devices following server hack

We may earn a commission for purchases made using our links.

LineageOS is the most popular AOSP-based custom ROM out there. Its origin can be traced back to CyanogenMod, which was itself not only the most well-known custom ROM many years ago but also the reason the OnePlus One was so well-received by the community. Over the years, the team behind LineageOS has kept the project updated with new versions of Android for dozens of Android devices. The latest version, LineageOS 17.1, is based on Android 10 and supports a long list of devices. Now, the custom ROM team has added official support for their latest release for a lot of devices from OnePlus, Samsung, Xiaomi, and more. Newly added devices include the Essential Phone, Moto X (2014), Samsung Galaxy A5 (2016), Xiaomi Redmi Note 5 Pro, and more.

The LineageOS team recently decided to cease the development of LineageOS 15.1 and jump to version 17.1 rather than 17.0 after they decided to rebase on top of the updated AOSP release corresponding to the Pixel 4/4 XL launch. With the update, the team also announced Lineage Recovery as the default option to install LineageOS on officially supported phones. 17.1 also added a new ThemePicker, a partial screenshot feature, and a lot more.

You can find the new LineageOS nightly builds for each of the following devices by tapping on “Get the builds here” on their respective Wiki pages. All of the devices listed here except for the Samsung Galaxy Grand 2 Duos are supported by LineageOS 17.1. The newly added Grand 2 Duos is supported by LineageOS 16 based on Android 9 Pie.

Device + XDA Forum LinkCode-name + Wiki PageMaintainer(s)
Essential Phonematahaggertk, intervigil, npjohnson, rashed
Motorola Moto X (2014)victarajro1979, linckandrea, npjohnson
OnePlus 2oneplus2OzzysCmAcc, aviraxp
OnePlus 7guacamoleb (mirror)*AshwinRC
Samsung Galaxy A3 (2016)a3xeltedanwood76, Stricted
Samsung Galaxy A5 (2016)a5xeltedanwood76, Stricted
Samsung Galaxy Grand 2 Duosms013g (mirror)*djchittoor
Samsung Galaxy S5 Neos5neoltedanwood76, Stricted
Wileyfox Swiftcrackling115ek
Xiaomi Mi A2jasmine_sprout (mirror)*mikeioannina
Xiaomi Mi 6Xwayne (mirror)*Isaac Chen
Xiaomi Mi Note 3jasondianlujitao
Xiaomi Redmi 2wt88047nicknitewolf
Xiaomi Redmi 7onclite (mirror)*Dhina17
Xiaomi Redmi Note 5 Prowhyred (mirror)*srfarias, SebaUbuntu
Xiaomi Redmi Note 6 Protwolip (mirror)*DD3Boh
Xiaomi Redmi Note 7lavender (mirror)*erfanoabdi

*Some of the download pages for newly added devices return a code 500 “Internal Server Error.” Until this bug is fixed, you can download the official builds from the official LineageOS download mirror. For those devices that require it, the download mirror for LineageOS Recovery can be found here.

Be sure to read the installation instructions for each of the devices as well as the other documentation linked such as for Lineage Recovery. Also, be sure to take a backup of your data before you start with the installation process.

Why the delay?

If you’re wondering why LineageOS has had a delay in getting new builds up, the answer is because LineageOS suffered a hack in early May. According to a statement published by the team on May 3rd, an attacker “used a CVE in our saltstack master to gain access to our infrastructure.” Salt is an open-source framework to manage servers that is used by loads of open-source projects like LineageOS. On April 30th, Cybersecurity firm F-Secure publicly disclosed a vulnerability in Salt that could be used to bypass authorization. Attackers quickly targeted Salt installations that were unpatched, resulting in dozens of servers being hacked.

The LineageOS team identified the attack and then quickly took down its servers. The team confirms that their build signing keys are unaffected (so third-parties can’t sign and distribute official LineageOS builds), the currently uploaded builds themselves are unaffected, and the project’s source code is unaffected.