And those who flashed the leaked GB update on the T-Bolts didn't have a problem either. It was the "official" OTA that screwed the T-Bolts...just like Sprint with a lot of the S2's (I was a victim of that one) But, for the millionth time, not everyone will experience the same results. Some people will be happy, some people will be mad. No 2 phones are identical. That's why custom ROMs work differently for everyone. My phone is PERFECT right now and everything works including the cut and paste, I get no "no sim" warnings, no "sd card unmounted" no frozen screens, have perfect reception, etc. Why on earth would I want to take a chance screwing that up? Sometimes it's the apps, and sometimes it's the carrier update. When I do decide to take it, I will do a factory reset first, pull the battery, and reboot. I've been rotting and ROMing phones since the Hero came out (aka Verizon Eris) and not just my phones. I know a little. The S3 is the first phone I've had for stock more than a day. I'm pleased with it, so I'm not changing it. I couldn't care less about Google Now, or JB because of TW. If I was running AOSP, yes, I'd want JB. I'm sure that I'll root my S3 in another 6 months or so, and start messing with ROMs...I'll just make sure I have a Note 2 sitting on my nightstand as my primary device when I do it. Right now, I only have my S3 and it's the first time I've only had one phone.