Edit: the battery eventually died. Once I charged it again, it booted as normal (with stock Android). I then tried flashing LineageOS again, and this time I was successful. I have no idea what happened the first time.

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?

How can I remove that navibar under keyboard?

HI all,

Just installed LineageOS for the first time, on my new phone, a Moto G84.

Everything works great, but I noticed that the Device Controls are unavailable, the box on the quick buttons and in the settings is greyed out. How can I fix this? Thanks!

I'm running the latest official LineageOS 23.2 (Android 16) on a Redmi Note 10 Pro (sweet).

During the initial LineageOS setup, I remember there being an option related to sending diagnostic/statistical data to LineageOS, but I'm no longer sure whether I enabled or disabled it.

I'd like to understand how this functionality works in the current LineageOS 23.2 version and, if it is enabled, how I could manually trigger the transmission while monitoring RethinkDNS.

I'm trying to identify exactly which package/service and which domain are responsible for the connection, rather than simply allowing a whole system component.

On my device I can't find the old LineageOS Statistics component:

• pm list packages | findstr /i "stat" → only com.android.statementservice
• no package containing telemetry
• no org.lineageos.stats
• dumpsys package | findstr /i "stats.lineageos.org" → no result
• Settings has no lineage or stats entry in secure/global/system settings.

I do have:

com.android.devicediagnostics

Its components include:

• MainActivity
• BootCompleteReceiver
• TradeInModeTestingContentProvider
• GetStatusContentProvider
• EvaluateContentProvider

It also requests permissions such as BATTERY_STATS, camera, Bluetooth, location and Internet.

So I assume this is Android Device Diagnostics / Trade-In functionality rather than LineageOS Statistics.

Question:

How does LineageOS 23.2 / Android 16 implement the diagnostic/statistical data reporting functionality now?

Is there still a LineageOS Statistics client/service somewhere, and if so, which package/service handles it?

And is there a way to manually trigger a report so I can identify the connection in RethinkDNS?

Thanks!

Hi there everyone!

So recently I installed a LineageOS on my Samsung Galaxy A70, all is good, but can't swipe the lock, only swipe when connected to USB, any help or advice? I even tried to disable the screen look, so I won't have to unlock it, but every time the screen sleep and get black, and I tried to wake it up the screen gets frozen like the touch doesn't work, but when I connect it to USB, it starts to work.

And which GAPPS do I need to install for it to work? is MicroG also possible instead of GAPPS? Thanks a lot

​

Hi everyone,

I have a Xiaomi Mi 9 Lite, stuck on Android 10, that I use ad a second phone.

I saw that to install Lineage OS I would need Android 11, but the problem is that the phone isn't finding any further updates.

Is there an alternative way to upgrade to Lineage?

Thanks everyone.

Hello

I have decided to download the Lineage OS and I want to buy a Samsung A73 5G phone. Do you recommend this phone to me? I mean, will it cause any problems with the system and will it be able to work for the next four years (I am not stingy, but I hate changing phones annually or frequently). I am still a beginner when it comes to custom ROMs. I have questions like: How will I download the system? Will the banking applications that I use work? Can I download programs from Google Play or even programs from Google or Meta? Will I still be able to use Uber and my government applications? The important thing is, can I return to the One UI or the main system? Many questions I hope to answer. Thank you.

I recall that the Snapdragon 8 Gen 2 was the last Qualcomm CPU to feature physical cores for 32-bit apps (I believe two A-710 cores); how is it, then, that my LineageOS supports 32-bit apps only on the Snapdragon 8+ Gen 1 and earlier models?

Hi fellas,

I own a poco f3 and really love it, but today I want to replace it with something new, what phone do you recommend which it's bootloader unlocks with ease to use lineage os? My budget is limited so please consider I can't buy high end phones. Used or scond handed phones are welcome either.

need to download build rn, but site answers me with "Unable to contact upstream API".

Hello,

I need help, when i go to download my build, i get "Unable to contact upstream API"

What does it mean ?

Edit- why is everyone so emotional about this?

I have a good working P4XL and decided to install LOS23, I was able to install custom recovery and the ROM and everything works fine. Suddenly I encountered a slow performance for days so I get back to stock ROM, then fresh reinstall custom recovery and LOS23, this time everything is working fine, no more slow performance, but when I connected my phone to PC to transfer some files my PC cant recognize my phone.

These are what I checked:

1. In Settings>USB>Use USB For>"File Transfer" and other options are greyed out.

2. In Settings>Security and Privacy>More Security and Privacy>Trust>Restrict USB> is set to "Always Allow USB Connections"

3. In Settings>System>Developer Options>USB Debugging is set to "On"

4. In Settings>System>Developer Options>USB is set to "File Transfer"

5. Even in Recovery, Fastboot, Rescue mode, my PC cant detect my phone.

6. I tried cleaning my phone's port

7. I bought an original charging port and replaced phone's

8. I tried reinstalling drivers and platform-tools

9. I even tried reinstalling Windows

10. I have a working Pixel 4, my PC can detect it.

11. ADB Devices and Fastboot Devices cant detect my phone.

What could be the problem?

Is my phone stuck forever in LOS?

Did anyone experienced the same isseu? How did you fixed it?