LineageOS Tutorial for Beginners: Complete Guide

Android Guides » Android devices » LineageOS Tutorial for Beginners: Complete Guide

If you're considering switching to LineageOS and you're coming from stock Android , it's normal for everything to sound like gibberish at first: bootloader, TWRP, GApps, ADB, fastboot… In this guide, you'll find the entire process explained step by step in simple language, designed for beginners who want to proceed safely without bricking their phones.

The goal is for you to understand what LineageOS is, how to install it, and how to get the most out of it with apps and settings focused on privacy, performance, and convenience . We'll also cover some practical tips for avoiding common mistakes (and unpleasant surprises) when flashing ROMs, as well as interesting uses for mobile phones and devices like the Raspberry Pi.

What is LineageOS and why is it worth trying?

On a practical level, this means you can have a clean Android experience, free of bloatware from the manufacturer, with frequent security updates and plenty of extra customization options . It's ideal for getting the most out of older phones (for example, a Nexus 5 running a derivative of Android 11) or for having more control over your privacy.

The LineageOS source code is publicly available on platforms like GitHub and GitLab , so any developer or community can review it, improve it, or create variations (such as builds with MicroG, derivatives for Raspberry Pi, etc.). This openness is one of its greatest strengths compared to the proprietary layers of many manufacturers.

It's also important to understand that LineageOS doesn't include Google apps and services by default . This gives you more control over your privacy, but if you want the Play Store and other Google apps, you'll have to install a separate Google Apps (GApps) package during the flashing process.

Important warnings before you begin

Manipulating your phone's internal software is no joke: unlocking the bootloader, changing the recovery, and installing custom ROMs always involve risk . If something goes wrong, you could brick your device or lose all your stored data.

Therefore, it's crucial to understand that you are solely responsible for what you do with your device . Guides and tutorials are typically tested in controlled environments and with devices designed for testing, not with your personal mobile phone that you use daily. If you follow this tutorial, do so at your own risk and always with the utmost caution.

Another key point is that not all Android phones are compatible with LineageOS, and not always with official builds . The LineageOS website and wiki have a list of officially supported models, along with their specific instructions. Additionally, forums like XDA Developers offer unofficial, community-maintained versions for many more devices.

Also keep in mind that unlocking the bootloader and flashing a ROM will erase all your phone's data : photos, apps, conversations, everything. Before doing anything, make full backups and verify that you can restore them if something goes wrong. In these kinds of processes, a backup is your lifeline.

Prerequisites for installing LineageOS on an Android mobile

Before you start typing commands, make sure you have all the necessary equipment and software ready . This will prevent you from getting stuck in the middle of the process.

On one hand, you need a compatible Android smartphone or tablet with its USB cable, and on the other, a computer (Windows, macOS, Linux, or even some systems like ChromeOS will work) with an internet connection. A powerful computer isn't necessary; any decent computer from a few years ago will do for flashing a ROM.

On the other hand, you'll need to install Google's official ADB and fastboot tools on your PC , which allow you to communicate with the device from a terminal or command-line interface. These can be downloaded from the Google Developers website, and the installation instructions are straightforward.

A very practical tip is to always use the original USB cable for your phone (or a good quality one) . Cheap, poor-quality cables can cause connection drops and interrupt critical flashing processes, which is the last thing you want when you're writing to your phone's internal memory.

Finally, check the LineageOS wiki to see if your model is supported and note its codename . This identifier is what you'll see in the filenames of ROMs, TWRP, and GApps packages. If it doesn't match, don't flash, as you could damage your device.

Download files: ROM, recovery and Google Apps

The next step is to gather all the packages you're going to flash so you don't have to improvise . You'll typically need three types of files: the LineageOS ROM, a custom recovery, and optionally, the Google Apps.

On the LineageOS downloads page, you'll search for your device by its commercial name or codename and download the latest build available for your model. The file usually has a long path and name, along with the version, date, and a mention of whether it's a "signed" or "nightly" build.

Next, you'll need a compatible custom recovery; the most widely used and reliable is TWRP (TeamWin Recovery Project) . On the official TWRP website, you can search for your model and download the exact image. Be very careful with variations (for example, different Galaxy S5 models or versions with different processors) because the recovery must be specific to each one.

If you want to have the Play Store, Google Services, Gmail, Maps, and other Google apps , you'll need to download a GApps package adapted to your device's architecture (ARM or ARM64) and the Android version your LineageOS is based on. There are several GApps projects, but the general concept is the same: they are flashed right after the ROM.

Once you've downloaded all these files, it's very helpful to copy them to the same folder where you have ADB and fastboot installed . You can also rename them to something simpler, for example: TWRP.img, LINEAGE.zip, and GAPPS.zip. This way, the commands you'll have to type in the terminal will be much shorter, and you'll avoid typos.

Backups and activation of developer options

Before tackling anything serious, focus on protecting your data. The first step is to create the most complete backup possible of your phone's contents . You can use desktop tools like Helium, dedicated backup apps, or traditional methods such as copying photos and important files to your computer or the cloud.

Once you have the backups backed up, you need to enable Developer Options on Android to allow USB debugging and, if available, OEM unlocking . This is usually done by tapping repeatedly on "Build number" in Settings > About phone; you'll then see the new "Developer options" menu.

Within that menu, you'll need to enable USB debugging and OEM unlocking, if available. If your phone doesn't display the OEM unlocking switch, don't worry, many devices handle it differently; the important thing is that USB debugging is enabled so that ADB can communicate with the device.

At this point, you can connect your smartphone to your computer with the USB cable and verify that the drivers are installed correctly . It's common for the operating system to display a window requesting USB debugging authorization on the phone; always accept the PC's fingerprint on the device to avoid having to confirm each time.

Bootloader unlock: gateway to the ROM

The bootloader is the component that decides which operating system is loaded. As long as it remains locked, you won't be able to freely flash a custom ROM . The procedure for unlocking it varies considerably between manufacturers and models, so the best course of action is to check the specific instructions for your device on the LineageOS wiki and its XDA Developers subforum.

In many cases, the process involves connecting the phone to the PC, using ADB to reboot into fastboot mode, and then running an unlock command . Before doing so, it's advisable to open a terminal in the platform-tools folder and type a simple `adb devices` to confirm that the phone is correctly detected.

A typical command sequence might be something like `adb reboot bootloader` to switch to fastboot, then `fastboot devices` to re-verify the connection, and finally a command like `fastboot oem unlock` or `fastboot flashing unlock` , depending on the manufacturer. This last command is the one that actually unlocks the bootloader and almost always erases all data from the device.

If you encounter errors when running fastboot commands in Windows, you may not be in the correct folder or you may be missing manufacturer-specific drivers . In that case, navigate to the folder where you installed ADB using a command like `cd %userprofile%\adb-fastboot\platform-tools` and reinstall the official device drivers from the manufacturer's website.

When the unlocking process is complete, the phone will usually restart with a factory reset . You'll need to go through the initial Android setup wizard again and, very importantly, re-enable USB debugging in Developer Options before proceeding with the next steps.

Installing TWRP or another custom recovery

With the bootloader now unlocked, it's time to replace the original manufacturer's recovery with an advanced recovery like TWRP . This will allow you to perform full wipes and easily flash the ROM, GApps, and other ZIP files like Magisk.

First, reconnect your phone to your computer, open a terminal in the ADB folder, and run `adb devices` to ensure everything is working correctly. Then, type `adb reboot bootloader` to enter fastboot mode again, and then type `fastboot devices` to verify that the device is responding.

Once verified, it's time to flash the recovery image. The command is usually something like `fastboot flash recovery TWRP.img` , provided you've renamed the file to that name and are in the correct folder. This step overwrites the original recovery with the custom one, so it's critical that the file corresponds exactly to your model.

Once the flashing process is complete, it's best to reboot directly into the new recovery using your device's key combination (for example, power + volume down or up, depending on the model). If you let Android boot instead, some phones will restore the factory recovery, and you'll have to repeat the process.

If everything went well, you'll see the TWRP interface on your screen, usually asking for permission to enable modifications to the system partition or to decrypt the storage . Accept according to the recommendations in your model's specific guide, and you'll be ready to begin wiping and flashing the ROM.

Wipes, flashing of LineageOS and GApps

Before installing anything, it's necessary to clean up the system. From the TWRP main menu, go to Wipe > Format Data to format user data. TWRP will warn you that you're about to erase everything, but if you've already made backups, this shouldn't be a problem. This step is crucial to avoid conflicts with remnants of the previous system.

When the formatting is complete, return to the Wipe screen and select Advanced Wipe . Check the boxes for Dalvik/ART Cache, System, and Cache , leaving the other sensitive partitions untouched unless your specific guide instructs otherwise. Then, slide the "Swipe to Wipe" control to complete the wipe.

With the system ready, you need to copy the LineageOS ROM (and the other necessary ZIP files) to the phone's internal storage . Since you can't boot into Android yet, the easiest way is to use the ADB "push" command. With the device in TWRP and connected to the PC, run something like `adb push LINEAGE.zip /sdcard/` from the terminal and wait for the transfer to finish.

If you're also installing Google Apps and Magisk to root your device , repeat the process with their files: for example , `adb push GAPPS.zip /sdcard/` and `adb push magisk.zip /sdcard/` . Be patient, because GApps packages are usually larger than the ROM itself and may take longer to copy.

Once all the files are on your device, open TWRP's Install menu and locate the LineageOS ZIP file in /sdcard/ . Tap it and add the GApps and Magisk packages to the flash queue if you want to flash them in the same session. Make sure you've selected the correct three files before tapping "Swipe to confirm Flash".

After a few minutes, TWRP will indicate that the installation has finished successfully . At this point, it usually offers two buttons: “Wipe cache/dalvik” and “Reboot System”. It is highly recommended to wipe the cache/dalvik and, when finished, tap “Reboot System” so that the phone boots up for the first time with LineageOS.

First start, checks and what to do if something goes wrong

The first boot of a new ROM is usually slower than normal. Don't be alarmed if the phone stays on the LineageOS boot animation for several minutes , with its three circles on a curved line. The system is generating caches and internal configurations.

As a reference, if you've been watching the animation for more than 15 minutes without it progressing , it's very likely that something didn't flash correctly. In that case, try forcing a restart by holding down the power button until the device turns off and then restarts. If it still doesn't get past the animation, you'll need to go back to TWRP, repeat the wipes, and re-flash LineageOS and the GApps.

Once the boot process is complete, you'll see the Android welcome screen where you can choose your language, connect to Wi-Fi , and, if you've installed GApps, sign in with your Google account . From here, you can restore your backups and start using LineageOS as normal.

From that point on, you no longer need to unlock the bootloader or reinstall the custom recovery every time you change ROMs . If you later decide to try other ROMs, simply repeat the wipe and flash process from TWRP, remembering that it's always a good idea to make new backups before changing ROMs again.

Recommended apps for LineageOS: privacy, convenience, and extras

Once you have the system up and running, the fun begins: fine-tuning LineageOS with applications that fit well in an environment without Google or with less dependence on its services , prioritizing free software (FOSS) whenever possible.

As an alternative to the Play Store, you can install Aurora Store (for Google Play apps) and Aurora Droid (for open-source repositories) . Both allow you to download APKs without a Google account and also offer AuroraServices, which facilitates automatic updates. However, it's advisable to save copies of important APKs to an SD card or your computer, because downloads via a browser sometimes fail or are saved in .bin format.

If you're not convinced by the dialer and SMS app that come with LineageOS, you can look for open-source alternatives like Koler for calls and QKSMS for messaging . These are lightweight, visually appealing apps with all the essential features, perfect for maintaining a coherent system without heavy layers.

For the keyboard, FlorisBoard is a very interesting option, offering advanced features, more emojis, and a privacy-friendly approach . It integrates seamlessly with custom ROMs and can replace the default keyboard if you want something more customizable without resorting to closed keyboards.

In the multimedia realm, many people install YouTube Vanced (or its current variants) to have an ad-free YouTube experience with background playback and without needing to rely on official Google Play Services. These apps usually include their own adapted MicroG for logging in if desired, although they also work for watching videos without logging in.

MicroG, adblock, and file management in custom ROMs

One of the major differences between LineageOS and standard Android is that it doesn't include Google Play Services . For those who want to continue using push notifications, maps, and other Google features without installing the full suite, there's the MicroG project, which freely implements parts of those APIs.

LineageOS does not natively support MicroG due to technical and signature issues . However, some developers maintain specific builds called "Lineage for MicroG," which include modifications to enable native signature forgery, allowing MicroG to be used as a direct replacement for Google services.

Another aspect that many users prioritize when changing ROMs is system-level ad blocking. Apps like AdAway or Blokada stand out here, allowing you to filter ads across the entire device network . They usually require elevated permissions or special DNS or VPN settings, but once configured, you get a much cleaner experience.

For managing compressed files and navigating folders in a custom ROM, a powerful file manager like ZArchiver is very useful, and it has been running stably for years . It allows you to decompress and compress virtually any format, manage large files, and move them between internal storage and SD cards with a simple interface.

An important warning regarding advanced customization: if you're a beginner, installing Magisk or complex modules on your first ROM is not recommended . In many cases, GSI ROMs, some stock firmware backups, or ramdisk modifications may not be compatible with patched boot images, leading to errors that are difficult to diagnose.

Practical tips for changing ROMs without surprises

It's quite common that, once you get the hang of it, you end up trying three or four different ROMs before returning to LineageOS or another one that convinces you . To prevent this constant "ROM flashing" from becoming a game of Russian roulette, it's advisable to follow a series of best practices.

A very useful tip is to always perform a factory reset from your custom recovery before wiping and installing a new ROM. It's an extra step that might take a few minutes, but it minimizes the chance of leftover files from the previous installation causing unusual problems.

During these processes, it's normal for the phone to appear frozen or stuck on a screen, especially during intensive wipes or when rebuilding encryption. Often, it's not that the phone is broken, but rather that it's performing security tasks and securely erasing data . As long as you see activity (progress bars, moving icons), give it time.

Some LineageOS builds have reported occasional bugs, such as the inability to use USB file transfer in MTP mode . If this happens to you, you can always resort to alternative solutions like using the `adb push` or `adb pull` commands to move files , or simply using external SD cards.

It's also common for some browsers to download files in .bin format instead of .apk due to the download header or server configuration. To avoid this hassle, you can install a dedicated download manager like Download Navi, which is FOSS (Free-to-User Service), stable, and offers many options for pausing, resuming, and organizing large downloads.

LineageOS on Raspberry Pi: Turn your mini PC into Android

Besides mobile phones and tablets, LineageOS can also be used to give a Raspberry Pi a second life, turning it into a multimedia box, a pseudo-tablet, or an Android app testing environment . Thanks to its lightweight design and lack of bloatware, it adapts quite well to this type of hardware.

The most interesting boards for this are the Raspberry Pi 4 and Raspberry Pi 400 , which share hardware but differ in form factor (the Pi 400 is integrated into a keyboard). Something similar can also be done with a Raspberry Pi 3 B+, ​​although with some performance limitations, making it ideal for lighter uses.

The installation process usually involves flashing the LineageOS image onto the microSD card using tools like balenaEtcher or Raspberry Pi Imager , inserting the card into the Pi, and powering it on. After the first boot, you'll see the LineageOS logo and go through a setup wizard similar to that of an Android phone: language, Wi-Fi, account, etc.

If you want to use the Play Store in this environment, you'll need to install a compatible GApps package (for example, ARM64 and the appropriate Android version) by sideloading via ADB or using a custom recovery like TWRP adapted for Raspberry Pi . Afterward, it's advisable to adjust some performance parameters, disable animations, and, if possible, use faster storage such as a USB SSD.

Practical uses of LineageOS on Raspberry Pi and limitations to consider

With LineageOS running on your Pi, you can turn it into an Android media center with access to apps like YouTube, Netflix, Spotify, and Kodi , connecting it to your TV like a home Android TV. It's also useful for building a retro Android-based console using emulators like RetroArch.

Another very interesting possibility is using the Raspberry Pi as a testing environment for Android app development . Instead of always relying on resource-intensive emulators or having several physical phones, you can deploy your application on the Pi and test its behavior in a real and inexpensive ARM environment.

With a compatible touchscreen and some DIY skills, it's possible to assemble a Raspberry Pi-based DIY tablet with LineageOS , ideal for home control panels, home automation, information panels, or simply as a learning project.

Even so, let's be realistic: not all Android apps work well on Raspberry Pi . Some depend on specific hardware, DRM, or advanced graphics acceleration that isn't always available or perfectly supported in Pi builds. Furthermore, while decent, the performance doesn't match that of a commercial Android tablet.

With the right optimizations (performance tweaks, disabling animations, and sufficient storage), you can achieve a fairly smooth and functional experience, ideal for experimenting and learning . However, you should be aware that it requires some trial and error and that not everything will be perfect from the start.

After all this, the main idea that becomes clear is that LineageOS is a powerful tool for extending the life of your devices, gaining control over your privacy, and learning how Android really works , as long as you follow the installation steps, make good backups, and combine the ROM with the right apps for your needs (from FOSS alternatives to Google services to ad-blocking and file management solutions) on both mobile devices and Raspberry Pi-based projects.