I was thinking about switching over to CWM recovery since I've been hearing some bad things about TWRP, but I am not sure how to do this. Could anyone give me a guide or point me in the direction of one?
jguns112 said:
I was thinking about switching over to CWM recovery since I've been hearing some bad things about TWRP, but I am not sure how to do this. Could anyone give me a guide or point me in the direction of one?
Click to expand...
Click to collapse
Not sure what bad you've been hearing about TWRP, but after using both, TWRP is easier, faster, and doesn't create all the blob files. Stick with TWRP
Sent from my SCH-I535 using xda app-developers app
jguns112 said:
I was thinking about switching over to CWM recovery since I've been hearing some bad things about TWRP, but I am not sure how to do this. Could anyone give me a guide or point me in the direction of one?
Click to expand...
Click to collapse
Dont be a silly nancy a stick with TWRP
iSheep... iSheep... Meowww that's Apple VZW GSIII
I just switched from cwm to twrp lolll its much better...
Sent from my SCH-I535 using xda app-developers app
I've just been seeing that TWRP doesn't properly get rid of everything and was leaving traces of previous ROMs or something like that. Maybe this isn't true?
I'm using TWRP at present. In the past I have used a CWM style recovery and am certainly more comfortable with the interface with CWM, but will be giving TWRP a fair chance to win me over.
Just flash cwm like you did twrp. And cwm doesnt create those dup files by default anymore and in the past you could have easily changed it to tar in the options.
c4manceph said:
I'm using TWRP at present. In the past I have used a CWM style recovery and am certainly more comfortable with the interface with CWM, but will be giving TWRP a fair chance to win me over.
Click to expand...
Click to collapse
I'm in the same boat as you. I've used CWM for as far back as I've been modding my android phones, but I recently switched to TWRP (because I thought it would solve a problem I thought I was having; it didn't) and I like it so far. The interface seems much more user-friendly than CWM, so I really have no reason to switch back at this point.
I personally find TWRP to be much better than CWM right now.
I think the layout for twrp is way better. But I have had zero problems with CWM which I have been using for well over a year.
I just see no need to make the switch
sent from that young galaxy s3!
I want to move to TWRP from CWM. The steps are to just go thru the normal install of TWRP?
Is there a way to remove CWM?
Sent from my GT-N8013 using Tapatalk HD
Related
Was gonna give TWRP recovery a try... I am currently using CWM and didn't know if it would be safe to just use the goo app and flash TWRP that way. I have always used CWM and wanted to try something new and just want to be safe when going about it.
Sent from my SCH-I535 using xda app-developers app
I tried it, but I didn't like much. To much switching pages to do things, such as format, erase cashed, and dalvic. But who knows you might just like it.
Sent from my SCH-I535 using xda app-developers app
Yes you can install TWRP any way you like. One recovery will simply overwrite the other. Nothing to worry about.
My only brick
The one time i ever truly bricked a phone after close to 30 times rooting and unlocking boot loaders was with TWRP and this phone. I am talkin complete brick, like qualcom drivers request show up on windows brick, the kind brick that you just throw at a window, because you got no charging light, no vibration, no light what so ever.
Btw i was only flashing a rom
I never touched TWRP after .
Thanks for the input guys..... Gonna stick with CWM for now. Seen a fair amount of negative stuff towards TWRP in the forums and don't want to risk anything.
Sent from my SCH-I535 using xda app-developers app
Been running TWRP since received pre-order device. No problems whatsoever.
prdog1 said:
Been running TWRP since received pre-order device. No problems whatsoever.
Click to expand...
Click to collapse
Seconded.
Used the gooapp to flash twrp and haven't had any problems. In fact I switched over from cwm because while installing liquidsmooth cwm kept giving me error 7. Everything I googled told me it was a problem with my recovery, so switched to twrp and presto
Although watch which version of twrp because I was reading the Cleanrom lite thread and ppl were having issues with the latest twrp at the time of their postings. It was around end of September that they were saying this, I believe.
Sent from my SCH-I535 using xda premium
prdog1 said:
Been running TWRP since received pre-order device. No problems whatsoever.
Click to expand...
Click to collapse
Thirded
prdog1 said:
Been running TWRP since received pre-order device. No problems whatsoever.
Click to expand...
Click to collapse
+1
Sent from my SCH-I535 using xda app-developers app
I used to use cwm and now have been using twrp and have never had a problem. This guy above you can't blame twrp for your brick you don't know if that's what it was. Twrp I like better cause I can move my backup folder and copy it even to another computer. Cwm has the blob folder which you can't see which files belong to which backup so you can't just move one backup you have do do them all
Tap'n
evolishesh said:
I tried it, but I didn't like much. To much switching pages to do things, such as format, erase cashed, and dalvic. But who knows you might just like it.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Don't know what you were looking out but CWM is the one where the wipes/format are on different pages. All wipe options in TWRP are on the wipe page right next to each other. Newest version now released.
Back in the day (droid eris days) there was cwm and twrp and twrp was thought of to cause more issues than anything so it was recommended to use cwm. Now it seems to have changed (at least regarding the gs3). Is this true? IS twrp that much better/stable/safer than cwm? I've never used twrp (have seen videos/screen shots) and it looks alot easier...well user friendly...just curious as to if it is more stable/safer or just as safe as cwm? When it comes to changing the recovery in a phone I view that as updating a bios in your computer...don't do it unless you really really need to (last time I upgraded a bios the power went out the same time....not a good day). Just curious as to fellow flashers opinion on the topic? Seems twrp has been getting alot more updates than cwm as well.
EI
Excessiveidling said:
Back in the day (droid eris days) there was cwm and twrp and twrp was thought of to cause more issues than anything so it was recommended to use cwm. Now it seems to have changed (at least regarding the gs3). Is this true? IS twrp that much better/stable/safer than cwm? I've never used twrp (have seen videos/screen shots) and it looks alot easier...well user friendly...just curious as to if it is more stable/safer or just as safe as cwm? When it comes to changing the recovery in a phone I view that as updating a bios in your computer...don't do it unless you really really need to (last time I upgraded a bios the power went out the same time....not a good day). Just curious as to fellow flashers opinion on the topic? Seems twrp has been getting alot more updates than cwm as well.
EI
Click to expand...
Click to collapse
I only used TWRP, its so much more innovative and easy to use with the touch based interface and i have absolutely no problems with it.
Another another note, probably not the right forum for this thread lol...
Yea I wasn't sure if this was the right forum or not.... But figured recovery deals with development sooooooo...
Sent from my SCH-I535 using xda app-developers app
Excessiveidling said:
Yea I wasn't sure if this was the right forum or not.... But figured recovery deals with development sooooooo...
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You were still in the wrong. Plus, there's already a dedicated TWRP recovery thread in the dev section.
To answer your question, TWRP really is a nice recovery. I usually stay a few versions behind the latest because what works now is good enough for me. I don't think you can go wrong with either TWRP or CWM, but having used CWM for so long I wanted to see what else was out and TWRP didn't disappoint. It's as safe as a custom recovery can be flashing modified software not intended for your phone.
Sent from my SCH-I535 using xda app-developers app
Step 1) From the root of your android device tree:
Code:
mkdir -p .repo/local_manifests
curl http://teamacid.github.com/manifests/sgh-t959v/TWRP/twrp.xml > .repo/local_manifests/twrp.xml
Step 2) Wait for noiphonehere to update his tree to include my commit, the sync your device tree to match his
OR (for the impatient)
Cherry pick my commit yourself:
https://github.com/fbis251/android_...mmit/fe504f4d7602432d5de97585698af963aafdd0ab
heard that idevice is kinda excited when seeing this haha
Nice.
I might add this.
Sent from Aries within the 1st Galaxy
Is it more of a personal preference or is TWRP better then CWM?
Edit .... is this simply to allow users to switch to TWRP if I build with CWM?
Have you guys heard of 4ext touch recovery?
Dwack said:
Is it more of a personal preference or is TWRP better then CWM?
Edit .... is this simply to allow users to switch to TWRP if I build with CWM?
Click to expand...
Click to collapse
TWRP includes a file manager in recovery, so if something goes horribly wrong and you need to replace a required init.d script file, you can actually do it without needing a computer for your ADB.
It also looks pretty. And is touch friendly. Friendly touch. Good touch. Mhmm.
But it's the file manager that makes me choose TWRP over CWM any chance I get.
Cooptx said:
Have you guys heard of 4ext touch recovery?
Click to expand...
Click to collapse
According to what its developer says at http://www.4ext.net/status_update.php we're unlikely to ever be supported.
Unlikely:
Older Samsung devices like:
Samsung Galaxy SII
Samsung Galaxy Note
Click to expand...
Click to collapse
Maybe we should focus on recovery options that actually work for our phone?
I was asking if you have ever heard of it. I wasn't asking for it
Theraze said:
TWRP includes a file manager in recovery, so if something goes horribly wrong and you need to replace a required init.d script file, you can actually do it without needing a computer for your ADB.
It also looks pretty. And is touch friendly. Friendly touch. Good touch. Mhmm.
But it's the file manager that makes me choose TWRP over CWM any chance I get.
According to what its developer says at http://www.4ext.net/status_update.php we're unlikely to ever be supported.Maybe we should focus on recovery options that actually work for our phone?
Click to expand...
Click to collapse
Well....
Nexus S has the same hardware we have....
http://forum.xda-developers.com/showthread.php?t=1646108
For all your file managing needs
i've used it. it's nice.
TWRP will be pretty awesome
I tried CWR Touch on my friends SGS2 and its a bit buggy. CWR is ok but TWRP makes it easier and has a file manager too!
It already is. If things go to plan tonight I might have a present for you guys .
@FBis251: Yo man, , sr that I thought u asked how was the TWRP kernel flashing man so I told u it was normal but just after flashing a ROM via TWRP, I knew what u asked It couldn't flash properly (or mayb just my compile got this not yours ^^)
daothanhduy1996 said:
@FBis251: Yo man, , sr that I thought u asked how was the TWRP kernel flashing man so I told u it was normal but just after flashing a ROM via TWRP, I knew what u asked It couldn't flash properly (or mayb just my compile got this not yours ^^)
Click to expand...
Click to collapse
After using your kernel, TWRP wouldn't backup or flash anything. Gonna go back to stock and work my way back up because I can't flash anything with CWM in it.
Sent from my SGH-T959V using xda app-developers app
Whoa weird. I've been able to restore/backup properly on mine. I need to mess around with the cm10.1 based version of it since all of my testing has been on team acid's aries cm9.
The JB kernel might be adding problems to TWRP, but on ICS it's still working fine, even flashing noiphone's cm10.1 build worked from TWRP.
Yeah I ran in to this last night trying to back and flash a new ROM. I could restore from an old back up, it was fine until it reached the recovery part then it freaked you out.
I had to one click.
Sent from my SGH-T959V using xda premium
johnadelic said:
Yeah I ran in to this last night trying to back and flash a new ROM. I could restore from an old back up, it was fine until it reached the recovery part then it freaked you out.
I had to one click.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Okay I know exactly what you mean and was able to replicate the issue. I'll try to see what's going on behind the scenes for this since a boot.img restore should only take a second or two when you recover from a backup.
Something about color/overlay image could not be applied (something like that) in adb shell adb logcat when u go into recovery with twrp.
Sent from my SGH-T959V using Tapatalk 2
Has anyone compiled a flash able yet?....just curious.
From my T959W running Illusion
What is the best way to install CWM on my TF300T, I am on the 4.2 bootloader, and I tried to put the CORRECT JB 4.2 version of TWRP 2.5.0 and it is like a split screen and will not function. Some time before that it asked for a password when I booted the recovery. I just want to start fresh with Clockwork Mod I guess.
Please point me in the correct direction.
Thank you
ScottBroker said:
What is the best way to install CWM on my TF300T, I am on the 4.2 bootloader, and I tried to put the CORRECT JB 4.2 version of TWRP 2.5.0 and it is like a split screen and will not function. Some time before that it asked for a password when I booted the recovery. I just want to start fresh with Clockwork Mod I guess.
Please point me in the correct direction.
Thank you
Click to expand...
Click to collapse
Not to be a douche but use the search function. And use twrp. Cwm is too buggy on the tf300. Its very easy for it to bug out and brick your pad.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mhays705 said:
Not to be a douche but use the search function. And use twrp. Cwm is too buggy on the tf300. Its very easy for it to bug out and brick your pad.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
well you are being a DB!
Do you not think I would search , too many posts with too many options.
TY for nothing. TWRP on TF3000T is very buggy btw.
ScottBroker said:
well you are being a DB!
Do you not think I would search , too many posts with too many options.
TY for nothing. TWRP on TF3000T is very buggy btw.
Click to expand...
Click to collapse
If you searched you would have seen all your questions are answered in the stickies. Also you would have seen twrp is recommended over cwm due to cwm bricking devices. I'm sure you would prefer that not to happen.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If anyone has some useful information, please let me know.
Thanks
ScottBroker said:
If anyone has some useful information, please let me know.
Thanks
Click to expand...
Click to collapse
First and foremost learn how to search. Its a damn stickied topic. Here is what your looking for took less than a minute to search. http://forum.xda-developers.com/showthread.php?t=2187982
If you learned to read you wouldn't have a double screened twrp.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have tried that and still get a split screen, that is why I want to just flash CWM.
I have looked at that thread as well..
ScottBroker said:
I have tried that and still get a split screen, that is why I want to just flash CWM.
I have looked at that thread as well..
Click to expand...
Click to collapse
Update to the most recent boot loader. I'm trying to tell you. You have to use twrp. Cwm bricks the tf300t while flashing ROMs. Everyone advises not to use it. I don't even think there's a guide here for it since its too much of a liability. If your getting a split screen you are doing something wrong. Reading everything and doing everything exactly right is the name of the game here. The tf300 is way to easy to brick. If your having problems just installing a custom recovery your best to just stay away from flashing on this device. You have to pay attention to boot loader version and firmware version or you are going to get errors. Your lucky you haven't hard bricked yet.
I know what I'm talking about. I didn't just fall off the turnip truck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mhays705 said:
Update to the most recent boot loader. I'm trying to tell you. You have to use twrp. Cwm bricks the tf300t while flashing ROMs. Everyone advises not to use it. I don't even think there's a guide here for it since its too much of a liability. If your getting a split screen you are doing something wrong. Reading everything and doing everything exactly right is the name of the game here. The tf300 is way to easy to brick. If your having problems just installing a custom recovery your best to just stay away from flashing on this device. You have to pay attention to boot loader version and firmware version or you are going to get errors. Your lucky you haven't hard bricked yet.
I know what I'm talking about. I didn't just fall off the turnip truck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the advise, but as you can see, I have almost 3 times the thanks than you have posts. But anyway, I have been flashing for years, I have had every Iphone, and every Galaxy and have not had problems like with the tablet. I like TWRP, I have the latest bootloader, I am on 4.2.....
Maybe I will just return to stock and start fresh again...
Thanks anyway
ScottBroker said:
Thanks for the advise, but as you can see, I have almost 3 times the thanks than you have posts. But anyway, I have been flashing for years, I have had every Iphone, and every Galaxy and have not had problems like with the tablet. I like TWRP, I have the latest bootloader, I am on 4.2.....
Maybe I will just return to stock and start fresh again...
Thanks anyway
Click to expand...
Click to collapse
FYI, I went back to stock, and reflashed, and now with your helpful guide, I am back on TWRP.
TY
ScottBroker said:
FYI, I went back to stock, and reflashed, and now with your helpful guide, I am back on TWRP.
TY
Click to expand...
Click to collapse
This is defiantly one of the most sensitive device to do everything on. Asus wasn't to friendly. Its like they want you to brick. And my bad about the rudeness extreme lack of sleep has made me very irritable.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Indeed flashing cwm is another way to brick the TF300. Lucky you didn't flash it.
The problem is that the latest bootloader changes the partition table on the TF300 - it makes /system larger in order to accommodate the larger Asus ROM. The issue is most of the legacy recoveries including the non 4.2 twrp and cwm don't understand this and thus the device becomes bricked as the partition table is now messed up.
sbdags said:
Indeed flashing cwm is another way to brick the TF300. Lucky you didn't flash it.
The problem is that the latest bootloader changes the partition table on the TF300 - it makes /system larger in order to accommodate the larger Asus ROM. The issue is most of the legacy recoveries including the non 4.2 twrp and cwm don't understand this and thus the device becomes bricked as the partition table is now messed up.
Click to expand...
Click to collapse
Gotta love sbdags knowledge and amazing rom
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Anyone?
Sent from my SCH-I535 using xda premium
Never mind...
Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium