Database Users

[Q] KNOX and binary counter

Hi! I know if I flash a firmware or a root file,it will set KNOX to 0x1.Ok,but I will buy the phone without warranty.I just want to know one thing
Will flashing a firmware bring up a yellow triangle?And can it be removed via Triangle Away? Or will it show anything else beside the 0x1 KNOX?

Please, take anything you want just don't give me the triangle, the dreaded triangle of death.... haha
I don't know if the n3 has a triangle but I do know that chainfire the author said his tools do not work on knox devices. So no triangle away.

I just rooted my Note 3, no triangle
Sent from my SM-N9005 using Tapatalk 4

Sorry for stupid question guys but as far as I know if KNOX is set to 0x1 it can't be restored and your warranty is void for all the time,right?

Simonna said:
Sorry for stupid question guys but as far as I know if KNOX is set to 0x1 it can't be restored and your warranty is void for all the time,right?
Click to expand...
Click to collapse
Yup, speculation is that there is a type of efuse that once blown is irreversible. And yes the KNOX warranty is void. Now whether or not a carrier representative (if carrier branded) will know to check this flag and deny you is another matter.

Thanks @Pliind

This knox warranty.
Is it triggered if a official firmware is flashed via odin?
Like i have an 02UK n3.
With my s4 i just changed CSC flashed BTU rom and viola.
Doing this on n3 voids that warranty?

So I wanna get this straight! When I get my Note 3 from Verizon, if I deny Knox on my first boot I will lose my warranty. Which I am OK with, but can I flash a custom recovery and ROM and root with no issues??
Sent from my SCH-I535 using Tapatalk 2

harosxcomp170 said:
So I wanna get this straight! When I get my Note 3 from Verizon, if I deny Knox on my first boot I will lose my warranty. Which I am OK with, but can I flash a custom recovery and ROM and root with no issues??
Click to expand...
Click to collapse
No. Denying a Knox prompt is the least of our problems with Verizon. In order to flash a custom ROM, we have to unlock the bootloader or get around it with Loki or SafeStrap in order to install a custom recovery.
It is possible to root a phone with a fully locked bootloader and without a custom recovery, however (like the S4)

docnok63 said:
No. Denying a Knox prompt is the least of our problems with Verizon. In order to flash a custom ROM, we have to unlock the bootloader or get around it with Loki or SafeStrap in order to install a custom recovery.
It is possible to root a phone with a fully locked bootloader and without a custom recovery, however (like the S4)
Click to expand...
Click to collapse
Hmm really considering just keeping my S3 now. So if I purchased a international note 3 from eBay I would have a unlocked bootloader but wouldn't be able to receive 4G data from Verizon in the USA? Right?
Sent from my SCH-I535 using Tapatalk 2

harosxcomp170 said:
Hmm really considering just keeping my S3 now. So if I purchased a international note 3 from eBay I would have a unlocked bootloader but wouldn't be able to receive 4G data from Verizon in the USA? Right?
Click to expand...
Click to collapse
Correct, If having an unlocked bootloader is crucial to you, I'd wait until you see what the development community comes up with on the initial release of Note 3's or just wait to buy the Developer Edition 3-8 weeks later. You know that variant will have an unlocked bootloader, but you'll also have to pay full price.

docnok63 said:
No. Denying a Knox prompt is the least of our problems with Verizon. In order to flash a custom ROM, we have to unlock the bootloader or get around it with Loki or SafeStrap in order to install a custom recovery.
It is possible to root a phone with a fully locked bootloader and without a custom recovery, however (like the S4)
Click to expand...
Click to collapse
Well, Loki is out of the question, it is not compatible.

designgears said:
Well, Loki is out of the question, it is not compatible.
Click to expand...
Click to collapse
Not with locked bootloader, no. But there's a chance it could be modified if we get that magic key.

I will pretty much go with the stock ROM and a kernel with CWM and root.I do not want to install CM or AOKP,because I will loose the function,like S Pen menu,etc...Maybe I will install a custom ROM based on stock

docnok63 said:
Not with locked bootloader, no. But there's a chance it could be modified if we get that magic key.
Click to expand...
Click to collapse
Nope, it doesn't work with the S800, already confirmed with jcase.

Root de la Vega (doesnt trigger knox) possible to port N900/N9005

UPDATED POST:
Hello,
As @Dumbo53 has mentioned below posts, there is a root method by the developer @designgears and it seems that this root method does NOT trigger the knox flag.
Unfortunately, it is just for the AT&T Note 3 devices.
Maybe someone could port this root method for our international N900 and N9005 model devices?
Root de la Vega:
http://forum.xda-developers.com/showthread.php?t=2474422
----------------------------------------------------
Hello there,
I wanted to share something from Chainfire's Auto-Root thread.
Chainfire has mentioned:
Using this root method sets current binary and system status to custom. Additionally, it will also trigger the KNOX warranty void status.
This device store the traditional flash counter. Nor is is possible with Triangle Away to reset the current binary status. You will need to flash a stock kernel and stock recovery to reset the binary status.
The KNOX warranty status change is permanent, and a service center may deny warranty based on this flag - even if the other flags are reset correctly. The KNOX flag being tripped may also prevent certain Samsung KNOX features from working (enterprise security features).
If this is something you care about, use a root method not based on custom kernels or recoveries, like a modified system partition. These are possible, but I don't personally make them, so look around!
Click to expand...
Click to collapse
So my question is simple:
Is there any talented developer who can look at the system partition on the devices N900/9005 and somehow to look if he can modify it to root without triggering the knox counter. Iaw chainfire's post, it seems to be possible, but we need a talented developer to look for this
I would be really so happy, if it can be done this way...

No because if you do anything you alter the md5 checksum m8 and knox watch this
Sent from my SM-N9005 using Tapatalk 4

BlueChris said:
No because if you do anything you alter the md5 checksum m8 and knox watch this
Sent from my SM-N9005 using Tapatalk 4
Click to expand...
Click to collapse
I was talking according to Chainfire, dude. He just showed us that there could "may be" a way to root without knox would recognise this.
I think may be knox watches only the bootloader and recovery situation (if it is custom or official).
Chainfire's root method includes to flash first insecure recovery and after root flashes back the official recovery. During this process knox recognise the shortly time with the insecure recovery and the counter goes to 0x1. But iaw Chainfire's post, i think if someone could root without touching the recovery or kernel, it could be possible not to trigger the knox during the root process.

I don't think we will have a way to bypass it. I think once you get root it will still trigger it.
Funny how this is something from an Android device and not an iDevice.
Guess Samsung got tired of fixing devices after someone oc the hell out of it!
Sent from my SM-N9005 using XDA Premium 4 mobile app

There already is a root method that doesn't trigger the Knox flag by designgears, but as of now only for At&t Note 3 (Root de la Vega). It however only gives root, not a custom recovery. There are already people begging him to port it to other devices and he seems to be willing to do them one by one.
Sent from my SAMSUNG-SGH-I317

Dumbo53 said:
There already is a root method that doesn't trigger the Knox flag by designgears, but as of now only for At&t Note 3 (Root de la Vega). It however only gives root, not a custom recovery. There are already people begging him to port it to other devices and he seems to be willing to do them one by one.
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
Thanks mate, i will also look to his thread and beg him for n900

Sounds promising. Don't really need a custom recovery thanks to xposed.
Sent from my SM-N9005 now Free

Knox problem thanks (lovelesss)

we are waiting for n900 please

n900 I want to wait for the Root de la Vega.

What about N9005?

vinokirk said:
What about N9005?
Click to expand...
Click to collapse
+1
Sent from my SM-N9005 using Tapatalk 4

vinokirk said:
What about N9005?
Click to expand...
Click to collapse
Yeah I can add N9005 also as request on this topic.
Changing the subject of this thread just a sec

I don't have any information showing Knox flag in Odin mode, Exynos SM-N900. Does this mean my phone doesn't have this flag?

[Q] i9505 "clean" stock Android

Hello guys,
I’m aware this has been discussed many times before, but this information is "old" most of the times. My Galaxy S4 (i9505) is now running stock Touchwiz Android 4.3 (i9505XXUEMJ7).
What I want to do is the following: flash my phone to a i9505G, but with some research I've found that that isn't possible. Are there any other ways to get the clean i9505G 4.4.2 ROM without any changes (like root) on my i9505? (I know there are much custom ROM's, but if possible I'd like to keep it "stock".)
Since I'm running 4.3 with Knox I'm a little scared about the Knox 0x1 status, is this already "resolved" or will this still be a problem?
Thanks.

Broodplank's AOSP rom is the way to go:
http://forum.xda-developers.com/showthread.php?t=2397511
You still need to flash a custom recovery to flash it, though. I recommend CWM. Simply works.

tsphere said:
Broodplank's AOSP rom is the way to go:
http://forum.xda-developers.com/showthread.php?t=2397511
You still need to flash a custom recovery to flash it, though. I recommend CWM. Simply works.
Click to expand...
Click to collapse
Thanks for your reply. Rooting and flashing a custom recovery shouldn't be a problem, however I'm still a little worried about Knox, there simply isn't a way to reset it after it goes to 0x1?
The HTC One can be "changed" into a HTC One Google Edition: http://forum.xda-developers.com/showthread.php?t=2358781
But as far as I can tell this isn't possible for the Galaxy S4?

As far as i seen, once you flash something with odin, your knox flag gets changed. However it's not clear to me whether it changes the warranty actually...

tsphere said:
As far as i seen, once you flash something with odin, your knox flag gets changed. However it's not clear to me whether it changes the warranty actually...
Click to expand...
Click to collapse
It's not just the warrenty I'm worried about. If I want to sell the phone later I want it to be fully working, I assume with Knox 0x1 Knox isn't working anymore?

JoeyLe said:
Thanks for your reply. Rooting and flashing a custom recovery shouldn't be a problem, however I'm still a little worried about Knox, there simply isn't a way to reset it after it goes to 0x1?
The HTC One can be "changed" into a HTC One Google Edition: http://forum.xda-developers.com/showthread.php?t=2358781
But as far as I can tell this isn't possible for the Galaxy S4?
Click to expand...
Click to collapse
In theory every non G device can be converted into a G device if the hardware model is the same but in practice is not always accomplished 100%. The problem here is Knox, for waht I understand it has 2 layers: The knox bloatware that comes stock on sammys ROM and the off rom portion included in the bootloader. The bootloader is basically what the system loads up first
. so it can't bypassed. So to kkep it simple, if you flash ANYTHING (not sure however if re flashing the stock original ROM activates the flag) on the knox bootloader (AKA: new bootloader) the ''flag'' will change to 0x1, this flag is called eFuse so basically 0x1 means is burned and it can't be changed ANYWAY. If you don't plan to use your phone for work you shouldn't care about the flag.
For more information you can check this thread
http://forum.xda-developers.com/showthread.php?t=2447832

JoeyLe said:
It's not just the warrenty I'm worried about. If I want to sell the phone later I want it to be fully working, I assume with Knox 0x1 Knox isn't working anymore?
Click to expand...
Click to collapse
1. It isn't clear if Knox 0x1 voids warranty or not.
2. If you have Knox 0x1 your phone will work fine, but you won't be able to use Knox security enhancements.
3. You can't convert the 9505 to the 9505G, the Google Play edition has different bootloader, modem and pit partition.
Enviado do meu Xposed Galaxy S4 4G LTE

dclarkg said:
In theory every non G device can be converted into a G device if the hardware model is the same but in practice is not always accomplished 100%. The problem here is Knox, for waht I understand it has 2 layers: The knox bloatware that comes stock on sammys ROM and the off rom portion included in the bootloader. The bootloader is basically what the system loads up first
. so it can't bypassed. So to kkep it simple, if you flash ANYTHING (not sure however if re flashing the stock original ROM activates the flag) on the knox bootloader (AKA: new bootloader) the ''flag'' will change to 0x1, this flag is called eFuse so basically 0x1 means is burned and it can't be changed ANYWAY. If you don't plan to use your phone for work you shouldn't care about the flag.
For more information you can check this thread
http://forum.xda-developers.com/showthread.php?t=2447832
Click to expand...
Click to collapse
Thank you very much! That was very interesting to read. I personally don't care about Knox, all the Samsung bloatware is the main reason I want to have stock Android on my S4.

dandroid13 said:
1. It isn't clear if Knox 0x1 voids warranty or not.
2. If you have Knox 0x1 your phone will work fine, but you won't be able to use Knox security enhancements.
3. You can't convert the 9505 to the 9505G, the Google Play edition has different bootloader, modem and pit partition.
Enviado do meu Xposed Galaxy S4 4G LTE
Click to expand...
Click to collapse
Thanks for the information. I see there are many custom roms which are very close to stock Android, that should be fine as well.

JoeyLe said:
Thanks for the information. I see there are many custom roms which are very close to stock Android, that should be fine as well.
Click to expand...
Click to collapse
Sure, but the 4.4 roms (Google Play) have one main issue, random reboots.

[Q] Bootloader

I am curious what the difference between a dev vzw n3 and a retail with Knox tripped 0x1?
Sent from my SM-N900V using Tapatalk

Imarik81 said:
I am curious what the difference between a dev vzw n3 and a retail with Knox tripped 0x1?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
A retail with Knox tripped means the owner either did some unsupported mod or used an old root method and the warranty is now void. It does not mean the bootloader is unlocked.
A Dev Note 3 has Knox tripped but can be bootloader unlocked.
Don't get a Knox tripped retail.

changt34x said:
A retail with Knox tripped means the owner either did some unsupported mod or used an old root method and the warranty is now void. It does not mean the bootloader is unlocked.
A Dev Note 3 has Knox tripped but can be bootloader unlocked.
Don't get a Knox tripped retail.
Click to expand...
Click to collapse
Not exactly but close...the Dev Note 3 does not have knox tripped out of the box. Once you flash anything custom in odin, then knox is tripped. However that is all irrelevant because there is no warranty anyway aside from a 1 yr on mechanical defects.

droidstyle said:
Not exactly but close...the Dev Note 3 does not have knox tripped out of the box. Once you flash anything custom in odin, then knox is tripped. However that is all irrelevant because there is no warranty anyway aside from a 1 yr on mechanical defects.
Click to expand...
Click to collapse
Well I tripped my Knox. It's not the end of the world. It does stink though. I'm running Eclipse right now but I'd love to check out Cm11. Is that possible?
Sent from my SM-N900V using Tapatalk

@lmarik81 - I think the pointed question you need to ask is:
"Suppose I want to intentionally blow my Knox warranty flag on my retail device - will the retail device become equivalent to a dev device at that time?"
I *think* the answer is "NO - you will still not be able to boot unsigned kernels."
But it would be better if someone with a blown Knox retail device can validate the above with a "yeah, I tried that on my (blown Knox) retail device and it didn't work" ... either that or refute that assertion from contrary experience.
Direct first-person experience is very desirable here.
[Edit] @lmarik81 - mind saying how you blew yours? Flashing the recovery partition, or something else?
.

Is it possible to hard brick my device by doing this? I'm tempted to try if I can just restore back with worst case 0x2.
Sent from my SM-N900V using Tapatalk

I had the case off the back of my phone and some how the battery came out as I was flashing either a rom or recovery and when I turned the phone back on I went into recovery and it tripped.
Sent from my SM-N900V using Tapatalk

If you are rooted you can use the Triangle Away app and reset your counter.. works for me

Custom recovery and KNOX 0X0 ??

Now that we have Root without KNOX problems.. Will it ever be possible to flash custom Recovery / Roms too... And still have KNOX 0x0 ?

You can use Safestrap Recovery
Please read carefully before taking any step

What version of Safestrap revovery to use on the F model ?

joeherlev said:
What version of Safestrap revovery to use on the F model ?
Click to expand...
Click to collapse
Safestrap is only for ATT and Verizon devices afaik, it probably does not work on the G900F.

Okay.. So I wont try.. Will it ever be possible to have custom recovery for F model then without KNOX 0x1 ?

joeherlev said:
Okay.. So I wont try.. Will it ever be possible to have custom recovery for F model then without KNOX 0x1 ?
Click to expand...
Click to collapse
Not atm, KNOX is impossible to hack as security is iron clad

gee2012 said:
Not atm, KNOX is impossible to hack as security is iron clad
Click to expand...
Click to collapse
But how can it be done on models with locked bootloader then ?

joeherlev said:
But how can it be done on models with locked bootloader then ?
Click to expand...
Click to collapse
Safestrap creates virtual partitions afaik and writes data on those, look here http://forum.xda-developers.com/showthread.php?t=2793891 for more info.

joeherlev said:
Now that we have Root without KNOX problems.. Will it ever be possible to flash custom Recovery / Roms too... And still have KNOX 0x0 ?
Click to expand...
Click to collapse
Sure. Anyone who says otherwise is exercising a certain failure of imagination.
That however doesn't mean that it is easy. And you certainly can't put a fixed time frame on it. A few weeks ago we couldn't root the locked bootloaders on a Verizon or ATT phone. Then Pinkie Pie discovered the CVE-2014-3153 vulnerability and Geohot developed the towel root exploit on that doorstep.
And if you haven't been following the forums here recently we've seen some exciting work and success in not only downgrading a device from Kitkat to Jellybean but also undoing the Knox flag in the process. Something that Samsung told us was impossible. But now we find that Samsung was playing fast and loose with the truth again. They told us that the Knox qfuse was a permanent and irreversible OTP. But it turns out that qfuses, or some of the qfuses at least can actually be reset if we are creative.
Samsung probably does this to make their own code development easier. Certainly it's easier for them to reset a Knox flag than have to replace a motherboard when factory refurbishing devices. The lesson in all of this is to take pronouncements that something is impossible with a grain of salt. All is not always as it seems. Yes the day will come when we can flash a custom recovery or kernel and still have a 0x0 Knox flag.
.