yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] ivanich:
Somehow it gets fixed, can't point you to exact steps but I rebooted to recovery few times and removed db file and wiped caches.
[OnePlus 3 & 3T Cross Device Development] simmeone:
I removed locksetting.db, add a new pin and tried to add new FP. The sensor does not recognised.

No clean install...
[OnePlus 3 & 3T Cross Device Development] ivanich:
Just a suggestion, skip setup pin first but setup fingerprint and it would ask you to setup pin before fp, after that I got it working
[OnePlus 3 & 3T Cross Device Development] simmeone:
Does not work, sensor not recognise
[OnePlus 3 & 3T Cross Device Development] lutherkingmartin:
I'm on 9.0.3 firmware + TWRP 3.3.1-0 + LOS 06-16 build + encrypted phone

I try to lock bootloader with "fastboot oem lock", but after lock, the phone reboot every 2 seconds. If I boot in TWRP, I can't decrypt data with my password.

After unlocking again, all is ok, but it seems you can't use lock bootloader with lastest TWRP + lastest LOS + encrypted phone.

Maybe it can work if I format data and encrypt again after lock bootloader ?
[OnePlus 3 & 3T Cross Device Development] kenboyles72:
So, if one has unlocked BL and IS NOT encrypted, one can just flash as normal and have no issues right? It's just those that are encrypted that are having issues?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Because my device is unencrypted, I can lock or unlock BL... as I please... but only without screen lock !

My setup: FW 9.0.3 / TWRP 3.3.1-0 / ext4 / unencrypted / unlocked BL / latest official LOS 16.0 build / pico open gapp / official LOS addon SU
[OnePlus 3 & 3T Cross Device Development] simmeone:
Does fingerprint sensor works?

No idea why the sensor not recognise? Hmm I don't want wipe all my data, damn...
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I just added ... but only without screen lock !
[OnePlus 3 & 3T Cross Device Development] Dirk:
That's what i want to know. I think it's been hinted at that this is the case, although i can't understand why. I thought the difficulty was because of an incompatability when trying to flash new firmware onto an unlocked Bootloader. Why would Encryption come into it?

Edit: Eric runs unencrypted and had to clean install when flashing 9.0.3 the first time. I guess that's the answer. We'll all be clean flashing soon.

[MENTION=734765]lutherkingmartin[/MENTION]

Despite the assertions from the OP that it should work, i don't think anyone has been able to relock the Bootloader without issues, let alone relock it and flash new ROM builds without Data loss. New TWRP or not.

I think it'll take a lot of work testing, gathering Logs and fixing the issues before this ever becomes a reality.
[OnePlus 3 & 3T Cross Device Development] simmeone:
Here is a screenshot from logcat...
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
If BL locked/unlocked requires an unencrypted device without screen lock (unless I'm mistaken.)... What's the point?
[OnePlus 3 & 3T Cross Device Development] :
I'm not sure - havn't tetsted myself, because I don't want to miss fastboot's flash and boot commands - but I belive you additionally need to disable OEM unlocking in devopts before locking the bootloader (and vice versa prior to unlocking).
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
After my last clean install (today), I forgot to check this point ... and .... please, see the enclosed screenshot ... ???

Note my BL is unlocked ... of course.
[OnePlus 3 & 3T Cross Device Development] :
At least you don't need to disable it, when you try to lock the next time... ;) SCNR
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Anyway, I don't see the point of locking the bootloader... so it suits me very well.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Oh man... I'm really annoyed to have to do another clean install for being able to install the latest updates again. :mad:

Why can't we stick with firmware 5.0.8 until upgrading works correctly... :confused:
[OnePlus 3 & 3T Cross Device Development] sighunter:
me too, did that a couple of weeks ago and is much work, even with Titanium Backup etc
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=5091734]dianlujitao[/MENTION] only knows... :D SCNR

---------- Post added at 21:53 ---------- Previous post was at 21:50 ----------

Try Migrate app ... It's fast and effective.

==> https://xdaforums.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
[OnePlus 3 & 3T Cross Device Development] kenboyles72:
A clean install doesn't bother me, as I do a clean install every time I flash a new update anyways. I'm also not flashing every new update either, I usually update once a month. I use TiTbu for backup and restore and flash the app zip in twrp, along with everything else. So it's a one step process.
[OnePlus 3 & 3T Cross Device Development] :
Because we don't know when and if at all we get a booloader prebuilt from OnePlus without this (compile time) setting (I honestly doubt, that this wasn't intended by OnePlus and if this setting is subject to be "fixed" at all).

And: what are you complainimg about? There seem to be - at least - thre ways to update without loosing data, two of them proofed to work...

Finally: I highly respect [MENTION=9708417]Eric_Lev[/MENTION] for admitting his lack of prperation on his erloer attempts, instead of complaining it's not working as expected (what are knowledge-less expectations worth for other then disapointment?) and blaming fw, twrp or whatever. Just relax and wait some time with updating and use the time for reading this thread, the OOS 9.0.3 rom thread and the OOS 9.0.3 firmware thread...
[OnePlus 3 & 3T Cross Device Development] vaio4ever:
Does anyone experience Google Photos crashing (not even successfully opening after the spash screen) with 16 June LOS and 16 June OpenGapps Stock?
[OnePlus 3 & 3T Cross Device Development] S4turno:
According to reports on some telegram groups about Google Camera, it's crashing on other phones too. Try an older version of GPhotos or a different gallery app (eg: Simple Gallery) until Google fixes it.
[OnePlus 3 & 3T Cross Device Development] vaio4ever:
I am unable to install other versions because they always fail to install (as APKs).

Maybe it's due to the fact that it's flagged as a system app, maybe i'll wait for the next update to be inclued into the opengapps.

Moreover it's now with its English name "Photos" while until yesterday it was Italian (I live there) "Foto" and also Chrome is in English since some weeks. Who knows...
[OnePlus 3 & 3T Cross Device Development] gianni281:
Just wondering if anyone is having issues upgrading to the build? I performed a full data format (wipe/advanced/format data) in twrp installed the 9.0.3 firmware followed by the new build, latest nano opengapps and magisk 19.3. I boot the phone and can't get past the initial setup as phone is telling me it doesn't have an active data connection and can't read the sim. Soon after this the android phone app crashes and phone reboots to recovery.

I proceeded to format again (wipe everything including internal storage) and this time I installed full oos 9.0.3 along with magisk 19.3. Managed to boot and setup phone and everything was functioning as it should with oos 9.0.3 (radios/wifi) and no app crashes and I was happy that there was no issue with the phone or the radios.

At this point I redownloaded latest lineage build along with nano gapps. I format the phone again (including internal storage) copy the freshly downloaded zips, flash them and boot the device and once again I have no radio, phone app crashes and phone boots to recovery.

I then download the lineageos build from the 15th, format the phone again and flash the build from the 15th which is actually what I've ended up sticking with.

I'm running a 3t with the latest twrp 3.3.1-0. I have an unlocked bootloader and I'm not currently encrypted.

Not sure whether it's just me having these issues or if there's an issue with the latest build.
[OnePlus 3 & 3T Cross Device Development] koltun:
I experiences similar issue. OP3 on 9.0.3 firmware and radio with TWRP 3.3.1-0. After upgrading to June 16th sim unlock does not work (for non of my 2 sims). I tried first with regular update (no factory reset) and with factory reset. All looks good (so far) on build from June 15th.

---------- Post added at 10:06 PM ---------- Previous post was at 09:07 PM ----------

I'm on locked BL, encrypted FW 9.0.3, TWRP 3.3.1-0, LOS16 6-15. And I do not have any warning message. I followed guide posted for OP5 by [MENTION=7052208]Optimuspro[/MENTION]. - it does say that you need to format first. I was playing with this for over a week. I think it is important to:

- start with latest TWRP

- then flash FW 9.0.3

- then do recovery and boot signing with AOSP keys

- lock bootloader and setup screen lock and encrypt at the very end

I did 2-3 updates after locking BL. ALWAYS updated from TWRP (no data wiping needed) and ALWAYS flashed VerifiedBootsigner with custom keys after update.

I run into weird issues only with todays (June 16) build (mentioned SIM unlock problem). and had to go back to June 15.
[OnePlus 3 & 3T Cross Device Development] Lazy-Mind:
[MENTION=5091734]dianlujitao[/MENTION]

I' m on latest build. My data is unencrypted. Fw 9.0.3.

After update my fingerprint scanner is broken. I can't delete fingerprint or create new. in addition, in order to go to the phone I had to delete locksettings.db PLS Fix it.
[OnePlus 3 & 3T Cross Device Development] :
That's right. I am one of those who did just a dirty flash with 9.03 firmware and latest nightly without any issues.
[OnePlus 3 & 3T Cross Device Development] Organized:
Last week I upgraded my OnePlus 3 to the latest 9.0.3 stock ROM (with Magisk) and was facing some issues, such as very slow finger print recognition and performance issues in general. Also I had pretty serious battery drain, even using AKT Zhana's Profile.

Yesterday I switched to LineageOS (nightly 16.06.2019) with 9.0.3 firmware and Magisk and it's absolutely beautiful! Some settings are a bit difficult to find when you used OOS for years, but after the phone is set up completely it's really nice. Battery drain over night (8hrs) with OpenVPN connected is only 5%.

One thing annoys me anyway: when looking at the Launcher the "Ok, Google" voice recognition is ALWAYS on, even turned off in the settings of the Google Assistant! When I'm inside an app this is not happening. Maybe the developers could have a look at that. If you need some details (logs) or something, please let me know.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Please read these posts carefully:

https://xdaforums.com/showpost.php?p=79736966&postcount=2382

https://xdaforums.com/showpost.php?p=79738371&postcount=2395

https://xdaforums.com/showpost.php?p=79737571&postcount=2385

and the next ones.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Delete these files (using TWRP terminal or file manager if rooted), reboot, and then set up your fingerprints again:

/data/system/users/0/fpdata

data/system/users/0/settings_fingerprint.xml

See https://xdaforums.com/oneplus-3/one...ageos-16-0-oneplus-3-3t-t3866517/post79378447
[OnePlus 3 & 3T Cross Device Development] simmeone:
Thank you! This fixed the issue with not recognizing sensor! Works now :good:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
A question about encryption

Encrypting a device is easy... Settings > Security & location > Encryption & credentials

But how to decrypt an encrypted device without losing/formatting the Data partition?
[OnePlus 3 & 3T Cross Device Development] lutherkingmartin:
Any complete guide link for relock bootloader with LOS16 please ? I'm very interested.
[OnePlus 3 & 3T Cross Device Development] :
Analysis:

https://xdaforums.com/showpost.php?p=79736834&postcount=825

Fix:

https://github.com/nvertigo/android...mmit/2a1230bd37d102e9940fbdeb4a8f434b5a75d5c0

https://github.com/nvertigo/proprie...mmit/4e9999540c7e09c0939fd85d00187e473f18b91d

You can replace the three files manually (never tested exchanging files in the system partition with locked bootloader, though) or wait for [MENTION=5091734]dianlujitao[/MENTION] fixing it in the los repo.

EDIT:

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250329
[OnePlus 3 & 3T Cross Device Development] gianni281:
[MENTION=4405529]nvertigo67[/MENTION] Thanks I'll wait for [MENTION=5091734]dianlujitao[/MENTION] to fix. Wasted a few hours wiping and flashing along with checking this thread. I didn't see any other members reporting the same issues at the time and at least now I have confirmation the issue is with the OnePlus firmware. Bright side - I'm running the latest firmware now, so I'll be able to update to the fixed nightly without wiping again.
[OnePlus 3 & 3T Cross Device Development] :
The ril/ims issues has nothing to do with the firmware, but with the blobs used inside the rom. ims always had this issues with native oos blobs, that's why we always kanged other msm8996 device's ims. Since the oos native ims blobs works for most setups - inluding mine - dianlujitao has just droped the pinnimg of the kanged blobs. Though I understand that blaming fw is really on vogue nowdays, this is NOT related to fw.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
Let's see if I've got this right, I will try a "for dummies" like me recap, I hope it doesn't contain too many mistakes.

[MENTION=5091734]dianlujitao[/MENTION] increased fw requirements in order to support OOS 9 blobs. Unfortunately, a Oneplus fixed firmware, allowing to upgrade on devices with BL unlocked and user data partition encrypted without a clean flash, will probably never released, so there is no point to wait further. Theorically the bootloader can be locked without losing data, since latest TWRP supports locked bootloader.

https://xdaforums.com/showpost.php?p=79736966&postcount=2382

However no one has (still) succeeded in the enterprise and the thread experts are skeptical

https://xdaforums.com/showpost.php?p=79739863&postcount=2417

So, if guys like me, with BL unlocked and user data partition encrypted, wants to upgrade to newer LOS releases without losing data, they can choose between alternatives:

1. install a modded firmware version by [MENTION=4405529]nvertigo67[/MENTION], probably the quickest and safest, but the less canonical and not recommended by the author itself: https://xdaforums.com/showpost.php?p=79738371&postcount=2395

2. try their luck and lock the bootloader, maybe with some extra setting: https://xdaforums.com/showpost.php?p=79740141&postcount=2420

3. clean flash installation, including userdata partition reformat and reencrypt, maybe with the help of Titanium backup or other migration tool: https://xdaforums.com/showpost.php?p=79740323&postcount=2426

Right now, I'm tempted with the first option, it seems to me the fastest solution to buy time and see what happens.

But there is (at least) one thing that I don't understand: If I do clean flash installation and I manage to install fw 9.0.3, upgrade LOS and get my data back, what will happen when fw 9.0.4 (or similar) will be the new requirement? Is this a one-time critical upgrade or we will have to periodically face the same issue?
[OnePlus 3 & 3T Cross Device Development] :
No. If your bootloader is already locked, just go ahead. The modded fw only makes sense if three points are met: bootloader is 5.x.x, device is encrypted and bottloader is unlocked. Please read https://xdaforums.com/showpost.php?p=79738371&postcount=2395 , especialy the lost under "Prerequisite":
[OnePlus 3 & 3T Cross Device Development] drevel123:
I just updated to the latest build using the unmodified 9.0.3 fw package from 14th build:

- unencrypted

- latest TWRP

- locked Bootloader

Dirty flashing didn't work as the phone booted to recovery after showing the Lineague Boot Animation for several seconds.

Clean flashing worked fine, I then restored the data partition from the nandroid backup I did prior to flashing. The phone booted fine, but my lockscreen pattern wasn't recognised.

I deleted the lockscreen pattern and the fingerprint settings via TWRP and now, everything is working just fine.

(My sim-card isn't protected, so I cannot say whether it would work with pin-protection for the Sim Card. With my unprotected sim, there are no problems).

Thank you for your tips that made me able to install the newest build without that much hassle :good: And thank you for the great rom of course.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
Just a misleading typo in my post, now fixed, thanks for noticing. Unfortunately my bootloader IS unlocked, otherwise I wouldn't have bothered to write my post.
[OnePlus 3 & 3T Cross Device Development] fiepi:
Delete /data/system/users/0/fpdata
[OnePlus 3 & 3T Cross Device Development] koltun:
* As a XDA n00b i can't post links yet *

Search for "Guide: Relock bootloader with custom rom on oneplus 5/5t" on XDA for guide.

To eliminate all warning after relocking you'd need to sign with AOSP verity key (per [MENTION=5091734]dianlujitao[/MENTION] comment in the "op3: Enable OEM unlock and bootable image signing" LOS Gerrit). You can get them from Android Google Sources under /platform/build/+/master/target/product/security/.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
A question about encryption

Encrypting a device is easy... Settings > Security & location > Encryption & credentials

But how to decrypt an encrypted device without losing/formatting the Data partition?

Found a way to decrypt without losing everything on Reddit:

1. Boot to TWRP

2. Perform a Nandroid backup in TWRP

3. Copy all data from External storage to PC (your backup)

4. Wipe or Advanced wipe > Format DATA as EXT4 or F2FS

5. Reboot to TWRP

6. Copy your Nandroid backup (all TWRP directory) of PC to External storage

7. Restore your NAndroid backup

8. If you had a screen lock, it won't work.

You need to delete the lock screen files (using TWRP terminal or file manager if rooted)

/data/system/gatekeeper.*

/data/system/locksettings.*

(see this post: https://xdaforums.com/showpost.php?p=79111125&postcount=1204 - Credit: [MENTION=2911853]BillGoss[/MENTION])

if using fingerprints,

/data/system/users/0/fpdata

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

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

8. Copy all data (your backup) from PC to External storage

9. Reboot system

Sounds right ? .... I think so, but I haven't checked yet.
[OnePlus 3 & 3T Cross Device Development] Dirk:
An interesting experiment. I'm already decrypted and happy to stay that way. (For some reason i've never understood, crDroid doesn't force encrypt. At least for me.) You run decrypted too right? What method are you using to stay that way? Is it a no-verity zip or something?

Another way to get decrypted and stay that way would be to format with 3.2.3-1. Say goodbye to your encryption footer and never have to worry about encryption again! :p
[OnePlus 3 & 3T Cross Device Development] Mr.Jay:
Trying to update but it says error 7 on recovery. I know that's a firmware related issue but lately I've been reading some post about people loosing data after flashing the newer firmwares on unlocked/decrypted devices.

Any safe method of flashing the new firmware in order to update the ROM without loosing data?

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] Dirk:
Use the modded firmware from nvertigo67. Just read back a few pages.
[OnePlus 3 & 3T Cross Device Development] :
Lineage doesn't force encrypt - oos does:

grep encrypt oxygenos/system/vendor/etc/fstab.qcom los16/out/target/product/oneplus3/system/vendor/etc/fstab.qcom
oxygenos/system/vendor/etc/fstab.qcom:/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,nodiratime wait,forceencrypt=footer,check
oxygenos/system/vendor/etc/fstab.qcom:/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,forceencrypt=footer,check
oxygenos/system/vendor/etc/fstab.qcom:#/devices/soc/74a4900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,encryptable=footer
los16/out/target/product/oneplus3/system/vendor/etc/fstab.qcom:/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,nodiratime wait,encryptable=footer,quota
los16/out/target/product/oneplus3/system/vendor/etc/fstab.qcom:/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,encryptable=footer,quota

As long as you stay with los/los-based rom you don't need to do anything to keep the device unencrypted, but skip manually encrypting.

Disclaimer: running a device with custom recovery without secured boot is grossly neglient.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I run decrypted since I switched to the dark side of the Force (i.e. my last clean flash + official 9.0.3 fw update)... :cool:

My setup is very common: TWRP 3.3.1-0, ext4, latest build , Gapps pico and LOS SU addon... Nothing very exciting !

Formatting with 3.2.3-1 is a crazy idea ... that I may test for fun... if I have time... :D

Edit: agree with [MENTION=4405529]nvertigo67[/MENTION], LOS doesn't force encrypt.
[OnePlus 3 & 3T Cross Device Development] Dirk:
That clears up my confusion nicely. I've been using the same ROM all year so had no idea that it was normal.

Running a device with custom recovery unencrypted is of course the same as running encrypted but with no on-boot security, which is what i've always done anyway. (As you know i hate the janky FDE bootup). My OP5 uses FBE and crDroid does force encrypt on that device. I leave it like that.
[OnePlus 3 & 3T Cross Device Development] :
You are right. I should have been more exact. Fixed it.

(Honestly, running a device encrypted with "default_password" is so... it never comes to my mind... BTW: I would give the green lock in trust not for encryption, but for secured boot.)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
You make me think of Statler and Waldorf in The Muppet Show ... :D ... SCNR
[OnePlus 3 & 3T Cross Device Development] :
Then [MENTION=1763460]Dirk[/MENTION] and me are doing everything right... ;)
[OnePlus 3 & 3T Cross Device Development] bons:
+1. No issues on unlocked bootloader en unencrypted phone.
[OnePlus 3 & 3T Cross Device Development] rlees85:
Just a word of warning about the 9.0.2+ and the data loss / bootloader bug.

I am not 100% sure but I think this goes beyond just crashing the data encryption key. I (blindly) updated lineageos and the 9.0.2 blobs a couple of days ago without knowing about any of this and blew all my data away (just want you want 10pm on a Sunday night).

I then accepted I lost everything and used twrp to do a simple format and set things up. Phone was unstable and battery was going from 80% to straight off. At this point I thought I'd try some things out.

I tried to install stock 9.0.2. It worked but the stock recovery would NOT boot.

I tried to re-lock bootloader, it would NOT relock (just said are you sure, I press yes, it reboots, still locked).

Tried a lower OxygenOs official firmware, still recovery would not work and still boot loader would not lock.

So I think this screws more then just /data to be honest. If you haven't updated yet personally I would not bother!

In the end I used EDL to go back to 100% stock and OTA'd all the way to 9.0.3. Bootloader unlocks & locks OK. From here I've unlocked the bootloader again and installed latest lineageos. Doubt I'll be upgrading the firmware on this phone again especially oxygenos blobs.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I consider this a valid option. Return to full stock, update, customise from scratch. At least if all else fails.

Seems to be 50/50. Eric was unlocked and unencrypted but needed to clean flash. I guess prepare for the worst and hope for the best!

I'll be trying it Dirty for sure, but ready to Clean if necessary. Or i might just say effit and stop flashing new builds. I'm happy with my setup right now. I doubt if it's going to get any better.