I also tried looking at XDA, and I cannot get the thing to boot TWRP at all. Any help is appreciated. Model is ZE552XL.
Previously I indicated that my last update that worked was on Lineage-23.2-20260504-Nightly-Guamp-signed-zip, May 11 & May 18 updates kept taking back to May 4. I have tried to correct it using Adb and fastboot, but I am not getting back into recovery in order to sideload those updates. When I go to recovery mode it reboots several times and then starts the system. There is one other OP Handshake6610 having the same problem.
Are the updates faulty ? How can I get it into recovery mode again?
I was just using the calculator on my OnePlus 11 running the latest Lineage. It stopped responding to touch input for a few seconds and then the screen turned off. It wouldn't restart. I connected it to my PC and it's in EDL mode ("Qualcomm HS-USB QDLoader 9008"). Because OnePlus has some kind of security lock on EDL mode, as far as I know it's completely bricked unless I send it to them, and people's experiences with that online have been...mixed.
I have no idea if this is a software glitch (whether in Lineage or not) or a hardware failure. The device was almost new and had less than 40 battery cycles, but it's long out of warranty. (bought on eBay, I think it just sat for a while)
If any of my undertstandings about EDL mode above are incorrect, please let me know! And if anyone has any ideas about how to recover this or what could have caused this, let me know... Even if I get it fixed, not sure I can trust this device anymore.
Context: Since about 2023 I have gone down the path of open source software, and I've loved every second. Currently, I'm effectively entirely open source in my household (from PCs to phones and routers) but TVs are effectively the last foothold they have in my home. I have two 2019 (foster) Shield TV Pro's on dumb TVs to run Stremio and youtube clients, but I'd love to fully be rid of Google's Android TV (and potentially youtube in the future too).
Following this I've done my research into custom ROMs for the Shield, and LineageOS seems to be the only suggestion. In spite of this, there's essentially NO media online about it other than 3 forum posts, so I wanted to pose the question to the community...
Is anyone daily-driving LineageOS on their Nvidia Shield TV in 2026? Are there any major drawbacks? Bugs? Whats the stock UI like? Customization? Does HDMI CEC still work? If I have to go back, will I fuck it all up and have a brick? Give me your takes, as the most recent discussion is 3 years old at this point!
Hello, I'm posting this to see if there are more people getting this problem where devices like capri (the one I'm using) or guam may suddenly hit ramoops after some time and kernel panics, this behaviour maybe related to MGLRU especially the lru_gen_look_around() function being present in the ramoops log, this also could be a deadlock in queued_spin_lock_slowpath inside shrink_page_list and page_vma_mapped_walk path.
The device becomes sluggish after the active(anon) memory drops to 0 which makes LMK aggressive, killing as many processes it can, the inactive(anon) memory becomes inflated as time passes and then the kernel panic.
Despite the issue being reported many times on the bug tracker a little attention has been brought by maintainers and the bug remains, I'm not scolding any dev but what I'm asking for is a bit of time and attention to this egregious bug ofc take your times what I need is assurance that this will be worked with at least.
Purchased a used V50, great condition but looks like it’s a test version? Is there nothing I can do with this other than leave it as is? I only plan on using it as a DAP so don’t need many apps or cell.
Android System
Serial console enabled
Performance is impacted. To disable, check bootloader.
Watermark on screen
userdebug
9.60.16(96001600)
Android 12
Kernel version
4.14.190
Ige@android-build
Build number
flashlm_lao_com-userdebug 12 SKQ1.211103.001
221082202b3b4 test-keys
Software version
V450VM3F1
Software status
Modified
Device: Samsung Galaxy Tab A7 SM-T505
Codename: gta4ll
ROM: LineageOS 23
Carrier: BSNL India
Issue: "VoLTE Supported by Device" shows No in Pixel IMS app.
Mobile data shows "No connection" even though LTE is connected.
Calls work fine. Internet actually works but signal bars are grey.
Already tried:
- Carrier config XML edits
- Pixel IMS + Shizuku
- setprop commands for VoLTE
- Magisk volte_fix module
Is there a build of LineageOS 23 for gta4ll with VoLTE enabled?
Or any way to enable it without rebuilding from source?
Does anyone knows how to fix it? I remamber that gcam worked for me on oxygenos.
I bought pixel 5 because I've been wanting a smaller phone. Since the updates stop at android 14 I got on Lineage OS. Everything works fine but no RCS which is kind of a deal breaker. Is there a work around for this that works these days?
Otherwise my other option for a smaller phone would probably have to be an iPhone mini and I'd much rather stay with android than go to apple
Because I am selling my Pixel (8) Fold to upgrade to the Pixel 10 Fold, I picked up my old reliable Razer Phone 2 ("aura") - my backup phone, on which I run LineageOS 22. And when I updated everything to current time, I noticed it was still on A15 - and after reading this blog post here, I now know why. https://lineageos.org/Changelog-30/
My kernel is on 4.9.x, which does not seem to have the mandatory eBPF changes backported - but on the other hand, hardware support for the chipset in the phone, should have, at one point or another, become mainstream. It's a really old SoC by comparison now (Qualcom SDM845) and thus I wonder if it would be possible to bump the kernel version, to thus allow it to get A16 support...
In the Wiki, and the source tree, I can spot the maintainer - but just bursting through the front door and screaming "update kernel!1!!!11" does not sound like the proper path :P
What can I do to test and then submit this change? I'd love to eek out a little more livespan from this phone! It's been a super reliable fallback and so I would want to do something to give back to the people that have made sure it can run this way.
My goal would be to test out a few 5.x LTS kernels and then 6.x to see which one sticks. If I could nail it on a 6.x LTS, that'd be pretty amazing.
So yeah... what else can I do than to download the source and build my own image, upload it to the phone, boot and see what happens? - And, since this a bit of a bigger project structure, how do I submit a "pull request"? On Github, it's for one repo in a tab - but Lineage, and Android stuff in general, is spread across a whole bunch of repos...
Thanks!
As I have been using Windows X lite Optimum 11 25 H2 in my HP N208 TX model from last 2 years which is running smoothly on my device but I am quite confused will I will be able to flash Lineage Os on this modified Windows?
I have never flashed any custom rom on my device but I am curious about Lineage Os as I have heard a lot about this rom & I have seen many Videos on YouTube but I am very confused will it be a stable rom for my device?
I am looking for a long term stable custom Rom where I can get regular Android updates, security Updates and patches?
As I want to use Banking apps like - Yono Sbi and Bhim Upi for payment.
Please if someone can guide me how to flash this rom?
As a beginner I don't know much I have read a little bit but still I want some guidance from the community 🙏
I’m on OnePlus 6T, LineageOS 15. The official X app was working fine before.
I installed Piko X to try it, and after attempting to login there, the official X app stopped working too. Now it always shows: “Please use X.com or official X apps to proceed with log in/sign up.
Browser login on x.com works fine, only the app is broken. I already tried reinstalling X and clearing app data/cache.
Any fix?
I've heard really bad things about it.
If anyone has pictures they took using the LineageOS camera app, I'd love to see them.
Je compte acheter un téléphone (notamment un google pixel) et installer lineageOS dessus.
J'aimerais savoir si prendre un reconditionné ne gêne pas son fonctionnement ou si je dois faire attention à certains paramètres.
So question is if anyone has found solution for this? Problem occurs only after fast charging when phone gets hot. With previous LOS it worked flawlessly every single time, spot on! Now when it happened once, few reboots helped to get it back again, worked till now when I can't get it back and settings app is crashing when i try to access fingerprint settings using search as these are missing from device lock aettings screen.
Is my only option downgrade?
I came across this article a couple of days ago about google forcing users of android to have google play services in order to pass their new recaptcha. What do people like me who have google-less phones do about this? Is there a way around this?
Well, the title pretty much says it all. Left the phone in the bathroom at the store about a week ago and had to wait a week to get another one. Am using the same telephone company and number however on the new phone i forgot to install Gapps. i downloaded and installed WA and went through the setup process but i don´t see any old messages. i visited Drive and see a 2.8 Gb file under WhatsApp which i suppose are all my old messages, etc. but no way to get WA to download them. Any ideas? Thanks ahead of time for helping...
Or maybe it wasn't successful.
I put LineageOS on my OnePlus N30 5G. I read instructions, verified firmware, followed the instructions successfully until the 2nd to last step (installing Gapps was what I was about to do). The phone said it was sucessful, my command line said it was successful (or gave me no reason to be concerned) and now my phone won't start. Screen is black, no combination of buttons or commands does anything. It is effectively a brick.
If I plug it into my PC, my PC will detect something with the typical windows sound, and I can hold the power buttons on the phone and it will presumably cycle the power. Device removed sound, device inserted sound. But nothing else happens. The device manager detects something that I'm lead to believe is the Qualcomm EDL thing (it shows up as QUSB_BULK_CID:xxxx_SN:xxxxxxxxxx)
I've passed what I am knowledgeable enough to do. Any help would be appreciated.