Root & encryption? - Galaxy S6 Q&A, Help & Troubleshooting

So I recently got the Galaxy s6. I had a note 3 prior to this, it was rooted but I could never get it to encrypt while being rooted. So this time I decided to encrypt my phone before rooting it, I still haven't tried rooting it I'm fear of the encryption bricking my phone. Can someone put my mind to ease that it would? I been searching on Google and couldn't find anything. Also, if that is the case, how do I encrypt a phone after I root it?
Edit: another question I can't find a straight answer to, what exactly does Knox do? I can't seem to find the Knox app on my s6 like I did with my note 3. I checked on the s6 and Knox hasn't been tripped

I don't know about the root/encryption thing.
But there's two things KNOX does.
One it is used for enterprise purposes where you can store confidential data on a KNOX encrypted partition.
Two, it is the detecting mechanism that checks wether your phone has been rooted/unlocked.
You can't find the app because you need to download it from the Play Store on the S6 and newer Samsung devices.

@MikeChannon, thread is dead. Lock it up.
Sent from my Samsung Galaxy S6 using XDA Labs

Related

Any way to root yet without voiding warranty?

I'm new to Samsung devices and apparently that Knox efuse is a real SOB to deal with. I don't need custom recoveries/kernels or anything fancy, just want to be able to use superuser.
I know there's at least *a* root exploit for the S7, but I'm sure it also blows the efuse. Is there a "systemless root" or anything like what the S5/S6 had that doesn't trip knox?
your question can be answered with a 5 minute search but no. bootloader is locked, system is verified on boot
I thought that's what the point of non-system root was though? So that you aren't modifying system
There is no way to root without tripping Knox (the 0x1 Warranty Void flag). This has been the case since the eFuse was introduced (at least back on the Note 3).
Sent from my SM-G930W8 using Tapatalk
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
123421342 said:
your question can be answered with a 5 minute search but no. bootloader is locked, system is verified on boot
Click to expand...
Click to collapse
That's for Snapdragon 820 units. We don't know if the OP has Snapdragon or Exynos
Sent from my SM-G930W8 using Tapatalk
I don't have my S7 yet, but I was going to get one soon. How would I find out if it's Snapdragon or Exynos once I get one?
I swear I saw some threads about S6 rooting without tripping Knox...
drfsupercenter said:
I don't have my S7 yet, but I was going to get one soon. How would I find out if it's Snapdragon or Exynos once I get one?
I swear I saw some threads about S6 rooting without tripping Knox...
Click to expand...
Click to collapse
If you buy a US version, it should be snapdragon. The international/non-US version is the Exynos.
Ah, OK. Well I'm in the US so that answers that.
I would not risk it for the biscuit
http://pingpongroot.co/PingPongRoot-tutorial.html
This is the thing I was talking about. It works for the S6/S6 Edge, so why can't we do this on S7?
Something I was thinking about... Knox basically verifies the checksum of the system partition upon booting, right? Well, there are system updates (I had two of them after turning the phone on the first time) and those obviously modify the system partition. Which means the checksum has to be updated during that process or it would trip Knox just for doing an OTA update! So the million-dollar question is, couldn't we just spoof that ourselves?
And more importantly, why wouldn't "systemless root" do the trick? I can understand tripping Knox if you start deleting things from /system using your new root powers, but what about just using it to modify data? That's one of the main things I use root for, backing up and restoring data, which is a totally separate partition from /system.
Rooting Without Voiding Warranty [Samsung Galaxy s7] DEFINITELY POSSIBLE
drfsupercenter said:
I'm new to Samsung devices and apparently that Knox efuse is a real SOB to deal with. I don't need custom recoveries/kernels or anything fancy, just want to be able to use superuser.
I know there's at least *a* root exploit for the S7, but I'm sure it also blows the efuse. Is there a "systemless root" or anything like what the S5/S6 had that doesn't trip knox?
Click to expand...
Click to collapse
There most certainly is a very easy way to root the Samsung galaxy s7 snapdragon to use superSU.
I did it on my sprint Samsung galaxy s7 very easily and sprint is supposed to make it the
hardest.
http://forum.xda-developers.com/galaxy-s7/how-to/samsung-galaxy-s7-sm-g930p-root-xposed-t3502829
I did this like a month ago, but ended up undoing it thanks to Pokémon Go and SafetyNet. If you know a solution let me know...
drfsupercenter said:
I'm new to Samsung devices and apparently that Knox efuse is a real SOB to deal with. I don't need custom recoveries/kernels or anything fancy, just want to be able to use superuser.
I know there's at least *a* root exploit for the S7, but I'm sure it also blows the efuse. Is there a "systemless root" or anything like what the S5/S6 had that doesn't trip knox?
Click to expand...
Click to collapse
Complete guide to root without voiding warranty!
http://forum.xda-developers.com/galaxy-s7/how-to/samsung-galaxy-s7-sm-g930p-root-xposed-t3502829

[Question] Rooting a SM-T817V and SM-N920V without tripping KNOX or using ext. Device

So i own a Samsung Galaxy Note 5 (SM-N920V) and a Samsung Galaxy Tab S2 (SM-T817V) Both sold by Verizon and both on Android OFW 6.0.1
I've been reading a lot of posts on XDA saying that rooting these devices could potentially Brick the devices should KNOX be tripped (Because AT&T and Verizon are jackasses).
I was wondering if this has changed recently or not (I know that KingRoot fails completely cause i tried today).
Also due to my PC being out of commision the only methods i have for rooting are those that can be done on the device itself without the help of USB external devices such as a PC.

KingRoot Questions

1. Did anyone try KingRoot and found a working method?
2. Does this trip the Knox Counter as soon as it works?
Both questions are related to the portable version of KingRoot for Android.
Thanks.
1) no
2) no one used it so they can't say what it does, if anything
Mystixor said:
2. Does this trip the Knox Counter as soon as it works?
Both questions are related to the portable version of KingRoot for Android.
Thanks.
Click to expand...
Click to collapse
Any method of rooting this device will trip the Knox counter.
the_scotsman said:
Any method of rooting this device will trip the Knox counter.
Click to expand...
Click to collapse
Really? And I always thought it was due to flashing a new firmware...
Sent from my SM-G955F using XDA Labs
Mystixor said:
Really? And I always thought it was due to flashing a new firmware...
Sent from my SM-G955F using XDA Labs
Click to expand...
Click to collapse
Nope, flashing new official samsung firmware won't trip Knox.
the_scotsman said:
Nope, flashing new official samsung firmware won't trip Knox.
Click to expand...
Click to collapse
Well what I wanted to stress wasn't that a custom firmware trips Knox but that KingRoot does not flash a new firmware and therefore potentially does not trip Knox. All it uses is an exploit to change some specific root-determining system files.
Sent from my SM-G955F using XDA Labs
Mystixor said:
Well what I wanted to stress wasn't that a custom firmware trips Knox but that KingRoot does not flash a new firmware and therefore potentially does not trip Knox. All it uses is an exploit to change some specific root-determining system files.
Sent from my SM-G955F using XDA Labs
Click to expand...
Click to collapse
Knox detects if system files are changed, it is simply not possible to change or modify any system files in any way without tripping Knox. So if you managed to use any sort of 3rd party application to root (not possible currently), the application would trip Knox, because it modifies system files.
The Knox security bombproof to the level that a physical fuse is blown inside the phone when Knox is tripped, meaning there is no way to un-trip Knox through software once it's been tripped. It's possible to fool the ROM to think that it's not tripped (like some S8 ported ROMs, to enable secure folder), but warranty can never be restored, as the Knox counter in download mode can't be tricked.
galaxyYtester said:
Knox detects if system files are changed, it is simply not possible to change or modify any system files in any way without tripping Knox. So if you managed to use any sort of 3rd party application to root (not possible currently), the application would trip Knox, because it modifies system.
Click to expand...
Click to collapse
It was possible
Kingroot used to work on s6 you could root with knox intact and use all root features only thing that would trip knox was custom recovery and/or rom
Wish it could be done with s8
skinza said:
It was possible
Kingroot used to work on s6 you could root with knox intact and use all root features only thing that would trip knox was custom recovery and/or rom
Wish it could be done with s8
Click to expand...
Click to collapse
That was over 2 years ago, when you could use root tools to reset the counter back to not tripped. Nowadays the security is much more strict, and there's a physical fuse inside the phone that gets blown when Knox is tripped. Knox isn't a bootloader-only thing anymore, now it scans system files to see any third party tampering, and gets tripped if it's detected.
galaxyYtester said:
That was over 2 years ago, when you could use root tools to reset the counter back to not tripped. Nowadays the security is much more strict, and there's a physical fuse inside the phone that gets blown when Knox is tripped. Knox isn't a bootloader-only thing anymore, now it scans system files to see any third party tampering, and gets tripped if it's detected.
Click to expand...
Click to collapse
Yep, Knox is totally solid these days. Its impossible to not trip it when rooting. F*** it and root the phone anyway, if it breaks ill claim it on insurance not through warranty.
Sent from my SM-G955F using Tapatalk
galaxyYtester said:
That was over 2 years ago, when you could use root tools to reset the counter back to not tripped. Nowadays the security is much more strict, and there's a physical fuse inside the phone that gets blown when Knox is tripped. Knox isn't a bootloader-only thing anymore, now it scans system files to see any third party tampering, and gets tripped if it's detected.
Click to expand...
Click to collapse
There was no need to reset anything i rooted used some tweaks then when i restored my knox was still 0x0
I never phiscally reset anything
Even while i was rooted my phone still said 0x0
skinza said:
There was no need to reset anything i rooted used some tweaks then when i restored my knox was still 0x0
I never phiscally reset anything
Even while i was rooted my phone still said 0x0
Click to expand...
Click to collapse
I didn't mean that, I meant that if you rooted with a method that worked through bootloader (Not kingoroot), you still could restore Knox to not tripped through root tools. Knox security used to be that simple to bypass, nowadays it's impossible to revert once tripped.
Having successfully rooted two HTC devices and a Samsung devices in the past and loved every minute of it, I was kinda excited when Kingroot props said it was possible to root the later Notes... but I never did my old Note 4, partially but not primarily because of the Knox issue.
I've heard different things RE: Knox, pretty much covers what everyone else has been saying here (no way to reset Knox, possible to reset Knox, "soft-root" via Kingroot trips/doesn't trip Knox counter, etc.) Personally, since the Note 4 issue where (correct me if I'm wrong) that Samsung phone was the first one that full rooting was impossible, I've pretty much given up on rooting for a while. Though S8+ may be possible to root (provided you're OK with possibly never resetting Knox), I'm OK with my S8+ non-rooted stock (for now), just like I HAD to be OK with my old Note 4 never being able to be rooted.
I guess my bottom line take on all this is, root at your own risk, know what you're doing, and do it if you can say "Knox be damned" and have no intention of trading the phone back in or reselling it to someone who knows nothing about rooting.
Sent from my SM-G955U using XDA Premium HD app
BereanPK said:
Having successfully rooted two HTC devices and a Samsung devices in the past and loved every minute of it, I was kinda excited when Kingroot props said it was possible to root the later Notes... but I never did my old Note 4, partially but not primarily because of the Knox issue.
I've heard different things RE: Knox, pretty much covers what everyone else has been saying here (no way to reset Knox, possible to reset Knox, "soft-root" via Kingroot trips/doesn't trip Knox counter, etc.) Personally, since the Note 4 issue where (correct me if I'm wrong) that Samsung phone was the first one that full rooting was impossible, I've pretty much given up on rooting for a while. Though S8+ may be possible to root (provided you're OK with possibly never resetting Knox), I'm OK with my S8+ non-rooted stock (for now), just like I HAD to be OK with my old Note 4 never being able to be rooted.
I guess my bottom line take on all this is, root at your own risk, know what you're doing, and do it if you can say "Knox be damned" and have no intention of trading the phone back in or reselling it to someone who knows nothing about rooting.
Click to expand...
Click to collapse
Root became possible on note 4 after a program to alter cid to dev version was released. Also because something was possible before shouldn't mean it's possible anymore as things are updated, common sense.
skinza said:
There was no need to reset anything i rooted used some tweaks then when i restored my knox was still 0x0
I never phiscally reset anything
Even while i was rooted my phone still said 0x0
Click to expand...
Click to collapse
As I said, it's not possible to root the S8 without tripping Knox. Regardless of how it was with the S6. This is the S8, it's different. It cannot be done.
the_scotsman said:
As I said, it's not possible to root the S8 without tripping Knox. Regardless of how it was with the S6. This is the S8, it's different. It cannot be done.
Click to expand...
Click to collapse
Definitely
Those days are over unless someone gets lucky,i know they wont though just wishful thinking
Well.. Do samsung says knox became bulletproof, or does the best hackers see it that way to?
rk73 said:
Well.. Do samsung says knox became bulletproof, or does the best hackers see it that way to?
Click to expand...
Click to collapse
Both sides.
Sent from my SM-G955F using XDA Labs

S6/S7 Root clarification?

This may be a bonehead question but...
I've been reading some of the forums for a few days now and Im at my wits end with not being able to root my Verizon Galaxy S6 (SM-G920V) due to bootloader blockage. I am noticing that it is seemingly possible to root an S7 on Verizon though. How is this possible considering the same stipulations, and an S6 being the more outdated phone??
On the S6 i believe it's possible via CF-AutoRoot, however, mine (G920W8) got it's IMEI/EFS lost and corrupted by the stock recovery it flashes back so not really recommend using it.
Protip: don't get Verizon Locked devices if you are willing to Root

Disable Knox Xcover 5 (not yet rooted)

I"d like to root my new phone before putting any stuff on it, but according to the Magisk installation guide using it will trip Knox.
Already knowing the unofficial software warning when rebooting from my current phone, this is a nuisance i"d like to avoid.
Sadly, the disable option for all Knox apps is inaccessible.
Does anyone know how to enable disabling them on the not yet rooted phone?

Categories

Resources