Something I noticed recently is eBay has been blocked on devices running LineageOS, I have a few devices with LineageOS installed with G-apps and it will say in the Play store that it's only compatible with my other devices that are not running Lineage, anyone know why this is the case and are the devs working on something that will fix this issue?

Cześć wszystkim,

Jestem całkowicie zablokowany z moim **AYN Odin 3 (Snapdragon 8 Elite)** i bardzo potrzebuję pomocy lub nowszego pakietu oprogramowania. Moje urządzenie jest obecnie uwięzione w pętli między Fastboot/Bootloader a Trybem Pobierania Awaryjnego (EDL 9008).

Oto dokładna historia tego, co się stało, jakich narzędzi użyłem i co już próbowałem przez ostatnie 24 godziny:

**1. Pliki i oprogramowanie użyte:**

* Użyłem **QFIL (v2.0.3.5)** jako Administrator. * Pakiet oprogramowania, którego używam, to `Odin3_20251206.7z` (pobrany z linku Google Drive znajdującego się w starszych wątkach Reddit). * Plik programisty użyty to `xbl_s_devprg_ns.melf` , a typ pamięci jest poprawnie ustawiony na **UFS** (cel ma układ Kioxia UFS).

**2. Początkowy problem z akumulatorem/ładowaniem:**

* Podczas pierwszych prób ciągle dostawałem `Sahara Error function: port_connect:99 Failed to open com port handle` lub błędy zapisu Firehose. * Przez Fastboot CMD potwierdziłem, że akumulator był krytycznie niski (`battery-voltage: 3475mV`). Fastboot zgłaszał `FAILED (remote: 'Warning: battery's capacity is very low')`. * Udało mi się wykonać wymuszone wyłączenie sprzętowe i ładowałem urządzenie przez wiele godzin na wolnej ładowarce ściennej. Napięcie akumulatora osiągnęło pomyślnie **3609mV**, co obejście zabezpieczeń akumulatora Qualcomm.

**3. Wyniki flashu QFIL (sukces, ale brak uruchomienia):**

* Przy naładowanym akumulatorze QFIL teraz pomyślnie flashuje oprogramowanie **w 100% za każdym razem**. * Log kończy się z `{All Finished Successfully}` oraz `Download Succeed`. * **Problem:** Tuż po flashu urządzenie albo jest kompletnie martwe/czarne (utknięte w pętli Hard EDL 9008 aż zmuszę do 30-sekundowego twardego resetu z Vol Down + Power) LUB wibruje raz, pokazuje logo AYN przez 5-6 cykli pętli, a następnie **z powrotem uruchamia się w trybie Bootloader / Fastboot**. * Całkowicie odmawia uruchomienia systemu Android lub trybu odzyskiwania. Wybieranie "Tryb odzyskiwania" za pomocą klawiszy sprzętowych po prostu rebootuje go z powrotem do Bootloadera.

**4. Konfiguracje, które już próbowałem:**

* Flashowanie z `Active Boot Partition: 0` (Slot A) oraz `Active Boot Partition: 1` (Slot B). Na slocie 1 uzyskuję 5-6 cykli logo zanim nie uda mi się dm-verity i wraca do bootloadera. * Flashowanie z włączonym `Erase All Before Download` w konfiguracji Firehose. * Używając *Menedżera partycji* w QFIL, aby ręcznie `Erase` zarówno `userdata` jak i `misc` partycje, aby usunąć wszelkie uszkodzone flagi szyfrowania. QFIL informuje o pomyślnym usunięciu, ale pętla uruchamiająca pozostaje. * Próba komend fastboot (`fastboot -w`, `fastboot erase userdata`, `fastboot format:ext4 userdata`). Wszystkie zwracają `FAILED (remote: 'unknown command')` , ponieważ bootloader Odin 3 jest zablokowany i mocno ograniczony.

**Moje podsumowanie:**
Sprzęt wydaje się być w doskonałej kondycji. Ładowanie działa, reaguje na kombinacje przycisków, wchodzi w EDL/Fastboot na żądanie i bezbłędnie akceptuje surowe dane przez Firehose. Mocno podejrzewam, że pakiet oprogramowania `Odin3_20251206` ma starszy lub testowy podpis wersji, który nie pasuje do rewizji płyty głównej mojego urządzenia, co powoduje **dm-verity / Bezpieczne uruchamianie** odrzuca go.

Czy ktoś ma **nowszy pakiet oprogramowania QFIL do rozblokowania** dla Odina 3? Czy istnieje jakiś ukryty sposób, aby zmusić bootloader do zaufania tej wersji po czystym reflaszu?

Każda pomoc będzie bardzo cenna. Dziękuję!

Hi all,

I'm so happy with Lineage. Finally got it successfully installed on my new motorola phone after a brutal 8 day wait.

One thing i'm missing is the support for LHDC (including LHDC 5) which was available natively on stock A15, but is not available at all on Lineage. Google AI claims that since my phone has support for LHDC built in, there's a good chance the maintainer extracted and included them with the build, but alas, this is not the case.

I did read somewhere that it is included with A17. Will this codec be included natively with all Lineage 24 builds? Thanks!

Also: is there any way to get the date on the status bar next to the time? I used to do this through AOSP mods, but can't find any working way to do this now. And it's probably a very trivial thing to do if you know how to do it, but I do not.

Is anybody getting reminders of upcoming alarms ? It's annoying AF. I mean, the alarm IS the reminder.

Does anybody know where I can turn these off ?

Yesterday I was watching some videos about custom ROMs and LineageOS caught my attention.

I have some experience formatting computers and have been using Linux daily for over a year, and I'm curious to try an open-source ROM on my phone, but I believe that installing a custom ROM on a phone isn't the same as installing a Linux system on a PC.

Most importantly, I think it's worth noting that I currently only have access to one phone, which means that permanently damaging it would be a big problem.

Do you think it's worth trying to see if the custom ROM works for me?

Hello, I have a Xiaomi Mi A1 (Tissot) and I want to install Lineage on it. Claude recommends installing version 18 (Android 11) and not the latest versions because they are resource-intensive on Tissot. He also says that after version 18 there are unresolved bugs for this phone. What do you think? Where can I download the official version 18, since I can't find it on the Lineage website? Thank you very much.

Hello! I was trying to install LineageOS on my Oneplus Pad 2 (OPD2403) and was following the official wiki (https://wiki.lineageos.org/devices/caihong/install/variant2/).

I installed the latest stock os version based on android 16 (OPD2403_16.0.5.702) as mentioned in the wiki. I followed every step and unlocked the bootloader, but when I tried to flash the images, I encountered this error:

$ fastboot flash boot boot.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 201326592).
Sending 'boot' (196608 KB) FAILED (remote: 'Requested download size is more than max allowed
')
fastboot: error: Command failed

Has anyone encountered this issue or know what might be wrong? Any help is greatly appreciated. Thanks in advance!

Trying to get Lineage working alongside ArmadaOS on my Odin 2 Portal. Seems like the install process would leave the Linux partition alone for the most part.

Update:

If you already have Rocknix ABL, skip to the step where you flash the recovery image, and continue from there.

To enter fast boot you need to enter recovery mode from Rocknix, and then from there you can enter fast boot to flash a new recovery. Then reboot to the Rocknix ABL and enter recovery mode again and you’ll be in the Lineage Recovery OS.

I have a lineageOS install with android 16, I want to reflash the rom but this is giving me issues:

https://wiki.lineageos.org/devices/a21s/install/

If your device is currently using a newer or older version than the required version, please up- or downgrade to the required version before proceeding with your LineageOS installation.

The required version is Android 12, which may be lower than the LineageOS version you are about to install - this is not an error! If there are multiple updates of that version (e.g. security updates), make sure to use the latest!

If you need to upgrade or downgrade your device, please search online for guides. We are unable to provide specific instructions here and on our support platforms.

I can't find any info on how to downgrade online. The warning is also a little confusing (talks about firmware but then mentions android version? The rest of the second paragraph also makes no sense). Can I just ignore that warning and try to flash it anyway?

​Hi everyone,

​I am attempting to flash LineageOS (lineage-23.2-20260902-nightly-a71-signed.zip) onto my Samsung Galaxy A71 (a71). Lineage Recovery is installed and running fine on the phone, but I am stuck at the adb sideload step because no host device seems to establish a connection with the phone while it's in recovery mode.

​Setup & Hardware:

​Target Device: Samsung Galaxy A71 (a71) in Lineage Recovery (Apply update -> Apply from ADB).

​Host Attempts: Linux and Windows 11 PC, as well as a Samsung Galaxy A55 5G via USB-C to USB-C cable.

Hi Reddit,

I built a Linux shell script that clones LineageOS applications so they install alongside the default system ones. The clone gets its own package ID, and you can personalize its name and icon and sign it with your own key or the public Android debug key. The script runs from a local page in your default browser and works on any distribution and desktop environment.

Sixteen apps are currently supported :

• System Essentials : Dialer (phone), Contacts, Messaging, DeskClock, ExactCalculator.
• Media & Utility : Jelly (browser), Aperture (camera), Twelve (music player), Glimpse (gallery), Gallery2.
• Tools & Settings : Recorder, Camelot (PDF viewer), Etar (calendar), AudioFX (equaliser), Backgrounds (wallpapers), Profiles.

This project is published under GPL-3.0: https://codeberg.org/213YaZ786/lineage-app-cloner/

Feel free to use the repository's issue tracker to submit bug reports or to share your thoughts right here in this thread.

Peace be upon him who believes.

I am trying my best to flash LineageOS onto my Samsung Galaxy Tab E. However, after I flashed the recovery image (which I obtained from Samloader RS), and after the PC Command Prompt shows the tablet has been flashed successfully, it stays on the, 'downloading.... do not turn off target' screen. After waiting for over 20 minutes just to be safe, I tried turning it off and manually booting into recovery*........and nothing. It stays on that screen. I cannot turn it off, and I obviously nothing happens if I try to boot into from recovery with it still on.

What am I missing? I am pulling out what little hair I have left! Help!

*These are the instructions I have been using to download LineageOS. Up until I got stuck, everything was going smoothly.

Tengo un Xiaomi Redmi Note 10S, cambie la ROM original por LineageOS 23.2 (Rosemary).

El problema: no puedo mover o copiar archivos del almacenamiento interno a las Tarjeta SD, pero si puedo mover archivos desde la SD al almacenamiento interno.

Por favor ayuda.

I love my Sony Xperia 1 III so a few months back I installed LineageOS on it but since I wasn't satisfied with the lack of GPay I went back to stock but everything was working perfectly on lineageos. Recently since I got a pixel 11 pro I decided to install back lineages on my Xperia so I could get a increase in battery life so I go down the process again but quickly discover that although my simcard is detected I could not connect to the network, no sms, call or data and when going though service menu I saw that it would not register on the network. I tried another simcard from another carrier and the same exact issue so after a bit of research I was seeing some people had a hardware problem so I decided to relock and check but sure enough all functions are working on stock rom. not sure what's happening I know ive made sure to install it right and followed instructions to a T. Ive installed it over and over a couple of times and tried all 3 versions on the site, sadly the last working version from may I am missing the main signed build but have the .img files so I can't reinstall it to test if the version is the one with the issues. not sure if anyone has had something like this happen but it would be nice for some help on it. on a happy note I got my new battery installed a few minutes ago and along with it a new back cover and clear case, makes me sad to not use it as much especially ever since I found out there is a way to subdue the beast that is the 888+

The phone is Razer phone 2 Aura.

The bootloader is unlocked. Device is detected in fastboot.

I followed the official guidelines. I managed to get to lineage OS recovery and also send the lineage OS. It is successfully sent to my device. 2/2 However on the time of booting for the first time, it just goes to the black screen with Android and just doesn't boot into Lineage.

I've traced me steps back. all the builds are correctly installed and even tried with multiple different cables. All goes smoothly until the moment of truth.

Any suggestions or advice gladly welcome.

Edit: I did discover some kinks. Like after sending the boot.img recovery file, to get to recovery unless I disconnect the phone from the laptop, it doesn't get to Lineage recovery. So similarly, are there some things I'm missing that's preventing the final step from happening. TIA

Buenas como les va? Quería saber cómo solucionar esto que creo es un error cuando juego con mi batería al 100% y con 120hz por ejemplo brawl stars va muy fluido y sin nada de lag también si lo uso conectado al cargador pero cuando llega a 60% empiezo a tener mucho bajones de fps y es muy molesto y ojo no se sobre calienta ni nada cuando lo uso cargando teniendo ese porcentaje bajo va sin nada de bajones de fps

Hi all,

I'm trying to install LineageOS on my Motorola Moto E7 Plus (XT2081-1, codename "guam") and I'm stuck at the recovery-boot step. Hoping someone who's dealt with this specific device/firmware can point me in the right direction.

What I've done so far (all successful, no errors):

1. Unlocked the bootloader via the official Motorola unlock site — confirmed unlocked (yellow "bootloader is unlocked" warning shows on every boot, securestate: flashing_unlocked).
2. Flashed dtbo.img: fastboot flash dtbo dtbo.img → OKAY.
3. Downloaded recovery.img fresh from download.lineageos.org/guam (~100MB, matches the official mirror size).
4. Flashed recovery to both slots:

​

   fastboot flash recovery recovery.img   → wrote to recovery_b, OKAY
   fastboot flash recovery_a recovery.img → OKAY
   fastboot flash recovery_b recovery.img → OKAY

1. Tried booting into recovery multiple ways:
   • fastboot reboot recovery
   • fastboot boot recovery.img (temporary boot, no flash)
   • Manually navigating the bootloader menu with volume keys to "Recovery mode" and confirming with Power

Result every single time: device shows the yellow "bootloader is unlocked" warning screen → Motorola boot logo → falls straight back into the stock Android system. It never shows the LineageOS recovery logo/menu.

Troubleshooting already ruled out:

• Not a bad USB cable/port (tried multiple).
• Not a corrupted download (re-downloaded from scratch, file size matches official mirror exactly).
• Not a slot mismatch (flashed recovery to both recovery_a and recovery_b explicitly).

Relevant fastboot getvar all output:

current-slot: b
version-bootloader: MBM-3.0-guam_retail-90e6a6b9642-220629
product: guam
board: guam
secure: yes
hwrev: PVT
radio: LATAM
storage-type: eMMC
securestate: flashing_unlocked
verity-state: enforcing (0)
iswarrantyvoid: yes
sku: XT2081-1
carrier_sku: XT2081-1
ro.carrier: retbr
ro.build.fingerprint: motorola/guam_retail/guam:10/QPZS3/0.30-Q3-38-69-12/916393:user/release-keys
version-baseband: HA10_11.167.01.82R GUAM_LATAMDSDS_CUST
slot-count: 2
slot-successful:_a: no
slot-successful:_b: no
slot-unbootable:_a: yes
slot-unbootable:_b: no
slot-retry-count:_a: 0
slot-retry-count:_b: 4
frp-state: no protection (0)

My question: Is there a known quirk with the LATAM/retbr firmware variant of guam that prevents booting into a custom recovery even with a correctly flashed image? Or does verity-state: enforcing need to be dealt with first (e.g. flashing a matching vbmeta.img with --disable-verity --disable-verification) before the device will accept booting an unsigned recovery?

Any pointers from someone who's flashed this exact model (XT2081-1) successfully would be hugely appreciated. Happy to provide more logs if useful.

Hi, I have flashed LineageOS on other devices but I am stuck in a loop at stage 5 with this one. Following the instructions on a Mac, I use the command to flash recovery but when I select recovery mode it shows me the nothing logo, then the unlocked boot loader warning, then goes back to bootloader/ fastboot mode. I have tried all 3 available recovery images. I’ve also tried using the shortcut to restart into recovery but this just does the same thing (loads to bootloader). Any ideas?

I have LineageOS 23.2 on pixel7a. My hardware sim slot stopped detecting 4g networks after I removed a eseim from another carrier. Due to this I cannot use data with sim1. Sim works fine on other phones.

Any ideas?

Thanks

83% of LineageOS installations are unofficial, according to stats.lineageos.org

I'm curious about whether this is based on a technical reason or the original maintainer just doesn't want to keep supporting them, in which case I may try to take a look into it and see if I can continue it.

So since lineageOS is built off of android if android blanket removes OEM unlocking from a device like the pixel 7 but its already running an unlocked bootloader and lineageos would that mean that next time lineageOS updates it'd also have it removed or?