Just recovered from an issue using cwm recovery on a HTC Rezound. While it was fun to resolve, fear of turning it into a paperweight was not the best feeling.
Will there be similar issues with cwm recovery on the N7? Should one stay away from a ROM that requires cwm recovery?
I've had no problems with cwm on the Nexus 7. What kind of problems did you have?
*Sent from Nexus S*
I have flashed, probably, ten times on my N7.....All using CWM with absolutely no problems.
The official cwm 6.0.1.0 is still rock solid touch recovery. No problem since I had it. I'm constantly using it for the cm10 nightlies and custom kernels.
Tapatalked from my Ace 2
I did have one instance where CWM recovery couldnt see the storage and i could not flash anything after formatting. I had a backup on the PC though and was able to bring it back manually.. its always a good idea to be careful!
Sent from my Google Nexus 7 using xda app-developers app
Related
I'm trying to get Clockwork Mod installed on my wife's Nexus S via ROM Manager but whenever I reboot into recovery it's just the default recovery.
I had this issue with my Nexus S too and I never resolved it. I was only able to flash via fastboot. This isn't an option on my wife's phone as it's not unlocked and I don't want to wipe everything.
Sent from my Nexus S using XDA
How can you flash cwm without unlocking? I don't think that's possible(correct me if I'm wrong).
Sent from my Nexus S from Tapatalk
ljordan2 said:
How can you flash cwm without unlocking? I don't think that's possible(correct me if I'm wrong).
Sent from my Nexus S from Tapatalk
Click to expand...
Click to collapse
You mean rooting? You're supposed to be able to flash it from within Android if your phone is rooted. OEM unlocking the phone lets you flash things from the bootloader. However, despite that I haven't been able to do it.
I finally gave up. Since the phone is rooted I just backed everything up with Titanium Backup and then OEM unlocked the phone and I'm not restoring from scratch. Not sure I'll ever have an answer to this issue.
Note: If the phone is rooted and you have flash_image, you can use that to flash custom recovery(without bootloader unlocking) 'manually'.
cbstryker said:
I'm trying to get Clockwork Mod installed on my wife's Nexus S via ROM Manager but whenever I reboot into recovery it's just the default recovery.
I had this issue with my Nexus S too and I never resolved it. I was only able to flash via fastboot. This isn't an option on my wife's phone as it's not unlocked and I don't want to wipe everything.
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I have had the same problem with ROM manager ever since I bought it. What I do is flash the recovery a few times. I'll hit flash recovery, and when it finishes I'll do it like 3 or 4 more times and eventually the recovery will stick.
Sent from my Nexus S using xda premium
To fix this, flash CWM recovery using ROM Manager, and then install root explorer. Using root explorer, rename /system/etc/install-recovery.sh to something else (e.g. /system/etc/install-recovery.sh-RENAMED) and that should make your CWM recovery stick. Otherwise it gets overwritten on each boot by the stock Android recovery.
I actually just learned this over the weekend when I got my new NS and I had to do the same thing. I've previously been a happy SGS i9000 owner for the past 2 years, so the NS is pretty new to me still.
i had the same bug i flash a more oldest vercion of rom manager and cmw and that work for me but im crazy ,there are better methods I just tell my experience
Just flashing using CWM..dont flash using ROM manager...many users have problems flashing from ROM manager..
rhainman said:
To fix this, flash CWM recovery using ROM Manager, and then install root explorer. Using root explorer, rename /system/etc/install-recovery.sh to something else (e.g. /system/etc/install-recovery.sh-RENAMED) and that should make your CWM recovery stick. Otherwise it gets overwritten on each boot by the stock Android recovery.
I actually just learned this over the weekend when I got my new NS and I had to do the same thing. I've previously been a happy SGS i9000 owner for the past 2 years, so the NS is pretty new to me still.
Click to expand...
Click to collapse
This ^
Sent from my Nexus S
I used to use CWM for everything, but then on my one xl TWRP worked a lot better. How is it on the N10? Anything missing from either one? Is CWM still the the more common one?
Sent from my One X using xda app-developers app
I'm using TWRP on my Nexus 10. I used to use CWM on my S3, but switched to TWRP. Mostly for goomanager support and placing your back ups to an external SD card. Also unlike CWM it's easier to place backups on your computer because there are no "blobs" like CWM.
Not saying CWM is bad, I just prefer TWRP.
I just finished flashing twrp on my galaxy nexus this weekend and reclaimed more than a gig of wasted space, (wtf is blobs?). Now all my devices run twrp as a recovery. Also for the first time since my nexus one I don't have rom manager installed. Twrp/goo is the recovery of choice these days.
Don't forget to donate, it's a small price to pay for what your getting!
I found TWRP better on my Nexus 7 then CWM. I haven't tried CWM on my Nexus 10, but TWRP is working great, and I have no reason to try CWM currently.
espionage724 said:
I found TWRP better on my Nexus 7 then CWM. I haven't tried CWM on my Nexus 10, but TWRP is working great, and I have no reason to try CWM currently.
Click to expand...
Click to collapse
I installed cwm because i didnt really know twrp. Im not sure if its as usual but my cwm is rebooting into recoveryevery 15 sec...
Ill flash twrp now
Which one should i use ? I heard that some people have issue flashing with TWRP .. Is this a lie ?
tlf55 said:
Which one should i use ? I heard that some people have issue flashing with TWRP .. Is this a lie ?
Click to expand...
Click to collapse
Both TWRP ans CWM are good. You could also try Phil`z Touch recovery from here http://forum.xda-developers.com/showthread.php?t=2210081&highlight=phil+z. It`s just that TWRP has some more options and it is themable. For me personaly CWM is fine. Just try them out and keep the one you like most.
I never used CWM as I have always used TWRP.
I would recommend TWRP because its easy to understand and theme-able.
i used cwm for a long time. then tried twrp and well, its better. its faster, i seem to have less problems overall and its finally starting to be aware of what im doing, that means flashing is easier because it tries to guess what you will need next, like wipe/cache buttons after flashing instead of making you click through a myriad of hacky options, things like staying in the folder where you picked your last file or install-queues made me switch.
molesarecoming said:
i used cwm for a long time. then tried twrp and well, its better. its faster, i seem to have less problems overall and its finally starting to be aware of what im doing, that means flashing is easier because it tries to guess what you will need next, like wipe/cache buttons after flashing instead of making you click through a myriad of hacky options, things like staying in the folder where you picked your last file or install-queues made me switch.
Click to expand...
Click to collapse
This guy knows what's up.
+1 to that.
TWRP every time for me.
I just find CWM fiddly and over engineered, especially the touch version.
TWRP has nice big buttons for my sausage fingers too. You're a lot less likely to do something wrong by accident in TWRP due to it's "Swipe to activate" function
Is 2.5 the latest twrp version
Sent from my Nexus 4 using xda premium
im still on cwm
[FONT="Arial ="5"]
• Sony Live with Walkman
I use CMW on my S3 and TWRP on my N4.
I have been using CMW for years and I'm very use to it. I don't really like how TWRP looks. Although it looks simple to use because of the large tiles but I still prefer CMW any other day.
Sent from my Nexus 4 using Tapatalk 2
CWM is nice and straight forward. It can be a little confusing at first in TWRP how to wipe /data while maintaining /data/media. However, TWRP supports open recovery scripts while CWM uses a proprietary format only supported by its own ROM Manager.
Haven't used either on the N4, but my vote goes to TWRP.
CWM for long time and I like it a lot so never bother myself to change it
Sent from my Nexus 4 using Tapatalk 2
I've never had any problems with CWM or TWRP, but I prefer TWRP's interface. Try them both and stick with the one you like?
Twrp is miles ahead of clockwork.
Queue flashing is brilliant
Sent from my Nexus 4 using xda premium
Another vote for TWRP. Queuing up your zips is great. There are also themes for it.
Sent from an N4 blessed with AOKP and sanctified by Faux123!
Although I like TWRP better I've had quite a few failed ROM flashes with it. I don't have those same problems with the same files with CWM. This is on three different phones that I currently have.
I prefer to like Cwm than twrp but, I just wanna feel twrp ... How to install twrp? Can it be flashable zip?
Sent from my Xperia Live with Walkman using xda premium
airjyp said:
I prefer to like Cwm than twrp but, I just wanna feel twrp ... How to install twrp? Can it be flashable zip?
Sent from my Xperia Live with Walkman using xda premium
Click to expand...
Click to collapse
You can have the TWRP recovery in 3 ways, 1) flash it via fastboot, 2) install via flashable zip file in your current recovery, 3) use ROM Manager and flash it.
Easiest way to install TWRP is probably through goomanager.
I've installed TWRP on all my devices so far. I like the interface of it more than cwm. Just flash both and check them out, everybody has its own preferences. (like on kernels and roms ... )
go to the TWRP thread and click on the paperclip in the thread name and you will see a bunch of different version of TWRP but may I suggest the latest for N$ 2.6.3.3... When you flash its generally multiple files and TWRP allows for less usage as far as your volume button is concerned.
I am new to rooting. I have rooted my razr m from the official 4.1.2 update. I want to install roms.
I have installed the safestrap 3.12 and every time i reboot my device it says "safestrap:disabled" and just normally boots my device.
Help!
oox102 said:
I am new to rooting. I have rooted my razr m from the official 4.1.2 update. I want to install roms.
I have installed the safestrap 3.12 and every time i reboot my device it says "safestrap:disabled" and just normally boots my device.
Help!
Click to expand...
Click to collapse
You'll have to press the button that says "click here to enter recovery"
If it's not there, you flashed the wrong safestrap. Most ROMs are going to CWM/TWRP tho, so it may not be a bad idea to unlock and install one of those
Sent from my XT907 on CM10 using Tapatalk 2
sloosecannon said:
You'll have to press the button that says "click here to enter recovery"
If it's not there, you flashed the wrong safestrap. Most ROMs are going to CWM/TWRP tho, so it may not be a bad idea to unlock and install one of those
Sent from my XT907 on CM10 using Tapatalk 2
Click to expand...
Click to collapse
Cannon
I also have SS 3.12 out of habit I guess. I know there are other choices now like TWRP 2xx or 3xx. I'm still a little confused tho maybe you can clarify for me:
When Hashcode developed SS, didn't he base it of off TWRP? So why would (should) I switch if its technically the same program?
The only reason I was reluctant to move over to the newer TWRP recover WA because I have a few safe strap recoveries that I'm afraid would work with TWRP. Do you know if they are compatible? If they are then I'll switch.
And you did mention CWM, but I was under the impression that CWM was dated and considered an older (inferior) recovery option compared to SS our TWRP? Is there a new CWM now with a similar interface to TWRP?
the only issue I have with SS is when I try to create a new ROM slot it only uses the internal storage (which if very limited on my phone) but I have tons if free space on my ext SD card. If the new TWRP or CWM have an option to utilize the external space for the creation of ROM slots that would be great!
Thanks
Sent from my XT907 using xda app-developers app
OK so SS is not actually a recovery. It's a hack to get something like a recovery (and a very good hack at that) but it's not actually recovery. With twrp or cwm, if you happen to flash /system, you can still access recovery.
Twrp has more features than cwm, but cwm isn't outdated. Either works fine, I prefer cwm tbh.
Sent from my XT907 on CM10.1 using Tapatalk 2
sloosecannon said:
OK so SS is not actually a recovery. It's a hack to get something like a recovery (and a very good hack at that) but it's not actually recovery. With twrp or cwm, if you happen to flash /system, you can still access recovery.
Twrp has more features than cwm, but cwm isn't outdated. Either works fine, I prefer cwm tbh.
Sent from my XT907 on CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the info. I knew there was more to it than I realized.
Sent from my XT907 using xda premium
I've had this problem since I first flashed the 10.1 nightlies months ago, and I was curious if anyone else has noted this problem.
When I turn off or reboot my phone, more often than not the Samsung Galaxy S4 logo screen just hangs there, without booting into the OS. I often have to reboot my phone 4 or 5 times to get CM to boot. This has been happening more and more frequently too.
Does anyone else have this issue?
Which recovery/version are you using to wipe/flash?
According to Cyanogenmod this is already a known issue. Check their Original Cyanogenmod thread and post #2.
Just found out myself.
xBeerdroiDx said:
Which recovery/version are you using to wipe/flash?
Click to expand...
Click to collapse
I'm going to take a wild stab in the dark and say TWRP. I've never had an issue with any other recovery after formatting data.
Sent from my GT-I9505G using xda app-developers app
Most likely it's a problem with TWRP.
Just wondering, how would someone with TWRP flash to CWM? Would they have to use odin to flash to stock, root and then download clockworkmod to flash? Or can I just flash CWM over TWRP?
Im running slim bean with twrp 2.5.0.2 and experience this problem.
When stuck on Samsung screen boot into recovery. When in twrp recovery use the option in the lower right to boot into recovery again. Then use that same option to boot system.
Sent from my SGH-I337 using xda app-developers app
Use CWM instead of TWRP. I was using TWRP and had this issue 1 out of 3 reboots. I haven't had the Samsung logo hang since I flashed CWM.