I've been reading through tons of posts trying to figure out which recovery works best for flashing zips and/or installing OTA updates. I'd like to get a thread going so that it's more clear which recovery ROM is recommended and why. I've been using TWRP but find the touch to be spotty at BEST, also I got my phone into a bootloop after installing the 174.44.1 OTA update and it seemed like a lot of ppl that had no issues were using Philz CWM. So anyway, please post opinions!
I have the same query.
grahamgo said:
I have the same query.
Click to expand...
Click to collapse
Have also been reading a lot about those recoveries.
I started with CWM because I had good experience with it on my Acer S120.
Recently (yesterday to be precisely) I changed to Philz CWM after I had to do a reflash of the whole system.
I decided for Philz because of the buggy touch functions from TWRP I read about.
So far I'm pleased with Philz CWM.
Can you link to where you obtained Philz CWM and which version are you using. I have just installed TWRP v2.6.3.0 and it seems fine (I couldn't find v2.6.3.2 which I think is the latest ver).
i had philz cwrm and when i did "restore default" for resetting settings original from menu settings, didn't work. it is a bug and for me, that want a phone complete working, this is important. most users use wipe from recovery but i want that function!!!
now i have v2.6.3.2 twrp and all is workind, even touch slide that before (until 2.6.3.0) was bugged.
same issue of philz recovery for my ex phone htc desire 500.... is philz that insert something error for restoring and even i asked many forum, noone know solution and many users don't know because don't try (or don't want try)
I use twrp with no issues at all (pretty sure the touch bug was fixed a while ago). But then I've also heard that Phil's cwm is brilliant, so I guess it's just down to personal preference?
Sent from my Google Nexus G -
Can someone point me to the correct twrp 2.6.3.2 for moto g please. The one I found installed but says its 2.6.3.0 although its working fine.
Sent from my Nexus 7 using Tapatalk
grahamgo said:
Can you link to where you obtained Philz CWM and which version are you using. I have just installed TWRP v2.6.3.0 and it seems fine (I couldn't find v2.6.3.2 which I think is the latest ver).
Click to expand...
Click to collapse
Here is where I got mine http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt1032
It's for the XT1032 ofcourse.
grahamgo said:
Can someone point me to the correct twrp 2.6.3.2 for moto g please. The one I found installed but says its 2.6.3.0 although its working fine.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I read somewhere that it was a typo. Mine says 2.6.3.0 after the install of 2.6.3.2. And yes its running fine, no bugs that I can see.
@slamor. OK, thanks yes its very responsive and seems to be perfect, the date is now correct too. Just that niggling v2.6.3.0 that shows up. I am reluctant to try Philz CWM only because I have several backups that I want to hang onto. Maybe Philz CWM uses the same backup/restore format? But right now it ain't broken, so no need to fix it!
Sent from my Nexus 7 using Tapatalk
I dont know about that. From past experience I could Never use CWM backups on TWRP and vice versa.
Think about it as ...working.
Related
Hello, I'm using T-Mobile (UK) HTC One SV with JB (rooted)
I follows this link to root my phone and thus I've got the JB CWM version listed in the link.
The problem is when I boot into recovery mode into the CWM, the screen is shifted a bit to left and the cropped/shifted part is appearing on the right! (I hope I'm making some sense with this 'shifted screen' explanation. I'd like to post a screenshot if someone can help me with getting a screenshot in recoverymode) Anybody else facing this problem? If yes, how can I fix it?
On a slightly different note, I'd like to admit that whilst following the rooting procedure mentioned above, I tried to be a 'smart arse' and tried flashing CWM 6.0.3.8 on the device, which just wouldn't load /data with error
Code:
Can't mount /data
and same with cache and respective logs. And because of that I wasn't able to do a backup either. I tried, quite a few times, to format the SD card into FAT32 etc but it was having none of it! :crying:. Then when I slapped myself for not following the procedure, like a good boy , and got the same CWM listed in the link, I was able to do backup and no errors were being displayed in regards to mounting of /data. :good: I thought I'd share my experience on for others to learn from.
This screen flickering is a know problem of this touch recovery.
Its not developed to the end.
I recommend you to use TWRP recovery which is fully functional.
old.splatterhand said:
This screen flickering is a know problem of this touch recovery.
Its not developed to the end.
I recommend you to use TWRP recovery which is fully functional.
Click to expand...
Click to collapse
Thanks for quick reply. I've never used TWRP and to be honest, quite new to this depth of rooting, recovery etc. Does TWRP offer similar set of features as CWM? And is there a 'touch' TWRP for this device on JB? If so, could you kindly post me the link.
Most up to date version you will find here:
[TWRP 2.6] Updated 9/21/13 All variants TWRP recovery 2.6
Another (older):
[Recovery] TWRP Recovery 2.x
Yes, all touch and has more features than cwm.
old.splatterhand said:
Most up to date version you will find here:
[TWRP 2.6] Updated 9/21/13 All variants TWRP recovery 2.6
Another (older):
[Recovery] TWRP Recovery 2.x
Yes, all touch and has more features than cwm.
Click to expand...
Click to collapse
Thanks a lot! I shall give it a try
I'm rooted and was running stock 4.4.2 with an unlocked bootloader. I flashed CWM 6.0.4.4 touch recovery and I can't even boot into recovery. It bootloops. Any ideas?
edit #1
Actually it just booted into fastboot and it gave the reason "Flash Failure" huh?
edit #2
Seem's the best bet is to steer away from CWM and use TWRP, Booted to fastboot, flashed twrp and than cyanogenmod and boom. I'm where I wanted to be. I'll try to help figure out what's up with CWM though if that would help anyone else that had this issue....
there is nothing wrong with cwm. you used a version not compatible with your system version.
bweN diorD said:
there is nothing wrong with cwm. you used a version not compatible with your system version.
Click to expand...
Click to collapse
This. 6.0.4.4 is not compatible with the KK OTA. If you want to use CWM you need to use the 6.0.4.9 one dhacker posted last week.
I'm new to rooting/unlocking. I used towelroot and Moto-pocalypse on an XT926 running KK. I know that I need to use CWM to backup my phone, but all the tutorials I found online seem outdated. I was wondering if someone could link me to a more recent tutorial or explain to me what I need to do. I would really appreciate it.
Hi,
i'm using the official CM 11 on my XT925 and pretty much installed every new Nightly - never had any serious Problems, not even with Bluetooth (i get no Track in the Display, but at least it works ).
Since the 01.07.2014 Nightly i can't install the Nightlys anymore, because it wants a KK/ Kernel 3.4 compatible Bootloader. First, i flashed the new TWRP 2.7.1.0. Didn't work, very strange Problem (see below). So then i tried the new CWM 6.0.4.9. Also didn't work... same error message as with CWM 6.0.4.4 (which I used until now) - "no KitKat Compatible recovery detected". So I tried philz touch recovery. Also doesn't work.
Now i'm back with the 30.06.2014 Nightly.
Now the strange part: TWRP didn't recognize any touch inputs at all, I had to hard-reboot the phone. Also Philz touch recovery didn't recognize any touch inputs. CWM 6.0.4.4 hat the "Swipe-Touch" thingy, which I used, but it seems that CWM 6.0.4.9 also doesn't recognize any touch inputs! I can't swipe.
So the big questions are: What the hell have I done wrong, that no Recovery is not recognizing any touch inputs anymore?! Flashed it with fastboot, everything looked ok, only got an "ERROR: could not get pipe properties", but it flasehd it and it worked - apart from the touch.
It wouldn't even be such a big "bother" if the new CWM could install the new CM Nightly... Am I really stuck with 30.06.?
greetings,
David
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So, to install new nightlies we have to flash the KK OTA first, right?
TYG
pbosio said:
So, to install new nightlies we have to flash the KK OTA first, right?
Click to expand...
Click to collapse
Take a look HERE.
If I were you I'd wait for the official kk bootloader....if you read the previous post the method being used is risky for our model.
Sent from my RAZR HD using XDA Free mobile app
i was installing elementalx on my nexus 5 via cwm. after going through the installer it asked if i wanted to fix root as i would lose it otherwise. i clicked yes. after that it started rebooting but got stuck on google. then went black. then again it showed google and is still looping. please help!!!
Try clearing cache by going to recovery.... Else my man you might need to flash stock again .....
To shutdown the phone press volume down and power till the time you get 3 vibrations
Dirty flash the ROM your on. What ROM did you flash EX on top of?
1) Download and flash the latest TWRP recovery.
2) Reflash your ROM. (Wipe cache and Dalvik)
3) Reflash ElementalX.
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).
BirchBarlow said:
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).
Click to expand...
Click to collapse
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.
theesotericone said:
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.
Click to expand...
Click to collapse
It was the other way round for me.... Twrp gave me issues .... I always use cwm touch .... Works good for me
i was on stock
BirchBarlow said:
1) Download and flash the latest TWRP recovery.
2) Reflash your ROM. (Wipe cache and Dalvik)
3) Reflash ElementalX.
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).
Click to expand...
Click to collapse
i am on stock so will i have to install the 5.0.1 factory image. also once in a while green screen comes asking whether to reboot or go into dload mode. also do i flash twrp before the factory image. can you tell me how this is done via pc as i was using flashify.
thanks guys
thanks guys it worked. i flashed stock and its working perfectly. thanks.
theesotericone said:
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.
Click to expand...
Click to collapse
I didn't say it doesn't work, I said it's problematic. I believe CWM is built on JB, so incompatibilities exist with KK and LP. For example, when you exit CWM whether you are rooted or not, it will tell you that you have a problem with root and offer to fix it. This is because CWM can't detect the SuperSU binary, it doesn't search the right place. Therefore novice users will say select okay causing CWM to install an outdated version of the SuperSU binary into the wrong location causing all sorts of problems with KK or LP. This is just one example of why it's better to just avoid CWM. TWRP is current and backward compatible. CWM is practically ancient.
1. CWM lacks functionality
2. CWM uses outdated legacy location of /data/media rather than /data/media/0 as sdcard/internal storage
3. CWM's option to "fix root" actually breaks root (and possibly other things)
BirchBarlow said:
I didn't say it doesn't work, I said it's problematic. I believe CWM is built on JB, so incompatibilities exist with KK and LP. For example, when you exit CWM whether you are rooted or not, it will tell you that you have a problem with root and offer to fix it. This is because CWM can't detect the SuperSU binary, it doesn't search the right place. Therefore novice users will say select okay causing CWM to install an outdated version of the SuperSU binary into the wrong location causing all sorts of problems with KK or LP. This is just one example of why it's better to just avoid CWM. TWRP is current and backward compatible. CWM is practically ancient.
Click to expand...
Click to collapse
Lethargy said:
1. CWM lacks functionality
2. CWM uses outdated legacy location of /data/media rather than /data/media/0 as sdcard/internal storage
3. CWM's option to "fix root" actually breaks root (and possibly other things)
Click to expand...
Click to collapse
I never really thought about it from a noob stand point so there is that. With me it works but I will stop publicly saying so after this post. You guys do bring up valid points and I'm just used to using it. TWRP back when had loads of issues so I steered very clear of it for a long time. Now it seems the tables are turned. I know eventually I'll have to make the switch but for now I'm still happy with playfulgods swipeable build of CWM. You both have my respect for trying to steer users down a more user friendly option.
theesotericone said:
I never really thought about it from a noob stand point so there is that. With me it works but I will stop publicly saying so after this post. You guys do bring up valid points and I'm just used to using it. TWRP back when had loads of issues so I steered very clear of it for a long time. Now it seems the tables are turned. I know eventually I'll have to make the switch but for now I'm still happy with playfulgods swipeable build of CWM. You both have my respect for trying to steer users down a more user friendly option.
Click to expand...
Click to collapse
Hey, what works for you, works (until it breaks, of course).
But for newer users, TWRP is now recommended as it's more friendly, as well as being up-to-date. CWM has had it's time.
Has anyone one used the latest twrp recovery? I know know there have been issues with past versions.
Been working fine for me. I only use it for a little before flashing ktoonsez recovery. If you aren't having issues with your current one, really no need to change. I just always grab the latest when "starting over" from a full firmware flash.
El.Dante565 said:
Has anyone one used the latest twrp recovery? I know know there have been issues with past versions.
Click to expand...
Click to collapse
I always grab the latest. So I snatched it up when 2.8.7 hit the floor. In fact this was my first time installing twrp with twrp. I have always used Odin but it's easy and it's been working great for me since the day it was released
Sent from my SM-G900P using Tapatalk
elesbb said:
Been working fine for me. I only use it for a little before flashing ktoonsez recovery. If you aren't having issues with your current one, really no need to change. I just always grab the latest when "starting over" from a full firmware flash.
Click to expand...
Click to collapse
I'm currently on NK5 4.4.4 and haven't updated it.. I know there's a current L update I can download, OTA, but I rather try some roms.. The thing is I'm not too sure about what recovery I can install. Is TWRP 2.8.7.0 gonna work with me or do I have to use SafeStrap? There's a bunch of options but not too clear on what will work with the current state my phone is in. I'm ready to root. Just need to know what custom recovery to flash..
kaslopis said:
I'm currently on NK5 4.4.4 and haven't updated it.. I know there's a current L update I can download, OTA, but I rather try some roms.. The thing is I'm not too sure about what recovery I can install. Is TWRP 2.8.7.0 gonna work with me or do I have to use SafeStrap? There's a bunch of options but not too clear on what will work with the current state my phone is in. I'm ready to root. Just need to know what custom recovery to flash..
Click to expand...
Click to collapse
Well I have used twrp recovery pretty religiously it has an good interface. Some find the Phil's CWM is good as will although I don't think that they is any more support for that, but there is one floating out there. I have never used SafeStrap. I believe that is used for lock bootloader which would be unnecessary for our Sprint phone which are unlocked.