[ROM][OFFICIAL][enchilada][12] LineageOS 19

Search This thread
Does SafetyNet validation work? Does Google Play (in Settings) show your device as verified?
You might also need to follow:
and wait for a day or so until it shows up in Play Store.
Safetynet works with universal safetynet fix Magisk module. I use exactly the same packages and modules as on 18.1, but in the 19.1 build something is different. :unsure:

P.S. If i use the ih8sn mod luk1337 with the following settings:
BUILD_FINGERPRINT=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys
BUILD_DESCRIPTION=OnePlus6-user 11 RKQ1.201217.002 2111252325 release-keys
BUILD_SECURITY_PATCH_DATE=2021-11-01
BUILD_TAGS=release-keys
BUILD_TYPE=user
BUILD_VERSION_RELEASE=11
BUILD_VERSION_RELEASE_OR_CODENAME=11
DEBUGGABLE=0
MANUFACTURER_NAME=OnePlus
PRODUCT_NAME=A6003
everithing is works as intended, but with this (I assume) I can't use magisk anymore...
 
Last edited:
May 8, 2014
43
19
Pune
I developed 'Can't open camera issues' on LineageOS 18.1. None of the apps could open the camera, tried restarting, app data clear, none of it helped. So I updated the os to latest 18.1 with a dirty flash, then to Lineage OS 19 with a dirty flash, the problem was still there. Then I did a clean flash and the problem is still there. Can anyone help? Also, miss the customization bits on os19.

EDIT - Another bug that I noticed is, I'm not getting Call notifications, the phone rings, but the call screen doesn't show up. I then need to wait for call to stop ringing, then open call log, and then redial.
Update to this - after installing the update, I was constantly facing forced restart issue. After booting, The phone would restart after 50-60 seconds. And that cycled continued. I clean flashed the rom once again and the issue was still there. but the error went away after half a day, on its own. So I continued using it ignoring the issue.


About camera not starting - The error did not resolve. after a few days, my front camera started, but not the back one. Whatsapp camera, when opened, used to stay stuck at the first frame that camera used to see. front camera worked perfectly. That led me to believing that there was no hardware issue.


After a few more days, the phone died after a day or two. I was in the office with no charger, the battery died on me (my bad) and the phone refused to turn on. tried 15 seconds long press, volume down+power button, both volume buttons+power button, but none of it worked. Although I did see a 'battery critically low' error once, I quickly put the phone on charging and tried to turn on the phone after 10-15 minutes, and no luck. tried overnight charging using original charger, and no luck.

Assuming that I had CrashDump error a few months ago and some mobile repair guys had worked on the motherboard, I thought it must be a hardware issue and gave the phone to the repair once again. They charged me 50$ saying that there was some sort of IC issue on the motherboard.

I feel like I may have panicked and have been scammed by the people at the repair shop. I should have tried unbrick tools first. But in my defense, the phone wasn't even connecting to the PC.

Have had a very bad experience with the phone in the last few weeks. During my crashdump error, the phone repair guy said that this error is very common for oneplus 6 devices. I'm planning on getting a new phone now, and not a oneplus device for sure. I had glorious 6 years of oneplus one and then oneplus 6 died early on me. Also, not a fan of the direction where oneplus is going right now.
 
Last edited:
  • Like
Reactions: sid4306

bformz

Member
Sep 17, 2012
28
2
Hi, I upgraded from 18 to 19...everything went rather smoothly....I am having a hell of a time getting Magisk to work though...I tried sideloading it, it said that it was installed but when I launch the app it still says N/A. I tried patching the recovery.img and boot.img, it did the same thing, said it installed but still shows NA. Is anyone else having issues getting Magisk to work with 19? Maybe there are some leftover files of magisk causing issues?
 

madman

Senior Member
Apr 21, 2011
1,652
466
Planet Earth
OnePlus 5
OnePlus 6
Hi, I upgraded from 18 to 19...everything went rather smoothly....I am having a hell of a time getting Magisk to work though...I tried sideloading it, it said that it was installed but when I launch the app it still says N/A. I tried patching the recovery.img and boot.img, it did the same thing, said it installed but still shows NA. Is anyone else having issues getting Magisk to work with 19? Maybe there are some leftover files of magisk causing issues?
Have you tried uninstalling Magisk using the uninstall.zip method mentioned in their documentation? Maybe that will clean up the thing properly? And after its cleaned up, try sideload?

 

Spaceoid

Senior Member
Mar 29, 2013
345
118
Dortmund
Have you tried uninstalling Magisk using the uninstall.zip method mentioned in their documentation? Maybe that will clean up the thing properly? And after its cleaned up, try sideload?

I tried exactly that a few days ago, but instead of uninstalling, the renamed manager.apk just sideloaded Magisk. XD Not sure though if user error of if uninstalling via zip is not supported anymore.
 

Forage

Senior Member
May 18, 2012
150
32
Hi, I upgraded from 18 to 19...everything went rather smoothly....I am having a hell of a time getting Magisk to work though...I tried sideloading it, it said that it was installed but when I launch the app it still says N/A. I tried patching the recovery.img and boot.img, it did the same thing, said it installed but still shows NA. Is anyone else having issues getting Magisk to work with 19? Maybe there are some leftover files of magisk causing issues?
If you tried patching recovery.img and boot.img it sounds to me that you are not following the provided installation instructions properly since you only need to patch boot.img. If you have indeed not followed the instructions from start to finish I can't help but ask just in case: did you make sure you flashed the patched boot.img from your computer after getting it patched by the Magisk app?
 
  • Like
Reactions: Spaceoid

Imotep95

Senior Member
Sep 14, 2012
1,681
2,682
Belgrade
I have video and audio stutters in youtube and yt music. This happened when I turned off phone for a day and then started using it again. Same happened on other roms, I used msm tool to go back to stock and then to los19. Is it a known bug?
Ok i disabled transcoding and its fine now.
Screenshot_20220628-004933_Settings.png
 
  • Like
Reactions: sid4306

Spaceoid

Senior Member
Mar 29, 2013
345
118
Dortmund
Just to confirm - after having sideloaded Magisk last week, after this week's OTA Magisk and root are still kept, no need to flash to inactive slot or anything.
Still I do not understand why I couldn't re-install it via patched boot.img last week after OTA. The ways of Magisk are mysterious.
 
  • Like
Reactions: olifee and lm089

Spaceoid

Senior Member
Mar 29, 2013
345
118
Dortmund
Super super minor thing, but since the latest LOS update yesterday I cannot set my system wallpaper through the system gallery anymore. The option is gone.
Not a big deal, I can still do it via the system settings (or supposedly even with a different gallery app), but I thought I'd mention it here.
 
  • Like
Reactions: olifee
I am confused with the Magisk posts here. Can someone clarify?

Which version of Magisk should I use on 19.1?
Can I just sideload or do I need to patch boot.img?
Should I uninstall Magisk before upgrading 18.1 to 19.1?

I am currently on LOS 18.1 with Magisk 24.1 and Zygisk (with root hiding issues). I plan to upgrade to 19.1.
 

Spaceoid

Senior Member
Mar 29, 2013
345
118
Dortmund
I am confused with the Magisk posts here. Can someone clarify?

Which version of Magisk should I use on 19.1?
Can I just sideload or do I need to patch boot.img?
Should I uninstall Magisk before upgrading 18.1 to 19.1?

I am currently on LOS 18.1 with Magisk 24.1 and Zygisk (with root hiding issues). I plan to upgrade to 19.1.
Both 24.3 and 25.1 work perfectly fine with LOS 19.1. I guess I'd recommend 25.1 as it's the newest stable.
You can either sideload or do the patched-boot.img method. If you sideload, Magisk will survive any further OTA. Sideloading is apparently not officially supported anymore, though, so it might be that this method will cause problems in the future. Flashing a patched boot.img is the official way of getting Magisk. It is a little more work for an OTA, though (just google "Magisk OTA" and read the official instructions).

Sadly I do not know if you should better uninstall Magisk before upgrading, I did a clean flash to LOS 19.1.
 
  • Like
Reactions: elmzahn

madman

Senior Member
Apr 21, 2011
1,652
466
Planet Earth
OnePlus 5
OnePlus 6
I am confused with the Magisk posts here. Can someone clarify?

Which version of Magisk should I use on 19.1?
Can I just sideload or do I need to patch boot.img?
Should I uninstall Magisk before upgrading 18.1 to 19.1?

I am currently on LOS 18.1 with Magisk 24.1 and Zygisk (with root hiding issues). I plan to upgrade to 19.1.
I upgrade from 18.1 to 19.1. There was no need to do uninstall Magisk. As I originally sideloaded Magisk (and thus this can survive usual OTAs) Magisk was working out of the box on 19.1 for me. Now if your Magisk survived usual 18.1 -> 18.1 upgrades, you probably did the same.

Magisk is something that you can fix later. Just make sure to follow the guide (and specifically not booting into LOS before flashing GApps if you had them).
 
  • Like
Reactions: elmzahn

Chris Kerry

Senior Member
Nov 23, 2010
71
19
Greetings.
With some difficulties, I finally got v.19-20220621 nightly to install and run with NikGApps and Magisk smoothly. Everything is running perfectly (no reboots others report, etc).
However, the Google speech services installed from the playstore keeps force closing. Ivona TTS, that I've used for years on all my other phones, also force closing when installed.
Thus, I presently don't have any tts that can be used. This is a big problem for me because I usually get apps to read aloud articles for me when on the move.
Any solutions?
PS: Clean install EXACTLY as stated. Also, no titanium backup restores from previous. No (extra) Magisk modules installed (apart from the main Magisk itself).
 
Last edited:

madman

Senior Member
Apr 21, 2011
1,652
466
Planet Earth
OnePlus 5
OnePlus 6
Greetings.
With some difficulties, I finally got v.19-20220621 nightly to install and run with NikGApps and Magisk smoothly. Everything is running perfectly (no reboots others report, etc).
However, the Google speech services installed from the playstore keeps force closing. Ivona TTS, that I've used for years on all my other phones, also force closing when installed.
Thus, I presently don't have any tts that can be used. This is a big problem for me because I usually get apps to read aloud articles for me when on the move.
Any solutions?
PS: Clean install EXACTLY as stated. Also, no titanium backup restores from previous. No (extra) Magisk modules installed (apart from the main Magisk itself).
I have Google Speech Services installed and I don't see any force closes. The only difference here I can think of is you are not using recommended GApps package. Is there any special reason that you want to use NikGApps? If you don't have any, maybe you can try dirty flashing MindTheGapps version or do clean flash and use MTG. The dirty flash is risky business, so hopefully you have things backed up (considering you just flashed things, you probably do).
 

lm089

Senior Member
The dirty flash is risky business, so hopefully you have things backed up
I tried the other day using the official NikGapps uninstall method from their FAQ pages, then flash MTG. That sort-of worked but some google part constantly reminded me to finish my phone setup, which I never could accomplish. Back at Nik now.
Sadly, clean flash seems to be the only way to switch gapps solutions
 

Chris Kerry

Senior Member
Nov 23, 2010
71
19
Does
I tried the other day using the official NikGapps uninstall method from their FAQ pages, then flash MTG. That sort-of worked but some google part constantly reminded me to finish my phone setup, which I never could accomplish. Back at Nik now.
Sadly, clean flash seems to be the only way to switch gapps solutions
Does "clean flash" necessarily involve factory reset with LOS recovery? That is a big difficulty for me because repopulating my internal storage is a full day's job.
I am unaware of LOS recovery permitting just a cleaning of data, cache and system partitions (excl. Internal Storage), as TWRP could. OTOH, can I use TWRP to erase those partitions, for both A & B, and then using LOS recovery to flash on the ROM & MGapps: would this also be "clean install"?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I've also experienced the notification sound crackling issue, but only on first install.

    The first time I installed (maybe 3-4 builds ago), the OTP, trust, and setup notifications during/after the setup process were all very crackly. I tried calling the phone and sending it messages too, all the notifications crackled. Then I tried a media audio stream (YouTube video in the browser), and it sounded fine. Immediately after that, the notifications started sounding fine too.

    The next day I did another clean flash, and I had the same crackling notifications during the setup process. This time, I didn't try anything else, just started a Swift Backup restore and left my phone for half an hour. When I came back, the notification sounds were perfectly fine. 🤷‍♂️

    Edit: Forgot to mention, I have no problems with notifications now, and I leave my phone on ring mode for most of the day.
    2
    Okay, I managed to restore the backup. I'll post my exact steps for reference, perhaps it'll help someone. Perhaps even future me, when I get into this mess again.

    TL;DR: Keep system installation zip for each backup you wish to be able to restore.

    So, I had two backups, newer based on LOS from 28.06 and older based on LOS 15.06. I had an install zip with LOS version from 15.06, but I didn't have one from 28.06 and it was already gone from LOS download site.

    1. First, I copied everything from internal storage onto my computer. This procedure will wipe data and sdcard so copy your twrp backups and other data to avoid losing it.
    2. Rebooted to fastboot (power+volume up)
    3. Flashed LOS recovery: fastboot flash boot ./lineage-19.1-20220615-recovery-enchilada.img
    4. Booted to recovery (from fastboot)
    5. Used factory reset option (this will wipe your data including internal memory, backup your data)
    6. Flashed the same version of LOS as was in the older backup adb sideload adb sideload ./lineage-19.1-20220615-nightly-enchilada-signed.zip (used install update option)
    7. Rebooted recovery (switches active slot)
    8. Flashed gapps adb sideload ./MindTheGapps-12.1.0-arm64-20220605_112439.zip
    9. Flashed again the same version of LOS as was in the older backup adb sideload adb sideload ./lineage-19.1-20220615-nightly-enchilada-signed.zip (now in the second slot)
    10. Rebooted recovery (switches active slot)
    11. Flashed gapps again adb sideload ./MindTheGapps-12.1.0-arm64-20220605_112439.zip
    12. Went through initial setup in the OS - didn't set any pin
    13. Rebooted to fastboot adb reboot bootloader
    14. Booted TWRP fastboot boot twrp-3.6.2_11-0-enchilada.img
    15. It didn't decrypt data partition
    16. Flashed TWRP: advanced -> flash current TWRP
    17. Rebooted recovery - it decrypted data now
    18. Sideloaded magisk (because I had it in my backup, not sure if that's needed) adb sideload Magisk-v25.0.apk
    19. Downloaded the older backup (with LOS from 15.06) onto the phone adb push ../2022-07-03--19-28-17_lineage_enchilada-userdebug_12_SQ3A22060500/ /sdcard/TWRP
    20. Restoring data alone didn't work (system didn't finish booting)
    21. Restoring boot, system, data worked
    22. Rebooted twice for proper working system
    Now I had a working system with a month old backup, but I wanted to restore the newer backup for which I didn't have the system install zip. I'm sure it worked by an accident but I'll post my steps. They were taken right after I confirmed that a month old backup is restored and is booting properly.
    1. First I switched to the other slot in TWRP.
    2. Made a backup of the key store so that TWRP will be able to decrypt data: adb pull /data/system/recoverablekeystore.db .
    3. Restored only data from the newer backup
    4. Restoring data overwrote the keystore so I backed this one up as well: adb pull /data/system/recoverablekeystore.db ./recoverablekeystore.db.from_backup
    5. Pushed original keystore (AFAICT this enables TWRP to decrypt the data): adb push ./recoverablekeystore.db /data/system/recoverablekeystore.db
    6. Rebooted to system, however it didn't finish booting
    7. Rebooted to recovery (it decrypted the data)
    8. Restored keystore from backup: adb push ./recoverablekeystore.db.from_backup /data/system/recoverablekeystore.db (effectively this is the same as restoring data from backup again at this point)
    9. Restored system and boot from newer backup
    10. Rebooted to system and it booted properly.
    Now, I'm certain that some of these steps are not needed, however I have a working system now and I can't spend any more time to narrow it down. It weird that it worked, since I tried similar steps while first flashing newest LOS (27.07) and when I restored system+boot I got into recovery bootloop.

    For now, it seems that the only working way to restore backup is to first have system installation zip. Perhaps some shenanigans with keystore could work, but I couldn't work that out.

    Thanks to @lm089 and @tabletalker7 for their instructions.
    2
    That got me thinking:
    Just tried to use the alert slider every other hour, and voila: No more issues until now.
    Although it's not a perfect solution, it works fine for me.

    Thanks a lot!
    So this evening I let my phone sit in loud mode for around 4 hours and did not notice any sound issue. Might be the time span was too small, or it is somewhat not a general problem...

    Edit: The same evening, I received a SMS without receiving a notification! I just saw it right now after opening the SMS app. First time it happens. As I read further above, this might be a kinda known issue. Still never happened to me before, and I communicate lots via SMS.
    Still, might also be I swiped the notification away by accident. :D

    Edit2: I found this regarding the SMS 'issue', which is quite interesting:
    https://www.reddit.com/r/LineageOS/comments/n5dttk Seems to be a long-known bug with the stock SMS app of LOS. Two different fixes are offered, too, either via ADB command or by switching to a different, third-party messaging app.
    1
    i am on latest oos what instructions do i need to follow to upgrade to 19.1 safely without errors ?
    This is the guide for you:

    If you follow it closely, no errors or problems should arise.
    1
    Any chance to have Wireguard kernel implementation?
  • 37
    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 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:
    6
    Just did a dirty flash from LOS 18.1 and everything works fine.

    I had to reinstall some Google apps (YouTube, Gmail, Keep, GCam, Photos), as they stopped working after the upgrade (maybe because I accidentally clicked No on the Signature verification failed screen while flashing Gapps and didn't notice, then the OS didn't boot. whoops. So I went back into the recovery and flashed Gapps again. Sure enough, the install went through. So be careful and make sure to click the correct button, lol)

    Everything else seems to work perfectly!

    Thanks again LuK for your work!

    In case anyone with Gapps and Magisk wants to try a dirty flash from 18.1, here are the steps I did:
    (you're on your own if things break! better to do a clean flash! magisk isn't officially supported!)

    1. Restored images in Magisk
    2. Removed PIN and fingerprints
    (Not sure if these first two steps are needed, but did them just in case)
    3. adb reboot sideload
    4. adb sideload lineage-19.1-20220426-nightly-enchilada-signed.zip
    5. Advanced->Reboot to Recovery
    6. Apply Update->Apply from ADB
    7. adb sideload MindTheGapps-12.1.0-arm64-20220416_174313.zip
    8. adb sideload Magisk-v24.3.apk
    9. Back->Reboot system now
    5
    I'm using a single SIM and I see the same thing often. I guess it depends on the amount of icons you have in the status bar. I observed this since the first build
    Change the smallest width to 411 in developer options.
    Before OOS 11 it was set to 411 by default but that changed with OOS11.
    4
    I'm on the May 17th enchilada nightly, and came directly from 18.1. I'd like to use ANT+, but no worky :confused:. Is this a known issue? Are there plans to fix it?

    ANT+ also didn't work when I went from 17.1 to 18.1, but I fixed it by upgrading the firmware. I tried that again on 19, but it didn't fix it this time.

    Here is what the ANT Tester app shows on LOS 19:

    View attachment 5619435
    4
    Question: Will there ever be more stable versions than the "nightlies"? I'm unsure where to put them in terms of quality and stability- should they be considered as "alpha" versions? Or are they even more reliable than "betas"?

    Thanks in advance.
    imo the first 2 nightlies were perfectly stable. No crashes, fc, excessive battery drain, whatever. (y)