I had the same issue. Executing "enable-verity" via adb shell and reboot did fix it for me.
[ROM][OFFICIAL][kebab][13] LineageOS 20
- Thread starter LuK1337
- Start date
I had the same issue. Executing "enable-verity" via adb shell and reboot did fix it for me.
Concerning update, yes, no more than this. At least, what I can recognise from the logcat
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:
After a bunch of attempts to fix the situation*, I ended up in the following state:
(* the latest state of the phone is (I think) the result of
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)
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
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.
(* 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)
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)
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.
Last edited:
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:
Thanks a ton to @LuK1337!
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!
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'
Last edited:
followed this guide https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/ and when i flash the magisk.img it just goes back to fastboot >_<
myQ app doesn't work on https://lineage-20.0-20230119-nightly-kebab-signed.zip/ , unable to log in / app becomes unresponsive
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.
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.
Last edited:
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
Last edited:
@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..
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!
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!
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
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
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.
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
[ROM][OFFICIAL][kebab][13] LineageOS 20
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...
forum.xda-developers.com
interestingly enough a13 one causes cts profile mismatch, 12 not..but out of scope for this thread I suppose.
Last edited:
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?
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?
Similar threads
- Locked
Top Liked Posts
-
1
Happy to help. And magisk is the only one really. Luckily it's awesome! Lol
You can patch the boot img, which I think is the recommended method, but I've been able to just rename the APK to zip and adb sideload it. I would try that first.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to...
github.com
11
I think your right.
The android file manager does not have the option to install apps.
I installed simple file manager from apkpure and now I can install apps.
Thanks -
2Whilst I love the Lineage Os project, there should be a way to report errors to not so technical users. I think that's the obstacle of the today roms landscape and why it's a bit in decadence. Technology evolved and most OEM roms have mechanisms for reporting errors without any hassle.
I'm a developer myself, but I just don't specialize in Android, so don't know a lot of the tool or how to use them. Just to make android apps...
This is not a rant at all, but just what I've been feeling since I've been installing custom roms from 2014/2015...
In the lineage os gitlab there are a lot of errors that I think would be valid. Logcat, description of problems, etc... But just because they don't exactly follow a template are closed in a determined time. Even if the necessary info is present.
This is a hassle for normal users. And some of them might go back to their oems skin like I'm about to do.
Thanks for the help anyways
That's correct, custom firmware is absolutely not for beginners. And the posts clearly state that.1
Strange behaviour... I use USB type c headphones and they work very well, I have never suffered anything similar to that.1
That's not uncommon in hardware diagnostics. It could be a flaw in the LineageOS build, or a hardware flaw that doesn't have the same outcome on different codebases.
But either way the outcome is probably the same. This will probably not be fixable.
If you want to do some further diagnostics, and see if we can find a bug to file (I can show you how to do that also). The next step would be a reboot of the phone, trigger the "bug" and then check your phone logs.
This is my fav app for doing so.
If you want help looking at the logs, don't post the text in the thread here. Upload it to pastebin or similar service, and post a link to that log.
I can help take a look
I've had the app installed forever, so I'm not 100% sure on this, but I think you can use root or adb to give it access to your phone logs. At least I know root isn't mandatory, but you might have to jump through some hoops to get it running with the appropriate permissions
1
Post the logs. We will always need an exact error or logs to be able to help. Instructions are in my comment right above yourHi people! I'm having a big problem and would like to know if it happens to you too.
I did all the installation steps listed in the Lineage OS wiki. Installed it, everything was working fine at first. But lately since the original installation + the new updates my device randomly hangs in a black screen, like if you couldn't exit the standby mode, and have to reset it pressing the power button for a really long time. Even using Android auto happens
It's starting to happen with some frequency. Didn't have this problem in oxygen is rom.
I tried saving logcats, but since the device gets stuck with no previous advice I don't actually know how to read them and the possible error.
Any help or guidance would be appreciated
Here is some info:
Lineage Version: 20-20230302-NIGHTLY-kebab
Compilation: lineage_kebab-userdebug 13 TQ1A.230205.002 3a48ea0afd
Model: Kb2003
Sim1 carrier: None
Sim2 carrier: Yoigo1
I think your right.
The android file manager does not have the option to install apps.
I installed simple file manager from apkpure and now I can install apps.
Thanks -
21
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. You can also view the Changelog for a full list of changes & features.
Instructions :
Downloads :
GPL compliance :
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
Code: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:10
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.zip5
Adaptive-brightness definitely does not work as you'd expect, unless the LOS 19.1 behavior is what you'd expect/want.
Adaptive brightness not functioning as expected and is often far too bright (OnePlus 8T/kebab- LOS20) (#5361) · Issues · LineageOS / issues / android · GitLab
Expected Behavior Expected behavior would be a...gitlab.com
If I compare the current behavior to either the stock software or other devices entirely with other and/or stock OS's, the LOS 20 behavior is extremely aggressive when it detects any source of light. It typically jumps to around 80% in many circumstances and rarely adjusts itself lower unless there is a massive drop in what the sensor detects. For the sake of argument, I've been keeping adaptive turned on and then manually adjusting the slider to try and help it "learn" but I've not seen anything that even resembles learned behavior.4
Hi,
Take a look here,
New posts
-
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)- Latest: IronTechmonkey
-
