yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Just ignore the FBE error message. It's a bug in SAR TWRP (search for FBE in the TWRP thread). The error message only displays on unencrypted phones.

As to your other issue. Possible explanation. If you've formatted the data partition and then (without having booted the system) copied files across, they get written to /data/media.

But a booted system has /sdcard as /data/media/0. So your "missing" files may still be there.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
New promotions batch (other one was abandoned & split) this one is merged already

https://review.lineageos.org/c/LineageOS/hudson/+/271384

This is the batch OP3 is in, not merged yet:

https://review.lineageos.org/c/LineageOS/hudson/+/271387
[OnePlus 3 & 3T Cross Device Development] 19Gonzo82:
Yesterday I clean flashed this ROM together OpenGapps nano and Magisk 20.3. The setup always crashed and looped at the point when the Google assistant is to be configured. I clean flashed again with the same result. Any ideas what could be the reason?
[OnePlus 3 & 3T Cross Device Development] pijas82:
You want magisk for what?
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
The way it works for me is to boot to recovery before every flash. Also when upgrading the rom I have to clean flash and then restore data, otherwise it won't boot (using SAR-TWRP). Couldn't tell you why.
[OnePlus 3 & 3T Cross Device Development] 19Gonzo82:
Root access for various apps.
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
It looks like with the Android 10 builds of LineageOS, it will be viable to use the LineageOS Recovery instead of TWRP. Question is though, is the LineageOS recovery signed with the AOSP Verity key like the latest versions of TWRP are? Signing with the AOSP Verity key means the bootloader can be relocked safely and Recovery will continue to function normally.
[OnePlus 3 & 3T Cross Device Development] punio4:
Isn't LineageOS recovery only for A/B devices?
[OnePlus 3 & 3T Cross Device Development] :
Most probably: yes. (16.0 recovery is signed and I don't see any reason why 17.1 shouldn't be signed.)

If it's not (I really don't think so), take a look at this flashable zip for signing the boot i,age, it's not too hard to adopt it for signing the recovery.
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
Thanks [MENTION=4405529]nvertigo67[/MENTION], I am hopeful then as I also don't see why they wouldn't sign the 17.1 branch recovery too.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
https://www.reddit.com/r/LineageOS/comments/fpfpva/broken_lineageos_171_builds/
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
and the countdown is on... https://review.lineageos.org/q/owner:johnsonnolen%40gmail.com+batch

==> https://www.lineageoslog.com/17.1/oneplus3

Thanks to [MENTION=5091734]dianlujitao[/MENTION] and the LineageOS team!
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
off topic but since lineage is shipping it's own recovery so should we flash the recovery also whenever nightlies will rollout if we intend to stick with lineage eco system.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I believe it doesn't apply to our device (A only). See the section on recovery in https://lineageos.org/Changelog-19/
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
As far as i know all devices updating to lineage-17.1 must support lineage recovery but maintainer can suggest twrp as alternative. Moreover, TWRP's compatibility with lineage updater is a concern since it gave a lot of headache on 16.0 cycle.
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
In fact, the downloads page for the OnePlus 3(T) now offers a LineageOS Recovery download for respective 16.0 releases.

Good question. Personally, I'd rather use the LineageOS Recovery if I were to use LineageOS, much like OEM ROMs use their own OEM Recovery respectively. It does raise some questions however, such as:

Will it automatically overwrite whatever Recovery is present once LineageOS boots for the first time (I assume not, or wonder if possibly this is where the Maintainer's preference for suggesting TWRP could influence such behaviour).

When performing System OTA Updates, will the Recovery also be updated (Like OEM ROMs), or just the System itself?
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
TWRP is still recommended, lineage recovery does NOT support FDE thus you might encounter problems when installing magisk and opengapps
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
Darn, that's a bummer. Probably shouldn't be offered on the downloads page then, or least there should be an official warning on the Wiki or something. It does seem to contradict the claim that all LineageOS 17.1 devices must support the LineageOS Recovery if such an issue exists, although I guess the criteria is it must merely be bootable (Or compatible with LineageOS alone)?

Oh and thank you so very kindly for doing such an excellent job supporting our aging, yet still brilliant phones and congratulations to you and the LineageOS team on the upcoming release!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
So I installed the recovery, just to see what it looks like. It's definitely not a replacement for TWRP - it's too minimal. May be fine for flashing (I didn't try it), but no option to backup and restore.

I couldn't take screenshots (which TWRP allows), so you'll have to try it out for yourselves.
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
I imagine it looks similar to CyanogenMod's old Recovery? Would you be willing to test its behaviour when FDE is indeed used?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
My phone is encrypted and the recovery doesn't ask me for my password, so it can't see anything in the data partition.

And I'm not going to try an OTA because I'm on another rom.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
NIghtly 17.1 builds are on their way.

Yay (Now let's hope it's not some kind of sick April Fools joke.)

You kan monitor the first nightly 17.1 build here: https://www.lineageoslog.com/17.1/oneplus3
[OnePlus 3 & 3T Cross Device Development] punio4:
If I understood correctly, you'd need a locked bootloader to pass SafetyNet, but that also breaks TWRP and updating LOS.

I was hoping that using Lineage Recovery would enable system updates with a locked bootloader.
[OnePlus 3 & 3T Cross Device Development] :
Twrp works with locked bootloader since more then half a year. The ota issue on los16 is related to twrp, encrypted data and secured boot (aka boot password), and doesn't relate to locked/unlocked bl by any means. Since los recobery doesn't support encryption, it can't solve the ota issue on encrypted data partitions.
[OnePlus 3 & 3T Cross Device Development] punio4:
Oh. So using TWRP with no encryption and locked bootloader would enable me to use LOS OTA / dirty flash and pass safetynet without needing magisk hide?

Altho using Gpay with no encryption sounds like a horrible idea.
[OnePlus 3 & 3T Cross Device Development] Flippiej:
If I read things right our device is one of the few that should be able to relock the bootloader signed and everything (to keep the new safetynet measures happy) while keeping TWRP and LOS installed.

I'm not sure what the correct way to implement this would be, but I'm going to look into it before flashing 17.1.

edit: Already answered above, ignore my post.
[OnePlus 3 & 3T Cross Device Development] :
I've lost track if backuptools in los17 are fixed. If so: yes. If backuptools are still broken: no.

The save ways is: use the update app for downloadimg and flash the updated rom manually.
[OnePlus 3 & 3T Cross Device Development] TheAvengingTITAN:
Its still queued, hasn't even started from what I can see.

Check this link to see what has been queued, what has been successfully built, and what has failed: https://buildkite.com/lineageos/android/builds?branch=lineage-17.1&page=2
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
I may have been wrong. I thought all the 17.1 nightly builds were failing. I was looking at https://buildkite.com/lineageos/android-nightly but it looks like I should have checked https://buildkite.com/lineageos/android instead.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
https://buildkite.com/lineageos/android/builds/21200#c6f6c1d7-d4e2-4748-96e8-8e7ae730ea00

Build is running
[OnePlus 3 & 3T Cross Device Development] pijas82:
Yeah ,thanks
[OnePlus 3 & 3T Cross Device Development] TheAvengingTITAN:
https://buildkite.com/lineageos/android/builds/21200#c6f6c1d7-d4e2-4748-96e8-8e7ae730ea00

The build was successful, now just gotta wait for it to show up on the downloads section :)
[OnePlus 3 & 3T Cross Device Development] ContactFront:
Success!
[OnePlus 3 & 3T Cross Device Development] moso11:
The build is up: https://ftp.acc.umu.se/mirror/lineageos/full/oneplus3/20200401/
[OnePlus 3 & 3T Cross Device Development] pijas82:
Time to wait official announcement ?
[OnePlus 3 & 3T Cross Device Development] :
Imagine that's april fools build
[OnePlus 3 & 3T Cross Device Development] Vasu D:
Built is up:good:
[OnePlus 3 & 3T Cross Device Development] ContactFront:
Sneak peek of the announcement

https://review.lineageos.org/c/LineageOS/www/+/267504/55/_posts/blog/2020-04-01-Changelog-24.md
[OnePlus 3 & 3T Cross Device Development] pijas82:
Official
[OnePlus 3 & 3T Cross Device Development] :
No. Most probably same procedure as los16, los15 and los14.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
So, just dirty flashed the official 17.1 over 16.0 but I'm still on TWRP 3.2.x

Everything seems to work flawlessly, should I flash the new modded recovery linked at the beginning of this thread or lineage recovery?
[OnePlus 3 & 3T Cross Device Development] pijas82:
Dirty flash ? , you need twrp for gapps and magisk if you want
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Dirty flash (wipe cache, dalvik cache and system + flash LOS 17.1 build, gapps and magisk + restart system) = ok

Mobile data, wifi and bluetooth networks = ok

Camera = ok

Sound = ok

GPS = ok

Safetynet status = passed

Everything seems to work flawlessly but need time to evaluate LOS 17.1 on OP3 in depth!

My config : OnePlus 3T / FW 9.0.6 / TWRP 3.3.1-1 / ext4 / unencrypted / BL locked / LOS 17.1 build / open gapp nano / Magisk_v20.4

Edit : add "my" procedure of dirty flash.
[OnePlus 3 & 3T Cross Device Development] TheAvengingTITAN:
Official Download is here!

https://download.lineageos.org/oneplus3
[OnePlus 3 & 3T Cross Device Development] :
How do you know? Apart from the snap issue, which has shown up after two dirty major version changes, it's pretty short to claim dirty flashimg is working...
[OnePlus 3 & 3T Cross Device Development] punio4:
Everything seems to work fine. Locking the bootloader with TWRP passes SafetyNet, but WhatsApp seems to complain about a custom ROM.

It still has the green tint that LOS16 had in night mode:

https://gitlab.com/LineageOS/issues/android/-/issues/872

Was hoping that would get fixed with a new android version.

EDIT:

It's actually much worse:

https://imgur.com/a/l45YVTA
[OnePlus 3 & 3T Cross Device Development] remedya:
Thanks, useful information. I can't get VoLTE and VoWiFi on the Three UK network even though I switched on the appropriate switches. I was getting VoLTE on the final build of OxygenOS. Are you getting these to work? If so, is there an icon?
[OnePlus 3 & 3T Cross Device Development] knpk13:
Clean flashed April 1 build with April 1 Nano opengapps. Works fine but during setup, it won't let me continue if I don't setup voice match. If I click on skip it just keeps looping back to the last setup page. I'm guessing it's a gapps bug though.
[OnePlus 3 & 3T Cross Device Development] votz11:
i made a clean flash, 17.1 first build + open gapps pico + magisk , all great but cts false, any idea how to pass ? thanks

edit: cts cant pass with nvertigo67 patches https://xdaforums.com/showpost.php?p=78433987&postcount=3
[OnePlus 3 & 3T Cross Device Development] thesplitter:
I'm not really claiming that it's working, merely wanted to see how it managed the jump :)

Will probably make a full format in a while, so far I don't see weird crashes.

You still suggest to flash the modded TWRP then?
[OnePlus 3 & 3T Cross Device Development] Vasu D:
Same for me too.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Did you ever see VoWiFi working on OOS? I'd be surprised if you did. I've never seen it work on Three unless the phone was purchased from them and using their modified Firmware. VoLTE was working on custom ROMs on Pie, but Three restrict the 800Mhz Band that they use for VoLTE. If you're in an area that can get an 1800Mhz (normal 4G) signal, or a 3G signal, you will never connect to the 800Mhz Band. It's prioritised lowest.

I've given up hope that the custom ROM community will figure out what secret sauce Three are adding to their Firmware to make VoWiFi work. I don't think we'll ever see it on our ROMs.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5091734]dianlujitao[/MENTION]:

There is a mismatch of

https://github.com/LineageOS/androi...b/lineage-17.1/init/init_oneplus3.cpp#L53-L54

and

https://github.com/LineageOS/androi...us3/blob/lineage-17.1/lineage_oneplus3.mk#L36

[MENTION=9805762]votz11[/MENTION] and [MENTION=9190178]Vasu D[/MENTION]:

Try setting ro.build.fingerprint in /system/build.prop to https://github.com/LineageOS/androi.../blob/lineage-17.1/init/init_oneplus3.cpp#L53 or https://github.com/LineageOS/androi.../blob/lineage-17.1/init/init_oneplus3.cpp#L54 and reboot.

If it works, it works. If you expirience issues: use the modded one. Official 3.3.1-1 seems to have - at least partial - sar support; I wouldn't recommend using something prior to this.
[OnePlus 3 & 3T Cross Device Development] punio4:
Install magiskhide props config and run it.
[OnePlus 3 & 3T Cross Device Development] moso11:
Did you get it fixed?
[OnePlus 3 & 3T Cross Device Development] votz11:
[MENTION=7858776]punio4[/MENTION] thanks for the tip

so.. to pass safetynet easy, just:

open magisk >> settings >>enable Magisk Hide , close magisk app and open it again , i dont install any module

cts: true

go to google play store app info, force stop it, clear storage and cache , open google play store and update some apps, cts will pass
[OnePlus 3 & 3T Cross Device Development] :
a Question about Lineage recovery because I still not completely understand it.

As I understand, both TWRP or Lineage recovery can be installed on OP3T and combined with every rom.

WHen installed, for both the bootloader can be locked again to pass safetynet, but will only work in combination with Lineage?

Still not completely clear how the process works...
[OnePlus 3 & 3T Cross Device Development] votz11:
for Adaway app enable 'systemless hosts in Magisk Manager settings', reboot your device and try again

OnePlus 3T / FW 9.0.6 / TWRP 3.3.1-1 / ext4 / LOS 17.1 build / open gapp pico / Magisk_v20.4
[OnePlus 3 & 3T Cross Device Development] BillGoss:
The ability to work with a locked bootloader is all about the keys used to sign the software. Official TWRP, Los, and Los recovery are signed with the correct keys, so they work with a locked phone.

The recovery partition is separate from the rom and not used by the rom itself. So it's up to you what recovery you use.
[OnePlus 3 & 3T Cross Device Development] mangokm40:
Does "ext4" mean there is something I can install that will allow ext4 formatting of the SD card?

Thanks.
[OnePlus 3 & 3T Cross Device Development] votz11:
ext4 mean that i have my cache, data , system all to ext4 form
[OnePlus 3 & 3T Cross Device Development] Dirk:
If you have an SD Card in your phone you're either in the wrong forum or you've made a mess of your SIM Tray! :p
[OnePlus 3 & 3T Cross Device Development] pijas82:
Safety test without magisk
[OnePlus 3 & 3T Cross Device Development] mangokm40:
Hahaha.....Thanks! I forgot about this phone doesn't have it. LOL :silly:
[OnePlus 3 & 3T Cross Device Development] knpk13:
Nope. I just setup the voice match and proceeded with the setup. I deleted the voice match data in the Google app afterwards. This happened last week too when I clean flashed an unofficial version of LOS 17. Not sure if the opengapps team is aware of it. I'll check their thread and ask there.

Update:

Apparently been happening to some people since last month.

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/post82159535
[OnePlus 3 & 3T Cross Device Development] pijas82:
Fixed flash magisk 20.4 beta
[OnePlus 3 & 3T Cross Device Development] pijas82:
What happened?
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
Darn I guess the build got pulled right after I installed it. Maybe because of the build.prop mismatch? I dunno.
[OnePlus 3 & 3T Cross Device Development] pro_drive:
The file lineage-17.1-20200401-nightly-oneplus3-signed.zip 404 not found now.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
it doesn't hurt, the .mk one is just a placeholder and expected to be overridden by the .cpp one

-------------------------

all 17.1 builds were removed because /system can't be mounted rw on some devices after flash due to signing, not sure if op3 is affected but still got removed.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
FYI ... https://www.lineageos.org/Changelog-24/

Upgrading to LineageOS 17.1

To upgrade, please follow the upgrade guide for your device found here ... https://wiki.lineageos.org/devices/oneplus3/upgrade

If you’re coming from an unofficial build, you need to follow the good ole’ install guide for your device, just like anyone else looking to install LineageOS for the first time. These can be found here ... https://wiki.lineageos.org/devices/oneplus3/install

Please note that if you’re currently on an official build, you DO NOT need to wipe your device.

If you are installing from an unofficial build, you MUST wipe data from recovery before installing.

Thanks to [MENTION=5091734]dianlujitao[/MENTION] and the LineageOS team!
[OnePlus 3 & 3T Cross Device Development] TheAvengingTITAN:
So I dirty flashed the official build over the latest unofficial build by dianlujitao.

Literally just wiped cache partitions, flashed the official build, gapps and magisk. I haven't run into any issues so far whatsoever. So what exactly is wrong with flashing over the unofficial build? Am I missing something?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Yeah well, I've done that as well, no major issues aside from the battery going down significantly at a rate of 1% every minute with the screen on. Logcat is also full of errors.

Sure, a dirty flash from 16.0 jumping 2 major versions all the way to 17.1 is feasible, the phone will boot up and nothing is lost. It IS impressive.

But I wouldn't suggest that, so many things are different and so many things can go wrong unnoticed.
[OnePlus 3 & 3T Cross Device Development] TheAvengingTITAN:
Yeah coming from 16.0 or 16.1 straight to 17.1 by dirty flashing is a no-no to me since it's almost become a rule of thumb to me that with every major android version, I gotta start fresh.

But yeah no issues whatsoever on unofficial to official 17.1 builds so far, despite them stating that "If you are installing from an unofficial build, you MUST wipe data from recovery before installing".
[OnePlus 3 & 3T Cross Device Development] punio4:
Gesture navigation back isn't working.

There's also the following string in the notification shade: 10 (QQ2A.200305.003)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It's part of the build number (About phone).
[OnePlus 3 & 3T Cross Device Development] moso11:
Has anyone got QuickSwitch working on 17.1?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Firstly, thanks [MENTION=5091734]dianlujitao[/MENTION] for, again, having our phone on the first official build.

I did a clean install because a dirty flash on [MENTION=4244522]pitrus-[/MENTION] Los 17.1 (which I've happily used for the past two months) failed to boot.

It's nice to see that tap and pay using NFC is working nicely.

The thing I notice that hasn't changed since the first build of 17.1 is that the Gallery app has an empty timeline and that it still shows all the images for album art in the Music directory (I think this last point is a bug with the media scanner, not Gallery).

The other issue I noticed is that the Files app is unresponsive for a few minutes after a clean install (is it waiting for something, possibly the media manager?).

Other than that I've had no problems.

I would like to mention that I think the LineageOS wiki installation page is a problem because it points to the official TWRP download.

TWRP 3.3.1-1 works fine for installing and backing up the system, but it cannot restore a system partition backup properly - the phone won't boot and Rescue Party drops you back in TWRP. We saw this when the experimental 17.1 first came out.

We still need to use the TWRP SAR version (https://androidfilehost.com/?w=files&flid=104480&sort_by=date&sort_dir=DESC) to effectively backup and restore the system partition.

I can just see lots of comments from new 17.1 users when they can't restore their backups.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Is it OK to use the pulled build then? Does dirty flashing a newer build fix it or do you recommend clean flashing again?
[OnePlus 3 & 3T Cross Device Development] bjo81:
Dirtyflashed my OP3 yesterday with the 17.1 build and pico-OpenGapps. Had to clean data/cache for google play store and everything else went smooth.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
After having massive battery drain and Christmas tree like errors on the logcat I would refrain to write in the wiki that it's a good idea to dirty flash the 17.1 over the official 16.0

I had to format and everything runs smoothly now.

I would write in the upgrade wiki that it's highly suggested to wipe data.
[OnePlus 3 & 3T Cross Device Development] bjo81:
Which massive drain did you have? The drain on my OP3 seems normal at the moment.
[OnePlus 3 & 3T Cross Device Development] unimke:
New build is up!
[OnePlus 3 & 3T Cross Device Development] Roman91:
Bootloop after a dirty flash over an official 16.0.

So care

[MENTION=5091734]dianlujitao[/MENTION] Thanks for keeping our phones alive
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About LOS 17.1, I have the same feeling as [MENTION=2911853]BillGoss[/MENTION]... Great work!

About TWRP, I agree but SAR TWRP is not compatible with pre-10 ROMs. So this information should be clearly stated on the LineageOS wiki installation page.

About OTA updater, it is working correctly from lineage-17.1-20200401-nightly-oneplus3-signed to lineage-17.1-20200402-nightly-oneplus3-signed.

Note: I performed a dirty flash from official LOS 16 to official LOS 17.1

My dirty flash: wipe cache, dalvik cache and system + flash LOS 17.1 build, gapps and magisk + restart system (twice)

My config: OnePlus 3T / FW 9.0.6 / TWRP 3.3.1-1 / ext4 / unencrypted / BL locked / LOS 17.1 build / open gapps nano / magisk
[OnePlus 3 & 3T Cross Device Development] pijas82:
So, new version its safe for install. I'm on 01 /04 build , and I will clean flash
[OnePlus 3 & 3T Cross Device Development] thesplitter:
My issue probably was because of the gapps that I had installed, I had the stock package, after the upgrade I had to flash micro.

The battery drain seemed caused by some constant errors on gapps, that's why after a data wipe everything went well.

The wiki should be updated just because many users may have different configurations, if 10 of them had no apparent issues at all after a dirt flash 16.0>17.1 and other 40 had issues of various kinds because of their many different configuration, it is safe to suggest to everyone that a data wipe is suggested and a dirty flash may be cause of issues.

I have however to congratulate for this 17.1 to all maintainers of LineageOS quite the achievement to have this stability on a just released ROM.

Yes, I also agree on the fact that the wiki should also mention about SAR TWRP.