[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Okay, a quick update just in case anyone sees this that can help me. Also, it's a handy way for me to journal everything I have learned/tried so far to fix this phone.

1. The problem has happened to one other person. He was running CF's 1.3 base rom, updated Moto Actions, and his phone started crashing and taking 5-10 minutes to boot, assuming it boot at all.

2. I've tried restoring 4.4.4 and reflashing 5.1 (in the way that preserves the 4.4.4 bootloader) several times now. I managed to get a logcat on 5.1. Here it is: https://mega.nz/#!64ABlZbB!F9gEJlwAfS8xXvno3WjNEpliRADtYnl-nDk4p4HVJlw but here is an interesting highlight from it:

--------- beginning of crash

F/libc ( 932): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 997 (android.ui)

F/libc ( 1809): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 1832 (android.ui)

F/libc ( 2117): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 2140 (android.ui)

F/libc (10991): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 11014 (android.ui)

F/libc (11292): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 11315 (android.ui)

F/libc (11628): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 11651 (android.ui)

F/libc (11922): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 11945 (android.ui)

F/libc (12258): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 12281 (android.ui)

F/libc (12550): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 12573 (android.ui)

F/libc (12886): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 12909 (android.ui)

F/libc (13178): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 13201 (android.ui)

F/libc (13512): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 13535 (android.ui)

F/libc (13804): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 13827 (android.ui)

F/libc (14143): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 14166 (android.ui)

F/libc (14438): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 14461 (android.ui)

F/libc (14775): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 14798 (android.ui)

F/libc (15067): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 15090 (android.ui)

F/libc (15404): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 15427 (android.ui)

F/libc (15696): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 15719 (android.ui)

F/libc (16033): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 16056 (android.ui)

F/libc (16324): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 16347 (android.ui)

F/libc (16661): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 16684 (android.ui)

F/libc (16953): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x430000 in tid 16976 (android.ui)

I've tried googling this error, but I can only find posts relating to debugging android apps that are in development.

3. I'm fairly certain that the Motorola Sensor Services are the source of the problem, and that this apk flashes drivers that control the various sensors used by Moto to a partition that isn't modified when going between 4.4.4 and 5.1, which is why factory resets/going back to 4.4.4/cache wipes does not solve the problem. My theory is that Moto Sensor Services updated at the same time as Moto Actions (maybe as a part of that update) and flashed an updated sensor firmware to this mystery partition (maybe /firmware? I wish I could wipe it, but there's a lot of important looking stuff stored on that partition, and judging from the number of problems I'm getting from a corrupt driver install, I can only imagine what that would do) that went horribly wrong. I accidentally fixed this flash by letting Motorola Sensor Services uninstall that mistake when I restored 4.4.4 that one time. Unfortunately, I let it upgrade again (kicking myself) and it seems that Motorola Sensor Services no longer realizes its mistake when I restore 4.4.4.

4. The other user who experienced this (my2cents) managed to convince Motorola to send him a new phone for free. This is awesome, and I'm waiting for him to get back to me with what he told them to make that happen. If the phone they send out is new, chances are it will have 4.4.4 and be good to go. If it's refurbished, it will probably have a locked down 5.1. I will never forgive myself if I can't use jcase and beaups' sunshine bootloader unlock when it comes out (which will require root, and therefore mofo compatibility), so 5.1 is not an option. I've found affordable-ish, new 64 gb turbos with 4.4.4, so I'd rather do that than be locked down. I suppose I could always sell the locked down phone to offset this cost.

Anyway, if you are knowledgeable and have some time, please look at my logcat. If you can figure out what I have to do to unbork this thing, I would be pretty psyched.