Installing LineageOS zips in Recovery results in “Error 7”
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 #[email protected] or on the subreddit and provide a recovery log.
My device is officially supported, but there’s no zips for it on the download page. Where are they?
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.
My device is not officially supported, but I’d really like to give LineageOS a try. Can you support my device?
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.
My device is not on the device list, but it is just the same as that other model. Can I use it?
If your device is not listed, it’s not supported.
“The same” is not “equal” which means it needs a separate build
The list of supported models for my device doesn’t contain a specific one I need. Can I still use it?
We try to have the list as complete as possible. If yours isn’t there it will either not work or we couldn’t test it
A build for my device disappeared? Where’d it go?
Occasionally a build is broken. If this happens, we remove it until the next build cycle. It is also possible the device is no longer in the official build roster and its old builds are being purged, or that the version it supported is no longer supported. You can check your device’s wiki page to confirm support status.
Where can I find the last build for xxx device before support was dropped or its LineageOS version was deprecated?
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 are so many images on the download portal. What are they?
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!
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.
Will you enable signature spoofing?
Once again, it isn’t our place to lie about security features. No.
Where does the updater app store the downloaded zip?
Mirrors? Why don’t you use torrents? Or IPFS? Or carrier pigeons?
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.
Can/should I relock my bootloader?
Few devices allow for it and even less work properly after that. Relocking can result in actual unusable devices, so be warned!
I have relocked my bootloader and can’t get my device to work anymore. What now?
Sorry, as per earlier in this FAQ, 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.
Will my device receive the next android version?
We can’t tell you. “No ETA” includes the “IF”, not just the “WHEN”
I am following a guide/video somewhere on the internet and am stuck, help?
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.
I read somewhere/was told that you support my device?