Try rooting manually with ADB command line. Google is your bff

 

Yes the Framaroot 181 was the exploit that worked before,
Guess the carrier got shown something.

If any on on tmo hasn't taken this update, could you Please download OTAsnatcher from the playstore
it could help us beat them.

https://play.google.com/store/apps/details?id=com.otasnatcher&hl=en
Available here
Thanks;

 

I haven't updated and have the T-Mobile version of 4.2.2; L2HUMH2 and would be more than happy to pull it for you guys, but I don't see how this would help as this phone doesn't allow ANY rom, even stock, to be flashed. There are a few forums on here of people trying to flash stock to fix bricked OT Fierce' only to receive an error message, as well as flashing to try and unlock the bootloader which resulted in an error messaging triggering 'T-Mobile securelock'. Point being, you're better off with an up to date non-root working phone, than a bricked one "running" the older version. I say running in quotes because the only thing you may get is the boot logo. Especially if this is your replacement, and you know how easy these are to brick, I'd say just make due until you can buy a new phone. I've bricked one by receiving an update after Removing one bloatware app and made anothers power/lock button stop functioning by trying to change the boot logo, luckily I fixed it(sort of) and am still using the phone but now have all sorts of problems with it.

I know if you're like me, it's frustrating not being able to have your devices exactly how you want and only cluttered by the apps if your choosing, etc. but it's better than the alternative.