Frequently Asked Questions

• The most common reasons for this error are:
  • You are trying to install a build for a different device. You need to make sure you download the zip for the correct device and variant.
  • You are attempting to migrate from an unofficial build to official LineageOS. A full data wipe is needed if you are coming from something other than an official build of LineageOS.
  • Your vendor/modem/bootloader is too old (or maybe too new). Flash the correct stock image for your device, before wiping data and attempting to install LineageOS again. This information should be listed on the device’s wiki page.
  • Your recovery is outdated. Flash the newest available version of the recommended recovery image for your device.
• If your error still persists after confirming these are not causing your issue, ask someone for help on IRC #lineageos@Libera.Chat or on the subreddit and provide a recovery log.

No. When migrating from an unofficial build to an official LineageOS build, you must follow the installation guide for your device exactly as written. We will not provide support for any other installation path.

If you have already booted into LineageOS, you will need to perform a factory reset and then sideload the recommended Google apps package before booting LineageOS again. The first boot of LineageOS performs critical system initialization. Installing Google apps after this process has completed can lead to a variety of issues, so they must be installed prior to the initial boot.

/data/lineageos_updates/

Few devices allow for it and even less work properly after that. Relocking can result in actual unusable devices, so be warned!

Sorry, as per the question right above, we don’t support this usecase and there may not be a good way to recover. XDA, other similar forums or a search engine may be of use.

Be patient. Devices are slowly being built throughout the week. Maintainers have busy lives, and sometimes an issue is holding it back. Please do not ask for ETAs.

• The download portal exposes various images for our devices. Some are required for the installation or upgrade process (which you can read up on your device’s instructions), some are just there and might help us when we try to debug or fix an issue for you.
• If they aren’t mentioned on your device’s wiki pages, just ignore them!

• In short, you can’t. We don’t build more than 2 versions usually (exemptions were made when major hurdles prevented a large amount of devices to receive a newer version) and we don’t keep old builds around for a multitude of reasons, the largest being that we won’t keep old, insecure, potentially broken builds around. Additionally, we don’t have the server space (or the space on mirrors) to do so.
• There might be archives in the wild and you can check if they are actually signed by LineageOS here. Please don’t expect us to provide any support for them, though, beyond what we offer on this wiki!

• Official support does not guarantee that a build will be produced for every week. Builds may be skipped or temporarily removed due to infrastructure issues, build failures, or device-specific problems detected during the build process.
• In some cases, a build may also be removed if the device is no longer part of the official build roster, if older builds are being purged, or if the LineageOS version it supported is no longer maintained.
• A skipped or removed build does not necessarily mean that support for the device has been dropped. You can check your device’s wiki page to confirm its current support status.
• Please do not ask for ETAs.

• All devices are maintained by open source contributors - sorry, we don’t take device requests. If you would like to bring-up LineageOS for a device, and can meet some basic standards, we’ll happily look into making it official.
• If you would like to submit your device tree and kernel for official builds, please take a look at Submitting a port page.

• If your device is not listed, it’s not supported.
• “The same” is not “equal” which means it needs a separate build.

• We try to keep the list of supported models as comprehensive as possible and effectively do not support any that are not listed.
• If your model is not listed, it is not supported. We do not keep track of the reasoning for which models are supported and which are not, so please don’t ask!

If it’s on this list, we do, otherwise not.

• All devices must meet our Device support requirements.
• If something doesn’t work, look into How to submit a bug.

Because all maintainers are volunteers doing this in their free time, and someone happened to love this device enough to bring it up and properly support it.

• There are none.
• See what other similar devices did to get them to work.

You can report it! Please carefully read the How to submit a bug page before reporting it.

• Short: Don’t ask.
• Longer: We are doing this in our free, unpaid time. Thus, we don’t take feature requests and simply work on our own ideas.

Finding other people that have your issue, especially on other devices, is not helpful to solving it. Instead, to best help us solve the issue, please report it properly as shown here.

• We can’t provide support for any third-party modifications or software since we don’t maintain it.
• Ask whoever provided it to you, because it’s their work.

• LineageOS devices receive several different kinds of security updates, each residing in a different part of the software stack:
  • Android (AOSP) Security Patches: These are the security updates published by Google for supported Android versions. LineageOS integrates, tests, and ships these patches for all supported devices as quickly as possible. Every maintained device receives these AOSP security updates.
  • Vendor Security Patch Level (Vendor SPL): These patches come from the device manufacturer and apply to proprietary vendor components (such as HALs, drivers, and other closed-source binaries). The Vendor SPL reflects the patch level of the stock firmware your device’s vendor blobs were taken from. In most cases, this corresponds to the latest available stock build for that device, but for a variety of reasons, some devices extract from an older, or carrier specific build.
  • Firmware (Bootloader/Modem/etc.): These are hardware-specific often closed-source components such as the bootloader, modem, TrustZone/TEE, etc. LineageOS cannot update these on its own. Many devices ship the expected firmware in their installation package, but some require the user install a specific firmware version prior to attempting to install LineageOS. Please refer to you device’s specific installation guide for more information on this process!

Some devices pass their bootloader unlock status and verity status to Android’s kernel during boot. We don’t purposefully remove those flags, as it isn’t our place to lie about security features. There’s also a blog post about this topic, which explains our reasons further.

• We only provide help for officially supported devices for which we provide our own guides. Follow those instead!
• If you follow the official guide for your device line-by-line and still experience issues, feel free to ask again.

Push notifications require GApps or MicroG. When using MicroG you will need to enable GCM (Google Cloud Messaging) in MicroG’s settings.

In the event that all Google accounts were not removed from the device (as required by the installation instructions), stock Android’s Factory Reset Protection (FRP) persists on the device and causes these problems. In order to resolve this, follow these instructions:

1. Boot into recovery mode
2. Select “Advanced” and then select “Enable ADB”
3. Now, open an adb -d shell from a command prompt (on Windows) or terminal (on Linux or macOS) window. In that shell, type the following command: wipe-frp
4. And from the same shell, type the following command: reboot

This question isn’t new. To list a few reasons:

• A majority of builds are downloaded on mobile devices via our updater. Mobile devices have limited bandwidth and monthly quotas.
• Bandwidth is plentiful for open source projects. We have roughly 100gbit available to us.
• We occasionally need to remove a build because of a device-breaking bug. This is much harder, or impossible, to accomplish with torrents.
• We currently keep the last 4 builds per device. Older builds do not have the latest security patches.
• The top 5 devices account for 50% of our users. 95% of our builds do not have enough users to justify torrents.
• Pigeons are slow and stupid. They also tend to be hit by vehicles and make a delicious treat for predators. We could send your build via pigeon, but chances are very slim it would make it to you.

We can’t tell you. ‘No ETA’ includes the ‘IF’, not just the ‘WHEN’.

We don’t recommend rooting, so we’re unable to provide support for it. Rooting can create serious security vulnerabilities and may cause issues that sometimes require a full system reinstall to fix. Rooting also enables the user to take actions that could permanently damage the device.