yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
If you guys need something pulled from the n5, let me know. I have it and I'm on this thread quite frequently.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Ok - for reference - got this deep sleeping again by force stopping chrome, and deleting all data, and rebooting.

I then had a wakelock on RILJ - so turned off Location Services. Turning it on again after was enough to break the wake lock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PhillyFlyer:
Yeah - what you just did there...is called an opinion. Battery/performance abilities vary from device to device. Flashing kernels is always done at the discretion of the user and to be honest, I am getting different results/improved battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ariesdroid:
Not disagreeing with you at all...and that's obviously my opinion or i wouldn't have typed it... o_O

Just saying though, i was able to get 8 hours+ with 7 1/2 hours screen time on my stock battery with the regular stock kernel, what kind of screen time are you getting with KT?? just curious....Cause i know even on 4.3/4.3.1 most people have a hard time getting 7 hours of screen time on 1 charge...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
I have tried to ROM on my Rogers SGH-i747m, using I747MUMLJ1 modem (latest one that doesn't have garbled call display with Rogers, see end of post for more).

I followed the instructions in the OP, i had some succes with it, it did boot, i did successfully go thru the setup process, download my apps.

However i had one (pretty big) issue: My signal would drop every 2s and come back after about 2s, Making data usage very unstable. Whenever i could make a call, the signal would stay and i can talk for as long as i want. But i had to synchronise my push of the call button with when the signal bars are showing up.

I don't know if it'll be of any help, but im including a catlog.

By the way, i'm not asking for support, just putting this out there if it can be of any help to anyone. I knew before trying the rom that some stuff was gonna broken :)

References:

Modem garbled call display : http://xdaforums.com/showpost.php?p=42198728&postcount=539
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Anyone been getting FC's on the GAPPS in the OP with the camera fix flashed? I don't get it all the time, just randomly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
I use I747MVLDMF1 on FIDO which is rogers network.. Works fine. your modem is from Oct 12, looks very old. Maybe try and update your bootloaders as well.

My data would drop the same way as I mentioned in a post a page back, but only after flashing 11/17 ktkernel.

Heres the catlog, I couldn't get a boot log of the data drop but the one you supplied looks about the same.

https://docs.google.com/file/d/0B1ql7ydolU52SHlzWkFzSzE1YkE/edit

I'll upload a new log with the 11/17 ktkernel method. Maybe it will be of use to someone.

Maybe the issues are related to our CND modems?

Also, look at this.. I feel like there's still bugs in the Rogers network that still need to be ironed out. http://globalnews.ca/news/893513/rogers-cell-service-down-in-parts-of-canada/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
I was having boot problems after flashing it. I cleared dalvik, and cache. Booted fine after that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
I'll try I747MVLDMF1 on CM 10.2 M1 and make sure my Call Display still works. Once i'm done with that, ill try again and report back :)

But yeah, our Canadian modems are proving to be a PITA so far...

As for current Rogers status, i had perfect signal before and perfect after. I doubt the 45mninutes / 1 hour i had 4.4 was precisely during outage :) hehe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
That was just a one night outage over a month ago. No problems before of after that. It was just one of those things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
I'll just leave this here...Beta 6 is near. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I'm running that kernel with no problems, over clocked to 17 GHz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pitmaster:
Happy happy joy joy! :D

Craft. Beer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
Holy crap! Careful, you're likely to melt your phone. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
I think it has to do with me being on i747m with a bootloader not matching my newer modem. The updated bootloader never worked well with any custom roms. June 1st.

I'd go right to 7 if the camera doesn't work. LOL only so many times one can say the camera doesn't work until.. bricks the forum!

1.7 is beauty on ktkernel. I installed 11/16 without a cache/dalvik wipe and it was fine... Seems like its easier to leave the bugs in than clean them out.. :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
Yeah, I was just being silly because they forgot the decimal, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
New build posted. OP and changelog updated.

As always I'd recommend a full wipe, BUT if you want to try a flashover, follow these steps.

Make a nandroid

Format cache

Format system

Flash new build

Flash Gapps without reboot in between

Reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Awesome!

Camera fix no longer needed???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
Correct. No camera fix should be needed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Camera good!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
I've never been able to get any kind of performance like that out of my phone. I used to run my Hyperion 4200mAh, and get long times, but still bad performance. I've tried all kinds of settings on KT747, disabling syncing, Greenify, etc... Never gotten anything that good.

And that's because I actually do stuff with my phone while the screen is on :D

I've never gotten 7 hours of screen time on a stock battery, even on stock TW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalfangs:
Anyone have issues after dirty flash? Curious if it's necessary for this update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamFan05:
Special Surprise

If anyone wants to try out an update of twrp, go to their google+ page and look around at all the posts. If you're smart enough you'll find it.

It's a .tar file so flash it in odin. I flashed a 4.4 rom with it this morning and it worked perfectly. Have Fun
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ariesdroid:
I did stuff with my phone as well...i was at work though and left the screen off setting to 30 min just to see how long it would take to kill it...lol. I just finished a more realistic run today and ended up with 14 hours on time and 5h 40m screentime....which is still pretty good IMO...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
can we in place upgrade? (dirty flash) or need a full wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Keland44:
guess i'll give this a go good work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
At work right now, so tried a quick dirty flash. So far so good. Running fine, camera is there and front and back both work (Gapps mini 11/18). Tethering still a no-go for me (wasn't working on Beta 3 or 4 for me either). I'll try a clean install when I get home for that, but I'm not optimistic as it hasn't worked on this rom or Quantum for me.

So far so good though, otherwise. Great stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Beta 6 is smooth! One thing, it hangs waiting for adb in usb debugging through Samsung GS3 ToolKit on my end. Although this is always buggy territory, my computer could use a reboot.

So I updated my bootloader via zip recovery to latest June 1st i747m boot_CWM_I747MVLDMF1.zip to get rid of any connectivity bugs and its all working nice. Give it a try! The latest modem should be fine also, connected to june 1st loaders.

[BOOTLOADER] How to Install a Bootloader Update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
anyone have a mirror for those experimental GAPPs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mikessv:
Is anyone having problems with Netflix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
yes me too..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Yes, i was already on that bootloader, just the modem i had reverted to an older version because my Caller IDs were showing up as weird ascii symbols. I installed Beta6, but my office is a giant Faraday-cage, so i get no signal in here. I'll report back later tonite once i get out of the cage :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
The garbled call display issue was resolved by an update to CM a while ago, I believe. Any I747M modem should work fine on Rogers/Fido now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] legauxg:
Link is down for experimental GAPPS. anyone was able to download it? If so could you mirror it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ariesdroid:
....

If you are on G+ go here --> https://plus.google.com/u/0/communities/101234693143539947480 and scroll down and you will see a post by Steve Spencer with the link to download a working netflix apk. It also has chromecast support as well. If you have Netflix in your apps on the playstore make sure to uncheck "Auto Update" on it or when it updates it wont work. I have it installed on RLS1 and it works perfect.

*EDIT

here's the link... working Netflix (But still go check out my community please! hehe

http://www.androidfilehost.com/?fid=23212708291678471
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
It doesn't get hot, it's been fine, thinking about cranking it up a little more, I do this in increments.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Ok I did a dirty flash... (yes I know, i know)... everything seems to be ok... There is a Camera... but I am missing Gallery now. Now I do have a gallery from Beta 5(RLS1) from TiBU... will that be safe to use?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
Another bug,overscroll not working,instead shows a white square..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiggs82:
Does any one lock screen shortcuts settings fc on beta 6 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Ok, reflashed to beta6, with MF1 modem and bootloader, on i747m.

Getting goid and stable signal. Data works fine (after changing to Rogers LTE in the network settings).

So far it seems pretty stable. My 64gb exfat formatted microsd works well. Camera works as much as it was working on CM 10.2, meaning exposure setting is still not working but both front and back are working.

So far this looks dailyable. Will report more as i test it more.

Envoyé de mon SAMSUNG-SGH-I747 en utilisant Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
Reflash regular PA Gapps. Not my modified Gapps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alekos:
What Gapps did you use exactly? I keep getting force close on gapps... I've tried all 3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
pa_gapps-full-4.4-20131118-signed

Envoyé de mon SAMSUNG-SGH-I747 en utilisant Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnknownTroll1:
Bugs

Security>Face Unlock and Security>Pattern both cause Settings to crash. Anyway I can go back to the previous build? If so can anyone link me the file?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Getting kinda hot here not sure about battery, have to charge it back up. On reboots it can stall in the middle of boot animation and reboot again.

Some greenify superuser problems as well. Reinstalled SuperSU
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
Neither crash for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
Im gonna give this new one a try coming from RLS1 11.14 version.

this is the order I am going to try:

clean install of rom

flash supersu

reboot set up CM

reboot into recover and flash GAPPS

set up apps

set superuser permissions

turn on ART and wait.

Does that sound correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] warri:
Pattern crashes for me. Also when I edit the notification tiles I get a com.android so has stopped working, though it changes correctly.

I did a clean flash and am running the gaps from 1118 not modified
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
yeah me too^^^

also having really bad drain. it will not sleep on the past 2 builds :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] john.fast:
I notice in your screen shot there is the "ok google" feature? can i enable that in this build? Or is that screenshot not from this build. thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
Sleeps fine here. Find out what app is keeping your phone from sleeping.

Long press your home screen, hit settings and turn on Google now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] john.fast:
I have done that, but i don't have the always listening "ok google" showing... hmm interesting, not sure why i would be missing that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
What do you guys call a clean flash? Did you format SYSTEM like the instructions in the OP say? I just went through the whole process of backing up my rom, wiping data / factory reset, FORMATTING SYSTEM, flashing the rom, booting up, flashing the KANGED Gapps and rebooting. I've attached a screenshot of my Pattern Lock screen working fine. That's frustrating.

It won't always tell you to say "Ok Google". Have you tried saying, "Ok Google"? It should work anytime you're at your home screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] john.fast:
No nothing, I will try another clean flash and see if that changes things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] warri:
Yes sir, formatted system after a data/cache wipe.

Then flashed, then flashed the kanged... After some force closes I tried the regular gapps no success.

I can try formatting system again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
Did you change launchers (i.e. Nova Launcher or another)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
Well I apologize if you did. Most people with issues are skipping that step and not understanding why they have different issues. The Quick tiles are a WIP and will probably have bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] john.fast:
No i didn't, however i just figured it out. Language needed to be US english, not Canadian. Didn't know that. Thanks for the help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wash23:
Following instructions exactly. Using PA full Gapps. Everything seems to be working great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxwithanx:
Anyone have an idea of when Google Voice+ might be incorporated in these CM builds? I mean I realize no one knows an exact date but Jesus it's hard leaving it. Was by far the most game-changing phone experience I could ask for (as Google Voice's texting system is just truly atrocious).

I'm assuming it's probably pretty far down the list in the CM world.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
cm-11-20131114-UNOFFICIAL-d2att.zip from here: http://www.androidfilehost.com/?a=show&w=files&flid=291

But why not restore your Nandroid?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnknownTroll1:
Thanks

4.4 is amazing in terms of battery life and the fact that it is sooo much faster. Anyway I love your work so far dev!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
It may be something never incorporated in CM. Part of the reason you are required to go out and get your own gaaps. They are "restricted" by adding those things in the ROM by Google themselves
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxwithanx:
GV+ is not an application made by Google. It's to circumvent the crap app Google has. So it doesn't have anything to do with GAPPS. Regardless, it has been incorporated in CM since July...

http://www.androidpolice.com/2013/0...s-apps-to-send-messages-through-google-voice/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
yep, install was flawless. I had some denied permissions but reflashed supersu and no problems since. camera is front and rear working. didn't turn on ART yet but will once my exchange email sync.

keep it up, nicely done!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Pattern lock force closes when I make a pattern for security.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
Now that I'm in the right forum for the right phone....

Sheesh talk about a blonde moment....(I'm blonde so I can say that lol)

Ok, I'm scared...that was too easy. I'm waiting for my phone to blow up lol

I have ART working. Couldn't use the modified mini gapps so I used the full gapps from 2013-11-15. Had to flash supersu v1.69 update but I HAVE ART running lol. Get a gapps has stopped error...once then it goes away like the little annoyance that it is.

I have front and back cameras, gallery, LTE. I restored all my apps and data from titanium before I switched to ART and all is good...thank you :)

Not sure what you did but I don't care. I couldn't get ART to work for the life of me and now it does. Now I can see what everyone is raving about.

Again thanks so much!!

(First image is front facing second is rear)

OMG!! I wish I could capture the speed of just files loading in Clean Master. I know who cares right? but crap it is fast lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
Ah, my mistake
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] john.fast:
i am getting a lot of "com.android.phone" has stopped errors....anyone know what could be causing this. i get them during using google services like hangouts, chrome, and accessing the pull down menu settings. Any help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
I'd reflash and a clean one if you didn't already
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ariesdroid:
... no root

I just got all the way through setting up beta 6 and everything was working... even both cameras... then i went open rom toolbox pro and realized that root was broken... I then went to recovery and flashed superSU v1.69 and even that didnt fix it... root was gone... I did everything the sane way i always have on all these biilds... not sure why.. or what happened but its sucks real loud...

back on RLS1 for now...

***EDIT*** Disregard!!! Re-flashed and flashed SuperSU at the same time and all is well!!! Everything is working!! Haven't enabled art yet. Need to make a nandroid first...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxwithanx:
Can someone shed light on why the Play Store SuperSU is not being just dl'ed and installed. Going through recovery is suggested?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
You can't just install through play store. It's a little more delicate than that. You have to find a flashable zip and flash SuperSu.

Crack-Flasher
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxwithanx:
....odd. I just found it in the Play Store (where it's been for quite a while), downloaded and installed....from the Play Store. Working just fine.

EDIT: Nevermind, see what you are saying now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
It had been their for quite awhile. No one doubted that. However to override superuser and make SuperSU the root of your phone, I was under the impression from chainfire that you had to flash it first, then update in the store. I understand you can download the app and open it up and stuff. Are you sure it's your default su app?

Crack-Flasher
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalfangs:
How do I change the quick settings tiles to look like the screenshot in the OP? I don't see anything in the Interface options.:confused:

EDIT: Solved, ignore this post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
You also have to be connected to the internet to make it work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
Disregard! :sly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
can confirm on a clean install the when selecting pattern, settings does crash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
If I remember correctly(which can ALWAYS be in question) in order for our brothers on the 747m to work correctly, they will need to have the RIL modified in the modem to work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
An updated bootloader yes.

Nicotine, caffeine, taurine, amphetamine, and classical music.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
Oh and BTW:

Samsung Phones to get Android 4.4 Update

For now, there is an internal Samsung Knox document which was leaked, and which showed a few devices which are going to get the Android 4.4 update, and the document actually showed the devices which would get the Samsung Knox in the coming update. The devices are as follows:

Samsung Galaxy S4

Samsung Galaxy S4 Zoom

Samsung Galaxy S4 Active

Samsung Galaxy Note 3

Samsung Galaxy Mega (no confirmation whether the 5.8, 6.3 or both)

Samsung Galaxy S3

Samsung Galaxy Note II

Samsung Galaxy S4 Mini

Samsung Galaxy Tab 3 & Tab 2

Sourse: http://androidadvices.com/list-android-phones-android-44-kitkat-firmware-update/

Sorry to go a bit off topic
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
UGH.... first the 4.3 update and now this...

so we would need to wait for the official bootloader update from our carriers?

:( :( :( :( :( :( :( :( :(

Edit: i am still getting a status 7 error. Followed all the instructions very VERY carefully. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] finneginsfast:
Every other d2att rom I've flashed has been fine, why would this one need modification?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
yeah i wondered that too when data didnt work for me on the 4.3 touchwiz leak. i could run 4.3 aosp roms with data no problem but not touchwiz without this stupid bootloader update..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
I can't speak on your experiences, but this is something that I saw in discussion on the Stock 4.3 release. And based on the experience that joshuagalipeau is having, it may be an issue. Just putting it out there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
Thanks for that good information!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Up and running and all is good so far. On initial boot had two bootloops and then the device booted.

Then went back into recovery and Installed 4.4 PA Gapps. Just playing around now. Checking out what's new.

Thank you jermaine : )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
jermaine151

still getting that status 7. followed the directions perfectly, no idea what is wrong :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
Do you have one of these bootloaders?

"I747UCDLK3"

"I747UCDMG2"

"I747MVLDLK4"

"I747MVLDMF1"

"I747MUMBLK3"

"I747MUMBLL1"

If not, it won't let you flash unless you remove those checks from the script. That would be at your own risk, though.

If you're brave and want to try it, I posted instructions here: http://xdaforums.com/showpost.php?p=47300683&postcount=63
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
yes i have I747MVLDMF1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
FWIW I'm on the newest CWM Touch Recovery. Also running LK3 Modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
What version of CWM are you running?

I used v6.0.4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
CWM Recovery touch v6.0.3.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
6.0.4.3 here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jermaine151:
Update your recovery. Your version was not updated for KitKat.