Development [ROM][OFFICIAL][lemonade][12L] LineageOS 19
- Thread starter andr01dfr3ak
- Start date
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?
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 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.
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.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 .
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.)
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.)
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:
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:
Gelöst: DKB TAN2go mit Visa Secure trotz Root (2022) » elcombri.de
Ich zeige dir in diesem HowTo, wie du TAN2go und 3D Visa Secure der DKB auf deinem gerooteten Android-Gerät nutzen kannst.
www.elcombri.de
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?
Will get faster in time. Let's be glad it's working. Is def a slow process though. Make some coffee !
I'm not complaining about the time as much as fearing something I did wrong or not. Right now I've enabled "prioritize update process" to see it works better or not. Will see the results in the next week OTA update.
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.
Thanks. I just updated my phone through the default system updater. I can confirm that all my Magisk settings, mods, and their configs are retained (including Widevine L1) and there's no issue.
Yessir, I still have this issue and was beginning to wonder if I was the only one, thanks for confirmation.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
25
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
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:7
The black screen of death has been fixed (or at least it should be). The OOS 13 kernel made it very easy to reproduce the issue.
The fix will be included in the next update (December 11).6This 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):
Reboot to recovery.Write down which slot you are currently on somewhere. You will need it in case the update does not boot correctly.Go to Apply Update > Apply from ADB, and use "adb sideload" to flash the newer build of LineageOS.If you installed Gapps or Magisk or any type of addon previously, go to Advanced > Reboot to recovery. Otherwise, select "Reboot system now".Go to Apply Update > Apply from ADB, and flash your modules the same way you flashed LineageOS.When you are done, select "Reboot system now".
- Reboot to bootloader. This can be done with "adb reboot bootloader".
- From there, use "fastboot --set-active=<slot>", replacing <slot> with the slot you were on previously.
- Reboot to system. You can just select "START" with the volume buttons and confirm by pressing the Power button.
5Starting 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.5Anyone 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/+/334681cwb-test.zip
drive.google.com
