yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Rated R:
is this ok?

https://drive.google.com/open?id=1QKddGfFWadIiVYy66NCcplqdQMWOeYbK

I have only changed log buffer size to 4 MB and reboot twice
[OnePlus 3 & 3T Cross Device Development] Zelete:
Same here, just tried a full wipe of all partitions, installed lineage from 21/06, installed open_gapps-arm64-9.0-nano-20190622 (no Magisk or custom kernels), booted and setup phone, and SELinux is Disabled.

Trust shows this als a notification alert and a red icon in Trust settings.
[OnePlus 3 & 3T Cross Device Development] Rated R:
Have you got 3 or 3t?
[OnePlus 3 & 3T Cross Device Development] Zelete:
3T
[OnePlus 3 & 3T Cross Device Development] Rated R:
Me too, this could be a clue
[OnePlus 3 & 3T Cross Device Development] Phalaea:
Before I do this: Will my internal storage (sdcard) be wiped at this point of the tutorial? Because I get an error (can't find some files) when pulling /sdcard/data with adb pull so I don't have a complete backup of my internal storage. Is the backup with adb pull only in case something goes wrong or will I definitely need it in step 13/14?
[OnePlus 3 & 3T Cross Device Development] Dirk:
The only thing you absolutely need from Internal Storage is your Nandroid Backup. Anything else is purely personal files that you might not want to lose. The App data that is stored on Internal Storage is handy to transfer back as it might save you having to setup your App Settings/Defaults again.
[OnePlus 3 & 3T Cross Device Development] Rated R:
I have found this on jyra

https://gitlab.com/LineageOS/issues/android/issues/849
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=2715579]Rated R[/MENTION] and [MENTION=4557929]Zelete[/MENTION]

A few questions:

TWRP = 3.3.1-0 ?

Did you flash 9.0.3 fw BL locked or unlocked ?

Did you flash 9.0.3 fw before or after build ?
[OnePlus 3 & 3T Cross Device Development] wistlo:
I voted "remain"---er, "wait"-- in this forum's Migrate to official Pie firmware for now with risk of losing data? poll, but this guide looked straightforward and it was! Many thanks to the folks in this thread who got this working (I spent more time reading posts to catch up up on the history than I did actually performing the upgrade). . I am now running my 3T on 9.0.3 FW, 20160621 LOS. I ran into a couple of logistical issues mostly Windows 10 related, so I put in some notes in italics below. If I a step is hidden, that means it worked exactly as described in the OP:

''
[OnePlus 3 & 3T Cross Device Development] Dirk:
What's your selinux state having done that?
[OnePlus 3 & 3T Cross Device Development] Zelete:
Hey, I'm on TWRP 3.3.1-0. Bootloader was unlocked when I flashed 9.0.3.

I flashed the fw before I think the 16th. Today I wiped and clean flashed everything.
[OnePlus 3 & 3T Cross Device Development] Rated R:
1) Yes

2) BL is unlocked

3) Before
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Like me and SELinux = Enforcing on my side...
[OnePlus 3 & 3T Cross Device Development] Rated R:
3 or 3T?
[OnePlus 3 & 3T Cross Device Development] :
There's something really strange with your logcat. The system part is completely missing. Your log starts with:

--------- beginning of main

My logs start with

--------- beginning of system

If you just type "adb logcat -d", what do you see in the very first line? If you use an app for logs, check with the documentation how to get an uncrippled log, please.
[OnePlus 3 & 3T Cross Device Development] wistlo:
Enforced

"Enforcing"

See screenshot:

Not directly related: I do have root access, but through Magisk 19.3. I thought the status used to indicate that (probably a change in Magisk?).

I have a PIN lock screen, but no boot PW, so I have a caution "needs secure lock screen" on encryption.
[OnePlus 3 & 3T Cross Device Development] Rated R:
--------- beginning of system is after, row 74

I provided you that logcat with logcat -d command
[OnePlus 3 & 3T Cross Device Development] :
:good:

That would explain, why I can't reproduce this. I'm still using: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

[MENTION=371528]Everybody[/MENTION] suffering from selinux stuck on permissve: are you using an unlocked bootloader?

[MENTION=371528]Everybody[/MENTION] using a locked bootloader: what's your selinux status?

---------- Post added at 14:00 ---------- Previous post was at 13:56 ----------

Wow. Strange. I don't say it's wrong, but I've never seen that before. From the timestamps (and the logcat order) system always happens before main on my device.
[OnePlus 3 & 3T Cross Device Development] Rated R:
Oh god, with oxygenos-9.0.3-bl-km-5.0.8-firmware-3T.zip

SElinux is enforcing

!!!! 3T and BL unlocked
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
3T ... see my signature.

Edit: my 9.0.3 fw = https://www.celsoazevedo.com/files/android/oneplus3t-modem-firmware/
[OnePlus 3 & 3T Cross Device Development] :
:angel:

Can you switch nfc on?

I think I need to update my mantra from "gapps suckz" to "9.0.x bootloader and keymaster suckz".... :silly:

---------- Post added at 14:10 ---------- Previous post was at 14:08 ----------

Is your bl locked?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Unlocked ... Of course ... ;)
[OnePlus 3 & 3T Cross Device Development] Zelete:
I'm sorry I'm a noob, but is oxygenos-9.0.3-bl-km-5.0.8-firmware-3T.zip safe to flash for Lineage? I'm going to clean install everything again then with this fw.
[OnePlus 3 & 3T Cross Device Development] Rated R:
NFC toogle works
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
https://www.celsoazevedo.com/files/android/oneplus3t-modem-firmware/

Edit: for a clean flash, use this one or [MENTION=4405529]nvertigo67[/MENTION]'s fw (https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164)
[OnePlus 3 & 3T Cross Device Development] mumapizza:
9.0.3 firmware

06.19. lineageos build

locked bootloader

Pico gapps

3.3.1 twrp

nfc works
[OnePlus 3 & 3T Cross Device Development] :
He isn't asking for a link to the firmware, but if it's safe to use the modded fw from here: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

Answer: for me it's working great since about 3 weeks. So: yes, it's safe to use. But if a clean flash is planed anyway, you might consider what I've written here: https://xdaforums.com/showpost.php?p=79769987&postcount=9

It's better to ask modded fw related questions in the modded fw thread: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
[OnePlus 3 & 3T Cross Device Development] Dirk:
I think you're committed to a clean install with format /data at this point. Using:

twrp 3.3.1-0

fw 9.0.3

los 2016-06-21

...as you were planning.

Edit: The version of TWRP you were using (3.2.3-1) will break Encryption if you format with it, so make sure you are on the newer build before you begin.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
An alternative :

==> https://xdaforums.com/showpost.php?p=79748697&postcount=2468
[OnePlus 3 & 3T Cross Device Development] mordax777:
Hello everyone,

I was trying to update from lineage-16.0-20190614 to lineage-16.0-20190621.

But I am getting this error message in teamwin recovery(3.2.3-10):

Updater process ended with ERROR: 7
Error installing zip file '@/cache/recovery/block.map

image: imgur. com /DZtHt13

Can someone tell me what the problem could be, I am not so experienced in this?

Many thanks.
[OnePlus 3 & 3T Cross Device Development] :
Read the two or three lines before Error 7. Most probably firmware. If so, start reading before updating the firmware.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
*** Be careful ***

From build 20190616, a new firmware (9.0.3 fw) is required. Otherwise you'll get error 7 when installing the zip

The 9.0.3 fw update is not trivial and can cause damage (i.e. you can brick your device !)

So take the time to read this thread before flashing the new firmware.

First, read this post (https://xdaforums.com/showpost.php?p=79736966&postcount=2382) and the following ones.

For example:

https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

https://xdaforums.com/showpost.php?p=79748697&postcount=2468

https://xdaforums.com/showpost.php?p=79769445&postcount=2516
[OnePlus 3 & 3T Cross Device Development] Dirk:
Who demoted you to lvl 1 tech support? You're putting noobs like me out of a job! :p

Thanks are owed to everyone in the thread who got on top of this firmware update business so quickly. Because of your efforts we already know the potential pitfalls, bugs and workarounds. That means for the majority of users the information they need is already out there, before they even need it. Not just on LOS but all LOS Based ROMs that will shortly be experiencing the same challenges.

Great team effort everyone. Pats on the back all round. :good:
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Hey [MENTION=1763460]Dirk[/MENTION], you think you're just Tier 1? Come on, you're already Tier 2 ;)
[OnePlus 3 & 3T Cross Device Development] bendodge:
FYI, I just updated my wife's OP3T from 5.0.8 and 2019-06-15 to current. Storage was not encrypted.

First, I locked the bootloader. After flashing 9.0.3 + 2109-06-21, the launcher crashed every time the PIN was entered. Flashing back to 5.0.8 and restoring a full TWRP backup didn't fix it. Solution was to delete the following files from /data/system:

locksettings.db
locksettings.db-shm
locksettings.db-wal

Removed lockscreen PIN entirely, then flashed to 9.0.3 and 2019-06-21. No issues enabling PIN again afterwards.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I refuse to improve my standing in life. I am, have always been and will always be, a bottom-rung, working class grunt. :)

Which is a problem as i also refuse to take orders. (You can see how that might be awkward).
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
What's your selinux state now? ... (Settings > Security & location > Trust)

Bootloader unlocked or locked ?
[OnePlus 3 & 3T Cross Device Development] Roman91:
Same here, but now I cant reenable the fingerprint, when I click to add my print; it just escapes as when u press the home button. Can you try pls?

Selinux -> application
[OnePlus 3 & 3T Cross Device Development] Dirk:
To avoid confusion:

What were you using:

TWRP?

ROM Build?

Firmware?

Encryption Status?

Bootloader Status?

What builds are you trying to flash of:

TWRP?

ROM Build?

Firmware?

What method/procedure/steps did you follow during the upgrade?
[OnePlus 3 & 3T Cross Device Development] Roman91:
TWRP?3.2.3.1

ROM Build?the last one, of 21 or 22 june

Firmware? 9.0.3

Encryption Status? no encryption

Bootloader Status?unlocked I guess, I'm on LOS

I just dirty flashed the firmware (after I saw the error trying to flash the rom with all that op3 commits, 1 week ago)

then I flashed again the rom (with tons of commits) and PIN stoped to work;

I deleted the locksettings.db and tried to re-add the prints;

no way, when I try to add a print it does just like a home button
[OnePlus 3 & 3T Cross Device Development] :
Before doing anything else, start reading the twrp thread. Hint: twrp 3.2.3-1 is well known to be broken.

BTW: it's no good idea to add something to the quoted posting of someone else! It's not only really bad manner (it looks like [MENTION=1763460]Dirk[/MENTION] would have recommended using broken software) it's also confusing and one can't reply with quoting your setup!

---------- Post added at 10:18 ---------- Previous post was at 10:06 ----------

JFYI:

For easier reference and more detailed information, I've made an own thread for the modded firmware:

https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

Also: I think it's just fair to discuss the modded fw in a seperate thread, since OP recommends locking (and optional unlocking) the bootloader.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I think that's the first report of a problem doing the update Dirty on an unencrypted device. Before hitting the panic button i'd recommend giving the modified Firmware a flash to see if it fixes your problem:

https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

If that doesn't help, restore the Nandroid that you took before starting this adventure and then either dirty flash the modified firmware with new ROM build, or do a clean install using the Official 9.0.3 with new ROM build.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
OK and done ... I just updated my previous post:

==> https://xdaforums.com/showpost.php?p=79777086&postcount=2570

PS: 9.0.3 fw update causes a lot of damage to youths who don't read/understand the thread... Predictable but the OP and the official guide should be updated (imho).
[OnePlus 3 & 3T Cross Device Development] Hydro8:
Hi

I upgrade my oneplus 3 to nighty 19/06/2019 and my firmware to 9.0.3

I had a problem with password so I must rename lock file to bypass lock screen.

Now I can enter into my phone, set a new password but I can't use fingerprint.

Do you know how to get fingerprint back or must I go back to old firmware + lineage os nighty ?

Thank for your help.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Boot to TWRP and delete the two following files with TWRP file manager:

/data/system/users/0/fpdata/user.db

/data/system/users/0/settings_fingerprint.xml

Credit: [MENTION=2911853]BillGoss[/MENTION] (https://xdaforums.com/showpost.php?p=79742341&postcount=2438)

Do not forgot in the future to read in deeph the thread... This issue is well-known.
[OnePlus 3 & 3T Cross Device Development] :
I doubt that.

BTW: Even if we have kernel support and kang eas supporting perfd blobs from marlin, where should we get an eas supporting powerhal? If you want to port eas into a custom rom, https://github.com/EAS-Project is a good starting point. If you want to port eas to los, you can start here: https://github.com/EAS-Project/msm8996-eas.

IMHO getting 16.0 (kernel and rom) stable and working is much more important, then bringing eas in.
[OnePlus 3 & 3T Cross Device Development] xuser_:
I think DU 12 is EAS supported??
[OnePlus 3 & 3T Cross Device Development] Neontc:
Anyone found a way to get rid of this?
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
If you know to use apktool, you can edit the ims.apk with this change:

https://github.com/DroidFreak32/ImsVolteMod/commit/e67e10952e5fff13f622a696de1c9fa76c501e2f

I'll edit this comment soon with the link to modified apk , you could also replace the apk with another ROM's ims.apk but I'm not sure if it causes other issues

Edit:

Download and rename this to ims.apk https://drive.google.com/file/d/1JgL8fcjSlz6hAxWzFfp5WHiaVndgP-Sc/view?usp=drivesdk

Backup existing ims.apk from /system/priv-app/ims/ims.apk

Replace /system/priv-app/ims/ims.apk with downloaded apk, make sure you keep the permissions unchanged (644 or rw-r--r--)

reboot and check if everything is fine, else restore the backed up apk

This is experimental. Do not report any phone/volte related bugs if you are doing this. Confirm if the bug/crash is present with the original apk before reporting
[OnePlus 3 & 3T Cross Device Development] pjgowtham:
I used this app to get rid of it. Calling works in the process. (ROOT REQUIRED)

https://play.google.com/store/apps/details?id=com.aboutmycode.NotificationsOff

untick org.codeaurora.ims
[OnePlus 3 & 3T Cross Device Development] Neontc:
I was just in the middle of trying to figure out how to work apktool when you posted this haha. So I tried replacing the APK with the one you linked and the notification is still showing. Instead of saying "HD capable" it shows "VOLTE capable" :crying:
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
Check the git commit I've linked to see what you might've missed :)
[OnePlus 3 & 3T Cross Device Development] Neontc:
My mistake. I thought the apk you linked was already modded. I finished modding my own and now that annoying notification is finally gone! Thank you for the help
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've now been using 181205 for more than a week and I've not had any freezes, reboots, or any other problems.

The only issues I've come across are UI ones:

- network traffic indicator doesn't work (a known issue)

- NFC is not listed in the available status bar icons and NFC does not display on the status bar when enabled

And that's it!

I'm looking forward to to this becoming the official version for our phones.
[OnePlus 3 & 3T Cross Device Development] trentonite:
Agreed. I had some small hiccups initially but this ROM is very stable. There are only 2 small issues that I'm facing, none of which are major.

1) The SIM being HD Compatible notication.

2) When my phone went into battery saver mode (<10%), all notifications and alarms were stopped. Alarm was set at 530a and didn't go off until I turned the screen on around 6 when I woke up to check the time.
[OnePlus 3 & 3T Cross Device Development] Hazuki Amamiya:
hi [MENTION=5091734]dianlujitao[/MENTION] when I was compiling from source, I got the following error:

FAILED: /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 /a/16.0/host/linux-x86/bin/checkpolicy -M -c 30 -o /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.conf ) && (/a/16.0/host/linux-x86/bin/sepolicy-analyze /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp permissive > /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ) && (if [ \"userdebug\" = \"user\" -a -s /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ]; then echo \"==========\" 1>&2; echo \"ERROR: permissive domains not allowed in user builds\" 1>&2; echo \"List of invalid domains:\" 1>&2; cat /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains 1>&2; exit 1; fi ) && (mv /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy )"
device/oneplus/oneplus3/sepolicy/mm-qcamerad.te:3:ERROR 'unknown type camera_socket' at token ';' on line 78896:
allow mm-qcamerad camera_data_file:sock_file { create unlink };
allow mm-qcamerad camera_socket:sock_file { create unlink };
checkpolicy: error(s) encountered while parsing configuration
/a/16.0/host/linux-x86/bin/checkpolicy: loading policy configuration from /a/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.conf
[ 30% 29753/96347] //externa...c/expand.c [linux_glibc x86]
ninja: build stopped: subcommand failed.
08:03:50 ninja failed with: exit status 1

Any idea? Am I missed any repository which didn't download automatically during init? I added only "TheMuppets/proprietary_vendor_oneplus" for passing the pre-compilation check before actual compilation.
[OnePlus 3 & 3T Cross Device Development] ZVNexus:
Pick all the stuff related to SEPolicy from gerrit. Or build permissive.
[OnePlus 3 & 3T Cross Device Development] ivanich:
Actually you don't need to cherry-pick all op3 selinux stuff from gerrit anymore, it was merged today https://review.lineageos.org/q/owner:dianlujitao%40lineageos.org
[OnePlus 3 & 3T Cross Device Development] laupuy:
oh, maybe you should try this new one 181215 https://androidfilehost.com/?fid=11410963190603875429

:p

;)

Edit

Changelog (post #2) 2018.12.15:

Sync latest source

Fix some suspend issue

Kernel baseline updated to LA.UM.7.5.r1-03700-8x96.0

Minor bug fixes
[OnePlus 3 & 3T Cross Device Development] dom001:
Does anyone have bluetooth issues too? I cannot find my speaker anymore with this rom. I already cleared cache and data from bluetooth app without success.
[OnePlus 3 & 3T Cross Device Development] ele95:
is anyone have lag in animations when you open and close options in settings
[OnePlus 3 & 3T Cross Device Development] mumapizza:
im using this rom without gapps and gps doesnt work, also tried with unifiedNLP with various lookups no luck. build 12.05. and now 12.15. same issue for me. firmware 5.0.7 and 5.0.8 tried
[OnePlus 3 & 3T Cross Device Development] realtos:
nope mine become more and more fluid but last 2 updates is the same fastness. opens right away

---------- Post added at 03:20 PM ---------- Previous post was at 03:19 PM ----------

thats not supprising
[OnePlus 3 & 3T Cross Device Development] knpk13:
It's working with gapps? I had gps problems for a while too and it was masked by the fact that Google location service still worked even if GPS didn't. I honestly have no idea what happened but after a couple weeks my GPS started working again. I clean flashed and tried different roms and troubleshooting, thought it was a hardware problem in the end.
[OnePlus 3 & 3T Cross Device Development] realtos:
anyone know if this build has the latest merges done earlier today? cant figue out the timestamps from gerrit to compare to the upload time on android host :)
[OnePlus 3 & 3T Cross Device Development] Hydro8:
Thank it worked great !
[OnePlus 3 & 3T Cross Device Development] bendodge:
Enforcing.

Bootloader was unlocked, but I locked it before flashing anything else. Still locked, or at least there's no warning screen on boot anymore.
[OnePlus 3 & 3T Cross Device Development] :
I'm with you. As far as I understand, OP only wants to support the "lock the bootloader"-method.

(Frankly: sometimes the dark side of my soul is amused: lack of reading leads to loss of data...)

I also agree with you, that we all underestimated the possible impacts - at least me. First I thought, the only probematic setup is 5.0.x bl unlocked AND userdata encrypted.

The more people with unencrypted userdata update their firmware, it seems to me, that updating from 5.0.x to 9.0.x with unlocked bootloader and userdata unencrypted leads to permanent loss of fingerprint sensor.

Some scenarios (though I havn't gasp the pattern, yet) lead to permissive selinux and broken nfc.

But the strangest, most ugly and most omnious isuue, are the reports of bootloaders, that doesn't allow to relock.

Since we have your directions and the great guide by [MENTION=8423339]Johannes1098[/MENTION], we may put together a migration guide handling more scenarios then just "install lates twrp and relock the bootloader" - on the other hand: people loosing data because of a lack of reading won't read another guide either, which completely demotivates me to do so...
[OnePlus 3 & 3T Cross Device Development] :
Are there any options how to install a new TWRP version, if bootloader on your phone is locked and your phone is encrypted? It's a little bit tricky, isn't it?
[OnePlus 3 & 3T Cross Device Development] :
Since all twrp recovery images from 3.3.1-0 on are signed with the aosp keys, it should work flawlessly - like replacing a aosp signed boot image with another aosp signed bootimage. The only restriction is you need to flash with either twrp or dd-method, since "fastboot flash" doesn't work on locked bootloaders anymore.
[OnePlus 3 & 3T Cross Device Development] :
Thank you. What about 3.3.0-1 version?
[OnePlus 3 & 3T Cross Device Development] :
Why do you want to update to 3.3.0-1?
[OnePlus 3 & 3T Cross Device Development] :
Not really. I want to migrate from 3.3.0-1 to 3.3.1-0.
[OnePlus 3 & 3T Cross Device Development] :
This would have been a usefull piece of information in your original question. We can only read what you write - we can't know what you think.

Just flash 3.3.1-0 as image from within 3.3.0-1.

Sidenote: this is not related to los in any way. twrp related questions with no relation to los should go to the twrp thread.