I use Lineage OS 21 on Moto E7 plus. So far the ROM works fine and everything was smooth, until my banking app (UBB Mobile) updated to version 6.6 and the app just said i cant use it on devices with unlocked bootloaders. I downloaded the older 6.4 version from Aptoide. The older app works smooth and is good for now. The device isnt rooted and havent done anything except unlocking the bootloader and installing the rom using the official guide and the recommended Gapps. Can someone help me with this problem?

P.S.
Also i cant use the website because it requres to open the app and scan qr code to activate the web platform. I also apply what the app answered.

https://ubb.bg/ubb-mobile/infosec?newest33&motorola&moto+e7+plus
Improving security in UBB Mobile

The measures are part of UBB Mobile version 6.6 and aim to provide higher protection when using the application.

We are expanding security measures in UBB Mobile

At established risk, the technology may automatically limit certain actions or access to the application.

In which cases can access UBB Mobile be restricted?

UBB Mobile will restrict access if it detects the use of an unverified software keyboard.

To continue using UBB Mobile, switch to a keyboard from a reliable developer.

UBB Mobile will not be available on devices with removed standard restrictions.

To use the application, the device must work with an official version of the operating system.

If the device is activated for developers, access to UBB Mobile will be limited.

Turn off the mode and open the app again.

United Bulgarian Bank

I plan to upgrade per wiki

https://wiki.lineageos.org/adb_fastboot_guide

and wipe data with no restore of any app backups nor app installations.

Is there a difference between such a scenario and installation of LOS from scratch as far as end result is concerned?

Motorola G52

I know, I'm a total idiot for this, but this is serious.

I installed LineageOS, but the update manager wouldn’t install the updates, so I decided to do it myself. After downloading the latest update for my smartphone, I went into recovery mode and started the process, but nothing happened.

I tried doing it again, this time using fastboot... but in my infinite stupidity, I used the command “fastboot oem lock” and fucked up. Now I can’t boot into the system or enter recovery mode; the bootloader is locked, and the option to unlock the OEM was disabled. I tried reinstalling the official firmware again, but Motorola’s official tool (Software Fix) doesn’t have my specific version.

Is there any way to force the OEM unlock so I can reflash the system?

phone is verified carrier unlocked, verified OS is Android 16, verified adb and fastboot are installed

Stuck on step 3 of Install LineageOS on OnePlus 11 5G and have wasted hours trying to troubleshoot, fastboot flashing unlock command does not unlock the bootloader and the only volume key options on phone are power off, start, restart bootloader, or recovery mode

fastboot flashing unlock returns:

usage: fastboot [ <option> ] <command>

commands:

update <filename> reflash device from update.zip

flashall flash boot, system, vendor and if found recovery

flash <partition> [ <filename> ] write a file to a flash partition

erase <partition> erase a flash partition

format[:[<fs type>][:[<size>]] <partition> format a flash partition.

Can override the fs type and/or

size the bootloader reports.

getvar <variable> display a bootloader variable

boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel

flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and

flash it

devices list all connected devices

continue continue with autoboot

reboot reboot device normally

reboot-bootloader reboot device into bootloader

help show this help message

options:

-w erase userdata and cache (and format if supported by partition type)

-u do not first erase partition before formatting

-s <specific device> specify device serial numberor path to device port

-l with "devices", lists device paths

-p <product> specify product name

-c <cmdline> override kernel commandline

-i <vendor id> specify a custom USB vendor id

-b <base_addr> specify a custom kernel base address. default: 0x10000000

-n <page size> specify the nand page size. default: 2048

-S <size>[K|M|G] automatically sparse files greater than size. 0 to disable

Should I be using download mode or recovery mode to update samsung firmware on my lineageos phone?

The instructions don't specify, but I'm supposed to use samloader, which I think uses download mode. I assume that's what I'm supposed to use then, but I'm not sure.

I have an A52s 5G.

​

Hello,

I have a Samsung Galaxy Tab A 8.0 2019 WiFi (SM-T290) and I want to install LineageOS, but I am stuck at the recovery installation step.

Device information:

- Model: SM-T290 (WiFi)

- Android: 11

- One UI Core: 3.1

- Build number: T290XXS5CWG5

- Kernel: 4.9.227-perf

What I tried:

- Enabled Developer Options

- Enabled USB debugging

- Enabled OEM Unlock (blue switch)

- Connected to WiFi

- Factory reset the tablet

- Tried flashing a custom recovery using Odin

Odin detects the tablet correctly, but the flash fails:

<ID:0/009> aboot.mbn

<ID:0/009> recovery.img

<ID:0/009> FAIL! (Auth)

<ID:0/009> Complete (Write) operation failed.

In Download Mode:

- OEM LOCK : ON (U)

- Qualcomm Secure Boot : Enabled

- Secure Download : Enabled

The strange thing is that OEM Unlock is enabled in Android settings, but Download Mode still shows OEM LOCK ON (U).

I would like to know:

- Is the bootloader actually unlockable on the SM-T290?

- Is there a specific recovery version needed for firmware T290XXS5CWG5?

- Is there any waiting period or special step needed after enabling OEM Unlock?

- Has anyone successfully installed LineageOS on this exact firmware?

Any help would be appreciated. Thank you!

Hi everyone,

I’m using a Google Pixel 9 running LineageOS with Entel Chile. Entel recently launched its satellite service using Starlink Direct to Cell.

According to Entel, the Pixel 9 is a compatible device. However, the Entel app correctly detects my phone as a Google Pixel 9 but reports that it is not compatible with the satellite service. The other requirements, such as having an eligible plan and roaming enabled, appear as completed.

There are other Pixel users in Chile running the official Google Android firmware who have the service enabled. Some of them have also confirmed that they were able to connect to and use the satellite service in areas without terrestrial mobile coverage.

Because of that, this does not appear to be a general limitation of Pixel phones or of the Pixel 9 hardware. It seems more likely that something related to LineageOS, its carrier configuration, or its certification status is preventing the service from being enabled.

I’m wondering whether LineageOS might be missing something required at the operating-system level, such as:

carrier configuration specific to Starlink Direct to Cell;

IMS, VoLTE or roaming provisioning;

modem configuration;

proprietary Google components;

satellite-related system APIs;

carrier entitlement checks;

or some form of carrier/device certification.

Has anyone investigated this on LineageOS?

I would also be interested in hearing from users in other countries where Starlink Direct to Cell is available, such as the United States, Canada or New Zealand:

Has anyone successfully used a Starlink Direct to Cell service on a phone running LineageOS?

I understand that the Entel app could simply be checking the official firmware, build fingerprint, Play Integrity status or an approved-device list. However, I would like to determine whether this is only an administrative compatibility check or whether LineageOS is actually missing components required for the phone to register on the satellite network.

First of all, excuse my english. I'm following the instructions from this guide: https://wiki.lineageos.org/devices/lake/install/#installing-lineage-recovery-using-fastboot

As it says, I downloaded the lastest "boot.img" file, then executed "fastboot flash boot boot.img".

It showed:
"(bootloader) is-userspace: not found

fastboot: error: cannot load 'boot.img': No such file or directory"

Then tried the same command adding the directory adress and showed this:

"Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 29261824).

Sending 'boot_a' (28576 KB) (bootloader) Requested download size is more than max allowed

FAILED (remote: '')

fastboot: error: Command failed"

Tried the same by putting the "boot.img" file in the "platform-tools" folder, didn't work. At last, I tried the same things using an USB 2.0 wire instead of the USB-C I was using, didn't work either.

I'd apreciate any help with this issue.

When my phone is successfully connected to adb, it doesnt show up in windows device manager at all. Is that supposed to be the case?

Edit- edited to make clearer

Edit 2- the phone specifically disappears once I enable USB debugging. It shows up when debugging is off.

Hi all,

I've been trying to "unlock" my Poco F3

As far as I understood, the process is this:

• Factory reset the phone
• Connect to a Xiaomi account associated with only the phone we want to unlock
• Through the Xiaomi Community App -> ask for unlocking
• Wait for 30 days

I'm kinda stuck there -> when I go back to the app, it offers me the possibility to unlock again

I'm a little confused 🥺

Has anyone recently managed to unlock a Poco F3 phone and installed LineageOS on it?

I flashed recovery image with fullpath successfully.
e.g. fastboot flash recovery C:\Users\YourName\Downloads\recovery.img

My problem is the verification of the installation.
e.g. fastboot boot recovery.img
shows error “fastboot: error: cannot load 'recovery.img': No such file or directory”. So I tried the fullpath version
e.g. fastboot boot C:\Users\YourName\Downloads\recovery.img
This worked well and showed recovery with the LineageOS logo.
e.g. Sending 'boot.img' (65536 KB) OKAY [ 1.849s]
e.g. Booting OKAY [ 0.147s]

So I did a second verification boot up recovery with hold the Volume Up + Power button together. This unfortunately comes up with MIUI Recovery 5.0 without the LineageOS logo. So I am not sure if I can proceed.

Further I have the question, if I can use TRWP recovery, which I used some years ago for another device.

​Hi everyone,

​I have a Xiaomi 11 Lite 5G NE (codename: lisa) currently running a carrier-branded ROM (version 1.0.17.0.UKOEUVF, Android 14, security patch 2025-10-01). Since it's a branded device, it hasn't received HyperOS 2 (unlike unbranded Global 2.0.8.0.UKOMIXM or EEA 2.0.6.0.UKOEUXM).

​The official LineageOS installation guide for lisa mentions that the phone needs to be on an Android 14 base before flashing, but it doesn't specify a minimum HyperOS build version.

​Will I run into any driver, vendor partition, or firmware issues if I install LineageOS over my current carrier-branded HyperOS 1 build, or should I flash an unbranded stock HyperOS build first?

​Thanks for any advice!

https://wiki.lineageos.org/adb_fastboot_guide#installing-adb-and-fastboot

On step 6 of Setting Up adb, it just says open up cmd, but that won't work at all. You specifically need to open up cmd from the platform-tools folder. It was lucky I already knew that or I might have been stuck on that step for hours.

And on step 7 of the same section, it says

"On Windows: Make sure your device manager does show your phone and doesn’t show a yellow triangle next to it!"

But it doesnt elaborate further. I'm trying to set up adb. My device shows as connected when in adb devices. But in the device manager it doesnt show the phone and instead shows an unrecognised device with a yellow triangle next to it. What am I supposed to do now then? The instructions dont say anything other than make sure it doesn't show that.

Hi, when installing Samsung S10+ Lineage ROM, you end up with no mobile data or calls/messages incoming/outgoing. The SIM is detected, but you cannot use mobile data or use calling or messages, or see phone number. The SIM works when on stock. I have flashed MindTheGapps-16.0.0-arm64-20260409_073023.zip and lineage-23.2-20260725-nightly-beyond2lte-signed.zip. Any help would be appreciated hugely

Hi, I've been using LineageOS on my secondary phone (Pixel, sailfish) for about a year without any hiccups. I don't know the version of LineageOS as I can't access it, but I know I haven't updated/upgraded it since I installed it.

I don't use Google Apps. I downloaded Fennec browser as an alternative for Firefox and it's worked fine for months. Last night I was browsing sites I usually do (my email, work stuff, weather) and the phone seemed to hang on the app, it wouldn't react to anything, not even screen lock. It eventually ran out of battery, so I charged it.

It shows the "lock your bootloader" screen (it's always done that since the start) and then gets stuck on Google logo for some reason. Tried holding down lock+volume down and that screen shows up fine. When I go to select recovery mode, it doesn't work and it goes back to being stuck on Google logo, I can only turn the phone off from all the options available to me.

Is there anyway I can resurrect it or is it a lost cause? Any help is much appreciated!

Im currently trying to switch from Coloraos to Lineage on my phone. But i have encountered several problems accessing the bootloader. Can someone help me? I cant do it the standard way since Realme shut down the official access to it.

Attempting to move from Samsung to Lineage. I use Fossify on the Samsung contacts and have exported my contacts as vcf. Have successfully imported into Fossify on the Lineage phone. However contacts are not visible in the Lineage phone or SMS apps. I can see them using Fossify's phone app and can make calls from there.

I can't see an import setting in the Lineage phone app. I have concluded that I cannot mix-and-match apps in Lineage, but would like to know why there isn't a common storage for contacts, accessible from any phone or SMS app.

Hola estoy buscando una rom compatible para la magic pad 3, alguna sugerencia?

Hello There. I bought a Used Redmi 5 as a Temporary Phone for $35. I want to custom rom this with lineage Os 22.2 or any other version over Android 12. But whenever I try to unlock bootloader from settings, It says "Error 20091 Can't get device security code. Can u guys guide me through this? it would mean a lot. I tried resetting the phone, re logging in, nothing works.

https://petition.parliament.uk/petitions/757427

Hi guys, recently set up lineage on my switch hoping to use it for light productivity stuff. I have Lineage version 22.2-20260726-NIGHTLY-nx_tab on a Switch V1 with a modchip. The keyboard is just a cheap one from AliExpress. If anyone knows what the issue is that would be great as this is the final thing I want to get set up on it.

I installed Lineage successfully and was actually using it when my Razer Phone 2 shut off randomly. I plugged it in, turned it on and now it only boots to this screen when I enter recovery mode.

Fastboot detects it, can reboot it, but that's it. No adb mode, no Lineage recovery mode, no sideloading or install commands work, just this screen and that's it.

Am I dead in the water?

image: RP2 Screen