Up until recently, I've been a fan of CWM, but now that I am playing with 4.4 custom ROMs and various kernels (particularly Apolo), I am getting some experience with TWRP as well. I like TWRP. It seems more flexible than the 4.4. compatible CWM, but I'd like to know which is really the preferable recovery to use, i.e, what the typical shortcomings or problems are with each with 4.4.
corvus.corax said:
Up until recently, I've been a fan of CWM, but now that I am playing with 4.4 custom ROMs and various kernels (particularly Apolo), I am getting some experience with TWRP as well. I like TWRP. It seems more flexible than the 4.4. compatible CWM, but I'd like to know which is really the preferable recovery to use, i.e, what the typical shortcomings or problems are with each with 4.4.
Click to expand...
Click to collapse
It comes down to which you prefer. One isn't technically 'better' than the other. However on i9100 with a combined kernel/recovery, you'll likely end up using whatever comes bundled with your kernel of choice. Bear in mind you can't 'mix' backups between the two... I.e. if you make a backup in TWRP, you need to restore it in TWRP, same goes for CWM.
Sent from a galaxy far, far away
I was using CWM with the stock rooted roms until about the end of last year, when I switched to Omnirom which uses TWRP.
I think TWRP is more easy to use it, with a better UI.
I used CWM until i upgraded to KK, now im with TWRP, other that the fact im still a bit lost on menus at times, i havent really felt much of a difference (im not much of a power user, just the usual wipe/new rom kind of person)
Related
Folks...
I've been using ClockworkMod for a while on my HTC Incredible and today I received my Woot table.
I installed ClockworkMod on the tablet and did a backup of my "stock" image (I applied the 3588 update).
From reading these ROM threads, it looks like there's some differences in how I am used to interacting with Clockwork and some of these warnings sound pretty ****ing dire...
If I install a ROM, isn't going back to my previous backup a matter of formatting and restoring? It sounds like some of these ROMs interfere with Clockwork in such a way that could result in a bricked device. I've been wiping and restoring on my Incredible for almost a year now and I've never heard of a ROM dicking with Clockwork before...
What's the difference or am I making a mountain of a molehill here?
There is a very specific version of CW that bekkit put together for the G=Tab. The problem isn't the rom messing with CW, it usually is Rom Manager that will mess with it. Rom Manager usually will want updated, especially with CM installs.
I have had to nvflash the tablet in the past after upgrading CW via rom manager.
The other issue that is common, and I have had happen to my beloved Dinc, is having to repartition the storage. The groundwork for the Dinc was much, much more stable than the default tapNtap that is released with the tablet.
Something some people may also miss is the kernel for GB is much different than the kernel with froyo.
Rest assure, bricking this thing seems to be an accomplishment and almost impossible. Trust me, I have given my best effort to do so. With nvflash or adb almost any tablet can be recovered.
One last thing to look out for, how internal storage is handled. Some roms use internal as emmc (like the Dinc), while others mount as sdcard. CW doesn't handle this switch gracefully. You can mount usb storage in advanced menu and move the recovery files over if needed.
While dharr18 is mostly correct there are a few ROMs floating around out there that will have trouble with clockworkmod. TwoTapsX and TnT Lite 5.0 (both currently held from distribution by the developer) are based on a UAT build (3991) that require using the stock recovery and bootloader from build 3588+ to install correctly. There is some speculation that this may be the standard going forward.
Thanks KJ, I forgot about those two as I have not loaded them to date.
dharr18 said:
The problem isn't the rom messing with CW, it usually is Rom Manager that will mess with it. Rom Manager usually will want updated, especially with CM installs.
.
Click to expand...
Click to collapse
Yeah, I fell into that trap... really FUBAR'ed my tab until i had to nvflash a full recovery.
dharr18 said:
Thanks KJ, I forgot about those two as I have not loaded them to date.
Click to expand...
Click to collapse
You're welcome. I run TTX regularly (well... in between my attempts to find creative new ways to brick this thing...).
Deacon,
The truth is there ARE some dire consequences. Bricking a G-Tablet is extremely hard,
but you can lose data. If something breaks on your tab and your have loaded a ROM
you do not have a warranty. There are risks involved.
And in my opinion a lot of people try to do too much too fast and too often wind up
in dire straights.
There are stickies on most of the recovery/problematic stuff. Good to read them first.
Rev
the problem isn't with the ROM
I follow roebeet and the tnt lite ROM - VS is updating their boot loader from 1.1 to 1.2 in some of their OTA updates. Mostly the 3588 and the 3991. If you are playing with those or it came installed then it can be a bit of a hassle depending on what ROM you are playing with. I updated my gtab to 3991 and was able to nvflash it back to 3588 and install vegan5.1 and tnt lite up to 4.2 without any issues. Just be sure to read up and be able to complete an nvflash if it gets ugly on you. I really recommend learning a little linux - nvflash is a breeze in there.
Is there any chance one of the devs working on this device can get CWM recovery working for it? I've used CWM exclusively on my OG Droid and Inc 2.... I'm hesitant to use a recovery I'm unfamiliar with on my Inc 4G.
The only recovery available is TWRP. I don't know of anything being worked on through other developers. But trust me on this, TWRP is far superior and easier to use. Just an opinion, but wanted to shed some of your fears. I've used TWRP on several phones and it works extremely well.
Do you know if ROM Manager can be used with TWRP? Or would it even be necessary to install ROM Manager?
Sent from my HTC Incredible 4G
RomManager is designed for CWM. I strongly doubt it will work giving recovery commands that reboot the phone. In fact, judging by the comments left about RomManager lately, I don't think it supports much of anything any more.
Pandalero said:
Do you know if ROM Manager can be used with TWRP? Or would it even be necessary to install ROM Manager?
Sent from my HTC Incredible 4G
Click to expand...
Click to collapse
*Madmoose* said:
RomManager is designed for CWM. I strongly doubt it will work giving recovery commands that reboot the phone. In fact, judging by the comments left about RomManager lately, I don't think it supports much of anything any more.
Click to expand...
Click to collapse
rom manager is usually compatible with other recoveries (4ext comes to mind)
i cant speak from experience w/ twrp though
I think Koush kind of got overwhelmed with Rom Manager tbh. Soo many phones out there now...huge damn undertaking. It's slipped a little in popularity. I've read some posts where people were talking about experiences with him and support. Don't know how true they are as I've never spoke with him and everything posted on the interwebz is the gawd-honest troof. But support for new phones I think is seriously lacking at this point.
Whatever you do though, don't force CWM into your phone through Rom Manager though...you could be without a recovery
*Madmoose* said:
I think Koush kind of got overwhelmed with Rom Manager tbh. Soo many phones out there now...huge damn undertaking. It's slipped a little in popularity. I've read some posts where people were talking about experiences with him and support. Don't know how true they are as I've never spoke with him and everything posted on the interwebz is the gawd-honest troof. But support for new phones I think is seriously lacking at this point.
Whatever you do though, don't force CWM into your phone through Rom Manager though...you could be without a recovery
Click to expand...
Click to collapse
Thanks for the insight. My personal experience with Koush and his products have all been good. I was just wary of flashing something I've never used. My main goal right now is to just root my Inc 4G so I can get free WiFi tether. I'm grandfathered into unlimited data, but that doesn't include WiFi Hotspot. Then I'm going to wait for some CM10.
I will not even consider porting CWM. It is the worst available recovery and rom manager is garbage.
CWM was great on older devices like the original Incredible, but on newer devices, it has invited a lot of problems. You're much better off with TWRP. When the time comes to install custom ROMs on this device, consider using Goo Manager instead of ROM Manager--many developers are now supporting their ROMs on Goo.im and Goo Manager can do everything with TWRP that ROM Manager could do with CWM in terms of flashing.
polarimetric said:
CWM was great on older devices like the original Incredible, but on newer devices, it has invited a lot of problems. You're much better off with TWRP. When the time comes to install custom ROMs on this device, consider using Goo Manager instead of ROM Manager--many developers are now supporting their ROMs on Goo.im and Goo Manager can do everything with TWRP that ROM Manager could do with CWM in terms of flashing.
Click to expand...
Click to collapse
Thanks. I'm gonna flash TWRP tonight.
polarimetric said:
CWM was great on older devices like the original Incredible, but on newer devices, it has invited a lot of problems. You're much better off with TWRP. When the time comes to install custom ROMs on this device, consider using Goo Manager instead of ROM Manager--many developers are now supporting their ROMs on Goo.im and Goo Manager can do everything with TWRP that ROM Manager could do with CWM in terms of flashing.
Click to expand...
Click to collapse
Can you explain why CWM isn't so good and TWRP superior? Im really curious?
I have used both, I had CWM on a few phones but only recently got introduced to TWRP when I needed to put a recovery on a tablet (kindle fire I think...). That being said, the Dinc 4G is the 2nd device I put that recovery on, and I guess it works fine, I mean its done everything expected of it without fail, then again, CWM was pretty reliable as well... soo...
JDMpire said:
Can you explain why CWM isn't so good and TWRP superior? Im really curious?
I have used both, I had CWM on a few phones but only recently got introduced to TWRP when I needed to put a recovery on a tablet (kindle fire I think...). That being said, the Dinc 4G is the 2nd device I put that recovery on, and I guess it works fine, I mean its done everything expected of it without fail, then again, CWM was pretty reliable as well... soo...
Click to expand...
Click to collapse
CWM has been associated with bad blocks, failing to fully wipe device partitions, and disabling charging while the phone is off making the phone remarkably difficult to resurrect if the battery dies, among many other device-specific problems (for example, 5.0.2.0 failing to make a nandroid backup with the ext4 mod flashed on the original Incredible). It's also annoyingly proprietary (ironic, when its primary purpose is flashing open-source ROMs...) in the sense that it ties in specifically with ROM Manager and the two are not very compatible with much of anything else (for example, openrecoveryscript).
TWRP is much more open (which is why apps like Goo Manager are able to support it) and has one really crucial brick-proofing feature that sets it apart: a battery indicator. (Some ports of CWM Touch have battery indicators baked in, but CWM Touch has largely been a porting mess and adoption has been very slow.)
Hi all,
I am about to try to get my phone onto JellyBean, and have read through these two threads:
http://forum.xda-developers.com/showthread.php?t=1238070
http://forum.xda-developers.com/showthread.php?p=53235945
Think I get the drift, but one small question...where/what installs the newer Clockworkmod or TWRP recovery? Are they part of the ROM itself? The threads above make it sound as if they are, and if so, which versions of Jellybean use which recovery software (I can use either, per se, since I have tried both on my Nook Color, but that was easy compared to this install). If they're not, where in the process should they be installed?
Thanks in advance for pointing me in the right direction.
Eric
Yes jellybean wasn't particular about which recovery you could flash from.
Yes the ROM includes the recovery and the kernel.
yes on the fascinate the recovery and kernel are built together, and can only be installed as one item.
This is different from nearly every device.
In my listing of kernel/recoveries, that is why i tried to include which recovery it comes with and the ROM from which it was combined with so you can go back to reference if needed.
The actual functioning of the two recoveries is not different. they both do exactly the same thing just the ui it's different and some prefer one over the other...
Thanks very much...I am now successfully playing around with my 4.2.2 version of Paranoid Android.
Eric
I'm trying really hard to do this without being dopey. I want to get my Galaxy Tab 10.1 P7510 to slim down and speed up, so I want to root and apply a new ROM. This much I'm pretty sure of. I understand that I need to replace the recovery code, which will allow me to replace the stock ROM with a modded ROM. (How am I doing?). I think I need Odin running on my PC to load the new recovery. I understand booting into recovery mode (I think). I've read about putting the new ROM on my device and rebooting into it. I believe I then need to install google apps to get some of the basic stuff (like Play store) back on the device. I assume that is because they are not part of the modded ROMs? But... how the heck does one decide WHICH recovery, WHICH ROM, WHICH gapps and the right versions of each? I'm going around and around. I'm willing to do the research, but I'm not even clear on the high-level process and steps, let alone the details, finer points. I'm a retired app developer (client server, Oracle, Powerbuilder) so I have some idea of what I'm doing. Just some. Thanks in advance if anyone cares to help.
jberthoty said:
I'm trying really hard to do this without being dopey. I want to get my Galaxy Tab 10.1 P7510 to slim down and speed up, so I want to root and apply a new ROM. This much I'm pretty sure of. I understand that I need to replace the recovery code, which will allow me to replace the stock ROM with a modded ROM. (How am I doing?). I think I need Odin running on my PC to load the new recovery. I understand booting into recovery mode (I think). I've read about putting the new ROM on my device and rebooting into it. I believe I then need to install google apps to get some of the basic stuff (like Play store) back on the device. I assume that is because they are not part of the modded ROMs? But... how the heck does one decide WHICH recovery, WHICH ROM, WHICH gapps and the right versions of each? I'm going around and around. I'm willing to do the research, but I'm not even clear on the high-level process and steps, let alone the details, finer points. I'm a retired app developer (client server, Oracle, Powerbuilder) so I have some idea of what I'm doing. Just some. Thanks in advance if anyone cares to help.
Click to expand...
Click to collapse
A custom ROM can be installed via custom recovery or Odin, so you don't really need a custom recovery before installing it, however it is higly advised.
To say it all, you don't even need root to flash a custom recovery. Some custom recovery like CM also come already rooted.
It is because they are not part of the custom ROM, since including gapps source code would take up more space and some other issues. Regarding the fact about which recovery and ROM to choose... the fact that there is a lot of them doesn't mean that they are very different. Some are based on the source code of another and just add little features that one must be looking for in order to be interested. Generally, TWRP and CWM are the ones most documented. With a simple google comparision research you should be able to decide. Custom ROMs are also based on two vastly documentet projrcts: CM and AOSP. Start with the regular ones, try them both, stock with one if you don't need anything else or start looking around among the forks.
However, I started using custom ROMs with an objective: build source code. For this scope, I decided to use CM for it's huge documentation, since I was looking for a kernel that did one particolar thing, but there wasn't one so I did it on my own. Just to say, I don't know how it feels like to be in decisive about what ROM to pick up.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way.
On my Nexus 6, there are several ROMs derived from stock images. In fact, I am running one right now. So I was surprised to find out there don't seem to be any for the Nexus 9. There doesn't even seem to be a recovery flashable .zip of an unmodified stock ROM. Why is this? Is there simply not enough developer interest?
I think lack of developer interest is part of the problem. Even with the N6, there's not much in the way of "stock, rooted" ROMs with no other modifications. It probably stems from how easy it is to flash factory images and root, etc.
On the one hand, I'm fine flashing factory images, but I may not have my PC handy to flash (e.g. I was on vacation when a security update came out a while back). It would be nice if there were a tool like Flashify or a way in recovery to flash factory images without a PC. I, too, miss flashable stock ROMs, but I also don't feel comfortable asking a dev to take time out of their life to create one.
Sent from my Nexus 9 using Tapatalk