Note 3
AP: N9005XXUBMJ3
CP: N9005XXUBMJ2
CSC: N9005OXXBMJ3
Is there a solution to root it without tripping knox?
Big thx.
lion_sta said:
Note 3
AP: N9005XXUBMJ3
CP: N9005XXUBMJ2
CSC: N9005OXXBMJ3
Is there a solution to root it without tripping knox?
Big thx.
Click to expand...
Click to collapse
The general response around is that there is none (yet).
IMHO it might be interesting if you also connect you phone with USB-debugging mode activated and then you do from a command-line
adb shell
and then
getprop ro.boot.bootloader
If you are not familiar with adb (or you do not have adb and the USB-debugging stuff) but you have a terminal emulator installed on the phone (which you can do from the play store even if you are not rooted) you can try that last command directly in the terminal on the phone.
If the result is something like N9005XXUBMI7 then you can use URDLV.
If not and you are very determined to root at the risk of the knox status we might try some other solutions.
xclub_101 said:
.
Click to expand...
Click to collapse
Did it, and this is what I get.
[email protected]:/ $ adb shell
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ getprop ro.boot.bootloader
N9005XXUBMJ3
[email protected]:/ $
Does this mean that if I were to root I am certainly loosing warranty?
Or people are not 100% sure?
lion_sta said:
Did it, and this is what I get.
[email protected]:/ $ adb shell
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ getprop ro.boot.bootloader
N9005XXUBMJ3
[email protected]:/ $
Does this mean that if I were to root I am certainly loosing warranty?
Or people are not 100% sure?
Click to expand...
Click to collapse
MJ3 bootloader does not let you install any previous ROM/bootloader and MJ3 and later stock ROMs are known to no longer work with URDLV.
I have expressed here:
http://forum.xda-developers.com/showthread.php?t=2642207
the idea that just rooting should be possible without triggering knox, but my Note 3 is already successfully rooted using URDLV with knox 0x0 so for the moment I do not plan in making more tests on this part.
That being said if there are users that are decided to root even at the risk of triggering their knox status I think it might be very interesting to do such tests with a better plan instead of just jumping on CF-root or similar.
OK, I am willing to take some risks, especially since you say that it is ”possible”.
Let me explain why I need the rooting maybe you can advise.
I am region locked without the possibility of going to that region and speaking the 5 mins.
I have read and learned that using the regionlock away tool would remove the loc even after unrooting.
So this is my plan, just root, use the tool, unroot.
What do you think?
lion_sta said:
OK, I am willing to take some risks, especially since you say that it is ”possible”.
Let me explain why I need the rooting maybe you can advise.
I am region locked without the possibility of going to that region and speaking the 5 mins.
I have read and learned that using the regionlock away tool would remove the loc even after unrooting.
So this is my plan, just root, use the tool, unroot.
What do you think?
Click to expand...
Click to collapse
1. If you want people to know that you answered then you should quote them - that way they get a notification
2. Are you only region-lock or also network-locked? Surprisingly if you are network-locked it will be much "knox-safer" (but it will cost in the area of 10-15 EUR or so).
3. Do you have kind of hope for any kind of Samsung warranty?
4. Extra advice "just in case" - disable right now both system updates and security updates.
xclub_101 said:
1. If you want people to know that you answered then you should quote them - that way they get a notification
2. Are you only region-lock or also network-locked? Surprisingly if you are network-locked it will be much "knox-safer" (but it will cost in the area of 10-15 EUR or so).
3. Do you have kind of hope for any kind of Samsung warranty?
4. Extra advice "just in case" - disable right now both system updates and security updates.
Click to expand...
Click to collapse
1. Sorry bout that, been on a forum where it was kindda forbiden.
2. Unfortunately only region locked, tho not 100 % sure.
3. Don't we all? For as long as it is at least "possible"
4. Well, I don't think it is possible. I get this bugging notification every day to install. Have not seen an option to disable.
lion_sta said:
1. Sorry bout that, been on a forum where it was kindda forbiden.
2. Unfortunately only region locked, tho not 100 % sure.
3. Don't we all? For as long as it is at least "possible"
4. Well, I don't think it is possible. I get this bugging notification every day to install. Have not seen an option to disable.
Click to expand...
Click to collapse
2. If you place inside a different SIM (than the network for which is locked) and it directly asks for unlock code it is network-locked. If not it might only be region-locked.
3. As far as I understand Samsung warranties are only offered at best inside the same region for which the lock is present - so if the phone is from UK at best you can hope in a warranty inside EU - but I would not hope too much, most often you also need a warranty certificate filled by an AUTHORIZED Samsung seller; next-best would be some warranty in the same country, but very, very often the warranty comes from the seller himself and there is no other warranty
4. The ROM OTA update should ask you for a country and ask if you agree with the terms, if you say that you do not agree then it should not bother you again. The "security updates" is for a separate setting - in General - Security - "Auto update security". Disable that and get rid of the OTA updates first!
5. Check your precise current kernel version (that is just to clarify where you are) - if it was build after (I believe) October-December 2013 or so you must wipe everything and reinstall the original MJ3 ROM.
6. Then you need to check this thread
http://forum.xda-developers.com/showthread.php?t=2565758
note that from some point on Samsung kernels have fixed that method, this is discussed starting in this post:
http://forum.xda-developers.com/showthread.php?p=48749875#post48749875
xclub_101 said:
2. If you place inside a different SIM (than the network for which is locked) and it directly asks for unlock code it is network-locked. If not it might only be region-locked.
3. As far as I understand Samsung warranties are only offered at best inside the same region for which the lock is present - so if the phone is from UK at best you can hope in a warranty inside EU - but I would not hope too much, most often you also need a warranty certificate filled by an AUTHORIZED Samsung seller; next-best would be some warranty in the same country, but very, very often the warranty comes from the seller himself and there is no other warranty
4. The ROM OTA update should ask you for a country and ask if you agree with the terms, if you say that you do not agree then it should not bother you again. The "security updates" is for a separate setting - in General - Security - "Auto update security". Disable that and get rid of the OTA updates first!
5. Check your precise current kernel version (that is just to clarify where you are) - if it was build after (I believe) October-December 2013 or so you must wipe everything and reinstall the original MJ3 ROM.
6. Then you need to check this thread
http://forum.xda-developers.com/showthread.php?t=2565758
note that from some point on Samsung kernels have fixed that method, this is discussed starting in this post:
http://forum.xda-developers.com/showthread.php?p=48749875#post48749875
Click to expand...
Click to collapse
Before doing the other points please tell me what you think about the point 5 -
2. We should continue as if it was only region locked, because when I bought it it was specified that it was carrier free
3. I am in Moldova, and my sister is in Romania - where the phone is from, close but not close enough it seems.
4. Done
5. Check image
6. In the first thread there, in the list of succesfully rooted devices is not present the Note 3. You are not the only one to have pointed me in that direction. But still want to make sure that it will work on Note 3.
lion_sta said:
Before doing the other points please tell me what you think about the point 5 -
2. We should continue as if it was only region locked, because when I bought it it was specified that it was carrier free
3. I am in Moldova, and my sister is in Romania - where the phone is from, close but not close enough it seems.
4. Done
5. Check image
6. In the first thread there, in the list of succesfully rooted devices is not present the Note 3. You are not the only one to have pointed me in that direction. But still want to make sure that it will work on Note 3.
Click to expand...
Click to collapse
3. Then it makes some sense to keep Knox 0x0 (but be extra-careful with the water, in my experience in many countries Samsung official service dismisses 90% of the claims based on the internal water detectors (plenty of them).
5. IMHO you have a good chance to have saferoot still working. Saferoot from the thread I mentioned above is nice since if it fails it just fails to root but it does not set knox 0x1. Even if it fails as it is now (there is a very small chance that the fix was not in the kernel and you still got it before you disabled the security updates) it might still be worth to wipe everything and then write original MJ3 ROM and try again (this time certainly without any updates, without even connecting the phone on the net).
If you manage to root with MJ3 and keep knox 0x0 IMHO it might be worth to keep the root (and hide it with Wanam xposed) then eventually to go to MJ7 or so (with Mobile Odin Pro). Again - strictly IMHO - 4.4.2 is not yet worth it.
xclub_101 said:
3. Then it makes some sense to keep Knox 0x0 (but be extra-careful with the water, in my experience in many countries Samsung official service dismisses 90% of the claims based on the internal water detectors (plenty of them).
5. IMHO you have a good chance to have saferoot still working. Saferoot from the thread I mentioned above is nice since if it fails it just fails to root but it does not set knox 0x1. Even if it fails as it is now (there is a very small chance that the fix was not in the kernel and you still got it before you disabled the security updates) it might still be worth to wipe everything and then write original MJ3 ROM and try again (this time certainly without any updates, without even connecting the phone on the net).
If you manage to root with MJ3 and keep knox 0x0 IMHO it might be worth to keep the root (and hide it with Wanam xposed) then eventually to go to MJ7 or so (with Mobile Odin Pro). Again - strictly IMHO - 4.4.2 is not yet worth it.
Click to expand...
Click to collapse
3 - thx for the advice.
5. No luck. Now for the next step, how do I wipe and what are the risks? Also how do I find the original MJ3 ROM?
lion_sta said:
3 - thx for the advice.
5. No luck. Now for the next step, how do I wipe and what are the risks? Also how do I find the original MJ3 ROM?
Click to expand...
Click to collapse
A simple wipe is the easy part - you just factory-reset or go in recovery and do a (full) wipe (all data in the phone will be lost). The more complex part would be to find the original ROM - I would guess it could be on a page like this:
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=ROM#firmware
EDIT:
And before going to Odin be 100% certain that you disabled reactivation lock if you ever enabled it. And Odin mode is always involving some risk, read a little around before jumping into it.
lion_sta said:
Note 3
AP: N9005XXUBMJ3
CP: N9005XXUBMJ2
CSC: N9005OXXBMJ3
Is there a solution to root it without tripping knox?
Big thx.
Click to expand...
Click to collapse
Yes. I used Kingo root app for mine, and preserved Knox 0x0. Google it.
shayind4 said:
Yes. I used Kingo root app for mine, and preserved Knox 0x0. Google it.
Click to expand...
Click to collapse
Not working for me, asks to install custom rom.
So, something weird just happened. Did the thing with Kingo root at home, and it told me that my device could not bee rooted without tripping knox.
Drivers - Kies, That app that is telling that an app had to stop because ... - apparently running.
Same app, installed the drivers from Kingo, on its own. I stopped the app ”hat is telling that an app had to stop because ...” but it still appeared during the process.
Result - Succes, I am rooted. Big thx to you all.
lion_sta said:
So, something weird just happened. Did the thing with Kingo root at home, and it told me that my device could not bee rooted without tripping knox.
Drivers - Kies, That app that is telling that an app had to stop because ... - apparently running.
Same app, installed the drivers from Kingo, on its own. I stopped the app ”hat is telling that an app had to stop because ...” but it still appeared during the process.
Result - Succes, I am rooted. Big thx to you all.
Click to expand...
Click to collapse
Did it void the knox status?
buntoo said:
Did it void the knox status?
Click to expand...
Click to collapse
No. BTW it worked with the 1.1.8 while at home I was trying with 1.2.0.
Still, the main reason why I rooted was to get the RegionLock Away and it is not working. Bummer.
lion_sta said:
No. BTW it worked with the 1.1.8 while at home I was trying with 1.2.0.
Still, the main reason why I rooted was to get the RegionLock Away and it is not working. Bummer.
Click to expand...
Click to collapse
unfortunately it doesn't work for the exynos (SM-900)
buntoo said:
unfortunately it doesn't work for the exynos (SM-900)
Click to expand...
Click to collapse
I missread what you said. Was too self centered.
does kingo works on exynos running 4.3?
Sent from my SM-N900 using XDA Premium 4 mobile app
Related
The first 3 things I did when I got my S4 were:
- Open the packaging
- Update the firmware
- Root the ROM
Then... I find out afterwards about this knox fiasco and guess what? I'm 0x1 - I ain't even mad bro.
What I am mad about however, is the fact I cant seem to achieve a full device root, only can on do what most are calling a 'partial root' - and that's whether that be by installing a pre-rooted rom or using a flashable root file.
That affects me because half my root apps work, and half don't.
For instance: Titanium Backup? all good... Helium? Says cant work, no root (yes I know about desktop method)
So my questions are these:
1. Is there a definite way of achieving full device root on a knox-enabled rom?
2. If not, how likely is it to be possible in future?
3. If unlikely (or impossible) is the only option an AOSP rom? and are they even fully rootable when knox enabled?
If there is no hope on the horizon, I think I'm gonna have to flog this sucker on eBay.
melvatron said:
The first 3 things I did when I got my S4 were:
- Open the packaging
- Update the firmware
- Root the ROM
Then... I find out afterwards about this knox fiasco and guess what? I'm 0x1 - I ain't even mad bro.
What I am mad about however, is the fact I cant seem to achieve a full device root, only can on do what most are calling a 'partial root' - and that's whether that be by installing a pre-rooted rom or using a flashable root file.
That affects me because half my root apps work, and half don't.
For instance: Titanium Backup? all good... Helium? Says cant work, no root (yes I know about desktop method)
So my questions are these:
1. Is there a definite way of achieving full device root on a knox-enabled rom?
2. If not, how likely is it to be possible in future?
3. If unlikely (or impossible) is the only option an AOSP rom? and are they even fully rootable when knox enabled?
If there is no hope on the horizon, I think I'm gonna have to flog this sucker on eBay.
Click to expand...
Click to collapse
1. No.
2. Probably not.
3. AOSP is always the best option if full device control is something you want. Knox is something that prevents root from working properly. There is little to no hope on the horizon, so my advice is: Get your listing ready.
Don't you feel "safer" having Knox protecting your device from you (and protecting Samdung from warranty liability)?
Yeah sure, I feel safer.... if by safe, you mean imprisoned and my freedom restricted.
I coulda just bought an iPhone off the bat if i wanted that kinda safety!
I updated my phone today and I was able to root it an disable KNOX.
I used CF-Autoroot http://autoroot.chainfire.eu/ and it worked flawlessly and when I was updating the binary I got the option to disable KNOX.
Root Instruction:
1. Flash with Odin
2. Add a google account incase it has not been setup yet.
3. Install SuperSU from Market.
4. Open it and it wil ask you to update binary.
Respect to the developer.
Futhermore, I got CWM with one of the methods I was using when on JB 4.1.2
PLS NOTE: You will lose warranty if phone is rooted at this time. If you will like to keep your warranty with no possibility to go back to an older android version, please AVOID rooting your ROM and wait for custom ROM with KNOX disabled
Cheers,
But.. I don't know whether to use the i9305 or I9305T files :/
My device is I9305T but has been running I9305 FW (and probably bootloaders) for a while...
For those who need some more links/instructions:
Backup your data, SMS, settings - and make sure you got an IMEI backup
http://forum.xda-developers.com/showthread.php?t=1946915
If you use Google's 2-Step Verification, make sure you can receive the SMS via a 2nd phone or have a backup option like landline or authenticator app.
I removed my SD card (just in case) and did a full system wipe just to get rid of everything I did to my system over the last year:
Hold down volume up, home and power buttons, when screen turns on, leave these buttons, do the full system wipe. (Don't think this is really necessary though.)
Install 4.3 on your i9305
http://www.androidegis.com/how-to/install-android-4-3-update-galaxy-s3-lte-i9305/
Switch the phone off after first book (at SIM PIN prompt).
Get CF-Auto-Root and install it
EDIT: http://forum.xda-developers.com/showthread.php?t=1957273
Now after your phone booted you can run the Samsung setup. Add your Google account.
Install SuperSU from the Play Store - not SuperUser
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Update the binary and disable KNOX
Enjoy
For me what worked, was installing PhilZ Touch (latest version), and using the built-in rooting function of the recovery. Then, installing SuperSU gave me perfect root.
Does anyone know if Koush's superuser app works in any way in this release? I would prefer to use an open-source superuser app.
gulbrillo said:
For those who need some more links/instructions:
Backup your data, SMS, settings - and make sure you got an IMEI backup
http://forum.xda-developers.com/showthread.php?t=1946915
If you use Google's 2-Step Verification, make sure you can receive the SMS via a 2nd phone or have a backup option like landline or authenticator app.
I removed my SD card (just in case) and did a full system wipe just to get rid of everything I did to my system over the last year:
Hold down volume up, home and power buttons, when screen turns on, leave these buttons, do the full system wipe. (Don't think this is really necessary though.)
Install 4.3 on your i9305
http://www.androidegis.com/how-to/install-android-4-3-update-galaxy-s3-lte-i9305/
Switch the phone off after first book (at SIM PIN prompt).
Get CF-Auto-Root and install it
http://forum.xda-developers.com/showthread.php?t=2219803
Now after your phone booted you can run the Samsung setup. Add your Google account.
Install SuperSU from the Play Store - not SuperUser
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Update the binary and disable KNOX
Enjoy
Click to expand...
Click to collapse
Did you mean to link the [GT-I9505 + GT-I9505G] CF-Auto-Root page, or should we get the file from [GT-I930x/T/N][SHV-E210*][SHW-M440S] CF-Auto-Root?
Damn, sorry - that was my mistake. I just changed the link above - it should have been http://forum.xda-developers.com/showthread.php?t=1957273 of cause. Thanks!
aaronsclee said:
Did you mean to link the [GT-I9505 + GT-I9505G] CF-Auto-Root page, or should we get the file from [GT-I930x/T/N][SHV-E210*][SHW-M440S] CF-Auto-Root?
Click to expand...
Click to collapse
I don't understand if this method preserves the warranty.
No , it doesn't . By flashing CF-Root you will get Knox count 1 .
seaman5705 said:
No , it doesn't . By flashing CF-Root you will get Knox count 1 .
Click to expand...
Click to collapse
Uh. I think, at this point, that the best thing (for me) is to not update.
Update using Heimdall, and skip flashing tz.img and sboot.bin. Be aware that this will break WiFi until a custom kernel is released
Sent from my GT-I9305 using xda app-developers app
I prefer to wait until a solution will be find.
lallolu said:
I updated my phone today and I was able to root it an disable KNOX.
Click to expand...
Click to collapse
Thanks for sharing this interesting experience.
But I think it would be kind of you to edit the OP to say in a very visible way that someone doing that looses his warranty with no possibility to go back at this time (until a solution is found, but no one knows if this will ever be the case ...) because of the new Knox bootloader and the new Knox warranty void flag.
Ed Roid said:
Thanks for sharing this interesting experience.
But I think it would be kind of you to edit the OP to say in a very visible way that someone doing that looses his warranty with no possibility to go back at this time (until a solution is found, but no one knows if this will ever be the case ...) because of the new Knox bootloader and the new Knox warranty void flag.
Click to expand...
Click to collapse
Thanks mate for clarifying the issue of Knox flag and warranty. I will wait for a dev to make Knox-free rom.
if you'd like to have 4.3 stock rom with root and warranty, you can update your phone to 4.3 using Mobile Odin PRO latest version (3.85). Let's say you're on 4.1.2, just download 4.3 for your phone, move it to phone storage, flash it using Mobile Odin PRO with EverRoot and Inject Mobile Odin features. This way you'll have a 4.3 rooted in warranty.
steebro said:
This way you'll have a 4.3 rooted in warranty.
Click to expand...
Click to collapse
4.3 stock + root + warranty ok but no wifi, am i right ?
Ed Roid said:
Thanks for sharing this interesting experience.
But I think it would be kind of you to edit the OP to say in a very visible way that someone doing that looses his warranty with no possibility to go back at this time (until a solution is found, but no one knows if this will ever be the case ...) because of the new Knox bootloader and the new Knox warranty void flag.
Click to expand...
Click to collapse
Thanks for pointing that out. I have updated the OP.
steebro said:
if you'd like to have 4.3 stock rom with root and warranty, you can update your phone to 4.3 using Mobile Odin PRO latest version (3.85). Let's say you're on 4.1.2, just download 4.3 for your phone, move it to phone storage, flash it using Mobile Odin PRO with EverRoot and Inject Mobile Odin features. This way you'll have a 4.3 rooted in warranty.
Click to expand...
Click to collapse
For sure?
I've buy the Pro Version ( in this moment the version is only working with this Mobile ( nobody knows, at which time the support will be stopped ) ).
I don't want see, that Knox is incr. from 0x0 to 0x1 with this procedure ....
THX
Wesie said:
For sure?
Click to expand...
Click to collapse
I think I've read that Mobile Odin isn't able to flash the bootloader. If this is really the case then it is true (old bootloader = no Knox flag). Note that you will also need to flash a custom kernel cause stock 4.3 kernel without Knox bootloader breaks wifi.
SHV-E210K
how can you root SHV-E210K with official 4.3 firmware?
Ed Roid said:
that someone doing that looses his warranty with no possibility to go back at this time because of the new Knox bootloader and the new Knox warranty void flag.
Click to expand...
Click to collapse
What about triangle away? (Or downgrading to a earlier stock Knox free ROM and than triangleing away?)
I have a Canadian Telus GS4 running SlimKat, and would like to return it to stock for a warranty replacement on the "SIM card not detected" issue that I'm having.
I would like to confirm that the steps I am taking to do so are correct and possibly get some help troubleshooting some issues I am having along the way.
Step 1:
Download stock firmware from this thread http://forum.xda-developers.com/showthread.php?t=2269304
Step 2:
Download Odin 3.07 from this thread http://forum.xda-developers.com/showthread.php?t=2258628
Step 3:
Flash stock firmware via Odin.
Now on to the Questions and issues I am having.
Question 1: Is it necessary to reset the binary counter to 0? If so, then what are my options?
I understand that Triangle Away will do the trick, but it warns that I must be using a stock kernel to be safe. I am currently running SlimKat. Do I need to return to stock using the above method, then re-root, then use Triangle away...THEN return to stock again? This feels like the long way around, are there other options?
Question 2: Does it matter which stock firmware I flash via Odin?
According to http://www.sammobile.com/firmwares/1/?model=SGH-I337M&pcode=TLS#firmware there are 3 options of stock firmwares. Is the latest (from the link I pasted above in my "Step 1") alright, or should I go back to 4.2?
Thanks for checking this out! Hopefully this can help others with the same problem.
L_B said:
I have a Canadian Telus GS4 running SlimKat, and would like to return it to stock for a warranty replacement on the "SIM card not detected" issue that I'm having.
I would like to confirm that the steps I am taking to do so are correct and possibly get some help troubleshooting some issues I am having along the way.
Step 1:
Download stock firmware from this thread http://forum.xda-developers.com/showthread.php?t=2269304
Step 2:
Download Odin 3.07 from this thread http://forum.xda-developers.com/showthread.php?t=2258628
Step 3:
Flash stock firmware via Odin.
Now on to the Questions and issues I am having.
Question 1: Is it necessary to reset the binary counter to 0? If so, then what are my options?
I understand that Triangle Away will do the trick, but it warns that I must be using a stock kernel to be safe. I am currently running SlimKat. Do I need to return to stock using the above method, then re-root, then use Triangle away...THEN return to stock again? This feels like the long way around, are there other options?
Question 2: Does it matter which stock firmware I flash via Odin?
According to http://www.sammobile.com/firmwares/1/?model=SGH-I337M&pcode=TLS#firmware there are 3 options of stock firmwares. Is the latest (from the link I pasted above in my "Step 1") alright, or should I go back to 4.2?
Thanks for checking this out! Hopefully this can help others with the same problem.
Click to expand...
Click to collapse
I had the exact same issue with the sim slot. But having the AT&T variant and MDL firmware is a rarity. If I sent mine into Samsung they would upgrade my bootloader to the more secure on and give me the official 4.3 update. I didn't want to loose my custom recovery, so I took it to a local iFixit workshop. Know the guy there and he fixed my iPhone 4S a few years back. Said it would be no problem for him to replace my entire sim slot for $10.
Hopefully you can find someone locally to do this for you. If you send your phone in, count on it coming back with a more secure bootloader (knox).
MattMJB0188 said:
I had the exact same issue with the sim slot. But having the AT&T variant and MDL firmware is a rarity. If I sent mine into Samsung they would upgrade my bootloader to the more secure on and give me the official 4.3 update. I didn't want to loose my custom recovery, so I took it to a local iFixit workshop. Know the guy there and he fixed my iPhone 4S a few years back. Said it would be no problem for him to replace my entire sim slot for $10.
Hopefully you can find someone locally to do this for you. If you send your phone in, count on it coming back with a more secure bootloader (knox).
Click to expand...
Click to collapse
I am quite uneducated on the knox bootloader. I understand what it is but I didn't know it would be on the Telus firmware. A quick google search shows that it would be around 15 bucks for me to get the SIM slot fixed up. Not a huge deal...but my phone is still under warranty.
EDIT: Update - I replaced the SIM card reader in the phone and am still having the SIM card undetected issue. Either I received a faulty SIM card reader, or there are other issues with the phone.
L_B said:
I am quite uneducated on the knox bootloader. I understand what it is but I didn't know it would be on the Telus firmware. A quick google search shows that it would be around 15 bucks for me to get the SIM slot fixed up. Not a huge deal...but my phone is still under warranty.
EDIT: Update - I replaced the SIM card reader in the phone and am still having the SIM card undetected issue. Either I received a faulty SIM card reader, or there are other issues with the phone.
Click to expand...
Click to collapse
Then you might want to send it in to Samsung. I'd rather you have a phone lol. I believe the 4.3 update will only give you knox, which keeps track of custom firmware. Your bootloader will not be locked. Sorry for the confusion.
MattMJB0188 said:
Then you might want to send it in to Samsung. I'd rather you have a phone lol. I believe the 4.3 update will only give you knox, which keeps track of custom firmware. Your bootloader will not be locked. Sorry for the confusion.
Click to expand...
Click to collapse
I do plan on sending it in but am having trouble returning it to stock... :S never had to do it before and Odin is giving me trouble
EDIT: Update - my Odin was freezing at "SetupConnection" for the longest time. Went to a different computer and it worked... flashed MK6 firmware (might have been a mistake to pick mk6?) but not the phone is back to stock and knox counter is at 0x0.
L_B said:
I do plan on sending it in but am having trouble returning it to stock... :S never had to do it before and Odin is giving me trouble
EDIT: Update - my Odin was freezing at "SetupConnection" for the longest time. Went to a different computer and it worked... flashed MK6 firmware (might have been a mistake to pick mk6?) but not the phone is back to stock and knox counter is at 0x0.
Click to expand...
Click to collapse
Well my point was that once you get the phone back from Samsung, they will always know if you flash a custom recovery by the knox. Unless your phone had knox before? But if its at 0x0 you have nothing to worry about.
MattMJB0188 said:
Well my point was that once you get the phone back from Samsung, they will always know if you flash a custom recovery by the knox. Unless your phone had knox before? But if its at 0x0 you have nothing to worry about.
Click to expand...
Click to collapse
I need to do more reading on knox, but I didnt see anything about the knox flag in download mode when I was on the custom firmware and recovery, I think going from custom to the most recent MK6 firmware for the I337M put the indiciation there.
Thanks for your help.
It's also interesting to point out that since I flashed back to stock with odin, my SIM card issue has gone away for the time being. I'll update if it comes back haha.
I dont understand way they would deny a warranty on a phone that has a non-standard rom on it.
I mean if the sim slot is bad, its bad - not that some app made it bad, or the removal of ATT Navigation software caused it to break.
*yeah yeah I know, in the EULA it states stuff about circumventing the OS voids warranty
It just seems anal to spend a lot of time examining the entire OS and partitions when they can just toss in a sim card and recreate issue and just fix it.
...then again, I am not Samsung
atari800 said:
I dont understand way they would deny a warranty on a phone that has a non-standard rom on it.
I mean if the sim slot is bad, its bad - not that some app made it bad, or the removal of ATT Navigation software caused it to break.
*yeah yeah I know, in the EULA it states stuff about circumventing the OS voids warranty
It just seems anal to spend a lot of time examining the entire OS and partitions when they can just toss in a sim card and recreate issue and just fix it.
...then again, I am not Samsung
Click to expand...
Click to collapse
I was under the impression that if the knox counter read 0x1 than they would not touch the phone, regardless if you touched it or not.
I have not seen a post that someone's phone was returned not fixed with a note/reason that the phone was modified outside of specification. Also imagine a dumpster of fixable phones that are untouched due to knox flag was triggered?
atari800 said:
I have not seen a post that someone's phone was returned not fixed with a note/reason that the phone was modified outside of specification. Also imagine a dumpster of fixable phones that are untouched due to knox flag was triggered?
Click to expand...
Click to collapse
Wasn't that the whole point of knox? If it reads 0x1 then the warranty is void?
Knox is an overall security layer, helping promote Android devices in the workplace.
For more info - read this
atari800 said:
Knox is an overall security layer, helping promote Android devices in the workplace.
For more info - read this
Click to expand...
Click to collapse
Well the knox flag in download mode is... "knox warranty void"
That's how it reads, or something like that.
True it can show that, but outside of chainfires explaination of how it is blown and "what has been hearing about Samsung service centers". If you read his article, there is a lot of maybes, mights, and even ends his article with "take it with a grain of salt".
Their are a lot of mad people in his chat, but I didn't find anyone saying they got denied. Samsung can do what they want, but they know word of mouth is as big as advertising is. One person saying "I installed a program, it broke is my phone and Samsung is not honoring the warranty" has a huge impact on people regardless if they know and/or understand rooting.
Knox security void can mean the phone can no longer be certified for enterprise grade applications or environments. That the security mechanism is tainted thus considered broke and not repairable.
Just my point of view - I have total respect for chain fire
Edit: Additional info
The Magnuson-Moss Warranty Act (1975) says that to refuse warranty, the company must prove that the problem with phone (or any other device that fails) was the caused by the customer.
So a defective sim card reader (unless obviously damaged by a consumer) should be covered where a modified corrupted partition table causing a boot failure (and also not a wide spread incident) may not be covered as this is more of a damage from a "non-friendly" application caused by the consumer.
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.
Hey I believe many people have questions around the KNOX and warranty void if you root/install custom recovery.
So I woud like to know:
Is there any software besided KingOroot (doesn't work in A5 510M) or Kingroot (I'm not installing that thing because plenty of people says it steal your data or are impossible to remove) which can root without messing with partitions / custom recovery, meaning it won't trigger the knox counter?
Has anyone confirmed that by only having the KNOX counter triggered samsung has denied to give warranty? Even if the phone is unroot?
Is there any method that roots the device without KNOX tripping?
Thanks
if you are on a 5.1.x device, you might wanna give systemless root a try, i think they ported it to 5.1.x as it was a Marshmallow solution initially.
aside of that, nope.
also, a few regions, like Europe, do not accept root, and especially knox triggering as a warranty void.
and my personal two cents, trigger it, no worth at all, if your device ends up unbootable, there is no way they are going to bother reading through your chip of what you have done, most of the time you'll win the procedures if you need warranty
PlutoDelic said:
if you are on a 5.1.x device, you might wanna give systemless root a try, i think they ported it to 5.1.x as it was a Marshmallow solution initially.
aside of that, nope.
also, a few regions, like Europe, do not accept root, and especially knox triggering as a warranty void.
and my personal two cents, trigger it, no worth at all, if your device ends up unbootable, there is no way they are going to bother reading through your chip of what you have done, most of the time you'll win the procedures if you need warranty
Click to expand...
Click to collapse
thanks pal! I believe samsung has made it very easy for support to check whether the knox is triggered or not, otherwise how would it help anything with them fixing less phones?
In germany (its in europe,lol) knox counter on 1 is not a problem when in warranty,just look my thread in q/a section.
The only way they would know that is through going in Download Mode... So, this is just a crazy thought, but I always planned that if something went so wrong that I couldn't fix it myself (I mean if I can go to Download I can probably still fix whatever is wrong unless the device is bricked), I would just break the volume buttons, so that they can't get to Download Mode either. I know, a rash decision, but just food for thought.
Kingroot is easily removed. Don't believe all the silly scare mongering.
It's the most successful root exploit available without tripping knox.
ashyx said:
Kingroot is easily removed. Don't believe all the silly scare mongering.
It's the most successful root exploit available without tripping knox.
Click to expand...
Click to collapse
I have read plenty of cases of the thing working like a virus, sending data to china, making it impossible to remove. I will not put that in my phone. I have tried kinOroot and it didn't work. But sent stuff outside anyways...
fscussel said:
I have read plenty of cases of the thing working like a virus, sending data to china, making it impossible to remove. I will not put that in my phone. I have tried kinOroot and it didn't work. But sent stuff outside anyways...
Click to expand...
Click to collapse
So you just go from what read rather than try it yourself and you think KingOroot is different? It does contact servers in China, that's how it works.
It's easily removed by simply uninstalling or using SuperSume.
Millions of people have used it and I don't know of one documented case of someone being hacked after using it lol.
KingRoot contacts servers in China because it takes little-to-no space. A version of it that doesn't have to contact any server, and still grant you root access... Well, such an app would be over 3GB big, and would be of the same size, even after it finishes the job and gets you root access. It would be extremely inefficient, and that is an understatement. The servers in China contain the exploits that can be used to grant access to root without using a custom recovery (as a custom recovery would trip KNOX). There are thousands and thousands of files in those servers. As I said, it would be possible to make a one-click-root app that can root thousands of devices and that doesn't make contact with any server, but you would have to include all those thousands of files in the app, in order for it to work. No one is crazy enough to do such a thing.
ashyx said:
So you just go from what read rather than try it yourself and you think KingOroot is different? It does contact servers in China, that's how it works.
It's easily removed by simply uninstalling or using SuperSume.
Millions of people have used it and I don't know of one documented case of someone being hacked after using it lol.
Click to expand...
Click to collapse
King-V said:
KingRoot contacts servers in China because it takes little-to-no space. A version of it that doesn't have to contact any server, and still grant you root access... Well, such an app would be over 3GB big, and would be of the same size, even after it finishes the job and gets you root access. It would be extremely inefficient, and that is an understatement. The servers in China contain the exploits that can be used to grant access to root without using a custom recovery (as a custom recovery would trip KNOX). There are thousands and thousands of files in those servers. As I said, it would be possible to make a one-click-root app that can root thousands of devices and that doesn't make contact with any server, but you would have to include all those thousands of files in the app, in order for it to work. No one is crazy enough to do such a thing.
Click to expand...
Click to collapse
I have read that if you try to remove it you can in fact brick your cell...
fscussel said:
I have read that if you try to remove it you can in fact brick your cell...
Click to expand...
Click to collapse
Holy smokes...is this serious? :sly:
ashyx said:
Holy smokes...is this serious? :sly:
Click to expand...
Click to collapse
why so funny? Reson is simple:
After people install kingroot it add many unwanted programs, and also refuses to be uninstalled. People then try to use SuperSU ME to remove it and leave just supersu, and in this process many have got a bricked device. They say this happens because of the kingroot's code to fight anything that tries to remove it.
Now, are you some sort of associate of kingroot?
PlutoDelic said:
if you are on a 5.1.x device, you might wanna give systemless root a try, i think they ported it to 5.1.x as it was a Marshmallow solution initially.
aside of that, nope.
also, a few regions, like Europe, do not accept root, and especially knox triggering as a warranty void.
and my personal two cents, trigger it, no worth at all, if your device ends up unbootable, there is no way they are going to bother reading through your chip of what you have done, most of the time you'll win the procedures if you need warranty
Click to expand...
Click to collapse
systemless root needs custom recovery installed as far as I can tell. So knox counter already 0x1 because of custom recovery.
Also I would like to know, if I install custom recovery, and the an OTA update comes, for 6.0, I would have to first remove TWRP, as so to use the OTA, after that, reinstall TWRP, would that trigger the knox again?
0x2 ??
fscussel said:
why so funny? Reson is simple:
After people install kingroot it add many unwanted programs, and also refuses to be uninstalled. People then try to use SuperSU ME to remove it and leave just supersu, and in this process many have got a bricked device. They say this happens because of the kingroot's code to fight anything that tries to remove it.
Now, are you some sort of associate of kingroot?
Click to expand...
Click to collapse
They say, he says, she says, do you actually have a clue what you are talking about?
I'm pretty sure I do.
It can be removed like any other app.
If you actually knew what you were talking about you'd know that.
It wont allow another root exploit to easily replace it, this is down to some silliness between Chainfire and King team. It is a pain but it can still be removed or replaced no problem. I wrote a whole guide how to do it.
Literally millions have achieved root with KingRoot and for many is the only way they can.
I dont advocate it nor am I against it.
Dont judge something until you've tried it.
I'll say no more on the matter now as I'm getting dizzy.
ashyx said:
They say, he says, she says, do you actually have a clue what you are talking about?
I'm pretty sure I do.
It can be removed like any other app.
If you actually knew what you were talking about you'd know that.
It wont allow another root exploit to easily replace it, this is down to some silliness between Chainfire and King team. It is a pain but it can still be removed or replaced no problem. I wrote a whole guide how to do it.
Literally millions have achieved root with KingRoot and for many is the only way they can.
I dont advocate it nor am I against it.
Dont judge something until you've tried it.
I'll say no more on the matter now as I'm getting dizzy.
Click to expand...
Click to collapse
1) I don't know if it works in my A5 2016 510M, can't find a compatible list or a report.
2) I have read reports of problems uninstalling it.
3) I have read reports of problems uninstalling it with SuperSU Me, including bricking.
4) I find you very arrogant.
fscussel said:
1) I don't know if it works in my A5 2016 510M, can't find a compatible list or a report.
2) I have read reports of problems uninstalling it.
3) I have read reports of problems uninstalling it with SuperSU Me, including bricking.
4) I find you very arrogant.
Click to expand...
Click to collapse
You are obviously learning what you know from other misinformed users.
1. Just try it if it doesn't work it doesn't work just uninstall it.
2. As I have said, no such issue.
3. There's a reason why replacing it with SuperSU bricks some devices and it has absolutely nothing to do with kingroot.
If you attempt to replace it with SuperSU on anything above 5.0.2 on a Samsung device it's likely to soft brick it and cause a boot loop.
This is due to Samsungs root restriction policy in the kernel. The same goes for Android 6.0 devices.
To root with supersu on these devices you need a patched boot.img to remove the selinux restriction.
4. I find you very misinformed.
ashyx said:
You are obviously learning what you know from other misinformed users.
1. Just try it if it doesn't work it doesn't work just uninstall it.
2. As I have said, no such issue.
3. There's a reason why replacing it with SuperSU bricks some devices and it has absolutely nothing to do with kingroot.
If you attempt to replace it with SuperSU on anything above 5.0.2 on a Samsung device it's likely to soft brick it.
This is due to Samsungs root restriction policy in the kernel. The same goes for Android 6.0 devices.
To root with supersu on these devices you need a patched boot.img to remove the selinux restriction.
4. I find you very misinformed.
Click to expand...
Click to collapse
very misinformed but I have just saved my device from brick, because if you did your work your would see it's android 5.1.1 and it's samsung.
Now let me know if it works with a samsung 5.1.1 with KNOX and perhaps I will try it.
Also let me know how to remove it and install SuperSU over it.
fscussel said:
very misinformed but I have just saved my device from brick, because if you did your work your would see it's android 5.1.1 and it's samsung.
Now let me know if it works with a samsung 5.1.1 with KNOX and perhaps I will try it.
Also let me know how to remove it and install SuperSU over it.
Click to expand...
Click to collapse
Kingroot won't brick your device, replacing it with supersu will. Not sure where in this discussion I said anything to the contrary? :what:
ashyx said:
Kingroot won't brick your device, replacing it with supersu will. Not sure where in this discussion I said anything to the contrary? :what:
Click to expand...
Click to collapse
very non-productive answer... please check again