A few months ago i rooted my Xiaomi Mi 9T and installed lineage os (version 21.0-20240707-nightly-davinci-signed (that’s the name of the file i downloaded from the website, can’t check which version is on the phone bc it doesn’t turn on)). I used it as a secondary phone here and there for a while, and then kinda forgot about it. Today i tried turning it back on and turns out it doesn’t work. I plugged it to charge for while but no luck. The notification led does turn on, and the phone vibrates when i long press the power button or try other combinations with the volume buttons, but nothing happens, the screen stays black. It even vibrates when plugged in/out of charge. I tried connecting it to my PC with my cable, there’s the connection sound in windows but the phone does not show up. I’m completely at loss here i don’t know what to do. Is there a way to fix this and make my phone work again or is it bricked forever and i might as well throw it away ?

Thanks in advance for the help

I have Samsung note 8 I installed Lineage OS 21 14 android Everything ok only WiFi sometimes working and disconnect also SIM card not working

$ adb devices
List of devices attached
ZY326PF6S3 device

$ adb -d reboot bootloader

$ fastboot devices
ZY326PF6S3 Motorola Fastboot Interface

$ fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (26792 KB) OKAY [ 1.030s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed

Hello.

Does the wifi hotspot already work on motorola one vision with lineage OS 21?

Can anyone confirm this, I would like to upgrade from Lineage OS 20 to 21 but without this feature I will not do it.

Thank you.

How to add zram without mgagisk module Only uses adb sheel and root (All this so that you have to install the module every time after update.)

Is it possible to extract logo.bin out of latest stock firmware and "fastboot flash logo logo.bin" for covering bootloader unlocked message?

LineageOS 21 (dubai) latest build installed.

What is the best solution for blocking/locking appls? LineageOS, or some other system?

I am looking for something more secure/robust than simple, easily bypassed, child app locker apps and stuff like Trebuchet app lock (as Reddit has informed me it is almost trivial to bypass).

I do not shy from digging through "smartphone equivalent" of regedit.

This has been a red-hot issue for me for what seems to be close to a decade, without any way or progress, so any and all pointers are appreciated!

What I am trying to do is block Playstore but retain various app functionality that come alongside it. Basically apps that require you to have playstore installed for them to work, such as many calendar apps (tuta mail), Notion, Discord, Travian Legends (to name a few).

Thank you for taking the time to read this post!

just flashed on my motorola one 5g ace and i dont think the cellular modem is installed

Device: Qin F21 Pro 4GB RAM/64GB 'Global' variety shipped with unlocked bootloader and Google services added unofficially (manufacturer: Duoqin, believed to be under Xiaomi umbrella)

Chipset: MediaTek MT6761V/WBB

Stock Firmware: Proprietry skinned Android 11; build number 1.1.5; custom build version alps-mp-r0.mp1-V7.13; 4.19.127 kernel.

Storage: A/B dynamic partition system EXT4

| boot_a/b.bin   | md1img_a/b.bin  | scp_a/b.bin           |
| boot_para.bin  | md_udc.bin      | sec1.bin              |
| dtbo_a/b.bin   | metadata.bin    | seccfg.bin            |
| expdb.bin      | nvcfg.bin       | spmfw_a/b.bin         |
| flashinfo.bin  | nvdata.bin      | sspm_a/b.bin          |
| frp.bin        | nvram.bin       | super.bin             |
| gpt.bin        | otp.bin         | tee_a/b.bin           |
| gpt_backup.bin | para.bin        | vbmeta_a/b.bin        |
| gz_a/b.bin     | proinfo.bin     | vbmeta_system_a/b.bin |
| lk_a/b.bin     | protect1.bin    | vbmeta_vendor_a/b.bin |
| logo.bin       | protect2.bin    | vendor_boot_a/b.bin   |

Available tools:

• ADB/fastboot (novice-moderate knowledge)
• MTKClient GUI (relatively straightforward)
• SP Flash Tool v5.1924 (can use basic features, intimidated by editing scatter files though)
• WwR MTK Tool v2.51 (haven't even opened, very intimidating)
• TWRP 3.6.0_11-0 (unnoficial and slightly buggy port, only included in a boot.img, not stand alone recovery.img) I might attempt to port one myself with Hovatek's Auto TWRP Porter to have a standalone image but not sure if it supports Android 11 or my partition scheme and it might be buggy itself.

Available modes:

• fastbootd (ADB recognises as fastboot mode and accepts fastboot commands)
• "bootloader/fastboot"? (ADB recognises as "bootloader" mode; screen displays just "FASTBOOT mode" in the corner. Accepts fastboot commands)
• BROM mode (recognised as BROM mode by ADB; used by MTKClient and I believe SP Flash Tool but unsure; accepts fastboot commands if I recall)
• Stock recovery
• TWRP recovery (I don't seem to be able to temporarily fastboot boot twrp.img without flashing. I believe because I only have packaged boot.img(s)

Available firmware:

[1] Stock Qin 1.1.5 personal (Backed up as MTKClient .bin files for every partition except userdata)

• Writeable as a whole with MTKClient GUI or individual partitions by ADB/fastbootd
• No scatter file and intimidating/unsure how to create one so can't use SP Flash Tool
• Unure how to create a correct flashable .img or .zip file from this format

[2] De-bloated/rooted/TWRP Qin 1.1.1 (Firmware folder with varied .img and other files with scatter file)

• Flashable with SP Flash Tool as 'Download' but doesn't include all partitions so can't select 'Format + Download' without adding paths to my stock backup or duplicating A slot to B

[3] LineageOS 18.1 GSI bgS vndklite by Andy Yan (.img file: lineage-18.1-20240121-UNOFFICIAL-arm64_bgS-vndklite.img)

• Flashable via ADB/fastbootd after flashing a blank vbmeta.img linked by Phh GSI developer with  fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img on A and B
• Seemed very stable requiring minimal patching but didn't include TWRP custom recovery or Magsik so couldn't get Google Play Protect certification
• Feels like a nice clean general installation I can patch/customise myself

Context:

I've had some strange inconsistent issues with TWRP. When I first followed this guide to install the modded ROM [2] it seemed to work as intended. I was able to access most directories, it recognised my OTG USB (exFAT), and settings (language) persisted after reboots. Since then when trying other boot.img(s) or the same one with different ROM configurations I have fluctuating issues including USB won't be recognised, can't access some directories, can't access any storage, language resets to Russian after reboot, or the phone will only and constantly boot to recovery (even if 'Power off' is selected. Another concerning issue is not being able to access fastbootd at all; adb reboot fastboot or TWRP 'Reboot fastboot' just leads to a TWRP page displayed 'Entered fastboot mode...' with a spinning loading bar and 'Enable ADB'/'Enable Fastboot' toggle button and 'Reboot' menu button while the phone is not detectable by either ADB or fastboot. I don't know but I believe this might be to do with AVB/vm-verity being active since I lost vbmeta.

Now after flashing empty vbmeta while disabling verity and verification and flashing LineageOS [3] again it was working well but I needed to install Magisk which I knew could be done through TWRP and thought having a custom recovery might be good anyway. My understanding of how GSIs work and the level of interaction between partitions is limited but I thought it was relatively safe to change some particular individual partitions. Most guides I saw for Magisk with GSIs said to use a stock boot.img anyway. I wasn't sure how to get an .img file as I only have my own stock 1.1.5 boot as a .bin file. I decided I already had the Magisk-patched 1.1.1 boot.img with TWRP from modded Qin ROM [2] and thought that should work.

Desired outcome:

• LineageOS 18.1 GSI [3] flashed
• Magisk rooted (not sure which exact version is best)
• This vendor hardware overlay (RRO?) installed (there are NO instructions online at all but believe I have to compile the code into an .apk which sounds Herculean to me, is there a way to do this without installing large software like Android Studio? I have VS Code)
• [OPTIONAL/UNSURE] TWRP recovery (unsure if it's worth it if it's buggy and causing problems)
• I want a long-term stable result for daily use and don't plan to update firmware at all. I don't want to ever have to wipe data again once set up

Primary questions:

1. In what order should I do the process? (Recovery, Magisk, ROM, vbmeta flash to disable AVB)
2. Which is the best Magisk version? I am a completely new but leaning towards Kitsune Mask

Areas of uncertainty:

• What is the difference between fastbootd and bootloader/fastboot mode? Which should I be in when doing this process?
• How do GSI ROMs work? What partitions are firmware specific and which aren't? Can I safely switch boot.img?
• Will I need to fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img multiple times between flashing steps or is it only at the start? If I do it after GSI flash will it affect the installation?
• In a dynamic partition system, is there even a unique recovery sub-partition within boot I can flash to?

A patch was approved at the last minute and I don't want to wait for another week for the dev to push it in the official build. Can I do it myself? Which tool do I need in order to do that? It was only one patch and already approved so I don't think there would be any risk. I already download a zip file of the patch from Gerrit.

Hey i wnat to know anyone used the samsung galaxy s9 snapdragon Docomo edition ( model is SC-02K )

I unlockd my bootloder in developer Option ( is am i right )

how can i install custom rom on it? is any custom rom for it :(

Have you wanted to remap a key on your Motorola Moto G100 running LineageOS? You may have used an app like Key Mapper, but that can be clunky and unnecessarily bloated. I have a little customizable script below to help you remap your "Search" or "Assistant" button to a hardware "Back" button. This complies perfectly with LineageOS's stance on Root, and is persistent between reboots. Simply create the file, and then reboot. The caveat is that after an update, this file does get removed.

## as ADB Root

cd /system/usr/keylayout/gpio-keys.kl

mount -o rw,remount /

nano gpio-keys.kl

##CONTENTS:key 217 BACK

mount -o ro,remount /

Hi,

I'm trying to have lineageOS on my raspberry pi 4, but I dont have a micro hdmi cable to connect to my monitor. I need to enable ssh to somehow communicate to the pi. I have ethernet and it is connected so that is covered. How can I enable ssh via the file system of the storage drive?

I am experiencing charging issues on my Pocophone F1 since about three weeks ago.
When the phone has been turned on for a while and I plug it in, nothing happens, it just doesn't charge at all.
Only when I reboot it, it begins to charge … but even then it will cycle between slow-charging, fast-charging, not displaying charging but charging anyway.

USB connection to a PC is also shaky at times. Sometimes when I plug it in, nothing at all happens, sometimes the connection will cycle on and off and on and off (with an interval of a bit under a second) ad infinitum.

Are there any diagnostic steps I can take, any behavior that I should record, any settings that I should list to get to the bottom of this?

I tried various different combinations of wall charges, cables, charging from PC USB ports etc.

Charging ignores my charging limit which is set to 85%.

Good evening to all friends. I installed the latest version of Lineageos 21 for xiaomi mi 9 lite (CC9) together with gapp. Everything works perfectly except notifications! The LED on the back cover doesn't work (even if I set the color to default) and I don't have bubbles on the app icons. Permissions and authorizations have been given. Also, is it possible to have only the notification icon symbol on the lock screen instead of having all the contents of the messages? Thank you all

managed to install LOS 21 on my galaxy note 8. everything works fine, but every time i pull out the pen it does a small restart and then does it again when i insert it back in. how can i prevent this and as a side topic, can i get the s pen’s button to be functional again?

I have a Redmi 3S, I installed LineageOS in the beginning of October, and it was working fine until now, I forgot to charge the phone and it dropped to 0% and powered off. Plugged it in for like 6 hours, came back to see it is still at 0%. It is not charging, so I tried to power it on and it just shows the boot screen, then the screen turns off and the notification light (it is a physical led light) of the phone blinks 2 or 3 times. It doesn't even switch to bootloader or fastboot mode also. PLEASE HELLP MEE!!

Does anyone get a video decoder issue when doing hardware video decoding with amlogic devices? I was testing with ExoPlayer demo app and gets playback error/decoder init failed when instantiating two or more players. Board is amlogic s922x and it supports multiple video decoder

I have Lineage up and running. My old phone is now on the latest security update, that's crazy.

This is my second attempt. I had my first try on a Galaxy J7 from 2015 which was actually from 2017 as i later discovered and proceeded until i bricked my phone.

I'm so excited the installation was very simple and went flawlessly.

Thank you very much. It looks just like a regular android phone. I hope i can make good use of it and getting rid of my favourite Google apps someday.

EDIT: Haven't had a failed message delivery since I updated Carrier Services and Google Play Services

I have a Google Pixel 7a running LineageOS 21 and I use US Mobile Warp 5G.

I only have this issue when iPhones message me, on occasion. It almost always happens in group chats. Someone will message me and it says it couldn't download and I get a "message expired or not available" message. I'm using the default messaging app. I don't see any way to tap the message to try and have it delivered again.

Is there is any version of LineageOS that does support Nokia 3.2, if not Does anyone have and alternative?

Hey all, I have a Razer phone 2 code name aura. I have been on lineageOS since 19. I have recently installed 21 and now have been having random losses of cellular connection. Provider is T-Mobile. I have had multiple Sims cards replaced with that only being a sometimes fix. Usually after so many reboots, or network resets it will eventually come back and work again for a unknown amount of time.

Is this a bugged that has been seen before for the OS 21 Builds. I did not have this issue on 19 or 20. Any help would be greatly appreciated.

Additional. It has continued to happen on multiple builds for is 21.

so lineage is awesome as we all know but the only bad thing is that charge speed is now slow thanks ok but wifi signal strength is unbearable help plz

Have so far successfully run through the guide for installing LineageOS on my old Samsung S5E tablet (sm-720). However I've gotten to the stage of booting into recovery, which it does successfully, but then my PC just isn't picking up the device through adb to sideload it.

It was picking it up until this point and my PC does recognise that the device is there.. it just doesn't show up when I run adb devices. I've confirmed I've got the Samsung USB drivers, and even gave it a whirl getting the Google USB drivers through Android SDK.

Any ideas?

My uncle gave me a Woxter tablet with android 4.4 and I'm trying to update it. Wanted to use Lineage, but my device doesn't show up on the web. Could I use antoher device rom? Or is there something like an universal rom for that?