[Motorola Atrix HD] br0adband:
Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:

- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)

- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)

- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually

- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)

- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it

- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect

- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode

- got the following error (which is known to a few other members in the past based on postings I located):

(typical info at the top of the screen)

Device is LOCKED. Status Code: 0

Battery OK

Connect USB
Data Cable

downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected

As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.

I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.

I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.

I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.

I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.

So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.

Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along... ;)

Thanks for reading, regardless.