[Essential Phone Themes, Apps, and Mods] dragynbane222:
BaNkS, got you a log, took a bit to get the script to save to a place that was actually available and not encrypted (by default it saves to /data/media/0/ which is not decrypted until one enters their pin/password from what I know, so saving a boot log there is useless)

The following lines (along with everything dying) is worrisome, though:

08-12 13:42:49.782 1854 2457 E bt_hci : Bluetooth HAL service died!
08-12 13:42:49.782 1854 2457 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 2457 (HwBinder:1854_1), pid 1854 (droid.bluetooth)
08-12 13:42:49.810 619 619 I ServiceManager: service 'suspend_control' died
08-12 13:42:49.819 4406 4406 I NetUtilsWrapper: Unexpected command: /system/bin/ip -4 rule del prio 11999
08-12 13:42:49.824 4407 4407 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
08-12 13:42:49.824 1261 1261 I /system/bin/tombstoned: received crash request for pid 2457
08-12 13:42:49.826 4407 4407 I crash_dump64: performing dump of process 1854 (target tid = 2457)
08-12 13:42:49.833 4407 4407 E DEBUG : failed to read fdsan table entry 0: No such process
08-12 13:42:49.834 4407 4407 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-12 13:42:49.834 4407 4407 F DEBUG : Build fingerprint: 'essential/mata/mata:10/QP1A.190711.052/351:user/release-keys'
08-12 13:42:49.834 4407 4407 F DEBUG : Revision: '1.8'
08-12 13:42:49.834 4407 4407 F DEBUG : ABI: 'arm64'
08-12 13:42:49.834 4407 4407 F DEBUG : Timestamp: 2019-08-12 13:42:49-0700
08-12 13:42:49.834 4407 4407 F DEBUG : pid: 1854, tid: 2457, name: HwBinder:1854_1 >>> com.android.bluetooth <<<
08-12 13:42:49.834 4407 4407 F DEBUG : uid: 1002
08-12 13:42:49.834 4407 4407 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
08-12 13:42:49.834 4407 4407 F DEBUG : x0 0000000000000000 x1 0000000000000999 x2 0000000000000006 x3 00000077d4bb8810
08-12 13:42:49.834 4407 4407 F DEBUG : x4 d3ba8f1efeff6862 x5 d3ba8f1efeff6862 x6 d3ba8f1efeff6862 x7 ffffff7f7f7f7f7f
08-12 13:42:49.834 4407 4407 F DEBUG : x8 00000000000000f0 x9 00000078ce2864e0 x10 0000000000000000 x11 0000000000000001
08-12 13:42:49.834 4407 4407 F DEBUG : x12 00000077d4bb8498 x13 ffffffffffffffff x14 0000000000000004 x15 ffffffffffffffff
08-12 13:42:49.834 4407 4407 F DEBUG : x16 00000078ce3528c0 x17 00000078ce330060 x18 00000077d46fc008 x19 00000000000000ac
08-12 13:42:49.834 4407 4407 F DEBUG : x20 000000000000073e x21 00000000000000b2 x22 0000000000000999 x23 00000000ffffffff
08-12 13:42:49.834 4407 4407 F DEBUG : x24 00000077d4bb9020 x25 00000077d4bb8a38 x26 00000078cd89a138 x27 00000000000fd000
08-12 13:42:49.834 4407 4407 F DEBUG : x28 0000007fc73b1090 x29 00000077d4bb88c0
08-12 13:42:49.835 4407 4407 F DEBUG : sp 00000077d4bb87f0 lr 00000078ce2e4170 pc 00000078ce2e41a0
08-12 13:42:49.835 4407 4407 F DEBUG :
08-12 13:42:49.835 4407 4407 F DEBUG : backtrace:
08-12 13:42:49.835 4407 4407 F DEBUG : #00 pc 00000000000821a0 /apex/com.android.runtime/lib64/bionic/libc.so (abort+176) (BuildId: b58d049709674405423a8d8de1a37f56)

Seems the BT HAL is dying, and not just dying, but segfaulting and for some reason taking the entire system with it.

Here's the entire log: https://del.dog/uyuyequnem

The system doesn't even seem to be up for an entire minute before rebooting, even if it's only partially up. So setting the script to collect the log for a minute seems to be sufficient

I can try and get the other stuff should it be needed

EDIT: looking at the log more, I'm seeing a lot of systemui crashes (seems to be related to wifi, as that's mentioned in the crash). I'd recommend looking at the entire log, see if there's anything more I'm missing. Also, rescueparty seems to be called before the BT HAL SIGABRT