CWM 6027 Touch from ATT forum
Alright....so alittle history. kc_exactly is to blame and to thank for this. He just got me thinking. Especially with people starting to test the JB port from houstonn. Which only flashes with CWM.
Disclaimer: You do this at your own risk!! Can't blame anybody but yourself if it messes things up!
I installed sk8erwitskil's Touch CWM 22.214.171.124 v14.4.7 from the ATT forums here. http://forum.xda-developers.com/show...18&postcount=1
I wanted to see if it would work as kc had said in a post earlier. And it did and does!!! CWM backup works using .tar. I haven't tried dedup yet.
So what's the purpose of this post you ask? Well, from what I've found out so far, we can install CWM, create a backup using .tar which is default, and restore with it. In "mount and storage" I formated system, data, cache. In advanced, I formated dalvic cache. Pretty much wiping out the phone and it restored just fine. Actually 4 times so far.
So, and again, part of this has been said by kc_exactly, if you keep TWRP, AND CWM6027 recoveries, your ROM of choice, and backups in both TWRP and CWM on your Internal storage you'll be able to bounce back and forth testing the JB port or whatever else will require CWM.
I've done this multiple times now and it's worked everytime!!!
Make a TWRP backup
Install CWM 6027, reboot to system
reboot to recovery and make a CWM backup using .tar
Now each time you want to use a different recovery, just install it, reboot to recovery and restore your backups.
Maybe this is old news, or even a "No sh*t Sherlock" thing. But our CWM had too many issues, and I'm really liking sk8erwitskil's Touch version. And it seems to be working well. I was in CWM for at least 10min straight and it never got hot.
It does have somewhat of a learning curve, so make sure you read sk8's instuctions on the first 2 posts.