yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I you have a oneplus bootlogo, you either havn't flashed xmas-firmware or modded your firmware after flashing xmas-firmware.

bootlogo (NLOS in the middle of the screen, "powe3d by android" at the bottom)

bootanimation

fading oneplus logo

pulsing NLOS logo

NLOS characters
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
The not accessible issue and the boot issue seems to be "introduced" upstream and are related:

https://xdaforums.com/oneplus-3/one...-oneplus-3-t3496850/post74865237#post74865237 (till the end of the thread)

As with NLOS, too, only very few devices suffer from those on los. And as far as I can see the people who solved this did a reformat of f2fs data partition.

I tried to start a discussion on what the devices with issues have in common, which differs from the devices with no issues, but nobody but [MENTION=4472938]opethrocks[/MENTION] was interested in. He solved it by formating data.

I would like to help you (as stated many times, I do NOT expirience this problems), so it's your turn to provide detailed information.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Has anybody noticed issues with gcam 4.4 since xmas-firmware?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Interesting. I'll get logs and try formatting too. Formatting is going to be a pain though lol. Can I restore a twrp backup after formatting?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I think so (on my last tests - 10 months ago: I could restore twrp data backups taken from f2fs on f2fs partition; ext4 backups on f2fs partitions, but restoring a f2fs backup on ext4 doesn't work). Don't forget to backup /sdcard on file basis. I use rsync to my linux server, but I'm pretty sure there are only very few people who like it: it's cli and you need a remote host supporting rsync. On the other hand: it's very configurable, you also backup modes and permissions (even xattr, if available) and you can use ssh for the connection (-e).

I'm pretty sure there are backup apps on play store, which are able to save /sdcard with all attributes and permissions for you, perhaps someone not liking cli can jump in here with a recommendation.

I've read in this thread someone is using twrp-4x. It's not 9fficial, so I have no change log - but I guess it's with O support. I don't know, which f2fs backport state is used here, most properly it's working, but to exclude a different f2fs state from the issues causes I strongly recommend official 3.2.1-0.

I remember from the time we had no official 3/t twrp, that getting rid of the old format I needed to change fs type and then change back, because just reformating data as f2fs formated the dm-0 volume and not the underlaying fs on sda15. What always worked: mkfs.f2fs /dev/block/sda15 in twrp's terminal. i don't know, if this is still true, but with manual formating you are surely formating the fs on the sd device and not the dm device.

Good luck!

EDIT: yes I know that formating data is a pain in the ass, but currently it's the only - at least for some people - known solution. :(

EDIT2: You need to umount /data before manually formating.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
Yes I'm getting weird artifacts with arnova modded gcam 5.1
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
[MENTION=4472938]opethrocks[/MENTION] May I ask what you did EXACTLY to make it work?

My data Partition is already f2fs according to twrp. However, I formatted it again to f2fs within twrp 3.2.1-0, then tried again to install the latest xmas FW rom, but I still end up on the NLOS Boot animation (Pulsing NLOS Logo), nothing happens from here.

It seems you had the same issue, how did you solve it exactly?

Did you click "Change/Repair partition" or did you press "Format Data" button (under wipe options)? The Format Data button actually erases EVERYTHING including the internal storage stuff (Pics, Music, twrp backups etc).

I need to know whether you just formatted the /data Partition or whether you formated the entire internal storage. I'm on a A3003, using twrp 3.2.1-0 , Data fs is already f2fs

thank you
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
Let's see...

First I did a simple wipe data and caches.

Then I flashed the ROM and gapps.

Then I rebooted recovery because /data would not mount.

Then I formatted /data.

Then I rebooted and all was well.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
I see, but your problem was very different from mine. didn't have a problem mounting /data, in fact everything goes well with the install, it just won't boot afterwards. anyway thanks for your reply.

No idea why I'm the only one with this. Unless someone has any other ideas I will have to wait for a newer version hoping it fixes my problem, or switch roms.

Btw I attached pics from what i happening during install, the pic with theNLOS Logo is where the fun ends for me
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Is the 4th pic the formatting?

You need to FORMAT data (pic shows only WIPE). Please read my previous posting.

Perhaps it's confusing for you: wiping cache and system triggers a format of those partitions. Wiping data does NOT trigger a format, but a "rm -rf". As you can read /data/media is not touched, so only some files arendeleted, but the partition's fs is untouched.

If you don't feel comfortable with the described manual formating, I highly recommend changing fs to ext4 and then back to f2fs - just to be sure.

On f2fs vs. ext4: ext4 is more stable, much better tested and more grown up. The speed advantage of f2fs - if there is any at all in real life usage - is marginal. I decided to use f2fs on my device, because it's much more prune to issues (sic!), and I wanted to expirience theses issues first... I still don't know, why only some devices suffer from this. :( Anyway: in terms of reliability I would always opt for ext4 (though I want to build amrom with both options working).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Try attaced boot image. I reverted three commits from LA.UM.5.5.r1-06400-8x96.0:

Revert "msm: camerav2: isp: Reserve rdi ub based on image size" — nvertigo

Revert "msm: camera: Synchronize v4l2 subscribe and unsubscribe event in camera.c" — nvertigo

Revert "msm: camera: isp: Allocate kernel page and map to userspace" — nvertigo

BTW: did you encrypt your f2fs data partition?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
I know the difference between format and wiping. As I said before I did a format (not pictured here) for the system partition but not for the Data partition since it's already f2fs according to twrp.

Anyhow I got the Rom to boot. I wiped, installed the xmas Rom (no boot) and then I restored from my September Backup the "BOOT" partition only, and finally the Phone bootet with the new ROM installed.

My question is, am I fine running with this setup or are there some disadvantages running with the old boot partition? I imagine this is not ideal, since I'm on the old Kernel,right? Any idea why it wouldn't boot with the latest boot partition?

Again, I did not try formatting the complete /data partition because it's already in f2fs and I really want to avoid doing that. Putting all stuff back into the phone will take me half a day. Besides, opethrocks had an altogether different issue so it's not certain re-formatting /data would solve this.

So the issue was with the Boot partition... any idea what might exactly cause the problem?

Thank You for your support
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
The actual "data" partition comprises of both the internal storage and the "data" partition you're talking about. You'll have to format the entire thing. That's what I'm about to do lol, I know it's a pain, but I'll take logs before I do that, probably this weekend.

Like nvertigo67 already mentioned, /data/media isn't touched when you wipe the data partition. And the system partition is supposed to be ext4 btw by default.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
[MENTION=3456089]nvertigo[/MENTION] the modded boot.img worked perfectly. And no I haven't encrypted data since formatting...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Yes I know that, hence why I'm trying to avoid formatting the whole thing. Why do you want to format your data? Are you having issues installing as well?

Also, for my understanding: ext4 is preferable overall, but in order for this ROM to work we need /data to be f2fs, correct?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] spida_singh:
I also had this and the boot image fixed it for me

Thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No. NLOS can run data on ext4 as well as on f2fs.

WARNING:

Using an old kernel may work (I don't support this setup!!!), but may lead to new issues/side-effects like freezes, panics and data loss. With the pre caf-06300 kernel the installation does not meet new sec updates criteria, since the asb patches are partly implemented in rhe caf updates. Also the next update will fail to boot, too., since the issue (incompatible f2fs) is not solved. I know formating data is a pain in the ass - but currently it's the only working solution I know of. :(
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Because it's the only working solution, I know of. Please read my postings and the links to laos thread in my postings again. As stated many times: I do NOT suffer from both issues - but as you can see in laos thread, the solution for both is the same. I don't know, why my f2fs partion has no problems, but everything I read here and in other threads is that reformating is the solution. And honestly: if you have read all that, I don't understand you still have that question.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Last Update for this year!

Build 20171230

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.

Changelog:

mcpu: use cortex-a53 with stock clang/llvm. — nvertigo

Revert "msm: camerav2: isp: Reserve rdi ub based on image size" — nvertigo

Revert "msm: camera: Synchronize v4l2 subscribe and unsubscribe event in camera.c" — nvertigo

Revert "msm: camera: isp: Allocate kernel page and map to userspace" — nvertigo

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

[SIZE=+2]DOWNLOAD[/SIZE]​

Happy flashing!

May the source be with you and yours in 2018!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Unfortunately this is not working for me. I changed /data from f2fs to ext4 and back to f2fs, wiped everything and try again to install, but the rom just won't boot. The manual mkfs.f2fs /dev/block/sda15 command doesn't work either, I get two Errors: "In use by system" and "Not available on mounted device" although I unmounted /data partition (Yes, I am sure I unmounted). Anyhow I guess change file system did work for formatting but it didn't solve my problem.

I do not know what else there is I could do, I never had such problems before. I spent hours trying to troubleshoot this myself but no game. Sadly I'm gonna have to switch to an OOS Rom now, thank you anyaway
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Relax, breathe... ;)

In twrp's shell use the mount command to see, why sda is in use. I guess dm-0 container is still active. Are you asked for password, when entering twrp? If so, the eesiest solution is not giving it, proceed to twrp's startup screen and format (if sda15 is not decrypted and therefore dm-0 isn't started twrp has no other chance then foemating the underlaying block device instead of dm-0). What's about pstore? Empty on every try?

Is the rom booting with ext4?

EDIT: try [MENTION=3878718]lord_[/MENTION]Boeffla's kernel (has the latest f2fs updates) or [MENTION=470754]Franco[/MENTION]'s kernel (not updated with latest laos updates - incl. f2fs updates).

EDIT2: Try to save the twrp logs -mespecially from formating.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Rom is not booting with ext4 either. I tried Boefla Kernel and it says "Recognized Device: Oneplus 3" and then aborts because of not compatible device. Same with Franko Kernel, can't install it, incompatible Device. Lineage Kernels used. I'm on a 3t A3003....

Attached the pic of what shows with the mount command after unmounting everything in twrp. Also attached logs after changing format and then additionally manually trying to format with console

Tried Audax OOS Rom for testing, it installed without any problems :rolleyes:

Worst thing is, now I cant even restore my old (working) backup, it won't accept the unlock pattern on the lock screen.

Update: I did manage to install the latest boeffla BETA kernel, however it is still not booting with it. Only thing that makes boot possible is restoring my old /boot partition in twrp
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
franco & boeffla kernel: the anykernel script is checking for ro.product.device of the rom (not of twrp), which is oneplus3t on lineage, but oneplus3 on oos AND twrp. I have set this to oos value, because it was the only way to make play services accept op3t as certified device. Just uncomment the checks, if you are sure you have greped the correct kernel image.

Mismatching lockscreen pin/pass is a long known issue: after restoring the backup (still in twrp) delete /data/system/locksettings.db. Reference: https://xdaforums.com/android/software-hacking/remove-lockscreen-recovery-t3530008 (in your case locksettings.db is sufficient)

Removing encryption and redoing user fs: this is worth a try: https://xdaforums.com/oneplus-3/help/removing-encryption-t3422581
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Sounds like you use a outdate/wrong version of TWRP. Are you sure you are on the latest version for 3T? If you phone tells you, you got a oneplus 3 while trying to flash a kernel or rom, your TWRP is borked. Had similar stuff before.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
OT: Happy New Year to everyone!

EDIT: I mxed up ro.build.product and ro.product.device. It's corrected now.

If the assert fails when checking the properties of twrp you would be right. But the issue here has a deeper going cause:

On OOS ro.build.product is oneplus3. On twrp properties ro.build.product is oneplus3. On NLOS ro.build.product is oneplus3 (otherwise play services will not accept the device as "certified".

On LOS builds ro.build.product is oneplus3t.

anykernel2 is - at least for boeffla and franco - mounts system and checks the build.prop of the installed rom for ro.build.product for oneplus3t.... Boom!

Just remove the assert from the customs kernel update-binary, which is a bash script for anykernel2.

EDIT:

After rethinking the above issue with custom kernel update-binaries, I came to the conclusion this is easier, then unpack, change, pack and resign the flash script.

If you want to use i.e. franco's r33 or stable boeffla, try this:

flash rom according to your common routine. Do not reboot now, but:

mount /system.

open terminal.

type (without double quotes): "sed -i -e 's/ro.build.product=OnePlus3/ro.build.product=OnePlus3t/g' /system/build.prop".

flash custom kernel.

return to terminal.

revert the prop changes by typing (without the double quotes): "sed -i -e 's/ro.build.product=OnePlus3t/ro.build.product=OnePlus3/g' /system/build.prop"

reboot to system.

EDIT:

BTW: [MENTION=3044422]mad-murdock[/MENTION] is right: if you manage to put an op3 twrp on a op3t, the error message would be the very same.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE

Build 20180106

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.

I've done some testing with toolchains: I couldn't find any advantage using Snapdragon llvm, so I decided to stay with laos stock clang. I also found that using a gcc-6 based cortex-a53 toolchain on the kernel (instead of 4.9) makes the resulting kernel a very little bit more bat friendly. But I did NOT found any advantage of UBERTC/Linaro compared to plain (no Linaro patches and enhancements) gcc-6 build for cortex-a53.

Considering those observations, I decided to use:

kernel: cortex-a53 optimized gcc-6.4.1 (crosstool-ng, config: https://bitbucket.org/nvertigo/aarc...og.bz2?at=master&fileviewer=file-view-default)

All other c- and c++-code in the rom: stock laos llvm/clang

Your milleage may vary, but to me this combination is CURRENTLY giving the best ballance of performance and bat life. Let me know your impressions.

Changelog:

Remove Snapdragon LLVM. — Nvertigo

Add aarch64-linux-android-6.4: stock gcc version 6.4.1 20171215 (crosstool-NG crosstool-ng-1.23.0-288-gadaa3a5d

Remove aarch64-linux-android-6.x. — Nvertigo

Remove aarch64-linux-android-5.x. — Nvertigo

Remove aarch64/aarch64-linux-android-4.9. — Nvertigo

Remove aarch64-linux-android-4.9-kernel. — Nvertigo

Fix derp in opting in LINEAGE_VERSION_APPEND_TIME_OF_DAY. — nvertigo

Opt in LINEAGE_VERSION_APPEND_TIME_OF_DAY. — nvertigo

Use GNU gcc 6.4.1 for kernel building. — nvertigo

gcc-6.4.1: disable unused-const-variable warnings. — nvertigo

gcc-6.4.1: remove unsed variable fsm_en. — nvertigo

gcc-6.4.1: fix a bunch of (misleading) indents. — nvertigo

bluetooth: hci_sock: Fix warning detected by gcc 5.3.1 — NewEraCracker

tfa9890: tfa_container: Fix warnings detected by gcc 5.3.1 — NewEraCracker

treewide: Fix code errors detected using Linaro GCC 6.3.1 — Sultan Alsawaf

treewide: Properly fix use of uninitialized variables — Sultan Alsawaf

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

[SIZE=+2]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE

Build 20180109

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.

Some new fs, fs-crypt and sdcardfs patches has been merged upstream. Perhaps these also solve the remaining issues with bootloops, though I have only very little hope these will avoid the necessity of reformatting the user-data partition.

Changelog:

fscrypt: move to generic async completion — Gilad Ben-Yossef

crypto: introduce crypto wait for async op — Gilad Ben-Yossef

fscrypt: lock mutex before checking for bounce page pool — Eric Biggers

fscrypt: new helper function - fscrypt_prepare_setattr(

fscrypt: new helper function - fscrypt_prepare_lookup(

fscrypt: new helper function - fscrypt_prepare_rename(

fscrypt: new helper function - fscrypt_prepare_link(

fscrypt: new helper function - fscrypt_file_open(

fscrypt: new helper function - fscrypt_require_key(

fscrypt: remove unneeded empty fscrypt_operations structs — Eric Biggers

fscrypt: remove ->is_encrypted(

fscrypt: switch from ->is_encrypted(

fs, fscrypt: add an S_ENCRYPTED inode flag — Eric Biggers

fscrypt: clean up include file mess — Dave Chinner

fscrypt: fix dereference of NULL user_key_payload — Eric Biggers

fscrypt: make ->dummy_context(

ANDROID: sdcardfs: Add default_normal option — Daniel Rosenberg

ANDROID: sdcardfs: notify lower file of opens — Daniel Rosenberg

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

[SIZE=+2]DOWNLOAD[/SIZE]​

P.S.: chagallwifi build is updated as well.

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ndep:
guys, I've been using this rom for a long time smoothly, probably almost a year, on my oneplus 3. Now that it's 2018, I thought I should give it an update, but now the leading post is saying "only for oneplus 3T"... the memory is already vague about this but I think somewhere in the past it's saying to be compatible with both 3/3t, right? thanks.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Most properly you mixed up forums: this is the 3t forum. My rom has always been for 3t only. It won't flash or boot on OnePlus3.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ndep:
oh sorry! it turns out I actually mixed up my correct phone model no... I am using 3t. :angel:

BTW, I know you are not supporting custom kernel here, but here is a quick question, do you happen to know whether I could flash ElementalX 3.18 for los on your ROM? I recently purchased their kernel manager, which keeps prompting a kernel update...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] RaEsAcademy:
You can disable the notification in the app settings.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You can. If ElemenralX relies on the same asset mechanism like boeffla and franco flashable zips, follow the steps I recommended here.

EDIT:

General Reminder: There is noch such thing like "too much nandroids".
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ndep:
haha, gotcha, thanks for the reminder.

will try that next week.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (January security patch)

Build 20180116

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.

Changelog:

Xtra Fixes - https, version check & version 3 — Wyatt Riley

January security update.

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

[SIZE=+2]DOWNLOAD[/SIZE]​

P.S.: chagallwifi build is updated as well - aptx enabled.

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (WireGuard-0.0.20180118)

Build 20180120

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.

Changelog:

Revert "Track our own version of android_vendor_codeaurora_telephony." — Nvertigo

Update WireGuard to 0.0.20180118.

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

[SIZE=+2]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Update: Sdclang

This build is compiled from the very same source code then the 0120 build. The only difference is the clang/llvm toolchain: this one is build with SDCLANG enabled (3.8.8). You can dirty flash (wipe cache and dalvik) both versions back and forth. Releasenotes apply for both builds.

Please try both a couple of days (at least 2 charging cycles), and tell me your expirience with both builds, especially regarding bat life and performance. I depend on your feedback. Thanx in advance.

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

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

Thanx in advance!

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vinoxflame:
1st time trying this ROM,

data, cache and system already on ext4

done a full wipe - flashed ob15 firmware - ROM - dynamic gapps mini - reboot to system

waited 15 minutes for it to boot but it did'nt, stuck at boot animation (fading NLOS logo)