[Droid Ultra Q&A, Help & Troubleshooting] TEPEM:
Ok guys, I presume everyone is on their place and you managed to grab yourself plenty of popcorn and soda. Just make yourself more comfortable and the continuation of this story follows just right away!

You might not like it. So the disclaimer is: "If you have an immense trust in the only omniscent and omnipotent MOTOROLA god - please don't read this further on. You will find it most offensive, humiliating and uncomfortable is such a case. Ugh, I warned you!"

First I tried to reach out to Motorola support online. I have to admit I have not spent countless hours explaining the case. I tried to be as much specific as I could and it seems this worked. But huh... Support Representative told that they are not trained to provide such as support as in my case. Sounds familiar, right? In other words: "It is so nice that you spent extra money bying our DE device. It's obviously above any appraisal that you try to contribute and take you time to try resolving the issue. Really sorry, but rest assured that Motorola just does not give a f%$k about it."

I don't have anything personal against representative who tried to help and I do appreciate his willingness to assisst me but the general corporate attitude towards the customer - I simply have no words for it. I kindly asked a support person for a small favour of pointing any Motorola technical guys devs/supports to this forum thread where I raised this question.... No one replied.

Ok now let's get back to the matter - so I experimented a bit with my UNLOCKED BL XT1080MDEV this week flashing different stock FWs just to get out of this bootloop. I flashed the following FWs with RSDLite:

(CFC) VZW-4.4.0-SU2-3.3-release-keys.xml

(CFC) VZW-4.4.0-SU2-3-15-release-keys.xml

(1FF) VZW-4.4.4-SU4.21-release-keys.xml

(CFC) VZW-4.4.4-SU5-24-release-keys.xml

All flash processes were as smooth as Moto Ads and promises but never ended with a booting Android - all the same bootloop on "Warning Unlokced Bootloader..." message when I just realized that BL version upgardes every time I flash newer FW like that: 30B2 -> 30B2 -> 30B6 -> 30B9

while FW version part ) always remain the same:

NFOro.build.date: Tue Aug 6 18:39:38 CDT 2013

INFOro.build.id: 12.9.0Q2.X-160-OBK_TA-14-7

INFOro.build.tags: release-keys

INFOro.build.type: user

INFOro.build.user: hudsoncm

INFOro.build.version.codename: REL

INFOro.build.version.

incremental: 7

INFOro.build.version.release: 4.2.2

INFOro.mot.build.customerid: verizon

INFOro.product.name: obake-maxx_verizon

INFOro.build.fingerprint[0]: motorola/obake-maxx_verizon/obak

INFOro.build.fingerprint[1]: e-maxx:4.2.2/12.9.0Q2.X-160-OBK_

INFOro.build.fingerprint[2]: TA-14-7/7:user/release-keys

INFOro.build.version.full[0]: Blur_Version.12.7.7.obake-maxx_v

INFOro.build.version.full[1]: erizon.Verizon.en.US

INFOkernel.version[0]: Linux version 3.4.42-gfd1a699-00

INFOkernel.version[1]: 151-gc170e6f (hudsoncm@il93lnxdr

INFOkernel.version[2]: oid50) (gcc version 4.6.x-google

INFOkernel.version[3]: 20120106 (prerelease) (GCC) ) #

INFOkernel.version[4]: 1 SMP PREEMPT Tue Aug 6 19:24:04

INFOkernel.version[5]: CDT 2013

That makes me think that

flash memory has weirdly gone into RO mode for some reason

. So I ended up having a DE device sftbricked at this point and needless to say I am not able to downgrade as well. One word for it - MOTOROLA :D

As a summary I was lucky owner of functional XT1080MDEV just for 2 days before it went to the Happy Hunting Ground. I bet you wouldn't call just bootloader mode available a functional state of the smartphone ;)

I need to admit that in my case it is a total waste of money: I bothered to buy it new in a box from the person in Russia - it is more than 800 miles (while I reside in Moldova) for 270 EUR - just to have new Motorola DE device. But it is Motorola who had me again.... :good:

Hope this story would be a good lesson for you and I wish you never waste your time and money like I did.

Sorry guys, That is it.