[ROM][OFFICIAL][enchilada][11] LineageOS 18.1

Search This thread

vikash1994b

Senior Member
Dec 7, 2012
1,022
615
29
New Delhi
Xiaomi Mi 3
Xiaomi Mi A1
Just want to say thank you for LuK1377, the ROM is REALLY GREAT ! The smoothness and new features of Android 11 makes me wanna stick to it, even though it's still in early development.

I'm running the latest build from today and just want to give my feedback about one point: even though the screen is set to time out in 30 seconds (in my case), it turns off and a second later, it turns on again without anyone touching the phone.
If I block my phone using the power button, it works correctly. If I wait the 30 seconds, it stays awake (phone not charging, stay awake option on dev options is off).

The battery life was also not great (when I was using the build from october 11th, still testing this one) but it's expected and I'm not concerned about it.

Thank you again LuK1337!
Not happening on 14th oct build.
 

Cygnust

Senior Member
Jul 22, 2008
691
97
Paris
OnePlus 6
Google Pixel 7 Pro

angourakis

Senior Member
Aug 16, 2010
229
118
São Paulo
Magisk 21 works for me just flashing in twrp.

For me , at least the official one, doesn't and I tried beta and canary versions. Just a modded version from another thread installs from twrp and boots fine.
And I don't want to risk running a modded version for a couple reasons:

1) security (not sure what else is inside the modded version
2) the module I use refuses to work on modded versions (energized)

I understand it's a bit more work to do patching the boot image everytime I update builds but, for me, it's worth it
 
Last edited:
  • Like
Reactions: cavjr08
D

Deleted member 8828390

Guest
Shouldnt there be a network permission in settings for apps? I seem to recall lineage had this earlier. I know some other roms do have this aswell.
Is it just not implemented, or not a planned feature at all?
 

Cygnust

Senior Member
Jul 22, 2008
691
97
Paris
OnePlus 6
Google Pixel 7 Pro
Hi guys,
Hi @LuK1337
i'm pretty lost.
I installed LineageOS 18.0 with twrp on my OP6 enchilada.

Decided to give a go to magisk, followed the patch boot method and when I rebooted my phone is stuck on "phone is starting"
When rebooting to twrp, it asks for a decryption password but mine does not work.

Made an adb logcat and it gives me "Failed to find provider info for com.android.contacts (user not unlocked)" (logcat attached)

Here's a complete summary :

Hi guys, I have a pretty serious problem with encryption
I'd like by all ways to avoid formatting my sdcard
long story short, I have a OnePlus 6, tried to flash LineageOS 18.0, it worked.
Then tried to flash magisk using the boot.img patched method then my phone launched LineageOS and phone was stuck on phone is starting.
I found out that my data was not decrypted, no matter what.
Tried to go back to OOS 10.3.6, but it doesn't boot, it's endlessly on the boot logo.
When I go to TWRP (official 3-4.0.3):
- when booted directly from the phone, twrp doesn't asks for a pin and gives me the data encrypted (seems like acting like OOS or LineageOS)
- when booted from fastboot twrp asks for a pin but my usual pin doesn't work.

I'm pretty screwed by now and can't boot my phone.
I'd like to avoid formatting my sdcard because my latests online backup are old

Many thanks for your help
 
Last edited:
D

Deleted member 8828390

Guest
Hi guys,
Hi @LuK1337
i'm pretty lost.
I installed LineageOS 18.0 with twrp on my OP6 enchilada.

Decided to give a go to magisk, followed the patch boot method and when I rebooted my phone is stuck on "phone is starting"
When rebooting to twrp, it asks for a decryption password but mine does not work.

Made an adb logcat and it gives me "Failed to find provider info for com.android.contacts (user not unlocked)" (logcat attached)

Here's a complete summary :

Hi guys, I have a pretty serious problem with encryption
I'd like by all ways to avoid formatting my sdcard
long story short, I have a OnePlus 6, tried to flash LineageOS 18.0, it worked.
Then tried to flash magisk using the boot.img patched method then my phone launched LineageOS and phone was stuck on phone is starting.
I found out that my data was not decrypted, no matter what.
Tried to go back to OOS 10.3.6, but it doesn't boot, it's endlessly on the boot logo.
When I go to TWRP (official 3-4.0.3):
- when booted directly from the phone, twrp doesn't asks for a pin and gives me the data encrypted (seems like acting like OOS or LineageOS)
- when booted from fastboot twrp asks for a pin but my usual pin doesn't work.

I'm pretty screwed by now and can't boot my phone.
I'd like to avoid formatting my sdcard because my latests online backup are old

Many thanks for your help
Did you wipe data?
Edit: currently regular magisk zip does not work. You need a modded one. You can find it it syberiaOS 11 thread.
Also, magisk will crash when opening, so enable airplane mode, change channel to stable in magisk, and disable airplane mode again.
 
Last edited by a moderator:

Cygnust

Senior Member
Jul 22, 2008
691
97
Paris
OnePlus 6
Google Pixel 7 Pro
Did you wipe data?
Edit: currently regular magisk zip does not work. You need a modded one. You can find it it syberiaOS 11 thread.
Also, magisk will crash when opening, so enable airplane mode, change channel to stable in magisk, and disable airplane mode again.

Hi,
I wiped data but not formatted sdcard.
For magisk, I made the patching method given before.

Now I'm screwed.
my analysis at the moment is that the phone doesn't ask for pin when not booted from fastboot.
That's why any os boots endlessly.
When booted from fastboot twrp asks for a pin lock but none works ..
Hope @LuK1337 has time to check my logcat and give an advice
 

LuK1337

Recognized Developer
Jan 18, 2013
8,940
18,141
Samsung Galaxy S III I9300
Moto G 2014
Hi,
I wiped data but not formatted sdcard.
For magisk, I made the patching method given before.

Now I'm screwed.
my analysis at the moment is that the phone doesn't ask for pin when not booted from fastboot.
That's why any os boots endlessly.
When booted from fastboot twrp asks for a pin lock but none works ..
Hope @LuK1337 has time to check my logcat and give an advice

Your whole /data is screwed up, format it.
11-01 12:30:03.276 595 595 I vold : List of Keymaster HALs found:
11-01 12:30:03.276 595 595 I vold : Keymaster HAL #1: Keymaster HAL: 3 from QTI SecurityLevel: TRUSTED_ENVIRONMENT HAL: android.hardware.keymaster@3.0::IKeymasterDevice/default
11-01 12:30:03.276 595 595 I vold : Using Keymaster HAL: 3 from QTI for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@3.0::IKeymasterDevice/default
11-01 12:30:03.282 635 635 E KeyMasterHalDevice: Begin send cmd failed
11-01 12:30:03.282 635 635 E KeyMasterHalDevice: ret: 0
11-01 12:30:03.282 635 635 E KeyMasterHalDevice: resp->status: -26
11-01 12:30:03.283 595 595 E vold : begin failed, code -26
11-01 12:30:03.283 595 595 E vold : Failed to find working ce key for user 0
11-01 12:30:03.283 595 595 E vold : Couldn't read key for 0
 
  • Like
Reactions: cavjr08 and darksx

coomac

Senior Member
Apr 9, 2011
118
65
OnePlus 8T
Google Pixel 6 Pro
Hi,
I wiped data but not formatted sdcard.
For magisk, I made the patching method given before.

Now I'm screwed.
my analysis at the moment is that the phone doesn't ask for pin when not booted from fastboot.
That's why any os boots endlessly.
When booted from fastboot twrp asks for a pin lock but none works ..
Hope @LuK1337 has time to check my logcat and give an advice
Looks like you have to format data no matter what. If you've been booting directly with "fastboot boot twrp.img", you can try doing "fastboot flash boot twrp.img" instead. That usually lets me decrypt in twrp to copy files out. If it doesn't work, RIP to your files. My condolences.
 

zhangzy

Member
May 7, 2018
41
7
I just flashed rom and nikgapps, and the phone app crashed. SMS cannot be sent and received. Contacts cannot be synchronized. The power button has no advanced restart options
 
did anyone try flashing with flamegapps? does flamegapps package work fine?

FlameGapps is rather buggy unfortunately. It probably varies per install. One occasion I installed it, it wouldnt boot into system at all. Another install with exact same steps reproduced and it booted for some reason. Im having zero issues with NikGapps as of right now, so I would suggest to stay with that for now until other gapp packages make progress.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 36
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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:
    8
    Guys I was checking out the gerrit and found something to be excited about.


    If I interpret it right, we should be included in the initial batch of devices being promoted to 19.1 🥳 and Luk1337 is probably staying our Maintainer.
    6
    Dear Forum, i plan to switch my OP6 back to LOS as well.
    Back, because once i bought it some years ago, i was running LOS on it, but then switched to OOS, due to some struggles (and it was the first phone since the good old Motorola Milestone, where CyanogenOS gave me Froyo for the first time :D ).
    I don't need root or anything extraordinary, just LOS and Google apps. my Question: will the build in updater work and preser Gapps during updates? In the past due to A/B Layout, i always had to go to recovery, flash update and gapps, reboot into Recovery, flash gapps again, to no loose them.
    And on my OP3 the builtin Updater is not working, i always have to flash manually through TWRP ;(
    Thanks in advance!
    GAPPS are preserved. If you dont need anything fancy, then also just use LineageOS recovery. This will most probably also fix your update isues on OP3.
    Also had a OP3 before and LOS recovery worked flawless.

    Slightly "offtopic":
    I was kind of afraid that our OP6 support was dropped, because nothing happened on the LineageOS Gerrit regarding our device. But Lukasz jsut pushed a whole lot of commits. So Android 12 seems inbound! (Whenever LOS team decides to release)
    4
    I always update via OTA. I always have to patch a new boot.img with Magisk and install via fastboot, but Gapps are kept.
    No need for fastboot. Go into the Magisk app before installing the OTA, click on Uninstall Magisk, then Restore Images. Now install the OTA via the built in updater. Once the OTA update is installed, do not reboot. Go back into the Magisk app. Click on Install Magisk, select Install to Inactive Slot (After OTA), and only then reboot.

    Full instructions can be found here: https://topjohnwu.github.io/Magisk/ota.html