Develop Bugs

|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |

|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here.
If you have not updated to 4.4, go here.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Edit:
Here is some potentially useful info for root method #1 from ansonantonym.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery then flash SuperSu and the Knox Remover
4) Reboot
5) Download SuperSu from the Play Store
6) Open SuperSu and update the binary when prompted
7) Reboot
8) Enjoy rooted 4.3/4/4
Downloads:
Odin
TWRP (Odin flashable tar)
SuperSu (v1.65)
SuperSu (v2.01)
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
Please be sure to thank Chainfire, Dees_Troy, and Kaito95.
*****

Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

jeremyds45 said:
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.

upndwn4par said:
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
Click to expand...
Click to collapse
Ah it is so nice to have root again... Thank you so much for putting up with a noob.
Crazy events of a noob that lead me to root
Installed ota 4.3
Tried to root and install superuser by odin and then custom recovery to flash
Root didn't happen because of knox
Could only get to CWM custom recovery if it was right after odin and battery pull?...
Flashed the script to remove knox, which did remove knox
Tried the same root method as above and no root access
Tried supersu and then updating in play with no success
Changed security update settings etc nothing
Reset delvik, cache, permissions, etc nothing
Different root method and files for odin, and custom recovery stuck
Used files from this thread, went into custom recovery and flashed supersu
Installed supersu from play store...
Updated the binary using custom recovery
Rebooted...
ROOT access, all root applications work fine and root sticks even after reboots
I never messed with cf auto root method
THANK you guys for your time effort and sharing, helps noobs out like me a lot!

Sweet! I've missed root since I upgraded using the OTA file you provided. Looking forward to much other great things coming from you

Thank You
upndwn4par said:
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here. Make sure you understand the risks and uncertainties described in the OP.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery and flash SuperSu.
4) Flash the Knox Remover
5) Reboot
6) Download SuperSu from the Play Store
7) Update the binary when prompted
8) Reboot
8) Enjoy 4.3
Downloads:
Odin
TWRP (Odin flashable tar)
UpdateSuperSu
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
*****
Click to expand...
Click to collapse
Method two absolutely worked. Thank you so much. I was scared to flash TWRP but knowing you did it gave me the courage. Have full root and happy

questions about this root
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.

THANKS!!!! your a lifesaver didn't know how much longer i could take without root

Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??

bkong said:
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
Click to expand...
Click to collapse
use the TWRP method worked perfected for me

Thanks

PimpMyPC said:
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
Click to expand...
Click to collapse
The second method worked great. I believe (and the way that worked for me) that you use your custom recovery to flash the knox script, not using Odin and pda. I don't think it removed anything other than knox, there is a different script for removing knox and att bloatware. Should still be able to factory reset... But can't guarantee that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Root & Knox
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????

tailgunner9 said:
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
Click to expand...
Click to collapse
Those settings are just for granting device administrator privileges. If unchecked, Knox is still doing it's thing, just not at an administrative level.
Yes, it is safe to try and root.
I have Android Device Manager as admin. That way if I ever lose my device I can just log in to the Play Store and locate and / or wipe the device.

To do this just flash the recovery.img file using odin and clicking the pda button correct?

Is there a way to freeze Knox instead of deleting it in the event I would want to go back to full stock?

After you are rooted, use an app like Titanium Backup(pro) or My Backup pro. Both will freeze it.

Root
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks

tailgunner9 said:
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
Click to expand...
Click to collapse
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.

indymx said:
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
Click to expand...
Click to collapse
Thanks indymx, may get the nerve up to try it on my AT&T S3. Let me know if you run into any problems. Guess Rom Manager and other programs that require Root are working Ok and you have rebooted few times to be sure it keeps Root?? Have Happy Thanksgiving.

Root is Gone?

So all of sudden, my rooted S3 is not rooted anymore.
I wanted to use Titanium Backup and it says
"Sorry, I could not acquire root privileges. This application will *not* work! Pleasre verify that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command."
and then I tried my other root applications such as Greenify, App Ops and they are all saying my phone isn't rooted anymore.
I don't understand, I never upgraded my phone after I rooted and I never flashed a different rom and kept the Touchwiz Rom.
I used this guide to root my phone originally:
http://forum.xda-developers.com/showthread.php?t=1771687
My phone is running 4.3 Android (Same Version I used when Rooted in the first place)
Baseband Version: T999UVUEMJC
Please let me know what to do

check if supersu is working properly.

Cronoss said:
check if supersu is working properly.
Click to expand...
Click to collapse
It isn't.
The following message pops up:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"

magic132131 said:
It isn't.
The following message pops up:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
Click to expand...
Click to collapse
My suggestion would be to back everything up and re flash root66.

Cronoss said:
My suggestion would be to back everything up and re flash root66.
Click to expand...
Click to collapse
Would I lose all my data?
In terms of re flash root66, that means simply using Odin and re-rooting my phone like I do the first time right? Would it be the same instructions too?

magic132131 said:
Would I lose all my data?
In terms of re flash root66, that means simply using Odin and re-rooting my phone like I do the first time right? Would it be the same instructions too?
Click to expand...
Click to collapse
I'm not sure if you are going to lose your data.. so that's why I said to back everything up, just in case.
And yes.. same method as before from that post.

Befoe you flash again. Try uninstalling then installing supersu again

SoulEater- said:
Befoe you flash again. Try uninstalling then installing supersu again
Click to expand...
Click to collapse
I can't uninstall supersu as it gives me no option to do so. I can only uninstall all updates that were applied but not complete remove and then install it.

I had this happen on my Tmobile Galaxy S3.
I read somewhere else on XDA that you just had to install the latest SuperSU, in zip form, from recovery mode.
I havent posted enough here to be able to post a link, but you can find it on chainfires website.
Then reboot and it should work.

4.4. KitKat for Wifi Note 10.1 2014 P600 Q&A

Hi guys I have some questions about the new Firmware and KitKat in general and you may have answers I'll try to update first post with your answers!
-Will I loose root when I flash through Odin? --> Yes
-Is the new firmware rootable, or is there a way to keep root when I upgrade from rooted 4.3?
-->For upgrade yes: If you are rooted on 4.3 you can restore root by flashing a custom recovery and flash superSU manually.
-->chainfire autoroot works but you need to update the superSU app through play store after flashing.
-Will KitKat restrict access to my SD card? -->Yes but fixable through an app or editing a file (needs root), there is already a thread about that.
-Can I still use flash with KitKat? How?
-->Yes, there is a hacked version see 2nd post for link.
-How is the touchscreen driver? Is the stuttering fixed? Do touch and hold actions still drop after ~23sec?
-->Pretty much fixed. To about the same state as the improved Kernel we had a while ago.
-Are there any apps that are not working (root apps too)?
-Gesture Controls? --> works
-Xposed framework app settings? -->works
-Is Hancom Office included or does it still work? --> not included but does still work.
Thats about what I can think of a the moment.

Hi,
If you are already rooted then all you have to do is re install TWRP and then flash SU zip then you have root.
For flash player, download hacked version here, it works I tested it on new software :
http://forum.xda-developers.com/go...e-how-to-play-flash-video-android-4-t2548001
Also, xposed works. Tested it on new software
Sent from my Note 2014 using Tapatalk

Chainfire's Auto Root does work, once you flash it thru odin and reboot, go to the Play store and update the app.
- Please update OP

Here's a question: I'm already rooted. Is flashing the stock KitKat image via Odin and rerooting the only way to upgrade?

starfall42 said:
Here's a question: I'm already rooted. Is flashing the stock KitKat image via Odin and rerooting the only way to upgrade?
Click to expand...
Click to collapse
If you are already rooted, I assume you have TWRP too. Just download this KitKat rom, full wipe and install.
http://forum.xda-developers.com/show....php?t=2720631

Itchiee said:
Chainfire's Auto Root does work, once you flash it thru odin and reboot, go to the Play store and update the app.
- Please update OP
Click to expand...
Click to collapse
Not for me I flashed a stock 4.4 kit kat on my tablet coming from root 4.3. I then flashed chainfire autoroot thru odin on the 4.4 and the superuser there only problem is it displays this ' There is no SU binary installed, and SuperSU cannot install this is a problem! I formatted my 4.3 before flashing it maybe thats why?

itachi30s said:
Not for me I flashed a stock 4.4 kit kat on my tablet coming from root 4.3. I then flashed chainfire autoroot thru odin on the 4.4 and the superuser there only problem is it displays this ' There is no SU binary installed, and SuperSU cannot install this is a problem! I formatted my 4.3 before flashing it maybe thats why?
Click to expand...
Click to collapse
Not sure... I installed KK on the tablet via Odin, then rebooted and setup, then rebooted into download mode and flashed auto root thru Odin.
Upon reboot I got an error selecting SuperSU, but once I updated it thru the Play Store its been fine.
Using ES Explorer I removed the items I don't need and removed all of the Knox stuff.
There are a few of us this worked for so I don't know what went wrong for you.
If you don't succeed then try again, and again, and again....Good luck.

Do I have to update to kitkat bootloader?

gcrutchr said:
Do I have to update to kitkat bootloader?
Click to expand...
Click to collapse
Not needed. The bootloader is same for 4.3 and 4.4

Itchiee said:
Not sure... I installed KK on the tablet via Odin, then rebooted and setup, then rebooted into download mode and flashed auto root thru Odin.
Upon reboot I got an error selecting SuperSU, but once I updated it thru the Play Store its been fine.
Using ES Explorer I removed the items I don't need and removed all of the Knox stuff.
There are a few of us this worked for so I don't know what went wrong for you.
If you don't succeed then try again, and again, and again....Good luck.
Click to expand...
Click to collapse
Thx for the response from what i can see you never fully wipe your data before installing 4.4 KK but i did so i believe i lost my root like that. So when i updated the supersu never carried over from 4.3

Srikar_NBK said:
Not needed. The bootloader is same for 4.3 and 4.4
Click to expand...
Click to collapse
Thanks.

Itchiee said:
Not sure... I installed KK on the tablet via Odin, then rebooted and setup, then rebooted into download mode and flashed auto root thru Odin.
Upon reboot I got an error selecting SuperSU, but once I updated it thru the Play Store its been fine.
Using ES Explorer I removed the items I don't need and removed all of the Knox stuff.
There are a few of us this worked for so I don't know what went wrong for you.
If you don't succeed then try again, and again, and again....Good luck.
Click to expand...
Click to collapse
man you're awesome thx a bunch I saw my mistake, I was using chain fire root except the one I had downloaded from a third party site wasn't exactly for my device. Went to chainfire official site got the autoroot bam im rooted at.
Rep + 1

How do you get hancom office?

-Will KitKat restrict access to my SD card? -->Yes but fixable through an app or editing a file (needs root), there is already a thread about that.
Click to expand...
Click to collapse
Sorry, but I cant find thread related to the issue .
What do you mean by `fixable through an app`? I`m not rooted and full stock.

Kit Kat SD Card Issue
clouds5 said:
Hi guys I have some questions about the new Firmware and KitKat in general and you may have answers I'll try to update first post with your answers!
-Will KitKat restrict access to my SD card? -->Yes but fixable through an app or editing a file (needs root), there is already a thread about that.
Click to expand...
Click to collapse
Is this the app you are referring to? http://forum.xda-developers.com/showthread.php?t=2684188

Still not out in Germany

I intend on rooting this tablet. Am I better off rooting 4.3 and then flashing KK update? Or is it possible to update to KK and then root?

supremekizzle said:
I intend on rooting this tablet. Am I better off rooting 4.3 and then flashing KK update? Or is it possible to update to KK and then root?
Click to expand...
Click to collapse
Both ways work equally well I was already rooted with 4.3 but either way has been confirmed working so it doesn't matter.

clouds5 said:
Both ways work equally well I was already rooted with 4.3 but either way has been confirmed working so it doesn't matter.
Click to expand...
Click to collapse
Thank you. So any guide I find on rooting 4.3 should be the same procedure as 4.4?

supremekizzle said:
Thank you. So any guide I find on rooting 4.3 should be the same procedure as 4.4?
Click to expand...
Click to collapse
Yes. Refer to this one
http://forum.xda-developers.com/showthread.php?t=2490805

Note 8.0 N5110 Rooting Issue

Hey guys I've been trying to root my tablet all day today. I tried using chainfires one click method with odin. SuperSU got installed but it closes as soon as it opens(I have tried going to the play store but it says SuperSU is a system app and will only let me open). I've no clue what to do at this point. Is there a way I can use odin to go back to stock? Before the 4.4.2 update or better, is there any different root method for 4.4.2?

I rooted my n5110 on 4.4.2 NE2 using Kingo. It takes awhile but worked. I had the same issue with CF-Autoroot.

Alright I'll see what happens. I'll try that

Thanks I'll post results later

Kingo just failed for root

SuperSU still doesn't even open. It closes automatically

Kingo didn't work. CF oneroot with odin didn't work. I have no clue whats going on.

I am having the exact same issue, neither CF-AutoRoot nor Kingo has been successful at getting root access...
on KOT49H N5110.XXDNE1
The thing has resisted my concentrated efforts for two evenings thus far

root with cf-autoroot and try update supersu from here
https://www.dropbox.com/s/x8cr7ytfcqxmlmc/SuperSU 2.01.apk
then launch supersu to update su binary and disable knox notification

memooffon said:
root with cf-autoroot and try update supersu from here
https://www.dropbox.com/s/x8cr7ytfcqxmlmc/SuperSU 2.01.apk
then launch supersu to update su binary and disable knox notification
Click to expand...
Click to collapse
Dude.... I don't even know what to say. You un****ed my tablet lol. Much appreciated. I did have to go into SuperSU and enable it at boot and make it install as a system app. Otherwise when I restart tablet it would keep force closing again

darandster2 said:
Dude.... I don't even know what to say. You un****ed my tablet lol. Much appreciated. I did have to go into SuperSU and enable it at boot and make it install as a system app. Otherwise when I restart tablet it would keep force closing again
Click to expand...
Click to collapse
Don't forget to hit his "Thanks" button.

I have a problem to root my note 5110
It has 4.4.2 and I can't enter in download mode
Do you have an idea to do it (I tried the classical method)?
Thanks

darandster2 said:
Hey guys I've been trying to root my tablet all day today. I tried using chainfires one click method with odin. SuperSU got installed but it closes as soon as it opens(I have tried going to the play store but it says SuperSU is a system app and will only let me open). I've no clue what to do at this point. Is there a way I can use odin to go back to stock? Before the 4.4.2 update or better, is there any different root method for 4.4.2?
Click to expand...
Click to collapse
Use this method :
1. Flash the CF auto root via odin
2. Flash TWRP or CWM recovery via odin
3. Boot to recovery
4. Flash this : http://goo.gl/kpOHVm
5. Reboot
After that, open supersu and update binary + disable Knox.

SuperSU Error after cf-auto

Hi friendly xda android enthusiasts. I have, after many issues, finally rooted my gt-n5110 using odin and cf-auto. Workered without a hitch. Odin passed, tab rebooted, and BAM, "superSU has stopped working". I immediately navigated myself over to the playstore to reinstall SuperSU and for the first time i have ever seen it wouldnt allow me to. It only gave me a choice to open. No update no uninstall. Going into my apps list it was not present on downloads but was available on device list. Clucked it and no option to uninstall, only to force stop or turn off. So it is incorporated as a system with no access to it. This has me stumped. I have only seen old threads with answers to this and they are temp fixes. Need to know what i can do to fix this on a permanent basis and if someone could help me understand how and why this issue occured it would give me a better understanding and possibly prevent further issues. Thanks in advance guys.

Try the flashable version in this post after you install a custom recovery with odin.
ramjet73

ramjet73 said:
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
Click to expand...
Click to collapse
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?

mattdiehl83 said:
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
Click to expand...
Click to collapse
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73

ramjet73 said:
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
Click to expand...
Click to collapse
Doing now. Thankyou. Fingers crossed.

I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Sent from my AT&T Galaxy Note 3 using Tapatalk®

andygev35 said:
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Click to expand...
Click to collapse
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73

OS X
ramjet73 said:
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
Click to expand...
Click to collapse
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?

mattdiehl83 said:
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
Click to expand...
Click to collapse
The recovery? I don't know if there is an OS X version of Odin.
ramjet73

ramjet73 said:
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
Click to expand...
Click to collapse
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X

You could try this: http://forum.xda-developers.com/showthread.php?t=2598203
Sent from my AT&T Galaxy Note 3 using Tapatalk®

done.
Hi guys sorry for the delay in update. I ended up using VM ware and it allowed to operate as windows on OS X. I installed TWRP, went into the file manager in TWRP and removed the superSU, i then flashed superSU and rebooted. Once back to the tablet i went and restored services to superSU and went into the play store. And finally the playstore gave me the option the update the superSU. And then the rest was all normal installation of superSU. Hope this thread helps anybody dealing with these issues.

Glad you got it working. :good:
This post in the CF-Autoroot thread might be helpful as well.
ramjet73

there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root

hmmmm.....
Bordo_Bereli51 said:
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
Click to expand...
Click to collapse
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.

mattdiehl83 said:
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
Click to expand...
Click to collapse
I read all the post and didnt found something
YOU DONT NEED TO DELETE SUPERSU 2.0.1
Install 2.02 apk and go to supersu, then to settings and push to /system
This is the easiest way. the one you found: go to recovery delete that and this. download supersu 2.0.2 apk and install it not the recovery zip i mean the APK! i didnt say the flashable supersu zip.
oh wait, yes you are a intelligent boy, you know everything.

mattdiehl83 said:
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
Click to expand...
Click to collapse
That's a bit of a dilemma.
Unfortunately Samsung does not support using fastboot and bootloader mode (they call it download mode) so that standard SDK tool Google provides for Windows, Linux and MAC OS X isn't applicable. Your best bet would be to find a Windows PC that you can use to flash the recovery with Odin since that is the most common and best documented method.
Edit: NVM, somehow I responded to an old post of yours.
ramjet73