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

Search This thread

Ray_Blue

Member
Aug 10, 2020
5
4
Hello everyone.:)
I'm using Universal SafetyNet Fix for Realme.
Screenshot_20220630-115143_Settings.png
Screenshot_20220630-115209_Yet Another SafetyNet Attestation Checker.png
 
  • Like
Reactions: mattie_49

velocitysages

Member
Oct 29, 2020
20
1
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.
when i tried to update from first build of lineageos 19.1 to second build of lineageos 19.1, it says system update corrupted, and it need for clean flash, how to fix it?
 

AtoZ0to9

Senior Member
Unfortunately I am having more issues similar to the unresponsive back button on other parts of the screen. I can't tell if it's the screen or a UI freeze, but I think the latter. I really wanted this one to work. I'll try to hold on for the next weekly, but it's doubtful.
 

mattie_49

Senior Member
Feb 4, 2010
3,344
1,045
Seymour Tn
OnePlus 9 Pro
Unfortunately I am having more issues similar to the unresponsive back button on other parts of the screen. I can't tell if it's the screen or a UI freeze, but I think the latter. I really wanted this one to work. I'll try to hold on for the next weekly, but it's doubtful.
I was getting black screen yet heptic feedback for buttons. Came down to having to do multiple times in a few hours. Holding all 3 buttons to force reboot. I think it's system Ui as well. I tried making it work. Was great other than this issue. But quite the bug
 
I was getting black screen yet heptic feedback for buttons. Came down to having to do multiple times in a few hours. Holding all 3 buttons to force reboot. I think it's system Ui as well. I tried making it work. Was great other than this issue. But quite the bug
I have a feeling this has to do with the feature that blocks screen wake-up when the phone is in a pocket. I have switched it off and have never experienced this bug again. You can find this setting at the bottom of the display settings.
 
I couldn't pass either. Thought I had it but no. Something in the build makes it mismatch cts. It will get better in time. Just thought with it being official it would be useable with magisk. That's not the case. In your case it's detecting the unlocked bootloader you needed unlocked to get where you are .:(
You have to use the universal safetynet fix and magisk props conf. With that you pass all safetynet checks, but some banking apps will detect root anyway. There is a tool called island which makes those apps work with the help of an work environment. Your have to install the banking app, activate magisk hide for the app, clone it via island into the work environment and delete the original app from the private profile.
 

WesTD

Senior Member
Nov 22, 2013
1,122
691
Eskişehir
OnePlus 9
I've just flashed latest build but i have some problems;

1. Phone services use location
2. VOLTE or VoWiFi is not working.
3. Auto brightness is not working well. ( i think it is common bug for OnePlus devices.)
 

AtoZ0to9

Senior Member
I have a feeling this has to do with the feature that blocks screen wake-up when the phone is in a pocket. I have switched it off and have never experienced this bug again. You can find this setting at the bottom of the display settings.
This seems to have fixed it, huge thanks. I'll give the magisk / island solution a try.

So I can flash magisk in LOS recovery without having to load any patched boots? It's my first slot A/B phone, so this is new to me. I am to understand that I just flash magisk in LOS recovery, except for an update, I would flash it to the inactive slot, because that's what takes the update, correct?
 
Last edited:
  • Like
Reactions: ms1h1d
This seems to have fixed it, huge thanks. I'll give the magisk / island solution a try.

So I can flash magisk in LOS recovery without having to load any patched boots? It's my first slot A/B phone, so this is new to me. I am to understand that I just flash magisk in LOS recovery, except for an update, I would flash it to the inactive slot, because that's what takes the update, correct?

I'm glad to help. Yes, I've renamed the APK to .zip and flashed it via lineage recovery. The magisk app didn't show up afterwards so I also installed the APK manually. Everything works as intended. I just bought this phone and the 20220627 build is the first rom this phone has ever seen, but I guess when you update to a new lineage build via the ota updater you have to reflash magisk. I've got this link which explains the island solution, but it is in german. Maybe google translate can help:
 
  • Like
Reactions: AtoZ0to9

61zone

Member
May 8, 2013
13
3
Dhaka
OnePlus 9
OTA updates takes 1.5-2 hours to complete installation. Specially "finalizing package installation" process takes more than an hour itself. Is this normal or I am missing something?
 

AkkiV

Senior Member
Jul 5, 2013
94
38
Update ran through very smoothly, apart from the very long update procedure. For those who want to know: I can confirm that magisk and all modules are surviving the update without a reflash to be necessary.
Gapps too? Regardless, it's nice to know Magisk modules surviving OTA updates.
 
  • Like
Reactions: ms1h1d

Twist79

Senior Member
Jul 16, 2011
321
92
Vienna
OnePlus 8T
OnePlus 9
I can confirm the sometimes unresponsive back button. I thought it to be my fault at first.

And my battery page still reports 13000% battery use by my display since last charge. I am on the newest nightly.
 
Last edited:
  • Like
Reactions: AtoZ0to9

Top Liked Posts

  • 1
    Black screen bug again in a few hours on cwb-test-4 :/.

    Does it matter which boot slot and vendor_boot they are installed in?

    With cwb-test-4 by default it is installed in slot b, but I think other times it has been installed in slot a.
    I just force install in both slots (boot and vendor_boot), but vendor_dlkm won't let me force it (Writing 'vendor_dlkm_a' FAILED (remote: 'No such file or directory')), by default it installs in slot b too.
    You shouldn't need to do anything more than flash them to the active partition your on. And one fails . It's ok your still getting patch.
  • 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
    Using MSM I restored to OO11, then upgraded all the way to C.61 and followed every step on the installation guide, including copying the partitions. After starting the device the sensors are sadly still not working.
    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!
  • 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.