[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T

[diziet_sma]

Today I rebooted into recovery but instead found myself in a fast boot loop, could only power off or get fastboot menu, i managed to reflash twrp 3.5.2_9.0 using fastboot from pc and now i can get into recovery, but the contents of /sdcard are a lot of wierdly named folders:
cheeseburger:/ # ls sdcard/
2HkwtsC8kSQA3pe0LlPspA 9YqEbihMy5FRu8yDZP1k5B Fv1Px9jslw+06iARBiRrlB Mp9GPbudSTC9o+SNug2tZA XY,aR,pPfmitPk53R,GWDA aYNWkkMV4GsBVD09ZLeipA e+rFsqA3RXAesW4wu8w,sD qf6JC45Wlb7+rUkWGswiJC
2y+WuEpoF37TuSyufFe,HB AB696CEuBUShOIpJivLr8C H2RFRFT5Ygei4z27vg1lvA NjJ9oA2tYzoDcjdy+tuvwD YKtUFgl2PUlFF,PA0+AAQA dE5sE,dl6sT2OEtYsGukbB fq4L5m2dZ2FrcoqugkJzUB zXw6pZc1bafEaAlHYzY4WA
3ZJoZA7WrLHf7iktdUXhOC EuHOHWxt,jhLEietoXeZvD HNJqI1rT39V6TRdd2u,nVA W1LYk7CsztHidpCjcLDH3A ZNUDOttOYzQ9bMoR4R,nED dxb1gPfxSvU+3nZaIpcmsC gkkbiVEqwZuDBbDlmU5pGC
cheeseburger:/ #

these look like encryption keys to me
the twrp log says:
updating partition details...
...done
enablefilecrypto_failed
full selinux support is present
mtp enabled

and that's it.
needless to say the phone won't reboot into system,
is there a way that i can at least get off my phone the user data using adb - which now show the device after reflashing the recovery

diziet

further to this I pulled the partition that is mounted on /data and mounted it on my pc:

Spoiler

[root@mycroft diziet]# mount -t ext4 phone.img testdir/
[root@mycroft diziet]# ls testdir/
adb/ dalvik-cache/ magisk_backup_261e63b9c32738c38ee0feb0f778620f750609c5/ magisk_backup_a213c837e0620f483af8c0f081f59c2ea0a2bced/ misc_de/ system/
adbroot/ data/ magisk_backup_2a1ab4fbaff22f63edf4c44ced2c7d77c45e2c57/ magisk_backup_c600b21274dd5b70b8db717e04ecfa75898bd54c/ nfc/ system_ce/
anr/ dpm/ magisk_backup_3691b52a653e8eb818f26b85c7864de68a82bbf7/ magisk_backup_c79e5cd7ae833a4598bdf1e215baa48ac18cf1b1/ ota/ system_de/
apex/ drm/ magisk_backup_3bff959bc7f980d722f8c5d3eab6781559b80482/ magisk_backup_d1ff2bad9a208ecce4db0892ff819088974a45e9/ ota_package/ tombstones/
app/ gsi/ magisk_backup_3fe961c7fb4f7623d28abeb17819801b6f5e1d65/ magisk_backup_d8517d11d87c5b7fe8c4fc6348c2666c9cad05a3/ per_boot/ unencrypted/
app-asec/ incremental/ magisk_backup_4c3f0880b016bf9eb6aa4c2f0db2b9ba88eae686/ magisk_backup_def75c34259e2b3a89a6bd54c3ad991ff68bb4e8/ preloads/ user/
app-ephemeral/ lineageos_updates/ magisk_backup_514fb2e1d90cb399c3d34195e680769cbb8557aa/ magisk_backup_e3ba97144decbc61fd6a6c7d5658da98d3107c0a/ property/ user_de/
app-lib/ local/ magisk_backup_58fa9bc927ebbb216046d9eb2cf489fb7a4b671c/ magisk_backup_f2a87f92ef6f56164d1f65c869d9d6966e43d204/ resource-cache/ vendor/
app-private/ lost+found/ magisk_backup_6db98efd436e8db43677bef0753074f65377f38b/ magisk_backup_f62d85a36ff8ef5de6ed3c1ba96058864587a2a7/ rollback/ vendor_ce/
app-staging/ magisk_backup_04fd473160b700a8b5e7ecf970f27ac3a4533ff8/ magisk_backup_8a40ad3814dc1c1720f10d5d0de6e6a2fb8ba0e9/ media/ rollback-observer/ vendor_de/
backup/ magisk_backup_1083a24e57c6b75a913f5e904ef76494b3eb83fe/ magisk_backup_9a2ec9366fa84eac8885ab2feeee25f105c4bde7/ mediadrm/ server_configurable_flags/
bootchart/ magisk_backup_1b077aa144282cf592ca199bcc0b33a76a6dd15f/ magisk_backup_9ca87e5724ece724f189f1f376ce018d8ad3cdca/ misc/ ss/
cache/ magisk_backup_1dcedf37ff51bf3a64127b14ece5830e7e8a33ad/ magisk_backup_9d418b7a288cd31fca09df7623a0b54c11e24d1d/ misc_ce/ ssh/
[root@mycroft diziet]#

although the directories have readable names they are all full of files like the ones in my first post.

according to this:

Spoiler

[root@mycroft diziet]# ls testdir/media/0/
2FFyNvizm-vzBetpxtWb9hEaUB7YjOEW/ 9jCRKhc1DUHFWz9xP7Il7NO6CESBGK1l/ IvjqRLu-TCIa1lgkyVS4wQbVQPfZ4okp/ PljL5hk7LSSevxasCtzRBXishcMuD__s/ vBhW2o4QpWD2QcItK_CkBAF36tFL-bAp/ ZhV6w0J8s74dkbPE35U6O9kO0WKs4ZJb/
4Nr43H-fsl3qpycCnlvltvsrRVoGC4uJ/ aBqW8LmXLVaEeziHFbf_GC6E6LXo5WXv/ jOn3H-XiFTBWvWDkLrBze4hdKozcMhw3/ skcUpWZxw8xAoPe6QLgBJYUOkibiu6y8/ vJBwmB-ZJ8FHk6hIvU53X-lT1HW2-58V/ zJlK97yDWkRZQw1O2zrYDPUbg0Z49J_E/
8HEiKiOiYS-27FsukaLFvU-uJLtf4f1H/ dO0nDKm5klx3lqAZsFvrcny7SLYddYWO/ lqxom5kZWHmHHRVRMeUY6In4bO8vWJcv/ svuiESFpj_uY0lIFWNoPVRbF_wC0DwAQ/ XjoFq0fdp2UX9mvRnz6fKbYPmd_Rb1gD/ ZrlpNg7D3XE9phKbGDJyXkQuLw_ZU5N5/
9IBVz_y7FGwgSW5iRahw5g7BNpQmlaeG/ ehp_vWpemXBM2hvP5nbSJPSoLzUuaLcZ/ MP8YHdZt2kFdvNXg88XSS_n3mWlIypms/ utKuAIVanSufii-5aXeZXawcqrogmcxU/ xMSSQzHW5YbNmPQoYLfYjA7c2Ml-677w/
[root@mycroft diziet]# du -sh testdir/me
media/ mediadrm/
[root@mycroft diziet]# du -sh testdir/media/0/
27G testdir/media/0/
[root@mycroft diziet]#

my stuff still seems to be there, but either corrupted or encrypted, but I thought that android did encryption on partitions not files, but how can a fully working phone reboot into a situation like that?

 

[nic2873]

further to this I pulled the partition that is mounted on /data and mounted it on my pc:

Spoiler

[root@mycroft diziet]# mount -t ext4 phone.img testdir/
[root@mycroft diziet]# ls testdir/
adb/ dalvik-cache/ magisk_backup_261e63b9c32738c38ee0feb0f778620f750609c5/ magisk_backup_a213c837e0620f483af8c0f081f59c2ea0a2bced/ misc_de/ system/
adbroot/ data/ magisk_backup_2a1ab4fbaff22f63edf4c44ced2c7d77c45e2c57/ magisk_backup_c600b21274dd5b70b8db717e04ecfa75898bd54c/ nfc/ system_ce/
anr/ dpm/ magisk_backup_3691b52a653e8eb818f26b85c7864de68a82bbf7/ magisk_backup_c79e5cd7ae833a4598bdf1e215baa48ac18cf1b1/ ota/ system_de/
apex/ drm/ magisk_backup_3bff959bc7f980d722f8c5d3eab6781559b80482/ magisk_backup_d1ff2bad9a208ecce4db0892ff819088974a45e9/ ota_package/ tombstones/
app/ gsi/ magisk_backup_3fe961c7fb4f7623d28abeb17819801b6f5e1d65/ magisk_backup_d8517d11d87c5b7fe8c4fc6348c2666c9cad05a3/ per_boot/ unencrypted/
app-asec/ incremental/ magisk_backup_4c3f0880b016bf9eb6aa4c2f0db2b9ba88eae686/ magisk_backup_def75c34259e2b3a89a6bd54c3ad991ff68bb4e8/ preloads/ user/
app-ephemeral/ lineageos_updates/ magisk_backup_514fb2e1d90cb399c3d34195e680769cbb8557aa/ magisk_backup_e3ba97144decbc61fd6a6c7d5658da98d3107c0a/ property/ user_de/
app-lib/ local/ magisk_backup_58fa9bc927ebbb216046d9eb2cf489fb7a4b671c/ magisk_backup_f2a87f92ef6f56164d1f65c869d9d6966e43d204/ resource-cache/ vendor/
app-private/ lost+found/ magisk_backup_6db98efd436e8db43677bef0753074f65377f38b/ magisk_backup_f62d85a36ff8ef5de6ed3c1ba96058864587a2a7/ rollback/ vendor_ce/
app-staging/ magisk_backup_04fd473160b700a8b5e7ecf970f27ac3a4533ff8/ magisk_backup_8a40ad3814dc1c1720f10d5d0de6e6a2fb8ba0e9/ media/ rollback-observer/ vendor_de/
backup/ magisk_backup_1083a24e57c6b75a913f5e904ef76494b3eb83fe/ magisk_backup_9a2ec9366fa84eac8885ab2feeee25f105c4bde7/ mediadrm/ server_configurable_flags/
bootchart/ magisk_backup_1b077aa144282cf592ca199bcc0b33a76a6dd15f/ magisk_backup_9ca87e5724ece724f189f1f376ce018d8ad3cdca/ misc/ ss/
cache/ magisk_backup_1dcedf37ff51bf3a64127b14ece5830e7e8a33ad/ magisk_backup_9d418b7a288cd31fca09df7623a0b54c11e24d1d/ misc_ce/ ssh/
[root@mycroft diziet]#

although the directories have readable names they are all full of files like the ones in my first post.

according to this:

Spoiler

[root@mycroft diziet]# ls testdir/media/0/
2FFyNvizm-vzBetpxtWb9hEaUB7YjOEW/ 9jCRKhc1DUHFWz9xP7Il7NO6CESBGK1l/ IvjqRLu-TCIa1lgkyVS4wQbVQPfZ4okp/ PljL5hk7LSSevxasCtzRBXishcMuD__s/ vBhW2o4QpWD2QcItK_CkBAF36tFL-bAp/ ZhV6w0J8s74dkbPE35U6O9kO0WKs4ZJb/
4Nr43H-fsl3qpycCnlvltvsrRVoGC4uJ/ aBqW8LmXLVaEeziHFbf_GC6E6LXo5WXv/ jOn3H-XiFTBWvWDkLrBze4hdKozcMhw3/ skcUpWZxw8xAoPe6QLgBJYUOkibiu6y8/ vJBwmB-ZJ8FHk6hIvU53X-lT1HW2-58V/ zJlK97yDWkRZQw1O2zrYDPUbg0Z49J_E/
8HEiKiOiYS-27FsukaLFvU-uJLtf4f1H/ dO0nDKm5klx3lqAZsFvrcny7SLYddYWO/ lqxom5kZWHmHHRVRMeUY6In4bO8vWJcv/ svuiESFpj_uY0lIFWNoPVRbF_wC0DwAQ/ XjoFq0fdp2UX9mvRnz6fKbYPmd_Rb1gD/ ZrlpNg7D3XE9phKbGDJyXkQuLw_ZU5N5/
9IBVz_y7FGwgSW5iRahw5g7BNpQmlaeG/ ehp_vWpemXBM2hvP5nbSJPSoLzUuaLcZ/ MP8YHdZt2kFdvNXg88XSS_n3mWlIypms/ utKuAIVanSufii-5aXeZXawcqrogmcxU/ xMSSQzHW5YbNmPQoYLfYjA7c2Ml-677w/
[root@mycroft diziet]# du -sh testdir/me
media/ mediadrm/
[root@mycroft diziet]# du -sh testdir/media/0/
27G testdir/media/0/
[root@mycroft diziet]#

my stuff still seems to be there, but either corrupted or encrypted, but I thought that android did encryption on partitions not files, but how can a fully working phone reboot into a situation like that?

I had a similar problem in an older version and reflashed LineageOS and GApps. But do a TWRP backup to an external sdcard before doing anything just in case...

 

[smolley]

Same here. This has been going on for some weeks now. Before that (September/October) the ROM was achieving more like 2.5 days of battery life.
It simply doesn't enter deep sleep (this is over night, ignore the updater as that is happening the last two minutes only):

Same issue with me, the battery drains very rapidly. I'm going to try going back to an older build.

Also, my phone no longer rings when getting phone calls so I don't know I have someone calling me until a get a voicemail notification. Outgoing calls work fine.

 

[js-xda]

Huge battery draw after charging. Any idea?
Reboot and vipe dalwik/cache twrp helping but only to next charging

Same here. This has been going on for some weeks now. Before that (September/October) the ROM was achieving more like 2.5 days of battery life.
It simply doesn't enter deep sleep (this is over night, ignore the updater as that is happening the last two minutes only):

Same issue with me, the battery drains very rapidly. I'm going to try going back to an older build.

Also, my phone no longer rings when getting phone calls so I don't know I have someone calling me until a get a voicemail notification. Outgoing calls work fine.

No such issues here using cheeseburger running build of 20211122 (before 20211108 and 20211011) and NikGApps core. Battery lasting most of the time more than 2 days with my regular use pattern.

 

[debby_]

Huge battery draw after charging. Any idea?
Reboot and vipe dalwik/cache twrp helping but only to next charging

OK. Looks like - Dec 6 build fixed problem.

 

[side]

i cant boot lineage 18.1 zips .... i use latest twrp from twrp.me , wiped everything, installed zip, installed gapps and rebooted. but nothing happened. stay at splash and then reboot to recovery i am coming from stock 8.0

i also tested full wipe + lineage zip , without gapps.
any ideas?

 

[LV198]

i cant boot lineage 18.1 zips .... i use latest twrp from twrp.me , wiped everything, installed zip, installed gapps and rebooted. but nothing happened. stay at splash and then reboot to recovery i am coming from stock 8.0

i also tested full wipe + lineage zip , without gapps.
any ideas?

You came from Stock Android 8.0? Then I would recommend that you first upgrade to latest stock. There were significant changes in Stock ROM since then that are necessities for Lineage os.

 

[js-xda]

Updating cheeseburger from build 20211122 to 20211220, I had a one-time-issue:

After unlocking upon restart, there were frequent "black screens" - just black for a very short moment and also not accepting input (e. g. during entering PIN where I knew where to push). I rebooted into recovery, wiped Dalvik/ART and rebooted to system. Since then (6 h 30 min), issue is gone. Can't say whether a reboot alone would have been sufficient. Only difference to a typical boot after an update for me was that the phone was on SIM lock screen for quite a while (10 min?) before I unlocked SIM and device.

Reporting just in case more users have this issue.

 

[CharlesDicken]

OK. Looks like - Dec 6 build fixed problem.

I'm still getting battery drain.

Can other confirm it's fixed?

 

[rlewis19]

Hi,
I'm currently using a 5T with oos 9.0.11. At one time I was running oos 10.0.1 but had significant problems receiving calls and texts consistently. It was so bad I had oneplus revert my phone back to 9. I saw in the prerequisites for LOS 18.1 to be at the latest 10 firmware. I'm concerned that doing so will reintroduce the spotty call and text situation. If I go from oos 9.0.11 to LOS 18.1, am I just asking for trouble?

Thank you,
R

 

[djlooka]

I'm still getting battery drain.

Can other confirm it's fixed?

I also experienced an abnormal battery drain with all builds after the 6th of December.
Reverting to that build "fixes" it. If I were you I'd at least download a copy of it before it disappears from the official servers.

OT: I also noticed 2 more issues (these have been around for a while).
1) the "state machine" behind the earpiece/loudspeaker toggle gets messy at times and after a call in which I go from, e.g. speaker to loudspeaker, I cannot go back to speaker and all subsequent calls only use the loudspeaker from then on. This affects also other apps (e.g. music player/newpipe only emitting audio through the earpiece).
I only found 3 workarounds:
i) use the phone dialer, start a call and quickly toggle the loudspeaker on/off before the tone goes off, and immediately terminate the call;
ii) plug/unplug the audio jack;
iii) reboot the phone.

2) this might very well be unrelated, but when I make a call using Signal while on 4G, very often (but not always!) the callee cannot hear me if I was the one to place the call (I can hear them OK). If they call me instead, there are no issues. Everything works when the call is started while using the WiFi.

I'm sharing the above 2 issues here in case anyone else has experienced them: if that's the case I can put together a proper bug report.

 

[eagledipesh]

I also experienced an abnormal battery drain with all builds after the 6th of December.
Reverting to that build "fixes" it. If I were you I'd at least download a copy of it before it disappears from the official servers.

OT: I also noticed 2 more issues (these have been around for a while).
1) the "state machine" behind the earpiece/loudspeaker toggle gets messy at times and after a call in which I go from, e.g. speaker to loudspeaker, I cannot go back to speaker and all subsequent calls only use the loudspeaker from then on. This affects also other apps (e.g. music player/newpipe only emitting audio through the earpiece).
I only found 3 workarounds:
i) use the phone dialer, start a call and quickly toggle the loudspeaker on/off before the tone goes off, and immediately terminate the call;
ii) plug/unplug the audio jack;
iii) reboot the phone.

2) this might very well be unrelated, but when I make a call using Signal while on 4G, very often (but not always!) the callee cannot hear me if I was the one to place the call (I can hear them OK). If they call me instead, there are no issues. Everything works when the call is started while using the WiFi.

I'm sharing the above 2 issues here in case anyone else has experienced them: if that's the case I can put together a proper bug report.

I am also facing similar issues you mentioned in point 2

For point 1 it's not critical hence never noticed such issues

 

[rlewis19]

Hi,
I'm currently using a 5T with oos 9.0.11. At one time I was running oos 10.0.1 but had significant problems receiving calls and texts consistently. It was so bad I had oneplus revert my phone back to 9. I saw in the prerequisites for LOS 18.1 to be at the latest 10 firmware. I'm concerned that doing so will reintroduce the spotty call and text situation. If I go from oos 9.0.11 to LOS 18.1, am I just asking for trouble?

Thank you,
R

Has anyone else had any issues with the 5t's latest firmware and receiving calls or texts consistently?

 

[eagledipesh]

Hello all,

For those who wants to use stock oneplus camera, you can use version below 3.4.25, any version after this 3.8 and above wont wont.

Known issue : Portrait mode is broken, it doesn't detect 2nd cam....

you can search for the app version on apk mirror.

Some of you might already know this, however i though of sharing it for those who are not aware.

 

[albe1628]

Hi guys,
my op5 with lineage is not recognized by windws ?
What can i do ?

 

[Sketch85]

I flashed the ROM yesterday. Everything works fine except wifi. If I want to connect to my own wifi which is dual band (2,5GHz/5GHz) the connection is continously dropping and reconnecting (every 10 seconds).

If I connect to my guest wifi, which is the same router and dual band as well it is working.

Anybody with a similar issue?

 

[avuman]

Interested in this rom possibly. I couldn't find a clear answer searching through this thread, but does SMS with VoLTE work? Can encryption also be enabled?

 

[madman]

Interested in this rom possibly. I couldn't find a clear answer searching through this thread, but does SMS with VoLTE work? Can encryption also be enabled?

Yes encryption works out of the box as this is official LOS. I don't know if you can decrypt stuff afterwards and stuff like that as I never tried it (no performance reasons to do so).

About VOLTE, this is very sketchy corner of networking where there is no real standard implementation by carriers. For me VOLTE worked just fine (besides the issue on first call after reboot which has a workaround). VOLTE is going to be very much dependent on carrier that you are using but most of the major carriers should work just fine. I don't know what is SMS with VOLTE specifically but yeah I have sent SMS when my phone was connected to LTE if that is what you are looking for.

 

[capdcanoa]

Do you know how to pass safetyNet with Magisk?
I installed magisk module made by kDrag0n but in our phone it doesn't work. I would like to use Google pay.
Thank you.

 

[madman]

Do you know how to pass safetyNet with Magisk?
I installed magisk module made by kDrag0n but in our phone it doesn't work. I would like to use Google pay.
Thank you.

Searching the thread for word safetynet would have answered the question