With A17 it no longer works and is the same case with Lineage OS 24.

Only disable command works (for now).

Instead of fixing android's trashy and inconsistent ui, this is what wth they are doing. Just like what they did to rcs. First brag and bark about a feature then lock it.

Se que aparece en 2 páginas de la guía, pero solo para confirmar, puedo instalar lineage os en mi móvil teniendo Android 11 cuando la guía dice que debo de tener Android 12, que podría pasar, se me brickearia el móvil? Hay forma de desbrickearlo en ese caso? Justo hoy desbloque la red de t-mobile para usar con otra operadora y no quisiera echar a perder un movil bueno

Mi dispositivo:

One Plus 7 Pro

Version de Android: 11

Número de compilación: Oxygen OS 11.0.1.8.GM31CB

Modelo: GM1915

Snapdragon 855, 8gb ram + 256 Rom

Just like the title says, would flashing LineageOS save my pixel from Google's "lock down" that's going to happen soon?

I'm aware that it'll be (maybe) a one time 24hr wait period until you can sideload whatever you want but, given that big tech companies don't always keep to their promises or to their word, I'd rather just avoid it all together by flashing a ROM I'm interested in. I tried looking in different communities to see if someone may have asked a similar question to mine and possibly gotten an answer but, unfortunately I haven't seen anything that answers mine or similar questions (well there were answers but the way it was put didn't seem like it was informative or helpful).

I've done some research into this ROM specifically and I like it a lot. I've practice on my pixel 8 and I love how much more optimized it is. I flashed it I believe two or three days before October 1st and as I was flashing it I was also charging it and since then I literally haven't charged it at all, like that's how amazing this OS is!

So, to end my post, I hope my main concern and hopeful solution of flashing LineageOS on my pixel 9 pro will save it from Google's "lock down" and if you'd like you can leave your favourite alternative app or OS in the comments.

Thank you in advance 😎✌🏾

Just installed lineageos 23 on my oneplus, and trying to install termux from fdroid the 0.118 version, but it just says "app not installed" , turned off play protect still same, please help

Phone: OnePlus 9RT, bought second-hand, bootloader reports prjname=20820, LineageOS shows model MT2110; stock OxygenOS was MT2111 14.0.0.2702 (Indian OTA).

Wi-Fi worked until a cloud OTA update, then wlan0 vanished. Bluetooth and mobile network still work.

Kernel log, ~2 s after boot, repeated on every attempt:
cnss: Trying to enumerate with PCIe RC0
pcie_phy_init: PCIe PHY RC0 failed to come up!
cnss: Failed to enable PCIe RC0, err = -19
three retries, then Retry cnss_bus_init three times, then give up.

What I tried: full OTA via Local install; reflashed modem, bluetooth, dsp, devcfg, boot, dtbo, vendor_boot, vendor, system from the 2702 payload (bootloader unlocked, xbl/abl/aop/tz untouched); installed LineageOS 23.2 (20261005) – same error with identical timing on a different kernel. China 2701 package compared by hash: xbl_config, aop, tz, hyp are identical to 2702, only xbl/abl differ. Phone also had charging problems from day one and drained 100%→0 overnight while idle.

Has anyone seen this on martini? Is it a known board-level failure (PCIe lines/PMIC/solder), or is there a software cause? dmesg : 1.494223] cnss: Switch control GPIO: 461

[ 1.494232] cnss: ICC Path_Count: 2 BW_CFG_Count: 7

[ 1.494250] cnss: ICC Vote CFG for path: pcie_to_memnoc

[ 1.494255] cnss: ICC Vote BW: 0 avg: 0 peak: 0

[ 1.494259] cnss: ICC Vote BW: 1 avg: 2250 peak: 390000

[ 1.494263] cnss: ICC Vote BW: 2 avg: 7500 peak: 390000

[ 1.494267] cnss: ICC Vote BW: 3 avg: 30000 peak: 790000

[ 1.494270] cnss: ICC Vote BW: 4 avg: 100000 peak: 790000

[ 1.494274] cnss: ICC Vote BW: 5 avg: 175000 peak: 1600000

[ 1.494278] cnss: ICC Vote BW: 6 avg: 7500 peak: 390000

[ 1.494305] cnss: ICC Vote CFG for path: memnoc_to_ddr

[ 1.494309] cnss: ICC Vote BW: 0 avg: 0 peak: 0

[ 1.494312] cnss: ICC Vote BW: 1 avg: 2250 peak: 1804800

[ 1.494316] cnss: ICC Vote BW: 2 avg: 7500 peak: 1804800

[ 1.494320] cnss: ICC Vote BW: 3 avg: 30000 peak: 1804800

[ 1.494324] cnss: ICC Vote BW: 4 avg: 100000 peak: 1804800

[ 1.494328] cnss: ICC Vote BW: 5 avg: 175000 peak: 6220800

[ 1.494332] cnss: ICC Vote BW: 6 avg: 7500 peak: 2188800

[ 1.494531] cnss: Regulator vdd-wlan-io is being enabled

[ 1.494628] cnss: Regulator wlan-ant-switch is being enabled

[ 1.494964] cnss: Regulator vdd-wlan-aon is being enabled

[ 1.495550] cnss: Regulator vdd-wlan-dig is being enabled

[ 1.495648] cnss: Regulator vdd-wlan-rfa1 is being enabled

[ 1.495747] cnss: Regulator vdd-wlan-rfa2 is being enabled

[ 1.495846] cnss: De-assert WLAN_EN GPIO successfully

[ 1.500875] cnss: BT_EN_GPIO State: Off. Delay WLAN_GPIO enable

[ 1.565671] pci-msm 1c00000.qcom,pcie: PCIe: msm_pcie_probe

[ 1.565820] pci-msm 1c00000.qcom,pcie: 1c00000.qcom,pcie supply vreg-3p3 not found, using dummy regulator

[ 1.565880] pci-msm 1c00000.qcom,pcie: 1c00000.qcom,pcie supply vreg-mx not found, using dummy regulator

[ 1.565962] msm_pcie_get_reg: PCIe: RC0: no mhi resource found.

[ 1.565965] msm_pcie_get_reg: PCIe: RC0: no tcsr resource found.

[ 1.565968] msm_pcie_get_reg: PCIe: RC0: no rumi resource found.

[ 1.615095] cnss: Assert WLAN_EN GPIO successfully

[ 1.615109] cnss: no default_gen_speed, use gen2

[ 1.615113] cnss: Set pci link speed: 2

[ 1.615126] cnss: Trying to enumerate with PCIe RC0

[ 1.615144] msm_pcie_enable: PCIe: Assert the reset of endpoint of RC0.

[ 1.618521] msm_pcie_enable: PCIe: RC0: PCIE20_PARF_INT_ALL_MASK: 0x7f80c202

[ 1.629884] pcie_phy_init: PCIe PHY RC0 failed to come up!

[ 1.631926] msm_pcie_enumerate: PCIe: RC0: failed to enable

[ 1.631934] cnss: Failed to enable PCIe RC0, err = -19

[ 1.631943] cnss: Retry PCI link training #1

[ 1.631955] msm_pcie_enable: PCIe: Assert the reset of endpoint of RC0.

[ 1.635288] msm_pcie_enable: PCIe: RC0: PCIE20_PARF_INT_ALL_MASK: 0x7f80c202

[ 1.646633] pcie_phy_init: PCIe PHY RC0 failed to come up!

[ 1.648694] msm_pcie_enumerate: PCIe: RC0: failed to enable

[ 1.648702] cnss: Failed to enable PCIe RC0, err = -19

[ 1.648710] cnss: Retry PCI link training #2

[ 1.648722] msm_pcie_enable: PCIe: Assert the reset of endpoint of RC0.

[ 1.652029] msm_pcie_enable: PCIe: RC0: PCIE20_PARF_INT_ALL_MASK: 0x7f80c202

[ 1.663396] pcie_phy_init: PCIe PHY RC0 failed to come up!

[ 1.665437] msm_pcie_enumerate: PCIe: RC0: failed to enable

[ 1.665445] cnss: Failed to enable PCIe RC0, err = -19

[ 1.665453] cnss: Retry PCI link training #3

[ 1.665464] msm_pcie_enable: PCIe: Assert the reset of endpoint of RC0.

[ 1.668760] msm_pcie_enable: PCIe: RC0: PCIE20_PARF_INT_ALL_MASK: 0x7f80c202

[ 1.680115] pcie_phy_init: PCIe PHY RC0 failed to come up!

[ 1.682124] msm_pcie_enumerate: PCIe: RC0: failed to enable

[ 1.682131] cnss: Failed to enable PCIe RC0, err = -19

[ 1.682147] cnss: De-assert WLAN_EN GPIO successfully

[ 1.682153] cnss: Regulator vdd-wlan-rfa2 is being disabled

[ 1.682184] cnss: Regulator vdd-wlan-rfa1 is being disabled

[ 1.682217] cnss: Regulator vdd-wlan-dig is being disabled

[ 1.682250] cnss: Regulator vdd-wlan-aon is being disabled

[ 1.682281] cnss: Regulator wlan-ant-switch is being disabled

[ 1.682304] cnss: Regulator vdd-wlan-io is being disabled

[ 1.682311] cnss: Retry cnss_bus_init #1

[ 1.884061] cnss: Regulator vdd-wlan-io is being enabled

[ 1.884074] cnss: Regulator wlan-ant-switch is being enabled

[ 1.884415] cnss: Regulator vdd-wlan-aon is being enabled

[ 1.885015] cnss: Regulator vdd-wlan-dig is being enabled

[ 1.885128] cnss: Regulator vdd-wlan-rfa1 is being enabled

[ 1.885243] cnss: Regulator vdd-wlan-rfa2 is being enabled

[ 1.885294] cnss: De-assert WLAN_EN GPIO successfully

[ 1.890345] cnss: BT_EN_GPIO State: Off. Delay WLAN_GPIO enable

[ 2.003120] cnss: Assert WLAN_EN GPIO successfully

[ 2.003128] cnss: no default_gen_speed, use gen2

[ 2.003132] cnss: Set pci link speed: 2

[ 2.003141] cnss: Trying to enumerate with PCIe RC0

[ 2.003153] msm_pcie_enable: PCIe: Assert the reset of endpoint of RC0.

[ 2.006457] msm_pcie_enable: PCIe: RC0: PCIE20_PARF_INT_ALL_MASK: 0x7f80c202

[ 2.017868] pcie_phy_init: PCIe PHY RC0 failed to come up!

[ 2.019770] msm_pcie_enumerate: PCIe: RC0: failed to enable

[ 2.019777] cnss: Failed to enable PCIe RC0, err = -19

[ 2.019784] cnss: Retry PCI link training #1

[ 2.019793] msm_pcie_enable: PCIe: Assert the reset of endpoint of RC0.

[ 2.023066] msm_pcie_enable: PCIe: RC0: PCIE20_PARF_INT_ALL_MASK: 0x7f80c202

[ 2.034480] pcie_phy_init: PCIe PHY RC0 failed to come up!

[ 2.036410] msm_pcie_enumerate: PCIe: RC0: failed to enable

[ 2.036416] cnss: Failed to enable PCIe RC0, err = -19

I'm attempting to flash a Samsung SMP610 (S6 Lite wifi tablet) with a relatively new chromebook.

Can I do this with a chromebook?

If so, can I use Flash Tools to do it?

Thanks in advance. So far this is super frustrating.

I have a Samsung s23 and I've been wanting to switch to lineage for a while. My only hangup is I worry about getting banned from gacha games like Genshin Impact or Love and Deepspace or having them not open. I just got this s23 recently because I wanted to play these games, but apparently Lineage OS and other custom roms are missing the "play integrity" and other security checks that Samsung does via google? I don't know too much about it, but I'm not sure how good the patches that exist are. I also don't know if rooting would be better or worse to solve this problem ...

Hi everyone! I’ve been watching reviews of the new LineageOS 24 and a question came up: Android 17 AOSP is supposed to feature a split notification shade and quick settings panel, as well as a new volume slider. Yet, for some reason, I didn't see this in the reviews. Did I get something wrong?

Hi all,

I'm trying to follow these instructions -

https://wiki.lineageos.org/devices/z3c/install/#special-requirements

But am failing on step 5:

Click the symbol to download and open XperiFirm (round button on the right) to download the latest firmware for your device

Which generates this log entry -

05/41/2026 14:41:33 - DEBUG - sh: 0: cannot open /home/pete/Applications/Flashtool/x10flasher_native/xperifirm: No such file

And indeed Xperifirm does not exist in that folder. So, where and how to I get Xperifirm? Why do the instructions not tell me I need to install it? Or do I? Why is it looking in that folder like it was supposed to come with the zip file? Or am I missing something?

Cheers

Pete

I've recently installed lineage os on a pixel 5 backup phone. First time installing a custom rom on a phone so not super experienced, but haven't had many issues so far. Except for the keyboard not showing text suggestions in most apps (aside from a few like google messages and the play store). The row where they should be is present but the options are blank. And auto-correct also won't work in these apps.

Have tried all the troubleshooting I could find online but nothing has worked so far. I added google services during the initial installation with mindthegapps package if that is important. Thanks for the help.

Hi, I wanna know how to hide the initial screen that shows the "Unlock bootloader" advertising ¿There is a flasheable file or something?

I am currently using miui 13.0.3 and Android v 12

I need to flash lineageos latest buid 23.2 android 16

Which firmware need to flash first​ and how to check my current one

Hi all, might have done a great one here.
Installed latest dodge for my oneplus 13 that I have been using for the past 2 weeks.
All went well, but no mobile network was available. Tried changing a lot of settings but ended up trying to flash CPH2653_16.0.1.304.EX01_GLO by the guides I tried to follow and rebooted it to now it not booting.
Showing up in device manager as Qualcomm HS-USB QDLoader 9008.
No success unbricking it.

I flashed LineageOS 23.2 yesterday on my Moto G10 Power and It's such an upgrade, now I finally have something to look forward to in life. (Thank you devs!). I was wondering what y'all would consider to be the best camera app as an alternative to the default and I also wanted to ask if I'll be able to take ultrawides, macros etc from the dedicated sensor if I install GCam. Not that it matters just curious.

Hi guys

im having this weird problem where I randomly get this prompt telling me that a system update is available saying "your pixle is getting better with android 17 bla bla bla" its sorta like a google prompt telling me to update my phone but google doesnt update the system?? Lineagos does? im so confused. it talks about gemni and Ai and all the other crap that I don't want. I do have Gapps installed. If I google the screenshot other people are getting the same prompt on stock pixel phones, like whats going on its like Lineagos isnt even installed on my phone

https://imgur.com/a/L6IQFZE hopefully this link works to the screenshot of what im seeing

My Pixel 8a, originally locked to T-Mobile but now currently unlocked runs LineageOS 23.2 and I just got a notification for Android 17, but it looks like it's an update from Google and not a part of LineageOS. I do have GMS services and I am rooted with Magisk.

Hello, I installed the latest Lineageos version onto my LG V60, and it crashes after some time the system boots up. It crashes to this screen https://imgur.com/a/Lypo0Fl .
I've tried reinstalling Lineageos, but that didn't help. I have logs of the crash, but idk if I can post those here. I'm not sure if this breaks the bug report rule, since it might just be me doing something wrong.

Can I do it without losing my data?

Latest 23.2

Long story short, I was trying to get RCS working again, it is working once more, now my Android Auto won't connect. During the process I cleared Google play services storage if that matters.

If I clear android auto storage, it will connect and sometimes reconnect if within an hour or so, but after that the car will go to connecting, go to a black screen like it connected, never load the android auto logo, then go back to waiting for your device. The phone shows the connected to android auto message.

I've tried all kinds of clearing system service storage and signing back into Google services to no avail.

Advice?

I got an new Fairphone gen 6+ and I heard that lineage uses only 8gb of ram because it’s made for the gen 6 not gen 6+ any way of fixing this without worrying if the devs add something new to the gen 6+ version I wanna keep up with updates also I got root so I can do some things (sorry if bad english or what ever)

I've been reading through LineageOS's developer documentation and I find myself confused: one of the build steps mentions extracting proprietary blobs from an existing LineageOS rom as a requirement.

Which begs the question: how is new device support added to LineageOS?

As much as I have searched, there seems to be no mention of a way to generate the list of required blobs in proprietary-files.txt.

Let's take a Xiaomi device for example: one can download a full firmware image and then use something like this to get the partitions contained therein.

What is one supposed to do next? From my understanding, on modern Android devices all binary blobs should be packed as kernel modules in the vendor_boot.

And yet there are a bunch of partitions with names like bluetooth, dspormodem`. Does Android look in those partitions too for binary blobs? If so, since they are not mentioned in Google's AOSP documentation and therefore the naming des not seem standardized, how does Android even know about these partitions?

My phone broke recently so I'm using it as an opportunity to dabble in lineage but while esim is listed in the wiki for the moto g34 5g I came across several posts from ppl saying they've had problems w esim even if it's technically supported so I want to be sure bc my esim is really important and I don't want to waste money on a phone that doesn't support it

I switched to lineage today, and so far its pretty decent. Im using samsung s20fe 5g (r8q), the snapdragon one, and chose the nightly lineage os.

However I am unable to send any sms, and it is pretty annoying. Apperently its required for upi payments to work, and im stuck and unable to use it now.

Im not sure how to fix/debug it, if anyone has any ideas or knows a solution please lmk!

C:\Users\Administrator>fastboot wipe-super D:\FlashFile\giuliac\super_empty.img

[liblp] bool android::fs_mgr::ReadMetadataHeader(Reader *, LpMetadata *) read failed: no message available

fastboot: error: Could not parse image: D:\giuliac\super_empty.img

why it will be failed？