[ROM][OFFICIAL][fajita][11] LineageOS 18.1

Search This thread

retry0001-coffee

Senior Member
Oct 21, 2019
140
49
Unlock the bootloader first. I would avoid TWRP. You don't need it. Recovery is built into the ROM now because there is no longer a dedicated recovery partition (blame android for this). Whenever you update the LOS ROM, recovery is updated with it. If you insist on TWRP, you will have to manually reinstall it every time you update. Follow the directions. How did you even install LOS if you haven't unlocked the bootloader?
 

Not-Aus

Senior Member
Hello together,
I am on LOS 18.1 from 23. Dezember 2021.
When i want to install an LOS update by the build in updater, the boot process always fails. After 3 or 4 fails, the phone switches back to partition A and boots fine to its old system.

Does anyone have an idea on how to fix this?

(Latest Magisk ist installed.)
 

letmedanz

Senior Member
Aug 26, 2010
2,754
4,146
Bangalore
Same issue here as well.
Download and installation from inbuilt updater finished.
Reboots into lineage recovery in slot b where it says no os, to reset and format.
Switching partition and rebooting boots back into the older install.
Latest OOS 11 firmware was previously installed
 
  • Like
Reactions: Not-Aus

retry0001-coffee

Senior Member
Oct 21, 2019
140
49
Whatever is wrong seems specific to you, or a group of users. Try to figure out what you've done differently with your customizations. The problem likely stems from something peculiar you've done.
 

Geitekont

Member
Aug 10, 2019
13
1
I have a question (couldnt find it on google) Every time when i install a update my phone doesn't boot properly.. I get stuck in de recovery mode (i guess) when i format my data the OS boots again. But i have to walk trough the hole process like its a new phone (installing all the apps again). Its very anoying. Doest someone know a solotuin ? I am now on the latest Lineage OS + Gapps.


Tx
 

Geitekont

Member
Aug 10, 2019
13
1
I have no idea, is there a way i can see that ? ( think i used stock or something like that, if this is what you mean)
 

retry0001-coffee

Senior Member
Oct 21, 2019
140
49
Not sure where you can see that, but opengapps does leave a log of what it did on the filesystem. Anyway I'm just making guesses. You could try to manually install newer firmware from within recovery and see if that works. I am not going to walk you through that though.

BTW, to everybody having problems: if your vendor patch level is not November 1, 2021, and your phone is not converted to the international version (i.e. Still using T-mobile), then you're running in a non-standard state, which means unpredictable behavior. If you're messing around with TWRP, or installing anything other than opengapps pico, I will assume you messed something up and it's the reason for your problems. When you're having problems that the majority are not having, then y ou need to look at what you're doing differently.
 

Not-Aus

Senior Member
BTW, to everybody having problems: if your vendor patch level is not November 1, 2021, and your phone is not converted to the international version (i.e. Still using T-mobile), then you're running in a non-standard state, which means unpredictable behavior. If you're messing around with TWRP, or installing anything other than opengapps pico, I will assume you messed something up and it's the reason for your problems. When you're having problems that the majority are not having, then y ou need to look at what you're doing differently.
For me I can say, the firmware is the latest, the phone is not branded, GApps are Nano (that really is okay and not problematic), I don't mess around with TWRP and modify the system with mysterious things / hacks / mods, etc.
The only additional thing is Magisk for being able to use an adblocker. Just that - and no other "special" stuff.

The installation process, was clean - the way it should be. I am not new to LineageOS.

Anyways - booting from _b does not work after updating. The initial installation on _a does work without problems.
 
  • Like
Reactions: letmedanz

dlexik

Member
Apr 5, 2004
13
0
Dubai
I've recently switched from OOS to LineageOS. I use Melomania Touch earbuds that support TWS+.

On OOS each earbud connected using TWS+ via bluetooth to the phone individually and showed the individual battery percentage and I could turn one off without affecting the other. On Lineage it's only connecting via a single earbud that then relays the connection to the other bud and only shows a battery percentage for the directly connected bud. From what I can see in previous commits TWS+ should work in Lineage. Just wondering if that's the case for the 6T please?

I was thinking about swapping to LOS now that it looks like 19 is moving into stable release sometime soon -- but I am a big user of Qualcomm BT TWS+ with single earbus and don't want to lose this feature to pair each bud individually. Is this working for anyone ? Prof. Y - did you manage to get this fixed ? Thanks any and all and of course for the ongoing effort making LOS better and better !!
 

Prof. Yaffle

Senior Member
Mar 19, 2008
327
21
OnePlus 6T
I was thinking about swapping to LOS now that it looks like 19 is moving into stable release sometime soon -- but I am a big user of Qualcomm BT TWS+ with single earbus and don't want to lose this feature to pair each bud individually. Is this working for anyone ? Prof. Y - did you manage to get this fixed ? Thanks any and all and of course for the ongoing effort making LOS better and better !!
No, no joy for me. When I pair for the first time the first bud pairs and the second bud pairs too as a separate connection the same as OOS but doesn't actually connect to the phone. Only one bud can actually be connected to the phone at a time unlike OOS. This is confirmed as the directly connected bud has higher battery drain when I look in the Melomania app.
 
Last edited:
  • Like
Reactions: dlexik
I have a question (couldnt find it on google) Every time when i install a update my phone doesn't boot properly.. I get stuck in de recovery mode (i guess) when i format my data the OS boots again. But i have to walk trough the hole process like its a new phone (installing all the apps again). Its very anoying. Doest someone know a solotuin ? I am now on the latest Lineage OS + Gapps.


Tx
Use lineage recovery and install on both partion don't forget to follow the official installation guide. I do have the issue when I installed using twrp but after using lineage recovery all the perfect and Ota works fine
 

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    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:
    15
    Good news for us all! Our devices (enchilada/fajita) have been officially promoted to lineageos 19.1. Find the relevant commits here:

    Enchilada: https://review.lineageos.org/c/LineageOS/lineage_wiki/+/321288/22/_data/devices/enchilada.yml
    Fajita: https://review.lineageos.org/c/LineageOS/lineage_wiki/+/321288/22/_data/devices/fajita.yml

    @EdwinMoq (Hope I'm tagging the right Edwin) It is great to have you as our official maintainer for fajita :)

    Thank a lot for all your work on our devices Edwin and Luke, looking forward to many more years of LOS <3
    9
    @LuK1337 Tahnks for all your hard work.
    Will our beloved 6T also get official 18.1 support?
    Eventually.
    8
    I have gone through the trouble of extracting firmwares from the December 2021 update to OnePlus 6T's OxygenOS (version 11.1.2.2 - package OnePlus6TOxygen_34.J.62_OTA_0620_all_2111252336_339a2fa8335f21) using payload-dumper-go

    But to make the process easier for others, i will share the resulting .img firmware files and the steps to update your firmware..

    1) Download the extracted firmwares:
    https://drive.google.com/file/d/1vhtMEVX0vG2fhNBQfcu0LaKrq1F1K_ah/view?usp=sharing

    2) Follow the firmware flashing steps:
    Code:
    1) Boot to Recovery
    2) Enter Fastboot (e.g for LineageOS recovery: "Advanced" > "Enter Fastboot")
    3) Connect phone to PC with USB cable
    4) Open cmd (command prompt) in your adb / fastboot binaries location folder, and then start flashing..
    Enter commands 1 by 1:
    
    fastboot flash --slot=all abl abl.img
    fastboot flash --slot=all aop aop.img
    fastboot flash --slot=all bluetooth bluetooth.img
    fastboot flash --slot=all cmnlib cmnlib.img
    fastboot flash --slot=all cmnlib64 cmnlib64.img
    fastboot flash --slot=all devcfg devcfg.img
    fastboot flash --slot=all dsp dsp.img
    fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
    fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
    fastboot flash --slot=all hyp hyp.img
    fastboot flash --slot=all keymaster keymaster.img
    fastboot flash --slot=all LOGO LOGO.img
    fastboot flash --slot=all modem modem.img
    fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
    fastboot flash --slot=all qupfw qupfw.img
    fastboot flash --slot=all storsec storsec.img
    fastboot flash --slot=all tz tz.img
    fastboot flash --slot=all vendor vendor.img
    fastboot flash --slot=all xbl xbl.img
    fastboot flash --slot=all xbl_config xbl_config.img
    
    fastboot reboot
    
    Done, now your phone will boot up with the updated firmwares.

    I should mention that today i first updated the firmware, rebooted before i was going to get today's new LineageOS build. But before i did so, i noticed that the interface was snappier.. so clearly not due to the LineageOS update, rather they made some performance tweaks in the latest firmwares from Dec 2021 OxygenOS..

    So it's really worth updating your firmware. Also because it bumps the vendor security patch level to November 1, 2021 (the OxygenOS update is, as they say, focussed on security fixes)

    Note: if you're looking for the entire original OxygenOS 11.1.2.2 ROM, i also uploaded that here: OnePlus6TOxygen_34.J.62_OTA_0620_all_2111252336_339a2fa8335f21.zip

    Btw thanks @LuK1337 i've used your LineageOS on my 6T for the past 4 months, and the experience has been perfect!
    5
    Why do the builds say nightly and not stable on the download page? I thought the ROM was "official" and stable now?
    lmao.