yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Interesting. This is the first report of this with ext4. Can you supply us with information on the exact versions you are using, please? Is anything left in pstore? What recovery/rom setup did you use prior to NLOS? Did you try the insecure bootimage? Can you pull logs with the insecure bootimage? Since I can't reproduce this, I relay on your infprmation.

EDIT:

Try attached bootimage: unzip and flash the contained boot.img as image in twrp-3.2.1-0 rightbafter flashing the rom.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] sikica133:
2 days with regular 20/01 build: averaging 10%/30min ~5hrs sot. standard results for me

1 day with snap compiler: way worse xD roughly 15%/30min. will report if it suddenly gets better, but doubt it. seems much snappier though.

clean flashed both, same apps, same settings
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vinoxflame:
Came from OB21 (encrypted if that matters), twrp-3.2.1-0

here's how i installed this ROM - did a wipe(data, cache and system) flashed the ob15 firmware

flashed ROM then the boot.img you provided

rebooted the system - still stuck at the nlos boot animation(w/ blue LED light)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] sikica133:
can you rollback from oreo to any other N rom and boot it up using that method? doubt this is nlos issue, rather recovery/rollback prob. you should 1. format data and 2. try eng.stks recovery
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I've suspected exactly this issue (downgrading from O) for the situations, in which the bootloop is not f2fs related - but I never got enough information to have to offer more then a suspicion.

Encryption MAY be something, whats changed between N and O. But if you FORMAT (not only wipe) data it's removed anyway. For me these versions works perfectly:

https://eu.dl.twrp.me/oneplus3t/twrp-3.2.1-0-oneplus3t.img.html

https://androidfilehost.com/?fid=889764386195918677 (BeansGapps-Mini-7.1.x-20170725.zip)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cabrox:
Sorry if it has been discussed before in this thread but I can't find it.

Is there a way to use a non-eas but los-compatible kernel with this ROM, or it just supports the original packed kernel?

Thanks in advance

EDIT: Sorry I did not search enough, https://xdaforums.com/showpost.php?p=74867476&postcount=2070 , question dismissed!

2nd EDIT: OMG, it has happened a lot of things with this ROM in the last month, now I feel a little silly for making that question before.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vinoxflame:
Hi, I just tried flashing sultan's LOS and it booted even coming from an oreo ROM.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
What's about the test boot image? Whats about logs with the unsecure boot image? What's about pstore?

We can debug this together - but since I can't reproduce this on my device, I relay on getting the information from your side. I'm sure you can imagine, that asking over and over again and getting only parts of it, doesn't make this easier... :( (or keep me motivated to fight this - remember: it's working for me...)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE

Build 20180131

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:

Mantainance: synced to los.

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

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

Happy flashing!

P.S.: chagallwifi build is updated as well - f2fs for cache and data fixed.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Rhodesgod:
is this the los or has additional options ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
It's a LaOS with some additions. You can find and read them on the 1st post.

(Some examples: Substratum support, microG support, etc...)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] abdulmajed1:
No Update Oreo?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Not now, but later: current los O codebase is IMHO early beta (los staff considering los-15 builds even alpha). My approach is delivering a stable daily driver:

You get, what I use. Stability - in the meaning of reliability - will always be my first priority.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] abdulmajed1:
Bootlogo last update Why :(
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
???

Last update of rom has no bootlogo (no firmware at all). The bootlogo choices were updated months ago.

Sorry, but I don't understand your pm, neither.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] abdulmajed1:
Im install this rom

lineage-14.1-20180131_145631-NLOS-oneplus3t.zip

But stopted Nlos Logo After install
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Format data - not only wipe data (use the "format data" button from twrp-3.2.1-0 wipe screen - just wiping data or formating data via twrp-3.2.1-0->wipe->advanced wipe->tick data... is NOT sufficient!).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Oreo for the impatient

OT:

If I wouldn't need my device for nlos development, I would try [MENTION=6663552]DarkExistence[/MENTION] AICP Oreo builds.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] abdulmajed1:
​

I'm sure you made a full format before installing Rom

And my Twrp This

twrp-3.2.1-x_blu_spark_v8.61

---------- Post added at 06:42 PM ---------- Previous post was at 06:39 PM ----------

​

This my ROM Now
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Julian_os:
Same here
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I've got some new information regarding the crackling noise when a wired headset is plugged in.

Today I installed the build from the 3rd February. I called two different people and they said the call was clear (no crackling).

I was so happy that the one issue that stopped me from using LineageOS was gone. I restored my apps and used my phone as normal.

I called my friend about 10 minutes ago and he asked if I'd been playing with my phone as the crackling noise had some back.

I genuinely do not know why the crackling noise is happening and I don't know where to start looking to find the cause of the issue.

Does anyone have any ideas?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Wow, just wow. 0℅ battery in 2 hours.

Disclaimer: build from latest source. No idea if you can reproduce on latest build yet. Also a lot of apps installed.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
You said it happened after restoring your apps. Might be a long shot, but maybe it's app related? Maybe you can find out if and which app. Then we could reproduce and maybe fix.

If you restore your apps with titanium, you only restore user apps?

edit: where has the quote gone? xda plz!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Working here without issues.

There might be a workaround though. It was reported to work earlier on this thread. It sounds stupid, but please just try and report back:

Boot to recovery. Backup data partition. Then restore data partition only. Reboot. Alert slider should work.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
It works for you, but did you by chance perform a full wipe before flashing this build?

That workaround, it was me who posted it here. It worked earlier, but not on this build. I've tried, twice actually. :(
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] apascual89:
Hey, quick question, what gapps package did you flash? When you clean flashed, did you complete the LineageOS setup wizard or did the gapps change it for the aosp one?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
I flashed "open_gapps-arm64-7.1-nano-20170203.zip" that I downloaded earlier today.

Now that you mention it, it could easily have been the AOSP one. How to spot the difference?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] apascual89:
The LineageOS is bright white screens with the lineage branding. If you want to check if it's the gapps, flash clean without gapps and check the slider.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
(without reading all replys and probably missing something):

I also use pixel launcher. But I use the flashable zip here from xda. Difference between installing on system and on userdata is, on system it has the privileges to allow to show google now if you swipe left. AFAIK as an user app, it cannot.

Same goes for action launcher 3 (as far as I read - considering to buy to be sure): If it is a system app (converted by titanium and the like), it has google now integration, installed as a user app, it has not.

For some people like me, the google now integration is an essential part. Still, you can download and flash the pixel launcher zip. Correct me, if I am wrong, I switch to the userland app then asap.

---------- Post added at 01:52 AM ---------- Previous post was at 01:45 AM ----------

[MENTION=5073087]bu44er[/MENTION] - this was meant to go to you. No idea why the quote disappeared, but anyway, another notification. I hope we can figure this out. Once we can reproduce the crackling, there is a high chance its fixable.

---------- Post added at 02:31 AM ---------- Previous post was at 01:52 AM ----------

I assume you meant to say 141-work. starting build now and going to bed.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Yes.

On alert slider: please get a logcat and dmesg from directly after setting middle position to something different (or the top positin or both).

Have you tried setting all to none, and reenabling?

Have you tried different opengapps nano package (assuming there is a reason, for not using the recommended package)? Have you tried booting without gapps?

Is this only happening on different versions of this rom; or have you expirienced similar issues on other roms?

What recovery are you using? What are the exact steps you take to install? From which rom do you come?

I have clean flashed different versions of this rom, but never suffered from this - so atm I have no idea, how to help you. It's hard to fix something, I don't expirience, I don't have logs or no error/warning in logs. So we need to try to gather as much information aa possible.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Trying the source build libril was on my todo-list, anyway. It's just happening earlier. Rule of thumb: build from source as much as possible, as long as it doesn't effect stability.

Of course I'll wait for [MENTION=3044422]mad-murdock[/MENTION]s and your confirmation, but if it works for the two of you, I'll put it in the next build.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Sadly, I don't find the time to follow your thread on a regular basis - sorry for this lazy question: what gapps package is the least problematic to your expirience?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] l0veysingh:
Sorry edited.....posted in wrong thread
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
There we go. THIS IS IT!

[MENTION=4405529]nvertigo67[/MENTION] [MENTION=3515982]apascual89[/MENTION]

It has been a busy morning for me. :)

A flash without any gapps package gave me a totally different setup experience, indeed with the lineage branding and a working slider in the end.

After the setup, I can flash either the recommended gapps package or the most recent, the slider keeps working so it's a setup-issue only.

So, having established that, I cleaned everything and used the recommended package 20170120 straight after flashing the OS, which also worked fine. Like your OP promises.

Nvertigo, I know your OP clearly states:

By not using that specific package I broke it myself, sorry for that. In my defence, I've been actively flashing and toying around for many years and I've not encountered the situation where only a specific compile date of gapps would work. I'm afraid more people will think so and make the same mistake as I did.

I diff'd the gapps logs from both installations, the only notable difference was that the non-working gapps install has this extra line printed in the log:

Runtime Permissions | Reset

(not sure if this is relevant)

So, long story a bit less long:

OS + recommended gapps package = Lineage setup, results in working slider

OS + recent gapps package = AOSP setup, results in not working slider

OS only = Lineage setup, working slider. Either (any?) gapps package can be flashed afterwards, slider keeps working.

I would recommend spending a few more words on this in the OP, people should really stick to the download you've linked ... or face the wrath of the alert slider. ;)

(@Julian_os, you had the same issue, perhaps this will solve it for you as well?)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
Off-topic but

When I take a picture with my front camera, most of the times the colors will be washed out or to bright. This only happens on 16mp, not in 4mp mode

Is there any workaround? Is it a known-bug?

thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Disclaimer_1: gapps suckz (feeling a bit like Cato the older about Carthago)

Disclaimer_2: Without [MENTION=3515982]apascual89[/MENTION] input, I wouldn't have related this to gapps, too. Thanx!

I've changed op with a link to my posting on why gapps is restricted 2 days ago. What more should I write about? I can't force anybody to belive me... ...people read op just once - if at all, don't stick to the directions, and wonder if they have lost their way... I try hard, not only to say "do this, followed by that and then...." but also to give an explenation on why this way is reasonable, but in the end it's up to every individual, how to deal with this.

Happy it is solved for you! May the other user with the broken slider confirm it's solved? Thanx in advance.

EDIT:

Disclaimer_3: you are allowed to hit the thanx button on [MENTION=3515982]apascual89[/MENTION]'s posting!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'm 100% sure I did nothing to your devices data partition!

Please use official twrp-3.2.1-0 (on the official los thread some users had difficulties with blu_spark) and format data (wiping data or formating by ticking data and changing fs IS NOT THE SAME!!!! You need to get rid of the complete container - use the damn format data button with official twrp-3.2.1-0!).

If the old build works, but the current build doesn't, it's incompatible data fs for >95%.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] abdulmajed1:
Do you mean make a format like pictures and videos?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No.

I mean: boot to recovery (official twrp-3.2.1-0), tap on "wipe", tap on "format data" and swipe to confirm.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hypnoc:
I have the same issue comimg from NitrogenOS 8.1 with ext4. I'm going to do this but I'm a little confused.

What is pstore?

Which partition do I flash the image file, boot or system image?

And what do I do after I flash it?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Persistant Storage (/sys/fs/pstore)

I know I'm an awfull ****hole, but I can't resist this one: what do you think, why it's called boot.img? *lol*

Honestly: it's better to ask once more before bricking the device! Flash boot.img as boot partition.

Power off device, set up adb, if "waiting for device" shows up, power device on and cross fingers, that the bootloop occurs AFTER adbd is fired during boot... (don't forget to replace fw again, if coming from O.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hypnoc:
I did it. Sadly, logcat didn't generate any log.

I knew it sound dumb and think it was supposed to be boot as the name suggest too. :D

But you said "flash as image" and I was unsure if it could mean system image. So, just to be sure. ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I've never understood people flashing funny things without knowledge or asking on their 400€ devices. Asking once more is absolutly ok. Then again the leittle devil in my head said: you can't let go this chance... ;) Ibelive you got that right... ;)

No logs means adbd isn't started. Try to get pstore:

If the bootloop occurs, switch of the device. Then directly boot to recovery. I the advanced menu start filemanager or terminal and copy the complete content of /sys/fs/pstore/ to sdcard or usb-otg (if you have an usb stick available - prefered and easier). Use adb or the stick to transfer the saved pstore content to pc, tab or something with internet connection, put it in a zip and attach it here.

BTW: an usb-stick for nandroids and other backups is always a good idea - especially on sdcard-less devices (or devices with sdcard added to system memory). It's also easier to copy logs...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
TWRP Version Ambiguity

Lately I've referred to "official twrp-3.2.1-0" many times. I always thought this nameing- and version-conventions have been biunique. Sadly this isn't true anymore!

[SIZE=+1]The original version 3.2.1-0 was non-unified and based on Nougat kernel sorces. This version (and the complete 3t history) has been removed from TeamWin's device downloads, and got replaced by an unified, Oreo kernel based version![/SIZE]​

Anyway, whenever

[SIZE=+1] I've referred to "official twrp-3.2.1-0", I've talked of the original version!!! From now on I will refer to "original nougat twrp-3.2.1-0"[/SIZE]​

Since this version is removed from the TeamWin Downloads, I've placed it on my gdrive:

[SIZE=+1]DOWNLOAD: original nougat twrp-3.2.1-0 for OnePlus 3T[/SIZE]

Sorry for any misunderstandings, but changing the kernel sources from N to O without changing the version and removing the previous images is something, that just havn't come to my mind... ...till now... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE

Build 20180206

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.

There has been some confusion on twrp versions, lately. For nlos always use the "original nougat twrp-3.2.1-0".

If you have issues with bootloops or access to data with some apps, use "original nougat twrp-3.2.1-0" to FORMAT(!) the data partition of the device:

Backup all your data (eveything under /sdcard/; i.e. Downloads, Vodeo, DCIM, etc...)

Boot to "original nougat twrp-3.2.1-0".

Tap on "Wipe".

Tap on "Format Data".

Confirm with swipe. This actually clears your complete data partition, including all data and encyption.

Check if the newly created fs is the type you want (ext4 and f2fs is supported) - eventually change it to your liking.

Just follow the OP's procedure for first installs from OP's "Installation" section (clearing data is allready done, of course).

I have reintroduced lineageos Snpdragon Camera (Snap), because of it's new implemented QuickReader - the issue with crashes on one of the first ff-cammtaken pics is still present. Wiping system and reflashing BeansGapps-Mini-7.1.x-20170725.zip is highly recommended!

Changelog:

op3: Address SELiunx denials — dianlujitao

op3: Unbreak perfd — dianlujitao

Revert "Drop LineageOS/CAF SnapCam aka Snap." — nvertigo

qcacld-2.0: Update to LA.UM.5.5.r1-06700-8x96.0 — dianlujitao

Merge tag 'LA.UM.5.5.r1-06700-8x96.0' into cm-14.1 — dianlujitao

ANDROID: xattr: Pass EOPNOTSUPP to permission2 — Daniel Rosenberg

ANDROID: sdcardfs: Move default_normal to superblock — Daniel Rosenberg

ANDROID: sdcardfs: Fix missing break on default_normal — Daniel Rosenberg

f2fs: Reset to v4.14-rc1-3.18 — dianlujitao

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] sikica133:
i assume snap is still buggy and generally worse than gcam mods? trying to decide whether it's worth it to wipe 20/01 build
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
As stated in the announcement: snap is still buggy.

Your assumption seems to be a misunderstanding: I've replaced aosp cam with Snap - you can still use your preferred cam apps, like GCam and OpenCamera.

I assume you mean wiping data or formating data by "wipe 20/01 build". If 20/01 is running fine for you, just wipe cache, dalvik and system. Flash 06/02 build and gapps (and - if wanted - a root solution). You do not need to fiddle around with your installed GCammat all, since youmdon't need to wipe or format data.

If you suffer from bootloop, you need to reformat the complete data partition (detailed step-by-step description is in the last announcement). This will delete ALL data from your device.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] sikica133:
...rant, not nlos related...

I know I can use alternative cams, the thing is, messenger lite and some other apps I use misbehave when it comes to gcam mods and are unable to take the pictures and send them. They'll snap the picture fine, just wont allow sending. Yeah, I can do it manually and add the photo as an attachment, but thats just inconvenient. Aosp cam on the other hand has no such problems, so I use both, its just that aosp cam is bad :P. So was just wondering whether snap was worth the upgrade. And by upgrade I mean clean flash. I don't do partial's so no data and a ton of wasted time on re-logging in apps ^^ And yeah, I tend to push gcam as well as nova/adaway/greenify/etc as system apps via flashable zip along with a cleanup script, gapps and magisk (4in1 package yay), so yeah, it's gonna get flashed anyways :P

TLDR: It's not really the flashing part thats the problem, rather is the snap worth re-logging into everything xD

TLDR2: Never had any bootloop issues on NLOS. Guess it's the clean flash that does it for me
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx for pointing out the interoperatability issue with Snap - I wasn't aware of this.

I reintroduced Snap because of QuickReader. Since therenare lots of qr-code readers around, I tend to go back to aosp cam. But I would like to think about and hear/read some more oppinions.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Nlos-14.1: Eol

Ladys and Gentleman, ( ;) )

thanky you very much for using NLOS-14.1.

I want to give you the opportunity to mentally prepare for the end of life of your rom (NLOS-14.1). This doesn't mean 14.1 support is droped immidiatly, there will definetly be a Feb. Security Patch update. Depending on my progress on NLOS-15.1 there will also be an Mar. Security Patch Update, if 15.1 is not running to my satisfaction.

As you can see, NLOS Oreo will be based on LineageOS again. I did not know an ETA, but have started working on O.

May the source be with you, NVertigo
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Ayyyyyy

Recently switched to OOS Oreo OB's. Gonna switch back to NLOS if you get 15.1 up haha.