[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
We know exactly what he did. It's not a mystery. But besides him...

Most of these people bricking their phones on the 6.0.1 OTA are installing the OTA, then either

1) trying to install the OTA file again to "fix" something or

2) trying to downgrade back to Lollipop.

See

this thread from a week ago for examples of both.

I could show you even more if you wish. Like here:

(If they had UNLOCKED bootloaders with TWRP installed, we could help them.)

Or third cause of bricking is ...

3) trying to install OTA on an encrypted phone.

Initially,

encrypted phones couldn't handle the 6.0.1 OTA

. Verizon paused the 6.0.1 OTA rollout for a few days, told people with bricked phones to send them in for replacement, and then resumed the OTA rollout -- without ever confirming they fixed the issue.

For the first two points, you can't reinstall OTA update again on a locked bootloader as it's basically only a partial firmware file which looks for the previous Lollipop firmware.

You also can't downgrade from Marshmallow back to Lollipop on a Droid Turbo locked bootloader.

Even if the cause was neither of those two scenarios -- or the encryption problem, it doesn't matter. Regrettably, his phone is a brick until Verizon decides to release the full firmware. Then he and others can use the Repair Assistant or flash via RSD. That's been said time and time and time again.

Or unless some dev comes up with some magic?

This situation has been going on for for WEEKS, in various threads with several people. Maybe you haven't kept up?

I feel very sorry for him, but there's nothing we can do.

Here's what he says the reason is:

And THAT has not been released yet. OK? This has already been discussed many, many, many times over the past few weeks. New people coming in with this problem are not aware and we are having to give them the bad news.

It's Verizon's fault for not making the full firmware available.

---------- Post added at 07:05 PM ---------- Previous post was at 06:55 PM ----------

Look, I don't know everything. I'm not a dev. But I try to help people and I have helped lots of people. I do tons of research for my answers or it's based on hard won experience.

If I don't know an answer, I'm not going to pull one out of thin air. My answers are based on facts or personal experience.

I'm the one two years ago who pointed out the XT1250 = XT1254 (same radio bands, same FCC ID)when Verizon Droid Turbo owners didn't even know about that or even wanted to admit it -- and Verizon was lying through their teeth they had a worldwide exclusive, when they didn't even have a U.S. exclusive. I proved it to all the naysayers. I knew this because of my research/knowledge of the U.S. cell phone industry.

I'm the one who found the XT1225 had LTE band 5 (which AT&T uses) and HSPA band IV (which T-mobile uses) by doing modem software scan when Motorola didn't want to initially admit it. They left those bands off the official specs for some reason. (I know why, but too long a story for here.)

If I do answer and I even post direct links to manufacturer/carrier statements (research), and then someone else comes along right behind me and says the exact opposite -- then yes I will probably point out that is not correct answer.

But I'm always glad to help.