Develop Bugs

[Q] Upgrading from rooted EK02 to EL29.

I recently rooted my phone following the instructions posted on this forum. Everything went great and I have been running my phone rooted for a number of weeks now (EK02).
Well, I redownloaded the e4gtauto-sfx.exe package, ran the OTA Compliance check for EK02-EL29 and everything was fine. I proceeded to go with options C and then L (Install BootImg EL29+CWM-Rogue) and that went without a hitch, rebooted and everything appears to be running fine. I checked my phone settings and noticed the following:
Baseband Version: S: D710.10 S.EK02
Kernel Version: 2.6.35.7-SPH-D710.EL29-CL852097
Build Number: GINGERBREAD.EK02
Click to expand...
Click to collapse
Can someone explain why the baseband version and build number still say EK02? I was under the impression that information above would all say EL29. Should I run the OTA update?
Thanks.

ExitusLSU said:
I recently rooted my phone following the instructions posted on this forum. Everything went great and I have been running my phone rooted for a number of weeks now (EK02).
Well, I redownloaded the e4gtauto-sfx.exe package, ran the OTA Compliance check for EK02-EL29 and everything was fine. I proceeded to go with options C and then L (Install BootImg EL29+CWM-Rogue) and that went without a hitch, rebooted and everything appears to be running fine. I checked my phone settings and noticed the following:
Can someone explain why the baseband version and build number still say EK02? I was under the impression that information above would all say EL29. Should I run the OTA update?
Thanks.
Click to expand...
Click to collapse
Can't explain to you why it still says that but I'm running EL29 ROMs and they still say baseband EK02 so don't run it again. It's updated and as long as its running fine, leave it alone.
Edit: After looking at QBking77's video http://www.youtube.com/watch?v=BfZaALRWANQ&feature=player_embedded#!, at the 49 sec mark it shows build number EL29 and Baseband EK02. Hmmm, not sure what that means. So I guess at least the baseband should have changed.

lopezpm said:
Can't explain to you why it still says that but I'm running EL29 ROMs and they still say baseband EK02 so don't run it again. It's updated and as long as its running fine, leave it alone.
Click to expand...
Click to collapse
Thanks for the quick reply.
I'm not running any custom ROMs at the moment. I just wanted the phone rooted. The interface looks the same as it did when I got the phone. When I update via the auto process I described above, is it only updating the kernel? Does the broadband version and build number refer to the user interface?

Total Noob here, but a friend rooted my phone (to give me WIFI tether, did not flash a ROM) yesterday and this morning Sprint pushed the EL29 update which I installed. Did I screw up by installing the OTA update on a root-only phone?

ExitusLSU said:
I recently rooted my phone following the instructions posted on this forum. Everything went great and I have been running my phone rooted for a number of weeks now (EK02).
Well, I redownloaded the e4gtauto-sfx.exe package, ran the OTA Compliance check for EK02-EL29 and everything was fine. I proceeded to go with options C and then L (Install BootImg EL29+CWM-Rogue) and that went without a hitch, rebooted and everything appears to be running fine. I checked my phone settings and noticed the following:
Can someone explain why the baseband version and build number still say EK02? I was under the impression that information above would all say EL29. Should I run the OTA update?
Thanks.
Click to expand...
Click to collapse
I could be wrong, and if I am, I'm sure to be corrected. Your Baseband, kernel, and ROM (what the build number refers to) are all seperate parts. The Baseband I believe refers to your modem. It looks like the only thing you updated was the kernel, as the recovery (CWM-Rogue) is actually part of the kernel, not your ROM. Make sure the ROM you're running is EL29 based. To flash the updated EL29 modem, check out the Epic 4G Touch development forum, there is a thread stickied with all of the available modems that are flashable from CWM.
Did that help?
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
ShoePhone said:
Total Noob here, but a friend rooted my phone (to give me WIFI tether, did not flash a ROM) yesterday and this morning Sprint pushed the EL29 update which I installed. Did I screw up by installing the OTA update on a root-only phone?
Click to expand...
Click to collapse
You just lost root. Installing any update pushed by the carrier will remove your root access.

seph1cloud said:
I could be wrong, and if I am, I'm sure to be corrected. Your Baseband, kernel, and ROM (what the build number refers to) are all seperate parts. The Baseband I believe refers to your modem. It looks like the only thing you updated was the kernel, as the recovery (CWM-Rogue) is actually part of the kernel, not your ROM. Make sure the ROM you're running is EL29 based. To flash the updated EL29 modem, check out the Epic 4G Touch development forum, there is a thread stickied with all of the available modems that are flashable from CWM.
Did that help?
Click to expand...
Click to collapse
Appreciate the help. That cleared a lot of things up for me.
Once I update those components to the appropriate EL29 components, do you know if the Sprint OTA update notification will go away or do I need to just go ahead and follow the stickied thread about disabling update notifications?
Thanks.

seph1cloud said:
[/COLOR]
You just lost root. Installing any update pushed by the carrier will remove your root access.
Click to expand...
Click to collapse
How do I go about getting root back, without the help of my friend? Thanks for your help. Pretty sure he used the auto root method with et4g files, etc from what I watched him do.

Never accept OTA's once you're rooted.
http://forum.xda-developers.com/showthread.php?p=19269878
Read the whole thing 2 or 3 times. Watch the videos also by qbking77
Sent from my SPH-D710 using Tapatalk

lopezpm said:
Never accept OTA's once you're rooted.
http://forum.xda-developers.com/showthread.php?p=19269878
Read the whole thing 2 or 3 times. Watch the videos also by qbking77
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
So after reading the Autoroot thread you linked, am I interpreting it correctly that since I updated with the OTA EL29, I can't have stock root (as I had previously) but root + CWM Rom? If so, what does this change on my end as far as the Touchwiz interface, etc? Does tethering/Hotspot come automatically with CWM? Thanks for your patience as I am guessing these are pretty rudimentary questions.

ShoePhone said:
So after reading the Autoroot thread you linked, am I interpreting it correctly that since I updated with the OTA EL29, I can't have stock root (as I had previously) but root + CWM Rom? If so, what does this change on my end as far as the Touchwiz interface, etc? Does tethering/Hotspot come automatically with CWM? Thanks for your patience as I am guessing these are pretty rudimentary questions.
Click to expand...
Click to collapse
I would just flash a stock rooted EL29 ROM with ODIN
sent from the near past

ShoePhone said:
So after reading the Autoroot thread you linked, am I interpreting it correctly that since I updated with the OTA EL29, I can't have stock root (as I had previously) but root + CWM Rom? If so, what does this change on my end as far as the Touchwiz interface, etc? Does tethering/Hotspot come automatically with CWM? Thanks for your patience as I am guessing these are pretty rudimentary questions.
Click to expand...
Click to collapse
CWM or ClockworkMod Recovery is simply a custom recovery that is used for various purposes. With CWM you can do a nandroid backup,flash ROMs, Kernels, Themes, etc. A custom recovery is something you definitely want. The touchwiz interface will not be affected at all by achieving root or installing a custom recovery. Wifi-Tether is not something that is automatically installed with root, however once rooted, you should be able to install Wifi-Tether without any issues.

ShoePhone said:
So after reading the Autoroot thread you linked, am I interpreting it correctly that since I updated with the OTA EL29, I can't have stock root (as I had previously) but root + CWM Rom? If so, what does this change on my end as far as the Touchwiz interface, etc? Does tethering/Hotspot come automatically with CWM? Thanks for your patience as I am guessing these are pretty rudimentary questions.
Click to expand...
Click to collapse
You can have exactly what you had before. If you want just root, you can have that. If you want root+CWM you can have that. If you want just CWM, you can have that.
What they plugged in EL29 is the exploit used by the Auto Root package (Option A) to achieve root. Instead of having you run Option A, I just did it for you and pre-rooted a EL29 ROM and packaged it as an ODIN One-Click.
Basically you just double-click on the ODIN One-Click, reboot your phone into d/l mode, connect your phone to your PC, and press start.
Use the ODIN EL29 link in my signature.
If you want CWM, just use Auto Root Option C to install EL29+CWM-Rogue (you don't need to do this unless you want to)
---------- Post added at 04:20 AM ---------- Previous post was at 04:15 AM ----------
ExitusLSU said:
I recently rooted my phone following the instructions posted on this forum. Everything went great and I have been running my phone rooted for a number of weeks now (EK02).
Well, I redownloaded the e4gtauto-sfx.exe package, ran the OTA Compliance check for EK02-EL29 and everything was fine. I proceeded to go with options C and then L (Install BootImg EL29+CWM-Rogue) and that went without a hitch, rebooted and everything appears to be running fine. I checked my phone settings and noticed the following:
Can someone explain why the baseband version and build number still say EK02? I was under the impression that information above would all say EL29. Should I run the OTA update?
Thanks.
Click to expand...
Click to collapse
The OTA Compliance Check is there to tell you *if* the OTA update will be successful on your phone. It checks all the files the OTA patches to make sure they haven't been deleted or modified.
You would still need to run the EL29 OTA update to actually get a full EL29. However, I would suggest you install the pre-rooted EL29 ODIN One-Click in my signature, as that will keep your root.
Option C in Auto Root only installs CWM (which is packed into the EL29 kernel), thus only your kernel changed version #s. Ideally you would run the aforementioned pre-rooted EL29 ODIN One-Click to have a rooted stock EL29, then decide you want CWM, and run Auto Root Option C to install EL29+CWM-Rogue.
Alternatively, you might be on a previous version of the ROM but want to try the EL29 kernel and would install EL29 or EL29+CWM-Rogue to see how it performs with your previous ROM.

ExitusLSU said:
Appreciate the help. That cleared a lot of things up for me.
Once I update those components to the appropriate EL29 components, do you know if the Sprint OTA update notification will go away or do I need to just go ahead and follow the stickied thread about disabling update notifications?
Thanks.
Click to expand...
Click to collapse
I haven't read the sticky about disabling the update notifications but I'm running all EL29 (custom ROM, modem and, EL29 based kernel) and do not get the update notifications.
There is an application called Sprint Installer that handles OTA updates and notifications which may be stripped out of the ROM I'm using. You can uninstall or freeze the Sprint Installer with Titanium Backup.

so does EL29 work better than the Ek02?

Depends. For some people yes, for some people no.

I'm actually having trouble....
I got the message saying that a new update can be installed. I click it but when it tries to install it it gives me the android guy with the triangle and "!" mark in it. It won't update :/. I use the UnNamed Rom v2.0.1. I then tried to wipe the phone back to factory reset. I wiped to factory reset, wiped cache, and wiped delvik cache. Maybe then I could download the new EL29 OTA. I tried to restart the phone and I just get the Samasung Galaxy S2 logo and it hangs.
When I install the UnNamed Rom zip, it works again.
Please help.... I am kinda new to this. :/

I just want to get ride of the notification. I'm a freak about not having anything up there .
So is there something we need to download to get this update? Kinda new to root so don't really know what to do here.

sfhub said:
You can have exactly what you had before. If you want just root, you can have that. If you want root+CWM you can have that. If you want just CWM, you can have that.
What they plugged in EL29 is the exploit used by the Auto Root package (Option A) to achieve root. Instead of having you run Option A, I just did it for you and pre-rooted a EL29 ROM and packaged it as an ODIN One-Click.
Basically you just double-click on the ODIN One-Click, reboot your phone into d/l mode, connect your phone to your PC, and press start.
Use the ODIN EL29 link in my signature.
If you want CWM, just use Auto Root Option C to install EL29+CWM-Rogue (you don't need to do this unless you want to)
---------- Post added at 04:20 AM ---------- Previous post was at 04:15 AM ----------
.
Click to expand...
Click to collapse
Thanks for the help. If I now want to use the AutoRoot Option C above, what will the addition of CWM-Rogue give me?

O lord! My Galaxy 2 is rooted, and I woke up this morning to that OTA update. It's stuck on the little green android and exclamation screen. Any ideas where to go from here? Thanks for any suggestions....I don't want to brick my phone.

dougswub said:
O lord! My Galaxy 2 is rooted, and I woke up this morning to that OTA update. It's stuck on the little green android and exclamation screen. Any ideas where to go from here? Thanks for any suggestions....I don't want to brick my phone.
Click to expand...
Click to collapse
Just hit the home button and you should see recovery, home or power, I forget which I hit but once I did the exclamation went away and I just rebooted normally.

ICS Update

Hello All,
FYI: This is stock Not rooted.
I got the prompt this morning on my Sprint Galaxy S2 Epic Touch 4g for a system update to ICS It had a full charge I clicked to reboot it started counting down and all it did was reboot, it didn't update I checked the about section and the build and everything is the same and if I go to the system update area now it just says your phone is up to date. Any ideas on what happened?
Thanks in Advance.
Ryan B.l

Something probably went wrong and it didn't boot into recovery or if it did, it is possible the update had some issues.
There is probably a log file in the /cache directory somewhere.
If you really want FF18, IMO the simplest way is just download the pre-rooted FF18 ODIN OneClick here;
http://forum.xda-developers.com/showthread.php?t=1721229

sfhub said:
Something probably went wrong and it didn't boot into recovery or if it did, it is possible the update had some issues.
There is probably a log file in the /cache directory somewhere.
If you really want FF18, IMO the simplest way is just download the pre-rooted FF18 ODIN OneClick here;
http://forum.xda-developers.com/showthread.php?t=1721229
Click to expand...
Click to collapse
Thanks for the prompt reply, I appreciate it. I just booted into recovery and wiped the partition cache and rebooted to see if that would help at all. If not then I may just have to manually update as suggested.

I've been using one of Calkulin's ROMs - If I want to try out the stock ICS update, should I flash back to a stock GB ROM first or would I still get a notification to update?

If you are on a custom ROM, you might get the notification, but it won't pass the verification stage when it tries to install.
I would just use the pre-rooted FF18 ODIN OneClick (Full Version) available here:
http://forum.xda-developers.com/showthread.php?t=1721229

sfhub said:
If you are on a custom ROM, you might get the notification, but it won't pass the verification stage when it tries to install.
I would just use the pre-rooted FF18 ODIN OneClick (Full Version) available here:
http://forum.xda-developers.com/showthread.php?t=1721229
Click to expand...
Click to collapse
I found the firmware update at the link below and downloaded it and renamed it to update.zip and rebooted to recovery and ran the update from sd and it updated fine
http://community.sprint.com/baw/thread/89419?start=105&tstart=0

Clockwork Mod won't stick

I'm trying to flash Clockwork Mod onto a friend's TMO S3 with Odin. I was able to do this successfully with my TMO S3, both are running UVALH2.
Odin says the flash was successful, I restart the phone and try to boot into the custom recovery but it keeps taking me to the stock recovery. I tried a few more times with the same results.
Am I missing something?

Try the no tripping the flash counter method found in the stickies found in the dev section.
You should be able to get around your problem with this method.
Sent from my SGH-T999 using xda premium

kpizzle said:
I'm trying to flash Clockwork Mod onto a friend's TMO S3 with Odin. I was able to do this successfully with my TMO S3, both are running UVALH2.
Odin says the flash was successful, I restart the phone and try to boot into the custom recovery but it keeps taking me to the stock recovery. I tried a few more times with the same results.
Am I missing something?
Click to expand...
Click to collapse
The UVALH2 update includes two files that will overwrite recovery every reboot
You can fix this issue by renaming the following files using root explorer
Rename:
/system/recovery-from-boot.p to /system/recovery-from-boot.p.bak
and
/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak
Once you've done that, reflash CWM through ROM Manager and recovery will stick

ingenious247 said:
The UVALH2 update includes two files that will overwrite recovery every reboot
You can fix this issue by renaming the following files using root explorer
Rename:
/system/recovery-from-boot.p to /system/recovery-from-boot.p.bak
and
/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak
Once you've done that, reflash CWM through ROM Manager and recovery will stick
Click to expand...
Click to collapse
You are the man!!!

there's a little "thanks" button on my post.. feel free to click it
and no problem, glad to help!

ingenious247 said:
The UVALH2 update includes two files that will overwrite recovery every reboot
You can fix this issue by renaming the following files using root explorer
Rename:
/system/recovery-from-boot.p to /system/recovery-from-boot.p.bak
and
/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak
Once you've done that, reflash CWM through ROM Manager and recovery will stick
Click to expand...
Click to collapse
So I just realized something. I can't even attain root access, how can I edit these files?

Can flash mrRobinson's LH2 w/root and you will have full LH2 stock with root. It is an Odin package and only flashes /system partition so no /data loss.

kpizzle said:
So I just realized something. I can't even attain root access, how can I edit these files?
Click to expand...
Click to collapse
Flash CWM through Odin, but turn off the auto reboot in Odin
That way it won't overwrite it
Then power down when it's done, and boot into recovery, Flash Superuser

Will i still be able to receive JB OTA update when the time comes, if i rename these two files and flash CWM through ROM manager?

arthaz28 said:
Will i still be able to receive JB OTA update when the time comes, if i rename these two files and flash CWM through ROM manager?
Click to expand...
Click to collapse
No, you cannot receive OTA updates unless you are on stock recovery.
So you would have to Odin back to stock before accepting the update, which is simple enough.
Or just wait for someone to take the update and make a flashable zip file which will happen pretty quickly once the OTA comes out

ingenious247 said:
No, you cannot receive OTA updates unless you are on stock recovery.
So you would have to Odin back to stock before accepting the update, which is simple enough.
Or just wait for someone to take the update and make a flashable zip file which will happen pretty quickly once the OTA comes out
Click to expand...
Click to collapse
You don't need stock recovery for any reason at all. Not anymore.

I never said you needed it. I was answering the question that was asked.
And if you don't want to flash a modified version of a stock ROM, then yes, you do need stock recovery. Some of us don't like deodexed ROMs and care to choose what we debloat.

ingenious247 said:
I never said you needed it. I was answering the question that was asked.
And if you don't want to flash a modified version of a stock ROM, then yes, you do need stock recovery. Some of us don't like deodexed ROMs and care to choose what we debloat.
Click to expand...
Click to collapse
Thank you sir!
After I was rooted, I created a backup using CWM. So, if the update comes out, I can just flash my backup stock ROM again using CWM rand I should be able to receive the OTA update, right?
(sorry I am a noob and still learning about this whole rooting, custom ROM, etc stuff)

arthaz28 said:
Thank you sir!
After I was rooted, I created a backup using CWM. So, if the update comes out, I can just flash my backup stock ROM again using CWM rand I should be able to receive the OTA update, right?
(sorry I am a noob and still learning about this whole rooting, custom ROM, etc stuff)
Click to expand...
Click to collapse
No, you would have to Odin back to stock which would overwrite CWM with stock recovery. If you're not familiar with Odin read up on it, it's really easy to use. Just make sure you get it from the correct thread for your phone model and you'll be fine.
Sent from my SGH-T999 using xda premium

[Q] Root for Samsung GS3 on stock 4.1.1?

Hi,
I recently bought the Samsung Galaxy S3 on T-Mobile, to replace my Motorola Droid X on Verizon. Love the new phone, but miss my root capabilities - aka there's a bunch of bloat. There's an OTA not being forced for 4.1.1, but when I tried to root that, I soft bricked and got stuck in a boot loop at the pulsing Samsung. I grabbed ODIN and was able to push the stock 4.0.4 back into it and get it working again, baseband T999UVLH2, Kernel 3.0.8-925100, build IMM76D.T999UVALH2. Is there a way to root this phone, or a stock rooted ROM I could push up with ODIN?
I'm not looking to load custom ROM's, just have some of the abilities I had on my DX when it was rooted and get rid of some of the stock crap that I don't need.
I originally tried to do this with Samsung Galaxy S3 Toolkit v6.0, and soft bricked the phone. I followed the directions online, and did it as instructed, but yeah. Any help would be greatly appreciated.

All you need to root is the touch 6.0 clockwork mod recovery tar file which is available on xda as zip file and the odin version 3+ and follow instructions thats all thats needed to root, make sure you also put the superuser app inside the root of your sd card meaning connect your galaxy s3 to computer then open the root sd card and put it inside there, i believe there is a clockwordmod touch that already comes with superuser so you may not have to worry about putting superuser in root. here i'll grab links for you now. u dont checkmark anything on odin except select pda and browse for the tar file. Here is guide for your device with download links.
The clockworkmod touch recovery version is by far best and always works well with almost all roms.
I would also recomend you use liquidsmooth rom or if you want to test out the new android 4.2 cm but camera doesn't work on 4.2 cm10.1 now however it's a very nice custom rom
Btw, make sure you flash the superuser.zip file that you placed in your sd card while you are in clockwork mod recovery otherwise you wont comlete the root. to get into cwm you gotta hold volume up home button and power button at same time.
http://www.theandroidsoul.com/how-to-install-cwm-touch-recovery-6-0-for-t-mobile-galaxy-s3/

Or even easier you can go here:
http://forum.xda-developers.com/showthread.php?t=1949687
[Firmware/OTAs] T999(V) Official, Leaked & Root66 FW & OTA Updates!
Just flash the root66 udljva file and it is just pure stock prerooted. Just follow the doc's instructions and all will be good.
Sent from my galaxy nexus using Tapatalk 2

rawdaddymagraden said:
Or even easier you can go here:
http://forum.xda-developers.com/showthread.php?t=1949687
[Firmware/OTAs] T999(V) Official, Leaked & Root66 FW & OTA Updates!
Just flash the root66 udljva file and it is just pure stock prerooted. Just follow the doc's instructions and all will be good.
Sent from my galaxy nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks to both of you, I'm rooted, exactly the way I wanted to be. I couldn't get CWM to flash in stock recovery, nor could I get Root66 to flash in recovery, so I just pushed it with Odin. All I need to do now is get CWM Touch on it, and I'll be set. I'm reinstalling my root apps as we speak.
Thanks again!

Odin cf auto root is the quickest and simplest.

seattlestexan said:
Thanks to both of you, I'm rooted, exactly the way I wanted to be. I couldn't get CWM to flash in stock recovery, nor could I get Root66 to flash in recovery, so I just pushed it with Odin. All I need to do now is get CWM Touch on it, and I'll be set. I'm reinstalling my root apps as we speak.
Thanks again!
Click to expand...
Click to collapse
Flash cwm via Odin uncheck auto reboot. Then go straight to recovery then reboot. I'd wipe cache and dalvik while in there though.
http://forum.xda-developers.com/showthread.php?t=1809307
[RECOVERY]TWRP 2.3.1.0 touch recovery [2012-10-15]

[Q] Can't Root? What are my options?

I have an i747M, from Fido (rogers) running the stock 4.3 firmware. yesterday i tried to root it using odin to install CWM, and then CWM to install supersu.
after successfully installing supersu, i restarted the phone, and got knox blocking the app. i updated it from Play, but then i couldn't open it, and it said it can't install the binary. when my phone asked to update the security certificates, i (stupidly) agreed.
i downloaded the .zip for supersu 1.89, and tried installing that, with the same result, but this time i also can't uninstall supersu.
i've bumped my binary counter, but i'm back to basically stock now.
my goal is to install aokp. is there a way to do it without gaining root first?
if i install CWM through odin, can i flash the aokp rom from CWM?
will the phone reset the recovery?
is this risky?

You could try installing a pre-rooted Rogers rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
I was not able to find a pre-rooted 4.3 for Fido and, since you intend to install a custom rom and recovery, the pre-rooted Rogers ROM might be a good place to start.

It's there a reason to install a rooted rom before aokp? As far as I can tell, I can install aokp without rooting at all.
or am I missing something?
Sent from my SGH-I747M using xda app-developers app

Yes, you can just install a custom ROM without rooting first.
I mentioned the prerooted ROM because you post said you wanted to install su.

Ok, please confirm i have this procedure correct:
1. i use Odin to install CWM
2. boot straight into CWM
3. from inside CWM, i flash the AOKP zip file, and then the gapps zip file
my understanding is that this will keep cwm as my recovery and install aokp with gapps.
am i missing anything?
audit13 said:
Yes, you can just install a custom ROM without rooting first.
I mentioned the prerooted ROM because you post said you wanted to install su.
Click to expand...
Click to collapse

Milothicus said:
Ok, please confirm i have this procedure correct:
1. i use Odin to install CWM
2. boot straight into CWM
3. from inside CWM, i flash the AOKP zip file, and then the gapps zip file
my understanding is that this will keep cwm as my recovery and install aokp with gapps.
am i missing anything?
Click to expand...
Click to collapse
Just make sure you flash a tar version of CWM that is meant for your phone.
I can't really speak about 4.3 because I'm on 4.1.2 but the method you described is the same method I used.

Milothicus said:
I have an i747M, from Fido (rogers) running the stock 4.3 firmware. yesterday i tried to root it using odin to install CWM, and then CWM to install supersu.
after successfully installing supersu, i restarted the phone, and got knox blocking the app. i updated it from Play, but then i couldn't open it, and it said it can't install the binary. when my phone asked to update the security certificates, i (stupidly) agreed.
Click to expand...
Click to collapse
If you want to kill Konx to enable root you can flash this knox removal script: http://forum.xda-developers.com/showthread.php?t=2507931
If you are just going to flash AOKP via CWM, this may not be necessary, but this is the answer to your Knox problem.