Develop Bugs

Install CWM on new AT&T S3

Why does this never work the way its supposed to for me??
Anyway, so I just got my S3 and I hate the stock ROM already so I want to go to CM (9 maybe, 10 if it works well). I'm right now just trying to get Clockwork recovery installed and working and seem to be failing miserably. At first it seemed to be going ok, I downloaded Odin 3.04 and a recovery TAR that was on the Android Authority guide for the AT&T S3. I ran the install no problems, and booted into recovery without issue. I then tried installing CM10 and it gave and Status 7 assert failure.
After a lot of digging I finally found some people saying that it was because of an incorrect version of CWM, so I dug around till I found a 6.0.1.0 tar that says its for my phone. I install that and now I can't get into recovery at all. It will still boot into the stock rom but that's it. I saw some suggestions saying that unchecking auto reboot, and f. reset time would fix this so I did that and still nothing. I can't get into recovery at all. Is there a definitive (as in this still works) guide out there somewhere??

forwardbias said:
Why does this never work the way its supposed to for me??
Anyway, so I just got my S3 and I hate the stock ROM already so I want to go to CM (9 maybe, 10 if it works well). I'm right now just trying to get Clockwork recovery installed and working and seem to be failing miserably. At first it seemed to be going ok, I downloaded Odin 3.04 and a recovery TAR that was on the Android Authority guide for the AT&T S3. I ran the install no problems, and booted into recovery without issue. I then tried installing CM10 and it gave and Status 7 assert failure.
After a lot of digging I finally found some people saying that it was because of an incorrect version of CWM, so I dug around till I found a 6.0.1.0 tar that says its for my phone. I install that and now I can't get into recovery at all. It will still boot into the stock rom but that's it. I saw some suggestions saying that unchecking auto reboot, and f. reset time would fix this so I did that and still nothing. I can't get into recovery at all. Is there a definitive (as in this still works) guide out there somewhere??
Click to expand...
Click to collapse
Ok so I found some CWM tars that they they're v.6+ that I can get installed (at least I assume so since Odin says it worked) but when I get in there the version listed at the top is 5.5.0.4, should this number not match? I haven't even gotten around to trying to get it to install CM10 yet.

I used rom manager to flash its recovery. No problems what so ever.
Sent from my SGH-I747 using xda premium

defnow said:
I used rom manager to flash its recovery. No problems what so ever.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
By Rom Manager you are talking about the App you use from within the OS? So would I need root for this?

https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
Installed ROM manager....opened it and click install recovery. Done. Yes, you have to be rooted to use that app.
Sent from my SGH-I747 using xda premium

defnow said:
Installed ROM manager....opened it and click install recovery. Done. Yes, you have to be rooted to use that app.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Awesome suggestion! Worked perfectly thank you!!

How are you guys getting TWRP to install?

Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium

mr1080p said:
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".

SysAdmNj said:
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
Click to expand...
Click to collapse
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium

mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
U have to make sure u are rooted first.
Sent from the TermiNOTEr!

mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?

SysAdmNj said:
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
Click to expand...
Click to collapse
Yes. CWM and ported ROM. Everything works well I just want TWRP. But I guess I'll do with CWM. If it aint broke then why fix it. It works I guess. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium

Check your build prop for device name. Maybe its not correct because of the Rom you're on. Whats the error you're getting?

Did you ever get TWRP on your phone?

I've had goofy issues with TWRP but much prefer it to CWM. Originally rooted using CWM and SuperSu and switched to TWRP when I flashed CleanRom several times via Romtoolbox pro I've flashed updated Twrp it said it was successful but when it rebooted was soft bricked! Had to use Odin and original CWM to get back in and re-install everything (nandroids were twrp backups) found file downloaded to sdcard that worked fine! Odd...
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==

wargear said:
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
Click to expand...
Click to collapse
If by "installed" you are referring to the recovery program itself (and not your backups), you can only have one recovery 'installed' at one time as there is only 1 "Recovery" partition on the device (/dev/block/mmcblk0p9). So if you want to install CWM instead of your current TWRP (or visa-versa), either flash the appropriate new recovery zip via your current recovery... or Odin3 flash your desired new recovery tar. Either way, it will write to the same recovery partition. If you are referring to your backups... these are stored in the designated path you selected (either internal sd or external sd)... in the TWRP/BACKUPS folder. In that folder, you will have a device id #... in that folder are your backups.

Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.

wargear said:
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
Click to expand...
Click to collapse
Which version of Odin3 are you using? When I used Odin3 v1.85 I would get the "PASSED" but with Odin3 v3.07, I also only got "RESET" (on an WindowsXP box)... but both flashed it correctly (and auto rebooted after flash)

Galaxy Note2 TOOLKIT V3.0.0 ATT]
I tried the [Galaxy Note2 TOOLKIT V3.0.0 ATT] http://forum.xda-developers.com/showthread.php?t=2052779 out of curiosity sake. Worked for me installing TWRP 2.3.2.3 without a hitch. Great tool from what I can see, and that's just one of it's many features. Great for simplifying things for new Android users just entering the customizing scene and regulars alike. Big ups to mskip for making this available. I can foresee myself grabbing the donate version here real soon.
And to get yourself SIM unlocked, get yourself back to 4.1.1 and give this a whirl.http://forum.xda-developers.com/showthread.php?t=2014982 Bought my device used, was supposedly unlocked, wasn't. Even came with an unlock code that the previous owner purchased. Firstly it's a no go on 4.1.2, secondly still didn't work when I dropped back to 4.1.1. But this http://forum.xda-developers.com/showthread.php?t=2014982 will set you free. Big thanks owl74 for posting. Once again XDA forums saves my hair from being pulled out.

At a loss with cwm

Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay

maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.

pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..

Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951

pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks

Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways

Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app

RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?

Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump

what version of CWM are you currently running?

you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.

xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7

Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app

CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).

zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app

Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.

Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app

CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app

CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files

RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!

Root Access Possibly Lost Fix Root?

I have my N7 on bone stock, rooted with superSU 1.60 installed. I flashed the .zip made by Chainfire, and no matter the recovery CWM non-touch , CWM, or TWRP after making a backup , I hit reboot system, and I get this message every time.
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
I've selecting option 1 multiple times and I still get the same message after a backup ,and before rebooting!! Root access works fine on all my apps and everything else I'm just curious as to why I'm seeing this via any recovery thanks. I'm sure its silly and an easy fix.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Try v1.55
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip

Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app

I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app

Jewveeski said:
Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've done this, i disable auto-update, flashed the v1.55 in CWM and rebooted. Now i cant use SuperSU anymore? tells me i have to update binaries. And i know that if i do the "root access possbibly lost" error comes again? any solutions?

In settings there is an option for reinstall as seen in the pic below click that then reboot your device , then reboot to recovery flash version v1.55 and make sure you still have the auto update feature in the play store unchecked. See if that works.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Same issue on a Galaxy Nexus running 4.3 stock rooted... SU requires an update and then the recovery thinks root has been lost (this is not actually the case)... any ideas?

lost root and twrp
so i first discovered i lost root when it said no binary found then when i was going into twrp to reflash the zip all i get is a dead android on its back with a red triangle hovering over it. Went back into adb and flash recovery twrp.img and it says successful but i still get the same thing. any one know the correct thread to point me to? ive looked but cant find this problem. my device boots fine and i can get to the boot loader just not recovery.

Same thing happens with my Nexus 4, I always hit No because it says root may have been lost even if I just enter CWM without flashing any rom or doing any action but rebooting to system

Jewveeski said:
I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same message on my SGS4 with stock Android 4.3 and SuperSU v1.80.

Same message with my GT-i9300, CWM 6.0.4.4 Touch (i've tried also with CWM 6.0.4.3 NO Touch) and SuperSU v.1.80

I have the same problem too on my Galaxy Nexus GSM 4.3 build JWR66Y with SuperSu by Chainfire v1.8.6 and CWM Touch Recovery v6.0.4.3
Is there a solution?
Thanks in advance
Happy Holidays and Merry Christmas

Same message, S4 mini GT-I9195 4.3 su 1.86

Same message here...
I am running CM 10.2 with CWM Touch and SuperSUv1.86
Is this a big problem?
I think CWM should work just fine regardless of this message right?
If anyone has truly found a "recent" fix please let us know.
Oh i tried reinstalling CWM Touch and that did not fix the problem..
Thank you all for your time and assistance.

Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195

kamikaze702k said:
Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195
Click to expand...
Click to collapse
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow

droidshadow said:
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow
Click to expand...
Click to collapse
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195

maybe we should switch to TWRP?...
kamikaze702k said:
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195
Click to expand...
Click to collapse
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow

droidshadow said:
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow
Click to expand...
Click to collapse
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195

TWRP is the way to go!
kamikaze702k said:
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195
Click to expand...
Click to collapse
So i just switched my Verizon SGS3 (d2vzw) from CWM Touch to TWRP Touch 2.6.31 and i go to error message/warning about the SU binary being corrupted. This seems to be just an isolated incident with CWM and Android ROM's running 4.3+
With all of the work I have been doing with my Nexus 7 FLO + TWRP Recovery I decided to go ahead and switch my phone to TWRP. It was kind of hard to switch because I started out with CWM but I have just quickly become such a fan of TWRP.
If you don't want to wait for CWM to fix this issue which i am sure they will in their next update try out TWRP i think you will like it!
If you want an easy way to install TWRP recovery manager use the app "GooManager" from the Google Play store and use the your menu button on your phone and choose the open install open recovery script.
Or you could just as easily download the recovery image file from the official TWRP website and flash it with the app flashify.
Don't you just love technology!?
-droidshadow

(Root) Can someone point me in the right direction...Please!!

I am trying to root my sons Note 2 and I am not sure of what the newest root method is...or for that matter, which method still works! I have been searching on here and youtube and I don't know which is the correct method...The Note is fully updated to 4.4.2.

cmdauria said:
I am trying to root my sons Note 2 and I am not sure of what the newest root method is...or for that matter, which method still works! I have been searching on here and youtube and I don't know which is the correct method...The Note is fully updated to 4.4.2.
Click to expand...
Click to collapse
My suggestion is not to worry about root. Rooting is only needed if you stick with pure stock ROM which sucks.
If I were you these are the steps I would take. Download custom recovery (philz 6.07.9) and use Odin to flash it. Then download custom ROM and flash that in custom recovery. Custom ROMs come rooted 99% of the time.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
My suggestion is not to worry about root. Rooting is only needed if you stick with pure stock ROM which sucks.
If I were you these are the steps I would take. Download custom recovery (philz 6.07.9) and use Odin to flash it. Then download custom ROM and flash that in custom recovery. Custom ROMs come rooted 99% of the time.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will give that a try...Thank You!

If you have any questions just ask and I will do my best to help you out.
Sent from my SPH-L900 using XDA Premium 4 mobile app

I am giving it a go now... I am very familiar with Twrp... Will that recovery ok?

jlmancuso said:
If you have any questions just ask and I will do my best to help you out.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I do have a quick question...
1) I have enabled usb debugging...installed odin and downloaded the correct recovery for the phone.
2) I reboot the phone and get to download mode.
3) Plug in the cable and it gets recognized in Odin
4) click PDA button and navigate to Tar file
5) Once I hit start it goes through the whole process and says PASS
6) When I boot into recovery...using volume up, home key and power it brings me back into stock recovery
Do you have any idea what I am missing?

After you flash recovery does the device reboot automatically? If so recovery is most likely being overwritten. In Odin turn off auto reboot option. Once flash is finished disconnect and pull battery. While inserting battery press and hold power, vol +, home. You should now boot into recovery.
You stated you wanted to use twrp recovery which is okay as long as it is 2.8.0 or newer. Older versions of twrp don't work for newer ROMs.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
After you flash recovery does the device reboot automatically? If so recovery is most likely being overwritten. In Odin turn off auto reboot option. Once flash is finished disconnect and pull battery. While inserting battery press and hold power, vol +, home. You should now boot into recovery.
You stated you wanted to use twrp recovery which is okay as long as it is 2.8.0 or newer. Older versions of twrp don't work for newer ROMs.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That did it! I went ahead and installed Philz...Thank You!

cmdauria said:
That did it! I went ahead and installed Philz...Thank You!
Click to expand...
Click to collapse
Great. While philz is different from twrp it is the best recovery for our device. Hope your son enjoys this. Even though it is not a new device it is a real nice one and I will have it till mine dies so there will be at least on person pumping out new ROMs for this device.
Sent from my SPH-L900 using XDA Premium 4 mobile app

I am about to root my note 2 but wonder how reinstall my previous recovery files? Say I no longer want the custom ROM do I simply flash and reinstall the back up or does the procedure differ?

rerooting
i'm looking for the same thing myself. my 4.4.2 got the OTA update. and root is now gone.
i'm not interested in custom roms. i just want the root back. with my hotspot back.
so, how would i reacheive root????? with the update.
last time i spent basically a whole week just to get this accomplished. seems as the note2 phone is dieing off when it comes to this matter.
i'm not sure on the recover mode. when i do the vol + home + power. it goes into a screen that has 2 paragraphs of red lettering. and the menu items are blue lettering. with black background screen and the droid with red triangle.
what recovery is that?

snowwy66 said:
what recovery is that?
Click to expand...
Click to collapse
Without actually seeing it, I can't be 100% sure, but it does sound like you are describing the stock recovery.

DJ_Barcode said:
Without actually seeing it, I can't be 100% sure, but it does sound like you are describing the stock recovery.
Click to expand...
Click to collapse
it had the purple back screen before. so how can i get the recovery and root back.
i really don't want to spend another week trying to figure it out again but if i have to go backwards to the original 4.4.2. how would i turn off the update.
i basically only use this phone as my trucker gps. so it's not like i have a lot of stuff to redownload.

snowwy66 said:
it had the purple back screen before. so how can i get the recovery and root back.
i really don't want to spend another week trying to figure it out again but if i have to go backwards to the original 4.4.2. how would i turn off the update.
i basically only use this phone as my trucker gps. so it's not like i have a lot of stuff to redownload.
Click to expand...
Click to collapse
I guess my first question would be, why do you need a custom recovery? You're not flashing custom ROMs, so the only real benefit you'd get from a custom recovery is the ability to make nandroid backups.
The "purple back screen" recovery is Philz. The overwhelming majority of us use Philz v6.07.09 to flash ROMs and the like.
As for re-rooting, be sure to do this before you install your custom recovery (if you do indeed even need one, and I mentioned before). Many of the auto-root applications install the stock recovery as part of the process. I'd recommend ChainFire Auto-Root, but you may also try KingoRoot.

DJ_Barcode said:
I guess my first question would be, why do you need a custom recovery? You're not flashing custom ROMs, so the only real benefit you'd get from a custom recovery is the ability to make nandroid backups.
The "purple back screen" recovery is Philz. The overwhelming majority of us use Philz v6.07.09 to flash ROMs and the like.
As for re-rooting, be sure to do this before you install your custom recovery (if you do indeed even need one, and I mentioned before). Many of the auto-root applications install the stock recovery as part of the process. I'd recommend ChainFire Auto-Root, but you may also try KingoRoot.
Click to expand...
Click to collapse
i don't, if i don't have to. all i want is root.
thanks, will give those a shot when i get home tonight.

thank you barcode. the cf autoroot was just the trick i needed. we have root again.
now if i can just find a way to turn off the auto update for the rom.