Installing LineageOS zips in TWRP 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.
If your error still persists after confirming these are not causing your issue, ask someone for help IRC (#lineageos@freenode) 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 have a working device tree/kernel, and would like to submit it for official builds, please contact firstname.lastname@example.org with links to them. Please note - your device must have full hardware support (i.e., every peripheral works) and must be stable.
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.
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.
Can 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.