yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I lost myself for few minutes once I read "Single Malt Scotch". Can't wait to go home after work and pour my "finally Friday night" Glenfi-15.

I was about to ask the same thing. What actually that firmware will bring along that would make it worth this "format internal memory or relock bootloader" hassle. I am using that community build on an unlocked bootloader. Had to format the internal memory but i've reencrypted and its working fine now. the only issue is slower FP and "considerable" delay in FP unlock speed.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I've been using my phone like a Harmonica all day and i'm still sober! Rubbish Firmware. :p

Enjoy your Friday night tipple. Wish i could join you.
[OnePlus 3 & 3T Cross Device Development] Flounderist:
Hi. I tried to migrate from unofficial to official twice using the signature script but the device reboots on recovery every time. What's your setup before moving to official? Any magisk or mod?
[OnePlus 3 & 3T Cross Device Development] bumbum.droid:
Running the included kernel and having magisk installed I did no prep other than copiying the script over. It did not reboo itself. What guide were you using?
[OnePlus 3 & 3T Cross Device Development] Flounderist:
No guide at all also here. Just flashed the migration script and then official build. I will try without flashing a custom kernel.
[OnePlus 3 & 3T Cross Device Development] :
IMHO: if you clean flash you'll safe the time fiddeling witn the migartion scrpt(s), and much more important: you don't need to wonder on each issue, if it's a side effect of migrating... Increasing the possibility of side effects doesn't help you, nor others, nor the dev to make the rom better.
[OnePlus 3 & 3T Cross Device Development] bumbum.droid:
Well that should be obvious. Idk why you needed to comment like that though. None of us were complaining to the dev. If there are problems and we didn't clean flash that's our fault ofc. No one argues the opposite.
[OnePlus 3 & 3T Cross Device Development] Flounderist:
I know that clean flash is more than advisable. I am just incredibly lazy in the latest times.
[OnePlus 3 & 3T Cross Device Development] :
How can you know that? How many "phantom" issues I've hunted the last years has been side effcts of migrating instead of clean flashing? How many "real issues" solved by clean flashing have been side effects of migrating? How many questions have poluted this and other threads are the result of migrating?

I've never stated that you intentionally complain about issues resulting from migrating, but claiming "None of us were complaining to the dev." is falsified if a user that has migrated asks "does anybody else expirience xyz".

If I accumulate the time I've spended on hunting down issues, that vanished after a clean flash from the last 5 years, I end up not in hours, but in months - that's why I comment like this: if you wonder if it's time for a clean flash, the answer is yes.

If all users, who migrated would follow the policy "as long as it works, you are fine, but if an issue occurs, clean flash and reproduce the issue before asking for help and/or reporting the issue", I'll ask the moderators to delete my comment.
[OnePlus 3 & 3T Cross Device Development] Flounderist:
Guys, I need your help.

I tried to move from unofficial to official using the migration script, but no luck again. Device bootlooped and then rebooted in recovery.

Once restored a backup, I get stuck in the bootloader page.

I can revert to recovery, but even wiping data and clean flashing latest official, the device cannot complete the boot process.

Any hint?

Edit: I moved back to TWRP 3.2.3-10 and the restored backup booted fine.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Boot in recovery

Wipe cache/dalvik and system ... Not Data

Flash latest build + GApp + SU (if needed)

Re-Boot system

Enjoy ... Hope so.

If it doesn't work.... Clean install.

Edit: you need at least OxygenOS 5.0.8 firmware to flash latest build.
[OnePlus 3 & 3T Cross Device Development] Flounderist:
Thanks for the info but the problem is that I couldn't boot even after wiping data.

I assume it is a recovery bug, I didn't take any log before fixing for a double check.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I assume you used twrp-3.3.0-1?
[OnePlus 3 & 3T Cross Device Development] Dirk:
What TWRP did you make the backup with? I assume the latest from our recent conversations, or was the backup older than that?
[OnePlus 3 & 3T Cross Device Development] Flounderist:
The backup was made using 3.3.0. The restore is successful with both recoveries, but I can boot only on 3.2.3-10.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Have you try with 3.3.0-1 ?
[OnePlus 3 & 3T Cross Device Development] Flounderist:
Yes it was the latest build, sorry for typo.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Strange...

ASAP, I'll perform a Nandroid backup with TWRP 3.3.0-1 and try to restore it.

Edit: have you try to perform a clean install (full wipe of cache/dalvik/system/data + flash latest build+gapp only) with TWRP 3.3.0-1 ?
[OnePlus 3 & 3T Cross Device Development] Dirk:
I don't think there's much that can be learned right now, with the added complication of the Migration fubar. It muddies the water. All we can do is keep an eye out for reports of Backups failing to restore on latest TWRP and try to gather information and logs.

In case it turns out to be relevant, what file system are you using and were you Encrypted?

I'll echo what [MENTION=4405529]nvertigo67[/MENTION] has previously said. In situations where a clean install is warranted, any attempts to shortcut the process often end up taking longer than the clean install would have in the first place. Not to mention all the bugs that may, or may not, have been caused by taking a shortcut. I say may, or may not, because once you've taken that step you'll never be sure either way.

I don't know anyone who would change the Duvet cover and sheets, but not the pillowcases at the same time. I wouldn't want a half-clean install any more than i'd want half-clean bedding.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
For information:

==> Restoring a Nandroid backup fails with TWRP 3.3.0-1.

Edit: Sorry, I was on 3.2.3-10 and It fails with 3.3.0-1 !!!!
[OnePlus 3 & 3T Cross Device Development] Flounderist:
The device is unencrypted, f2fs since day one.

As I mentioned in the first post, I also tried a clean flash (ROM only, no gapps, no system wiped) when the migration and the first restore failed both.

Even clean flash, I repeat, rebooted my device in bootloader status.

Then I swapped twrp, restored backup again and the device boot happened.

Maybe after easter hols I will retry the whole thing. :D
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
An alternative: full wipe with cache and data as ext4 ...
[OnePlus 3 & 3T Cross Device Development] Dirk:
There are levels to 'clean flash'. For some a swipe-to-wipe is sufficient. Others will insist on doing each partition seperately from the Wipe/Advanced menu. After the migration fubar i would consider nothing less than a FORMAT to be 'clean'.

It's perfectly possible that 3.3.0-X is to blame and everything might have worked had 3.2.3-10 been used from the start. Impossible to say with a sample size of one, and with added complications along the way.

If you're still looking to update, use 3.2.3-10 now that you're already on it. Take the opportunity to Format Data to EXT4 for better compatability and enjoy the feeling of beginning your Official LOS 16 journey with a proper clean slate.
[OnePlus 3 & 3T Cross Device Development] Flounderist:
F2fs is working fine so I can't see the point in changing my file system. I'd like to move to official builds with the minimum effort, so far :D
[OnePlus 3 & 3T Cross Device Development] Dirk:
That ship has already sailed. :D If you'd Formatted and started installing when the migration failed you'd be finished already! Takes me an hour from beginning to end, having been through every setting and opening every single app to restore/configure it.

Sooner begun, sooner done.

---------- Post added at 22:31 ---------- Previous post was at 22:16 ----------

Good to know. It's early days with 3.3.0 so there may yet be Gremlins that could be uncovered. That said, (and it bears repeating), you EXT4 like a normal person! :D

f2fs is for edgy hipsters who like to rebel against convention. Like wearing drainpipe jeans that were last in fashion in 1969 and are as fit for purpose as a chocolate Teapot. :p

Edit: If for no other reason, at least OTA auto-update will work with EXT4.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Is the process of formating with ext4 as simple as copying the whole data partition to a pc or thumb drive, formating the partition, and recopying the files back?
[OnePlus 3 & 3T Cross Device Development] Flounderist:
I have a good number of devices and I can affirm that same of them are working better with data formatted as f2fs.

I know it will start the Easter Flame, but I could feel comfortable with it even on an high performance device like op3t.

Being lazy AF at the moment, I will stuck on unofficial builds for a while. When I will find some spare time for a good clean flash, I will go for it.

If in trouble, I will format data as ext4, I promise :cowboy:
[OnePlus 3 & 3T Cross Device Development] abhibnl:
[MENTION=5091734]dianlujitao[/MENTION]

Please don't include that firmware. It also requires a complete internal memory format if you want to go back to oreo OOS. I think its an unnecessary PITA for something that might not bring along any significant improvements. I would highly suggest to keep the current firmware and maybe cherry pick some parts of new blobs, if that's possible
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Does Los 16 run on OOS 9.0 beta firmware?

tl;dr: yes

So I installed the OOS 9 beta and had to format /data because I was encrypted and have an unlocked bootloader. My phone now is on the 9.0 firmware, encrypted (ext4 data partition) with on boot password, using TWRP 3.3.0.1

I then decided I'd try running Los on the 9.0 firmware so I restored my Los 16 backup, but the phone wouldn't boot - doesn't even get to the point of asking for the boot password.

So I did a clean install of Los and that booted up just fine. I then backed up the clean install, and restored it. But the phone wouldn't restart (Edit 2: this problem happens on TWRP 3.3.0.1 but not on TWRP 3.2.3.1 or fix-3). So a clean install works, but a restored clean install doesn't. So I dirty flashed the Los rom again and this time the phone restarted!

I then restored my full, working Los backup (from before installing OOS 9.0 beta), dirty-flashed the rom, deleted the lock screen password files, and rebooted.

Yay! It worked!

So here I am on my restored Los 16 rom, on OOS 9.0 beta firmware writing this post.

The one thing I had to fix was my fingerprints. The phone wouldn't recognise them. I had to delete the following two files, reboot, and set up my fingerprints again:

/data/system/users/0/fpdata

data/system/users/0/settings_fingerprint.xml

Conclusions:

1. Los 16 runs fine on OOS 9.0 beta firmware.

2. Restored system partitions from a TWRP backup won't boot. You have to flash the rom again. (Edit 2: this problem happens on TWRP 3.3.0.1 but not on TWRP 3.2.3.1 or fix-3. With 3.2.3.1 or fix-3, you can restore the system from a backup and boot)

3. Old fingerprint settings don't work on the new firmware and have to be set up again.

I'm now off to see if I can restore my OOS 5.0.8 rom the same way.

Edit 1: OOS 5.0.8 works on 9.0 beta firmware. I used the same approach as for Los. However, I used a 5.0.8 zip file that didn't include the 5.0.8 firmware because I didn't want to overwrite the 9.0 firmware
[OnePlus 3 & 3T Cross Device Development] DarthVesh:
So you're able to install the Android 9 Community Build via TWRP 3.3? I'll assume via a clean flash? Also, was your bootloader unlocked or did you still have to relock it?
[OnePlus 3 & 3T Cross Device Development] kenboyles72:
I had an issue with the latest twrp-3.3.0-1. Did a clean flash and phone wouldn't boot. Flashed twrp-3.2.3-1 and did a clean install and booted fine.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
From the 2nd paragraph in my post:

I "had to format /data because I was encrypted and have an unlocked bootloader"

"using TWRP 3.3.0.1"

I'm still unlocked and [re]encrypted. I used the Format Data button in TWRP (which decrypts the phone), not the Advanced Wipe button.
[OnePlus 3 & 3T Cross Device Development] DarthVesh:
Thanks!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I said that I couldn't restore the system partition from a backup and boot successfully on OOS 9.0 beta firmware in my previous post https://xdaforums.com/oneplus-3/one...ageos-16-0-oneplus-3-3t-t3866517/post79378447

I've since discovered that this problem happens on TWRP 3.3.0.1 but not on TWRP 3.2.3.1 or fix-3. With 3.2.3.1 or fix-3, you can restore the system from a backup and boot successfully.

I've updated my post (Edit 2).
[OnePlus 3 & 3T Cross Device Development] Dirk:
You got a log i think, didn't you?

What do you think the problem is? Gut feeling.
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
And I faced the same while using TWRP v3.2.3-0.

I've not yet upgraded to the newer TWRP. Faced the exact same issue. BTW, backup was made on v3.2.3-0 itself & I was trying to restore it using the same TWRP. Unfortunately, couldn't take logs.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes, I've got TWRP logs. But not logs from the system trying to boot up. And I have no idea where the problem lies.

I've never tried to take logs from the phone while it's in the process of booting. I do know that I can't get an ADB connection until after the phone asks for the boot password and I don't get to that point when restoring a backup using TWRP 3.3.0.1.

I'm going to paste what info I have in the TWRP thread as it's not really relevant to Los.
[OnePlus 3 & 3T Cross Device Development] Dirk:
nvertigo has you covered below...
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=2911853]BillGoss[/MENTION], [MENTION=1763460]Dirk[/MENTION] and [MENTION=7193743]Flounderist[/MENTION]

I confim... Restoring a Nandroid backup fails with TWRP 3.3.0-1 !

Sorry about my previous post yesterday ... I must have been drinking too much Nikka from the barrel!

==> https://xdaforums.com/showpost.php?p=79377794&postcount=1831
[OnePlus 3 & 3T Cross Device Development] :
First - and most important: thank you for testing and sharing the results in a structured way!!!

Getting logs from booting is only possible, if adbd is started successfully. If the boot process fails before adbd is started, you have no chance to get a log.

If you want logs from a clean flash's first boot, you need an unsecured build (to avoid the need to allow the device on adb and to allow adb at all).

The only way to get a log in these situations is pstore:

On the very next reboot after the failed boot - this is typically a boot to recovery - get the content of /sys/fs/pstore. It's absolutly mandatory to do this on the very next reboot! I.e. if you have connected the device via usb, and switch of the device, it will automatically boot the kernel for showing the poer off charging pics: this will overwrite the pstore with the logs from booting for power off charging.

[MENTION=5091734]dianlujitao[/MENTION]: as long as nandriod restoring isn't fixed, it's better to revert the recommemdation in OP to 3.2.3-10. Backup/restore is a basic twrp feature, which should work reliable, before recommending it.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Were you in the barrel at the time by any chance? ;)

Thanks for the update. :good:

I hope people are reading the thread before posting about Boot failures after backup restores and clean installs for weeks to come. Looks like the message is, stick with 3.2.3-10 for now.

The link again for those who need it:

https://androidfilehost.com/?fid=1395089523397907195
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Really some weird stuff is going on these days in the 3/3T world! [emoji14]

Flashing/Updating OOS Pie builds with TWRP on Unlocked Bootloaders causing /data corruption, TWRP breaking encryption (the v3.2.3-1 fiasco), a brand new 'stable' TWRP v3.3.0-x arrival & then suddenly it also started showing weird behaviours [emoji14]

I'll still be sticking to the good old v3.2.3-0 till the time it works ;)
[OnePlus 3 & 3T Cross Device Development] :
3.2.3-10 has proofed to work reliable. With 3.2.3-0 you arn't able to format to f2fs (as least as long as you don't know, what you are doing).

I'd recommend 3.2.3-10.
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
I'll be continuing this conversation in the TWRP thread ;)

I've been going slightly OT I believe.
[OnePlus 3 & 3T Cross Device Development] :
I thought the topic of our conversation is the recommendation in this thread's OP, isn't it?:confused:
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Yes indeed it started with that... But I myself have some really 'noob' questions that I don't want to spam this thread with... [emoji14] :cowboy:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
As a reminder :

TWRP 3.2.3-10 (@dianlujitao's TWRP) : https://androidfilehost.com/?fid=1395089523397907195).
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
How did you reencrypt your device? Your /data was decrypted after the Factory Reset in TWRP. So did you reencrypt the device with the OOS 5.0.8 or LOS 16? I assume that you didn't encrypt it with the 9 Open Beta because that doesn't boot with an open bootloader. Am I right?

The next question for me is: What if there is a newer Open Beta Build or a final Pie release. Can you update the firmware once you are on a Pie based firmware or would it crash the /data again.. I hope so that it doesn't do that... ;)

And another question: would this work with formatting /data as f2fs and not ext4. I think it would work - but I'm not sure about the encryption. Of course you need a TWRP that doesn't break the encryption footer while formatting/factory reset the /data Partition. But after the /data was corrupted and now formatted new - the encryption footer is gone or not? (in ext4 it isn't as [MENTION=2911853]BillGoss[/MENTION] tested - he could reencrypt the data partition.) So with the right TWRP version 3.2.3-10 you should also be able to to this procedure exactly the same in f2fs...

Maybe I'll try and error later..
[OnePlus 3 & 3T Cross Device Development] :
A factory reset does NOT remove encryption - in deed a factory reset dosen't touch media, and tells so on the console output.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Okay. So a format of /data in TWRP would also remove the ecryption?

And what is needed after installing pie firmware. A factory reset or a formatting of /data?
[OnePlus 3 & 3T Cross Device Development] :
That depends on what format option (wipe main page vs. advanced page) you use. See the twrp thread for details - it's explained there.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Ahh okay. Thanks. So the same procedure with f2fs and a TWRP with the f2fs encryption footer fix should work... Maybe I could try that later or tomorrow..
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Decrypting: Wipe>Format data removes the encryption AND formats /data as ext4 (I stayed with this). If you want to continue using f2fs you'll have to also change the format after decrypting using Wipe>Advanced with one of dianlujitao's TWRP versions (3.3.0.1, 3.2.3.10, fix-3).

Re-encrypting: OOS has force encryption enabled so simply booting OOS encrypts /data. So I formatted /data, flashed OOS 9.0 beta and booted the system.

Updates: I have no idea what OnePlus are planning for their updates. It would be nice if they didn't require a complete format of /data again.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
I just took a backup with TWRP 3.2.3-10 and noticed the time and date of the folder are incorrect. TWRP thinks it's the 7th on June, 1972, at 930am. All of that is wrong. I searched the TWRP thread for a solution and what I found suggested this issue is caused by the Rom. ???
[OnePlus 3 & 3T Cross Device Development] Dirk:
It's not the ROM. That build of TWRP doesn't display the time correctly. The new 3.3.0 does, but as you might have seen we don't recommend using that. If you flash 3.3.0, reboot Recovery and then flash back to 3.2.3-10 the time will display properly. (Until you next Format presumably)
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
backup "system image" as a workaround, it works.

I'm still not clear what goes crazy after restoring a system backup as I'm unable to capture useful logs so far.

---EDIT:

The root cause of the issue is /system isn't assigned with a valid selinux context after mke2fs, I'll investigate later

---EDIT2:

A fix is up https://gerrit.omnirom.org/33894
[OnePlus 3 & 3T Cross Device Development] :
Yep, we've found that workaround. [MENTION=2911853]BillGoss[/MENTION] has tested that succesfully.

Since the logs from fix3 (tar backup/restore working) and 3.3.0-1 (tar backup/restore NOT working) are nearly identical, I hoped pstore (log impossible at that boot stage) could help us to shine some light on it. If you state it's not usefull, getting pstore doesn't make sense, of course.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Another workaround is, after restoring just (re-) install the LOS ZIP.

After that the system boots successfully (again) and you won't lose any system modifications, e.g. the LOS su-addon or other system modifying ZIPs.

The advantage is that this works even if you haven't taken a system image before.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
That worked. Thanks.

I've been running into another potential bug that I'm not sure if it's caused by the ROM or the app(s) involved.

Every time I reboot I need to re-enable AOSP keyboard in order to restore spell check capability. I'm using SwiftKey and normally keep AOSP virtual keyboard disabled to prevent the notification. I thought at first it was an issue with system language and SwiftKey language not being set the same but those are correct. Anyone else run into this?
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Update to community beta pie firmware is recommended for LOS 16?

https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166/post79397249
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Nope.

Nevertheless, it runs fine on OOS 9 beta firmware.
[OnePlus 3 & 3T Cross Device Development] enochpc:
I realize there have been documented AudioFX issues, but is anyone else having audio issues on 4-22 build? I have AudioFX disabled, but I have no external speaker audio and no headphone audio. I am going to try a clean flash of 4/23 in a bit but was wondering if anyone else had the same issue. Reboot didn't change anything. I think phone audio is working, but the speakers were working yesterday as well, this all just started this morning.

Edit: Clean flash of 4-23 seems to have done the trick, maybe just too many dirty flashes in a row.
[OnePlus 3 & 3T Cross Device Development] linrunner:
Beware of OB40 firmware

I strongly advise against it.

I did it on my OP3 with lineage-16.0-20190418-nightly-oneplus3-signed.zip and ended up with a corrupted data partition (decryption successful).

After a factory reset, re-encryption and data recovery from my TWRP/Nandroid backup the result was still unsatisfactory:

SIM wasn't recognized

"fingerprint hardware not recognized"

Signal app refused to start
[OnePlus 3 & 3T Cross Device Development] BillGoss:
If you search this thread for "fingerprint" you'll find that there's a fix for it.

I've had no problems running Los on the beta firmware (it's what I'm using now).