yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Please, read the 10 last post and you'll understand why this commit was merged
[OnePlus 3 & 3T Cross Device Development] Dirk:
No solution as yet, but it's been raised on Gitlab:

https://gitlab.com/LineageOS/issues/android/issues/849

My recommendation for the 9.0.3 Firmware update has gone from "Clean Install required, (Format if Encrypted)", to "Don't bother until all the issues are fixed".

The workaround for now would be to use the Modified Firmware:

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

If you have a working Nandroid from before you attempted the update, (and you can restore it), i suggest going back to that and then dirty flashing the modified Firmware and new ROM build.
[OnePlus 3 & 3T Cross Device Development] zezinho7:
Dirk thank you very much. I thought there is something wrong with my device because nobody else mentioned it. Again thank you very much !
[OnePlus 3 & 3T Cross Device Development] uresh.kuruhuri:
That's what I thought.

That's what I thought after an earlier reply confirming about ANT+ with a screenshot from ANT Tester. Thank you for confirming the same and this gives confidence.
[OnePlus 3 & 3T Cross Device Development] :
Reading before ppsting would help, of course.

For people, who doesn't like to follow this thread, it would be sufficient to read the commit message, the comments and follow the link in the comment.

It's also usefull to read the change itself (first line):

# Set max transceive length for IsoDep frames

Google is full of usefull information on "android nfc isodep":

https://www.google.com/search?ei=Hx...9......0....1..gws-wiz.......0i71.-fCIvgbSve0

"Extended length" relates to the length of the frames read from the tag - not to the distance of tag and device, of course.

I completely lack understanding for "Can't seem to find any information on it?"... :(

It would have been usefull to read before posting!

The last 30 pages are full of people repprting selinux as permissive or disabled. Thinking you are alone is a sign of lack of reading and/or searchimg before posting.

There is something wrong with your device, because it works for others. I've made a suggestion how to try to track this down two or three pages back.
[OnePlus 3 & 3T Cross Device Development] zezinho7:
nvertigo67 i searched the whole thread for selinux right before the post where somebody posted selinux issues yesterday and did not find any helpful post. the post yesterday i missed.

the issue is not with the firmware 9.0.3 and not with lineage os i am pretty sure now. because as i said the issue persists if oos is flashed using stock recovery.

the device still is not in "original" state.

for now it seems nobody found a solution yet and there is no description with technical steps should be taken to eliminate the issue.

about the dm-verity thing i am not sure what should be checked.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Your assertion that it's not the Firmware seems fallacious when both OOS and LOS are both using it. Rather, it would appear to be the common element in both cases.

Edit: Reading your post again, i think you probably added a 'not' by mistake. In that case you're probably correct. If both OOS and LOS are Permissive in some cases, the Firmware is a common element.

Has anybody had that issue with the modified firmware? I don't think i've seen it reported.
[OnePlus 3 & 3T Cross Device Development] :
It's surely related to updating fw from 5.0.x tp 9.0.x.

If ypu can't find, you havn't searched:

https://xdaforums.com/showpost.php?p=79812969&postcount=2658 (second search hit for "selinux" - first is your posting...

Repeating what is already posted, because we havn't fornd a solition, yet, with the comment of "can't find any helpful post" isn't usefull for solving this.

Stop trolling.
[OnePlus 3 & 3T Cross Device Development] VVMM:
I have just installed the latest build, clean install, but the vibrator does not work. So no haptic feedback. Is this known?

Nevermind, it works after another reboot.
[OnePlus 3 & 3T Cross Device Development] zezinho7:
Finally got it fixed and want to share the info. Selinux is enforcing now using latest firmware 9.0.3 and latest lineage 16.

The solution takes a bit time but here is what i did:

1. Create twrp 3.3.1 nandroid backup of data partition (+efs if you are scary) and store it on pc

2. Run unbrick tool to restore original partition layout and dm-verity state, as described here: https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047

3. Boot device now to old OOS 3 (wifi may not work for now) and save stable 5.0.8 rom from op homepage to internal device storage

4. Boot old OOS recovery and start adb sideload

5. Sideload (install) the 5.0.8 stable rom

6. Boot 5.0.8 rom: connect wifi (working again) and install suggested ota update to 9.0.3 stable

7. Boot 9.0.3 rom and enable developer mode and allow bootloader unlocking

8. Unlock bootloader using fastboot oem unlock, confirm and when phone restarts switch directly to bootloader/fastboot before it wipes data (to save time)

9. Flash twrp 3.3.1 in fastboot mode and directly re-lock bootloader

10. Boot to twrp recovery

11. In twrp save the latest lineage os build (i use lineage for microg 20190625) from pc to internal storage and flash it

12. Wipe caches, format data

13. Save nandroid backup from step 1 to device (still in twrp) and restore data partition

14. Boot, Selinux is enforcing now

I guess there is an issue on some devices itself that did not stand out before 9.0.3 bootloader. Before getting it fixed i installed 4.0.2 firmware and directly saw the message dm-verity warning after booting. Later firmwares did not show the warning message or ignored the issue?

It was not possible to fix it using fasboot oem disable_dm_verity + fastboot enable_dm_verity although fastboot message indicated the commands were completed successfully.

What i could imagine is that there are some flags or some data on the device that are modified after flashing different firmwares using different twrp versions and this causes trouble with the 9.0.3 bl and older ones but not with the 5.x bl which ignores the issues.

EDITED
[OnePlus 3 & 3T Cross Device Development] :
And for me it's reading always the same redudant postings, followed by statements like "I thought there is something wrong with my device because nobody else mentioned it.", what make me think Imwrong here and should stop reading and helping here.

I really appriciate this posting of yours!

Yep, that is exactly what was on my mind, when suggesting the dm-verity trick. I wasn't sure it's really the dm-verity 4.x fw trick to get rid of, but I was 99% sure, that it's a different bootloader config.

Great job pinning it down! Thanx for sharing!
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
I'm sorry but I'm not understanding your point... your selinux is NOT enforcing after flashing 9.0.3 FW + los16 (last version) and you used the unbrick tool and a 4.0.2 OOS firmware to solve it, getting selinux enforcing?? ... Okay, it seems like a Polański's super production...

I understand the position of [MENTION=4405529]nvertigo67[/MENTION], there're people who are tired of repeating the same thing over and over again, trying the people do NOT make mistakes in order to avoid PROBLEMS/BRICKS and keeping the community save... but a large part of the users do what they want, then post because they're getting errors they shouldn't get if they had followed the instructions/warnings or need help... We're here to help us not to destroy us.

WITHOUT READ = BRICK!

ANYWAY coming from unlocked bootloader with 5.0.8 STABLE FW and selinux enforcing (of course) as base + custom PIE rom, flashed 9.0.3. STABLE FW > enforcing selinux using TWRP 3.3.1-0... no need for unbrick tool or 4.0.2 fw!!
[OnePlus 3 & 3T Cross Device Development] Dirk:
No need in YOUR case, but his case was not your case. You didn't get the selinux bug. He did. Or do you think he was jumping through hoops because he is a performing Poodle?

Perhaps you believe all the people who have been affected by the bug weren't previously using 5.0.8, the Firmware of choice for about a year? Or perhaps weren't using unlocked Bootloaders with their custom ROMs, which has always been a requirement as far as i can remember.

Or perhaps it is the case that everybody begun with 5.0.8 firmware, on a ROM that was Enforcing and with an unlocked Bootloader, but instead just got unlucky with the 9.0.3 lottery?
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
I believe in the people they update the STOCK FW to the LATEST and STABLE VERSIONS, plus if they try to install a custom rom, UPDATE THE TOOLS TO ACHIEVE IT (TWRP) to avoid bugs, making their devices most compatible with those customized firmwares as recommended, finally READ and FOLLOW the instructions from the people they created and tested the customizations. that's what I believe. A house can't be built in the epicenter of an earthquake...

BTW stock version has always had an enforcing selinux AFAIK, if it's not your case, try to think which files did you messed up - as advice.
[OnePlus 3 & 3T Cross Device Development] Dirk:
You still don't get it and sadly never will. Hell bent on blaming the victims of this bug as you are. This has nothing to do with 'following instructions'. Why are you pointing out that stock is Enforcing? We all know this. It wouldn't be a bug at all if the firmware upgrade was leaving everyone in 'Enforcing'. That would be normal. Do you perhaps not understand what the bug is?

You point out the Gitlab report. Redundently. We already know it exists. Want to try and guess why it exists? Perhaps it's beyond your comprehension.

Next time you have an issue make sure you let us know so that all the people who don't have that issue can shove your ridiculous posts back in your face.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
I understood the problem perfectly, and I'm not "shoving" nothing in anyone's face, was I said is what I believe in, why is there a problem like this even if there is a solution that was conscientiously tested and "works"... , devices are the same, which files did the user use, how to, it changes. I know what you mean, of course...

PS: I just want to quote the Gitlab report, not to show, its was commented
[OnePlus 3 & 3T Cross Device Development] VVMM:
I experience some WiFi disconnect problems with latest build, clean install from OxygenOS 9.0.3. WiFi seems to disconnect randomly and them reconnects, meantime the connection switches to LTE and back to WiFi.
[OnePlus 3 & 3T Cross Device Development] zezinho7:
[MENTION=220241]Viper[/MENTION]

If you use custom roms there can always be issues/bugs and not only with custom roms. There is no way to avoid it even if you try to convince people of your secure way to update. Also it is not the right way to only trust instructions from others, if the instructions are wrong you are lost?

According to your comments ota update must no longer be used because new bugs can be installed. I am sure you did. Hope the offtopic discussion stops here.
[OnePlus 3 & 3T Cross Device Development] Chol:
Hi,

2 weeks ago I updated the firmware to 9.0.3 and re-locked the bootloader. Afterwards, I normally updated LineageOS using the integrated updater. After the update, the device rebooted, asked for the decryption PIN but instead of booting the OS, it booted back to TWRP. :(

So I completely reset the device by reverting to stock OS 9.0.3. Afterwards I reinstalled TWRP 3.3.1-0 and current LineageOS following the official instructions, this time without re-locking the bootloader. The device worked fine until today where I wanted to update again using the integrated updater. Same situation as last time: reboots after update, asks for decryption PIN and does not boot into the OS but goes into TWRP. :(

Any suggestions?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Don't use the integrated updater. :)
[OnePlus 3 & 3T Cross Device Development] Chol:
Now I restored my backup and the device is stuck at the OnePlus "Powered by Android" screen. :crying:
[OnePlus 3 & 3T Cross Device Development] :
On twrp 3.3.x.x restoring system is known to be broken - see twrp thread for details.

Either backup/restore system as image or dirty flash the rom version you've done the backup from. Again: see twrp thread for details.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Why did you try to restore a backup instead of manually installing the ROM build that had already been downloaded by the updater?

If you're still interested in getting up to date with as few problems as possible, i suggest manually flashing the modified firmware from here,

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

with the latest ROM build. The latest TWRP (3.3.1-0) has been reliable so you might want to start by upgrading to that, if you haven't already.
[OnePlus 3 & 3T Cross Device Development] Chol:
Thanks both for your help, now the old version is working again. I will try to use the modified firmware next time I dare to update. It is a bit unfortunate that the 9.0.3 firmware was made a requirement for updating, but the stock 9.0.3 firmware does not work with the integrated updater.
[OnePlus 3 & 3T Cross Device Development] Dirk:
The stock firmware has many issues, as does the updater.

Fortunately both can be avoided.

[MENTION=4405529]nvertigo67[/MENTION] The man who brought us the 'least annoying ROM on XDA', now with 'the least annoying firmware'.
[OnePlus 3 & 3T Cross Device Development] generalprobe:
[MENTION=4405529]nvertigo67[/MENTION] I wanted to thank you for adding this NFC related patch. Indeed now my passport is readable for the first time.

In addition I had to delete /data/nfc/nfaStorage.bin1 again)

Unfortunately the NFC connection is too weak to change the PIN of my passport. Is there something we could do to amplify the signal?
[OnePlus 3 & 3T Cross Device Development] :
No idea. If it works on oos it could make sense to compare the libnfc*.conf files of los and oos.
[OnePlus 3 & 3T Cross Device Development] ceanth:
What never? I had been using integrated updater for quite some time without any issues.

Update: Actually I had with using the updater, update flashed ok but I got the rescue party error. Had to restore backup and install update manually via TWRP and it worked. I will be avoiding the updater from now on!
[OnePlus 3 & 3T Cross Device Development] Imnoa:
It's borked since a few weeks, download the rom manually and flash manually via TWRP and you're fine
[OnePlus 3 & 3T Cross Device Development] :
Interesiting. We have reports in this very thread, that just manually reflashing the rom in the rescue party twrp sessionmis sufficient to recover. So, you say that doesn't work anymore?

...or you help solving this. I've requested some additional information some weeks ago in this very thread.

...or you flash manually the updater downloaded zip or you use lineage updater from playstore. Quite some workarounds are mentioned in this very thread.

Interesting. How do you know? To my knowledge we havn't tracked down yet, if it's the updater, some selinux rules or twrp.

OK. Now for the third time:

If anybody is willing to help to track this down:

Please, check if the ota automatic flashing also failes on twrp 3.2.3-10 or 3.2.3-0. Only if those versions of twrp gives a resue party, too, make a log of the updater acition in the rom and in twrp-3.3.1-0:

make sure you can connect with adb. In the booted rom as well as in twrp

when the rom is up and running, start "adb logcat >logcat-rom-ota.txt"

fire up the updater and start the updating

when the device reboots, the adb command will return

as soon as twrp boots, try "adb logcat >logcat-twrp-ota.txt"

If the ota automatic flashing works on twrp 3.2.3-0 or 3.2.3-10, please reinstall twrp-3.3.1-0 and get only the twrp log (above steps 4 & 5).

If somebidy wants to blame me for redundancy: you are right, every single point (including the quoted parts) are already mentioned in this thread. Sorry, for repeating already posted stuff again!
[OnePlus 3 & 3T Cross Device Development] 666biker:
Hello, had anyone tried to change adjusting ringer volume by default instead of media volume in these latest releases? some time ago it works for my (button mapper app.) but now, when the "arrow symbol" was introduced, it stops working like expect... any hints? thanks
[OnePlus 3 & 3T Cross Device Development] realtos:
ola peeps got a tiny question about my 3t and los16, is there any way to get bankin app like VISA on the phone and working? i cant use it cuz it say my phone is ofc unlocked, any way to trick it? ive tried to use magisk and hide but im not sure its the right method cuz ROOT and unlocked arent the same thing i believe

thanks :)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Magisk should do it if it's configured correctly. Custom Kernel is another option providing you use one that's compatable with LOS right now.

Relocking your Bootloader is a third option. It should be possible and in theory should allow Banking Apps to work without complaint. I think this has yet to be tested though.
[OnePlus 3 & 3T Cross Device Development] realtos:
but relocking bootloading wont allow me to use magisk and youtube vanced ect inside los anymore right? if yes im gonna try that :)

sidenote: also my magisk say its rooted but setting/trust say its not thought, maybe thats the problem
[OnePlus 3 & 3T Cross Device Development] :
Magisk is a systemless solution - other then addonsu.

In deed trust checks the devopts settings for checkimg for root. I.e.: uninstall magisk, flash addonsu, set devopts to apps and adb, uninstall addonsu and reflash magisk. Check trust... ;) It's no problem for your issue. You just need to make sure to pass safetynet and playstore is shown as certified. Any of [MENTION=1763460]Dirk[/MENTION]'s suggestions will do.

---------- Post added at 12:58 ---------- Previous post was at 12:43 ----------

If your app can't handle the expandable volume panel, your app needs adjustment for that. You know better then us, what's your app is doing/relying on/needing.
[OnePlus 3 & 3T Cross Device Development] cultofluna:
Can't download anything from the store...

Any suggestion...( Clear app data already, reboot, reinstall the ROM...etc.. nothing works)
[OnePlus 3 & 3T Cross Device Development] Imnoa:
https://play.google.com/store/apps/details?id=com.google.android.gms

Already updated this ?

(Or try wiping dalvik or reflashing opengapps nano/pico)
[OnePlus 3 & 3T Cross Device Development] cultofluna:
This is what I'm getting when I clicked on the link
[OnePlus 3 & 3T Cross Device Development] cultofluna:
I'll reflash gapps...

Thanks
[OnePlus 3 & 3T Cross Device Development] cultofluna:
No success . unfortunately..

Flashed gapps wiped dalvick
[OnePlus 3 & 3T Cross Device Development] :
I'd suggest you give some basic information:

detailed description of the issue including steps to reproduce, error messages and logs

regression or right after cleanflash

if it's a regression, what may the trigger (aka what has exactly changed on the device, since it was working)

version of all software packages used

detailed setup description (mods, kernels, formware, bootloader status, everything, which is not the clean flash of the rom)
[OnePlus 3 & 3T Cross Device Development] cultofluna:
I've just updated to latest build 1- 7

Nothing else has changed
[OnePlus 3 & 3T Cross Device Development] :
If you belive that this information is sufficient and answers my previous posting, the only solution is obvious: clean flash with only gapps pico or nano.
[OnePlus 3 & 3T Cross Device Development] cultofluna:
Just flash the ROM with gapps nano...

Install magisk ( no modules)

Sorry but I prefere to try another rom...

Anyway I'm using this phone just as a back up device

OP6T Is my daily driver...

Thanks for helping

Cheers
[OnePlus 3 & 3T Cross Device Development] 666biker:
it was application from Google play, which I found that work for Android 9.

It was not special application for this purpose, but it was possible to adjust settings to reach that behavior.

Unfortunately, after introducing that "arrow symbol" while adjusting volume, this application has now different behavior, so I am looking for some next possible solution, how to achieve that I will see ringer volume on screen when I will press volume button on locked screen or home screen. I think, by default, it should be up to user (not google) :-/ if he prefer to adjust ringer or media volume as default via some "option" in audio settings of Android Pie.

thanks
[OnePlus 3 & 3T Cross Device Development] :
Yoir claim "my (button mapper app.)" misled me to think it's your app, aka you are themdev of the app.

My advise doesn't change, though. If the app can't handle the expandable volume panel (yes, the arrow has an additional function... ;) ), the app needs adjustment. If younarn't the dev, contact the dev and ask him to fix his app to handle the expandable volume panel.

For your feature request: I wasn't able to find out how to place feature requests for los.
[OnePlus 3 & 3T Cross Device Development] defi231:
flashing 16.06 LOS_ locked device

Hi , my op 3t is locked, i flashed new twrp, 9.0.3 fw+modem only and lineage-16.0-20190701-nightly-oneplus3-signed

my phone shows me = device has loaded a different operating system

is this normal? can i get rid of this?
[OnePlus 3 & 3T Cross Device Development] :
What was the setup, before flashing the above? What was/is your bootloader status? Can you still boot to twrp? Can you still boot to fastboot mode?

If the answer to the last two questions is no: unbrick tool.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I have many questions.

You relocked your Bootloader sometime?

What was the status of the OEM Unlock option in Developer Options before the update process?

At what stage of boot do you get the 'device has loaded a different operating system' message'?

Can you boot to Recovery?

Can you OEM Unlock in Fastboot Mode currently?

Were you already using 9.0.3 when updating or are you coming from 5.0.8 setup?

Did you clean install?
[OnePlus 3 & 3T Cross Device Development] defi231:
sry for mssing information..phone is totally working fine. it just bothers me that the phone is showing this at startup.

phone was unlocked twrp on LOS 5.0.8, i just locked BL with fastboot installed twrp flashed fw+modem 9.0.3 and installed new LOS
[OnePlus 3 & 3T Cross Device Development] Dirk:
This is literally the 'official' method of updating to 9.0.3 that was recommended by the OP as far as i recall. First time i've seen anyone do it this way successfully though, i think. :good:

At what stage of startup does the message appear?

What did you do with the OEM Unlock setting throughout the relocking/updating process?

Does the ROM pass Safetynet out of the box right now? (If you don't mind checking it would be interesting to many of us).

Were you encrypted or unencrypted through this process?

Did you have to remove security measures prior to update?

Sorry for all the questions but we can learn a lot from your experience.