Develop Bugs

[Q] SGH-I317M with KNOX can not be rooted

Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.

Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203

Stewegg said:
Can't even start SuperSU
Click to expand...
Click to collapse
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3

VeeDaub said:
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3
Click to expand...
Click to collapse
Where is the Reactivation Lock located?
I can not find it in the Security Settings.

mrevankyle said:
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203
Click to expand...
Click to collapse
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?

Stewegg said:
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?
Click to expand...
Click to collapse
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
Link to philz recovery tar for our phone i317M
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/philz_touch_6.19.3-t0lteatt.tar.md5

Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk

Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
Simple. First get the root. Like the su binary and stuff. once you are rooted get suersu. What I mean by first get root is literally get root through a program or something. After this you will have root but you wont have root access. So get supersu now and launch the app. It will ask to update your su binary. Say yes. then the thing will say something about knox then ask you if you want to try to disable knox. Tap yes and knox should be disabled and your su binary should be updated and working.

I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:

My phone is I317M Rogers, it run stock 4.3. I followed this guide, http://forum.xda-developers.com/showthread.php?t=2618261 rooted success.

Eun-Hjzjined said:
Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk
Click to expand...
Click to collapse
ifentanez said:
I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:
Click to expand...
Click to collapse
koodiifin said:
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
......
Click to expand...
Click to collapse
koodiifin's way worked perfectly!
Thank you koodiifin!

[GUIDE] how to root Sph-L710/L710T S3 4.4.2 (updated as of 8/19/2015)

I'm sorry i had the wrong links and because of this i had miss information. So i formally apologize by updating with the proper links.
this first method doesn't work with the Sph-L710T or the Sph-L710 on NJ2/NJ3
First method: You can root the stock 4.4.2 ND8/NDC:laugh:
1st. Make sure your on 4.4.2 ND8 or NDC
2nd. Download Towel Root
3rd. Place Towel Root in sdcard or internal storage
4th. With any file manager find and install Towel Root
5th. Open Towel Root and well root
6th. Go to play store and download https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and also https://play.google.com/store/apps/details?id=stericson.busybox&hl=en let super user update the binary
7th. Flash any recovery you want {personally i went with PhilZ Touch (this was before PhilZ had a root Option)}
8th. Enjoy your rooted stock 4.4.2 ND8/NDC
Down below is one more way too root Stock ND8/NDC/NJ2/NJ3 or NF4/OA3 (L710T) and basically any other update
(link to the almighty ODIN)
Second Method: mostly recommended
1st. Odin flash TWRP
2nd. In Odin choose PDA, PA or AP then select the TWRP Tar you just downloaded
3rd. Make sure Auto reboot is unchecked (also at this time your s3 should be in download mode)
4th. Hit start and let Odin let it finish!!
5th. Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery
6th. now your in TWRP
7th. so to root your stock rom with TWRP flash the following file SuperSU.zip by Chain fire (pro tip. Install any other custom recovery the same way I did for TWRP above if it is in .tar format)
and here is Philz recovery for the D2Lte 6.48.4 ( which you must flash in TWRP)
and here is TWRP that was made specifically for the D2Rephersher/triband/L710T TWRP (which you must flash in a recovery)
Third method Most recent.
Hidyman said:
This is in reference to Samsung Galaxy S3 for Boost Mobile SPH-L710.
Just want to let anyone out there that updated their Boost S3 to L710VPUC0J1 know that you can still root and/or ROM your phone.
Use the instructions to (use Odin to) update the recovery to TWRP first (in the second set of instructions). I had trouble trying to go right to PhilZ Recovery (which I believe is based off of ClockWorkMod). I Had to do the TWRP (twrp-2.8.7.0-d2spr.img.tar) first.
It was the only way to get it to actually accept the recovery, not sure why, maybe because the latest Samsung firmware fixed an exploit or two.
This is an older phone, but it is still a viable one.
I hope this helps someone out there.
It took me a while to figure this quandary out.
As always this WILL flag KNOX, but I'm sure this won't be an issue at this date and time (8/2016).
Click to expand...
Click to collapse

work on ND8 rom? sprint phone?

Tekone said:
work on ND8 rom? sprint phone?
Click to expand...
Click to collapse
i want to say yes but towel root does come with a warning that it might brick your device.....but i want to say yes since most things that can be done to the ND8 can be done to the NDC and also in reverse order.....so try it and report back it will be good to know if it works on both bootloaders

Sprint S3 Android 4.4.2 ND8-It works!
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!

oops
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.

henhun said:
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
Click to expand...
Click to collapse
ND8 or NDC? have you tried updating your profile/PRL?

6th_Hokage said:
ND8 or NDC? have you tried updating your profile/PRL?
Click to expand...
Click to collapse
Ya know. People keep talking about ND8 and ND___. I have no idea what that means. I know I should be embarrassed.
UPDATE: FIGURED IT OUT, BASEBAND VERSION. GOTCHA. IT IS NDC.
I was JUST coming back to update my post. I DID update the PRL and restarted my phone. That seems to have done the trick. Thank GOD I got my data connection back!! It worked. Even though I found the info somewhere else, thank you so much for the quick reply. PRL update fixes the problem. You're awesome.

I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app

jbnorton0524 said:
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
many users of basically the same phone report different things with every root method out there. If it worked for you that's great tell other users what you did for it to work and if it didn't work, then ask for help and you will get help; some people don't have success with any method while others do with all of the methods.....my phone falls under every method.....

Successful Towelroot on VM Galaxy S3 4.4.2.NDC
6th_Hokage said:
you can root the stock 4.4.2
first step make sure your on 4.4.2
second step download Towel Root
third step place Towel Root in sdcard or internal storage
fourth step with any file manager find and install Towel Root
fifth step root
sixth step go to play store and download Superuser (Chainfire) and also Busy Box (Stericson) let super user update the binary
seventh step flash any recovery you want personally i went with Philliz Touch
eighth step if you want flash a custom rom now if not enjoy your rooted stock 4.4.2
Click to expand...
Click to collapse
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is usafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave

dave260 said:
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is unsafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
Click to expand...
Click to collapse
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the binary (<---completely forgot to fix that) you must hit the option normal not TWRP/CWM

churninern said:
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
Click to expand...
Click to collapse
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.

Darkangels6sic6 said:
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Click to expand...
Click to collapse
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all

Knox Counter and "Device Status"
6th_Hokage said:
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the recovery you must hit the option normal not TWRP/CWM
Click to expand...
Click to collapse
Thanks for your response. I may be over thinking these indicators. All I did was Towelroot, successfully. On the phone, the "About Device, Status" now says CUSTOM (was "Official"). The Knox counter according to app "Phone Info" shows Knox Counter at 0x0. As you said, since the counter is not tripped, should be no problem on warranty. So then Device Status CUSTOM is not a problem? I'm not really worried about warranty at this point, but I think I'll hold off further mods for another 6 moths.
Thanks again for your help!

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
Thanks. I tried the md8 and mk3 "mk3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all.
I'm guessing maybe I should install twrp. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most md8 Roms want you to odin or flash an md8 base.

Darkangels6sic6 said:
Thanks. I tried the ND8 and MK3 "MK3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all
I'm guessing maybe I should install TWRP. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most ND8 Roms want you to Odin or flash an md8 base.
Click to expand...
Click to collapse
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
6th_Hokage said:
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
Click to expand...
Click to collapse
I was afraid you would say that.

Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!

strangelady said:
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
Click to expand...
Click to collapse
your welcome strangelady and if you want check out the links in my signature area for other cool stuff

added two more t=root methods

[Q] I747MVLUFNF2 Root

So I recently updated to the I747MVLUFNF2 update in Kies from the I747MVLUFNE6 Update and I can't seem to root it using towelroot (I keep getting a phone unsupported message). Is there another method to root the phone without tripping KNOX?

Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.

DocHoliday77 said:
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
Click to expand...
Click to collapse
I understand once I root it with CF Auto Root then the warranty bit is tripped, but does this prevent me from using my phone with kies to update or backup? Or what exactly happens?

It just means you cannot use Knox for secured storage. The vast majority of us hate knox anyway so you might actually call this a win!
Of course it also means they can refuse warranty services, but most never need this, and many have reported their warranty being honored regardless.
Otherwise, it has no other effect on how you use your device, flash roms, root, etc.

I have the same issue.
I don't care about knox... but rooting it with the other ways that I know installs the super user app properly but then the SU app keeps crashing... I was assuming it was because of knox but now I'm not sure anymore, tried to reset it and to reflash the rom twice and every time it did the same thing...
Do you have any ideas why that might be happening?
I really would need a solution as I hate unrooted 4.4.2... :S
Thank you!

After rooting, you should be able to open SuperSU and it'll update its binary if needed and will disable knox.
Did you do that part?

I did try to update SU... The result was the same... the SU app would crash when I tried to launch it, before it even gives you the screen to disable knox... Trying to download the slightly older I747MVLUFNE6 which hopefully will root better...

You cant downgrade firmware. You could flash a rom, but i dont think that's what you were getting at.
How did you try to root? Have you tried using the oldest method we've got? Seems to never fail when others do!
Flash custom recovery with Odin.
From recovery flash the SuperSU update zip. You can find it by going to chainfires thread. (Its also in my sig bit I haven't added the very latest version yet)

Yeah, I realized my stupidity after posting the last message... I was thinking of flashing the older rom in... but that would have crapped out...
Finally got it to work...
Thought I had tried it before... but now I kind of doubt myself >.>
Reflashed the same version of the rom ... Found a really old version of auto-root, flashed it in... then I could update SuperSU and it disabled Knox...
Should have tried a bit harder before posting... sorry about that...
Thank you very much for your help.

Bob Terwilliger said:
Yeah, I realized my stupidity after posting the last message... I was thinking of flashing the older rom in... but that would have crapped out...
Finally got it to work...
Thought I had tried it before... but now I kind of doubt myself >.>
Reflashed the same version of the rom ... Found a really old version of auto-root, flashed it in... then I could update SuperSU and it disabled Knox...
Should have tried a bit harder before posting... sorry about that...
Thank you very much for your help.
Click to expand...
Click to collapse
Hi Bob
please witch version of auto-root have you use ?

The one I used was hard to find. Most people only post a link to Chainfire's website when making a rooting tutorial. This was a problem because Chainfire updated his official auto-root release with the latest SuperSU apk, making it impossible to update...
http : // androidxda . com / root - samsung - galaxy - s 3 - sgh-i747m
(can't post links yet, apparently...remove all spaces from previous line after copying it to address bar)
The guy from the above website decided to go the longer way of uploading an auto-root that he re-zipped himself. Not sure why he did that but it was perfect for what I needed.
Just download and unzip the auto-root that he provided and you'll be able to root your 4.4.2 SGH-I747M.

Bob Terwilliger said:
The one I used was hard to find. Most people only post a link to Chainfire's website when making a rooting tutorial. This was a problem because Chainfire updated his official auto-root release with the latest SuperSU apk, making it impossible to update...
http : // androidxda . com / root - samsung - galaxy - s 3 - sgh-i747m
(can't post links yet, apparently...remove all spaces from previous line after copying it to address bar)
The guy from the above website decided to go the longer way of uploading an auto-root that he re-zipped himself. Not sure why he did that but it was perfect for what I needed.
Just download and unzip the auto-root that he provided and you'll be able to root your 4.4.2 SGH-I747M.
Click to expand...
Click to collapse
Using the zip you provided, which version of SU did you use?

The auto-root tar in the zip the guy provided on his site is dated 2014-2-27 11:13.

Bob Terwilliger said:
The auto-root tar in the zip the guy provided on his site is dated 2014-2-27 11:13.
Click to expand...
Click to collapse
i have tried this one but it doesn't solve my problem, SuperSU crashed when it start, i don't understand what is the cause :crying:

It'll work... SuperSU crashing is normal... you need to go to the play store and update SuperSU... after that you'll be able to run the app and disable Knox.

Bob Terwilliger said:
It'll work... SuperSU crashing is normal... you need to go to the play store and update SuperSU... after that you'll be able to run the app and disable Knox.
Click to expand...
Click to collapse
thanks bob, i discover that the problem was about the I747MVLUFNF2 rom, so I changed it by I747MVLUFNE6 and all ok now
thank you again :good:

I did the opposite. I flashed the latest version of CF-Auto-Root from http://autoroot.chainfire.eu/. SuperSU was crashing, so I re-flashed the latest version of SuperSU (v2.01) from http://download.chainfire.eu/supersu and it worked fine after that. This was on the I747MVLUFNF2 ROM.

DocHoliday77 said:
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
Click to expand...
Click to collapse
I've also updated to the latest firmware for gs3-1747m and tried to root using these new rooting tools that are on the device itself. Can you elaborate on an older version that would work on the device? My data pins on the mico-usb port were damaged, so I cannot transfer any data with a PC. Can't use Odin or other devices that require USB debugging
Thanks!

If Towelroot doesn't work, there is no other way to root without using Odin and a PC.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

hey
aryan.yazdani said:
I've also updated to the latest firmware for gs3-1747m and tried to root using these new rooting tools that are on the device itself. Can you elaborate on an older version that would work on the device? My data pins on the mico-usb port were damaged, so I cannot transfer any data with a PC. Can't use Odin or other devices that require USB debugging
Thanks!
Click to expand...
Click to collapse
Actually... PM me, I'll tell you how I did it.

PH4 root?

Hi,
How do I root ph4? I was going to use the chainfire method but they don't have ph4 listed.
Also does anyone know anything about hotspots for it? I got my phone refurbished after my old one broke so I cannot do the old MSL trick that the bastards greyed out.

piggynuts said:
Hi,
How do I root ph4? I was going to use the chainfire method but they don't have ph4 listed.
Also does anyone know anything about hotspots for it? I got my phone refurbished after my old one broke so I cannot do the old MSL trick that the bastards greyed out.
Click to expand...
Click to collapse
Try to use chainfire auto-root.
PG1,PE2,PE1 weren't listed but it works for them and I think it will work for PH4.
Sent from my SM-N910P using Tapatalk

piggynuts said:
Hi,
How do I root ph4? I was going to use the chainfire method but they don't have ph4 listed.
Also does anyone know anything about hotspots for it? I got my phone refurbished after my old one broke so I cannot do the old MSL trick that the bastards greyed out.
Click to expand...
Click to collapse
Yea cf autoroot still works with ph4 i allready tested it but after flash cf autoroot in odin my device reboot 3 times but it works.

Trex888 said:
Yea cf autoroot still works with ph4 i allready tested it but after flash cf autoroot in odin my device reboot 3 times but it works.
Click to expand...
Click to collapse
Sweet thanks, for cf root what do I do ? There is a big list of models and none match my firmware.

piggynuts said:
Sweet thanks, for cf root what do I do ? There is a big list of models and none match my firmware.
Click to expand...
Click to collapse
Download this works for me on sprint note 4 n910p
https://download.chainfire.eu/585/CF-Root/CF-Auto-Root/CF-Auto-Root-trltespr-trltespr-smn910p.zip

I can confirm that version of cf works on PH4.

Hello I just got a note 4 for Sprint. How do I know which version I have? I want to root. Thanks. I'm on 6.0.1

Trying to root on PH4
PH4 Marshmallow TAR: N910PVPU4DPH4_N910PSPT4DPH4_SPR.zip
md5: 2644201b1b9e5eb47e6dc9ba9e1172ff
Downloaded this update and flashed it with Odin
Worked great
Now needed to get root back, tried chainfire auto root (samsung SM-N910P), get stuck in boot loop.
Tried it twice, get to the screen with the red android man with a patch over his eye and says going to recovery, but just loops
Did verify that have correct checksums.
Any suggestions?
----> Solved ------------------------------
Installed [ROM][6.0.1] Stock PH4 | De-bloated | DeoDexed | N910PVPU4DPH4 [10/3/16]
Directions were slightly confusing to me, but eventually I got into recovery via Odin and then installed the above mentioned ROM and it gave me rooted access.
I thought I needed root access before installing a ROM, but did not.
This Worked =), so far so good. Enjoying the ROM.

Just got pushed an Update.

Any idea what's in the new update that's rolling out?
Sent from my SM-N910V using XDA-Developers mobile app

My mom was also pushed an update yesterday. Havnt read anything about it yet

Darca said:
Any idea what's in the new update that's rolling out?
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks like a security update but thanks for the heads up. If you are unlocked and rooted I made a safe upgrade to PJ2. I removed aboot and the stock recovery so it's safe to flash.. Grab it here if you want to flash it with Odin. This is stock so you will need to flash supersu after it reboots to recovery mode and then after you reboot you will need to remove the OTA updater and bloat.
EDIT: Here is the update for the Non Rooted Retail version DO NOT flash this if you want to stay rooted and unlocked!!
View attachment 3964458

Misterxtc said:
Looks like a security update but thanks for the heads up. If you are unlocked and rooted I made a safe upgrade to PJ2. I removed aboot and the stock recovery so it's safe to flash.. Grab it here if you want to flash it with Odin. This is stock so you will need to flash supersu after it reboots to recovery mode and then after you reboot you will need to remove the OTA updater and bloat.
EDIT: Here is the update for the Non Rooted Retail version DO NOT flash this if you want to stay rooted and unlocked!!
View attachment 3964458
Click to expand...
Click to collapse
I took the update over-the-air on my unrooted Note 4 and the IR Blaster stopped working. The phone was only a week old and I I'm sending it back to eBay for a refund. Did anyone have any problems with their IR blaster?

doctor-cool said:
I took the update over-the-air on my unrooted Note 4 and the IR Blaster stopped working. The phone was only a week old and I I'm sending it back to eBay for a refund. Did anyone have any problems with their IR blaster?
Click to expand...
Click to collapse
Bummer, I haven't had a problem with mine.

Misterxtc said:
Bummer, I haven't had a problem with mine.
Click to expand...
Click to collapse
I used Odin to flash your PJ2_Stock_Restore on a different/ rooted note 4 and it worked. Only thing was it put that quick connect drop down in the notifications. I re-flashed your PJ2_Stock_Restore using FlashFire, System and Cache only and it removed the drop down. I don't know why? So it worked both ways but I liked the results better with FlashFire.

doctor-cool said:
I used Odin to flash your PJ2_Stock_Restore on a different/ rooted note 4 and it worked. Only thing was it put that quick connect drop down in the notifications. I re-flashed your PJ2_Stock_Restore using FlashFire, System and Cache only and it removed the drop down. I don't know why? So it worked both ways but I liked the results better with FlashFire.
Click to expand...
Click to collapse
I noticed that too and do not like it. I didn't mod it at all other than removing the stock recovery and aboot. Now I wonder if removing the stock recovery is causing the issue... I'll make a new one with the stock recovery and see if that fixes it.

doctor-cool said:
I used Odin to flash your PJ2_Stock_Restore on a different/ rooted note 4 and it worked. Only thing was it put that quick connect drop down in the notifications. I re-flashed your PJ2_Stock_Restore using FlashFire, System and Cache only and it removed the drop down. I don't know why? So it worked both ways but I liked the results better with FlashFire.
Click to expand...
Click to collapse
I'm pretty sure not adding the stock recovery added the quick launch. Here is another with the stock recovery, I tried it and didn't have the quick connect after a factory reset.
VZW_PJ2_DEV_ED_Stock_Restore

Misterxtc said:
I'm pretty sure not adding the stock recovery added the quick launch. Here is another with the stock recovery, I tried it and didn't have the quick connect after a factory reset.
VZW_PJ2_DEV_ED_Stock_Restore
Click to expand...
Click to collapse
I had also taken out the recovery from the one you posted above, but I didn't get the quick connect in the notification drop down. I wonder if the csc isn't getting added. When I was playing around with the data fixes I noticed that if you take the customer.xml out of the mix it changes a bunch of stuff and adda that quick launch.

My wife is using this phone on the Rogers network up here in Canada. Other than being carrier unlocked, it is completely stock. I know that before she inherited it from me, I had manually updated it a couple of times with the stock recovery.
Although it was two phones ago, I'm sure I can figure out how to update with these latest patches. Can someone please tell me which, if any, of the above listed links can be safely used to update the phone with the stock recovery without root or tripping knox?
Any help would be greatly appreciated..

crutzulee said:
My wife is using this phone on the Rogers network up here in Canada. Other than being carrier unlocked, it is completely stock. I know that before she inherited it from me, I had manually updated it a couple of times with the stock recovery.
Although it was two phones ago, I'm sure I can figure out how to update with these latest patches. Can someone please tell me which, if any, of the above listed links can be safely used to update the phone with the stock recovery without root or tripping knox?
Any help would be greatly appreciated..
Click to expand...
Click to collapse
If it's the 910V use this file if you are NOT and will not be rooting or flash this one if you rooted and unlocked. Do a factory reset after you flash either of these with Odin.