[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Another update on this problem:

I talked to Motorola support and got them to RMA the phone. I found out later that you don't even have to talk to anyone. Just go to Motorola's support page, request a repair, type in your IMEI number and bam, new phone. There are two options: one is free and requires an inspection of the damaged phone, and one is $25 and does not. I picked the $25 one for obvious reasons. However, if you're strapped for cash, it has been confirmed that if you upgrade to official 5.1, the bootloader software status will revert back to official. However, the Q flag will still read as 1/1 (aka modified), so someone who really wants to know if you've been doing warranty-violating things will be able to tell if they're really looking. If the phone I receive has 5.1 on it, I'll sell the thing and buy one with 4.4.4 (or maybe even an XT1250 with an unlockable bootloader, depending on how much cash I get for the one I sell. That would be fun). If it has 4.4.4, I'll keep it, flash a rooted 4.4.4 image and stay there until someone smarter than me can sort this nightmare out.

Speaking of the nightmare, I still have a few days left with the broken phone to bash my head against this brick wall a little more, so let's get to it:

A third user has now reported the same problem. This user was using CF 1.3 with V4A. Nothing that he has flashed or wiped, etc., has helped so far, and I'm not expecting it to (sorry dude). I'm thinking that we can eliminate the possibility that this is a hardware issue, unless of course there was a manufacturing defect in one specific lot of Turbos that we all happen to have. I'm thinking the only hope of solving this problem is to get Motorola Sensor Services to downgrade whatever it messed up, so that's the new objective. It did it once, it can do it again. As for why it hasn't affected everyone on rooted 5.1, that's hard to say. My guess is that MSS doesn't immediately perform its update when a new version is downloaded. I think there might be some sort of trigger which causes the driver update to happen silently, and only some of us have pulled that trigger.

For the record, I want to note that I warned the users on the CF Turbopop thread about this problem, but I was largely dismissed as just another n00b who messed something up because he was too lazy to read. I suppose I don't blame them. I would have probably done the same thing. There is certainly no shortage of people like that on that thread.

I discovered that on a rooted, otherwise stock, 5.1 ROM, the power button will not wake up the screen once it sleeps. However, the phone is still on and able to receive adb commands as long as you plug it in and get it connected to adb before the screen goes dark. I found an old Motorola Sensor Services apk on the internet and tried to install it via adb. It wouldn't let me since it is an older version of the one currently installed. My next move (once I get home from work) is to try to find where MSS is installed, remove it (if it's in system, remove it from the .img and then reflash), and try to install this older version.

Now of course, the easiest way to get an older version of MSS on there would be to revert to 4.4.4, but I've tried that about a thousand times now and I have not been able to get that magical "uninstall sensor firmware" message to appear again, so we'll see if I get incredibly lucky with this one. I don't have high hopes.

If that doesn't work, I'm going to get a root browser up and running (root operations have largely resulted in freezes so far, and a logcat I looked at recently even said that an operation of SuperSU was denied, but maybe I'll get lucky) and see if the firmware partition is mounted during normal operation (it's not mounted in fastboot mode, and I found that out by going a little crazy and trying to wipe it). If so, maybe I can find the sensor files and delete them (I'll look for dates of modification and try to find files that are newer). Hopefully this won't cause the thing to self destruct, but instead cause MSS to take another shot at it.