Development [ROM][OFFICIAL][lemonade][12L] LineageOS 19

Search This thread
For the 20220511-FASTBOOT package,I can not flash the partition "vendor-dlkm".When flashing in fastbootd mode,it says no such a partition.So when I flash other partitions successfully,phone cant boot into system instead it boots into bootloader mode.I have update firmware to OOS12 C47 via lineage os wiki method.
Can you try flashing the package while in bootloader mode?
 
Can you try flashing the package while in bootloader mode?
Still having no partitions,which are "vendor_dlkm" and "super_empty".Phone is in bootloader mode.
1652624419332.png
 

Harshith292002

New member
Jan 30, 2019
1
0
Hi, I'm currently using paranoid android sapphire beta 1 on my op9. Will this ROM be more stable than that and is ROM good to flash on a daily use device ?
 

neelchauhan

Senior Member
Dec 25, 2016
51
27
Google Pixel 3
Google Pixel 6 Pro
Hi, I'm currently using paranoid android sapphire beta 1 on my op9. Will this ROM be more stable than that and is ROM good to flash on a daily use device ?
I have run both LOS19 and PA Beta 1 on my OP9. However my LOS was a self-built one with OOS11 firmware.

They both are be stable, but I didn't try OP's firmware.

However, if you brick when flashing PA->LOS, do a MSM flash (I tried PA but didn't like it).
 

Olomorn

Member
Apr 6, 2016
11
2
Hi, thanks for your work, @andr01dfr3ak
So if I understand correctly, to install your latest version (lineage-19.1-20220511-FASTBOOT-lemonade.zip), since I am on the latest version of OOS12, I can just follow the normal procedure, is that it ? No need to downgrade to OOS11 ?
 
I've uploaded a new build. This time, you don't need to use fastboot to flash it, and you can just follow the normal instructions instead.

This time, you need to flash both the vendor_boot and the recovery images before you can reboot into recovery. Then you can flash the updated build normally.
 

henkka22

Senior Member
I've uploaded a new build. This time, you don't need to use fastboot to flash it, and you can just follow the normal instructions instead.

This time, you need to flash both the vendor_boot and the recovery images before you can reboot into recovery. Then you can flash the updated build normally.
sms still not working for me on this build
 

Olomorn

Member
Apr 6, 2016
11
2
I have 2 questions before I do the installation :
- is it compatible with every models? I use LE2113, is it ok?
- is there a way to still use both back cameras? I tried using the GCam on stock OOS and it worked poorly.

Thanks :)
 

Olomorn

Member
Apr 6, 2016
11
2
Okay, I may wait a little bit longer until this is fixed then, but I am really looking forward to this. Thanks again for your work!
 

jdse

New member
May 30, 2022
3
1
WA
- The only model this may not work on is LE2117
I'm running this on LE2117. All it took was first flashing it to Global with MSM.

Android thinks it's an LE2113 now, but it runs great otherwise!

Edit - this no longer works with the build requiring A.12 firmware, however this will flash just fine on top of the stock TMO OOS 12 LE2117 firmware!

If you want to use this ROM with mobile data on LE2117, I recommend returning it to stock first and updating OOS all the way. The guide on the Wiki will work perfectly.

Thank you for all your excellent work OP and others!
 
Last edited:

xxxuuuzzz

New member
Jun 1, 2022
2
1
when I follow the Update firmware steps and type fastboot flash --slot=all abl abl.img, there is a error: unknow option -- slot=all, how can i solve it?
 

hamzaarbeed

New member
Nov 24, 2015
2
0
Hello,
I have lineageos 19.0 04062022 running. I tried to flash the new lineage os 19.1, but no luck. I get qualcomm crash dump screen. So I flash the old one lineage 19.0 for the phone to work again.
I think the firmware upgrade to oos 12 didn't work for me.
I followed the following steps to upgrade.
let me know if I am not doing it correctly.
1. download the latest oos for European version My phone model is LE2113.
2. run ./payload-dump-go payload.bin.
3. go to extracted folder run all the fastboot flash commands from the official lineage os page for upgading instructions. This takes time, it looks like it is done correctly.
4. Sideload lineage 19.1
Reboot.
Here the phone shows me qualcomm crash drump screen.

Edit:
I figured it out.
I was upgrading firmware using OOS 11 not OOS 12.
"fastboot: error: cannot load 'engineering_cdt.img': No such file or directory"
There is no engineering_cdt.img in OOS 11.
When I searched I found out that I was trying to do upgrade using OOS 11
I'm dumb sorry.
Thank you
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Anyone who is having issues with the black screen bug, test out the images in this ZIP and report back.

    Includes this change: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8350/+/334681
    4
    It happened to me yesterday once at night and today another two, before it happened to me 2 or 3 times a day easily. Maybe it's mitigated but not resolved I think.
    Ambient display off
    tap to wake off
    prevent accidental wake-up on

    What is also happening to me is that the phone sometimes turns on by itself in my pocket (I hear it starts to dial in the emergency call menu), I don't understand why, if I put my hand on the top of the phone for too much touch does not turn on the screen, the sensor seems to work fine.

    New images to try
    3
    @ZVNexus Around 24h gone by with no black screens at all. The pulse on pick up, fingerprint reading from ambient and general unlocking all feel smoother too

    New images to test.
    2
    If you are having issues with cwb-test-2, you will also have issues with cwb-test-3. I have uploaded cwb-test-4 with some recent changes from OPPO. Please report back if the issue persists.

    1
    I think they are saying C.61 is 'an upgrade too far' as changes are not yet merged and you should have stopped upgrading at C.48.

    I also made this mistake with my new OP9, but I'd like to point out the installation guide clearly states to be on the latest version, which isn't true in this case. That should probably be updated.


    EDIT: I "updated" my firmware using a full OTA zip (c47 in my variants case) by following these instrcutions https://wiki.lineageos.org/devices/lemonade/fw_update and all sensors are back!
    That worked, thanks! I followed your steps and installed C.47 in both slots, sensors are working for me now too, thank you!
  • 22
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, 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 our 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:
    5
    This section is for updating LineageOS. You must have your device connected to your computer to do this.

    To update to newer builds of LineageOS 19.1, follow these steps (assuming you're already on LineageOS 19.1 or updating from LineageOS 19.0):

    1. Reboot to recovery.
    2. Write down which slot you are currently on somewhere. You will need it in case the update does not boot correctly.
    3. Go to Apply Update > Apply from ADB, and use "adb sideload" to flash the newer build of LineageOS.
    4. If you installed Gapps or Magisk or any type of addon previously, go to Advanced > Reboot to recovery. Otherwise, select "Reboot system now".
    5. Go to Apply Update > Apply from ADB, and flash your modules the same way you flashed LineageOS.
    6. When you are done, select "Reboot system now".
    If an update does not boot, follow these steps:
    1. Reboot to bootloader. This can be done with "adb reboot bootloader".
    2. From there, use "fastboot --set-active=<slot>", replacing <slot> with the slot you were on previously.
    3. Reboot to system. You can just select "START" with the volume buttons and confirm by pressing the Power button.
    5
    Starting this month, all builds that I upload will require OOS 12 firmware to boot. You must follow the instructions here BEFORE you can even update to these builds:

    https://wiki.lineageos.org/devices/lemonade/fw_update
    Make sure you also update the engineering_cdt partition while you do this.

    After this, you must reboot into bootloader mode and flash the new recovery image, which I will also upload. From there, boot into recovery and flash the new build. If you had Gapps installed, reboot into recovery and flash them again.
    5
    Anyone who is having issues with the black screen bug, test out the images in this ZIP and report back.

    Includes this change: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8350/+/334681
    4
    The first build of LineageOS 19.1 (Android 12L) has been uploaded for the OnePlus 9. All LineageOS 19.0 users can upgrade to this build normally.