yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] testadeferro:
Reboot in download mode (vol - middle key power at same time) when you see a warning vol + and you will see
[Galaxy S 4 General] gorandroid:
There's no clue about that thing
[Galaxy S 4 General] Dan1909:
Then you're not on a firmware that has the KNOX bootloader.
[Galaxy S 4 General] gorandroid:
which means?

I can't check which one firmware is, the phone isn't with me ATM.
[Galaxy S 4 General] Dan1909:
Read some of the threads about this, they'll help you much more than I can.

In short... Only more recent firmwares include the KNOX bootloader, which is what causes the flags you were looking for. If you are on an earlier firmware than when KNOX was first included, then you won't have the system which causes the flags.
[Galaxy S 4 General] My1xT:
Galaxy S2 wont get knox anyway...
[Galaxy S 4 General] gorandroid:
so if i root s4 would that flag gets screw up?
[Galaxy S 4 General] Gillion:
Yes.
[Galaxy S 4 General] Dan1909:
Possibly not.

It depends what firmware you are on.
[Galaxy S 4 General] gorandroid:
alright i'll tell you when i get the phone. thanks anyway :)
[Galaxy S 4 General] admir83x:
Thanx man ;)
[Galaxy S 4 General] dpeddi:
Where is the research on latest posts? 95% of post here is OT. There is a Q/A thread for questions!

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 General] My1xT:
Simplistic Framwork Thread for Note 2 is even worse...
[Galaxy S 4 General] Mitsch79:
Hi,

i don't think that the bootloader get's locked when flashing a knox firmware. At least not during the flashing process.

I managed to flash I9505XXUEMJ5_I9505OXAEMJ5_DBT on my phone using odin. I instantly flashed CF-Root before

i startet the setup (oobe) of the phone. Unfortunately i found that my WiFi was broken when i finally bootet the phone,

so i quit setup and flashed above fw again. And again I instantly flashed CF-Root with the result that Wifi was broken again.

This time i went through the setup and had a functional phone without wifi.

Since it's nice to have wifi working, i decided to go back to I9505XXUBMGA_I9505OXABMGA_DBT. And guess what,

i flashed it without any problems.

I tried to flash I9505XXUEMJ5_I9505OXAEMJ5_DBT again, but this time i first setup the phone without rooting it. Wifi

was working and i received a Samsung Apps update and a security update that told me about SE Enforcing Android stuff.

I had this security update installed and afterwards had the knox bootloader.

So in my case, it looks like the bootloader is either installed or locked up by the security update not by the fw. Which

i my opinion means, that the knox flag is some bit inside the bootloader area, which is now protected. I don't think it's

an eFuse even if Sammy tells so (at least i hope so ;) )

P.S.: besides that Philz is now unable to format the /preload partition of the phone because access is denied. Maybe someone should have a look there?
[Galaxy S 4 General] jjnhl68:
This is very interesting! And don't tell me that your Knox is 0X0!?!?:confused:
[Galaxy S 4 General] JohnnyRebel:
Cw-root absolute give-away. But his statement is intriguing.
[Galaxy S 4 General] Braulio00:
Install oficial by odin and don't have 0x1 knox?
[Galaxy S 4 General] gerardo87:
As I know install official firmware by odin don't flag knox, only if you want try to downgrade your firmware to one with the old bootloader. Am I right?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 General] TappistRT:
Looking for guesses on my situation

I'll admit that I searched through many pages of this gigantic thread and didn't quite find my scenario, so here's my question:

As of about 3 days ago:

SCH-i545

Rooted stock via the motochopper exploit with VRAUMDK

Removed some bloatware, then incorrectly attempted to flash PacMan ROM, soft bricked my phone. (I installed the rom over the stock one without wiping first. D'oh!)

Yesterday:

Re-flashed stock recovery with Odin. Currently have root access but I haven't done anything else to the phone yet

DFU mode says "Samsung Official" and I have no binary counts

SO ...

If I were to do a quick factory restore and remove root and upgrade to 4.3: Would Knox trigger?

I'm sort of on the fence because on one hand I'd like to move forward with stock updates from now on, but on the other hand, I'm afraid about this whole warranty status thing in case my phone ever takes a poop.
[Galaxy S 4 General] worktorest:
I'm thankful i don't have to deal with the KNOX bootloader.

Do we have KNOX only when we update to the official 4.3 firmware on stock Samsung Touchwiz ROM?

How is it that so many people made the update when most people are on custom ROMs?
[Galaxy S 4 General] noodlecore:
A noob question here.

By flashing latest stock kernel, will it update with a new bootloader (knox) as well? TQ
[Galaxy S 4 General] jagnik:
how can i check my knox counter friends???
[Galaxy S 4 General] testadeferro:
Just enter in download mode and You will see.
[Galaxy S 4 General] noypi_101:
after entering download mode and checking knox status, how do you exit download mode?
[Galaxy S 4 General] silverhunk:
no. Even 4.2.2 XXUD*** has knox bootloader like mine and 4.3 has advance knox security.

most people, who have just bought S4, update via ota to the latest firmware without knowing first the knox.

Its what happened to me :(
[Galaxy S 4 General] akadkaya:
exit with power button
[Galaxy S 4 General] worktorest:
I just booted into Download mode to check, and it seems nothing to do with KNOX showed up. Cheers.
[Galaxy S 4 General] HC4Life:
When u enter in Download Mode and press volume up u don't see information about the status of your device including knox?
[Galaxy S 4 General] worktorest:
I see the status of my device being custom and stuff, but nothing about KNOX showed up. I guess I'm on the old bootloader then.
[Galaxy S 4 General] bungadudu:
Cool research thread! :banghead:
[Galaxy S 4 General] clonednull:
yes and the result of the research is:

1. people are too lazy to use the search function

2. people flash everything without even thinking before doing (better ask afterwards)

3. people like bashing samsung

...well nothing new here :silly:
[Galaxy S 4 General] peepooh:
MODEM

HELLO, what about if I downgrade the modem? Can it also trigger the knox flag?
[Galaxy S 4 General] :
There's still a q/a for this

[True Friendship doesn't exist]
[Galaxy S 4 General] lgkahn:
not lucky smart.. you should never flash a firmware without waiting for others (dumber than you) and find out what it entails and what the new bootloader does. Also you should have ota and all firmware update programs frozen or better yet removed from system/app like me if you are rooted. That way you can control when the firmware updates.. I guess if you keep your phone completely stock and unrooted than "lucky" may be appropriate as you are playing russian roulete with when the phone gets updated and you are at the mercy of the carriers. But in this case why not just use iphone if you are not rooting and tweeking phone?

---------- Post added at 02:34 PM ---------- Previous post was at 02:22 PM ----------

that is not true.. not being able to go back to older firmware is not the same as being able to do anything you want.
[Galaxy S 4 General] Simonetti2011:
Why would you want to go back to old firmware? Hoping it will clear the KNOX flag?! hahahahahahaha!
[Galaxy S 4 General] Biune:
KNOX is a solution for companies, home users are not the target here, reade more > samsung.com/global/business/mobile/solution/security/samsung-knox

Samsung official stated on Twitter that flag DOES NOT result warranty loss.

Only the flag with stock rom installed results warranty loss. So you can just install branded rom b4 sending the phone to repair.
[Galaxy S 4 General] Braulio00:
Only the flag with stock ROM installed resulta warranty loss? The flag (1) until now not have the solution
[Galaxy S 4 General] chubby65:
Don't believe everything Samsung tells you mate

Their nothing but sneaky lying bastards
[Galaxy S 4 General] Mitsch79:
Exactly that's what i'm telling you.

1. Flashed I9505XXUEMJ5_I9505OXAEMJ5_DBT which is a knox firmware

2. Flashed CF-Root before oobe => no Wifi but no knox flag at all <= this would have triggered knox if it were in place

3. Flashed I9505XXUEMJ5_I9505OXAEMJ5_DBT which is a knox firmware

4. Flashed CF-Root before oobe => no Wifi but no knox flag at all <= this would have triggered knox if it were in place

5. Flashed I9505XXUBMGA_I9505OXABMGA_DBT

6. Flashed I9505XXUEMJ5_I9505OXAEMJ5_DBT which is a knox firmware

7. Went through oobe

8. Installed security update which came by ota => bootloader locked and knox flag appears knox 0x0

9. Flashed CF-Root => knox 0x1

So, the firmware is not causing the bootloader lock and knox flag to appear, but the ota security update.

Which makes me believe that this knox flag thingy is software or at least stored somewhere inside the now

locked bootloader part instead of being an efuse.

Greetz
[Galaxy S 4 General] paamet:
[MENTION=4061944]Mitch[/MENTION]

This is useful! Can anyone confirm? How is bootloader locked...technically spraking?
[Galaxy S 4 General] Ivymike52:
i know that knox is not an efuse... it told me a Samsung's technical
[Galaxy S 4 General] kaalalto:
At least this topic became again a search one ! So that means KNOX flag is simply some bits stored somewhere ? Does it help us if we want to flash previous non-KNOX versions of the bootloader ?
[Galaxy S 4 General] Braulio00:
http://xdaforums.com/showthread.php?t=2504258

It's a good news. If it's true
[Galaxy S 4 General] BlueChris:
Seems true
[Galaxy S 4 General] Fishweb74:
Hello, I have 0x1 Knox and the counter at 20 ! I did the upgrade to version MJ7 ITV, but I had many problems and the binary remained unofficial, I did downgrade to MH8 rooted triangle away and I was able to reset the counter 20 to 0 ! the binary is official and everything works perfectly even if the flag is always 0x1 Knox, now I installed version MHB official ITV! sorry for my bad english
[Galaxy S 4 General] kakyyabata:
Samsung KNOX uses systematic security checks to ensure that only valid kernels are used. First, in the hardware, the Primary Boot Loader verifies the integrity of the Secondary Boot Loader 1, by authenticating its signature using a PKI certificate. Similarly, the Secondary Boot Loader 1 verifies the integrity of the Secondary Boot Loader 2, and the Secondary Boot Loader 2 verifies the integrity of the Android Boot Loader. The Android Boot Loader loads only a Samsung-authorized kernel, which has a Samsung certificate as its Root-of-Trust

Source https://www.samsungknox.com/overview/technical-details
[Galaxy S 4 General] My1xT:
Then we simply need to replace all 4 bootloaders before flashing sth. else...

Gesendet von meinem GT-P3110 mit Tapatalk 4 Beta
[Galaxy S 4 General] xaaronx:
There was another thread about some technician guy resetting someones 0x1 to 0x0, just throwing out an idea that maybe the eFuse register address could be changed to an efuse that's not blown, and that's how it could be... semi-reset?
[Galaxy S 4 General] :
Yeah u tell me when you succeed this so far we need to be able to reflash all bootloaders since if u want to go back it won't update the bl (if not necessary)

[True Friendship doesn't exist]
[Galaxy S 4 General] taltalon:
Guys,

Per this post it seems that ODIN is capable of flashing KNOX stock firmware - am i correct here?

lets say you have a KNOX Stock firmware (stock no root) installed. a newer one is out from another region - can you flash it without breaking KNOX. - again no root - just plain stock firmware. Can someone respond on this one?

Thanks

tal
[Galaxy S 4 General] wPatriot:
I wouldn't do that if I were you. It will still pretty much lock your bootloader, it just won't display the knox warranty flag.
[Galaxy S 4 General] spinky360:
Yeah ! Thats normal! but to see if you ca reset knox warranty
[Galaxy S 4 General] kurtisuk:
Expecting my S4 back tomorrow from repair at Anovo (samsung repair), just hoping they havent updated my software..... Fingers crossed!
[Galaxy S 4 General] theq86:
I advise you to NOT DO THIS.

The bootloader is signed and the signature is checked by a lower level component. If you change anything in the bootloader binary the signature is broken. Worst case would be a dead phone.
[Galaxy S 4 General] spinky360:
I have insurance :) this explains all
[Galaxy S 4 General] chickentuna:
Yep. Messing with the bootloader can cause serious damage. Don't do it unless you know the consequences or you'll end up with a shiny paper weight.

EDIT: Seems like the poster has an insurance, carry on then. I wish you luck!
[Galaxy S 4 General] ValenteL:
But... what is KNOX?

http://www.samsung.com/global/business/mobile/solution/security/samsung-knox

And: http://www.sammobile.com/2013/09/23...t-seems-to-prep-the-device-for-use-with-knox/
[Galaxy S 4 General] spinky360:
We know already :)
[Galaxy S 4 General] theq86:
Here some technical information about knox.

https://www.samsungknox.com/overview/technical-details

It seems, that Knox bootloader also verifies the kernel image before it loads it. This would mean you cannot install a custom kernel or custom recovery without triggering the warranty void flag.

Very hard to break
[Galaxy S 4 General] muamers:
I really dont get it...you buy a phone but you dont own it (almost). Its like you buy a PC and if you install Ubuntu on it (or any other OS) your warranty is woid. So whats the point? Forcing someone to use the Samsung TW that is full of crap that slows down the system?

Whats the next step? Maybe we will later be forced to use a system full of adds so Samsung can get more money?

Or Samsung wants to transfer the phones to something like an iPhone, locked down for everything.

I know i can always buy another phone but thats not anymore the Android (comunity) that i remember...i use Linux because of my freedome to do what i want and use what i want and not to be forced for anything.

Maybe the future is Ubuntu mobile OS.
[Galaxy S 4 General] LyuboA:
If knox down site is only warranty and not been able to downgrade to non knox firmware I can live with that but I think that this is just first step to one more secure non modified system which will make samsung devices useless to us

Send via I9505 using XDA Premium
[Galaxy S 4 General] spinky360:
How I was saying. We are to small for this big "game"
[Galaxy S 4 General] ValenteL:
Deleted. Sorry!
[Galaxy S 4 General] arovik:
Anyone know if the new builds (after dmh8) fixes this problem?
[Galaxy S 4 General] Daagen:
It's not a problem, it's a feature :cyclops:
[Galaxy S 4 General] arovik:
I'm thinking of all of us who reflashed original firmware and got 0x1 on the know warranty counter...
[Galaxy S 4 General] difyel:
Imho we need to mobilize the media to our cause , some articles about how samsung is becoming another control freak ,creating a bad but truthful vibe around samsung products will certainty make them reconsider this cracking down on our liberty .

Sent From my Gt-i9505
[Galaxy S 4 General] Shebee:
Mine says 0x30... do I have Knox firmware or not?
[Galaxy S 4 General] xtrustkillx:
I believe that there will be knox free leak
[Galaxy S 4 General] chickentuna:
Does it say KNOX WARRANTY VOID? If not then no you don't have a knox enabled firmware
[Galaxy S 4 General] farfrmnormal:
Removed question and posted in proper thread
[Galaxy S 4 General] js8:
+1 On this question :)
[Galaxy S 4 General] nilezon:
Please, this is not a Q&A thread.
[Galaxy S 4 General] testadeferro:
Well people just received my s4 from warranty repair.

Knox flag was 0x1 and my screen membrane was Brocken. They replace the screen without charges.

I asked service from Samsung and they told me that the flag isn't mean of warranty void at all.

Only Knox will not able to run anymore.

I asked why and if it was reversible and the guy told no. And no further explanations after I insisted with him.
[Galaxy S 4 General] chickentuna:
Well that's good news. I just hope that it's the same here in my country. I haven't triggered the flag yet bec. I'm still on the old bootloader. But it's good to know that they're still giving warranties even if the knox state was 0x1
[Galaxy S 4 General] js8:
Thank you, you are correct. I thought perhaps since 50% of the posts are questions and answers that the thread title had been superseded :) Perhaps your pedantry will nudge it back in line.
[Galaxy S 4 General] Adnan1973:
http://xdaforums.com/showthread.php?t=2504258
[Galaxy S 4 General] js8:
FWIW - I was on Djembey's Pre-Rooted Stock Odexed Full MI8 (which included the Knox Bootloader). I had flashed the MI8 ROM with Odin and Knox was 0x0. Been running it for several weeks and it was great - fast, smooth and good battery life.

I just flashed Djembey's Pre-Rooted Stock Odexed Full MJ7 with Odin 3.04 and it is still Knox 0x0. Xposed Framework and Installer are active. Sound and WiFi work fine from flash, without any mods. [[ As always, many thanks to [MENTION=4398524]DjeMBeY[/MENTION] ]]

[MENTION=5267414]taltalon[/MENTION] - fyi. Not exactly what you asked, but close.
[Galaxy S 4 General] testadeferro:
I will post there.

That´s a bit contraditory.
[Galaxy S 4 General] bungadudu:
So according to that topic Samsung technicians use a riff box and an ort jtag to reset the KNOX counter.

So the knox counter can be reset! :eek::sly::cool:

Can anybody test this?
[Galaxy S 4 General] jossilint:
thread too long, but on short that even if that Knox thing is 0x1 i still can install CWM and Cyanogenmod, SlimRom etc...? it is just for warranty and for some special Knox security purpose? am i right?
[Galaxy S 4 General] Adnan1973:
right
[Galaxy S 4 General] gorandroid:
Hey.me again. The firmware is I9505XXUEMJ5

Is it the right one?

Sent from my Galaxy S2 powered by NeatROM
[Galaxy S 4 General] testadeferro:
No. You have mj7.
[Galaxy S 4 General] gorandroid:
What do you mean? Lol. It's mj5

Sent from my Galaxy S2 powered by NeatROM
[Galaxy S 4 General] .NetRolller 3D:
Apparently my RPMB theory is right then.

We know so far:

-Samsung can reset the flag without altering any hardware.

-The flag is in the eMMC.

-Apparently not in either the Boot or User partition areas.

-The flag is not a Samsung extension to eMMC, as some Qualcomm S4s have Toshiba eMMCs.

That leaves only RPMB, or unpartitioned boot or user space, both moddable.

Do we have decrypted bootloader images to analyze?
[Galaxy S 4 General] jossilint:
Thanks that is all i needed to know. I dont understand why so much fuzz around this, if you want keep warranty/Knox feature then stay on original rom or you want use custom rom then blow this Knox to kingdom come.
[Galaxy S 4 General] lmerega:
The problem is when you would like to root to obtain normal features (i.e. Screen Recording) and this trig your knox flag...

I don't care about cooking or "made home" kernels, I do need root...

And this triggers Knox :(
[Galaxy S 4 General] Ugly-051:
It makes perfect sense to securitize corporate devices in this way and Knox looks a brilliant solution. But rolling this out to public devices is un-reasonable and I’m sure Samsung are going to loose custom for this, unless they of course get the business side of things in like BES users then it may work in their favour.

This is my first disappointment of Samsung devices, only had my GS4 for a few months.
[Galaxy S 4 General] bvhoesel:
Odin flash did not trap knox flags

OK. Don't shoot the messenger. I do not know how to prove it beyond any doubt but the next story is really true!

I had a CF-auto-Root'ed GT-I9505. Fiddling with Triangle Away and Voodoo OTA Rootkeeper I managed in the past to get several OTA's installed. Two days ago (in a wild mood ??) I decided to do an update check. An update was available (43MB) and I installed it. Yesterday I noticed an error on Titanium backup and realized I lost root. Since I never had problems with CF-auto-Root I ran it (latest version) again. But this time it did not work. The flash did do something but did not complete successfully. As a result after the reboot a yellow triangle with the the message 'Firmware upgrade encountered a issue. Please select recovery mode in Kies and try again'. Trying Kies did not do anything. I could not install or recover a firmware. Probably (obviously?) since it root 'upgrade was not done via Kies.

I did notice the knox messages in the recovery screen which I had not seen before Both were at 0x0. Reading various threads about knox, odin and unbricking I was sure that my unbricking via odin would trap the knox flag(s). But what else could be done so I was at peace with this and I went along with a odin flash.

Since I did know know on what firmware version I originally was I search what was available for my region what I found was PHN-I9505XXUDMHB-20130922121848 which is supposed to be the latest Dutch version available. Using odin 3.04 I flashed this version. And to my surprise I have a 'brand new' phone in terms of kernel and rom. I am back on the official Samsung kernel and rom (was custom before) and the knox flags are both still on 0x0.

Checking for an update it states I have the newest updates already. This morning it said I could not update because of a modded phone.

It looks I am back on the situation from yesterday (including all user data, no data was lost in the odin flash!). Latest updates but no root. I am hesitant to try the CF-auto-Root again. For now I am going to try to live without root :crying:.
[Galaxy S 4 General] My1xT:
try Kingo root, works pretty nice, even when not yet perfectly...
[Galaxy S 4 General] code72:
A root method without Knox increase with instructions:

http://www.youtube.com/watch?v=SbynuhV_7PU
[Galaxy S 4 General] mrm1:
Yeh but there is some concern about what it is connecting too when installed

Sent from my GT-I9505
[Galaxy S 4 General] My1xT:
can somebody maybe reset his/her n3 and use a network logging too to check what it does.

but Port 80 looks like a website...
[Galaxy S 4 General] bungadudu:
Ok, so why can't someone take a look at that exe, remove the dubious code and repackege the whole thing in a safe and easy to use app?
[Galaxy S 4 General] JohnnyRebel:
Copying your hidden phone data to make perfect chinese knockoffs.
[Galaxy S 4 General] galnet:
KNOX IS NOT AN eFUSE

As I thought knox is not an eFUSE... Or else this WOULDN'T be possible...
[Galaxy S 4 General] Braulio00:
This? I can't see well, I have i9500 and the knox boot is different, I only have the first 3 lines more warranty bit 1.. Don't have 0x1 or else. Your bootloader have a lot of things
[Galaxy S 4 General] Bessagabriel:
The "KNOX WARRANTY VOID" is set to 0xfffffffffc
[Galaxy S 4 General] Braulio00:
In my GT i9500 have warranty bit 1. Only this! Product name, current status and system status.
[Galaxy S 4 General] galnet:
On the i9500 I believe you don't have to worry about the Knox Bootloader at present. The I9505 has these lines in bootloader and normally 0x0 or 0x1 for Knox Warranty... This picture shows that the Knox Warranty part can be changed via Software alone.
[Galaxy S 4 General] Braulio00:
I install the 4.3 by odin like wanam says, I don't know anything about knox when I installed, my boot only have warranty bit in download mode and only show '1' don't have 0x1 or something like your picture, I agree with you, this is not a efuse.
[Galaxy S 4 General] Adnan1973:
Flash only tz.mbn from old rom (with old bootloader) and receive what is in the picture
[Galaxy S 4 General] galnet:
Yes, but it shows that the Flag is able to be re-wrote meaning that it can't be an eFuse.
[Galaxy S 4 General] Adnan1973:
Yes I think so, if it can be damaged in this way
[Galaxy S 4 General] galnet:
Can somebody who is on 4.3 I9505 without 0x1 tipped.. IE you still have 0x0 please dump a .pit file using Heimdall and upload it here please.
[Galaxy S 4 General] Obagleyfreer:
How do we do that? I have an i9505 at home which is still on old bootloader.
[Galaxy S 4 General] Braulio00:
I think he says the new bootloader but without the flag for comparison. Compare flag 0x1 with 0x0
[Galaxy S 4 General] chickentuna:
Via heimdall. There is an option there to extract pit files from your device. At least it's there on my mac. I can't do this as I'm on an old bootloader. So my pit is useless.