• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][enchilada][11] LineageOS 18.1

Search This thread

kouzelnik3

Senior Member
Dec 29, 2011
465
137
24
Prague
jakubkasanda.g6.cz
OnePlus 6
Oh, that's a good point. I didn't flash the latest OOS yet. The last OOS I used on it was A10.

That's gonna erase my phone right?
It wont. If you use TWRP, boot into it, flash OOS 11, then LOS build, then twrp, then reboot recovery (for slot swap), do the process again, flash magisk optionally and reboot. You are done. :)
 
  • Like
Reactions: webtroter

webtroter

Member
Jun 23, 2012
49
5
Longueuil
It wont. If you use TWRP, boot into it, flash OOS 11, then LOS build, then twrp, then reboot recovery (for slot swap), do the process again, flash magisk optionally and reboot. You are done.
Thank you for the process
Thank you for the link :)


I'm gonna use the official Lineage process.

I have no problem using fastboot boot twrp.img, but I think I'll use the official method for safety.
 
Last edited:
  • Like
Reactions: kouzelnik3

webtroter

Member
Jun 23, 2012
49
5
Longueuil
It wont. If you use TWRP, boot into it, flash OOS 11, then LOS build, then twrp, then reboot recovery (for slot swap), do the process again, flash magisk optionally and reboot. You are done. :)

Up to you, I just written what I did when I was perfoming this upgrade :)


Thank you to you two!

The Firmware upgrade with the Lineage process was very fast. Very probably faster than flashing the whole OOS then LOS.

I confirm Dash is working now. I'll try to remember next time about the fw upgrade.
 

Sh0X31

Senior Member
Mar 27, 2010
1,394
645
Frankfurt am Main
Guys,
I have one question before I flashe los. When I compare the Battery life between OOS 11 and LOS 181, is there a big difference? Which one is more battery friendly? Thanks
 

lcrubn

Member
Jan 26, 2016
10
2
Hello,
I'm trying to do the firmware update and I'm receiving this error message:

error: Could not check if partition abl has slot all

do you know why?


Thanks in advance for the help
 

lcrubn

Member
Jan 26, 2016
10
2
Yes, I rebooted the device in fastboot mode. I'm using lineageOS recevery.
Also I've followed the lineageOS wiki to install the ROM.
 

CrysisLTU

Senior Member
Feb 1, 2012
311
371
Hello,
I'm trying to do the firmware update and I'm receiving this error message:

error: Could not check if partition abl has slot all

do you know why?


Thanks in advance for the help
Make sure to use the latest platform-tools.
Also, you need to flash via the recovery's fastboot menu.
 

ed57

Member
Sep 15, 2010
49
19
Thank you to you two!

The Firmware upgrade with the Lineage process was very fast. Very probably faster than flashing the whole OOS then LOS.

I confirm Dash is working now. I'll try to remember next time about the fw upgrade.
Hi all, thanks for confirming this is working. Do you get anything indicating it is dash charging? By me nothing, maybe normal I don't know

On the other hand, is it advised or useless to upgrade the fw after each lineage update?

Thanks in advance for your answer
 

webtroter

Member
Jun 23, 2012
49
5
Longueuil
Hi all, thanks for confirming this is working. Do you get anything indicating it is dash charging? By me nothing, maybe normal I don't know

On the other hand, is it advised or useless to upgrade the fw after each lineage update?

Thanks in advance for your answer

The first hint I had is that AccA was showing a low mA charging current, never over 2000. Dash goes higher than that.

I couldn't rely on the LED indicator on the phone, because that doesn't work in LOS, as far as i know.

Also, I then used some USB tools I have to confirm that the phone wasn't negotiating a dash charging protocol.
 

ed57

Member
Sep 15, 2010
49
19
One another question : I read somewhere on A/B devices it is not recommended to update the lineageos recovery at the same time as the rom itself. Is that right? Or is it safe to leave the option checked in preferences in the top right dots? (in the builtin Updater app)
 
Last edited:

leaderred

Senior Member
Dec 2, 2010
69
13
OnePlus 6
One another question : I read somewhere on A/B devices it is not recommended to update the lineageos recovery at the same time as the rom itself. Is that right? Or is it safe to leave the option checked in preferences in the top right dots? (in the builtin Updater app)
I always update ota with option for recovery update and have no problems
 
  • Like
Reactions: ed57

Top Liked Posts

  • 1
    More questions:

    I outsourced my 2FA for online banking on a separate device, so safetynet doesn't bother me to much, but if I could recover Widevine L1, I would be very happy. Is it possible to regaining it, by locking the bootloader, while using LOS Recovery & LOS, or would this brick my device? 😂

    You can get Widevine again if you relock your bootloader. But to do that you need to build your LOS and sign it yourself and do a lot of other stuff. Detailed guide here -> https://forum.xda-developers.com/t/...s-6t-with-a-self-signed-build-of-los.4113743/

    But I warn you, you take all the responsibilities and no one is to blame. But it should work fine for 18.1 too.
  • 1
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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 :
    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.

    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:
    Whenever we take photo using stock lenage camera it is not focussing and pic get blurred
    1
    Do you guys also have the issue that if you take a photo in WhatsApp, the actually taken image always is BIGGER than shown on the screen before shooting the photo? Like, the image itself catches more than is shown on the screen, I am not talking file size.

    I had a similar issues as long as I was using GCam. After using GCam, this problem would also be present in other apps accessing the camera. A reboot fixed it.

    So I stopped using GCam, and went back to the default camera app.
    1
    Hi! I just installed LOS on a NOS ("new old stock") Oneplus 6 EU Version I got for a bargain. First I updated completely Stock to OOS 11.1.2.2. Then I installed the 20211228 build according to instructions. I am using a german provider in the O2/Telefonica Network. I activated VoLTE and VoWifi in the settings, but seeing the diagnostics when dialing *#*#4636#*#* it shows me it is using GSM for the calls, even though being connected to 4G with good signal strength. Is it a configuration thing or do I have to go through this Qualcom Modem Setup procederes, which can be found in the Stock ROM threads?
    To answer my own question: Yes, I had to use the Qualcom tools.

    How to enable VoLTE:
    1. Enable in settings and see if it works
    2. If yes, good, you're done. If no, follow this guide: https://forum.xda-developers.com/t/...geos-17-1-for-eu-carriers-oneplus-6t.4119785/

    Important: Backup your EFS Partition before applying any changes. You delete a config, which I dont know if it could be necessary at some point, or if you delete some other config by accident.

    Remark: You do not need magisk. It is enough to enable ADB + ADB root in developer settings. You can enable adb root by typing "adb root". When you then enter "adb shell", you have root permission. Also the mentionend "setprop" command didnt work. This one works: "setprop sys.usb.config diag,serial_cdev,rmnet,adb"
    1
    To answer my own question: Yes, I had to use the Qualcom tools.

    How to enable VoLTE:
    1. Enable in settings and see if it works
    2. If yes, good, you're done. If no, follow this guide: https://forum.xda-developers.com/t/...geos-17-1-for-eu-carriers-oneplus-6t.4119785/

    Important: Backup your EFS Partition before applying any changes. You delete a config, which I dont know if it could be necessary at some point, or if you delete some other config by accident.

    Remark: You do not need magisk. It is enough to enable ADB + ADB root in developer settings. You can enable adb root by typing "adb root". When you then enter "adb shell", you have root permission. Also the mentionend "setprop" command didnt work. This one works: "setprop sys.usb.config diag,serial_cdev,rmnet,adb"
    Omg, I had already given up on this, thank you so much, I got volte and vowifi working now, awesome
    1
    In b4 don't ask for ETAs, I know...
    But does anyone know if @LuK1337 is working on lineageos 19 for enchilada, or anyone else for that matter. Last year he had an early test build ready in October, now it's December. I'm definitely not complaining, just wondering if someone puts effort into this or if I will have to look for another device soon.
  • 30
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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 :
    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.

    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:
    3
    If anybody is curious, Ive been crawling through the code commits. Unfortunately, it looks like both Enchilada and Fajita will have to wait for some time due to issues that were encountered when booting. At least for Fajita. It will be some time until we get our first official build.

    UPDATE 1: Both Enchilada and Fajita have been reverted from the hudson branch, which indicates official commit status has been reversed. Our savior Luk has got hands full with work on these issues I imagine, so wait times will extend. Hang tight lads! We will land on Hudson soon, I hope.

    UPDATE 2: That was quick! Seems like Luk figured out the issue for Fajita and has opened a commit to merge fajita to 18.1 official again. Fajita and enchilada are merged to the Hudson branch once again. This is good news, and I am hoping that the enchilada build will be posted and merged on schedule.
    3
    Anyone else having touchscreen issues with the latest build? Like not responding to some touches and not being able to pull down the notification shade?

    Edit: reverted to last week's build and the issue is gone. So some commit messes with the touchscreen.