Database Users

Need help with rooting Rogers Galaxy S4 I337M

So first off, I am have a lot of questions that I might as well ask.
First, will rooting my Rogers Samsung Galaxy S4 I337m mess anything up with the carrier? Like, will i still be able to call and text, etc?
Secondly, can my carrier track that I have a rooted phone?
And this is the most important question, how do I actually root this phone? Most of the methods I have tried don't work because the security app "KNOX" keeps denying access for the root to happen. I have tried many ways to remove KNOX from the phone, but none of them work....So how do I actually root this phone without having KNOX shut me down?
Anyways, thanks for the help!

Pellisco said:
So first off, I am have a lot of questions that I might as well ask.
First, will rooting my Rogers Samsung Galaxy S4 I337m mess anything up with the carrier? Like, will i still be able to call and text, etc?
Secondly, can my carrier track that I have a rooted phone?
And this is the most important question, how do I actually root this phone? Most of the methods I have tried don't work because the security app "KNOX" keeps denying access for the root to happen. I have tried many ways to remove KNOX from the phone, but none of them work....So how do I actually root this phone without having KNOX shut me down?
Anyways, thanks for the help!
Click to expand...
Click to collapse
So ...based on the question, and the fact that this is your first post, it appears you have a fair bit of reading to get through before doing it but yes the phone does everything rooted as it did before, you just have access to the whole file system (which means you will have the ability to break things that were "roped off for your protection" before rooting)
No your carrier doesn't know or care you are rooted... unless you do break something and bring it in asking them to fix it, then they will tell you you broke it yourself tough luck. (unless of course you reverse everything back to stock first)
FIRST read all (really... read all of it) of the 2nd and 3rd thread in "AT&T Samsung Galaxy S 4 General"
[GUIDE][INFO] The beginner's info thread (aka. the noob helper) and [HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2
Then you can root. The "CF Auto-root" method works perfectly on all the Canadian carrier versions (they only differ in carrier bloat.), then install a custom recovery, then install a good backup utility, I suggest TiBu (which will also allow you to remove Knox).
Good luck.

robinsonj said:
So ...based on the question, and the fact that this is your first post, it appears you have a fair bit of reading to get through before doing it but yes the phone does everything rooted as it did before, you just have access to the whole file system (which means you will have the ability to break things that were "roped off for your protection" before rooting)
No your carrier doesn't know or care you are rooted... unless you do break something and bring it in asking them to fix it, then they will tell you you broke it yourself tough luck. (unless of course you reverse everything back to stock first)
FIRST read all (really... read all of it) of the 2nd and 3rd thread in "AT&T Samsung Galaxy S 4 General"
[GUIDE][INFO] The beginner's info thread (aka. the noob helper) and [HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2
Then you can root. The "CF Auto-root" method works perfectly on all the Canadian carrier versions (they only differ in carrier bloat.), then install a custom recovery, then install a good backup utility, I suggest TiBu (which will also allow you to remove Knox).
Good luck.
Click to expand...
Click to collapse
Yes, I know this is my first post, and you may think I don't know much about rooting, but I have had some experience in the past. I did root my Samsung Galaxy Tab 2, first time I soft bricked it, then actually got to root and stuff to work, so I have some knowledge on what I am doing.
Those two threads that you have linked me, I have looked over and learn't some stuff from them. I have also downloaded CF Auto-Root for the I337m version. I know how to work it, through using Odin and download mode, exact same way I rooted my tablet.
I just have one more question though, rooting it with odin through download mode, that bypasses KNOX and allows the root to work? Cause if I tried rooting with any program like motochopper, KNOX would block it.

Pellisco said:
Yes, I know this is my first post, and you may think I don't know much about rooting, but I have had some experience in the past. I did root my Samsung Galaxy Tab 2, first time I soft bricked it, then actually got to root and stuff to work, so I have some knowledge on what I am doing.
Those two threads that you have linked me, I have looked over and learn't some stuff from them. I have also downloaded CF Auto-Root for the I337m version. I know how to work it, through using Odin and download mode, exact same way I rooted my tablet.
I just have one more question though, rooting it with odin through download mode, that bypasses KNOX and allows the root to work? Cause if I tried rooting with any program like motochopper, KNOX would block it.
Click to expand...
Click to collapse
OK just didn't want you to brick your phone by not really understanding Odin... It is writing to the system partition and has been known to make a mess if the wrong files are dropped in the bootloader or if a download is interrupted.
I'm afraid all I really know about KNOX is from reading about the problems with the 1.x implementation and that the latest was supposed to be the solution for BYOD in a secure enterprise...
I Odined CF Auto-Root and had no issues whatsoever... I'm pretty sure KNOX can only run inside the OS, so in download mode you're outside of where it can interfere with anything. After the root and a custom recovery the first thing I did was freeze all KNOX and "enterprise" files just in case.

robinsonj said:
OK just didn't want you to brick your phone by not really understanding Odin... It is writing to the system partition and has been known to make a mess if the wrong files are dropped in the bootloader or if a download is interrupted.
I'm afraid all I really know about KNOX is from reading about the problems with the 1.x implementation and that the latest was supposed to be the solution for BYOD in a secure enterprise...
I Odined CF Auto-Root and had no issues whatsoever... I'm pretty sure KNOX can only run inside the OS, so in download mode you're outside of where it can interfere with anything. After the root and a custom recovery the first thing I did was freeze all KNOX and "enterprise" files just in case.
Click to expand...
Click to collapse
Okay. Hopefully KNOX doesn't interfere with anything. I also noticed in download mode:
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-CONFIG-LSB: 0x20
Write Protection: Enable
eMMC Burst Mode: Enabled
So which ones trip when I root it? I know that the 'Current Binary' will trip if I install a custom rom, but, what about the KNOX stuff? I know that the Warranty Void will then turn to '0x1' and I think the kernel lock will change too, but not 100% sure.
Also, what about Write Protection? Will that have anything to do with writing new software onto the phone and will block it?

Pellisco said:
Okay. Hopefully KNOX doesn't interfere with anything. I also noticed in download mode:
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-CONFIG-LSB: 0x20
Write Protection: Enable
eMMC Burst Mode: Enabled
So which ones trip when I root it? I know that the 'Current Binary' will trip if I install a custom rom, but, what about the KNOX stuff? I know that the Warranty Void will then turn to '0x1' and I think the kernel lock will change too, but not 100% sure.
Also, what about Write Protection? Will that have anything to do with writing new software onto the phone and will block it?
Click to expand...
Click to collapse
You may want to look at the top of this page.... http://autoroot.chainfire.eu/ states CF-auto root will trip Knox warranty... if your rooting, you should install a custom recovery and do a nand backup before you do anything else root without backup can have some ill side effects if you mess around with your files/apps... ie delete something that is critical.... of coruse custom recovery trips something else too I forget what it was but I am sure it's been discussed a couple times throughout the forum.... all I can say is read lots.... most times someone can get you out of a jam but I prefer not to go there in the first place.. so I read before I do.... most here will tell you it's the best way.... pay close attention to those who have messed up... good indication of what not to do....

One other thing I noticed was that there are locked boot loaders on certain devices.
So I have been wondering, does the Rogers Samsung Galaxy S4 come with a locked boot loader? Cause if it does, and I try and root my phone, there is a high chance that it will brick the device.

[Q] Has anyone tried KINGROOT on the Note 4?

While searching for a root method that wouldn't trip KNOX I ran into KINGROOT. I also read that rooting using this method for the Note 4 meant only a temporary root access, that would cease to work when the phone was rebooted.
This temporary root could work for me as I'm trying to get access to the extSDcard in 4.4.4 (Lollipop didn't work out for me, horrible battery life).
So I was wondering if anyone has tested it... Here is the link to KINGROOT thread: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461

I have it installed but I haven't tried it yet because I don't have time atm to reinstall everything if something goes wrong.
Have you tried it?

tried it, the phone just went to reboot then kingroot apps stated that no root available yet. so in the end, i just root the phone using chainfire root method,lol.

Framaroot doesn't work either. Cf auto root is the way to go
Sent from my SM-N910F

I have rooted with Kingroot, I've been following the SuperSuMe thread in the AT&T Note 4 General section. Kingroot works just fine if you reboot your phone after installing the apk and once the phone has rebooted then run the app to root. The root is only temporary though and WILL disappear when you reboot your phone and you will then have to rerun kingroot to root again.

Thanks for the replies
Sylntnyt said:
I have rooted with Kingroot, I've been following the SuperSuMe thread in the AT&T Note 4 General section. Kingroot works just fine if you reboot your phone after installing the apk and once the phone has rebooted then run the app to root. The root is only temporary though and WILL disappear when you reboot your phone and you will then have to rerun kingroot to root again.
Click to expand...
Click to collapse
Did your Knox stay 0x0? A temporary root works for me, what I'm really hoping for is to enable external SD access to my apps. I'm guessing that if you enable it when rooted it won't go away after you lose root...

henriquehfc said:
Thanks for the replies
Did your Knox stay 0x0? A temporary root works for me, what I'm really hoping for is to enable external SD access to my apps. I'm guessing that if you enable it when rooted it won't go away after you lose root...
Click to expand...
Click to collapse
Yes Knox remains 0x0 because the kernel, bootloader, and recovery remain untouched. As far as the external SD access, it can be enabled, but from what I gather from the other thread, is that it will revert back if the phone reboots. The reason is due to a security check Sammy put into the boot process. So put plainly, you'd have to set it up again after rerooting.

Sylntnyt said:
Yes Knox remains 0x0 because the kernel, bootloader, and recovery remain untouched. As far as the external SD access, it can be enabled, but from what I gather from the other thread, is that it will revert back if the phone reboots. The reason is due to a security check Sammy put into the boot process. So put plainly, you'd have to set it up again after rerooting.
Click to expand...
Click to collapse
I guess I'll just have to try it out... Hope it works with the 910C as well as the AT&T version.

henriquehfc said:
I guess I'll just have to try it out... Hope it works with the 910C as well as the AT&T version.
Click to expand...
Click to collapse
Apparently the new KingRoot is able to root the Galaxy Note 4 without tripping KNOX ...?

MarcoCzen said:
Apparently the new KingRoot is able to root the Galaxy Note 4 without tripping KNOX ...?
Click to expand...
Click to collapse
Not for lollipop, root strategy unavailable. Tested for both 5.0.1 and 5.1.1.

tried but kingroot failed

lucaoldb said:
Not for lollipop, root strategy unavailable. Tested for both 5.0.1 and 5.1.1.
Click to expand...
Click to collapse
That clears the air then. I have tried Kingroot v 4.5 with my sm-n910c / lollipop and to no avail.

I'm really liking the sound of a temp root. I use NFC banking and it hates root but I want a few pre-loaded apps removed. (Facebook for one) and cant without root.
BUT as I'm on 5.1.1 I guess I cant use this.
And I like to do a backup using Titanium Backup every month or so, and that also needs root. A temp root would be perfect for me.
Will kingroot be able to work on lollipop after an update or are we SOL completely?
(BTW, Note 4, 5.1.1)

Sylntnyt said:
Yes Knox remains 0x0 because the kernel, bootloader, and recovery remain untouched. As far as the external SD access, it can be enabled, but from what I gather from the other thread, is that it will revert back if the phone reboots. The reason is due to a security check Sammy put into the boot process. So put plainly, you'd have to set it up again after rerooting.
Click to expand...
Click to collapse
Hi what was your android version?? And banking apps run with no problem??

my knox cannot be install because custom os previously been installed on this device

how to install my knox in my device . it say my knox cannot be installed because custom os been installed on this device . help me

Hello!
Did you root your phone? If you need to use Knox, you should reset your phone to its original state. I recommend flash the firmware again, you'll not loose data or anything, it'll only remove root.
// Galaxy E5

FMAranda said:
Hello!
Did you root your phone? If you need to use Knox, you should reset your phone to its original state. I recommend flash the firmware again, you'll not loose data or anything, it'll only remove root.
// Galaxy E5
Click to expand...
Click to collapse
i'm using E7 .

dabgartirth said:
i'm using E7 .
Click to expand...
Click to collapse
No difference, mate. Have you done root or anything? If positive, you need to roll back your phone to original state.

After KNOX flag is tripped, there is no way to use KNOX apps again, they're disabled forever whatever you do.

I'm having this problem with my s6 and I only got it brand new today and haven't done anything other than sign in to play store and downloaded my apps

Galaxy S8 Secure folder with Knox ?

Hello
How to use secure folder with Knox 0x1 ?
It there any way to do this ?

no

locarno said:
Hello
How to use secure folder with Knox 0x1 ?
It there any way to do this ?
Click to expand...
Click to collapse
Once your Knox is tripped you can not use secure folder. There is no fix for a tripped Knox.

Is it possible to mask the 0x1 to make Knox and Samsung Pay work?

WilliamBlake said:
Is it possible to mask the 0x1 to make Knox and Samsung Pay work?
Click to expand...
Click to collapse
Yes MagiskHide masks the 0x1 Value to 0x0 and it might work to use some of the features that check for the Knox counter value.
0. You need to be rooted with the latest version of Magisk.
1. You need to change the name of the Magisk Manager app to a different name using the "Hide Magisk Manager" function.
2. Turn on MagiskHide in settings and check Samsung pay and Secure folder (And all the apps that help them run like Samsung pay framework etc.) in the MagiskHide tab.
3. Delete any files in your internal storage that have Magisk in the name.
4. (Optional) If you dont want to be rooted you can also disable Superuser access within the Magisk Manager App.
Edit: You may also have to enable "Magisk Core Only Mode" so that no modules or anything extra is loaded that Samsung Pay could possibly detect.
This is not 100% guarenteed to work but it is worth a try as it is close as you are going to get to knox 0x0.

JJcoder said:
Yes MagiskHide masks the 0x1 Value to 0x0 and it might work to use some of the features that check for the Knox counter value.
0. You need to be rooted with the latest version of Magisk.
1. You need to change the name of the Magisk Manager app to a different name using the "Hide Magisk Manager" function.
2. Turn on MagiskHide in settings and check Samsung pay and Secure folder (And all the apps that help them run like Samsung pay framework etc.) in the MagiskHide tab.
3. Delete any files in your internal storage that have Magisk in the name.
4. (Optional) If you dont want to be rooted you can also disable Superuser access within the Magisk Manager App.
This is not 100% guarenteed to work but it is worth a try as it is close as you are going to get to knox 0x0.
Click to expand...
Click to collapse
Once Knox is tripped it triggers an Efuse, that can only be fixed by a motherboard replacement. Samsung Pay will never work once Knox has been tripped.

stonedpsycho said:
Once Knox is tripped it triggers an Efuse, that can only be fixed by a motherboard replacement. Samsung Pay will never work once Knox has been tripped.
Click to expand...
Click to collapse
I know, but MagiskHide masks the value to 0x0.

JJcoder said:
I know, but MagiskHide masks the value to 0x0
on boot.
Click to expand...
Click to collapse
That will not make Samsung Pay work.

stonedpsycho said:
That will not make Samsung Pay work.
Click to expand...
Click to collapse
Are you sure? Maybe if you just enable MagiskHide it wont work; but if you follow all of my steps how can Samsung pay detect Knox 0x1 and root? Maybe you have to reinstall Samsung Pay? I am still on the 7 day jail (RMM state lock) on my S8 so I can't experiment with it right now.

JJcoder said:
Are you sure? Maybe if you just enable MagiskHide it wont work; but if you follow all of my steps how can Samsung pay detect Knox 0x1 and root? Maybe you have to reinstall Samsung Pay? I am still on the 7 day jail (RMM state lock) on my S8 so I can't experiment with it right now.
Click to expand...
Click to collapse
It will not fix the Efuse though.

stonedpsycho said:
It will not fix the Efuse though.
Click to expand...
Click to collapse
You are right! I'm not trying to revert the eFUSE that
is not possible. I am trying to mask the value so that Samsung Pay and other apps will think that Knox is 0x0 and that the phone is not rooted. My question is
how can Samsung Pay detect Knox 0x1 even when following all of the steps I listed above while all of the Knox Status apps on the Play Store say 0x0 while simply enabling MagiskHide and checking the app in the MagiskHide tab?

JJcoder said:
You are right! I'm not trying to revert the eFUSE that
is not possible. I am trying to mask the value so that Samsung Pay and other apps will think that Knox is 0x0 and that the phone is not rooted. My question is
how can Samsung Pay detect Knox 0x1 even when following all of the steps I listed above while all of the Knox Status apps on the Play Store say 0x0 while simply enabling MagiskHide and checking the app in the MagiskHide tab?
Click to expand...
Click to collapse
I am no expert and don't understand how it all works but if there was a way or workaround for Samsung Pay to work I think the talented Devs here on XDA would have found a solution by now, like one did for Secure Folder.

stonedpsycho said:
I am no expert and don't understand how it all works but if there was a way or workaround for Samsung Pay to work I think the talented Devs here on XDA would have found a solution by now, like one did for Secure Folder.
Click to expand...
Click to collapse
Did anyone actually try following the steps I listed? Maybe you also have to enable Magisk Core only mode so no modules or anything extra is loaded that Samsung Pay could possibly detect? If that doesn't work then what about reinstalling Samsung Pay and it's framework after following these steps?
As I said I wish I could try myself but I am still in RMM state: Prenormal

JJcoder said:
Did anyone actually try following the steps I listed? Maybe you also have to enable Magisk Core only mode so no modules or anything extra is loaded that Samsung Pay could possibly detect? If that doesn't work then what about reinstalling Samsung Pay and it's framework after following these steps?
As I said I wish I could try myself but I am still in RMM state: Prenormal
Click to expand...
Click to collapse
I have never tried that but I highly doubt it will work still.
Jail time! You tried the trick of moving the clock forward 7+ days?

stonedpsycho said:
I have never tried that but I highly doubt it will work still.
Jail time! You tried the trick of moving the clock forward 7+ days?
Click to expand...
Click to collapse
Yes, but it didn't work for me (because I think it only works on Oreo and im on Pie)
So I just have to wait 7 days.

JJcoder said:
Yes, but it didn't work for me (because I think it only works on Oreo and im on Pie)
So I just have to wait 7 days.
Click to expand...
Click to collapse
I know it can be hit and miss and can take a few attempts, probably worth another try. I only faced jail time on Oreo, but I use a Note 8.
If you do get Spay to work though, please let us know as so many people will be very happy with you :fingers-crossed:

stonedpsycho said:
I know it can be hit and miss and can take a few attempts, probably worth another try. I only faced jail time on Oreo, but I use a Note 8.
If you do get Spay to work though, please let us know as so many people will be very happy with you :fingers-crossed:
Click to expand...
Click to collapse
Well im already on my third day and if the date trick doesn't work then i'll have to start all over again.
As yes I will let everyone know if I can get Samsung Pay to work

issues after unroot my device

so i have galaxy s10+ sm-g975F
i rooted the phone then i flash the last firmware G975FXXUFHVG4 to relock the bootloader and get fresh clean software
so here is the issues samsung pass keep detecting the device was rooted
the second package disabler owner app cannot sit as an admin anymore giving me java errors
i flash other firmware i keep getting the same issue
i email package disabler pro asking them what the issue they give me no answer
how i can totally get rid of all the root files on my phone

UP

Simple, once you root, you lose KNOX forever.
Pass, Secure Folder need KNOX.
You can unroot by just flashing the latest firmware with Odin. But KNOX related stuff, that's bye bye forever.

PlutoDelic said:
Simple, once you root, you lose KNOX forever.
Pass, Secure Folder need KNOX.
You can unroot by just flashing the latest firmware with Odin. But KNOX related stuff, that's bye bye forever.
Click to expand...
Click to collapse
ic i really dont care about knox package disabler all what i care about
i remove the unwanted bloatware using adb command

seen_bawl said:
ic i really dont care about knox package disabler all what i care about
i remove the unwanted bloatware using adb command
Click to expand...
Click to collapse
Just so we dont get confused here.
When i say KNOX, i don't mean any sort of package disabler, i mean the KNOX security system inside Samsung phones. It's an eFuse that gets tripped once you root, and it's impossible to revert back.
Some Samsung services such as Secure Folder, Samsung Pass, WILL NEVER work even if you flash the latest official rom.
Now, if you want my two cents, debloating used to work, but not as much anymore, of course i may stand corrected, but i tested it myself without any difference in results.
Why dont you make use of the Deep Sleep listing in Device care, that way you limit an app from waking up unless you actually want too. Of course, im assuming this is all for battery gains.