[ROM][dumpling][9.0.X] LineageOS 16.0 (Pie) for Oneplus 5T

[crakerjac]

@2955732195, by default, Android is encrypting the device unless you specifically tell it not to. I don't know if it just encrypts the SD card or the system partition as well, but it's more than just the finger print lock. Older Android phones did not do this (by default) and it tends to lead to behaviors like what you are seeing.

For example, came from MSM Extended. When to migrate to LineageOS, I did a factory reset, flashed the FW, LineageOS then GAPPS. When I went to reboot, it brought me back to TWRP (same as you). I had to go into Advanced in TWRP and 'Format Data', which wiped my SD card (actually just user memory, but Android calls it the SD card). I then pulled the zip files back over via ADB, reflashed and I was up and running.

Is there any reason you are running AddonSU vs Magisk? Shouldn't you boot and run through the Android setup before flashing this anyways?

 

[2955732195]

@2955732195, by default, Android is encrypting the device unless you specifically tell it not to. I don't know if it just encrypts the SD card or the system partition as well, but it's more than just the finger print lock. Older Android phones did not do this (by default) and it tends to lead to behaviors like what you are seeing.

For example, came from MSM Extended. When to migrate to LineageOS, I did a factory reset, flashed the FW, LineageOS then GAPPS. When I went to reboot, it brought me back to TWRP (same as you). I had to go into Advanced in TWRP and 'Format Data', which wiped my SD card (actually just user memory, but Android calls it the SD card). I then pulled the zip files back over via ADB, reflashed and I was up and running.

Is there any reason you are running AddonSU vs Magisk? Shouldn't you boot and run through the Android setup before flashing this anyways?

sorry for giving a such delayed replay.
Im busy these days but i found that use codexwork's encryption TWRP works for me . As the AddonSU, i just thought that its release by lineageos team ,and it may has more stability or so....and i remember the offical document for AddonSU says that : FLASH AddonSU before your first boot or the system will crash and bootloop unlease you do a factory reset in TWRP. so i flashed it at the very begining

 

[Martezgarki]

sorry for giving a such delayed replay.
Im busy these days but i found that use codexwork's encryption TWRP works for me . As the AddonSU, i just thought that its release by lineageos team ,and it may has more stability or so....and i remember the offical document for AddonSU says that : FLASH AddonSU before your first boot or the system will crash and bootloop unlease you do a factory reset in TWRP. so i flashed it at the very begining

I faced the same issue with you. It wasn't caused by recovery version itself but it's broken Open GApps. I wasted a lot of time figuring out what's the cause, trying out variants of Open GApps to no avail, only to realize that some members mentioned you have to use older GApps (6th Oct release) few pages back. One of the reddit threads also mentioned this: https://www.reddit.com/r/LineageOS/comments/e6n0l4/warning_open_gapps_build_20191204_fails_to_boot. Sideloaded 6th Oct release instead and booted up fine. Would be immensely helpful if this was included in first post but I guess they should fix it soon.

 

[samnangseng]

Is the full screen gesture similar to OOS work on this rom? That's the only one feature that retain me from using this best rom.

 

[LV198]

Is the full screen gesture similar to OOS work on this rom? That's the only one feature that retain me from using this best rom.

Just Install the XDA "Navigation Gestures" app from Google Play. Works similar but has a lot more features for personalisation

 

[Jon1764]

...

 

[angry_goldfish]

Today I tried upgrading from lineage-16.0-20190908-nightly-dumpling-signed.zip to both lineage-16.0-20200120-nightly-dumpling-signed.zip and lineage-16.0-20200122-nightly-dumpling-signed.zip. This failed with the system auto-rebooting to recovery when Linage failed to boot.

I think these recent nightly images are just broken or require a full data wipe/reset.

 

[Prometheus]

Today I tried upgrading from lineage-16.0-20190908-nightly-dumpling-signed.zip to both lineage-16.0-20200120-nightly-dumpling-signed.zip and lineage-16.0-20200122-nightly-dumpling-signed.zip. This failed with the system auto-rebooting to recovery when Linage failed to boot.

I think these recent nightly images are just broken or require a full data wipe/reset.

If you tried it with 23rd GApps then GApps are the problem.

 

[angry_goldfish]

If you tried it with 23rd GApps then GApps are the problem.

I actually did download the 23rd's pico gapps, but I don't think that's the problem because I flashed without gapps for testing and it still had the problem. Further yet, I believe I flashed my old image with the 23rd's gapps and it was okay. In all I tried upgrading something like four times before I gave up. I just went back to my old nightly image and it was fine.

I have had similar problems with gapps in the past, so I had that in mind when I was trying to install.

I'll try with another set of images in a few days and if that doesn't work I'll try and figure out what it is from my /data/data that's buggering it all up.

 

[gene2]

What is the difference between the official twrp and the other twrp from codeworkx? i had problems with the official one. after booting the stock rom twrp was replaced with the stock recovery. twrp has write permissions. After flashing magisk.zip before booting the stock rom for the first timesolved the problem. Then i flashed lineage os 16.0 with that official twrp, wiped cache/data but the custom roms isn't booting. it ends with the lineage boot screen, then twrp starts. is this because of the wrong twrp?

 

[Lex_Michdeandroid]

I'm not sure if I'm old fashioned because I'm running Lineage 16 still, but I do so here I am.

This phone should have 4K DCI ability (or am I wrong?), but I only see 4K UHD. Also in OpenCamera I can't use DCI, just 4K UHD.

Does anyone know how to get the thing filming in DCI?

 

[Mentor.37]

very low volume

Yes it is.
I just made my first calls with my 2nd hand opo5t and I the sound is way too low. I could experiment with the volume values if I knew where to find them

Hi @giorgiosimeoni, same problem here, first calls with my 2nd hand opo5t with lo16 and the sound is way too low, obviously in the settings everything is already at max. Did you solved the problem? Is it an hardware or software problem?

 

[juan_rugge]

I just want to thank you. i'm really enjoying my phone again. ever since i update to stock Pie, my 5t felt like a mid-range, full of lag. LOS runs very fluid, and the battery it's AMAZING!!
BIG THANK YOU <3

 

[Lex_Michdeandroid]

So I wanted to backup my phone in twrp for the first time, but it gave me an error. (createtarfork 255 something)

It also asks me for the decryption pattern, but my usual pattern I use to open my phone doesn't work.

What is going on here?

Sent from my OnePlus 5T using XDA Labs

 

[crakerjac]

Any reason night builds for this have stopped?

 

[Specu3800]

Any reason night builds for this have stopped?

They've just started releasing LOS 17.1 for other devices, so probably they are working on one for our phone (other OnePlus devices already have it)

 

[crakerjac]

They've just started releasing LOS 17.1 for other devices, so probably they are working on one for our phone (other OnePlus devices already have it)

The maintainer for the 5/5T has already said he is busy with other items and it will likely be a while before we get an official LOS 17.x.

 

[Lex_Michdeandroid]

I'm getting the idea this phone isn't really popular in the community...

Sent from my OnePlus 5T using XDA Labs

 

[IanTester]

The maintainer for the 5/5T has already said he is busy with other items and it will likely be a while before we get an official LOS 17.x.

That's a shame. There has been an unofficial 17.x ROM but it hasn't been updated since mid January.

 

[InsaneNutter]

That's a shame. There has been an unofficial 17.x ROM but it hasn't been updated since mid January.

That's by codeworkx (the official maintainer for the 5T) and would eventually become the official rom when it meets the LineageOS charter, presuming development continues.