Related
As you may already know, the latest Samsung firmwares came with a new secured bootloader. You can recognize it in download mode easily. It states: Knox warranty void: 0x0 or 0x1.
As for now, there is no way to reset that flag from 0x1 to 0x0.
Then I read in a comment of Chainfires post concerning that flag, that as long as you do not try to downgrade to a non secured bootloader, this flag will not change. He claims to have that information directly from Samsung.
https://plus.google.com/u/0/+Chainfire/posts
Jeffery Butler said:
FYI...Samsung told me that Knox warranty becomes 0x1(void) when the device with secured bootloader attempts to have non-secured bootloader. MH1 is the very first binary with secured bootloader. If MH1 is attempted to be downgraded to lower version(i.e. MGD) which has non-secured bootloader, then Knox warranty becomes void forever, and this means that the device can be used only for non-Knox device(no container can be created).
Click to expand...
Click to collapse
Has anyone already experience with rooting an "untouched" S4 which has the secured bootloader and can confirm or decline that?
- - - - - - - - - -
Conclusions and Facts about KNOX-enabled firmwares (based on statements from chainfires post and it's comments above, ans based on this thread)
Not possible to downgrade to KNOX-disabled firmwares/bootloaders (An attempt sets 0x1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package: see http://forum.xda-developers.com/showthread.php?t=2444671, not confirmed)
Even if you flash a KNOX-enabled firmware via odin (e.g. the latest fw) knox will be set to 0x1
Flashing unsigned or modified images via odin will set knox to 0x1
Samsung stated, resetting the flag is impossible
KNOX is mandatory and can not be completely removed
Warranty Void is no counter, it is a flag (0,1) it was never seen 0x2 or so
Mirroring all partitions from a clean 0x0-Device to a 0x1-Device via JTAG produces an unfunctional device (reversible by restoring the 0x1 partitions on the phone)
KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the knox warranty
Assumptions on how KNOX flag in bootloader works:
Some experts think, an eFuse is involved. (http://en.wikipedia.org/wiki/EFUSE). An eFuse is mostly only incremential. Even unwriteable by low level tools or JTAG. But it is still not proven, that eFuse is used.
Knox technical information:
https://www.samsungknox.com/overview/technical-details
Also interested in this..
(don't really have high expectations though... )
I used the CF Auto Root to root an unlocked i9505 and the flag changed. I have since un-rooted and restored to factory settings however the flag remains the same and no Knox container can be created on the device now.
If anybody has an update to a solution for this that would be greatly appreciated.
My status changed to 0x1 after flashing full NON-ROOTED , UNTOUCHED XXUDMGG with STOCK KERNEL MH1!!! :/
In my case STOCK KERNEL triggered this flag! When I tried to downgrade the FW it always failed in Odin and KNOX WARRANTY wasn't increased...
It's really confusing and it looks like Samsung is lying to us....
Lie about what?
DjeMBeY said:
My status changed to 0x1 after flashing full NON-ROOTED , UNTOUCHED XXUDMGG with STOCK KERNEL MH1!!! :/
In my case STOCK KERNEL triggered this flag! When I tried to downgrade the FW it always failed in Odin and KNOX WARRANTY wasn't increased...
It's really confusing and it looks like Samsung is lying to us....
Click to expand...
Click to collapse
You flashed stock firmware and you voided KNOX Warranty?
Damn...
I wish you good luck in trying to figure out what to do now!
In the same Chainfire Google+ post, somebody mentioned there could be a so called 'eFuse'.
Like a normal fuse, a piece of hardware gets broken beyond repair. The 'e' means that this can be triggered and checked by software.
But I am no expert, this is just hearsay.
Sent from my GT-I9505 using xda app-developers app
bungadudu said:
Lie about what?
Click to expand...
Click to collapse
About details... This flag should change ONLY if you try to downgrade the bootloader but it's not the case...
nfsmw_gr said:
You flashed stock firmware and you voided KNOX Warranty?
Damn...
I wish you good luck in trying to figure out what to do now!
Click to expand...
Click to collapse
Yeah, I'm really angry! :/
I simply repacked MGG and included previous STOCK Kernel MH1... KNOX WARRANTO VOID = 0x1
WTF Samsung????!!????!!! :/
seems samsung also checks kernel and recovery binaries. whenever something tries to bypass knox the flag is incremented.
OT: It sucks and I really will sell S4 for Nexus 5 when it's released
theq86 said:
seems samsung also checks kernel and recovery binaries. whenever something tries to bypass knox the flag is incremented.
OT: It sucks and I really will sell S4 for Nexus 5 when it's released
Click to expand...
Click to collapse
I think Samsung's aim was to make the Knox functionality as 'secure' as possible and it seems to have worked (for now) and so is fulfilling its intended purpose. When I first heard about it, it seemed to be something intended for business/enterprise mobile use, so wasn't expecting it to roll out to all consumer handsets (especially not fully enforcing it).
Once the flag is incremented does that mean that the knox functionality can no longer be used? I know we all want to have a choice, but are the current consequences just that we are unable to downgrade firmware?
harise100 said:
In the same Chainfire Google+ post, somebody mentioned there could be a so called 'eFuse'.
Like a normal fuse, a piece of hardware gets broken beyond repair. The 'e' means that this can be triggered and checked by software.
But I am no expert, this is just hearsay.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Interesting. Offtopic... I remember the Xbox 360 used a similar thing, 192 fuses and one was blown every time the bootloader and/or dashboard was updated, eventually they started using this to prevent downgrades and detect tampering.
They want Knox-enabled firmwares to run on totally secure, untampered phones. Not surprising, really.
jas0nuk said:
Interesting. Offtopic... I remember the Xbox 360 used a similar thing, 192 fuses and one was blown every time the bootloader and/or dashboard was updated, eventually they started using this to prevent downgrades and detect tampering.
They want Knox-enabled firmwares to run on totally secure, untampered phones. Not surprising, really.
Click to expand...
Click to collapse
Well, I am always a fan of full reversibility. It's like a flaw to me to have a visual mark that I changed something.
If that Knox flag would touch the warranty only in case you used the phone in a company, and would not change anything for normal users I could live with is. But how to distinguish exactly between private and corporate usage?
It's unfair to be forced this way...
Does anyone know hot o downgrade ABOOT.MBN
I tried to do JTAG with an old bootloader and now i have no power at all, If I do JTAG with a new bootloader, then phone works fine again.
Even all partition from a good old phone I have copied to new I9505 and as soon flash pass, no power up at all.
Any idea how to downgrade ABOOT.MBN and good scripts to do that?
Thanks.
exprxp said:
I tried to do JTAG with an old bootloader and now i have no power at all, If I do JTAG with a new bootloader, then phone works fine again.
Even all partition from a good old phone I have copied to new I9505 and as soon flash pass, no power up at all.
Click to expand...
Click to collapse
Another indicator for an eFuse. Even with JTAG you can not reprogram the fuse chip. It could be a check somewhere in the low level firmware, or even in PBL for the knox warranty state...
Remember, it could have been there since S4 release. Just that the new bootloader enabled the fuse thing.
theq86 said:
Another indicator for an eFuse. Even with JTAG you can not reprogram the fuse chip. It could be a check somewhere in the low level firmware, or even in PBL for the knox warranty state...
Click to expand...
Click to collapse
What I haven't tried yet to replace eMMC chip, I think that KNOX security inside that chip. I tried to do JTAG via USB Recovery tool for QDLOAD device. When my phone works fine I just shot Resistor on a board and phone will go into QDLOAD by itself.
I will try all ways then I can write you back the status of my job.
I'm very interested in the qdload thing. If I got it right, you can do jtag via usb? how ? what tools needed ?
DjeMBeY said:
I simply repacked MGG and included previous STOCK Kernel MH1... KNOX WARRANTO VOID = 0x1
WTF Samsung????!!????!!! :/
Click to expand...
Click to collapse
So basically you flashed a modified and thus nonofficial firmware?
SAFE with Knox
I am not a developer so I just add here a few links from Engadget:
It's an IT manager's pipe dream, of sorts. A comprehensive collection of features that include Security Enhanced (SE) Android, secure boot, TrustZone-based Integrity Monitoring (TIMA) for protecting the kernel, Single Sign On (SSO) and that application container concept made famous by BlackBerry, just to name a few
Feb 2013 - Samsung announces SAFE with Knox
http://www.engadget.com/2013/02/25/samsung-safe-with-knox/
May 2013 - Samsung Knox gets official DoD approval for government use
http://www.engadget.com/2013/05/03/samsung-knox-gets-official-dod-approval-for-government-use/
Sept 2013 - Samsung opens up Knox security platform to all consumers - HAPPY people!
http://www.engadget.com/2013/09/04/samsung-opens-up-knox-security-platform-to-all-consumers/
http://www.engadget.com/2013/09/04/lookout-knox/
So it is a 'Feature' - we still should have the option to say 'No thanks'.
trveller72 said:
I am not a developer so I just add here a few links from Engadget:
It's an IT manager's pipe dream, of sorts. A comprehensive collection of features that include Security Enhanced (SE) Android, secure boot, TrustZone-based Integrity Monitoring (TIMA) for protecting the kernel, Single Sign On (SSO) and that application container concept made famous by BlackBerry, just to name a few
Feb 2013 - Samsung announces SAFE with Knox
http://www.engadget.com/2013/02/25/samsung-safe-with-knox/
May 2013 - Samsung Knox gets official DoD approval for government use
http://www.engadget.com/2013/05/03/samsung-knox-gets-official-dod-approval-for-government-use/
Sept 2013 - Samsung opens up Knox security platform to all consumers - HAPPY people!
http://www.engadget.com/2013/09/04/samsung-opens-up-knox-security-platform-to-all-consumers/
http://www.engadget.com/2013/09/04/lookout-knox/
So it is a 'Feature' - we still should have the option to say 'No thanks'.
Click to expand...
Click to collapse
darn it.. Samsung :x :screwy::screwy:
Send my E-960/S4 LTE/N2 GSM and /Galaxy Y to xda
Does knox warranty change the device status to unofficial? If so, this will also break Miracast/screen mirroring (HDCP fails) permanently until one is able to reset the counter.
Just wondering how many of you out there have KNOX 0x1, and why?
here comes the 1st unfortunate one
I, be cause i hâve rooted my S4
Me too i use cm10.2
Sent from my GT-I9505 using xda app-developers app
Let's say I'm still on old bootloader and I won't update it, ever.
.TanTien said:
Let's say I'm still on old bootloader and I won't update it, ever.
Click to expand...
Click to collapse
I'm rooted so I could use Odin Mobile, flash 4.3, keeping old bootloader, stay rooted and KNOX 0x0.
But I'm still trying to figure out if it's possible to use custom recovery like CWM or TWRP without triggering KNOX
Alternatively some other way to make NanDroid backups ...
I dont, luckily on old bootloader, running stock 4.2.2 with root only, im planning to wait till official 4.4 kitkat releases
Sent from my GT-I9505 using xda premium
Sadly I'm here...
From universe with my gs4 snapdragon powered!
Old bootloader and intend to keep it like that
Sent from my GT-I9505 using XDA Premium 4 mobile app
0x1 before, but now 0x0
my s4 is 0x1 before, but now 0x0 on knox, but i returned it for warranty purposes (WIFI problem), and guess what!
new main board means new bootloader, mean my knox vwarranty void reverted back to 0x0.
Here in the Philippines, 0x1 is still under warranty. :laugh:
aboutmarkanthony said:
my s4 is 0x1 before, but now 0x0 on knox, but i returned it for warranty purposes (WIFI problem), and guess what!
new main board means new bootloader, mean my knox vwarranty void reverted back to 0x0.
Here in the Philippines, 0x1 is still under warranty. :laugh:
Click to expand...
Click to collapse
Good for you :good:
Have heard people talking about flashing wrong firmware by purpose in order to get device (or main board) replaced.
But hopefully some smart dev find another solution down the road
I have Knox 0x1 and Phone still within warranty peroid.
But dont care low custom Roms too much ...
Don't have Knox, I have the Google Play edition and bootloader is unlocked.
0x1 and dont really care
I wanted original rooted rom, now I have it with bonus KNOX 0x1 on top of it
Still 0x0 here with 4.2.2. bootloader on GoldenEye custom 4.3, had very briefly entertained the idea of going fully official with no root/custom anything, but installed GoldenEye 4.3 ROM and its too good to leave. Would mainly miss being able to remove the extra bloat/use an adblocker and a few other things, but overall just like a lighter, slighly tweaked, stock based ROM. Interesting to see quite a few with 0x1.
gsmyth said:
Still 0x0 here with 4.2.2. bootloader on GoldenEye custom 4.3, had very briefly entertained the idea of going fully official with no root/custom anything, but installed GoldenEye 4.3 ROM and its too good to leave. Would mainly miss being able to remove the extra bloat/use an adblocker and a few other things, but overall just like a lighter, slighly tweaked, stock based ROM. Interesting to see quite a few with 0x1.
Click to expand...
Click to collapse
Yes ... Interesting to see so many with 0x1 and quite a lot considering 0x1 (including my self).
Mittaa said:
Yes ... Interesting to see so many with 0x1 and quite a lot considering 0x1 (including my self).
Click to expand...
Click to collapse
Thought you had a solution or action plan?
YOSEFE said:
Thought you had a solution or action plan?
Click to expand...
Click to collapse
I have a solution and an action plan :laugh:
My solution is to f*** Samsung and my plan is to do this by triggering KNOX 0x1.
I accept playing around flashing custom firmware is my own decision and if something goes wrong I will pay for repair.
But if something not related to flashing get defective (let say screen or button), and Samsung Service center tells me that I lost warranty because of KNOX 0x1. Then I might have to make a bad firmware flash, play dumb and get me a new main board paid by Samsung!
I can't accept not being able to make a NanDroid backup and I have a need of controlling misbehaving apps by freezing or removing even if this requires root (Samsung bloatware included).
I got knox 0x1 and don't really care about warrant void I have other options for replacement
Sent from my GT-I9505 using Tapatalk
Ok, so I recently (about 2 weeks ago) bought a brand-new/stock Samsung Galaxy S3 through Amazon as an upgrade for Verizon. When I received and activated it, etc, it went through a series of downloading/rebooting/installing screens which I assume means that it was updating to the latest official firmware.
Anyway, now I want to try putting a custom ROM on my S3 (I'm kinda new at this, like I just started reading about it yesterday), and as far as I know, it's running Android version 4.3, which is also said to contain Knox, which would prevent loading any custom ROMs. However, when I go into download mode on my S3, it says the following:
---------------------------
ODIN MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
----------------------------
As far as I can tell, there's no mention of Knox, but maybe there's something I'm missing?
As I said, I'm new at this, so I might be missing alot of stuff. But my main question is whether or not I'd be able to root my phone and flash a custom ROM without damage (barring my own mistakes)?
OblivionDawn said:
Ok, so I recently (about 2 weeks ago) bought a brand-new/stock Samsung Galaxy S3 through Amazon as an upgrade for Verizon. When I received and activated it, etc, it went through a series of downloading/rebooting/installing screens which I assume means that it was updating to the latest official firmware.
Anyway, now I want to try putting a custom ROM on my S3 (I'm kinda new at this, like I just started reading about it yesterday), and as far as I know, it's running Android version 4.3, which is also said to contain Knox, which would prevent loading any custom ROMs. However, when I go into download mode on my S3, it says the following:
---------------------------
ODIN MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
----------------------------
As far as I can tell, there's no mention of Knox, but maybe there's something I'm missing?
As I said, I'm new at this, so I might be missing alot of stuff. But my main question is whether or not I'd be able to root my phone and flash a custom ROM without damage (barring my own mistakes)?
Click to expand...
Click to collapse
Knox has nothing to do with locked bootloader from 4.3 version. You're no 4.3 so no flashing custom rom/kernel/recovery for you. There is a work around called safestrap and it's not fully functional yet...you just have to wait a bit ...longer see how everything play out!
Oh, I was under the impression that Knox was the thing causing the bootloader to be locked. You're saying that 4.3 is just universally locked for the time being?
Also, am I still able to root my S3 using Saferoot while it's on 4.3?
OblivionDawn said:
Oh, I was under the impression that Knox was the thing causing the bootloader to be locked. You're saying that 4.3 is just universally locked for the time being?
Also, am I still able to root my S3 using Saferoot while it's on 4.3?
Click to expand...
Click to collapse
Yes and Yes, you can use saferoot to root 4.3.
OblivionDawn said:
Oh, I was under the impression that Knox was the thing causing the bootloader to be locked. You're saying that 4.3 is just universally locked for the time being?
Also, am I still able to root my S3 using Saferoot while it's on 4.3?
Click to expand...
Click to collapse
Verizon is responsible for locking the bootloader. Knox has nothing to do with it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Verizon is responsible for locking the bootloader. Knox has nothing to do with it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Tell that to every s4 owner.
ThePagel said:
Tell that to every s4 owner.
Click to expand...
Click to collapse
All knox does is count, unless I'm missing something.
Sprint and T-Mobile both have knox on their 4.3 update, but neither have locked bootloaders.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
All knox does is count, unless I'm missing something.
Sprint and T-Mobile both have knox on their 4.3 update, but neither have locked bootloaders.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
+1
Hi all,
today I've updated my S6 (920F) to 5.1.1. It was a mint S6 32Gb carrier locked to MEO (Portugal) and I've updated it with odin with the TPH version (Portugal unlocked). Strange thing happened when I've went again after flashing I went to download mode to check knox and it has a awkward status: KNOX WARRANTY VOID: 1 (0x0000). So...I have 1 for Void but 0x0000 which is normaly not void. Can anyone tell me what happened?
thanks in advance
Anyone?!
Picture plz am not following what you have mentioned
Iloudsan said:
Picture plz am not following what you have mentioned
Click to expand...
Click to collapse
If you use Odin the phone will be 0x1, all root method do that too, even recovery.
And i like how xda advertise to have working recovery without tripping knox...
Quite expensive phone and still you troll people...
I know 1 thing through, knox tripped or not still a great phone, even through it still have too mjuch software installed that are NOT needed.
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