Related
Ok, i have flash BL without knowing the knox counter, now its 0x01... well, my question are:
In future it will be possible a reset?
No warranty?
Will rise again the counter of knox if i flash rom or kerner, or its only for BL?
yonghai94 said:
Ok, i have flash BL without knowing the knox counter, now its 0x01... well, my question are:
In future it will be possible a reset?
No warranty?
Will rise again the counter of knox if i flash rom or kerner, or its only for BL?
Click to expand...
Click to collapse
What bootloader?
Where did I you find it?
Knox cannot be reset. With a tripped Knox you cannot use Samsung Pay nor get OTA updates, and also you voided your warranty.
t-shock said:
What bootloader?
Where did I you find it?
Click to expand...
Click to collapse
XtreStoLite 2.0 i flash the guide with BL..
roydok said:
Knox cannot be reset. With a tripped Knox you cannot use Samsung Pay nor get OTA updates, and also you voided your warranty.
Click to expand...
Click to collapse
So I feeling really nice xD thanks
t-shock said:
What bootloader?
Where did I you find it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467
From here, i flash the bootloader...
@yonghai94 Can you send a screenshot?
t-shock said:
@yonghai94 Can you send a screenshot?
Click to expand...
Click to collapse
a screenshot with what? when was in odin mode that can see a knox 0x01 or system info?
roydok said:
Knox cannot be reset. With a tripped Knox you cannot use Samsung Pay nor get OTA updates, and also you voided your warranty.
Click to expand...
Click to collapse
Thats not true i tripped knox and after i got bored trying out custom Roms put original rom back on and received 5.1.1 update without issue.
roydok said:
Knox cannot be reset. With a tripped Knox you cannot use Samsung Pay nor get OTA updates, and also you voided your warranty.
Click to expand...
Click to collapse
1) whether or not Samsung Pay is affected our not hasn't been proven yet. I wouldn't normally use it anyway
2) OTA receipt is no different from any other rooted device, unroot and it should work or just wait for a Rom with the new OTA built in.
3) warranty really depends on what the issue is, if you deal with your wireless provider or have to deal with Samsung and where you are.
It had never been a big deal or a hindrance to me on past devices.
roydok said:
Knox cannot be reset. With a tripped Knox you cannot use Samsung Pay nor get OTA updates, and also you voided your warranty.
Click to expand...
Click to collapse
tripped knox only disables samsung pay you can still get ota's just you need to have unmodifed stock firmware!
Inwould really like to use samsung pay. Is there absolutely no way to reset Knox trip counter? ?
jcorcione said:
Inwould really like to use samsung pay. Is there absolutely no way to reset Knox trip counter? ?
Click to expand...
Click to collapse
Currently no.
Dang
jcorcione said:
Dang
Click to expand...
Click to collapse
ONLY board hardware replacement will resolve this issue.
roydok said:
Knox cannot be reset. With a tripped Knox you cannot use Samsung Pay nor get OTA updates, and also you voided your warranty.
Click to expand...
Click to collapse
No, that both Samsung Pay and OTA updates won't work not because tripping knox, but because rooted device. Also online bank security keycode apps won't work in a rooted device as Samsung Pay won't, just because pay security reasons. With tripped knox and non rooted device both functionalities should still work.
What won't work with tripped knox (rooted or not rooted) is Samsung My Knox, so you won't be able to use both personal and enterprise enviroment on same device, or you won't be able to use two different whatsapp accounts on same device using My Knox (without need of third party whatsapp clients or swap directories or things like that...).
Enviado desde mi SM-T520 usando Tapatalk 2
jaswinky said:
No, that both Samsung Pay and OTA updates won't work not because tripping knox, but because rooted device. Also online bank security keycode apps won't work in a rooted device as Samsung Pay won't, just because pay security reasons. With tripped knox and non rooted device both functionalities should still work.
What won't work with tripped knox (rooted or not rooted) is Samsung My Knox, so you won't be able to use both personal and enterprise enviroment on same device, or you won't be able to use two different whatsapp accounts on same device using My Knox (without need of third party whatsapp clients or swap directories or things like that...).
Enviado desde mi SM-T520 usando Tapatalk 2
Click to expand...
Click to collapse
So why does Android pay work then?
Sent from my Nexus 7 using XDA-Developers mobile app
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
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
Is therer any way to use Samsung Pay on a rooted S6 with Android 7?
May be possible
If you have tripped Knox Counter while rooting. You can never use Samsung Pay I guess. If you have Magisk Root Method If the safetynet feature checks out then. You can probably use Samsung Pay.
I've seen a thread where a guy said it's possible to use Samsung Pay on a rooted S7 by flashing skme sort of stock kernel. Is something like that possible on the S6?
Somehow on my S8+ with TWRP and custom ROM, KNOX isn't tripped unlike my S7 Edge. I've always thought that flashing custom recovery will trip KNOX. Any ideas why it isn't tripped? Mayby how to figure it out and reproduce?
Here's a screenshot from S8+
Some custom kernels will allow masking of Knox being tripped.
It is and apps that won't run with it tripped still will won't run. It is purely cosmetic...
did you try any other app to corroborate devcheck app finding?
raul6 said:
did you try any other app to corroborate devcheck app finding?
Click to expand...
Click to collapse
I've just tried phone info Samsung from play store. Also reported as not tripped. Knox warranty void: 0x0
Can you recommend something else?
It could well be, as ultramag69 said earlier, that your custom rom is simply masking the fact that knox is in fact tripped. Try Secure Folder if it works
This is not a question for the Note 9 community.
To test, just try using something Knox related, like:
Secure Boot
Secure Folder
Samsung Pay
Samsung Pass
Could be related to SamFail but not sure.
willhemmens said:
This is not a question for the Note 9 community.
To test, just try using something Knox related, like:
Secure Boot
Secure Folder
Samsung Pay
Samsung Pass
Could be related to SamFail but not sure.
Click to expand...
Click to collapse
Well if it would be reproducible I would root Note 9 so to me it was Note 9 related.
It's the ROM that is masking it as mentioned above :crying:
I was hoping sami f**** up