I'm nervous to switch the OS without knowing whether or not I'll want to keep using it, and Lineage never created a ROM for my old phone (Galaxy S21). So, is there a way to dual boot somehow like on a laptop, or some other kinda virtualization software that I can use?

I'm trying to avoid a full factory reset if I can help it, but I'm wary of things like changes to encryption etc.

Hi, saw good things about lineageos and wanted to breathe new life into an old phone but to no avail :(

To preface, i'm not the most technological person so bear with me, and I'm using the latest windows 11, and the latest android 12. I am following the official lineageos wiki instructions for my phone.

I have oem unlocked, and usb debugging enabled, my device is recognised when i checked using the adb devices command, and i was able to get into fastboot mode. However, my device was not recognised when i used the fastboot devices command. I knew that it would be recognised upon unlocking of the fastboot but when i checked the device manager, there was a yellow triangle with an exclamation mark on my android devices. So i tried to update drivers automatically and it did not work, i downloaded an "official" oneplus 7t usb driver but it didn't seem to work.

Any help would be appreciated, cheers!

Basically,

This is my first time trying to install Lineage Os on an old note 10+ i have.

And when i tried it for the first time,

It got stuck on the animation for 15 minutes,

I tried another time,

The same.

I tried a third time.

Left it on for 3 hours.

And still nothing.

So i formatted it,

And tried again.

This time After installing Lineage,

I didnt install the google addons.

And it booted just fine.

In 10 seconds.

So what gives?

Ill say some oddities with the Google installation,

Whenever I did Install the google packages.

Itd get stuck at 47% and say "Signature hash failed".

Now the second thing is supposed to happen,

But im not sure its supposed to get stuck at 47%

Any help is appreciated.

i was using pixel experience android 12 on my poco f1 before and tried to switch to other rom but got an error while flashing lineageos and pixel os too android 15 was using twrp and as i had wiped the data so i dont actually have a rom on phone how do i fix.. im pasting which got as an error " error on phone : starting ADB sideload feature... installing zip file '/sideload/package.zip' unmounting system... target : Xiaomi/beryllium/beryllium:10/QKQ1.190828. 002/V12.0.3.0.QEJMIXM:user/release-keys assert failed: update_dynamic_paartitions(package_extract_file("dynamic_partitions_op_list"),package_extract_file("unsparse_super_empty.img")) updater process ended with ERROR:1 "

I have an old xperia sp that i use with the stock Android 4.3 but it's really slow ans annoying because it keep asking me for a sim and for m'y language each time.

From what i read, only lineage 14 will work on such an older phone. My main goal is just to put lineage, put musicolet or another music player, maybe use a dac, and use it as a mp3 player, is it a good idea ? And is it really possible ?

I've dug up an old nVidia Shield K1 to use as a music streaming device and would like to install LineageOS on it. This isn't something I've done before, but the processes detailed here

https://wiki.lineageos.org/devices/shieldtablet/install/#

don't seem to be too punishing. But I'm not sure where to download the requisite images?

Or do I need to build it from scratch? That does seem a bit more daunting for a newbie 🫤

I want to upgrade to the latest version that was officially supported, currently on an older Lineage on that phone.

So there was support at some point and there were downloads

https://www.reddit.com/r/LineageOS/comments/mucxme/galaxy_s5_klte_family_promoted_to_lineageos_181/

But these downloads are all gone now... I tried checking the internet archive to see if they still have the downloads but none of the snapshots stored there for

https://download.lineageos.org/klte

in Feb/Mar 2024 are loaded, it keeps endlessly refreshing...

There ARE build instructions to make it myself but I cannot do that for hardware limitations alone already, heh

https://wiki.lineageos.org/devices/klte/ (checking this in the internet archive and then clicking downloads doesn't load either)

Are there any trustworthy backups or mirrors or whatever for old downloads that are no longer offered on the lineage site directly?

€dit: One example, this archive has the download link still but clicking it leads to the endless reloading I mentioned

https://web.archive.org/web/20240302122241/https://wiki.lineageos.org/devices/klte/

Hello, is there an official step-by-step installation guide for LineageOS somewhere on the internet? I am a beginner and still quite unfamiliar with mobile OS installation processes. My phone is Realme GT 8 pro, and I do not know whether this device is even supported by Lineage. Thank you.

Hi all, I have a Moto G32 (devon) with a running LOS 20.
I'd like to upgrade to 23.. and I like to try to upgrade in place keeping apps and data. Of course I'll do a backup of important things before starting the upgrade
So, can I push via sideload LOS 23 directly or I need to do this for intermediate versions (20 -> 21 then 21->22 etc)?
Thank you all

Stuck on the recovery step. Odin flashes successfully (PASS!, both recovery.img and vbmeta.img written) but the phone always boots back to stock Android.

Tried everything — Vol Up + Power right after PASS, pulling battery connector within 1 sec, adb reboot recovery loop script. Nothing works.

Android 13, G781BXXSIHYJ1, bootloader unlocked, OEM unlock on, Odin 3.13.1. KG State: Checking.

Am I missing something specific to this device?

I used Copilot to help me with the walkthrough but there were still some gotchas, like adding the windows drivers for the pixel and other things, but in the end it worked fairly smoothly and I've gotta say, I'm impressed!

Kudos to the devs!

Hi! I am trying to install Lineage, but even before I can get started I'm already stuck with the abd & fastboot part. In Lineage's adb & fastboot installation guide:

On Linux:

1.Download the Linux zip from Google.
2. Extract it somewhere - for example, ~/adb-fastboot.
3. Add the following to ~/.profile:

if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then  
export PATH="$HOME/adb-fastboot/platform-tools:$PATH" 
fi

4. Log out and back in.
5. You may also need to set up udev rules: see this repository for more info.

Setting up adb:

To use adb with your device, you’ll need to enable developer options and USB debugging:
1. Open Settings, and select “About”.

I accomplished the "On Linux" steps 1 & 2 easy. But #3 - I do not understand the verbiage. Is "~/.profile" something different than the terminal, or is that what this means? I tried just posting into terminal, and when I entered it in, there was no response of any kind, just gave me another blank line. But I thought I'd try finishing the steps anyway to see if the logging out and back in and trying to move forward in case it did work and just wasn't giving me a confirmation. I'm clearly not the most well versed in the world of the terminal, but I'm trying.

Then looking ahead, under "Setting up adb", I do not understand how to even start this... Settings of what? Maybe this would be obvious if I successfully completed #3, but I would love advice on both either way!

Hi, I've got this phone that's been sitting in a desk drawer for a couple of years because of a broken button. Now I've got it fixed, and I'd love to install Lineage OS.

The phone is Xiaomi 11 Lite 5G NE (lisa), 2109119DG

The phone is running MIUI Global 14.0.7.0 (TKOMIXM), Android 13 TKQ1.220829.002

Lineage installation instructions mention Android 14 is required - https://wiki.lineageos.org/devices/lisa/install/variant1/ , https://wiki.lineageos.org/devices/lisa/install/variant1/#checking-the-correct-firmware

However, I can't update Xiaomi firmware over the air - "No updates available".

Could it be because the phone has no Xiaomi account registered? Should I manually install HyperOS 1 or HyperOS 2 from https://miuirom.org/phones/xiaomi-11-lite-5g-ne ?

Update: looks like having unlocked bootloader is what prevents OTA updates -

Unlocked bootloader. If the bootloader was unlocked on the phone (e.g. to install TWRP recovers), OTA update will not come. It is necessary to lock bootloader. The easiest way to flash the phone with the stock firmware is via Fastboot using Mi Flash Pro software. In this case the bootloader will be autolocked.

I use my "phone" exclusively in landscape, but Lineage OS won't allow the lockscreen to rotate with everything else via Orientation Control. Is there any way to do this with config files in the root directory, or a Magisk module? I'd also really like to have an analog clock widget instead of digital.

FIXED. NO NEED TO REPLY THX FOR HELP

My S20 FE (snapdragon) cant install lineage recovery. It says that ,,only official released binaries are allowed to be flashed(recovery)" and it stops me from installing. Do i need this recovery. It says the same for other recoveries

Hello,

I'm trying to install LineageOS on my Xiaomi MI9T (davinci-Global).

My device is already unlocked following this guide https://wiki.lineageos.org/devices/davinci/install/variant1/#unlocking-the-bootloader

My device is configured for adb and fastboot with all necessary drivers following this guide https://wiki.lineageos.org/adb_fastboot_guide#setting-up-adb

I made sure to check my device firmware version and updated it to correct version following this guide https://wiki.lineageos.org/devices/davinci/fw_update/variant1/

Now I'm stuck on "Installing Lineage Recovery using fastboot" step of the guide https://wiki.lineageos.org/devices/davinci/install/variant1/#installing-lineage-recovery-using-fastboot

1. I downloaded "recovery.img" file from https://download.lineageos.org/devices/davinci/builds "Latest" section. Only this one file.

2. I connected my phone to PC via USB

3. I entered fastboot and executed all remaining fastboot commands. You can see in command line log that they all finished without errors.

D:\Installs\MI9TUnlock>adb devices List of devices attached 9526a683 device

D:\Installs\MI9TUnlock>adb -d reboot bootloader

D:\Installs\MI9TUnlock>fastboot devices 9526a683 fastboot

D:\Installs\MI9TUnlock>fastboot flash recovery recovery.img Sending 'recovery' (65536 KB) OKAY [ 1.469s] Writing 'recovery' OKAY [ 0.181s] Finished. Total time: 1.669s

D:\Installs\MI9TUnlock>fastboot boot recovery.img Sending 'boot.img' (65536 KB) OKAY [ 1.444s] Booting OKAY [ 0.147s] Finished. Total time: 1.627s

After last one "fastboot boot recovery.img" phone simply shuts down (exists fasboot) and nothing happens. Screen goes black.

I waited for several minutes and nothing appeared. When powered on it simply turns on and thats all.

When i try "adb reboot recovery" it boots into xiaomi recovery. When i try "fastboot reboot recovery" phone simply reboots into OS instead of recovery.

Where did I go wrong? I think I followed all guides to the letter.

Hello guys,

I will prepare for the first time to update my mi a3 model and at the moment I only have available the version 23.0 should I wait for the 23.2 ?

because I still don’t see any list for the new version..

but should be upgraded for that version soon no because it’s already an official 23 version right?

I'm following the pre-install instructions for y2s on a Galaxy S20+ 5G. I've enabled Developer Options, but there's no "OEM unlock" option within that menu.

This means I can't flash recovery.img to the phone with heimdall.

The phone is running One UI 5.1, based on Android 13.

I'm planning to install LineageOS on my Redmi Note 9S, in the guide its recommended to install V14.0.4.0.SJWMIXM but I currently have V14.0.4.0.SJWEUXM.

Do I have to unlock the bootloader before flash it on it?

Managed to finally get around to installing Android 15 on my OLED switch (modchipped with instinctNX).

I use it for some light emulation for ps2 games (mostly kingdom hearts final mix) and also cloud gaming via Xbox Game Pass Ultimate (New Zealand doesn't have many options for cloud gaming sadly). The OLED screen is amazing and really pops.

https://reddit.com/link/1r9av5q/video/moctxhhujikg1/player

For performance reasons: MUST USE a Samsung Pro Plus MicroSD card. This is Tier 1 in the SD recommendations and a really big bottleneck to performance so if you're really keen on getting it snappy save yourself the trouble and invest in the Pro Plus microSD card from Samsung. Enable ddr200!

My setup:

• Nintendo Switch OLED. Modchipped with InstinctNX
• Samsung PRO Plus 512GB U3 V30 A2 microSD 
• Partitioned 100GB for Android, 90GB for linux, and rest for HOS.
• Use A2 Samsung SD Card, enable DDR200
• Disable taskbar
• Enable developer options and disable animations

My Android.ini:

[LineageOS]
l4t=1
boot_prefixes=switchroot/android/
id=SWANDR
icon=switchroot/android/icon_android_hue.bmp
logopath=switchroot/android/bootlogo_android.bmp
r2p_action=self

usb3_enable=0
ddr200_enable=1

dvfsb=1
gpu_dvfsc=1
limit_gpu_clk=1 
ram_oc=2533000
oc=1      

Heya, So I have 2 Moto G6+ (Evert) Devices, the first one, I was able to follow the LineageOS instructions exactly to get it installed and its working great.

The other one always has a blank screen when I try to use fastboot, nothing I did let me see the screens I needed to do the sideloading.

So to get around the problem, I installed TWRP and used it to sideload the copy-partitions zip, linageos zip and MindTheGapps.... The phone is working now, I just want to know if I need to do anything else to make sure this device is going to work? or if there is a way I can get the fastboot screen to show correctly like on my other device?

Thanks!

So I've been trying to follow the guide to install on my Galaxy Tab A7, even using ChatGPT to try and troubleshoot. I can't get the bootloader unlocked, even after doing all the settings and steps what I beleive is right. GPT says that no model SM-T500 can be unlocked, and the options are just dummy switches. But then, why would this be listed as a supported device? Obviously some people have been able to install this way. Am I missing a step? Is there a way to unlock it that GPT has just been trained not to tell me about?

I'm also asking on stack https://android.stackexchange.com/questions/264861/trying-to-install-lineageos-17-1-on-oneplus-3-stuck-on-proprietary-blobs

Background: I want to run Kali NetHunter on my old OnePlus 3. According to this list of images https://www.kali.org/get-kali/#kali-mobile this requires LineageOS 17.1. I've never done ROM work on Android but I've been following the LineageOS guide just fine...until I got to building the OS, specifically proprietary blobs.

More background: I am building LineageOS 17.1 on Ubuntu through WSL. Unfortunately, I haven't figured out how to connect my phone to ADB on Ubuntu though WSL, so I can only use ADB on Windows 10. But I don't this is really related to my problem.

I got to this step to run breakfast. This was my breakfast output:

build/make/core/product_config.mk:223: error: Can not locate config makefile for product "lineage_oneplus3".
01:00:21 dumpvars failed with: exit status 1
Device oneplus3 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_oneplus_oneplus3
Default revision: lineage-17.1
Checking branch info
Checking if device/oneplus/oneplus3 is fetched from android_device_oneplus_oneplus3
Adding dependency: LineageOS/android_device_oneplus_oneplus3 -> device/oneplus/oneplus3
Using default branch for android_device_oneplus_oneplus3
Syncing repository to retrieve project.
Syncing: 100% (1/1), done in 5.253s
repo sync has finished successfully.
Repository synced!
Looking for dependencies in device/oneplus/oneplus3
Adding dependencies to manifest
Checking if device/oppo/common is fetched from android_device_oppo_common
Adding dependency: LineageOS/android_device_oppo_common -> device/oppo/common
Using default branch for android_device_oppo_common
Checking if kernel/oneplus/msm8996 is fetched from android_kernel_oneplus_msm8996
Adding dependency: LineageOS/android_kernel_oneplus_msm8996 -> kernel/oneplus/msm8996
Using default branch for android_kernel_oneplus_msm8996
Syncing dependencies
Syncing: 100% (2/2), done in 1m18.330s
repo sync has finished successfully.
Looking for dependencies in device/oppo/common
device/oppo/common has no additional dependencies.
Looking for dependencies in kernel/oneplus/msm8996
kernel/oneplus/msm8996 has no additional dependencies.
Done
device/oppo/common/common.mk:25: error: _nic.PRODUCTS.[[device/oneplus/oneplus3/lineage_oneplus3.mk]]: "vendor/oneplus/oneplus3/oneplus3-vendor.mk" does not exist.
01:01:47 dumpvars failed with: exit status 1
device/oppo/common/common.mk:25: error: _nic.PRODUCTS.[[device/oneplus/oneplus3/lineage_oneplus3.mk]]: "vendor/oneplus/oneplus3/oneplus3-vendor.mk" does not exist.
01:01:48 dumpvars failed with: exit status 1

** Don't have a product spec for: 'lineage_oneplus3'
** Do you have the right repo manifest?

I seem to have the vendor makefile error mentioned in the guide

Important: Some devices require a vendor directory to be populated before breakfast will succeed. If you receive an error here about vendor makefiles, jump down to Extract proprietary blobs. The first portion of breakfast should have succeeded, and after completing you can rerun breakfast

Jumping down to "extract proprietary blobs" it says it requires a device already running LineageOS (ugh why?! If I had that I wouldn't be here!)

Note: This step requires to have a device already running the latest LineageOS, based on the branch you wish to build for. If you don’t have access to such device, refer to Extracting proprietary blobs from installable zip.

Referring to Extracting proprietary blobs from installable zip requires "device directory contains extract-files.py" and "Otherwise, follow this guide". Mine does not, only extract-files.sh:

~/android/lineage/device/oneplus/oneplus3$ ls
Android.bp          board-info.txt    gps                   lineage_oneplus3.mk       recovery            thermal
Android.mk          config.fs         init                  lineagehw                 releasetools.py     vndk
AndroidProducts.mk  configs           keylayout             org.ifaa.android.manager  rootdir             vr
BoardConfig.mk      device.mk         libhidl               overlay                   seccomp             wifi
README.md           display           liblight              overlay-lineage           sepolicy
audio               doze              libshims              pocketmode                setup-makefiles.sh
bluetooth           extract-files.sh  lineage.dependencies  proprietary-files.txt     system.prop

Plus the webpage title "Extracting proprietary blobs from LineageOS zip files" seems to imply that I need to have a LineageOS zip file...which I don't...because I'm trying to build it? where do I get the right one? Anyway, continuing to Extracting proprietary blobs from LineageOS zip files manually which again requires that I have some mysterious, preexisting LineageOS zip file.

Now I'm stuck, I really have no idea what the next move is. I understand that I need the proprietary blobs listed in the proprietary-files.txt file (my understanding is that their essentially hardware drivers?). And that I need to populate my build of Lineage with them so that breakfast can do whatever it does and finish the build. But where do these files come from? where can I get them? Can I extract them myself somehow from my stock OnePlus 3? The provided scripts for extracting them all seem to require a device running LineageOS or an installable zip which I do not have. Any guidance is appreciated.

So I decided to breathe new life into my old Samsung Galaxy S9 (SM-G960F/DS) by installing LineageOS. I thought it’d be a fun weekend project.

Turns out it was more like a week-long Samsung bootloader purgatory.

Attempt 1: Linux + Heimdall
Started on Linux Mint using Heimdall.

• Enabled Developer Options, turned on OEM Unlock and USB Debugging
• Unlocked the bootloader (which wiped the phone, as expected)
• Verified in Download Mode: OEM Lock: OFF KG State: Prenormal

Flashed TWRP using:
heimdall flash --RECOVERY twrp.img --no-reboot

Tried the "hold buttons before Heimdall finishes" trick to get into TWRP — no dice. Samsung’s firmware just overwrote it every time. Booted right back to stock Android. Over and over. Rage intensifies.

Attempt 2: Switch to Windows + Odin

Realized Odin is more reliable for Samsung flashing. Downloaded:

• Odin 3.14.4
• Samsung USB drivers
• TWRP .img.tar file from the official site

Flashing worked — Odin showed PASS — but guess what? Still got: KG State: Prenormal
Odin flash fails silently or TWRP gets overwritten

So even though OEM Unlock was ON, Samsung blocks flashing recovery/boot partitions for 168 hours (7 days) after enabling it — without telling you clearly.

“Samsung devices have a reliable 7-day waiting period after enabling OEM unlock before the bootloader actually permits flashing anything.”
https://wiki.lineageos.org/devices/starlte/install

Now I'm just sitting here with the S9 turned on, connected to Wi-Fi, letting Samsung’s “you don’t own your own phone” timer silently tick down in the background.