yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] gregsarg:
CF is the best and safest root method. ..

It was purpose built for the device by a developer who doesn't take chances. ..

CF is lean and accomplishes only one purpose. ...root...

Return to stock is painless on this device and this software makes it possible. ..

If you want to do it right. ..use CF auto root...

Once rooted. ..use Odin to flash either CWM or TWRP recovery. ..

Then run yourself a factory rom backup and a copy of your EFS folder and place them on PC for safe keeping. ..

Then your ready to enjoy the great roms we have here. ..

Happy rooting. ...g
[AT&T Samsung Galaxy Note II] drnecropolis:
Many thanks as always for your hard work.

It is much appreciated!
[AT&T Samsung Galaxy Note II] Eddie_Brock:
Will this work with the latest official 4.3 firmware?

I just semi-bricked my device trying install the update, so I'm a little hesitant to try this, but I'd really like root to remove a bunch of added bloatware.
[AT&T Samsung Galaxy Note II] Spacemonkie4207:
Helps if you specify your carrier and model.

There's a link a few pages back for a link to the latest Canadian firmware.

Worked for me on my I337m with Bell csc.

Tripped Knox so my warranty is now void but that's fine with me.
[AT&T Samsung Galaxy Note II] Eddie_Brock:
As it says in my signature, it's a I317M. I'm currently using the official Rogers 4.3 firmware.

I'm glad to see someone else has had success with 4.3. I too am not concerned about Knox at this point.
[AT&T Samsung Galaxy Note II] gregsarg:
Check here for the info...

http://autoroot.chainfire.eu

Looks like other than knox trips...and data wiping if your partition is encrypted ....the root works fine...

But check his site for confirmation...g
[AT&T Samsung Galaxy Note II] LostinCanada:
Please Help! Can't run Titanium Backup Pro or Root Checker since CF-Auto-Root!

Please help! I have the Samsung Galaxy Note II - SGH-i317M. After the recent update to Android 4.3, I downloaded the most recent version of Odin and CF-Auto-Root from the beginning of this thread - instructions followed to the letter and I received a "Pass!" notification and successful re-boot.

When I ran Root Checker to verify root, I got a message that my system seems to be running very slow and Root Checker got stuck in "checking for root". So I cancelled that and ran Titanium Backup Pro. It hung up forever checking root and then finally said it couldn't acquire root privileges.

I was aiming for stock firmware and root - not sure why I'm having trouble this time around as my phone was previously rooted (thanks Chainfire!) on stock firmware and I had no issues.

Suggestions?

Thanks!
[AT&T Samsung Galaxy Note II] LostinCanada:
Ok never mind! Solved my problem! I guess I didn't read ALL the bits and pieces. .. had to reinstall superSU. Now I can run Hola/Pandora in Canada once again. :)

As well, I am now able to use Root Checker and Titanium Backup Pro without issue! :)
[AT&T Samsung Galaxy Note II] kabinoff:
I was able to fully root, remove Knox, etc. Now my issue is the wifi bug...any solutions? it turns on, sees all the networks, just fails to ever connect
[AT&T Samsung Galaxy Note II] geeve420:
Okay so I did a search and read as much as I could. Am I correct in thinking this works on an Att note 2 on official 4.3. I am a little confused, because I had read it kills wifi, then I read it didn't, then I read titanium backup doesn't work etc.

I would like to know if this is way to go. I don't care about knox and the counter. I was at 4.1.2 and my wife updated it this morning without me knowing :(

Thanks

Geeve
[AT&T Samsung Galaxy Note II] geeve420:
Sorry for double post (couldn't edit from the app) it worked. Took some work to get SU working but got it...
[AT&T Samsung Galaxy Note II] TheXclusive814:
I am on the ATT i317 running the 4.3 OTA. Looking into using CF-Auto-Root. Website says it will trip KNOX WARRANTH VOID status. Do we just use TriangleAway to reset that if we ever need to get our phone replaced due to hardware faluire (non root issues)? Or does the KNOX have nothing to due with the flash counter?

My current phone has a bad headphone jack and I reset it before I cal ATT and I may want to runs Rooted Stock when I get my replacement. But still want the need to go back if ever needed for a replacement
[AT&T Samsung Galaxy Note II] mindmajick:
They are different. Triangle away will clear the flash counter but AFAIK there isn't a way to clear the Knox counter yet.

--》Sent from my mind to your screen
[AT&T Samsung Galaxy Note II] Medic24:
So I did the cf auto root but I don't have any options to get into recovery mode I have no way to flash roms with no custom recovery any help would appreciate it
[AT&T Samsung Galaxy Note II] gregsarg:
Flash a custom recovery via Odin. ..

TWRP 2.6.3.1 works nicely. ..

Then use the 3 button combo to boot recovery from the powered down device. ...g
[AT&T Samsung Galaxy Note II] Eddie_Brock:
This has happened twice now, unsure what's going on; after flashing the CF auto root for my device and installing SuperSU, a few days later all my root apps report that they cannot acquire root access. I then have to reflash the file.

I'm on stock 4.3 with untouched recovery, kernel and bootloader.

Ideas?
[AT&T Samsung Galaxy Note II] ShrekOpher:
Have you tried turning on survival mode in the supersu settings?
[AT&T Samsung Galaxy Note II] Eddie_Brock:
Good call, not sure if it was enabled or not. I will reflash the root package and try again.
[AT&T Samsung Galaxy Note II] eboy_gb:
Hmm...so I've used CF-auto root and everything seemed fine (stock recovery) but I can't seem to update superSU? I can only open (not uninstall) it from the Play Store and every time I do try to open it I get the pop up window "unfortunately, SuperSU has stopped".

So what am I doing wrong?:p

EDIT - Never mind, got it sorted out. Did the obvious and flashed a recovery via odin, then went into recovery and flashed an updated superSU zip.
[AT&T Samsung Galaxy Note II] Eddie_Brock:
You failed to mention that this is a PRO-only feature.

Upon attempting to install to /System on my device, I lost root access again, and had to reflash via Odin.

I see that some users have had success flashing via a custom recovery, is this something I should consider next?
[AT&T Samsung Galaxy Note II] Eddie_Brock:
Update: I flashed the latest TWRP, then tried to manually install the latest SuperSU.zip . Upon restarting, my apps are reporting that they are not getting root access. I don't understand what the hell is going on.
[AT&T Samsung Galaxy Note II] Eddie_Brock:
Update 2: TWRP disappeared today too, stock samsung recovery appeared after a reboot or two today.

SuperSU is reporting no root access, even after immediately flashing the ChainFire package...

Is it likely that somehow flashing ChainFire's SU package restored the stock recovery?

Suggestions?
[AT&T Samsung Galaxy Note II] Xenther:
Hey, all! So I'm new to this device, just got it from my S/O two days ago. Also new to rooting (kind of). I have a rooted Moto X, but never played with the bootloader or anything, just on stock with the Moto X. I factory restored the Note 2 I got, and it's on 4.1.2. I rooted it successfully using the method in this thread. Am I able to install custom ROMs now, like ParanoidAndroid, or is there something else I have to do first?

Thanks!

Nevermind! Did a Nandroid backup and just flashed PAC. Thanks so much for this easy root! So much easier than Moto X was!
[AT&T Samsung Galaxy Note II] xuanphucn:
would this method trip my knox status on 4.3?
[AT&T Samsung Galaxy Note II] gregsarg:
Yes....

Knox will be tripped....g

Sent from my NOTE 2.750...

Courtesy of our amazing developers...
[AT&T Samsung Galaxy Note II] xuanphucn:
any idea if the vroot method would trip my knox status also?
[AT&T Samsung Galaxy Note II] gregsarg:
Don't know about vroot....but given that the exploit is achieving the same outcome.....the risk is roughly the same...

With Knox and it's aggressive nature toward tampering at the root level....the risk of Knox being tripped is high....

User beware....as root will get you inside of the device....taking your warranty with it...

For Samsung devices....the days of returning devices to stock are over....unless a significant breakthrough is achieved in the future....g

Sent from my NOTE 2.750...

Courtesy of our amazing developers...
[AT&T Samsung Galaxy Note II] royalh:
Just a thought here, but when you are able to get root, do you let SuperSU turn off the Knox security?
[AT&T Samsung Galaxy Note II] Eddie_Brock:
Sorry, I forgot to post back here... I did a titanium backup of all my apps, factory reset, then flashed a pre-rooted ROM.

I haven't had any issues with losing root since.

Thanks for your suggestion regardless.
[AT&T Samsung Galaxy Note II] willyghost:
need help please

Hi guys,

I have the i317, i followed the guide and now i dont understand, first i rooted then installed the twrp recovery via odin. The phone showed me the TWRP recovery and then reebot and now i always get an error saying SUPERSU has stopped. Now the worst part is I Cant Access Doenload Mode with the 3 finger salute. It just shows sansung logo and boots. I also cannot access WIFI ??? Please Help Me dont know what to do...
[AT&T Samsung Galaxy Note II] toanau:
Custom recovery and super user does not work.
[AT&T Samsung Galaxy Note II] nickfar2000:
Man I hate this its like as soon as I think I got everything read and am ready to root my fiance's i317 on MK6 4.3, I read that something that tells me now it doesn't work, we don't care about whole Knox warranty deal, but after reading the past couple pages it looks as if people are having probs just rooting with stock recovery, so confused, I thought this CF Root exploit via Odin, then update Super SU and it kills Knox and your good to go; minus warranty of course. Does anyone know THE BEST way to root this phone on 4.3 without having issues?
[AT&T Samsung Galaxy Note II] mindmajick:
This would be the best way.

I'm on 4.3 rooted stock and cf-auto root works for me every time.

As you said- flash with Odin and it just works.

Pm me if you need help.

-》Sent from my mind to your screen.
[AT&T Samsung Galaxy Note II] gregsarg:
This..^^^^^^^^.....g
[AT&T Samsung Galaxy Note II] shawn0223:
question

I'm considering picking up a note 2 for $100, I can't seem to find anything that confirms that the boot loader its on can be rooted and if I can flash a custom recovery/ Rom. Can anyone confirm if this cf root will work on the baseband and if I can flash a recovery/ Rom. I wanted to be absolutely sure this was possible before buying, specially with Knox and the way Samsung/AT&T have been locking down phones. Baseband version below.

Baseband version I317UCAMH3

Thanks in advance guys
[AT&T Samsung Galaxy Note II] ShrekOpher:
If you don't mind voiding the warranty then it's all good. Root deknox and enjoy.
[AT&T Samsung Galaxy Note II] shawn0223:
Nah. Don't care for the warranty. Just don't want tw on the phone lol. That's why I wanted to be sure that boot loader wasn't locked to where i can't flash anything
[AT&T Samsung Galaxy Note II] willblake13:
If it is working on MK6, MH3 will be a walk in the park. Chainfire doesn't release anything less than perfection. ;)
[AT&T Samsung Galaxy Note II] gregsarg:
Awesome...

It's not truly yours until it's rooted and performing to your satisfaction...

CF will get you rooted just fine...g
[AT&T Samsung Galaxy Note II] equlizer:
Well ive used this before to get root and now all of a sudden its not working :( It goes through the flash process and the red android comes up and says its doing its thing and the flash counter goes up but thats about it. I can't seem to get root on 4.1.2 again.

I used to be on 4.1.2 then rooted with this method to get to 4.1.1 to unlock. Then updated back to 4.1.2 now i cannot root anymore :(

I tried 3.07 and 3.09 and 1.85. Still no go.
[AT&T Samsung Galaxy Note II] momchi:
confirmed working on SGH-i317 ATT BMK6 Android 4.3

Ok, confirmed working flawlessly on SGH-i317 (ATT NoteII) on Android 4.3 Baseband I317UCUBMK6

(!) This has the new bootloader and I was a bit nervous with CF-Auto-root running the reboot and stock-recovery replacement (as some complained that TWRP recovery was left un-removed after the whole process completed). But, I tested it later -- original "recovery" is there.

The process went very smooth, (there is about a 20-30 sec delay before you see the CF-Autoroot echo lines), it rebooted the deice perfectly and root checker verified that it was indeed rooted.

Status of device in settings does show "Modified" (I am fine with that). Have not run "triange away" as I don't care about it.

(!) Now, after reboot you WILL GET message (from KNOX?) a nagging pop up message saying that "An attempt to access your phone's secure area was blocked". And I did get "SuperSU" binary failed message box. But, after installing the update from Google Play (yes, SuperSU is different from "superuser" app, and it should say "Chainfire" as author) all is cool. SuperSU asked me if I wanted to disable KNOW, which I said yes, and it reported successful (de-KNOX-ing :)...

:laugh::good:
[AT&T Samsung Galaxy Note II] Deevusone:
odin3.ini file

Hi,

In the Odin zip file from the link that was provided by the OP in his 2nd post, there's a odin3.ini file.

In the CF-Auto-Root zip file for the i317m model, there's also a odin3.ini file, but the parameters in this file differs from the .ini file from the Odin zip file.

Which odin3.ini file should i be using? the one from CF-Auto-Root? or the original one from the odin zip file?

I basically extracted both zip files into one folder, or should i extract each zip file into its own separate folder?
[AT&T Samsung Galaxy Note II] snowin:
Will this still work to root if I flash the new Stock 4.4.2 Firmware (I317MVLUDNF1)? Just want to make sure.

Thanks,

~snowin
[AT&T Samsung Galaxy Note II] equlizer:
what can i use to root afterwards?
[AT&T Samsung Galaxy Note II] dgerryts:
Confirmed working on Telus I317m on stock KitKat 4.4.2
[AT&T Samsung Galaxy Note II] chris19000:
Tried with same device only encrypted. No go. Asks for encryption password, accepts, then shuts down and stays dead until you turn back on. Tried so far - reset, pull battery reset, wipe cache reset, nothing yet. Few more things to try.

Edit: Re-flashed it, little android unlock dude stayed up a little longer this time after putting in passkey but went back to dead screen again. Phone is not actually shut down though as I had thought, when I plugged in while dead the pc recognizes it being plugged in, just no connection. Don't want to do FR but need the phone. Will report back.
[AT&T Samsung Galaxy Note II] chris19000:
Tried Safe mode, then re-flashing 4.4.2 update over top hoping it would overwrite whatever was locking it out during unencryption on start up but didn't work. Ended up having to do factory reset after all. Oh well, hopefully this will save someone else the time of trying it out. Some threads in other dev forums that were working on this and seems like a work around with a questionable rooting method gave success to some others but in either case can't work with just this for now so if you have security settings for work email access or something that require encryption this is not for you - especially when your boss is trying to call you on your dead phone while you are figuring it out :o
[AT&T Samsung Galaxy Note II] 06SilveradoZ71:
Just wanted to let everyone know that this works on 4.4.2 at&t stock rooted no problem thanks

---------- Post added at 07:54 PM ---------- Previous post was at 07:48 PM ----------

I like white better 2 lol
[AT&T Samsung Galaxy Note II] dmxsoulja3:
With this, is it going to unlock the bootloader, so I'm going to lose my data? I am trying to root 4.4.2 to run things like Greenify and get battery stats back again. I still suffer from wakelocks and have yet to narrow it down, it isn't an app, it ends up being either the mdm_ one or the wifi wake locks, and its getting frustrating trying to figure out without access to the battery stats anymore
[AT&T Samsung Galaxy Note II] 06SilveradoZ71:
You dont loose data when you run cf auto root
[AT&T Samsung Galaxy Note II] dmxsoulja3:
Appreciate that info! I will give it a go tonight
[AT&T Samsung Galaxy Note II] 06SilveradoZ71:
So did you gain root?
[AT&T Samsung Galaxy Note II] marckusdavis:
Sorry, I need to make sure I fully understand this too. So you have an SGH-i317 and were rooted. You installed the OTA update to 4.4.2 which unrooted you. Then you ran CF-AutoRoot and were able to successfully re-root on 4.4.2?

UPDATE:

Well, after reading another post where this worked, I decided to give it a try. It seemed to work, but then I get the message "Unfortunately SuperSU has stopped". I tried the solution using ES File Explorer to reinstall SuperSU.apk to no avail and there is no "UPDATE" button in Google Play, only OPEN, ENABLE or DISABLE so I can't update the binary. Any help would be greatly appreciated!

UPDATE 2:

Got it working, sort of! Since rooting seemed to work, but the old binary for SuperSU kept stopping, I downloaded the updated SuperSU zip file from here and then used ES File Explorer to look into the zip and find and run/install the Superuser.apk file. That works, but it does not appear to survive a reboot, so for each reboot I have to redo this process. Good enough work-around for now though as I'm sure there will be a complete solution down the road.

UPDATE 3 (probably final):

Was able to use the "Clean up for reinstallation from Google Play" option in the SuperSU settings. After reboot, Google Play then gave me the option to Install SuperSU which I did. It now survives reboot and it also, FINALLY, disabled the stupid Knox (which from what I read, was the cause of all of these problems in the first place. You have to be quick with the fingers though because as soon as SuperSU gave the option to disable Knox, a second later Knox closed it. I had to fire up SuperSU again and then click the disable Knox OK button IMMEDIATELY to kill it). I'm a happy, rooted Note 2 user on KitKat now! Hope all of this info. is helpful to someone else.
[AT&T Samsung Galaxy Note II] dmxsoulja3:
So far this method is working for me, I just got the new SuperSU apk loaded, and it updated, and now its trying to disable KNOX, I don't know how long its supposed to take but its been running for a few minutes.
[AT&T Samsung Galaxy Note II] gregsarg:
Once your root is established and working...(Knox disabled of course )...download SELINUX mode changer apk from the play store and set your kernel SE status to permissive....

Otherwise...you may continue to have root issues...

And if you just want to bypass Selinux altogether...you have the option to flash Agni kernel which is set permissive anyway...

Glad you are rooted and rocking the kitkat note 2....g
[AT&T Samsung Galaxy Note II] DoctorQMM:
g - this is good info... thanks. Q: can SELinux status be "turned off" in KK roms like it could in 4.3 (MK6 AT&T)? just going by my system status on SkyNote rom (MK6/MJ4 hybrid rom) which had stock kernel... SELinux status is "turned off"... so not sure if that is same as "permissive".
[AT&T Samsung Galaxy Note II] dmxsoulja3:
Downloaded and ran the app, thanks for the info. So far no issues, I was able to update SuperSU and disable KNOX, the only thing I'm not sure of is if it is disabled, I'm not getting any notifications, but I do still see some of the files running in cached processes. Is there anything I should be turning off or freezing with KNOX, or if SuperSU ran and did its this I'm good?
[AT&T Samsung Galaxy Note II] marckusdavis:
Glad you're finally rooted! I went in with Titanium Backup and froze all KNOX stuff (as well as all the bloatware) except for KNOX VPN. I wasn't sure if that would be safe, so I've left it. I don't show any KNOX processes running at the moment.
[AT&T Samsung Galaxy Note II] gregsarg:
Freezing the Knox components would be my suggestion as well...using titanium backup...g

---------- Post added at 07:51 PM ---------- Previous post was at 07:38 PM ----------

Well...not exactly the same Doc...but with basically the same effect...

The stock kernel set to "permissive" allows the user to interface the kernel without limitations...but SElinux is still technically running within the kernel...

On Agni kernel...the dev has effectively "shut down" the SElinux function within the kernel...or even removed it entirely...

With a stock kernel showing a "turned off" state...I would think the developer has done the same modification to the stock kernel as well...

And based on my recent permissive state being set with the new NE5 update...I can see no difference between this newer build versus the 4.3 kernel "permissive" state...

I'm not a kernel guy Doc...but that's my best description of the process...

Please feel free to correct me if you see it happening otherwise...g
[AT&T Samsung Galaxy Note II] bobiscool07:
I have an untouched SGH-I317M on Koodo, OTA updated to the latest 4.4.2 ROM. Will this method work on my device? Or do you think this device has a locked bootloader?
[AT&T Samsung Galaxy Note II] force70:
Ive yet to see a canadian sammy device with a locked bootloader. Knox yes for sure but no locked bootloader. My i317m is also 4.4.2..got another ota the other day also....its my work phone so its not even rooted but i think that's going to change soon lol.

sent from my Canadian Note, Note 2 or S4
[AT&T Samsung Galaxy Note II] bobiscool07:
I get "unfortunately SuperSu has stopped working" and the application appears as an android in the app drawer. I cannot launch it either without crashing. Root checker says I have no root. The device went through everything fine, and rebooted itself and installed. Not sure what the next step is.

Edit: Installed the apk seprately, and it loaded SuperSu - but if I reboot I goes back and I have in reinstall the apk. I have root once I reinstall the apk every reboot.... the app [MENTION=3927388]gregsarg[/MENTION] mentioned "download SELINUX mode changer apk from the play store and set your kernel SE status to permissive" says is changed to permissive - but when i check settings or relaunch the app, its still at enforcing..
[AT&T Samsung Galaxy Note II] force70:
Which version of odin are you using? I hope not 1.85

sent from Canada via my Note 3, Note 2 or One X +
[AT&T Samsung Galaxy Note II] bobiscool07:
I used the one that was included in the link to the CF-Auto link, and not the attached file. v 3.07
[AT&T Samsung Galaxy Note II] force70:
Try 3.09.....best for the latest software.i had to use it to go from 4.3 to 4.4 on my note 3

Use the AP button..pda is gone on 3.09.

sent from Canada via my Note 3, Note 2 or One X +
[AT&T Samsung Galaxy Note II] force70:
All good...bit of a pain to get supersu working but no biggie.check post 291..good info there.

sent from my Canadian Note 3, Note 2 or S4
[AT&T Samsung Galaxy Note II] bobiscool07:
Thanks, I went into the options after manually installing the apk, and selected "install as system app", after a reboot it was fine. Factory reset it and everything is still good - except that its still on enforcing and not passive.
[AT&T Samsung Galaxy Note II] force70:
Use the app recommended on the other post..i did and working perfect.

sent from Canada via my Note 3, Note 2 or One X +
[AT&T Samsung Galaxy Note II] bobiscool07:
I used this app that matches the name mentioned. I get a notification that it was changed to passive after granting it root access. When I go into settings to verify, its still on enforcing. When I relaunch the app again, it too has gone back to enforcing enabled.
[AT&T Samsung Galaxy Note II] Drahkarg:
I'm at a complete loss. On all levels, using Odin 1.85, 3.07 and 3.09, everything seems to go well. All programs report a PASS. It goes into the recovery and does its thing (I think, I go to a red Odin screen and a status script runs). Android upgrades. SuperSU crashes, every single time and Root Checker reports no root. I feel like I just got my first S2 again, and it's really irritating. Anyone have any suggestions? Something I may have missed?

Supersu is present, it just shoots itself in the head before doing anything useful.