[Q] Whoops, TiBu freeze brick! Flash or ??

[Komodo Rogue]

Hello, any advice/suggestions would be appreciated!

After doing the update process (Root v2) I went back into TiBu and started freezing the bloat, and I kinda got carried away (I didn't even know what everything I froze was... stupid! To any other dummies out there: just because it has motorola in the name, don't assume it's bloat, apparently).

Then I left TiBu and turned off my phone. Upon reboot, it brought up the red moto dual core thing, and then it did the first 2-3 seconds of the red moto dual core with red wavy animations around the circle, but then suddenly stopped and the red light began flashing.

Holding volume up and volume down on subsequent reboots brought up different messages about starting some kind of protocol and fast boot, respectively, but after five minutes I figured that they were just frozen too.

So I f'ed it up. Right now I'm just charging my phone to do the "[Guide] Flash SBF to Atrix" directions. But INSTEAD, is there any way I can just defrost what was frozen in tibu without going through all that? Not a huge deal, but I'd rather not do the SBF Flash (looked lengthy to a noob like me) AND the update process again.

Thanks!

 

[Komodo Rogue]

Ah, found this link that explains how to use super one click to "recover from a soft brick caused by freezing needed apps or services."

I need to "run shell root from superoneclick in Early USB Enumeration." I have a mac, so I downloaded the drivers and super one click onto a ****ty, borrowed netbook. The problem is I don't know how to run it in early usb enumeration, and even running s.o.c. seems problematic because my atrix starts booting up when connecting to the ****ty netbook, and gets itself nice and soft bricked/frozen/stuck.

I really don't want to keep guessing and doing battery pulls - I fear eventually my Atrix will get tired of this mistreatment and REALLY brick itself for good... if anyone has any info, please help!