Related
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
aperture said:
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
Click to expand...
Click to collapse
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
riverboat2001 said:
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
Click to expand...
Click to collapse
As long as you are using cm, I don't think it will be a problem. I will never go back to official. The problem stems from an issue with the stock recovery from Samsung. So in short, the devs are aware of the issue, but Samsung doesn't seem to care. As long as you are running the current cwm, and the dev isn't an idiot, you shouldn't have a problem. (No offense aorth and locerra, I know you're aware)
Sent from my Galaxy Tab 7 Plus
riverboat2001 said:
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
Click to expand...
Click to collapse
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
wingie6200 said:
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
Click to expand...
Click to collapse
Wow, thanks so much for taking the time to offer your advice.
I only have myself to blame for getting into this pickle! After Flashing so many different ROM's on loads of devices i just got a bit blaiz'e
Last night i did a wipe and factory reset through CWM and it all went well, so my question is, giving that i know i'm at risk, i can see three options,which is the "safest"
1/ Put tab away and don't use it until Samsung release a fix we can use
2/ Keep using the tab, but have that worrying niggle in the back of my mind
3/ Follow the post above and carry out the suggested procedure outlined above? (is it 1000% safe?
Can i assume that if i go as far as recovery mode via the ICS version to see the "recovery 3e" but don't wipe/factory reset i'm safe?
And consequently if i DON'T see that i would be safe to go ahead?
I do feel as if I'm sitting on a time-bomb here
(years ago i would have spent weeks messing around with this sort of thing, but as a middle aged housewife thats always on the go, i don't have the time, I just like to get my stuff working fast and bloatware free and i'm happy!)
Once again thanks for your input.
lol cant guarantee the 1000% safe part (since the offending code is in part coming from samsung) but people are aware of it / working to fix it and all non stock stuff is most probably safe. the CWM 6.0.1.0 definitely is, just used it myself.
and these things are kinda random (if all posts are to be believed) so i would just use the tab normally and worry about it much.. reports also say that samsung does repair these bricked tabs under warranty in case the unthinkable does happen.
and its not a time bomb :laugh:! (although there would probably be an app for that somewhere..)
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
ringnutz said:
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Kuniokun said:
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Click to expand...
Click to collapse
Yeah, I did.. happened the first time
Sent from my myTouch 4g via Tapatalk
Brickbug is caused by ****ty flashing firmware on some of our devices.
No danger with cwm 6.0.1.0 from aorth. We r safe!
Sent from my GT-P6200 using xda app-developers app
There are a bunch of threads asking about the differences between CWM and TWRP, but I have a question that I think is more specific and I have not seen answered.
Is there any reason besides personal preference for using one over the other?
In most ROM installation guides and such they mention CWM. But I personally like using TWRP better. Does it actually matter? Is there something that I won't be able to do in TWRP that CWM does? So fare, it seems like they do the same thing.
There is nothing different as far as functionality, aside from being able to flash more than one package at a time and the ability to wipe cache and dalvik cache right after flashing a package. (Which I don't recommend doing, it might throw you into a boot loop upon rebooting) only wiping the regular cache is recommended right after flashing packages. Wiping dalvik is usually performed *before* you flash a package.
So, to answer your question... it's pretty much (but not all) cosmetic differences.. plus, the added ease of access features.
But when TWRP is compared to an outdated recovery system such as clock work mod, then yeah it seems like light years of differences. Yes I said it, CWM IS OUTDATED.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
_Zero said:
But when TWRP is compared to an outdated recovery system such as clock work mod, then yeah it seems like light years of differences. Yes I said it, CWM IS OUTDATED.
Click to expand...
Click to collapse
You can say anything you want, but that doesn't make it true. That outdated recovery is the only supported recovery for a lot of ROMs.
aycockonxion said:
You can say anything you want, but that doesn't make it true. That outdated recovery is the only supported recovery for a lot of ROMs.
Click to expand...
Click to collapse
Supported by whom lol twrp flashes everything cwm will to go as far as to say outdated is too far yes but to say twrp won't do it is just ridiculous this is why best threads are dumb
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Thanks
aycockonxion said:
You can say anything you want, but that doesn't make it true. That outdated recovery is the only supported recovery for a lot of ROMs.
Click to expand...
Click to collapse
This is the heart of my question. Do I need CWM for specific ROM's? And if so, why? You seem to suggest so.
Illnevertell said:
Supported by whom lol twrp flashes everything cwm will to go as far as to say outdated is too far yes but to say twrp won't do it is just ridiculous this is why best threads are dumb
Click to expand...
Click to collapse
But then here the suggestion is that it is not so.
Also, you state exactly why I didn't word this as a best thread. Because I also think those are dumb. They just get people spouting their personal opinions and using that as proof that one is better than the other.
I don't care which one people feel is better, I simply want to know whether there is anything I can't do with one (mainly TWRP) versus the other.
I would have to accept the responses to this thread as saying no, there isn't anything (important) that I can't do with one versus the other. There may be conveniences in one versus the other (like multiple zip installs at once in TWRP), but no show stoppers.
Thanks for your responses.
_Zero said:
There is nothing different as far as functionality, aside from being able to flash more than one package at a time and the ability to wipe cache and dalvik cache right after flashing a package. (Which I don't recommend doing, it might throw you into a boot loop upon rebooting) only wiping the regular cache is recommended right after flashing packages. Wiping dalvik is usually performed *before* you flash a package.
So, to answer your question... it's pretty much (but not all) cosmetic differences.. plus, the added ease of access features.
But when TWRP is compared to an outdated recovery system such as clock work mod, then yeah it seems like light years of differences. Yes I said it, CWM IS OUTDATED.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
sk8erwitskil's CWM touch is FAR from outdated (last updated 9/17/12). I personally prefer it to TWRP, but TWRP is great too.
You really can't go wrong with either one. Give each a shot and see what you like best.. it's a better route than asking some of the *cough* -opinionated- *cough* people around here.
.
Locoman_ said:
sk8erwitskil's CWM touch is FAR from outdated (last updated 9/17/12). I personally prefer it to TWRP, but TWRP is great too.
You really can't go wrong with either one. Give each a shot and see what you like best.. it's a better route than asking some of the *cough* -opinionated- *cough* people around here.
.
Click to expand...
Click to collapse
That's what I'm saying both work its all preference
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Locoman_ said:
sk8erwitskil's CWM touch is FAR from outdated (last updated 9/17/12). I personally prefer it to TWRP, but TWRP is great too.
You really can't go wrong with either one. Give each a shot and see what you like best.. it's a better route than asking some of the *cough* -opinionated- *cough* people around here.
Click to expand...
Click to collapse
This. You can't go wrong with sk8er's CWM Touch or TWRP. The only recovery you should stay away from is non-touch CWM. The older versions of button-mashing CWM have a history of doing bad things to Skyrockets.
If a ROM requires one recovery or another, the dev will specify as much. The dev may also suggest a certain recovery, even if it will work on the other. Lots of people like CWM, and lots of others like TWRP. Changing recoveries is not hard at all, so go ahead and try both. Get a feel for which you like more. Nothing to lose by trying them both out.
Kind of funny to see that there are recovery zombies out there. ROM zombies we all knew about, but recovery zombies? :laugh:
_Zero said:
There is nothing different as far as functionality, aside from being able to flash more than one package at a time and the ability to wipe cache and dalvik cache right after flashing a package. (Which I don't recommend doing, it might throw you into a boot loop upon rebooting) only wiping the regular cache is recommended right after flashing packages. Wiping dalvik is usually performed *before* you flash a package.
So, to answer your question... it's pretty much (but not all) cosmetic differences.. plus, the added ease of access features.
But when TWRP is compared to an outdated recovery system such as clock work mod, then yeah it seems like light years of differences. Yes I said it, CWM IS OUTDATED.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I have a Touchpad and a Skyrocket and I've always just installed the updates then wiped cache and dalvik. Are you saying that's not what you should be doing with CM9/CM10?
I personally like CWM Touch over TWRP as well.
But at the same does it really matter when it's a 5sec flash to switch between either one?
copene said:
I have a Touchpad and a Skyrocket and I've always just installed the updates then wiped cache and dalvik. Are you saying that's not what you should be doing with CM9/CM10?
Click to expand...
Click to collapse
Wiping dalvik will not brick you. I always wipe cache and dalvik 3 times before an update and one time after. Never had a bootloop caused by anything other than stupidity (forgot to wipe cache/dalvik before flashing 3 updates in a row, oops).
sb0 said:
But at the same does it really matter when it's a 5sec flash to switch between either one?
Click to expand...
Click to collapse
This. So much of this.
^^^ ??
sb0 said:
^^^ ??
Click to expand...
Click to collapse
I'm agreeing with you wholeheartedly.
Yea I just flashed twrp couple days ago. I will stick w cwm where I am more comfortable... at least until more justifiable reason(s) to switch.
Ppl say its outdated but u can also see this as a more widely tested product too (been around longer... more ppl are using, etc.).
Sent from my SAMSUNG-SGH-I727 using xda premium
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.
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
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