I'm really trying to understand the difference. Is it more a personal preference in using a touch interface & options, or are there some core differences as to why you should use one over the other, especially in flashing the ICS ports we're using on our T989's.
In one post I've been reading, they're instructing you to use 'touch recovery' to flash the ROM. And in other post I've been reading, a highly trusted member said he won't use touch anymore because of issues he's had with it. I've seen it go both ways many times.
I read in another post, that one member thought the 2 versions handled the cache partition differently. If that's the case, doesn't using thederekjay's Darkside SuperWipe make that null & void anyway, because it formats, erases and aligns all the disks partitions properly anyway before you flash?
I've never used touch to flash an ICS ROM, or any ROM yet, and I'm certainly not against it. But I haven't had a lot of the issues that some are having either to make me go that way. So I'm trying to determine, or see if you guys really think that using one version over the other can really make a difference in the stability of the ROM; and if so...then why? Thanks!
And of course; if the OP tells me to use touch recovery to flash their ROM, I will certainly do so if I flash the ROM. Just trying to get a better understanding.
I use touch. Its just a personal preference. Then again the errors are a hit or miss thing.
Sent from my SGH-T989 using Tapatalk
recovery version doesn't matter. it would be quite cumbersome to flash a different recovery every time i wanted a different rom. Touch vs no touch just affects GUI and user interacting, nothing more.
When in RECOVERY I want stability ....no touch gimmicks necessary if there's even the slightest chance of an error.
Sent from my SGH-T989 using XDA
bzlik88 said:
When in RECOVERY I want stability ....no touch gimmicks necessary if there's even the slightest chance of an error.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
word. having to button press your way thru the menues is a security feature.
SGS2 (T989) on CM7_373R5
Touch is the best way!!
I used for much time the Classic CWM, until I want flash the new ICS Rom; I have a lot problems, boot loop, kernel loop, reboots, FCS…. My solution was the new CWM Touch Version.
After I make all wipes with this CWM Touch version all things on ICS for T-Mobile t989 works very very well.
In my opinion non-touch recovery works best because its stable and touch recovery is still experimental and can still have some bugs.
Sent from my SGH-T989 using XDA
osangoqui said:
I used for much time the Classic CWM, until I want flash the new ICS Rom; I have a lot problems, boot loop, kernel loop, reboots, FCS…. My solution was the new CWM Touch Version.
After I make all wipes with this CWM Touch version all things on ICS for T-Mobile t989 works very very well.
Click to expand...
Click to collapse
I had the same experience. Which was confusing.
I figured it was just people not flashing properly which was causing the issues.
So I used non-touch CWM. Tried 4 times with various combinations of wiping to try and get it to boot. To no avail.
Flash touch CWM, flash once, works perfectly. So confused as to why that is.
So this is what confuses me. I was just reading through some posts at the 'NexusMod' thread. A member posted that some of the issues another member was having with the ROM was due to the user using standard recovery. He said standard recovery makes the cache partition as r/o instead of r/w and this is causing some of the issues when people flash the ICS ROMS.
Really? So in GB ROMS it doesn't matter if it's r/o because I've always used standard recovery and never had, or heard of these issues before related to the recovery?
So there's that big of a difference between the 2 versions of recovery that one leaves the cache partition as r/o and the other r/w. That seems pretty major to me if true. I'm not doubting anybody here, just trying to get a better understanding so I know which recovery to use.
I like and just feel safer using the non-touch version. But if need be, I could go touch... If I need too.
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Related
sorry before, may be this is a stupid thread for asking common stuffs about recovery
but i just wanna know for this time what's your favourite custom recovery between cwm and ext4 recovery touch (include the version) or may be the others that u think the best. thank you guys
Probably ext 4
Sent from my SGH-T989 using xda premium
Both are awesome, but I like CWM more
I've used both and both are great.
I personally find that CWM (ClockworkMod) is a little more straightforward and has a cleaner look to it. CWM now has touch, albeit it's not as feature or interface rich as 4ext's touch interface.
I should point out, however, that using CWM with some ROM's, I was unable to make selections when the ROM gives you options during flashing. For example, when I was flashing a rom that gave the option of installing the OC daemon, CWM didn't give me the option, it just said installation (of the OC daemon) cancelled, whereas 4ext said yes or no, and I was able to choose.
I use ROM Manager (+ premium) from the market to flash back to clockwork mod when I've had 4ext installed, and use 4ext Recovery Control to flash 4ext back.
I would post the links but xda says I can't yet Not new to android or xda by any means, but new to posting
Hope this helps
The recovery is called 4EXT, and that's what you should refer to it, as to avoid any sort of misunderstanding with the "ext4" filesystem.
With that said, 4EXT Touch is the best you can get. It has a lot of bugs fixed over from CWM. It is also fully compatible with ROM Manager.
Link to the 4EXT site: http://4ext.net/
4ext touch is what I prefer. I started with cwm and have mad love for it, but after one of the updates is was working awkward for me and I tried 4ext and never looked back.
I might add cwm is fixed now, and works flawlessly.
Sent from my myTouch_4G_Slide using xda premium
They both flash roms fine. So to me, eh who cares? I mean no offense to the respective devs, but I compare it to who makes a better key to my car? Who cares as long as it works. Imho.
P.s. I know some people like fancy keyless entry and keyless start and panic mode.... so for them it makes a difference.
Sent from my HTC Desire Z using Tapatalk
So heres a question:
Wgy do we have rogue recovery with the kernels when we cant flash ROMs from it.
Well we arent supposed to.
Why not repack the kernel with pure CWM and eliminate everyone form having to take the extra step of flshing back to CWM before flashing a new ROM
tramane said:
So heres a question:
Wgy do we have rogue recovery with the kernels when we cant flash ROMs from it.
Well we arent supposed to.
Why not repack the kernel with pure CWM and eliminate everyone form having to take the extra step of flshing back to CWM before flashing a new ROM
Click to expand...
Click to collapse
It won't matter as its the ics kernel that is the problem not rouge not Acs not cwm.....
Sent from my SPH-D710 using xda premium
I've been flashing with it. So have plenty of others. Some people bricked and they may have been using rogue but I wrecked a Honda once.... Its usually user error.
Sent from my SPH-D710 using XDA
You have a point.Im coming from original Epic 4g and im deffinetly confused about the kernels on Epic Touch.
This is what I mean:On original Epic they had kernels that you could flash on top of just about any rom in cwm or odin.But for Epic Touch im yet to find any kernels for it.Yes there are some stock EL29EG31,etc.. in wiki pages but thats it?
There are only two kernels on wiki that are non stock and they are Hitman's kernel and Rogue kernel,is that all we got?Og Epic had about 30 different nonstock kernels.
So my question is this:
1 Are Rogue and Hitman kernels come with their own cwm?
2 Are Rogue and Hitman are only two nonstock kernels?
3 Are all the other lernels on wiki EL29,EL26,EG30,etc.. are just stock or modified stock?
4 Can any of those kernels(besides ics Rogue of course) be flashed to any GB rom?
5 Are there any difference between different versions of Rogue and Hitman?Or latest is the best?
6 And if Rogue and Hitman also come bundled with their own version of cwm,what is the difference between those two cwm's?
I been on original epic xda forums for years and this **** is confusing,they should make a thread for new people.
Pretty sure its not user error, given that at least 3 of our most prominent bleeding edge devs bricked doing it. I made the mistake of believing it was user error, but all evidence points to the contrary.
The reason we have recovery on ICS kernels is there are things at this point that you can safely flash (basically, anything that doesn't wipe data). You can safely flash the visual voicemail .zips from rogue ICS recovery on AOSP roms, for example. But you can't flash a whole rom. You can make a nandroid for later restore from EL26 cwm. You can do a lot of things actually. Just don't flash an actual rom, and you should be fine.
lviv the reason there aren't many options on the ET for recovery is there aren't many devs that work with it. SteadyHawkin repacks rogue for us, and that's about it. We used to have a few others that did so, but now it's just SH. Personally I don't really care as rogue recovery works perfectly fine, and the reason we use stock CWM from EL26 is because it's all we need (no point in repacking another kernel since we all have access to that one, why waste the effort to put CWM on EL29 when chris41g did a fine job on EL26 and we are all using it for ICS flashing right now?). No point putting any more work into packing a diff recovery on ICS kernels when there's no source and there's a ton of fear of bricking going on.
I'm certainly no dev, but those are my observations.
I've said this before in the threads discussing the bricks. I am not a dev, so they can correct me.
I don't think the bricks had anything to do with the rogue repacks. I think it has to do with the way ICS handles the data partition. It seemed like the bulk of the bricks happened when we tried a factory reset, or wipe data and at that point we burned up our emmc chips.
Sounds crazy that that is possible just wiping a data partition, but it was pretty consistent.
At first I thought it was the temp touch recovery because that was what people were using when ICS was first leaked. I think most of us were also flashing it through the stock recover rather than odin or mobile odin. But, it began happening with rogue repacks as well.
Once the source drops these problems will probably clear up.
To the ops question, someone already answered. We can flash just about everything else with the repacks. I prefer the rogue repacks because he has streamlined them making them handier to use.
Sent from my SPH-D710 using Tapatalk
I understand that some have had luck and others haven't. It just seems to me that if it doesn't brick every phone then it can't be the recovery itself. There has to be another common denominator. I guess the issue is that until that common denominator is figured out it could be dangerous to use.
Sent from my SPH-D710 using XDA
Devi0124 said:
I understand that some have had luck and others haven't. It just seems to me that if it doesn't brick every phone then it can't be the recovery itself. There has to be another common denominator. I guess the issue is that until that common denominator is figured out it could be dangerous to use.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Exactly, I have been flashing things with the Rouge recoveries with no issues at all. I always use the Format all zip though and not the wipe in recovery, and that does wipe data so not really sure what is causing people to brick there phones.
I've never bricked using the ICS repacked recoveries, and I've used em to flash to different roms without format.zips before we knew it was even an issue, but now that I know this could potentially brick your phone, I won't be doing anything in recovery anymore except flashing themes or something that does not involve wiping. I'm not longer on ICS anymore though, as I see it completely pointless until official is out. Too much flashing, and not enough functionality ATM to see usable, runs kinda slow too, not complaining at all just stating why I'm not on it, when it's official it will be great, and the devs will be able to tweak the final build for some massive speed.
It is the data partition I believe, I'm not 100% sure on this but I think the wipe in recovery doesnt actually just wipe but reformats and resets the partition sizes whereas the wipeall zips just erase the data leaving the partitions alone
To simplify compare it to reformatting your harddrive in your PC.vs just factory resetting it or deleteing the data off of the drive leaving the OS intact but removing added on data
Sent from my SPH-D710 using xda premium
i flashed roms with rouge
FYI there's evidence of problems in the kernel source.
I9100 update4 seems fine - but apparently Koreans are having lots of problems with the SHW-M250S/K/L source drop, and also gokhanmoral of SiyahKernel encountered a bunch of bricks when he attempted to rebase on the SHW-M250* source code base.
I'm another original epic owner that just switched to the touch....I've rooted and flashed ics.....now over there on the epic 4g we don't have ics source either...but we have cwm that flashes roms ,backups, restores, we can even flash a ROM to boot from the sdcard to calibrate the sensors and update your prl....so why do we need source on the touch to acquire those luxuries?
XDA Premium
rujelus22 said:
Exactly, I have been flashing things with the Rouge recoveries with no issues at all. I always use the Format all zip though and not the wipe in recovery, and that does wipe data so not really sure what is causing people to brick there phones.
Click to expand...
Click to collapse
Same here as far as flashing things via rogue recovery. I even nandroided back to a gb rom from the fc24 repack, after wiping manually. I am not a fan of wipe all, i just like to verify my actions, so I do it manually. I am definitely not sure what is causing issues, but different phones have different actions on kernels in general, and our phones arent even near ready to handle them. That is why it is taking so long in order to push out official ICS, cause they need it to function on every phone, not just one. I am running mijjah XPLOD mini, and it works fantastic on my phone, but during charging it overheated until I flashed over the FD19 kernel.... Then problem solved. Maybe just a lot of these phones were first gen epic touches, and they couldnt handle the newest kernel..... I just bought my phone in december, so maybe my phone can handle it.... Just a something to ponder over.
Sent from my SPH-D710 using xda premium
Entropy512 said:
FYI there's evidence of problems in the kernel source.
I9100 update4 seems fine - but apparently Koreans are having lots of problems with the SHW-M250S/K/L source drop, and also gokhanmoral of SiyahKernel encountered a bunch of bricks when he attempted to rebase on the SHW-M250* source code base.
Click to expand...
Click to collapse
Thanks Entropy512 for the great response and insight! I hope more of the newbies (and some of the other hold outs) read your post. If guys like you, SiyahKernel, SteadyHawkin and some of other unbelievably fantastic devs can major issues and/or brick their device, and have found it to be the kernal (the other 'real' devs' have said that too!); than I for one and going with that! Thanks for all your work. Hopefully we'll get the final real source soon and than can pick through that.
-EViL-KoNCEPTz- said:
It is the data partition I believe, I'm not 100% sure on this but I think the wipe in recovery doesnt actually just wipe but reformats and resets the partition sizes whereas the wipeall zips just erase the data leaving the partitions alone
To simplify compare it to reformatting your harddrive in your PC.vs just factory resetting it or deleteing the data off of the drive leaving the OS intact but removing added on data
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I think you nailed it EK. If you watch what's going on in recovery when you flash the format all zip, it formats system which is not the same as a factory reset. After system it formats cache and dalvik. I haven't heard of any bricks flashing Calkulin's format all zip with an ICS recovery and then flashing an ICS rom. I've done it myself a few times but to be safe I now flash the EL26 kernel first.
I'm just curious what the general consensus is out there between these two recovery modules. I've always used cwm rec until recently when I couldn't test flash ANY cm10 jb roms. I had to install twrp in order to flash them and it worked right away. It nice to have touchscreen controls but newer cwm's have that now too so I guess I just want to be sure I'm not losing anything or missing out on anything by leaving cwm rec for twrp .. and many say to switch anyways but what is the general feeling out there and what are you others using?
Sent from my SGH-I747M using Tapatalk 2
TWRP to me just has a better layout and mor responsive touch UI.. Havent had any problems with it so far not being able to flash or anything so...
+1 TWRP is overall smoother and easier to use IMO, and 0 issues so far flashing anything or restoring backups.
I've used CWM since it was available for the Samsung Captivate. Great program. I'm now using TWRP, and I like it better. It appears to be faster, quicker backups and allows for more options. TWRP feels more responsive than Touch CWM (and I paid for that program).
Two points to consider. Backups for each program are only able to be restored by that program. Meaning, you can't restore a CWM backup using TWRP and you can't restore a TWRP backup using CWM.
If you use TWRP v2.2.1, the INTERNAL SD card mount point is \data\media instead of extSdCard. That's really confusing for CWM users and really annoying general.
You can flash recovery zips in both CWM or TWRP.. I flash my .zips from the external card now that I'm using TWRP.....
Both great programs....:good:
My favorite part about TWRP is that you can enable compression on nandroid backups.
Sent from my SGH-I747 using xda premium
cellgeek said:
I've used CWM since it was available for the Samsung Captivate. Great program. I'm now using TWRP, and I like it better. It appears to be faster, quicker backups and allows for more options. TWRP feels more responsive than Touch CWM (and I paid for that program).
Two points to consider. Backups for each program are only able to be restored by that program. Meaning, you can't restore a CWM backup using TWRP and you can't restore a TWRP backup using CWM.
If you use TWRP v2.2.1, the INTERNAL SD card mount point is \data\media instead of extSdCard. That's really confusing for CWM users and really annoying general.
You can flash recovery zips in both CWM or TWRP.. I flash my .zips from the external card now that I'm using TWRP.....
Both great programs....:good:
Click to expand...
Click to collapse
Yep, I too had been using cwm since my first Captivate...and have always enjoyed it but have also recently switched to TWRP and find it to be better and plan to use it now.as.my only recovery.
It is unfortunate but true that u can't restore backups from the others program so all.my old.cwm nandroid backups are basically useless now unless I reinstall cwm but that's OK moving forward I guess.
I too was a bit confused by the internal.SD card file.system location in data/media and still.don't understand it but as long as u know then its OK. So far it sounds like twrp is the future of recovery and more and more people are switching...and the touch function and extra options.are.nice.features.
The bottom line is as long as I am not missing out on something or losing some important functionality then I'm fine with the switch from cwm and.will.stay with TWRP but will never deny the popularity and usefulness of cwm and how it got me going in the whole.game of flashing and.mod'ing phones.
TWRP is by far the best recovery I have ever used. I couldn't imagine life without it now.
hallo13th said:
TWRP is by far the best recovery I have ever used. I couldn't imagine life without it now.
Click to expand...
Click to collapse
I totally agree. I was using CWM on my Thrill and didn't get a chance to use TWRP till I got my Fire. Now I will only use TWRP. CWM is an excellent recovery but I like the features of TWRP better.
Sent from my SGH-I747 using xda premium
a lot of the rooting/recovery guides are suggesting to use clockwork recovery, is that just because twrp wasn't really supported back then? any issues noticed with using twrp on the sgs3?
as with all programs there is no "best" just personal preference: try one, then the other and settle on that which suits yoiur phone and needs "the best"
I tried TWRP and went back to CWM -- many others, obviously, tried and preferred TWRP
TWRP is easier & more efficient to use. Bar none.
But with that said, IMO CWM is still the better recovery for some situations. First, there is more support for CWM still.
Second, if you use a ROM's built in functionality to update itself (like AOKP has), then that requires CWM as far as I can tell.
Also keep in mind that it's easier to screw up on TWRP because it is touch-based. I've accidentally pressed buttons without meaning to. It's only a matter of time before that gets me into trouble.
I just wish CWM would remove the thousand "no" that you have to sort through before getting to a "yes". And I wish they would update it more often.
I did pay for my ClockworkMOD, btw.
hey guys please give me tips on the twrp
i gave up on cwm i couldn't install cm10 on my galaxy s3 i747m ROGERS (at&t)
so can someone walk me through the twrp way of flashing cm10 rom
pleaaaaaaasee
cheers
totti107 said:
hey guys please give me tips on the twrp
i gave up on cwm i couldn't install cm10 on my galaxy s3 i747m ROGERS (at&t)
so can someone walk me through the twrp way of flashing cm10 rom
pleaaaaaaasee
cheers
Click to expand...
Click to collapse
Exactly the same as cwm. Except all wiping option are put together in the wipe menu, you can select multiple file to flash on after another and fix permissions is in the advanced menu.
Sent from my SGH-I747 using xda app-developers app
CZ Eddie said:
TWRP is easier & more efficient to use. Bar none.
But with that said, IMO CWM is still the better recovery for some situations. First, there is more support for CWM still.
Second, if you use a ROM's built in functionality to update itself (like AOKP has), then that requires CWM as far as I can tell.
Also keep in mind that it's easier to screw up on TWRP because it is touch-based. I've accidentally pressed buttons without meaning to. It's only a matter of time before that gets me into trouble.
I just wish CWM would remove the thousand "no" that you have to sort through before getting to a "yes". And I wish they would update it more often.
I did pay for my ClockworkMOD, btw.
Click to expand...
Click to collapse
I use the touch version of cwm and am very thankful for the thousands no's, help mitigate those "oh crap" moments that touch screen introduces.
Sent from my SAMSUNG-SGH-I747 using xda premium
CZ Eddie said:
TWRP is easier & more efficient to use. Bar none.
But with that said, IMO CWM is still the better recovery for some situations. First, there is more support for CWM still.
Second, if you use a ROM's built in functionality to update itself (like AOKP has), then that requires CWM as far as I can tell.
Click to expand...
Click to collapse
Task and ktoonzes aokp ota updater now works with the newest twrp.
TWRP. I like its layout, and love that I can build a stack of .zips to flash. (Not sure if CWM has that feature, won't be causing me to switch over to it.)
Encrytion and backups!
The most impressive feature of TWRP hasn't been mentioned in this thread yet.. TWRP supports flashing ROM's on devices that have been fully encrypted !
Also, it allows for backup and restore of ROMs on encrypted devices that neither CWM nor CWM Touch support.
OhNJ n
Sent from my SPH-L720 using XDA Premium 4 mobile app
I personally like cwm but the newest version has bugs so i switched to twrp but i found some sites that the 2.1 version can hard brick your phone...so im wondering if twrp 2.2 is reliable?
ClaireH said:
I personally like cwm but the newest version has bugs so i switched to twrp but i found some sites that the 2.1 version can hard brick your phone...so im wondering if twrp 2.2 is reliable?
Click to expand...
Click to collapse
I've been using TWRP 2.2 since it came out and have never had any problems with it. I was having problems with CWM and since I switched I have yet to have any complaints.
Give it a shot and let us know.
Is your question which one is more reliable which i think is more of a personal thing depending on your needs or loyalties where as is TWRP 2.2 reliable. Now I am not sure where and what circumstances 2.1 TWRP may have bricked a phone but since we are running 2.2 there is nothing to worry about. For as long as it has been out if there were any issues you would of heard of them by now. Try them both and you figure out which one better suits your needs
I used to use CWRM ( tried the latest touch and non-touch ) because I was familiar with it and the brick reports scared me, but I used to have a lot of issues after flashing ROMs and restoring texts, even though I did everything right.
Finally said screw it, and tried TWRP 2.2 - my issues are now mostly gone. And queuing up zips and a file manager are niice. So yea, my vote's on TWRP.
Russian smashed across the interwebz from my Galaxy SII.
The reason people were getting bricked on older versions of TWRP is due to user error. Once you wiped the system and ROM, the phone is "blank." People were then clicking the "reboot system" option without flashing a new ROM. As such, the phone couldn't boot. New version does not allow that option.
TWRP is the best in my opinion as it has several features like zip queueing (queue all of your zips at once ex: ROM, Gapps, etc...) and an onscreen keyboard for naming backups.
Only thing I don't like about TWRP is no "wipe battery stats". Other than that, TWRP is nifty but I still use darkside wipes out of habit from CWM.
Hype As Fruck said:
Only thing I don't like about TWRP is no "wipe battery stats". Other than that, TWRP is nifty but I still use darkside wipes out of habit from CWM.
Click to expand...
Click to collapse
Per Google themselves, wiping battery stats is not necessary and does nothing. Any perceived benefit is purely placebo.
Rod3 said:
Per Google themselves, wiping battery stats is not necessary and does nothing. Any perceived benefit is purely placebo.
Click to expand...
Click to collapse
Per darkside cache wipe... "wiping battery stats" and never had a battery reading issue.
Sent from my SGH-T989 using xda premium
I put CWM on my phone because it's what came with the CM9.1 ROM that I originally flashed.
After switching to a different rom such as Jedi Knight or JMT9, I found TWRP 2 to work wonders for what I need and the way I want info to be displayed. I found that with the touchscreen functions it's much easier to navigate recovery, though CWM has touchscreen functions now as well.
I prefer TWRP. It wipes everything completely clean, no need to flash TDJ's superwipe. It is also more reliable than CWM imo.
Sent from my SGH-T989 using xda app-developers app
Alarmmy said:
I prefer TWRP. It wipes everything completely clean, no need to flash TDJ's superwipe. It is also more reliable than CWM imo.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I was using CWM and switched to TWRP for this reason. No extra superwipe steps.
Hype As Fruck said:
Per darkside cache wipe... "wiping battery stats" and never had a battery reading issue.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Cache wipe does not wipe battery stats, only cache and dalvick. Per if it helps you sleep at night, use CWM and wipe them.
Sent from my SGH-T989 using xda premium
Hype As Fruck said:
Per darkside cache wipe... "wiping battery stats" and never had a battery reading issue.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I think that was put in place to keep people from asking for it, as well as for completeness.
It does nothing on our phone. Fact
Sent from my SGH-T989 using xda app-developers app
Dougshell said:
I think that was put in place to keep people from asking for it, as well as for completeness.
It does nothing on our phone. Fact
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I know they say wiping battery stats does nothing but so many swear by it that at this stage you might as well let them just go for it.
OP - It looks like TWRP has won in your poll, now that you have asked the question what will you do with this info?
I've tried both... never really had issues... One thing Im finding is that alot of MMS/SMS/Call Log etc. recovery tools will not work with a CWM 6 nandroid backup... Managed to get them out with Titanium Backup though, so not a problem
After switching from CWM, I've never had an issue with TWRP 2.2 so far.
But, if you decide to use CWM, I'd like to suggest: CWM 5.0.27non-touch + Darkside scripts.
TWRP is preferred
I use TWRP because of the UI and reliability. Never had an issue with it.
In some threads, OP request that you use a certain recovery whether its CWM (certain version) or TWRP so I usually keep different recoveries saved to my sd card just in case.
Plus TWRP looks better.
Go with TWRP, you will be for sure to not need those Darkside Wipes. (Reliable)
on CWM you may have to use them, depending on version (Questionable)
Im new to this device and have been reading through the dev forums and notice that everyone uses different recoveries. Does it matter really wich one you use? I like twrp but I had problems with it when I had my g2x. Is there a deffinitave answer as to wich one works best on this device? (CWM or TWRP) I know that this is mostly based on user preference but it seems that some custom roms will only install on a specific recovery.
Thanks in advance.
Sent from my SGH-T989
personally everyone has there own opinion i use CWM on my vibrant & GS2 but i use TWRP on my nexus s and nexus 7 not sure what my mytouch uses but CWM for always will and always has worked well without any bugs or hiccups that TWRP sometimes has but TWRP is very simple and straight forward its all on whats your preference though if you are going to use TWRP the latest is 2.6 and you should not flash it through GOO manager use the odin file when you get there
TWRP is by far a better way to go, not that CWM is a bad recovery, its just not updated frequently, and with the new scripts flashing jb roms sometimes things don't always work right, I've used both and I think twrp is a better choice, I've never had an issue with it like I have on cwm, plus with twrp u won't need superwipe scripts or anything like that anymore, overall I think its a more complete recovery
Sent from my SAMSUNG-SGH-T989 using xda premium