yashsingh1/xdaforums huggingface dataset:
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] LuK1337:
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

Instructions :

https://wiki.lineageos.org/devices/kebab

Downloads :

https://download.lineageos.org/kebab

GPL compliance :

https://github.com/LineageOS/android_kernel_oneplus_sm8250

Reporting Bugs

DO NOT Report bugs if you're running a custom kernel or you installed Xposed

Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)

If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)

If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

What is your--
LineageOS version:
LineageOS Download url:
Gapps version:

Did you--
wipe:
restore with titanium backup:
reboot after having the issue:

Are you using--
a task killer:
a non-stock kernel:
other modifications:

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] ALGOPOP:
Where can i find the "latest Android 13 full stock ROM" for KB2003 as mentioned in the Instructions? On the Oneplus Site i only find a Android 11 ROM for download. I am on LOS 19.1 atm.

Thanks...
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] LuK1337:
KB2001_11_F.13 - https://gauss-componentotacostmanua...22/11/15/71ff9f8989a040d58e73869a9e078c43.zip

KB2003_11_F.13 - https://gauss-componentotacostmanua...22/11/18/83d837a54bd647c3902634d271f6cc2d.zip

KB2005_11_F.13 - https://android.googleapis.com/packages/ota-api/package/e61f1cf7c6a55e531113091deadfb7acb96901da.zip
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] pabx:
Updated from LOS19 to 20 yesterday - no issues so far (other than the phone wanting my SIM code 3x after the first boot). Thanks a lot LuK1337!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] trance89:
+1

Migrated from 19.1, everything is ok. Thanks for this new year's present Luk! :)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Andreas T.:
Also migrated from 19.1 - working great so far. Thank you very much!

Just one minor problem I noticed about the new camera: video recording turns off after some time and the screen goes black. Probably the normal idle time till the screen turns off, but the camera should somehow prevent it, no?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] LuK1337:
https://review.lineageos.org/c/LineageOS/android_packages_apps_Aperture/+/346656
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Daviteusz:
Has the black flicker associated with fod been fixed (when using 60hz refresh rate)?

View attachment 5798613

If not, is it possible to force 120hz on the lock screen and ambient display to remove this?

ColorOOS bypassed this bug this way.

Edit:

After update to QPR2, this bug is fixed on lockscreen/ambient display. Sometimes I see it when unlocking bitwarden app, but this is not big deal.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
I migrated over from 19.1 this morning and things look good so far here. (y)

I will test/report if the Bluetooth/adaptive brightness issues I'd recently reported for the latest 19.1 builds are still ongoing with 20.

EDIT: Bluetooth seems fine, adaptive brightness is unchanged and leaves at lot to be desired.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
Bug Report: (on Gitlab)

Adaptive Brightness is incredibly aggressive at times when you don't expect it to be and it seems to jump to 80%+ in many situations vs. the stock behavior being more like 25-40% in those same situations.

LineageOS version: 20-2022-1231-NIGHTLY-kebab

LineageOS Download url: https://mirrorbits.lineageos.org/full/kebab/20221231/lineage-20.0-20221231-nightly-kebab-signed.zip

Gapps version: MindTheGapps-13.0.0-arm64-20221025_100653

Did you--

wipe: No

restore with titanium backup: No

reboot after having the issue: Yes

Are you using--

a task killer: No

a non-stock kernel: No

other modifications: Magisk, MindTheGapps

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

- The stock OOS software has a very "as expected" adaptive brightness curve and I never experienced this overly aggressive behavior.

- This behavior has been present on all versions of LOS19.1 and now 20 that I have used.

- Full wipes and reinstalls never changed this behavior.

- I would say, anecdotally of course as I'm not tracking it meticulously, that this happens 40-50% of the time.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] 4ronie4:
I was planning to upgrade to LOS19 when 20 came out. Right now I have firmware of OOS 11 and LOS18, is it ok to flash directly OOS 13 firmware and then LOS 20 and skip OOS12 and LOS19?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] exthomeboy:
the os runs wonderfully. the new camera app looks good but can't keep up with gcam in terms of image quality. The fingerprint sensor works, but somehow slower than other os.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Shmi117:
I just upgraded from my 19.1 install.

1. Downloaded stock Android 13 linked above from LuK

2. Dumped payload with payload-dumper-go, rebooted into fastboot

3. Followed vendor image upgrade instructions

4. Rebooted into 19.1 recovery, flashed lineage 20 .zip

5. Rebooted again to switch slots, flashed magisk

6. Success!

Thanks LuK!!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] IAAxl:
Thank you for sharing your steps! This really gave me the courage to do it.

I'll... I'll have a try... 😖
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] sido201:
Please help, the phone is stuck in the start loop! @LuK1337

I had had CalyxOS (A12) on it for months and everything ran pretty well, but unfortunately no updates came and the device is no longer supported. Now I wanted to change to LineageOS 20. Since I unfortunately found no instructions on how to do this, I did the following:

- 1 FW update, under CalyxOS the versoin 11 was used.

- unfortunately came during the execution 2 errors: please see paste bin

(https://bin.disroot.org/?96f93b2e4680e174#GmX4Vpia1Cz6hAmhKvFuEz6no88jWcPG8MQAzk1BDNC6)

These are:

Sending 'mdm_oem_stanvbk' (4732 KB) OKAY [ 0.164s]

Writing 'mdm_oem_stanvbk' FAILED (remote: 'No such file or directory')

Sending 'spunvm' (348 KB) OKAY [ 0.011s]

Writing 'spunvm' FAILED (remote: 'No such file or directory')

on this I looked in the LOS installation guide and thought maybe run these commands first:

fastboot flash dtbo <dtbo>.img

fastboot flash vbmeta <vbmeta>.img.

the result was:

[me@me-82a2 OP8T]$ fastboot flash dtbo dtbo.img

Sending 'dtbo_a' (24576 KB) OKAY [ 0.837s]

Writing 'dtbo_a' OKAY [ 0.154s]

Finished. Total time: 0.997s

[me@me-82a2 OP8T]$ fastboot flash vbmeta vbmeta.img

Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]

Writing 'vbmeta_a' OKAY [ 0.003s]

Finished. Total time: 0.008s

Then I repeated the step before, so FW update, unfortunately with the same result!

Next I did : fastboot reboot fastboot

Now the phone starts since 30 minutes in continuous loop,

each process takes not even 1 second :(

THANKS for any help!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] xCassidi:
If im coming over from another custom ROM based on OOS13; is there any shorter method than MSM back to 11, re unlock BL, flashing OOS 13 twice and then installing the new ROM?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Pyntux:
I am using F.15 Oxygen OS on my KB2003, is that OK for installing LOS 20?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] erictmc:
Anyone know where to download just the firmware for Android 13 for 8T KB2003? Don't feel like downloading the full ROM (over 4GB). Thanks in advance.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] tostah:
I had the same issue. Executing "enable-verity" via adb shell and reboot did fix it for me.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] 21prods:
Concerning update, yes, no more than this. At least, what I can recognise from the logcat
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] 21prods:
That was it, thank you.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] djlooka:
Hi all, I've been sitting on this problem for a few days (opened a thread on Reddit already but I couldn't get to a solution - not sure what the etiquette is for cross posting to different sites!).

A summary of my case is the following: I made a couple of huge mistakes while upgrading from LineageOS 19.1 to 20.

Firstly I did not back up the phone, secondly I was reading from the wrong wiki page so I ended up missing the crucial part about upgrading the firmware.

My (incorrect) steps:

started from LineageOS 19.1 without upgrading FW

adb reboot bootloader

fastboot flash recovery lineage-20.0-20230119-recovery-kebab.img

This lead to a Qualcomm CrashDump screen.

After a bunch of attempts to fix the situation*, I ended up in the following state:

the phone boots to fastboot mode

any attempt to run the recovery from there ends up with a black screen

in this state, the phone responds to adb list devices with

List of devices attached

c9cf7ae7 unauthorized

which makes me believe that the recovery is indeed booting, although the screen is completely black and I cannot authorize my computer (it was authorized before this whole mess I caused)

running any command in this state (predictably) leads to

error: device unauthorized.

This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wron

Otherwise check for a confirmation dialog on your device.

I am therefore stuck in a limbo where I cannot use the recovery to discover whether the phone is ddr4 or ddr5, so I cannot upgrade the firmware now.

(* the latest state of the phone is (I think) the result of

flashing LOS20's recovery

realising my mistake

flashing LOS19's dtbo.img, vbmeta.img and recovery.img to both slots)

I am aware that I can most likely use the MSM tool to flash the original firmware, but this would crucially wipe the data, which I would like to avoid since it's my girlfriend's phone and there are some irreplaceable files on it.

Is anyone** aware of a way that would allow me to recover the data before using the MSM tool and restarting from scratch? I would be forever grateful!

(*I'm mainly thinking of @LuK1337 here, but I am genuinely open to suggestions and can provide further details if needed)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] LuK1337:
Ask on IRC, this is too annoying to deal with on forums.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] JedidroidX:
Flash the recovery and dtbo , vbmeta of the last successful Lineage that was installed via bootloader. Just hold all buttons down (volume + - and power) until fastboot screen is shown than flash files. Should be able to recover from that issue. Than reflash the same Lineage that was working before. You also may need the boot.img of the last lineage that was successfully installed then flash with the other images in bootloader. The recovery should boot up. You may need that Lineage payload and use the payload dump tool to retrieve that boot.img.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] djlooka:
Solved!

The black screen was because I started from an Android 11 firmware, which didn't work with the 19.1 recovery.

Steps to recover:

from fastboot, flashed boot.img/dtbo.img/recovery.img from here

"Reboot to recovery" <- this booted the Lineage 18.1 recovery

ran adb shell getprop ro.boot.ddr_type to discover that the phone was ddr4 in my case

selected "Advanced" -> "Enter fastboot"

followed the guide to upgrade to A13 FW

selected "Enter recovery"

sideloaded LineageOS 20

Thanks a ton to @LuK1337!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] anarchotaoist:
UPGRADE 2001 COMPLETE - ON LINUX

Upgrade LOS from 19.1 to 20.0 retaining all data.​

Read every article about this device on LOS wiki. (https://wiki.lineageos.org/devices/kebab/)

Backed up with adb backup, adb pull and Seed Vault.

Downloaded the firmware Luk provided on page 1 for 2001

Extracted the firmware files using payload dumper python version. I could not work out how to run the linked payload-dumper-go version!

Boot up LineageOS recovery

Go to “Advanced” -> “Enable ADB”

Check your DDR type using the following command: adb shell cat /proc/devinfo/ddr_type (mine was ddr4)

Go to “Advanced” -> “Enter fastboot” It will then show 'fastbootd'

Update firmware to OOS 13 version. (https://wiki.lineageos.org/devices/kebab/fw_update) YES ALL 20 files!

Flash correct XBL files (mine were the two for ddr4)

fastboot flash recovery

reboot to recovery. Noticeably recovery said 19.1! ?? I ignored the version.

Appy update - adb sideload lineage.zip

Reboot system - new bootloading message 'Orange'

SUCCESS!!!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] RJSC:
Is there any way to do an OTA upgrade and not overwrite the recovery with lineageos?

The option on the updater to no update recovery is blocked, but this device has a separate recovery partition, so it should be possible to do.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] dharkness:
followed this guide https://xdaforums.com/t/guide-how-t...national-kb2000-kb2001-kb2003-kb2005.4178675/ and when i flash the magisk.img it just goes back to fastboot >_<
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] gdfajkldfkwfj:
myQ app doesn't work on https://lineage-20.0-20230119-nightly-kebab-signed.zip/ , unable to log in / app becomes unresponsive
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] dagustl:
First thanks a lot for Lineage20 @LuK1337 !

Works fine so far on my 8T KB2003 EU (Clean Install yesterday with the newest build after setting back with MSM-Tool and upgrading to OxygenOS F15)

I just have the issue that i can almost not see the "Download" and "Cancel" button on downloads with the default browser.

It´s a little bit visible on display settings in dark design but almost nothing in light design .

It´s no problem with Firefox.

Best regards, and have a nice weekend. :)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Sredna76:
Thank you for inspiring me to do similar upgrade 19.1 to 20.0. I am using the microG version of LineageOS but the steps should be similar. This dirty upgrade worked for me but may not work for others.

1. Download latest TWRP (twrp-3-recovery-installer.zip) ,Firmware Flasher script for Oneplus 8 series (https://github.com/Wishmasterflo/Firmware_flasher) and check for your 8t fw in the mega folder ,I downloaded fw_Oneplus8T_EU_OOS13_F15.zip download latest LOS 20.0 or LOS 20.0 microG

2. Install TWRP and boot in to recovery & flash Firmware Flasher script for Oneplus 8 series (fw_Oneplus8T_EU_OOS13_F15.zip)

3. Flash latest LOS 20.0 zip

4. Flash twrp flashable zip

5. Reboot in to recovery and flash magisk or whatever you need (gapps)

6. Reboot system
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] praveen7682:
@LuK1337 thanks for lineageos20..I flashed the latest update using fastboot installer followed by mindthegapps 25102022 from lineage wiki and format data..the setup completed without issues but after restore apps didn't work since it was not connecting to any internet WiFi or mobile data.internet not working only for google apps.but internet works normally in browser.pls help me what wrong with my installation..
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Lomobasd:
Hi,

can someone confirm for me if the brightness of the always on display (ambient display) is fixed in LOS 20 now?

With 19 the brightness of the always on screen would go to lowest brightness after a view seconds for me which mage it completely unusable.

Thanks in advance!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
Update for anyone that finds stock adaptive brightness insufficient:

As of the nightly update on 1/26 there appeared to be many luminance sensor changes, and I can confirm that the light sensor has now been exposed in such a way that third party applications that manage brightness can now detect the sensor and utilize it appropriately. After upgrading I did immediately test the stock adaptive brightness feature for a day, just for the sake of argument in case its behavior had changed, and I do not see any material improvement in it's function.

That said, since the luminance sensor is exposed now, I am using Velis to manage brightness and it is working quite well. (For me, the AMOLED dim setting with slight adjustments to the curve is working great)

@LuccoJ - FYI
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Lomobasd:
Ok i upgraded and the always an is still broken. Even worse now the fingerprint scanner sporadically doesn't work form always on screen now. It detects the finger but the screen below the finger doesn't turn on.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] rocketda7331:
Do you have A13 based i8hsn conf? For now I plugged the previous ones based on A12 and it seems to work, but if you got something more up to date would be nice.

// Nevermind, it can be found here

https://xdaforums.com/t/rom-official-kebab-13-lineageos-20.4536037/post-87944629

interestingly enough a13 one causes cts profile mismatch, 12 not..but out of scope for this thread I suppose.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] binngy:
I'm not getting any apps in the fullscreen menu. Any fixes possible ?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] D€INOS:
Really awesome to see such amazing development!

Some questions:

Do AoD / Ambient display have issues?

Is Fingerprint is slower than OOS?

Do Adaptive brightness have major issues so it's better not to use?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
I don't use AoD so I can't speak to that one.

The fingerprint reader seems to work just fine vs. OOS, I don't notice any difference.

For stock adaptive brightness I would steer clear entirely as it's not even remotely close to OOS. If you read back in the thread you'll see a lot of conversation about it.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] gdfajkldfkwfj:
Is there a working version of Google Camera for LOS 20? The one from Google play store keeps crashing, LOS's stock camera is lacking (can't select between multiple cameras, landscape photo saved as vertical, no panorama / photosphere)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Max-P:
AoD works just fine, although it does need to be manually enabled and it's not easy to find in the settings. Fingerprint is about as responsive as stock. I don't use adaptive brightness but reports in this thread say it's pretty buggy anyway.

Aperture (LineageOS' included camera app) does support switching cameras. It's the "0.6", "0.9" "1x" and "1" zoom options, which is separate from the software zoom control. Because that's what those cameras effectively are: 2 wide cameras, the regular one, and the macro one.

If you want GCam, you need Arnova's GCam from here with the matching profile: https://www.celsoazevedo.com/files/android/p/camera-unlocker-oneplus-8-9r/

No need for the Magisk module, LOS comes with the cameras unlocked.

GCam is still extremely buggy in my opinion, so I just use Aperture for most uses, unless I really want to make a 48MP picture or want the advanced processing.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Recall0317:
Hi guys, first post on the forums!

I have LOS20 installed on my 8T and have been liking it, but I do have some problems. I am currently running the latest OS version (February 2nd) with stock LOS recovery and the devices is not rooted.

First is the automatic brightness which just does not work. I have Velis installed and it does not detect the brightness sensor. This is not a deal breaker for me, but somewhat annoying still.

The other one is the bigger problem, and new with the LOS20. The proximity sensor is not working at all. Velis reports it too as "not found" like the brightness sensor.

I've read through this topic and it seems that the auto brightness is a complicated issue but some of the users have a working proximity sensor. I too had it working with LOS19.1 with the same device. Is there any way to get the proximity sensor working without rooting the devices? I prefer not rooting my daily phone for app usability.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] luspi:
Adaptive brightness is working pretty well for me on my 8T+. Using the app "Sensors Toolbox", it lists a light sensor by name "stk33502 wise Light Sensor Non-wakeup" and correctly lists the current lx value. For proximity it lists the "stk33502 Proximity Sensor Wakeup", however, it only two value options, 5cm or 0cm, although they at least show up as expected.

I also installed the Velis app, but this app is not able to detect any sensors, so it might be an issue with that particular app...?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Recall0317:
Said app doesn't show the sensor. Tried checking with AIDA64 and found some info.

Ambient light sensor is listed with name "tcs3408 Ambient light sensor rear Non-wakeup". That code tcs3408 is also tied to bunch of other sensors such as RGB Sensor, Flicker Sensor etc. Proximity sensor is not found at all. Also none of those tcs3408 show any data though, just the name.

Basically any sensor readings I get from AIDA are related to gyroscope and accelerometer. This seems a bit weird. Is there anything to be done?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] luspi:
Hm, it looks like we have two different sensors... that probably explains why they work for some but not others.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] JedidroidX:
Been using Lineage for about 5 days on my Oneplus 8T TMO variant. My current network is Verizon.

It seems I stop receiving text after some time and the only way to receive text is by either rebooting the device or enabling and disabling airplane mode. Sending text always works, is there a fix for this or perhaps maybe using a different sms app would resolve the issue.... (SIgnal)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] gdfajkldfkwfj:
bluetooth audio in Google Voice stopped working in latest LOS build, same issue as OOS

How can I revert back to KB2007's official rom and re-lock bootloader?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] JedidroidX:
just use the msm tool than update to latest OOS. You can find msm tools all over xda. Msm will automatically lock the boot loader.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] silverhazesupreme:
Been itching to get off stock OxygenOS and give LineageOS another try. I want to use gapps but the bare minimum and I found that NikGapps has a core package that has less Google bloat than MindTheGapps. Has anyone tried it on Android 13? Will it work?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] 21prods:
I did and it works, no problem up until now.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] silverhazesupreme:
Can confirm, just flashed it and it works
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Does Google assistant still work with it?