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

olifee said:

Does SafetyNet validation work? Does Google Play (in Settings) show your device as verified?
You might also need to follow:

Google Play Certification

What it is, and how it affects you

lineageos.org

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.

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

Click to expand...

everithing is works as intended, but with this (I assume) I can't use magisk anymore...

JordiMas said:

How can you say it's working fine???

Because it IS working fine on my phone, didn't have a single forced reboot since quite a few weeks now. No probs with auto rotation

aniruddhavispute said:

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.

bformz said:

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?

madman said:

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?

Installation

The Magic Mask for Android

topjohnwu.github.io

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.

bformz said:

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?

elmzahn said:

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.

elmzahn said:

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).

Chris Kerry said:

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).

Click to expand...

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).