yashsingh1/xdaforums huggingface dataset:
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
One last thing I can think of (which worked for some) is to flash full OOS with treble support and reboot back to recovery then flash LOS normally. It did work before I've realised that there are firmware zips available to update the firmware.

That it worked before doesn't mean that flashing OOS without booting it can corrupt any data and booting it also could be a complete mess :/

Oh another thing that comes to my mind: AFAIK the bootloader definitely doesn't change if flashing the firmware. I remember after RMAing my device I flashed the latest OOS and suddenly the bootloader unlock warning screen completely changed. There is no way of telling the bootloader version but some old version could potentially prevent the Treble enabling.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] U35632317:
Will it be possible to decrypt data partition in twrp in future? For now I need to format data everytime I want to flash even if I've removed Pin/Fingerprint before.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
Decrypting is not possible but you can use no-verity.zip ;)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] U35632317:
Oh, so it will never be possible again? :(

I like the security of encryption so I am not going to remove this ^^
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] droidsometimes:
Are you talking about stock or LOS here? Because I'm on LOS, I'm encrypted, and so far I had no problems flashing LOS updates, neither with stock nor codeworkx TWRP. Thus, I'm slightly confused now. :confused:

And, regarding /vendor partition, because I also had no vendor appear after flashing 5.1.4 firmware, what's the consensus now: go back to full OOS for once, because the bootloader needs updating?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
It never was and probably never will be. Still, you don't need to format /data to flash anything. Especially upgrades from the same ROM. I see no point in doing that :confused:
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] dlmartin:
I am finding the stock lineage kernel on this weeks 08/27 build is good on battery life. Also the play protect certification fix earlier in the posts works with the Magisk config module. The play store now says certified in the play store settings. Magisk still says "no response" when you check but everything is working fine as others have reported.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] U35632317:
OK, maybe I mixed up something.

I was on stock for a few months. When I was on custom roms before, I was able to enter my pin in twrp to get access to the data partition.

If i reboot to twrp now (latest lineage build) there is no password prompt. Even on terminal is decrypting not possible. Because of encryption I'm not able to flash anything. I need to format data to get access.

Maybe is there something wrong with my recovery?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] tesna:
If you use latest TWRP it does support decrypting by entering your PIN in TWRP. I always stays encrypted and never had to format data when updating the rom . I dont want a stranger have access to my data in case my phone is lost/stolen.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] U35632317:
Yeah, this is my goal too. But for some reason it does not Work.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 3lMghraby:
I have an idea

before updating the rom or firmware just remove your password from settings before booting to recovery
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Regina Rainbow:
I don't think there's a consensus yet, but flashing OOS 5.1.4 was the only thing that worked for me eventually. Since OOS 5.1.5 is already requiring a working vendor partition (updater-script is checking for it), the "vendor partition creation magic" should happen somewhere inside of the official OOS 5.1.4 Build. (Be it at installation or at boot time.) So, what worked for me:

Edit (08/30/18): Better head over to Post #1704 by [MENTION=6016024]Macusercom[/MENTION] for a faster and more secure way to do this - especially if your device is encrypted.

Edit (08/31/18): Solved in Post #1721 by [MENTION=3208754]codeworkx[/MENTION]

1. Backed up my LOS 15.1 installation with official TWRP 3.2.3-1

2. Flashed official OOS 5.1.4 (=full ROM), also with TWRP 3.2.3-1

3. Let OOS 5.1.4 boot (in case vendor partition is being created during boot or while OOS 5.1.4 is running for the first time)

4. Reboot to recovery (which should now be overwritten by stock recovery due to step 3)

5. Install official OOS 5.1.5 (if this works, vendor partition is in place and working, because the updater-script of 5.1.5 cancels the installation, if it's missing.)

5a) If data partition has been encrypted before step 1, it might be necessary to flash 5.1.5 via OTG sideload (because stock recovery can't decrypt data encrypted by LOS 15.1)

5b) If data partition has been encrypted before step 1, OOS 5.1.4/5.1.5 might get stuck on first time setup - that's no problem for our cause, just ignore it and reboot

6. Let OOS 5.1.5 boot, just for the fun of it and to confirm everything went OK

7. Reboot to fastboot mode ("fastboot flash recovery twrp.img")

8. Reboot to TWRP and restore backup from step one

It's not the simplest method, but it worked for me. On encrypted devices one or two extra steps might be necessary, especially a full external backup of sdcard might be wise, in case you end up having to do a full wipe or TWRP can't decrypt data anymore.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] U35632317:
Thanks for that hint but I tried this several times already
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] HipHopBlond:
I tried Installing codeworkx's TWRP 3.2.3, upgrading to OOS FW 5.1.5... still not able to install 27th build, coming from 20th. I also get an error code 7 with the vendor partition error, I would be really happy if we find a way to do this without wiping just before Android P.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] coolgoose1:
Vendor partition error

Same vendor partition error that others have reported.

I have tried twrp-3.2.3-0-codeworkx, twrp-3.2.2-0-codeworkx and the official twrp-3.2.3-1 and tried various combinations of firmware-5.1.4/reboot-bootloader-or-recovery-or-system/firmware-5.1.5/reboot. I feel like this has something to do with the bootloader version or the twrp version when we first flashed 5.1.4 firmware.

Does anyone know if there is a way to upgrade just the bootloader ?

Does anyone know which partition should I be looking for in fdisk output to confirm existence of vendor partition ?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
Not that I know of. I don't think there is a flashable bootloader zip. It has to be the bootloader as it works for some and for others it doesn't. I tried the exact same steps with codeworkx' recovery and still get the failed to mount /vendor issue as well as error 7 when flashing LOS 15.1 from this week.

I'm gonna try flashing OOS 5.1.4 and then LOS 15.1 afterwards. No way to flash the bootloader files in fastboot :(
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Seferi:
I have the latest codeworkx-twrp and had already 5.1.4 firmware but flashed again just in case.. Just followed the codeworkx's steps and everything is working fine..

1. Nandroid backup

2. flash 5.1.4 firmware and reboot to recovery

3. flash 5.1.5 firmware and reboot to recovery

4. flash nightly and additional zips you need to ( in my case camera libfix for gcam to work and reboot system.

Here is the link for all the firmwares:

https://xdaforums.com/showthread.php?t=3728665&page=11

Hope it helps someone..
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
My solution for the /vendor issue:

Be warned: Your doing it at your own risk and it is definitely a very dirty way to do it but it doesn't require any factory reset.

Only do this if you tried that and it didn't work: https://xdaforums.com/showpost.php?p=77462354&postcount=1668

Requirements:

- TWRP by codeworkx (for /vendor support): https://xdaforums.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673

- Download OOS 5.1.4 from here: https://xdaforums.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265

- Firmware 5.1.5 from this thread here which has this link: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/dumpling/firmware/

Steps:

Flash TWRP by codeworkx either via "fastboot flash recovery" or in TWRP itself by selecting the image file and then "recovery".

Reboot to the new TWRP recovery

Flash the full OOS 5.1.4 ROM and DO NOT REBOOT

Flash LineageOS 15.1 (no treble) afterwards e.g. from what you're currently running and reboot to the bootloader

(this is to prevent OOS 5.1.4 from booting, I don't know what would happen if you do. This could mess /data and everything up)

Reboot to TWRP again (/vendor error is still shown)

Flash the 5.1.5 firmware

Flash LineageOS 15.1 with Treble and it should flash now without any error

Reboot, wipe cache/dalvik if you want to and it should be working

Issues:

After flashing the full OOS 5.1.4 ROM it could be that certain apps crash due to a permission reset. Reinstalling either via the Play Store or TitaniumBackup helps. All permissions (camera, location etc.) could and probably will be reset by doing this. Also it could be necessary to reinstall whatever Gapps you have if the Play Store doesn't work anymore. However, you do not have to wipe or restore any Nandroid backups or systems but definitely keep a backup of your existing pre-Treble system just in case.

Note:

If anybody can achieve a flashable bootloader update zip, this would make the issue go away. As I can see only bootloaders from before OOS 5.1.4 (before Treble) do not create a /vendor partition and the firmware zips do not update the bootloader. The only way is to flash full OOS 5.1.4 (OOS 5.1.3 doesn't do it, OOS 5.1.5 requires /vendor to be working) and reboot at least once into TWRP again. This updates the bootloader while also flashing OOS to /system. Immediately flashing LineageOS 15.1 won't change the bootloader so the new bootloader will stick. Booting into the OOS system is definitely not recommended and could require a wipe.

At some point everyone had OOS on their OnePlus 5T and if you never flashed OOS 5.1.4 before going to LineageOS 15.1 you won't be able to simply flash the 5.1.4 firmware and have /vendor enabled. You will have to have flashed OOS 5.1.4 at some point. That's why codeworkx' steps work for some and for others they don't.

Fyi I'm currently encrypted so it worked with encryption.

I'm not responsible for anything. Do it at your own risk! What worked for me doesn't have to work for anyone else.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] nicfio:
This is just another solution (reported from Reddit and it worked for me!! ):

1 - Download This onto your phone

2 - Boot into TWRP (3.2.3-1 official works)

3 - Install the zip file you downloaded

4 - Reboot your recovery (I did this just in case, though I'm sure it's safe to skip to the next step)

5 - install firmware 5.1.5

6 - reboot to recovery

7 - install latest lineageos zip file

8 - reboot to system

Reboot!
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] mvmike:
Yep, you can extract the boot.img from any of the official OOS releases. In any case, remind to flash not only the bootloader via "fastboot flash boot boot.img" but also flash the recovery just after, if not you end up in a bootloop issue (don't know why, but it's like the recovery it's not recognized after booloader update).

---------- Post added at 10:27 AM ---------- Previous post was at 10:26 AM ----------

No need to format anything? :)

And what about vendor zip?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] nicfio:
No, just follow the points above. :D:D
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] bdwilk:
The boot.img is the kernel, per se. It is definitely not the bootloader.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
AFAIK boot.img doesn't contain the bootloader but only the kernel? :confused:
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] mvmike:
Yep, just read about it, I was wrong... sorry for the misleading info :eek:
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] rouma7:
+1 worked on my device as well. no loss of data and upgraded from 20180820 to 20180827 using codeworkx's TWRP 3.2.3-0
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] mvmike:
Worked for me too :)

No need to format, no data loss, no need to flash vendor .
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] codeworkx:
It's not the same as official.

This script is using my hacked up sgdisk binary to rename some spare partition (1.5 GB). Result: 1.5 GB vendor partiton

Official op rom is splitting the partition into two parts (1.0 and 0.5 GB). Result: 1.0 GB vendor and 0.5 GB reserve3.

There's a chance that this will cause problems in future. But chance is very low.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] giddie:
So are we left with any low-impact "correct" option for creating the vendor partition? I prefer not to resort to flashing OOS 5.1.4. The 5.1.4 firmware alone is not sufficient for me. Presumably I'm missing an updated bootloader that doesn't yet have a separate install package available?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] coolgoose1:
+1, same here
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] codeworkx:
Just this then: https://xdaforums.com/showpost.php?p=77479318&postcount=1704

Bootloader + Firmware: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/dumpling/firmware/

I didn't go back to OOS and for me it was enough to flash 5.1.4 firmware from https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/dumpling/firmware/ via TWRP and reboot straight back to TWRP.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] coolgoose1:
There is nothing in 5.1.4.zip that touches vendor partition. Nor is there anything of that sort in 5.1.5.zip. I am not able to understand how the vendor partition would be created unless it is created by

a binary uploaded in 5.1.4, when first run

the bootloader, upon seeing 5.1.4

or a flash, be it OOS, OpenBeta or plain vendor partition flash

or manually renaming a partition to vendor, either via a script or on terminal
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] autry7:
You have to use the latest TWRP. 3.2.3-1. I'm encrypted and using a pattern lock without issue.

https://dl.twrp.me/dumpling/twrp-3.2.3-1-dumpling.img.html
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] codeworkx:
We think its the bootloader.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
I guess the issue is that nobody knows for sure what it is. I assume the code for the bootloader is locked down so nobody can say for sure how it works.

The point is that for some flashing 5.1.4/5.1.5 worked and for others it didn't (keep in mind that people are more likely to comment here if it didn't work) so I assume the odds are 50:50.

Flashing OOS 5.1.4 without even booting it does work, however. Either the firmware zips are missing something or the full OOS rom does something that nobody has figured out yet.

Fact is, there is a solution that works. Either by following codeworkx' steps or mine.

And as I said before: I have flashed firmware zips for LOS and always had the old secure boot warning screen with white ugly small text. Before I sent it in for RMA I flashed the latest OOS and suddenly the warning message was yellow and larger. This stayed the same for me until this day. So flashing the same OOS version as the firmware zip changed something in the bootloader even though the firmware zip contains the bootloader. I have no idea why but the OOS ROM zips seem to update the bootloader while the firmware zips don't.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] codeworkx:
reuploaded 5.1.4 and 5.1.5 firmware zips. we missed to flash abl.elf.

getting vendor partition should work now.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
Thank you! :o

That probably explains why my bootloader only updated after flashing OOS. abl.elf never seemed to have been included in the firmware files provided. Glad you could figure it out :)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] asferreira:
It worked! Thanks !
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] droidsometimes:
Indeed it worked, thank you very very much! :good: :)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] khan1989:
I flashed the re-uploaded version of firmware 5.1.5, and now my bootloader warning has been updated to the "bigger text" version, but I am still getting vendor partition cannot be mounted error in TWRP codeworkx.

Do i need to re-flash the re-uploaded 5.1.4 too? Or is there something else I'm missing?

What do we do with the vendor zip file? Can that be flashed?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 3lMghraby:
I flashed the old files since the update 27\8 and booted successfully with vendor partition mounted

should I flash both files again

or just 5.1.5 to get the updated bootloader ?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] khan1989:
I flashed the re-uploaded 5.1.4 fw, booted phone, rebooted to recovery and flashed the re-uploaded 5.1.5 fw, booted phone, rebooted to recovery and still, unable to mount '/vendor' partition invalid argument.

Using

Lastest build: twrp-3.2.3-0-20180822-codeworkx-dumpling.img

LOS

15.1-20180820-NIGHTLY-dumpling
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] sam3000:
If you already have a vendor partition then it's fine to just flash 5.1.5. If you didn't, you should reflash 5.1.4, reboot to twrp and then reflash 5.1.5.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 3lMghraby:
1-download latest build 27\8

2-new 5.1.4 and 5.1.5 firmwares

3-flash 5.1.4

4-reboot to recovery

5-flash 5.1.5

6-flash lineage os 27\8

7-gapps
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] giddie:
Works perfectly! Glad there's a simple explanation after all :)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] khan1989:
Just flashed latest lineageos over my existing fw 5.1.5 flashed and it worked, no more vendor errors. Was scared to flash lineage incase i lost my data.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] HipHopBlond:
Oh. My. God.... I was just thinking it can't get worse, and then I tried to flash Magisk 17.00... ended up being stuck in a bootloop.

I was very angry and came here to see what's new, saw the updates, decided to try on top of the mess....

It actually worked, it installed the latest version, error is gone, and I was able to boot just fine!!!

Then I checked Magisk and it seems like it was saying that it's not installed.

Tried installing the 17.0 magisk zip, ended with error 2....

Tried the uninstall package, ended with error 255... first time I'm seeing this...

So then I extracted the boot image from LOS build 27th, and chose the option to patch it (patch boot image) within Magisk.

It generated boot_patched.img, moved it to storage, went back in TWRP, installed it as boot, and rebooted to system.

Magisk is now working perfectly, safetynet is onpoint and I'm running latest LOS...

Thank you so much [MENTION=3208754]codeworkx[/MENTION]!!!
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 3lMghraby:
default color profile is missing for me

am I the only one with this ?

is there an adb command to revert ?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
Same here on latest nightly. In the past it was like that, then they've added more options including the standard one. It appears they've removed it again. I had to wipe data to get it working. But maybe an update will add the option again. Earlier nightlies definitely supported it.

EDIT: At that point in time the "None" option was definitely there: https://xdaforums.com/oneplus-5t/de...os-15-1-oreo-oneplus-5t-t3730058/post76856519
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Pinguin1337:
Hello,

I'm on the latest lineage build + opengapps nano + magisk 17.1. But saftynet test failed (ctsProfile: false)?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
That's normal. Nothing you can do :(
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] evilzombie:
one way to "fix" this is to modify /system/build.prop and change the ro.build.fingerprint to be ...

OnePlus/OnePlus5T/OnePlus5T:8.1.0/OPM1.171019.011/06131716:user/release-keys
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Seferi:
I'm just curious why the old firmware zip worked for some of us and some not..

It worked for me but should I still flash the new zip you uploaded? :confused:
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
They forgot to flash a part of the bootloader. It was inside the zip but it didn't flash it. That's why /vendor hasn't been created as the bootloader was not updated properly.

So the people who flashed OOS 5.1.4 at some point got the new bootloader while those who only used the firmware zips didn't. Even Doc's firmware files don't include the bootloader afaik.

If it works it shouldn't be an issue but I doesn't hurt flashing the new 5.1.5 firmware to make sure your bootloader is up to date ;)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 3lMghraby:
I had to factory reset to bring it back to default value

even clearing data for lineage settings didn't work
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] codeworkx:
will be fixed on next build
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] angelus errare:
I recently did a full wipe and clean install of the latest nightly, but I'm now getting a false flag for CTS, which I dont think I was on an older build. Is this normal? The phone wasn't rooted.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 3lMghraby:
there is a fix

you need to have magisk

install hide props module and use terminal to modify you fingerprint to get the official oneplus 5t(or whatever you wnt)

and you will pass it
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] angelus errare:
That worked, thank you!
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
I didn't even know that such a module exists. Thanks!
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 3lMghraby:
you're welcome :)

I also made a thread about it to make all people know

with an explanation of the cause

https://xdaforums.com/oneplus-5t/how-to/guid-bypassing-safetynet-august-t3837809
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Pauzzz:
Hey guys, coming from OOS 5.1.2 and I'm getting persistent play services and play store has stopped errors. I flashed twrp, backed up, factory reset, flashed firmwares, reboot, flashed ROM, flashed opengapps arm64, final reboot. I've read the thread but I couldn't find any others with my issue in recent builds. I tried setting up my GSF ID but still doesn't work.

nvm got it, titanium backup is dumb
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] khan1989:
Can confirm, standard is back!
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Macusercom:
It's now implemented :)

https://review.lineageos.org/#/c/226511
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 3lMghraby:
I was among the first to download and flash latest build

and thank you for letting me know
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] GammaRay654:
bug?

i have a problem with whatsapp front camera, the camera get frozen when select front camera but rear camera works fine how can solve this?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 3lMghraby:
can confirm this

I attached logcat

https://drive.google.com/file/d/1m4ZhkdVmevJ9Dsf-160Jc5ICMYX1GG67/view?usp=sharing