[Verizon Motorola Droid Turbo Android Development] TheSt33v:
That's correct. Not taking system software updates is rule number 1 of any sort of device unlocking, and I've done plenty of that across all kinds of devices. I was also one of the first people to test the method that we use to get 5.1 working on our phones, so I'm familiar with what I can and cannot flash and why.I suppose I can't definitively say that Moto Actions is the culprit, but this is what I know for certain:

1. This problem occurred shortly after Moto Actions updated.

2. The problem was solved once after restoring to 4.4.4 and allowing the phone to "complete uninstallation" of the Motorola Sensor Firmware.

3. After re-flashing rooted 5.1 (and all of the appropriate images that accompany the system image), the problem re-appeared shortly after allowing Moto Actions to update (which was a stupid decision on my part, but at the time I wasn't entirely sure that Moto Actions was the problem, and even if it was, I was assuming like the rest of you that a simple wipe would solve the problem).

4. After taking a stupid amount of time to boot, the phone will occasionally seem to work mostly fine. However, opening Moto and going to the gestures section instantly causes the phone to crash again, further suggesting that my phone is having issues with these sensors, or more likely the drivers that control them.

5. This exact same problem occurred for at least one other person, so the odds of it being a hardware failure that occurred at the exact same time and exhibits the exact same symptoms is unlikely. Before I learned of the other case, I was assuming that it was hardware because it just felt like it was. I have enough experience with building/maintaining computers to get a rough idea of when a problem is most likely hardware related. Sadly, this isn't a desktop and I can't start pulling/replacing parts.

6. Factory resetting through the bootloader, factory resetting through settings, restoring 4.4.4, restoring 5.1, restoring 4.4.4 again, wiping cache, wiping cache/clogo/userdata via fastboot does nothing to solve the problem. On the rare cases where the phone seems to be working properly, doing any of these things seems to make the problem reoccur.

Now, that leaves two explanations:

1. It is a hardware problem, it was a coincidence that it happened at the same time as someone else, and I didn't actually fix the problem that one time. I just didn't use it long enough to see it freeze/take 30+ minutes to boot again.

2. Moto Actions writes drivers/firmware files/something to a partition that isn't modified during a software update (which is why resetting/restoring doesn't fix the problem) which either conflicts with the 4.4.4 bootloader/5.1 system mismatch (unlikely since we don't have a symphony of angry voices with busted phones) or this writing process ended up with a corrupted driver for myself and the other case. Since I don't know what this partition is, I cannot modify it (assuming the locked bootloader will even let me). If this is the case, my best bet is to somehow force the action of Motorola Sensor Services to perform the same firmware uninstall that it miraculously did the first time I restored 4.4.4. But how?

Anyone have any thoughts?

UPDATE: I managed to get the thing booted long enough to view the partitions from an adb shell using the df command. There's a relatively small partition called firmware that I'd be willing to bet is flashed by Motorola Sensor Services. Also, the androidmanifest.xml of the MSS app has a section called FLASH, which leads me to believe that it does flash something (though I can't tell what or where). The apk also seems to contain xml's that deal with installation and uninstallation actions, which leads me to believe that this is indeed the app that I'm looking for. But how to trigger any of that is still a mystery to me. I love a puzzle, but I love working phones more. If anyone knows how to dump that partition and send me an image of it, I will love you forever. Unless of course the bootloader stops me when I try to flash it, in which case I will love you only slightly less. adb pull /firmware will get you all of the files, but I'm not familiar with how to package those up into an image that fastboot/my phone will like.

UPDATE2: I turned on a developer option to give me "not responding" notifications for all apps. What apps are constantly not responding? Camera and Moto Display. What do these two apps have in common? They utilize Motorola Sensor Services, or whatever that app flashes. Also, I'm starting to realize that this has nothing to do with CF's system image or rooted 5.1 images, so I won't be posting any more about this here. I would still appreciate help from those who know more than me though.

---------- Post added at 12:07 AM ---------- Previous post was at 12:02 AM ----------

What? How? What number did you call? What did you tell them?