yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
[MENTION=7898890]The T[/MENTION]wo users having issues with 17 booting:

You both tried a dirty flash, aren't you?

Is it booting if you also wipe system (and reflash gapps)?

Is it booting on a clean flash?

Is it stopping on bootlogo or on bootanimation?

If it hangs on bootanimation, gimme the complete content of /sys/fs/pstore.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
I tried wiping system, and even clean flashed and still won't boot. It hangs on boot animation while the led is blue. How do I get /sys/fs/pstore? Adb pull during boot?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Maybe your download is corrupt
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If in bootanimation DIRECTLY boot to twrp and copy the content from /sys/fs/pstore to sdcard.

The easiest way to do this is download zip and zip.md5sum to the very same directory. If zip.md5sum is present, twrp does the check for you, and will not install the zip if the checksums mismatch.

An other idea: if some vpn software is active it MAY interfere with the wireguard kernel additions.

On Wireguard: since no one is using wireguard (at leaat I got null feedbaxk, when I asked for a real world test) in a production environment, and the way wg is fetching and patching itself in the rom is violating my way to test something (only clean builds work reliable), I'll drop wg again dor now. See: https://xdaforums.com/showpost.php?p=74899802&postcount=116
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
one of two users with 20171217 boot issues

Yes, dirty flash first time in my usual four steps, which are

1) remove Magisk by uninstall.zip

2) flash NLOS ROM

3) install Magisk by flashing 14.0 Magisk .zip

4) Add some media files with a .zip

These four steps have worked for months.

Second time, tried dirty flash of just NLOS after cache/davlik wipe.

Same result in all cases : boot animation (i.e. the fading 1+ logo followed by NLOS logo varying brightness) displays indefinitely.

Third try: Wiped dalvik, cache data (but not data/media), and system, tried flash of NLOS file without anything else (no gapps, no beans)

Result: the same, boot animation (i.e. the fading 1+ logo followed by NLOS logo varying brightness) displaying indefinitely.

(See above - clean except for internal storage. )

Boots to 1+ Start warning/boot selector, 1+ splash screen, NLOS logo 1+ icon fade followed by pulsing logo. (This is bootanimation, as I understand it.)

Will do at my earliest opportunity. THis phone is my daily driver for work and it is used heavily all day.

The F2FS delay in TWRP startup means I have to budget my time on reboots to recovery. (Anyone who knows of a 3T TWRP that gets around the F2FS start-up delay, let me know please!)

As mumapizza suggests, I'm going to redownload a fresh copy in case the download is somehow corrupt. I did turn on checksum verification in TWRP flash, and the file passed it. I have had corrupt downloads occasionally (as in maybe twice in six years), but the flash process always detected the corruption.

By the way, over these months NLOS has been the most stable ROM in my experience, including family members who stick with stock Android or iPhones. Very good work.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
For everyone who wants to test and use wireguard for free here is a guide from sultanxda thread: https://xdaforums.com/showpost.php?p=74820584&postcount=3369

Wireguard is realy nice and quick vpn protection if your out on public wifi, without draining the battery like openvpn.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] kixx22:
How SoT on this ROM?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Status & Future

I like WireGuard. I like eas. But what I like more then these two: a rom booting on everybody's 3t!

When I started to put Wireguard in, I thought it's a fire and forget missile. Nobody has known (or - at least: me) that this triggered the insanity of my eas patching... The good point: bat life with hmp is better, then at the point when I had put eas in. When I implemented eas bat life was better then with hmp; now it's at least on the same level evtl. even slightly better with hmp.

(@mumapizza: though I havn't believed you - after some days of usage, I think you were right, now.)

The time I've spended on nlos' kernel it's missing now. There are two points even more important to me then nlos: family and friends! So this is my plan:

I want to get out a build booting for evrybody before Christmas - putting back wireguard after New Year. ATM I would like to stay with hmp (no eas), because I honestly fear the implications of errornous merging of 450+ patches and the resulting complexity of side effects.

The next build will be without SDCLANG, UBERTC and additional optimizations.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx. That's a report!

I would have the clean flash expected to boot.

If the md5sums are matching the propability of an corrupted download is near 0 - very near... ;)

I'll put out a test-build later - try that. If that also fails to boot and pstore is empty, I'll provide an unsecure bootimage, to try to get an early adb connect.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
These zips are build from sources synced around 8:00 h UTC. Both are build with los stock llvm and los stock gcc-4.9 kernel toolchain. These are NO test-builds in meaning of stability and usability: everybody with no issues should directly update to the wireguard zip. The two usees with booting issues should start with the wireguard-less build, and progress to the wireguard build only if this is working.

Standard toolchains build without wireguard

ROM: https://drive.google.com/open?id=1nVBzjzGntd-ol4Zbjfzf6XJWUSFqe9Sm

MD5: https://drive.google.com/open?id=1dKtwGFa3CUfBVQNc3MrRBecTL-JchSS6

Standard toolchains build including wireguard

ROM: https://drive.google.com/open?id=1mjpQmZ_oLnQTJoOBKYVfQ874-0PIp2TE

MD5: https://drive.google.com/open?id=1TX71TPpLwBYXt7Q-lo-82ORN5lkTV9de

[MENTION=7898890]The T[/MENTION]wo users with boot issues:

Dirty flash, but include system-wipe and gapps-flash. Leave out root for first boot. If it hangs, try booting directly to recovery and try to get the content of pstore. After that wipe dalvik and cache and try booting again. Wven a second dirty flash is worth a try. If that all fails: drop me a note, and I'll provide an unsecure build.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
The 12/20 no wireguard build won't boot for me. I used twrp 4.0.2-1, wiped system, flashed ROM then gapps. I was able to grab sys/fs/pstore. https://drive.google.com/file/d/1Z1QwGRIQOBbbMKgyjoyvbSrtDpqeRfmk/view?usp=drivesdk
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
In /sys/fs/pstore there should be a second file named console-ramoops, isn't it?

Is data encrypted? If so: which fs and on which platform have you done the encryption?

Are you 100% sure, you are using ob15 fw?

Would you try this build (and everybody else, too - because this is the release candidate for xmas build), please.

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

MD5: https://drive.google.com/open?id=1R74nOKv7H7GdeUIVAtuiiECJuWWzkQxQ
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
In the link I posted is the pmsg-ramoops-0 file, there was no console-ramoops. I'm definitely using ob15. Data is encrypted. And it was originally encrypted on OOS iirc.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Is xmas-rc1 working for?

If not: I'm clueless. Do you have any ideas what could be the difference from your setup compared to mine? I'm running out of ideas. :( I don't understand, why removing eas breaks booting for you, but not for me - there has to be a difference. What ammI missing?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yohannos:
[MENTION=4405529]nvertigo67[/MENTION]

I had bootloops with 20171217 plus 20171220-no-wireguard -- but tadaaaa the latest pre-xmas release work pretty fine! :o I never had problems with this perfect rom for half a year (dirty flashing) until this damm 20171217 ruined it all. my config now and before is trwp 3.2.01, fw ob15, magisk 14, beansgapps 20170725. the only difference is that i changed data partition to not encrypted (due to installation of omni8) and ext4 (due to faster trwp-bootup).

after this terrible bootloop from 20171217 on I tried a lot: clean flash (complete data, system etc), no rooting, starting from null (going back to oos 4.02) but nothing works. I will try to decrypt data again to see whether this might be a problem and report soon.

I have to admit I was using omni rom 8 to test oreo for a few days - but (i know its not fair, because 8 is in such a early state) this rom is the best i was using for 5 years. thanks a lot.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
12/20 no wireguard fails for me too.

In TRWP, I navigated to /sys/fs/pstore, but there were no files there.

To make sure there was not anything funky about my phone, I clean flashed the lineageos.org 12/15/2017 combined 3/3T ROM. Booted correctly. Now I'm back on nandroid-restored 20171213 NLOS.

Interestingly, my Android PIN was not recognized after restoring NLOS. I recovered by deleting the related files in data/system. (I do not use a start-up pin with TWRP). Explainable, because data/system is out on the SD card. I really don't want to wipe that.

Encrypted: yes, as was set by default

File system: F2FS for data, I beleive all others are ext4 (all default, never changed)

Firmware: modem shows date of 09-15-2017. I have missed few iterations of NLOS and no "-firmwares", to my knowledge.

Will try the latest build.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
OT:

This is a known one - at least for M and N roms. I guess for O roms, too, but I have never tested an O rom. The first time I always disabled pass/pin before backup, and setting pass/pinmafter restore again. Then I discovered if I backup with pin set, and delete just locksettings.db (in twrp directly after rom flash) I only need to activate pass/pin again (setting for startup - aka discmencryption, too). This is faster for me.

Back to business:

I would like to ask everybody (especially those with boot issues on 17) to try xmas-rc1 and report back as soon as possible. I would like to put out a build working for everybody before Xmas (till tomorrow evening), because I'm not going to work on the rom over Xmas. I think that's fair enough.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] stevenkyk:
Dirty flashed xmas-rc1 over lineage-14.1-20171217_101455-NLOS-oneplus3t.zip, booted up fine with working wg.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
Christmas rc-1 will not boot for me. Same procedure as before, wiped system, flash ROM then gapps. Tried again wiping cache, dalvik, flash ROM then gapps. Then wiped system, flash ROM no gapps. And final attempt flashed ob15, ROM then gapps... Nada. I tried every way i could imagine. Thanks for all your hard work and awesome rom, I'm still happy on the 11/30 build. Here is pmsg-ramoops...

https://drive.google.com/file/d/1bU90fL6Liaxc6ATftuEaJ8Kf1IsOKc8u/view?usp=drivesdk
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
No issues here with Christmas rc-1

Thank you and great Christmas days for you
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Looks the same as the last one. There is an error on keymaster. To be sure, your keymaster partition isn't corrupted, the xmas-rc1 came with firmware (worked at least for [MENTION=8802980]yohannos[/MENTION] :) ), so we can exclude mismatching firmware aa well for you and [MENTION=3242790]wistlo[/MENTION].

Correckt me, if I'm wrong: with no-opt you have tried a clean flash, aren't you?

Last point I can think of is different model: I'm on A3003. Would you report your's, please? [MENTION=535343]all[/MENTION]: to keepmthis simple: when [MENTION=4472938]opethrocks[/MENTION] has reported his excat type, and anybody has the very same, please report if it's booting with xmas-rc1 or not.

[MENTION=451969]opeth[/MENTION]erocks and [MENTION=3242790]wistlo[/MENTION]: do you have adb via cable unning on your notebook, workstation or server? If so, would you like to try to get an logcat on an unsecure build?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
[MENTION=4405529]nvertigo67[/MENTION] My model is A3000. I tried a full wipe clean install of 12/17 build and since have been doing dirty flashes. I am able to get a logcat but it would have to be later today.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Great! Take your time - I need to make an unsecure bootimage first, too. Later today is great! (I'll edit this posting with the link, when ready.)

EDIT:

Unzip attached file; boot to twrp-3.2.1-0; dirty flash xmas-rc1; switch to image flashing mode and flash boot-unsecure-xms-rc1.img; power down the device; prepare your adb and connect the cable; power on the device; when the bootlogo shows up fire off "adb logcat >logcat.txt" wait 5 minutes and press ctrl-c.

A word of warning: the kernel is forcing permissive - always! You can't switch to enforcing. adb is UNSECURED: no need to authenticate! I wouldn't run any mobile or wifi lan on this. Keep the time you running this boot.img as short as possible: it's only for debugging!!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
IMS

Is IMS working for anybody with any carrier, or has been working?

If not (that's what I think), I would like to remove IMS.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
Have ADB, but the enabled machine is in Windows 10 upgrade hell. Fun with System Restore. (Company Win 7 laptop forbids driver installation).

Model A3000, US purchase.

On a hunch I tried regular Lineage 20172215 to 20171222 upgrade, as others in that thread have reported similar boot problems. No such luck here; upgrade went through.

[I miss my NLOS network monitor. I am not wanting to invest time in xposed).]

I have some paying work to do over holidays, but will give best effort to collect ADB. I am considering backing out the ~80Gb on storage to external and reformatting to ext4, if only to get out of the 20 min TWRP startup (3.1.1-2). Just need to find the time.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
Grrrr.... I tried to get a logcat, but I'm using my gf's macbook, nuff said. Terminal kept saying waiting on device... At work now, will try again ASAP.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
First of all: thanx for helping to hunt this down!

Second: one more try is ok, don't waste more time on this (though I like apple bashing - no chance on this one).

Third: (I'm waiting for years to use this) Absence of proof, is not proof of absence....

Not getting logs, doesn't mean we havn't gained new information (if we like this bit of information is an other question). When I was testing the unsecure bootimage,I realized that the earliest point I receive logs is a split second after entering my encryption pin. That means adbd (on the device's side) is started the very first time in the boot process just when data is decrypted.

In the ramoops file I found errors regarding keymaster.

So I think we can reasonable guess the bootloop is at that point, when decrypting is starting.

The next test would be reformating data. :( (Yes, I know...)

I would suggest you use f2fs (not because it's superiour, but because it's what I use, an therefor we can compare behavior).

Before wiping your devices there are one or two more tests: if 13 was working for you, extrct boot.img from 13 and flash it after xmas-rc1. This will not result in a perfctly working rom, but if we guessed correctly, it should boot.

I'll put out the xmas build today (just saw there are squashed commits for caf-06400 in los kernel's repo - perhaps we are lucky, and those do the job for us *crossing fingers*).

I'll try to help the two of you even the next days, but I've promised my people to not spend too much time on the rom over Xmas and New Year.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (xmas-firmware build)

Build 20171223 (xmas-firmware)

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:

Firmware requirements have not changed, but to avoid unneseccary hussles during Xmas I included the firmware (with nlos bootlogo) again for this build.

disable SDCLANG and UBERTC for now (to minimize any issues).

Bootlogo: add NLOS bootlogo. — nvertigo

net/wireguard: add wireguard importer — nvertigo

Revert "msm: mdss: Do not attempt to request TE irq again if already requested" — dianlujitao (laos/cm-14.1

op3: Regen defconfig — dianlujitao

ANDROID: ion: Fix uninitialized variable — Daniel Rosenberg

drivers: staging: Update qcacld-2.0 driver — Luca Stefani

Merge tag 'LA.UM.5.5.r1-06400-8x96.0' of https://source.codeaurora.org/quic/la/kernel/msm-3.18 into cm-14.1 — dianlujitao

sepolicy: allow apps to stat processes. — nvertigo (nvertigo/nlos-14.1, github/nlos-14.1, nlos-14.1

sepolicy: allow cameraserver to search mpctl socket directories. — nvertigo

sepolicy: add a bunch of denials need for different apps. — nvertigo

sepolicy: allow hostapd to access diag_device. — nvertigo

gps: update to LA.UM.5.5.r1-06400-8x96.0. — nvertigo

Revert "IMS: fix derp: remove some test settings again." — nvertigo

sepolicy: allow time_daemon to connect to unix_stream_socket. — nvertigo

sepolicy: allow mediacodec to search mpctl. — nvertigo

sepolicy: allow system_server to use setsched. — nvertigo

init: set downmigrate after upmigrate. — nvertigo

init: remove some artefacts from eas. — nvertigo

oneplus3: Enable framework sched boost — Sultanxda

BoardConfig.mk: remove out-commented SDCLANG. — nvertigo

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] afrob:
This means we dont need anything expect your Rom + gapps?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
[MENTION=4405529]nvertigo67[/MENTION] what method would you recommend for formatting data?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
[MENTION=3242790]wistlo[/MENTION] and [MENTION=4472938]opethrocks[/MENTION]:

Please check once if xmas-firmware is working.... ...not that we miss a test. Honestly: I expect the build to faile on your setup.

Attached you find a boot.img with kernel src based on los src, at the point where LA.UM.5.5.r1-06100-8x96.0 was merged. If my guess was good enough, this should boot.

DO NOT FLASH THIS, IF YOUR INSTALLATION IS ALREADY RUNNING FINE!!!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
[MENTION=4405529]nvertigo67[/MENTION] old boot.img with Christmas build 12/23 won't boot either.

Edit: after formatting data the Christmas build booted up beautifully. Its a Christmas miracle!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Glad to read this!

May I ask you, to try encrypting data? (I expect it to work.)

Thanx for your assistance on debugging this - quite some people are just staying away, after I use the phrase "logcat"...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I know, it's to late, now. Havn't seen that posting yesterday.

twrp-3.2.1-0, format as f2fs - 4x may work,I just don't know.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
That depends on use-case: from 30 minutes (with 4 1/2 day standby and about 90 minutes phone calls) to nearly 9h (forgot my phone at home with koffein enabled).

To answer your question on the same general level it was asked: good, of course! ;)

OP -> Installation -> 2.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] delaya73:
Hello. Thanks!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] abdulmajed1:
Last update Stop Nlos Logo After install ??
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I dirty flashed the Xmas update from an older EAS build. Noticed I couldn't access any of my files on internal storage. Everything from every app said location not found. So had to restore my backup. Anyone else having the same problem?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
OT:

Merry Christmas to yours and you. I wish you all a peacefull and prosper Chrismas time!

Back to business:

Bootlogo? Sure? Or did you mean bootanimation?

If you mean bootanimation: read the last pages: [MENTION=4472938]opethrocks[/MENTION] dis a great job in debugging thismandmfinding a solution. His postings are a good example on giving required information.

Logs? Which eas build do you come from? What have you tried allready?

[MENTION=566169]both[/MENTION]: You can try flashing an old (before latest f2fs update) third party kernel? On the long run you won't be able to avoid reformating data.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
[MENTION=371528]Everybody[/MENTION] with bootup issues: what fs are you using on cache? Try ext4 for now. Don't forget to report.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Oh. I dirty flashed over 30 Nov build. Can you tell me more about the latest f2fs update? That's probably it. Why do I need to reformat data?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Read the last pages. If I would know, why very few installations have issues withe the latest upstream f2fs changes, and others aren't effected, I would have told [MENTION=4472938]opethrocks[/MENTION] already... ;) Second time: Logs?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I have already read the last few pages (I read every post in your thread lol, even if I don't understand it. I've been reading your posts in the wireguard thread as well). Those people had trouble with booting. I had no trouble with booting. I just can't access anything on internal storage. I couldn't save logs because it wouldn't let me save the log file to internal storage since I can't access it. :(

So I restored my backup.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Forget the module or wg related boot issues, they stop booting very early - in deed init was never execed. The last pages were on incompatible data partitions. You say you have issues on accessing data partition... What do you think?

Most basic method for logs: adb, of course...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Due to new job and lack of time I haven't updated the Rom since September. Anyhow over christmas I took my time to get the latest update for LAOS here.

I dirty flash the xmas update over old installation -- > No Boot (stuck at NLOS Logo)

I formated everything and clean flashed the Rom --> No Boot (stuck at NLOS Logo)

I read here something about problems with the fs format.

Checked mine, Data was f2fs, System was ext4. Formatted System to f2fs as well in twrp and tried install again --> No Boot (Stuck at NLOS Logo)

Help? :(
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Sure it's bootlogo and not bootanimation? For the first I'm clueless. If it's bootanimation:

[MENTION=4472938]opethrocks[/MENTION] solved this by formating data (not only wipe, but really format). Try twrp-3.2.1-0.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Well it's the NLOS Logo on black background, AFTER the oneplus bootup logo, nothing else . So I guess it's the bootanimation?

Anyhow I tried actually formatting the Data partition to fsf2 as suggested, still no success, phone stays in boot-up limbo.

I don't know what else to do, this is my 4th installation attempt. I guess I'm stuck on my old Rom then :crying: